EP2430795B1 - Procédé et dispositifs de la prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion - Google Patents

Procédé et dispositifs de la prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion Download PDF

Info

Publication number
EP2430795B1
EP2430795B1 EP10716983.1A EP10716983A EP2430795B1 EP 2430795 B1 EP2430795 B1 EP 2430795B1 EP 10716983 A EP10716983 A EP 10716983A EP 2430795 B1 EP2430795 B1 EP 2430795B1
Authority
EP
European Patent Office
Prior art keywords
multicast
fcc
user interface
interface device
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Not-in-force
Application number
EP10716983.1A
Other languages
German (de)
English (en)
Other versions
EP2430795A1 (fr
Inventor
Raziel Haimi-Cohen
John P. Hearn
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alcatel Lucent SAS
Original Assignee
Alcatel Lucent SAS
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alcatel Lucent SAS filed Critical Alcatel Lucent SAS
Publication of EP2430795A1 publication Critical patent/EP2430795A1/fr
Application granted granted Critical
Publication of EP2430795B1 publication Critical patent/EP2430795B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/23424—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H04N21/4383—Accessing a communication channel
    • H04N21/4384—Accessing a communication channel involving operations to reduce the access time, e.g. fast-tuning for reducing channel switching latency
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/44—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream or rendering scenes according to encoded video stream scene graphs
    • H04N21/44016—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream or rendering scenes according to encoded video stream scene graphs involving splicing one content stream with another content stream, e.g. for substituting a video clip
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64—Addressing
    • H04N21/6405—Multicasting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17336—Handling of requests in head-ends

Definitions

  • the present invention relates generally to internet protocol television (IPTV), and more particularly to fast channel change (FCC) methods and apparatus.
  • IPTV internet protocol television
  • FCC fast channel change
  • a subscriber or user is provided with an interface device, such as a set-top box (STB) or receiver, for communicating with network equipment, which may comprise, for example, a DSL access multiplexer (DSLAM).
  • STB set-top box
  • the interface device is configured to receive and process for presentation on a television or the like, a content stream corresponding to a channel selected by the user.
  • the subscriber interface device In order to receive a given selected channel in an IPTV system, the subscriber interface device will typically join a multicast stream corresponding to the selected channel. This is problematic in that there can be a substantial delay, on the order of several seconds, between user entry of a channel change command and receipt of decodable multicast data for the new channel. Because decoding the video stream is typically a recursive process, i.e., decoding a frame relies on previously decoded frames, decoding must start at an "entry point," where no prior frames are needed. Therefore, once an STB joins the multicast of a new channel, it has to wait for the next entry point in the stream in order to begin decoding. The interval between such entry points, however, may be hundreds of milliseconds or even seconds. This is the major cause of delay in channel change. During this channel change delay period, the screen of the presentation device is usually blank or frozen, which can be particularly annoying to the viewer when channel surfing.
  • FCC fast channel change
  • the STB begins playing the new channel shortly after it receives the first unicast packet; hence the channel change appears to be fast.
  • the FCC server "catches up” with the multicast, it signals the STB to join the multicast stream for the new channel.
  • the STB joins the multicast and continues to play from the multicast stream.
  • the subscriber's loop (between the STB and DSLAM) is of limited bandwidth.
  • the FCC server were to send the FCC unicast to the STB at the channel's data rate in parallel to the multicast, packet loss might occur.
  • the server drops the unicast rate to a fraction of the channel data rate. Therefore, during the time from receiving the "join multicast" signal until beginning to receive the multicast input, the STB receives data at a rate significantly lower than the rate at which it consumes data, with the balance obtained from a buffer which had been accumulated before, when the server unicast rate was higher than the channel data rate.
  • the server has to select the starting point at a sufficiently long delay.
  • a significant drawback of the conventional FCC approach is that the amount of data per FCC transaction is very sensitive to the variability of the multicast join time, that is, the time from sending a join request until receiving the first multicast packet.
  • This interval can be modeled as a random variable with a long-tailed distribution that can vary from a few milliseconds to several hundreds of milliseconds.
  • provisioning a conventional FCC system for all cases of multicast join time results in a major increase in FCC transaction duration, which for most cases is not needed, and makes it harder to scale-up the FCC system to handle greater numbers of FCC transactions.
  • Document US 2008282301-A1 discloses a method of providing video content which includes receiving a channel change data packet from a set-top box device at a subscriber premise via a packet-based video distribution network, where the channel change data packet includes data indicating a requested channel and a channel change index value, and the method also includes reading the channel change data packet to identify the channel change index value, the channel change index value indicates an available bandwidth at the subscriber premise to receive video content of the requested channel via the packet-based video distribution network, and the method also includes allocating an overhead bandwidth to the set-top box device based on the channel change index value.
  • Another approach to the channel change delay problem relies on a high bandwidth link to the subscriber. Generally, using more bandwidth alleviates the problem, but due to limitations in the distribution system, additional bandwidth may not be available or cost-effective.
  • the invention relates to a method and devices in accordance with the independent claims. Preferred embodiments are set forth in the dependent claims.
  • the present description in the illustrative embodiments provides improved techniques for fast channel change in an IPTV system or other type of signal distribution system.
  • a fast channel change (FCC) procedure of the invention after an FCC server has completed unicast transmission to a user interface device, such as a set-top box (STB), and the STB has requested to join the multicast stream for the new channel, the STB is configured to predict whether it will run out of packets at least some interval (e.g., several hundred milliseconds) before that actually happens. If the STB predicts that it will run out, it leaves the multicast and sends a message, referred to herein as a RESTART message, to the FCC server. In response to the RESTART message, the FCC server increases its output data rate to the unicast level, which is faster than the multicast rate. When the FCC server catches up with the multicast, it signals the STB to join the multicast for the new channel and the transaction continues as before.
  • FCC fast channel change
  • FIG. 1 is a schematic representation of an exemplary environment 100 in which the present invention can be either fully or partially implemented.
  • Environment 100 includes a content distribution network 110, which in this embodiment is a broadband-over-internet-protocol (IP) network.
  • content distribution network 110 may be a cable, satellite, Digital Subscriber Line (DSL), fiber-optic-to-home, data, and/or a combination of any of the aforementioned types of content distribution networks.
  • Portions of network 110 may be wired or wireless, and have any suitable topology.
  • Content distribution network 110 may also include or be coupled to other networks such as the Internet or an intranet.
  • the network 110 may comprise any type of communication network suitable for transporting signals associated with the provision of television services, and the invention is not limited in this regard.
  • portions of the network 110 may comprise local networks, wide area networks, the Internet, etc. Numerous alternative arrangements are possible, as will be apparent to those skilled in the art.
  • multicast video streams containing encoded content are typically distributed from one or more content sources 115 which may comprise otherwise conventional service provider equipment, including, for example, headend systems, satellites, servers, etc.
  • the network 110 comprises a combination of network elements such as routers and switches 120, 130 and a plurality of nodes such as Digital Subscriber Line Access Multiplexer (DSLAM) 140 for distributing video streams to a plurality of subscriber interface devices, such as a set-top box (STB) 150.
  • DSLAM 140 Digital Subscriber Line Access Multiplexer
  • STB 150 set-top box
  • the subscriber interface device 150 will be assumed to be a set-top box (STB), but in other embodiments may comprise, for example, receivers, computers, cellular handheld terminals or other processor-based devices, in any combination. Such devices are also referred to herein as user interface devices or “clients” and may be implemented as a separate device, such as an STB, a satellite receiver (not shown), a modem (not shown) or other devices which are connected to a presentation device 160 such as a TV.
  • the user interface device 150 may also be integrated with or part of a display device such as a TV, computer (not shown) or monitor (not shown) which has a screen for rendering and displaying content (audio and/or video content).
  • the STB 150 may have a conventional hardware implementation, including, for example, a processor coupled to a memory and a decoder 152 for converting received content streams to a form suitable for presentation by the device 160.
  • the memory may include an electronic random access memory (RAM), a read-only memory (ROM) or other type of storage device, as well as portions or combinations of such devices.
  • a portion of the memory may comprise an input buffer 151 for storing content streams received from the distribution network 110 and feeding the decoder 152, preferably at a constant bit rate.
  • the processor and memory are used in storage and execution of one or more software programs for implementing interface device portions of the fast channel change processing techniques disclosed herein.
  • the memory may be viewed as an example of what is also referred to herein as a computer-readable storage medium.
  • the network 110 also includes at least one fast channel change (FCC) server 125 arranged at some intermediate point between the content source 115 and DSLAM 140.
  • FCC fast channel change
  • the FCC server 125 provides a unicast video stream to the STB 150 via DSLAM 140.
  • the FCC server 125 receives the multicast stream from the content source 115 and caches that for provision, when needed, as a unicast stream.
  • a single FCC server 125 will engage in multiple FCC transactions with multiple STBs, often simultaneously. For clarity of description. FCC transactions between one FCC server and one STB are described herein.
  • router 120 represents the last common router in the multicast route to the STB 150 and to the FCC server 125.
  • Router 130 represents the first common router in the multicast route and the FCC unicast route to the STB 150.
  • Routers 120 and 130 may be the same network element. Dashed or dotted arrows indicate that there may be intermediate network elements (routers, switches) in between which are not depicted in FIG. 1 .
  • the FCC server 125 may be implemented on a common processing platform with one or more other servers of the system, or may be distributed across multiple such processing platforms.
  • FIG. 1 shows only a single DSLAM 140, one pair of routers/switches 120, 130, and a single FCC server 125, a given embodiment can of course include multiple such elements.
  • the system 100 may further include additional elements of a type found in conventional implementations of such a system, such as switches, content servers, ad servers, etc.
  • DSLAM 140 is a network element which presents an interface of the content distribution network 110 to the STB 150 and can be implemented conventionally.
  • the STB 150 is coupled to DSLAM 140 via a point-to-point, bidirectional connection 145 which may be a DSL, cable, fiber-optic or wireless link or any other suitable connection.
  • Content streams from the network 110 are passed by the DSLAM 140 on to the STB 150.
  • the STB 150 transmits control messages to the DSLAM 140 such as channel change request messages. Requests for channel changes from the STB 150 go to the DSLAM 140, which passes them on to the FCC server 125.
  • the FCC server 125 When the FCC server 125 receives a channel change request, it begins streaming the requested channel data to the STB 150 in unicast for a period of several seconds. Initially, this is the only data stream received by the STB 150 and thus the FCC server 125 can utilize the full bandwidth available to the STB. At some point, the FCC server 125 instructs the STB 150 to join the multicast stream for the new channel and sometimes afterwards the FCC server 125 terminates the unicast stream. Once the STB 150 begins receiving the multicast stream, or at some time before then, the bit rate of the unicast stream has to be dropped accordingly in order to avoid overloading the connection 145 and causing packet loss.
  • FIG. 2 illustrates the aforementioned phases of streaming in an FCC transaction between STB 150 and FCC server 125.
  • Dashed line 201 represents the arrival of multicast packets of a given content stream at the FCC server 125. These multicast packets arrive at the FCC server continuously. At any given point in time the FCC server has the last few seconds of multicast transmission cached, that is, stored in memory.
  • Solid-lined plot 202 represents the unicast packet transmission from the FCC server 125 to the STB 150.
  • Dotted line 203 represents the output of packets from the buffer 151 to the decoder 152 of the STB 150.
  • data rates are normalized so that the multicast data rate is 1 (as represented by line 201), as is the data rate from the input buffer 151 to the decoder 152 of the STB 150 (line 203).
  • all data streams are of constant bit rate, without any jitter; the fact that the data streams may consist of discrete packets is ignored, with each data stream treated as a continuous bit stream flow (terms such as "packet" are used to indicate a specific point in a data stream); denting (skipping frames in the unicast stream by the server) is not performed; once the STB 150 joins the multicast, each multicast packet arrives at the STB and at the FCC server 125 at the same time; the transmission delay of the unicast from the FCC server to the STB is negligible and ignored; processing times at the FCC server and at the STB are negligible and ignored; and the STB begins decoding the new channel immediately when it receives the first unicast packet from the
  • Phase 1 begins at time T 1 with the reception of the FCC request at the FCC server 125. Since processing delays at the FCC server 125 are assumed to be negligible, as soon as the FCC server 125 receives an FCC request, it begins unicast streaming the requested channel data to the STB 150.
  • the packets sent by unicast are taken from the FCC server's cache beginning with the packet received by the server at time T 0 . (It should be noted that the packet received by the server at time T 0 must be an entry point.)
  • the difference D S between T 1 and T 0 is the initial time gap between the incoming multicast packets and the outgoing unicast packets. The determination of this interval is discussed below in greater detail.
  • the rate of the unicast streaming during Phase I is 1+ E , where E is a burst factor (E > 0).
  • E is a burst factor (E > 0).
  • Sending data from the FCC server 125 at a rate higher than 1 is possible because the sending begins at a point which is a period D S behind the multicast reception at the FCC server.
  • E is selected so that 1+ E is the available bandwidth for streaming data to the STB 150.
  • the FCC server output data rate 1+ E is higher than the input rate 1, the gap between the incoming multicast packets and the outgoing unicast packets is decreasing during Phase 1.
  • the duration of phase 1 may he several seconds.
  • the FCC server 125 instructs the STB to join the multicast.
  • the STB 150 sends an internet group management protocol (IGMP) join request to DSLAM 140 at time T 2 .
  • IGMP internet group management protocol
  • T J There is an interval T J from the sending of an IGMP join request by the STB 150 at time T 2 until the time at which the first multicast packet is received by the STB 150.
  • the interval T J referred to as the multicast join time, is a random variable which changes from request to request. It has a minimum, T J min , but its distribution has a long tail and T J can have a high maximum value. The significance of the multicast join time and its variability in an FCC transaction are discussed below in greater detail.
  • Phase 2 is the interval starting at time T 2 and lasting up to T J min .
  • the FCC server 125 does not have to share the bandwidth with the multicast, but it cannot send data at a rate faster than 1 because after catching up with the multicast, the server cannot send packets faster than the rate at which it receives them.
  • the FCC server 125 continues sending data to the STB 150 at rate 1 for a period no longer than T J min , which typically will not be more than several tens of milliseconds.
  • T J min the relative size of T J min is exaggerated for clarity of illustration.
  • the FCC server 125 reduces the rate of the unicast stream to the STB 150, even though the STB might not actually begin to receive the multicast stream until some later time, T 2 + T J .
  • This reduction in the unicast rate at time T 2 + T J min marks the beginning of Phase 3.
  • the STB 150 receives both the unicast stream from the FCC server 125 as well as the multicast stream. So that the total bit rate of the multicast stream and the unicast stream does not exceed the available bandwidth of 1+ E , the FCC server 125 preferably drops the unicast rate to E during Phase 3.
  • the FCC server 125 does not know exactly when the STB 150 begins receiving the multicast stream until after the fact (if at all). Hence it preferably drops the rate at the earliest time at which the STB can begin receiving multicast, namely at T 2 + T J min .
  • the horizontal difference between the plot 202 and the line 203 is the time interval between the reception of a unicast packet at the STB 150 and the packet's provision to the STB decoder 152.
  • plot 202 and line 203 meet and this time interval is substantially zero.
  • T 3 T 2 + T J ⁇ min + D S 1 - E .
  • unicast packets would have arrived at the STB 150 after the time at which they would be needed by the decoder 152, i.e. too late to be useful.
  • the last usable unicast packet is represented by point 212 which corresponds to the intersection of plot 202 and line 203.
  • the FCC server 125 can calculate T 3 using Eq. I and stop the unicast stream no later than time T 3 , which marks the end of Phase 3.
  • the duration of Phase 3 is a few hundred milliseconds. It should be noted that in a well-designed system the FCC server 125 does not typically continue to unicast until time T 3 .
  • the STB 150 receives the first multicast packet and reports to the FCC server 125 the time which corresponds to that first multicast packet. The server keeps streaming until it sends the same packet in unicast and then stops.
  • the STB 150 begins to decode the unicast data corresponding to the multicast data at time T 0 , and since the STB decodes the data at rate 1, it constantly decodes data which is D S behind the multicast stream at any given point in time. (Note that in FIG. 2 , line 203 is parallel to line 201, offset in time by the interval D S . ) Therefore, by time T 2 when the unicast stream has caught up with the multicast stream and Phase 1 ends, the STB buffer 151 has accumulated an amount D S of data. The buffer 151 maintains this level during Phase 2, during which the input rate into the buffer equals the output rate to the decoder 152.
  • phase 3 however, unicast data arrives at rate E but is decoded by the STD at rate 1. Therefore, assuming 0 ⁇ E ⁇ 1, the STB buffer 151 will be depleted at a time D S 1 - E after the beginning of Phase 3.
  • the multicast join should be completed (i.e., the first multicast packet should be received by the STB) no later than V after the beginning of Phase 3.
  • T J and E are network parameters that may not be readily alterable or may be beyond the control of the FCC system designer, in which case the only way to insure that no gap occurs would typically be by increasing D S so that the condition of Eq. 4 is satisfied even for the largest possible value of T J . As seen from Eqs. 2 and 3, this would result in a proportionate increase in the duration of Phase 1 and the amount of data sent during this phase.
  • the multicast join time T J is a random variable with a long-tailed distribution and can occasionally have a large maximum value. As such, it may be impossible or impractical to require a seamless handover from unicast to multicast for the largest possible value of T J ; i.e., for the condition of Eq. 4 to always be met. Doing so could make the duration of the unicast stream and the amount of data sent in unicast too large for large scale operation (i.e. running many FCC sessions in parallel).
  • a maximum value of T J for which the handover can be expected to be seamless with a given, preferably high, probability is specitied, designated herein as H J .
  • D S is selected so that if the join time T J does not exceed H J , the handover from unicast to multicast will be seamless with the given probability.
  • H J is preferably selected so that the probability of T J > H j is small (e.g., less than 5%). If, however, the join time T J does exceed H J , exemplary procedures implemented as described below, can handle such a case to provide a seamless handover.
  • H J has a value of a few hundred milliseconds.
  • FIG. 3 is a flowchart of an exemplary embodiment of a procedure, as may he carried out by STB 150, for handling an FCC transaction.
  • an FCC request is sent via the DSLAM 140 to the FCC server 125.
  • the FCC server 125 responsively unicasts data to the STB 150 with some initial time gap D S and at 302, the STB receives this unicast stream at rate 1+E. As described above with reference to FIG. 2 , this occurs in Phase 1.
  • the FCC transaction proceeds into Phase 2, starting with the STB sending a multicast join request at time T 2 responsive to a message from the FCC server.
  • the level of the STB buffer 151 is substantially constant through Phase 2 and begins to be depleted in Phase 3 so that it will be empty at a time B T 2 1 - E after the start of Phase 3.
  • the parameters of Eq. 5 used by the STB 150 to calculate J max can be obtained by a variety of suitable means. Because the STB buffer level at time T 2 can be expected to be substantially constant through Phase 2, the buffer level may be determined, for example, as soon as the STB 150 receives the message from the FCC server 125 to join the multicast, later within Phase 2 or shortly after the beginning of Phase 3, ostensibly to obtain a more accurate level in case there is a change in the buffer level during Phase 2.
  • the parameter T J min can be provisioned in the STB 150, or the STB can estimate it by tracking the interval from the time it receives the signal to join the multicast until the unicast data rate drops to well below 1.
  • the burst rate E may be known to the STB via provisioning or estimated from either the incoming data rate or the rate of depletion of the buffer 151 after the time T 2 + TJ min , in Phase 3.
  • any or all of the parameters D S , T J min . E may be communicated by the FCC server. For example, these values may be included in the message from the FCC server signaling the STB to join the multicast.
  • the STB 150 waits to join the multicast; i.e., it awaits reception of the first multicast stream packet.
  • the STB 150 monitors the time that has elapsed since the join request was sent. If this time has not exceeded J max determined at 304, the STB continues to await the multicast stream as it continues to receive the FCC unicast stream. If the multicast stream begins before the elapsed time exceeds J max , operation proceeds normally in Phase 3, as represented by 307. Phase 3 then ends at 308 as the unicast stream from the FCC server 125 ends.
  • operation proceeds to 309.
  • the STB 150 knows that it will run out of data by the time the FCC unicast ends and in response takes preemptive action to prevent such an occurrence.
  • a scenario is depicted in FIG. 4 .
  • the STB leaves the multicast group by sending an IGMP "leave" message to the DSLAM 140 and preferably waiting for a short time (e.g. ⁇ 100 msec) to verity that the multicast stream has been stopped; that is, that no multicast packets arrive after sending the IGMP "leave” message.
  • a short time e.g. ⁇ 100 msec
  • the STB sends a RESTART message to the FCC server 125.
  • this occurs at or about time T 2 + J max [ B ( T 2 )].
  • FIG. 4 does not show the aforementioned waiting time between leaving the multicast and sending the RESTART message).
  • the RESTART message acts as an additional request to join the same channel.
  • the FCC server 125 Upon receiving the RESTART message from the STB 150, the FCC server 125 will revert to a new "Phase 1," designated Phase 1a in FIG. 4 , but without backing off; it will simply increase the effective data rate to 1+ E and keep unicast streaming data to the STB ( FIG. 3 , step 302) from the point in which it is currently in the unicast stream.
  • the RESTART message and its implementation can be incorporated, for example, as an enhancement of a current or new FCC protocol or standard, or as part of a proprietary scheme.
  • the FCC server will instruct the STB to join the multicast, and continue following the same procedure as in the first attempt, with the hope that this time the first multicast packet will arrive sooner.
  • the STB sends a multicast join request at time T 2a ( FIG. 3 , step 303). This marks the beginning of a new "Phase 2," designated Phase 2a in FIG. 4 .
  • Phase 2a As in Phase 2, during Phase 2a the unicast rate drops to 1 until the interval T J min has elapsed at time T 2 a + T J min .
  • Phase 3a the STB 150 will determine ( FIG. 3 , 304) a new value for J max based on the level of its buffer 151 at time T 2a in accordance with Eq. 5. This new value is shown in FIG. 4 as J max [ B ( T 2 a )]. Note that the time T 2a + J max [ B(T 2 a )] corresponds to the multicast arrival at the FCC server of the last usable unicast packet, as represented by point 212a. The STB 150 then waits, once again, for the multicast to start (305, 306). In the meantime, Phase 2a comes to an end at time T 2 a + T J min and a new "Phase 3," designated Phase 3a begins. As in Phase 3, the unicast rate in Phase 3a drops to E.
  • the STB 150 begins to receive the multicast stream before expiration of the time interval J max [ B ( T 2 a )], at time T 2 a + T J .
  • the STD receives both the multicast and unicast streams ( FIG.3 , 307) in Phase 3a until the unicast ends at time T 3 a (308).
  • D S In a conventional system, without a restart procedure such as that described above, D S must be set to cover a broader range of the distribution of T J (e.g., 99.5%) in order to provide acceptable FCC performance.
  • a restart procedure such as that described above allows D S to be set to a lower value because a smaller range of the distribution of T J (e.g., 95%) can be accommodated.
  • FCC transactions in which the join times exceed this range e.g., the remaining 5% of transactions
  • Reducing the requirement H J thus makes it possible to substantially reduce the duration of each FCC transaction and the amount of data required in an FCC unicast. This makes each FCC transaction less demanding, thereby increasing the availability and the number of FCC requests that can be supported by a given FCC server, thereby also reducing the costs associated with implementing a system having FCC functionality.
  • FIG. 5 is a flowchart of a further exemplary embodiment of an FCC transaction in which the STB repeatedly updates the estimate of J max as it waits to join the multicast (304, 305 and 306).
  • This allows for more accurate estimation of the critical time point T 2a + J max [ B ( T 2 a )] by observing the rate of depletion of the STB buffer over time and is especially useful in situations where some of the aforementioned simplifying assumptions, such as no denting, do not hold. In those situations, the plot 202 may not be exactly piecewise linear and the closer one gets to the critical time point, the better it can be estimated.
  • a desired goal of an embodiment of the invention is to reduce the average of the duration of Phase 1, D 1 , and the average of the amount of unicast data transmitted, B 1 , in Phase 1 of a FCC transaction.
  • Optimizing the selection of the parameter H J (the maximum allowable multicast join time for normal operation) in accordance with the actual distribution of the multicast join time helps achieve this goal. Selecting H J too high will result in unnecessarily increasing D S and therefore also D 1 and B 1 (per Eqs. 2 and 3), while selecting H J too low will result in too many FCC transactions going through a recovery procedure, such as the restart procedure described above, and incurring the overhead associated with it.
  • H J is preferably adaptive to channel, time and/or usage. In other words, the values of H J and thus D S are selected in accordance with the channel, time and/or usage.
  • the probability of a FCC transaction resorting to a restart procedure is estimated at the FCC server at any given time t as P t .
  • the probability P t can be estimated, for example, by considering time intervals of fixed duration (e.g. 10 seconds) and in each interval calculating the ratio between the number of FCC transactions using the restart procedure to the total number of FCC transactions in that interval. If the probability P t exceeds some pre-set target probability P d (e.g., 5%) then H J (and D S ) is increased and if P t ⁇ P d then H J (and D S ) is decreased.
  • some pre-set target probability P d e.g., 5%
  • the server may estimate the distribution of the multicast join time directly.
  • a client typically reports to the FCC server when it receives the first multicast packet in each FCC transaction, which allows the server to determine the multicast join time for each FCC transaction.
  • the FCC server can use these values to estimate the current distribution of the multicast join time for a particular channel, for example by generating a histogram of all multicast join times for a particular channel in a given interval of time (e.g., the last 60 seconds).
  • the server can set T J min to a value according to this distribution.
  • P d the probability of restart, for this particular value of D S .
  • the unicast rate into the STB buffer 151 is E while the output rate to the decoder 152 is 1. If the client sends a RESTART message, it does so a time V after the start of Phase 3.
  • the gap between the incoming unicast and multicast is zero; after Phase 3 starts, the unicast is received at rate E while the multicast proceeds at rate 1.
  • the duration and the amount of data transmitted during the first phase after each RESTART request are also D 1 a and B 1 a , respectively.
  • initial Phases 2 and 3 and Phases 2a and 3a after each RESTART can be ignored because their durations are typically much shorter than those of Phases 1 and 1a. (The durations of these phases are exaggerated in FIGs. 2 and 4 for illustrative purposes).
  • the amount of data transmitted in these phases is even lower in comparison to Phases 1, 1a.
  • the FCC server can determine D exp and B exp in accordance with Eqs.
  • the FCC server When the FCC server receives a FCC request for a particular channel, it considers the entry points in the cache. Typically the number of such entry points is quite small, often less than ten. Each such entry point corresponds to a value of D S . The FCC server can calculate D exp and/or B exp for each entry point and select the entry point which yields the lowest value(s).
  • D 1 and B 1 in Eqs. 9 and 10 would he replaced by the corresponding expressions for the total durations and unicast data amounts of Phases 1, 2 and 3 and D 1 a and B 1 a would be replaced by the corresponding expressions for the total durations and unicast data amounts of Phases 1a, 2a and 3a.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Claims (15)

  1. Procédé de traitement d'une transaction de changement de canal rapide « FCC » comprenant les étapes suivantes :
    envoyer une demande FCC à un serveur FCC (125) en réponse à une demande de changement de canal au niveau d'un dispositif d'interface utilisateur (150) ;
    transmettre un flux de monodiffusion à partir du serveur FCC (125) au dispositif d'interface utilisateur (150) en réponse à la demande FCC ;
    réduire le débit auquel le flux de monodiffusion est transmis au dispositif d'interface utilisateur (150) ;
    envoyer une demande de rattachement à une multidiffusion à partir du dispositif d'interface utilisateur (150) pour se rattacher à une multidiffusion du canal demandé ;
    déterminer un temps maximum de rattachement à une multidiffusion pour garantir un transfert sans interruption entre le flux de monodiffusion et la multidiffusion ;
    envoyer un message de redémarrage au serveur FCC (125) si le temps maximum de rattachement à une multidiffusion s'écoule avant que le dispositif d'interface utilisateur (150) ne se rattache à la multidiffusion ; et
    augmenter le débit auquel le flux de monodiffusion est transmis entre le serveur FCC (125) et le dispositif d'interface utilisateur (150) en réponse au message de redémarrage.
  2. Procédé selon la revendication 1, dans lequel le temps maximum de rattachement à une multidiffusion est déterminé en fonction d'un niveau de tampon du dispositif d'interface utilisateur (150).
  3. Procédé selon la revendication 1, dans lequel le temps maximum de rattachement à une multidiffusion est déterminé de manière répétée avant que le dispositif d'interface utilisateur (150) ne se rattache à la multidiffusion.
  4. Procédé selon la revendication 1, dans lequel le flux de monodiffusion est transmis avec un retard initial qui est déterminé de manière adaptative par le serveur FCC (125).
  5. Procédé selon la revendication 1, comprenant en outre la réduction du débit auquel le flux de monodiffusion est transmis au dispositif d'interface utilisateur (150) au moins un intervalle de temps de rattachement minimum après l'envoi de la demande de rattachement à une multidiffusion à partir du dispositif d'interface utilisateur (150).
  6. Dispositif d'interface utilisateur (150) pour traiter une transaction de changement de canal rapide « FCC » configuré pour :
    envoyer une demande FCC à un serveur FCC (125) en réponse à une demande de changement de canal ;
    recevoir un flux de monodiffusion à partir du serveur FCC (125) ;
    envoyer une demande de rattachement à une multidiffusion pour se rattacher à une multidiffusion du canal demandé ;
    déterminer un temps maximum de rattachement à une multidiffusion pour garantir un transfert sans interruption entre le flux de monodiffusion et la multidiffusion ;
    envoyer un message de redémarrage au serveur FCC (125) si le temps maximum de rattachement à une multidiffusion s'écoule avant que le dispositif d'interface utilisateur (150) ne se rattache à la multidiffusion ; et
    recevoir un flux de monodiffusion redémarré à partir du serveur FCC (125).
  7. Dispositif d'interface utilisateur (150) selon la revendication 6, dans lequel le temps maximum de rattachement à une multidiffusion est déterminé en fonction d'un niveau de tampon du dispositif d'interface utilisateur (150).
  8. Dispositif d'interface utilisateur (150) selon la revendication 6, dans lequel le temps maximum de rattachement à une multidiffusion est déterminé de manière répétée avant que le dispositif d'interface utilisateur (150) ne se rattache à la multidiffusion,
  9. Dispositif d'interface utilisateur (150) selon la revendication 6 comprenant l'envoi d'un message au serveur FCC (125) une fois que le dispositif d'interface utilisateur (150) se rattache à la multidiffusion.
  10. Support de stockage lisible par processeur comprenant un code de programme exécutable qui, lorsqu'il est exécuté dans un dispositif d'interface utilisateur (150), entraîne la configuration du dispositif d'interface utilisateur (150) selon la revendication 6.
  11. Serveur de changement de canal rapide « FCC » (125) pour traiter une transaction FCC configuré pour :
    recevoir une demande FCC envoyée en réponse à une demande de changement de canal au niveau d'un dispositif d'interface utilisateur (150) ;
    transmettre un flux de monodiffusion au dispositif d'interface utilisateur (150) en réponse à la demande FCC ;
    réduire le débit auquel le flux de monodiffusion est transmis au dispositif d'interface utilisateur (150) ;
    signaler au dispositif d'interface utilisateur (150) de se rattacher à une multidiffusion du canal demandé ;
    recevoir un message de redémarrage provenant du dispositif d'interface utilisateur (150) ; et
    augmenter le débit auquel le flux de monodiffusion est transmis au dispositif d'interface utilisateur (150) en réponse au message de redémarrage.
  12. Serveur FCC (125) selon la revendication 11 configuré pour recevoir un message provenant du dispositif d'interface utilisateur (150) indiquant que le dispositif d'interface utilisateur (150) s'est rattaché à la multidiffusion.
  13. Serveur FCC (125) selon la revendication 11, configuré pour transmettre le flux de monodiffusion avec un retard initial qui est déterminé de manière adaptative par le serveur FCC (125).
  14. Serveur FCC (125) selon la revendication 11, le serveur (125) étant en outre configuré pour réduire le débit auquel le flux de monodiffusion est transmis au dispositif d'interface utilisateur (150) au moins un intervalle de temps de rattachement minimum après l'envoi de la demande de rattachement à une multidiffusion à partir du dispositif d'interface utilisateur (150).
  15. Support de stockage lisible par processeur comprenant un code de programme exécutable qui, lorsqu'il est exécuté dans un serveur FCC (125) entraîne la configuration du serveur FCC (125) selon la revendication 11.
EP10716983.1A 2009-05-13 2010-04-29 Procédé et dispositifs de la prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion Not-in-force EP2430795B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/464,982 US8161515B2 (en) 2009-05-13 2009-05-13 Fast channel change handling of late multicast join
PCT/US2010/032902 WO2010132210A1 (fr) 2009-05-13 2010-04-29 Prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion

Publications (2)

Publication Number Publication Date
EP2430795A1 EP2430795A1 (fr) 2012-03-21
EP2430795B1 true EP2430795B1 (fr) 2014-10-15

Family

ID=42320717

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10716983.1A Not-in-force EP2430795B1 (fr) 2009-05-13 2010-04-29 Procédé et dispositifs de la prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion

Country Status (6)

Country Link
US (1) US8161515B2 (fr)
EP (1) EP2430795B1 (fr)
JP (1) JP5420759B2 (fr)
KR (1) KR101286830B1 (fr)
CN (1) CN102422649B (fr)
WO (1) WO2010132210A1 (fr)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101753973B (zh) * 2008-12-12 2013-01-02 华为技术有限公司 一种频道切换方法、装置和***
US8150993B2 (en) * 2009-10-29 2012-04-03 At&T Intellectual Property I, Lp Synchronization of clients to maximize multicast opportunities
KR101268629B1 (ko) * 2009-11-05 2013-05-29 한국전자통신연구원 시청률 예측 연동 복수 멀티캐스트를 이용한 고속 채널 전환을 위한 채널 서버, 채널 예측 서버, 단말기 및 그 방법
US9357244B2 (en) * 2010-03-11 2016-05-31 Arris Enterprises, Inc. Method and system for inhibiting audio-video synchronization delay
US9009765B2 (en) 2011-01-26 2015-04-14 Telefonaktiebolaget L M Ericsson (Publ) Method and server for fast channel change in unicast-multicast IPTV networks
US9049481B2 (en) * 2011-05-25 2015-06-02 Cisco Technology, Inc. Fine-tuning the time for leaving/joining a multicast session during channel changes
US9264508B2 (en) * 2011-08-19 2016-02-16 Time Warner Cable Enterprises Llc Apparatus and methods for reduced switching delays in a content distribution network
GB2500406A (en) * 2012-03-20 2013-09-25 Qarva Ltd Providing rapid channel changes, with client itself assessing technical environment and network connection parameters
CN104144359B (zh) * 2013-05-10 2017-08-22 中国电信股份有限公司 Iptv组播频道快速切换的方法及***
CN103347207B (zh) * 2013-06-28 2017-10-17 江苏省邮电规划设计院有限责任公司 一种iptv组播频道快速切换的方法
US10735823B2 (en) * 2015-03-13 2020-08-04 Telefonaktiebolaget Lm Ericsson (Publ) System and method for optimized delivery of live ABR media
US10432688B2 (en) 2015-03-13 2019-10-01 Telefonaktiebolaget Lm Ericsson (Publ) System and method for optimized delivery of live ABR media
CN104811790A (zh) * 2015-05-14 2015-07-29 国网黑龙江省电力有限公司信息通信公司 一种结合单播和组播以加快数字电视机顶盒换台速度的方法
CN107637084A (zh) 2015-05-20 2018-01-26 Nxt解决方案公司 被管网络中的iptv
CN106412719B (zh) * 2015-08-03 2019-04-30 ***通信集团江苏有限公司 一种视频混播的实现方法、装置及***
US9826262B2 (en) * 2015-09-09 2017-11-21 Ericsson Ab Fast channel change in a multicast adaptive bitrate (MABR) streaming network using multicast repeat segment bursts in a shared progressive ABR download pipe
US9826261B2 (en) * 2015-09-09 2017-11-21 Ericsson Ab Fast channel change in a multicast adaptive bitrate (MABR) streaming network using multicast repeat segment bursts in a dedicated bandwidth pipe
US9928196B2 (en) 2015-09-30 2018-03-27 International Business Machines Corporation Programming interface operations in a driver in communication with a port for reinitialization of storage controller elements
US10083144B2 (en) 2015-09-30 2018-09-25 International Business Machines Corporation Programming interface operations in a port in communication with a driver for reinitialization of storage controller elements
CN106937155B (zh) * 2015-12-29 2020-06-02 北京华为数字技术有限公司 接入设备、因特网协议电视iptv***和频道切换方法
CN106850159B (zh) * 2017-02-24 2020-12-11 台州市吉吉知识产权运营有限公司 一种组播转单播传送方法及***
CN106961625B (zh) * 2017-03-13 2020-02-21 华为技术有限公司 一种频道切换方法及其装置
US10958948B2 (en) 2017-08-29 2021-03-23 Charter Communications Operating, Llc Apparatus and methods for latency reduction in digital content switching operations
CN107682718A (zh) * 2017-09-21 2018-02-09 烽火通信科技股份有限公司 多iptv平台下快速切换频道的方法及***
CN110505500A (zh) * 2019-08-06 2019-11-26 咪咕视讯科技有限公司 一种缓存数据发送处理方法及装置
CN115484468B (zh) * 2021-06-15 2024-01-09 北京字节跳动网络技术有限公司 一种连麦***、方法、装置、设备及存储介质
JP7094648B1 (ja) * 2021-12-20 2022-07-04 一般社団法人日本ケーブルラボ ブロードキャスト及びユニキャストのコンテンツを遅延させる端末、プログラム及び方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6006289A (en) * 1996-11-12 1999-12-21 Apple Computer, Inc. System for transferring data specified in a transaction request as a plurality of move transactions responsive to receipt of a target availability signal
KR20000036891A (ko) * 2000-03-31 2000-07-05 김지혜 멀티캐스트 필터링 및 유니캐스트로의 전환방법과 그 시스템
US7562375B2 (en) * 2003-10-10 2009-07-14 Microsoft Corporation Fast channel change
KR100605800B1 (ko) * 2003-11-12 2006-07-31 삼성전자주식회사 랜덤 액세스 단계의 서비스 품질을 구현하는이동통신단말과 그 방법
US20050183120A1 (en) * 2004-01-13 2005-08-18 Saurabh Jain Multi-user personalized digital multimedia distribution methods and systems
US20060020995A1 (en) * 2004-07-20 2006-01-26 Comcast Cable Communications, Llc Fast channel change in digital media systems
US7804831B2 (en) * 2005-04-01 2010-09-28 Alcatel Lucent Rapid media channel changing mechanism and access network node comprising same
CN101502156A (zh) * 2005-04-08 2009-08-05 美商内数位科技公司 网状网络中统合无缝信道切换方法及装置
US8054849B2 (en) * 2005-05-27 2011-11-08 At&T Intellectual Property I, L.P. System and method of managing video content streams
US8713195B2 (en) * 2006-02-10 2014-04-29 Cisco Technology, Inc. Method and system for streaming digital video content to a client in a digital video network
US8769591B2 (en) * 2007-02-12 2014-07-01 Cisco Technology, Inc. Fast channel change on a bandwidth constrained network
US7761902B2 (en) 2007-05-11 2010-07-20 At&T Intellectual Property I, L.P. System and method of providing video content
KR100880893B1 (ko) * 2007-09-14 2009-01-30 한국전자통신연구원 복수의 멀티캐스트를 이용한 ｉｐｔｖ 고속 채널 전환을위한 장치 및 그 방법

