Patent Description:
The disclosure herein generally relates to live media distribution, and, more particularly, to a method and a system for managing multimedia exchange in tele-robotics using dew computing technique.

Tele-robotics are used in different business domains. An enterprise may employ same tele-robotics infrastructure in different functionalities and settings. Tele-robotics help businesses to work in a better way and helps in completing work faster. In a situation where physically meeting is challenging, tele-robotics help in bridging the gap. As an instance, tele-robotics plays a key role in a remote office setup. Tele-robotics help in improving business communication between employees, clients and stakeholders. The interaction between entities in business communication becomes easy with the help of tele-robotics. Tele-robots help remote workers to collaborate and work together in an easier and unprecedented way. It enables remote workers gain visual and audio access to those who are present in the room thereby helping in reducing communication gaps. Tele-robotics are used in a wide range of industries such as health care, education, retail and so.

Popular technologies being used in tele-robotics are cloud-robotics, edge-cloud hybrid systems and web browser based real time communication. Cloud robotics are popular because of computing and storage constraints. However, too much cloud centricity not only increases the overall latency in getting the decision outcome, but also adds a certain probability of uncertainty in performance. Further, to mitigate the uncertainties and latency due to cloud only systems, edge cloud hybrid systems are considered as the latency in communicating to an edge is significantly lower than the cloud. Additionally, the edge node has enough capacity so that significant amount of computation load due to cognitive decision making can be offloaded to the edge. Also, certain amount of data requiring frequent access may be cached in the edge as well. However, such edge based systems increases the capital expenditure for a system. Also, it adds to the operating expenditure for maintaining and managing the edge infrastructure.

Nowadays, web browser based real-time communication has been considered for both multi-media and command exchange over the Internet between an operator and a robot. Web Real-Time Communication (WebRTC)is designed as a peer-to-peer (P2P) communication protocol suit for exchange of multi-media between two endpoints across the internet. WebRTC Application Programming Interfaces (APIs) allow the end-applications to establish end-to-end (E2E) low latency channel over a P2P association of the robot with an operator. However, if any one or both robot and operator nodes are behind restrictive network address translators (NATs) then establishing a direct P2P is not possible. In such cases, the P2P connection must be relayed through a special server called Traversal Using Relays around NAT (TURN) server. Most tele-robotic solutions work in a P2P topology whereby only one operator connects the robot. But, for multiparty tele-robotic sessions, all the participating entities including the robot need to connect through a central conferencing server residing in the cloud. This effectively leads to multiple P2P connections converging into a star-like topology. The cloud-centric topology is bound to cause delay leading to unpredictable increase in latency while transferring control commands, as well as while exchanging the visual feedback. The delay in transferring commands cause problems during live media distribution/multimedia exchange happening in the telerobotic session. Document <CIT> discloses a method of controlling operation of a robot using a cluster of nodes in a network. The method includes receiving, using a gateway cloud driver, robot state information from the robot via the network, and converting, using the gateway cloud driver, the robot state information into at least one message. The method further includes transmitting, using a message broker, the at least one message to the cluster of nodes via the network. The method further includes processing, using the cluster of nodes in the network, the at least one message by parallel computing, and generating, using the cluster of nodes in the network, a robot command to control the operation of the robot (Abstract). Document <CIT> discloses about a method, a system and a storage medium for command interaction between a robot and a cloud platform, wherein the method comprises the following steps: the cloud platform starts a network server; the robot starts a network client; the robot client sends a network connection request to the cloud platform; the cloud platform carries out identity verification on the robot connection request, establishes network connection and caches the session to a storage system; a user issues a command to the robot through the cloud platform, and the cloud platform finds out network connection through the cached session; the cloud platform starts a timing task, and monitors whether a command identification code exists in the storage system to confirm the reply of the robot; the robot finishes executing the command and replies the command to the cloud platform; and the cloud platform receives the reply message of the robot, distributes service program processing through the route, analyzes the command identification code and the execution result, stores the command identification code and the execution result in a cache of the storage system, and completes command execution. The method and the system can effectively improve the reliability and timeliness of command interaction between the robot and the cloud platform (Abstract).

