KR20190101340A - Apparatus and method for receiving a multimedia data packet - Google Patents

Abstract

The present invention relates to a method of receiving multimedia data packets. The method includes the following steps of: receiving data packets; and decoding the data packets. The data packets include a header and media data. The header includes classifier information for per-class QoS and label information for per-flow QoS. The classifier information provides a QoS class related with priority over the transmission of the data packets. The label information indicates an identifier of a flow to which the data packets belong. The flow is a data stream with a reserved network resource. The classifier information and the label information are generated on a layer between an upper protocol layer for providing the media data and a lower protocol layer which is a network layer. The layer provides a function for delivering information related with the media data provided from the upper protocol layer to the lower protocol layer by abstracting the information.

Description

Method and apparatus for receiving multimedia data packet {APPARATUS AND METHOD FOR RECEIVING A MULTIMEDIA DATA PACKET}

The present invention relates to a method and apparatus for receiving a multimedia data packet, and more particularly, to a method and apparatus for adaptively receiving a multimedia data packet according to a QoS scheme.

Multimedia services refer to services such as interactive services such as video telephony, streaming services such as video on demand (VOD) services, and multicast and broadcast services. Real-time multimedia services can be divided into interactive services, interactive services, and streaming services, depending on the type of service. In addition, the real-time multimedia service may be divided into unicast, multicast, and broadcast according to the number of users participating.

 In order to provide multimedia services, a method of providing a quality of service (QoS) in a network can be broadly classified into a BE (best effort) method, a per class QoS (QoS) method, and a per flow QoS (QoS) method. have.

The BE scheme means no support for QoS.

The QoS method by class is a method of processing according to importance in the middle of the network by varying the importance of each packet. That is, the QoS method for each class is a method of controlling QoS according to the importance of the packet, that is, the priority, regardless of which flow the packet belongs to. In order to support class-specific QoS schemes, resource reservation between a sender and a receiver is not necessary. For reference, the priority includes a loss priority, a delay priority, and the like.

* Quality method by flow is a method of reserving resources for each stream. That is, a method of reserving a resource (eg, bit rate, buffer state) or QoS (delay, loss rate, etc.) for each flow. Here, the flow refers to a stream required for one service. For example, the video stream, audio stream, and text stream required to provide on-demand video services become separate flows.

In addition to IEEE 802.16 (WiBRO, WIMAX) and Long Term Evolution (LTE), the UMTS (3G) of 3GPP is standardized to support QoS by class and QoS by flow. However, in order to use the QoS scheme, an interface between a media layer, which is a higher layer, and a network, which is a lower layer, is required.

The importance of each packet is different for each video packet when using Moving Picture Experts Group (MPEG) -2 and H.264 or in particular, scalable video coding (SVC). In order to effectively control the QoS of the video service, such a difference in importance of each packet must be identified. In IPv6, in order to identify the importance of each packet, the packet switching method reads 5 parameters (5 turples: recipient address, sender address, port number of corresponding service in receiver, port number of corresponding service in transmitter, and protocol used) in IPv6 header. Afterwards, the payload of the video packet must read header data that identifies the importance of the packet. This approach not only takes much processing time per packet, but also violates the protocol layer independence.

In other words, the router should read only the IP header of the packet and process the packet.

However, if the importance of each packet can be easily identified, quality of service (QoS) control can be smoothly performed in the router. For example, if the network condition is bad, packets that are not important may be discarded according to the importance of each packet.

Meanwhile, scalable video coding (SVC) technology or multi-view video coding (MVC) technology, which is currently being standardized, is based on the H.264 / Advanced Video Coding (AVC) standard. have. The format of the network abstraction layer unit (NALU) of H.264 / AVC is also used in the configuration of the bit string of the encoded data.

1 is a view for explaining a video coding layer (or video coding layer (VCL)) and a network abstraction layer (NAL) in H.264 / AVC.

In H.264 / AVC, a Network Abstraction Layer (VCL) 110 between a video coding layer (VCL) 110 that handles the video encoding process itself and a subsystem 130 that transmits and stores the encoded information. NAL) 120 is defined so that the video coding layer (VCL) and the network abstraction layer (NAL) are separated.

