WO2012107360A1 - Réseau superposé - Google Patents

Réseau superposé Download PDF

Info

Publication number
WO2012107360A1
WO2012107360A1 PCT/EP2012/051870 EP2012051870W WO2012107360A1 WO 2012107360 A1 WO2012107360 A1 WO 2012107360A1 EP 2012051870 W EP2012051870 W EP 2012051870W WO 2012107360 A1 WO2012107360 A1 WO 2012107360A1
Authority
WO
WIPO (PCT)
Prior art keywords
level nodal
entities
network
level
overlay network
Prior art date
Application number
PCT/EP2012/051870
Other languages
English (en)
Inventor
Hector H. Gonzalez-Banos
Robert Martin WOLFF
Manjesh MALAVALLI
Original Assignee
Xvd Technology Holdings Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/025,128 external-priority patent/US8688827B2/en
Priority claimed from US13/071,710 external-priority patent/US20120246295A1/en
Application filed by Xvd Technology Holdings Limited filed Critical Xvd Technology Holdings Limited
Publication of WO2012107360A1 publication Critical patent/WO2012107360A1/fr

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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • 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
    • H04L67/1044—Group management mechanisms 
    • H04L67/1051—Group master selection mechanisms
    • 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
    • H04L67/1087—Peer-to-peer [P2P] networks using cross-functional networking aspects
    • H04L67/1089—Hierarchical topologies
    • 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
    • H04L67/1087—Peer-to-peer [P2P] networks using cross-functional networking aspects
    • H04L67/1093—Some peer nodes performing special functions

Definitions

  • the present invention relates to multimedia and telecommunications technology, and more specifically, to communications networks.
  • MCUs Multi-point Control Units
  • Ad-hoc multi-point calls can sometimes circumvent the use of the MCU.
  • this comes at the expense of interoperability loss, additional endpoint complexity, and increased use of network bandwidth, since every participant in a multi-party conference must transmit their video and audio stream to every remote conference participant.
  • Hardware-based MCUs conventionally contain specialized hardware for performing various types of functionality, such as encoding, decoding and transcoding video and audio streams between different formats.
  • the hardware-based MCUs can additionally perform various types of value added functionality, such as recording video and audio data for several video codecs.
  • the hardware-based solution provides high performance and high fidelity of the video and audio signals.
  • cross- connecting units tends to be both complex and costly.
  • a host network is provided.
  • the host network includes a system of interconnected computers and can support one or more transport layer protocols.
  • a first overlay network is generated on top of the host network.
  • the first overlay network includes one or more first- level nodal entities. At least some of the first-level nodal entities operate as factories for generating second-level nodal entities in a second overlay network.
  • one or more factories dynamically generate the second overlay network.
  • the second overlay network includes several networked second-level nodal entities that can supp ort data processing and data communication between the second-level nodal entities.
  • a second-level nodal entity can function as a proxy server for another second-level nodal entity.
  • the first-level nodal entities can include one or more processes running in one or more networked virtual or physical servers.
  • the first-level nodal entities can be processes hosted in a cloud-computing environment.
  • a factory can destroy a second-level nodal entity, or a second-level nodal entity can destroy itself.
  • the one or more factories can generate, delete or migrate second-level nodal entities based on link congestion, user behavior, business targets, communication costs or communication failure.
  • Each factory can manage its generated second-level nodal entities and monitor computational resources consumed on its host and by the hosts for the second-level nodal entities generated by the factory.
  • the performance of the factories can be monitored and if a malfunctioning factory is detected, the tasks of the malfunctioning factory can be assumed by one or more of the other factories.
  • Data originating at a second-level nodal entity can be distributed to a designated set of second-level nodal entities in the second overlay network, wherein the designated set of second-level nodal entities is disjoint from other second-level entities in the second overlay network. Entities in the designated set of second-level nodal entities can be connected to form a graph, so that the second-level nodal entities in the designated set of second-level nodal entities constitute vertices of the graph and the connections between the second-level nodal entities constitute links of the graph.
  • Data can be distributed within the designated set of second-level nodal entities from a source second-level nodal entity to a destination second-level nodal entity along an acyclical path. The data distribution from the source second-level nodal entity to the destination second-level nodal entity along the acyclical path can be ensured by using a rooted tree having the source second-level nodal entity as a root.
  • the second overlay network can implement real-time publish-subscribe network functionality.
  • the real-time data stream can be published in several versions by one or more second-level nodal entities among the second-level nodal entities.
  • One or more second-level nodal entities can subscribe to real-time data streams published by one or more second-level nodal entities.
  • a second-level nodal entity can aggregate two or more real-time data streams into a single real-time data stream and retransmit the single real-time data stream.
  • a second-level nodal entity can transform a real-time data stream from a first format into a second format.
  • a second-level nodal entity can record a real-time data stream.
  • a second-level nodal entity can play back a data stream.
  • the host network can support a Transmission Control Protocol or a User Data Protocol.
  • the data communication among the second-level nodal entities can include video, audio, chat, financial market data, radar data, telemetry, telecommands, teleprescence data, haptics measurements, or telemedicine data.
  • the second overlay network can be a content delivery network, a publish-subscribe network, a data-centric publish-subscribe network, a real-time transport protocol network, a sensor network, a peer-to-peer network, a user datagram protocol network, or a content addressable storage network.
  • the second-level nodal entities can be nodes or supernodes of a peer-to- peer network.
  • Various implementations can include one or more of the following advantages.
  • Media streams can be interconnected and bridged in a fully decentralized manner, relying on existing IT infrastructure, and offer the same benefits as a centralized MCU. This is true not only for video communication, but also for other real-time and/or high-throughput applications.
  • a highly scalable, elastic, fault tolerant, variable cost network is provided that allows the connection and transformation of variable and high bandwidth streams according to business, quality or other goals.
  • FIG. 1 is a schematic diagram of a two layer overlay network on top of a host network, in accordance with one implementation.
  • the various implementations of the invention are directed to a two-level overlay network on top of a host network, such as a network supporting, for example, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP).
  • the first overlay network can be described as a persistent, dynamically scaled and highly available network.
  • the second overlay network is dynamically created by the first overlay network.
  • the first overlay network requires reasonable, but not stringent response times and relatively low bandwidth to support signaling.
  • the second overlay is configured dynamically by signals from the first overlay, and requires a real-time high bandwidth infrastructure for video and other high bandwidth real time communications.
  • the second overlay network further contains second-level nodal entities (referre d to henceforth as "entities”) that are instantiated, destroyed and supervised by the first overlay network.
  • entities serve as relays or proxies either for another entity within the second overlay network or for an external source outside the second overlay network.
  • These entities publish their stream of data, potentially in several versions. These versions can vary based on factors such as the quality of the stream, the encoding provided, or another transformation of the incoming data stream.
  • an entity can stream data to another entity in a cascading manner or stream the data directly to an external destination in an application endpoint. Entities can subscribe to a topic and receive a specific level of service that the entity requests.
  • the second overlay network can connect from a single parent and in a unidirectional manner to other entities in a "fan out configuration" until the stream arrives at one or several destinations, either external or other entities.
  • An exception to this general structure is an aggregator entity, which can combine two or more streams into a single stream and transmit this combined stream to a destination.
  • aspects of the present invention may be implemented as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware implementation, an entirely software implementation (including firmware, resident software, micro-code, etc.) or an implementation combining software and hardware aspects that may all generally be referred to herein as a "circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code emb odie d on a computer readable me dium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages, or declarative languages and domain-specific languages such as the Lua programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • FIG. 1 shows a schematic diagram of a two layer overlay network (100) on top of a host network, such as a TCP/UDP network, in accordance with one implementation.
  • a host network such as a TCP/UDP network
  • FIG. 1 shows a schematic diagram of a two layer overlay network (100) on top of a host network, such as a TCP/UDP network, in accordance with one implementation.
  • a host network such as a TCP/UDP network
  • the servers (106a-106f) can be either physical machines or software implementations of machines (i.e., a virtual machines), or a combination thereof.
  • the servers (106a-106f) are connected by means of a network, illustrated in FIG. 1 by interconnecting lines between the servers (106a- 106f), so that they can communicate with each other as needed.
  • the servers (106a- 106f) can be hosted either on data centers, co-location centers, computer facilities, server rooms, or in a so-called "cloud computing" environment.
  • Each server (106a-106f) can support one or more dynamically instantiated, maintained and destroyed factories (108a-108f).
  • a factory is a computer program that ordinarily runs as a background process in the hosting server.
  • the factories (108a-108f) can, as a result of receiving an appropriate instruction, create or destroy one or more dynamically instantiated entities (llOa-llOb) in the second layer (104).
  • Factories receive their instructions from dispatch controllers, which also act as nodes in the first overlay network.
  • Dispatch controllers are programmable devices that can execute scripts controlling one or more factories. There can be several dispatch controllers acting in concert to enhance scalability and elasticity.
  • the entities (110a- 110b) can forward and potentially modify streams of information to designated entities (llOa-llOb) in a network structure, illustrated by the two networks (112a- 112b) in the second layer (104), as will be described in further detail below.
  • a server such as server 106f, creates a factory (108f).
  • the factory (108f) gets paired with a dispatch controller and waits for further instructions.
  • a dispatch controller communicates with its factories under a master-slave arrangement with the dispatch controller as master. As the controller executes a script, it may direct a factory to create, delete or migrate entities.
  • the factory Upon receipt of the instruction, the factory (108f) creates a new entity (110a).
  • the factory spawns entity managers to handle groups of entities. These entity managers run either as stand-alone programs or threads within a factory. Entities are spawned by the entity managers and run as threads.
  • a factory communicates with the entity managers using a master-slave arrangement with the factory as master.
  • a factory can monitor the computational resources used by itself, by the entity managers, and by other programs sharing the same server. Entities communicate network conditions to the factory through the entity managers using event-based messaging.
  • a second-level nodal entity can be transferred to a new hosting factory during runtime. This is also referred to as migration.
  • migration occurs in response to factors such as network quality, latency and congestion, computational load, or detection of an imminent system failure. The operation also applies to an entity manager along with all its entities. Migration allows the end-user experience to remain nearly uninterrupted despite system-level changes
  • the factories (108a-108f) can also create additional redundant entities, which together form a network of entities that all serve the same data originating from a designated application endpoint. Having this redundancy can provide many benefits. For example, the latency over long distance network connections, such as trans-pacific communications, can be reduced, messages can be transformed into different quality levels, the load on the network can be balanced, transcoding of streaming data from one encoding to another can be done.
  • the factories (108a-108f) can form multiple independent networks in the second layer (104).
  • the second layer (104) can also be described as being composed of several disjoint networks (112a-112b), which each includes several networked entities (llOa-llOb).
  • an entity manager only runs entities instantiated for the same network in the second layer (104).
  • the factories (108a-108f) use a real time data-centric publish subscribe or similar system to provide highly efficient and inexpensive support for messaging, publish, subscribe, topic creation, topic destruction, topic modification, and other data driven support.
  • This data-centric communications is used to link a dispatch controller with the factories, a factory with the entity managers, and an entity manager with the entities.
  • the second layer (400) is use d for vide o communications, which often require bandwidths above approximately 300 kbps and latencies lower than approximately 300ms.
  • the entities (llOa-llOb) created by the factories (108a-108f) require these high-bandwidth and low-latency connections, and in certain applications some entities (108a-108f) might further require adequate computing power for video transcoding, video analytics, recording, and video scaling.
  • the entities (110a- 110b) are instantiated on demand, and the factories (108a-108f) have control over how many entities (llOa-llOb) are created and where they are created, depending among other things on factors such as network congestion, availability of computing resources, geographical locations of endpoint participants, and business considerations.
  • the duplication of additional factories (108a-108f) and subsequent on-demand creation of entities (llOa-llOb) by the factories (108a-108f) provides a highly scalable, elastic, fault tolerant, variable cost network that allows the connection and transformation of variable and high bandwidth streams according to business, quality or other goals.
  • each entity receives data streams from a single parent only.
  • the parent can be an application endpoint that initiated the need for an entity (llOa-llOb) or can be an entity (llOa-llOb) in a cascade of other entities (llOa-llOb) that eventually terminates at one or several final destinations.
  • Two-way communication can be achieved in some implementations by creating a similar, but disjoint network from the receiving application endpoint with a path to the originating application endpoint.
  • the entities (llOa-llOb) can be the vertices of a graph. Given a set N of nodal entities, the connections in the graph can be represented as a set L of links or edges, where a link or edge is a 2 -element subset of N specifying if a connection between a pair of nodes exists.
  • a link can be unidirectional, which states that communication travels along said link in only one direction. Conversely, a bi-directional link allows communication to travel in both directions.
  • the entities (llOa-llOb) implement a directed graph when all the links in the set L are unidirectional.
  • a desirable attribute in a communication network is to have messages originating from a source follow an acyclic path in its way to a destination. That is, the path must not contain cycles.
  • the entities (llOa-llOb) form a directed graph, where forward and reverse messages between two application endpoints follow different acyclic paths.
  • acyclic directed paths are guaranteed by construction.
  • the entities (llOa-llOb) are arranged in disjoint and independent graphs, and each graph is a unidirectional and simple graph describing a rooted tree with an originating source as root. It would be obvious for someone skilled in the art that this approach greatly simplifies the routing of messages from an originating source to any destination in the tree.
  • the entities can adapt their behavior, for example, based on link congestion, application requests, communication costs, communication failure, bandwidth availability, etc.
  • the adaptation can occur at various levels, such as at the level of an entity, path or topology.
  • a node can throttle both its demand for incoming data as well as its supply for outgoing data, regulating its behavior as a publisher and/or subscriber of data.
  • entities may route messages along different paths if redundant pathways exist.
  • factories can create, delete or move entities in order to change the overall characteristics of the network.
  • llOa-llOb can be connected into a network (112a-112b). Redundant entities (llOa-llOb) assure reliability of the stream and are managed by the factories (108a-108f) and dispatch controllers. The putative redundant entities (llOa-llOb) can also divide the stream for load balancing, or cost optimization and deliver the different streams either to a single final entity (llOa-llOb) for unification, or the final end point may sort out the streams as part of the decoding process.
  • the two-layer network (100) enables a scalable communication exchange for widely dispersed multi-channel media streams, ideal for crowd generated content and multi-way, real time interaction delivered either from a proprietary network of computers or as a cloud service.
  • the two-layer network (100) enables distributed learning with real time interaction of the remote students and distributed break out sessions of distributed groups of students. For example, first, there can be a massive "fan out" from the teacher to the students. Then the students can form groups with multi-way communication between the students in each group, which can be further supervised by the teacher, either simultaneously, or successively with changing the group of interest by the teacher. Then the two-layer network (100) can reconfigure back to a configuration in which the teacher broadcasts to her audience.
  • the two-layer network (100) enables real time video communication of actual or virtual video game play between different players, or the viewing of such game play by a third party for entertainment or pedagogical purposes.
  • the two-layer network (100) enables interoperability between otherwise incompatible video chat services.
  • chat services include Google Talk, Yahoo Messenger, Polycomm, or Cisco video conferencing.
  • Other types of transformations are also possible.
  • various implementations may include transformations that cause, for example, a video stream to be transformed to create cartoons, or avatars representing people.
  • Other transformations can include speech-to-text, or text-to-speech. Many further possibilities can be envisioned by those of ordinary skill in the art.
  • the two-layer network's entities can leverage scalable encodings such as that described in the Annex G extension of the H.264/MPEG-4 AVC video compression standard to deliver variable bandwidth streams, depending on the receiving application endpoint.
  • the level of bandwidth can be determined explicitly through configuration, or be determined by an entity (llOa-llOb) based on its algorithms.
  • the two-layer network (100) can enable real time bidirectional content delivery network type functionality by creating entities (110a- 110b) that are located geographically close to a demanding application endpoint and caching content on those entities (llOa-llOb).
  • the two-layer network (100) enables content addressable storage to enable the caching of exactly one copy that other application endpoints may access, for example, for movie editing or similar types of operations.

Abstract

Procédés, dispositif et système, comprenant des produits programmes informatiques, pour la mise en œuvre et l'utilisation de techniques qui permettent un réseau informatique superposé à deux niveaux, souple et évolutif. Un réseau hôte comprend un système d'ordinateurs interconnectés et peut supporter une ou plusieurs protocoles à couches de transport. Un premier réseau de recouvrement est créé sur le réseau hôte. Ce premier réseau de recouvrement comprend une ou plusieurs entités nodales de premier niveau. Au moins certaines des premières entités nodales de premier niveau fonctionnent comme des usines qui génèrent des entités nodales de second niveau dans un second réseau de recouvrement. En réponse à la réception d'une instruction, une ou plusieurs usines génèrent dynamiquement le second réseau de recouvrement. Ce second réseau de recouvrement comprend plusieurs entités nodales de second niveau en réseau qui peuvent supporter le traitement et la communication de données entre les entités nodales de second niveau.
PCT/EP2012/051870 2011-02-10 2012-02-03 Réseau superposé WO2012107360A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US13/025,128 2011-02-10
US13/025,128 US8688827B2 (en) 2011-02-10 2011-02-10 Overlay network
US13/071,710 2011-03-25
US13/071,710 US20120246295A1 (en) 2011-03-25 2011-03-25 Real Time Distribution of Layered Communication Using Publish-Subscribe Data-Centric Middleware

Publications (1)

Publication Number Publication Date
WO2012107360A1 true WO2012107360A1 (fr) 2012-08-16

Family

ID=45563043

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/EP2012/051870 WO2012107360A1 (fr) 2011-02-10 2012-02-03 Réseau superposé
PCT/EP2012/051874 WO2012107361A2 (fr) 2011-02-10 2012-02-03 Distribution en temps réel de communication en couches à l'aide d'un intergiciel centré sur les données de publication-abonnement

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/051874 WO2012107361A2 (fr) 2011-02-10 2012-02-03 Distribution en temps réel de communication en couches à l'aide d'un intergiciel centré sur les données de publication-abonnement

Country Status (1)

Country Link
WO (2) WO2012107360A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108804034A (zh) * 2018-05-22 2018-11-13 无锡辰云科技股份有限公司 一种基于读写分离的云终端处理方法及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022170214A1 (fr) * 2021-02-08 2022-08-11 Intel Corporation Gestion de congestion pour accès direct à la mémoire à distance (rdma) dans des réseaux cellulaires de prochaine génération

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008115221A2 (fr) * 2007-03-20 2008-09-25 Thomson Licensing Système de lecture en transit de poste à poste (p2p) organisé en grappes hiérarchiques

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008115221A2 (fr) * 2007-03-20 2008-09-25 Thomson Licensing Système de lecture en transit de poste à poste (p2p) organisé en grappes hiérarchiques

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PARDO-CASTELLOTE G: "OMG data-distribution service: architectural overview", MULTIMEDIA SIGNAL PROCESSING, 2002 IEEE WORKSHOP ON 9-11 DEC. 2002, PISCATAWAY, NJ, USA,IEEE, 19 May 2003 (2003-05-19), pages 200 - 206, XP010642373, ISBN: 978-0-7803-7713-4 *
SCHMIDT D C ET AL: "Addressing the challenges of mission-critical information management in next-generation net-centric pub/sub systems with OpenSplice DDS", PARALLEL AND DISTRIBUTED PROCESSING, 2008. IPDPS 2008. IEEE INTERNATIONAL SYMPOSIUM ON, IEEE, PISCATAWAY, NJ, USA, 14 April 2008 (2008-04-14), pages 1 - 8, XP031268539, ISBN: 978-1-4244-1693-6 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108804034A (zh) * 2018-05-22 2018-11-13 无锡辰云科技股份有限公司 一种基于读写分离的云终端处理方法及系统

Also Published As

Publication number Publication date
WO2012107361A2 (fr) 2012-08-16
WO2012107361A3 (fr) 2012-10-04

Similar Documents

Publication Publication Date Title
US8688827B2 (en) Overlay network
US11418440B2 (en) Routing virtual area based communications
US9565396B2 (en) Methods, systems and program products for initiating a process on data network
US9571793B2 (en) Methods, systems and program products for managing resource distribution among a plurality of server applications
US8655945B2 (en) Centralized rendering of collaborative content
EP2636199B1 (fr) Passerelle de signalisation, procédé, programme informatique et produit programme informatique pour une communication entre des protocoles http et sip
US20120246295A1 (en) Real Time Distribution of Layered Communication Using Publish-Subscribe Data-Centric Middleware
US8144632B1 (en) Methods, systems and program products for efficient communications during data sharing event
US9210200B1 (en) Methods, systems and program products for connecting users to operating nodes
US20150288926A1 (en) Framework to support a hybrid of meshed endpoints with non-meshed endpoints
Petrangeli et al. A scalable WebRTC-based framework for remote video collaboration applications
CN110650171B (zh) 一种视联网业务调度系统及方法
US20240106747A1 (en) Routing Virtual Area Based Communications
US11539919B1 (en) Dynamic cloud video composition
WO2012107360A1 (fr) Réseau superposé
Farahani et al. ALIVE: A Latency-and Cost-Aware Hybrid P2P-CDN Framework for Live Video Streaming
US11863592B2 (en) Active speaker tracking using a global naming scheme
Pal et al. Comparative analysis of new hybrid approach for overlay construction in P2P live streaming
Uma Maheswari et al. Reliability Enhanced Overlay Structure for Peer-to-Peer Video Streaming
Lombardo et al. A network-assisted platform for multipoint remote learning
Zhao Application-aware network design using software-defined networking for application performance optimization for big data and video streaming
Greenhalgh Understanding the network requirements of Collaborative Virtual Environments
Koren et al. OakStreaming: A Peer-to-Peer Video Streaming Library
Sakomaa Analysis of a web conferencing system: development and customisation
Xhagjika Resource, data and application management for cloud federations and multi-clouds

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: 12704026

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12704026

Country of ref document: EP

Kind code of ref document: A1