Method and apparatus for transmitting media data in multimedia transport system.
Abstract
A method for transmitting media data in a multimedia system, the method comprises: generating at least one multimedia data packet in association with a multimedia transmission unit, each multimedia data packet includes a packet header and a payload; and transmitting at least one multimedia data packet; wherein a payload header included in the payload includes: the identification information identifying the multimedia transmission unit that corresponds to the payload; the fragment indication information indicating the information related to a fragmentation of a data unit in the payload; a flag that indicates whether or not the aggregated data units are included in the load; a counter value related to a number for the next fragmented uploads from the multimedia transmission unit, the type information indicating a type of data included in the upload.

Term
7.6 yearsleft in the term
Expires 21 April 2034.
- Priority
- Filed
- Granted
- Today
- Expires
4 claims: 3 independent, 1 dependent
- 1CLAIMS REIVINDICACIONES IMPI IMPI INSTITUTO MEXICANO DE LA PRüFltDAlí INDUSTRIAL MEXICAN INSTITUTE DE LA PRüFltDAlí INDUSTRIAL Habiéndose descrito la invención como antecede, se reclama como propiedad lo contenido en las siguientes reivindicaciones:Having described the invention as above, the content of the following claims is claimed as property: 1. A method for transmitting multimedia data in a multimedia transmission system, characterized in that it comprises: 1. Un método para transmitir datos multimedia en un sistema de transmisión multimedia, el cual caracterizado porque comprende: generar al menos un paquete de datos multimedia relacionado con una unidad de transmisión de multimedia, en donde cada uno de al menos un paquete de datos multimedia comprende un encabezado de paquete y una carga que comprende datos multimedia;generating at least one multimedia data packet related to a multimedia transmission unit, wherein each of the at least one multimedia data packet comprises a packet header and a payload comprising multimedia data;transmitir el al menos un paquete de datos multimedia;transmitting the at least one multimedia data packet;en donde un encabezado de carga incluido en la carga incluye información de tipo que indica un tipo de datos incluido en la carga, información de indicación de fragmentación que indica información relacionada a fragmentación de los datos incluidos en la carga, información de bandera que indica si los datos incluidos en la carga son una pluralidad de unidades de datos, si se incluye un fragmento fragmentado desde la unidad de datos en la carga, un valor de contador relacionado al fragmento, en donde la información de tipo indica que los wherein a payload header included in the payload includes type information indicating a type of data included in the payload, fragmentation indication information indicating information related to fragmentation of the data included in the payload, flag information indicating whether the data included in the load is a plurality of data units, if a chunk fragmented from the data unit is included in the load, a counter value related to the chunk, where the type information indicates that the INSTITUTO MEXICANO datos incluidos en la carga es uno de metadaC^^'IJ^ de transmisión de multimedia, metadato de transmisión de multimedia, metadato relacionado a la unidad de datos, una unidad de datos que comprende información del tiempo, o una unidad de datos excepto por la información del tiempo. MEXICAN INSTITUTE data included in the upload is one of multimedia transmission metadata C ^^ 'IJ ^, multimedia transmission metadata, data unit related metadata, a data unit comprising weather information, or a data unit except for the weather information.
- 2The method according to claim 2. El método de conformidad con la reivindicación 1, caracterizado porque el valor de contador es información relacionada a un número de fragmentos detrás del fragmento incluida la carga. 1, characterized in that the counter value is information related to a number of fragments behind the fragment including the load.
- 3The method according to claim 3. El método de conformidad con la reivindicación 1, caracterizado porque la información de indicación de fragmentación indica que al menos una unidad de datos es incluida en los datos o el fragmento fragmentado desde la unidad de datos es incluido en los datos. 1, characterized in that the fragmentation indication information indicates that at least one data unit is included in the data or the fragmented fragment from the data unit is included in the data.
Independent claims3
288 paragraphs in 18 sections, as filed
(54) Title: METHOD AND APPARATUS FOR TRANSMITTING MEDIA DATA IN A MULTIPLE MEDIA TRANSPORTATION SYSTEM.
(54) Title: METHOD AND APPARATUS FOR TRANSMITTING MEDIA DATA IN MULTIMEDIA TRANSPORT SYSTEM.
(57) Summary
A method for transmitting media data in a multimedia system, the method comprises: generating at least one multimedia data packet in association with a multimedia transmission unit, each multimedia data packet includes a packet header and a payload; and transmitting at least one multimedia data packet; wherein a payload header included in the payload includes: the identification information identifying the multimedia transmission unit that corresponds to the payload; the fragment indication information indicating the information related to a fragmentation of a data unit in the payload; a flag that indicates whether or not the aggregated data units are included in the load; a counter value related to a number for the next fragmented uploads from the multimedia transmission unit, the type information indicating a type of data included in the upload.
(57) Abstract
A method for transmitting media data in a Moving Picture Experts Group (MPEG) Media Transport (MMT) system is provided. The method ineludes receiving a Media Processing Unit (MPU) fragmented into one or more Media Fragment Units (MFUs); generating one or more multimedia data packets each including a packet header and a payload, based on the MPU, and transmitting the one or more multimedia data packets to a terminal. A payload header included in the payload includes identification Information indicating an MPU to which at least one MFU included in the payload belongs, and a counter indicating the number of the at least one MFU.
IMPI
<img file="MX348574B_D0001.tif" />
«Or **
PATENT TITLE No. 348574
Owner (s): SAMSUNG ELECTRONICS CO, LTD.
Address: 129, Samsung-ro, Yeongtong-gu, Suwon-si, Gyeonggi-do, 16677, REPUBLIC OF
KOREA
Name: METHOD AND APPARATUS FOR TRANSMITTING MEDIA DATA IN A MULTIPLE MEDIA TRANSPORT SYSTEM.
Classification: CIP: H04N21 / 236; H04L29 / 06
CPC: H04N21 / 23614; H04N21 / 2381; H04N21 / 4343; H04N21 / 4348; H04N21 / 4381;
H04N21 / 64322; H04N21 / 85406
Inventor (s): KYUNG-MO PARK; SUNG-OH HWANG; SUNG-RYEUL RHYU; JAE-YEON SONG
REQUEST
Number: International Presentation Date:
MX / a / 2015/014695 April 21, 2014
PRIORITY
Country: Date: Number:
KR April 19, 2013 10-2013-0043855
Validity: Twenty years
Expiration Date: April 21, 2034
Issue Date: June 20, 2017 ....... ......>
The reference patent is granted based on articles 1<sup>or</sup>, 2<sup>or</sup> fraction V, 8 · fraction M, and 59 of the Industrial Property Law.
In accordance with article 23 of the Industrial Property Law, this patent is valid for twenty years, non-extendable, counted from the filing date of the international application and will be subject to the payment of the fee to keep the rights in force.
Whoever signs this title does so based on the provisions of articles 6<sup>or</sup> fractions III and 7<sup>or</sup> bis 2 of the Industrial Property Law (Official Gazette of the Federation (OOF) 06/27/1991, amended on 08/02/1994, 10/25/1306, 12/26/1997, 05/17/1999, 01/26/2004, 06/16/2005, 01/25/2006, 05/06/2009, 06/01/2010, 06/18/2010, 06/28/2010, 01/27/2012 and 09/09 04/2012): articles 1<sup>or</sup>, 3 * fraction V part a), 4<sup>or</sup> and 12th sections I and III of the Regulations of the Mexican Institute of Industrial Property: DCF J4M2 / 1399; ' amended on 07/01/2002, 07/15/2004, 07/28/2004 and 09/07/2007); items 1<sup>or</sup>, 3<sup>or</sup>, 4<sup>or</sup>, 5 'section V subsection a), T8 sections I and fll and 30 of the Organic Statute of the Mexican Institute of Industrial Property (DOF 12/27/1999, amended on 10/10/2002, 07/29/2004, 04 / 08/2004 and 13/09/2007), 1<sup>or</sup>, 3 and 5 'subsection a) of the Agreement that delegates powers to the Deputy General Directors. Coordinator, Divisional Directors / ^ Titulares ^ de, Regional Offices, Divisional Deputy Directors, Departmental Coordinators and other subordinates of the Mexican Institute of Industrial Property, (D OF 12/15/1999, amended 02/04/2000, 07/29 / 2004, 08/04/2004 and 09/13/2007).
This document is signed with an advanced electronic signature (FIEL), based on articles 7 BIS 2 of the Industrial Property Law; 3 of its Regulations, and 1 section III, 2 section V, 26 BIS and 26 TER of the Agreement establishing the guidelines for the use of the Payment and Electronic Services Portal (PASE) of the Mexican Institute of Industrial Property, in the procedures indicated.
<td></td><td>THE DIVISIONAL DIRECTOR OF PATENTS</td>
<td></td><td>NAHANNY CANAL REYES Original string:</td>
<td></td><td>NAHANNY MARISOL CANAL REYES | 00001000000403252793 | Administration Service Tax | 1695 || MX / 2017/48565 | MX / a / 2015/014695 | Patent title PCTl1027 | RGZ | Page (s) 1 | U8e80pJLrYZs7LP3z6UurQHhsAk = iMr & JTjWMrai Digital stamp:</td>
<td>ace</td><td>U9THvwqS5OuXL3aRZ / BvKq0tlda8GEcE1u + iOIMOMzYevqp3irZGRa8UA6ci64Gmyvb / fGeZ55ZfB8UeeBUBGY2aw8 JKJSMÍE? dpssYnz0DsVCyaKfWUX¡8ipPGQyPQTKx7Q8DF4a2xaQ3wGWnlbO86eJsS1e0mXbMSQ6NyekMNzw8ATnKsndt7joNpP SsSrSsPS 17nO2nNjanjBuXxXpLt3NkqUOdy3HAFFGLbl0WSdlOKHbyNsOKHlQsUqKHorc8t3EbtyS20DCqtxCsxCLKhd3c / eup</td>
<td></td><td>dxljy + nVNnBO + KLRvOGi7YpshCfEOZ9BYNQTMWx / 8Z9KQ / 6mPlqLI8PvraV8kPu5D + / OEvkg ==</td>
Arenal No. 550 Floor 1, Pueblo Santa Mana Tepepan, Xochii Tiilco. 16020, validity in Mexico.
(55) 53340700 www, gob, rnx / impi
<img file="MX348574B_D0002.tif" />
METHOD AND APPARATUS TO TRANSMIT DATA FROM • MEXICAN INSTITUTE fSMí • FROM «OPIEUAD 1Λ.
_ INDUSTRIAL
MULTIPLE COMMUNICATION MEDIA TRANSPORTATION SYSTEM
Field of Invention
The present description relates to an apparatus for generating and transmitting a multi-media transport packet in a multi-media transport system providing a multi-media service, and a method thereof.
Background of the Invention
Generally, interactive services such as multicast, broadcast and video telephony, and 24/7 streaming services such as Video on Demand (VOD) service are referred to as multi-media services. Multi-media services can be classified into real-time multi-media services and non-real-time multi-media services. Real-time multi-media services can be classified into unicast services, multicast services, and broadcast services depending on the number of users thereof. In addition, real-time multi-media services can be classified into interactive services and streaming services.
Ref. 260223 depending on the type of service.
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY
<img file="MX348574B_D0003.tif" />
In the multi-media network of the related art, the Transport Stream (TS) of the Moving Picture Experts Group (MPEG) -2 has been used for the streaming of multiple media content. MPEG-2 TS has been used as a transmission technology to transmit a multiplexed bitstream of a plurality of multiple media programs (e.g., a plurality of encoded video bitstreams) in a transmission environment that provides a fixed bandwidth that has errors. For example, MPEG-2 TS has been suitably used in multi-media devices such as Digital Televisions (TVs) in the multi-media era.
FIGURE 1 illustrates a hierarchical structure to support MPEG-2 TS according to the related art.
• With reference to FIGURE 1, the layers to support MPEG-2 TS may include a media encoding layer 110, a sync layer 120, a delivery layer 130, a network layer 140, a data link 150 and a physical layer 160.
The media encoding layer 110 and the sync layer 120 can be configured in one format, in which the
IMPI ^
INSTITUTE - MLXíCaNí>, media data (or media carrier) can be used as a basic unit for transmission. Delivery layer 13 0, network layer 14 0, data link layer 150, and physical layer 160 can configure one block of data (for example, an Access Unit (AU)) in the format configured by the sync layer 12 0, as a multi-media transport packet that is written to a separate recording medium or that is transmitted. The configured multi-media transport packet can be transmitted to a subscriber terminal through a predetermined network.
For this purpose, the sync layer 120 may include a chunk block 122 and an access unit 124. Delivery layer 130 may include an MPEG-2 TS / MP4 Real Time Transport Protocol (RTP) Payload format / File Delivery over One-Way Transport (FLUTE). 132, RTP / Hypertext Transfer Protocol (HTTP) 134 and User Datagram Protocol (UDP) / Transmission Control Protocol (TCP). English) 136.
However, MPEG-2 TS may have several limitations in supporting multiple media services. Specifically, the limitations of
IMPIAS
MEXICAN INSTITUTE.
MPEG-2 TS may include a communication transmission deficiency due to fixed page size and unnecessary transfer which can occur when data is transmitted using a specific transport protocol for audio / video and an Internet Protocol (IP).
Therefore, an MPEG Media Transport (MMT) standard has recently been proposed by MPEG as one of the multi-media transport technologies to support multi-media services based on MPEG technology. In particular, the MMT standard has been proposed by MPEG to overcome the limitations of MPEG-2 TS.
For example, the MMT standard can be applied to efficiently transmit hybrid content over a heterogeneous network. The term hybrid content as used herein can refer to a set of content that has multiple media elements for audio, video, applications, and the like. The term "heterogeneous network" as used herein may refer to a network in which a multiple media network, a communication network, and the like are mixed.
Furthermore, the MMT standard is intended to
INSTITUTE MtXiCANv Give the FKOFüDAD to define the transmission technology adapted d ^ S ^ alTtteífeer for IP which is now the basic technology '^' BH la ved-de · - transmission for multiple media services.
Therefore, continuous research and standardization has been conducted on the MMT standard to provide efficient MPEG transport technology in the typical multi-media service environment that varies on an IP basis.
The above information is presented as background information only to aid in an understanding of the present description. No determination has been made, and no statement is made, as to whether any of the foregoing might be applicable as prior art in connection with the present disclosure.
Brief Description of the Invention Technical Problem
In particular, in the MMT standard, there is a need for a way to provide efficient MPEG transport technology in the hybrid network environment in which a single terminal connects to a plurality of networks and provides media services. multiple, and in the recent multi-media service environment designed to provide hybrid content that is comprised of not just data from
IMPI ^
MEXICAN INSTITUTE
OF THE audio and video PROPERTY but also the application, gadget ^^^ hiag & ff ^ and the like, and that can be consumed in the un-Trauagio terminal ·; Solution to the problem
The aspects of the present description are to solve at least the problems and / or disadvantages mentioned above and to provide at least the advantages described below. Accordingly, one aspect of the present disclosure is to provide a method and apparatus for configuring a multi-media transport packet in a multi-media system that supports Internet Protocol-based multi-media services ( IP).
Another aspect of the present disclosure is to provide a method and apparatus for creating a multi-media transport package based on multi-media data for hybrid content or hybrid service that is created based on Media Transport technology. (MMT) of the Moving Pictures Expert Group (MPEG) and transmit the created multi-media transport package.
According to one aspect of the present description, a method is provided for transmitting media data in a multimedia system, the method comprises: generating at least one multimedia data packet in association with a multimedia transmission unit, each data packet
MEXICAN INSTITUTE 06 LA l'HOriíDAl) “I, INDUSTRIAL multimedia includes a packet header and a payload; and transmitting at least one multimedia data packet; wherein a 'payload header included in the payload includes: the identification information that identifies the multimedia transmission unit corresponding to the payload; the fragment indication information indicating the information related to a fragmentation of a data unit in the payload; a flag that indicates whether or not the aggregated data units are included in the load; a counter value related to a number for the next fragmented uploads from the multimedia transmission unit, the type information indicating a type of data included in the upload.
Brief Description of Figures
The foregoing aspects, qualities and advantages and other aspects, qualities and advantages of certain embodiments of the present description will be more apparent from the following description taken in conjunction with the associated figures, in which:
FIGURE 1 illustrates a hierarchical structure to support Moving Picture Expert Group (MPEG) -2 Transport Stream (TS) according to related art;
FIGURE 2 illustrates a structure of a multiple media payload for transmitting an MPEG Media Transport (MMT) based Packet (MMTP).
MEXICAN INSTITUTE Jj in multi-service / content through a network ° 'ti ^ D¿ ^^ t¿!
Internet (IP) in an MMT system according to one mode of the present description;
FIGURE 3 is a control flow diagram for configuring an MMTP packet and for transmitting a configured MMTP packet in an MMT system in accordance with one embodiment of the present disclosure;
FIGURE 4a schematically illustrates an example of a configuration of a Media Processing Unit (MPU) in accordance with one embodiment of the present disclosure;
FIGURE 4b illustrates an example of a Media Fragment Unit (MFU) configuration that can be created based on the MPU file in FIGURE 4A in accordance with one embodiment of the present disclosure;
FIGURE 4c illustrates an example of a detailed configuration of an MFU in accordance with one embodiment of the present disclosure;
FIGURE 4d illustrates an example of a configuration of a payload that is configured based on the MFU in FIGURE 4c in accordance with one embodiment of the present disclosure;
FIGURE 5 illustrates an example of a method to configure a payload of a building block of
WICKED
INSTITUTE MEX1CANU
OF THE PKOPlbDAL ·
MPU / MFU that is configured based on the 3 ^ Ηίνο '<sup>Ν</sup>^§<sup>κ1</sup>^ Ρυ> εϊϊ - ΪΈ FIGURE 4a and to create an MMTP package of<sup>1</sup> eorr uner agreement · mode of the present description;
FIGURES 6a and 6b illustrate examples of MPU configurations that are distinguished depending on real-time requirements according to one embodiment of the present disclosure;
FIGURE 7 illustrates an example of the configuration of an MPU providing the real-time multi-media service in FIGURE 6a, in payload units in accordance with one embodiment of the present disclosure;
FIGURE 8 illustrates an example non-real time multi-media service configuration in FIGURE 6b in payload units according to one embodiment of the present disclosure;
FIGURE 9 illustrates a transmission entity for transmitting media data in an MMT system in accordance with one embodiment of the present disclosure; Y
FIGURE 10 illustrates a receiving entity for receiving media data in an MMT system in accordance with one embodiment of the present disclosure.
Throughout the figures, like reference numerals will be understood to refer to like parts, components and structures.
ΐΝίΠτυτι) MtxiCANC _. T DI Ul £ «OMkDAL · Detailed Description of the Invention * ^
The following description with reference to the associated figures is provided to aid in a comprehensive understanding of various embodiments of the present description as defined by the claims and their equivalents. It includes several specific details to aid in that understanding but these should be considered as exemplary only. Accordingly, those of ordinary skill in the field will recognize that various changes and modifications can be made to the various modalities described herein without departing from the scope and spirit of the present disclosure. Furthermore, 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 bibliographic meanings, but are only used by the inventor to enable a clear and consistent understanding of the present description. Accordingly, it should be apparent to those skilled in the field that the following description of various embodiments of the present description is provided for the purpose of illustration only and not for the purpose of limiting the description as defined by the appended claims and their claims. equivalents.
ΙΜΡΙ ^ 5
MEXICAN INSTITUTE
It should be understood that the forms a, el and la include referents nlnralps am ^ nncq<sub>11Q </sub>the context clearly dictates otherwise. Thus, for example, reference to a component surface includes reference to one or more of these surfaces.
By the term "substantially" it is meant that it is not necessary that the referenced characteristic, parameter or value be achieved exactly, but rather that deviations or variations, including for example tolerances, measurement errors, measurement accuracy limitations and other factors known to those people in the field, can occur in quantities that do not preclude the effect that the feature was intended to provide.
In the later-described embodiment of the present description, the hierarchical structure defined in the MPEG Media Transport (MMT) standard will be described. Furthermore, in one embodiment of the present disclosure, a way is provided for configuring a multi-media transport packet. Accordingly, a detailed description will be made of a layer-related operation to create a multi-media data packet according to an embodiment of the present description in the hierarchical structure defined in the MMT standard. In the present description, a media transport package
ΙΜΡΙ @ ^ multiple communication (referred to in omjyiatfgfi ^ MMTP packet) for an MMT service, it will be defined as a packet that transmits a transport payload configured from the MMT content. An MMTP (MMT Protocol) packet according to one embodiment of the present description may include Quality of Service (QoS) information related to the required transport information.
In one embodiment of the present description, a header information configuration for creating an MMTP packet will be described in more detail later. The header information may include information about the configuration of multiple media data of a desired size by fragmenting or combining multiple media data that is provided in units of a predetermined size in an upper layer, for a payload. of an MMTP packet.
One embodiment of the present disclosure may conceptually include an MMT service by means of a multi-media system (hereinafter referred to as an MMT system) based on the MMT standard.
Although Ultra High Definition (UHD), Video On Demand (VOD), 24/7 Live Streaming, Archives, Gadgets, Book
IΜ ΡI 5¾
MEXICAN INSTITUTE Electronico (Ε), metadata and similar content for the MMT service, will be aparpnt-p pav-a --- those people of ordinary experience in the field that the totality of other content that can be expressed as an electrical signal it may be the content for the MMT service.
Multiple media data for each of the variety of content can be encapsulated in a predetermined format by an MMT encapsulator, which configures an MMTP packet, and then the MMTP packet can undergo hybrid delivery to a subscriber's terminal across the heterogeneous network. The term heterogeneous network indicates a network for the transmission environment in which a multi-media network, Internet Protocol (IP), and the like are mixed.
Upon receipt of the MMTP packet which has undergone hybrid delivery over the heterogeneous network, the subscriber's terminal can extract data from multiple media corresponding to the desired content of the MMTP packet, and can provide, to the user, video, audio, application and the like that correspond to the extracted multiple media data. Each of the multi-media data corresponding to the video, audio, application and the like provided for the specific content is
<img file="MX348574B_D0004.tif" />
IMPI INSTITUTO MEXICANA, DE LA FROHEDAb will be defined as an asset. Subscriber terminal term may include 4α · most-do '-I-oo devices that can support multiple media services in one embodiment of the present disclosure. Typical examples of the subscriber's terminal can be an IP Television (TV), a smart phone and the like.
Therefore, the goals that can be achieved by the MMT service may include High Quality Content Delivery, Hybrid Content Support, Hybrid Network Support and the like.
FIGURE 2 illustrates an example of a hierarchical structure for transmitting a multi-service / content-based MMTP packet through a heterogeneous network in an MMT system in accordance with one embodiment of the present disclosure.
With reference to FIGURE 2, for the purpose of configuring an MMTP packet and transmitting the configured MMTP packet in the MMT system, a plurality of, for example, seven layers is required. The seven layers may include a media encoding layer 210, an encapsulation layer (hereinafter referred to as a Layer E) 220, a delivery layer (referred to as a Layer D or Layer T) 230 and 290, a network layer 240, a data link layer 250, a physical layer 260, and a Mexican control layer (hereinafter referred to as a Ca ^ a'ií ^^ L includes, for example, MMT Cl 270 and MMT C. 2 2 8 0., _
In accordance with one embodiment of the present disclosure, multi-service / content-based multiple media data can be created by media encoding layer 210 and E-Layer 220 between the seven layers. Therefore, these two layers can be considered as a configuration of a multi-media data generation unit. Furthermore, since an MMTP packet is configured by Layer D 230 among the seven layers, Layer D 230 can be considered as a configuration of a multi-media packet generation unit. In other words, Layer D 23 0 corresponding to the multi-media packet generation unit can configure the header information by means of a Packet Identifier (ID) to identify the MMTP packet, the quality of service connected at the network layer and the information required to measure the performance of the end-to-end network and can configure an MMTP packet by combining the header information with data from multiple media.
Among the seven layers, Layer E 220, Layer D 230, Layer D.3 290, Layer Cl 270 and Layer C.2 280 are very high in relevance to the MMT standard. La Capa E ~ MEXICAN INSTITUTE J
0 is responsible for the generation of content. £ ^ 4 & £ i®íjT ^^ Layer D 230 and Layer D.3 290 are responsible for the efficient transmission of the content created through the heterogeneous network and the Cl of MMT 2 70 and the C.2 of MMT 280 are responsible for the total operation for the consumption management and transmission management of the hybrid content.
The E Layer 22 0 may include an E.3 layer of MMT 222, an E.2 layer of MMT 224, and an El layer of MMT 226. The E.3 layer of MMT 222 can generate a media data chunk or a media chunk processing unit (for example, a Media Chunk Unit (MFU)), which is the basic unit for MMT service, through the use of the encoded multi-media data provided of the media encoding layer 210 as an input. The E.2 layer of MMT 224 can generate a Media Operation Unit or a Media Processing Unit (MPU) for MMT service using the MFU generated by the E.3 layer of MMT 222. The El layer of MMT 226 can generate hybrid content by combining and fragmenting the provided MPUs of the E.2 layer of MMT 224 and can generate a format for storing and transmitting the generated hybrid content.
The MPU is used to set the active value, multi-media data, multi-media data is either data
Timed IMPI or non-timed data.
individual is a collection of one or more MPUs, therefore the MPU is a container for timed or non-timed data decodable independently of other MPUs. Specifically, if it is timed data, a video is provided to a receiving entity, for example, the video includes one or more images, configuration information for processing each of the images. Each of the images is configured for an MFU and the MFUs are delivered to the receiving entity and the MPU is fragmented into data units, MFUs, smaller than the AU.
The D layer 230 may include a Dl layer of MMT 232 and a D.2 layer of MMT 234. The Dl layer of MMT 232 is responsible for configuring the MFUs that constitute an object unit (e.g. MPU) that is transmitted, in a structured packet payload to correspond to the MMTP packet structure. The D.2 layer of MMT 2 34 is responsible for an Application Protocol (AP) that plays a role similar to the Real Time Transport Protocol (RTP) or the Hypertext Transfer Protocol (HTTP). Layer D.3 of MMT 290 performs an operation for optimization between each layer constituting Layer E 220 and each layer constituting Layer D 230.
The Cl of MMT 270 can provide information related to the generation and consumption of hybrid content and the related C.2 of MMT
280
<img file="MX348574B_D0005.tif" />
with streaming hybrid content.
FIGURE 3 is a control flow diagram for configuring an MMTP packet and transmitting the configured MMTP packet in an MMT system in accordance with one embodiment of the present disclosure.
The operations in FIGURE 3 can be performed by MMT 234 D.2 which constitutes Layer D 230 between the layers described in FIGURE 2.
Referring to FIGURE 3, the D.2 of MMT 234 may receive multiple media data from the Dl of MMT 232 in step 310. The multiple media data that is sufficient to provide a hybrid service or content Hybrid of the Dl of MMT 232 and an active value of MMT corresponding to each of the multiple media data can be provided.
In operation 312, the D.2 of MMT 2 34 may configure the header information to configure an MMTP packet based on a payload that is configured depending on the multiple media data received in operation 310. The information The header information may include header information from an MMTP packet header region that is described in Table 5 below, and information about a payload header that is described in Table 2 below.
<img file="MX348574B_D0006.tif" />
The header may include at least one of a packet ID to identify an MMTP packet, the quality of service connected at the network layer, and the information required to measure end-to-end network performance.
In step 314, the D.2 of MMT 234 may configure an MMTP packet for a hybrid multi-media service. In other words, D.2 of
MMT 234 can configure an MMTP packet by combining the multiple media data received in step 310 with the header information configured in step 312.
After configuring the MMTP packet, the
D.2 of MMT 234 can transmit the configured MMTP packet to a subscriber terminal through the heterogeneous network in step 316.
A detailed description will now be made of a method for configuring an MMTP packet over a T.2 Layer which is responsible for transmitting an MMTP packet for an MMT service, according to one embodiment of the present description. The MMTP packet according to one embodiment of the present disclosure may include a header region and a payload region. In one embodiment of the present description, the header information that is written in the header region and the media data of
MUICANI INSTITUTE. OE THE PHoPItpAU multiple communication that are written in the regr® »useful craSSsfeifa must be defined. The packet of mmt ^ hIi · ^ .. ι, τ ^ ^ <-> in one embodiment of the present description must be defined to guarantee the required QoS.
Additionally, a plan capable of performing flow control for the MMTP packet configured in accordance with one embodiment of the present disclosure must also be prepared. Furthermore, the flow of control according to one embodiment of the present description and the function that an IP protocol provides by means of the QoS level must be capable of being superseded.
Finally, in an embodiment of the present description, in order to transmit the target unit (for example, MPU) that is desired to be transmitted, the procedure for exchanging information with other layers through Layer T.2 and the contents of information exchanged Due to the procedure and the delivery method of the same must also be defined.
Table 1 below illustrates an example of an MMTP packet structure in accordance with one embodiment of the present disclosure.
Table 1
MMTP Packet Header MMTP Payload
With reference to Table 1, the MMTP packet may include an MMTP packet header region and a
<img file="MX348574B_D0007.tif" />
IMPI
MEXICAN INSTITUTE DE LA PROPERTY payload region of MMTP. In the region of c'a'bece:
MMTP packet can be written info-de-eebeek & a & a-qua. corresponds to the control information used to receive multi-media data for the hybrid service / content transmitted by the MMTP packet. Multiple media data can be written to the MMTP payload region for hybrid / content service. The MMTP payload region can include a payload header and payload data.
Table 2 below illustrates an example of a payload header structure written in the MMTP payload region that makes up the MMTP packet. Table 2
MMT payload header
<td colspan="2">Lengthvariable</td><td colspan="2">Typevariable</td><td>fj</td><td>F T</td><td>TO Ό '</td><td>R 'one'</td><td>P 'one'</td><td>AND Ό '</td><td>S '0'</td>
<td>data_offset</td><td>flag_count</td><td>numDU</td><td colspan="8">DU_offset</td>
<td> .....</td><td colspan="2">DU_offset</td><td colspan="8"></td>
<td colspan="11">Payloadsequencenumber</td>
<td colspan="11">header_extension</td>
With reference to Table 2, the payload header may include the following information. The names, number of bits and values identified in this document are only one implementation and may be varied in other embodiments of the present description.
- length (16 bits): This information
<img file="MX348574B_D0008.tif" />
length of MMTP payload. If ge include spurious data (eg padding, null data, and the like) in the MMTP payload for the purpose of maintaining the length of the MMTP payload, the spurious data can be excluded.
- type (8 bits): This information represents the type of the data included in the MMTP payload. In Table 3, the information represents an example of the type of data that can be included in the MMTP payload.
Table 3
<td>Value</td><td>Type of data</td><td>Definition of Data Unit</td>
<td>0x00</td><td>MPU</td><td>An individually generically usefully loaded MPU.</td>
<td>0x01</td><td>MPU metadata</td><td>Metadata of an MPU.</td>
<td>0x02</td><td>Chunk metadata</td><td>Metadata of an MPU chunk.</td>
<td>0x03</td><td>MFU Aligned</td><td>An MFU that contains timed or non-timed data which is aligned with the payload boundary.</td>
<td>0x04</td><td>MFU</td><td>An MFU that contains timed or non-timed data which does not align with the payload limit.</td>
<td>0x05</td><td>signaling message</td><td>Complete signaling message, individual message.</td>
<td>0x06</td><td>Repair symbol Error Correction Without</td><td>Individual, complete FEC repair symbol.</td>
WICKED
ΙΝ.-ΓΙΤϋτ. ><sub>UI</sub>,„-----. ---
<td></td><td>Non-Return Channel (FEC)</td><td>----------------------------- '^ τιηιτυ Mexican- OF LA PKOPItbAU t INDUSTRIAL</td>
<td rowspan="2">0x07- 0x9F</td><td rowspan="2">ISO reserved for future use</td><td></td>
<td></td>
<td>OxAO - OxFF</td><td>Reserved for private use</td><td></td>
-MPU (0x00): The MPU can be configured as an MMTP payload without considering the internal structure information of the MPU that is desired to be transmitted. Therefore, the MMTP payload can be configured to include an MPU, or it can be configured to include a part of an MPU that is longer than that of the payload.
-MPU metadata (0x02): If an MMTP payload is configured considering the internal structure information of the MPU to be transmitted, the MMTP payload can include MPU metadata. The MPU metadata, which is control information for processing an MPU that constitutes the MMTP payload, may correspond to a codec parameter for encoding an MFU.
-Fragment metadata (0x03): If an MMTP payload is configured considering the internal structure information of the MPU that is desired to be transmitted, the MMTP payload can include fragment metadata. The chunk metadata can represent control information for a chunk unit of each of the MFUs included in the MMTP payload.
IMPI nSTITUTt) MEXICAN OF INDUSTRIAL PROPERTY
<img file="MX348574B_D0009.tif" />
-MFU aligned (0x04): If an MMTP payload is configured considering the internal structure information of the MPU that is desired to be transmitted, the MMTP payload can be configured considering an interval of MFUs. In other words, the aligned MFU represents that the MMTP payload includes at least one MFU, where at least the MFU is aligned to the payload limit of
MMTP.
-MFU (0x05): If an MMTP payload is configured considering the internal structure information of the MPU that is desired to be transmitted, the MMTP payload can include at least one MFU fragment, where at least the FMU chunk is configured regardless of an MMTP payload length. Therefore, a length of at least the FMU fragment is smaller or larger than the length of the MMTP payload.
As a specific example, the MMTP payload can be configured to include a part of an MFU that has a length greater than that of the payload.
- f_i (2bits): This information represents a fragmentation indicator indicating a unit interval of an MMTP payload. Table 4 below illustrates an example of a fragmentation indicator value.
<img file="MX348574B_D0010.tif" />
Table 4
IMPI
MEXICAN INSTIVUTU OF INDUJTklAL PROPERTY
<td>Value</td><td>Description</td>
<td> 00</td><td>The payload contains one or more complete data units.</td>
<td> 01</td><td>The payload contains the first data drive chunk.</td>
<td> 10</td><td>The payload contains a data unit chunk that is neither the first part nor the last part.</td>
<td> 11</td><td>The payload contains the last chunk of data drive.</td>
With reference to Table 4, f_i = '00' may indicate a case where an MMTP payload includes at least one full DU DU, MPU. The DU according to one embodiment of the present description may correspond to an MFU or an MPU depending on the characteristics of the data. If the DU is assumed to be a data DU for a real-time multi-media service, the DU may correspond to an MFU. In this case, f_i = '00' can indicate a case where an MMTP payload is configured in MFU units and includes at least one MFU. If the DU is assumed to be an image, the DU may correspond to an MPU. In this case, if f_i has a value of '00', an MMTP payload can be configured as an MPU. Furthermore, fi = '01' can indicate a case where an MMTP payload includes a first DU fragment between DU fragments that constitute a DU. In this case, with the conviction that the DU is an MFU, the MMTP payload may include the first MFU fragment among the MFU fragments obtained by
IMPI ^
INSTITUTO MÍXlCANO fragment the MFU, if f_i has a value of ^<sup>B</sup>cMíSíírr * »Üi '' fcS.
has a value of '10', the payload of ΜΜΪ® — may include a DU fragment different from the first DU fragment and the last DU fragment among the DU fragments that make up a DU. For example, with the conviction that the DU includes three DU fragments, the MMTP payload can include the central DU fragment, if f_i has a value of '10'. Finally, if f_i = '11', an MMTP payload can include the last DU fragment among the DU fragments that make up a DU.
- fragmentation_flag (F: 1 bit): If the MMTP payload transmits a fragmented MPU (for example, MFUs), fragmentation_flag can be specified as 1.
- aggregation_flag (A: 1 bit): If the MMTP payload transmits a plurality of MPUs, the aggregation_flag can be indicated as 1.
- RAP_flag (R: 1 bit): If the data included in the MMTP payload includes a data unit (for example, a Random Access Point (RAP)) that allows random access, RAP_flag can be specified as 1. Data with RAP_flag = 'l' can be information indicating that the data can be decoded directly. For example, an MMTP payload is assumed to include one MPU that corresponds to each of ten continuous scenes over time that make up an arbitrary video. In
INSTITUTO MEXICANv IH LA PROPIEDAD in this case, the header of the payload. <sup>IN</sup>í'Wií?! büir ** ^ nRAP_flag that corresponds to each of the e — MPUa. <3emre -wi specific example, an MPU with RAP_flag = 'l' can correspond to an intra-coded frame (I frame) that is 5 encodes independently, between the frames that make up the video.
payload_id (P: 1 bit): If there is identifier information that corresponds to a media operation unit (for example, MPU) of a DU included in MMTP payload 10, then payload_id can be specified as 1.
extension_flag (E: 1 bit): If the header information in the MMTP payload structure is required to be extended, axtension_flag can be specified as 1.
data_offset (8 bits): This information represents an address of a starting point of the payload data included in the MMTP payload.
fragment_counter (frag_count: 8 bits):
If the MMTP payload includes MFUs obtained by fragmentation of an MPU, fragment_counter may correspond to the number of payloads, which indicates the MFU of the MPU, which is included in the MMTP payload.
number_data_unit (numDU: 4 bits): If the MMTP payload includes the data unit number, for example, if the MMTP payload includes a plurality of
<img file="MX348574B_D0011.tif" />
IMPI USTTTUTÜ MUlCANO MPUs, number_data_unit can indicate the number
- DU_offset (16 bits): If a payload · ·., Gives MMJJ aa transmits as it is composed of a plurality of MPUs, DU_offset can indicate a starting value for each of the MPUs that constitute the MMTP payload. In this document, a DU may correspond to an MPU. In an alternative embodiment, DU_offset can be replaced by a length of each MPU. In this case, numDU cannot be used.
- payload_id (32 bits): If an MMTP payload is composed of at least one MFU obtained by fragmenting an MPU or if an MMTP payload is configured by combining a plurality of MPUs, payload_id can indicate a identifier of an MPU that the MMTP payload includes. If a transmission side fragments multi-media data and transmits the fragmented multi-media data through a plurality of multi-media packets, the identifier of an MPU can be used to assemble a plurality of data from multiple media that a receiving side has received through the plurality of multiple media packets.
- payload_sequence_flag (P: 1 bit): This information is set with 1 bit to indicate presence
IMPÍ of the sequence number of a tndustuial payload - payload_sequence_number (32 bits): This information indicates the sequence number of an MMTP payload.
An index corresponding to the order of a multi-media transport packet that is transmitted can be used as an example of the payload_id. In some cases, payload_id can be used as an index that corresponds to an identifier of a multi-media transport packet or an active value.
Furthermore, a plurality of datagram may be included in an MMTP payload that constitutes a multi-media transport packet. In this case, the multi-media data corresponding to each of a plurality of services or content written in an MMTP payload can be separated and an independent datagram can be obtained with only the separate multi-media data. considering the length described in the header information. Alternatively, a datagram can be obtained by being assembled with the multi-media data that is previously received or will be received later.
Table 5 below illustrates an example of
<img file="MX348574B_D0012.tif" />
IMPI;
MEXICAN INSTITUTE f header information written in a region of<sup>F</sup> MMTP packet constituting an mmtp packet __
MMP packet header
Table 5
<td colspan="4">paketjd</td><td colspan="9">paket_sequence_number</td>
<td colspan="4">paket_sequence_numeber</td><td colspan="9">timestamp</td>
<td colspan="4">timestamp</td><td>Q T</td><td>F Ό '</td><td>P Ό '</td><td>FEC</td><td>BEEF</td><td>TB</td><td>DS</td><td>R Ό '</td><td>S Ό '</td>
<td>TB</td><td>Flowjabel</td><td>AND '0'</td><td>reserved</td><td colspan="9">pivate_user_data</td>
- packet_id (16 bits): This is an identifier of an MMTP packet and has the same identifier of a single packet for the same multi-media stream. In other words, this is assigned to each active security to distinguish packages of one active security from another.
- packet_sequence_number (32 bits): This indicates a sequence number of an MMTP packet and the sequence number can be indicated as a sequentially incrementing number, for each of the totality of multi-media transport packets that are transmitted. In other words, the sequence number can be an arbitrary value incremented by one for each MMTP packet. However, the sequence number can increment sequentially for each multi-media transport packet that has the same] ίΜpi packet id through the information setting ¿E ^^ ia ^ sfo ^ configuration. Pre-setting setting information can be transmitted by being included in multi-media data control information.
- timestamp (32 bits): This indicates the time instance in which an MMTP packet is transmitted or delivered based on the time information from the Network Time Protocol (NTP). NTP time information, which is Coordinated by Universal Time (UTC), can be used for end-to-end delay measurement. A bit rate can be adjusted based on the NTP timing information.
- QoS_classifier_flag (Q: 1 bit): This sets QoS qualifier information with 1 bit.
- FEC_type (FEC: 2 bits): This indicates type information related to the Error Correction without Return Channel (FEC, for its acronym in English).
- type_of_bitrate (TB: 3 bits): This information indicates the type of the multi-media transport packet. Table 6 below illustrates an example of the package type. In this document, the type of the multi-media transport packet can be distinguished depending on the bit rate of the packet. The package type can be used for programming packages and set values of a
IMPI receive buffer on a terminal ^ uj ^ ofe ¡nt> l OT1AL or an intermediate network device. For example, if the packet type is set to a fixed bit rate (for example, '000'), a buffer on the receiving terminal and a packet scheduler on the intermediate network device can use a buffer that has a fixed size, for media processing, or you can set the packet type to a fixed value, for queuing.
Table 6
<img file="MX348574B_D0013.tif" />
<td>Value</td><td>Description</td>
<td> 000</td><td>Constant Bit Rate (CBR): A bit rate of the transport packet is maintained.</td>
<td> 001</td><td>Non-Constant Bit Rate (nCBR): A transport packet bit rate is not maintained.</td>
<td> 010-111</td><td>Reserved</td>
So far, a description has been made of the structure of an MMTP packet and the definition and configuration of each header information written in the header region that constitutes the MMTP packet.
A description will now be made of a method for configuring an MPU-based MMTP payload and generating an MMTP packet carrying the MMTP payload in accordance with one embodiment of the present description.
FIGURE 4a schematically illustrates an example of
IMPIOS __ ___ „ηττ _______ an MPU configuration according to a present description. ,.
With reference to FIGURE 4a, an MPU file 400 created from the content of MMT may include header information 402 and Media DATa (MDAT) 404 corresponding to media data. Header information 402 may include File TYPe (FTYP) which indicates the type of the file, MMPU which corresponds to MPU configuration information, MOOV which corresponds to codec setting information for media, and Movie Fragment ( Movie Fragment) (MOOF) that corresponds to detailed information about the fragment unit. MDAT 404s can include Video Samples (VSs) 406 that correspond to encoded media data and Hint Samples (HSs) 408 that correspond to additional information for media, such as mutual priority, mutual dependency. , size and the like of the media data. As illustrated in FIGURE 4a, each of the VSs and HSs can include only relevant VSs such as VSs 406 and can include only relevant HSs such as HSs 408, in an MDAT table (eg, MDAT 404s).
For the generation of an MMTP packet, a configured MMTP payload based on the MPU 4 00 line can be commonly configured by being divided into media data and structure information in its process of
.. .......... IMPIO configuration. The INDUSTRIAL structure information ^ * · * <Ζ ”* 402 header information such as FTYP, MMPU, MOOV, MOOF and the like.
An MPU / MFU 410 building block for configuring MMTP packets can be configured based on the MPU 400 file. The MPU / MFU 410 building block includes a separate payload (for example, MPU 412 metadata) that includes structure information, and MFUs that include pairs of HSs and VSs.
For example, an MFU 414 can include VS # 1 and HS # 1 in the MDAT 404. In an alternative mode, an MMTP payload can be configured to match or not match the chunk unit (for example, MFU or MPU ) of the MDAT. For example, if the MMTP payload is configured not to match the MDAT chunk unit, the MMTP payload can include a chunk of an MFU that is longer than its own length. The MMTP payload configuration can be represented by the type of the payload header described above. A specific example is described below with reference to FIGURE 4b.
FIGURE 4b illustrates an example of an MFU configuration that can be created based on the MPU file in FIGURE 4a in accordance with one embodiment of the present disclosure.
IΜ ΡI ΙΝύ ι ΙΤΌΤΟ MEXICANO y LE LA PROPIELA!) With reference to FIGURE 4b, a load '& ^' Úteir '^ Se-MMTP # 1 422 may include MP3J metadata <sup>1</sup> que—> noluyan, ... components (for example, FTYP, MMPU, and MOOV) of the header information described above. The MPU metadata can include a separate MPU. In this case, the MMTP # 1 422 payload packet type can be represented as an MPU. The packet type can be included as a component of the MMTP packet header. Also, a value of the type included in the payload header of MMTP payload # 1 422 can be set as '0x01' in Table 3 representing the MPU metadata. An MMTP # 2 424 payload may include MOOF and chunk metadata that includes a header portion of the MDATs. In this case, the packet type of the MMTP # 2 424 payload can correspond to an MPU and the type included in the payload header of the MMTP # 1 422 payload can be set to '0x02' in the Table 3, which indicates the fragment metadata. As another example, an MMTP # 3 426 payload can include only the VSs (for example, the VS # 2, VS # 3, and VS # 4 data samples) in the MDATs. In this case, additional information (for example, priority that corresponds to each VS, mutual dependency information, a counter indicating a start position of the data sample, and the like) for the VSs can be configured as configuration information of an indication hint
IMPI
MMT. The MMT indication track can be<sup>N</sup>^ MLcl & ^^ imhistrial MMT indication track configuration information located on the upper front of the MFU that includes the VSs. An example of a detailed configuration of an MFU is described below with reference to FIGURE 4c.
FIGURE 4c illustrates an example of a detailed configuration of an MFU in accordance with one embodiment of the present disclosure.
With reference to FIGURE 4c, for example, an MFU 430 can be fragmented into a plurality of sections that are the same length. In an alternative embodiment, the MFU 430 can be fragmented into a plurality of sections that have different lengths. The first section 432 between the sections may include the MMT indication track of the data samples that make up the MFU 430. For each of the other sections, the VSs that make up the MFU 430 can be assigned depending on the size of each of the other sections. In this case, each of the other sections can be configured to include at least one VS, or it can be configured to include a part of a VS, according to one embodiment of the present description.
FIGURE 4d illustrates an example of a configuration of a payload that is configured based on the MFU in FIGURE 4c according to one embodiment of the
<img file="MX348574B_D0014.tif" />
present description. INDUSTRIAL
With reference to FIGURE 4d, for example, a payload 440 may include a section 444 that corresponds to one of the sections that make up the MFU in FIGURE 4c. Section 444 may correspond to the payload data described above. A payload 440 can be generated by attaching a payload header 442 to section 444. The payload 440 can correspond to the MMTP payload region in Table 1. The payload header 442 may include the priority for the section 444, the mutual dependency information, the counter indicating a start position of the data sample, and the like. Therefore, if section 444 is the first section that includes the MMT indication track among the sections that make up the MFU in FIGURE 4c, the payload header 442 may include information that overlaps the MMT indication track. If section 444 is one of the other sections that make up the MFU in FIGURE 4c, section 44 may include the priority for each of the other sections, the mutual dependency information, the counter indicating a start position of the sample data and the like. Then, if a packet header 446 joins payload 440, an MMTP packet 448 completes. As a result, the MMTP packet 448 may include the packet header 446, the payload header 442, and the section
8 -------------------------------- IMPIOS 'Tin INJTITbJO MEXICANO .¿i
444 Corresponding to the payload data of its alternate mode, the MMTP packet 448 may include a plurality of payloads 440.
FIGURE 5 illustrates an example of a method for configuring a payload from an MPU / MFU building block that is configured based on the MPU file in FIGURE 4a and for creating an MMTP packet according to a embodiment of the present description.
With reference to FIGURES 4a and 5, the MPU metadata 412 configured in accordance with the method described in FIGURE 4a may be, for example, a component of an MMTP payload. In other words, the MPU 412 metadata can correspond to payload data and the MMTP 515a payload can be generated by attaching a payload header to the MPU 412 metadata as described in FIGURE 4d.
Similarly, the MFU described above 414 can also be a component of an MMTP payload 515b. The MFU 414 can also correspond to payload data and the MMTP 515b payload can be generated by attaching a payload header to the MFU 414 as described in FIGURE 4d. As another example, an MFU that includes only one MOOF 420 can also be generated as a 515c payload by attaching a payload header to it. The payload header can be configured as shown in Table
2.
<img file="MX348574B_D0015.tif" />
An MMTP packet 516 can be INDUSTRIAL BKOPIETY in at least one MMTP payload that is generated as described above. In other words, the package
MMTP 516 can be generated by attaching a packet header to each of at least one MMTP payload. The packet header can be configured as shown in Table 5.
FIGURES 6a and 6b illustrate examples of MPU configurations that are distinguished depending on real-time requirements in accordance with one embodiment of the present disclosure.
FIGURE 6a illustrates an example of an MPU configuration that provides a real-time multi-media service in accordance with one embodiment of the present disclosure.
With reference to FIGURE 6a, the MPU may include, for example, an ftyp / styp (stream type) frame, a sidx frame, an mmpu frame, a moov frame, a moof frame, and a mdat. The ftyp box, the mmpu box and the moov box can be MPU metadata components and the sidx box can be optionally included only for the MPU that provides a real-time multi-media service. The sidx table can be an index of MFUs that make up the MPU. The moov box may include media track information in addition to the indication track information.
MEXICAN INSTITUTE
MMT as compared to the MPU providing multi-media non-real time in FIGURE 6b. The MMT indication track information may be information indicating the position of an MMT indication track of each MDAT included in the MPU. The user can determine the position of the MMT indication track and obtain the MMT indication track for the MDATs to be received, using the determined position. The media track information may be information indicating the position of each MDAT included in the MPU. Similarly, for the media track information, the user can determine the position of each MDAT included in the MPU and receive MDAT using the determined position. The moof table corresponding to the real-time data that is carried substantially by the MPU may include at least one traf. The traf can provide the time to decode a VS that constitutes the mdat. In comparison, FIGURE 6b illustrates an example of an MPU configuration that provides a multi-media service that is not in real time.
With reference to FIGURE 6b, the MPU may include an ftyp frame, an mmpu frame, a moov frame, a meta frame, and article frames. The moov box can include only MMT indication track information. MMT indication track information can be
IMPI ^ iK'Tin iTt »μ f.Jr ican information indicating the position of each square ^^ '^^ rtSC · ^! that is received. The meta box may include the information location (iloc) indicating the position of article boxes that make up the MPU.
The MPU according to another embodiment of the present description can be configured depending on the data file or the application.
FIGURE 7 illustrates an example configuration of an MPU providing the real-time multi-media service in FIGURE 6a, in payload units in accordance with one embodiment of the present disclosure.
With reference to FIGURE 7, a payload 700 can be configured by defining, as MPU metadata, an ftyp frame, an mmpu frame, and a moov frame among the MPU components that require the media service. multiples in real time in FIGURE 6a. The 702 and 704 payloads can be configured using the mdat boxes and their position information. The mdat frame that constitutes each of the payloads 702 and 704 represents fragment metadata for MFUs that constitute its payload, and each mdat frame can be fragmented into a plurality of MFUs.
FIGURE 8 illustrates an example configuration of a multi-media service that is not in
IMPI ^ real time in FIGURE. 6b in units of industrial ¿cHS ^ & op ^ SI according to one embodiment of the present description.
With reference to FIGURE 8, a payload 800 can be configured by defining, as MPU metadata, an ftyp box, an mmpu box, a moov box, and a meta box that constitutes an MPU that requires the service of multiple media that is not real time in FIGURE 6b. Like an MFU, each of the article frames can constitute one of the 802 and 804 payloads.
FIGURE 9 illustrates a transmission entity for transmitting media data in an MMT system in accordance with one embodiment of the present disclosure.
With reference to FIGURE 9, a transmission entity 900 for transmitting media data in an MMT system includes a controller 902, a transceiver 904, and an MMTP packet generator 906. The transceiver 910 communicates with an apparatus for receiving data. multi-media data provider from the multi-media data provider in the MMT system under the command of controller 920. The controller 902 has control over the MMTP packet generator 906 to perform the operations described in this document to generate an MMTP packet, then the MMTP packet generator 906 configures the header information to configure an MMTP packet based on in a payload that is configured
............ IMPI depending on media data © ®ca> ®nicwiulM ™ i ^ a'Jj wuwümwi)
INOHSTMAl
The MMTP packet generator 906 can configure one or more MMTP packets by combining the multiple media data received in step 310 with the header information configured in step 312. The generated MMTP packets include a packet header. and a payload, the payload includes a payload header and payload data. The header information may include header information for an MMTP packet header region that is described in Table 5 below, and information about a payload header that is described in Table 2 below. The header information included in the packet header and the payload header, for example. The header information includes information indicating that the payload data includes an MPU, if the payload data includes at least one fragmented MFU in the MPU, the header information includes a position information of at least the MFU and the type of data included in the payload data and the controller (902) has control over the transceiver 910 to perform the operations described in this document to transmit media data in the MMT system. Apparatus 900 may include other components, such as a data setter and memory.
FIGURE 10 illustrates a receiving entity for
OF INDUSTRIAL PROPERTY receive media data in an IM system one embodiment of the present description.
With reference to FIGURE 10, the receiving entity 1000 for receiving the media data in an MMT system includes a controller 1002, a transceiver 1004, an MPU reconstruction unit 1006, and a display unit 1008. The transceiver 1010 is communicates with an apparatus for transmitting media data in the MMT system under the command of controller 1002. If the transceiver 1010 receives at least one MMTP packet, the controller 10 02 obtains header information from a packet header and a payload header from at least the MMTP packet, for example. The header information includes information indicating that the payload data includes an MPU, if the payload data includes at least one fragmented MFU in the MPU, the header information includes a position information of at least the MFU and a data type included in the payload data.
Specifically, controller 1002 has control over MPU reconstruction unit 100 6 to reconstruct MPUs or MFUs included in the payload data based on the obtained header information. Then, the MPU reconstruction unit 1006 determines the MPU or MFUs that constitute multiple media data through the use of the header information. Then the controller (1002) has control over
DE LA PAOM8DAÜ V · »* - <4eU¿
INDUSTRIAL Jt »display to provide audio, subtitles, etc. corresponding to multiple media data, through images on a display screen, using the MPU or specified MFUs. Then the display unit 1008 displays the multi-media data through a display screen. Apparatus 1000 may include other components, such as a data setter and memory.
As is apparent from the above description, one embodiment of the present description may provide a method for configuring a multi-media payload to transmit a hybrid service or content over an IP network and to generate and transmit a multi-media package based thereon, thereby making it possible to support efficient MPEG transmission in the multi-media environment.
The methods described in this document according to one embodiment of the present disclosure can be implemented in the form of hardware (physical components), software (programming elements), or a combination thereof. Any of this software can be stored, for example, on a volatile or non-volatile non-transient storage device such as a Read Only Memory (ROM)
Random Access Memory (RAM,
<img file="MX348574B_D0016.tif" />
for its acronym in English), a memory chip, a memory device or a Circuit
Integrated (IC) or a recordable and machine-readable (e.g. computer) optical or magnetic medium such as a Compact Disc (CD), a Digital Versatile Disc (DVD , for its acronym in English), a magnetic disk or a magnetic tape, regardless of its ability to be erased or its ability to be recorded again. Also, it will be appreciated that the methods described herein in accordance with one embodiment of the present disclosure can be implemented by a computer or a portable terminal which includes a controller and a memory, in which memory can be an example of a non-transient storage medium that is machine readable that is suitable for storing one or more programs that include instructions for implementing certain embodiments of the present disclosure.
Accordingly, one embodiment of the present disclosure includes a program that includes code for implementing any method defined in the appended claims of the present disclosure and a non-transient machine-readable (computer) storage medium for storing the program. In addition, the program
IMPI may be electronically transferred INDUSTRIAL predetermined such as a communication signal transferred over a wired or wireless connection, and the present disclosure appropriately includes program equivalents.
While the present description has been shown and described with reference to various embodiments thereof, those skilled in the field will understand that various changes in form and details can be made in this document without departing from the spirit and scope of the present description. as defined by the appended claims and their equivalents.
It is noted that in relation to this date, the best method known to the applicant for putting the aforementioned invention into practice is the one that is clear from the present description of the invention.
<img file="MX348574B_D0017.tif" />
Contents18
26 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26
38 members in 9 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020130043855 | Republic of Korea | – | |
| 20130043855 | Republic of Korea | A | |
| 20130043855 | Republic of Korea | A | |
| 2014003470 | Republic of Korea | W | |
| 2014003470 | Republic of Korea | W | |
| 1020130043855 | – | – | – |
| KR20130043855 | – | – | – |
| PCTKR2014003470 | – | – | – |
| WO2014KR03470 | – | – | – |
Members38
| Document | Office | Kind | |
|---|---|---|---|
| CA2909906A1 | Canada | A1 | |
| CA3122639A1 | Canada | A1 | |
| US2014317664A1 | United States of America | A1 | |
| WO2014171806A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20140125690A | Republic of Korea | A | |
| KR101484843B1 | Republic of Korea | B1 | |
| JP2015528251A | Japan | A | |
| CN105191323A | China | A | |
| MX2015014695A | Mexico | A | |
| EP2987330A1 | European Patent Office (EPO) | A1 | |
| JP5898380B2 | Japan | B2 | |
| JP2016140089A | Japan | A | |
| EP2987330A4 | European Patent Office (EPO) | A4 | |
| RU2015149465A | Russian Federation | A | |
| MX348574BThis record | Mexico | B | |
| JP2018011319A | Japan | A | |
| RU2644400C2 | Russian Federation | C2 | |
| JP6290950B2 | Japan | B2 | |
| CN108650528A | China | A | |
| CN109040791A | China | A | |
| RU2018102310A | Russian Federation | A | |
| US10412423B2 | United States of America | B2 | |
| JP2019193293A | Japan | A | |
| US2019394506A1 | United States of America | A1 | |
| JP6843714B2 | Japan | B2 | |
| RU2018102310A3 | Russian Federation | A3 | |
| JP6887466B2 | Japan | B2 | |
| RU2750337C2 | Russian Federation | C2 | |
| JP2021122149A | Japan | A | |
| CN109040791B | China | B | |
| US11245940B2 | United States of America | B2 | |
| EP2987330B1 | European Patent Office (EPO) | B1 | |
| CN108650528B | China | B | |
| CA2909906C | Canada | C | |
| US2022159320A1 | United States of America | A1 | |
| JP7212102B2 | Japan | B2 | |
| CA3122639C | Canada | C | |
| US11665384B2 | United States of America | B2 |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Grant or registrationFG | FG |
Numbers
- Publication
- 348574
- Publication, DOCDB
- 348574
- Publication, EPODOC
- MX348574
- Application
- 2015014695
- Application, DOCDB
- 2015014695
- Application, EPODOC
- MX202015014695
Titles2
- English
- METHOD AND APPARATUS TO TRANSMIT MEDIA DATA IN A MULTIPLE MEDIA TRANSPORTATION SYSTEM.
- Spanish
- METODO Y APARATO PARA TRANSMITIR DATOS DE MEDIOS EN UN SISTEMA DE TRANSPORTE DE MEDIOS DE COMUNICACION MULTIPLES.
Classification
- CPC, 9
- H04N21/23614
- H04N21/2381
- H04L9/40
- H04N21/85406
- H04N21/4343
- H04N21/4348
- H04N21/4381
- H04N21/64322
- H04N21/236
- IPC, 3
- H04N21 236
- H04L29 06
- H04L47 43