KR20160150065A - MMT apparatus and method for supporting de-capsulation buffer management - Google Patents

Abstract

An MMT device and method supporting decapsulation buffer management is disclosed. One embodiment is a method for managing a de-encapsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system, wherein the MMT transmitting entity performs encapsulation for one or more assets Generating a plurality of MMT protocol packets, generating MMT transmitting entity-specific buffer management information that is applied separately to one or more assets for management of a decapsulation buffer, and generating MMT transmitting entity- And transmitting the buffer management information for each asset to the MMT receiving entity.

Description

[0001] MMT apparatus and method for supporting de-encapsulation buffer management [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a media transfer service technology based on an MPEG Media Transport (MMT) system, and more particularly, to a technique of supporting de-encapsulation buffer management of an MMT receiving entity Technology.

MMT (MPEG Media Transport) is a new standard technology developed for the storage and transmission of multimedia contents in MPEG sub-working group. The existing standard technology based on the MPEG system division defines functions such as packetization, synchronization, and multiplexing necessary for transmitting multimedia contents in a broadcasting network, and it is widely used as standardized as MPEG-2 TS (Transport Stream) technology. However, MPEG-2 TS technology is developed based on the existing broadcasting network, and there is an inappropriate element in transmission of multimedia contents for IPTV broadcasting or mobile broadcasting based on IP (Internet Protocol) based network environment It is inefficient. Therefore, the MPEG system division has recognized the necessity of a new media transmission standard considering the new media transmission environment as well as the expected media transmission environment in the future, and as a result, the MMT standard has been developed as a result.

ISO / IEC 23008-1, which is the currently developed MMT standard, specifies various kinds of signaling messages. Currently, ISO / IEC 23008-1 2 ^nd edition ', which includes new signaling messages. An example of this is the signaling message for decapsulation buffer management called the Hypothetical Receiver Buffer Model (HRBM) data removal message. The HRBM data cancellation message is used to prevent the MMT packet from being lost due to buffer overflow in the decapsulation buffer of the MMT receiving entity or stopping the media playback due to the buffer exhaustion. Based on the information included in the HRBM data cancellation message, the data stored in the decapsulation buffer can be deleted in a predetermined unit.

Typically, an MMT receiving entity may receive several types of media data, i.e., assets simultaneously. That is, the MMT receiving entity may receive only media data for a specific asset, but may simultaneously receive media data for a plurality of assets during a specific time. The media data may have different media compression characteristics as well as transmission characteristics for each asset. However, the management of the currently considered decapsulation buffer does not sufficiently consider the characteristics of various media data stored in the decapsulation buffer, but merely decapsulates the decapsulation buffer based on the amount of the media data stored in the decapsulation buffer Only schemes to prevent buffer overflow or exhaustion are considered.

One object of the present invention is to provide an MMT apparatus and method capable of managing a decapsulation buffer by reflecting characteristics of various media data stored in a decapsulation buffer.

Another object of the present invention is to provide an MMT apparatus and method capable of managing a decapsulation buffer by differentiating each media data even if a plurality of media data is stored in a decapsulation buffer.

According to an aspect of the present invention, there is provided a method of managing a de-encapsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system, Encapsulating at least one asset to generate a plurality of MMT protocol packets, wherein the MMT transmitting entity is configured to store per-asset buffer management information that is separately applied to the one or more assets for management of the decapsulation buffer And transmitting the plurality of MMT protocol packets and the asset-specific buffer management information to the MMT receiving entity.

According to an embodiment of the present invention, the buffer management information for each asset may be transmitted to the MMT receiving entity using an HRBM data cancellation message generated by the MMT transmitting entity. To this end, the HRBM data removal message may include identification information for identifying an applied asset. The identification information may be information in the same format as the packet identifier included in the header of the MMT protocol packet.

According to another aspect of the present invention, there is provided a method of managing a de-encapsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system, Comprising the steps of: receiving a plurality of MMT protocol packets generated by encapsulating one or more assets from an MMT transmitting entity and buffered asset management information per asset; and transmitting the buffered asset management information to the one or more assets And separately managing the decapsulation buffer according to the HRBM.

According to an aspect of the embodiment, the MMT receiving entity can receive the buffer management information for each asset from the MMT transmitting entity using an HRBM data cancellation message. In this case, the HRBM data clear message may include identification information for identifying an applied asset. The identification information may be information in the same format as the packet identifier included in the header of the MMT protocol packet.

According to another aspect of the present invention, there is provided an MMT transmitting entity that supports management of a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) A processor for generating a plurality of MMT protocol packets by performing encapsulation on one or more assets and for generating per-asset buffer management information separately applied to the one or more assets for management of the decapsulation buffer, And a transmitter for receiving the plurality of MMT protocol packets and the buffer management information for each asset from the processor and transmitting the MMT protocol packets to the MMT receiving entity.