Embodiments of the present disclosure present technological improvements as solutions to one or more of the above-mentioned technical problems recognized by the inventors in conventional systems. The invention is defined in claim <NUM>-<NUM>.

As discussed earlier, popular technology that is available currently for facilitating exchange of multimedia between two endpoints across the Internet is WebRTC as it allows the end-application to establish end-to-end low latency channel over a P2P association of the robot with the operator. However, if any one or both robot and operator nodes are behind restrictive NATs, then establishing a direct P2P is not possible. And, in such cases, the P2P connection is relayed through a special server called TURN server. Currently, most of the telerobotic solutions that are working in a P2P topology allow only one operator to connect with the robot. So, in cases where multiple parties want to connect with the robot simultaneously, a central conferencing server residing in the cloud is used. The use of central conferencing server for forming multiparty connection further leads to multiple P2P connections that ultimately converge into a star-like topology. And that somehow breaks the true sense of P2P that one would like to leverage through WebRTC APIs as cloud-centric topology is bound to cause delay which further leads to unpredictable increase in latency while transferring control commands, as well as while exchanging the visual feedback.

Additionally, some available techniques use edge-cloud based hybrid architecture for a multi-user scenario. Basically, the edge-cloud based hybrid architecture uses a session manager and a media broadcaster in the cloud for facilitating multi-party connection. However, these techniques still have the cloud-centric signaling delay and uncertainty, and the delay in exchange of multimedia, which further reduces the synergy between the control commands transferred over low-latency P2P path and the visual feedback transferred via the cloud.

So, a technique that can efficiently manage multimedia aggregation and distribution while reducing cloud-centric overhead is still to be explored.

Embodiments of the present disclosure overcome the above-mentioned disadvantages by providing a system and a method for multimedia exchange in tele-robotics using dew computing. The system of the present disclosure first identifies a dew signaling server wherein a tele-presence robot device present in the enterprise network offers to act as the dew signaling server. The system then instantiates a dew interface at a public cloud server and establishes a first peer-to-peer (P2P) connection between the dew interface present at the public cloud server and the dew signaling server i.e., the tele-presence robot device. Thereafter, the system establishes a second P2P connection between the dew signaling server and a cloud media manager present in the public cloud server via the cloud signaling server. Once the second P2P connection is established, the system identifies a computing device present in an enterprise network as a dew media manager. The dew media manager information is then shared with the cloud signaling server via the dew signaling server.

Further, once the dew media manager is available, the system establishes a third P2P connection between the dew media manager and the cloud media manager via the cloud signaling server. A media management logic is then instantiated into the dew media manager via the cloud media manager using the third P2P connection. The dew media manager then performs multimedia exchange within one or more enterprise user devices connected to the enterprise network.

Additionally, the system also collects one or more media streams originating from the one or more enterprise user devices via the dew media manager which are then shared with the cloud media manager via the dew media manager. The cloud media manager then shares the media stream with non-enterprise user devices associated with non-enterprise users of the enterprise network.

In the present disclosure, the system and the method use the dew media manager which is part of the enterprise network to perform multimedia exchange within one or more enterprise user devices that are connected to the enterprise network, thereby ensuring improved quality of experience for enterprise users while reducing the cloud centric overhead as the device present within the enterprise network is handling the multimedia exchange. Further, the tele-presence robot device can be stopped urgently by the enterprise in case it is observed that the action of the tele-presence robot device is posing as a threat for the enterprise users.

<FIG> illustrates an exemplary representation of an environment <NUM> for managing multimedia exchange in tele-robotics using dew computing related to at least some example embodiments of the present disclosure. Although the environment <NUM> is presented in one arrangement, other embodiments may include the parts of the environment <NUM> (or other parts) arranged otherwise depending on, for example, establishment of peer-to-peer (P2P) connection, performing signaling negotiations, etc. The environment <NUM> generally includes a tele-presence robot device, such as a tele-presence robot device <NUM>, and a public cloud server <NUM>, each in communication with an enterprise network <NUM>. The public cloud server <NUM> is also in communication with a network <NUM>.

