WO2015194904A1

WO2015194904A1 - Method for compressing transmission packet in ip-based broadcast network

Info

Publication number: WO2015194904A1
Application number: PCT/KR2015/006236
Authority: WO
Inventors: 황성희; 양현구; 금지은
Original assignee: 삼성전자 주식회사
Priority date: 2014-06-20
Filing date: 2015-06-19
Publication date: 2015-12-23

Abstract

The present disclosure relates to a broadcasting method of a transmission apparatus in an IP-based broadcast network, the method comprising: an operation of generating an MPEG media transport protocol (MMTP) packet using a media processing unit (MPU) for a service; an operation of determining an IP session identifier for identifying an IP session for the service, and generating an IP packet using the MMTP packet and the IP session identifier; and an operation of transmitting the generated IP packet in a radio frequency (RF) channel, wherein the IP session identifier maps a combination of a source IP address, a destination IP address and a destination port for the IP packet, and at least one of the IP session identifier, the source IP address, the destination IP address and the destination port is transferred through a first layer signaling.

Description

Transport Packet Compression in IP-based Broadcasting Networks

The present disclosure relates to a method and apparatus for transmitting and receiving data in an IP-based broadcast communication network, and to a method and apparatus for compressing a transmitted IP packet.

Recently, an internet protocol (IP) based broadcast communication system in which communication through a broadband network and communication through a radio frequency (RF) has been converged has been designed and constructed.

In today's broadcast communication systems, data congestion over the network increases as the propensity for high-quality content consumption increases and high-capacity content such as high definition (HD) and ultra high definition (UHD) contents increases. Data congestion is getting deeper.

Accordingly, it is necessary to efficiently design transmission data in order to efficiently transmit data in a broadcast communication network.

The present disclosure proposes a scheme for efficiently designing transmission data in an IP-based broadcast communication network.

The present disclosure proposes a technique for efficiently using an IP packet transmitted on a broadcast communication protocol.

In addition, the present disclosure proposes a concrete layer signaling method of a broadcast communication protocol.

In addition, the present disclosure proposes an operation of a client receiving layer signaling in an IP-based broadcast communication network.

In addition, the present disclosure proposes a configuration of a compressed IP packet to be transmitted in an IP-based broadcast communication network.

The present disclosure provides a broadcasting method of a transmitting device in an IP-based broadcasting network, the method comprising: generating an MPEG media transport protocol (MMTP) packet using a media processing unit (MPU) for a service; Determining an IP session identifier identifying an IP session for the service, and generating an IP packet using the MMTP packet and the IP session identifier; And transmitting the generated IP packet in a radio frequency (RF) channel, wherein the IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet. The at least one of the IP session identifier, the source IP address, the destination IP address, and the destination port is transmitted through first layer signaling.

The present disclosure also provides a method for receiving a broadcast of a client in an IP-based broadcast network, the method comprising: receiving an RF channel for a service and decoding a physical layer pipe (PLP) of the RF channel; Obtaining an IP session identifier by parsing a first layer signal included in the PLP; Obtaining an IP packet corresponding to the service from the PLP using the IP session identifier; And depacketizing the IP packet to obtain a MPEG media transport protocol (MMTP) packet, and to obtain a Media Processing Unit (MPU) from the MMTP packet, wherein the IP session identifier is a source for the IP packet. An identifier for mapping a combination of an IP address, a destination IP address, and a destination port, wherein at least one of the source IP address, the destination IP address, and the destination port is received through the first layer signaling. Suggest a method.

The present disclosure also provides an IP session identifier for generating a MPEG media transport protocol (MMTP) packet using a Media Processing Unit (MPU) for a service in a transmitting device in an IP-based broadcasting network, and identifying an IP session for the service. A controller configured to determine a value and generate an IP packet using the MMTP packet and the IP session identifier; And a transceiver configured to transmit the generated IP packet in a radio frequency (RF) channel, wherein the IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet. And at least one of the IP session identifier, the source IP address, the destination IP address, and the destination port is transmitted through first layer signaling.

In addition, the present disclosure provides a client device in an IP-based broadcasting network, comprising: a transceiver configured to receive an RF channel for a service; And decoding a physical layer pipe (PLP) of the RF channel, parsing a first layer signal included in the PLP to obtain an IP session identifier, and using the IP session identifier, an IP corresponding to the service from the PLP. And a controller for acquiring a packet, depacketizing the IP packet to obtain a MPEG media transport protocol (MMTP) packet, and obtaining a media processing unit (MPU) from the MMTP packet, wherein the IP session identifier is the IP. An identifier that maps a combination of a source IP address, a destination IP address, and a destination port for a packet, wherein at least one of the source IP address, destination IP address, and destination port is received through the first layer signaling A client device is proposed.

According to the present disclosure, the broadcast transmission apparatus of the present disclosure does not need to transmit a UDP header and an IP header having a fixed size for every packet, thereby compressing the transmitted IP packet, and as a result, the size of the IP packet is reduced and used. The efficiency of the transmission resources can be increased.

1 illustrates a protocol stack according to the present disclosure that may be applied to an ATSC 3.0 system;

2A, 2B and 2C are diagrams illustrating the concept of a compression method of an IP packet of the present disclosure;

3 illustrates, in terms of RF channel, L2 signaling transmitted on one RF channel in RF broadcasting;

4 is a diagram illustrating a broadcast reception method of a client in a first case according to an embodiment of the present disclosure;

5 is a diagram illustrating a broadcast reception method of a client in a second case according to an embodiment of the present disclosure;

6 is a diagram illustrating a broadcast transmission method of a broadcast transmission device according to an embodiment of the present disclosure;

7 illustrates a configuration of a client device according to one embodiment of the present disclosure;

8 is a diagram illustrating a configuration of a transmitting apparatus according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description will be omitted. The terms to be described below are terms defined in consideration of functions in the present disclosure, and may be changed according to a user's or operator's intention or custom. Therefore, the definition should be made based on the contents throughout the specification.

Prior to the detailed description of the present disclosure, examples of the meanings that can be interpreted for several terms used herein are given. However, it should be noted that the present invention is not limited to the example of interpretation given below.

The broadcast transmission device is a subject that communicates with a client, and may also be referred to as a transmission device or a server.

A client is an entity that communicates with a broadcast transmitting device, and includes a TV, a user equipment, a mobile station (MS), a mobile equipment (ME), a device, a terminal, and the like. It may also be referred to as.

In the present disclosure, the term 'compressed' does not mean only when an algorithm for compressing a packet is applied, but also refers to a case where the length of a packet is shortened as a result of one or more processing.

1 is a diagram illustrating a protocol stack according to the present disclosure that can be applied to an ATSC 3.0 system.

The Advanced Television Systems Committee (ATSC) 3.0 system is a standard system for digital television transmission over terrestrial, cable, and satellite networks.

The MPU 100, which is a basic transmission unit constituting broadcast content, may be, for example, an ISO base media file format (ISOBMFF). The MPU 100 may be configured in an MMTP packet to be processed in an MPEG media transport (MMT) payload format and transmitted to the MMTP protocol (MMT Protocol) 102. Optionally, in the configuration process for the MMTP, AL-FEC (application layer forward error correction) 104 encoding may be further performed on the processed MPU.

The MMTP packet may be configured as a UDP packet 106 by adding a User Datagram Protocol (UDP) header, and the configured UDP packet may be configured as an IP packet 108 by adding an IP header.

The IP packet 108 configured as described above may be RF broadcasted through the layer 2 (L2) 110 and the physical layer (PHY) 116. The layer 2 may include a service signal (hereinafter referred to as an 'L2 signal') 112 including an IP session identifier, IP session information, and the like, and AV synchronization information 114 that may be used for content display.

Arrow 120 illustrates the protocol stack of the transmit end being RF broadcast. Meanwhile, the protocol stack of the transmitting end broadcasted through the broadband is illustrated by arrow 130. In addition to the MPU, the broadcast content broadcast through broadband may further include a Dynamic Adaptive Streaming over HTTP (DASH) Media Presentation Description (MPD) 114.

Tables 1 to 3 illustrate the structures of the UDP header and the IP header.

Table 1

TABLE 2

TABLE 3

Table 1 shows the structure of the UDP header, Table 2 shows the structure of the IP header in the case of IPv4 (IP version 4), and Table 3 illustrates the structure of the IP header in the case of IPv6 (IP version 6). Referring to Tables 1 to 3, the UDP header has a size of 8 bytes, and the IP header has a size of 20 bytes (IPv4) or 40 bytes (IPv6).

For example, when content having a 10,000 byte size is RF broadcasted, if the 10,000 byte content is transmitted in a unit MMTP packet of 1,000 bytes, 10 MMTP packets are transmitted. At this time, the 10 MMTP packets generated from the content will have the same source IP address, destination IP address, and destination port.

Therefore, when the size of the content is large, the space of the UDP header and the IP header included in the plurality of MMTP packets is overlapped to include the same information (source IP address, destination IP address, and destination port), which is This impedes the efficient use of resources.

Thus, the present disclosure does not include the UDP header and the IP header, but includes information for identifying an IP session (different by source IP address, destination IP address, and destination port). Suggest ways to do it. In this case, the information for identifying the IP session may be transmitted through signaling of another layer (hereinafter, referred to as a 'first layer') which is transmitted every predetermined period. As such, the broadcast transmission apparatus of the present disclosure does not have to transmit a UDP header and an IP header having a fixed size for every packet, thereby compressing the transmitted IP packet, and as a result, a transmission resource used by reducing the size of the IP packet. Can increase the efficiency.

2A, 2B and 2C are diagrams illustrating the concept of an IP packet compression method according to the present disclosure.

In FIG. 2A, the general IP packet 200 further includes a UDP header 204 having a size of 8 bytes and an IP header 202 having a size of 20 or 40 bytes in addition to the UDP payload 206. do.

In FIG. 2A, the compressed IP packet 210 according to the present disclosure does not include a conventional UDP header and an IP header. The compressed IP packet 210 may include an IP session identifier 212 in the header in addition to the UDP payload 206. The UDP payload 206 may be, for example, an MMTP packet. The IP session identifier 212 is information for identifying an IP session identified by a source IP address, a destination IP address, and a destination port. For example, the IP session identifier 212 may be expressed in size of 8 bits. That is, for IP packets of the same IP session, an IP session identifier of the same value is set in the header of the compressed IP packet.

The mapping information of the IP session and the IP session identifier, that is, the information of the IP session indicated by the IP session identifier (that is, the source IP address, the destination IP address, and the destination port), may be included in another layer (any layer, for example). For example, it may be transmitted through a Layer 2) signal. The information of the IP session may further include the same (ie, common) value of the information in the UDP / IP packet header for the IP packets, in addition to the source IP address, destination IP address, and destination port. Can be. If the same (i.e. common in IP packets) values are operated with one value across all IP sessions, the transmitter and the receiver mutually promise the same value (e.g. In case of sharing with each other or in advance, the same value may not be transmitted.

The first layer signal may be, for example, an L2 signal of an ATSC system, an upper layer signal (for example, a signal signal of Layer 3 such as an MMT layer or a service layer), or an L1 (Layer 1) signal such as a PHY layer. Can be. For example, the information on the IP session indicated by the IP session identifier may be generated in Layer 3 (L3) and transmitted through Layer 2 (L2) signaling. Layer 2 of the ATSC system may be referred to as a link layer as a layer that interfaces between an IP layer or more and a PHY layer.

Optionally, the compressed IP packet may further include at least one of checksum 214 information and length 216 information.

The checksum information 214 is a value used to check the integrity of the UDP payload 206, and by using the checksum, the broadcast reception device can check the integrity of the received data. Optionally, the checksum information may be reused as it is in the UDP header of a general IP packet, and may have a size of, for example, 16 bits.

Optionally, the checksum information may be omitted if the reliability of the data reproduced in the PHY layer is sufficiently guaranteed.

The length information 216 is length information used by the broadcast reception device to receive an IP packet. The length information may indicate the total length of the compressed IP packet or may indicate the length of the UDP payload 206. Optionally, the length information may be reused as it is in the UDP header of the general IP packet, and may have a size of, for example, 16 bits.

2B and 2C show examples 220 and 230 of compressed IP packets that do not include length information in accordance with the present disclosure.

When a compressed IP packet is applied to a baseband packet (BPB) as shown in FIGS. 2B and 2C, the

compressed IP packets

220 and 230 are compressed IP packets illustrated in FIG. 2A because the BBP packets include length information. The length information of may be omitted. That is, the length information may be included in the

headers

222 and 232 of the BBP packet transmitted in the compressed IP packet and transmitted.

If necessary, the general UDP header and other fields of the IP header included in Tables 1 to 3 may be optionally further included.

Hereinafter, the case where the identifier of the IP session and the information of the IP session are transmitted by L2 signaling will be described in detail.

3 is a diagram illustrating L2 signaling transmitted from one RF channel in RF broadcasting in terms of an RF channel.

In FIG. 3, it is assumed that the broadcast reception device (or client) has already completed an initial scan for RF broadcasting. Accordingly, it is assumed that the client already knows an electronic program guide (EPG), and that the client already knows an RF channel and a physical layer pipe (PLP) number mapped to the TV channel when the user selects a specific TV channel. . The TV channel corresponds to a logical channel. For example, service of TV channel i may be transmitted in PLP number j of RF channel k.

The service may correspond to a package of the MMT standard, correspond to a label, or correspond to one TV channel. The TV channel may correspond to a sub-stream of one PLP or BBP (baseband packet). One RF channel that is RF broadcast in an ATSC 3.0 system may have a band of 6 MHz, for example, and may include multiple logical channels (ie, services).

3A illustrates a first case in which an L2 signal is transmitted in each of a plurality of PLPs included in an RF channel.

One RF channel 300 includes two

PLPs

310 and 320. The

PLPs

310 and 320 may be allocated to TV broadcasters such as, for example, National Broadcasting Company (NBC), Columbia Broadcasting System (CBS), and American Broadcasting Company (ABC). The

PLPs

310 and 320 transmit at least one

service

312, 314, and 322, respectively, which may correspond to one TV channel. In this case, the two

PLPs

310 and 320 transmit

L2 signaling information

316 and 324, respectively. That is, one L2 signal may be transmitted per PLP.

3B illustrates a second case where an L2 signal for all of the multiple PLPs included in an RF channel is transmitted in any one PLP.

One RF channel 330 includes three

PLPs

340, 350, and 360. One PLP 340 of the

PLPs

340, 350, and 360 is used to transmit an L2 signal for all

PLPs

340, 350, and 360 included in the RF channel 330. That is, the specific PLP 340 transmits the L2 signal for all services included in the RF channel. The

PLPs

350 and 360 may transmit at least one

service

352, 354, and 362, respectively.

The

L2 signaling information

316, 324, and 342 illustrated in FIGS. 3A and 3B may be transmitted, including mapping information of the IP session identifier and the IP session, proposed in the present disclosure.

Table 4 illustrates L2 signaling information transmitted in the first case.

Table 4

In the first case, since the L2 signal is transmitted for each PLP, the L2 signal needs to identify IP session information for the entire service included in the PLP. In the case of the MMT standard, the service corresponds to a package. In Table 4, 'Number_of_package' describes the entire service.

As illustrated in Table 4, the L2 signaling information may include an 'IP session identifier' (IP session identifier) corresponding to the number of IP sessions.

Then, the client receiving the L2 signaling, what is the IP session mapped to the IP session identifier using 'Source IP Address', 'Destination IP Address' and 'Destination Port' included with the IP session identifier. You will know. The IP session identifier may be represented by, for example, 8 bits. In this case, 256 (= 2 ⁸ ) IP sessions may be identified using the IP session identifier. The number of bits for the representation of the IP session identifier may be changed according to implementation.

Optionally, the L2 signaling information may further include a 1-bit 'Compression Flag'. The Compression Flag is information transmitted to indicate whether a transport IP packet is a general IP packet or a compressed IP packet.

Optionally, the L2 signaling information may further include an 'IP version'. The IP version is information used to indicate whether the version of the transmitted IP packet is IPv4 or IPv6.

Table 5 illustrates L2 signaling information transmitted in the second case.

Table 5

In the second case, since one L2 signal is transmitted for each RF channel, the L2 signal needs to identify IP session information for all services included in all PLPs of the RF channel. The service is a concept corresponding to a package in the case of the MMT standard, and Table 5 indicates that 'Number of PLPs' describes all PLPs of the RF channel.

As illustrated in Table 5, the L2 signaling information may include an 'IP session Identifier' corresponding to the number of IP sessions.

Then, the client receiving the L2 signaling, using the 'Source IP Address', 'Destination IP Address' and 'Destination Port' included with the IP session identifier, what IP session is mapped to the IP session identifier? You will know. The number of bits for the representation of the IP session identifier may be changed according to implementation.

Optionally, the L2 signaling information may further include a 'Compression Flag' of 1 bit. The Compression Flag is information transmitted to indicate whether a transport IP packet is a general IP packet or a compressed IP packet.

Optionally, when the Compression Flag in Table 4 and Table 5 represents a compressed IP packet, the information of the IP session may be obtained by adding IP packets other than the source IP address, destination IP address, and destination port. It may further include a value (s) having the same (ie, common) value of the UDP / IP packet header information. However, if the same (i.e. common) values above operate at the same value across all IP sessions, and if the mutual appointment of the transmitter and receiver (e.g., promises a predetermined value by specification) is set, The common value may not be included.

4 is a diagram illustrating a broadcast reception method of a client in a first case according to an embodiment of the present disclosure.

The client tunes to the TV channel (if a TV channel is selected by the user) (400).

The client decodes 402 the PLP corresponding to the selected TV channel.

The client parses an L2 signal transmitted through the PLP to obtain IP session information for the selected TV channel (404). The IP session information may include a source IP address, a destination IP address, and a destination port of the IP session information mapped to the IP session identifier.

The client filters 406 the BBP substream corresponding to the selected TV channel in the decoded PLP. Specifically, the client may filter the BBP substream corresponding to the TV channel by checking a label described in the BBP header. Optionally, the client may perform the filtering using the IP session information (source IP address, destination IP address, destination port).

The client depacketizes the filtered BBP to obtain an IP packet or a UDP packet (408). Specifically, if the IP packet is compressed, the client grasps IP session information mapped to the IP session identifier, and de-compresses the IP packet or UDP packet using the IP session information. IP packets or UDP packets can be obtained. The client depackets the obtained IP packet or UDP packet to obtain an MMTP packet (410).

The client depackets the MMTP packet to obtain an MPU (412). Optionally, the client may further perform an operation for parsing an MMT signal.

The client de-capsulates the MPU to obtain content data (414).

The client performs an AV display using at least one of audio video (AV) synchronization information (AV sync information) transmitted through an L2 signal and the MMT signal and the acquired content data (416). The MMT signal may be, for example, MMT-Composition Information (MMT-CI).

5 is a diagram illustrating a broadcast reception method of a client in a second case according to an embodiment of the present disclosure.

The client tunes to the TV channel (if a TV channel is selected by the user) (500).

The client decodes a specific PLP included in the RF to obtain L2 signal information (502).

The client parses the L2 signal included in the specific PLP to obtain IP session information for the selected TV channel (504).

The client decodes 506 a PLP corresponding to the selected TV channel.

The client filters 508 the BBP substream corresponding to the selected TV channel in the decoded PLP. Specifically, the client may filter the BBP substream corresponding to the TV channel by checking a label described in the BBP header. Optionally, the client may perform the filtering using the IP session information (source IP address, destination IP address, destination port).

The client de-packetizes the filtered BBP to obtain an IP packet or a UDP packet (510). Specifically, when the IP packet is compressed, the client grasps IP session information mapped to the IP session identifier, and decompresses the IP packet or UDP packet using the IP session information to decompress the IP packet or UDP packet. Acquire. The client depackets the IP packet or the UDP packet to obtain an MMTP packet (512).

The client depackets the MMTP packet to obtain an MPU (514). Optionally, the client may further perform an operation for parsing an MMT signal.

The client de-capsulates the MPU to obtain content data (516).

The client performs an AV display using at least one of AV sync information transmitted through the L2 signal and the MMT signal and the acquired content data (518). The MMT signal may be, for example, MMT-CI.

6 is a diagram illustrating a broadcast transmission method of a broadcast transmission device according to an embodiment of the present disclosure.

The transmitting device generates an MMTP packet using at least one MPU for a particular service (eg, a TV channel) (600).

The transmitting device determines an IP session identifier for identifying an IP session for the service and includes the IP session identifier in the MMTP packet by including the IP session identifier (without including a conventional UDP header or IP header). Create 602. Optionally, the compressed packet may further include checksum information for integrity checking. Optionally, the compressed packet may further include length information indicating the length of the IP packet or the length of the MMTP packet.

The transmitting device may include the IP session identifier in the L2 signal (604).

The transmitting device generates a BBP substream using the IP packet or the UDP packet, generates a PLP by PHY layer encoding the L2 signal and the BBP substream, and broadcasts the generated PLP through an RF channel. (608). Optionally, information identifying whether the IP packet is compressed or not may be included in a BBP header included in the IP packet. For example, an uncompressed IP packet and a compressed IP packet may be distinguished according to a value (eg, 0 or 1) of a type field indicating a type of a payload of a BBP packet. In addition, the length information of the compressed IP packet may be indicated by the length information of the BBP header. In this case, the compressed IP packet may not include the length information.

7 is a diagram illustrating a configuration of a client device according to an embodiment of the present disclosure.

The client device of FIG. 7 is a device that performs the operations of the client described in this disclosure. For example, the client device may perform the broadcast reception method described with reference to FIGS. 4 and 5.

The client device may include a transceiver 730 that receives various signals broadcast from a broadcast transmission device, and a controller 700 that controls the transceiver 730 and processes the received various signals. Although shown as a separate module, the transceiver 730 and the control unit 700 may be implemented as a single device, of course.

The controller 700 may be understood to perform an operation of the client described in the present disclosure.

For example, the controller 700 may include various detailed modules 702 to 720 as follows, but may be implemented as a single module like the controller 700.

The RF tuner 702 performs RF tuning on the TV channel according to the TV channel input from the user.

The DLP decoder 704 may perform PLP decoding corresponding to the RF channel (first case) or decode a specific PLP for L2 signaling (second case).

The L2 signaling parser 712 parses the L2 signal from the decoded PLP to obtain IP session information for the TV channel, and the parsed L2 signal is a BBP substream filter 706 and an IP / UDP decompressor 710. ) Or the AV display unit 718.

