WO2012162674A1 - Multipath overlay network and its multipath management protocol - Google Patents
Multipath overlay network and its multipath management protocol Download PDFInfo
- Publication number
- WO2012162674A1 WO2012162674A1 PCT/US2012/039733 US2012039733W WO2012162674A1 WO 2012162674 A1 WO2012162674 A1 WO 2012162674A1 US 2012039733 W US2012039733 W US 2012039733W WO 2012162674 A1 WO2012162674 A1 WO 2012162674A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- source
- aggregator
- helper
- path
- release
- Prior art date
Links
Classifications
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- 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/52—Multiprotocol routers
-
- 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer
-
- 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
-
- 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
Definitions
- the present disclosure relates generally to communication networks, and more particularly, communication access in Wireless Wide Area Networks (WWANs).
- WWANs Wireless Wide Area Networks
- Access links such as a wireless air interface between an access terminal and a base station
- WWANs Wireless Wide Area Networks
- multimedia applications increasingly introduce a higher traffic load on access links of WWANs, causing unsatisfactory user experience.
- the device may use multiple cooperative devices to increase its access capacity. More specifically, an out of band link between the primary node and its cooperative node in conjunction with the access link of the cooperative node may provide an alternative path to the WWAN for the primary node's traffic. Hence, multiple paths can be established between a source and its destination for an application stream.
- An overlay network can manage multiple paths for an application stream.
- the multipath overlay network is on top of and compatible with the existing network infrastructure. Further, the multipath overlay network may only be perceived as an application by the underlying network.
- the instant specification describes an overlay network architecture that serves as a multipath transportation facility between traffic sources and destinations.
- the multiple paths provided by this multipath overlay network between a pair of source and destination nodes can be used to transport multiple descriptions of a traffic application stream.
- the multipath overlay network architecture may be built on top of, and may be compatible with the existing network infrastructure. Interested applications can use the multipath transportation facility provided by this multipath overlay network to enhance its traffic performance, such as throughput, reliability, delay jitter, etc.
- a source apparatus includes a processing system and a memory coupled to the processing system.
- the processing system is configured to support a multimedia communication session for sending data over a plurality of paths from the source to an aggregator, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- an aggregator apparatus in another aspect of the disclosure, includes a processing system and a memory coupled to the processing system.
- the processing system is configured to support a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- an aggregator helper apparatus includes a processing system and a memory coupled to the processing system.
- the processing system is configured to support a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths includes the aggregator helper, selected by the aggregator.
- a source helper apparatus includes a processing system and a memory coupled to the processing system.
- the processing system is configured to support a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths comprising the source helper, selected by the source.
- Another aspect of the disclosure provides a method of communication from a source.
- the method includes supporting a multimedia communication session for sending data over a plurality of paths from the source to an aggregator, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- a method of communication from an aggregator includes supporting a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- a method of communication from an aggregator includes supporting a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- Yet another aspect of the disclosure provides a method of communication utilizing a source helper.
- the method includes supporting a multimedia communication session for sending data over a plurality of paths from a source to an aggregator, where a first path of the plurality of paths includes the source helper, selected by the source.
- a source apparatus includes means for supporting a multimedia communication session for sending data over a plurality of paths from the source to an aggregator, where a first path of the plurality of paths includes at least one helper node; and means for selecting, by the source, the at least one helper node.
- an aggregator apparatus includes means for supporting a multimedia communication session for sending data over a plurality of paths from a source to the aggregator, where a first path of the plurality of paths includes at least one helper node; and means for selecting, by the aggregator, the at least one helper node.
- Yet another aspect of the disclosure provides an aggregator helper apparatus.
- the aggregator helper apparatus includes means for supporting a multimedia communication session for sending data over a plurality of paths from a source to an aggregator, where a first path of the plurality of paths includes the aggregator helper; and means for receiving a selection by the aggregator.
- the source helper includes means for supporting a multimedia communication session for sending data over a plurality of paths from a source to an aggregator, where a first path of the plurality of paths includes the source helper; and means for receiving a selection by the source.
- a computer program product includes a computer-readable medium having code for supporting a multimedia communication session for sending data over a plurality of paths from a source apparatus to an aggregator apparatus, where a first path of the plurality of paths includes at least one helper node selected by the source or the aggregator.
- FIG. 1 is a block diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
- FIG. 2 is an illustration of a multipath overlay network.
- FIG. 3 illustrates a protocol stack of the overlay network data plane.
- FIG. 4 illustrates a protocol stack of the control plane.
- FIG. 5 illustrates an example of a label distribution
- FIG. 6 illustrates a state transition diagram
- FIGs. 7A-7F illustrate Specification and Description Language (SDL) diagrams for an Aggregator.
- SDL Specification and Description Language
- FIG. 8 illustrates a state transition diagram for an aggregator helper.
- FIGs. 9A-9B illustrate an SDL diagram for an aggregator helper.
- FIG. 10 illustrates a state transition diagram for a source.
- FIGS. 1 lA-1 IF illustrate an SDL diagram for a source.
- FIG. 12 illustrates a state transition diagram for a source helper.
- FIGs. 13A-13B illustrate an SDL diagram for a source helper.
- FIG. 14 is an example of a packet header of multipath overlay network data packets.
- FIG. 15 is an example of a packet header of multipath overlay network signaling messages.
- FIG. 1 is a block diagram illustrating an example of a hardware implementation for an apparatus 100 employing a processing system 114.
- the processing system 114 may be implemented with a bus architecture, represented generally by the bus 102.
- the bus 102 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1 14 and the overall design constraints.
- the bus 102 links together various circuits including one or more processors, represented generally by the processor 104, and computer- readable media, represented generally by the computer-readable medium 106.
- the bus 102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
- a bus interface 108 provides an interface between the bus 102 and a transceiver 1 10.
- the transceiver 1 10 provides a means for communicating with various other apparatus over a transmission medium.
- a user interface 112 e.g., keypad, display, speaker, microphone, joystick
- the processor 104 is responsible for managing the bus 102 and general processing, including the execution of software stored on the computer-readable medium 106.
- the software when executed by the processor 104, causes the processing system 1 14 to perform the various functions described infra for any particular apparatus.
- the computer-readable medium 106 may also be used for storing data that is manipulated by the processor 104 when executing software.
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- CDMA2000 Evolution-Data Optimized
- UMB Ultra Mobile Broadband
- Wi-Fi Wi-Fi
- WiMAX WiMAX
- IEEE 802.20 Ultra-Wideband
- Bluetooth Bluetooth
- any other suitable system any other suitable system.
- the actual telecommunication standard and/or network architecture employed will depend on the specific implementation and the overall design constraints imposed on the system.
- FIG. 2 is an illustration of the architecture of a multipath overlay network 200 in accordance with some aspects of the present disclosure.
- the multipath overlay network 200 includes various paths between different nodes such as one or more traffic sources (“source”) 210, and one or more traffic destinations (“aggregator”) 220.
- the source 210 and the aggregator 220 may each "discover" specific "helpers” to establish the paths, and to route substreams of a streaming session between the respective source 210 and aggregator 220.
- Each multimedia communication session (“streaming session”) may include a source 210, one or more source helpers 215 (optional), one or more aggregator helpers 225 (optional), and an aggregator 210.
- a traffic substream may flow from a source 210 to a source helper 215, then to an aggregator helper 225, and then to an aggregator 220.
- the selected source helper 215 and aggregator helper 225 thus serve to relay the substream of the streaming multimedia communication session from the source 210 to the aggregator 220.
- data If data is transmitted from the source 210 directly to the aggregator 220, that data may be characterized as a first description of the streaming session.
- Substreams of data transmitted over other paths, e.g., utilizing one or more helpers, may be characterized as second and subsequent descriptions of the streaming session.
- multiple descriptions of the streaming session may be transmitted over separate paths and reassembled at the aggregator 220 for an enhanced quality of service by virtue of the additional bandwidth being utilized.
- the source helper 215 and the aggregator 210 may thus "cooperatively help" the source 1 10 and the aggregator 120 to achieve, for example, a streaming communication that has a quality greater than a threshold value of quality, in order to enhance a user experience.
- the sources 210 are the traffic sources of a streaming session
- the aggregators 220 are the traffic destinations of the streaming session.
- a source helper 215 is a cooperative node, which may be selected by the source 210 to receive and retransmit a description of the session in a substream.
- An aggregator helper 225 is a cooperative node, which may be selected by the aggregator 220 to receive and retransmit a description of the session in a substream.
- 225 can be a helper for one or more traffic sessions at the same time. That is, a node can take different roles for different traffic sessions, i.e., as a source 210, a source helper 215, an aggregator 220, and/or an aggregator helper 225.
- FIG. 3 illustrates protocol stacks of certain nodes in the overlay network data plane in accordance with some aspects of the disclosure.
- the data plane can be utilized to deliver the multimedia data across the multipath overlay network 200.
- the data packets may traverse multiple hops on the multipath overlay network 200.
- the protocol stack for the source 302 includes a physical layer (PHY) 302a, a medium access control layer (MAC) 302b, an internet protocol layer (IP) 302c, a user datagram protocol/transmission control protocol layer (UDP/TCP) 302d, an overlay routing layer 302e, and a real-time transport protocol layer (RTP) 302f.
- PHY physical layer
- MAC medium access control layer
- IP internet protocol layer
- UDP/TCP user datagram protocol/transmission control protocol layer
- RTP real-time transport protocol layer
- the protocol stack for the source helper 304 includes, at an input side, a PHY layer 304al, a MAC layer 304bl, an IP layer 304cl, and a UDP/TCP layer 304dl; and at an output side, a PHY layer 304a2, a MAC layer 304b2, an IP layer 304c2, and a UDP/TCP layer 304d2.
- the source helper 304 further includes an overlay routing layer 304e.
- the protocol stack for the aggregator helper 306 includes, at an input side, a PHY layer 306al, a MAC layer 306bl, an IP layer 306cl, and a UDP/TCP layer 306dl; and at an output side, a PHY layer 306a2, a MAC layer 306b2, an IP layer 306c2, and a UDP/TCP layer 306d2.
- the aggregator helper 306 further includes an overlay routing layer 306e.
- the protocol stack for the aggregator 308 includes a PHY layer 308a, a MAC layer 308b, an IP layer 308c, a UDP/TCP layer 308d, an overlay routing layer 308e, and an RTP layer 308f.
- the multipath overlay network 200 utilizes a UDP or a TCP port (e.g, a predetermined UDP or TCP port) for transporting overlay network data packets.
- a UDP or a TCP port e.g, a predetermined UDP or TCP port
- an end-to-end UDP/IP transport can be utilized between those nodes.
- an end-to-end UDP/IP transport can be utilized between the source 302 and the source helper 304; between the source 302 and the aggregator helper 306; between the source helper 304 and the aggregator 308; and between the aggregator helper 306 and the aggregator 308.
- FIG. 4 illustrates a protocol stack of the overlay network control plane in accordance with some aspects of the disclosure.
- the control plane of the multipath overlay network may be used to setup, release, and switch a path in the data plane between a respective source 210 and aggregator 220.
- each of the respective nodes includes a PHY layer, a MAC layer, an IP layer, and a TCP layer.
- each of the respective nodes includes an overlay control layer.
- multipath overlay network signaling messages may traverse a single hop on the multipath overlay network. That is, if a data path segment is expected between a respective pair of nodes (e.g., between a source helper 402a and a source 402b; between a source 404a and an aggregator 404b; or between an aggregator 406a and an aggregator helper 406b), TCP/IP transport can be utilized between those nodes.
- the multipath overlay network uses a transmission control protocol (TCP) port (e.g., a predetermined TCP port) for transporting overlay network signaling messages.
- TCP transmission control protocol
- the multipath overlay network routing function uses a label switching mechanism to route the data traffic.
- an input label ID can be used by the source helper 215, the aggregator helper 225, and the aggregator 210 to identify the data packets of a unique stream (e.g., a substream) received by the underlying node.
- an output label ID can be used by the source 210, the source helper 215, and the aggregator helper 225 to identify the data packets of a unique stream (e.g., a substream) to be sent by the underlying node.
- the input label ID may be assigned by the recipient of the data packet during the signaling phase, and in one aspect, may be unique only from the perspective of the recipient.
- the output label ID may be assigned by the sender of the data packet.
- a node in the multipath overlay network When a node in the multipath overlay network receives a multipath overlay network data packet, the node examines the input label ID and then sends out this packet to a next hop overlay network address, which may be the destination of the packet in the underlying network.
- the packet may be tagged with the corresponding output label ID.
- Table 1 An example of a switching table is shown in Table 1.
- FIG. 5 is an illustration of a multipath overlay network substantially similar to that illustrated in FIG. 2, further including details to illustrate distribution of label IDs.
- the label IDs that are assigned by a common node are tagged with the same alphabetic character.
- a first overlay network data packet may be sent from source 1 210 along a direct path to aggregator 2 220d.
- the source 1 210 may assign an output label ID of dl, corresponding to the overlay network address of the aggregator 2 220d; and similarly, because this particular data packet is to follow a direct path, the next hop overlay network address also may correspond to that of aggregator 2 220d.
- the data packet arrives at the aggregator 2 220d, the data packet then receives an input label ID corresponding to the overlay network address of the source.
- a second overlay network data packet may be sent from source 1 210 along an alternative path to aggregator 2 220d.
- the alternative path includes source helper 215a and aggregator helper 225b.
- the source 1 210 may assign an output label ID of dl, corresponding to the overlay network address of aggregator 2 220d.
- the next hop overlay network address corresponds to that of source helper 215a.
- the source helper 215a assigns an input label ID corresponding to the overlay network address of source 1 210, since that node was the source of the data packet; and retains the output label ID of aggregator 2 220d.
- the source helper 215a assigns a next hop overlay network address corresponding to that of the aggregator helper 225b.
- the aggregator helper 225b assigns an input label ID corresponding to the overlay network address of source helper 215a, and retains the output label ID of aggregator 2 220d.
- the aggregator helper 225b assigns a next hop overlay network address corresponding to that of aggregator 2 220d.
- aggregator 2 220d assigns an input label ID corresponding to the overlay network address of the aggregator helper 225b.
- an aggregator 220 may be capable of receiving information over multiple paths from a corresponding source 210.
- an aggregator 220 may include a master state machine that governs the path management of the multiple paths it has with the corresponding source 210.
- a master state machine for an aggregator 220 can include multiple atomic state machines.
- each atomic state machine governs the path management of a single path between the aggregator 220 and the corresponding source 210.
- a state transition diagram 600 for an aggregator 220 in accordance with some aspects of the disclosure is shown in FIG. 6.
- the aggregator 220 has states including a Released state 610; a Wait for Aggregator Helper to Join state 620; a Wait for Source to Join state 630; a Joined state 640; a Wait for Aggregator Helper to Replace state 650; and a Wait for Source to Switch state 660.
- the aggregator 220 may utilize timers including an Original Helper Join timer, a Replacement Helper Join timer, and a Source Join timer.
- the aggregator 220 may utilize a binary state variable "helper_active" for state reduction, with, e.g., a default value set to false. Signaling messages that are not designed to be handled as inputs at a certain state may be queued for delayed processing.
- FIGs. 7A-7F are specification and description language (SDL) flow charts illustrating state transitions in the state transition diagram 600 illustrated in FIG. 6.
- SDL specification and description language
- the aggregator 220 may send an Aggregator Helper Join Request message 704 to the corresponding aggregator helper 225, and start an Original Helper Join timer 706. The aggregator 220 may then enter the Wait for Aggregator Helper to Join state 620.
- the aggregator 220 has sent an Aggregator Helper Join Request message, and is awaiting, for the duration of the Original Helper Join timer, an Aggregator Helper Join Response message.
- the aggregator 220 may receive an Aggregator Helper Join Response message 710. If the message is not accepted, the aggregator 220 may enter the Released state 610.
- the aggregator 220 may then set the helper_active variable to true 711, send a Source Join Request message 712, start a Source Join timer 714, and enter the Wait for Source to Join state 630. [0058] As illustrated in FIG. 7C, at the Wait for Source to Join state 630, the aggregator
- the aggregator 220 has sent a Source Join Request message, and is awaiting, for the duration of the Source Join timer, a Source Join Response message.
- the aggregator 220 may enter the Released state 610.
- the aggregator may wish to release the helper corresponding to the helper_active variable, so it may send a Helper Release Request message 718 to its helper, set the helper_active variable to false, and thereafter enter the Released state 610.
- the aggregator 220 may receive a Source Join Response message 722 from the source 210 in response to the Source Join Request message. If the aggregator 220 does not accept the Source Join Response message, then the aggregator 220 follows the process outlined just above to enter into the Released state 610. If the aggregator 220 accepts the Source Join Response message from the source 210, then the aggregator 220 enters the Joined state 640.
- the aggregator 220 may receive an Aggregator Switch Request message 724 from the source 210, to request the aggregator 220 to switch a path between the source 210 and the aggregator 220. The aggregator 220 may then respond to the source 210 with an Aggregator Switch Response message 726 and return to the Joined state 640.
- the aggregator 220 may receive a Helper Release Notification message 728 from a helper node, indicating to release a particular path utilizing that node, between the source 210 and the aggregator 220.
- the aggregator 220 may set the helper_active variable to false 730, and seek to find a replacement helper 732.
- the aggregator 220 may also receive an indication for replacing a joined helper 734, in response to which the aggregator 220 similarly may seek to find a replacement helper 732.
- the aggregator 220 may send a Source Release Command message 736 to the source 210 to release the path between the source 210 and the aggregator 220, and enter the Released state 610. If a replacement helper is found, the aggregator 220 may send an Aggregator Helper Join Request message 738 to the found aggregator helper 225, seeking to set up the path between the source 210 and the aggregator 220 utilizing the found aggregator helper 225. The aggregator 220 may then start the Replacement Helper Join timer 740, and enter the Wait for Aggregator Helper to Replace state 650.
- the aggregator 220 may receive a Source Release Notification message 742 from the source 210 indicating to release a path between the source 210 and the aggregator 220.
- the aggregator 220 may send a Helper Release Command message 744 to a joined helper to release a path between the source 210 and the aggregator 220 utilizing the corresponding helper, and set the helper_active variable false 746, before entering the Released state 610.
- FIG. 7E at the Wait for Aggregator Helper to Replace state
- the aggregator 220 has sent an Aggregator Helper Join Request message to a found replacement aggregator helper 225, and is awaiting, for the duration of the Replacement Helper Join timer, an Aggregator Helper Join Response message from the found replacement aggregator helper 225.
- the aggregator 220 sends a Source Release Command message 750 to the source 210 to release the path between the source 210 and the aggregator 220, and enters the Released state 610.
- the aggregator 220 enters the Joined state 640, retaining the path between the source 210 and the aggregator 220 that includes the helper corresponding to this particular atomic state machine. Further, prior to the expiration of the Replacement Helper Join timer, the aggregator 220 may receive an Aggregator Helper Join Response message 752 from a corresponding aggregator helper 225 in response to an Aggregator Helper Join Request message. If the aggregator 220 does not accept the Aggregator Helper Join Response message, then the aggregator 220 follows the process outlined above to enter into either the Released state 610 or the Joined state 640.
- the aggregator 220 may send a Helper Release Command message 754 to the original helper to release the corresponding path between the source 210 and the aggregator 220 utilizing that helper node. If the helper_active variable is false, the aggregator 220 may skip the sending of the Helper Release Command message 754. Next, the aggregator 220 may send a Source Switch Request message 756 to the source 210 to request the source 210 to switch a path between the source 210 and the aggregator 220, start the Source Join timer 758, and enter the Wait for Source to Switch state 660.
- the aggregator 220 has sent a Source Switch Request message, and is awaiting, for the duration of the Source Join timer, a Source Switch Response message.
- the aggregator 220 may send a Helper Release command 762 to the respective helper, to release the corresponding path between the source 210 and the aggregator 220 utilizing that helper node.
- the aggregator 220 may then set the helper_active variable to false 764, and enter the Released state 610.
- the aggregator 220 may receive a Source Switch Response message 766 from the source 210 in response to the Source Switch Request message. If the aggregator 220 does not accept the Source Switch Response message, the aggregator 220 may follow the process outlined just above to enter into the Released state 610. If the aggregator 220 accepts the Source Switch Response message 766, then the aggregator 220 enters the Joined state 640.
- FIG. 8 is an illustration of a state machine 800 corresponding to an aggregator helper 225, illustrated in FIG. 2.
- An aggregator helper 225 may include a Released state 810 and a Joined state 820. That is, the aggregator helper 225 may be joined to take part in forming a path, or may be released as a cooperative node.
- FIGs. 9A-9B are SDL flow charts illustrating state transitions in the state transition diagram 800 illustrated in FIG. 8.
- the aggregator helper 225 does not act as a cooperative node for a path between a source 210 and an aggregator 220.
- the aggregator helper 225 may receive an Aggregator Helper Join Request message 902 from an aggregator 220 to request the aggregator helper 225 set up a path between a source 210 and the aggregator 220.
- the aggregator helper 225 may send a Negative Aggregator Helper Join Response message 904 to the aggregator 220, and return to the Released state 810. If the aggregator helper 225 accepts the Aggregator Helper Join Request message, the aggregator helper 225 may send a Positive Aggregator Helper Join Response message 906 to the aggregator 220, and enter the Joined state 820, in which the aggregator helper 225 acts as a cooperative node in a path between a source 210 and the aggregator 220.
- the aggregator helper 225 acts as a cooperative node in a path between a source 210 and an aggregator 220.
- the aggregator helper 225 may receive a Release Indication message 908, indicating to release the path between the source 210 and the aggregator 220, including the aggregator helper 225.
- the aggregator helper 225 may send a Helper Release Notification message 910 to the aggregator 220 to release the corresponding path.
- the aggregator helper 225 may receive a Helper Release Command message 912 from an aggregator 220 to release a path between the aggregator 220 and a source 210.
- the aggregator helper 225 may enter the Released state 810, wherein the aggregator helper 225 does not act as a cooperative node for a path between a source 210 and an aggregator 220.
- a source 210 may be capable of sending information over multiple paths to a corresponding aggregator 220.
- a source 210 may include a master state machine that governs the path management of the multiple paths established with the corresponding aggregator 220.
- a master state machine for a source 210 can include multiple atomic state machines.
- each atomic state machine governs the path management of a path between the source 210 and the corresponding aggregator 220.
- a state transition diagram 1000 for a source 210 in accordance with some aspects of the disclosure is shown in FIG. 10.
- the source 210 has states including a Released state 1010; a Wait for Source Helper to Join state 1020; a Joined state 1040; a Wait for Source Helper to Replace state 1050; a Wait for Aggregator to Switch state 1060; and a Wait for Source Helper to Switch state 1070.
- the source 210 may utilize timers including an Original Helper Join timer, a Replacement Helper Join timer, and an Aggregator Join timer.
- the source 210 may utilize a binary state variable "helper_active" for state reduction, with, e.g., a default value set to false. Signaling messages that are not designed to be handled as inputs at a certain state may be queued for a delayed processing.
- helper_active a binary state variable set to false.
- FIGs. 11A-1 1F are SDF flow charts illustrating state transitions in the state transition diagram 1000 illustrated in FIG. 10.
- the path between the source 210 and the node corresponding to this particular atomic state machine is released.
- the source 210 may transition to the Joined state 1040 or the Wait for Source Helper to Join state 1020.
- the source 210 may receive a Source Join Request message 1 102 from an aggregator 220 to request the source 210 to setup a path between the source 210 and the aggregator 220.
- the source 210 may update path information 1104 to establish a direct path from the source 210 to the aggregator 220, and may move to the Joined state 1040. If the source 210 desires a helper, the source 210 may send a Source Helper Join Request message 1 106 to the corresponding source helper 215, and start an Original Helper Join timer 1 108. The source 210 may then enter the Wait for Source Helper to Join state 1020.
- the source 210 has sent a Source Helper Join Request message, and is awaiting, for the duration of the Original Helper Join timer, a Source Helper Join Response message.
- the source 210 may send a Negative Source Join Response message 1 112 to the aggregator 220, and may enter the Released state 1010.
- the source 210 may receive a Source Helper Join Response message 1 114. If the message is not accepted, the source 210 may send a Negative Source Join Response message 11 12 to the aggregator 220, and may enter the Released state 1010. If the message is accepted, the source 210 may then set the helper_active variable to true 1 116, send a Positive Source Join Response message 11 18, and enter the Joined state 1040.
- the source 210 may receive a Source Switch Request message 1120 from the aggregator 220, to request the source 210 to switch a path between the source 210 and the aggregator 220. If the helper_active variable is false, then the source 210 may update path information 1122 to indicate the new path between the source 210 and the aggregator 220, and may enter the Joined state 1040.
- the source 210 may send a Source Helper Switch Request message 1 124 to a source helper 215 to request the source helper 215 to switch a path between the source 210 and the aggregator 220, start the Source Helper Join timer 1 126, and enter the Wait for Source Helper to Switch state 1070. Further, in the Joined state 1040, the source 210 may receive a Helper Release Notification message 1128 from a helper node, indicating to release a particular path utilizing that node, between the source 210 and the aggregator 220. Here, to release the path, the source 210 may set the helper active variable to false 1130, and seek to find a replacement helper 1 132.
- the source 210 may also receive an indication for replacing a joined helper 1134, in response to which the source 210 similarly may seek to find a replacement helper 1 132.
- the source 210 may send a Source Release Notification message 1136 to the aggregator 220 to release the path between the source 210 and the aggregator 220, and enter the Released state 1010.
- the source 210 may send a Source Helper Join Request message 1 138 to the found source helper 215, seeking to set up the path between the source 210 and the aggregator 220 utilizing the found source helper 215.
- the source 210 may then start the Replacement Helper Join timer 1140, and enter the Wait for Source Helper to Replace state 1050. Further, in the Joined state 1040, the source 210 may receive a Source Release Command message 1 142 from the aggregator 220 indicating to release a path between the source 210 and the aggregator 220. Here, the source 210 may send a Helper Release Command message 1144 to a joined helper to release a path between the source 210 and the aggregator 220 utilizing the corresponding helper, and set the helper_active variable to false 1146, before entering the Released state 1010.
- the source 210 may receive an Indication to Release message 1148, in response to which the source 210 may send a Helper Release Command message 1 150 to the corresponding helper to release a path between the source 210 and the aggregator 220 utilizing that helper node.
- the source 210 may then set the helper active variable to false 1 152, send a Source Release Notification message 1154 to the aggregator 220, and enter the Released state 1010.
- the source 210 has sent a Source Helper Switch Request message, and is awaiting, for the duration of the Original Helper Join timer, a Source Helper Switch Response message.
- the source 210 may send a Helper Release command 1 158 to the respective helper, to release the corresponding path between the source 210 and the aggregator 220 utilizing that helper node. The source 210 may then set the helper active variable to false 1 160, and enter the Released state 1010. However, prior to the expiration of the Original Helper Join timer, the source 210 may receive a Source Helper Switch Response message 1 166 from the source helper 215 in response to a Source Helper Switch Request message. If the source 210 does not accept the Source Helper Switch Response message, the source 210 may follow the process outlined just above to enter into the Released state 1010. If the source 210 accepts the Source Helper Switch Response message 766, then the source 210 may send a Source Switch Response message 1 168 to the aggregator to respond to the Source Switch Request message, and may enter the Joined state 1040.
- the source 210 has sent a Source Helper Join Request message to a found replacement source helper 215, and is awaiting, for the duration of the Replacement Helper Join timer, a Source Helper Join Response message from the found replacement source helper 215.
- the replacement Helper Join timer expires 1 170, but if the helper active variable is false (indicating that the source 210 is not joined to a helper node), the source 210 sends a Source Release Notification message 1 172 to the aggregator 220 to release the path between the source 210 and the aggregator 220, and enters the Released state 1010.
- the source 210 enters the Joined state 1040, retaining the path between the source 210 and the aggregator 220 that includes the helper corresponding to this particular atomic state machine. Further, prior to the expiration of the Replacement Helper Join timer, the source 210 may receive a Source Helper Join Response message 1 174 from a corresponding source helper 215 in response to a Source Helper Join Request message. If the source 210 does not accept the Source Helper Join Response message, then the source 210 follows the process outlined above to enter into either the Released state 1010 or the Joined state 1040.
- the source 210 may send a Helper Release Command message 1176 to the original helper to release the corresponding path between the source 210 and the aggregator 220 utilizing that helper node. If the helper_active variable is false, the source 210 may skip the sending of the Helper Release Command message 1176. Next, the source 210 may send an Aggregator Switch Request message 1178 to the aggregator 220 to request the aggregator 220 to switch a path between the source 210 and the aggregator 220, start the Aggregator Join timer 1180, and enter the Wait for Aggregator to Switch state 1060.
- the source 210 has sent an Aggregator Switch Request message, and is awaiting, for the duration of the Aggregator Join timer, an Aggregator Switch Response message.
- the source 210 may send a Helper Release command 1 184 to the respective helper, to release the corresponding path between the source 210 and the aggregator 220 utilizing that helper node.
- the source 210 may then set the helper active variable to false 1 186, and enter the Released state 1010.
- the source 210 may receive an Aggregator Switch Response message 1188 from the aggregator 220 in response to the Aggregator Switch Request message. If the source 210 does not accept the Aggregator Switch Response message, the source 210 may follow the process outlined just above to enter into the Released state 1010. If the source 210 accepts the Aggregator Switch Response message 1 188, then the source 210 enters the Joined state 1040.
- FIG. 12 is an illustration of a state machine 1200 corresponding to a source helper 215, illustrated in FIG. 2.
- a source helper 215 may include a Released state 1210 and a Joined state 1220. That is, the source helper 215 may be joined to take part in forming a path, or may be released as a cooperative node.
- FIGs. 13A-13B are SDL flow charts illustrating state transitions in the state transition diagram 1200 illustrated in FIG. 12.
- the source helper 215 does not act as a cooperative node for a path between a source 210 and an aggregator 220.
- the source helper 215 may receive a Source Helper Join Request message 1302 from a source 210 to request the source helper 215 set up a path between the source 210 and an aggregator 220. If the source helper 215 does not accept the Source Helper Join Request message, the source helper 215 may send a Negative Source Helper Join Response message 1304 to the source 210, and return to the Released state 1210.
- the source helper 215 may send a Positive Source Helper Join Response message 1306 to the source 210, and enter the Joined state 1220, in which the source helper 215 acts as a cooperative node in a path between the source 210 and an aggregator 220.
- the source helper 215 acts as a cooperative node in a path between a source 210 and an aggregator 220.
- the source helper 215 may receive a Release Indication 1308, and in response, the source helper 215 may send a Helper Release Notification message 1310 to the source 210 to release the path between the source 210 and an aggregator 220 utilizing the source helper 215. Further, the source helper 215 may receive a Helper Release Command message 1312 from a source 210 to release a path between the source 210 and an aggregator 220.
- the source helper 215 may enter the Released state 1210, wherein the source helper 215 does not act as a cooperative node for a path between a source 210 and an aggregator 220. Still further, the source helper 215 may receive a Source Helper Switch Request message 1314 from the source 210 to request the source helper 215 to switch a path between the source 210 and an aggregator 220. Here, the source helper 215 may respond by sending a Source Helper Switch Response message 1316 and enter the Joined state 1220.
- FIG. 14 An example of a data packet header that may be utilized in multipath overlay network data packets are shown in FIG. 14.
- the message type field in the packet header of data packets may be set to "data,” and the data payload of the data packets may start immediately after the packet header.
- FIG. 15 An example of a signaling packet header that may be utilized in multipath overlay network signaling messages is shown in FIG. 15.
- the payload of the corresponding signaling messages may start immediately after the packet header.
- Table 2 The meanings of the packet header fields for a particular implementation in accordance with some aspects of the disclosure are given in Table 2.
- an information element for characterizing the overlay network message type may be carried.
- the message types utilized in an exemplary implementation in accordance with some aspects of the present disclosure are listed in Table 3.
- an Aggregator Helper Join Request message may be sent from the aggregator 220 to corresponding aggregator helper 225, in order to request the aggregator helper 225 to set up a path between the source 210 and the aggregator 220.
- An Aggregator Helper Join Request message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 4.
- An Aggregator Helper Join Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 5.
- the Aggregator Helper Join Response message may be sent from the aggregator helper 225 to the aggregator 220, in order to respond to a corresponding Aggregator Helper Join Request message.
- Aggregator Overlay network address of the aggregator used 32 bits address by the receiver of the Join Response to check whether this message should be processed
- Transaction ID May be equal to the transaction ID in the 8 bits
- Label ID Identifies the label ID that should be used for the 8 bits
- Source Join Request message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 6.
- the Source Join Request message may be sent from the aggregator 220 to the source 210 to request the source 210, in order to setup a path between the source 210 and the aggregator 220.
- Aggregator Overlay network address of the aggregator used 32 bits address by the receiver of the Join Request to identify its
- Source address Overlay network address of the source used by 32 bits
- Session ID Uniquely identifies the traffic session to be 32 bits
- Aggregator or Overlay network address of the aggregator 32 bits aggregator helper helper may be used by either the source or the
- Transport layer Transport layer type to be used for the data 4 bits type delivered over this path, such as TCP, UDP, etc.
- Source Join Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 7.
- the Source Join Response message may be sent from the source 210 to the aggregator 220, in order to respond to a Source Join Request message.
- the Aggregator Switch Request message may be sent from the source 210 to the aggregator 220, in order to request the aggregator 220 to switch a path between the source 210 and the aggregator 220.
- Source address Overlay network address of the source used by 32 bits
- Aggregator Overlay network address of the aggregator used 32 bits address by the receiver of the Switch Request to check
- Session ID Uniquely identifies the traffic session to be 32 bits
- an Aggregator Switch Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 9.
- the Aggregator Switch Response message may be sent from the aggregator 220 to the source 210, in order to respond to an Aggregator Switch Request message.
- Source Switch Request message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 10.
- the Source Switch Request message may be sent from the aggregator 220 to the source 210, in order to request the source 210 to switch a path between the source 210 and the aggregator 220.
- Aggregator Overlay network address of the aggregator used 32 bits address by the receiver of the Switch Request to identify
- Source address Overlay network address of the source used by 32 bits
- Session ID Uniquely identifies the traffic session to be 32 bits
- New Label ID New label ID to be used on the packet sent from 8 bits
- Source Switch Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 1 1.
- the Source Switch Response message may be sent from the source 210 to the aggregator 220, in order to respond to a Source Switch Request message.
- Source Helper Join Request message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 12.
- the Source Helper Join Request message may be sent from the source 210 to the source helper 215, in order to request the source helper 215 to set up a path between the source 210 and the aggregator 220.
- Source address Overlay network address of the source used by 32 bits
- Source Helper Join Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 13.
- the Source Helper Join Response message may be sent from the source helper 215 to the source 210, in order to respond to a Source Helper Join Request message.
- Source Helper Switch Request message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 14.
- the Source Helper Switch Request message may be sent from the source 210 to the source helper 215, in order to request a source helper 215 to switch a path between the source aggregator.
- Source Helper Switch Response message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 15.
- the Source Helper Switch Response message may be sent from the source helper 215 to the source 210, in order to respond to the Source Helper Switch Request message.
- Source Release Command message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 16.
- the Source Release Command message may be sent from the aggregator 220 to the source 210, in order to release a path between the source 210 and the aggregator 220.
- Table 16 Source Release Command Message
- Source Release Notification message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 17.
- the Source Release Notification message may be sent from the source 210 to the aggregator 220, in order to release a path between the source 210 and the aggregator 220.
- Source address Overlay network address of the source used by 32 bits
- Aggregator Overlay network address of the aggregator used 32 bits address by the receiver of the Release Notification to
- Session ID Uniquely identify the traffic session to be 32 bits
- a Helper Release Command message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 18.
- the Helper Release Command message may be sent from the aggregator 220 or the source 210 to its respective helper 225 or 215, in order to release a path between the aggregator 220 and the source 210.
- a Helper Release Notification message for a particular implementation in accordance with some aspects of the disclosure is listed in Table 19.
- the Helper Release Notification message may be sent from a respective helper 225, 215 to its aggregator 220 or source 210, in order to release a path between the source 210 and the aggregator 220.
- processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
- DSPs digital signal processors
- FPGAs field programmable gate arrays
- PLDs programmable logic devices
- state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
- One or more processors in the processing system may execute software.
- Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
- the software may reside on a computer-readable medium.
- the computer-readable medium may be a non-transitory computer-readable medium.
- a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
- a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
- an optical disk e.g., compact disk (CD), digital versatile disk (DVD)
- a smart card e.g., a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM
- the computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer.
- the computer-readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system.
- the computer- readable medium may be embodied in a computer-program product.
- a computer-program product may include a computer-readable medium in packaging materials.
- Nodes such as aggregators, sources, their respective helpers, processors contained therein, computer program products, etc., may "support" data transport and communication, as disclosed in the specification, by providing or originating data, as provided, for example, by a source (in one or more substreams containing distinct descriptions of the data), relaying a description of the data in a substream, as provided, for example by a source helper and aggregator helper, and by receiving and aggregating one or more descriptions of the data in respective substreams, as provided, for example, by an aggregator.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201280035826.0A CN103688507B (en) | 2011-05-26 | 2012-05-25 | Multipath overlay network and multipath management agreement thereof |
KR1020137034580A KR101523685B1 (en) | 2011-05-26 | 2012-05-25 | Multipath overlay network and its multipath management protocol |
JP2014512172A JP5852233B2 (en) | 2011-05-26 | 2012-05-25 | Multipath overlay network and its multipath management protocol |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/116,980 | 2011-05-26 | ||
US13/116,980 US9444887B2 (en) | 2011-05-26 | 2011-05-26 | Multipath overlay network and its multipath management protocol |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2012162674A1 true WO2012162674A1 (en) | 2012-11-29 |
WO2012162674A8 WO2012162674A8 (en) | 2014-01-03 |
Family
ID=46197735
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2012/039733 WO2012162674A1 (en) | 2011-05-26 | 2012-05-25 | Multipath overlay network and its multipath management protocol |
Country Status (6)
Country | Link |
---|---|
US (1) | US9444887B2 (en) |
JP (1) | JP5852233B2 (en) |
KR (1) | KR101523685B1 (en) |
CN (1) | CN103688507B (en) |
TW (1) | TWI499256B (en) |
WO (1) | WO2012162674A1 (en) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10051074B2 (en) * | 2010-03-29 | 2018-08-14 | Samsung Electronics Co, Ltd. | Techniques for managing devices not directly accessible to device management server |
US8995338B2 (en) | 2011-05-26 | 2015-03-31 | Qualcomm Incorporated | Multipath overlay network and its multipath management protocol |
US20120331551A1 (en) * | 2011-06-24 | 2012-12-27 | Koninklijke Kpn N.V. | Detecting Phishing Attempt from Packets Marked by Network Nodes |
US8885502B2 (en) | 2011-09-09 | 2014-11-11 | Qualcomm Incorporated | Feedback protocol for end-to-end multiple path network systems |
US8751698B1 (en) * | 2011-09-30 | 2014-06-10 | Emc Corporation | Storage path management host agent |
US8520533B1 (en) * | 2011-09-30 | 2013-08-27 | Emc Corporation | Storage path management bus view |
WO2014117775A1 (en) * | 2013-01-31 | 2014-08-07 | Codemate A/S | Network content delivery method using a delivery helper node |
US10158966B2 (en) * | 2014-11-05 | 2018-12-18 | At&T Intellectual Property I, L.P. | Connected car data links aggregator |
US10708173B2 (en) | 2015-06-12 | 2020-07-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Multipath forwarding in an overlay network |
US9942131B2 (en) * | 2015-07-29 | 2018-04-10 | International Business Machines Corporation | Multipathing using flow tunneling through bound overlay virtual machines |
CN112910713A (en) * | 2021-03-02 | 2021-06-04 | 山东省计算中心(国家超级计算济南中心) | Cloud-edge data distribution transmission method, edge node, control center and storage medium |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007021725A2 (en) * | 2005-08-12 | 2007-02-22 | Nokia Siemens Networks Gmbh & Co. Kg | A multi-source and resilient video on demand streaming system for a peer-to-peer subscriber community |
US20090073921A1 (en) * | 2007-09-19 | 2009-03-19 | At&T Services Inc. | Data forwarding in hybrid mesh networks |
US20100260190A1 (en) * | 2009-04-14 | 2010-10-14 | Skype Limited | Method and system for data transmission |
Family Cites Families (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5715516A (en) | 1995-10-18 | 1998-02-03 | Cellular Telecom, Ltd. | Method and apparatus for wireless communication employing collector arrays |
US6275470B1 (en) | 1999-06-18 | 2001-08-14 | Digital Island, Inc. | On-demand overlay routing for computer-based communication networks |
US6580909B1 (en) * | 1999-08-26 | 2003-06-17 | International Business Machines Corporation | Communications system and method based on the relative positions of mobile units |
US7062570B2 (en) | 2000-08-04 | 2006-06-13 | Avaya Technology, Corp. | High performance server farm with tagging and pipelining |
WO2002023934A1 (en) | 2000-09-15 | 2002-03-21 | Mspect, Inc. | Wireless network monitoring |
FI110977B (en) | 2001-02-09 | 2003-04-30 | Nokia Oyj | A mechanism for promoting services and authorizing a user |
US6834044B2 (en) | 2001-02-15 | 2004-12-21 | Telefonaktiebolaget L M Ericsson (Publ) | Multi-path data streaming in a wireless packet data network |
US20030007515A1 (en) | 2001-07-03 | 2003-01-09 | Apostolopoulos John G. | System and method for receiving mutiple description media streams in fixed and mobile streaming media systems |
US6954435B2 (en) | 2002-04-29 | 2005-10-11 | Harris Corporation | Determining quality of service (QoS) routing for mobile ad hoc networks |
US20040148391A1 (en) | 2003-01-11 | 2004-07-29 | Lake Shannon M | Cognitive network |
US7388841B2 (en) * | 2003-10-20 | 2008-06-17 | Mitsubishi Electric Research Laboratories, Inc. | Selecting multiple paths in overlay networks for streaming data |
EP1709769A1 (en) | 2004-01-30 | 2006-10-11 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Method for transferring packets in networks comprising a plurality of linked intermediate networks |
US7080173B2 (en) | 2004-05-27 | 2006-07-18 | Microsoft Corporation | Reducing information reception delays |
US7733769B1 (en) | 2004-06-08 | 2010-06-08 | Cisco Technology, Inc. | Method and apparatus for identifying a media path in a network |
EP1776806A1 (en) | 2004-08-13 | 2007-04-25 | Matsushita Electric Industrial Co., Ltd. | Method for providing mobility to a mobile host in a wireless network employing point-to-multipoint multi-protocol label switching |
US7715396B2 (en) | 2004-08-19 | 2010-05-11 | Microsoft Corporation | Network routing |
US7330457B2 (en) * | 2004-10-07 | 2008-02-12 | Polytechnic University | Cooperative wireless communications |
US20060224763A1 (en) | 2005-03-18 | 2006-10-05 | Sharp Laboratories Of America, Inc. | Switching and simultaneous usage of 802.11a and 802.11g technologies for video streaming |
KR100687739B1 (en) | 2005-03-29 | 2007-02-27 | 한국전자통신연구원 | Method for monitoring link performance and diagnosing active status of link for Ethernet Passive Optical Network |
WO2007020563A1 (en) | 2005-08-19 | 2007-02-22 | Koninklijke Philips Electronics N.V. | Method and apparatus of multiple antennas transmission |
US8467377B2 (en) | 2005-08-24 | 2013-06-18 | Qualcomm Incorporated | Interleaving VoIP/VIP transmission in multiple sessions to increase quality of service in mobile devices having multiple interfaces |
JP2007074564A (en) | 2005-09-08 | 2007-03-22 | Oki Electric Ind Co Ltd | Network routing method and radio station |
US20070110035A1 (en) | 2005-11-14 | 2007-05-17 | Broadcom Corporation, A California Corporation | Network nodes cooperatively routing traffic flow amongst wired and wireless networks |
US7839850B2 (en) | 2006-01-30 | 2010-11-23 | Juniper Networks, Inc. | Forming equal cost multipath multicast distribution structures |
KR101256687B1 (en) | 2006-02-13 | 2013-04-19 | 리서치 파운데이션 오브 더 시티 유니버시티 오브 뉴욕 | Apparatus for setting multipath and method thereof |
US7643427B2 (en) | 2006-03-28 | 2010-01-05 | Nec Laboratories America, Inc. | Multipath routing architecture for large data transfers |
US8976670B2 (en) | 2006-11-16 | 2015-03-10 | Rockstar Consortium Us Lp | System and method for delivering packet data over a multiplicity of communication links |
JP4830025B2 (en) | 2006-11-29 | 2011-12-07 | トムソン ライセンシング | CONTRIBUTIONAWARE peer-to-peer live streaming service |
US9094416B2 (en) | 2006-11-29 | 2015-07-28 | Thomson Licensing | Contribution aware peer-to-peer live streaming service |
US7630370B2 (en) | 2007-02-28 | 2009-12-08 | Sharp Laboratories Of America, Inc. | Overlay join latency reduction using preferred peer list |
CN101287268B (en) | 2007-04-13 | 2012-05-09 | 中兴通讯股份有限公司 | Method for updating connection relation of wireless relay station |
JP2008301002A (en) | 2007-05-30 | 2008-12-11 | Nec Corp | Data processor, line selection control method used therefor, and program thereof |
US8175043B2 (en) * | 2007-12-20 | 2012-05-08 | Verizon Patent And Licensing Inc. | Method and system for establishing disparate connection paths from a mobile user device to a base station through a mobile peer-to-peer (PTP) network |
WO2009092155A1 (en) | 2008-01-22 | 2009-07-30 | Nortel Networks Limited | Path selection for a wireless system with relays |
KR101414632B1 (en) | 2008-03-06 | 2014-07-03 | 엘지전자 주식회사 | Method for communicating in a mobile station and system with relay stations |
MX2010011654A (en) | 2008-04-22 | 2010-11-26 | Thomson Licensing | Method and apparatus for multicast tree management in multi-hop relay communication system. |
US20090290555A1 (en) | 2008-05-21 | 2009-11-26 | Comsys Communication & Signal Processing Ltd. | Autonomous anonymous association between a mobile station and multiple network elements in a wireless communication system |
US7953010B2 (en) | 2008-07-30 | 2011-05-31 | Avaya Inc. | System and method of controlling in-bound path selection based on historical and continuous path quality monitoring, assessment and predictions |
US20100088390A1 (en) | 2008-10-03 | 2010-04-08 | Microsoft Corporation | Data sharing proxy for mobile devices |
US7738406B2 (en) * | 2008-10-08 | 2010-06-15 | Microsoft Corporation | Models for routing tree selection in peer-to-peer communications |
JP2010109825A (en) | 2008-10-31 | 2010-05-13 | Advanced Telecommunication Research Institute International | Radio device and radio network with the same |
US20100121971A1 (en) | 2008-11-10 | 2010-05-13 | Samsung Electronics Co., Ltd. | Multipath transmission of three-dimensional video information in wireless communication systems |
JP5436451B2 (en) | 2008-12-26 | 2014-03-05 | パナソニック株式会社 | Communication terminal, communication method, program |
WO2010143894A2 (en) | 2009-06-10 | 2010-12-16 | Lg Electronics Inc. | Method and apparatus for transmitting frame in wireless local area network (wlan) system |
US20100315958A1 (en) | 2009-06-11 | 2010-12-16 | Luo Xiapu | Method for non-cooperative measurement of network data-path quality |
US9277021B2 (en) * | 2009-08-21 | 2016-03-01 | Avaya Inc. | Sending a user associated telecommunication address |
US8489722B2 (en) | 2009-11-24 | 2013-07-16 | International Business Machines Corporation | System and method for providing quality of service in wide area messaging fabric |
US8995338B2 (en) | 2011-05-26 | 2015-03-31 | Qualcomm Incorporated | Multipath overlay network and its multipath management protocol |
US20120311072A1 (en) | 2011-06-01 | 2012-12-06 | Qualcomm Incorporated | Multipath management architecture and protocols for mobile multimedia service with multiple description coding |
US8885502B2 (en) | 2011-09-09 | 2014-11-11 | Qualcomm Incorporated | Feedback protocol for end-to-end multiple path network systems |
-
2011
- 2011-05-26 US US13/116,980 patent/US9444887B2/en not_active Expired - Fee Related
-
2012
- 2012-05-25 KR KR1020137034580A patent/KR101523685B1/en not_active IP Right Cessation
- 2012-05-25 TW TW101118734A patent/TWI499256B/en active
- 2012-05-25 CN CN201280035826.0A patent/CN103688507B/en not_active Expired - Fee Related
- 2012-05-25 WO PCT/US2012/039733 patent/WO2012162674A1/en active Application Filing
- 2012-05-25 JP JP2014512172A patent/JP5852233B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007021725A2 (en) * | 2005-08-12 | 2007-02-22 | Nokia Siemens Networks Gmbh & Co. Kg | A multi-source and resilient video on demand streaming system for a peer-to-peer subscriber community |
US20090073921A1 (en) * | 2007-09-19 | 2009-03-19 | At&T Services Inc. | Data forwarding in hybrid mesh networks |
US20100260190A1 (en) * | 2009-04-14 | 2010-10-14 | Skype Limited | Method and system for data transmission |
Non-Patent Citations (1)
Title |
---|
MOHAMED HEFEEDA ET AL: "PROMISE: PeertoPeer Media Streaming Using CollectCast", PROCEEDINGS OF THE 11TH. ACM INTERNATIONAL CONFERENCE ON MULTIMEDIA. MM'03. BERKELEY, CA, NOV. 4 - 6, 2003; [ACM INTERNATIONAL MULTIMEDIA CONFERENCE], NEW YORK, NY : ACM, US, vol. CONF. 11, 2 November 2003 (2003-11-02), pages 1 - 10, XP002409310, ISBN: 978-1-58113-722-4 * |
Also Published As
Publication number | Publication date |
---|---|
KR101523685B1 (en) | 2015-05-28 |
CN103688507B (en) | 2016-10-19 |
US20120303822A1 (en) | 2012-11-29 |
TW201306534A (en) | 2013-02-01 |
JP2014522592A (en) | 2014-09-04 |
CN103688507A (en) | 2014-03-26 |
KR20140017678A (en) | 2014-02-11 |
TWI499256B (en) | 2015-09-01 |
WO2012162674A8 (en) | 2014-01-03 |
JP5852233B2 (en) | 2016-02-03 |
US9444887B2 (en) | 2016-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9444887B2 (en) | Multipath overlay network and its multipath management protocol | |
US8995338B2 (en) | Multipath overlay network and its multipath management protocol | |
US20150237525A1 (en) | Traffic Shaping and Steering for a Multipath Transmission Control Protocol Connection | |
US20120311072A1 (en) | Multipath management architecture and protocols for mobile multimedia service with multiple description coding | |
KR102178236B1 (en) | Devices for multipath communication over multiple radio access technologies | |
US9998298B2 (en) | Data transmission method, apparatus, and computer storage medium | |
US10673991B2 (en) | Method and system for the scheduling of packets in a bundling scenario based on TCP tunnels and native TCP information | |
WO2013029521A1 (en) | Method, flow-distribution equipment, user terminal and system for data transmission | |
US9661550B2 (en) | Communication apparatus, communication method, and communication system | |
CN109218111B (en) | Method for processing message and repeater | |
WO2019196853A1 (en) | Tcp acceleration method and apparatus | |
WO2013040277A1 (en) | Transmitting data over multiple networks | |
CN106034078B (en) | Method and system for reducing DR change of PIM protocol | |
Guo et al. | Join and spilt TCP for SDN networks: Architecture, implementation, and evaluation | |
CN113454959A (en) | Control plane network function, user plane network function, and packet processing method using the same | |
CN111247837A (en) | Method and device for binding data stream and computer storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12724843 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2014512172 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20137034580 Country of ref document: KR Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12724843 Country of ref document: EP Kind code of ref document: A1 |