Map encoded data 111 generated in the VCL to a bit string of a sub-system such as H.264 / AVC file format 131, Real-time Transport Protocol (RTP) 133, or MPEG-2 system 135 In order to do this, the NAL 120 processes the encoded data 111 generated in the VCL and information of a parameter set or Supplemental Enhancement Information (SEI) and the like 113 in a NAL unit (NALU).

The NAL unit is divided into a VCL NAL unit 123 and a non VCL NAL unit 125. The VCL NAL unit 123 is a NAL unit corresponding to the encoded data 111 generated in the VCL, and the non-VCL NAL unit 125 is a NAL unit corresponding to information of a parameter set or SEI 113. .

The NAL unit basically includes a NAL header and a raw byte sequence payload (RBSP), which is a data portion generated as a result of video compression in the VCL.

2 is a diagram illustrating a format in NAL units.

Referring to FIG. 2, the NAL unit 200 includes a NAL header 210 and a NAL payload 240.

NAL header 210 generally has a size of 1 to 5 bytes. The NAL header 210 includes NALU type information 220 for indicating the type of NAL unit and layer identification information 230 for identifying a layer of compressed original data included in the NALU payload. ).

The NALU type information 220 includes a 1-bit fixed bit (F) field 221, a 2-bit NRI (nal_ref_idc) field 222 which is a flag indicating whether or not it is a reference picture, and an identifier indicating the type of a NAL unit. 5 bits NALU Type field 223 is included.

The layer identification information 230 may include, for example, a combination of priority, spatial layering level, temporal layering level, and / or quality layering level. That is, the layer identification information 230 is an 8-bit Priority field (P) 231 for indicating priority to identify a layer of compressed original data, and for indicating a spatial layering level. 3-8 bits Dependency_id field (D) 232, 3-8 bits Temporal_level (Temporal Level) field (T) 233 to indicate temporal layering level, and / or quality It may include a Quality_level (Q) field 234 of 2 to 8 bits to indicate the layering level.

For reference, the format of the NALU is equally used in MVC (Multi-view Video Coding). However, in MVC, view identification information for identifying a view instead of the layer identification information 230 may be included in the NAL header together with the NALU type information 220.

According to the NAL unit format according to the current SVC or MVC described above, in order to identify a layer or a view of the NAL unit, both the layer identification information 230 and the view identification information of the NAL header must be parsed. In particular, the layer identification information 230 has a size of 4 bytes or less, and all the values of P (231), D (232), T (233), and Q (234) must be known through parsing of the NAL header 210. The layer to which the corresponding NAL unit belongs can be determined. However, parsing all of the NAL header 210 to know the values of P (231), D (232), T (233), and Q (234) of the NAL header 210 burdens the processor and increases the cost of the system. It can cause an increase.

In addition, the NAL header 210 includes a NRI field 222 and a Priority field (P) 231 as well as packets such as layer identification information 230 such as the D 232, the T 233, and the Q 234. It contains a variety of information that can identify the importance of the, because there is no relationship between the information is difficult to use it. For example, with respect to the layer identification information D 232, T 233, and Q 234, a packet having '1' as the value of D 232 and a packet having '1' as the value of T 233. In this case, if there is no understanding of the predictive relationship of the coding process, the superiority and priority of the two packets cannot be distinguished.

In addition, the current network abstraction layer (NAL) is designed only for video services. Therefore, for future media services in which various media components such as audio, video, text, and user interface are combined, it is necessary to introduce a media abstraction layer capable of abstraction regardless of the type of media component.

The present invention provides a method and apparatus for receiving an adaptive multimedia service when providing a multimedia service.

In addition, the present invention provides a media abstraction layer that enables the lower network layer to utilize information of an application layer by abstracting various media elements.

In addition, the media abstraction layer according to the preferred embodiment of the present invention provides specific importance information for the lower layer based on the understanding at the MPEG level.

In addition, the information generated through the media abstraction layer according to the preferred embodiment of the present invention is included in the IP header, thereby facilitating access to necessary information by simple processing in a lower layer.

A method for receiving a multimedia data packet according to an embodiment of the present invention may include receiving a data packet and decoding the data packet, wherein the data packet includes a header and media data. The header includes classifier information for per-class QoS and label information for per-flow QoS, the identifier information relating to the transmission priority of the data packet. Provide a QoS class, wherein the label information indicates an identifier of a flow to which the data packet belongs, the flow is a data stream to which network resources are reserved, and the generation of the identifier information and the label information provides the media data. Is performed in a layer between an upper protocol layer and a lower protocol layer that is a network layer. Followed by abstraction information associated with the media data supplied from the higher protocol layer, and provides a function of transmitting to the lower protocol layer.

An apparatus for receiving a multimedia data packet according to an embodiment of the present invention, a processor; And a receiver configured to receive a data packet under control of the processor, wherein the data packet includes a header and media data, and the header includes classifier information and per flow information for per-class QoS. (per-flow) includes label information for QoS, the identifier information providing a QoS class related to the transmission priority of the data packet, the label information to identify the flow to which the data packet belongs. The flow is a data stream for which network resources are reserved, and the generation of the identifier information and the label information is performed at a layer between an upper protocol layer that provides the media data and a lower protocol layer that is a network layer. Related to the media data provided by the higher protocol layer The information abstraction, there is provided a function of transmitting to the lower protocol layer.

Representative effects according to a preferred embodiment of the present invention are as follows.

In a preferred embodiment of the present invention, by providing a media abstraction layer applicable to all multimedia data, the multimedia service can be provided by reflecting the importance or priority of the media data, resource reservation status, network status, or user requirements. have.

According to a preferred embodiment of the present invention, the simplified header structure does not require the device that receives the IP packet to parse fields corresponding to the flow label every time, thereby enabling efficient resource utilization of the receiving device.

1 is a diagram for explaining a video coding layer and a network abstraction layer in H.264 / AVC;
2 is a diagram for explaining a format in NAL units;
3 is a diagram illustrating a configuration of a transmitting side according to a preferred embodiment of the present invention;
4 is a view for explaining a method of including MAL information in an IP packet according to an embodiment of the present invention;
5 is a view for explaining the structure of an IP packet header including MAL information according to a preferred embodiment of the present invention;
6 is a view for explaining the configuration of a network entity device according to an embodiment of the present invention;
7 is a diagram illustrating a receiving side apparatus according to a preferred embodiment of the present invention.

In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. In addition, terms to be described below are terms defined in consideration of functions in the present invention, and may be changed according to the intention or custom of a user or an operator. Therefore, the definition should be made based on the contents throughout the specification.

Prior to detailed description, the basic concepts of the present invention will be described.

In the preferred embodiment of the present invention, a network abstraction layer used in MPEG-4 / AVC (Advanced Video Coding (H.264), Scalable Video Coding (SVC), Multi-view Video Coding (MVC), etc.), which are standards for video data. It complements the concept of Network Abstraction Layer (NAL) and applies it to services not only video data but also other media (audio, graphics, text, etc.) data.

As described with reference to FIG. 2, the existing NAL header 210 includes various information indicating the importance of a video packet. In addition, the NAL header used in the SVC includes layer recognition information 230 that can recognize a temporal layer, a spatial layer, and a quality layer, and the NAL header used in the MVC includes information indicating a view number. It is.

The information included in the NAL header is information generated by being abstracted from a top-down interface transferred from an upper protocol layer to a lower protocol layer and may indicate the importance of a corresponding packet. According to the state of the packet service can be adaptively provided.

The present invention defines the identifier "media classifier" and "label" in order to extend the concept of the NAL to all media. In the present invention, the "media separator" is responsible for providing abstracted priority information so that priority information of the media can be utilized without specific understanding of the media in the lower protocol layer. The "label" is an identifier for distinguishing each stream (for example, a video stream or an audio stream).

In addition, the present invention proposes a Media Abstraction Layer (MAL), which is a top-down interface that abstracts information related to media data to be transmitted. In the following description, data related information abstracted from the MAL may be referred to as MAL information.

Meanwhile, in the present invention, the transmitting apparatus (server or terminal) generates the MAL information and includes the packet in the header of the packet and transmits the packet. And transmit the packet accordingly.

