WO2014156034A1 - サーバ、ルータ、受信端末および処理方法 - Google Patents
サーバ、ルータ、受信端末および処理方法 Download PDFInfo
- Publication number
- WO2014156034A1 WO2014156034A1 PCT/JP2014/001467 JP2014001467W WO2014156034A1 WO 2014156034 A1 WO2014156034 A1 WO 2014156034A1 JP 2014001467 W JP2014001467 W JP 2014001467W WO 2014156034 A1 WO2014156034 A1 WO 2014156034A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- ccn
- fec
- content data
- processing
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/14—Routing performance; Theoretical aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
- H04L45/3065—Route determination based on the nature of the carried application for real time traffic
Definitions
- the present invention relates to a server, a router, a receiving terminal, and a processing method, and more particularly, to a server, a router, a receiving terminal, and a processing method for realizing real-time data distribution on CCN (Content Centric Network).
- CCN Content Centric Network
- CCN is a next-generation network architecture, which is a content distribution technology that manages content in a name space and caches it in a router on the network (for example, see Non-Patent Document 1).
- Content distribution on the CCN network is realized by a receiver receiving the content transmitting an interest packet for the content.
- the recipient who receives the content can acquire the content without being aware of the location where the content is stored by designating the content by the name space.
- a recipient who receives content can efficiently receive the content by using the CCN network.
- the CCN network is a receiver-oriented system in which a recipient who receives content requests and acquires the content. Therefore, by using the CCN network, a large number of people can receive content such as a moving image site efficiently and with high quality.
- packet loss may occur due to congestion, etc., as in the case of communication on the Internet.
- packet loss occurs, there is a possibility that communication quality may be deteriorated such that complete content data cannot be received.
- Non-Patent Document 1 Non-Patent Document 2, and Patent Document 1
- Patent Document 2 a method for dealing with packet loss on the CCN network using retransmission
- Non-Patent Document 1 Even if the retransmission method shown in the above Non-Patent Document 1, Non-Patent Document 2, and Patent Document 1 is used to cope with a packet loss on the CCN network, it is possible to ensure real-time content data acquisition. There is a problem that you can not.
- the present invention has been made in view of the above-described circumstances, and an object thereof is to provide a server, a router, a receiving terminal, and a processing method that can ensure real-time performance of content data acquisition.
- a server is a server that performs processing on a real-time stream transmitted via a CCN (Content-Centric Network) network, and a CCN receiving unit that acquires a packet by the CCN network;
- a CCN transmission unit that transmits a packet to the CCN network, a conversion process for improving the real-time property of the content data, a conversion processing unit that generates the packet of the content data subjected to the conversion process, and an interest packet
- a server control unit that updates a routing table describing the content of processing, and the server control unit, when the CCN receiving unit receives an interest packet for the content subjected to the conversion processing, Issuing an interest packet for the original content data of the content to be processed;
- the conversion processing unit performs the conversion process on the original content data. And performing a control to generate a packet of the original content data that has been subjected to the
- the present invention it is possible to realize a server, a router, a receiving terminal, and a processing method that can ensure real-time performance of content data acquisition.
- FIG. 1 is a diagram illustrating an example of a content distribution system on a CCN network.
- FIG. 2 is a diagram illustrating an example of a configuration of the content distribution system according to the first embodiment.
- FIG. 3 is a diagram illustrating an example of a detailed configuration of the processing server according to the first embodiment.
- FIG. 4 is a diagram illustrating an example of a detailed configuration of the receiving terminal according to Embodiment 1.
- FIG. 5A is a diagram illustrating an example of a packet configuration configuring the FEC content in the first embodiment.
- FIG. 5B is a diagram illustrating an example of a packet configuration that configures the FEC content in the first exemplary embodiment.
- FIG. 6 is a sequence showing a processing flow of the content distribution system in the first embodiment.
- FIG. 1 is a diagram illustrating an example of a content distribution system on a CCN network.
- FIG. 2 is a diagram illustrating an example of a configuration of the content distribution system according to the first embodiment.
- FIG. 7 is a diagram showing a processing flow for issuing an interest packet of the receiving terminal in the first embodiment.
- FIG. 8A is a diagram illustrating an example of a configuration of an interest packet in CCN.
- FIG. 8B is a diagram illustrating an example of a configuration of an FEC interest packet according to Embodiment 1.
- FIG. 8C is a diagram illustrating an example of a configuration of an FEC interest packet according to Embodiment 1.
- FIG. 8D is a diagram illustrating an example of a configuration of an FEC interest packet according to Embodiment 1.
- FIG. 8E is a diagram illustrating an example of a configuration of an FEC interest packet according to Embodiment 1.
- FIG. 8A is a diagram illustrating an example of a configuration of an interest packet in CCN.
- FIG. 8B is a diagram illustrating an example of a configuration of an FEC interest packet according to Embodiment 1.
- FIG. 8C is a diagram illustrating an example of a configuration of an
- FIG. 9 is a diagram illustrating a processing flow until the processing server according to the first embodiment transmits the converted content data.
- FIG. 10 is a diagram illustrating an example of a configuration of a route table in the first embodiment.
- FIG. 11 is a diagram illustrating an example of a configuration of an interest packet for the original content generated in the processing server according to the first embodiment.
- FIG. 12A is a diagram illustrating another example of the configuration of the FEC interest packet according to Embodiment 1.
- FIG. 12B is a diagram illustrating another example of the configuration of the FEC interest packet according to Embodiment 1.
- FIG. 13 is a sequence showing a processing flow of the content distribution system in the second embodiment.
- FIG. 14 is a diagram showing a processing flow in which the receiving terminal according to the second embodiment issues an interest packet for original content data and an FEC interest packet for redundant data.
- FIG. 15 is a diagram illustrating a processing flow until the processing server according to the second embodiment transmits redundant data.
- FIG. 16 is a diagram illustrating a processing flow until the processing server according to the third embodiment transmits the content data after the conversion processing.
- FIG. 17 is a diagram illustrating an example of a detailed configuration of the router according to the fourth embodiment.
- FIG. 18 is a diagram showing a processing flow of the CCN router that has received the route advertisement packet issuance of the processing server and the route advertisement packet in the fifth embodiment.
- FIG. 1 is a diagram showing an example of a content distribution system on the CCN network.
- the content distribution system 900 shown in FIG. 1 includes a publisher 901, CCN routers 903 and 905, and a CCN network 904.
- Publisher 901 performs primary distribution of content and holds content 902.
- CCN routers 903 and 905 are examples of CCN routers and are connected via a CCN network 904.
- the CCN router 903 includes a PIT (Pending Interest Table) 911, a cache 912, and an FIB (Forwarding Information Base) 913.
- the CCN router 905 includes a PIT 906, a cache 907, and an FIB 908.
- the cache 907 and the cache 912 store the content data received once.
- PIT 906 and PIT 911 record from which interface the interest packet is received and transmitted to which interface.
- FIB 908 and FIB 913 record to which face an interest packet for data for each namespace should be sent.
- the CCN network 904 is composed of one or more CCN routers. Like all CCN routers 903 and 905, all CCN routers have a cache for storing content data received once, a PIT that records from which interface an interest packet has been received and sent to which interface, and each name. An FIB that records to which face an interest packet for data corresponding to a space should be transmitted is provided.
- Each of content receiver A 910 and content receiver B 909 is a content receiver using a PC or the like, for example, and the PC or the like to be used is connected to the CCN network 904 through a CCN router 905.
- the content receiver A 910 transmits an interest packet having a name space corresponding to the content 902 to the CCN router 905.
- the CCN router 905 sends the CCN network 904 to the CCN network 904 according to the contents of the FIB 908. Transfer packets of interest.
- the CCN router 905 If the CCN router 905 holds content data corresponding to the name space of the packet of interest in the cache 907, the CCN router 905 sends the content data back to the content receiver A 910.
- the CCN router in the CCN network 904 that has received the packet of interest repeats the same operation as the CCN router 905.
- the interest packet issued by the content receiver A 910 is sent to the publisher 901. To reach.
- the publisher 901 that received the interest packet sends back the content data corresponding to the interest packet from the content receiver A 910 to the CCN router 903.
- the CCN router 903 transfers the content data (here, the content 902) acquired to the corresponding interface based on the information described in the PIT 911 when the interest packet is transferred to the publisher 901, and the cache 912 Store the received data in. Thereafter, the CCN router in the CCN network 904 and the CCN router 905 transfer data according to the contents of the PIT, whereby the content 902 is distributed to the content receiver A 910.
- the content receiver B 909 issues an interest packet for the content 902 and transmits it to the CCN router 905.
- the CCN router 905 since the CCN router 905 holds content data corresponding to the interest packet issued by the content receiver B 909 in the cache 907, the CCN router 905 performs content data (for the interest packet issued by the content receiver B 909 ( Send back the content 902).
- the content receiver B909 can acquire the same content received by the content receiver A910. Since the content data held in the CCN router cache can be used, traffic in the CCN network 904 is not increased. In other words, by using a CCN network that holds content in the cache of the CCN router, it is possible to reduce the traffic of the entire network at the time of content distribution.
- content distribution on the CCN network is realized by using an interest packet including a name space when acquiring content. Therefore, the recipient who wants to receive the content (hereinafter also referred to as the content recipient) can specify the content by the name space, so that the content recipient can efficiently and without being aware of the location where the content is stored. Can receive content.
- the CCN network is a receiver-oriented system in which a content receiver requests and acquires content. Therefore, by using the CCN network, a large number of people can receive content such as a moving image site efficiently and with high quality.
- Non-Patent Document 1 Non-Patent Document 2, and Patent Document 1
- Patent Document 2 a method for dealing with packet loss on the CCN network using retransmission
- Non-Patent Document 1 the receiver requesting the content sets the effective time of the interest packet sent out by himself / herself, and determines that a packet loss has occurred when the content cannot be acquired even after the effective time has passed, so the interest packet Is disclosed again.
- Non-Patent Document 2 in addition to the timeout of interest packets, when a router on the network fails to acquire content, it returns a NACK (negative acknowledgment) packet to notify the receiver of the occurrence of packet loss, and notification A method is described in which the receiving side receiving the packet retransmits the packet of interest.
- NACK negative acknowledgment
- Patent Document 1 describes a method of detecting a packet including an error by a relay CCN router.
- Non-Patent Document 1 and Non-Patent Document 2 when the retransmission control method described in Non-Patent Document 1 and Non-Patent Document 2 is used, packet loss occurs on the CCN network, and the content receiver cannot acquire the content. Can retransmit the interest packet for the content data that could not be acquired, and can cope with packet loss on the CCN network.
- Non-Patent Document 1 Even if the retransmission method described in Non-Patent Document 1, Non-Patent Document 2, and Patent Document 1 is used to cope with packet loss on the CCN network, the real-time property of content data acquisition cannot be ensured. There is a problem. Hereinafter, this problem will be described in detail.
- content distribution using the CCN network is performed mainly by the content receiver. Therefore, packet loss occurs, and when the interest packet is retransmitted in order to reacquire the content, the content receiver must detect the occurrence of the packet loss.
- Non-Patent Document 1 it is necessary for the content receiver to wait for the interest packet issued by the content receiver to expire. That is, with the method described in Non-Patent Document 1, it takes a long time to detect the occurrence of packet loss, and the real-time property of content data acquisition cannot be ensured.
- Non-Patent Document 2 in addition to the method described in Non-Patent Document 1, when the relay CCN router fails to acquire the content data corresponding to the interest packet, the NACK is sent back to return the interest packet.
- the content receiver can detect the packet loss within the valid time.
- RTT Random Trip Time
- the CCN router in which the packet loss has occurred is required at least for detecting the occurrence of the packet loss. That is, when the publisher and the content receiver are located at a distance, it is not possible to ensure the real-time property of content data acquisition.
- Patent Document 1 it is possible to detect a packet including an error by a relay CCN router, but it is impossible to detect the occurrence of a packet loss until the content receiver receives the content data. is there. That is, in the method described in Patent Document 1, in order to acquire content data that could not be acquired due to packet loss, as a result, it took time equivalent to that of Non-Patent Document 1, and the real-time property of content data acquisition was reduced. It cannot be secured.
- Non-Patent Document 1 As described above, even if the retransmission method described in Non-Patent Document 1, Non-Patent Document 2 and Patent Document 1 is used to cope with packet loss on the CCN network, it takes time to acquire the content, The real-time property of acquisition is lost. That is, the real time property of content data acquisition cannot be ensured. On the other hand, if the retransmission control is not performed in order to emphasize the real-time property of content acquisition, content acquisition due to packet loss will be given up, leading to a decrease in content quality.
- Real-time distribution on the CCN network depends greatly on the processing capability of the publisher.
- the publisher When performing content distribution, it is also possible for the publisher to place the content in the publisher's cache by performing content encoding processing or the like in advance. For this reason, it is considered that content distribution does not always place a heavy load on publishers.
- the publisher when content distribution is performed in real time, the publisher continues to receive an interest packet for the latest content issued by the content receiver. In this case, the publisher that has received the interest packet must continuously perform processing such as encoding within a limited time in order to realize real-time content distribution.
- Non-Patent Document 1 a mobile network is also assumed as means for connecting to the CCN network.
- a terminal with limited resources such as a portable terminal can be considered as a publisher.
- the processing required for the publisher may easily exceed the processing capability.
- a server is a server that processes a real-time stream transmitted through a CCN (Content-Centric Network) network.
- a CCN receiving unit that obtains a packet
- a CCN transmitting unit that transmits the packet to the CCN network
- a conversion process for improving real-time performance of the content data and a packet of the content data that has been subjected to the conversion process
- a conversion processing unit to be generated and a server control unit that updates a route table that describes the content of the processing for the interest packet.
- the server control unit is interested in the content for which the CCN receiving unit has performed the conversion processing.
- an enhancement to the original content data of the content to be processed by the conversion process is performed.
- the CCN transmission unit obtains the original content data to be processed from the CCN network, it issues a taste packet to the CCN transmission unit.
- the conversion process is performed on the original content data, the packet of the original content data that has been subjected to the conversion process is generated, and the CCN transmission unit is transmitted as a reply packet of an interest packet for the content that has undergone the conversion process To control.
- the conversion process is an FEC process
- the conversion processing unit adds redundant data to the original content data to be processed, thereby performing a packet of the original content data on which the FEC process has been performed.
- the server control unit when the CCN receiving unit receives an interest packet for the content on which the FEC processing has been performed from the CCN network, the original content of the content to be processed by the FEC processing
- the FEC processing is performed on the original content data by causing the conversion processing unit to perform the FEC processing.
- a packet of the original content data that has been processed may be generated.
- the conversion process is a transcoding process
- the conversion processing unit performs the transcoding process on the original content data to be processed, and a packet of the original content data subjected to the transcoding process.
- the server control unit issues an interest packet for the original content data of the content when the CCN receiving unit receives an interest packet for the content subjected to the transcoding process from the CCN network.
- the conversion processing unit performs the transcoding process on the original content data, and generates a packet of the original content data subjected to the transcoding process. As Good.
- the server further includes a content cache that holds at least one of the original content data subjected to the conversion process by the conversion processing unit and the original content data received by the CCN reception unit,
- the content cache may be used for the conversion process for the original content data or a reply packet for the interest packet for the content subjected to the conversion process.
- the server further includes a server load monitoring unit that monitors a server load, and the server load monitoring unit generates a route advertisement packet including at least load information indicating the server load, and passes through the CCN transmission unit. It may be transmitted to the CCN network.
- a router is a router that transmits a real-time stream transmitted through a CCN network, and a CCN receiving unit that acquires a packet by the CCN network, and a packet to the CCN network. Describes the CCN transmission section to be transmitted, the conversion processing for improving the real-time property of the content data, the conversion processing section for generating the packet of the content data subjected to the conversion processing, and the contents of the processing for the interest packet
- a router controller that updates a routing table that generates an interest packet for the content data that has undergone the conversion process or an interest packet to a redundant part that has undergone the conversion process of the content data; and
- the router control unit is configured to handle the content that has been subjected to the conversion process by the CCN reception unit.
- an interest packet for the original content data of the content to be processed in the conversion process is issued, and the CCN transmission unit is controlled to transmit the interest packet, and the CCN reception is performed.
- the conversion processing unit performs the conversion processing on the original content data, and the packet of the original content data that has been subjected to the conversion processing is obtained. Control is performed so that the CCN transmission unit transmits the packet as an interest packet return packet for the content subjected to the conversion process.
- the conversion process and the distribution of the content after the conversion process are performed not by the publisher but by the router of this aspect, so even in an environment where packet loss occurs on the CCN network, without increasing the load on the publisher, It is possible to achieve high-quality content distribution that requires real-time performance.
- the conversion process is an FEC process
- the router control unit is statistical information calculated based on the real-time stream received by the CCN receiving unit, and includes packet loss rate, packet of interest packet transmission
- the content data obtained by calculating the required FEC strength from statistical information including RTT (Round Trip Time) until acquisition and packet acquisition time information for real-time stream reproduction, and performing FEC processing at the FEC strength.
- An interest packet for a redundant portion of content data that has been subjected to FEC processing with the FEC intensity may be generated.
- a receiving terminal is a receiving terminal that acquires a real-time stream via a CCN network, and is received by a CCN receiving unit that acquires packets by the CCN and the CCN receiving unit. Based on the real-time stream, the necessary FEC strength is calculated, and the interest packet for the content data subjected to the FEC processing with the FEC strength or the redundant portion of the content data subjected to the FEC processing with the FEC strength.
- a terminal control unit that generates an interest packet to the CC, a CCN transmission unit that transmits the interest packet generated by the terminal control unit, and a line of the FEC process that is a reply packet to the interest packet transmitted by the CCN transmission unit
- the original content data or the packet of the redundant portion is decoded, and the original content data It comprises a FEC decoder for correcting the Kettorosu, the.
- the terminal control unit is statistical information calculated based on the real-time stream received by the CCN reception unit, and includes packet loss rate, RTT from interested packet transmission to packet acquisition, and real-time stream reproduction.
- the necessary FEC intensity may be calculated from statistical information including packet acquisition time information for the.
- a processing method is a processing method of a server that performs processing on a real-time stream transmitted through a CCN network, and a CCN reception step of acquiring a packet by the CCN network;
- a server control step that updates a route table describing the content of processing for the server, and when the server control step receives an interest packet for the content subjected to the conversion processing in the CCN receiving step, To the original content data of the content to be processed The interest packet is issued, the control packet is transmitted in the CCN transmission step, and when the original content data to be processed is acquired from the CCN network in the CCN reception step, the conversion processing step To perform the conversion process on the original content data, generate a packet of the original content data subjected to the conversion process, and in the CCN transmission
- a processing method is a processing method for a router that performs transmission of a real-time stream transmitted through a CCN network, the CCN receiving step of acquiring a packet by the CCN network, and the CCN A CCN transmission step of transmitting a packet to the network, a conversion process for generating a packet of the content data subjected to the conversion process, performing a conversion process for improving the real-time property of the content data, and a process for the interest packet
- a router control step for updating a routing table describing the contents of the router, wherein the router generates an interest packet for the content data subjected to the conversion process or an interest packet for the redundant part subjected to the conversion process of the content data
- the router control step includes the C In the N reception step, when an interest packet for the content subjected to the conversion process is received, an interest packet for the original content data of the content to be processed by the conversion process is issued, and in the CCN transmission step, the In the CCN reception step, when the original
- the processing method is a processing method of a receiving terminal that acquires a real-time stream via a CCN network, the CCN receiving step of acquiring a packet by the CCN, and the CCN reception Based on the real-time stream received in the step, the required FEC strength is calculated, and the interest packet for the content data subjected to the FEC processing with the FEC strength or the content data subjected to the FEC processing with the FEC strength.
- a terminal control step for generating an interest packet to the redundant part of the terminal includes a CCN transmission step for transmitting the interest packet generated in the terminal control step, and a reply packet for the interest packet transmitted in the CCN transmission step
- the original content data subjected to FEC processing Other includes a FEC decoding step of decoding the packet of the redundant portion, modifies the packet loss of the original content data.
- FIG. 2 is a diagram illustrating an example of a configuration of the content distribution system according to the first embodiment.
- the content distribution system 1 shown in FIG. 2 includes a CCN router 11 that holds content, a processing server 12, and a receiving terminal 14, which are connected via a CCN network 13.
- the receiving terminal 14 sends an interest packet (hereinafter also referred to as an interest packet after the conversion process) to the content subjected to the conversion process for improving the real-time property. Issue.
- an interest packet is issued for the content data before the conversion process (hereinafter also referred to as original content).
- the processing server 12 When the processing server 12 receives an interest packet (a post-conversion processing interest packet) for content that has undergone conversion processing for improving real-time performance, the processing server 12 stores the original content corresponding to the post-conversion processing interest packet as the CCN that holds the content. Obtained from the CCN network 13 including the router 11, performs a conversion process, and sends the original content subjected to the conversion process.
- an interest packet a post-conversion processing interest packet
- the processing server 12 stores the original content corresponding to the post-conversion processing interest packet as the CCN that holds the content. Obtained from the CCN network 13 including the router 11, performs a conversion process, and sends the original content subjected to the conversion process.
- FIG. 3 is a diagram illustrating an example of a detailed configuration of the processing server according to the first embodiment.
- the processing server 12 illustrated in FIG. 3 is a server that performs processing on a real-time stream transmitted via the CCN network 13.
- the processing server 12 includes a server load monitoring unit 121, a conversion processing unit 122, a CCN receiving unit 123, a server control unit 124, and a CCN transmitting unit 125.
- the CCN receiving unit 123 and the CCN transmitting unit 125 are connected to the CCN network 13.
- the CCN receiving unit 123 acquires a packet through the CCN network 13. In addition, the CCN receiving unit 123 receives the original content data of the content to be processed by the conversion processing unit 122.
- the CCN transmission unit 125 transmits a packet to the CCN network 13.
- the CCN transmission unit 125 transmits a packet of original content data that has been subjected to the conversion processing by the conversion processing unit 122.
- the conversion processing unit 122 performs conversion processing for improving the real-time property on the content data, and generates a packet of content data subjected to the conversion processing. More specifically, the conversion processing unit 122 receives the original content data of the content to be processed by the conversion process received by the CCN receiving unit 123 from the server control unit 124, and performs conversion processing for improving real-time characteristics.
- the conversion processing is, for example, FEC processing.
- the conversion processing unit 122 generates a packet of the original content data subjected to the FEC process by adding redundant data to the original content data to be processed. That is, the conversion processing unit 122 receives the original content received by the CCN receiving unit 123 from the server control unit 124, and performs FEC processing as conversion processing.
- the conversion process may be a transcoding process, for example.
- the conversion processing unit 122 performs a transcoding process on the original content data to be processed, and generates a packet of the original content data subjected to the transcoding process. That is, the conversion processing unit 122 may receive the original content received by the CCN receiving unit 123 from the server control unit 124 and perform transcoding processing as conversion processing.
- the server control unit 124 controls the conversion processing unit 122, the CCN reception unit 123, and the CCN transmission unit 125, and issues the interest packet to the original content on the CCN network. In addition, the server control unit 124 updates the route table describing the content of the processing for the interest packet.
- the server control unit 124 when the CCN receiving unit 123 receives an interest packet (an interest packet after the conversion process) for the content subjected to the conversion process, the content to be processed by the conversion process An interest packet for the original content data is issued, and control is performed to cause the CCN transmission unit 125 to transmit the interest packet. Then, when the CCN receiving unit 123 acquires the original content data to be processed from the CCN network 13, the server control unit 124 causes the conversion processing unit 122 to perform conversion processing on the original content data, and the conversion processing The original content data packet is generated, and the CCN transmission unit 125 is controlled to transmit it as a reply packet of the interest packet (interchange packet after conversion processing) for the content subjected to the conversion processing.
- the conversion process is, for example, an FEC process
- the server control unit 124 When the CCN receiving unit 123 receives an interest packet (an interest packet after conversion processing) for the content that has been subjected to the FEC process from the CCN network 13, the server control unit 124, the original content data of the content that is the processing target of the FEC process Issue an interest packet for.
- the server control unit 124 causes the conversion processing unit 122 to perform the FEC process on the original content data, and performs the FEC process.
- the original content data packet is generated.
- the conversion process is, for example, a transcoding process
- the server control unit 124 issues an interest packet for the original content data of the content.
- the server control unit 124 acquires the original content data from the CCN network 13
- the server control unit 124 causes the conversion processing unit 122 to perform a transcoding process on the original content data, and the packet of the original content data that has been subjected to the transcoding process. Is generated.
- the server control unit 124 has a route table that records a correspondence relationship between an interest packet for the content that has undergone the conversion process (an interest packet after the conversion process) and an interest packet for the original content. Since the route table will be described later, description thereof is omitted here.
- server control unit 124 may include a content cache.
- the server load monitoring unit 121 generates a route advertisement packet including at least load information indicating the server load, and transmits the route advertisement packet to the CCN network 13 through the CCN transmission unit 125.
- the server load monitoring unit 121 has a function of calculating the processing capacity of the processing server 12, issuing a route advertisement packet, and passing it to the CCN transmission unit 125.
- the detailed operation of the server load monitoring unit 121 will be described in a fifth embodiment to be described later.
- FIG. 4 is a diagram showing an example of a detailed configuration of the receiving terminal in the first embodiment.
- the receiving terminal 14 shown in FIG. 4 is a terminal that acquires a real-time stream via the CCN network 13.
- CCN transmission unit 141 includes a CCN transmission unit 141, a CCN reception unit 142, a control unit 143, a video decoder 144, and an FEC decoding unit 155.
- the CCN transmission unit 141 transmits the interest packet generated by the control unit 143.
- the CCN receiving unit 142 acquires a packet through the CCN network 13.
- each of the CCN transmission unit 141 and the CCN reception unit 142 is connected to the CCN network 13 with a function of transmitting and receiving packets corresponding to the name space of the CCN network. .
- the control unit 143 is an example of a terminal control unit, and when content that has undergone conversion processing for improving real-time characteristics is required, an interest packet (conversion processing) for the content that has been subjected to conversion processing for improving real-time characteristics. Post-interest packet) is issued. If data that has not been subjected to the conversion process is necessary, an interest packet for the original content before the conversion process is issued).
- the control unit 143 calculates the size of redundant data necessary for correcting the lost packet (hereinafter referred to as necessary FEC strength) based on the real-time stream received by the CCN receiving unit 142, and An interest packet is generated for the content data that has been subjected to FEC processing with the required FEC strength.
- the control unit 143 is statistical information calculated based on the real-time stream received by the CCN reception unit 142, and is used for packet loss rate, RTT (Round Trip Time) from packet transmission to packet acquisition, and real-time stream reproduction. Necessary FEC intensity is calculated from statistical information including packet acquisition time information.
- control unit 143 issues an interest packet including the calculated FEC intensity and bit rate and transmits it to the CCN transmission unit 141 in order to acquire content data that has been subjected to FEC processing (hereinafter also referred to as FEC content data). To do.
- control unit 143 calculates a time RTT from when the interest packet is issued until the data packet is received.
- control unit 143 receives the data received by the CCN receiving unit 142, calculates the packet loss rate, and then calculates the necessary FEC intensity and bit rate.
- FIG. 5A and FIG. 5B are diagrams illustrating an example of a packet configuration that configures the FEC content in the first embodiment.
- FIG. 5A shows a packet constituting the FEC content A.
- the FEC content A is composed of data packets 401 to 410, and redundant packets 411 and 412 are added. Redundant packets 411 and 412 in FEC content A are generated based on the contents of data packets 401-410.
- FIG. 5B shows a packet constituting the FEC content B.
- the FEC content B is composed of data packets 413 to 423, and redundant packets 423 to 428 are added. Redundant packets 423 to 428 in FEC content B are generated based on the contents of data packets 413 to 422.
- FEC content A two redundant packets are added to ten data packets.
- the FEC intensity in this case is referred to as 20%.
- FEC content B six redundant packets are added to ten data packets. In this case, the FEC intensity is 60%.
- the FEC decoding unit 155 operates when the conversion process is an FEC process, for example.
- the FEC decoding unit 155 decodes the packet of the original content data subjected to the FEC process, which is a reply packet to the interest packet transmitted by the CCN transmission unit 141, and corrects the packet loss of the original content data. That is, the FEC decoding unit 155 performs decoding from the received FEC content data to the original content data, and performs packet loss correction when a packet loss is detected.
- the receiving terminal 14 receives the FEC content A composed of the packets shown in FIG. 5A, and that the two or less data packets cannot be received because the two or less data packets are lost.
- the receiving terminal 14 can reproduce the lost data packet (loss packet) from the redundant packet and the data packet that can be received by the added redundancy. In this way, the receiving terminal 14 can acquire the necessary data packets 401 to 410 regardless of the occurrence of packet loss.
- the receiving terminal 14 recovers the data packet by the redundant packet. It can be performed.
- the video decoder 144 receives the content subjected to the conversion process, decodes it, and delivers it to a video playback device, a video recorder, or the like.
- the conversion process is an FEC process
- the video decoder 144 receives and decodes the signal decoded by the FEC decoding unit 155, and passes the decoded signal to a video reproduction device, a video recorder, or the like.
- the video decoder 144 sends information on the received video stream to the control unit 143.
- FIG. 6 is a sequence showing a processing flow of the content distribution system in the first embodiment.
- the receiving terminal 14 issues an interest packet (an interest packet after the conversion process) for the content (the content after the conversion process) subjected to the conversion process for improving the real-time property (S11).
- the CCN network 13 that is, each CCN router on the CCN network 13 confirms whether or not the converted content corresponding to (the requested) converted interest packet issued in S 11 exists in the CCN network 13. (S12).
- the post-conversion processing interest packet is transferred on the CCN network 13 based on the FIB of each CCN router.
- the interest packet after conversion processing reaches the processing server 12.
- the processing server 12 issues an interest packet for the original content of the content to be converted based on the interest packet after the conversion processing (S16). Since details of S16 will be described later, description thereof is omitted here.
- the interest packet for the original content is transferred to the CCN router 11 holding the original content via the CCN network 13.
- the CCN router 11 that holds the original content returns a data packet of the original content to the received interest packet (S17).
- the returned original content data packet is transferred to the processing server 12 via the CCN network 13.
- the processing server 12 performs a conversion process on the received original content (S18), and generates content data after the conversion process.
- the processing server 12 returns the converted content to the interest packet after the conversion processing in accordance with the contents of the PIT (S19). Since details of S18 and S19 will be described later, description thereof is omitted here.
- the receiving terminal 14 can acquire the content after the conversion processing.
- FIG. 7 is a diagram showing a processing flow for issuing an interest packet of the receiving terminal in the first embodiment.
- control unit 143 is activated when a packet is received (when a packet arrives) or upon a user request (S111, S119).
- packet arrival of the control unit 143 is performed by a notification that the CCN reception unit 142 has received the packet and the control unit 143 has received the packet, and the control unit 143 is activated (S111).
- the CCN receiving unit 142 passes received data such as content data to the control unit 143 (S112).
- control unit 143 detects the packet loss by monitoring the difference in the serial number of the passed content data and the FEC necessary for correcting the lost packet from the statistical information such as the occurrence probability of the packet loss.
- the intensity is calculated (S113).
- control unit 143 determines whether or not it is necessary to issue an interest packet for the subsequent content (next content) included in the received data (S114). If it is determined in S114 that it is not necessary to issue an interest packet for the next content (No in S114), the process ends.
- control unit 143 needs to perform FEC processing on the content to be issued the next interest packet. Whether or not is determined (S115).
- the control unit 143 determines whether or not FEC processing is necessary for the content to be issued next interest packet from the statistical information such as the packet loss rate (packet loss occurrence probability) and RTT of the passed content data. Determine. Note that the determination in S115 may use statistical information based on data such as the packet loss rate and RTT of FEC content data acquired in the past.
- the control unit 143 performs the FEC content data that has been FEC processed on the original content with the necessary FEC intensity.
- FEC interest packet requesting is issued (S116).
- the control unit 143 issues, to the FEC interest packet, an FEC interest packet including a time stamp at the time of packet issuance and a content acquisition limit time in addition to the strength of the FEC. By including the time stamp in the FEC interest packet, it can be used to measure the RTT from when the FEC interest packet is issued to when the content is received.
- the control unit 143 issues an interest packet for a name space having an FEC service prefix, which will be described later, as an FEC interest packet.
- the control unit 143 also includes a time stamp at the time of issuance in this interest packet. By including the time stamp in the interest packet, it can be used for measuring the RTT from when the interest packet is issued to when the content is received.
- the CCN transmission unit 141 transmits the FEC interest packet or the interest packet created by the control unit 143 toward the CCN network 13 (S118).
- FIG. 8A is a diagram illustrating an example of a configuration of an interest packet in CCN.
- 8B to 8E are diagrams illustrating an example of the configuration of the FEC interest packet according to Embodiment 1.
- FIG. 8A is a diagram illustrating an example of a configuration of an interest packet in CCN.
- 8B to 8E are diagrams illustrating an example of the configuration of the FEC interest packet according to Embodiment 1.
- FIG. 8A is a diagram illustrating an example of a configuration of an interest packet in CCN.
- 8B to 8E are diagrams illustrating an example of the configuration of the FEC interest packet according to Embodiment 1.
- Non-Patent Document 1 The configuration of the interest packet 43 shown in FIG. 8A is described in Non-Patent Document 1, and is an example of the configuration of a general interest packet used on the CCN network 13.
- the interest packet 43 is composed of fields 431 to 433.
- the field 431 is a field for inputting a name space corresponding to the content requested by the content receiver. For example, when a content receiver requests data in the namespace “test / video /” at a bit rate of “512 kbps”, the name space “test / video / 512 kbps” is input to the field 431, and the data is Can be specified in this namespace.
- the field 432 is a field for entering the scope of the packet of interest and other information.
- the field 433 is a field where a sender (content receiver) inputs a random number in order to ensure the uniqueness of the packet of interest.
- the field 433 into which a random number is input has the same content receiver at the same time when each CCN router included in the CCN network 13 receives an interest packet. It is used to determine whether or not a packet of interest has been received in the past.
- the FEC interest packet 44 illustrated in FIG. 8B, the FEC interest packet 45 illustrated in FIG. 8C, the FEC interest packet 46 illustrated in FIG. 8D, and the FEC interest packet 47 illustrated in FIG. 8E each have contents having a name space of “test / video / 512 kbps”.
- 2 is an example of a configuration of an FEC interest packet that requests content data to which redundant data with 50% FEC strength is added.
- a field 451 shown in FIG. 8C, a field 461 shown in FIG. 8D, and a field 471 shown in FIG. 8E are fields for inputting a name space corresponding to the FEC content requested by the content receiver.
- the field 442 shown in FIG. 8B, the field 452 shown in FIG. 8C, the field 462 shown in FIG. 8D, and the field 472 shown in FIG. 8E are fields for entering the scope of the FEC interest packet and other information.
- a field 443 shown in FIG. 8B, a field 454 shown in FIG. 8C, a field 463 shown in FIG. 8D, and a field 474 shown in FIG. Is a field for inputting.
- the service for performing the FEC processing provided by the processing server 12 has a namespace prefix “fec.” On the CCN network 13. It is shown.
- the service that performs the FEC processing provided by the processing server 12 has a prefix of the name space “fec /” on the CCN network 13.
- the FEC intensity may be specified together with the name space for requesting the FEC interest packet as shown in a field 441 shown in FIG. 8B and a field 461 shown in FIG. 8D. Further, as shown in a field 453 shown in FIG. 8C and a field 473 shown in FIG. 8E, an extension header (extension field) for indicating the FEC strength may be defined and described in that portion.
- processing server 12 on the CCN network 13 corresponds to the name space “fec.”
- the processing server 12 corresponds to the name space “fec /” when the FEC interest packet 46 and the FEC interest packet 47 are issued by the receiving terminal 14.
- FIG. 9 is a diagram showing a processing flow until the processing server in the first embodiment sends the content data after the conversion processing.
- the processing server 12 is activated upon reception of the FEC interest packet or the original content packet (S160), and determines whether or not the received packet is an FEC interest packet (S161).
- the processing server 12 determines whether the same FEC interest packet has been received before (S162). . In the present embodiment, the processing server 12 determines whether or not the same FEC interest packet has been received before by checking whether or not the same FEC interest packet exists in the route table.
- the processing server 12 confirms whether the destination candidate of the interest packet for the original content converted in S163 exists in the FIB (S164).
- the processing server 12 adds an entry to the route table (S166). More specifically, the processing server 12 adds an entry including the received FEC interest packet, the FEC interest packet for the original content after the FEC process, and information on the face that transmitted the interest packet for the original content. Details of the configuration of the route table will be described later.
- the processing server 12 receives the original content packet in S160 as a response to the interest packet for the original content data transmitted in S165, for example.
- the packet received by the processing server 12 is not an FEC interest packet (No in S161), and the received original content packet and the corresponding interest packet are present in the route table entry. It is confirmed whether or not (S167).
- the processing server 12 when the processing server 12 confirms that the received original content packet and the corresponding interest packet are present in the entry of the route table (Yes in S167), the processing server 12 The FEC interest packet is created and transmitted while comparing the correspondence between the FEC interest packet in the route table and the interest packet for the original content (S168).
- the processing server 12 performs FEC processing using the conversion processing unit 122. Further, the processing server 12 transmits the created FEC interest packet from the CCN transmission unit 125.
- the processing server 12 deletes the entry in the route table (S169). More specifically, since the FEC process is completed, the processing server 12 deletes the entry in the route table in which the FEC interest packet corresponding to the FEC content transmitted in S168 is described.
- the packet of the FEC content transmitted in S168 is transferred to the CCN receiving unit 142 of the receiving terminal 14 in light of the PIT of the relay CCN router included in the CCN network 13.
- the control unit 143 receives the packet of the FEC content received by the CCN reception unit 142 and determines whether the packet is the packet of the FEC content.
- the FEC decoding unit 155 decodes the packet.
- the FEC decoding unit 155 performs erasure correction when a packet loss occurs when decoding the packet.
- the video decoder 144 receives the original content data decoded by the FEC decoding unit 155 and sends it to an external video playback device or video recorder.
- FIG. 10 is a diagram showing an example of the configuration of the route table in the first embodiment.
- FEC interest packet information 511 includes FEC interest packet information 511, original content interest packet information 512, reception face information 513, and transmission face information 514, and is used to manage the interest packets.
- FEC interest packet information 511 information on the FEC interest packet received by the processing server 12 is described, and in the reception face information 513, face information on which the interest packet has been received is described.
- original content interest packet information 512 information on the original content interest packet obtained by converting the FEC interest packet is described, and in the transmission face information 514, face information on which the original content interest packet is transmitted is described.
- the interface or application (hereinafter also referred to as a reception face) from which the processing server 12 has received the FEC interest packet is “0”, “0” is written in the field of the reception face information 513 (described). ).
- the original content interest packet obtained by converting the FEC interest packet is “/ test / video / 512 kbps”
- “/ test / video / 512 kbps” is written in the column of the original content interest packet information 512.
- the interface or application (hereinafter also referred to as a transmission face) from which the processing server 12 has transmitted the original content interest packet is “2, 4”, “2, 4” is displayed in the transmission face information 514 column. Written.
- the information described in the route table 51 is not limited to the four types of examples described above. For example, information on random numbers given for each interest packet described in Non-Patent Document 1 may also be described in the route table 51. Further, the timeout time of each interested packet may be described in the route table 51.
- the format of the route table 51 is not limited to the above-described table, and may be realized, for example, by extending the PIT described in Non-Patent Document 1.
- FIG. 11 is a diagram illustrating an example of a configuration of an interest packet for the original content generated in the processing server 12 according to the first embodiment.
- the interest packet 61 shown in FIG. 11 is composed of fields 611 to 613.
- the field 611 is a field for inputting the name space of the original content corresponding to the FEC content requested by the content receiver.
- a field 612 is a field for filling in additional information such as a scope of an interest packet for the original content when acquiring the content.
- a field 613 is a field in which a sender (processing server) inputs a random number to ensure uniqueness of the original content.
- FIG. 11 shows an example in which the processing server 12 converts an FEC interest packet for content having the name space of test / video / 512 kbps shown in FIGS. 8A to 8E into an interest packet for the original content.
- the processing server 12 inputs the name space test / video / 512 kbps of the original content corresponding to the FEC content specified by any one of the FEC interest packets in FIGS. 8A to 8E in the field 611.
- the server of the present embodiment even in an environment where packet loss occurs on the CCN network, it is possible to achieve high-quality content distribution that requires real-time performance without increasing the load on the publisher. It becomes possible.
- the erasure correction using FEC may be performed in each CCN router.
- the role of the processing server may be the CCN router that holds the content.
- the original content has been described as video data in the present embodiment, it is not limited to video data. Any audio data or image data that requires real-time data may be used.
- FIGS. 8B to 8E. 12A and 12B are diagrams illustrating another example of the configuration of the FEC interest packet in Embodiment 1.
- FIG. 12A and 12B are diagrams illustrating another example of the configuration of the FEC interest packet in Embodiment 1.
- the FEC interest packet may be an FEC interest packet 71 configured in a TLV (Type-Length-Value) format having fields of Type, Length (length), and Value (value), for example, as shown in FIG. 12A.
- TLV Type-Length-Value
- contents indicating that the FEC processing is performed as the Type of the FEC interest packet 71 is entered, and in the field 712, the Length of the FEC interest packet 71 is entered.
- the fields 713 to 715 are the same as the fields 441 to 443 shown in FIG.
- the FEC interest packet may be an FEC interest packet 72 that is converted so that a third party cannot read a part of the name space.
- a part of the name space corresponding to the FEC content requested by the content receiver is converted by a hash or the like so that it cannot be read by a third party.
- “fec.test / video / 512 kbps” input in the field 451 in FIG. 8C or “fec / test / video / 512 kbps” input in the field 471 in FIG. 8E is “fec /% abc%”.
- An example in the case of conversion to “012” is shown.
- the fields 722 to 724 are the same as the fields 452 to 454 or the fields 472 to 474 shown in FIG. 8C or FIG.
- the redundant data constituting the FEC content may have a name space independent of the original content.
- the receiving terminal issues an interest packet for the redundant data and an interest packet for the original content independently.
- the original content and the redundant data can be acquired from the CCN network.
- the conversion process is an FEC process
- the receiving terminal issues an interest packet for redundant data by FEC and an interest packet for the original content instead of the interest packet after the FEC process. To do.
- FIG. 13 is a sequence showing a processing flow of the content distribution system in the second embodiment.
- FIG. 13 shows the processing flow of the content distribution system when the receiving terminal 14A receives redundant data and original content separately.
- the receiving terminal 14A and the processing server 12A according to the present embodiment are the same as the receiving terminal 14 and the processing according to the first embodiment except for the processing for the interest packet for the redundant data by FEC (FEC interest packet) and the interest packet for the original content.
- FEC FEC interest packet
- the receiving terminal 14A issues an interest packet for the original content (S21), and issues an FEC interest packet for redundant data (S22). Note that either S21 or S22 may be performed first.
- the interest packet for the original content issued in S21 is sent to the CCN network 13 and reaches the router or publisher holding the original content via the CCN network 13. This router or publisher returns a packet of the original content data in response to the interest packet for the original content (S23).
- the receiving terminal 14A receives the original content data packet returned via the CCN network 13 (S24), and acquires the original content data.
- the CCN network 13 that is, each CCN router on the CCN network 13, confirms whether or not redundant data corresponding to (requested) the interest packet issued in S22 exists in the CCN network 13 (S25).
- the FEC interest packet issued in S22 is sent to the CCN network 13 and transferred on the CCN network 13 based on the FIB of each CCN router.
- the FEC interest packet for the redundant data reaches the processing server 12A.
- the processing server 12A issues an interest packet for the original content based on the FEC interest packet for redundant data (S28).
- the interest packet for the original content issued in S28 reaches the router or publisher holding the original content, and this router or publisher returns the data packet of the original content to the received interest packet (S29). ).
- the returned original content data packet is transferred to the processing server 112 A via the CCN network 13.
- the processing server 12A performs FEC processing on the received original content (S30), and generates redundant data thereof.
- the processing server 12A returns the redundant data to the FEC interest packet for the redundant data according to the contents of the PIT (S31).
- the receiving terminal 14A receives the redundant data packet sent from the processing server 12A in S31 via the CCN network 13 (S32).
- the original content and the redundant data exist on different CCN routers, so the receiving terminal 14A can efficiently acquire the FEC content.
- FIG. 14 is a diagram illustrating a processing flow in which the receiving terminal 14 according to the second embodiment issues an interest packet for original content data and an FEC interest packet for redundant data. Note that the processing flow shown in FIG. 14 is a detailed version of S21 and S22 in FIG.
- control unit 143 is activated when a packet is received (when a packet is received) or upon a user request (S211, S219). Below, the case where it starts by packet arrival is demonstrated first.
- S211 to S213 and S214 are the same as S111 to S113 and S115 described in FIG.
- control unit 143 issues an interest packet for the original content data (S215), and the necessary content is issued.
- An FEC interest packet for redundant data subjected to FEC processing with FEC intensity is issued (S216). Note that either S215 or S2167 may be performed first.
- the control unit 143 issues an FEC interest packet including a time stamp when the packet is issued in addition to the strength of the FEC. By including the time stamp in the FEC interest packet, it can be used to measure the RTT from when the FEC interest packet is issued to when the content is received.
- the control unit 143 issues an interest packet for a name space having a redundant data prefix as an FEC interest packet.
- the control unit 143 issues an interest packet for the original content data including the time stamp at the time of issue.
- the CCN transmission unit 141 transmits the interest packet (interest packet or FEC interest packet or the like) created by the control unit 143 toward the CCN network 203 (S218).
- the interest packet for the original content data issued in S1206 and S1210 can be defined as an interest packet 701 in FIG.
- FIG. 15 is a diagram showing a processing flow until the processing server in the second embodiment sends redundant data.
- FIG. 15 is different from FIG. 9 described in the first embodiment in that the FEC interest packet for the content after the FEC processing is the FEC interest packet for the redundant data, and the data packet of the FEC content transmitted after the FEC processing is the redundant data.
- the difference is that each data packet is changed.
- the processing server 12 is activated upon reception of an FEC interest packet or original content packet for redundant data (S280), and determines whether the received packet is an FEC interest packet for redundant data (S281).
- the processing server 12A When the processing server 12A confirms that the entry of the FEC interest packet for the redundant data exists in the route table (Yes in S287), the processing server 12A creates the FEC interest packet for the redundant data with reference to the route table. And it transmits from CCN transmission part 125 (S288).
- the processing server 12A deletes the entry of the transmitted redundant data interest packet from the route table (S289).
- S282 to S286 are the same as S161 to S166 of FIG.
- the redundant data packet transmitted in S288 is received by the receiving terminal 14A.
- erasure correction can be realized by decoding redundant data together with the original content data acquired in S24.
- the server of the present embodiment even in an environment where packet loss occurs on the CCN network, it is possible to achieve high-quality content distribution that requires real-time performance without increasing the load on the publisher. It becomes possible.
- the processing server 12 in the present embodiment has a content cache that stores content data received once.
- the processing server 12 further includes a content cache that holds at least one of the original content data that has been converted by the conversion processing unit 122 and the original content data that has been received by the CCN receiving unit 123.
- the cache is used as a return packet for an interest packet for the content that has undergone conversion processing or conversion processing for the original content data.
- FIG. 16 is a diagram showing a processing flow until the processing server in the third embodiment sends the content data after the conversion processing.
- the processing server 12 receives and activates the FEC interest packet or the original content packet (S381), and determines whether the received packet is an FEC interest packet (S382).
- the processing server 12 determines whether the same FEC interest packet has been received before (S383). . In the present embodiment, the processing server 12 determines whether or not the same FEC interest packet has been received before by checking whether or not the same FEC interest packet exists in the route table. In S383, if the processing server 12 confirms that the same FEC interest packet entry exists on the route table (Yes in S382), the processing server 12 discards the interest packet and ends the processing.
- the processing server 12 when the processing server 12 confirms that the content cache of the processing server 12 has the data cache of the FEC content (Yes in S384), the processing server 12 transmits the cached FEC content by CCN. It transmits from the part 125 (S385), and complete
- the processing server 12 confirms whether or not the content cache of the processing server 12 has the data cache of the original content (S387).
- the processing server 12 When the processing server 12 starts processing with the original content packet in S381, it is determined in S382 that the processing server 12 received is not an FEC interest packet (No in S382), and in S392, the processing server 12 Obtains the original content data and caches the received original content data.
- the processing server 12 confirms whether an entry of the FEC interest packet exists in the route table (S393).
- the processing server 12 confirms that the entry of the FEC interest packet exists in the route table in S393 (Yes in S393), the processing server 12 refers to the route table and the FEC in the conversion processing unit 122 An interest packet is created, the created FEC interest packet is stored in the content cache, and the FEC interest packet is transmitted from the CCN transmission unit 125 (S394).
- the processing server 12 deletes the entry from the route table (S395) and ends the processing.
- the server of the present embodiment even in an environment where packet loss occurs on the CCN network, it is possible to achieve high-quality content distribution that requires real-time performance without increasing the load on the publisher. It becomes possible.
- the processing server 12 can handle only the redundant data shown in the second embodiment.
- processing server 12 may further have a function of performing a route advertisement on the original content data held in the content cache and sending back the original content packet when an interest packet for the original content data is received.
- each CCN router on the CCN network 13 has a function of issuing an interest packet after conversion processing and generating data after conversion processing will be described.
- FIG. 17 is a diagram illustrating an example of a detailed configuration of the router according to the fourth embodiment.
- the router 21 shown in FIG. 17 transmits a real-time stream transmitted via the CCN network 13.
- 17 includes a conversion processing unit 222, a CCN reception unit 223, a router control unit 224, a CCN transmission unit 225, an FEC decoding unit 226, and a cache 227.
- the CCN receiving unit 223 acquires a packet through the CCN network 13.
- the CCN transmission unit 225 transmits the interest packet generated by the router control unit 224.
- each of the CCN transmission unit 225 and the CCN reception unit 223 is responsible for the function of transmitting and receiving packets of interest corresponding to the name space of the CCN network 13 and is connected to the CCN network 13. .
- the FEC decoding unit 226 operates when the conversion process is an FEC process, for example.
- the FEC decoding unit 226 is the same as the FEC decoding unit 155 of the receiving terminal 14 and decodes the packet of the original content data subjected to the FEC process, which is a reply packet to the interest packet transmitted by the CCN transmission unit 225, Correct the packet loss of the original content data. That is, the FEC decoding unit 226 has a function of decoding the received FEC content data into the original content data and performing packet loss correction when a packet loss is detected.
- the conversion processing unit 222 performs a conversion process for improving real-time performance on the content data, and generates a packet of content data subjected to the conversion process.
- the conversion processing unit 222 is the same as the conversion processing unit 122 of the processing server 12, performs a conversion process for improving real-time properties on content data, and generates a packet of content data subjected to the conversion process. . More specifically, the conversion processing unit 222 receives the original content data of the content to be processed by the conversion process received by the CCN receiving unit 223 from the router control unit 224, and performs conversion processing for improving real-time characteristics.
- the conversion processing is, for example, FEC processing.
- the conversion processing unit 222 generates a packet of the original content data subjected to the FEC process by adding redundant data to the original content data to be processed. That is, the conversion processing unit 222 receives the original content received by the CCN receiving unit 223 from the router control unit 224, and performs FEC processing as conversion processing.
- the conversion process may be a transcoding process, for example.
- the conversion processing unit 222 performs a transcoding process on the original content data to be processed, and generates a packet of the original content data subjected to the transcoding process. That is, the conversion processing unit 222 may receive the original content received by the CCN receiving unit 223 from the router control unit 224 and perform the transcoding process as the conversion process.
- the router control unit 224 controls the conversion processing unit 222, the CCN reception unit 223, the CCN transmission unit 225, and the FEC decoding unit 226, and controls the router 21.
- the router control unit 224 has the function of the control unit 143 of the receiving terminal 14, and when content that has undergone conversion processing for improving real-time characteristics is necessary, the content that has been subjected to conversion processing for improving real-time characteristics Interest packet (interesting packet after conversion process) is issued, or an interest packet is issued to the redundant portion where the content data conversion process has been performed.
- the router control unit 224 issues an interest packet for the data that has not been subjected to the conversion process (also described as the original content before the conversion process is performed).
- the router control unit 224 calculates the FEC strength necessary for correcting the lost packet based on the real-time stream received by the CCN receiving unit 223, and the FEC processing is performed with the necessary FEC strength.
- An interest packet for content data is generated.
- the router control unit 224 is statistical information calculated based on the real-time stream received by the CCN receiving unit 223, and includes a packet loss rate, an RTT from an interest packet transmission to packet acquisition, and a packet acquisition time for real-time stream reproduction.
- the necessary FEC intensity is calculated from the statistical information including the information.
- the router control unit 224 generates an interest packet for the content data that has been subjected to the FEC processing with the FEC strength or an interest packet for a redundant portion of the content data that has been subjected to the FEC processing with the FEC strength.
- the router control unit 224 has a function of the conversion processing unit 122 of the processing server 12 and is responsible for issuing an interest packet for the original content on the CCN network 13. In addition, the router control unit 224 updates the route table describing the content of processing for the interest packet.
- the router control unit 224 becomes a processing target of the conversion process.
- An interest packet for the original content data of the content is issued, and control is performed to cause the CCN transmission unit 225 to transmit the interest packet.
- the router control unit 224 causes the conversion processing unit 222 to perform conversion processing on the original content data, and the conversion processing
- the original content data packet is generated, and the CCN transmission unit 125 is controlled to transmit it as a reply packet of the interest packet (interchange packet after conversion processing) for the content subjected to the conversion processing.
- the cache 227 stores (caches) original content data received by the router 21, content data after conversion processing such as FEC processing received or generated, and redundant data.
- the router 21 when the router 21 receives an FEC interest packet and an FEC interest packet for redundant data, the same processing as the processing flow shown in FIG. 16 is performed. However, activation by a user request in S211 and S219 does not occur.
- the router 21 when the router 21 receives the FEC interest packet (S381, S382), if the same FEC interest packet exists in the route table (Yes in S383), the router 21 discards the packet. In S383, when the same FEC interest packet does not exist in the route table (No in S383), the router 21 refers to the cache 227 and confirms whether the data of the FEC content exists (S384).
- the router 21 converts the FEC interest packet into an interest packet for the original content and creates an entry in the route table (S386). ).
- the router 21 creates an FEC interest packet with reference to the route table, and caches the FEC content data in the cache 227. Transmission is performed and the entry is deleted from the route table (Yes in S393, S394, and S395).
- the router 21 deletes the entry in the route table (S389) and ends the process.
- the router 21 When the router 21 receives the content data packet, it performs the same processing as the processing flow shown in FIG. 3 and FIG.
- the router 21 calculates the necessary FEC intensity from statistical information such as the packet loss occurrence probability of the content data packet received by the CCN receiving unit 223 (S213).
- the router control unit 224 issues the interest packet for the original content data (S215), and is necessary.
- An FEC interest packet is issued for redundant data that has been FEC processed with a high FEC strength (S216).
- the router 21 describes the correspondence between the received interest packet and the converted FEC interest packet in the route table. If FEC processing is not required, the normal interest packet is also transferred to the next content acquisition.
- the router 21 stores the received content data in the cache 227.
- the router 21 caches the received original content data in the cache 227.
- the conversion processing unit 222 refers to the route table to refer to the FEC interest packet. And the FEC interest packet is transmitted to the cache 227 after being cached (S394). Thereafter, the router 21 deletes the entry in the route table (S395) and ends the process.
- the router 21 When the router 21 receives an interest packet for normal content that has not been subjected to conversion processing such as FEC processing, the router 21 receives content data corresponding to the name space of the received interest packet in the same manner as a normal CCN router. Is stored in its own cache 227, the content data is sent back to the face that received the interest packet. When there is no corresponding content data in its own cache 227, the interested packet is transferred to the CCN network 13 according to the contents of its own FIB.
- the router of this embodiment even in an environment where packet loss occurs on the CCN network, it is possible to achieve high-quality content distribution that requires real-time performance without increasing the publisher's load. It becomes possible.
- Non-Patent Document 1 discloses a technique in which a router that owns content can advertise a route to a router using a routing protocol such as OSPF or IS-IS.
- the processing server 12 monitors the remaining capacity of its own server with the server load monitoring unit 121, and distributes the remaining capacity of the processing capacity on the route advertisement by the CCN transmission unit 125. This will be described with reference to FIG.
- the configuration of the processing server 12 is the same as that shown in FIG.
- FIG. 18 is a diagram showing a processing flow of the CCN router that has received the route advertisement packet issuance of the processing server and the route advertisement packet in the fifth embodiment.
- the server load monitoring unit 121 is activated by a timer (S41).
- the server load monitoring unit 121 measures the processing load of the processing server 12 (S42), and creates a route advertisement including the measured processing load (S43).
- the CCN transmission unit 125 transmits the route advertisement packet created by the server load monitoring unit 121 to the CCN network 13 (S44).
- the route advertisement packet is received by the adjacent neighboring CCN router (S45), and the conversion processing request to the processing server 12 is increased or decreased according to the processing capacity of the processing server 12 advertised.
- the adjacent CCN router that has received the route advertisement packet performs processing from the adjacent CCN router.
- the cost of the route to the server 12 is set small.
- the processing capacity of the processing server 12 indicated by the information included in the route advertisement packet is small, the cost of the route from the adjacent CCN router to the processing server 12 is large.
- the server of the present embodiment even in an environment where packet loss occurs on the CCN network, it is possible to achieve high-quality content distribution that requires real-time performance without increasing the load on the publisher. It becomes possible.
- the adjacent CCN router that has received the route advertisement packet transfers the interest packet after the conversion process such as the FEC interest packet or the FEC interest packet for the redundant data to the processing server 12 having a large route cost. cut back.
- the adjacent CCN router that has received the route advertisement packet increases the transfer of FEC interest packets, FEC interest packets for redundant data, and the like to the processing server 12 having a small route cost.
- the adjacent CCN router may control the transfer amount of the interest packet after the conversion processing such as the FEC interest packet and the redundant data interest packet, etc., in two stages by transferring / not transferring using the route cost and the threshold value.
- each adjacent CCN router receives the route advertisement
- the cost of the route to the processing server 12 set by each adjacent CCN router may be described in the FIB of each adjacent CCN router.
- the processing contents of the packet transfer control in the adjacent CCN router are described in the extension header portion of the route advertisement packet issued from the processing server 1601 side. It may be.
- the server, the router, the receiving terminal, and the processing method thereof according to the embodiment of the present invention the real-time property of content data acquisition can be ensured. Furthermore, by using the server and router of the present embodiment, even in an environment where packet loss occurs on the CCN network, high-quality content distribution requiring real-time performance is achieved without increasing the load on the publisher. It becomes possible.
- the server, router, receiving terminal, and processing method thereof according to one or more aspects of the present invention have been described above based on the embodiment. However, the present invention is not limited to this embodiment. Absent. Unless it deviates from the gist of the present invention, one or more of the present invention may be applied to various modifications that can be conceived by those skilled in the art, or forms constructed by combining components in different embodiments. It may be included within the scope of the embodiments.
- the server, router, and receiving terminal are specifically a computer system composed of a microprocessor, ROM, RAM, hard disk unit, display unit, keyboard, mouse, and the like. is there.
- a computer program is stored in the RAM or hard disk unit.
- Each device achieves its functions by the microprocessor operating according to the computer program.
- the computer program is configured by combining a plurality of instruction codes indicating instructions for the computer in order to achieve a predetermined function.
- a part or all of the components constituting each of the above devices may be configured by one system LSI (Large Scale Integration).
- the system LSI is an ultra-multifunctional LSI manufactured by integrating a plurality of components on a single chip, and specifically, a computer system including a microprocessor, ROM, RAM, and the like. .
- a computer program is stored in the RAM.
- the system LSI achieves its functions by the microprocessor operating according to the computer program.
- a part or all of the constituent elements constituting each of the above devices may be constituted by an IC card or a single module that can be attached to and detached from each device.
- the IC card or the module is a computer system including a microprocessor, ROM, RAM, and the like.
- the IC card or the module may include the super multifunctional LSI described above.
- the IC card or the module achieves its function by the microprocessor operating according to the computer program. This IC card or this module may have tamper resistance.
- the present invention may be the method described above. Further, the present invention may be a computer program that realizes these methods by a computer, or may be a digital signal composed of the computer program.
- the present invention also provides a computer-readable recording medium such as a flexible disk, hard disk, CD-ROM, MO, DVD, DVD-ROM, DVD-RAM, BD (Blu-ray ( (Registered trademark) Disc), or recorded in a semiconductor memory or the like.
- the digital signal may be recorded on these recording media.
- the computer program or the digital signal may be transmitted via an electric communication line, a wireless or wired communication line, a network represented by the Internet, a data broadcast, or the like.
- the present invention may be a computer system including a microprocessor and a memory, the memory storing the computer program, and the microprocessor operating according to the computer program.
- program or the digital signal is recorded on the recording medium and transferred, or the program or the digital signal is transferred via the network or the like and executed by another independent computer system. You may do that.
- the present invention can be used for servers, routers, receiving terminals, etc., and in particular, can be used for servers, routers, receiving terminals, etc. that constitute a content distribution system that distributes video content in real time.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
以下、本発明の一態様を得るに至った経緯について説明する。
[コンテンツ配信システムの構成]
図2は、実施の形態1におけるコンテンツ配信システムの構成の一例を示す図である。図2に示すコンテンツ配信システム1は、コンテンツを保持するCCNルータ11と、処理サーバ12と、受信端末14とを備え、これらはCCN網13を介して接続されている。
図3は、実施の形態1における処理サーバの詳細構成の一例を示す図である。図3に示す処理サーバ12は、CCN網13を介し伝送される実時間ストリームに対して処理を行うサーバである。この処理サーバ12は、サーバ負荷監視部121、変換処理部122、CCN受信部123、サーバ制御部124およびCCN送信部125を備える。CCN受信部123およびCCN送信部125はCCN網13に接続されている。
次に、図4を用いて受信端末14の詳細構成について説明する。
図6は、実施の形態1におけるコンテンツ配信システムの処理フローを示すシーケンスである。
次に、図7を用いて受信端末14が変換処理後の興味パケットを発行する処理フローについて説明する。以下では、変換処理としてFEC処理を行う場合を例に挙げて説明する。
次に、受信端末14等が生成する興味パケットおよび変換処理後興味パケットの構成例について、図を用いて説明する。以下でも、変換処理としてFEC処理を行う場合を例に挙げて説明する。
次に、図9を用いて処理サーバ12が変換処理後の興味パケットを受け取ってから、変換処理後の興味パケットに対応する変換処理後のコンテンツデータを送出するまでの処理フローについて説明する。なお、この処理は、図6におけるS16、S18およびS19を詳細化したものに相当する。以下では、変換処理としてFEC処理を行う場合を例に挙げて説明する。
次に、興味パケットに対する処理の内容を記述する経路テーブルの構成の一例について説明する。
次に、処理サーバ12において生成される元コンテンツに対する興味パケットの構成の一例について説明する。
以上、本実施の形態によれば、コンテンツデータ取得のリアルタイム性を確保することができるコンテンツ配信システム、サーバ、受信端末および処理方法を実現することができる。
実施の形態1のコンテンツ配信システムでは、受信端末が変換処理後の興味パケットを発行し、変換処理後のコンテンツデータを受信する場合の例について説明した。具体的には、実施の形態1ではFECコンテンツ(元コンテンツとFECによる冗長データを含むコンテンツ)が名前空間のプリフィックス「fec.」「fec/」に対応するとしていたため、受信端末はFEC興味パケットだけを発行し、FECコンテンツデータの受信を行うとして説明した。
図13は、実施の形態2におけるコンテンツ配信システムの処理フローを示すシーケンスである。図13では、受信端末14Aが冗長データと元コンテンツとをそれぞれ別々に受信する場合のコンテンツ配信システムの処理フローが示されている。なお、本実施の形態の受信端末14A、処理サーバ12Aは、FECによる冗長データに対する興味パケット(FEC興味パケット)と元コンテンツに対する興味パケットに対する処理を除いて、実施の形態1の受信端末14と処理サーバ12と同様である。
次に、図14を用いて受信端末14Aが興味パケットとFEC興味パケットとを発行する処理フローについて説明する。
一方、S214においてFEC処理が必要でないと判定された場合(S214でNo)には、元コンテンツデータに対する興味パケットのみを発行する(S217)。ここで、制御部143は、発行時のタイムスタンプを含めて元コンテンツデータに対する興味パケットを発行する。
次に、図15を用いて処理サーバ12Aが冗長データに対するFEC興味パケットを受け取ってから、冗長データに対するFEC興味パケットに対応する冗長データを送出するまでの処理フローについて説明する。なお、この処理フローは、図13におけるS28、S30およびS31の処理を詳細化したものである。
以上、本実施の形態によれば、コンテンツデータ取得のリアルタイム性を確保することができるサーバおよびサーバの処理方法を実現することができる。
実施の形態1および実施の形態2では、処理サーバがコンテンツキャッシュを有しない場合について説明した。実施の形態3では、処理サーバがコンテンツキャッシュを有する場合について説明する。なお、受信端末の構成および動作、各パケットの構成については実施の形態1および実施の形態2に説明した通りであるため、説明を省略する。
本実施の形態の処理サーバ12は、実施の形態1における処理サーバ12に加えて一度受信したコンテンツデータを保存するコンテンツキャッシュを有する。具体的には、処理サーバ12は、さらに、変換処理部122で変換処理を行った元コンテンツデータおよびCCN受信部123で受信した元コンテンツデータのうち少なくとも一方を保持するコンテンツキャッシュを備え、このコンテンツキャッシュは、元コンテンツデータに対する変換処理もしくは変換処理を行ったコンテンツに対する興味パケットに対する返信パケットに利用される。
図16を用いて処理サーバ12が変換処理後の興味パケットを受け取ってから、変換処理後の興味パケットに対応する変換処理後のコンテンツデータを送出するまでの処理フローについて説明する。以下では、変換処理としてFEC処理を行う場合を例に挙げて説明する。
以上、本実施の形態によれば、コンテンツデータ取得のリアルタイム性を確保することができるサーバおよびその処理方法を実現することができる。
実施の形態1、実施の形態2および実施の形態3においてFEC興味パケット等の変換処理後興味パケットの発行は受信端末のみが行うとして説明したがそれに限らない。また変換処理後のコンテンツデータの生成処理については処理サーバが行うとして説明した画それに限らない。
以下、図17を用いてルータ21の詳細構成について説明する。
次に、以上のように構成されたルータ21が変換処理後の興味パケットを発行する処理フローについて説明する。以下では、変換処理としてFEC処理を行う場合を例に挙げて説明する。
以上、本実施の形態によれば、コンテンツデータ取得のリアルタイム性を確保することができるルータおよびその処理方法を実現することができる。
非特許文献1において、コンテンツを所有するルータはOSPFやIS-IS等のルーティングプロトコルを用いて、ルータまでの経路広告を行うことができる技術が開示されている。
図18は、実施の形態5における処理サーバの経路広告パケット発行と経路広告パケットを受信したCCNルータの処理フローを示す図である。
以上、本実施の形態によれば、コンテンツデータ取得のリアルタイム性を確保することができるサーバおよびその処理方法を実現することができる。
11、903、905 CCNルータ
12、12A 処理サーバ
13、904 CCN網
14、14A 受信端末
21 ルータ
43、61 興味パケット
44,45、46、47、71、72 FEC興味パケット
51 経路テーブル
121 サーバ負荷監視部
122、222 変換処理部
123、142、223 CCN受信部
124 サーバ制御部
125、141、225 CCN送信部
143 制御部
144 映像デコーダ
155、226 FEC復号部
224 ルータ制御部
227、907、912 キャッシュ
401~410、413~422 データパケット
411、412、423~428 冗長パケット
431、432、433、441、442、443、451、452、453、454、461、462、463、471、472、473、474、611、612、711、712、713、714、715、721、722、723、724、 フィールド
511 FEC興味パケット情報
512 元コンテンツ興味パケット情報
513 受信フェイス情報
514 送信フェイス情報
901 パブリッシャー
902 コンテンツ
906、911 PIT
908、913 FIB
909 コンテンツ受信者B
910 コンテンツ受信者A
Claims (12)
- CCN(Content Centric Network)網を介し伝送される実時間ストリームに対して処理を行うサーバであって、
前記CCN網によりパケットを取得するCCN受信部と、
前記CCN網にパケットを送信するCCN送信部と、
コンテンツデータに対してリアルタイム性向上のための変換処理を行い、当該変換処理を行った前記コンテンツデータのパケットを生成する変換処理部と、
興味パケットに対する処理の内容を記述する経路テーブルを更新するサーバ制御部と、を備え、
前記サーバ制御部は、
前記CCN受信部が前記変換処理の行われたコンテンツに対する興味パケットを受信した場合には、前記変換処理の処理対象となる前記コンテンツの元コンテンツデータに対する興味パケットを発行して、前記CCN送信部に前記興味パケットを送信させる制御を行い、
前記CCN受信部が前記CCN網から前記処理対象の元コンテンツデータを取得した場合には、前記変換処理部に前記元コンテンツデータに対する前記変換処理を行わせ、当該変換処理を行った前記元コンテンツデータのパケットを生成させ、前記CCN送信部に、前記変換処理の行われたコンテンツに対する興味パケットの返信パケットとして送信させる制御を行う、
サーバ。 - 前記変換処理は、FEC処理であり、
前記変換処理部は、
前記処理対象の元コンテンツデータに対して冗長データを付加することにより、前記FEC処理を行った元コンテンツデータのパケットを生成し、
前記サーバ制御部は、
前記CCN受信部が前記CCN網から前記FEC処理の行われたコンテンツに対する興味パケットを受信した場合には、前記FEC処理の処理対象となる前記コンテンツの元コンテンツデータに対する興味パケットを発行し、
前記CCN受信部が前記CCN網から前記処理対象の元コンテンツデータを取得した場合には、前記変換処理部に前記元コンテンツデータに対する前記FEC処理を行わせ、当該FEC処理を行った前記元コンテンツデータのパケットを生成させる、
請求項1に記載のサーバ。 - 前記変換処理は、トランスコーディング処理であり、
前記変換処理部は、
前記処理対象の元コンテンツデータに対して前記トランスコーディング処理を行い、当該トランスコーディング処理を行った元コンテンツデータのパケットを生成し、
前記サーバ制御部は、
前記CCN受信部が前記CCN網から前記トランスコーディング処理の行われたコンテンツに対する興味パケットを受信した場合には、前記コンテンツの元コンテンツデータに対する興味パケットを発行し、
前記CCN網から前記元コンテンツデータを取得した場合には、前記変換処理部に前記元コンテンツデータに対する前記トランスコーディング処理を行わせ、当該トランスコーディング処理を行った前記元コンテンツデータのパケットを生成させる、
請求項1に記載のサーバ。 - 前記サーバは、さらに、
前記変換処理部で前記変換処理を行った前記元コンテンツデータおよび前記CCN受信部で受信した前記元コンテンツデータのうち少なくとも一方を保持するコンテンツキャッシュを備え、
前記コンテンツキャッシュは、前記元コンテンツデータに対する前記変換処理もしくは前記変換処理を行ったコンテンツに対する興味パケットに対する返信パケットに利用される、
請求項1~3のいずれか1項に記載のサーバ。 - 前記サーバは、さらに、
サーバ負荷を監視するサーバ負荷監視部を備え、
前記サーバ負荷監視部は、サーバ負荷を示す負荷情報を少なくとも含む経路広告パケットを生成し、前記CCN送信部を通じて前記CCN網に送信する、
請求項1~4のいずれか1項に記載のサーバ。 - CCN網を介し伝送される実時間ストリームの伝送を行うルータであって、
前記CCN網によりパケットを取得するCCN受信部と、
前記CCN網にパケットを送信するCCN送信部と、
コンテンツデータに対してリアルタイム性向上のための変換処理を行い、当該変換処理を行った前記コンテンツデータのパケットを生成する変換処理部と、
興味パケットに対する処理の内容を記述する経路テーブルを更新するルータ制御部であって、変換処理の行われた前記コンテンツデータに対する興味パケットまたは前記コンテンツデータの変換処理が行われた冗長部分への興味パケットを生成するルータ制御部と、を備え、
前記ルータ制御部は、
前記CCN受信部が前記変換処理の行われたコンテンツに対する興味パケットを受信した場合には、前記変換処理の処理対象となる前記コンテンツの元コンテンツデータに対する興味パケットを発行して、前記CCN送信部に前記興味パケットを送信させる制御を行い、
前記CCN受信部が前記CCN網から前記処理対象の元コンテンツデータを取得した場合には、前記変換処理部に前記元コンテンツデータに対する前記変換処理を行わせ、当該変換処理を行った前記元コンテンツデータのパケットを生成させ、前記CCN送信部に前記変換処理の行われたコンテンツに対する興味パケットの返信パケットとして送信させる制御を行う、
ルータ。 - 前記変換処理は、FEC処理であり、
前記ルータ制御部は、
前記CCN受信部で受信した前記実時間ストリームに基づき算出した統計情報であってパケット損失率、興味パケット送出からパケット取得までのRTT(Round Trip Time)および実時間ストリーム再生のためのパケット取得時間情報を含む統計情報から、必要なFECの強度を計算し、前記FECの強度でFEC処理が行われた前記コンテンツデータに対する興味パケットまたは前記FECの強度でFEC処理が行われたコンテンツデータの冗長部分への興味パケットを生成する、
請求項6に記載のルータ。 - CCN網を介して実時間ストリームの取得を行う受信端末であって、
前記CCNによりパケットの取得を行うCCN受信部と、
前記CCN受信部で受信した前記実時間ストリームに基づき、必要なFECの強度を計算し、前記FECの強度でFEC処理の行われたコンテンツデータに対する興味パケットまたは前記FECの強度でFEC処理の行われたコンテンツデータの冗長部分への興味パケットを生成する端末制御部と、
前記端末制御部により生成された興味パケットを送信するCCN送信部と、
前記CCN送信部が送信した前記興味パケットに対する返信パケットである前記FEC処理の行われた前記元コンテンツデータまたは前記冗長部分のパケットを復号し、前記元コンテンツデータのパケットロスを修正するFEC復号部と、を備える、
受信端末。 - 前記端末制御部は、
前記CCN受信部で受信した前記実時間ストリームに基づき算出した統計情報であって、パケット損失率、興味パケット送出からパケット取得までのRTTおよび実時間ストリーム再生のためのパケット取得時間情報を含む統計情報から、前記必要なFEC強度を計算する、
請求項8に記載の受信端末。 - CCN網を介し伝送される実時間ストリームに対して処理を行うサーバの処理方法であって、
前記CCN網によりパケットを取得するCCN受信ステップと、
前記CCN網にパケットを送信するCCN送信ステップと、
コンテンツデータに対してリアルタイム性向上のための変換処理を行い、当該変換処理を行った前記コンテンツデータのパケットを生成する変換処理ステップと、
興味パケットに対する処理の内容を記述する経路テーブルを更新するサーバ制御ステップと、を含み、
前記サーバ制御ステップは、
前記CCN受信ステップにおいて前記変換処理の行われたコンテンツに対する興味パケットを受信した場合には、前記変換処理の処理対象となる前記コンテンツの元コンテンツデータに対する興味パケットを発行して、前記CCN送信ステップにおいて前記興味パケットを送信させる制御を行い、
前記CCN受信ステップにおいて前記CCN網から前記処理対象の元コンテンツデータを取得した場合には、前記変換処理ステップに前記元コンテンツデータに対する前記変換処理を行わせ、当該変換処理を行った前記元コンテンツデータのパケットを生成させ、前記CCN送信ステップに、前記変換処理の行われたコンテンツに対する興味パケットの返信パケットとして送信させる制御を行う、
処理方法。 - CCN網を介し伝送される実時間ストリームの伝送を行うルータの処理方法であって、
前記CCN網によりパケットを取得するCCN受信ステップと、
前記CCN網にパケットを送信するCCN送信ステップと、
コンテンツデータに対してリアルタイム性向上のための変換処理を行い、当該変換処理を行った前記コンテンツデータのパケットを生成する変換処理ステップと、
興味パケットに対する処理の内容を記述する経路テーブルを更新するルータ制御ステップであって、変換処理の行われた前記コンテンツデータに対する興味パケットまたは前記コンテンツデータの変換処理が行われた冗長部分への興味パケットを生成するルータ制御ステップと、を含み、
前記ルータ制御ステップは、
前記CCN受信ステップにおいて前記変換処理の行われたコンテンツに対する興味パケットを受信した場合には、前記変換処理の処理対象となる前記コンテンツの元コンテンツデータに対する興味パケットを発行して、前記CCN送信ステップにおいて前記興味パケットを送信させる制御を行い、
前記CCN受信ステップにおいて前記CCN網から前記処理対象の元コンテンツデータを取得した場合には、前記変換処理ステップにおいて前記元コンテンツデータに対する前記変換処理を行わせ、当該変換処理を行った前記元コンテンツデータのパケットを生成させ、前記CCN送信ステップにおいて前記変換処理の行われたコンテンツに対する興味パケットの返信パケットとして送信させる制御を行う、
処理方法。 - CCN網を介して実時間ストリームの取得を行う受信端末の処理方法であって、
前記CCNによりパケットの取得を行うCCN受信ステップと、
前記CCN受信ステップにおいて受信した前記実時間ストリームに基づき、必要なFECの強度を計算し、前記FECの強度でFEC処理の行われたコンテンツデータに対する興味パケットまたは前記FECの強度でFEC処理の行われたコンテンツデータの冗長部分への興味パケットを生成する端末制御ステップと、
前記端末制御ステップにおいて生成された興味パケットを送信するCCN送信ステップと、
前記CCN送信ステップにおいて送信された前記興味パケットに対する返信パケットである前記FEC処理の行われた前記元コンテンツデータまたは前記冗長部分のパケットを復号し、前記元コンテンツデータのパケットロスを修正するFEC復号ステップと、を含む、
処理方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014537392A JP6190376B2 (ja) | 2013-03-26 | 2014-03-14 | サーバ、ルータ、受信端末および処理方法 |
CN201480001274.0A CN104322020B (zh) | 2013-03-26 | 2014-03-14 | 服务器、路由器、接收终端及处理方法 |
US14/402,331 US9781028B2 (en) | 2013-03-26 | 2014-03-14 | Transcoding and dynamic error correction for content centric networks using a proxy server |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-063441 | 2013-03-26 | ||
JP2013063441 | 2013-03-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014156034A1 true WO2014156034A1 (ja) | 2014-10-02 |
Family
ID=51623052
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/001467 WO2014156034A1 (ja) | 2013-03-26 | 2014-03-14 | サーバ、ルータ、受信端末および処理方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9781028B2 (ja) |
JP (1) | JP6190376B2 (ja) |
CN (1) | CN104322020B (ja) |
WO (1) | WO2014156034A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016059022A (ja) * | 2014-09-12 | 2016-04-21 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 端末装置、ゲートウェイ装置および中継装置 |
JP2017022687A (ja) * | 2015-07-09 | 2017-01-26 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 通信制御装置及び通信制御方法 |
CN108605012A (zh) * | 2015-11-18 | 2018-09-28 | 凯迪迪爱通信技术有限公司 | 通信装置以及计算机可读存储介质 |
Families Citing this family (139)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9456054B2 (en) | 2008-05-16 | 2016-09-27 | Palo Alto Research Center Incorporated | Controlling the spread of interests and content in a content centric network |
US8923293B2 (en) | 2009-10-21 | 2014-12-30 | Palo Alto Research Center Incorporated | Adaptive multi-interface use for content networking |
US9280546B2 (en) | 2012-10-31 | 2016-03-08 | Palo Alto Research Center Incorporated | System and method for accessing digital content using a location-independent name |
US9400800B2 (en) | 2012-11-19 | 2016-07-26 | Palo Alto Research Center Incorporated | Data transport by named content synchronization |
US10430839B2 (en) | 2012-12-12 | 2019-10-01 | Cisco Technology, Inc. | Distributed advertisement insertion in content-centric networks |
US9978025B2 (en) | 2013-03-20 | 2018-05-22 | Cisco Technology, Inc. | Ordered-element naming for name-based packet forwarding |
US9935791B2 (en) | 2013-05-20 | 2018-04-03 | Cisco Technology, Inc. | Method and system for name resolution across heterogeneous architectures |
US9444722B2 (en) | 2013-08-01 | 2016-09-13 | Palo Alto Research Center Incorporated | Method and apparatus for configuring routing paths in a custodian-based routing architecture |
US9407549B2 (en) | 2013-10-29 | 2016-08-02 | Palo Alto Research Center Incorporated | System and method for hash-based forwarding of packets with hierarchically structured variable-length identifiers |
US9276840B2 (en) * | 2013-10-30 | 2016-03-01 | Palo Alto Research Center Incorporated | Interest messages with a payload for a named data network |
US9401864B2 (en) | 2013-10-31 | 2016-07-26 | Palo Alto Research Center Incorporated | Express header for packets with hierarchically structured variable-length identifiers |
KR102131699B1 (ko) * | 2013-11-07 | 2020-07-08 | 삼성전자주식회사 | 컨텐츠 송신기 및 컨텐츠 수신기와, 컨텐츠 송신 방법 및 컨텐츠 수신 방법 |
US10101801B2 (en) | 2013-11-13 | 2018-10-16 | Cisco Technology, Inc. | Method and apparatus for prefetching content in a data stream |
US10129365B2 (en) | 2013-11-13 | 2018-11-13 | Cisco Technology, Inc. | Method and apparatus for pre-fetching remote content based on static and dynamic recommendations |
US9311377B2 (en) | 2013-11-13 | 2016-04-12 | Palo Alto Research Center Incorporated | Method and apparatus for performing server handoff in a name-based content distribution system |
US10089655B2 (en) | 2013-11-27 | 2018-10-02 | Cisco Technology, Inc. | Method and apparatus for scalable data broadcasting |
US9503358B2 (en) | 2013-12-05 | 2016-11-22 | Palo Alto Research Center Incorporated | Distance-based routing in an information-centric network |
US9379979B2 (en) | 2014-01-14 | 2016-06-28 | Palo Alto Research Center Incorporated | Method and apparatus for establishing a virtual interface for a set of mutual-listener devices |
US10098051B2 (en) | 2014-01-22 | 2018-10-09 | Cisco Technology, Inc. | Gateways and routing in software-defined manets |
US10172068B2 (en) | 2014-01-22 | 2019-01-01 | Cisco Technology, Inc. | Service-oriented routing in software-defined MANETs |
US9374304B2 (en) | 2014-01-24 | 2016-06-21 | Palo Alto Research Center Incorporated | End-to end route tracing over a named-data network |
US9954678B2 (en) | 2014-02-06 | 2018-04-24 | Cisco Technology, Inc. | Content-based transport security |
US9678998B2 (en) | 2014-02-28 | 2017-06-13 | Cisco Technology, Inc. | Content name resolution for information centric networking |
US10089651B2 (en) | 2014-03-03 | 2018-10-02 | Cisco Technology, Inc. | Method and apparatus for streaming advertisements in a scalable data broadcasting system |
US9836540B2 (en) | 2014-03-04 | 2017-12-05 | Cisco Technology, Inc. | System and method for direct storage access in a content-centric network |
US9473405B2 (en) | 2014-03-10 | 2016-10-18 | Palo Alto Research Center Incorporated | Concurrent hashes and sub-hashes on data streams |
US9391896B2 (en) | 2014-03-10 | 2016-07-12 | Palo Alto Research Center Incorporated | System and method for packet forwarding using a conjunctive normal form strategy in a content-centric network |
US9626413B2 (en) | 2014-03-10 | 2017-04-18 | Cisco Systems, Inc. | System and method for ranking content popularity in a content-centric network |
US9407432B2 (en) | 2014-03-19 | 2016-08-02 | Palo Alto Research Center Incorporated | System and method for efficient and secure distribution of digital content |
US9916601B2 (en) | 2014-03-21 | 2018-03-13 | Cisco Technology, Inc. | Marketplace for presenting advertisements in a scalable data broadcasting system |
US9363179B2 (en) | 2014-03-26 | 2016-06-07 | Palo Alto Research Center Incorporated | Multi-publisher routing protocol for named data networks |
US10063476B2 (en) * | 2014-03-28 | 2018-08-28 | Research & Business Foundation Sungkyunkwan University | Content centric networking system providing differentiated service and method of controlling data traffic in content centric networking providing differentiated service |
US9363086B2 (en) | 2014-03-31 | 2016-06-07 | Palo Alto Research Center Incorporated | Aggregate signing of data in content centric networking |
US9716622B2 (en) | 2014-04-01 | 2017-07-25 | Cisco Technology, Inc. | System and method for dynamic name configuration in content-centric networks |
US9390289B2 (en) | 2014-04-07 | 2016-07-12 | Palo Alto Research Center Incorporated | Secure collection synchronization using matched network names |
US10075521B2 (en) | 2014-04-07 | 2018-09-11 | Cisco Technology, Inc. | Collection synchronization using equality matched network names |
US9451032B2 (en) | 2014-04-10 | 2016-09-20 | Palo Alto Research Center Incorporated | System and method for simple service discovery in content-centric networks |
US9992281B2 (en) * | 2014-05-01 | 2018-06-05 | Cisco Technology, Inc. | Accountable content stores for information centric networks |
US9609014B2 (en) | 2014-05-22 | 2017-03-28 | Cisco Systems, Inc. | Method and apparatus for preventing insertion of malicious content at a named data network router |
US9455835B2 (en) | 2014-05-23 | 2016-09-27 | Palo Alto Research Center Incorporated | System and method for circular link resolution with hash-based names in content-centric networks |
US9276751B2 (en) | 2014-05-28 | 2016-03-01 | Palo Alto Research Center Incorporated | System and method for circular link resolution with computable hash-based names in content-centric networks |
US9825860B2 (en) * | 2014-05-30 | 2017-11-21 | Futurewei Technologies, Inc. | Flow-driven forwarding architecture for information centric networks |
US9537719B2 (en) | 2014-06-19 | 2017-01-03 | Palo Alto Research Center Incorporated | Method and apparatus for deploying a minimal-cost CCN topology |
US9516144B2 (en) | 2014-06-19 | 2016-12-06 | Palo Alto Research Center Incorporated | Cut-through forwarding of CCNx message fragments with IP encapsulation |
US9426113B2 (en) | 2014-06-30 | 2016-08-23 | Palo Alto Research Center Incorporated | System and method for managing devices over a content centric network |
US9699198B2 (en) | 2014-07-07 | 2017-07-04 | Cisco Technology, Inc. | System and method for parallel secure content bootstrapping in content-centric networks |
US9959156B2 (en) | 2014-07-17 | 2018-05-01 | Cisco Technology, Inc. | Interest return control message |
US9621354B2 (en) | 2014-07-17 | 2017-04-11 | Cisco Systems, Inc. | Reconstructable content objects |
US9729616B2 (en) | 2014-07-18 | 2017-08-08 | Cisco Technology, Inc. | Reputation-based strategy for forwarding and responding to interests over a content centric network |
US9590887B2 (en) | 2014-07-18 | 2017-03-07 | Cisco Systems, Inc. | Method and system for keeping interest alive in a content centric network |
US9535968B2 (en) | 2014-07-21 | 2017-01-03 | Palo Alto Research Center Incorporated | System for distributing nameless objects using self-certifying names |
US9882964B2 (en) | 2014-08-08 | 2018-01-30 | Cisco Technology, Inc. | Explicit strategy feedback in name-based forwarding |
US9503365B2 (en) | 2014-08-11 | 2016-11-22 | Palo Alto Research Center Incorporated | Reputation-based instruction processing over an information centric network |
US9729662B2 (en) | 2014-08-11 | 2017-08-08 | Cisco Technology, Inc. | Probabilistic lazy-forwarding technique without validation in a content centric network |
US9391777B2 (en) | 2014-08-15 | 2016-07-12 | Palo Alto Research Center Incorporated | System and method for performing key resolution over a content centric network |
US9467492B2 (en) | 2014-08-19 | 2016-10-11 | Palo Alto Research Center Incorporated | System and method for reconstructable all-in-one content stream |
US9800637B2 (en) | 2014-08-19 | 2017-10-24 | Cisco Technology, Inc. | System and method for all-in-one content stream in content-centric networks |
US9497282B2 (en) | 2014-08-27 | 2016-11-15 | Palo Alto Research Center Incorporated | Network coding for content-centric network |
US10204013B2 (en) | 2014-09-03 | 2019-02-12 | Cisco Technology, Inc. | System and method for maintaining a distributed and fault-tolerant state over an information centric network |
US9553812B2 (en) | 2014-09-09 | 2017-01-24 | Palo Alto Research Center Incorporated | Interest keep alives at intermediate routers in a CCN |
US10193662B2 (en) * | 2014-09-19 | 2019-01-29 | Panasonic Intellectual Property Corporation Of America | Router, terminal, and congestion control method for router and terminal |
US10069933B2 (en) | 2014-10-23 | 2018-09-04 | Cisco Technology, Inc. | System and method for creating virtual interfaces based on network characteristics |
US9590948B2 (en) | 2014-12-15 | 2017-03-07 | Cisco Systems, Inc. | CCN routing using hardware-assisted hash tables |
US9536059B2 (en) | 2014-12-15 | 2017-01-03 | Palo Alto Research Center Incorporated | Method and system for verifying renamed content using manifests in a content centric network |
US10237189B2 (en) | 2014-12-16 | 2019-03-19 | Cisco Technology, Inc. | System and method for distance-based interest forwarding |
US9846881B2 (en) | 2014-12-19 | 2017-12-19 | Palo Alto Research Center Incorporated | Frugal user engagement help systems |
US10003520B2 (en) | 2014-12-22 | 2018-06-19 | Cisco Technology, Inc. | System and method for efficient name-based content routing using link-state information in information-centric networks |
US9473475B2 (en) | 2014-12-22 | 2016-10-18 | Palo Alto Research Center Incorporated | Low-cost authenticated signing delegation in content centric networking |
US9660825B2 (en) | 2014-12-24 | 2017-05-23 | Cisco Technology, Inc. | System and method for multi-source multicasting in content-centric networks |
US9602596B2 (en) | 2015-01-12 | 2017-03-21 | Cisco Systems, Inc. | Peer-to-peer sharing in a content centric network |
US9946743B2 (en) | 2015-01-12 | 2018-04-17 | Cisco Technology, Inc. | Order encoded manifests in a content centric network |
US9916457B2 (en) | 2015-01-12 | 2018-03-13 | Cisco Technology, Inc. | Decoupled name security binding for CCN objects |
US9954795B2 (en) | 2015-01-12 | 2018-04-24 | Cisco Technology, Inc. | Resource allocation using CCN manifests |
US9832291B2 (en) | 2015-01-12 | 2017-11-28 | Cisco Technology, Inc. | Auto-configurable transport stack |
US9462006B2 (en) | 2015-01-21 | 2016-10-04 | Palo Alto Research Center Incorporated | Network-layer application-specific trust model |
US9552493B2 (en) | 2015-02-03 | 2017-01-24 | Palo Alto Research Center Incorporated | Access control framework for information centric networking |
US10333840B2 (en) | 2015-02-06 | 2019-06-25 | Cisco Technology, Inc. | System and method for on-demand content exchange with adaptive naming in information-centric networks |
US9736263B2 (en) | 2015-02-16 | 2017-08-15 | Telefonaktiebolaget L M Ericsson (Publ) | Temporal caching for ICN |
US10075401B2 (en) | 2015-03-18 | 2018-09-11 | Cisco Technology, Inc. | Pending interest table behavior |
US9819892B2 (en) * | 2015-05-21 | 2017-11-14 | Semtech Canada Corporation | Error correction data in a video transmission signal |
US10116605B2 (en) | 2015-06-22 | 2018-10-30 | Cisco Technology, Inc. | Transport stack name scheme and identity management |
US10075402B2 (en) | 2015-06-24 | 2018-09-11 | Cisco Technology, Inc. | Flexible command and control in content centric networks |
US10701038B2 (en) | 2015-07-27 | 2020-06-30 | Cisco Technology, Inc. | Content negotiation in a content centric network |
US9986034B2 (en) | 2015-08-03 | 2018-05-29 | Cisco Technology, Inc. | Transferring state in content centric network stacks |
US10610144B2 (en) | 2015-08-19 | 2020-04-07 | Palo Alto Research Center Incorporated | Interactive remote patient monitoring and condition management intervention system |
US9832123B2 (en) | 2015-09-11 | 2017-11-28 | Cisco Technology, Inc. | Network named fragments in a content centric network |
US10355999B2 (en) | 2015-09-23 | 2019-07-16 | Cisco Technology, Inc. | Flow control with network named fragments |
US9977809B2 (en) | 2015-09-24 | 2018-05-22 | Cisco Technology, Inc. | Information and data framework in a content centric network |
US10313227B2 (en) | 2015-09-24 | 2019-06-04 | Cisco Technology, Inc. | System and method for eliminating undetected interest looping in information-centric networks |
US10454820B2 (en) | 2015-09-29 | 2019-10-22 | Cisco Technology, Inc. | System and method for stateless information-centric networking |
US10263965B2 (en) | 2015-10-16 | 2019-04-16 | Cisco Technology, Inc. | Encrypted CCNx |
US9794238B2 (en) | 2015-10-29 | 2017-10-17 | Cisco Technology, Inc. | System for key exchange in a content centric network |
US10009446B2 (en) | 2015-11-02 | 2018-06-26 | Cisco Technology, Inc. | Header compression for CCN messages using dictionary learning |
US9807205B2 (en) | 2015-11-02 | 2017-10-31 | Cisco Technology, Inc. | Header compression for CCN messages using dictionary |
US10021222B2 (en) | 2015-11-04 | 2018-07-10 | Cisco Technology, Inc. | Bit-aligned header compression for CCN messages using dictionary |
US10097521B2 (en) | 2015-11-20 | 2018-10-09 | Cisco Technology, Inc. | Transparent encryption in a content centric network |
US10356209B2 (en) * | 2015-11-30 | 2019-07-16 | Futurewei Technologies, Inc. | System and method to support context-aware content requests in information centric networks |
US9912776B2 (en) | 2015-12-02 | 2018-03-06 | Cisco Technology, Inc. | Explicit content deletion commands in a content centric network |
US10097346B2 (en) | 2015-12-09 | 2018-10-09 | Cisco Technology, Inc. | Key catalogs in a content centric network |
US10078062B2 (en) | 2015-12-15 | 2018-09-18 | Palo Alto Research Center Incorporated | Device health estimation by combining contextual information with sensor data |
US10257271B2 (en) | 2016-01-11 | 2019-04-09 | Cisco Technology, Inc. | Chandra-Toueg consensus in a content centric network |
US9949301B2 (en) | 2016-01-20 | 2018-04-17 | Palo Alto Research Center Incorporated | Methods for fast, secure and privacy-friendly internet connection discovery in wireless networks |
US10305864B2 (en) | 2016-01-25 | 2019-05-28 | Cisco Technology, Inc. | Method and system for interest encryption in a content centric network |
US10043016B2 (en) | 2016-02-29 | 2018-08-07 | Cisco Technology, Inc. | Method and system for name encryption agreement in a content centric network |
US10742596B2 (en) | 2016-03-04 | 2020-08-11 | Cisco Technology, Inc. | Method and system for reducing a collision probability of hash-based names using a publisher identifier |
US10003507B2 (en) | 2016-03-04 | 2018-06-19 | Cisco Technology, Inc. | Transport session state protocol |
US10038633B2 (en) | 2016-03-04 | 2018-07-31 | Cisco Technology, Inc. | Protocol to query for historical network information in a content centric network |
US10051071B2 (en) | 2016-03-04 | 2018-08-14 | Cisco Technology, Inc. | Method and system for collecting historical network information in a content centric network |
US9832116B2 (en) | 2016-03-14 | 2017-11-28 | Cisco Technology, Inc. | Adjusting entries in a forwarding information base in a content centric network |
US10212196B2 (en) | 2016-03-16 | 2019-02-19 | Cisco Technology, Inc. | Interface discovery and authentication in a name-based network |
US11436656B2 (en) | 2016-03-18 | 2022-09-06 | Palo Alto Research Center Incorporated | System and method for a real-time egocentric collaborative filter on large datasets |
US10067948B2 (en) | 2016-03-18 | 2018-09-04 | Cisco Technology, Inc. | Data deduping in content centric networking manifests |
US10091330B2 (en) | 2016-03-23 | 2018-10-02 | Cisco Technology, Inc. | Interest scheduling by an information and data framework in a content centric network |
US10033639B2 (en) | 2016-03-25 | 2018-07-24 | Cisco Technology, Inc. | System and method for routing packets in a content centric network using anonymous datagrams |
US10320760B2 (en) | 2016-04-01 | 2019-06-11 | Cisco Technology, Inc. | Method and system for mutating and caching content in a content centric network |
US9930146B2 (en) | 2016-04-04 | 2018-03-27 | Cisco Technology, Inc. | System and method for compressing content centric networking messages |
US10425503B2 (en) | 2016-04-07 | 2019-09-24 | Cisco Technology, Inc. | Shared pending interest table in a content centric network |
US10027578B2 (en) | 2016-04-11 | 2018-07-17 | Cisco Technology, Inc. | Method and system for routable prefix queries in a content centric network |
US10404450B2 (en) | 2016-05-02 | 2019-09-03 | Cisco Technology, Inc. | Schematized access control in a content centric network |
US10320675B2 (en) | 2016-05-04 | 2019-06-11 | Cisco Technology, Inc. | System and method for routing packets in a stateless content centric network |
US10547589B2 (en) | 2016-05-09 | 2020-01-28 | Cisco Technology, Inc. | System for implementing a small computer systems interface protocol over a content centric network |
US10063414B2 (en) | 2016-05-13 | 2018-08-28 | Cisco Technology, Inc. | Updating a transport stack in a content centric network |
US10084764B2 (en) | 2016-05-13 | 2018-09-25 | Cisco Technology, Inc. | System for a secure encryption proxy in a content centric network |
US10798186B2 (en) | 2016-06-09 | 2020-10-06 | International Business Machines Corporation | Dynamic generation of network routing configuration with service requirements |
US10103989B2 (en) | 2016-06-13 | 2018-10-16 | Cisco Technology, Inc. | Content object return messages in a content centric network |
US10305865B2 (en) | 2016-06-21 | 2019-05-28 | Cisco Technology, Inc. | Permutation-based content encryption with manifests in a content centric network |
US10148572B2 (en) | 2016-06-27 | 2018-12-04 | Cisco Technology, Inc. | Method and system for interest groups in a content centric network |
US10009266B2 (en) | 2016-07-05 | 2018-06-26 | Cisco Technology, Inc. | Method and system for reference counted pending interest tables in a content centric network |
US9992097B2 (en) * | 2016-07-11 | 2018-06-05 | Cisco Technology, Inc. | System and method for piggybacking routing information in interests in a content centric network |
US10122624B2 (en) | 2016-07-25 | 2018-11-06 | Cisco Technology, Inc. | System and method for ephemeral entries in a forwarding information base in a content centric network |
JP6674856B2 (ja) * | 2016-07-27 | 2020-04-01 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 通信制御装置、通信制御方法及び通信制御システム |
US10069729B2 (en) | 2016-08-08 | 2018-09-04 | Cisco Technology, Inc. | System and method for throttling traffic based on a forwarding information base in a content centric network |
US10956412B2 (en) | 2016-08-09 | 2021-03-23 | Cisco Technology, Inc. | Method and system for conjunctive normal form attribute matching in a content centric network |
US10033642B2 (en) | 2016-09-19 | 2018-07-24 | Cisco Technology, Inc. | System and method for making optimal routing decisions based on device-specific parameters in a content centric network |
US10212248B2 (en) | 2016-10-03 | 2019-02-19 | Cisco Technology, Inc. | Cache management on high availability routers in a content centric network |
US10447805B2 (en) | 2016-10-10 | 2019-10-15 | Cisco Technology, Inc. | Distributed consensus in a content centric network |
US10135948B2 (en) | 2016-10-31 | 2018-11-20 | Cisco Technology, Inc. | System and method for process migration in a content centric network |
US10243851B2 (en) | 2016-11-21 | 2019-03-26 | Cisco Technology, Inc. | System and method for forwarder connection information in a content centric network |
KR102162350B1 (ko) * | 2019-02-14 | 2020-10-06 | 국방과학연구소 | 다중 통신 제어 장치 및 방법 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011010688A1 (ja) * | 2009-07-22 | 2011-01-27 | 日本電気株式会社 | コンテンツ配信システム、コンテンツ配信方法、コンテンツ配信プログラム |
WO2011049193A1 (ja) * | 2009-10-23 | 2011-04-28 | 日本電気株式会社 | 配信システム、ゲートウェイ、配信方法及びプログラム |
JP2012018525A (ja) * | 2010-07-07 | 2012-01-26 | Fujitsu Ltd | コンテンツ変換プログラム、コンテンツ変換システム及びコンテンツ変換サーバ |
WO2012088023A2 (en) * | 2010-12-20 | 2012-06-28 | Akamai Technologies, Inc. | Methods and systems for delivering content to differentiated client devices |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8510468B2 (en) * | 2000-04-17 | 2013-08-13 | Ciradence Corporation | Route aware network link acceleration |
US7639739B2 (en) * | 2001-11-02 | 2009-12-29 | The Regents Of The University Of California | Technique to enable efficient adaptive streaming and transcoding of video and other signals |
JP2004221756A (ja) * | 2003-01-10 | 2004-08-05 | Sony Corp | 情報処理装置および情報処理方法、並びにコンピュータ・プログラム |
US7856585B2 (en) * | 2004-01-28 | 2010-12-21 | Nec Corporation | Content distribution method, encoding method, reception/reproduction method and apparatus, and program |
WO2006066632A1 (en) * | 2004-12-24 | 2006-06-29 | Telecom Italia S.P.A. | Media transcoding in multimedia delivery services |
JP4513725B2 (ja) * | 2005-11-09 | 2010-07-28 | ソニー株式会社 | パケット送信装置、通信システム及びプログラム |
US9209934B2 (en) * | 2006-06-09 | 2015-12-08 | Qualcomm Incorporated | Enhanced block-request streaming using cooperative parallel HTTP and forward error correction |
US7774672B2 (en) * | 2006-07-07 | 2010-08-10 | Scientific-Atlanta, Llc | Requesting additional forward error correction |
US8091011B2 (en) * | 2007-10-09 | 2012-01-03 | Broadcom Corporation | Method and system for dynamically adjusting forward error correction (FEC) rate to adapt for time varying network impairments in video streaming applications over IP networks |
US8375436B2 (en) * | 2010-04-22 | 2013-02-12 | Palo Alto Research Center Incorporated | Session migration over content-centric networks |
JP2012049640A (ja) * | 2010-08-24 | 2012-03-08 | Osaka Univ | 符号化装置、符号化方法、動画像伝送システム |
KR20120070410A (ko) | 2010-12-21 | 2012-06-29 | 한국전자통신연구원 | 통신 노드 및 통신 방법 |
US9191459B2 (en) * | 2011-07-12 | 2015-11-17 | Futurewei Technologies, Inc. | Method and apparatus for seamless mobility techniques in content-centric network |
KR20130008325A (ko) * | 2011-07-12 | 2013-01-22 | 삼성전자주식회사 | 컨텐츠 중심 네트워크에서 컨텐츠 요청자, 중간 노드 및 컨텐츠 소유자의 통신 방법 |
US8837511B2 (en) * | 2011-08-12 | 2014-09-16 | Futurewei Technologies, Inc. | Seamless mobility schemes in names-data networking using multi-path routing and content caching |
US20130301415A1 (en) * | 2011-09-29 | 2013-11-14 | Avvasi Inc. | Methods and systems for managing media traffic based on network conditions |
KR20130048032A (ko) * | 2011-11-01 | 2013-05-09 | 한국전자통신연구원 | 컨텐츠 중심 네트워크에서 라우팅 방법 |
KR101913313B1 (ko) * | 2011-12-28 | 2018-10-31 | 삼성전자주식회사 | 게이트웨이에서 인터넷 프로토콜 기반 네트워크를 이용하여 컨텐츠 중심 네트워크를 구현하는 방법 및 그 게이트웨이 |
US20130219038A1 (en) * | 2012-02-17 | 2013-08-22 | Electronics And Telecommunications Research Institute | Router based on core score and method for setting core score and providing and searching content information therein |
CA2791935A1 (en) * | 2012-03-30 | 2013-09-30 | Disternet Technology, Inc. | Transcoding system and method |
US8891541B2 (en) * | 2012-07-20 | 2014-11-18 | International Business Machines Corporation | Systems, methods and algorithms for named data network routing with path labeling |
CN104704794B (zh) * | 2012-10-05 | 2018-06-08 | 诺基亚技术有限公司 | 用于代理在内容中心网络和互联网域之间的通信的方法 |
US9426053B2 (en) * | 2012-12-06 | 2016-08-23 | International Business Machines Corporation | Aliasing of named data objects and named graphs for named data networks |
US8965845B2 (en) * | 2012-12-07 | 2015-02-24 | International Business Machines Corporation | Proactive data object replication in named data networks |
US9049252B2 (en) * | 2012-12-17 | 2015-06-02 | International Business Machines Corporation | Efficient name management for named data networking in datacenter networks |
-
2014
- 2014-03-14 CN CN201480001274.0A patent/CN104322020B/zh active Active
- 2014-03-14 JP JP2014537392A patent/JP6190376B2/ja active Active
- 2014-03-14 US US14/402,331 patent/US9781028B2/en active Active
- 2014-03-14 WO PCT/JP2014/001467 patent/WO2014156034A1/ja active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011010688A1 (ja) * | 2009-07-22 | 2011-01-27 | 日本電気株式会社 | コンテンツ配信システム、コンテンツ配信方法、コンテンツ配信プログラム |
WO2011049193A1 (ja) * | 2009-10-23 | 2011-04-28 | 日本電気株式会社 | 配信システム、ゲートウェイ、配信方法及びプログラム |
JP2012018525A (ja) * | 2010-07-07 | 2012-01-26 | Fujitsu Ltd | コンテンツ変換プログラム、コンテンツ変換システム及びコンテンツ変換サーバ |
WO2012088023A2 (en) * | 2010-12-20 | 2012-06-28 | Akamai Technologies, Inc. | Methods and systems for delivering content to differentiated client devices |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016059022A (ja) * | 2014-09-12 | 2016-04-21 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 端末装置、ゲートウェイ装置および中継装置 |
JP2017022687A (ja) * | 2015-07-09 | 2017-01-26 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 通信制御装置及び通信制御方法 |
CN108605012A (zh) * | 2015-11-18 | 2018-09-28 | 凯迪迪爱通信技术有限公司 | 通信装置以及计算机可读存储介质 |
CN108605012B (zh) * | 2015-11-18 | 2020-11-03 | 凯迪迪爱通信技术有限公司 | 通信装置以及计算机可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20150095481A1 (en) | 2015-04-02 |
JPWO2014156034A1 (ja) | 2017-02-16 |
JP6190376B2 (ja) | 2017-08-30 |
CN104322020B (zh) | 2019-01-01 |
CN104322020A (zh) | 2015-01-28 |
US9781028B2 (en) | 2017-10-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6190376B2 (ja) | サーバ、ルータ、受信端末および処理方法 | |
US10798199B2 (en) | Network traffic accelerator | |
CN104662865B (zh) | 混合型http和udp内容分发 | |
JP6966542B2 (ja) | ライブビデオ送信方法およびシステムならびに装置 | |
JP4536383B2 (ja) | データ受信装置およびデータ受信方法 | |
US9959156B2 (en) | Interest return control message | |
US7159108B2 (en) | Anonymous peer-to-peer networking | |
KR20140009931A (ko) | 컨텐츠 이름 기반의 컨텐츠 중심 네트워크에서 컨텐츠 및 실시간 스트리밍 컨텐츠 제공을 위한 컨텐츠 요청자 및 컨텐츠 제공자의 통신 방법 | |
JP6344474B2 (ja) | Delay−Tolerant network(DTN)内でのデータ配送のための装置及び方法 | |
GB2423219B (en) | A network proxy client, a communication system and a method for providing a service between a server and an end client | |
JP2014520422A5 (ja) | ||
US10355999B2 (en) | Flow control with network named fragments | |
KR20160027910A (ko) | Ccn 파이프라인 스트림의 신뢰도있는 컨텐츠 교환 방법 및 시스템 | |
JP2006119738A (ja) | 電子メール送信システム | |
JP2007228064A (ja) | ネットワークシステムおよび通信装置 | |
JP2016066999A (ja) | ルータ、端末、およびそれらの輻輳制御方法 | |
JP2012151622A (ja) | 受信端末、パケットデータ受信方法、送信端末、送受信システム、中継端末およびパケットデータの中継方法 | |
JP2010034898A (ja) | データ送信装置及びデータ送信方法 | |
JP2008131599A (ja) | キャスト伝送装置及びキャスト伝送方法 | |
US9306824B2 (en) | Communication control apparatus, communication control method, and computer-readable non-transitory recording medium | |
JP2008092213A (ja) | 受信機、パケット再送方法及びプログラム | |
CN105321097B (zh) | 使消费者状态与内容中心网络中的兴趣相关联 | |
US20240205002A1 (en) | Method of checking segments in a peer-to-peer network | |
JP6875474B2 (ja) | 通信システムおよび通信方法 | |
Ivković et al. | An ad-hoc smartphone-to-smartphone live multimedia streaming application with real-time constraints |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2014537392 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14774110 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14402331 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14774110 Country of ref document: EP Kind code of ref document: A1 |