Also Published As

Publication number Publication date
US8161515B2 (en) 2012-04-17
JP2012527164A (ja) 2012-11-01
CN102422649A (zh) 2012-04-18
US20100293587A1 (en) 2010-11-18
EP2430795A1 (fr) 2012-03-21
CN102422649B (zh) 2014-06-04
KR101286830B1 (ko) 2013-07-17
JP5420759B2 (ja) 2014-02-19
KR20120008526A (ko) 2012-01-30
WO2010132210A1 (fr) 2010-11-18

Similar Documents

Publication Publication Date Title
EP2430795B1 (fr) Procédé et dispositifs de la prise en charge par changement rapide de canal d'un rattachement tardif en multidiffusion
US20100115566A1 (en) Fast Channel Change Request Processing
US8474001B2 (en) Near real time delivery of variable bit rate media streams
US9462343B2 (en) System and method of delivering video content
KR100898210B1 (ko) 디지털 신호를 전송하고 수신된 스트리밍 콘텐트 채널을 변경하기 위한 방법 및 장치, 및 컴퓨터 판독가능한 매체
US8190750B2 (en) Content rate selection for media servers with proxy-feedback-controlled frame transmission
EP2297880B1 (fr) Procédé et appareil de réduction de temps de réponse à un changement de canal pour télévision sur protocole internet
US8661486B2 (en) System and method of delivering video content
EP2563034B1 (fr) Réaffectation dynamique de bande passante
JP5551822B2 (ja) 複数の端末をユニキャスト伝送から段階的に遷移させるコントローラ
US8533760B1 (en) Reduced latency channel switching for IPTV
EP2466911B1 (fr) Méthode et dispositif pour transmettre rapidement un flux unicast pour changement de canal rapide
US7954132B2 (en) Method for reducing channel change time of internet protocol television (IPTV) and IPTV service provision server for implementing the same
JP2005526422A (ja) ソースから転送先への伝送のための通信システムおよび通信技術
EP2011308B1 (fr) Dispositif et procede de stockage dynamique de donnees multimedia
JP5807710B2 (ja) コンテンツ配信システム、コンテンツ配信方法及びプログラム
EP1395020A2 (fr) Méthode et appareil pour le contrôle dynamique d'un flux de données multimédia en temps réel
Balafoutis et al. The impact of replacement granularity on video caching
US11444863B2 (en) Leveraging actual cable network usage
KR20050118835A (ko) 손실률에 따른 ＱｏＳ를 제공하는 ＶＯＤ 서비스 제공시스템 및 방법
Sharma et al. Multimedia Streaming in Multicast Environment.

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20111213

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20130322

111Z Information provided on other rights and legal means of execution

Free format text: AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

Effective date: 20130410

RIC1 Information provided on ipc code assigned before grant

Ipc: H04N 21/6405 20110101ALI20131009BHEP

Ipc: H04L 12/18 20060101AFI20131009BHEP

Ipc: H04L 29/06 20060101ALI20131009BHEP

Ipc: H04N 21/44 20110101ALI20131009BHEP

Ipc: H04N 21/234 20110101ALI20131009BHEP

Ipc: H04N 21/61 20110101ALI20131009BHEP

Ipc: H04N 21/438 20110101ALI20131009BHEP

Ipc: H04N 7/173 20110101ALI20131009BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20140502

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ALCATEL LUCENT

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 692073

Country of ref document: AT

Kind code of ref document: T

Effective date: 20141115

D11X Information provided on other rights and legal means of execution (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010019550

Country of ref document: DE

Effective date: 20141127

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20141015

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 692073

Country of ref document: AT

Kind code of ref document: T

Effective date: 20141015

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150216

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150115

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150215

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150116

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010019550

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

26N No opposition filed

Effective date: 20150716

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150429

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150430

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150429

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20100429

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141015

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602010019550

Country of ref document: DE

Representative=s name: MENZIETTI WETZEL, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602010019550

Country of ref document: DE

Owner name: PROVENANCE ASSET GROUP LLC, PITTSFORD, US

Free format text: FORMER OWNER: ALCATEL LUCENT, BOULOGNE BILLANCOURT, FR

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20190418 AND 20190426

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20210503

Year of fee payment: 12

Ref country code: FR

Payment date: 20210430

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20210430

Year of fee payment: 12

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602010019550

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20220429

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220429

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20221103