CN112738645A

CN112738645A - Method and apparatus for transmitting and receiving signal in multimedia system

Info

Publication number: CN112738645A
Application number: CN202011447415.5A
Authority: CN
Inventors: 梁贤九; 李炳大; 柳永善
Original assignee: Samsung Electronics Co Ltd; Industry Academic Cooperation Foundation of Kyonggi University
Current assignee: Samsung Electronics Co Ltd; Industry Academic Cooperation Foundation of Kyonggi University
Priority date: 2015-06-23
Filing date: 2016-06-23
Publication date: 2021-04-30
Anticipated expiration: 2036-06-23
Also published as: JP6728246B2; CN107787586A; KR102473346B1; CN107787586B; EP3314906A4; CN112738645B; JP2018524904A; KR20170000312A; KR20220165693A; KR102598237B1; EP3314906A1

Abstract

A method of operating a transmitting apparatus in a multimedia system is provided. The method comprises the following steps: a data unit of a multimedia service is transmitted comprising event information related to an event, wherein the event comprises a notification to an application indicating that an action is to be taken.

Description

Method and apparatus for transmitting and receiving signal in multimedia system

The invention is a divisional application of an invention patent application with the application number of 201680036782.1 and the application date of 2016.

Technical Field

The present disclosure relates to a method and apparatus for transmitting and receiving signals in a multimedia system. More particularly, the present disclosure relates to a method and apparatus for transmitting and receiving event information related to an event in a multimedia system.

Background

Multimedia services represent services such as session services (such as video telephony), streaming services (such as Video On Demand (VOD) services), multicast and broadcast services, and the like.

Real-time multimedia services may be classified into session services, interactive services, and streaming services based on the type of service. Real-time multimedia services can be classified into unicast, multicast and broadcast based on the number of users joining the real-time multimedia service.

Moving picture experts group-2transport stream (MPEG-2 TS) is a technology for transmitting multimedia content, and a typical transmission technology for transmitting a bit stream (a plurality of encoded video bit streams) multiplexing a plurality of broadcast programs in a transmission environment in which an error exists.

A Moving Picture Experts Group (MPEG) media transmission technique has been proposed as one of multimedia transmission techniques for supporting multimedia services based on the MPEG technique. The MPEG Media Transport (MMT) technology is a new technology for providing MPEG of various types of multimedia services through various terminals such as a Television (TV), a mobile device, and the like in various types of network environments. For example, MMT techniques may be applied to efficiently transmit complex content over heterogeneous networks. Here, the complex content means a collection of content having multimedia elements collected through video, audio, application, and the like. For example, the heterogeneous network may be a network including a broadcasting network, a mobile communication network, and the like.

In order to support an application service based on a hybrid transmission technology in which a broadcast network organically interacts with a communication network, signaling information needs to be provided, and thus, a terminal may receive data or files required to run the application service using the broadcast network or the communication network and identify and select an application service and data related to the application service.

Therefore, there is a need to transmit and receive signaling information for providing application services in a system using MMT technology.

The above information is presented merely as background information to aid in understanding the present disclosure. No determination is made as to whether any of the above is potentially applicable for the prior art in light of this disclosure, nor is an assertion made.

Disclosure of Invention

Technical problem

Aspects of the present disclosure address at least the above problems and/or disadvantages and provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide an apparatus and method for transmitting and receiving a signal in a multimedia system.

Another aspect of the present disclosure is to provide an apparatus and method for transmitting and receiving event information related to an event in a multimedia system.

Another aspect of the present disclosure is to provide an apparatus and method for providing event information related to an event together with a multimedia service in a multimedia system.

Technical scheme

According to an aspect of the present disclosure, there is provided a method of operating a transmitting apparatus in a multimedia system. The method comprises the following steps: a data unit of a multimedia service is transmitted comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, there is provided a method of operating a transmitting apparatus in a multimedia system. The operation method comprises the following steps: first information is sent indicating the presence of a data unit of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, a method of operating a receiving device in a multimedia system is provided. The method comprises the following steps: a data unit of a multimedia service is received comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, a method of operating a receiving device in a multimedia system is provided. The method comprises the following steps: first information is received indicating the presence of a data unit of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, there is provided a transmitting apparatus in a multimedia system. The transmission device includes: a transmitter configured to transmit a data packet of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, there is provided a transmitting apparatus in a multimedia system. The transmission device includes: a transmitter configured to transmit first information indicating the presence of a data unit of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, there is provided a receiving apparatus in a multimedia system. The receiving apparatus includes: a receiver configured to receive a data unit of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

According to another aspect of the present disclosure, there is provided a receiving apparatus in a multimedia system. The receiving apparatus includes: a receiver configured to receive first information indicating a presence of a data unit of a multimedia service comprising event information related to an event, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document, to the extent that the terms "includes" and "includes," along with their derivatives, mean that including but not limited to, the term "or" is inclusive, meaning and/or that the phrase "associated with …" and "associated therewith," along with its derivatives, may represent include, interconnect with …, contain, connect to or connect with …, couple to or couple with …, communicate with …, cooperate with …, interleave, concatenate, approximate, bind to or bind with …, have … property, etc., and the term "controller" means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware, or software, or some combination of at least two of the same. It will be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

Drawings

The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description when taken in conjunction with the accompanying drawings, in which:

fig. 1 schematically shows a layer structure of an MPEG Media Transport (MMT) system according to an embodiment of the present disclosure;

fig. 2 schematically illustrates a configuration of MMT payloads in an MMT system according to an embodiment of the present disclosure;

fig. 3 schematically illustrates a logical structure of an MMT packet (package) in the MMT system according to an embodiment of the present disclosure;

fig. 4 schematically shows an operation process of a terminal for running an application service in an MMT system according to an embodiment of the present disclosure;

fig. 5 schematically shows an internal structure of an apparatus for receiving information related to an application service in an MMT system according to an embodiment of the present disclosure;

fig. 6 schematically shows a process for processing event information based on MMT signaling messages in an MMT system according to an embodiment of the disclosure;

fig. 7 schematically shows a process for processing event information based on a Media Processing Unit (MPU) in an MMT system according to an embodiment of the present disclosure;

fig. 8 schematically shows an internal structure of a transmitting apparatus in an MMT system according to an embodiment of the present disclosure; and

fig. 9 schematically shows an internal structure of a receiving apparatus in an MMT system according to an embodiment of the present disclosure.

Throughout the drawings, it will be noted that like reference numerals are used to depict the same or similar elements, features and structures.

Detailed Description

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the written meaning, but are used only by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

Although ordinal numbers such as "first," "second," etc., will be used to describe various components, these components are not limited herein. These terms are only used to distinguish one component from another component. For example, a first component could be termed a second component, and, similarly, a second component could be termed a first component, without departing from the teachings of the present inventive concept. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, quantities, operations, components, elements, or combinations thereof, but do not preclude the presence or addition of one or more other features, quantities, operations, components, elements, or combinations thereof.

Terms used herein, including technical terms and scientific terms, have the same meaning as terms commonly understood by those skilled in the art, as long as the terms are not defined differently. It should be understood that terms defined in commonly used dictionaries have the same meaning as those defined in the relevant art.

According to various embodiments of the present disclosure, an electronic device may include communication functionality. For example, the electronic device may be a smart phone, a tablet computer (PC), a mobile phone, a video phone, an e-book reader, a desktop PC, a notebook PC, a netbook PC, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a moving picture experts group phase 1 or phase 2(MPEG-1 or MPEG-2) audio layer 3(MP3) player, a mobile medical device, a camera, a wearable device (e.g., a head-mounted device (HMD), an electronic garment, an electronic stand (electronic branch), an electronic necklace, an electronic accessory, an electronic tattoo, or a smart watch), and the like.

According to various embodiments of the present disclosure, an electronic device may be an intelligent home appliance having a communication function. The smart home appliance may be, for example, a television, a Digital Versatile Disc (DVD) player, audio, a refrigerator, an air conditioner, a vacuum cleaner, an oven, a microwave oven, a washing machine, a dryer, an air purifier, a set-top box, a television box (e.g., Samsung HomeSync)^TM、Apple TV^TMOr Google TV^TM) A game machine, an electronic dictionary, an electronic key, a camcorder, an electronic photo frame, etc.

According to various embodiments of the present disclosure, the electronic device may be a medical device (e.g., a Magnetic Resonance Angiography (MRA) device, a Magnetic Resonance Imaging (MRI) device, a Computed Tomography (CT) device, an imaging device, or an ultrasound device), a navigation device, a Global Positioning System (GPS) receiver, an Event Data Recorder (EDR), a Flight Data Recorder (FDR), an automotive infotainment device, a naval electronic device (e.g., naval navigation device, gyroscope, or compass), an avionic device, a security device, an industrial or consumer robot, or the like.

According to various embodiments of the present disclosure, the electronic device may be furniture, a part of a building/structure, an electronic board, an electronic signature receiving device, a projector, various measuring devices (e.g., water, electrical, gas, or electromagnetic waveform measuring devices), and/or the like that include a communication function.

According to various embodiments of the present disclosure, the electronic device may be any combination of the above devices. In addition, it is apparent to those of ordinary skill in the art that the electronic device according to the various embodiments of the present disclosure is not limited to the above-described device.

According to various embodiments of the present disclosure, a terminal may be an electronic device, for example.

According to various embodiments of the present disclosure, the transmitting device may be a service provider or a terminal.

According to various embodiments of the present disclosure, the receiving device may be a terminal or a service provider.

According to various embodiments of the present disclosure, the transmitting and receiving apparatus may be a terminal or a service provider.

According to various embodiments of the present disclosure, it will be assumed that the term terminal may be interchangeable with the terms Mobile Station (MS), wireless terminal, mobile device, User Equipment (UE), and the like.

Embodiments of the present disclosure propose an apparatus and method for transmitting and receiving signals in a multimedia system.

Embodiments of the present disclosure propose an apparatus and method for transmitting and receiving event information related to an event in a multimedia system.

Embodiments of the present disclosure propose an apparatus and method for providing event information related to an event together with a multimedia service in a multimedia system.

The apparatus and method proposed in the embodiments of the present disclosure may be applied to various communication systems, such as a Long Term Evolution (LTE) mobile communication system, an LTE-advanced (LTE-a) mobile communication system, a licensed-assisted access (LAA) -LTE mobile communication system, a High Speed Downlink Packet Access (HSDPA) mobile communication system, a High Speed Uplink Packet Access (HSUPA) mobile communication system, a High Rate Packet Data (HRPD) mobile communication system proposed in third generation partnership project 2(3GPP2), a wideband multiple access (CDMA) mobile communication system proposed in 3GPP2, a CDMA mobile communication system proposed in 3GPP2, a CDMA mobile communication system proposed in Code Division Multiple Access (CDMA) mobile communication system proposed in 3GPP 8926, a mobile communication system using a CDMA scheme, a mobile communication method, and a mobile communication system using a CDMA scheme, The Institute of Electrical and Electronics Engineers (IEEE) 802.16M communication system, IEEE802.16e communication system, Evolved Packet System (EPS), and mobile internet protocol (mobile IP) system, digital video broadcast-handheld (DVP-H) service such as mobile broadcast service (such as digital multimedia broadcasting, DMB) service, digital video broadcast-handheld (ATSC-M/H) service, advanced television system committee-mobile/handheld (DMB) service, and the like), and digital video broadcast system of Internet Protocol Television (IPTV), MPEG (moving picture experts group, MPEG) transmission system, and the like. MPEG media transport will be referred to herein as MMT.

The method and apparatus proposed in the embodiments of the present disclosure may be applied to an Advanced Television Systems Committee (ATSC) system based on the MMT scheme.

For convenience, in various embodiments of the present disclosure, it will be assumed that the multimedia system is based on the MMT scheme.

The MMT protocol (MMTP) defines an application layer protocol for transferring a transfer frame including an MMT Payload Format (PF) through an Internet Protocol (IP) network.

The MMT payload includes an MMT payload format and is designed to be efficiently delivered. MMTP defines an encapsulation format, transport protocol, and signaling message format to efficiently transport MPEG media data over heterogeneous IP networks.

MMT technology defines data models such as packages, assets (assets), and the like. The package represents independent content (such as a movie) and the assets represent logical entities that classify elements, such as images, voice, data, etc., included in the content. Here, one package may include a plurality of assets. For convenience, the term asset may be interchanged with the term MMT asset and the term package may be interchanged with the term MMT package.

A layer structure of an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 1.

Fig. 1 schematically shows a layer structure of an MMT system according to an embodiment of the present disclosure.

Referring to fig. 1, the layer structure of the MMT system configures a multimedia data packet and includes a media coding layer 110 transmitting the multimedia data packet, an encapsulation function layer 120, a delivery function layer 130, a transport protocol layer 140, an IP layer 150, and a control function layer 100. The term encapsulation functional layer may be interchanged with the term layer E, the term transfer functional layer may be interchanged with the term layer D, and the term control functional layer may be interchanged with the term layer C.

According to an embodiment of the present disclosure, the media encoding layer 110 and the encapsulation function layer 120 operate as a multimedia data generator that generates multimedia content and/or multimedia data according to a multimedia service.

The transfer function layer 130 operates as a multimedia data configuration unit that configures multimedia data packets based on multimedia data input from the multimedia data generator. The transfer function layer 130 corresponding to the multimedia data configuration unit configures header information (header information) by identifying (identity) at least one multimedia data provided by the multimedia data generator, and configures a multimedia data packet by combining the header information and the at least one multimedia data.

The multimedia data compressed in the media coding layer 110 is packaged into a format similar to a file format by the encapsulation function layer 120. That is, the encapsulation function layer 120 generates a data segment (data segment) as a unit for the MMT service based on the encoded media data provided by the media encoding layer 110 or the stored media data, and generates an access unit for the MMT service using the data segment. Here, the access unit denotes a minimum media data entity to which the timing information belongs. The encapsulation function layer 120 generates packet formats for the generation, storage, and transmission of complex content by combining and/or splitting 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 adds an MMT transport packet header to the MMT payload format to configure an MMT transport packet, or configures a real-time protocol (RTP) packet using RTP as an existing transport protocol.

