as shown in fig1 , it is assumed for simplicity that a network including a repeater 1 connects a server device 2 and a client device 3 . at the request of the client device 3 , the server device 2 starts sending streaming packets of a requested content to the client device 3 through the repeater 1 in the network . the network is typically the internet . a streaming packet flowing from the server device 2 downstream to the client device 3 is buffered in the repeater 1 so as to adjust sending timing of the received streaming packet . although only one flow of streaming packets for the content is shown in fig1 for simplicity , the repeater 1 according to the present invention is allowed to individually buffer a plurality of flows . the details of the repeater 1 will be described later . the streaming packets buffered in the repeater 1 are sent to the client device 3 in adjusted timing . the client device 3 buffers streaming packet before it starts reproducing it to absorb delay variation in packet transmission . in this manner , the requested real - time content is played by a predetermined application in the client device 3 without interrupted sound or motion . since the repeater 1 temporarily buffers streaming packets received from the server device 2 , high - quality play of the delivered content at the client device 3 can be obtained even if the client device 3 has a relatively small capacity of a buffer provided therein . in addition , the client device 3 may send a reception condition notification packet back to the server side . when receiving the notification packet , the repeater 1 adjusts the packet buffering time depending on the reception condition of the client device 3 . referring to fig2 , the repeater 1 is provided with a packet analyzer 101 , a header analyzer 102 , a packet memory 103 , a flow registration table 104 , a packet manager , a packet sending controller , a server - to - client ( downstream ) signal reception terminal 107 , a client - to - server ( upstream ) signal reception terminal 108 , a server - to - client signal sending terminal 109 and a client - to - server signal sending terminal 110 . the packet analyzer 101 , when receiving a packet from the reception terminal 107 or 108 , determines whether the received packet is a streaming packet or a feedback information packet related to a flow registered in the flow registration table 104 . when it is a streaming packet or a feedback information packet , the packet analyzer 101 transfers it to the header analyzer 102 . when it is neither a streaming packet nor a feedback information packet , the packet analyzer 101 forwards it to a selected one of the server - to - client sending terminal 109 and the client - to - server sending terminal 110 depending on its destination address . further , as described in detail later , the packet analyzer 101 registers the address and port number of a streaming flow in the flow registration table 104 depending on whether the received packet uses a port number that is used by streaming transmission control protocol or is conventionally used by a streaming transmission application . the header analyzer 102 analyzes the header of the received streaming packet and notifies the packet manager 105 of information of the received packet such as a sequential number and a time stamp indicating a time instant of the server device 2 sending it . the packet memory 103 buffers streaming packets input from the header analyzer 102 and queues streaming packets for each flow until a sending instruction for a flow has been received from the packet sending controller 106 . a flow is defined as a set of packets related to a certain content transferring between a server device 2 and a client device 3 . the flow registration table 104 contains information related to each streaming flow in table form as shown in fig4 , which will be described in detail later . the packet manager 105 inputs the information of the received streaming packet from the header analyzer 102 and registers it for each flow into the flow registration table 104 . the packet manager 105 also outputs a packet sending instruction for each flow to the packet sending controller 106 when the time to send has come . the packet sending controller 106 , when receiving a packet sending instruction for a certain flow from the packet manager 105 , reads a head packet of a queue for the flow from the packet memory 103 and forwards it to the server - to - client signal sending terminal 109 . a packet sent from the server device 2 toward the client device 3 is received at the server - to - client signal reception terminal 107 and is forwarded to the packet analyzer 101 . a packet sent from the client device 3 toward the server device 2 is received at the client - to - server signal reception terminal 108 and is forwarded to the packet analyzer 101 . a packet output from one of the packet analyzer 101 and the packet sending controller 106 is sent from the server - to - client signal sending terminal 109 toward the client device 3 . a packet output from the packet analyzer 101 is sent from the client - to - server signal sending terminal 110 toward the server device 2 . referring to fig3 a , the server device 2 is provided with an application 21 and a communication terminal 22 through which packets are sent and received to and from the client device 3 . the application 21 allowing streaming packets to be sent to a client device corresponds to an application for processing streaming packets to play installed in the client device 3 . referring to fig3 b , the client device 3 is provided with a reception condition notifying section 31 , an application 32 , and a communication terminal 33 . the application 32 corresponds to the application 21 of the server device 2 and is designed to process streaming packets to play sound and video of the requested content . as described before , the application 32 is provided with a buffer for absorbing delay variations in packet transmission . the reception condition notifying section 31 calculates a difference between packet arrival timing and play timing of streaming packets processed by the application 32 . based on the calculated timing difference , the reception condition notifying section 31 produces a reception condition indicating the capacity of the buffer provided in the application 32 and the amount of available capacity thereof , and sends a reception condition notification packet carrying the reception condition as feedback information to the repeater 1 through the communication terminal 33 . assuming that the server device 2 sends streaming packets to the client device 3 through the repeater 1 in the network , an operation of the repeater 1 will be described hereinafter . in the above - described repeater 1 , when a packet is received at the server - to - client signal reception terminal 107 , the received packet is forwarded to the packet analyzer 101 . when receiving the packet , the packet analyzer 101 searches the flow registration table 104 for the destination address and port number ( flow identifying information ) of the received packet to determine whether the received packet is a streaming packet of a flow registered in the flow registration table 104 . further , in order to register the address and port number of a streaming flow in the flow registration table 104 , the packet analyzer 101 determines whether the received packet uses a port number that is used by the streaming transmission control protocol ( e . g . rtsp , port number 554 ) or is conventionally used by a streaming transmission application ( e . g . port number 6970 in a streaming transmission system realsystem ™ of realnetworks ). when a packet conforming to the streaming transmission control protocol has been received , the packet analyzer 101 analyzes the contents of the received packet to obtain information of address and port number used in streaming transmission . when a packet using a port number for conventional streaming transmission has been received , the packet analyzer 101 obtains information of address and port number of the received packet . in this manner , the packet analyzer 101 registers a pair of address and port number for each of source and destination into the flow registration table 104 ( see fig5 ). this method allows streaming data to be extracted from received various packets in the network such as an ip network transferring various kinds of packets . the packet analyzer 101 searches the flow registration table 104 for the destination address and port number of the received packet and , when a match is found ( that is , when it is a streaming packet ), the packet analyzer 101 transfers it to the header analyzer 102 . when it is not a streaming packet , the packet analyzer 101 forwards it to a selected one of the server - to - client sending terminal 109 and the client - to - server sending terminal 110 depending on its destination address . in other words , the repeater 1 plays a role as an ordinary repeater . in the case of a packet using a port number for conventional streaming transmission , it has not been registered in the flow registration table 104 but it is a streaming packet . accordingly , it is forwarded to the header analyzer 102 . in the case of a packet conforming to the streaming transmission control protocol , the contents of the packet is analyzed and registered in the flow registration table 104 and then is forwarded to a selected one of the server - to - client sending terminal 109 and the client - to - server sending terminal 110 depending on its destination address . when receiving a feedback information packet indicating the reception condition of the client device 3 , the packet analyzer 101 forwards it to the header analyzer 102 and the reception condition information is output to the packet manager 105 . when receiving a streaming packet , the header analyzer 102 analyzes the header of the received streaming packet to extract a sequential number of the relevant flow and a time stamp indicating a time instant of the server device 2 sending it . the address , port number , time stamp , and sequential number for the received streaming packet are output to the packet manager 105 and the streaming packet is output to the packet memory 103 . in many instances , the header format employs rtp ( real - time transport protocol rfc 1889 ) as shown in fig4 . the packet manager 105 registers the information of address , port number , time stamp , and sequential number for each flow identified by a pair of address and port number , into the flow registration table 104 . an example of the flow registration table 104 is shown in fig5 . some streaming delivery application does not employ the rtp or cannot analyze it . in this case , the header analyzer 102 cannot obtain the above information . accordingly , the header analyzer 102 notifies the packet manager 105 that necessary information cannot be obtained from this packet and forwards it to the packet memory 103 . the packet memory 103 buffers streaming packets input from the header analyzer 102 for each flow under the sending control of the packet sending controller 106 . this buffering absorbs packet delay variations due to transmission from the server device 2 to the repeater 1 through the network . the packet manager 105 performs the scheduling of time of issuing a packet sending instruction for each flow to the packet sending controller 106 by referring to the packet registration table 104 . in a certain flow , the first - arrival packet is scheduled to be sent at the time set by adding a predetermined time period to its arrival time . the set time may be stored in a next sending time field of the flow registration table 104 ( see fig5 ). when the set time has come , the packet manager 105 issues a packet sending instruction for that flow to the packet sending controller 106 . the second or later packet is scheduled to be sent at the time set by adding a sending time difference to the set time of the previous packet . the sending time difference is calculated from a difference between the time stamp of the second or later packet and the time stamp of the previous packet . when the time interval of packets received from the server device 2 is always constant , the second or later packet may be scheduled to be sent at the time set by adding the constant time interval to the set time of the previous packet . the constant time interval is calculated from a difference between the time stamp of the second packet and the time stamp of the first packet . in the case where information related to sending time cannot be extracted from a received packet , the playing rate informed from the client device 3 or an average reception rate of packets that have been received so far in the relevant flow can be used to determine the sending time interval for scheduling . when receiving a feedback information packet indicating the reception condition of the client device 3 , the packet analyzer 101 forwards it to the header analyzer 102 and the reception condition information is output to the packet manager 105 . the packet manager 105 can adjust the packet sending time interval depending on the reception condition of the client device 3 . for example , when a variation in the arrival time interval of packets in a certain flow becomes greater , the packet manager 105 temporarily makes the packet sending time interval longer to absorb a greater delay variation in packet delivery . contrarily , when a variation in the arrival time interval of packets in a certain flow becomes smaller , the packet manager 105 temporarily makes the packet sending time interval shorter to reduce the buffering time at the repeater 1 . this reduces absolute delay time occurring between the server device 2 and the client device 3 . the delay variation reduction by the repeater 1 buffering packets causes the absolute delay occurring between the server device 2 and the client device 3 to be increased . however , the control of delay variation by the repeater 1 using the feedback information from the client device 3 suppresses the absolute delay occurring between the server device 2 and the client device 3 . when receiving a packet sending instruction for a certain flow from the packet manager 105 , the packet sending controller 106 reads a head packet of a queue for the relevant flow from the packet memory 103 and forwards it to the server - to - client signal sending terminal 109 . a packet to be sent has the source address and port number of the packet originating device ( here , the server device 2 ) included in its header , not those of the repeater 1 . accordingly , for the client device 3 , the packet appears received directly from the server device 2 . when the client device 3 receives a streaming packet from the server device 2 through the repeater 1 , the streaming packet is forwarded to the application 32 through the communication terminal 33 ( see fig3 b ). after buffering the streaming packet to absorb delay variations in packet transmission , the application 32 plays the content based on the streaming packet . as described before , in the application 32 performing packet reception and play , the amount of available buffer capacity varies depending on a difference between playing rate and reception rate . the reception condition notifying section 31 produces a reception condition indicating the amount of available capacity of the buffer provided in the application 32 and a packet reception rate and sends the reception condition notification packet carrying the reception condition as feedback information to the repeater 1 through the communication terminal 33 . at the repeater 1 , the reception condition is used to adjust the buffering time of the buffer to allow adaptive delay variation absorption , suppressing the absolute delay occurring between the server device 2 and the client device 3 .