KR20150044365A - Method for setting generic file delivery mode using generic file delivery descriptor - Google Patents

Abstract

A method for setting a generic file delivery (GFD) mode by using a GFD descriptor is disclosed. A method for transmitting the GFD descriptor according to the present invention comprises the following: a step in which a GFD descriptor, which includes one or more code points that are to be transmitted to the GFD mode, is generated; a step in which the GFD descriptor is added to a signaling message that will be transmitted to the MPEG media transport (MMT) receiving entity; and a step in which the signaling message is transmitted to the MMT receiving entity.

Description

METHOD FOR SETTING GENERIC FILE DELIVERY MODE USING GENERIC FILE DELIVERY DESCRIPTOR USING GFD DESCRIPTOR [0002]

The present invention relates to a method of setting a GFD mode in an MMT receiving entity to use a GFD (Generic File Delivery) mode in an MMT (MPEG Media Transport), in particular a GFD descriptor including a code point of an object to be transmitted, To a GFD mode using a GFD descriptor so that the MMT receiving entity can use the GFD mode by transmitting the GFD mode to the MMT receiving entity in addition to the MMT receiving entity.

Looking at the transfer function area in the current MMT (MPEG Media Transport) standard, a separate MMTP payload is generated according to the MPU mode, the GFD mode, and the signaling message transmission mode, and the generated MMTP payload is encapsulated into an MMTP packet. In particular, in the GFD mode, the maximum size of an object to be transmitted is defined before the object is transmitted, and information about the object to be transmitted is defined in advance. The information is called a code point, and the GFD table is defined to transmit one or more code points in a bundle. In the case of using the GFD mode as described above, the GFD table should be transmitted to notify the information about the object to be transmitted. However, since the method for transmitting the GFD table is not defined at present, the MMT can provide the GFD transmission method. Further, when a plurality of code points are included in the GFD table, the total number of code points is not represented, so that the process of extracting the code points by the MMT receiving entity can be complicated, It is not possible to indicate whether or not the information about the selectively existing elements is included in the GFD table.

Accordingly, in the present invention, when the MMT sending entity tries to use the GFD mode, the GFD descriptor format and the GFD mode setting technique capable of setting the GFD mode by transmitting information such as the GFD table related to the GFD mode to the MMT receiving entity I want to.

Related prior art is Korean Patent Laid-Open Publication No. 2013-0035155 on a method and apparatus for transmitting and receiving a content.

It is an object of the present invention to enable transmission of information on the GFD mode to the MMT receiving entity so that the MMT can use the GFD mode.

It is also an object of the present invention to provide a method and apparatus for enabling GFD mode to be used more smoothly in an MMT receiving entity by generating information on constituent elements constituting a code point when generating a GFD descriptor for using the GFD mode .

According to an aspect of the present invention, there is provided a GFD descriptor transmission method including: generating a GFD descriptor including at least one code point to be transmitted in a GFD (Generic File Delivery) mode; Adding the GFD descriptor to a signaling message to be sent to an MMT (MPEG Media Transport) receiving entity; And sending the signaling message to the MMT receiving entity.

At this time, the code point may include at least one flag indicating whether or not the fields constituting the code point exist.

At this time, code points may be generated in the MMT transmitting entity by a number corresponding to at least one object to be transmitted in the GFD mode.

At this time, the MMT sending entity may generate the code point by generating a field constituting the code point according to the value of the at least one flag.

At this time, the step of generating a GFD descriptor may set a field constituting a basic header of the GFD descriptor based on at least one of a field constituting the code point and a total number of the code points.

Also, a GFD mode setting method according to an exemplary embodiment of the present invention includes: receiving a signaling message including a GFD descriptor from an MMT sending entity; Extracting a GFD descriptor included in the signaling message; And setting the GFD mode to the MMT receiving entity using the GFD descriptor to provide a GFD mode in the MMT.