According to an aspect of the embodiment, the MMT transmitting entity may transmit the buffer management information for each asset to the MMT receiving entity using an HRBM data cancellation message. To this end, the HRBM data removal message may include identification information for identifying an applied asset. The identification information may be information in the same format as the packet identifier included in the header of the MMT protocol packet.

According to another aspect of the present invention, there is provided an MMT receiving entity that supports management of a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) Comprising: a receiver for receiving a plurality of MMT protocol packets generated by encapsulating at least one asset from an MMT transmitting entity and buffer management information for each asset; and a buffer for storing the buffer management information for each asset received by the receiver, And managing the decapsulation buffer according to the HRBM.

According to the embodiment of the present invention described above, the MMT receiving entity can know which HRBM data removal message is applied for management of the decapsulation buffer for an asset by using the received buffer management information for each asset. Therefore, the MMT receiving entity can manage the decapsulation buffer by differentiating the assets or MMT protocol server storms having different media compression characteristics and transmission characteristics from each other according to the asset.

1 is a diagram schematically illustrating a functional architecture of an MMT system.
FIG. 2 is a view schematically showing the configuration and operation of HRBM.
FIG. 3 is a diagram for explaining a method of operating the MMT transmitting entity and the MMT receiving entity using the HRBM data cancellation message.
4 is a diagram schematically illustrating an example of the timing at which an MMT receiving entity plays back three received assets.
FIG. 5 is a diagram schematically illustrating an example of a process of processing multiplexed MPU streams received by the MMT receiving entity of FIG. 4 based on a virtual receive buffer model (HRBM).
6 is a diagram showing a header structure of an MMT protocol packet.
FIG. 7 is a diagram illustrating a structure of an HRBM data cancellation message according to an exemplary embodiment of the present invention. Referring to FIG.
8 is a view for explaining an operation method of an MMT transmitting entity and an MMT receiving entity to which an entity-specific decapsulation buffer management is applied according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The terms used in this specification are terms selected in consideration of functions in the embodiments, and the meaning of the terms may vary depending on the user, the intention or custom of the operator, and the like. Therefore, the meaning of the terms used in the following embodiments is defined according to the definition when specifically defined in this specification, and unless otherwise defined, it should be interpreted in a sense generally recognized by those skilled in the art.

1 is a diagram schematically illustrating a functional architecture of an MMT system. Referring to FIG. 1, a functional area 10 of a MMT system includes a signaling layer 12, an encapsulation layer 14, and a delivery layer 16. The upper layer of the MMT system has a media coding layer, and the lower layer includes a transport protocol layer and an internet protocol layer.

The signaling layer 12 generates information necessary for media presentation and consumption and control information for optimizing the transmission quality, and transmits the data through the MMT protocol or through a separate signaling protocol. The encapsulation layer 14 performs functions such as packetization, fragmentation, synchronization, and multiplexing of the transmitted media. The transport layer 16 performs network flow multiplexing, network packetization, and QoS control of the media transmitted through the network.

The present invention relates to a technique for supporting de-encapsulation buffer management of an MMT receiving entity. More specifically, in the present invention, HRBM is a technique for describing a mechanism for removing buffered media data from a decapsulation buffer, which is one of the buffers constituting a Hypothetical Receiver Buffer Model (HRBM) of an MMT receiving entity. Suggests an improved technique associated with the data cancellation message. The HRBM data cancellation message is generated at the signaling layer of the MMT sending entity and the generated message may be transmitted to the MMT receiving entity via the MMT transport layer or another network transport layer.

Before describing the decapsulation buffer management in the MMT receiving entity using the HRBM data cancellation message, a description will first be given of a brief description of the virtual receiving buffer model (HRBM) adopted by the MMT protocol (MMT protocol, MMTP) do. FIG. 2 is a view schematically showing the configuration and operation of HRBM.

2, the HRBM according to the MMTP includes a forward error correction decoding buffer 22, a de-jitter buffer 24 and an MMTP decapsulation buffer 24, . The FEC decoding buffer 22 serves to absorb the delay time generated in the FEC encoding process in the transmitter. The digital buffer 24 serves to absorb a variation of a reception delay time between packets generated in a packet transmission process through the network. The decapsulation buffer 26 serves to absorb a processing delay time generated in the packet encapsulation process at the transmitting end. In the HRBM, the total end-to-end delay experienced by the packet from the transmitting end to the receiving end is always constant, regardless of the buffering action of the buffers 22, 24, And is managed in a fixed manner.

The HRBM data cancellation message provides information regarding the management of the MMT receiving entity's decapsulation buffer 26. This message includes an initial delay before starting to remove data from the decapsulation buffer 26 and a rate of removing data from the decapsulation buffer 26 rate of removing data from de-capsulation buffer). If this message is signaled, then the MMT receiving entity may use an operation mode with a maximum required buffer size included in this message to prevent overflow or underflow of the decapsulation buffer 26 . Depending on the mode of operation selected by the MMT receiving entity, a complete MPU (Media Processing Unit), a movie piece or an MFU (Media Fragment Unit) may be restored and the reconstructed data may be delivered to a higher level do.

FIG. 3 is a diagram for explaining a method of operating the MMT transmitting entity and the MMT receiving entity using the HRBM data cancellation message.

Referring to FIG. 3, the MMT transmitting entity receives the compressed media data 31 according to a predetermined media compression codec, and transmits the compressed media data 31 to the MMT receiving entity. The compressed media data 31 does not necessarily have to be one asset, and compressed media data of various assets can be input to the MMT transmitting entity concurrently or sequentially.

The MMT transmitting entity performs an encapsulation process on the compressed media data to generate an MMT packet including the compressed media data (32). At the same time, the MMT transmitting entity generates a signaling message for transmitting and consuming the compressed media data and / or the generated MMT packet, wherein the generated signaling message includes an HRBM data clear message (33). As described above, in the HRBM data cancellation message, information necessary for managing the decapsulation buffer of the MMT receiving entity, that is, the MMT packet is decapsulated in the decapsulation buffer of the MMT receiving entity without overflow or depletion of the buffer Required buffer management information is included. The MMT transmitting entity transmits the generated MMT packet and the HRBM data removal message to the MMT receiving entity using the MMT protocol or another transmission protocol.

The MMT receiving entity receives various MMT packets (34). The MMT receiving entity receives the signaling message including the HRBM data cancellation message and may obtain the decapsulation buffer management information from the received HRBM data cancellation message (35). The MMT receiving entity can stably manage the buffer while avoiding overflow or exhaustion of the decapsulation buffer based on the acquired decapsulation buffer management information (36). In the MMT system, decapsulation buffer management is applied to all assets in a comprehensive manner, thereby enabling consumers to provide high quality media services through continuous playback.

Media streams transmitted in the MMT service based on the MMT protocol include various types of streams such as a video stream, an audio stream, a data stream, and a widget stream. Streams composed of non-timed data can be presented through independent playback processes in the receiving entity, and streams composed of timed data can be synchronized using synchronization time information And can be reproduced simultaneously in the receiving entity while maintaining temporal synchronization with each other. Each of these various types of media streams conceptually corresponds to an asset of the MMT, and the asset logically has a data structure including a plurality of MPUs. For example, if the media stream is a video stream, the asset is a concept corresponding to the entire specific video sequence, and the MPU is a concept corresponding to a frame group composed of an integer number of frames belonging to the sequence. The MFU is a further subdivided unit of the MPU, for example, a concept corresponding to the degree of slicing of video.

4 is a diagram schematically illustrating an example of the timing at which an MMT receiving entity plays back a plurality, e.g., three, of the received assets. Here, the three assets may be assets multiplexed and transmitted for one complete multimedia service. All of the assets in FIG. 4 correspond to temporal data, and the MMT receiving entity can reproduce data of the plurality of assets, for example, multiple streams while maintaining temporal synchronization on an MPU basis. The start-up playback time of each MPU is specified in a presentation information document (Presentation Information (PI) document).

Referring to FIG. 4, the MMT receiving entity simultaneously reproduces the first MPU (MPU # 1) of the first asset (Asset # 1) and the first MPU (MPU # 1) of the second asset (Asset # 2). Thereafter, the MMT receiving entity reproduces the first MPU (MPU # 1) of the third asset (Asset # 3). The MMT receiving entity then transmits the second MPU (MPU # 2) and the third MPU (MPU # 3) of the first asset (Asset # 1) to the second MPU (MPU # 2) of the second asset (Asset # And the third MPU (MPU # 3).

FIG. 5 is a diagram schematically illustrating an example of a process of processing multiplexed MPU streams received by the MMT receiving entity of FIG. 4 based on a virtual receive buffer model (HRBM).

Referring to FIG. 5, the MMT receiving entity 40 receives a multiplexed MPU stream in which a plurality of MPUs belonging to different assets are multiplexed and transmitted. At this time, the MMT receiving entity 40 classifies the MPUs multiplexed and received into assets to be respectively included through a demultiplexer 42, and then the MPUs sorted by the assets are classified into a corresponding virtual reception buffer model (HRBM) Therefore, processing is performed while buffering. For example, the MMT receiving entity 40 may decapsulate an MMTP packet input using the information contained in the received HRBM data cancellation message and / or remove the MMTP packet being buffered, It manages the replication buffer.

As shown in FIG. 5, when multiplexed streams of MPUs belonging to a plurality of assets are input, different assets have different delivery characteristics as well as media compression characteristics. Therefore, the parameters used for data removal in the decapsulation buffer may also be different for each asset, since the parameters related to the virtual reception buffer model must be different from one another.

However, according to the structure of the existing HRBM data cancellation message, information indicating which parameter included in the message is applied to which asset is not included. As a result, if the conventional technology is applied as it is, the MMT receiving entity applies the parameters included in the HRBM data removal message received at a specific time to all the received assets at the corresponding time. The decapsulation buffer management of this method does not take into consideration that the media compression characteristics as well as transmission characteristics may be different for each asset.

In order to solve such a problem, in the decapsulation buffer management method according to the embodiment of the present invention, the MMT transmitting entity transmits the HRBM data removal message and the identification information for identifying the asset to which the message is applied to the MMT receiving entity. That is, the MMT transmitting entity generates buffer management information for each asset for managing the decapsulation buffer separately for each asset, and transmits it to the MMT receiving entity. According to this, the MMT transmitting entity can determine the values of the parameters included in the HRBM data cancellation message for each asset, so that the decapsulation buffer can be managed in consideration of the compression characteristics and transmission characteristics of the specific assets. That is, the MMT transmitting entity generates an HRBM data removal message including parameters considering the compression characteristics and transmission characteristics of the corresponding asset, and identifies the asset to which the corresponding message is applied, together with the generated HRBM data removal message, As shown in FIG. And the MMT receiving entity can apply the parameters contained in the received HRBM data clear message to all the assets uniformly, but only to the assets indicated by the received identification information, either individually or individually.

According to an embodiment of the present invention, the identification information may be included in the HRBM message and transmitted from the MMT transmitting entity to the MMT receiving entity. To this end, the MMT transmitting entity may generate an HRBM data cancellation message including the identification information of the asset to which the message is applied and transmit the message to the MMT receiving entity. The MMT receiving entity may then parse the received HRBM data removal message and then use the parameters contained in the HRBM data removal message parsed in the management of the decapsulation buffer for the asset indicated by the identification information included in the message.

Here, if the identification information is capable of identifying an asset, there is no particular limitation on the type and expression format of the asset. If there is an asset identifier for each asset, it can be used as identification information. For example, a packet identifier (packet identifier or packet_id) may be used as the asset identifier. 6 is a diagram showing a header structure of an MMT protocol packet. Referring to FIG. 6, the MMT protocol uses a packet ID (packet_id) included in an MMTP packet header as an object for identification between assets . In an embodiment of the present invention, the packet identifier may be included in the HRBM data cancellation message and used to identify an asset to which the corresponding message is applied.

FIG. 7 is a diagram illustrating a structure of an HRBM data cancellation message according to an exemplary embodiment of the present invention. Referring to FIG. 7, the HRBM data cancellation message includes a message ID information, a version information, a length information, a packet ID information, an operation mode number_of_operation_mode information, a data removal type data_removal_type, Maximum decapsulation buffer size (max_decapsulation_buffer_size) information, and buffer management validity (buffer_management_valid) information. In FIG. 7, the packet ID information, the operation mode information, the data removal type information, the maximum decryption buffer size information, and the buffer management validity information are shown as components of the payload of the message, .

The message ID information indicates that the message is an HRBM data clear message. The version information indicates the version of the HRBM data removal message and the MMT receiving entity can check the version of the received HRBM data removal message using the version information. The length information indicates the length of the HRBM data removal message.

The packet ID information may be information that can be used to distinguish a specific asset from another asset, and may be a value derived from an asset ID of the corresponding asset. And the mapping between the asset ID and the packet ID may be transmitted from the MMT transmitting entity to the MMT receiving entity as part of the signaling information.

The mode of operation information provides information about the mode of operation in which the MMT receiving entity may choose to operate. The data clear type information provides information about the type of operation mode at the MMT receiving entity that removes the data being recovered from the decapsulation buffer. For example, the MMT receiving entity may determine whether the MPU Unit, movie fragment unit, MFU unit, and the like. The maximum decache buffer size information provides information about the maximum size required for the decapsulation buffer. The buffer management validity information provides information on whether or not the buffer management mechanism defined for the asset is applied.

8 is a view for explaining an operation method of an MMT transmitting entity and an MMT receiving entity to which an entity-specific decapsulation buffer management is applied according to an embodiment of the present invention. 8 may be an operation method of the MMT transmitting entity and the MMT receiving entity using the HRBM data cancellation message shown in FIG. Here, the MMT transmitting entity is a device for transmitting multimedia data and related information, and may be both a server and a client. The MMT receiving entity is a device for receiving and reproducing multimedia data and related information, and may include a media playback client including a smart phone and a smart pad.

Referring to FIG. 8, the MMT transmitting entity receives compressed media data 51 according to a predetermined media compression codec, and transmits the compressed media data 51 to the MMT receiving entity. The compressed media data 51 does not necessarily have to be an asset, and compressed media data of various assets can be input to the MMT transmitting entity concurrently or sequentially.

Then, the MMT transmitting entity performs an encapsulation process on the compressed media data to generate an MMT packet including the compressed media data (52). At the same time, the MMT transmitting entity generates a signaling message for transmission and consumption of the corresponding compressed media data and / or generated MMT packet, wherein the generated signaling message includes an HRBM data clear message (53).

According to an aspect of the present embodiment, the HRBM data removal message includes information necessary for managing the decapsulation buffer of the MMT receiving entity differentiated by the asset. That is, the MMT transmitting entity includes the buffer management information in consideration of the media compression characteristic and the transmission characteristic in which the difference is generated for each asset when generating the MMT protocol packet for the asset, in the HRBM data removal message. Here, the HRBM data cancellation message is an example of a message including buffer management information for each asset as described above. The MMT transmitting entity transmits an HRBM data removal message including buffer management information differentiated by the generated MMT packet to the MMT receiving entity using the MMT protocol or another transmission protocol.

For operation in such an MMT transmitting entity, the MMT transmitting entity may comprise a processor, either hardware implemented or implemented in software, with means for receiving compressed media data and means for transmitting the packet, . Then, the processor of the MMT transmitting entity performs a process according to reference numerals 52 and 53 of FIG. 8, that is, a process of generating MMTP packets through encapsulation of various assets input in the form of compressed media data, And a process of generating a signaling message including information for managing the decapsulation buffer (e.g., the HRBM data removal message of FIG. 7).

The MMT receiving entity receives various MMT packets (54). The MMT receiving entity receives the signaling message including the HRBM data cancellation message, and can acquire the decapsulation buffer management information differentiated by the asset from the received HRBM data cancellation message, that is, the buffer management information for each asset (55). The MMT receiving entity can stably manage the buffer while avoiding overflow or exhaustion of the decapsulation buffer for each asset based on the acquired decapsulation buffer management information (56). That is, the MMT receiving entity performs decapsulation buffer management by applying parameters included in the HRBM data cancellation message only to the entity indicated by the packet identifier included in the HRBM data cancellation message. Accordingly, in the MMT system to which the embodiment of the present invention is applied, it is possible to provide a high-quality media service through seamless playback to the consumer by managing the decapsulation buffer for each MMT asset.

For operation in such an MMT receiving entity, the MMT receiving entity may include a processor for receiving packets and means for recovering multimedia content, as well as a processor implemented in hardware or implemented in software . At this time, the processor of the MMT receiving entity processes the buffer management information for managing the decapsulation buffer, which is differentiated according to the process according to reference numerals 55 and 56 of FIG. 8, And a process of managing the decapsulation buffer for each asset according to the acquired buffer management information.

The above description is only an example of the present invention, and the technical idea of the present invention should not be interpreted as being limited by this embodiment. The technical idea of the present invention should be specified only by the invention described in the claims. Therefore, it is apparent to those skilled in the art that the above-described embodiments may be modified and embodied in various forms without departing from the technical spirit of the present invention.

Claims (13)

A method for managing a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system,
The MMT transmitting entity performing an encapsulation for one or more assets to generate a plurality of MMT protocol packets;
Generating, by the MMT transmitting entity, per-asset buffer management information that is separately applied to the one or more assets for management of the decapsulation buffer; And
And the MMT transmitting entity transmitting the plurality of MMT protocol packets and the asset-specific buffer management information to the MMT receiving entity. The method according to claim 1,
Wherein the buffer management information for each asset is transmitted to the MMT receiving entity using an HRBM data cancellation message generated by the MMT transmitting entity. 3. The method of claim 2,
Wherein the HRBM data removal message includes identification information for identifying an applied asset. The method of claim 3,
Wherein the identification information is information in the same format as a packet identifier included in a header of the MMT protocol packet. A method for managing a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system,
Receiving a plurality of MMT protocol packets and asset-specific buffer management information generated by the MMT receiving entity by encapsulating one or more assets from the MMT transmitting entity; And
And managing the decapsulation buffer according to the HRBM by applying the asset-specific buffer management information to the at least one asset separately by the MMT receiving entity. 6. The method of claim 5,
Wherein the MMT receiving entity receives the buffer management information for each asset from the MMT transmitting entity using an HRBM data cancellation message. The method according to claim 6,
Wherein the HRBM data removal message includes identification information for identifying an applied asset. 8. The method of claim 7,
Wherein the identification information is information in the same format as a packet identifier included in a header of the MMT protocol packet. In an MMT transmitting entity supporting management of a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system,
A processor for generating a plurality of MMT protocol packets by performing encapsulation on one or more assets and generating per-asset buffer management information that is separately applied to the one or more assets for management of the decapsulation buffer; And
And a transmitter for receiving the plurality of MMT protocol packets and the buffer management information for each asset from the processor and transmitting the MMT protocol packets to the MMT receiving entity. 10. The method of claim 9,
And generates an HRBM data cancellation message including the buffer management information for each asset and transmits the message to the MMT receiving entity. 11. The method of claim 10,
Wherein the HRBM data removal message comprises identification information for identifying an applied asset. 12. The method of claim 11,
Wherein the identification information is information in the same format as the packet identifier included in the header of the MMT protocol packet. In an MMT receiving entity supporting management of a de-capsulation buffer according to a Hypothetical Receiver Buffer Model (HRBM) in an MMT system,
A receiver for receiving a plurality of MMT protocol packets generated by encapsulating one or more assets from an MMT transmitting entity and buffer management information for each asset; And
And a processor for managing the decapsulation buffer according to an HRBM by separately applying the buffer management information for each asset received by the receiver to the one or more assets.

Images