A packet configured in the transfer function layer 130, that is, an MMT transport packet or an RTP packet, is generated as an IP packet in the IP layer 150 after passing through the transport protocol layer 140 supporting a protocol such as a User Datagram Protocol (UDP) or a Transport Control Protocol (TCP), and the generated IP packet is transmitted. Transport protocol layer 140 and IP layer 150 may operate as data transports.

In addition, the optionally present control function layer 100 generates control information or signaling information required for transmission of data and transmits the control information or signaling information together with the data, or transmits the control information or signaling information using a separate signaling device.

The MMT payload format generated in the transport function layer 130 defines the logical structure of the media unit(s) to be transported by the MMT protocol or RTP.

The MMT payload is specified by a payload format for conveying encapsulated data units or other information in accordance with the MMT layer protocol or other existing application transport protocols. The MMT payload provides information about the stream and information about the file transfer.

In a stream, a data unit may be a MMT Media Fragment Unit (MFU) or an MMT Media Processing Unit (MPU). For convenience, it will be noted that the term MMT MFU may be interchanged with the term MFU, and the term MMT MPU may be interchanged with the term MPU.

For file transfers, the data units may be MMT assets and MMT packages.

The layer structure of the MMT system according to an embodiment of the present disclosure has been described with reference to fig. 1, and the configuration of the MMT payload in the MMT system according to an embodiment of the present disclosure will be described with reference to fig. 2.

Fig. 2 schematically illustrates a configuration of an MMT payload in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 2, MMT payload 200 may include at least one of: at least one MMT MFU 210, at least one MMT MPU220, at least one MMT asset 230, and an MMT package.

MMT MFU 210 is independent of any media CODEC and represents a generic container that includes encoded media data that can be independently decoded by a media decoder.

MMT MFU 210 represents a segment of MMT MPU220 and is the smallest unit that can be independently decoded. For example, if a frame is used as an access unit to perform an encoding operation, MMT MFU 210 may be a video frame or a slice (slice) included in a frame.

The MMT MPU220 is a container including one or more MMT MFUs and additional information transfer and processing, and may include various numbers of MMT MFUs generated from different access units. The MMT MPU220 represents an encoded media data unit that is fully and independently decodable by MMT compatible entities and may have a specific size according to the application environment. For example, in video, the MMT MPU220 may have a size of 1 group of pictures (GOP). As another example, the MMT MPU220 may include a plurality of picture frames included in 1 GOP, and the MMT MFU (210) may include each picture frame. For example, 1 GOP may be 1 second of video. The MMT asset 230 is a data entity composed of one or more MMT MPUs, and is a largest data unit to which the same MMT composition information (MMT-CI) or MMT transport characteristics (MMT-TC) is applied. The MMT asset 230 includes only one type of data, which includes packetized or multiplexed data. For example, each MMT asset 230 may be one of: at least a portion of an elementary stream of audio, an MPEG user interface (MPEG-U) widget package, at least a portion of an MPEG-2 transport stream, at least a portion of an MPEG-4(MP4) file, and all or at least a portion of an MMT package.

For convenience, it will be noted that the term elementary stream may be interchanged with the term ES, the term transport stream may be interchanged with the term TS, the term MMT-CI may be interchanged with the term CI, and the term MMT-TC may be interchanged with the term Transport Characteristics (TC). Here, an elementary stream is defined by a particular media CODEC and may be logically one or more MMT assets. The MMT asset 230 supporting the layered CODEC and the multi-view CODEC may overlap with other MMT assets.

The MMT-CI represents information defining spatial and temporal relationships of MMT assets, and the MMT-TC defines quality of service (QoS) required to deliver the MMT assets. The MMT-TC may be represented as an asset delivery feature (ADC) for a particular delivery environment.

The MMT packet 240 is defined as a collection of encoded media data and related information that is processed by an MMT-compatible entity.

The configuration of MMT payloads in an MMT system according to an embodiment of the present disclosure has been described with reference to fig. 2. And a logical structure of an MMT packet in the MMT system according to an embodiment of the present disclosure will be described with reference to fig. 3.

Fig. 3 schematically shows a logical structure of an MMT packet in an MMT system according to an embodiment of the present disclosure.

Referring to FIG. 3, an MMT package 300 includes one or more MMT assets 320 and one or more ADCs 330 indicating MMT-C1310 and MMT-TC.

The MMT package 300 includes descriptive information such as an Identifier (ID) and location information of the MMT asset 320, and the MMT assets 320 within the MMT package 300 may be multiplexed or concatenated.

The processing of the MMT packet 300 may be performed based on the MPU. The one or more MMT assets 320 are a collection of one or more MPUs having the same MMT asset ID, and the TCs associated with each of the one or more MMT assets 320 are represented by one or more ADCs 330. One or more ADCs 330 may be used to configure the parameters of the MMT payload and the header information of the MMT packet by the entity encapsulating the MMT packet 300.

The configuration information for the MMT packet and information required for the terminal to receive and consume the configuration information of the MMT packet are transmitted through the MMT signaling message. In the MMT system, the MMT signaling function area defines a message format related to media consumption and media delivery.

In the MMT system, messages related to media consumption provide information required to consume transmitted media data, and these are defined as follows.

The Packet Access (PA) message for a purpose similar to the program map table (PMY) of MPEG-2TS includes all the information required to render the transmitted packets. The PA message is a message that needs to be first transmitted to receive and consume the MMT packet, and individual information can be updated by an additional message.

A Media Presentation Information (MPI) message providing presentation information is used to transmit various presentation information such as CI defined in international organization for standardization (ISO)/International Electronic Committee (IEC) 23008-11, Media Presentation Description (MPD) defined in ISO/IEC23009-1, and the like.

An MMT Packet Table (MPT) message provides information about the transmitted MMT packet. The MPT message provides an ID of the MMT package, MMT asset information included in the MMT package, and the like. For convenience, the term MPT may be interchanged with the term MMT Package (MP) table.

The Clock Relationship Information (CRI) message provides mapping information between Network Time Protocol (NTP) timestamps and System Timing Clocks (STCs) of MPEG-2 for synchronization between MMT assets and MPEG-2 ES.

A Device Capability Information (DCI) message provides terminal capability information required for media consumption.

Meanwhile, innovative technologies capable of realizing next-generation broadcasting and multimedia services, such as high-definition immersive broadcasting technologies (such as Ultra High Definition Television (UHDTV), three-dimensional TV (3-dimensional TV, 3DTV), multi-view TV, etc.), N-screen service technologies for organically using various types of fixed and portable multimedia devices, etc., and development of broadcast communication convergence and transmission networks have been proposed.

An application service that provides various additional information by interacting with a broadcast program or independently provides various additional information based on a hybrid transmission technology that realizes a convergence type multimedia service by organically interacting a broadcast network and a communication network is considered to be an indispensable success factor for a next generation broadcast service, and provides image content whose reality and realism are maximized. For convenience, it will be noted that the term application service may be interchanged with the term application.

Typical ones of the application services include viewer participation services (e.g., text messages, quizzes, votes, surveys, people polls, etc.), electronic commerce (such as ticketing, auctions, electronic coupons, mobile downloads, etc.), application services that can be provided independently of broadcast programming (such as weather, sports, games, etc.), portal services, targeted advertising, etc.