In this case, the step of setting the GFD mode may include separating and storing at least one or more code points included in the GFD descriptor by referring to the value of the number_of_Codepoints field of the GFD descriptor in the MMT receiving entity .

In this case, the separately storing step may include a method of copying the value of the number_of_Codepoints field to another variable, and a method of directly referring to a memory area where the value of the number_of_Codepoints field is stored, Value can be referenced.

In this case, the separately storing step may separate and store the code points until the value of the number_of_Codepoints field becomes zero.

According to the present invention, information about the GFD mode can be transmitted to the MMT receiving entity so that the MMT can use the GFD mode.

In addition, when generating the GFD descriptor for using the GFD mode, the present invention can use the GFD mode more smoothly in the MMT receiving entity by generating information about the constituent elements constituting the code point.

1 is a flowchart illustrating a method of transmitting a GFD descriptor according to an embodiment of the present invention.
2 is a flowchart illustrating a method of setting a GFD mode according to an embodiment of the present invention.
3 is a view showing a functional area constituting the MMT system.
4 is a diagram showing a configuration of a code point according to the present invention.
5 is a diagram illustrating a format of a GFD descriptor according to an embodiment of the present invention.
FIG. 6 is a diagram illustrating a process of separating and storing code points according to an embodiment of the present invention.

The present invention will now be described in detail with reference to the accompanying drawings. Hereinafter, a repeated description, a known function that may obscure the gist of the present invention, and a detailed description of the configuration will be omitted. Embodiments of the present invention are provided to more fully describe the present invention to those skilled in the art. Accordingly, the shapes and sizes of the elements in the drawings and the like can be exaggerated for clarity.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a flowchart illustrating a method of transmitting a GFD descriptor according to an embodiment of the present invention.

Referring to FIG. 1, a GFD descriptor transmission method according to an exemplary embodiment of the present invention may generate a descriptor including at least one code point to be transmitted in a GFD mode (S110). The GFD mode may transmit a code point, which is information about an object to be transmitted, such as a maximum size of an object to be transmitted before transmitting the object. Such a code point can be transmitted by bundling a plurality of code points according to the number of objects to be transmitted, and a GFD table can be used at this time. The GFD table can be transmitted using the GFD descriptor format.

At this time, the code point may include at least one flag indicating whether or not the fields constituting the code point exist. The code point is the value field, the fileDeliveryMode field. a startToI_flag field, an endToI_flag field, an EntityHeader_flag field, a maximumTransferLength field, a FileTemplate_length field, a FileTemplate_byte field, a File_length field, a File_byte field, a startTOI field, an endToIntegree, an EntityHeader_length field and an EntityHeader_byte field. The value field is a value used as a separator for code points, and can be set to a value from 1 to 255. That is, for different code points, the value field can be set to a different value. The fileDeliveryMode field indicates the type of object to be transmitted through the GFD mode. The fileDeliveryMode field can be set to 1 when transmitting a general file, or to 2 when transmitting an entity composed of a header and a file. The constantTransferLength_flag field may indicate whether each object has the same size when a plurality of objects are transmitted. It is set to 1 if all objects are the same size and the size of each object can be set in the maximumTransferLength field. The outOfOrderSending_flag field may indicate the presence or absence of the outOfOrderSending field. and may be set to one if the outOfOrderSending field is present. The FileTemplate_flag field may indicate the presence or absence of fields associated with the FileTemplate. It can be set to 1 if there are fields associated with the FileTemplate. It can be set to 0 if there is a File element of FLUTE instead of FileTemplate. The startTOI_flag field may indicate the presence or absence of a startTOI field. If the startTOI field is present, it can be set to 1. The endTOI_flag field indicates whether the endTOI field is present, and may be set to 1 if the endTOI field is present. The EntityHeader_flag field indicates the presence of EntityHeader related fields, and may be set to 1 if EntityHeader related fields are present. The maximumTransferLength field indicates the maximum size of the object to be transmitted. The maximum size of the object that can be transmitted depends on the length of the maximumTransferLength field. The FileTemplate_length field can indicate the size of the FileTemplate if the FileTemplate is included. The FileTemplate_byte field can refer to each byte unit of the FileTemplate included in the GFD descriptor. The File_length field can indicate the length of the File element if the File element of FLUTE is included instead of FileTemplate. The File_byte field may represent each byte unit of the File element included in the GFD descriptor. The startTOI field may represent the TOI of the first object to be delivered. The endTOI field may represent the TOI of the last object to be delivered. The EntityHeader_length field may indicate the length of the entity-header included in the GFD descriptor. The EntityHeader_byte field can be each byte unit of the entity-header. The Entity-header is set based on the form in section 7.1 of IETF RFC 2616 and can be applied to all objects belonging to the code point set in the value field. Whether or not information such as outOfOrderSending, FileTemplate, startTOI, endTOI, and EntityHeader is included in each code point through flags such as outOfOrderSending_flag field, FileTemplate_flag field, startTOI_flag field, endTOI_flag field and EntityHeader_flag field among the various fields constituting the code point .

Also, the code points may be generated in the MMT sending entity by a number corresponding to at least one or more objects to transmit in the GFD mode. Since code points are information about objects to be transmitted in GFD mode, code points can be generated for each object to be transmitted. Therefore, the number of code points included in the GFD descriptor may correspond to the number of objects to be transmitted in the GFD mode.

At this time, the MMT sending entity can generate a code point by generating a field constituting a code point according to at least one flag value. For example, fields indicating flag values such as outOfOrderSending_flag, FileTemplate_flag, startTOI_flag, endTOI_flag, and EntityHeader_flag may be checked to generate and set a field at the code point corresponding to each flag value.

At this time, a field configuring the basic header of the GFD descriptor can be set based on at least one of the field constituting the code point and the total number of code points. The GFD descriptor may have a basic header composed of a descriptor_tag field and a descriptor_length field. Also, there is a number_of_CodePoints field indicating the total number of code points included in the GFD descriptor, and the number of code points equal to the value set in this field may be successively added to the number_of_CodePoints field. The number_of_CodePoints field may have the same length as the next value field. Therefore, basically, both fields can have a length of 8 bits, and if the length of the value field is extended in the future, the length of the number_of_CodePoints field can be extended accordingly.

Thereafter, a GFD descriptor may be added to the signaling message to be sent to the MMT receiving entity (S120).

Thereafter, a signaling message may be transmitted to the MMT receiving entity (S130). For example, the generated GFD descriptor may be transmitted to the MMT receiving entity after the MPT message is transmitted in the asset_descriptors portion of the MP table included in the MPT message.

2 is a flowchart illustrating a method of setting a GFD mode according to an embodiment of the present invention.

Referring to FIG. 2, a GFD mode setting method according to an exemplary embodiment of the present invention may receive a signaling message including a GFD descriptor from an MMT sending entity (S210).

Thereafter, the GFD descriptor included in the signaling message may be extracted (S220). If the MMT receiving entity receives the signaling message and the GFD descriptor is included in the message, the GFD descriptor can be extracted and processed.

Thereafter, the GFD mode can be set to the MMT receiving entity using the GFD descriptor to provide the GFD mode in the MMT (S230).

At this time, the MMT receiving entity may refer to the value of the number_of_Codepoints field of the GFD descriptor and separately store at least one or more code points included in the GFD descriptor. The number_of_Codepoints field is a field for indicating the total number of code points included in the GFD descriptor. The number_of_Codepoints field may store code points appended to the number_of_Codepoints field by a value set in the number_of_Codepoints field.

In this case, the value of the number_of_Codepoints field can be referred to using any one of a method of copying the value of the number_of_Codepoints field to another variable and a method of directly referring to a memory area where the value of the number_of_Codepoints field is stored.

At this time, code points can be separately stored until the value of the number_of_Codepoints field becomes zero. For example, one code point included in the GFD descriptor is separated and stored, and the number of code points corresponding to the value of the number_of_Codepoints field is subtracted from the number of code points corresponding to the value of the number_of_Codepoints field. It can be done as an enemy. When storing each code point, the configuration of code points may be changed according to the values of the outOfOrderSending_flag field, the FileTemplate_flag field, the startTOI_flag field, the endTOI_flag field, and the EntityHeader_flag field.

3 is a view showing a functional area constituting the MMT system.

Referring to FIG. 3, the functional area constituting the MMT system is largely composed of an encapsulation layer, a delivery layer, and a signaling layer.

The encapsulation layer 310 defines a logical structure of the format of the data unit to be processed by the media content, the MMT package, and the MMT entity, and an implementation of the ISO base media file format (ISOBMFF) do. To provide the necessary information for adaptive delivery, the MMT package specifies the components that contain the media content and the relationships between them. The format of the data units is defined to encapsulate the encoded media for storage or delivery and to be easily converted between the two formats. The encapsulation layer 310 may be responsible for functions such as packetization, fragmentation, synchronization, and multiplexing of the transmitted media, for example. Various types of multimedia components may be encapsulated and combined to be transmitted and consumed by the functionality provided in the encapsulation layer. The configuration information of the encapsulated media component and the media component is provided in the functional area of the encapsulation layer 310. The main information for the encapsulated media components may include integration, priority, dependency of media fragments, timing information and structure information of the MPU, identification information of the MMT asset, initialization information, and codec information. The configuration information of the media components may include identification information of the MMT package and MMT asset, configuration information having a list of MMT assets, composition information of the MMT assets in the MMT package, and asset transfer characteristics.

The transport layer 320 defines a payload format and an application layer transport protocol. The payload format is defined to carry encoded media data regardless of the media type or encoding method. The application layer transport protocol provides enhanced features for delivery of packages including multiplexing and cross-layer communication. The transport layer 320 may perform network flow multiplexing, network packetization, QoS control, etc., of media transmitted over the network, for example. In addition, the transport layer 320 may include media multiplexing such as video, audio, and the like, packet level integration and segmentation, network packetization, QoS control, and synchronization between the transport layer and the encapsulation layer , Transport layer such as existing RTP, transport layer such as existing UDP and TCP, encapsulation layer, and interface with signaling layer. The transport layer 320 identifies the different types of payloads from the encapsulation layer 310 to handle the payload from the encapsulation layer 310. The transport layer 320 may handle temporary relationships between packets transmitted over different networks and different channels. The synchronization function may include hybrid network synchronization using a time stamp or the like. In addition, the transport layer 320 may handle the timing constraints of the MMT delivery packet for real-time media transmission. The transport layer 320 may perform error control of MMT media packets such as forward error correction and retransmission. The delivery layer 320 may perform flow control of the MMT media packet. The transport layer 320 may perform interactions with other MMT layers as well as a lower layer through a cross layer design in order to maintain a predetermined level of QoS for delivering MMT media packets. In addition, the transport layer 320 may provide a function for performing group communication.

The signaling layer 330 performs a signaling function. For example, the interface of the session initiation / control / management of the transferred media, the server based and / or client based trick mode, the service discovery, the synchronization and other layers such as the transport layer 320 and the encapsulation layer 210 Function and so on. Synchronization may include synchronization control in a hybrid network. The signaling layer 330 also defines the format of the messages that govern the delivery and consumption of MMT packages. The message for consumption management is used to announce the structure of the MMT package, and the message for the delivery management is used to inform the structure of the payload format and the configuration of the protocol.

4 is a diagram showing a configuration of a code point according to the present invention.

Referring to FIG. 4, a code point according to the present invention includes a value field, a fileDeliveryMode field. a startToI_flag field, an endToI_flag field, an EntityHeader_flag field, a maximumTransferLength field, a FileTemplate_length field, a FileTemplate_byte field, a File_length field, a File_byte field, a startTOI field, an endToIntegree, an EntityHeader_length field and an EntityHeader_byte field.

The value field is a value used as a separator for code points, and can be set to a value from 1 to 255. That is, for different code points, the value field can be set to a different value.

The fileDeliveryMode field indicates the type of object to be transmitted through the GFD mode. The fileDeliveryMode field can be set to 1 when transmitting a general file, or to 2 when transmitting an entity composed of a header and a file.

The constantTransferLength_flag field may indicate whether each object has the same size when a plurality of objects are transmitted. It is set to 1 if all objects are the same size and the size of each object can be set in the maximumTransferLength field.

The outOfOrderSending_flag field may indicate the presence or absence of the outOfOrderSending field. and may be set to one if the outOfOrderSending field is present.

The FileTemplate_flag field may indicate the presence or absence of fields associated with the FileTemplate. It can be set to 1 if there are fields associated with the FileTemplate. It can be set to 0 if there is a File element of FLUTE instead of FileTemplate.

The startTOI_flag field may indicate the presence or absence of a startTOI field. If the startTOI field is present, it can be set to 1.

The endTOI_flag field indicates whether the endTOI field is present, and may be set to 1 if the endTOI field is present.

The EntityHeader_flag field indicates the presence of EntityHeader related fields, and may be set to 1 if EntityHeader related fields are present.

The maximumTransferLength field indicates the maximum size of the object to be transmitted. The maximum size of the object that can be transmitted depends on the length of the maximumTransferLength field.

The FileTemplate_length field can indicate the size of the FileTemplate if the FileTemplate is included.

The FileTemplate_byte field can refer to each byte unit of the FileTemplate included in the GFD descriptor.

The File_length field can indicate the length of the File element if the File element of FLUTE is included instead of FileTemplate.

The File_byte field may represent each byte unit of the File element included in the GFD descriptor.

The startTOI field may represent the TOI of the first object to be delivered.

The endTOI field may represent the TOI of the last object to be delivered.

The EntityHeader_length field may indicate the length of the entity-header included in the GFD descriptor.

The EntityHeader_byte field can be each byte unit of the entity-header. The Entity-header is set based on the form in section 7.1 of IETF RFC 2616 and can be applied to any object belonging to the code point set in the value field.

5 is a diagram illustrating a format of a GFD descriptor according to an embodiment of the present invention.

Referring to FIG. 5, a GFD descriptor according to an embodiment of the present invention may have a basic header composed of a descriptor_id field and a descriptor_length field.

In addition, there is a number_of_CodePoints field indicating the total number of code points included in the GFD descriptor, and the number of code points equal to the value set in this field may be successively added to the number_of_CodePoints field. The number_of_CodePoints field may have the same length as the next value field. Therefore, basically, both fields can have a length of 8 bits, and if the length of the value field is extended in the future, the length of the number_of_CodePoints field can be extended accordingly.

FIG. 6 is a diagram illustrating a process of separating and storing code points according to an embodiment of the present invention.

Referring to FIG. 6, in the process of separating and storing code points according to an embodiment of the present invention, the value of the number_of_CodePoints field may be stored in a variable (S610).

Thereafter, it may be determined whether the value of the number_of_CodePoints field stored in the variable is 0 (S615).

If it is determined in step S615 that the value of the variable is not 0, a value obtained by subtracting 1 from the value of the variable may be stored as the value of the new variable in step S620.

Thereafter, each code point may be separately stored in the order of the number_of_CodePoints field of the GFD descriptor (S630).

As described above, the GFD mode setting method using the GFD descriptor according to the present invention is not limited to the configuration and method of the embodiments described above, but the embodiments can be applied to various implementations All or some of the examples may be selectively combined.

310: Insulation layer
320: transport layer
330: signaling layer

Claims (1)

Generating a GFD descriptor including at least one code point to transmit in a Generic File Delivery (GFD) mode;
Adding the GFD descriptor to a signaling message to be sent to an MMT (MPEG Media Transport) receiving entity; And
Transmitting the signaling message to the MMT receiving entity
And transmitting the GFD descriptor.

Images