The BBP substream filter 706 filters the BBP substream corresponding to the TV channel by checking a label of the BBP header. Optionally, the BBP substream filter 706 may use IP session information for the filtering operation.

The BBP depacketizer 708 depackets the filtered BBP to obtain an IP packet or a UDP packet. Optionally, the type field of the BBP header inside the IP packet determines whether a packet after BBP depacketization (ie, a depacketized BBP packet) is a normal (ie, uncompressed) IP packet or a compressed IP packet. Can be.

When the packet after depacketization of the BBP is a compressed IP packet, the IP / UDP decompressor 710 de-compresses the IP packet or the UDP packet to obtain an MMTP packet. In this case, the IP / UDP decompression unit 710 may use the IP session information mapped to the IP session identifier to decompress the IP packet or the UDP packet.

The MMTP depacketizer 714 depackets the MMTP packet to obtain an MPU.

The MMT signaling parser 720 parses the MMT signal and transmits the MMT signal to the AV display 718. The MMT signal may be, for example, MMT-Composition Information (MMT-CI).

The MPU decapsulation unit 716 de-capsulates the MPU to obtain content data.

The AV display unit 718 performs AV display using at least one of AV sync information transmitted through an L2 signal and the MMT signal and the acquired content data.

The transmitter of FIG. 8 is an apparatus that performs operations of the broadcast transmitter described in the present disclosure. For example, the transmitter may perform the broadcast transmission method described with reference to FIG. 6.

