CN112738645B

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

Info

Publication number: CN112738645B
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: 2023-05-30
Anticipated expiration: 2036-06-23
Also published as: JP2018524904A; JP6728246B2; CN107787586B; KR102598237B1; EP3314906A1; KR102473346B1; EP3314906A4; CN112738645A; KR20170000312A; CN107787586A; KR20220165693A

Abstract

Methods and apparatus for transmitting or receiving signals in a multimedia system are provided. The method of operating a receiving device in a multimedia system includes: event information related to an event is received, wherein the event comprises a notification to an application, the notification indicating that an action is to be taken, wherein the event information is received in a first event information box comprised in a media presentation description MPD if the event information indicates a first event for a service based on dynamic adaptive streaming, DASH, over a hypertext transfer protocol, wherein the event information is received in a second event information box comprised in a media processing unit, MPU, in an MMT payload if the event information indicates a second event for a service based on moving picture expert group media transport, MMT.

Description

Method and apparatus for transmitting and receiving signal in multimedia system

The present application is a divisional application of the invention patent application with the application date of 2016, 6, 23 and the application number of 201680036782.1.

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 (streaming service) (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 may be classified into unicast, multicast and broadcast based on the number of users joining the real-time multimedia services.

The moving picture expert group-2transport stream (moving picture experts group-2transport stream,MPEG-2 TS) is a technology for transmitting multimedia contents, and a typical transmission technology for transmitting a bit stream (a plurality of coded video bit streams) in which a plurality of broadcast programs are multiplexed in a transmission environment in which errors exist.

A moving picture expert group (moving picture experts group, MPEG) media transmission technology has been proposed as one of multimedia transmission technologies for supporting multimedia services based on the MPEG technology. The MPEG media transport (MPEG media transport, MMT) technology is a new technology for providing MPEG of various types of multimedia services through various terminals such as Televisions (TVs), mobile devices, etc. in various types of network environments. For example, MMT technology may be applied to efficiently transfer complex content over heterogeneous networks. Here, the complex content represents a collection of content having multimedia elements collected through video, audio, applications, and the like. For example, the heterogeneous network may be a network including a broadcast 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 and a communication network organically interact, it is necessary to provide signaling information, and thus, a terminal can receive data or files required to run the application service using the broadcast network or the communication network and identify and select the application service and data related to the application service.

Therefore, it is required to transmit and receive signaling information for providing an application service in a system using MMT technology.

The above information is presented merely as background information to aid in the understanding of the present disclosure. No decision is made as to whether any of the above is likely to be applicable to the prior art with respect to the present disclosure, nor is an assertion made.

Disclosure of Invention

Technical problem

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

Another aspect of the present disclosure is to propose 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 proposal

According to an aspect of the present disclosure, there is provided a method of operating a transmitting device 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, a method of operating a transmitting device in a multimedia system is provided. 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 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.

According to another aspect of the present disclosure, there is provided a transmitting apparatus in a multimedia system. The transmitting apparatus 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 transmitting apparatus includes: a transmitter configured to transmit 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.

According to another aspect of the present disclosure, there is provided a receiving apparatus in a multimedia system. The receiving device 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 to the detailed description that follows, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document, the terms "include" and "comprise" and their derivatives are intended to be inclusive, meaning and/or that the phrases "associated with …" and "associated with" and their derivatives may mean any device, system or portion thereof that includes, interconnects with …, contains, is connected to or is connected with …, is coupled to or is coupled with …, communicates with …, cooperates with …, interleaves, juxtaposition, is proximate to, is bound to or is bound to …, has the property of …, etc., and the term "controller" means any device, system or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware or software, or some combination of at least two thereof. 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 foregoing and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 schematically illustrates 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 the logical structure of an MMT package (package) in an MMT system according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates an operational procedure of a terminal for running application services in an MMT system according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates 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 illustrates a process for processing event information based on MMT signaling messages in an MMT system according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a process for processing event information based on a media processing unit (media processing unit, MPU) in an MMT system according to an embodiment of the present disclosure;

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

Fig. 9 schematically illustrates an internal structure of a receiving apparatus in an MMT system according to an embodiment of the 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 the various embodiments of the disclosure defined by the claims and their equivalents. It includes various specific details to aid understanding, but these are to be considered exemplary only. Accordingly, one 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 written meanings, but are used only by the inventors to enable clarity and consistency of understanding of the present 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 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 element from another element. For example, a first component may be termed a second component, and, as such, a second component may be termed a first component, without departing from the teachings of the present inventive concept. The term "and/or" as used herein 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, amounts, operations, components, elements, or combinations thereof, but do not preclude the presence or addition of one or more other features, amounts, operations, components, elements, or groups thereof.

The terms used herein, including technical terms and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art, provided that the terms are not defined differently. It should be understood that terms defined in commonly used dictionaries have the same meaning as those terms in the related 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, tablet computer (personal computer, PC), mobile phone, video phone, electronic book reader, desktop PC, notebook PC, netbook PC, personal digital assistant (personal digital assistant, PDA), portable multimedia player (portable multimedia player, PMP), moving picture experts group phase 1 or phase 2 (MPEG-1 or MPEG-2) audio layer 3 (MP 3) player, ambulatory medical device, camera, wearable device (e.g., head-mounted device (HMD), electronic garment, electronic necklace, electronic accessory, electronic tattoo, or smartwatch), or the like.

According to the present disclosureThe electronic device may be an intelligent household appliance with communication function. The smart home appliances may be, for example, televisions, digital versatile disc (digital versatile disc, DVD) players, audio, refrigerator, air conditioner, vacuum cleaner, oven, microwave oven, washing machine, dryer, air purifier, set top box, television box (e.g., samsung HomeSync) ^TM 、Apple TV ^TM Or Google TV ^TM ) Game machines, electronic dictionaries, electronic keys, camcorders, electronic photo frames, etc.

