WO2008033644A2 - Retransmission-based stream repair and stream join - Google Patents
Retransmission-based stream repair and stream join Download PDFInfo
- Publication number
- WO2008033644A2 WO2008033644A2 PCT/US2007/076264 US2007076264W WO2008033644A2 WO 2008033644 A2 WO2008033644 A2 WO 2008033644A2 US 2007076264 W US2007076264 W US 2007076264W WO 2008033644 A2 WO2008033644 A2 WO 2008033644A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- media stream
- media
- retransmission
- multicast
- address
- Prior art date
Links
Classifications
-
- 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- 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/16—Multipoint routing
-
- 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/12—Shortest path evaluation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
-
- 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
- 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/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- 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/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
-
- 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
- H04L2001/0092—Error control systems characterised by the topology of the transmission link
- H04L2001/0093—Point-to-multipoint
Definitions
- the present disclosure relates generally to a scheme for retransmission-based repair and fast stream join for Internet Protocol (IP) based media streams.
- IP Internet Protocol
- the Real-time Transport Protocol (RTP) and its related standards define a retransmission packet format and a way to give feedback via Negative ACKnowledgment (NACK) packets that data has been lost.
- RTP RTP
- RTP Retransmission RTP Retransmission
- RCP Feedback RCC4585
- RTCP with SSM Sessions are all incorporated by reference and describe unicast feedback and retransmission for unicast sessions, and unicast feedback with multicast retransmission for multicast sessions.
- the RTP protocol suite has limitations when used with certain types of Internet Protocol (IP) media transmissions, such as transmitting streaming video to different endpoints.
- IP Internet Protocol
- neither RTP, nor any other common media transmission protocol can perform unicast repair of multicast media streams or quickly and efficiently switch among different multicast media streams without loss of data.
- FIG. 1 shows a repair scheme used in a lookaside mode for multicast media streams.
- FIG.2 shows the repair scheme in FIG. 1 using IP anycast addresses.
- FIG. 3 is a diagram showing how different media streams can be associated with different IP anycast addresses.
- FIG. 4 is a diagram showing how the repair scheme is used in a source mode.
- FIG. 5 is a diagram showing another embodiment of a retransmission scheme used for channel joining.
- FIG. 6 is a flow diagram explaining in more detail the retransmission scheme shown in FIG. 5.
- a Real-time Transport Protocol (RTP)-based unicast repair scheme is used for repairing errors in RTP multicast streams.
- RTP Real-time Transport Protocol
- the repair scheme is extended to also rapidly join media channels. It should be noted that the terms channel and stream are used interchangeably below.
- a media stream source 12 may be a server, computer, or any other type of network processing device that can source IP media, such as video, audio, voice, data, etc., over an Internet Protocol (IP) network 10.
- IP Internet Protocol
- the media stream source 12 transmits a multicast media stream 14 over the IP network 10 which is received by different media stream receivers 24A-24N and also by a retransmission system 18.
- the media stream receivers 24 can be any device that receives and stores or renders the multicast media stream 14.
- the media stream receivers 24 could be Set Top Boxes (STB), Digital Video Recorders (DVR), computer terminals, Personal Computers (PCs), televisions with IP interfaces, Voice over IP (VoIP) phones, cell phones, Personal Digital Assistants (PDA), etc.
- the retransmission system 18 can be any type of media server that caches and retransmits portions of the multicast media stream 14.
- the media stream source 12 and retransmission system 18 are shown as separate devices but could reside in the same physical location and be connected together via a Local Area Network (LAN) or other backplane connectivity.
- LAN Local Area Network
- a Source Specific Multicast (SSM) multicast session is established for transmitting the multicast media stream 14 between the media stream source 12 and one or more of the media stream receivers 24.
- the media stream source 12 knows the IP addresses and ports to use for transmitting a particular media stream.
- the retransmission system 18 knows what IP addresses and ports to use for receiving the media stream and what address and port to use for sending retransmissions.
- the media stream receivers 24 know what IP address and port to listen for the media stream and the retransmissions, and where to send retransmission requests. All of this address and port information can be described using Session Description Protocol (SDP), but other media description schemes could be used.
- SDP Session Description Protocol
- the feedback target IP address 16 is used by the media stream receivers 24 as a destination address for requesting retransmissions for portions of the multicast media stream 14. For example, packets from the media stream 14 may not successfully arrive at particular media stream receivers, or may be received in a corrupted state.
- the media stream receivers 24 send retransmission requests 28 to the retransmission system 18 associated with the feedback target IP address 16 that includes information 30 identifying the lost media packets.
- retransmission requests 28 are unicast Real-time Transport Control Protocol (RTCP) Negative ACKnowledge (NACK) packets that use the feedback target address 16 as a destination address 29.
- RTCP Real-time Transport Control Protocol
- NACK Negative ACKnowledge
- Sending the unicast RTCP NACK packet 28 to the retransmission system 18 dynamically instantiates a unicast RTP repair session from the retransmission system to the requesting receiver, if one does not already exist.
- the retransmission system 18 includes a media cache 22 that caches the recent history of packets from the multicast media stream 14.
- lost packets for media stream 14 are identified in lost packet information 30 of the retransmission request 28.
- the retransmission system 18 identifies the packets in media cache 22 corresponding to the lost or corrupted packet information 30 in retransmission request 28.
- a repair session uses unicast NACK packets 28 and unicast media repair packets 34 for repairing a multicast media session.
- the media configuration shown in FIG. 1 is referred to as a "lookaside mode" because the retransmission system 18 (repair element) is not required to relay the original media stream 14 to the media stream receivers 24. Instead, the media stream source 12 multicasts the media stream 14 directly to the receivers 24.
- the lookaside mode may produce higher availability since the media stream 14 is not necessarily disrupted if the retransmission system 18 crashes or becomes unavailable.
- the unicast repair function ceases when the retransmission system 18 fails. Higher performance may also be provided since the retransmission system 18 only receives and caches the multicast media stream 14 and does not also have to retransmit the media stream 14 to the media stream receivers 24. Thus, by only providing media stream repair, the constant work factor for the retransmission system 18 is halved.
- the retransmission system 18 is distinguished from the media stream source 12 by using a feedback target address 16 for the retransmission system 18 that is different from the source IP address associated with the SSM media stream source 12. IP Anycast Addressing
- one embodiment of the repair scheme uses an IP anycast address 46 as the feedback target address for the retransmission system 18. This allows repair operations to be adaptively directed to the optimal currently available retransmission system 18A or 18B.
- the anycast addressing scheme exploits the metrics of IP unicast routing that automatically route packets to network processing devices associated with the cheapest IP routing cost.
- message 40 identifies a single IP anycast address 46 for multiple different retransmission systems 18A and 18B available for repairing the multicast media stream 14.
- This SDP is provided to both the retransmission systems 18A and 18B, as well as to the receivers so that they will direct their retransmission requests to that anycast feedback address.
- Both retransmission system 18A and 18B cache the media stream 14 and are available for retransmitting lost packets to any of the media stream receivers 24A-24D.
- IP anycast address refers to a unicast IP address that is used as a destination address simultaneously by multiple network processing devices.
- the network processing devices sharing IP address 46 include retransmission systems 18A and 18B.
- the retransmission systems 18A and 18B and the media stream receivers 24 operate in substantially the same manner as described above in FIG. 1.
- all of the media stream receivers 24A-24D each receive the same multicast media stream 14 from media stream source 12.
- the media stream receivers 24 could indirectly receive the multicast media stream 14 via a separate multicast stream sourced from one of the retransmission systems 18A or 18B. This embodiment is referred to as "source mode" and is described in more detail below in FIG. 4.
- Any of the media stream receivers 24A-24D may detect lost or corrupted packets or frames from the multicast media stream 14. In response, the receiver 24 sends out a unicast NACK retransmission request message 44.
- each of the media stream receivers 24A-24D in FIG. 2 is currently receiving the media stream 14 and one or more of them has identified lost packets from the media stream 14. Respectively, the receivers 24A-24D experiencing loss or corruption send out retransmission request messages 44A-44D.
- Each of the retransmission request messages 44A-44D includes the same IP anycast destination address 46 along with the associated media stream receiver source address 48A- 48D, respectively.
- the retransmission request messages 44A-44D also include lost packet information identifying which of the packets were lost from the multicast media stream 14.
- Routers 42 and 44 in the IP network 10 use internal routing metrics to select which of the retransmission systems 18 A or 18B has the cheapest IP routing cost for routing the messages 44A-44D. Since the IP anycast address 46 is shared by two different network processing devices 18A and 18B, the conventional routing metrics in the routers 42 and 43 will automatically select one of the two devices 18A or 18B for forwarding any messages 44A-44D.
- router 42 determines that retransmission system 18A has the shortest routing path for the retransmission request messages 44A and 44B received from receivers 24A and 24B, respectively.
- router 43 determines that retransmission system 18B has the shortest routing path for the retransmission request messages 44C and 44D received from receivers 24C and 24D, respectively.
- Retransmission system 18A receives unicast NACK retransmission request messages 44A and 44B and retransmission system 18B receives unicast NACK retransmission request messages 44C and 44D.
- the retransmission system 18A responds back by sending unicast media repair packets from its cache of multicast media stream 14 back to receivers 24A and 24B.
- retransmission system 18 A sends unicast media repair packets 34 back to the media stream receiver 24B identified in message 44B.
- Retransmission system 18B responds to retransmission request messages 44C and 44D by sending unicast media repair packets from its cache of multicast media stream 14 back to receivers 24C and 24D, respectively.
- This distributed routing of retransmission requests 44A-44D increases both availability and load sharing capacity while using substantially the same repair scheme described above in FIG. 1. For example, if either of the retransmission systems 18A or 18B is disabled, the routers 42 and 44 will automatically drop the disabled retransmission system from internal routing tables. Accordingly, repair requests previously routed to the disabled retransmission system 18 are automatically rerouted to a different one of the operational retransmission systems 18.
- FIG. 3 shows different IP anycast addresses used as feedback addresses for different media streams 54 and 56. This further increases the scalability of the media repair scheme by allowing one or more different retransmission systems 50 and 52 to be associated with different multicast media streams.
- one or more retransmission systems 50 can be specifically designated to provide media packet repair for a particular multicast media stream 54.
- the feedback target IP anycast address identified in the Source Specific Multicast (SSM) multicast session for multicast media stream 54 is used as the source address for each of the retransmission systems 50.
- one or more retransmission systems 52 can be designated to provide media packet repair support for a different multicast media stream 56.
- the feedback target IP anycast source address identified in the SSM multicast session for the multicast media stream 56 is used as the source address for each of retransmission systems 52.
- media stream receiver 24B is receiving packets for multicast media stream 54.
- media stream receiver 24B sends a unicast NACK retransmission request message 58 to the IP anycast destination address X associated with multicast media stream 54.
- the routers in the IP infrastructure (not shown) automatically route the retransmission request message 58 to one of the retransmission systems 50 which then sends back unicast media repair packets containing the identified lost packets.
- a retransmission system 50 may provide repair support for more than one media stream.
- FIG. 4 shows an alternative "source mode" for the repair scheme.
- retransmission sources 70 provide media stream repair and also operate as SSM distribution sources for the multicast stream 14 originally generated by media stream source 12.
- the media stream source 12 could be a local encoder, a local splicer, or a separate media stream server operating remotely in the IP network 10 from the retransmission sources 7OA and 7OB.
- the retransmission source 7OA caches the original media stream 14 in media cache 22A and if necessary "re-sources" the received media stream 14, operating as a legal RTP mixer/translator according to the RTP specifications. Similarly, retransmission source 7OB retransmits the original media stream 14 cached in media cache 22B as multicast media stream 64.
- the retransmission sources 7OA and 7OB still receive unicast NACK retransmission request messages 44 from the media stream receivers 24 when multicast media stream packets are lost.
- the retransmission sources 70 accordingly send back unicast media repair packets 34 containing the requested lost media.
- the two retransmission sources 7OA and 7OB also still share the same IP source address 46.
- This common IP source address 46 for the feedback target can again be identified for the multicast media session using out-of-band or in-band messaging.
- the messages 60 exchanged between the media stream source 12, retransmission sources 70, and the media stream receivers 24, associate media stream 14 with feedback target IP anycast address 46.
- Sharing the same IP destination address 46 provides high availability and load sharing for the repair scheme similar in a similar manner as described above in FIG. 2.
- both retransmission sources 7OA and 7OB in FIG. 4 also operate as retransmission sources for the media stream 14. Therefore, sharing the same SSM source address 46 also provides higher availability and load sharing with respect to the multicasting of the original media stream 14.
- Use of an anycast IP address as the SSM source address for the media source provides this capability as well.
- retransmission source 7OA re-originates media stream 14 as multicast media stream 62 and retransmission source 7OB re-originates media stream 14 as multicast media stream 64.
- the multicast packets 72 for multicast media stream 62 and the multicast packets 74 from multicast media stream 64 each use the same source IP address 46.
- Any routers 42 in the IP network 10 receiving both media streams 62 and 64 with the same source address automatically drop packets for one of the two streams according to a basic characteristic of multicast routing known as "reverse path forwarding". For packets being forwarded on a multicast tree, only those received from the upstream branch leading to the source IP address at the root of the tree are accepted for forwarding. In this example, the router 42 drops the multicast packets 74 for media stream 64 and only routes the multicast packets 72 for media stream 62 to the media stream receiver 24. If retransmission source 7OA is ever disabled, the router 42 will re-compute internal routing metrics and then automatically start routing the multicast packets 74 for media stream 64 to media stream receiver 24. Accordingly, using the shared IP anycast address 46 and the SSM source address also provides redundancy and load sharing for the multicast media stream source.
- the shared IP source address 46 still increases retransmission repair redundancy and load balancing as described above in FIG. 3 by allowing either of the retransmission sources 7OA or 7OB to receive and respond to the retransmission requests 44 sent by any of the media stream receivers 24 as described above in FIG. 3. It is also possible that one of the retransmission sources 70 may end up re-originating the multicast media stream to the receiver 24 while the other retransmission source 70 provides media stream repair support by receiving unicast retransmission requests 44 and responding back with media repair packets 34.
- a media stream receiver joining a new RTP session may have no idea what packets are needed to render the current stream. Also since multicast video sessions may be involved, the media stream receiver is in all likelihood "behind" the multicast stream in time and may need to "catch up". This is important because the media stream receiver may not be able to render the media stream until it receives an intra-coded frame that may have passed by shortly before the media stream receiver attempts to join the multicast session.
- a fast stream join scheme uses a variant of the repair schemes described above.
- Multiple different multicast media streams 82A-82N are generated by different media stream sources 80A-80N, respectively.
- Synchronization SouRCes (SSRCs ) used by the media streams are communicated out of band to the media stream receivers 24 in the SDP messages 84.
- the SDP messages 84 also include the feedback target IP addresses for the one or more retransmission systems 86 associated with repairing the multicast media streams as described above.
- a media stream receiver 24 detects a request to join a new multicast media stream and sends a unicast request 96 to the retransmission system 86 specifying the new channel which the receiver wishes to receive.
- a channel join request may detected, for example, by a set top box that detects a user using user interface 94 to select a new or different multicast media channel.
- the unicast channel join request 96 in one embodiment is substantially the same RTCP NACK retransmission request message described above in FIGS. 1-4.
- the message 96 is a NACK packet containing a Picture Loss Indication (PLI) 98.
- PLI Picture Loss Indication
- the PLI indication 98 notifies the retransmission system 86 to send all of the information needed to join a new identified media stream 102. This is different from the retransmission request messages 28 in FIG. 1 that instead requests specific lost packets from an already connected media stream.
- the channel join request 96 is sent by the media stream receiver 24 to the feedback target address 100 for the retransmission system 86 associated with the identified new media stream 102. It is worth noting that initiation of the fast channel/stream join scheme is similar to the repair scheme described above since it exploits the same NACK and retransmission machinery.
- the retransmission system 86 performs the following operations when the channel join request 96 is received.
- the retransmission system 86 determines which media stream channel the receiver 24 is joining using the SSRC 102 in the unicast NACK channel join request 96 and the destination transport address and port of the NACK packet. As described above, the SSRC 102 was previously communicated to the receiver 24 in the channel description of SDP message 84.
- the retransmission system 86 uses the cached video information for the selected media stream to extract from the cache all the elements the receiver 24 may need to "prime" its decoder 97.
- This may include a Moving Pictures Experts Group (MPEG) Program Association Table (PAT) and Program Map Table (PMT) elements, Encryption Control Messages (ECMs) and possibly other non-video data needed by the decoder 97.
- the retransmission system 86 in operation 114 constructs a Real-time Transport Control Protocol (RTCP) APPlication-specific (APP) decoder packet 88 and in operation 116 sends the decoder priming packet 88 to the media stream receiver 26 that requested the channel join.
- RTCP Real-time Transport Control Protocol
- APP APPlication-specific
- the retransmission system 86 references back into media cache 87 for the RTP data containing the most recent cached intra-coded frame (I-frame).
- the retransmission system 86 sends the cached RTP packets containing the I-frame and all subsequent frames 90 up to a current cache time to the media stream receiver 24.
- the identified frames 90 are burst to the receiver 24 at a much faster speed than what the media in the packets is actually rendered by receiver 24 (i.e., faster than real-time). This speeds up the channel join process by allowing the receiver to render video going back to the previous I- frame.
- the portions of the stream sent back are not necessary to simply join the new stream.
- the receiver can join the stream just by knowing the SDP for the media stream and performing a conventional IGMP join operation without asking for channel join.
- the burst of the cached data back from the prior I-frame allows the receiver to start rendering before the join completes and the next I-frame arrives. If the data were not burst faster than real-time, the receiver would not be able to "catch up" with the multicast stream, which is ahead of the receiver in time. Thus, the burst frames are essentially "back filling" to the previous I-frame so the receiver is able to render media prior to when the next I-frame arrives on the multicast stream.
- the decoder 97 in the receiver 24 is primed with the information from the decoder packet 88 and media frames 90. After being primed and receiving the burst, the receiver 24 can join the multicast group for the new stream and can start rendering any subsequent media from the joined multicast media stream 82N.
- the fast channel join scheme can exploit any of the anycast-based availability and load sharing features provided either by the look aside mode scheme in FIGS. 2 and 3 or the source mode scheme shown in FIG. 4.
- Various embodiments are anticipated whereby the repair or channel join schemes are used by service providers offering IPTV service over a variety of access networks, including, but not limited to, Digital Subscriber Loop (DSL), cable, WiMax, etc.
- DSL Digital Subscriber Loop
- WiMax Wireless Fidelity
- the media repair and channel join schemes are essentially stateless. They maintain no state about individual receivers except during a repair or channel join operation. This allows the system to scale much better than a system in which permanent or semi-permanent state is kept in the retransmission system about each receiver potentially wishing to request repair or channel join operations.
- the normal routing states in the routers in the IP network provide any knowledge required for ensuring retransmission requests or channel join requests are directed to operational retransmission systems 18.
- the routing metrics in the IP network routers also, as a by-product, provide a degree of load balancing.
- the media source, retransmission systems, and media stream receivers associated with a media stream are not required to keep track of which media stream sources or which retransmission systems are operational, or which media stream receivers are currently connected to which media streams.
- the RTP unicast repair scheme also does not require the retransmission systems to remember what repair or channel join packets have been previously received or sent to media stream receivers.
- Each retransmission or channel join request can be a single unitary request that is answered with a single response or group of responses by the retransmission system with no required state knowledge of what other repair operations have been previously performed for the requesting receiver.
- RTP protocol machinery with the above described extensions allows the creation of a unified technique for both retransmission-based media stream repair and fast channel joining (i.e., stream joining).
- Operation in either the lookaside mode or source mode can use anycast-based feedback addressing to improve scalability, robustness, and performance. Separate operations are unified with common mechanisms and low protocol, state, and computational overhead.
- the system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.
Abstract
The Real-time Transport Protocol (RTP) and its related standards define a retransmission packet format and a way to give feedback via Negative Acknowledge (NACK) packets for data that has been lost. In one embodiment, a unicast RTP repair session is associated with a main Source Specific Multicast (SSM) multicast session. Real-time Transport Control Protocol (RTCP) NACK packets(28) are then used for feedback to a SSM feedback target address. This dynamically instantiates unicast RTP repair for multicast sessions. The repair scheme can be used for repairing multicast channels or joining new multicast channels. In another embodiment, a media transmission device shares an IP address with one or more other media transmission devices. The shared IP address can also be used to route multiple identical multicast media streams(14) to different media stream receivers(24).
Description
RETRANSMISSION-BASED STREAM REPAIR AND STREAM JOIN
Technical Field
The present disclosure relates generally to a scheme for retransmission-based repair and fast stream join for Internet Protocol (IP) based media streams.
Background
The Real-time Transport Protocol (RTP) and its related standards define a retransmission packet format and a way to give feedback via Negative ACKnowledgment (NACK) packets that data has been lost. The following standards RTP (RFC3550), RTP Retransmission (RFC4588), RTCP Feedback (RFC4585), and RTCP with SSM Sessions (draft-ietf-avt-rtcpssm-11.txt) are all incorporated by reference and describe unicast feedback and retransmission for unicast sessions, and unicast feedback with multicast retransmission for multicast sessions.
However, the RTP protocol suite has limitations when used with certain types of Internet Protocol (IP) media transmissions, such as transmitting streaming video to different endpoints. For example, neither RTP, nor any other common media transmission protocol, can perform unicast repair of multicast media streams or quickly and efficiently switch among different multicast media streams without loss of data.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows a repair scheme used in a lookaside mode for multicast media streams. FIG.2 shows the repair scheme in FIG. 1 using IP anycast addresses.
FIG. 3 is a diagram showing how different media streams can be associated with different IP anycast addresses.
FIG. 4 is a diagram showing how the repair scheme is used in a source mode.
FIG. 5 is a diagram showing another embodiment of a retransmission scheme used for channel joining.
FIG. 6 is a flow diagram explaining in more detail the retransmission scheme shown in FIG. 5.
DESCRIPTION OF EXAMPLE EMBODIMENTS OVERVIEW
A Real-time Transport Protocol (RTP)-based unicast repair scheme is used for repairing errors in RTP multicast streams. By modeling the joining of a new media stream as a repair operation, the repair scheme is extended to also rapidly join media channels. It should be noted that the terms channel and stream are used interchangeably below.
Referring to FIG. 1, a media stream source 12 may be a server, computer, or any other type of network processing device that can source IP media, such as video, audio, voice, data, etc., over an Internet Protocol (IP) network 10. In this example, the media stream source 12 transmits a multicast media stream 14 over the IP network 10 which is received by different media stream receivers 24A-24N and also by a retransmission system 18.
The media stream receivers 24 can be any device that receives and stores or renders the multicast media stream 14. For example, the media stream receivers 24 could be Set Top Boxes (STB), Digital Video Recorders (DVR), computer terminals, Personal Computers (PCs), televisions with IP interfaces, Voice over IP (VoIP) phones, cell phones, Personal Digital Assistants (PDA), etc. The retransmission system 18 can be any type of media server that caches and retransmits portions of the multicast media stream 14. The media stream
source 12 and retransmission system 18 are shown as separate devices but could reside in the same physical location and be connected together via a Local Area Network (LAN) or other backplane connectivity.
In one embodiment, a Source Specific Multicast (SSM) multicast session is established for transmitting the multicast media stream 14 between the media stream source 12 and one or more of the media stream receivers 24. The media stream source 12 knows the IP addresses and ports to use for transmitting a particular media stream. The retransmission system 18 knows what IP addresses and ports to use for receiving the media stream and what address and port to use for sending retransmissions. The media stream receivers 24 know what IP address and port to listen for the media stream and the retransmissions, and where to send retransmission requests. All of this address and port information can be described using Session Description Protocol (SDP), but other media description schemes could be used.
The feedback target IP address 16 is used by the media stream receivers 24 as a destination address for requesting retransmissions for portions of the multicast media stream 14. For example, packets from the media stream 14 may not successfully arrive at particular media stream receivers, or may be received in a corrupted state.
The media stream receivers 24 send retransmission requests 28 to the retransmission system 18 associated with the feedback target IP address 16 that includes information 30 identifying the lost media packets. In one example, retransmission requests 28 are unicast Real-time Transport Control Protocol (RTCP) Negative ACKnowledge (NACK) packets that use the feedback target address 16 as a destination address 29. Sending the unicast RTCP NACK packet 28 to the retransmission system 18 dynamically instantiates a unicast RTP repair session from the retransmission system to the requesting receiver, if one does not already exist.
The retransmission system 18 includes a media cache 22 that caches the recent history of packets from the multicast media stream 14. During the unicast RTP repair session, lost packets for media stream 14 are identified in lost packet information 30 of the retransmission request 28. The retransmission system 18 identifies the packets in media cache 22 corresponding to the lost or corrupted packet information 30 in retransmission request 28.
The identified media packets in media cache 22 are sent as unicast media repair packets 34 back to the requesting media stream receiver 28. The media stream receiver 24 then inserts the received unicast media repair packets 34 into corresponding lost packet locations in the media stream 14. Thus, in one embodiment, a repair session uses unicast NACK packets 28 and unicast media repair packets 34 for repairing a multicast media session.
The media configuration shown in FIG. 1 is referred to as a "lookaside mode" because the retransmission system 18 (repair element) is not required to relay the original media stream 14 to the media stream receivers 24. Instead, the media stream source 12 multicasts the media stream 14 directly to the receivers 24. The lookaside mode may produce higher availability since the media stream 14 is not necessarily disrupted if the retransmission system 18 crashes or becomes unavailable.
In this example, only the unicast repair function ceases when the retransmission system 18 fails. Higher performance may also be provided since the retransmission system 18 only receives and caches the multicast media stream 14 and does not also have to retransmit the media stream 14 to the media stream receivers 24. Thus, by only providing media stream repair, the constant work factor for the retransmission system 18 is halved.
In the lookaside mode, the retransmission system 18 is distinguished from the media stream source 12 by using a feedback target address 16 for the retransmission system 18 that is different from the source IP address associated with the SSM media stream source 12.
IP Anycast Addressing
Referring to FIG. 2, in order to provide both high availability and load sharing, one embodiment of the repair scheme uses an IP anycast address 46 as the feedback target address for the retransmission system 18. This allows repair operations to be adaptively directed to the optimal currently available retransmission system 18A or 18B. The anycast addressing scheme exploits the metrics of IP unicast routing that automatically route packets to network processing devices associated with the cheapest IP routing cost.
To explain in more detail, message 40 identifies a single IP anycast address 46 for multiple different retransmission systems 18A and 18B available for repairing the multicast media stream 14. This SDP is provided to both the retransmission systems 18A and 18B, as well as to the receivers so that they will direct their retransmission requests to that anycast feedback address. Both retransmission system 18A and 18B cache the media stream 14 and are available for retransmitting lost packets to any of the media stream receivers 24A-24D.
Both of the retransmission systems 18A and 18B share the same IP anycast source address 46 identified in message 40. An IP anycast address refers to a unicast IP address that is used as a destination address simultaneously by multiple network processing devices. In this example, the network processing devices sharing IP address 46 include retransmission systems 18A and 18B.
The retransmission systems 18A and 18B and the media stream receivers 24 operate in substantially the same manner as described above in FIG. 1. In this example, all of the media stream receivers 24A-24D each receive the same multicast media stream 14 from media stream source 12. Alternatively, the media stream receivers 24 could indirectly receive the multicast media stream 14 via a separate multicast stream sourced from one of the retransmission systems 18A or 18B. This embodiment is referred to as "source mode" and is described in more detail below in FIG. 4.
Any of the media stream receivers 24A-24D may detect lost or corrupted packets or frames from the multicast media stream 14. In response, the receiver 24 sends out a unicast NACK retransmission request message 44. For explanation purposes, each of the media stream receivers 24A-24D in FIG. 2 is currently receiving the media stream 14 and one or more of them has identified lost packets from the media stream 14. Respectively, the receivers 24A-24D experiencing loss or corruption send out retransmission request messages 44A-44D.
Each of the retransmission request messages 44A-44D includes the same IP anycast destination address 46 along with the associated media stream receiver source address 48A- 48D, respectively. The retransmission request messages 44A-44D also include lost packet information identifying which of the packets were lost from the multicast media stream 14.
Routers 42 and 44 in the IP network 10 use internal routing metrics to select which of the retransmission systems 18 A or 18B has the cheapest IP routing cost for routing the messages 44A-44D. Since the IP anycast address 46 is shared by two different network processing devices 18A and 18B, the conventional routing metrics in the routers 42 and 43 will automatically select one of the two devices 18A or 18B for forwarding any messages 44A-44D. In this example, router 42 determines that retransmission system 18A has the shortest routing path for the retransmission request messages 44A and 44B received from receivers 24A and 24B, respectively. Alternatively, router 43 determines that retransmission system 18B has the shortest routing path for the retransmission request messages 44C and 44D received from receivers 24C and 24D, respectively.
Retransmission system 18A receives unicast NACK retransmission request messages 44A and 44B and retransmission system 18B receives unicast NACK retransmission request messages 44C and 44D. The retransmission system 18A responds back by sending unicast media repair packets from its cache of multicast media stream 14 back to receivers 24A and
24B. For example, retransmission system 18 A sends unicast media repair packets 34 back to the media stream receiver 24B identified in message 44B. Retransmission system 18B responds to retransmission request messages 44C and 44D by sending unicast media repair packets from its cache of multicast media stream 14 back to receivers 24C and 24D, respectively.
This distributed routing of retransmission requests 44A-44D increases both availability and load sharing capacity while using substantially the same repair scheme described above in FIG. 1. For example, if either of the retransmission systems 18A or 18B is disabled, the routers 42 and 44 will automatically drop the disabled retransmission system from internal routing tables. Accordingly, repair requests previously routed to the disabled retransmission system 18 are automatically rerouted to a different one of the operational retransmission systems 18.
FIG. 3 shows different IP anycast addresses used as feedback addresses for different media streams 54 and 56. This further increases the scalability of the media repair scheme by allowing one or more different retransmission systems 50 and 52 to be associated with different multicast media streams.
For example, one or more retransmission systems 50 can be specifically designated to provide media packet repair for a particular multicast media stream 54. The feedback target IP anycast address identified in the Source Specific Multicast (SSM) multicast session for multicast media stream 54 is used as the source address for each of the retransmission systems 50. Similarly, one or more retransmission systems 52 can be designated to provide media packet repair support for a different multicast media stream 56. The feedback target IP anycast source address identified in the SSM multicast session for the multicast media stream 56 is used as the source address for each of retransmission systems 52.
In this example, media stream receiver 24B is receiving packets for multicast media stream 54. If any of the multicast packets are lost, media stream receiver 24B sends a unicast NACK retransmission request message 58 to the IP anycast destination address X associated with multicast media stream 54. The routers in the IP infrastructure (not shown) automatically route the retransmission request message 58 to one of the retransmission systems 50 which then sends back unicast media repair packets containing the identified lost packets.
Thus, different retransmission systems can be associated with different media streams to further increase the repair scheme scalability. However, in other embodiments, a retransmission system 50 may provide repair support for more than one media stream.
FIG. 4 shows an alternative "source mode" for the repair scheme. In the source mode, retransmission sources 70 provide media stream repair and also operate as SSM distribution sources for the multicast stream 14 originally generated by media stream source 12. The media stream source 12 could be a local encoder, a local splicer, or a separate media stream server operating remotely in the IP network 10 from the retransmission sources 7OA and 7OB.
The retransmission source 7OA caches the original media stream 14 in media cache 22A and if necessary "re-sources" the received media stream 14, operating as a legal RTP mixer/translator according to the RTP specifications. Similarly, retransmission source 7OB retransmits the original media stream 14 cached in media cache 22B as multicast media stream 64.
In the source mode, the retransmission sources 7OA and 7OB still receive unicast NACK retransmission request messages 44 from the media stream receivers 24 when multicast media stream packets are lost. The retransmission sources 70 accordingly send back unicast media repair packets 34 containing the requested lost media.
In one embodiment, the two retransmission sources 7OA and 7OB also still share the same IP source address 46. This common IP source address 46 for the feedback target can again be identified for the multicast media session using out-of-band or in-band messaging. The messages 60 exchanged between the media stream source 12, retransmission sources 70, and the media stream receivers 24, associate media stream 14 with feedback target IP anycast address 46.
Sharing the same IP destination address 46 provides high availability and load sharing for the repair scheme similar in a similar manner as described above in FIG. 2. However, both retransmission sources 7OA and 7OB in FIG. 4 also operate as retransmission sources for the media stream 14. Therefore, sharing the same SSM source address 46 also provides higher availability and load sharing with respect to the multicasting of the original media stream 14. Use of an anycast IP address as the SSM source address for the media source provides this capability as well.
For example, retransmission source 7OA re-originates media stream 14 as multicast media stream 62 and retransmission source 7OB re-originates media stream 14 as multicast media stream 64. The multicast packets 72 for multicast media stream 62 and the multicast packets 74 from multicast media stream 64 each use the same source IP address 46.
Any routers 42 in the IP network 10 receiving both media streams 62 and 64 with the same source address automatically drop packets for one of the two streams according to a basic characteristic of multicast routing known as "reverse path forwarding". For packets being forwarded on a multicast tree, only those received from the upstream branch leading to the source IP address at the root of the tree are accepted for forwarding. In this example, the router 42 drops the multicast packets 74 for media stream 64 and only routes the multicast packets 72 for media stream 62 to the media stream receiver 24.
If retransmission source 7OA is ever disabled, the router 42 will re-compute internal routing metrics and then automatically start routing the multicast packets 74 for media stream 64 to media stream receiver 24. Accordingly, using the shared IP anycast address 46 and the SSM source address also provides redundancy and load sharing for the multicast media stream source.
The shared IP source address 46 still increases retransmission repair redundancy and load balancing as described above in FIG. 3 by allowing either of the retransmission sources 7OA or 7OB to receive and respond to the retransmission requests 44 sent by any of the media stream receivers 24 as described above in FIG. 3. It is also possible that one of the retransmission sources 70 may end up re-originating the multicast media stream to the receiver 24 while the other retransmission source 70 provides media stream repair support by receiving unicast retransmission requests 44 and responding back with media repair packets 34.
Extension of Repair Scheme for Fast Stream Join
Several observations can be made with respect to a stream join as compared with a media stream repair operation. A media stream receiver joining a new RTP session may have no idea what packets are needed to render the current stream. Also since multicast video sessions may be involved, the media stream receiver is in all likelihood "behind" the multicast stream in time and may need to "catch up". This is important because the media stream receiver may not be able to render the media stream until it receives an intra-coded frame that may have passed by shortly before the media stream receiver attempts to join the multicast session.
Referring to FIG. 5, a fast stream join scheme (alternatively referred to as a fast channel join) uses a variant of the repair schemes described above. Multiple different
multicast media streams 82A-82N are generated by different media stream sources 80A-80N, respectively. Synchronization SouRCes (SSRCs ) used by the media streams are communicated out of band to the media stream receivers 24 in the SDP messages 84. The SDP messages 84 also include the feedback target IP addresses for the one or more retransmission systems 86 associated with repairing the multicast media streams as described above.
A media stream receiver 24 detects a request to join a new multicast media stream and sends a unicast request 96 to the retransmission system 86 specifying the new channel which the receiver wishes to receive. A channel join request may detected, for example, by a set top box that detects a user using user interface 94 to select a new or different multicast media channel.
The unicast channel join request 96 in one embodiment is substantially the same RTCP NACK retransmission request message described above in FIGS. 1-4. However, in this embodiment, the message 96 is a NACK packet containing a Picture Loss Indication (PLI) 98. The PLI indication 98 notifies the retransmission system 86 to send all of the information needed to join a new identified media stream 102. This is different from the retransmission request messages 28 in FIG. 1 that instead requests specific lost packets from an already connected media stream.
The channel join request 96 is sent by the media stream receiver 24 to the feedback target address 100 for the retransmission system 86 associated with the identified new media stream 102. It is worth noting that initiation of the fast channel/stream join scheme is similar to the repair scheme described above since it exploits the same NACK and retransmission machinery.
Referring to both FIG. 5 and FIG. 6, the retransmission system 86 performs the following operations when the channel join request 96 is received. In operation 110, the
retransmission system 86 determines which media stream channel the receiver 24 is joining using the SSRC 102 in the unicast NACK channel join request 96 and the destination transport address and port of the NACK packet. As described above, the SSRC 102 was previously communicated to the receiver 24 in the channel description of SDP message 84.
In operation 112, the retransmission system 86 uses the cached video information for the selected media stream to extract from the cache all the elements the receiver 24 may need to "prime" its decoder 97. This may include a Moving Pictures Experts Group (MPEG) Program Association Table (PAT) and Program Map Table (PMT) elements, Encryption Control Messages (ECMs) and possibly other non-video data needed by the decoder 97. The retransmission system 86 in operation 114 constructs a Real-time Transport Control Protocol (RTCP) APPlication-specific (APP) decoder packet 88 and in operation 116 sends the decoder priming packet 88 to the media stream receiver 26 that requested the channel join.
In operation 118, the retransmission system 86 references back into media cache 87 for the RTP data containing the most recent cached intra-coded frame (I-frame). In operation 120, the retransmission system 86 sends the cached RTP packets containing the I-frame and all subsequent frames 90 up to a current cache time to the media stream receiver 24. The identified frames 90 are burst to the receiver 24 at a much faster speed than what the media in the packets is actually rendered by receiver 24 (i.e., faster than real-time). This speeds up the channel join process by allowing the receiver to render video going back to the previous I- frame.
The portions of the stream sent back are not necessary to simply join the new stream. The receiver can join the stream just by knowing the SDP for the media stream and performing a conventional IGMP join operation without asking for channel join. The burst of the cached data back from the prior I-frame allows the receiver to start rendering before the join completes and the next I-frame arrives. If the data were not burst faster than real-time,
the receiver would not be able to "catch up" with the multicast stream, which is ahead of the receiver in time. Thus, the burst frames are essentially "back filling" to the previous I-frame so the receiver is able to render media prior to when the next I-frame arrives on the multicast stream.
The decoder 97 in the receiver 24 is primed with the information from the decoder packet 88 and media frames 90. After being primed and receiving the burst, the receiver 24 can join the multicast group for the new stream and can start rendering any subsequent media from the joined multicast media stream 82N.
As with the basic packet repair operations, the fast channel join scheme can exploit any of the anycast-based availability and load sharing features provided either by the look aside mode scheme in FIGS. 2 and 3 or the source mode scheme shown in FIG. 4. Various embodiments are anticipated whereby the repair or channel join schemes are used by service providers offering IPTV service over a variety of access networks, including, but not limited to, Digital Subscriber Loop (DSL), cable, WiMax, etc.
It is also worth noting that the media repair and channel join schemes are essentially stateless. They maintain no state about individual receivers except during a repair or channel join operation. This allows the system to scale much better than a system in which permanent or semi-permanent state is kept in the retransmission system about each receiver potentially wishing to request repair or channel join operations. The normal routing states in the routers in the IP network provide any knowledge required for ensuring retransmission requests or channel join requests are directed to operational retransmission systems 18. The routing metrics in the IP network routers also, as a by-product, provide a degree of load balancing.
Thus, the media source, retransmission systems, and media stream receivers associated with a media stream are not required to keep track of which media stream sources
or which retransmission systems are operational, or which media stream receivers are currently connected to which media streams.
The RTP unicast repair scheme also does not require the retransmission systems to remember what repair or channel join packets have been previously received or sent to media stream receivers. Each retransmission or channel join request can be a single unitary request that is answered with a single response or group of responses by the retransmission system with no required state knowledge of what other repair operations have been previously performed for the requesting receiver.
Thus, the use of RTP protocol machinery with the above described extensions allows the creation of a unified technique for both retransmission-based media stream repair and fast channel joining (i.e., stream joining). Operation in either the lookaside mode or source mode can use anycast-based feedback addressing to improve scalability, robustness, and performance. Separate operations are unified with common mechanisms and low protocol, state, and computational overhead.
The system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.
For the sake of convenience, the operations are described as various interconnected functional blocks or distinct software modules. This is not necessary, however, and there may be cases where these functional blocks or modules are equivalently aggregated into a single logic device, program or operation with unclear boundaries. In any event, the functional blocks and software modules or features of the flexible interface can be implemented by themselves, or in combination with other operations in either hardware or software.
Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention may be modified in arrangement and detail without departing from such principles. I/We claim all modifications and variation coming within the spirit and scope of the following claims.
Claims
1. An apparatus comprising: a media retransmission device that caches portions of an Internet Protocol (IP) transmitted media stream and shares an IP address with one or more other media retransmission devices, the shared IP address causing retransmission requests from particular media stream receivers to be distributed back to the media retransmission device according to IP network topology relationships between the media retransmission device and a subset of media stream receivers.
2. The apparatus according to claim 1 wherein the shared IP address causes IP network routers to distribute the retransmission requests sent from the media stream receivers to different media retransmission devices sharing the IP address and having a cheapest IP routing cost.
3. The apparatus according to claim 1 wherein the shared IP address is an IP anycast address.
4. The apparatus according to claim 1 wherein the media retransmission device caches multicast media stream packets from a media stream source and receives unicast retransmission request packets from the media stream receivers that use the shared IP address.
5. The apparatus according to claim 4 wherein the media retransmission device sends unicast media repair packets back to the media stream receivers sending the retransmission request packets containing lost portions of the multicast media stream.
6. The apparatus according to claim 1 wherein the retransmission requests are Real-time Transport Control Protocol (RTCP) Negative Acknowledgment (NACK) packets that use the shared IP address as a destination address.
7. The apparatus according to claim 1 wherein the media retransmission device operates as both an original transmission source and retransmission repair source for the media stream.
8. The apparatus according to claim 1 wherein the media retransmission device operates only as a retransmission source for the media stream and a second transmission device operates as an original transmission source for the media stream.
9. The apparatus according to claim 1 wherein the received retransmission requests and the same shared IP address when identified as a media stream repair request cause the media retransmission device to send back cached media stream packets lost or corrupted from the media stream and when identified as a channel join request cause the media retransmission device to send decoder information and a group of cached media stream frames required for decoding a new media stream.
10. An apparatus comprising: a media stream receiver configured to send a unicast retransmission request for either requesting retransmission for a portion of a currently received multicast media stream or requesting joining a new multicast media stream, the media stream receiver further configured to receive back unicast repair packets that either contain the requested portion of the currently received media stream or contain a portion of the requested new media stream.
11. The apparatus according to claim 10 wherein the unicast retransmission request used for requesting retransmission of the currently received media stream is a Realtime Transport Control Protocol (RTCP) Negative Acknowledgement (NACK) packet and the unicast retransmission request used for requesting joining the new media stream is a RTCP NACK packet reporting Picture Loss Indication (PLI).
12. The apparatus according to claim 10 wherein the media stream receiver sends a lost packet message in the retransmission request that causes an identified portion of the currently received media stream to be transmitted back and sends a channel join message to cause a decoder information portion of a new media stream necessary for decoding the new media stream to be transmitted back.
13. The apparatus according to claim 10 wherein the media stream receiver uses an Internet Protocol (IP) anycast destination address in the retransmission request that is shared by multiple different retransmission devices, the IP anycast destination address causing the retransmission request to be routed to one of the multiple different retransmission devices with a cheapest routing cost.
14. An apparatus comprising : a media transmission device configured to cache a portion of a multicast media stream, the media transmission device further configured to receive a unicast Internet Protocol (IP) message requesting retransmission of at least a portion of the multicast media stream and then unicast back cached portions of the multicast media stream corresponding with the requested portion of the multicast media stream.
15. The apparatus according to claim 14 wherein the media transmission device operates as both an original transmission source that multicasts the media stream and as a retransmission source for retransmitting back cached portions of the media stream requested in the unicast IP message.
16. The apparatus according to claim 14 wherein the media transmission device is configured to identify requests in the unicast IP message to retransmit lost media packets from the multicast media stream and then send back portions of the cached multicast media stream corresponding with the lost media packets.
17. The apparatus according to claim 14 wherein the media transmission device is configured to identify requests in the unicast IP message to join a new media stream and then burst cached data back allowing a receiver to start rendering the new media stream.
18. The apparatus according to claim 17 wherein the media transmission device is configured to send decoder information and burst a group of the cached media stream that includes an intra-coded media frame (I-frame) required for decoding the portions of the new media stream prior to the next I-frame to be transmitted on the native multicast for that stream.
19. The apparatus according to claim 14 wherein the media transmission device is configured to transmit a multicast media stream and share an Internet Protocol (IP) source address with other media transmission devices transmitting the same multicast media stream, the shared IP source address causing only one of the multiple multicast media streams to be routed to any one media stream receiver.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200780022360XA CN101473571B (en) | 2006-09-11 | 2007-08-20 | Retransmission-based stream repair and stream join |
EP07814245.2A EP2062384B1 (en) | 2006-09-11 | 2007-08-20 | Retransmission-based stream repair and stream join |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US82526806P | 2006-09-11 | 2006-09-11 | |
US60/825,268 | 2006-09-11 | ||
US11/561,237 | 2006-11-17 | ||
US11/561,237 US8031701B2 (en) | 2006-09-11 | 2006-11-17 | Retransmission-based stream repair and stream join |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2008033644A2 true WO2008033644A2 (en) | 2008-03-20 |
WO2008033644A3 WO2008033644A3 (en) | 2008-10-02 |
Family
ID=39169595
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/076264 WO2008033644A2 (en) | 2006-09-11 | 2007-08-20 | Retransmission-based stream repair and stream join |
Country Status (4)
Country | Link |
---|---|
US (3) | US8031701B2 (en) |
EP (1) | EP2062384B1 (en) |
CN (1) | CN101473571B (en) |
WO (1) | WO2008033644A2 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7681101B2 (en) | 2007-04-16 | 2010-03-16 | Cisco Technology, Inc. | Hybrid corrective scheme for dropped packets |
US7937531B2 (en) | 2007-02-01 | 2011-05-03 | Cisco Technology, Inc. | Regularly occurring write back scheme for cache soft error reduction |
US7940644B2 (en) | 2007-03-14 | 2011-05-10 | Cisco Technology, Inc. | Unified transmission scheme for media stream redundancy |
US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US8218654B2 (en) | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
US8427948B2 (en) | 2008-02-07 | 2013-04-23 | British Telecommunications Public Limited Company | Communications network |
US8769591B2 (en) | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
US8935736B2 (en) | 2008-12-12 | 2015-01-13 | Huawei Technologies Co., Ltd. | Channel switching method, channel switching device, and channel switching system |
US9015555B2 (en) | 2011-11-18 | 2015-04-21 | Cisco Technology, Inc. | System and method for multicast error recovery using sampled feedback |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8514762B2 (en) * | 2007-01-12 | 2013-08-20 | Symbol Technologies, Inc. | System and method for embedding text in multicast transmissions |
US20080253369A1 (en) * | 2007-04-16 | 2008-10-16 | Cisco Technology, Inc. | Monitoring and correcting upstream packet loss |
US8634310B2 (en) * | 2007-06-26 | 2014-01-21 | Qualcomm Incorporated | Methods and apparatus for improved program acquisition for use with MPEG-2 based systems |
US8386629B2 (en) * | 2007-12-27 | 2013-02-26 | At&T Intellectual Property I, L.P. | Network optimized content delivery for high demand non-live contents |
US9705935B2 (en) * | 2008-01-14 | 2017-07-11 | Qualcomm Incorporated | Efficient interworking between circuit-switched and packet-switched multimedia services |
US8787153B2 (en) * | 2008-02-10 | 2014-07-22 | Cisco Technology, Inc. | Forward error correction based data recovery with path diversity |
FR2927749B1 (en) * | 2008-02-14 | 2010-12-17 | Canon Kk | METHOD AND DEVICE FOR TRANSMITTING DATA, IN PARTICULAR VIDEO. |
US8499323B2 (en) * | 2008-04-16 | 2013-07-30 | Nvidia Corporation | Method and apparatus for outputting media content |
US8379083B1 (en) * | 2008-07-17 | 2013-02-19 | Sprint Communications Company L.P. | Simultaneous viewing and reliable recording of multimedia content over a network |
US10063934B2 (en) * | 2008-11-25 | 2018-08-28 | Rovi Technologies Corporation | Reducing unicast session duration with restart TV |
EP2200220A1 (en) * | 2008-12-22 | 2010-06-23 | Thomson Licensing | Method and apparatus for reliable multicast streaming |
US8166179B2 (en) * | 2009-01-30 | 2012-04-24 | Cisco Technology, Inc. | Media streaming through a network address translation (NAT) device |
US9077784B2 (en) * | 2009-02-06 | 2015-07-07 | Empire Technology Development Llc | Media file synchronization |
US8189492B2 (en) * | 2009-03-18 | 2012-05-29 | Microsoft Corporation | Error recovery in an audio-video multipoint control component |
CN101938456B (en) | 2009-06-30 | 2014-03-12 | 华为技术有限公司 | Method, device and system for reducing media delays |
CN101588494B (en) * | 2009-06-30 | 2011-09-21 | 华为技术有限公司 | Method for processing media stream, communication system, and relative devices |
US8199752B2 (en) * | 2009-10-02 | 2012-06-12 | Limelight Networks, Inc. | Enhanced anycast for edge server selection |
US9168946B2 (en) * | 2010-03-19 | 2015-10-27 | Javad Gnss, Inc. | Method for generating offset paths for ground vehicles |
US9510061B2 (en) * | 2010-12-03 | 2016-11-29 | Arris Enterprises, Inc. | Method and apparatus for distributing video |
FR2977101A1 (en) * | 2011-06-24 | 2012-12-28 | France Telecom | RETRANSMISSION OF DATA LOST BETWEEN A TRANSMITTER AND A RECEIVER |
KR20130078463A (en) * | 2011-12-30 | 2013-07-10 | 삼성전자주식회사 | Multicast service method and apparatus in mobile communication system |
US9288136B2 (en) * | 2012-09-21 | 2016-03-15 | Cisco Technology, Inc. | Method and apparatus for in-band channel change for multicast data |
US20150138972A1 (en) * | 2012-11-23 | 2015-05-21 | Broadcom Corporation | Digital Subscriber Line (DSL) Communication System with Remote Back-Pressure |
KR101506770B1 (en) * | 2012-12-28 | 2015-03-27 | 삼성에스디에스 주식회사 | System and method for data transmission |
US9019992B2 (en) | 2013-01-08 | 2015-04-28 | Tangome, Inc. | Joint retransmission and frame synchronization for error resilience control |
US10567489B2 (en) * | 2013-03-15 | 2020-02-18 | Time Warner Cable Enterprises Llc | System and method for seamless switching between data streams |
US9906645B2 (en) * | 2013-04-03 | 2018-02-27 | Qualcomm Incorporated | Rewinding a real-time communication session |
JP2014230055A (en) * | 2013-05-22 | 2014-12-08 | ソニー株式会社 | Content supply device, content supply method, program, and content supply system |
CN104284135B (en) * | 2013-07-02 | 2017-11-24 | 华为技术有限公司 | Video transmission method and equipment |
US9363480B2 (en) | 2014-08-20 | 2016-06-07 | Cisco Technology, Inc. | Obtaining replay of audio during a conference session |
US9678864B2 (en) | 2014-12-03 | 2017-06-13 | Seagate Technology Llc | Data reallocation upon detection of errors |
US9571407B2 (en) | 2014-12-10 | 2017-02-14 | Limelight Networks, Inc. | Strategically scheduling TCP stream transmissions |
US11769119B1 (en) * | 2015-04-15 | 2023-09-26 | Allstate Insurance Company | Autonomous car repair |
US10110930B2 (en) | 2015-07-02 | 2018-10-23 | Dialogic Corporation | Robust packet loss handling in recording real-time video |
CN107124288B (en) * | 2016-02-24 | 2021-01-29 | 大唐移动通信设备有限公司 | Message processing method and device |
US10200428B1 (en) * | 2016-03-30 | 2019-02-05 | Amazon Technologies, Inc. | Unicast routing of a media stream to subscribers |
US20170311032A1 (en) * | 2016-04-20 | 2017-10-26 | Cisco Technology, Inc. | Content Identifier Remapping for Fast Channel Change |
CN106162257B (en) * | 2016-07-29 | 2019-05-03 | 南京云恩通讯科技有限公司 | A kind of adaptive network transmission optimization method of real-time video |
US10278156B2 (en) | 2016-09-19 | 2019-04-30 | At&T Intellectual Property I, L.P. | Streaming media cellular broadcast |
WO2018060449A1 (en) * | 2016-09-30 | 2018-04-05 | Net Insight Intellectual Property Ab | Playout buffering in a live content distribution system |
CN108234420B (en) * | 2016-12-21 | 2021-03-19 | 北京酷我科技有限公司 | System and method for solving video head loss of streaming media |
KR20200069520A (en) * | 2018-12-07 | 2020-06-17 | 삼성전자주식회사 | Electronic device and control method thereof |
CN111385241B (en) * | 2018-12-27 | 2022-02-18 | 北京紫荆视通科技有限公司 | Method, device and system for repairing lost packet of multimedia data and readable storage medium |
CN111740808B (en) * | 2019-03-25 | 2022-07-22 | 华为技术有限公司 | Data transmission method and device |
CN111756479B (en) * | 2019-03-27 | 2021-12-10 | 华为技术有限公司 | Communication method and device |
CN110730053A (en) * | 2019-09-09 | 2020-01-24 | 晶晨半导体(深圳)有限公司 | Network packet loss retransmission method based on TS format and UDP transmission mode |
CN115396503B (en) * | 2021-05-24 | 2023-11-24 | 阿里巴巴新加坡控股有限公司 | Information processing system, method for realizing information processing by information processing system and gateway |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040071128A1 (en) | 2002-10-15 | 2004-04-15 | Samsung Electronics Co., Ltd. | Reliable multicast data retransmission method by grouping wireless terminals in wireless communication medium and apparatus for the same |
US20050078698A1 (en) | 2002-01-30 | 2005-04-14 | Yoshinobu Araya | Broadcast communicating apparatus, method and system, and program thereof, and program recording medium |
US20050198367A1 (en) | 2003-12-29 | 2005-09-08 | Intel Corporation | Anycast addressing for internet protocol version six |
Family Cites Families (220)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3840862A (en) | 1973-09-27 | 1974-10-08 | Honeywell Inf Systems | Status indicator apparatus for tag directory in associative stores |
US4291196A (en) * | 1979-11-06 | 1981-09-22 | Frederick Electronics Corp. | Circuit for handling conversation data in a distributed processing telex exchange |
US4426682A (en) | 1981-05-22 | 1984-01-17 | Harris Corporation | Fast cache flush mechanism |
US4811203A (en) | 1982-03-03 | 1989-03-07 | Unisys Corporation | Hierarchial memory system with separate criteria for replacement and writeback without replacement |
US4802085A (en) | 1987-01-22 | 1989-01-31 | National Semiconductor Corporation | Apparatus and method for detecting and handling memory-mapped I/O by a pipelined microprocessor |
US5155824A (en) | 1989-05-15 | 1992-10-13 | Motorola, Inc. | System for transferring selected data words between main memory and cache with multiple data words and multiple dirty bits for each address |
US5307477A (en) | 1989-12-01 | 1994-04-26 | Mips Computer Systems, Inc. | Two-level cache memory system |
US5603012A (en) | 1992-06-30 | 1997-02-11 | Discovision Associates | Start code detector |
US5444718A (en) | 1993-11-30 | 1995-08-22 | At&T Corp. | Retransmission protocol for wireless communications |
US5729687A (en) | 1993-12-20 | 1998-03-17 | Intel Corporation | System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information |
US5483587A (en) | 1994-06-08 | 1996-01-09 | Linkusa Corporation | System and method for call conferencing |
US5551001A (en) * | 1994-06-29 | 1996-08-27 | Exponential Technology, Inc. | Master-slave cache system for instruction and data cache memories |
US5636354A (en) | 1994-09-06 | 1997-06-03 | Motorola Inc. | Data processor with serially accessed set associative memory cache interface and method |
US5524235A (en) | 1994-10-14 | 1996-06-04 | Compaq Computer Corporation | System for arbitrating access to memory with dynamic priority assignment |
US5600663A (en) | 1994-11-16 | 1997-02-04 | Lucent Technologies Inc. | Adaptive forward error correction system |
US5600366A (en) | 1995-03-22 | 1997-02-04 | Npb Partners, Ltd. | Methods and apparatus for digital advertisement insertion in video programming |
US5784362A (en) | 1995-04-17 | 1998-07-21 | Telefonaktiebolaget Lm Ericsson | Temporary frame identification for ARQ in a reservation-slotted-ALOHA type of protocol |
JP3123413B2 (en) * | 1995-11-07 | 2001-01-09 | 株式会社日立製作所 | Computer system |
EP0873626B1 (en) | 1995-11-15 | 2006-05-10 | Enterasys Networks, Inc. | Distributed connection-oriented services for switched communications networks |
US5734861A (en) | 1995-12-12 | 1998-03-31 | International Business Machines Corporation | Log-structured disk array with garbage collection regrouping of tracks to preserve seek affinity |
US5673253A (en) | 1996-02-29 | 1997-09-30 | Siemens Business Communication Systems | Dynamic allocation of telecommunications resources |
US6137834A (en) | 1996-05-29 | 2000-10-24 | Sarnoff Corporation | Method and apparatus for splicing compressed information streams |
US6065050A (en) | 1996-06-05 | 2000-05-16 | Sun Microsystems, Inc. | System and method for indexing between trick play and normal play video streams in a video delivery system |
US6332153B1 (en) | 1996-07-31 | 2001-12-18 | Vocaltec Communications Ltd. | Apparatus and method for multi-station conferencing |
US5828844A (en) | 1996-10-08 | 1998-10-27 | At&T Corp. | Internet NCP over ATM |
US5963217A (en) | 1996-11-18 | 1999-10-05 | 7Thstreet.Com, Inc. | Network conference system using limited bandwidth to generate locally animated displays |
US5933593A (en) | 1997-01-22 | 1999-08-03 | Oracle Corporation | Method for writing modified data from a main memory of a computer back to a database |
US6600733B2 (en) | 1997-02-06 | 2003-07-29 | Verizon Laboratories Inc. | System for interconnecting packet-switched and circuit-switched voice communications |
US5974028A (en) | 1997-02-24 | 1999-10-26 | At&T Corp. | System and method for improving transport protocol performance in communication networks having lossy links |
US5870763A (en) | 1997-03-10 | 1999-02-09 | Microsoft Corporation | Database computer system with application recovery and dependency handling read cache |
US6031818A (en) * | 1997-03-19 | 2000-02-29 | Lucent Technologies Inc. | Error correction system for packet switching networks |
FR2761562B1 (en) | 1997-03-27 | 2004-08-27 | France Telecom | VIDEO CONFERENCE SYSTEM |
US5914757A (en) | 1997-04-21 | 1999-06-22 | Philips Electronics North America Corporation | Synchronization of multiple video and graphic sources with a display using a slow PLL approach |
US6516435B1 (en) | 1997-06-04 | 2003-02-04 | Kabushiki Kaisha Toshiba | Code transmission scheme for communication system using error correcting codes |
US5926227A (en) | 1997-07-28 | 1999-07-20 | Lsi Logic Corporation | Video decoder dynamic memory allocation system and method with error recovery |
US5933195A (en) * | 1997-09-26 | 1999-08-03 | Sarnoff Corporation | Method and apparatus memory requirements for storing reference frames in a video decoder |
US6034746A (en) | 1997-10-27 | 2000-03-07 | International Business Machines Corporation | System and method for inserting data into a digital audio/video data stream |
US6151636A (en) | 1997-12-12 | 2000-11-21 | 3Com Corporation | Data and media communication through a lossy channel using signal conversion |
US6119205A (en) | 1997-12-22 | 2000-09-12 | Sun Microsystems, Inc. | Speculative cache line write backs to avoid hotspots |
US6480667B1 (en) | 1997-12-23 | 2002-11-12 | Intel Corporation | Method of time shifting to simultaneously record and play a data stream |
US6351474B1 (en) * | 1998-01-14 | 2002-02-26 | Skystream Networks Inc. | Network distributed remultiplexer for video program bearing transport streams |
US6278716B1 (en) * | 1998-03-23 | 2001-08-21 | University Of Massachusetts | Multicast with proactive forward error correction |
US6643496B1 (en) | 1998-03-31 | 2003-11-04 | Canon Kabushiki Kaisha | System, method, and apparatus for adjusting packet transmission rates based on dynamic evaluation of network characteristics |
US6445717B1 (en) | 1998-05-01 | 2002-09-03 | Niwot Networks, Inc. | System for recovering lost information in a data stream |
US6289054B1 (en) * | 1998-05-15 | 2001-09-11 | North Carolina University | Method and systems for dynamic hybrid packet loss recovery for video transmission over lossy packet-based network |
WO1999065239A2 (en) | 1998-06-11 | 1999-12-16 | Koninklijke Philips Electronics N.V. | Trick play signal generation for a digital video recorder |
US6301249B1 (en) | 1998-08-04 | 2001-10-09 | Opuswave Networks, Inc | Efficient error control for wireless packet transmissions |
US6236854B1 (en) | 1998-08-17 | 2001-05-22 | Nortel Networks Limited | Method and apparatus for controlling a conference call |
US6608820B1 (en) | 1998-08-17 | 2003-08-19 | Nortel Networks Ltd. | Method and apparatus for controlling a conference call |
US6141324A (en) | 1998-09-01 | 2000-10-31 | Utah State University | System and method for low latency communication |
JP2002526978A (en) | 1998-09-25 | 2002-08-20 | ソマ ネットワークス インコーポレイテッド | Methods and systems for telecommunications resource negotiation |
DE19845038A1 (en) | 1998-09-30 | 2000-04-06 | Siemens Ag | Method for connecting communication terminals to a switching system via a communication network |
US6637031B1 (en) | 1998-12-04 | 2003-10-21 | Microsoft Corporation | Multimedia presentation latency minimization |
US6480537B1 (en) | 1999-02-25 | 2002-11-12 | Telcordia Technologies, Inc. | Active techniques for video transmission and playback |
JP4015773B2 (en) | 1999-03-10 | 2007-11-28 | 松下電器産業株式会社 | Transceiver |
US6782490B2 (en) * | 1999-03-17 | 2004-08-24 | At&T Corp. | Network-based service for the repair of IP multicast sessions |
US6775247B1 (en) | 1999-03-22 | 2004-08-10 | Siemens Information And Communication Networks, Inc. | Reducing multipoint conferencing bandwidth |
US6996097B1 (en) | 1999-05-21 | 2006-02-07 | Microsoft Corporation | Receiver-driven layered error correction multicast over heterogeneous packet networks |
AU5038600A (en) | 1999-05-21 | 2000-12-28 | Microsoft Corporation | Receiver-driven layered error correction multicast over the internet |
US6532562B1 (en) | 1999-05-21 | 2003-03-11 | Microsoft Corp | Receiver-driven layered error correction multicast over heterogeneous packet networks |
US6594798B1 (en) | 1999-05-21 | 2003-07-15 | Microsoft Corporation | Receiver-driven layered error correction multicast over heterogeneous packet networks |
US6925068B1 (en) | 1999-05-21 | 2005-08-02 | Wi-Lan, Inc. | Method and apparatus for allocating bandwidth in a wireless communication system |
US6675216B1 (en) | 1999-07-06 | 2004-01-06 | Cisco Technolgy, Inc. | Copy server for collaboration and electronic commerce |
US6567929B1 (en) * | 1999-07-13 | 2003-05-20 | At&T Corp. | Network-based service for recipient-initiated automatic repair of IP multicast sessions |
US6804244B1 (en) * | 1999-08-10 | 2004-10-12 | Texas Instruments Incorporated | Integrated circuits for packet communications |
US6771644B1 (en) | 1999-09-17 | 2004-08-03 | Lucent Technologies Inc. | Program insertion in real time IP multicast |
US6650652B1 (en) | 1999-10-12 | 2003-11-18 | Cisco Technology, Inc. | Optimizing queuing of voice packet flows in a network |
US6608841B1 (en) * | 1999-12-30 | 2003-08-19 | Nokia Networks Oy | System and method for achieving robust IP/UDP/RTP header compression in the presence of unreliable networks |
US6671262B1 (en) | 1999-12-30 | 2003-12-30 | At&T Corp. | Conference server for automatic x-way call port expansion feature |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6792047B1 (en) * | 2000-01-04 | 2004-09-14 | Emc Corporation | Real time processing and streaming of spliced encoded MPEG video and associated audio |
GB2359209A (en) * | 2000-02-09 | 2001-08-15 | Motorola Ltd | Apparatus and methods for video distribution via networks |
AU2001234950A1 (en) | 2000-02-16 | 2001-08-27 | Sycamore Networks, Inc. | Method and apparatus for correcting data using a redundant path |
US6876734B1 (en) | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
US6721290B1 (en) | 2000-04-03 | 2004-04-13 | Hrl Laboratories, Llc | Method and apparatus for multicasting real time traffic in wireless ad-hoc networks |
JP2001320440A (en) | 2000-05-02 | 2001-11-16 | Sony Corp | Communication apparatus and method |
EP1281264B1 (en) | 2000-05-08 | 2012-12-12 | Broadcom Corporation | System and method for supporting multiple voice channels |
US6501739B1 (en) | 2000-05-25 | 2002-12-31 | Remoteability, Inc. | Participant-controlled conference calling system |
US6865157B1 (en) * | 2000-05-26 | 2005-03-08 | Emc Corporation | Fault tolerant shared system resource with communications passthrough providing high availability communications |
US7260826B2 (en) | 2000-05-31 | 2007-08-21 | Microsoft Corporation | Resource allocation in multi-stream IP network for optimized quality of service |
US6839325B2 (en) | 2000-06-09 | 2005-01-04 | Texas Instruments Incorporated | Wireless communication system which uses ARQ packets to ACK a plurality of packets from an 802.15 superpacket |
US7180896B1 (en) * | 2000-06-23 | 2007-02-20 | Mitsubishi Denki Kabushiki Kaisha | Method and system for packet retransmission |
US7373413B1 (en) * | 2000-06-28 | 2008-05-13 | Cisco Technology, Inc. | Devices and methods for minimizing start up delay in transmission of streaming media |
US6865540B1 (en) | 2000-08-09 | 2005-03-08 | Ingenio, Inc. | Method and apparatus for providing group calls via the internet |
US7007098B1 (en) | 2000-08-17 | 2006-02-28 | Nortel Networks Limited | Methods of controlling video signals in a video conference |
KR100450236B1 (en) | 2000-08-24 | 2004-09-30 | 마츠시타 덴끼 산교 가부시키가이샤 | Transmitting/receiving method and device therefor |
US7224702B2 (en) * | 2000-08-30 | 2007-05-29 | The Chinese University Of Hong Kong | System and method for error-control for multicast video distribution |
WO2002030067A1 (en) * | 2000-10-05 | 2002-04-11 | Mitsubishi Denki Kabushiki Kaisha | Packet retransmission system, packet transmission device, packet reception device, packet retransmission method, packet transmission method and packet reception method |
US7844489B2 (en) | 2000-10-30 | 2010-11-30 | Buyerleverage | Buyer-driven targeting of purchasing entities |
US6910148B1 (en) | 2000-12-07 | 2005-06-21 | Nokia, Inc. | Router and routing protocol redundancy |
US20020087976A1 (en) | 2000-12-28 | 2002-07-04 | Kaplan Marc P. | System and method for distributing video with targeted advertising using switched communication networks |
US6956828B2 (en) | 2000-12-29 | 2005-10-18 | Nortel Networks Limited | Apparatus and method for packet-based media communications |
US6976055B1 (en) | 2001-01-18 | 2005-12-13 | Cisco Technology, Inc. | Apparatus and method for conducting a transfer of a conference call |
US7003086B1 (en) | 2001-01-18 | 2006-02-21 | Cisco Technology, Inc. | Apparatus and method for allocating call resources during a conference call |
US6868083B2 (en) * | 2001-02-16 | 2005-03-15 | Hewlett-Packard Development Company, L.P. | Method and system for packet communication employing path diversity |
US7024609B2 (en) | 2001-04-20 | 2006-04-04 | Kencast, Inc. | System for protecting the transmission of live data streams, and upon reception, for reconstructing the live data streams and recording them into files |
US6766418B1 (en) | 2001-04-30 | 2004-07-20 | Emc Corporation | Methods and apparatus for accessing data using a cache |
WO2002091202A1 (en) | 2001-05-04 | 2002-11-14 | Globespan Virata Incorporated | System and method for distributed processing of packet data containing audio information |
US6937569B1 (en) | 2001-05-21 | 2005-08-30 | Cisco Technology, Inc. | Method and system for determining a relative position of a device on a network |
US7164680B2 (en) * | 2001-06-04 | 2007-01-16 | Koninklijke Philips Electronics N.V. | Scheme for supporting real-time packetization and retransmission in rate-based streaming applications |
US6792449B2 (en) | 2001-06-28 | 2004-09-14 | Microsoft Corporation | Startup methods and apparatuses for use in streaming content |
US6947417B2 (en) | 2001-06-29 | 2005-09-20 | Ip Unity | Method and system for providing media services |
US20030025786A1 (en) | 2001-07-31 | 2003-02-06 | Vtel Corporation | Method and system for saving and applying a video address from a video conference |
US7908628B2 (en) | 2001-08-03 | 2011-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content coding and formatting |
US8218829B2 (en) | 2001-08-20 | 2012-07-10 | Polycom, Inc. | System and method for using biometrics technology in conferencing |
JP2003152752A (en) | 2001-08-29 | 2003-05-23 | Matsushita Electric Ind Co Ltd | Data transmission/reception method |
US7127487B1 (en) | 2001-10-15 | 2006-10-24 | 3Com Corporation | System and method for sidebar functionality in a regular conference system |
US7355971B2 (en) | 2001-10-22 | 2008-04-08 | Intel Corporation | Determining packet size in networking |
KR100431003B1 (en) | 2001-10-31 | 2004-05-12 | 삼성전자주식회사 | Data transmitting/receiving system and method thereof |
US7003712B2 (en) | 2001-11-29 | 2006-02-21 | Emin Martinian | Apparatus and method for adaptive, multimode decoding |
US7257664B2 (en) | 2001-12-21 | 2007-08-14 | Lambert Everest Ltd. | Adaptive error resilience for signal transmission over a network |
US7379653B2 (en) | 2002-02-20 | 2008-05-27 | The Directv Group, Inc. | Audio-video synchronization for digital systems |
FR2838584A1 (en) * | 2002-04-16 | 2003-10-17 | Koninkl Philips Electronics Nv | Digital/audio word packet transmission mobile receiver via internet having network receiver demanding word retransmission where packet lost detected and transit time estimator deactivating demand where criteria exceeded. |
US7292543B2 (en) | 2002-04-17 | 2007-11-06 | Texas Instruments Incorporated | Speaker tracking on a multi-core in a packet based conferencing system |
US6677864B2 (en) | 2002-04-18 | 2004-01-13 | Telefonaktiebolaget L.M. Ericsson | Method for multicast over wireless networks |
EP1501310A4 (en) | 2002-04-26 | 2012-07-11 | Nec Corp | Moving picture data code conversion/transmission method and device, code conversion/reception method and device |
US8392952B2 (en) * | 2002-05-03 | 2013-03-05 | Time Warner Cable Enterprises Llc | Programming content processing and management system and method |
US7251697B2 (en) * | 2002-06-20 | 2007-07-31 | Koninklijke Philips Electronics N.V. | Method and apparatus for structured streaming of an XML document |
EP1535419B1 (en) * | 2002-09-06 | 2009-05-06 | Telefonaktiebolaget LM Ericsson (publ) | Method and devices for controlling retransmissions in data streaming |
US8411594B2 (en) | 2002-09-20 | 2013-04-02 | Qualcomm Incorporated | Communication manager for providing multimedia in a group communication network |
EP1553735A1 (en) | 2002-10-17 | 2005-07-13 | Matsushita Electric Industrial Co., Ltd. | Packet transmission/reception device |
US8233392B2 (en) * | 2003-07-29 | 2012-07-31 | Citrix Systems, Inc. | Transaction boundary detection for reduction in timeout penalties |
US7616638B2 (en) * | 2003-07-29 | 2009-11-10 | Orbital Data Corporation | Wavefront detection and disambiguation of acknowledgments |
US6931113B2 (en) | 2002-11-08 | 2005-08-16 | Verizon Services Corp. | Facilitation of a conference call |
US7260764B2 (en) | 2002-11-26 | 2007-08-21 | Qualcomm Incorporated | Multi-channel transmission and reception with block coding in a communication system |
EP1568230A1 (en) | 2002-11-27 | 2005-08-31 | Koninklijke Philips Electronics N.V. | I-picture insertion on request |
EP1432196A1 (en) | 2002-12-20 | 2004-06-23 | Matsushita Electric Industrial Co., Ltd. | Control traffic compression method in media data transmission |
JP3769752B2 (en) | 2002-12-24 | 2006-04-26 | ソニー株式会社 | Information processing apparatus and information processing method, data communication system, and program |
US7792982B2 (en) | 2003-01-07 | 2010-09-07 | Microsoft Corporation | System and method for distributing streaming content through cooperative networking |
EP1593107A4 (en) * | 2003-02-13 | 2010-08-18 | Nokia Corp | Method for signaling client rate capacity in multimedia streaming |
US7010108B2 (en) | 2003-02-21 | 2006-03-07 | Magicsoft Corporation | Method for scheduling videoconferences |
CN1531282A (en) | 2003-03-12 | 2004-09-22 | ���µ�����ҵ��ʽ���� | Packet trunk device |
US6959075B2 (en) | 2003-03-24 | 2005-10-25 | Cisco Technology, Inc. | Replay of conference audio |
EP2265009A3 (en) | 2003-04-24 | 2011-02-16 | Sony Corporation | Information processing apparatus, information processing method, program storage medium, and program |
CN100499879C (en) | 2003-05-13 | 2009-06-10 | 艾利森电话股份有限公司 | Method of reducing delay and user terminal |
US7603689B2 (en) | 2003-06-13 | 2009-10-13 | Microsoft Corporation | Fast start-up for digital video streams |
AU2004250927B2 (en) | 2003-06-16 | 2010-04-08 | Interdigital Vc Holdings, Inc. | Decoding method and apparatus enabling fast channel change of compressed video |
US7234079B2 (en) | 2003-07-11 | 2007-06-19 | Agency For Science, Technology & Research | Method and system for enabling recovery of data stored in a computer network; a method and a system for recovering data stored in a computer network |
EP1649706A4 (en) | 2003-07-18 | 2011-05-11 | Kodiak Networks Inc | Premium voice services for wireless communications systems |
US7460652B2 (en) | 2003-09-26 | 2008-12-02 | At&T Intellectual Property I, L.P. | VoiceXML and rule engine based switchboard for interactive voice response (IVR) services |
US8659636B2 (en) | 2003-10-08 | 2014-02-25 | Cisco Technology, Inc. | System and method for performing distributed video conferencing |
US7562375B2 (en) | 2003-10-10 | 2009-07-14 | Microsoft Corporation | Fast channel change |
JP4328283B2 (en) * | 2003-10-22 | 2009-09-09 | パナソニック株式会社 | Packet delivery control method |
CN1830164A (en) * | 2003-10-30 | 2006-09-06 | 松下电器产业株式会社 | Mobile-terminal-oriented transmission method and apparatus |
SE0302920D0 (en) | 2003-11-03 | 2003-11-03 | Ericsson Telefon Ab L M | Improvements in or relating to group calls |
US20050099499A1 (en) | 2003-11-10 | 2005-05-12 | Ariel Braunstein | Recyclable, digital one time use video camera |
WO2005048519A1 (en) | 2003-11-12 | 2005-05-26 | Koninklijke Philips Electronics N.V. | Communication method, system and device |
US7084898B1 (en) | 2003-11-18 | 2006-08-01 | Cisco Technology, Inc. | System and method for providing video conferencing synchronization |
US20050249231A1 (en) * | 2003-11-25 | 2005-11-10 | Asif Khan | Methods and systems for reliable distribution of media over a network |
JP2005184640A (en) | 2003-12-22 | 2005-07-07 | Fujitsu Ltd | Information distribution device and information distribution method |
JP4454320B2 (en) | 2004-01-09 | 2010-04-21 | 富士通株式会社 | Transmission apparatus, transmission control program, and transmission method |
US8737219B2 (en) | 2004-01-30 | 2014-05-27 | Hewlett-Packard Development Company, L.P. | Methods and systems that use information about data packets to determine an order for sending the data packets |
US7296205B2 (en) * | 2004-02-18 | 2007-11-13 | Nokia Corporation | Data repair |
US7397759B2 (en) | 2004-03-15 | 2008-07-08 | Microsoft Corporation | Response for spurious timeout |
US8683535B2 (en) | 2004-03-26 | 2014-03-25 | Broadcom Corporation | Fast channel change |
TWI401955B (en) | 2004-04-16 | 2013-07-11 | Panasonic Corp | A reproducing apparatus, a recording medium, a reproducing method, and a reproducing system |
US20050259803A1 (en) | 2004-05-19 | 2005-11-24 | Nokia Corporation | Managing a conference session |
US20050289623A1 (en) * | 2004-05-21 | 2005-12-29 | Mowaffak Midani | Bulk tuning of frequency-modulated video signals |
US20060013210A1 (en) | 2004-06-18 | 2006-01-19 | Bordogna Mark A | Method and apparatus for per-service fault protection and restoration in a packet network |
US20060020995A1 (en) | 2004-07-20 | 2006-01-26 | Comcast Cable Communications, Llc | Fast channel change in digital media systems |
US7599363B2 (en) | 2004-08-13 | 2009-10-06 | Samsung Electronics Co. Ltd | Method for reporting reception result of packets in mobile communication system |
US8291448B2 (en) | 2004-09-15 | 2012-10-16 | Nokia Corporation | Providing zapping streams to broadcast receivers |
US9197857B2 (en) | 2004-09-24 | 2015-11-24 | Cisco Technology, Inc. | IP-based stream splicing with content-specific splice points |
US8966551B2 (en) * | 2007-11-01 | 2015-02-24 | Cisco Technology, Inc. | Locating points of interest using references to media frames within a packet flow |
US20060075443A1 (en) * | 2004-09-27 | 2006-04-06 | Eckert Wieland P | Switching to a broadcast data stream |
US7478429B2 (en) | 2004-10-01 | 2009-01-13 | Prolexic Technologies, Inc. | Network overload detection and mitigation system and method |
US20060072596A1 (en) | 2004-10-05 | 2006-04-06 | Skipjam Corp. | Method for minimizing buffer delay effects in streaming digital content |
US7667728B2 (en) | 2004-10-15 | 2010-02-23 | Lifesize Communications, Inc. | Video and audio conferencing system with spatial audio |
US7673063B2 (en) * | 2004-10-15 | 2010-03-02 | Motorola, Inc. | Methods for streaming media data |
US7870590B2 (en) * | 2004-10-20 | 2011-01-11 | Cisco Technology, Inc. | System and method for fast start-up of live multicast streams transmitted over a packet network |
US7751324B2 (en) | 2004-11-19 | 2010-07-06 | Nokia Corporation | Packet stream arrangement in multimedia transmission |
SE0402876D0 (en) | 2004-11-25 | 2004-11-25 | Ericsson Telefon Ab L M | TV-like standards-compliant unicast streaming over IP |
US7477653B2 (en) | 2004-12-10 | 2009-01-13 | Microsoft Corporation | Accelerated channel change in rate-limited environments |
EP1675399A3 (en) * | 2004-12-23 | 2009-04-29 | Bitband Technologies Ltd. | Fast channel switching for digital TV |
KR100655909B1 (en) * | 2004-12-28 | 2006-12-11 | 삼성전자주식회사 | Ad hoc network for extending routing to support Internet Protocol version 6 protocol and routing extending method thereof |
KR100713419B1 (en) * | 2005-01-20 | 2007-05-04 | 삼성전자주식회사 | Selected Transmitted Real Time Splitter |
US20060188025A1 (en) * | 2005-02-18 | 2006-08-24 | Nokia Corporation | Error concealment |
US20060187914A1 (en) * | 2005-02-18 | 2006-08-24 | Fujitsu Limited | Method and device for managing heterogeneous communication networks |
US20060200842A1 (en) | 2005-03-01 | 2006-09-07 | Microsoft Corporation | Picture-in-picture (PIP) alerts |
US7668914B2 (en) * | 2005-03-28 | 2010-02-23 | Alcatel Lucent | Milestone synchronization in broadcast multimedia streams |
US7889654B2 (en) | 2005-03-30 | 2011-02-15 | At&T Intellectual Property Ii, L.P. | Loss tolerant transmission control protocol |
KR101223806B1 (en) | 2005-04-01 | 2013-01-17 | 알까뗄 루슨트 | Rapid media channel changing mechanism and access network node comprising same |
US20060242669A1 (en) * | 2005-04-20 | 2006-10-26 | Jupiter Systems | Display node for use in an audiovisual signal routing and distribution system |
US7676735B2 (en) * | 2005-06-10 | 2010-03-09 | Digital Fountain Inc. | Forward error-correcting (FEC) coding and streaming |
US7944992B2 (en) | 2005-06-17 | 2011-05-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Multicarrier CDMA system |
EP2485500B8 (en) | 2005-07-07 | 2017-04-26 | TiVo Solutions Inc. | System and method for digital content retrieval using a threshold indicator associated with the beginning of said recorded content |
US7747921B2 (en) | 2005-08-05 | 2010-06-29 | Sony Corporation | Systems and methods for transmitting data over lossy networks |
US20070044130A1 (en) * | 2005-08-16 | 2007-02-22 | Alcatel | System and method for implementing channel change operations in internet protocol television systems |
US7676591B2 (en) | 2005-09-22 | 2010-03-09 | Packet Video Corporation | System and method for transferring multiple data channels |
US20070110029A1 (en) | 2005-11-12 | 2007-05-17 | Motorola, Inc. | Method for linking communication channels of disparate access technologies in a selective call unit |
US20090092109A1 (en) | 2005-12-19 | 2009-04-09 | Torbjorn Cagenius | Method and Apparatus for Enabling Discovery Within a Home Network |
US20070200949A1 (en) | 2006-02-21 | 2007-08-30 | Qualcomm Incorporated | Rapid tuning in multimedia applications |
US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US8218654B2 (en) | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
KR100913904B1 (en) | 2006-04-14 | 2009-08-26 | 삼성전자주식회사 | Method and apparatus for performing automatic retransmission request in mobile telecommunication system |
US7573875B2 (en) * | 2006-05-19 | 2009-08-11 | Alcatel Lucent | Proactively providing a redundant multicast tree in an internet protocol television (IPTV) network |
US8245264B2 (en) | 2006-05-26 | 2012-08-14 | John Toebes | Methods and systems to reduce channel selection transition delay in a digital network |
WO2008000289A1 (en) | 2006-06-29 | 2008-01-03 | Telecom Italia S.P.A. | Method and apparatus for improving bandwith exploitation in real-time audio/video communications |
US7584495B2 (en) | 2006-06-30 | 2009-09-01 | Nokia Corporation | Redundant stream alignment in IP datacasting over DVB-H |
US7877660B2 (en) | 2006-07-07 | 2011-01-25 | Ver Steeg William C | Transmitting additional forward error correction (FEC) upon request |
US7532621B2 (en) * | 2006-08-30 | 2009-05-12 | Cornell Research Foundation, Inc. | Lateral error correction for time-critical multicast |
US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US7681101B2 (en) * | 2007-04-16 | 2010-03-16 | Cisco Technology, Inc. | Hybrid corrective scheme for dropped packets |
EP2070067B1 (en) | 2006-09-11 | 2020-05-06 | Cisco Technology, Inc. | Hybrid correction scheme for dropped packets |
US7937531B2 (en) | 2007-02-01 | 2011-05-03 | Cisco Technology, Inc. | Regularly occurring write back scheme for cache soft error reduction |
US8769591B2 (en) * | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
US7940644B2 (en) | 2007-03-14 | 2011-05-10 | Cisco Technology, Inc. | Unified transmission scheme for media stream redundancy |
US20080253369A1 (en) | 2007-04-16 | 2008-10-16 | Cisco Technology, Inc. | Monitoring and correcting upstream packet loss |
US7826348B2 (en) * | 2007-04-26 | 2010-11-02 | Cisco Technology, Inc. | Multicast fast reroute |
US8958486B2 (en) * | 2007-07-31 | 2015-02-17 | Cisco Technology, Inc. | Simultaneous processing of media and redundancy streams for mitigating impairments |
US8804845B2 (en) | 2007-07-31 | 2014-08-12 | Cisco Technology, Inc. | Non-enhancing media redundancy coding for mitigating transmission impairments |
US8001445B2 (en) * | 2007-08-13 | 2011-08-16 | Provigent Ltd. | Protected communication link with improved protection indication |
US20090055540A1 (en) * | 2007-08-20 | 2009-02-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and Systems for Multicast Control and Channel Switching for Streaming Media in an IMS Environment |
US8037392B1 (en) | 2007-09-11 | 2011-10-11 | Harmonic Inc. | Method for optimizing the forward error correction scheme |
US8154988B2 (en) * | 2007-12-06 | 2012-04-10 | Cisco Technology, Inc. | Delivery of streams to repair errored media streams in periods of insufficient resources |
US8787153B2 (en) | 2008-02-10 | 2014-07-22 | Cisco Technology, Inc. | Forward error correction based data recovery with path diversity |
US7684316B2 (en) * | 2008-02-12 | 2010-03-23 | Cisco Technology, Inc. | Multicast fast reroute for network topologies |
US7940777B2 (en) | 2008-02-26 | 2011-05-10 | Cisco Technology, Inc. | Loss-free packet networks |
US9312989B2 (en) | 2008-07-07 | 2016-04-12 | Cisco Technology, Inc. | Importance-based FEC-aware error-repair scheduling |
US7886073B2 (en) * | 2008-08-08 | 2011-02-08 | Cisco Technology, Inc. | Systems and methods of reducing media stream delay |
-
2006
- 2006-11-17 US US11/561,237 patent/US8031701B2/en not_active Expired - Fee Related
-
2007
- 2007-08-20 CN CN200780022360XA patent/CN101473571B/en not_active Expired - Fee Related
- 2007-08-20 EP EP07814245.2A patent/EP2062384B1/en not_active Not-in-force
- 2007-08-20 WO PCT/US2007/076264 patent/WO2008033644A2/en active Application Filing
-
2011
- 2011-03-08 US US13/043,437 patent/US8588077B2/en not_active Expired - Fee Related
-
2013
- 2013-10-04 US US14/045,813 patent/US9083585B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050078698A1 (en) | 2002-01-30 | 2005-04-14 | Yoshinobu Araya | Broadcast communicating apparatus, method and system, and program thereof, and program recording medium |
US20040071128A1 (en) | 2002-10-15 | 2004-04-15 | Samsung Electronics Co., Ltd. | Reliable multicast data retransmission method by grouping wireless terminals in wireless communication medium and apparatus for the same |
US20050198367A1 (en) | 2003-12-29 | 2005-09-08 | Intel Corporation | Anycast addressing for internet protocol version six |
Non-Patent Citations (1)
Title |
---|
See also references of EP2062384A4 |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8462847B2 (en) | 2006-02-27 | 2013-06-11 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US8218654B2 (en) | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
US9083585B2 (en) | 2006-09-11 | 2015-07-14 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US8588077B2 (en) | 2006-09-11 | 2013-11-19 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US7937531B2 (en) | 2007-02-01 | 2011-05-03 | Cisco Technology, Inc. | Regularly occurring write back scheme for cache soft error reduction |
US8769591B2 (en) | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
US7940644B2 (en) | 2007-03-14 | 2011-05-10 | Cisco Technology, Inc. | Unified transmission scheme for media stream redundancy |
US7681101B2 (en) | 2007-04-16 | 2010-03-16 | Cisco Technology, Inc. | Hybrid corrective scheme for dropped packets |
US8427948B2 (en) | 2008-02-07 | 2013-04-23 | British Telecommunications Public Limited Company | Communications network |
US8935736B2 (en) | 2008-12-12 | 2015-01-13 | Huawei Technologies Co., Ltd. | Channel switching method, channel switching device, and channel switching system |
US9015555B2 (en) | 2011-11-18 | 2015-04-21 | Cisco Technology, Inc. | System and method for multicast error recovery using sampled feedback |
Also Published As
Publication number | Publication date |
---|---|
US20140029628A1 (en) | 2014-01-30 |
WO2008033644A3 (en) | 2008-10-02 |
EP2062384A2 (en) | 2009-05-27 |
US9083585B2 (en) | 2015-07-14 |
CN101473571B (en) | 2013-11-13 |
US20080062990A1 (en) | 2008-03-13 |
EP2062384B1 (en) | 2017-10-04 |
EP2062384A4 (en) | 2016-04-20 |
US8031701B2 (en) | 2011-10-04 |
CN101473571A (en) | 2009-07-01 |
US8588077B2 (en) | 2013-11-19 |
US20110161765A1 (en) | 2011-06-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9083585B2 (en) | Retransmission-based stream repair and stream join | |
EP2119228B1 (en) | Unified transmission scheme for media stream redundancy | |
KR101571145B1 (en) | Method and apparatus for adaptive forward error correction with merged automatic repeat request for reliable multicast in wireless local area networks | |
US8711854B2 (en) | Monitoring and correcting upstream packet loss | |
US20170041682A1 (en) | Method and apparatus for distributing video | |
CN106301694B (en) | Method and device for reducing retransmission times of data packet in reliable multicast transmission | |
US8261148B2 (en) | Internet protocol multicast with internet protocol unicast/multicast error correction | |
US20120140645A1 (en) | Method and apparatus for distributing video | |
WO2022002043A1 (en) | Data retransmission method, network device, and computer readable storage medium | |
KR20110108366A (en) | Method and apparatus for reliable multicast streaming | |
US11601295B2 (en) | Content delivery with reliable multicast using a redundant unicast overlay network | |
US10951428B2 (en) | Reliable multicast using a redundant unicast overlay network | |
Afzal et al. | A holistic survey of wireless multipath video streaming | |
US20050188107A1 (en) | Redundant pipelined file transfer | |
CN106130746B (en) | Data transmission method and device | |
CN111245592B (en) | Signaling transmission method and device and computer readable storage medium | |
JP2017092581A (en) | Gateway unit, broadcast receiver, broadcast relay method, broadcast reception method, broadcast relay program, and broadcast reception program | |
US20220263673A1 (en) | Content distribution system, multicast unicast / multicast multicast converter, multicast unicast converter, content distribution method and content distribution program | |
CN115103202A (en) | IP video live broadcast transmission method and system capable of resisting network degradation | |
Peltotalo et al. | Scalable packet loss recovery for mobile P2P streaming | |
Lennox et al. | Real-Time Transport Protocol (RTP) Usage for Telepresence Sessions draft-lennox-clue-rtp-usage-02 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780022360.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07814245 Country of ref document: EP Kind code of ref document: A2 |
|
REEP | Request for entry into the european phase |
Ref document number: 2007814245 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007814245 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |