WO2019132643A1 - A system and method for managing presentation sessions - Google Patents

A system and method for managing presentation sessions Download PDF

Info

Publication number
WO2019132643A1
WO2019132643A1 PCT/MY2018/050077 MY2018050077W WO2019132643A1 WO 2019132643 A1 WO2019132643 A1 WO 2019132643A1 MY 2018050077 W MY2018050077 W MY 2018050077W WO 2019132643 A1 WO2019132643 A1 WO 2019132643A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
receiver
presentation
layout
user interface
Prior art date
Application number
PCT/MY2018/050077
Other languages
French (fr)
Inventor
Muhammad Hilmi MOHD SHARIFF
Danial Naghshbandi
Gin Xian KOK
Khong Neng Choong
Original Assignee
Mimos Berhad
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mimos Berhad filed Critical Mimos Berhad
Publication of WO2019132643A1 publication Critical patent/WO2019132643A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission

Definitions

  • the present invention relates to a system and method for managing presentation sessions.
  • Typical media streaming service includes media presentation, whereby presentation content is shared everywhere in real time, ranging from large seminar hall, medium meeting room and small classroom size.
  • presentation content is shared everywhere in real time, ranging from large seminar hall, medium meeting room and small classroom size.
  • Each scenario requires a diverse control of media flows. For instance, in a seminar hall, a moderator manages a presentation session by determining which users will able to share their presentation content from a laptop or computer to a display in order to keep the entire session on schedule.
  • the system employs an integration module for integrating one or more portions of a first media signal and second media signal into an integrated media signal for presentation.
  • the system also includes a receiver module for receiving configuration parameters for dynamically adjusting integrated portions of the first and second media signals from the integrated media signal.
  • the plurality of media signals are presented via a plurality of media outputs based on the configuration parameters such as priority levels, location and layout of the media signal.
  • United States Patent No. 7143177 B1 discloses a system and method for synchronising a plurality of presentation content portions.
  • the system includes a time generator, a presentation controlling node, a presentation time determining component, a time delay determining component and a presentation synchronisation component for synchronising display of nonstreaming portion of the presentation with one streaming portion.
  • the system distributes a presentation synchronously to presentation members, whereby at least one content portion is delayed depending on performance characteristics of network transmission. It has always been a problem for a moderator to switch from a current presentation to a next presentation session when different content sources are projected to different projector screens simultaneously.
  • the existing systems do not provide flexibility to handle media flow, whereby the user interfaces are only designed to meet a specific purpose at a time. Furthermore, the existing systems have lacked scalability to cater different application setups and requirements. Hence, there is a need for a system and method for managing media flows of multiple presentation sessions to address the abovementioned drawbacks.
  • the present invention relates to a system and method for managing presentation sessions.
  • the system (100) comprising at least two nodes (10) that include at least one sender (11) and at least one receiver (12).
  • the at least one sender (11) is configured to capture, encode and transmit media content
  • the at least one receiver (12) is configured to receive, decode and display incoming media content from the at least one sender (11).
  • the system (100) further comprising a node agent (13), a session host (20), and a moderator console (30).
  • the node agent (13) that is connected to the at least two nodes (10) is configured to identify node capability of each node (10) by detecting if the node (10) is connected to a display device or input device.
  • the session host (20) is connected to the node agent (13) and is configured to manage node registration and relay control commands to the at least two nodes (10).
  • the moderator console (30) is connected to the session host (20) and is configured to host a user interface (32) to control presentation content flow.
  • the method for managing presentation sessions is characterised by the steps of identifying node capability of a plurality of nodes (10) by the node agent (13), relaying the node capability of the plurality of nodes (10) to a node manager (21), and setting up the presentation sessions by the moderator console (30).
  • the step of identifying node capability of the plurality of nodes (10) by the node agent (13) includes the sub-steps of determining if each node (10) has any external output display connection, computing a built-in display resolution if no external output display connection is detected to the node (10), determining if receiver mode is enabled in a configuration file if the built-in resolution is more than a predetermined value, enabling receiver capability on the node (10) if the receiver mode is enabled in the configuration file, and enabling sender capability on the node (10) if any input device connection is detected.
  • FIG. 1 illustrates a block diagram of a system (100) for managing a plurality of presentation sessions according to an embodiment of the present invention.
  • FIG. 2 illustrates a flowchart of a method for managing a plurality of presentation sessions according to an embodiment of the present invention.
  • FIG. 3 illustrates a flowchart of sub-steps for identifying each node capability as in step 2000 of the method of FIG. 2.
  • FIG. 4 illustrates a flowchart of sub-steps for setting up presentation session as in step 5000 of the method of FIG. 2.
  • FIG. 5a illustrates a flowchart of sub-steps for setting up presentation mode as in step
  • FIG. 5b illustrates an example of a queued mode layout in a user interface (32) of the system (100) of FIG. 1.
  • FIG. 5c illustrates an example of a normal mode layout in a user interface (32) of the system (100) of FIG. 1.
  • FIG. 6a illustrates a flowchart of sub-steps for setting up receiver (12) as in step 5600 of FIG. 4.
  • FIG. 6b illustrates an example of the queued mode layout on the user interface (32) having a sender indicator box.
  • FIG. 6c illustrates an example a normal mode with split layout on the user interface (32) of the system (100) of FIG. 1.
  • FIG. 6d illustrates an example of a standard layout for the normal mode on the user interface (32) having an anchor button.
  • FIG. 6e illustrates an example of linking receivers (12) using the anchor button.
  • FIG. 7 illustrates a flowchart of sub-steps for setting up sender in queued mode as in step 5800 of FIG. 4.
  • FIG. 8 illustrates a flowchart of sub-steps for setting up sender in normal mode as in step 5800 of FIG. 4.
  • FIG.1 illustrates a block diagram of a system (100) for managing a plurality of presentation sessions according to an embodiment of the present invention.
  • the system (100) controls media flow of the plurality of presentation sessions according to node associations.
  • the system (100) comprises a plurality of nodes (10) which include at least one sender (11) and at least one receiver (12) connected to a node agent (13), a session host (20), and a moderator console (30).
  • the node agent (13) is connected to the session host (20), whereas the session host (20) is further connected to the moderator console (30).
  • the sender (11) is configured to capture, encode and transmit media content, while the receiver (12) is configured to receive, decode and display incoming media content from at least one sender (11).
  • the node agent (13) is configured to identify node capability which is to identify if a node (10) is a sender (11), a receiver (12) or a combination of both by detecting if the node (10) is connected to a display device or input device.
  • the node (10) is considered a sender (11) if it is connected to the display device, whereas the node (10) is considered a receiver (12) if it is connected to the input device which may include a mouse or a keyboard.
  • the session host (20) that is configured to manage node registration and relay control commands to the plurality of nodes (10) comprises a node manager (21), a node registry (22) and a moderator host (23).
  • the node manager (21) is configured to receive registration information of a node (10) from the node agent (13) and relay commands received from the presentation manager (31) to the plurality of nodes (10).
  • the node registry (22) that is connected to the node manager (21) is configured to store node information and node capability from the node manager (21).
  • the moderator host (23) is connected to the node registry (22) and presentation manager (31).
  • the moderator host (23) is configured to extract and aggregate the node information from the node registry (22) and provide the information to the presentation manager (31).
  • the moderator console (30) is configured to host a user interface (32) that enables a dynamic set-up or configuration of presentation and control presentation content flow.
  • the moderator console (30) comprises a presentation manager (31), the user interface (32), and a configuration matrix (33).
  • the presentation manager (31) is configured to host the user interface (32) and relay commands to run the presentation session.
  • the user interface (32) is configured to display a graphical interface to a user for notification, set up nodes and collect commands for presentation.
  • the configuration matrix (33) is configured to store configuration of the presentation that includes presentation mode, presentation layout and node associations.
  • the presentation mode may include a queued mode and a normal mode.
  • the queued mode allows a moderator to queue a list of senders (11) for a particular receiver (12) in whatever order the moderator feels necessary. Additionally, the moderator may control the presentation flow during an ongoing presentation through the user interface (32).
  • the presentation layout is the screen setting which may include a split layout or a standard layout displayed on the user interface (32).
  • the split layout is used when display content comes from multiple sources concurrently, while the standard layout is used when the display content only comes from one source at a time.
  • only standard layout is displayed for the queued mode, while for the normal mode, the moderator may suitably choose between standard layout or split layout.
  • the moderator may conduct specific requirements for a presentation which may include one-to-one, one-to-many, many-to- one, and many one-to-one presentation sessions.
  • a one-to-one presentation session refers to a presentation session having one sender and one receiver.
  • a one-to-many presentation session refers to a presentation session having one sender and many receivers.
  • a many-to-one presentation session refers to a presentation session having many senders and one receiver, while a many one-to-one presentation session refers to a presentation session having multiple sender-receiver pairs.
  • FIG. 2 illustrates a flowchart of a method for managing a plurality of presentation sessions according to an embodiment of the present invention.
  • the node agent (13) identifies node capability of the plurality of nodes (10) as in step 2000.
  • the node agent (13) identifies if each node (10) is a sender (11), a receiver (12) or a combination of both by detecting if the node (10) is connected to a display device or input device.
  • the node agent (13) registers the plurality of nodes (10) and relays the node capability of the plurality of nodes (10) to the node manager (21) as in steps 3000 and 4000.
  • the moderator console (30) sets up the presentation session as in step 5000.
  • FIG. 3 illustrates a flowchart of sub-steps for identifying each node capability as in step 2000 of the method of FIG. 2.
  • the node agent (13) determines if the node (10) has connection with any external output display as in decision 2004.
  • the node agent (13) directly enables receiver capability on the node (10) as in step 2010 if any external output display connection to the node (10) is detected.
  • the node agent (13) thereafter determines if the node (10) has connection with any input device as in decision 2012.
  • the node agent (13) further computes a built-in display resolution of the node (10). If the built-in display resolution is more than a predetermined value as in decision 2006, the node agent (13) determines if a receiver mode is enabled in a configuration file as in decision 2008. A receiver mode refers to the capability of the node (10) to receive and display content from a sender (11). If the receiver mode is enabled in the configuration file, the node agent (13) enables the receiver capability on the node (10) as in step 2010. The node agent (13) thereafter determines if the node (10) has connection with any input device as in decision 2012.
  • the node agent (13) directly determines if the node (10) has connection with any input device as in decision 2012.
  • the node agent (13) enables sender capability on the node (10) as in step 2014 only if any input device connection is detected.
  • FIG. 4 illustrates a flowchart of sub-steps for setting up presentation session by the moderator console (30) as in step 5000 of the method of FIG. 2.
  • the presentation manager (31) generates the user interface (32) as in step 5200.
  • the presentation mode which can either be a normal mode or a queued mode is then set up through the user interface (32) as in step 5400.
  • the step of setting up the presentation mode through the user interface (32) is further explained in relation to FIG. 5a.
  • the plurality of receivers (12) are set up through the user interface (32) as in step 5600.
  • the step of setting up the plurality of receivers (12) is further explained in relation to FIG. 6a.
  • the plurality of senders (11) are set up through the user interface (32) according to the presentation mode as in step 5800.
  • the step of setting up the plurality of senders (11) in a normal mode is further explained in relation to FIG. 7, whereas the step of setting up the plurality of senders (11) in a queued mode is further explained in relation to FIG. 8.
  • FIG. 5a it illustrates a flowchart of the sub-steps for setting up presentation mode as in step 5400 of FIG. 4.
  • a presentation mode is selected based on available mode displayed in a dropdown menu in a configuration page of the user interface (32) as in decision 5422.
  • the presentation mode displayed on the dropdown menu may include a queued mode and a normal mode.
  • the user interface (32) is set up as a queued mode layout as in step 5424.
  • a control panel is also displayed in the user interface (32) to control presentation content flow as in step 5426, wherein the control panel may include but not limited to play, stop, next, and back buttons.
  • the user interface (32) is set up as a normal mode layout as in step 5430.
  • FIGS. 5b and 5c show the queued mode layout and normal mode layout of the configuration page of the user interface (32) according to an embodiment of the present invention.
  • the configuration page comprises a main area, a node list on top of the main area, and the dropdown menu on the top right of the configuration page.
  • An example of a control panel having play, back, and next buttons is shown in the queued mode layout in FIG. 5b.
  • FIG. 6a illustrates a flowchart of sub-steps for setting up receiver (12) as in step 5600 of FIG. 4.
  • a node (10) is transferred from the node list towards the main area on the configuration page of the user interface (32) as in step 5602.
  • the presentation manager (31) checks the node capability of the node (10) with the node registry (22) by determining if the node (10) is a receiver (12) as in decision 5606. If the node (10) is not a receiver (12), the node (10) is returned to the node list as in step 5609.
  • the presentation manager (31) further determines if the node (10) has been added as a receiver (12) previously as in decision 5608. This is to ensure that the node (10) is not added as a receiver (12) more than once. If the node (10) has already been added as a receiver (12), the node (10) is returned to the node list as in step 5609. On the other hand, if the node (10) has yet to be added, the node (10) is then added as a receiver (12) in the user interface (32) with the node capability is stored in the node registry (22) as in step 5610. Next, the moderator host (23) determines the selected presentation mode as in decision 5612.
  • the presentation manager (31) updates the user interface (32) to a queued mode layout by creating a receiver layout for each added receiver (12) as in step 5614, wherein the receiver layout comprises slots to be filled with chosen nodes (10) having sender capability.
  • the slots in the receiver layout for the queued mode are configured to determine the sequence of content to be displayed on the receiver (12).
  • the user interface (32) is further updated by the presentation manager (31) by including a sender indicator boxthat is configured to indicate the senders (12) of an ongoing presentation session as in step 5618.
  • FIG. 6b shows an example of the queued mode layout.
  • three nodes (10) from the node list are added as receivers (12) in the main area of the user interface (32) which are Node 15, Node 13, and Node 14.
  • Each added receiver (12) in the main area of the user interface (32) comprises a receiver layout with slots indicating the sequence of content to be displayed on the respective receiver (12). For example, for receiver 1 which is Node 15, three slots are filled with Node 2, Node 4, and Node 13 at first slot, second slot and fourth slot respectively. This indicates that the content of Node 2, Node 4 and Node 13 is displayed during first, second, and fourth presentation sessions respectively.
  • the queued layout includes a sender indicator box that indicates the senders (11) of the ongoing presentation session.
  • the ongoing presentation for this example is the second presentation session, whereby the senders (11) for the second presentation session are indicated from the second slot of each receiver (12) which are Node 4 and Node 5.
  • the content of Node 4 and Node 5 is displayed in Node 15 and Node 13 respectively.
  • the queued mode layout is preferably used for the many one-to-one presentation session.
  • the configuration of the presentation is updated by the configuration matrix (33) as in step 5636.
  • the moderator host (23) further determines if a split or standard layout is selected for the receiver (12) as in decision 5622.
  • split layout is selected, the layout on the user interface (32) is updated accordingly as in step 5634.
  • the split layout may include but not limited to 4 split screens, 2 vertically split screens, and 2 horizontally split screens, whereby these types of split layout are preferably used for many-to-one presentation session.
  • FIG. 6c shows an example of the normal mode with split layout on the user interface (32).
  • two nodes (10) from the node list in the user interface (32) are added as receivers (12) which are Node 1 and Node 5.
  • Each added receiver (12) in the main area of the user interface (32) comprises a split receiver layout with slots for nodes with sender capability indicating the content to be displayed simultaneously.
  • receiver 1 which is Node 1
  • the receiver layout is split into four slots, wherein three slots are filled with Node 2, Node 12, and Node 1 1 .
  • the content of Node 2, Node 12 and Node 1 1 is displayed simultaneously on Node 1 .
  • the configuration of the presentation is updated by the configuration matrix (33) as in step 5636.
  • the layout on the user interface (32) is updated accordingly as in step 5628.
  • the standard layout for the normal mode is preferably used for one-to-one and one-to-many presentation sessions, whereby the presentation sessions have one sender.
  • the standard layout further comprises an anchor button on each added receiver (12) in the user interface (32) to connect the receivers (12).
  • FIG. 6d shows an example of the standard layout having an anchor button.
  • two nodes (10) from the node list are added as receivers (12) in the main area of the user interface (32) which are Node 1 and Node 3.
  • Each added receiver (12) in the main area of the user interface (32) comprises a receiver layout with slots indicating the content of senders (11) to be displayed on the respective receiver (12).
  • the content of Node 2 is displayed on Node 1 and the content of Node 4 is displayed on Node 3 simultaneously.
  • the content of Node 5 is only displayed on Node 3 once Node 5 is selected by the user.
  • the anchor buttons in the user interface (32) are not linked and hence the added receivers (12) are not connected to each other.
  • the standard layout shown in FIG. 6d is preferably used for one-to-one presentation session.
  • the receivers (12) must be connected to each other as in step 5632.
  • the receivers (12) are linked through the anchor buttons in the user interface (32) and the configuration of the presentation is finally updated by the configuration matrix (33) as in step 5636.
  • An example of the receivers (12) linked through the anchor button is shown in FIG. 6e.
  • FIG. 7 illustrates the flowchart of sub-steps for setting up a sender (11) in queued mode as in step 5800 of FIG. 4.
  • the node (10) is considered as a sender (11)
  • the node (10) is added as a sender (12) for the receiver (12) as in step 5810 before the configuration of the presentation is updated by the configuration matrix (33) as in step 5812.
  • FIG. 6b shows an example of the queued mode layout.
  • three nodes (10) are added as senders (11) for receiver 1 .
  • the three nodes are Node 2, Node 4, and Node 13, whereby these nodes display the content during first, second, and fourth presentation sessions respectively.
  • FIG. 8 illustrates a flowchart of sub-steps for setting up sender (11) in normal mode as in step 5800 of FIG. 4.
  • the moderator host (23) transfers a node (10) from the node list towards an empty slot inside a receiver layout in the user interface (32) as in step 5820.
  • the presentation manager (31) checks the node capability with the node registry (22) by determining if the node (10) is a sender (11) as in decision 5824. If the node (10) is not a sender (11), the node (10) is returned to the node list as in step 5826. However, if the node (10) is considered a sender (11), the presentation manager (31) determines if a standard layout or a split layout is chosen as in decision 5828.
  • the presentation manager (31) further determines if all slots in the receiver layout are filled as in decision 5830. If all slots in the receiver layout are filled, the node (10) is returned to the node list as in step 5826. However, if there is still an empty slot inside the receiver layout, the node (10) is added as a sender (11) by the presentation manager (31) as in step 5832.
  • FIG. 6c which illustrates an example of the normal mode with split layout on the user interface (32)
  • the presentation manager (31) may still add one sender (11) to Node 1 and Node 5.
  • content from different senders (11) are displayed simultaneously by each receiver (12). Therefore, as shown in FIG. 6c, the content of Node 2, Node 12 and Node 1 1 are displayed simultaneously on Node 1 .
  • the node is directly added as a sender (11) by the presentation manager (31) as in step 5832.
  • the configuration of the presentation is updated by the configuration matrix (33) as in step 5834.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)