According to various embodiments of the present disclosure, the electronic device may be a medical device (e.g., a magnetic resonance angiography (magnetic resonance angiography, MRA) device, a magnetic resonance imaging (magnetic resonance imaging, MRI) device, a computed tomography (computed tomography, CT) device, an imaging device, or an ultrasound device), a navigation device, a global positioning system (global positioning system, GPS) receiver, an event data recorder (event data recorder, EDR), a flight data recorder (flight data recorder, FDR), an automotive infotainment device, a naval electronic device (e.g., a naval navigation device, a gyroscope, or compass), an avionics 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 a piece of 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 includes communication functionality.

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

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

According to various embodiments of the present disclosure, the transmitting apparatus 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), etc.

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 (long term evolution, LTE) mobile communication system, an LTE-advanced, LTE-a, licensed-assisted access (LAA) -LTE mobile communication system, a high speed downlink packet access (high speed downlink packet access, HSDPA) mobile communication system, a high speed uplink packet access (high speed uplink packet access, HSUPA) mobile communication system, a high speed packet data (high rate packet data, HRPD) mobile communication system proposed in third generation partnership project 2 (3 GPP 2), a wideband code division multiple access (wideband code division multiple access, WCDMA) mobile communication system proposed in 3GPP2, a code division multiple access (code division multiple access, CDMA) mobile communication system proposed in 3GPP2, an institute of electrical and electronics engineers (institute of electrical and electronics engineers, IEEE) 802.16M communication system, an IEEE802.16e communication system, an evolved packet system (evolved packet system, EPS) and a mobile internet protocol (mobile IP) system, such as a mobile multimedia services (DMB), a digital multimedia services (digital multimedia broadcasting (DMB), a digital television (24-handhold/handhold) mobile communication system, a digital television (dvb-24-handhold/digital television (hdv) mobile communication system, etc., IPTV), a moving picture expert group (moving picture experts group, MPEG) media transport MMT system, etc. Here, the MPEG media transport will be referred to as MMT.

The methods and apparatus presented in the embodiments of the present disclosure may be applied to an advanced television systems committee (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 an MMT scheme.

The MMT protocol (MMTP) defines an application layer protocol for delivering a delivery frame including a MMT Payload Format (PF) over an internet protocol (internet protocol, IP) network.

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

MMT technology defines a data model such as package, asset (asset), etc. The package represents independent content (such as a movie) and the asset represents a logical entity that classifies 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.

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

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

Referring to fig. 1, the layer structure of the mmt system configures multimedia data packets and includes a media coding layer 110 transmitting the multimedia data packets, 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 function layer is interchangeable with the term layer E, the term transfer function layer is interchangeable with the term layer D, and the term control function layer is interchangeable 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 from a multimedia service.

The delivery function layer 130 operates as a multimedia data configuration unit that configures multimedia data packets based on the multimedia data input from the multimedia data generator. The delivery function layer 130 corresponding to the multimedia data configuration unit configures header information (header information) by identifying (identifying) 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 encoding layer 110 is packetized into a format similar to a file format through 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 or the stored media data provided by the media encoding layer 110, and generates an access unit for the MMT service using the data segment. Here, the access unit represents the smallest media data entity to which the timing information belongs. The encapsulation function 120 generates packet formats for generation, storage, and transmission of complex content by combining and/or partitioning access units.

The delivery 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.

Packets configured in the delivery function layer 130, i.e., MMT transport packets or RTP packets, are generated as IP packets in the IP layer 150 after passing through the transport protocol layer 140 supporting a protocol such as a user datagram protocol (user datagram protocol, UDP) or a transport control protocol (transport control protocol, TCP), and the generated IP packets are transmitted. The transport protocol layer 140 and the IP layer 150 may operate as a data transmitter.

Further, the control function layer 100, which is optionally present, 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 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 or other information in accordance with the MMT layer protocol or other existing application transport protocol. The MMT payload provides information about the stream and information about file transfer.

In the stream, the data units may be MMT media fragment units (media fragment unit, MFU) or MMT media processing units (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 transfer, 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 MMT payloads 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 MMT payloads in an MMT system according to an embodiment of the disclosure.

Referring to fig. 2, the 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.

The MMT MFU 210 is independent of any media CODEC and represents a generic container that includes encoded media data that is independently decodable 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, the MMT MFU 210 may be a video frame or a slice included in a frame.

MMT MPU220 is a container that includes one or more MMT MFUs and additional information transfer and processing, and may include various numbers of MMT MFUs generated from different access units. MMT MPU220 represents an encoded media data unit that is fully and independently decodable by MMT compatible entities and may be of a particular size depending on 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 video. The MMT asset 230 is a data entity made up of one or more MMT MPUs and is the largest data unit to which the same MMT composition information (MMT composition information, MMT-CI) or MMT transfer characteristics (MMT transport characteristics, MMT-TC) are applied. The MMT asset 230 includes only one type of data, including packetized or multiplexed data. For example, each MMT asset 230 may be one of the following: at least a portion of an elementary stream of audio, an MPEG user interface (MPEG user interface, MPEG-U) widget packet, at least a portion of an MPEG-2 transport stream, at least a portion of an MPEG-4 (MP 4) file, and all or at least a portion of an MMT packet.

For convenience, it will be noted that the term elementary stream may be interchanged with the term ES, the term transport stream with the term TS, the term MMT-CI with the term CI, and the term MMT-TC with the term transport characteristics (transport characteristics, TC). Here, the elementary streams are defined by a specific media CODEC and may logically be one or more MMT assets. MMT assets 230 supporting layered CODECs and multi-view CODECs can overlap with other MMT assets.

The MMT-CI represents information defining the spatial and temporal relationship of the MMT asset, and the MMT-TC defines the quality of service (quality of service, qoS) required to deliver the MMT asset. MMT-TC may be represented as asset delivery characteristics (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 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 disclosure will be described with reference to fig. 3.

Fig. 3 schematically illustrates a logical structure of an MMT packet in an MMT system according to an embodiment of the 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) of the MMT asset 320 and location information, and the MMT assets 320 within the MMT package 300 may be multiplexed or concatenated.

Processing of the MMT package 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 TC associated with each of the one or more MMT assets 320 is represented by one or more ADCs 330. The one or more ADCs 330 may be used to configure parameters of the MMT payload and header information of the MMT packet by an 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 MMT systems, MMT signaling function regions define message formats related to media consumption and media delivery.

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

A Packet Access (PA) message for a purpose similar to the program map table (program map table, PMY) of the MPEG-2TS includes all information required to present the transmitted packets. PA messages are messages that need to be sent first to receive and consume MMT packets, and individual information can be updated by additional messages.

Media presentation information (media presentation information, MPI) messages providing the expression information are used to send various expression information, such as CI defined in international organization for standardization (international organization for standardization, ISO)/international electrotechnical commission (international electronical committee, IEC) 23008-11, media presentation description (media presentation description, MPD) defined in ISO/IEC23009-1, and so on.

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

The clock relationship information (clock relation information, CRI) message provides mapping information between the MPEG-2 network time protocol (network time protocol, NTP) timestamp and the system timing clock (system timing clock, STC) for synchronization between the MMT asset and the MPEG-2 ES.

The device capability information (device capability information, DCI) message provides terminal capability information required for media consumption.

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

Application services that provide various additional information by interacting with a broadcast program or independently provide various additional information based on a hybrid transmission technology that realizes a converged multimedia service by organically interacting a broadcast network and a communication network are considered to be indispensable success factors for next-generation broadcast services, and to provide image contents in which reality and reality 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, popularity choices, 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 (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 broadcast network or a communication network and 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 an overall attribute 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. Application services that interact with broadcast programs may provide a greater variety and richness of broadcast services by transmitting event information with broadcast programs. Here, an event includes a notification, e.g., a timing notification to an application service, a timing notification indicating that an action is to be taken.

An operation procedure 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 illustrates an operation procedure of a terminal for running an application service in an MMT system according to an embodiment of the disclosure.

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

Referring to fig. 4, at operation 405, 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 410, the terminal acquires signaling information of an application service related to a broadcast program through an application information stream as a channel providing the signaling related to the application service, and receives a data network required to run the application service using a broadcast network or a communication network, if any. For convenience, the signaling information and data for the application service 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 operation of an application service Y that provides additional information for the advertisement product at a particular portion of performance X (e.g., at the beginning of the advertisement). At operation 420, the terminal runs the application service Y, i.e., the 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 for 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 that may be used in the MPI table may include location 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 transmission protocols 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 an operation of the application service based on an 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 disclosure will be described with reference to fig. 5.

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

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

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 the following: MMT data receiver 510, real-time object delivery over unidirectional transport (ROUTE) data receiver 515, hypertext transfer protocol (hypertext transfer protocol, HTTP) data receiver 520, and XXX data receiver 525 to receive packets transmitted over a communication network or a broadcast network based on at least one of a transmission protocol such as MMT protocol, ROUTE protocol, and HTTP, and to output the received packets to file data receiver 530, media data receiver 540, or signaling data receiver 550 based on the type of the received packets. Here, XXX data receiver 525 denotes a data receiver for receiving packets transmitted based on transmission protocols other than MMT protocol, ROUTE protocol, and 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 (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 a packet transmitted through one of various file transfer protocols, extracts desired data from the received packet, and outputs the extracted data to the file processor 535. The file processor 535 configures a 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 in the MMT scheme, the media processor 545 may process the media data transmitted in the 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 of media data transfer through 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 complies with the dynamic adaptive streaming over HTTP (dynamic adaptive streaming over HTTP, DASH) format defined in ISO/IEC 23009-1, the media processor 545 may process the media data for transmission based on the ROUTE protocol. At this time, the media processor 545 generates a DASH segment by processing ROUTE packets output from the ROUTE data receiver 515, and presents the DASH segment through the service display 570.

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

If the packet output from the data receiver 505 includes signaling information, the packet is output to the signaling data receiver 550, thereby being used for the signaling data receiver 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 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 a 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.

The 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 an application service may be transmitted through a dedicated signaling channel or media data. That is, event information related to control of an application service may be included in 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. As another example, in a DASH scheme, signaling information may be sent through MPD or DASH segments that include media data. That is, in a DASH scheme, signaling information may be included in an MPD or DASH segment.

Therefore, in case 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 operation of each application service, and displays information about each application service through the service display 570. To this end, application manager 565 interacts with signaling processor 555 and file processor 535 to receive data and signaling information needed to provide application services.

A procedure of 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 as follows.

1) Transmission of signaling information related to application services

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

In embodiments of the present disclosure, an application information table (application information table, AIT) message, which is a signaling message sent over an MMT signaling session, may be used to send 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 the formats of the AIT message and the AI table included in the AIT message.

TABLE 1

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

In table 1, the message_payload field indicates the payload of the AIT message, and the 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 (uniform resource identifier, URI) for identifying the AIT message exists in the extension portion. 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 package may be transmitted through one AI table or a plurality of AI tables. Here, it will be noted that an AI table including information about all application services may be referred to as a complete AI table, and an AI table including a part of information about 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 indicates an ID of the AI table. The complete AI table and the subset AI table may have different table_ids. the values of the table_id field are sequentially allocated, 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" of the table_id-base subset AI table. The basic 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, not 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 the 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 table is independent (when the value of the ai_table_mode field is 2)).

Here, the ai_table_mode field indicates ai_table_mode indicating a processing scheme of the segmented AI table in case the AI table is segmented, 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, then all subset AI tables pre-stored in the MMT receiving entity with higher subset AI table numbers up to 14 are considered to have expired, except where AI_table_mode is in independent mode. Here, the MMT receiving entity includes a terminal. If the subset AI table number is not 0 and the value of AI_table_mode is 1, then the contents of the subset AI table having a different version than the version of the subset-0A 1 table stored in the MMT receiving entity will be ignored. If the subset AI table number is not 0 and the value of ai_table_mode is field 0, the contents of the subset AI table having a different version than 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 the 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, the MMT receiving entity will receive all subset AI tables with the lower subset AI table number having the same version as the AI table before processing the AI table. For example, if the MMT receiving entity does not receive a subset-2 AI table with the same version, the MMT receiving entity may not process the subset-3 AI table. In order_ir_release_processing_mode, if the AI table number of the subset AI table is not 0, the MMT receiving entity needs to process the AI table immediately after receiving the AI table 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 separately. 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	Reservation (Reserved)

Further, in table 2, an ai_table_descriptor_bytes field indicates a descriptor of an 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, the information related to the application service may be transmitted through an MPT message, which is a signaling message related to the MMT packet.

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

Upon detecting the presence of an application service within the MMT package through the MPT message, the terminal may acquire detailed information related to the application service by receiving the described AIT message.

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

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

TABLE 5

In table 5, the descriptor_tag field indicates a tag for identifying an index_event_descriptor field, the descriptor_length field indicates a length of the index_event_descriptor field, and the application_service_descriptor field indicates whether an application service exists within a packet. For example, if the value of the application_service_descriptor field is 0, this means that the application service does not exist within the package. If the value of the application_service_descriptor field is 1, this means that the application service exists within the package. Information related to the application service is transmitted through an AIT message.

2) Event information transmission

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

First, in a case where the time at which an event occurs can be known in advance (such as recorded broadcasting), a static event transmission scheme is used.

Second, in cases where the time at which an event occurs may not be known in advance (such as live broadcast), a dynamic event transmission scheme is used.

Event information is notified to the application service.

In one embodiment of the present disclosure, event information may be sent via MMT signaling messages (i.e., application event information (application event information, AEI) messages) sent via MMT signaling channels. 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 (e.g., AEI messages and application event (application event, AE) tables included in 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 can also include an ID for identifying the service at the extension to which the AEI message applies. The AEI message may also include a 1-bit flag indicating whether the URI is used to identify the AEI message at the extension. 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, the table_id field indicates the ID of the AE table. In table 7, the version field indicates the version of the AE table, and the length field indicates the 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, the number_of_app_events field indicates the number of events included in the AE table, and the ae_descriptor () field includes information of each event.

Event information is stored at the ae_descriptor () field, and may include various information related to an 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 a 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 one application_identifier () field.

TABLE 9

In table 8, the schema_id_uri_length field indicates the length of the schema_id_uri. For example, the schema_id_uri_length field may indicate a length in bytes. In table 8, the scheme_id_uri field defines the meaning and grammar (grammar) of a value transmitted through the event_data field, and the event_value_length field indicates the 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 values is determined by schema_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 at which the event is to be applied, an event_duration field indicates a media presentation time during which the event is available, and event_data indicates event content.

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

In the MMT protocol, media data is included in an MPU, which follows the ISOBMFF structure. 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 (scContainer): MPU (micro processing unit)

Mandatory: not be

Number of: zero or more

Grammar:

the } hemejd_uri field includes the meaning and syntax of the value transmitted through the event_data field, and the event_value field includes an event value. The range and meaning of the event values is determined by schema_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 the 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 an 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 embodiments of the present invention, event information is sent by an MPU included in an asset, and MMT signaling information may be used to inform that event information is included in the MPU included in the asset.

For this, the MP table transmitting MMT packet information includes an in_event_descriptor as a descriptor used at an asset level (asset-level).

The terminal may detect that event information is included in the MPU included in the asset by receiving the ink_event_descriptor via the MP table. Upon detecting that event information is included in an MPU included in an asset, the terminal receives the MPU and acquires event information from an evti box included in the MPU.

Table 11 shows an example of the format of the ink_event_descriptor.

TABLE 11

In table 11, a descriptor_tag field indicates a tag for identifying an index_event_descriptor, a descriptor_length field indicates a length of the index_event_descriptor, a schema_id_uri_length field indicates a length of the schema_id_uri, and a schema_id_uri field defines a meaning and a syntax of a value transmitted through an event_data field. For example, the schema_id_uri_length field may indicate a length in bytes.

In table 11, the 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 values is determined by schema_id_uri.

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

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

Referring to fig. 6, the terminal detects that a service is selected at operation 605. At operation 610, the terminal monitors reception of the MMT signaling message related to the service and parses the received MMT signaling message related to the service when the MMT signaling message is received. 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, and the like, based on the attributes of the application included in the AI table and the input parameters.

The terminal monitors reception of an AEI message as a signaling message including event information, and acquires information about 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 of the application service based on the event at operation 635. The control operations of the application service may include operations for initiating the application service, operations 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 MMT signaling messages in an MMT system according to an embodiment of the disclosure, various changes may be made to fig. 6. For example, while shown as a series of operations, the various operations in FIG. 6 may 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 illustrates a process for processing event information based on an MPU in an MMT system according to an embodiment of the disclosure.

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

If the MMT signaling message does not include the 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 an 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, and the like, based on the attributes of the application included in the AI table, and the input parameters.

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

If the asset level descriptor indicates that event information is included in the MPU, the terminal extracts event information from the MPU included in the asset and stores the event information every time 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 event application times may be obtained from an AE table within an AEI message. If the event application time is reached, the terminal performs a control operation of 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 disclosure, various changes may be made to fig. 7. For example, while shown as a series of operations, the various operations in FIG. 7 may overlap, occur in parallel, occur in a different order, or occur multiple times.

In embodiments of the present disclosure, the signaling table and descriptors are encapsulated as mmt_attc3_message () that can be configured as in table 12, and mmt_attc3_message () can be sent in MMTP's signaling message mode.

TABLE 12

In table 12, the message_id field indicates the ID of mmt_attc3_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_attc3_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_attc3_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_attc3_message () may be the number of bytes from the next byte after the length field to the last byte of mmt_attc3_message ().

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

In table 12, an attc3_message_content_type field indicates the type of information transmitted through a payload included in mmt_attc3_message (). The atsc3_message_content_type field may be implemented with a 16-bit field.

For example, the attc3_message_content_type field may indicate a value as shown in table 13.

TABLE 13

atsc3_message_content_type	Meaning of
		0x0000	Reservation of
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, an attc3_message_content_version field indicates a version of information transmitted through a message payload included in mmt_attc3_message (). For example, the atsc3_message_content_version field may be represented by an 8-bit field. The message payload may be distinguished based on a combination of service_id and atsc3_message_content_type.

In table 12, an atsc3_message_content_compression field indicates a compression scheme applied to an atsc3_message_content_byte field included in a message payload included in mmt_atcc3_message (). For example, the attc3_message_content_compression field may be implemented with an 8-bit field.

In table 12, the uri_length field indicates the length of the URI used to identify the message payload. For example, the uri_length field may be implemented with an 8-bit field. In the case that the URI is not used, the value of the uri_length field may be set to 0.

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

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

Meanwhile, mmt_atcc3_message () shown in table 11 may transmit signaling information of all formats including an extensible markup language (extensible markup language, XML) format, a binary format, etc. through a message payload, and a format of each signaling information may be identified using atcc3_message_content_type.

In the case where an in band_event_descriptor is transmitted through a payload included in mmt_attc3_message () in table 12, according to an embodiment of the present disclosure, the in band_event_descriptor may have a format as shown in table 14.

TABLE 14

In table 14, a descriptor_tag field indicates a tag for identifying an index_event_descriptor, a descriptor_length field indicates a length of the index_event_descriptor, and a number_of_assets field indicates the number of assets described in the index_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 the asset ID. For example, the asset_id_length field may indicate a length in bytes.

In table 14, a schema_id_uri_length field indicates the length of the schema_id_uri, and the schema_id_uri field defines the meaning and grammar of the value transmitted through the event_data field. For example, the schema_id_uri_length field may indicate a length in bytes.

In table 14, the event_value_length field indicates the length of the event_data field, and the event_data field includes an event value. The range and meaning of the event value is determined by the scheme_id_uri, and the event_value_length field may indicate a length in bytes.

In embodiments of the present invention, event information is sent by an MPU included in an asset, and MMT signaling information may be used to inform that event information is included in the MPU included in the asset. To this end, mmt_attc3_message () includes an index_event_descriptor as a descriptor used at the asset level in the payload.

The terminal may acquire an in band event descriptor through mmt_attc3_message (), and receive an MPU included in the asset when event information included in the MPU is detected, and may acquire event information from an evti box included in the MPU.

The internal structure of a transmitting apparatus in an MMT system according to an embodiment of the 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 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 transmission apparatus 800. More specifically, according to an embodiment of the present disclosure, the controller 813 controls operations related to an operation of transmitting and receiving event information in the MMT system. Operations related to operations of transmitting and receiving event information in an 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 detailed descriptions thereof will be omitted herein.

The transmitter 811 transmits various signals and various messages to other entities (e.g., MMT receiving entities 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 detailed descriptions 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 an MMT system, etc.) under the control of the controller 813. The various signals and the various messages received in the receiver 815 have been described with reference to fig. 1 to 7 and tables 1 to 14, and detailed descriptions thereof will be omitted herein.

The storage unit 817 stores various programs, various data, and the like related to operations related to 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. 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 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. The various signals and the various messages outputted by the output unit 819 have been described with reference to fig. 1 to 7 and tables 1 to 14, and detailed descriptions 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 for convenience of description only. 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 one processor.

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

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

The reception 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 reception apparatus 900. More specifically, according to an embodiment of the present disclosure, the controller 913 controls operations related to an operation of 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 transmitting 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 detailed descriptions thereof will be omitted herein.

The receiver 915 receives various signals and various messages from other entities (e.g., MMT transmitting entities 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 detailed descriptions thereof will be omitted herein.

The storage unit 917 stores various programs, various data, and the like 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. 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 operation 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 913. The various signals and the various messages output by the output unit 919 have been described with reference to fig. 1 to 7 and tables 1 to 14, and detailed descriptions 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 reception 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 combined into a single unit.

The receiving device 900 may be implemented with 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 transmission and reception of event information related to an event in a multimedia system.

Embodiments of the present disclosure enable provision of event information related to events together with multimedia services 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 (random access memory, RAM), compact disc ROM (CD-ROM), magnetic tapes, floppy discs, optical data storage devices, and carrier waves (such as data transmission through the internet). The non-transitory computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. In addition, functional programs, codes, and code segments for accomplishing the present disclosure can be easily construed by programmers skilled in the art to which the present disclosure pertains.

It is to be understood that methods and apparatus according to embodiments of the present disclosure may be implemented in hardware, software, and/or combinations thereof. The software may be stored in a non-transitory storage (e.g., erasable or rewritable ROM), memory (e.g., RAM, memory chip, memory device or memory integrated circuit (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.). Methods and apparatus in accordance with embodiments of the present disclosure may be implemented by a computer or mobile terminal including a controller and memory, and the memory may be an example of a non-transitory machine-readable (e.g., computer-readable) storage medium adapted to store a program or programs including instructions for implementing various embodiments of the present disclosure.

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

An 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 instructions indicating that the content protection method that has been installed is executed, information required for the content protection method, and the like; a communication unit for performing wired or wireless communication with the graphic processing apparatus; and a controller for transmitting the related program to the transmitting/receiving device based on a request of the graphic processing device or automatically transmitting the related program to the transmitting/receiving device.

While the present 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 present 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 an event is received,

wherein the event comprises a notification to the 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, the event information is received in a first event information box included in the media presentation description MPD,

Wherein if the event information indicates a second event for a service for moving picture expert group media based transmission MMT, 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 an 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 at which the MPU is presented and a time at which 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:

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

6. A receiving apparatus, comprising:

a processor; and

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

7. The receiving device of claim 6, wherein if the event information indicates a second event for an 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.

8. The reception apparatus according to claim 7, wherein the start time of the event includes a difference between a time at which the MPU is presented and a time at which the event is applied into 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: