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

Abstract

A method of setting a GFD mode using a GFD descriptor is disclosed. The method for transmitting a GFD descriptor according to the present invention comprises: generating a GFD descriptor including at least one code point to be transmitted in a Generic File Delivery (GFD) mode; Adding the GFD descriptor to a signaling message to be transmitted to an MPEG Media Transport (MMT) receiving entity; And transmitting the signaling message to the MMT receiving entity.

Description

GFD mode setting method using GFD descriptor {METHOD FOR SETTING GENERIC FILE DELIVERY MODE USING GENERIC FILE DELIVERY DESCRIPTOR}

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

Looking at the delivery functional area in the current MPEG Media Transport (MMT) standard, separate MMTP payloads are generated according to each of the MPU mode, GFD mode, and signaling message transmission mode, and the generated MMTP payload is encapsulated in MMTP packets. In particular, in the case of the GFD mode, information on the object to be transmitted, such as the maximum size of the object to be transmitted, is defined in advance before object transmission. The information is called CodePoint, and a GFD table is defined to bundle and transmit one or more code points. In the case of using the GFD mode as described above, the GFD table must be transmitted to inform information on the object to be transmitted.However, since a method for transmitting the GFD table is not currently defined, MMT can provide a GFD transmission method. In addition, when a plurality of code points are included in the GFD table, the process of extracting the code points by the MMT receiving entity may be complicated because the total number of code points is not indicated. A problem arises because it cannot be indicated whether information on optional elements is included in the GFD table.

Accordingly, in the present invention, when the MMT sending entity attempts to use the GFD mode, information such as the GFD table related to the GFD mode is transmitted to the MMT receiving entity to set the GFD mode and the GFD mode setting technology is disclosed. I want to.

As a related prior art, there is Korean Patent Publication No. 2013-0035155 on a method and apparatus for transmitting and receiving content.

An object of the present invention is to enable the MMT to transmit information on the GFD mode to the MMT receiving entity so that the GFD mode can be used.

In addition, it is an object of the present invention to generate a GFD descriptor for using a GFD mode, including information on components constituting a code point, so that the MMT receiving entity can use the GFD mode more smoothly. Is to do.

The method for transmitting a GFD descriptor according to the present invention for achieving the above object comprises: generating a GFD descriptor including at least one code point to be transmitted in a Generic File Delivery (GFD) mode; Adding the GFD descriptor to a signaling message to be transmitted to an MPEG Media Transport (MMT) receiving entity; And transmitting the signaling message to the MMT receiving entity.

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

In this case, the code points may be generated by the MMT sending entity by the number corresponding to at least one object to be transmitted in the GFD mode.

In this case, the MMT sending entity may generate the code point by generating a field constituting the code point according to the values of the at least one flag.

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

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

In this case, setting the GFD mode may include separately 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 step of separating and storing the number_of_Codepoints field is performed by using one of a method of copying the value of the number_of_Codepoints field to another variable and referring directly to a memory area in which the value of the number_of_Codepoints field is stored. You can refer to the value.

In this case, in the step of separating and storing, the code points may be separated and stored until the value of the number_of_Codepoints field becomes 0.

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

In addition, in the present invention, when generating a GFD descriptor for using the GFD mode, it is possible to more smoothly use the GFD mode in the MMT receiving entity by generating including information on components constituting the code point.

1 is an operation flow diagram showing a method for transmitting a GFD descriptor according to an embodiment of the present invention.
2 is an operation flow diagram showing a method of setting a GFD mode according to an embodiment of the present invention.
3 is a diagram showing a functional area constituting an MMT system.
4 is a diagram showing the configuration of a code point according to the present invention.
5 is a diagram showing the format of a GFD descriptor according to an embodiment of the present invention.
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 be described in detail with reference to the accompanying drawings as follows. Here, repeated descriptions, well-known functions that may unnecessarily obscure the subject matter of the present invention, and detailed descriptions of configurations are omitted. Embodiments of the present invention are provided to more completely explain the present invention to those with average knowledge in the art. Accordingly, the shapes and sizes of elements in the drawings may be exaggerated for clearer explanation.

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

1 is an operation flow diagram showing a method for transmitting a GFD descriptor according to an embodiment of the present invention.