In order for the terminal to support the application service, it is necessary to receive signaling information of data or files required to run the application service using a broadcasting network or a communication network, and to identify and select the application service and related data.

Signaling information related to application services can be classified into two types. That is, the signaling information may be classified into signaling information providing overall attributes for a single service (such as an application service list, an application service name, transmission information, etc.), and event information controlling the operation of the application service. An application service interacting with a broadcast program can provide a wider variety and rich broadcast services by transmitting event information with the broadcast program. Here, the event includes a notification, for example, a timing notification to an application service, a timing notification indicating that an action is to be taken.

An operation process of a terminal for running an application service in an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 4.

Fig. 4 schematically shows an operation process of a terminal for running an application service in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 4, it will be noted that the operation process of the terminal shown in fig. 4 is an operation process of a terminal for running an application service for providing a targeted advertisement at a specific time.

Referring to fig. 4, the terminal receives an audio stream and a video stream of a requested broadcast program (shown as "show X" in fig. 4) from a service provider and presents the audio stream and the video stream at operation 405. At operation 410, the terminal acquires signaling information of an application service related to a broadcast program through an application information stream as a channel providing signaling related to the application service, and receives a data network required to run the application service, if any, using a broadcast network or a communication network. For convenience, signaling information and data for application services may be referred to as application information.

At operation 415, the terminal receives event information transmitted through the event stream as a channel providing an event while presenting a broadcast program, and performs an operation according to the received event information. For example, in fig. 4, the terminal receives event information related to the execution of an application service Y that provides additional information of an advertised product at a specific part of a show X (e.g., at the start of an advertisement). At operation 420, the terminal runs an application service Y, i.e., an advertisement service, based on the event information. When a termination event for the application service Y is received after a predetermined time, the terminal terminates the application service Y at operation 425.

The MMT system defines various signaling messages related to media consumption and media delivery. However, the signaling messages that have been proposed so far provide configuration information for the package and information required for receiving each asset included in the package. The MPT used in the MPT message defines configuration information of each asset included in the package and location information required to receive each asset. A descriptor (descriptor) is used to provide additional information in addition to basic information such as configuration information of each asset and location information required for receiving each asset, and the MPT message defines a container format in which various descriptors can be stored.

The MPEG CI, which may be used in the MPI table, may include position information on a logical screen of the terminal and time information related to presentation of each asset included in the package. However, the main purpose of the MPEG CI is to provide control information of assets transmitted based on the MMT scheme, and may be difficult to be applied to application services transmitted through a transmission protocol other than the MMT protocol.

Therefore, embodiments of the present disclosure propose a scheme for transmitting information related to an application service and event information for controlling the operation of the application service based on the MMT scheme, and this will be described below.

An internal structure of an apparatus for receiving information related to an application service in an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 5.

Fig. 5 schematically shows an internal structure of an apparatus for receiving information related to an application service in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 5, the apparatus for receiving information related to an application service may be a terminal, for example.

The apparatus includes a data receiver 505, a controller 500, a signaling information Database (DB) 560, and a service display 570.

The data receiver 505 may include at least one of: an MMT data receiver 510, a real-time object delivery over unidirectional transport (ROUTE) data receiver 515, a hypertext transfer protocol (HTTP) data receiver 520, and a XXX data receiver 525, to receive a packet transmitted over a communication network or a broadcast network based on at least one of transmission protocols such as MMT protocol, ROUTE protocol, and HTTP, and to output the received packet to a file data receiver 530, a media data receiver 540, or a signaling data receiver 550 based on a type of the received packet. Here, the XXX data receiver 525 denotes a data receiver for receiving a packet transmitted based on a transmission protocol other than the MMT protocol, the ROUTE protocol, and the HTTP.

The file data receiver 530 acquires data included in the packet by processing the packet output from the data receiver 505 and outputs the data to the file processor 535. The file data receiver 530 receives MMTP packets transmitted in a Generic File Delivery (GFD) mode defined by the MMT scheme, configures MMTP payloads based on the MMTP packets, and outputs the MMTP payloads to the file processor 535. The file data receiver 530 receives packets transmitted through one of various file transfer protocols, extracts desired data from the received packets, and outputs the extracted data to the file processor 535. The file processor 535 configures the file based on the data output from the file data receiver 530.

Each of the media data receiver 540 and the media processor 545 processes media data. For example, in the case where the media data is an MPU defined by the MMT scheme, the media processor 545 may process the media data transmitted in an MPU mode of MMTP. At this time, the media data receiver 540 generates an MPU by configuring an MMTP payload based on the MMTP packet output from the MMT data receiver 510 within the data receiver 505, and the media processor 545 presents the MPU through the service display 570.

In the case where the media data is transferred by a file, the file processor 535 outputs the media file to the media processor 545, and the media processor 545 presents the media file through the service display 570.

In the case where the media data follows a dynamic adaptive streaming over HTTP (DASH) format defined in ISO/IEC23009-1, the media processor 545 may process media data transmitted based on the ROUTE protocol. At this time, the media processor 545 generates a DASH segment by processing the ROUTE packet output from the ROUTE data receiver 515, and renders the DASH segment through the service display 570.

The media data receiver 540 may output the media file to the media processor 545 after generating all media files complying with an ISO base media file format (ISOBMFF) such as an MPU or DASH segment, or output a portion of the media file to the media processor 545 before generating all media files in order to reduce time required for channel change.

If the packet output from the data sink 505 includes signaling information, the packet is output to the signaling data sink 550, thereby being used for the signaling data sink 550 to reconfigure the signaling information. The signaling information is output to the signaling processor 555 and additional operations are performed according to the signaling information. For example, if the signaling information is transmitted based on MMTP, the signaling data receiver 550 receives an MMTP packet including the signaling information from the MMT data receiver 510 and reconfigures an MMTP payload based on the received MMTP packet, and the signaling processor 555 parses the signaling information included in the MMTP payload to store necessary information at the signaling information DB 560.

If the signaling information is included in the file, the signaling processor 555 inputs the file including the signaling information output from the file processor 535 and parses the signaling information from the file to store necessary information at the signaling information DB 560.

Signaling processor 555 interacts with other configuration elements to perform additional operations based on the parsed signaling information. For example, upon receiving signaling information related to an application service, the signaling processor 555 outputs information required to receive data required to run the application service to the file data receiver 530, so that the file data receiver 530 receives the data required to run the application service.

Meanwhile, event information related to control of the application service may be transmitted through a dedicated signaling channel or media data. That is, event information related to control of the application service may be included in the media data. For example, in the MMT scheme, event information related to control of an application service may be transmitted through a signaling message or an MPU including media data. That is, in the MMT scheme, event information related to control of an application service may be included in the MPU. For another example, in a DASH scheme, signaling information may be sent over MPD or DASH segments that include media data. That is, in the DASH scheme, the signaling information may be included in the MPD or DASH segment.

Therefore, in case that event information is included in the media data, the media receiver data receiver 540 extracts the event information and outputs the event information to the signaling processor 555, thereby outputting the event information to the application manager 565, and the event information is used to control the operation of the application service.

The application manager 565 stores and manages overall information for application services, manages the operation of each application service, and displays information about each application service through the service display 570. To this end, the application manager 565 interacts with the signaling processor 555 and the file processor 535 to receive data and signaling information required for providing application services.

