KR102272335B1 - Method and server for providing contents through udp based multicast and user device - Google Patents

Abstract

A method for providing content by UDP-based multicast from a server includes receiving a first stream ID including a first channel ID from a first terminal, combining the first channel ID and the first content ID to provide a second stream ID generating a second stream ID, transmitting the second stream ID to the multicast network, generating a third stream ID by combining the first channel ID and the second content ID, and transmitting the third stream ID to the multicast network including the steps of

Description

Method of providing content through UDP-based multicast, server, and user terminal {METHOD AND SERVER FOR PROVIDING CONTENTS THROUGH UDP BASED MULTICAST AND USER DEVICE}

The present invention relates to a method for providing content through UDP-based multicast, a server, and a user terminal.

Web service refers to a technology that integrates and connects different types of information systems to easily call and use application software existing in other systems through the Internet as if it were one's own. When a web service environment is established, it is possible to receive web services with consistent content anytime, anywhere, on any device without the need to install necessary software for each terminal. Disclosed is a web service management system.

Recently, a new protocol called HTTP2 has been designated as standard, and the effect of reducing web page loading time through server push is expected. However, since the HTTP2 protocol allocates and manages a unique stream ID for each web resource (eg, HTML file, image, etc.) requested by the client, it is a multicast application that transmits the same packet to multiple clients at the same time. There is a drawback to this difficulty. For example, in the case of HTTP streaming, even the same web resource (video chunk) cannot be sent simultaneously through multicast because the stream ID requested by each client is different.

In addition, QUIC (Quick UDP Internet Connection), a new UDP-based transport protocol that provides TCP-level reliability and security, has recently been developed, and is expected to be utilized to provide faster web services. Existing web services have used TCP as a transport protocol, but while TCP provides reliable transmission, it has become an obstacle to improving web response speed and performance of multimedia services. However, as UDP-based transport protocols such as QUIC can be used for web services, it is expected that new web services based on multicast will appear in the future.

Web media service transmission using multicast reduces network congestion due to media services that generate large-scale traffic, such as existing HTTP live streaming, and reduces investment costs to improve wireless network transmission efficiency. We aim to improve the quality of media services such as shortening of response time and synchronization between clients by using UDP-based multicast transmission of web media services. We want to extend the business model by applying it to new services such as server push in the HTTP2 and SPDY-based web service environment. However, the technical problems to be achieved by the present embodiment are not limited to the technical problems described above, and other technical problems may exist.

As a technical means for achieving the above-described technical problem, an embodiment of the present invention includes the steps of receiving a first stream ID including a first channel ID from a first terminal, the first channel ID and the first content ID combining to generate a second stream ID; transmitting the second stream ID to a multicast network; generating a third stream ID by combining the first channel ID and a second content ID; It is possible to provide a method for providing content by multicast, including transmitting a stream ID to the multicast network.

In addition, another embodiment of the present invention is a receiver for receiving a first stream ID including a first channel ID from a first terminal, combining the first channel ID and the first content ID to generate a second stream ID A stream ID generating unit and a transmitting unit transmitting the second stream ID to a multicast network, wherein the stream ID generating unit generates a third stream ID by combining the first channel ID and the second content ID, The transmitting unit may provide a server that provides content through multicast that transmits the third stream ID to the multicast network.

In addition, another embodiment of the present invention provides a stream ID transmitter for transmitting a first stream ID including a first channel ID to a server, a session manager for opening a session of the first channel ID, and IGMP to a multicast network A message transmitting unit for transmitting a message, a stream ID receiving unit receiving a second stream ID in which the first channel ID and the first content ID are combined from a multicast network, and extracting the first channel ID of the second stream ID an extraction unit, a verification unit confirming whether the first channel ID extracted from the second stream ID is the same as the first channel ID included in the first stream ID; It is possible to provide a user terminal including a data receiver for receiving data through the first content ID included in the stream ID.

The above-described problem solving means are merely exemplary, and should not be construed as limiting the present invention. In addition to the exemplary embodiments described above, there may be additional embodiments described in the drawings and detailed description.

According to any one of the above-described problem solving means of the present invention, network congestion due to media services that generate large-scale traffic such as existing HTTP live streaming by transmitting web media services using multicast is reduced and investment costs are reduced to reduce the wireless network Transmission efficiency can be improved. With UDP-based multicast transmission of web media service, it is possible to improve media service quality such as shortening of response time and synchronization between clients. In a web service environment based on HTTP2 and SPDY, the business model can be extended by applying it to new services such as server push.

1 is a block diagram of a content providing system according to an embodiment of the present invention.
2 is a configuration diagram of a server according to an embodiment of the present invention.
3 is a diagram for explaining a process of providing content through UDP-based multicast in a server according to an embodiment of the present invention.
4 is a block diagram of a user terminal according to an embodiment of the present invention.
5 is a flowchart illustrating a process of receiving data through multicast in a user terminal according to an embodiment of the present invention.
6 is a flowchart illustrating a content providing method according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art can easily implement them. However, the present invention may be embodied in many different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, when a part is "connected" with another part, this includes not only the case of being "directly connected" but also the case of being "electrically connected" with another element interposed therebetween. . Also, when a part "includes" a component, it means that other components may be further included, rather than excluding other components, unless otherwise stated, and one or more other features However, it is to be understood that the existence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded in advance.

In this specification, a "part" includes a unit realized by hardware, a unit realized by software, and a unit realized using both. In addition, one unit may be implemented using two or more hardware, and two or more units may be implemented by one hardware.

Some of the operations or functions described as being performed by the terminal or device in the present specification may be instead performed by a server connected to the terminal or device. Similarly, some of the operations or functions described as being performed by the server may also be performed in a terminal or device connected to the server.

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

1 is a block diagram of a content providing system according to an embodiment of the present invention. Referring to FIG. 1 , the content providing system 1 may include a server 110 and a plurality of user terminals 120 . The server 110 and the plurality of user terminals 120 shown in FIG. 1 exemplarily show components that can be controlled by the content providing system 1 .

Each component of the content providing system 1 of FIG. 1 is generally connected through a network. For example, as shown in FIG. 1 , the plurality of user terminals 120 may be connected to the server 110 through a network.

The network refers to a connection structure in which information exchange is possible between each node, such as terminals and servers, and an example of such a network is Wi-Fi, Bluetooth, Internet, and Local Area (LAN). Network), Wireless Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), 3G, 4G, LTE, and the like.

In an embodiment, the server 110 may receive the first stream ID including the first channel ID from the user terminal 120 . The first stream ID may include, for example, a first channel ID in a predetermined bit (eg, 10 bits) of a 31-bit stream ID. Thereafter, the server 110 generates a second stream ID by combining the first channel ID and the first content ID, and multicasts the generated second stream ID and a web resource (video chunk) corresponding to the first channel. can be transmitted over the network. Thereafter, the server 110 generates a third stream ID by combining the first channel ID and the second content ID, and multi-processes the generated third stream ID and the next web resource (video chunk) corresponding to the first channel. It can be transmitted over a cast network. The second stream ID and the third stream ID include the first channel ID in a preset bit (for example, 10 bit) among a total of 31-bit stream ID, and a second stream ID in a bit different from the preset bit (for example, 21 bit). It may include one content ID or a second content ID. For example, only an odd number or an even number may be used as the content ID, and the second content ID may be a value obtained by increasing the first content ID by an odd number.

In another embodiment, the server 110 may receive the fourth stream ID including the second channel ID from the user terminal 120 . For example, the server 110 generates a fifth stream ID by combining the second channel ID and the third content ID, and multi-processes the generated fifth stream ID and a web resource (video chunk) corresponding to the second channel. It can be transmitted over a cast network. In addition, the server 110 generates a sixth stream ID by combining the second channel ID and the fourth content ID, and multicasts the generated sixth stream ID and the next web resource (video chunk) corresponding to the second channel. can be transmitted over the network. The fifth stream ID and the sixth stream ID include the second channel ID in a preset bit (eg, 10bit) among a total of 31-bit stream ID, and a second channel ID in a bit different from the preset bit (eg, 21bit). It may include a third content ID or a fourth content ID. For example, only an odd number or an even number may be used as the content ID, and the fourth content ID may be a value obtained by increasing the third content ID by an odd number.

In this case, the server 110 may transmit the generated stream ID and the web resource (video chunk) of the corresponding channel to the multicast network through a specific UDP port such as 5001.

The user terminal 120 may transmit (request) the first stream ID including the first channel ID to the server 110 . For example, when the user terminal 120 requests viewing of the first channel, the server 110 sends a first channel ID preset to 10 bits among a total of 31 bits first stream ID and a first stream ID including 0 of 21 bits. ) can be transmitted.

Thereafter, the user terminal 120 may transmit an IGMP message including a command to open a session of the first channel ID and join the multicast network.

In an embodiment (when the first channel is requested), the user terminal 120 receives a web resource (video) corresponding to the second stream ID and the first channel in which the first channel ID and the first content ID are combined from the multicast network. chunk) can be received. The user terminal 120 extracts the first channel ID of the second stream ID and checks whether it is the same as the first channel ID included in the requested first stream ID. As a result of the check, if the first channel ID is the same, A web resource (video chunk) corresponding to the second stream ID may be received. Thereafter, the user terminal 120 may receive a third stream ID in which the first channel ID and the second content ID are combined from the multicast network. The user terminal 120 extracts the first channel ID of the third stream ID and checks whether it is the same as the first channel ID included in the requested first stream ID, and as a result of the check, if the first channel ID is the same, A web resource (video chunk) corresponding to the third stream ID may be received. Here, the second content ID may be a value increased by an odd number than the first content ID.

In another embodiment (when the second channel is requested), when the user terminal 120 transmits (requests) the fourth stream ID including the second channel ID to the server, the user terminal 120 receives the request from the multicast network. A fifth stream ID in which the second channel ID and the third content ID are combined and a web resource (video chunk) corresponding to the second channel may be received. The user terminal 120 extracts the second channel ID of the fifth stream ID and checks whether it is the same as the second channel ID included in the fourth stream ID requested by the user terminal 120. As a result of the check, if the second channel ID is the same, A web resource (video chunk) corresponding to the fifth stream ID may be received. Thereafter, the user terminal 120 may receive a sixth stream ID in which the second channel ID and the fourth content ID are combined from the multicast network. The user terminal 120 extracts the second channel ID of the sixth stream ID and checks whether it is the same as the second channel ID included in the fourth stream ID requested by the user terminal 120. As a result of the check, if the second channel ID is the same, A web resource (video chunk) corresponding to the sixth stream ID may be received. Here, the fourth content ID may be a value increased by an odd number than the third content ID.

2 is a configuration diagram of a server according to an embodiment of the present invention. Referring to FIG. 2 , the server 110 may include a receiver 210 , a stream ID generator 220 , and a transmitter 230 . Here, the user terminal 120 will be referred to as the first terminal 120 .

The receiver 210 may receive the stream ID including the channel ID from the first terminal 120 . For example, the receiver 210 may receive the first stream ID including the first channel ID from the first terminal 120 . Also, the receiver 210 may receive the fourth stream ID including the second channel ID from the first terminal 120 . In this case, the first stream ID may include the first channel ID in a preset bit (eg, 10 bits), and the fourth stream ID may include the second channel ID in a preset bit.

The stream ID generator 220 may generate a stream ID by combining the channel ID and the content ID. For example, the stream ID generator 220 may generate the second stream ID by combining the first channel ID and the first content ID. The second stream ID may include the first channel ID in a preset bit and the first content ID in a bit different from the preset bit. For example, the stream ID generating unit 220 may generate a second stream ID by combining a preset first channel ID of 10 bits and a first content ID of 21 bits in a stream ID of a total of 31 bits.

Also, the stream ID generator 220 may generate a third stream ID by combining the first channel ID and the second content ID. The second content ID may be a value obtained by increasing the first content ID by an odd number. For example, when the 10-bit first channel ID is “110101011” in binary, the generated 31-bit stream ID value may include a value between “1790967809 to 1795162111” in decimal.

Alternatively, the stream ID generator 220 may generate a stream ID by combining the second channel ID and the content ID. For example, the stream ID generator 220 may generate a fifth stream ID by combining the second channel ID and the third content ID. For example, the stream ID generation unit 220 may generate a fifth stream ID by combining a preset second channel ID of 10 bits and a third content ID of 21 bits in a stream ID of a total of 31 bits. Also, the stream ID generator 220 may generate a sixth stream ID by combining the second channel ID and the fourth content ID. Here, the fourth content ID may be a value obtained by increasing the third content ID by an odd number.

The transmitter 230 may transmit the stream ID generated by the server 110 and a web resource (video chunk) of the corresponding channel to the multicast network. For example, the transmission unit 230 generates the second stream ID, the third stream ID, the fifth stream ID, and the sixth stream ID generated by the stream ID generation unit 220 through a specific UDP port such as 5001, and each A web resource (video chunk) corresponding to a stream ID can be transmitted over a multicast network. In this case, in the case of HTTP, a Quick UDP Internet Connection (QUIC) protocol may be used for reliable transmission.

3 is a diagram for explaining a process of providing an HTTP-based web resource through UDP-based multicast in a server according to an embodiment of the present invention. Referring to FIG. 3 , the plurality of user terminals 310 and 311 may request a first channel 301 or a second channel 302 from the server 320 . For example, in the case of the first channel 301, if the URL is "XXX.com/playback?live_ch_1_1790967808", the first channel ID is " 1101010110". For another example, in the case of the second channel 302, when the URL is "XXX.com/playbkac?live_ch_2_2055208960", the second channel ID corresponds to the first 10 bits of "1111010100000000000000000000000" obtained by binarizing "2055208960" “1111010100”. In this way, the user terminals 310 and 311 may request the content of the corresponding channel from the server using the multicast service URL information received from the server, for example, described in the ".m3u8" file.

For example, the plurality of user terminals 310 and 311 may transmit a stream ID including the first channel ID 1101010110 to the server 320 . Also, the plurality of user terminals 310 and 311 may transmit a stream ID including the second channel ID 1111010100 to the server 320 . In this case, the plurality of user terminals 310 and 311 may transmit an IGMP message including a join command to the multicast network.

When the server 320 receives the stream ID including the channel ID from the plurality of user terminals 310 and 311, the server 320 generates a stream ID including the channel ID and the content ID and transmits the web resource to the multicast network. have. For example, the server 320 is a first stream ID (331, 1790967819) combining the first channel ID (330) 1101010110 and the first content ID, the first channel ID (330) 1101010110 combining the second content ID The second stream IDs 332 and 1790967821 and the third stream IDs 333 and 1790967823 obtained by combining 1101010110 which is the first channel ID 330 and the third content ID may be transmitted to the multicast network. As another example, the server 320 combines the second channel ID 340, 1111010100, and the first content ID, 4 stream IDs 341 and 2055209435, and the second channel ID 340, 1111010100, combining the second content ID. The fifth stream IDs 342 and 2055209437 may be transmitted to the multicast network. Here, the content ID generated by the server 320 may be an odd incremented value.

4 is a block diagram of a user terminal according to an embodiment of the present invention. Referring to FIG. 4 , a stream ID transmitter 410 , a session manager 420 , a message transmitter 430 , a stream ID receiver 440 , an extractor 450 , a checker 460 , and a data receiver 470 . ) may be included.

The stream ID transmitter 410 may transmit the stream ID including the channel ID to the server 110 . For example, the stream ID transmitter 410 may transmit the first stream ID including the first channel ID to the server 110 . Also, the stream ID transmitter 410 may transmit the fourth stream ID including the second channel ID to the server 110 . The first stream ID may include the first channel ID in preset bits, and the fourth stream ID may include the second channel ID in preset bits. For example, when the channel ID is preset to 10 bits among a total of 31 bits of the first stream ID or the fourth stream ID, the remaining 21 bits may be set to 0 and transmitted to the server 110 .

The session manager 420 may open a session of the first channel ID. Also, when the desired channel is changed, the session manager 420 may open a session of the second channel ID.

The message transmission unit 430 may transmit an IGMP message to the multicast network. For example, the message transmitter 430 may transmit an IGMP message including a join command to the multicast network.

The stream ID receiver 440 may receive the stream ID generated by the server 110 and the web resource of the corresponding channel from the multicast network. For example, the stream ID receiver 440 may receive a second stream ID in which the first channel ID and the first content ID are combined and a web resource of the corresponding channel. Also, the stream ID receiver 440 may receive a third stream ID in which the first channel ID and the second content ID are combined and a web resource of the corresponding channel from the multicast network. The second stream ID includes the first channel ID in a preset bit, the first content ID in a bit different from the preset bit, the third stream ID includes the first channel ID in a preset bit, The second content ID may be included in a bit different from the set bit.

When the desired channel is changed to the second channel, the stream ID receiver 440 may receive a fifth stream ID in which the second channel ID and the third content ID are combined and a web resource of the corresponding channel. Also, the stream ID receiver 440 may receive a sixth stream ID in which the second channel ID and the fourth content ID are combined and a web resource of the corresponding channel. The fifth stream ID includes the second channel ID in preset bits, the third content ID in bits different from the preset bits, the sixth stream ID includes the second channel ID in preset bits, The fourth content ID may be included in a bit different from the set bit.

The extractor 450 may extract the channel ID included in the stream ID received from the multicast network. For example, the extractor 450 may extract the first channel ID of the second stream ID through a masking operation, or may extract the second channel ID of the fifth stream ID.

The check unit 460 may check whether the extracted channel ID is the same as the channel ID transmitted (requested) from the user terminal 120 to the server 110 . For example, the checker 460 may check whether the first channel ID extracted from the second stream ID is the same as the first channel ID included in the requested first stream ID. Also, the check unit 460 may check whether the second channel ID extracted from the fifth stream ID is the same as the second channel ID included in the fourth stream ID requested by the checker 460 .

As a result of checking, when the channel IDs are the same, the data receiver 470 may receive a web resource corresponding to the stream ID received from the multicast network. For example, when the first channel ID is the same as a result of checking, the data receiver 470 may receive a web resource corresponding to the second stream ID. Also, the data receiver 470 may receive a web resource corresponding to the fifth stream ID.

That is, the check unit 460 may receive data by only checking whether the channel ID transmitted from the stream ID transmitter 410 and the channel ID received from the stream ID receiver 440 are the same.

5 is a flowchart illustrating a process of receiving data through multicast in a user terminal according to an embodiment of the present invention. Referring to FIG. 5 , when the user terminal 120 receives a stream ID from the server 110 ( S510 ), the user terminal 120 may perform a bit masking operation on the stream ID ( S520 ). The user terminal 120 may check whether the received stream ID is the multicast stream ID requested by the user terminal 120 (S530). For example, when it is confirmed that the stream ID received from the user terminal 120 is not the multicast stream ID (S531), the user terminal 120 may determine whether the corresponding stream ID is in an Open state or Reserved state. (S540). At this time, when the corresponding stream ID is not in the Open state or Reserved state (S541), the user terminal 120 discards the corresponding stream ID (S550), and when the corresponding stream ID is in the Open state or Reserved state (S542), A normal stream (push) may be received (S560). The server may periodically transmit a push promise frame to a multicast address to provide the server push service. In this case, the server may use the already provided stream ID for multicast as a Reference ID. The server may transmit push contents to the corresponding screen ID between push promise frames. After receiving the push promise frame, the terminal receiving the multicast service may receive the push content.

For another example, if it is confirmed that the stream ID received from the user terminal 120 is the multicast stream ID (S532), the user terminal 120 determines whether the corresponding multicast stream ID is in an Open state or Reserved state. Can be (S570). At this time, when the corresponding multicast stream ID is not in the Open state or Reserved state (S571), the user terminal 120 discards the corresponding multicast stream ID (S550), and the corresponding multicast stream ID is in the Open state or Reserved state In the case of (S572), a multicast stream may be received (S580).

In the above description, steps S510 to S580 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. In addition, some steps may be omitted as necessary, and the order between steps may be changed.

6 is a flowchart illustrating a content providing method according to an embodiment of the present invention. The method of providing content by UDP-based multicast performed by the server 110 according to the embodiment shown in FIG. 6 is processed in time series by the content providing system 1 according to the embodiment shown in FIG. includes steps. Therefore, even if omitted below, the content already described with respect to the content providing system 1 according to the embodiment shown in FIG. 1 is based on UDP performed by the server 110 according to the embodiment shown in FIG. 6 . This also applies to the method of providing content by multicast.

In step S610, the server 110 may receive the first stream ID including the first channel ID from the first terminal. The first stream ID may include the first channel ID in a preset bit. In step S620, the server 110 may generate a second stream ID by combining the first channel ID and the first content ID. The second stream ID may include the first channel ID in a preset bit and the first content ID in a bit different from the preset bit. In step S630, the server 110 may transmit the second stream ID and the corresponding web resource to the multicast network. In step S640, the server 110 may generate a third stream ID by combining the first channel ID and the second content ID. The second content ID may be an increased value of the first content ID. In step S650, the server 110 may transmit the third stream ID and the corresponding web resource to the multicast network.

Although not shown in FIG. 6 , the server 110 receives a fourth stream ID including a second channel ID from the first terminal, and generates a fifth stream ID by combining the second channel ID and the third content ID. transmitting the fifth stream ID and the corresponding web resource to the multicast network, generating a sixth stream ID by combining the second channel ID and the fourth content ID, and the sixth stream ID and the corresponding web transmitting the resource to the multicast network. The fourth content ID may be an increased value of the third content ID.

In the above description, steps S610 to S650 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. In addition, some steps may be omitted as necessary, and the order between steps may be changed.

The method of providing an HTTP-based web resource in a UDP-based multicast manner performed by the server 110 described through FIG. 6 includes a computer program stored in a medium executed by a computer or an instruction executable by the computer. It may also be implemented in the form of a recording medium. Computer-readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. Also, computer-readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism, and includes any information delivery media.

The above description of the present invention is for illustration, and those of ordinary skill in the art to which the present invention pertains can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be.

Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a dispersed form, and likewise components described as distributed may be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the above detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention. do.

110: server
120: user terminal
210: receiver
220: Stream ID generator
230: transmission unit
410: stream ID transmitter
420: session management unit
430: message transmission unit
440: Stream ID receiver
450: extraction unit
460: confirmation unit
470: data receiving unit

Claims (17)

A method for providing content by UDP-based multicast from a server, the method comprising:
receiving a first stream ID including a first channel ID from a first terminal;
generating a second stream ID by combining the first channel ID and the first content ID;
transmitting the second stream ID to a multicast network;
generating a third stream ID by combining the first channel ID and the second content ID; and
transmitting the third stream ID to the multicast network;
A method of providing content in multicast, comprising a.
The method of claim 1,
wherein the second content ID is an increased value of the first content ID.
The method of claim 1,
receiving a fourth stream ID including a second channel ID from the first terminal;
generating a fifth stream ID by combining the second channel ID and the third content ID;
transmitting the fifth stream ID to the multicast network;
generating a sixth stream ID by combining the second channel ID and the fourth content ID; and
transmitting the sixth stream ID to the multicast network;
A method of providing content by multicast further comprising a.
4. The method of claim 3,
wherein the fourth content ID is a value obtained by increasing the third content ID.
The method of claim 1,
The method for providing content by multicast, wherein the first stream ID includes the first channel ID in a predetermined bit.
The method of claim 1,
The method for providing content by multicast, wherein the second stream ID includes the first channel ID in a preset bit and the first content ID in a bit different from the preset bit.
A server that provides content through UDP-based multicast,
a receiver for receiving a first stream ID including a first channel ID from a first terminal;
a stream ID generator generating a second stream ID by combining the first channel ID and the first content ID; and
A transmitter for transmitting the second stream ID to a multicast network,
When the stream ID generating unit generates a third stream ID by combining the first channel ID and the second content ID,
The transmitting unit transmits the third stream ID to the multicast network.
8. The method of claim 7,
The second content ID is a value obtained by increasing the first content ID, the server providing content by multicast.
8. The method of claim 7,
In the receiver,
When receiving the fourth stream ID including the second channel ID from the first terminal,
The stream ID generation unit,
generating a fifth stream ID by combining the second channel ID and the third content ID;
The transmission unit,
Transmitting the fifth stream ID to the multicast network,
The stream ID generation unit,
generating a sixth stream ID by combining the second channel ID and the fourth content ID;
The transmission unit,
The server for providing content by multicast, which transmits the sixth stream ID to the multicast network.
10. The method of claim 9,
The fourth content ID is a value obtained by increasing the third content ID, the server providing content through multicast.
8. The method of claim 7,
The first stream ID includes the first channel ID in a predetermined bit, the server for providing content in multicast.
8. The method of claim 7,
The second stream ID includes the first channel ID in a preset bit, and includes the first content ID in a bit different from the preset bit, a server for providing content by multicast.
A user terminal for receiving content through UDP-based multicast, comprising:
a stream ID transmitter for transmitting a first stream ID including a first channel ID to a server;
a session manager for opening a session of the first channel ID;
a message transmitter for transmitting an IGMP message to a multicast network;
a stream ID receiver configured to receive a second stream ID in which the first channel ID and the first content ID are combined from a multicast network;
an extraction unit for extracting the first channel ID of the second stream ID;
a checking unit that checks whether the first channel ID extracted from the second stream ID is the same as the first channel ID included in the first stream ID;
and a data receiver configured to receive data through a first content ID included in the second stream ID when the first channel ID is the same as a result of checking.
14. The method of claim 13,
The stream ID receiving unit,
receiving a third stream ID in which the first channel ID and the second content ID are combined from the multicast network.
14. The method of claim 13,
The stream ID transmission unit,
When the fourth stream ID including the second channel ID is transmitted to the server,
The session management unit opens a session of the second channel ID,
The stream ID receiver receives a fifth stream ID in which the second channel ID and the third content ID are combined from the multicast network,
The extraction unit extracts the second channel ID of the fifth stream ID,
The data receiver may be configured to receive data through a third content ID included in the fifth stream ID when the second channel ID extracted from the fifth stream ID corresponds to the second channel ID included in the fourth stream ID. receive,
The stream ID receiver may receive, from the multicast network, a sixth stream ID in which the second channel ID and the fourth content ID are combined.
14. The method of claim 13,
The first stream ID includes the first channel ID in a predetermined bit, the user terminal.
14. The method of claim 13,
The second stream ID includes the first channel ID in a preset bit, and includes the first content ID in a bit different from the preset bit, the user terminal.

Images