Referring to FIG. 1, a method for transmitting a GFD descriptor according to an embodiment of the present invention may generate a descriptor including at least one code point to be transmitted in the 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 code points may be transmitted by grouping a plurality of code points according to the number of objects to be transmitted, and in this case, a GFD table may be used. The GFD table can be transmitted using the GFD descriptor format.

In this case, the code point may include at least one flag indicating whether fields constituting the code point exist. The code point is the value field, fileDeliveryMode field. It can be composed of a constantTransferLength_flag field, outOfOrderSending_flag field, FileTemplate_flag field, startTOI_flag field, endTOI_flag field, EntityHeader_flag field, maximumTransferLength field, FileTemplate_length field, FileTemplate_byte field, File_length field, File_byte field, startTOI field, endTOI field, and EntityHeader_length field, and EntityHeader_length field. The value field is a value used as a code point separator and may be set to a value from 1 to 255. That is, the value field may be set to different values for different code points. The fileDeliveryMode field is a field indicating the type of object to be delivered through the GFD mode. It may be set to 1 when transmitting a general file and 2 when transmitting an entity consisting of a header and file. The constantTransferLength_flag field may indicate whether each of the objects has the same size when a plurality of objects are transmitted. When all objects have the same size, it is set to 1, and the size of each object can be set in the maximumTransferLength field. The outOfOrderSending_flag field may indicate whether the outOfOrderSending field exists. It may be set to 1 when the outOfOrderSending field is present. The FileTemplate_flag field may indicate whether fields related to FileTemplate exist. It can be set to 1 when there are fields related to FileTemplate. If there is a FLUTE file element instead of the FileTemplate, it may be set to 0. The startTOI_flag field may indicate whether the startTOI field exists. If the startTOI field is present, it may be set to 1. The endTOI_flag field indicates whether the endTOI field exists, and may be set to 1 if the endTOI field is present. The EntityHeader_flag field indicates whether fields related to EntityHeader exist, and may be set to 1 when there are fields related to EntityHeader. The maximumTransferLength field is a field indicating the maximum size of an object to be transmitted. The maximum size of an object that can be transmitted may vary according to the length of the maximumTransferLength field. The FileTemplate_length field may indicate the size of a FileTemplate when a FileTemplate is included. The FileTemplate_byte field may mean each byte unit of FileTemplate included in the GFD descriptor. The File_length field may indicate the length of the File element when the FLUTE File element is included instead of the FileTemplate. The File_byte field may mean each byte unit of a File element included in the GFD descriptor. The startTOI field may indicate the TOI of the object to be transmitted first. The endTOI field may indicate the TOI of the object to be delivered last. The EntityHeader_length field may indicate the length of the entity-header included in the GFD descriptor. The EntityHeader_byte field may be a unit of each byte of an entity-header. 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 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 as described above. Can be seen.

In addition, code points may be generated in the MMT sending entity by the number corresponding to at least one or more objects to be transmitted in the GFD mode. Since the code point is information on an object to be transmitted in the GFD mode, a code point 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.

In this case, the MMT sending entity may generate a code point by generating a field constituting a code point according to at least one flag value. For example, by checking the fields in which flag values such as outOfOrderSending_flag, FileTemplate_flag, startTOI_flag, endTOI_flag, and EntityHeader_flag appear, fields can be created and set in code points corresponding to each flag value.

In this case, a field constituting the basic header of the GFD descriptor may be set based on at least one of a 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. In addition, there is a number_of_CodePoints field indicating the total number of code points included in the GFD descriptor, and the same number of code points as the value set in this field may be successively attached after 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 also be extended accordingly.

Thereafter, the GFD descriptor may be added to the signaling message to be transmitted 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 loaded in the asset_descriptors part of the MP table included in the MPT message when the MPT message is transmitted later and transmitted to the MMT receiving entity.

2 is an operation flow diagram showing a method of setting a GFD mode according to an embodiment of the present invention.

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

After that, 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 corresponding message, the GFD descriptor may be extracted and processing may be started.

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

In this case, the MMT receiving entity may separately store 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. The number_of_Codepoints field is a field indicating the total number of code points included in the GFD descriptor, and code points following the number_of_Codepoints field may be separately stored as much as a value set in the number_of_Codepoints field.