3 is a diagram illustrating a configuration of a transmitting side according to a preferred embodiment of the present invention.

The transmitting side may be a server that provides a multimedia service.

The transmission device 300 includes a media data supply unit 301, a media abstraction layer unit 302, which is a unique configuration for the present invention, and a packet generator 303.

The media abstraction layer unit 302 receives one IP packet from the media data supply unit 301 (308), generates MAL information, and delivers it to the packet generator 303 (310). The media abstraction layer unit 302 transmits the IP packet received from the media data supply unit 301 to the packet generator 303 (309).

At this time, the MAL information on the media data generated by the media abstraction layer unit 302 may include media identifier information and label information. As described above, the media identifier information may be used to recognize abstracted importance information of the media packet in a lower network, and the label information may be used for the lower network to identify the packet.

The packet generator 303 generates a packet using the received MAL information 310 and the IP packet 309 from the media abstraction layer unit 302, and transmits the generated packet through the network 313. (311). Media identifier information and label information included in the MAL information may be included in a header of an IP packet or a packet header of another lower protocol.

An example of transmitting a packet according to the configuration of FIG. 3 will be described below.

First, the QoS method for each class using the media identifier generated in the MAL will be described.

Assume that the media identifier of the audio data stream is 1, the media identifier of the character data stream is 2, and the media identifier of the video data stream is 3, and the server and the terminal are previously promised (or set). It is also assumed that the priority for the stream in which the media separator is set is also promised between the transmitting side, the network entity, and the receiving side.

In this case, when the transmitting side wants to transmit a video data packet, the packet is generated and transmitted by setting media identifier information to 3 in the packet. The network entity (eg, a router) may recognize the QoS class of the received packet through the media identifier information (ie, 3) of the received packet. Thereafter, the network entity may determine whether to forward the packet in consideration of the network state and the forwarding policy of the QoS class.

Next, a flow-based (ie, stream-specific) QoS scheme using label information generated in the MAL will be described.

Assume that the label of the audio data stream is 1, the label of the text data stream is 2, and the label of the video data stream is 3, and the appointment is set in advance (or set) between the server and the terminal.

In this case, when the transmitting side wants to transmit the video data packet, the packet is set and the label information is set to 3 to generate and transmit the packet. Then, the network entity (for example, the router) may recognize the importance, priority, or resource reservation information of the received packet through the label information (ie, 3) of the received packet. Thereafter, the network entity may transmit the packet in consideration of network status and importance, priority, or resource reservation information of the received packet.

The label for each data stream and the importance, priority, or resource reservation information according to the label may be set in a call setup process between a transmitter, a receiver, and a network entity.

Hereinafter, MAL information which is media abstraction layer information proposed by the present invention will be described.

The MAL information is used to allow the lower-level network entities to recognize the abstracted QoS class of the media and to recognize the loss and delay importance, priority, or resource reservation information of the data packet. The information is included in the packet in the form of a label (ie tag). Meanwhile, the MAL information format proposed by the present invention may be used together with other existing protocol standards, for example, an IP header, a transmission control protocol (TCP) and a user datagram protocol (UDP) header, and an RTP header protocol.

In order to provide a media service using the MAL information, a call setup process between the transmitting and receiving network is required. That is, through the call establishment process, each network entity mutually promises what the label value means.

The table that summarizes the values of each label value is called a label table (LT). If a call setup process between a transmitting and receiving network such as a broadcasting network is impossible, a method of transmitting LT at periodic time intervals such as Program Map Tables (PMT) of the MPEG-2 system may be used.

Meanwhile, in a preferred embodiment of the present invention, the MAL information is divided into a media separator format for class QoS scheme and a label format for stream QoS scheme.

In case of the QoS method for each class, the media is abstracted based on the requirements for the loss rate and the transmission delay and included in the form of a delimiter without a resource reservation process for providing a service between a transmitter and a receiver.

For example, if one media service consists of one video stream, audio stream, and text stream for subtitle support, the MAL abstracts the QoS class according to the transmission delay and loss requirements of each stream. Format determines the media separator value. Optionally, the audio stream may be of higher importance than the video stream. As described later in FIG. 4, the media identifier value at this time may be inserted into a TOS (Type Of Service) field of the IPv4 header or a TC (Traffic Class) field of the IPv6 header. For example, if the size of the media identifier value is set to 2 bits, the importance of each packet is differentiated in the order of 11, 10, 01, 00. That is, a media identifier value of 11 can be inserted in an audio packet, 10 in a text packet, and 01 in a video packet.

Next, an example of applying different media separators to a plurality of sub streams constituting a single stream is as follows.

If video streams can be divided into layers of different priorities, such as SVCs, then the base layer must be of high importance for the three layers (base layer, advanced 1 layer, and advanced 2 layer), and priority arrival must be guaranteed over other layers. Therefore, the QoS class is assigned with low transmission delay and packet loss. The high layer 1 and the high layer 2 each allocate a lower class of QoS than the base layer. As shown in the above example, if the size of the media identifier is set to 2 bits, the QoS class is differentiated into 11 for the base layer, 10 for the high layer 1, and 01 for the high layer 2.

In the case of the flow-based QoS scheme, resource reservation is made for each stream and for this purpose, label information is included in the corresponding flow. For example, assuming that a resource of 300 kbps is reserved for a flow having a label value of 1, a label value generated in a sender and included in a packet is 1, and the network entity checks a label value included in the packet. In this case, the flow is transmitted using a resource of 300kbps corresponding to the label value 1 using the LT received in the call setup process and the label value of the packet. Optionally, in this case, the resources currently available may also be considered.

Optionally, the resource reservation may also be made for each session. That is, label information may be configured in stream units or session units according to whether a resource reservation is made in a stream unit or a session unit to support label switching when establishing a call between a transmission and reception network.

In addition, the resource reservation process and label information setting may be promised in advance in a call setup process between a transmitter and a receiver. For reference, when the network entity supports Multi Protocol Label Switching (MPLS), the label format of the present invention may be configured to be compatible with the label format supported by the MPLS. In this case, if the receiver can recognize the label of the present invention that is compatible with the label of the MPLS scheme, the existing NAL header defined in the SVC may not be transmitted. In addition, the information that does not change during one session among the contents of the existing RTP header and UDP header can be included in the label. The label switching is a technique for routing 3rd layer packets in a 2nd layer. In this case, a label is added to a data packet instead of an IP address to implement switching using the added label to enable high-speed switching.

Hereinafter, a method of transmitting the MAL information will be described.

4 is a diagram illustrating a method of including MAL information in an IP packet according to an embodiment of the present invention.

In the MAL information format defined in the preferred embodiment of the present invention, virtual headers for MAL packets are defined. Content included in the virtual header is to be included in a packet header (for example, an IP packet header) of a lower layer, and the virtual header 420 is internally divided into a media identifier header 421 and a label header 422. .

The media identifier header 421 may be applied when a lower layer uses a QoS scheme for each class, and its length may vary according to system configuration. In consideration of compatibility with the QoS protocol of each lower layer, about 3 to 6 bits are preferable. The media identifier header 421 may be inserted into the TOS field 411 of the IPv4 header 410 or inserted into the TC field 431 of the IPv6 header 430.

The label header 422 may be applied when the lower layer uses a flow-based QoS scheme. A total of 8 bit sized label header 422 is composed of 7 bits including the number of the label and 1 bit of the extension flag bit for extension if necessary. The label header 422 may be inserted into an extended IP header 413 of the IPv4 header 410 or inserted into a flow label field 433 of the IPv6 header 430.

5 is a diagram illustrating a structure of an IP packet header including MAL information according to a preferred embodiment of the present invention.

The example illustrated in FIG. 5 illustrates a method of simplifying a header by removing an identically repeated portion of a UDP header and an RTP header among a plurality of packets to be applied to a real time media stream, and including this information in the LT. Reference numerals 510, 530, and 540 denote IPv4 packets, and reference numeral 550 denotes IPv6 packets, and an example of generating label information by simplifying a UDP header and an RTP header in each packet.

Reference numeral 510 denotes a media packet for the transmission of real-time media data, such as an on-demand video service. Reference numeral 560 denotes a UDP header and reference numeral 570 denotes an RTP header.