A procedure for transmitting signaling information and event information related to an application service in an MMT system according to an embodiment of the present disclosure will be described below.

1) Sending of signalling information relating to application services

The signaling information related to the application service includes major attributes of the application service, such as the name, transmission scheme, life cycle, etc. of the application service.

In an embodiment of the present disclosure, an Application Information Table (AIT) message, which is a signaling message transmitted through an MMT signaling session, may be used to transmit information related to an application service. For convenience, it will be noted that the term AIT may be interchanged with the term AI table.

Table 1 shows an example of formats of an AIT message and an AI table included in the AIT message.

[ Table 1]

In table 1, a message _ ID field indicates an ID of an AIT message, a version field indicates a version of the AIT message, and a length field indicates a length of the AIT message. The length field indicates the length from the next position immediately after the length field to the end of the AIT message, and may be expressed as, for example, a length in bytes.

In table 1, a message _ payload field indicates a payload of an AIT message, and an AI _ table () field includes the AIT.

The AIT message may further include an ID for identifying a service to which the AIT message is applied. The AIT message may further include a 1-bit flag indicating whether a Uniform Resource Identifier (URI) for identifying the AIT message exists in the extension part. For example, if the 1-bit flag is on (on), a field indicating a URI may also be included in the AIT message.

Information of all application services included in the MMT packet may be transmitted through one AI table or a plurality of AI tables. Here, it will be noted that the AI table including information on all application services may be referred to as a full AI table, and the AI table including a part of the information on all application services may be referred to as a subset AI table.

Each subset AI table is included in a separate AIT message.

Table 2 indicates an example of the format of the AI table.

[ Table 2]

In table 2, a table _ ID field indicates a table _ ID, and the table _ ID represents an ID of the AI table. The full AI table and the subset AI table may have different table _ ids. the value of the table _ id field is sequentially assigned, so the subset AI table number of the subset AI table can be calculated based on the table _ id field. For example, the subset AI table number may be calculated as "table _ id — the table _ id of the base subset AI table. The base subset AI table represents a subset AI table whose subset AI table number is 0. For example, the subset AI table numbers from 1 to 14 indicate the subset AI table, rather than the base subset AI table, and the subset AI table number 15 indicates the complete AI table.

In table 2, the version field indicates the version of the AI table. If a new version of the AI table is received, the AI table is changed from the existing version of the AI table to the new version of the AI table. The version field may be analyzed the same as the version field in the MPI table included in the existing MMT signaling table (if the table _ id field indicates a complete AI table, and if the value of the table _ id field included in the subset-0 AI table is the same as the value of the table _ id field (when the value of the AI _ table _ mode field is 1), or if all subset AI tables having lower subset AI table numbers have the same version value as the value of the table _ id field (when the value of the AI _ table _ mode field is 0), or if the processing of the subset AI tables is independent (when the value of the AI _ table _ mode field is 2)).

Here, the AI _ table _ mode field indicates an AI _ table _ mode indicating a processing scheme of a fragmented AI table in the case where the AI table is fragmented, and is used similarly to the PI _ mode field in the MPI table included in the existing MMT signaling table. A detailed description of the PI _ mode field will be omitted herein.

If the subset 0AI table has an updated version, all subset AI tables previously stored in the MMT receiving entity having a higher subset AI table number up to 14 are considered to have expired, except in the case that the AI _ table _ mode is in standalone mode. Here, the MMT receiving entity includes a terminal. If the subset AI table number is not 0 and the AI _ table _ mode value is 1, the contents of the subset AI table, which has a different version than the version of the subset-0 a1 table stored in the MMT receiving entity, will be ignored. If the subset AI table number is not 0 and the AI _ table _ mode value is field 0, the contents of the subset AI table with a version different from the version of the subset AI table with the lower subset AI table number stored in the MMT receiving entity will be ignored. It will increment modulo 256 according to the version change.

In table 2, the length field indicates the length of the AI table, and indicates the length from a position after the length field to the end of the AI table. For example, the length field may indicate a length in bytes.

In the sequential _ order _ processing _ mode, if the subset AI table number of the AI table is not 0, then the MMT receiving entity will receive all subset AI tables with lower subset AI table numbers having the same version as the AI table before processing the AI table. For example, if the MMT receiving entity does not receive the subset-2 AI table with the same version, the MMT receiving entity may not process the subset-3 AI table. In order _ irelevant _ processing _ mode, if the subset AI table number of the AI table is not 0, the MMT receiving entity needs to process the AI table immediately after receiving it as long as the AI table of subset-0 stored in the MMT receiving entity has the same version as the AI table. In the independent _ processing _ mode, the version of each of the subset AI tables is managed individually. In the independent _ processing _ mode, a segmented AI table is applied.

Examples of values and descriptions used in the AI _ table _ mode field may be as shown in table 3.

[ Table 3]

AI_table_mode	Description of the invention
		00	"sequential_order_processing_mode"
01	"order_irrelevant_processing_mode"
		10	"independent_processing_mode"
11	Retention (Reserved)

Also, in table 2, an AI _ table _ descriptor _ bytes field indicates a descriptor of the AI table, an AI _ count field indicates the number of application services included in the AI table, and an application _ attributes () field indicates an attribute of each application service.

As described above, the AI table may include various attributes related to the application service, and the various attributes are included in the application _ attributes () field. The various attributes may include the name of the application service, the priority of the transmission information and data associated with the application service, and the like.

Table 4 shows an example of application _ attributes ().

[ Table 4]

In one embodiment of the present disclosure, information related to an application service may be transmitted through an MPT message, which is a signaling message related to an MMT packet.

The MPT message includes a descriptor indicating whether an application service exists within the MMT package. The terminal needs to receive an MPT message to present a broadcast message transmitted based on the MMT scheme, and can more quickly detect the presence of an application service because a descriptor indicating the presence of the application service is included in the MPT message.

When detecting that the application service exists in the MMT packet through the MPT message, the terminal may acquire detailed information related to the application service by receiving the described AIT message.

The MPT message includes information, if any, that needs to be first provided to the terminal among information included in the AIT, in addition to the notification of whether the application service exists. The information that needs to be provided first may be information useful for performance improvement, quality of experience (QoE) improvement of the terminal, and the like.

Table 5 shows an example of a format of an application _ service _ descriptor, which is a descriptor that may be included in an MPT message.

[ Table 5]

In table 5, the descriptor _ tag field indicates a tag for identifying the entry _ event _ descriptor field, the descriptor _ length field indicates the length of the entry _ event _ descriptor field, and the application _ service _ descriptor field indicates whether an application service exists within the packet. For example, if the value of the application _ service _ descriptor field is 0, it means that the application service does not exist within the packet. If the value of the application _ service _ descriptor field is 1, it means that the application service exists in the packet. Information related to the application service is sent via AIT messages.

2) Transmission of event information

The event information may be transmitted based on two schemes according to whether the time of the event occurrence can be known in advance.

First, in the case where the time of occurrence of an event can be known in advance (such as a recorded broadcast), a static event transmission scheme is used.

Second, in cases where the time of the event occurrence may not be known in advance (such as live), a dynamic event transmission scheme is used.

The event information is notified to the application service.