Abstract

The present invention relates to a system and method for managing a plurality of presentation sessions. The system (100) comprises a plurality of nodes (10) which include at least one sender (11) and at least one receiver (12) connected to a node agent (13), a session host (20), and a moderator console (30). The node agent (13) is connected to the session host (20), whereas the session host (20) is further connected o the moderator console (30). The method includes the steps of identifying node capability of the plurality of nodes (10) by the node agent (13), relaying the node capability of the plurality of nodes (10) to a node manager (21), and setting up the presentation sessions by the moderator console (30).

Description

A SYSTEM AND METHOD FOR MANAGING PRESENTATION SESSIONS
FIELD OF INVENTION
The present invention relates to a system and method for managing presentation sessions.
BACKGROUND OF THE INVENTION
Typical media streaming service includes media presentation, whereby presentation content is shared everywhere in real time, ranging from large seminar hall, medium meeting room and small classroom size. Each scenario requires a diverse control of media flows. For instance, in a seminar hall, a moderator manages a presentation session by determining which users will able to share their presentation content from a laptop or computer to a display in order to keep the entire session on schedule.
An example of a system and method for managing multiple presentation sessions is disclosed in United States Patent No. 9230513 B2. The system employs an integration module for integrating one or more portions of a first media signal and second media signal into an integrated media signal for presentation. The system also includes a receiver module for receiving configuration parameters for dynamically adjusting integrated portions of the first and second media signals from the integrated media signal. The plurality of media signals are presented via a plurality of media outputs based on the configuration parameters such as priority levels, location and layout of the media signal.
In another example, United States Patent No. 7143177 B1 discloses a system and method for synchronising a plurality of presentation content portions. The system includes a time generator, a presentation controlling node, a presentation time determining component, a time delay determining component and a presentation synchronisation component for synchronising display of nonstreaming portion of the presentation with one streaming portion. The system distributes a presentation synchronously to presentation members, whereby at least one content portion is delayed depending on performance characteristics of network transmission. It has always been a problem for a moderator to switch from a current presentation to a next presentation session when different content sources are projected to different projector screens simultaneously. The existing systems do not provide flexibility to handle media flow, whereby the user interfaces are only designed to meet a specific purpose at a time. Furthermore, the existing systems have lacked scalability to cater different application setups and requirements. Hence, there is a need for a system and method for managing media flows of multiple presentation sessions to address the abovementioned drawbacks.
SUMMARY OF INVENTION
The present invention relates to a system and method for managing presentation sessions. The system (100) comprising at least two nodes (10) that include at least one sender (11) and at least one receiver (12). The at least one sender (11) is configured to capture, encode and transmit media content, whereas the at least one receiver (12) is configured to receive, decode and display incoming media content from the at least one sender (11). In addition, the system (100) further comprising a node agent (13), a session host (20), and a moderator console (30).
The node agent (13) that is connected to the at least two nodes (10) is configured to identify node capability of each node (10) by detecting if the node (10) is connected to a display device or input device. The session host (20) is connected to the node agent (13) and is configured to manage node registration and relay control commands to the at least two nodes (10). The moderator console (30) is connected to the session host (20) and is configured to host a user interface (32) to control presentation content flow.
The method for managing presentation sessions is characterised by the steps of identifying node capability of a plurality of nodes (10) by the node agent (13), relaying the node capability of the plurality of nodes (10) to a node manager (21), and setting up the presentation sessions by the moderator console (30).
The step of identifying node capability of the plurality of nodes (10) by the node agent (13) includes the sub-steps of determining if each node (10) has any external output display connection, computing a built-in display resolution if no external output display connection is detected to the node (10), determining if receiver mode is enabled in a configuration file if the built-in resolution is more than a predetermined value, enabling receiver capability on the node (10) if the receiver mode is enabled in the configuration file, and enabling sender capability on the node (10) if any input device connection is detected.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.
FIG. 1 illustrates a block diagram of a system (100) for managing a plurality of presentation sessions according to an embodiment of the present invention.
FIG. 2 illustrates a flowchart of a method for managing a plurality of presentation sessions according to an embodiment of the present invention.
FIG. 3 illustrates a flowchart of sub-steps for identifying each node capability as in step 2000 of the method of FIG. 2.
FIG. 4 illustrates a flowchart of sub-steps for setting up presentation session as in step 5000 of the method of FIG. 2.
FIG. 5a illustrates a flowchart of sub-steps for setting up presentation mode as in step
5400 of FIG. 4.
FIG. 5b illustrates an example of a queued mode layout in a user interface (32) of the system (100) of FIG. 1.
FIG. 5c illustrates an example of a normal mode layout in a user interface (32) of the system (100) of FIG. 1.
FIG. 6a illustrates a flowchart of sub-steps for setting up receiver (12) as in step 5600 of FIG. 4. FIG. 6b illustrates an example of the queued mode layout on the user interface (32) having a sender indicator box.
FIG. 6c illustrates an example a normal mode with split layout on the user interface (32) of the system (100) of FIG. 1.
FIG. 6d illustrates an example of a standard layout for the normal mode on the user interface (32) having an anchor button.
FIG. 6e illustrates an example of linking receivers (12) using the anchor button.
FIG. 7 illustrates a flowchart of sub-steps for setting up sender in queued mode as in step 5800 of FIG. 4.
FIG. 8 illustrates a flowchart of sub-steps for setting up sender in normal mode as in step 5800 of FIG. 4.
DESCRIPTION OF THE PREFERRED EMBODIMENT
A preferred embodiment of the present invention will be described herein below with reference to the accompanying drawings. In the following description, well known functions or constructions are not described in detail since they would obscure the description with unnecessary detail.
Reference is made initially to FIG.1 which illustrates a block diagram of a system (100) for managing a plurality of presentation sessions according to an embodiment of the present invention. Generally, the system (100) controls media flow of the plurality of presentation sessions according to node associations. The system (100) comprises a plurality of nodes (10) which include at least one sender (11) and at least one receiver (12) connected to a node agent (13), a session host (20), and a moderator console (30). The node agent (13) is connected to the session host (20), whereas the session host (20) is further connected to the moderator console (30).
The sender (11) is configured to capture, encode and transmit media content, while the receiver (12) is configured to receive, decode and display incoming media content from at least one sender (11). The node agent (13) is configured to identify node capability which is to identify if a node (10) is a sender (11), a receiver (12) or a combination of both by detecting if the node (10) is connected to a display device or input device. The node (10) is considered a sender (11) if it is connected to the display device, whereas the node (10) is considered a receiver (12) if it is connected to the input device which may include a mouse or a keyboard.
The session host (20) that is configured to manage node registration and relay control commands to the plurality of nodes (10) comprises a node manager (21), a node registry (22) and a moderator host (23). The node manager (21) is configured to receive registration information of a node (10) from the node agent (13) and relay commands received from the presentation manager (31) to the plurality of nodes (10). The node registry (22) that is connected to the node manager (21) is configured to store node information and node capability from the node manager (21). The moderator host (23) is connected to the node registry (22) and presentation manager (31). The moderator host (23) is configured to extract and aggregate the node information from the node registry (22) and provide the information to the presentation manager (31).
The moderator console (30) is configured to host a user interface (32) that enables a dynamic set-up or configuration of presentation and control presentation content flow. The moderator console (30) comprises a presentation manager (31), the user interface (32), and a configuration matrix (33). The presentation manager (31) is configured to host the user interface (32) and relay commands to run the presentation session. The user interface (32) is configured to display a graphical interface to a user for notification, set up nodes and collect commands for presentation. The configuration matrix (33) is configured to store configuration of the presentation that includes presentation mode, presentation layout and node associations.
The presentation mode may include a queued mode and a normal mode. The queued mode allows a moderator to queue a list of senders (11) for a particular receiver (12) in whatever order the moderator feels necessary. Additionally, the moderator may control the presentation flow during an ongoing presentation through the user interface (32).
The presentation layout is the screen setting which may include a split layout or a standard layout displayed on the user interface (32). The split layout is used when display content comes from multiple sources concurrently, while the standard layout is used when the display content only comes from one source at a time. Preferably, only standard layout is displayed for the queued mode, while for the normal mode, the moderator may suitably choose between standard layout or split layout. By choosing the presentation mode and presentation layout, the moderator may conduct specific requirements for a presentation which may include one-to-one, one-to-many, many-to- one, and many one-to-one presentation sessions.
A one-to-one presentation session refers to a presentation session having one sender and one receiver. A one-to-many presentation session refers to a presentation session having one sender and many receivers. A many-to-one presentation session refers to a presentation session having many senders and one receiver, while a many one-to-one presentation session refers to a presentation session having multiple sender-receiver pairs.
FIG. 2 illustrates a flowchart of a method for managing a plurality of presentation sessions according to an embodiment of the present invention. Initially, the node agent (13) identifies node capability of the plurality of nodes (10) as in step 2000. The node agent (13) identifies if each node (10) is a sender (11), a receiver (12) or a combination of both by detecting if the node (10) is connected to a display device or input device. The node agent (13) then registers the plurality of nodes (10) and relays the node capability of the plurality of nodes (10) to the node manager (21) as in steps 3000 and 4000. Finally, the moderator console (30) sets up the presentation session as in step 5000.
FIG. 3 illustrates a flowchart of sub-steps for identifying each node capability as in step 2000 of the method of FIG. 2. Initially, the node agent (13) determines if the node (10) has connection with any external output display as in decision 2004. The node agent (13) directly enables receiver capability on the node (10) as in step 2010 if any external output display connection to the node (10) is detected. The node agent (13) thereafter determines if the node (10) has connection with any input device as in decision 2012.
However, if no external output display connection is detected as in decision 2004, the node agent (13) further computes a built-in display resolution of the node (10). If the built-in display resolution is more than a predetermined value as in decision 2006, the node agent (13) determines if a receiver mode is enabled in a configuration file as in decision 2008. A receiver mode refers to the capability of the node (10) to receive and display content from a sender (11). If the receiver mode is enabled in the configuration file, the node agent (13) enables the receiver capability on the node (10) as in step 2010. The node agent (13) thereafter determines if the node (10) has connection with any input device as in decision 2012.
On the other hand, if the resolution is less than the predetermined value as in decision 2006, or if the receiver mode is not enabled in the configuration file as in decision 2008, the node agent (13) directly determines if the node (10) has connection with any input device as in decision 2012.
The node agent (13) enables sender capability on the node (10) as in step 2014 only if any input device connection is detected.
FIG. 4 illustrates a flowchart of sub-steps for setting up presentation session by the moderator console (30) as in step 5000 of the method of FIG. 2. Initially, the presentation manager (31) generates the user interface (32) as in step 5200. The presentation mode which can either be a normal mode or a queued mode is then set up through the user interface (32) as in step 5400. The step of setting up the presentation mode through the user interface (32) is further explained in relation to FIG. 5a.
Thereon, the plurality of receivers (12) are set up through the user interface (32) as in step 5600. The step of setting up the plurality of receivers (12) is further explained in relation to FIG. 6a. Finally, the plurality of senders (11) are set up through the user interface (32) according to the presentation mode as in step 5800. The step of setting up the plurality of senders (11) in a normal mode is further explained in relation to FIG. 7, whereas the step of setting up the plurality of senders (11) in a queued mode is further explained in relation to FIG. 8.
Referring now to FIG. 5a, it illustrates a flowchart of the sub-steps for setting up presentation mode as in step 5400 of FIG. 4. Initially, a presentation mode is selected based on available mode displayed in a dropdown menu in a configuration page of the user interface (32) as in decision 5422. The presentation mode displayed on the dropdown menu may include a queued mode and a normal mode.
If queued mode is selected as in decision 5422, the user interface (32) is set up as a queued mode layout as in step 5424. A control panel is also displayed in the user interface (32) to control presentation content flow as in step 5426, wherein the control panel may include but not limited to play, stop, next, and back buttons. However, if normal mode is selected as in decision 5422, the user interface (32) is set up as a normal mode layout as in step 5430.
FIGS. 5b and 5c show the queued mode layout and normal mode layout of the configuration page of the user interface (32) according to an embodiment of the present invention. As shown in FIGS. 5b and 5c, the configuration page comprises a main area, a node list on top of the main area, and the dropdown menu on the top right of the configuration page. An example of a control panel having play, back, and next buttons is shown in the queued mode layout in FIG. 5b.
FIG. 6a illustrates a flowchart of sub-steps for setting up receiver (12) as in step 5600 of FIG. 4. Initially, a node (10) is transferred from the node list towards the main area on the configuration page of the user interface (32) as in step 5602. The presentation manager (31) then checks the node capability of the node (10) with the node registry (22) by determining if the node (10) is a receiver (12) as in decision 5606. If the node (10) is not a receiver (12), the node (10) is returned to the node list as in step 5609.
However, if the node (10) is considered as a receiver (12), the presentation manager (31) further determines if the node (10) has been added as a receiver (12) previously as in decision 5608. This is to ensure that the node (10) is not added as a receiver (12) more than once. If the node (10) has already been added as a receiver (12), the node (10) is returned to the node list as in step 5609. On the other hand, if the node (10) has yet to be added, the node (10) is then added as a receiver (12) in the user interface (32) with the node capability is stored in the node registry (22) as in step 5610. Next, the moderator host (23) determines the selected presentation mode as in decision 5612. If queued mode is selected, the presentation manager (31) updates the user interface (32) to a queued mode layout by creating a receiver layout for each added receiver (12) as in step 5614, wherein the receiver layout comprises slots to be filled with chosen nodes (10) having sender capability. The slots in the receiver layout for the queued mode are configured to determine the sequence of content to be displayed on the receiver (12). Furthermore, the user interface (32) is further updated by the presentation manager (31) by including a sender indicator boxthat is configured to indicate the senders (12) of an ongoing presentation session as in step 5618.
FIG. 6b shows an example of the queued mode layout. In this example, three nodes (10) from the node list are added as receivers (12) in the main area of the user interface (32) which are Node 15, Node 13, and Node 14. Each added receiver (12) in the main area of the user interface (32) comprises a receiver layout with slots indicating the sequence of content to be displayed on the respective receiver (12). For example, for receiver 1 which is Node 15, three slots are filled with Node 2, Node 4, and Node 13 at first slot, second slot and fourth slot respectively. This indicates that the content of Node 2, Node 4 and Node 13 is displayed during first, second, and fourth presentation sessions respectively.
Additionally, the queued layout includes a sender indicator box that indicates the senders (11) of the ongoing presentation session. The ongoing presentation for this example is the second presentation session, whereby the senders (11) for the second presentation session are indicated from the second slot of each receiver (12) which are Node 4 and Node 5. The content of Node 4 and Node 5 is displayed in Node 15 and Node 13 respectively. As the second slot of receiver 3 which is Node 14 is empty, no content is displayed on Node 14 during the second presentation session.
The queued mode layout is preferably used for the many one-to-one presentation session.
Finally, the configuration of the presentation is updated by the configuration matrix (33) as in step 5636. On the other hand, if normal mode is selected as in decision 5612, the moderator host (23) further determines if a split or standard layout is selected for the receiver (12) as in decision 5622.
If split layout is selected, the layout on the user interface (32) is updated accordingly as in step 5634. The split layout may include but not limited to 4 split screens, 2 vertically split screens, and 2 horizontally split screens, whereby these types of split layout are preferably used for many-to-one presentation session. FIG. 6c shows an example of the normal mode with split layout on the user interface (32). In this example, two nodes (10) from the node list in the user interface (32) are added as receivers (12) which are Node 1 and Node 5. Each added receiver (12) in the main area of the user interface (32) comprises a split receiver layout with slots for nodes with sender capability indicating the content to be displayed simultaneously. For example, for receiver 1 which is Node 1 , the receiver layout is split into four slots, wherein three slots are filled with Node 2, Node 12, and Node 1 1 . The content of Node 2, Node 12 and Node 1 1 is displayed simultaneously on Node 1 .
Once the user interface (32) is updated with the split layout, the configuration of the presentation is updated by the configuration matrix (33) as in step 5636.
On the other hand, if standard layout is selected as in decision 5622, the layout on the user interface (32) is updated accordingly as in step 5628. The standard layout for the normal mode is preferably used for one-to-one and one-to-many presentation sessions, whereby the presentation sessions have one sender. The standard layout further comprises an anchor button on each added receiver (12) in the user interface (32) to connect the receivers (12).
FIG. 6d shows an example of the standard layout having an anchor button. In this example, two nodes (10) from the node list are added as receivers (12) in the main area of the user interface (32) which are Node 1 and Node 3. Each added receiver (12) in the main area of the user interface (32) comprises a receiver layout with slots indicating the content of senders (11) to be displayed on the respective receiver (12). For example, the content of Node 2 is displayed on Node 1 and the content of Node 4 is displayed on Node 3 simultaneously. The content of Node 5 is only displayed on Node 3 once Node 5 is selected by the user. As shown in FIG. 6d, the anchor buttons in the user interface (32) are not linked and hence the added receivers (12) are not connected to each other. The standard layout shown in FIG. 6d is preferably used for one-to-one presentation session.
However, to enable a one-to-many presentation session, the receivers (12) must be connected to each other as in step 5632. To connect the receivers (12), the receivers (12) are linked through the anchor buttons in the user interface (32) and the configuration of the presentation is finally updated by the configuration matrix (33) as in step 5636. An example of the receivers (12) linked through the anchor button is shown in FIG. 6e. Once the two receivers (12) which are Node 1 and Node 2 are linked together, any sender (11) for both receivers (12) may display the content concurrently on both receivers (12). For example, as both receivers (12) Node 1 and Node 2 are linked together during a presentation session, the content of Node 4 is not only displayed on Node 1 , but the content of Node 4 is also displayed on Node 2.
Reference is now made to FIG. 7 which illustrates the flowchart of sub-steps for setting up a sender (11) in queued mode as in step 5800 of FIG. 4. Once receivers (12) have been set up as in step 5600, the moderator host (23) transfers a node (10) from the node list towards an empty slot inside a receiver layout in the user interface (32) as in step 5802. Next, the presentation manager (31) checks the node capability with the node registry (22) by determining if the node (10) is a sender (11) as in decision 5806. If the node (10) is not a sender (11), the node (10) is returned to the node list as in step 5808.
However, if the node (10) is considered as a sender (11), the node (10) is added as a sender (12) for the receiver (12) as in step 5810 before the configuration of the presentation is updated by the configuration matrix (33) as in step 5812.
Reference is once again made to FIG. 6b which shows an example of the queued mode layout. In this example, three nodes (10) are added as senders (11) for receiver 1 . The three nodes are Node 2, Node 4, and Node 13, whereby these nodes display the content during first, second, and fourth presentation sessions respectively.
FIG. 8 illustrates a flowchart of sub-steps for setting up sender (11) in normal mode as in step 5800 of FIG. 4. Initially, the moderator host (23) transfers a node (10) from the node list towards an empty slot inside a receiver layout in the user interface (32) as in step 5820. The presentation manager (31) then checks the node capability with the node registry (22) by determining if the node (10) is a sender (11) as in decision 5824. If the node (10) is not a sender (11), the node (10) is returned to the node list as in step 5826. However, if the node (10) is considered a sender (11), the presentation manager (31) determines if a standard layout or a split layout is chosen as in decision 5828.
If the split layout is chosen, the presentation manager (31) further determines if all slots in the receiver layout are filled as in decision 5830. If all slots in the receiver layout are filled, the node (10) is returned to the node list as in step 5826. However, if there is still an empty slot inside the receiver layout, the node (10) is added as a sender (11) by the presentation manager (31) as in step 5832.
For example, as shown in FIG. 6c which illustrates an example of the normal mode with split layout on the user interface (32), there is still one empty slot inside the split receiver layout of both added receivers of Node 1 and Node 5. Therefore, the presentation manager (31) may still add one sender (11) to Node 1 and Node 5. For a split layout, content from different senders (11) are displayed simultaneously by each receiver (12). Therefore, as shown in FIG. 6c, the content of Node 2, Node 12 and Node 1 1 are displayed simultaneously on Node 1 .
On the other hand, if the standard layout is chosen as in decision 5828, the node is directly added as a sender (11) by the presentation manager (31) as in step 5832. Finally, the configuration of the presentation is updated by the configuration matrix (33) as in step 5834.
While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specifications are words of description rather than limitation and various changes may be made without departing from the scope of the invention.

Claims

1 . A system (100) for managing presentation sessions comprising:
a) at least two nodes (10) that include:
i. at least one sender (11) configured to capture, encode and transmit media content; and
ii. at least one receiver (12) configured to receive, decode and display incoming media content from the at least one sender (11);
characterised in that the system (100) further comprising:
b) a node agent (13) connected to the at least two nodes (10) configured to identify node capability of each node (10) by detecting if the node (10) is connected to a display device or input device;
c) a session host (20) connected to the node agent (13) configured to manage node registration and relay control commands to the at least two nodes (10); and
d) a moderator console (30) connected to the session host (20) configured to host a user interface (32) to control presentation content flow.
2. The system (100) as claimed in claim 1 , wherein the session host (20) further comprising:
a) a node manager (21) configured to receive registration information of the node (10) from the node agent (13) and relay commands received from a moderator console (30) to the at least two nodes (10);
b) a node registry (22) configured to store node information and node capability from the node manager (21); and
c) a moderator host (23) configured to extract and aggregate the node information from the node registry (22).
3. The system (100) as claimed in claim 1 , wherein the moderator console (30) further comprising:
a) a presentation manager (31) configured to host the user interface (32) and relay commands to run the presentation sessions; and b) a configuration matrix (33) configured to store configuration of the presentation that includes presentation mode, presentation layout and node associations.
4. A method for managing presentation sessions is characterised by the steps of: a) identifying node capability of a plurality of nodes (10) by a node agent (13);
b) relaying the node capability of the plurality of nodes (10) to a node manager (21); and
c) setting up the presentation sessions by a moderator console (30).
5. The method as claimed in claim 4, wherein identifying node capability of the plurality of nodes (10) by the node agent (13) includes the steps of:
a) determining if each node (10) has any external output display connection;
b) computing a built-in display resolution if no external output display connection is detected to the node (10);
c) determining if receiver mode is enabled in a configuration file if the built- in resolution is more than a predetermined value;
d) enabling receiver capability on the node (10) if the receiver mode is enabled in the configuration file; and
e) enabling sender capability on the node (10) if any input device connection is detected.
6. The method as claimed in claim 5, wherein if any external output display connection is detected to the node (10), the steps further include:
a) enabling receiver capability on the node (10); and
b) enabling sender capability on the node (10) if any input device connection is detected.
7. The method as claimed in claim 4, wherein setting up the presentation sessions by the moderator console (30) includes the steps of:
a) generating a user interface (32) by a presentation manager (31); b) setting up presentation mode as either queued mode or normal mode; c) setting up receiver (12) through the user interface (32); and d) setting up sender (11) in queued mode or normal mode through the user interface (32).
8. The method as claimed in claim 7, wherein setting up the receiver (12) through the user interface (32) includes the steps of:
a) checking node capability of a node (10) that is transferred from a node list towards a main area on a configuration page of the user interface (32) by the presentation manager (31);
b) determining if the node (10) has previously been added as a receiver (12) by the presentation manager (31) if the node (10) is considered as a receiver (12);
c) adding the node (10) as a receiver (12) in the user interface (32) if the node (10) has not been added as a receiver (12);
d) determining if queued mode or normal mode is selected; and e) updating the user interface (32) to a queued mode layout to accommodate one-to-one presentation session if queued mode is selected.
9. The method as claimed in claim 8, wherein the queued mode layout updated in the user interface (32) comprises a receiver layout for each added receiver (12) that includes slots for nodes (10) with sender capability configured to determine the sequence of content to be displayed on the added receiver.
10. The method as claimed in claim 8, wherein if the normal mode is selected, the step further includes:
a) determining if split layout or standard layout is selected for the receiver (12) by a moderator host (23); and
b) updating the user interface (23) to a split layout to accommodate many- to-one presentation session if split layout is selected.
1 1 . The method as claimed in claim 10, wherein the split layout updated in the user interface (32) comprises a split receiver layout for each added receiver (12) that includes slots for nodes (10) with sender capability configured to indicate the content that is to be displayed simultaneously on the receiver (12).
12. The method as claimed in claim 10, wherein if the standard layout is selected, the step further includes updating the user interface (23) to a standard layout to accommodate one-to-one or one-to-many presentation sessions. The method as claimed in claim 12, wherein the standard layout updated in the user interface (32) comprises a receiver layout for each added receiver (12) that includes slots for nodes (10) with sender capability configured to indicate the content that is to be displayed one at a time on the receiver (12), and a button for each added receiver (12) configured to connect the receivers (12) during the presentation session to accommodate one-to-many presentation session. 1 The method as claimed in claim 7, wherein setting up the sender (11) in queued mode through the user interface (32) includes the steps of:
a) checking node capability of a node (10) by the presentation manager (31);
b) adding the node (10) as the sender (11) for the receiver (12) in the user interface (32) if the node (10) is considered as a sender (11); and c) updating configuration of presentation by a configuration matrix (33).
The method as claimed in claim 7, wherein setting up the sender (11) in normal mode through the user interface (32) includes the steps of:
a) checking node capability of a node (10) by the presentation manager (31);
b) determining if a split layout or standard layout is chosen;
c) determining if all slots in a receiver layout are filled if split layout is chosen;
d) adding the node (10) as a sender (11) for the receiver (12) by the presentation manager (31) if the receiver (12) still has an empty slot inside the receiver layout; and
e) updating configuration of presentation by a configuration matrix (33).
The method as claimed in claim 15, wherein if all slots in the receiver layout are filled, the node (10) is returned to the node list.
1 The method as claimed in claim 15, wherein if a standard layout is chosen, the steps further include: a) adding the node (10) directly as a sender (11) for the receiver (12) by the presentation manager (31); and
b) updating configuration of presentation by the configuration matrix (33).
PCT/MY2018/050077 2017-12-28 2018-11-16 A system and method for managing presentation sessions WO2019132643A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
MYPI2017705118 2017-12-28
MYPI2017705118A MY190448A (en) 2017-12-28 2017-12-28 A system and method for managing presentation sessions

Publications (1)

Publication Number Publication Date
WO2019132643A1 true WO2019132643A1 (en) 2019-07-04

Family

ID=67063985

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/MY2018/050077 WO2019132643A1 (en) 2017-12-28 2018-11-16 A system and method for managing presentation sessions

Country Status (2)

Country Link
MY (1) MY190448A (en)
WO (1) WO2019132643A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022025751A1 (en) * 2020-07-28 2022-02-03 Mimos Berhad A system and method for mirroring and distributing a presentation content

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6161137A (en) * 1997-03-31 2000-12-12 Mshow.Com, Inc. Method and system for providing a presentation on a network
US7165213B1 (en) * 1996-10-30 2007-01-16 Avaya Technology Corp. Method and system for coordinating media and messaging operations in an information processing system
US20100070997A1 (en) * 2008-09-12 2010-03-18 At&T Intellectual Property I, L.P. System for managing media presentations
US20110208804A1 (en) * 2010-02-23 2011-08-25 Microsoft Corporation Centralized management tool for remote presentation session server farms
WO2015088322A1 (en) * 2013-12-10 2015-06-18 Mimos Berhad System and method for managing multiple presentation sessions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7165213B1 (en) * 1996-10-30 2007-01-16 Avaya Technology Corp. Method and system for coordinating media and messaging operations in an information processing system
US6161137A (en) * 1997-03-31 2000-12-12 Mshow.Com, Inc. Method and system for providing a presentation on a network
US20100070997A1 (en) * 2008-09-12 2010-03-18 At&T Intellectual Property I, L.P. System for managing media presentations
US20110208804A1 (en) * 2010-02-23 2011-08-25 Microsoft Corporation Centralized management tool for remote presentation session server farms
WO2015088322A1 (en) * 2013-12-10 2015-06-18 Mimos Berhad System and method for managing multiple presentation sessions

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022025751A1 (en) * 2020-07-28 2022-02-03 Mimos Berhad A system and method for mirroring and distributing a presentation content