In the case of real-time media services, tens or hundreds of packets are typically transmitted every second per session. Due to the characteristics of a real-time media stream, headers of media packets transmitted have identically repeated fields for each packet transmitted during a session. Included. Fields 511, 512, 514, 515, 518, 519, and 520 are the same fields repeated every packet, and fields 513, 516 (or 533, 542, 552) and 517 are different for each packet. (Of course, in some cases, may be the same or overlap with other fields), a detailed description of these fields will be omitted since it may obscure the nature of the present invention.

The field to be noted is the NALH field at 520, which represents a NAL header, and as described in FIG. 2, the NAL header includes information indicating the importance or priority of the packet.

In the packet of reference number 530, fields 511, 512, 514, 515, 518, 519, and 520 that are identically repeated in the UDP header 560 and the RTP header 570 of the reference number 520 packet are collected and Inserted into the label information (flow label field) 531, the fields 513, 516, 517, which can vary from packet to packet, are arranged after the flow label field 531 (similar to label field 541).

In the packet 530, the Length field 532 overlaps with a Length field (not shown) included in the IP header. Therefore, the Length field 532 can be omitted. In addition, the TS field 534 is a time stamp. If the generation of the media data 535 (also similar to the media data 521, 535, 543, and 553) is periodic, the time stamp information can be known by calculation at the receiving end. Therefore, it can be omitted.

The reference numeral 540 packet indicates that the duplicated Length field 532 and the TS field 534 that can be calculated by the receiving side are omitted from the reference number 530 packet.

The reference number 550 packet illustrates an IPv6 packet. In the IPv6 header 551, there is a 24-bit flow label field. By using this field, the MAL information of the present invention can be included in the IPv6 header. .

When using the existing non-simplified header, the receiving side should parse all the fields. However, when the header is simplified as shown in FIG. 5, the fields corresponding to the flow labels do not need to be parsed every time.

The MAL information defined in the present invention has been described so far. Using such MAL information, it is possible to provide a service that guarantees QoS by class and QoS by flow using abstracted importance or priority without understanding media stream.

 In MPEG technology, a network entity that understands the importance or priority information of media and performs the forwarding using the media is called a media aware network element (MANE). Hereinafter, description will be made using the term “MANE”.

Hereinafter, the operation of the network entity, that is, MANE according to the present invention will be described.

For example, a network entity that forwards a received media packet, such as a router, a media access control (MAC) layer of IEEE 802 series, and a broadcast multicast service center (BMSC) of 3GPP, may use media identifier information included in MAL information. As a result, it can operate as a MANA (Media Aware Network Element) that can adaptively forward the packet according to the importance of the packet. For example, in a router using a DiffServ (Differentiated Service) routing method, if a data exceeds the buffer, the low priority packet is discarded. To this end, the media identifier value of the MAL information is checked.

In the case of a class-specific QoS scheme, the network entity adaptively processes a packet using importance information included in an IP header, that is, a media identifier value, regardless of which service the received packet belongs to. For example, if a media delimiter value of an audio packet is 11, a base layer video packet media delimiter value is 10, a media delimiter value of an advanced 1 layer video packet is 01, and a media delimiter value of an advanced 2 layer video packet is 00. When the network entity needs to discard any one of the packets due to network condition or overflow of the router buffer, the network entity discards the packet according to the media identifier value. That is, packets are discarded in the order of the high layer 2 video packet, the high layer 1 video packet, the base layer video packet, and finally the audio packet. For example, in the IEEE 802.11e standard, a packet is put in a queue determined according to importance information written in an IP header. Normally, priority is set in four steps, and there may be a difference in the method of handling the packet loss and the speed of the packet leaving the queue for each queue.

In the flow-based QoS scheme, a label value, which is a media identifier, is identified and QoS (bit rate, loss rate, delay, etc.) is supported by using a predetermined resource according to the label value. The determination of the predetermined resource may be determined according to a resource corresponding to the corresponding label by searching a resource reservation table stored in advance for each stream in the corresponding network entity. For example, if the QoS for the audio stream is set to Unsolicited Guaranteed Service (UGS) in IEEE 802.16, a predetermined QoS requirement is guaranteed accordingly. Therefore, the resource reservation table is stored in the network entity until the corresponding service ends. That is, when a packet is received from the transmitter, the label of the packet is checked, the QoS requirement of the stream of the label is searched in the resource reservation table, and a service is provided according to the resource accordingly.

6 is a diagram illustrating a configuration of a network entity device according to a preferred embodiment of the present invention.

When the forwarding policy decision unit 609 of the MANE 600 receives the packet from the transmitting side (606), it adaptively forwards the packet according to the forwarding policy (610). The forwarding policy depends on the media identifier value included in the MAL information of the received packet.

When the MANE 600 supports QoS for each service class, the MANE 600 checks the class of the media identifier value of the corresponding packet and determines whether to forward the corresponding packet accordingly. On the other hand, if the MANE 600 supports QoS per flow (i.e., stream), the label value is checked, and the resource allocated to the corresponding label stored in the resource reservation table 602 is checked (query-605). In operation 710, the server determines the available resource information of the available resource determination unit 604 (query-608, receives the inquiry result-607), and determines a forwarding policy in the available resources to forward the packet (710). .

Hereinafter, the operation of the receiving side according to an embodiment of the present invention will be briefly described.

7 is a diagram illustrating a receiving side apparatus according to a preferred embodiment of the present invention.

The receiving side equipment illustrated by FIG. 7 may be, for example, a user equipment.

The receiving side apparatus 700 includes a decoder 702 for each stream. The receiving device 700 also has a receiver 72 for receiving signals and a controller 704 for controlling the decoder 702. The decoder 700 secures as many buffers (not shown) as necessary.

If the packet received by the receiver 702 includes a label, the controller 706 may check the label and identify a decoder suitable for the packet. Also, if the packet received by the receiver 702 does not have a label, the controller 706 may read a TCP or UDP header to identify a decoder for decoding the media packet.

It should be noted that the flow chart of the configuration, operation or signal illustrated in FIGS. 3 to 7 is not intended to limit the scope of the present invention. That is, the configurations and operations described with reference to FIGS. 3 to 7 merely illustrate configurations that operate in the apparatus, and do not necessarily limit the implementation to be performed by all the processes or to be performed separately.

The above-described operations can be realized by providing a memory device storing the corresponding program code to any component in a network entity device such as a transmitting device, a receiving device or a MANE. That is, a component of a network entity device such as a sender device, a receiver device, or a MANE may be implemented by a processor or a central processing unit (CPU) that reads and executes program codes stored in a memory device.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

Claims (6)

In the method for the broadcast transmission device to receive a data packet,
Receiving a data packet,
Decoding the data packet;
The data packet includes a header and media data,
The header includes classifier information for per-class QoS and label information for per-flow QoS.
The delimiter information provides a QoS class related to the transmission priority of the data packet,
The label information indicates an identifier of a flow to which the data packet belongs, the flow is a data stream to which network resources are reserved;
The generation of the delimiter information and the label information is performed in a layer between an upper protocol layer that provides the media data and a lower protocol layer that is a network layer, and the layer abstracts information related to the media data provided by the upper protocol layer. Providing a function for delivering to the lower protocol layer. The method of claim 1,
The data packet includes bit rate information for the flow. The method of claim 1,
The data packet comprises buffer status information. In the broadcast receiving device for receiving a data packet,
A processor; And
A receiver for receiving a data packet under control of the processor,
The data packet includes a header and media data,
The header includes classifier information for per-class QoS and label information for per-flow QoS.
The delimiter information provides a QoS class related to the transmission priority of the data packet,
The label information is used to identify a flow to which the data packet belongs, the flow is a data stream to which network resources are reserved;
The generation of the delimiter information and the label information is performed in a layer between an upper protocol layer that provides the media data and a lower protocol layer that is a network layer, and the layer abstracts information related to the media data provided by the upper protocol layer. And providing a function for delivering to the lower protocol layer. The method of claim 4, wherein
And the data packet includes bit rate information for the flow. The method of claim 4, wherein
And the data packet includes buffer status information.

Images