In one embodiment of the present disclosure, the event information may be transmitted through an MMT signaling message (i.e., an Application Event Information (AEI) message) transmitted through an MMT signaling channel. The AEI messages can be applied to both static and dynamic event delivery schemes. In the dynamic event transmission scheme, event information may be included in media data in which an event occurs, for example, an MPU.

Tables 6 and 7 show examples of formats of MMT signaling messages including event information, for example, AEI messages and Application Event (AE) tables included in the AEI messages.

[ Table 6]

In table 6, the message _ ID field indicates the ID of the AEI message, the Version field indicates the Version of the AEI message, and the length field indicates the length of the AEI message. The length field indicates the length from the position after the length field to the end of the AEI message. For example, the length field may indicate a length in bytes. The AE _ table () field includes an AE table.

In one embodiment of the present disclosure, the AEI message may further include an ID for identifying the service at the extension portion to which the AEI message is applied. The AEI message can also include a 1-bit flag indicating whether the URI was used to identify the AEI message at the extension portion. If the 1-bit flag is on, a field indicating a URI may also be included in the AEI message.

[ Table 7]

In table 7, a table _ ID field indicates an ID of the AE table. In table 7, a version field indicates a version of the AE table, and a length field indicates a length of the AE table. The length field indicates the length from the next position after the length field to the end of the AE table. For example, the length field may indicate a length in bytes. In table 7, a number _ of _ app _ events field indicates the number of events included in the AE table, and an AE _ descriptor () field includes information of each event.

The event information is stored at the AE _ descriptor () field, and may include various information related to the event, such as an ID of an application service related to the event, a time and duration when the event is applied, an event operation, and the like.

Table 8 shows an example of AE _ descriptor ().

[ Table 8]

In table 8, a descriptor _ tag field indicates a tag for identifying AE _ descriptor (), a descriptor _ length field indicates the length of AE _ descriptor (), and an application _ identifier () field indicates a unique ID of an application to which an event is to be applied.

Table 9 shows an example of the format of an application _ identifier () field.

[ Table 9]

In table 8, a scheme _ id _ uri _ length field indicates the length of the scheme _ id _ uri. For example, the scheme _ id _ uri _ length field may indicate a length in bytes. In table 8, a scheme _ id _ uri field defines meaning and grammar (grammar) of a value transmitted through an event _ data field, and an event _ value _ length field indicates a length of the event _ data field. For example, the event _ value _ length field may indicate a length in bytes.

In table 8, the event _ value field indicates an event value. The range and meaning of the event value is determined by scheme _ id _ uri. In table 8, an event _ ID field indicates a unique ID of an event, an event _ presentation _ time field indicates a media presentation time to which the event will be applied, an event _ duration field indicates a media presentation time during which the event is available, and event _ data indicates an event content.

In an embodiment of the present disclosure, the event information may be transmitted through media data.

In the MMT protocol, media data is included in an MPU, which follows the ISOBMFF structure. The event information may be included in an evti box (box) included in the MPU, and an example of the format of the evti box is shown in table 10.

[ Table 10]

In table 10, sc container (scccontainer): MPU

Mandatory: is not provided with

Number: zero or more

Grammar:

the heme _ id _ uri field means and grammar of a value transmitted through the event _ data field, and the event _ value field includes an event value. The range and meaning of the event value is determined by scheme _ id _ uri. In table 10, the event _ ID field indicates a unique ID of an event, and the event _ presentation _ time _ delta field indicates a difference between a time when an MPU is presented and a time when a media (i.e., MPU) to which the event is applied is presented. That is, the event _ presentation _ time _ delta field indicates the start time of the event. The event _ duration field indicates the presentation time of the media during which the event is available (i.e. the duration of the event), and the event _ data field indicates the event content, i.e. the action initiated by the event. In table 10, the application _ identifier field indicates an ID of an application service to which an event is to be applied.

In an embodiment of the present invention, the event information is transmitted through an MPU included in the asset, and the MMT signaling information may be used to inform that the event information is included in the MPU included in the asset.

To this end, the MP table transmitting the MMT packet information includes an inbound _ event _ descriptor as a descriptor used on an asset-level (asset-level).

The terminal may detect that the event information is included in the MPU included in the asset by receiving the inbound _ event _ descriptor through the MP table. Upon detecting that the event information is included in the MPUs included in the asset, the terminal receives the MPUs and acquires the event information from the evti box included in the MPUs.

Table 11 shows an example of the format of the inband _ event _ descriptor.

[ Table 11]

In table 11, a descriptor _ tag field indicates a tag for identifying an inbound _ event _ descriptor, a descriptor _ length field indicates a length of the inbound _ event _ descriptor, a scheme _ id _ uri _ length field indicates a length of the scheme _ id _ uri, and the scheme _ id _ uri field defines meaning and syntax of a value transmitted through the event _ data field. For example, the scheme _ id _ uri _ length field may indicate a length in bytes.

In table 11, an event _ value _ length field indicates the length of the event _ data field, and the event _ value field includes an event value. For example, the event _ value _ length field may indicate a length in bytes. The range and meaning of the event value is determined by scheme _ id _ uri.

A procedure for processing event information based on an MMT signaling message in an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 6.

Fig. 6 schematically shows a process for processing event information based on an MMT signaling message in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 6, at operation 605, a terminal detects that a service is selected. At operation 610, the terminal monitors reception of the service-related MMT signaling message and parses the received service-related MMT signaling message upon reception thereof. At operation 615, the terminal determines whether the MMT signaling message includes an AIT message.

If the MMT signaling message does not include an AIT message, the terminal presents a video/audio stream of the selected service at operation 620.

If the MMT signaling message includes an AIT message, the terminal receives data related to the application service based on the AI table included in the AIT message at operation 625. At operation 625, the terminal may determine a time when the terminal starts receiving data related to the application service, whether the terminal immediately runs the application service, etc. based on the attributes of the application included in the AI table, and the input parameters.

The terminal monitors reception of an AEI message, which is a signaling message including event information, and acquires information on an event application time (event applied time) from an AE table included in the received AEI message when the AEI message is received. At operation 630, the terminal determines whether it reaches the event application time.

If it reaches the event application time, the terminal performs a control operation for the application service based on the event at operation 635. The control operation for the application service may include an operation for initiating the application service, an operation for terminating the application service, and the like.

If it does not reach the event application time, the terminal proceeds to operation 620.

Although fig. 6 illustrates a process for processing event information based on an MMT signaling message in an MMT system according to an embodiment of the present disclosure, various changes may be made to fig. 6. For example, while shown as a series of operations, various operations in FIG. 6 could overlap, occur in parallel, occur in a different order, or occur multiple times.

A process for processing event information based on an MMT signaling message in an MMT system according to an embodiment of the present disclosure has been described with reference to fig. 6, and a process for processing event information based on an MPU in an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 7.

Fig. 7 schematically shows a process for processing event information based on an MPU in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 7, at operation 705, the terminal detects that a service is selected. At operation 710, the terminal monitors for receipt of the service-related MMT signaling message and, upon receipt of the MMT signaling message, parses the received service-related MMT signaling message. At operation 715, the terminal determines whether the MMT signaling message includes an AIT message.

If the MMT signaling message does not include an AIT message, the terminal presents a video/audio stream of the selected service at operation 720.

If the MMT signaling message includes an AIT message, the terminal receives data related to the application service based on the AI table included in the AIT message at operation 725. At operation 725, the terminal may determine a time when the terminal starts to receive data related to the application service, whether the terminal immediately runs the application service, etc. based on the attributes of the application included in the AI table, and the input parameters.

The terminal, which has received the MMT signaling message in operation 710, determines whether event information is included in the MPU based on the MMT signaling message in operation 740. That is, the terminal determines whether event information is included in the MPU included in the asset by analyzing an asset level descriptor included in the MP table included in the MMT signaling message.

If the asset level descriptor indicates that the event information is included in the MPU, the terminal extracts the event information from the MPU included in the asset and stores the event information whenever the MPU included in the asset is received at operation 745.

At operation 730, the terminal periodically determines whether it reaches an event application time while presenting the service. For example, information about the event application time may be obtained from an AE table within the AEI message. If the event application time is reached, the terminal performs a control operation on the application service through the application-related event at operation 735.

Although fig. 7 illustrates a process for processing event information based on an MPU in an MMT system according to an embodiment of the present disclosure, various changes may be made to fig. 7. For example, while shown as a series of operations, various operations in FIG. 7 could overlap, occur in parallel, occur in a different order, or occur multiple times.

In an embodiment of the present disclosure, the signaling table and the descriptor are encapsulated as mmt _ atsc3_ message () that may be configured as table 12, and mmt _ atsc3_ message () may be transmitted in a signaling message mode of MMTP.

[ Table 12]

In table 12, the message _ ID field indicates the ID of mmt _ atsc3_ message (). For example, the message _ id field may be implemented with a 16-bit field. In table 12, the version field indicates the version of mmt _ atsc3_ message (). For example, the version field may be implemented with an 8-bit field.

In table 12, the length field indicates the length of mmt _ atsc3_ message (). For example, the length field may indicate a length in bytes, and may be implemented with a 32-bit field. The length of mmt _ atsc3_ message () may be the number of bytes from the next byte after the length field to the last byte of mmt _ atsc3_ message ().

In table 12, the service _ ID field indicates an ID for identifying a service to which information transmitted through a payload included in mmt _ atsc3_ message () is applied. For example, the service _ id field may be implemented with a 16-bit field. The service _ id field is set to match atsc of the USD to be described: serviceId attribute equal value.

In table 12, the atsc3_ message _ content _ type field indicates the type of information transmitted through the payload included in the mmt _ atsc3_ message (). The atsc3_ message _ content _ type field may be implemented with a 16-bit field.

For example, the atsc3_ message _ content _ type field may indicate a value as shown in table 13.

[ Table 13]

atsc3_message_content_type	Means of
		0x0000	Retention
0x0001	User service description
		0x0002	MPD
0x0003	Application information table
		0x0004	Application event information
0x0005	Video stream attribute descriptor
		0x0006	ATSC staggercasting (Staggercast) descriptor ()
0x007～0xFFFF	Reserved for future use

In table 12, the atsc3_ message _ content _ version field indicates the version of information transmitted through the message payload included in the mmt _ atsc3_ message (). For example, the atsc3_ message _ content _ version field may be represented by an 8-bit field. The message payloads may be distinguished based on a combination of service _ id and atsc3_ message _ content _ type.

In table 12, the atsc3_ message _ content _ compression field indicates a compression scheme applied to the atsc3_ message _ content _ byte field included in the message payload included in mmt _ atsc3_ message (). For example, the atsc3_ message _ content _ compression field may be implemented with an 8-bit field.

In table 12, a URI _ length field indicates the length of a URI used for identifying a message payload. For example, the URI _ length field may be implemented with an 8-bit field. In the case where the URI is not used, the value of the URI _ length field may be set to 0.

In table 12, a URI _ byte field indicates each byte of a URI used for identifying a message payload. The URI _ byte field may be implemented with an 8-bit field. For example, the URI _ byte field is represented as a universal encoding character set + conversion format (UTF) -8 character, and does not include a termination null character.

In table 12, the atsc3_ message _ content _ byte field indicates each byte of information transmitted through the message payload. For example, the atsc3_ message _ content _ byte field may be implemented with an 8-bit field.

Meanwhile, mmt _ atsc3_ message () shown in table 11 may transmit signaling information of all formats including an extensible markup language (XML) format, a binary format, and the like through a message payload, and may identify a format of each signaling information using atsc3_ message _ content _ type.

In the case where the inbound _ event _ descriptor is transmitted through the payload included in mmt _ atsc3_ message () in table 12, the inbound _ event _ descriptor may have a format as shown in table 14 according to an embodiment of the present disclosure.

[ Table 14]

In table 14, a descriptor _ tag field indicates a tag for identifying an inbound _ event _ descriptor, a descriptor _ length field indicates the length of the inbound _ event _ descriptor, and a number _ of _ assets field indicates the number of assets described in the inbound _ event _ descriptor. In table 14, an asset _ ID _ length field indicates the length of an asset ID, and an asset _ ID _ byte field indicates each byte of an asset ID. For example, the asset _ id _ length field may indicate a length in bytes.

In table 14, a scheme _ id _ uri _ length field indicates the length of the scheme _ id _ uri, and the scheme _ id _ uri field defines the meaning and grammar of the value transmitted through the event _ data field. For example, the scheme _ id _ uri _ length field may indicate a length in bytes.

In table 14, an event _ value _ length field indicates the length of an event _ data field, and the event _ data field includes an event value. The range and meaning of the event value are determined by scheme _ id _ uri, and the event _ value _ length field may indicate a length in bytes.

In an embodiment of the present invention, the event information is transmitted through an MPU included in the asset, and the MMT signaling information may be used to inform that the event information is included in the MPU included in the asset. To this end, mmt _ atsc3_ message () includes an inbound _ event _ descriptor as a descriptor used at the asset level in the payload.

The terminal may acquire the inbound _ event _ descriptor through mmt _ atsc3_ message (), and receive the MPU included in the asset upon detecting event information included in the MPU included in the asset, and may acquire the event information from the evti box included in the MPU.

An internal structure of a transmitting apparatus in an MMT system according to an embodiment of the present disclosure will be described with reference to fig. 8.

Fig. 8 schematically illustrates an internal structure of a transmitting apparatus in an MMT system according to an embodiment of the present disclosure.

Referring to fig. 8, the transmitting apparatus 800 may be an MMT transmitting entity, and the MMT transmitting entity may be a service provider or the like.

The transmitting apparatus 800 includes a transmitter 811, a controller 813, a receiver 815, a storage unit 817, and an output unit 819.

The controller 813 controls the overall operation of the transmitting apparatus 800. More specifically, according to an embodiment of the present disclosure, the controller 813 controls operations related to operations of transmitting and receiving event information in the MMT system. Operations related to the operation of transmitting and receiving event information in the MMT system according to an embodiment of the present disclosure have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The transmitter 811 transmits various signals and various messages to other entities (e.g., an MMT receiving entity included in the MMT system, etc.) under the control of the controller 813. For example, the MMT receiving entity may be a terminal or the like. Various signals and various messages transmitted in the transmitter 811 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The receiver 815 receives various signals and various messages from other entities (e.g., an MMT receiving entity included in the MMT system, etc.) under the control of the controller 813. Various signals and various messages received in the receiver 815 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The storage unit 817 stores various programs, various data, and the like related to operations performed in the MMT system to transmit and receive event information according to an embodiment of the present disclosure under the control of the controller 813. A storage unit 817 stores various signals and various messages received by the receiver 815 from other entities.