Also Published As

Publication number Publication date
MY190448A (en) 2022-04-21

Similar Documents

Publication Publication Date Title
KR101924163B1 (en) Methods, systems, and media for managing output of an hdmi source
EP2879379B1 (en) Methods, devices and system for media negotiation in a multi-stream meeting
US20140306865A1 (en) Method for communicating with a plurality of first display devices and at least one second display device, and electronic apparatus using the same method
KR101201191B1 (en) System and method for providing one class of users of an application a view of what another class of users of the application is visually experiencing
KR101860058B1 (en) System and method for online fan meeting
CN104050013A (en) Virtual desktop processing method, device and virtual desktop server
TW201637415A (en) Bridge device for large meetings
US20170134690A1 (en) Multi-display apparatus
CN113542660A (en) Method, system and storage medium for realizing conference multi-picture high-definition display
WO2019132643A1 (en) A system and method for managing presentation sessions
US20140115639A1 (en) Multi-vision virtualization system and method
US9178711B2 (en) Method and system for the dynamic management of the transmission of streams within a plurality of terminals
CN116166214A (en) Vehicle-mounted audio playing method, system and controller
US8019824B2 (en) Remotely operating computer software applications using low bandwidth
WO2013168287A1 (en) Relay device
CN111405308B (en) Method and device for sending live audio and video data
EP3367632B1 (en) A system and a method for switching focus and a connector
KR101738667B1 (en) Method and system for providing real-time contents
WO2020063087A1 (en) Display method and device
KR101928368B1 (en) Resource sharing method between devices
CN106341737B (en) IP multicast stream processing method, switch set, server and system
EP4134890A1 (en) Information processing device, information processing method, and program
CN114979738B (en) Wireless screen projection method, receiver and storage medium
CN112738445B (en) Multi-line plug flow method and device, storage medium and electronic equipment
JP6946122B2 (en) Trigger signal output device, trigger signal output method, broadcast master system, and program

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

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

Country of ref document: EP

Kind code of ref document: A1