In an embodiment, the public cloud server <NUM> is a shared platform to deliver computing services, such as applications, virtual machines, storage etc. by third party service providers through the Internet. Examples of the public cloud server <NUM> include, but are not limited to, Amazon elastic compute cloud (EC2), Microsoft Azure™, IBM's™ blue cloud, sun cloud, and Google™ cloud.

In an embodiment, the enterprise network <NUM> refers to a network that is created to fulfill network needs, such as data exchange, and running business processes of a large organization.

The enterprise network <NUM> and the network <NUM> may include, without limitation, a light fidelity (Li-Fi) network, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a satellite network, the Internet, a fiber optic network, a coaxial cable network, an infrared (IR) network, a radio frequency (RF) network, a virtual network, and/or another suitable public and/or private network capable of supporting communication among two or more of the parts or users illustrated in <FIG>, or any combination thereof.

Various entities in the environment <NUM> may connect to the enterprise network <NUM> and the network <NUM> in accordance with various wired and wireless communication protocols, such as Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), 2nd Generation (<NUM>), 3rd Generation (<NUM>), 4th Generation (<NUM>), 5th Generation (<NUM>) communication protocols, Long Term Evolution (LTE) communication protocols, or any combination thereof.

The public cloud server <NUM> includes a cloud signaling server <NUM> and a cloud media manager <NUM>. The tele-presence robot device <NUM> sends a connection request to the public cloud server <NUM> via the enterprise network <NUM> and the cloud signaling server <NUM>. In an embodiment, the connection request includes an offer to act as a dew signaling server. The public cloud server <NUM>, upon receiving the connection request, instantiates a dew interface at the public cloud server <NUM> based on the connection request. Thereafter, the public cloud server <NUM> considers the tele-presence robot device <NUM> as the dew signaling server.

Further, any arbitrary node i.e., any computing device <NUM> that is joining the enterprise network <NUM> is considered as the dew media manager (herein after referred as the dew media manager <NUM>). The environment <NUM> also includes an enterprise user device <NUM> connected with the enterprise network <NUM>, and a non-enterprise user device <NUM> connected to the network <NUM>. It should be noted that one enterprise user device and one non-enterprise user device is shown for the sake of explanation; there can be more number of enterprise and non-enterprise user devices.

The enterprise user device <NUM> is associated with an enterprise user (e.g., an employee working for an entity such as an organization) who wants to establish a telerobotic session for performing multimedia exchange within the enterprise network <NUM>. The non-enterprise user device <NUM> is associated with a non-enterprise user (e.g., external stakeholders, such as clients, vendors, certification authorities, etc.) who wants to receive media streams that are shared within the enterprise network from outside the enterprise network. Examples of the enterprise user device <NUM> and the non-enterprise user device <NUM> include, but are not limited to, a personal computer (PC), a mobile phone, a tablet device, a Personal Digital Assistant (PDA), a server, a voice activated assistant, a smartphone, and a laptop.

The dew media manager <NUM> and the cloud media manager <NUM> help in performing the multi-media communication/exchange with the enterprise user devices, such as the enterprise user device <NUM> as well as the non-enterprise user devices, such as the non-enterprise user device <NUM>. The details of how the multimedia exchange is performed is discussed in detail with reference to <FIG> and <FIG>.

The number and arrangement of clouds, devices, and/or networks shown in <FIG> are provided as an example. There may be additional clouds, devices, and/or networks; fewer clouds, devices, and/or networks; different clouds, devices, and/or networks; and/or differently arranged clouds, devices, and/or networks than those shown in <FIG>. Furthermore, two or more devices shown in <FIG> may be implemented within a single device, or a single device shown in <FIG> may be implemented as multiple, distributed systems or devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of the environment <NUM> may perform one or more functions described as being performed by another set of systems or another set of devices of the environment <NUM> (e.g., refer scenarios described above).

<FIG> illustrates an exemplary block diagram of a system <NUM> managing multimedia exchange in tele-robotics using dew computing, in accordance with an embodiment of the present disclosure. In some embodiments, the system <NUM> is embodied as a cloud-based and/or software as a service (SaaS) based architecture. In some embodiments, the system <NUM> may be implemented in a server system. In some embodiments, the system <NUM> may be implemented in a variety of computing systems, such as laptop computers, notebooks, hand-held devices, workstations, mainframe computers, servers, a network cloud and the like.

In an embodiment, the system <NUM> includes a public cloud server <NUM> (also referred as public cloud server <NUM> in <FIG>), and tele-presence robot device <NUM> (also referred as the tele-presence robot device <NUM> in <FIG>) that is communicatively coupled to the public cloud server <NUM> via an enterprise network (also referred as the enterprise network <NUM> in <FIG>).

In at least one example embodiment, the public cloud server <NUM> includes a first set of processors <NUM>, a first set of communication interface device(s) or input/output (I/O) interface(s) <NUM>, and one or more data storage devices or first memory <NUM> operatively coupled to the first set of processors <NUM>.

In at least one example embodiment, the tele-presence robot device <NUM> includes a second set of processors <NUM>, a second set of communication interface device(s) or input/output (I/O) interface(s) <NUM>, and one or more data storage devices or a second memory <NUM> operatively coupled to the second set of processors <NUM>.

The first set of processors <NUM> and the second set of processors <NUM> may be one or more software processing modules and/or hardware processors. In an embodiment, the first set of processors <NUM> and the second set of processors <NUM> can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) is configured to fetch and execute computer-readable instructions stored in the memory.

The I/O interface device(s) <NUM> and <NUM> can include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like and can facilitate multiple communications within a wide variety of networks N/W and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. In an embodiment, the I/O interface device(s) can include one or more ports for connecting a number of devices to one another or to another server.

The memory <NUM> and the memory <NUM> may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. In an embodiment, a database <NUM> can be stored in the first memory <NUM> and a database <NUM> can be stored in the second memory <NUM>. The memories <NUM> and <NUM> further comprise (or may further comprise) information pertaining to input(s)/output(s) of each step performed by the systems and methods of the present disclosure. In other words, input(s) fed at each step and output(s) generated at each step are comprised in the memories <NUM> and <NUM> and can be utilized in further processing and analysis.

It is noted that the system <NUM> as illustrated and hereinafter described is merely illustrative of a system that could benefit from embodiments of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure. It is noted that the system <NUM> may include fewer or more components than those depicted in <FIG>.

<FIG>, with reference to <FIG>, illustrates a schematic block diagram representation <NUM> of a multimedia exchange managed by the system <NUM> of <FIG>, in accordance with an embodiment of the present disclosure.

As seen in <FIG>, the public cloud server <NUM> present in the system <NUM> first receives a connection request from the tele-presence robot device <NUM> via the cloud signaling server <NUM>. The connection request includes an offer to act as a dew signaling server. Based on the connection request, the system <NUM> instantiates a dew interface at the public cloud server <NUM> and then establishes a first peer-to-peer connection (P2P) between the dew interface and the dew signaling server i.e., the tele-presence robot device <NUM>. Then, using the first P2P connection, the system <NUM> establishes a second P2P connection between the dew signaling server and the cloud media manager <NUM> via the cloud signaling server <NUM>. Thereafter, the system <NUM> identifies a computing device (e.g., the computing device <NUM>) present in the enterprise network <NUM> as a dew media manager (hereinafter also referred as the dew media manager <NUM>). In an embodiment, the identification is performed based on a session joining request received by the tele-presence robot device <NUM> from the computing device <NUM> offering to act as the dew media manager <NUM>.

Once the dew media manager <NUM> is identified, the dew media manager information is shared with the cloud signaling server <NUM> via the dew signaling server. Thereafter, the system establishes a third P2P connection between the dew media manager <NUM> and the cloud media manager <NUM> via the cloud signaling server <NUM> based on the dew media manager information. Further, using the third P2P connection, the cloud media manager <NUM> transfers a script to the dew media manager <NUM> to instantiate a media management logic into the dew media manager <NUM>. Once the media management logic is instantiated in the dew media manager <NUM>, the dew media manager <NUM> performs multi-media exchange within one or more enterprise user devices, such as the enterprise user device <NUM> connected the enterprise network <NUM>.

Additionally, the public cloud server <NUM> present in the system <NUM> collects media streams originating from the one or more enterprise user devices via the dew media manager <NUM> and then sends the collected media streams to the cloud media manager <NUM>. The cloud media manager <NUM> then shares the media streams with the non-enterprise user devices, such as the non-enterprise user device <NUM>.

<FIG> and <FIG>, with reference to <FIG>, represent an exemplary flow diagram of a method <NUM> for managing multimedia exchange in tele-robotics using dew computing, in accordance with an embodiment of the present disclosure. The method <NUM> may use the system <NUM> of <FIG> for execution. In an embodiment, the system <NUM> comprises one or more data storage devices or the first memory <NUM> and the second memory <NUM> operatively coupled to the first set of processors <NUM> and the second set of processors <NUM>, respectively. The first memory <NUM> and the second memory <NUM> is configured to store first and second set of instructions, respectively for execution of steps of the method <NUM> by the first set and the second set of processors <NUM>/<NUM>. The sequence of steps of the flow diagram may not be necessarily executed in the same order as they are presented. Further, one or more steps may be grouped together and performed in form of a single step, or one step may have several sub-steps that may be performed in parallel or in sequential manner. The steps of the method of the present disclosure will now be explained with reference to the components of the system <NUM> as depicted in <FIG>.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> receives a connection request from the tele-presence robot device <NUM> via the cloud signaling server <NUM>. The connection request includes an offer to act as a dew signaling server. In particular, the connection request includes the offer to use available resources of the tele-presence robot device <NUM> to institute a dew service i.e., to use them for instituting the dew signaling server.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> instantiates a dew interface at the public cloud server <NUM> based on the received connection request. It should be noted that the dew interface at the public cloud server <NUM> is instantiated by the cloud media manager <NUM>.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> establishes a first peer-to-peer (P2P) connection between the dew interface and the dew signaling server <NUM>. In particular, the first P2P connection is established between the dew interface and the tele-presence robot device <NUM>.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> establishes a second P2P connection between the dew signaling server <NUM> and the cloud media manager <NUM> via the cloud signaling server <NUM> based on the first P2P connection.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> identifies a computing device (e.g., the computing device <NUM>) present in the enterprise network <NUM> as a dew media manager via the second hardware processor <NUM>. In particular, the identification is performed based on the session joining request send by the computing device <NUM> to the tele-presence robot device <NUM>. The session joining request includes an offer to act as the dew media manager. In particular, the session joining request includes the offer to use available resources of the computing device <NUM> for instituting the dew media manager.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> sends the dew media manager information to the cloud signaling server <NUM> via the dew signaling server <NUM>. In particular, which node among a plurality of nodes i.e., computing devices that are connected to the enterprise network <NUM> is identified as the dew media manager. So, the dew media manager information includes node details of the dew media manager.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> establishes a third P2P connection between the dew media manager and the cloud media manager <NUM> via the cloud signaling server <NUM> based on the dew media manager information. Once the dew media manager information is available, the third P2P connection is established between the node identifies as the dew media manager and the cloud media manager <NUM> via the cloud signaling server <NUM>. In particular, the cloud signaling server <NUM> notifies the cloud media manager <NUM> with a special dew media manager identifier for the third P2P connection.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> transfers a script to instantiate a media management logic into the dew media manager via the cloud media manager <NUM> using the third P2P connection. In an embodiment, the script is a software program that includes the media management logic.

At step <NUM> of the method of the present disclosure, the first set of processors <NUM> of the system <NUM> performs multimedia exchange within one or more enterprise user devices, such as the enterprise user device <NUM> connected to the enterprise network <NUM> via the dew media manager. It should be noted that the prior to performing the multimedia exchange within the one or more enterprise user devices, the second set of processors <NUM> is configured by the second set of instructions to redirect one or more connection requests received from the one or more enterprise user devices to the dew media manager via an enterprise proxy.

In an embodiment, the second set of processors <NUM> collects one or more media streams originating from the one or more enterprise user devices via the dew media manager. Once the media streams are collected, the second set of processors <NUM> sends the collected one or more media streams to the cloud media manager <NUM> via the dew media manager. The cloud media manager <NUM> then shares at least one media stream of the one or more media streams with at least one non-enterprise user device, such as the non-enterprise user device <NUM> of the one or more non-enterprise user devices associated with a non-enterprise user of the enterprise network <NUM>. In particular, the cloud media manager <NUM> performs the multimedia exchange with the one or more non-enterprise user devices.

Further, the first set of processors <NUM> collects the one or more media streams originating from the one or more non-enterprise user devices via the cloud media manager. The media streams include, but are not limited to, audio streams, video streams and so on. Thereafter, the collected one or more media streams are sent to the dew media manager via the cloud media manager. The dew media manager then shares the at least one media stream with at least one enterprise user device, such as the enterprise user device <NUM> associated with an enterprise user of the enterprise network <NUM>.

Additionally, when the script to instantiate the media management logic is transferred to the dew media manager via cloud media manager using the third P2P connection, the second set of processors <NUM> is configured by the second set of instructions to send a P2P disconnection request to the cloud signaling server <NUM> via the dew interface. The P2P disconnection request is sent by the dew signaling server <NUM> upon determining that the dew media manager is handling the multi-media exchange with the one or more enterprise user devices.

As discussed earlier, the available techniques are cloud-centric in which the cloud maintains the multiple P2P connection with the robot for performing video aggregation and distribution which increases the computational load of the robot/tele-presence robot device. So, to overcome the disadvantages, embodiments of the present disclosure provide a method and a system that use a cloud-dew architecture for an efficient live media distribution. The method considers a node/computing device within the enterprise network as a dew media manager for multimedia management and distribution. The tele-presence robot device acts as a dew signaling server and helps in establishing P2P connection of all nodes connecting from within the enterprise network with the dew media manager. All media streams from the enterprise network users are passed through the dew media manager. The dew media manager then receives media streams from outside enterprise network users from a cloud media manager inside the public cloud server. In a similar way, the public cloud also receives media streams from within enterprise network users and distributes to the outside enterprise network users. Thus, the method of the present disclosure helps in reducing a lot of cloud-centric overhead during multi-media conferencing in tele-robotics session.

Thus, the means can include both hardware means, and software means.

Claim 1:
A system (<NUM>), comprising:
a public cloud server (<NUM>) communicatively coupled to an enterprise network (<NUM>), wherein the public cloud server (<NUM>) comprising:
a first memory (<NUM>) configured to store a first set of instructions, and
a first set of processors (<NUM>) coupled to the first memory (<NUM>) via a first set of communication interfaces (<NUM>), wherein the first set of processors is serving as a cloud signaling server and a cloud media manager; and
a tele-presence robot device communicatively coupled to the public cloud server via the enterprise network, wherein the tele-presence robot device further comprising:
a second memory (<NUM>) configured to store a second set of instructions, and
a second set of processors (<NUM>) coupled to the second memory (<NUM>) via a second set of communication interfaces,
wherein the first set of processors (<NUM>) is configured by the first set of instructions to:
receive a connection request from the tele-presence robot device via the cloud signaling server, wherein the connection request comprises an offer to act as a signaling server;
instantiate a interface at the public cloud server based on the connection request;
establish a first peer-to-peer P2P connection between the interface and the signaling server;
establish a second P2P connection between the signaling server and the cloud media manager via the cloud signaling server based on the first P2P connection;
identify a computing device present in the enterprise network as a media manager via the second hardware processor, wherein the identification is performed based on a session joining request received by the tele-presence robot device, and wherein the telepresence robot receives the session joining request from the computing device offering to act as the media manager;
send media manager information to the cloud signaling server via the signaling server;
establish a third P2P connection between the media manager and the cloud media manager via the cloud signaling server based on the media manager information;
transfer a script to instantiate a media management logic into the media manager via the cloud media manager using the third P2P connection; and
perform multimedia exchange within one or more enterprise user devices connected to the enterprise network via the media manager.