The output unit 819 outputs various signals and various messages related to operations related to the operations of transmitting and receiving event information performed in the MMT system according to an embodiment of the present disclosure under the control of the controller 813. Various signals and various messages output by the output unit 819 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

Although the transmitter 811, the controller 813, the receiver 815, the storage unit 817, and the output unit 819 are described as separate units in the transmitting apparatus 800, it should be understood that this is merely for convenience of description. In other words, two or more of the transmitter 811, the controller 813, the receiver 815, the storage unit 817, and the output unit 819 may be combined into a single unit.

The transmitting apparatus 800 may be implemented with a processor.

The internal structure of the transmitting device in the MMT system according to the embodiment of the present disclosure has been described with reference to fig. 8, and the internal structure of the receiving device in the MMT system according to the embodiment of the present disclosure will be described with reference to fig. 9.

Referring to fig. 9, the receiving apparatus 900 may be an MMT receiving entity, and the MMT receiving entity may be a terminal or the like.

The receiving apparatus 900 includes a transmitter 911, a controller 913, a receiver 915, a storage unit 917, and an output unit 919.

The controller 913 controls the overall operation of the receiving apparatus 900. More specifically, according to an embodiment of the present disclosure, the controller 913 controls operations related to operations for transmitting and receiving event information in the MMT system. Operations related to an operation of transmitting and receiving event information in the MMT system according to an embodiment of the present disclosure have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The transmitter 911 transmits various signals and various messages to other entities, for example, an MMT transmitting entity included in the MMT system, etc., under the control of the controller 913. For example, the MMT sending entity may be a service provider or the like. Various signals and various messages transmitted in the transmitter 911 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The receiver 915 receives various signals and various messages from other entities (e.g., an MMT transmitting entity included in the MMT system, etc.) under the control of the controller 913. Various signals and various messages received in the receiver 915 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

The storage unit 917 stores various programs, various data, and the like related to operations performed in the MMT system to transmit and receive event information according to an embodiment of the present disclosure under the control of the controller 913. The storage unit 917 stores various signals and various messages received by the receiver 915 from other entities.

The output unit 919 outputs various signals and various messages related to operations related to the transmission and reception of event information performed in the MMT system according to an embodiment of the present disclosure under the control of the controller 913. Various signals and various messages output by the output unit 919 have been described with reference to fig. 1 to 7 and tables 1 to 14, and a detailed description thereof will be omitted herein.

Although the transmitter 911, the controller 913, the receiver 915, the storage unit 917, and the output unit 919 are described as separate units in the receiving apparatus 900, it should be understood that this is merely for convenience of description. In other words, two or more of the transmitter 911, the controller 913, the receiver 915, the storage unit 917, and the output unit 919 may be incorporated into a single unit.

The receiving means 900 may be implemented by a processor.

As is apparent from the above description, embodiments of the present disclosure enable transmission and reception of signals in a multimedia system.

Embodiments of the present disclosure enable event information related to an event to be transmitted and received in a multimedia system.

Embodiments of the present disclosure enable event information related to an event together with a multimedia service to be provided in a multimedia system.

Certain aspects of the present disclosure may also be embodied as computer readable code on a non-transitory computer readable recording medium. The non-transitory computer-readable recording medium is any data storage device that can store data, which can be thereafter read by a computer system. Examples of the non-transitory computer readable recording medium include Read Only Memory (ROM), Random Access Memory (RAM), optical disk ROM (CD-ROM), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission through the internet). The non-transitory computer-readable recording medium may also be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. In addition, functional programs, codes, and code segments for accomplishing the present disclosure may be easily construed by programmers skilled in the art to which the present disclosure pertains.

It is understood that the methods and apparatus according to embodiments of the present disclosure may be implemented by hardware, software, and/or combinations thereof. The software may be stored in non-transitory memory (e.g., erasable or rewritable ROM), memory (e.g., RAM, a memory chip, a memory device or memory Integrated Circuit (IC)), or an optically or magnetically recordable non-transitory machine-readable (e.g., computer-readable) storage medium (e.g., CD, DVD, magnetic disk, magnetic tape, etc.). The methods and apparatus according to embodiments of the present disclosure may be implemented by a computer or mobile terminal including a controller and a memory, and the memory may be an example of a non-transitory machine-readable (e.g., computer-readable) storage medium suitable for storing a program or programs including instructions for implementing various embodiments of the present disclosure.

The present disclosure may include a program including a program for implementing the apparatus and method defined by the appended claims, and a non-transitory machine-readable (e.g., computer-readable) storage medium storing the program. The program may be electronically transferred via any medium, such as a communication signal, sent via a wired and/or wireless connection, and the present disclosure may include equivalents thereof.

The apparatus according to an embodiment of the present disclosure may receive a program from a program providing device connected to the apparatus via a wire or wirelessly and store the program. The program providing apparatus may include: a memory for storing an instruction indicating execution of an already installed content protection method, information required for the content protection method, and the like; a communication unit for performing wired or wireless communication with a graphics processing apparatus; and a controller for transmitting the relevant program to the transmitting/receiving device based on a request of the graphic processing device or automatically transmitting the relevant program to the transmitting/receiving device.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1. A method of operating a receiving device in a multimedia system, the method comprising:

event information associated with the event is received,

wherein the event comprises a notification to an application, the notification indicating that an action is to be taken,

wherein, if the event information indicates a first event for a service based on dynamic adaptive streaming over hypertext transfer protocol, DASH, the event information is received in a first event information box included in a media presentation description, MPD,

wherein if the event information indicates a second event for a service for transmitting the MMT based on the moving picture experts group media, the event information is received in a second event information box included in a media processing unit MPU in the MMT payload.

2. The method of claim 1, wherein if the event information indicates a second event for the MMT-based service, the event information comprises at least one of: an identifier ID of the event, a start time of the event, a duration of the event, and event data of the event.

3. The method of claim 2, wherein the start time of the event comprises a difference between a time the MPU is presented and a time the event is applied into the MPU.

4. The method of claim 2, wherein the event data comprises the action.

5. The method of claim 1, further comprising:

receiving first information indicating presence of the event information in the MPU if the event information indicates a second event for an MMT-based service.

6. A receiving apparatus, comprising:

a processor; and

a memory configured to store instructions that, when executed by the processor, cause the receiving apparatus to receive event information related to an event,

7. The reception apparatus according to claim 6, wherein if the event information indicates a second event for the MMT-based service, the event information includes at least one of: an identifier ID of the event, a start time of the event, a duration of the event, and event data of the event.

8. The reception apparatus according to claim 7, wherein the start time of the event includes a difference between a time when the MPU is presented and a time when the event is applied to the MPU.

9. The receiving device of claim 7, wherein the event data comprises the action.

10. The receiving device of claim 6, wherein the instructions, when executed by the processor, cause the receiving device to further: