Invented by Ashutosh Tripathi, Nagesh Pabbisetty, Subrata Roychoudhuri, Microsoft Technology Licensing LLC
The Microsoft Technology Licensing LLC invention works as followsThe techniques to manage recordings of multimedia conference events are discussed. A recording management component may be included in an apparatus to manage recording and reproducing operations for a multi-media conference event. The recording component can include an event capture module that records a multi-media conference event into a recorded meeting. The recording management component can include an event entity (entity event) module communicatively connected to the event capture module. This module is operative to create an entity event list of the recorded meeting. The recording management module may include an event reproduction component communicatively connected to the event entity module. This module is operative to reproduce a recorded meeting event. The recording component may include an event interface communicatively connected to the event replication module. The event interface module is operative to display the presence information of one or more entities in the entity event list, while reproducing the recorded event. “Other embodiments are described, and claims.
Background for Techniques for managing recordings of multimedia conferences
A multimedia conference system allows for multiple participants to share and communicate different types of media in a real-time collaborative meeting via a network. Multimedia conference systems can display various types of media using different GUI windows or views. One GUI view could include video images or participants. Another GUI view could include slideshows. A third GUI view could include text messages. This allows geographically dispersed participants to interact and exchange information in a virtual environment that is similar to the physical environment of a meeting where everyone is present.
Recording is an important component of most multimedia conference systems, as it allows asynchronous access of the meeting’s content and proceedings. Some of the most common scenarios are creating presentations or training materials for distribution or reuse, preserving context and material for an absentee, archiving to take notes offline or preserve discussions, or archiving in order to comply with laws and regulations. These scenarios are usually based on the assumption that the content of meetings and the discussions can be used after the meeting. Improvements to recording management techniques could enhance the value for these and other scenarios.
Various embodiments can be directed in general to multimedia conference systems. Some embodiments are aimed at techniques for managing recordings of a multi-media conference event. Multimedia conference events may involve multiple participants. Some may be in a conference hall, while others can participate remotely.
In one embodiment, an apparatus can include a recording component that manages recording and reproducing operations for a multi-media conference event. The recording component can include an event capture module that records a multi-media conference event into a recorded meeting. The recording management component can include an event entity (entity event) module communicatively connected to the event capture module. This module is operative to create an entity event list of the recorded meeting. The recording management module may include an event reproduction component communicatively connected to the event entity module. This module is able to reproduce the recorded event. The recording component may include an event interface communicatively connected to the event replication module. The event interface module is operative to display the presence information of one or more entities in the entity event list, while reproducing a recorded meeting event. “Other embodiments are described, and claims.
This Summary is intended to present a number of concepts that are described in more detail in the Detailed description. This Summary does not aim to identify the key features or essential elements of the claimed object matter. Nor is it meant to be used as a tool to limit the scope.
Various embodiments” include physical or logical structure arranged to perform specific operations, functions, or services. Structures can be physical, logical or a mixture of both. Hardware elements, software components, or a mixture of both can be used to implement the physical or logical structure. The descriptions of embodiments that refer to specific hardware or software components are examples, and not intended as limitations. The decision to use software or hardware elements in order to implement an embodiment is based on several external factors. These include desired computational rates, power levels and heat tolerances, budget for processing cycles, memory resources, bus speeds and other performance or design constraints. The physical or logical structure may also have corresponding connections that allow information to be communicated between the structures via electronic signals or messages. These connections can be wired or wireless, depending on the structure and/or information. Any reference to “one embodiment” or “an embodiment” is misleading. or ?an embodiment? At least one embodiment includes a certain feature, structure or characteristic that is described in conjunction with the embodiment. The phrase “in one embodiment” appears in several places. The phrase “in one embodiment” may appear in different places within the specification. This does not mean that they all refer to the same embodiment.
A multimedia system can include, amongst other network elements, an multimedia conference server, or another processing device, configured to provide web-conferencing services. A multimedia conference server, for example, may include a server component that mixes and controls different media types in a meeting or collaboration event such as a Web conference. Meeting and collaboration events can refer to any multi-media conference event that offers various types of multimedia content in a live or real-time online environment. ?multimedia event? or ?multimedia conference event.?
In one embodiment, a multimedia conference system can include one or multiple computing devices that are implemented as meeting consoles. The multimedia conference server can be connected to each meeting console to allow it to take part in a multi-media event. The multimedia conference server may receive different types of information from various meeting consoles during the event. It then distributes that information to all or some of the meeting consoles taking part in the event. This allows geographically dispersed participants to interact and exchange information in a virtual environment that is similar to an actual meeting where everyone is present.
In a virtual environment, it can be difficult to identify all the participants in a meeting. In a GUI, the participants in a multi-media conference are listed with a list of names. The participant list may include a participant’s name, image, location, title and other identifying details. Participants and identifying data for the participant list are typically obtained from the meeting console that is used to join a multimedia conference event. A participant, for example, uses a meeting interface to join a virtual conference room during a multimedia event. Before joining, the participant must provide various types of identification information in order to perform authentication with the multimedia server. The multimedia conference server authenticates a participant and allows them to access the virtual meeting room.
Recording is an important component of most multimedia conference systems, as it allows asynchronous access of the meeting’s content and proceedings. Some of the most common scenarios are creating presentations or training materials for reuse, or for a large audience, or preserving context and material for an absentee. Other high-level usage scenarios include archiving to preserve discussions or offline notes, or for offline note taking. These scenarios are usually based on the assumption that the content of meetings and the discussions can be used after the meeting.
The conventional recording management techniques are not satisfactory for many reasons. Recorded meetings are often viewed as a mere record of previous multimedia conferences. The recorded meeting events can be viewed as static files, which do not require any changes or modifications once the multimedia event is over. The playback of recorded meetings is typically a passive event where the viewer watches the recording or consumes it. A viewer might have questions regarding the topic discussed in the multimedia conference. The viewer will have to manually search through the meeting roster or the recording of the contact for the presenter. The viewer will then have to find the contact information of the participant and attempt to contact them to determine their availability. They may also need to establish a dialogue with the participant using various communication channels (e.g. telephone, email, or chat). It can be a long and tedious process, which some viewers might not consider worth it to ask a participant a simple question. The viewer has limited control over playback, including fast forward, reverse and pause. However, the recorded event is difficult for the viewer to modify and manipulate. The recorded meeting event, for example, may not be able to store any information or events which occur after the multimedia event has been recorded. For instance, viewing activities and discussion.
To solve these problems and others, the embodiments generally direct themselves to various enhanced recording-management techniques. Some embodiments focus on interactive playback to dynamically display a recorded event and store events that occurred after the recording. In one embodiment, a multimedia server, for instance, may have a recording component that provides enhanced recording, playback and access operations for a multi-media conference event. The recording component can allow viewers to interact dynamically with the viewing environment. For example, it may indicate when the participants recorded in the recorded event are online and ready for communication through a convenient communication channel such as instant message. This can be achieved, for instance, by retrieving the presence information of original participants in a recorded event, such attendees and presenters. The recording management component can also provide the presence of previous and current viewers to a recorded event. This allows for a dynamic environment in which viewers can discuss the recorded event. The recording management component can store these communications in the recorded event to ensure that it is always up-to-date with the post-recording activity. The viewers and participants can then more efficiently use recorded meetings events in a dynamic and robust manner.
FIG. The block diagram of a multimedia system 100 is shown in FIG. Multimedia conference 100 can be a system architecture that is suitable for various embodiments. Multimedia conference 100 can include multiple elements. A component can be any physical or logical arrangement arranged to perform a certain operation. Each element can be implemented in hardware, software or any combination of the two, depending on the desired design parameters and performance constraints. Hardware elements include semiconductor devices, chips, microchips and chip sets. Examples may also include processors and microprocessors. Software may be any of the following: software modules, routines and subroutines; functions, methods; interfaces. The multimedia conference system shown in FIG. Although FIG. 1 shows a limited number elements in a topology, multimedia conference system 100 can include more or fewer elements in alternative topologies depending on the desired implementation. In this context, the embodiments are not restricted.
In various embodiments, multimedia conference system 100 can be a part of a wired communication system, wireless communication system or combination of the two. The multimedia conference system 100, for example, may contain one or multiple elements that communicate information via one or several types of wired communication links. Wired communication links can include, for example, a cable, wire, printed circuit board, Ethernet connection, peer to peer (P2P), backplane fabric, semiconductor materials, twisted pair wires, coaxial cables, fiber optic connections, etc. The multimedia conference system may also include one or multiple elements that communicate information via one or several types of wireless communication links. Wireless communications links can include, for example, a radio, an infrared, a radio-frequency, Wireless Fidelity, or a portion or the spectrum.
In various embodiments, multimedia conference system 100 can be configured to communicate, manage, or process different types information, including media information and control data. Media information can include, for example, any data that represents content intended for users, such as voice, video, audio, image, textual, numerical, application, alphanumeric, graphic, etc. Media content can also be used to refer to media information. As well. Control information can be any data that represents commands, instructions, or control words for an automated system. Control information can be used, for example, to send media data through a system or to connect devices. It may also be used to instruct a device how to process media data in a certain way.
In various embodiments, multimedia conference system 100 may include a multimedia conference server 130. The multimedia conference system 130 can be any logical or physically entity that is configured to establish, control or manage a multimedia call between meeting consoles 100-1-m via a network. The network 120 can be a packet-switched, circuit-switched, or combination of the two. In different embodiments, multimedia conference server 130 can be implemented or comprised as any computing or processing device, including a computer or server, or a server farm or array, or a workstation, mini-computer or mainframe computer. The multimedia conference server may implement or comprise a computing architecture that is suitable for processing and communicating multimedia information. In one embodiment, the multimedia server 130 can be implemented with a computing system as described in FIG. 5. “Examples of the multimedia conference server may include, without limitation, a Microsoft Office Communications Server, a Microsoft Office Live Meeting server, etc.
A specific implementation of the multimedia server 130 can vary depending on the communication protocol or standard to be used. In one example, the Multiparty Multimedia Session Control Working Group Session Initiation Protocol SIP series of standards or variants may be used to implement the multimedia conference servers 130. SIP is proposed as a standard for initiating and terminating interactive sessions that include multimedia elements like video, voice, instant messages, online games and virtual reality. The multimedia conference server 130 can be implemented according to the International Telecommunication Union’s (ITU) H.323 standards or variants. H.323 defines a Multipoint Control Unit (MCU) for coordinating conference call operations. The MCU contains a multipoint control unit (MC) for H.245 signaling and one or several multipoint processors to mix and process data streams. SIP and H.323 are both essentially signaling standards for Voice over Internet Protocol or Voice Over Packet multimedia conference call operations. Other signaling protocols can be implemented on the multimedia conference server 120, but still be included in the scope of embodiments.
In general, the multimedia conference system 100 can be used to make multimedia conference calls. Multimedia conference calls usually involve the communication of voice, video and/or data between multiple endpoints. A public or private packet-network 120 can be used to make audio conferencing, video conferencing, audio/video conference calls, collaborate document sharing, etc. The packet network 120 can also be connected to the Public Switched Telephone Network via one or several VoIP gateways that convert between circuit-switched and packet information.
To establish a multi-media conference call via the packet networks 120, each meeting desk 110-1-m can connect to the multimedia conference server 130 using a variety of wired and wireless communication links that operate at different connection speeds, such as an intranet connection through a local network (LAN) with a high bandwidth, or a DSL or cable modem.
In various embodiments, multimedia conference server 120 may establish, control and manage a multimedia call between meeting consoles. In certain embodiments, a multimedia conference call can be a live web-based call that uses a web conference application with full collaboration capabilities. The multimedia conference server operates as a server central that controls and distributes the media information during a conference. The multimedia conference server 130 receives media data from the various meeting consoles (110-1-m), performs mixing for the different types of media data, and then forwards that media data to all or some of the participants. The multimedia conference server 130 allows one or more meeting consoles 110-1 to join a conference. The multimedia conference servers 130 can use various admission control methods to authenticate and include meeting consoles 110-1 m in a controlled and secure manner.
Click here to view the patent on Google Patents.