In this case, the value of the number_of_Codepoints field may be referred to by using one of a method of copying the value of the number_of_Codepoints field to another variable and referring directly to a memory area in which the value of the number_of_Codepoints field is stored.

At this time, each code point can be separated and stored until the value of the number_of_Codepoints field becomes 0. For example, by separating and storing one code point included in the GFD descriptor, and subtracting one from the number_of_Codepoints field value and the number of corresponding code points, it cycles until the number of remaining code points becomes 0. Can be done as an enemy. When storing each code point, the configuration of the code point may vary according to values of the outOfOrderSending_flag field, FileTemplate_flag field, startTOI_flag field, endTOI_flag field, and EntityHeader_flag field.

3 is a diagram showing a functional area constituting an MMT system.

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

The encapsulation layer 310 defines the logical structure of the format of the media content, the MMT package, and the data unit to be processed by the MMT entity and an implementation example in the ISO base media file format (ISOBMFF). do. In order to provide essential information for adaptive delivery, the MMT package specifies components including media content and relationships between them. The format of the data units is defined to encapsulate the encoded media for storage or delivery, and to easily convert between the two formats. The encapsulation layer 310 may be responsible for functions such as packetization, fragmentation, synchronization, and multiplexing of transmitted media. Various kinds of multimedia components can be encapsulated and combined with each other to be transmitted and consumed by functions provided in the encapsulation layer. The encapsulated media component and configuration information of the media component are provided in the functional area of the encapsulation layer 310. Main information about the encapsulated media components may include integration, priority, dependency of media fragments, timing information and structure information of MPU, identification information of MMT assets, initialization information, and codec information. The configuration information of the media components may include identification information of an MMT package and MMT asset, configuration information having a list of MMT assets, composition information of MMT assets in the MMT package, and asset delivery 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 delivery layer 320 may perform network flow multiplexing, network packetization, QoS control, etc. of media transmitted through a network, for example. In addition, the transport layer 320 between the transport layer and the encapsulation layer, multiplexing of media such as video and audio transmitted through the network, packet level integration and division, network packetization, QoS control, synchronization function , Transport layer such as RTP, transport layer such as UDP and TCP, encapsulation layer, and interface with signaling layer. The delivery layer 320 identifies different types of payloads passed over from the encapsulation layer 310 to handle the payload from the encapsulation layer 310. The transport layer 320 may handle a temporary relationship between packets transmitted through 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 timing restrictions of an MMT transport packet for real-time media transmission. The transport layer 320 may perform error control of MMT media packets such as omni-directional error correction and retransmission. The transport layer 320 may perform flow control of an MMT media packet. The transport layer 320 may interact with not only a lower layer but also another MMT layer through a cross-layer design in order to maintain a predetermined level of QoS for the delivery of an MMT media packet. In addition, the delivery layer 320 may provide a function for performing group communication.

The signaling layer 330 performs a silver signaling function. For example, session initialization/control/management of transmitted media, server-based and/or client-based trick mode, service discovery, synchronization and interface with other layers, i.e., the delivery layer 320 and the encapsulation layer 210 It can perform signaling functions for functions, etc. Synchronization may include synchronization control in a hybrid network. In addition, the signaling layer 330 defines a format of a message that manages delivery and consumption of an MMT package. The message for consumption management is used to inform the structure of the MMT package, and the message for delivery management is used to inform the structure of the payload format and the configuration of the protocol.

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

4, a code point according to the present invention is a value field and a fileDeliveryMode field. It can be composed of a constantTransferLength_flag field, outOfOrderSending_flag field, FileTemplate_flag field, startTOI_flag field, endTOI_flag field, EntityHeader_flag field, maximumTransferLength field, FileTemplate_length field, FileTemplate_byte field, File_length field, File_byte field, startTOI field, endTOI field, and EntityHeader_length field, and EntityHeader_length field.

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

The fileDeliveryMode field is a field indicating the type of object to be delivered through the GFD mode. It may be set to 1 when transmitting a general file and 2 when transmitting an entity consisting of a header and file.

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

The outOfOrderSending_flag field may indicate whether the outOfOrderSending field exists. It may be set to 1 when the outOfOrderSending field is present.

The FileTemplate_flag field may indicate whether fields related to FileTemplate exist. It can be set to 1 when there are fields related to FileTemplate. If there is a FLUTE file element instead of the FileTemplate, it may be set to 0.

The startTOI_flag field may indicate whether the startTOI field exists. If the startTOI field is present, it may be set to 1.

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

The EntityHeader_flag field indicates whether fields related to EntityHeader exist, and may be set to 1 when there are fields related to EntityHeader.

The maximumTransferLength field is a field indicating the maximum size of an object to be transmitted. The maximum size of an object that can be transmitted may vary according to the length of the maximumTransferLength field.

The FileTemplate_length field may indicate the size of a FileTemplate when a FileTemplate is included.

The FileTemplate_byte field may mean each byte unit of FileTemplate included in the GFD descriptor.

The File_length field may indicate the length of the File element when the FLUTE File element is included instead of the FileTemplate.

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

The startTOI field may indicate the TOI of the object to be transmitted first.

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

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

The EntityHeader_byte field may be a unit of each byte of an entity-header. 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.

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

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 same number of code points as the value set in this field may be successively attached after 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 also be extended accordingly.

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, first, a value of the number_of_CodePoints field may be stored in a variable (S610).

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

If the value of the variable is not 0 as a result of the determination in step S615, the value obtained by subtracting 1 from the value of the variable may be stored as the value of the new variable (S620).

Thereafter, each code point may be separated and stored in an order appended to 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 as described above, but the embodiments are implemented so that various modifications can be made. All or some of the examples may be selectively combined and configured.

310: Insulation layer
320: forwarding layer
330: signaling layer

Claims (10)

Generating a GFD descriptor including at least one code point to be transmitted in a Generic File Delivery (GFD) mode;
Adding the GFD descriptor to a signaling message to be transmitted to an MPEG Media Transport (MMT) receiving entity; And
Including the step of transmitting the signaling message to the MMT receiving entity,
The GFD descriptor includes at least one flag indicating whether fields constituting the code point exist,
The flag is
outOfOrderSending_flag indicating whether the outOfOrderSending field is present,
FileTemplate_flag indicating whether fields related to FileTemplate exist,
startTOI_flag indicating whether the startTOI field is present,
endTOI_flag indicating whether the endTOI field is present, and
An GFD descriptor transmission method comprising an EntityHeader_flag indicating whether the EntityHeader field exists. The method according to claim 1,
The GFD descriptor is
A method for transmitting a GFD descriptor, comprising: a basic header consisting of two fields. The method according to claim 2,
The GFD descriptor is
And a number_of_CodePoints field indicating the total number of the code points included in the GFD descriptor is included between the basic header and the code point. The method of claim 3,
The GFD descriptor is
And a value field having the same length as the number_of_CodePoints field. The method according to claim 1,
The GFD descriptor transmission method, wherein the number of code points corresponding to at least one object to be transmitted in the GFD mode is generated. Receiving a signaling message including a GFD descriptor from an MMT sending entity;
Extracting the GFD descriptor included in the signaling message; And
In order to provide a GFD mode, comprising the step of setting a GFD mode in the MMT receiving entity using the GFD descriptor,
The GFD descriptor includes at least one flag indicating whether fields constituting a code point exist,
The flag is
outOfOrderSending_flag indicating whether the outOfOrderSending field is present,
FileTemplate_flag indicating whether fields related to FileTemplate exist,
startTOI_flag indicating whether the startTOI field is present,
endTOI_flag indicating whether the endTOI field is present, and
And an EntityHeader_flag indicating whether the EntityHeader field is present. The method of claim 6,
The GFD descriptor is
A method of setting a GFD mode, comprising a basic header consisting of two fields. The method of claim 7,
The GFD descriptor is
And a number_of_CodePoints field indicating the total number of the code points included in the GFD descriptor between the basic header and the code point. The method of claim 8,
The GFD descriptor is
And a value field having the same length as the number_of_CodePoints field. The method of claim 6,
The GFD mode setting method, wherein the number of code points corresponding to at least one object to be transmitted in the GFD mode is generated.

Images