The transmitting device may include a transceiver 820 that broadcasts various signals to a client, and a controller 800 that controls the transceiver 820 and processes the various signals. Although illustrated as a separate module, the transceiver 820 and the controller 800 may be implemented as a single device.

The controller 800 may be understood to perform an operation of the broadcast transmission apparatus described in the present disclosure.

For example, the controller 800 may include various detailed modules 802 to 814 as follows. However, the controller 800 may be implemented as one module like the controller 800.

The MPU encapsulator 810 generates an MPU using content data corresponding to a specific TV channel.

The MMTP packetizer 808 generates an MMTP packet by using the generated MPU. Optionally, the MMT signal received from the MMT signaling generator 814 may be used to generate the MMTP packet. For example, the MMT signal may include MMT-CI.

The MMT signaling generator 814 may generate information such as MMT-CI and transmit the same to the MMT packetizer 808.

The L2 signaling generator 812 determines an IP session identifier for identifying an IP session for a specific service (eg, a TV channel), generates an L2 signal, and converts the IP session identifier into an IP / UDP compression unit ( 806 or to the PLP encoder 802.

The IP / UDP compression unit 806 generates the compressed IP / UDP packet by including the IP session identifier in the MMTP packet. Optionally, the compressed packet may further include checksum information for integrity checking. Optionally, the compressed packet may further include length information indicating the length of the IP packet or the length of the MMTP packet.

The BBP packetizer 804 generates a baseband packet (BBP) using the compressed IP / UDP packet. Optionally, the BBP packetizer 804 may set information distinguished from the general IP / UDP packet to indicate that the compressed IP / UDP packet is included in the type field included in the BBP header. In addition, the length information of the compressed IP / UDP packet may be indicated by the length information of the BBP header (length information included in the BBP header). When the length information of the compressed IP packet is indicated by the length information of the BBP header, the compressed IP packet may not include extra length information.

The PLP encoder 802 generates a PLP by PHY layer encoding the substream or L2 signal of the BBP.

The transceiver 820 broadcasts the generated PLP through an RF channel.

Although the present disclosure has been described mainly for transmitting IP session information to the L2 layer in IP compression, the IP session information may be transmitted in a higher layer such as MMT signaling and service signaling in addition to the L2 layer. It may be transmitted through PHY layer signaling or other signaling. In addition, when the IP session identifier and the corresponding IP session information are promised to each other between the transmitter and the receiver (for example, the IP session information and IP session identifier mapping information are provided as a specification, and the transmitter and the receiver operate according to the specification. In this case, the IP session information may not be actually transmitted.

1 to 8 illustrate the protocol stack configuration diagram, the compressed IP packet configuration diagram, the RF channel configuration diagram, the client broadcast reception method example, the broadcast transmission device example, the client device configuration diagram and the transmission It should be noted that the device configuration diagram is not intended to limit the scope of the present disclosure. That is, all the layers, PLPs, components, or steps of operation described in FIGS. 1 to 8 should not be interpreted as essential components for the implementation of the invention, and include only some of the components to impair the essence of the invention. It can be implemented within a range that does not.

The operations described above can be realized by providing the memory device storing the corresponding program code with any component in the server, the transmitting device, and the client device of the communication system. That is, the control unit of the server, the transmitting device, and the client device may execute the above-described operations by reading and executing the program code stored in the memory device by the processor or the central processing unit (CPU).

The various components of the server, the transmitting device, the client device, modules, etc. described herein are hardware circuits, for example complementary metal oxide semiconductor based logic circuits, firmware ) And hardware circuitry such as a combination of software and / or hardware and firmware and / or software embedded in a machine-readable medium. As an example, various electrical structures and methods may be implemented using transistors, logic gates, and electrical circuits such as application specific semiconductors.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described. However, various modifications may be possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure 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

A broadcasting method of a transmitting device in an IP (Internet protocol) based broadcasting network,

Generating an MPEG media transport protocol (MMTP) packet using a Media Processing Unit (MPU) for the service;

Determining an IP session identifier identifying an IP session for the service, and generating an IP packet using the MMTP packet and the IP session identifier; And

Including transmitting the generated IP packet in a radio frequency (RF) channel,

The IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet.

At least one of the IP session identifier, the source IP address, the destination IP address, and the destination port is transmitted via first layer signaling.
The method of claim 1,

The first layer signaling further includes at least one of length information indicating a length of the IP packet or the MMTP packet and checksum information for checking the integrity of the IP packet.
The method of claim 1,

Wherein the first layer signaling is Layer 2 (L2) signaling of an Advanced Television Systems Committee (ATSC) system.
The method of claim 1,

The first layer signaling is transmitted for each physical layer pipe (PLP) included in the RF channel.
The method of claim 1,

The first layer signaling is transmitted through one PLP of physical layer pipes (PLPs) included in the RF channel.
In the broadcast receiving method of a client in an IP (Internet protocol) -based broadcasting network,

Receiving an RF channel for a service and decoding a physical layer pipe (PLP) of the RF channel;

Obtaining an IP session identifier by parsing a first layer signal included in the PLP;

Obtaining an IP packet corresponding to the service from the PLP using the IP session identifier; And

Depacketizing the IP packet to obtain a MPEG media transport protocol (MMTP) packet, and obtaining an MPU (Media Processing Unit) from the MMTP packet,

The IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet.

At least one of the source IP address, the destination IP address and the destination port is received via the first layer signaling.
The method of claim 6,

The first layer signaling further includes at least one of length information indicating a length of the IP packet or the MMTP packet and checksum information for checking the integrity of the IP packet.
The method of claim 6,

Wherein the first layer signaling is Layer 2 (L2) signaling of an Advanced Television Systems Committee (ATSC) system.
The method of claim 6,

The first layer signaling is received for each PLP included in the RF channel.
The method of claim 6,

The first layer signaling is received through one PLP among the PLPs included in the RF channel.
In a transmission apparatus in an IP (Internet protocol) based broadcasting network,

Create a MPEG media transport protocol (MMTP) packet using a Media Processing Unit (MPU) for a service, determine an IP session identifier that identifies an IP session for the service, and use the MMTP packet and the IP session identifier A control unit for generating an IP packet; And

It includes a transceiver for transmitting the generated IP packet in a radio frequency (RF) channel,

The IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet.

And at least one of the IP session identifier, the source IP address, the destination IP address, and the destination port is transmitted via first layer signaling.
The method of claim 11,

The first layer signaling further includes at least one of length information indicating a length of the IP packet or the MMTP packet and checksum information for checking the integrity of the IP packet.
The method of claim 11,

And the first layer signaling is Layer 2 (L2) signaling of an Advanced Television Systems Committee (ATSC) system.
The method of claim 11,

And the first layer signaling is transmitted for each physical layer pipe (PLP) included in the RF channel.
The method of claim 11,

And the first layer signaling is transmitted through one PLP among physical layer pipes (PLPs) included in the RF channel.
A client device in an IP (Internet protocol) based broadcasting network,

A transceiver for receiving an RF channel for a service; And

Decode a physical layer pipe (PLP) of the RF channel, parse a first layer signal included in the PLP to obtain an IP session identifier, and use the IP session identifier to obtain an IP packet corresponding to the service from the PLP. A control unit for acquiring a packet, depacketizing the IP packet to obtain a MPEG media transport protocol (MMTP) packet, and obtaining a media processing unit (MPU) from the MMTP packet,

The IP session identifier is an identifier that maps a combination of a source IP address, a destination IP address, and a destination port for the IP packet,

And at least one of the source IP address, the destination IP address, and the destination port is received via the first layer signaling.
The method of claim 16,

The first layer signaling further includes at least one of length information indicating a length of the IP packet or the MMTP packet and checksum information for checking the integrity of the IP packet.
The method of claim 16,

And the first layer signaling is Layer 2 (L2) signaling of an Advanced Television Systems Committee (ATSC) system.
The method of claim 16,

Wherein the first layer signaling is received for each PLP included in the RF channel.
The method of claim 16,

And the first layer signaling is received through one PLP among PLPs included in the RF channel.