Patent Publication Number: US-2011069143-A1

Title: Communications Prior To A Scheduled Event

Description:
BACKGROUND 
     Collaboration event systems allow for collaboration between people in different locations. These systems allow participants to interact with one another through the use of audio and video equipment that provides real time audio and video communications. The process of connecting people across various locations may become complex, particularly where different groups of people desire to use part of the same collaboration event system for different collaboration events. 
     Participants of an event typically access a management system that allows events to be set up and configured. When one event overlaps with another event, the management system may perform a default action that does not result in an optimal resolution to the overlap. The limited abilities of a management system to handle overlaps may make the an event system less user friendly and result in frustration on the part of users, particularly given a wide range of overlaps and situations that can occur with participants of events. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagrams illustrating one embodiment of a collaboration event system. 
         FIGS. 2A-2B  are block diagrams illustrating embodiments of an event endpoint. 
         FIGS. 3A-3B  are block diagrams illustrating embodiments of configurations of audio/video devices. 
         FIG. 4  is a block diagram illustrating one embodiment of a collaboration system configured to allow persons associated with a scheduled event to communicate. 
         FIG. 5  is a flow chart illustrating one embodiment of a method performed by an event management system. 
         FIGS. 6A-6C  are block diagrams illustrating embodiments of communicating with a person who is associated with a scheduled event. 
         FIG. 7  is a block diagram illustrating one embodiment of events managed by an event management system. 
     
    
    
     DETAILED DESCRIPTION 
     In the following detailed description of the preferred embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. The following detailed description, therefore, is not to be taken in a limiting sense. 
     As described herein, an event management system manages collaboration events such as video teleconferences. The event management system maintains registered event specifications for each collaboration event and dynamic event context information that describes the status of collaboration events relative to each other. The event management system uses the registered event specifications and the dynamic event context information to optimize the interaction between collaboration events. The event management system also includes event endpoint information and policies that describes relationships among endpoints and rules associated with endpoints and event attendees. 
     The event management system is configured to provide a communications pathway between persons associated with a scheduled event prior to initiating the scheduled event. The event management system associates persons with the scheduled event using a registered event specification for the scheduled event and/or event endpoint information that associates the location or locations of the persons with the scheduled event. Using the associations, the event management system allows the persons to interact using the communications pathway prior to the scheduled event commencing. 
       FIG. 1  is a block diagrams illustrating one embodiment of a collaboration event system  100 . Collaboration event system  100  includes an event management system  110 , a set of event endpoints  120 ( 1 )- 120 (M), and a network  130  that interconnects event management system  110  and event endpoints  120 . 
     Collaboration event system  100  is configured to create and host collaboration events. A collaboration event is an activity with experiential relevance to people, possessing an extension in time and location. Examples of a collaboration event (hereafter “event”) include telepresence videoconferences and meetings conducted using collaboration studio such as a “Halo studio” offered by Hewlett-Packard Co. For each event, collaboration event system  100  exchanges a selected set of A/V media streams  124 ( 1 )- 124 (M) between a selected set or subset of event endpoints  120 ( 1 )- 120 (M). 
     An event includes a set of collaboration system topologies, each of which include a set or subset of event endpoints  120 ( 1 )- 120 (M). An event also includes a registered event specification  142  that specifies information such as a unique identity token, a purpose, a list of event attendees, a list of event resources, contact information of a host of the event, a priority of the event, start and end dates and times, and/or an event duration. Event resources may include event endpoints  120 , physical locations (e.g., a collaboration studio or conference room), input/output devices  136  (e.g., interactive touchpoints), and attendees  122 . 
     The collaborative event may take place in two or more locations (e.g., different cities) that each have an event endpoint  120  to connect a set of one or more attendees  122  or media resources in each of the locations. Cameras and microphones, for example, may capture video and audio from one or more of the locations (i.e., at one endpoint) and the video and audio may be output using one or more display devices and speakers, for example, at one or more other locations (i.e., one or more other endpoints). In addition, various types of pre-recorded A/V data, such as content from a DVD, may be transported to one or more of the locations where it may be output using a display device or speakers, for example. One or more locations of the collaborative event may include arrangements of office furniture (e.g., office chairs and a conference table) and A/V gear to provide persons with gaze awareness and a full immersion feeling. 
     Event management system  110  is configured to initiate, execute, host, and optimize collaboration events using registered event specifications  142 ( 1 )- 142 (N), dynamic event context  144 , and event endpoint information and policies  146 . Each event is registered with event management system  110 , either in advance (i.e., scheduled ahead of time) or in real time (i.e., scheduled on an ad hoc basis), to create a registered event specification  142  for the event using any suitable device for accessing event management system  110  (e.g., an event endpoint  120  or an input/output device  136 ). Event management system  110  may reference and use each registered event specification  142  for various purposes including preparation for and execution of an event in accordance with the information in a registered event specification  142 . 
     Dynamic event context  144  is real-time information that describes the status of events (e.g., in-progress, interrupted, extended, etc.), the status of events relative to each other (e.g., overlapping or not overlapping based on the start and end times of events), the status of event endpoints  120  and other media resources (e.g., available, reserved, in use or otherwise occupied, or unavailable), and the status of attendees  122  (e.g., checked-in at an event endpoint  120  or elsewhere or not checked-in along with any special privilege indicators or other attendee designations) for each event. Event management system  110  generates and maintains dynamic event context  144  to monitor and manage the real-time system status of collaboration event system  100 . 
     Endpoint information and policies  146  describes the locations, topologies, configurations, and operation policies of event endpoints  120 ( 1 )- 120 (M). Event management system  110  accesses event endpoint information and policies  146  for use in configuring and optimizing collaboration events. Event management system  110  may also reference and use other system information such as the time of day in the process of managing collaboration events. 
     Each event endpoint  120 ( 1 )- 120 (M) provides a respective set of one or more attendees  122 ( 1 )- 122 (M) with a respective set of one or more audio and/or visual media streams  124 ( 1 )- 124 (M) using network  130 . Each event endpoint  120  includes any suitable type, number, and combination of audio and/or visual input and/or output devices that are configured to generate, provide, and/or receive the respective set of media streams  124 . Media streams  124  may each be any suitable combination of live or pre-recorded audio and/or video data that may be combined in any suitable way and output to any number of attendees  122  in any number of event endpoints  120  by collaboration event system  100 . Each set of attendees  122 ( 1 )- 122 (M) includes one or more people where the number of people may stay the same, increase, or decrease during the course of an event. In addition, the set of event endpoints  120  for an event may stay the same, increase, or decrease during the course of an event. 
       FIGS. 2A-2B  are block diagrams illustrating embodiments of event endpoint  120 . In the embodiment of  FIG. 2A , event endpoint  120  includes a set of one or more audio and/or video (NV) devices  162 , a control unit  164 , a network interface  166  and a set of one or more input/output (I/O) devices  168 ( 1 )- 168 (Q). 
     A/V devices  162  includes any type, number, and combination of audio and/or video input and/or output devices. Examples of A/V input devices include microphones, still and video cameras, media players, and computer and storage systems. The A/V input devices capture, detect, receive or otherwise input live or pre-recorded media streams  124  and provide the input media streams  124  to control unit  164  and/or network interface  166 . Examples of A/V output devices include speakers, headphones, headsets, media recorders, and display devices such as projectors, computer monitors, and televisions. The A/V output devices receive media streams from control unit  164  and/or network interface  166  and provide, display, play, or otherwise output live or pre-recorded media streams  124 . 
     Control unit  164  manages the operation of event endpoint  120  by providing control signals and/or other information to and receiving control signals and/or other information from A/V devices  162 , network interface  166  and input/output devices  168 ( 1 )- 168 (Q). In some embodiments, control unit  164  may perform processing on media streams received from A/V devices  162  and/or network interface  166  prior to the media streams being provided to network interface  166  or output by A/V devices  162 . The processing may include coding or decoding media streams from one media and/or network format to another media and/or network format. 
     Network interface  166  includes any suitable type, number, and/or combination of network devices that allow event endpoint  120  to communicate with network  130  using network connection  134 . Network interface  166  receives media streams across network connection  134  and provides the media streams to control unit  164  and/or A/V devices  162 . Network interface  166  also receives media streams from control unit  164  and/or A/V devices  162  and provides the media streams to network  130  using network connection  134 . 
     I/O devices  168 ( 1 )- 168 (Q) include any suitable type, number, and/or combination of input and/or output devices that allow attendees  122 , administrators, or other persons to communicate with event endpoint  120 . The communications may cause event endpoint  120  and/or collaboration event system  100  to perform functions indicated by attendees  122 , administrators, or other persons. Examples of I/O devices  168  include interactive touchpoints, display screens, keyboards, and selection or navigation devices (e.g., a mouse, joystick, flywheel, or touchpad). 
     In other embodiments, the functionality of an A/V device  162  and an I/O device  168  may be included in a single unit such as a laptop computer. In addition, other embodiments may include A/V devices  162  but omit I/O devices  168  or may include I/O devices  168  but omit A/V devices  162 . 
       FIG. 2B  illustrates an embodiment of the operation of endpoint  120 ( 1 ). Endpoint  120 ( 1 ) provides attendees  122 ( 1 ) who are present at endpoint  120 ( 1 ) with media streams  124 ( 1 )( 1 )- 124 ( 1 )( 4 ) using any suitable type and/or combination of audio/video devices  162 ( 1 ). Audio/video devices  162 ( 1 ) are configured to allow for gaze awareness and a full immersion feeling for attendees  120 ( 1 ). 
     In the example of  FIG. 2B , media stream  124 ( 1 )( 1 ) provides information about the event attended by attendees  122 ( 1 ) (e.g., status information, notifications, configuration options, etc.) and media streams  124 ( 1 )( 2 )- 124 ( 1 )( 4 ) provide audio and video representations of by attendees  122 ( 2 )- 122 ( 4 ), respectively, who are present at event endpoints  120 ( 2 )- 120 ( 4 ), respectively. Attendees  122 ( 1 )- 122 ( 4 ) collectively represent the set of attendees who are present for the event illustrated by the example of  FIG. 2B . 
     In other embodiments, endpoint  120 ( 1 ) may provide other numbers of media streams  124 ( 1 ) to attendees  120 ( 1 ) and may have other configurations of audio/video devices  162 ( 1 ) relative to attendees  120 ( 1 ). 
       FIGS. 3A-3B  are block diagrams illustrating embodiments of configurations of audio/video devices  162 . 
     In one embodiment, A/V devices  162  includes integrated A/V gear that forms a collaboration studio such as a “Halo studio” offered by Hewlett-Packard Co. as shown in the embodiment  162 A of  FIG. 3A . In the embodiment of  FIG. 3A , video processors  202  provide video data from A/V switch  201  to display devices  204 ( 1 )- 204 ( 3 ), and display devices  204 ( 1 )- 204 ( 3 ) display the video data. Cameras  206 ( 1 )- 206 ( 3 ) capture video data and provide the video data to A/V switch  201 . An echo cancellation and mixing unit  208  mixes and processes audio data from A/V switch  201  and provides the processed audio data to amplifiers  210 . Amplifiers  210  amplify the audio data and provide the audio data to speakers  212 ( 1 )- 212 ( 3 ) and sub-woofer  214 . Speakers  212 ( 1 )- 212 ( 3 ) output the higher frequencies of the audio data, and sub-woofer  214  outputs the lower, bass frequencies of the audio data. Microphones  216 ( 1 )- 216 ( 3 ) capture audio data and provide the audio data to A/V switch  201 . 
     Display devices  204 ( 1 )- 204 ( 3 ) may be arranged in such a manner around a conference table and chairs to allow for gaze awareness and a full immersion feeling in one embodiment. 
     In another embodiment, A/V devices  162  includes A/V gear as shown in the embodiment  162 B of  FIG. 3B . In the embodiment of  FIG. 3B , video processor  222  provides video data from A/V switch  221  to display device  224 , and display device  224  displays the video data. Camera  226  captures video data and provides the video data to A/V switch  221 . An echo cancellation and mixing unit  228  mixes and processes audio data from A/V switch  221  and provides the processed audio data to speaker  232  and sub-woofer  234 . Speaker  232  outputs the higher frequencies of the audio data, and sub-woofer  234  outputs the lower, bass frequencies of the audio data. Microphone  236  captures audio data and provides the audio data to A/V switch  221  through echo cancellation and mixing unit  208 . 
     Referring back to  FIG. 1 , network  130  may be any suitable type of network or combination of networks formed from any suitable number, type, and/or combination of network devices (not shown). The network devices may operate using any suitable network protocol or protocols and may connect to any suitable number of event endpoints  120  or other computer or storage systems. Network  130  may include any suitable combination of secure networks (e.g., enterprise networks or corporate intranets) with limited and secure connections to other systems or unsecure networks with at least one unsecure connection to another system. 
     Network  130  may be a local, regional, or global network of any suitable network configuration that ranges from local point-to-point connections between event management system  110  and event endpoints  120  to a global array of connections that interconnect event management system  110  and event endpoints  120 . Network  130  may be private or publicly available and include one or more connections to the Internet. 
     Network  130  may be designed specifically to optimize high bandwidth with low latency to be able to transport live, interactive, audio, video, and other data rich media streams. Network  130  may have a smallest link of 45 Mbps, in one embodiment, to avoid any significant serialization delay. Network  130  may also use a flat network topology to minimize latency. In order to keep a high quality end-user experience, network  130  may keep the total one-way latency between any event endpoints  120  to less than one-quarter of a second. This total latency may encompass all aspects of encoding/decoding, encapsulation/de-encapsulation, capture and presentation, filtering, processing, compression and decompression, image compositing, and transport latencies across the transmission path. As the contribution of each component of network  130  to overall latency decreases (as technology improves), the length of the “reach” of where different sites can be physically located may be increased. 
     To better preserve the shortest paths capable of reliable delivery with little packet loss, bandwidth and network resource mechanisms (not shown) may be used to insure high-quality sessions for the duration of the collaboration session. As most traffic streams are presumed to take place linking a pair or small number of event endpoints  120  together for any given session, event management system  110  may have little presumption of event pre-emption once authorized events commence. In some embodiments, longer latency and/or loss tolerant sessions may be provided over network  130 . Such services may include directory, presence, messaging, credential verification, calibration, and time/name services for examples. 
     The interior of network  130  may concentrate on speedy delivery of traffic flows. Any access control, encryption/decryption and other proxy services, if needed, may occur at the edge of network  130  such as in event endpoints  120  and not the interior of network  130  in some embodiments. This design may make the core of the backbone of network  130  simpler to grow, maintain, stable, and very fast. 
     Event management system  110  connects to network  130  using a network interface  131  and a network connection  132 , and event endpoints  120 ( 1 )- 120 (M) connect to network  130  using respective network connections  134 ( 1 )- 134 (M). Each network connection  132  and  134 ( 1 )- 134 (M) may include any suitable type, number, and/or combination of wired or wireless network connections. For example, network connections  132  and  134 ( 1 )- 134 (M) may each be a leased line (i.e., a T3, optical, cable, or wireless high speed link) which provides a large data pipe to and from event management system  110 , event endpoints  120 ( 1 )- 120 (M), and input/output device  136 , respectively. 
     Input/output (I/O) device  136  may be any suitable type of device (e.g., a portable or non-portable device such as an interactive touchpoint, a computer, a cell phone, a media player, or a personal digital assistant) configured to communicate with event management system  110 . I/O device  136  is configured to receive inputs from a person  126  and/or provide outputs to person  126  as indicated by an arrow  137 . The outputs may include audio and/or video outputs. I/O device  136  connects to network  130  using any suitable wired or wireless network connection  138 . I/O device  136  may be omitted in some embodiments. 
     In operation, event management system  110  initiates, executes, hosts, and optimizes collaboration events using registered event specifications  142 ( 1 )- 142 (N), dynamic event context  144 , and event endpoint information and policies  146 . 
     Event management system  110  initiates execution of an event by allocating resources for creating a real-time representation of the event according to the registered event specification  142  of the event to optimize the experience of attendees  122 . The allocated resources include the set or a subset of event endpoints  120  as indicated by the registered event specification  142 . Event management system  110  continues execution of the event with changes to the topology of the event (e.g., the addition or removal of event endpoints  120  during the event) to maintain and optimize the experience of attendees  122  and ends as dictated by the registered event specification  142  or by external inputs (e.g., from an attendee  122 ). During execution, event management system  110  may describe an event as being “in-progress”. 
     In preparation for event execution (i.e., during event preparation) and during event execution, certain activities may be performed by event resources or event management system  110  that impact the management of the event, such as an attendee  122  checking in at an endpoint location, an input/output device associated with an endpoint, or another location. During the course of the lifecycle of an event, additional related artifacts may be added to the event, such as an archive of the execution of the event. 
     Event management system  110  optimizes event preparation and event execution for each registered event that requires various resources including those resources whose states may impact event preparation and execution. The optimization accounts for resources that may be in use by one or more in-progress events, resources that may be unavailable (e.g., requested for use by another event or out of service), key event attendees  122  that are missing, and other critical event information. Event management system  110  also optimizes event execution for in-progress events by preventing unwanted disruption of an event using resources required by the registered event and by handling requests for resources made by other events. 
     Event management system  110  performs the optimization using registered event specifications  142  for all related events including the primary event being prepared and other events in progress that are consuming needed resources and dynamic event context information  144  which includes information about event resources (e.g., resources used by other in-progress events and other status information about needed resources). Event management system  110  may also perform the optimization using information provided by attendees, administrators, and/or other persons via I/O devices  168  and/or  136  associated with the event in progress and the registered events and event endpoint information and policies  146 . Event endpoint information and policies  146  includes information about the physical and assigned relationships among resources, including relationship information about event endpoints  120  and I/O devices  168  and/or  136 , policies regarding the management of shared resources to facilitate optimal event execution, and principles governing the systems behaviors in consideration of the multitude of registered and dynamic information. 
     Using inputs from registered event specifications  142 , dynamic event context information  144 , I/O devices  168  and/or  136 , and event endpoint information and policies  146 , event management system  110  applies event optimization policies to interact with an in-progress event, with related resources such as endpoints  120 , and with related input/output devices  168  and/or  136 . In doing so, event management system  110  optimizes the experience of attendees  122  such as by event preparation and creating a plan for execution when an overlap is detected between two or more events. 
     As used herein, the term overlap refers to a commonality of resources between two or more events that may prevent one or more of the events from proceeding as currently defined by the respective registered event specifications  142  for the one or more events. The commonality may be an event endpoint or endpoints  120 , an event attendee  122 , an event resource (e.g., A/V equipment), or at least a portion of network  130  or network interfaces and connections  132  or  134 , for example, where the commonality is not conducive to being used by two or more events at the same time or close to the same time. 
     Event management system  110  is configured to provide a communications pathway between persons associated with a scheduled event prior to initiating the scheduled event using network interface  131  and network connection  132 . Event management system  110  associates the persons with the scheduled event using a registered event specification  142  for the scheduled event and/or event endpoint information  146  that associates the location or locations of the persons with event endpoints  120  of the scheduled event. Using the associations, event management system  110  allows the persons, who may be attendees  122  or other interested persons of the scheduled event, to interact using the communications pathway prior to the scheduled event commencing. The communication pathway may extend beyond endpoints  120  to hallways or vestibules outside of or nearby endpoints  120  or other locations remotely located from endpoints  120 . 
     Event management system  110  provides persons associated with a scheduled event with the ability to send communications to other persons associated with a scheduled event as shown in the embodiments of  FIGS. 4  and  5 .  FIG. 4  is a block diagram illustrating one embodiment of collaboration event system  100  configured to allow persons  126  and  128  associated with a scheduled event to communicate.  FIG. 5  is a flow chart illustrating one embodiment of a method performed by event management system  110  to provide the communications pathway. 
     In  FIG. 4 , an event is scheduled to occur between a set of event endpoints  120 ( 1 )- 120 (R) where R is less than or equal to M (i.e., the set of event endpoints  120 ( 1 )- 120 (R) represent a subset of event endpoints  120 ( 1 )- 120 (M) shown in  FIG. 1 ). A registered event specification  142  specifies the set of event endpoints  120 ( 1 )- 120 (R) for the scheduled event. During the scheduled event, event endpoints  120 ( 1 )- 120 (R) will provide respective media streams  124 ( 1 )- 124 (R) to respective sets of attendees  128 ( 1 )- 128 (R) of the scheduled event. The dashed arrows in  FIG. 4  indicate that the media streams  124 ( 1 )- 124 (R) are not yet being provided to attendees  128 ( 1 )- 128 (R) (i.e., the scheduled event has not commenced). Prior to or during the scheduled event, one or more other persons  126  may interact with one or more of the sets of attendees  128 ( 1 )- 128 (R) using input/output device  136  as indicated by arrow  137 . 
     A person  126  may be associated with the scheduled event in various ways. For example, a person  126  may be an organizer or attendee of the scheduled as identified by the registered event specifications  142  for the scheduled event. Person  126  may also be acting on behalf of organizers or attendees identified by the registered event specifications  142  for the scheduled event. Person  126  may further be attempting to register for the scheduled event by adding his or her name to the registered event specifications  142  for the scheduled event. In addition, person  126  may be associated with the scheduled event in response to event management system  110  detecting that person  126  is located at or near an event endpoints  120 ( 1 )- 120 (R) for the scheduled event. Each person  126  communicates with event management system  110  using an input/output device  136  (i.e., a device not associated with an endpoint  120 ). 
     Event management system  110  provides a communication pathway between input/output devices  136  used by persons  126  and input/output devices  168  used by attendees  128  (i.e., persons associated with a scheduled event) prior to initiating the scheduled event. The communication pathway is represented in  FIG. 4  by arrows  129 ( 1 )- 129 (R) and  137  and allows persons  126  and attendees  128  to send communications to persons  126  and attendees  128  at other locations (i.e., other endpoints  120  or locations of input/output device  136 ) prior to the scheduled event being initiated. 
     The embodiment of  FIG. 5  will be described with reference to the embodiment shown in  FIG. 4 . In  FIG. 5 , event management system  110  receives information from a person  126  or attendee  128  as indicated in a block  502 . The information may identify person  126  or attendee  128  directly or indirectly (e.g., using a name, a event code, or other identifier), identify a location of person  126  or attendee  128 , or specify or request an action to be performed by event management system  110  (e.g., person  126  or attendee  128  checking in for the scheduled event). Person  126  or attendee  128  inputs the information into a respective input/output device  136  or  168 , and device  136  or  168  provides the information to event management system  110 . 
     Event management system  110  associates person  126  or attendee  128  with a scheduled event as indicated in a block  504 . Event management system  110  detects an association between person  126  or attendee  128  and the scheduled event by identifying a relationship between person  126  or attendee  128  and the scheduled event. The relationship may depend on an identity of person  126  or attendee  128  as specified by the received information or, where an attendee  128  uses a device  168  which is associated with an endpoint  120 , a location of the device  168  as determined from the received information. 
     In one embodiment, event management system  110  associates person  126  or attendee  128  with the scheduled event by matching information received from person  126  or attendee  128  (e.g., a name, an event code, or other identifier) with information in the registered event specification  142  for the scheduled event. In another embodiment, event management system  110  associates person  126  or attendee  128  with the scheduled event by matching location information that identifies a location of a device  168  used by an attendee  128  with location information in the registered event specification  142  and/or event endpoint information and policies  146 . In other embodiments, event management system  110  associates person  126  or attendee  128  with the scheduled event in other suitable ways. 
     Event management system  110  determines whether to send a communication to the person  126  or attendee  128  as indicated in a block  506 . Event management system processes the information of block  502  and determines whether to send a communication to person  126  or attendee  128  using the information from person  126  or attendee  128 , registered event specification  142  for the scheduled event, and/or event endpoint information and policies  146 . 
     If event management system  110  decides to send a communication to the person  126  or attendee  128 , event management system  110  provides the communication to person  126  or attendee  128  as indicated in a block  508 . Event management system  110  may also provide the communication to other attendees  128  of or persons  126  associated with the scheduled event synchronously or asynchronously with providing the communication to person  126  or attendee  128 . Event management system  110  may select the communication of block  508  in accordance with policies corresponding to the scheduled event as expressed in registered event specification  142  and/or event endpoint information and policies  146  or default settings. 
     Device  136  or  168  receives the communication from event management system  110  and provides the communication to at least person  126  or attendee  128  and possibly other attendees of or persons associated with the scheduled event. Person  126  or attendee  128  may input a communication or other information into respective device  136  or  168  in response to the communication from event management system  110 , and device  136  or  168  provides the communication or other information to event management system  110 . Event management system  110  receives the communication or other information from person  126  or attendee  128 . 
     Event management system  110  determines whether other persons  126  or attendees  128  are checked in for the scheduled event as indicated in a block  510 . As part of checking in a person  126  or an attendees  128  for the scheduled event, event management system  110  detects an association between a person  126  or an attendees  128  and the scheduled event by identifying a relationship between person  126  or attendee  128  and the scheduled event. If other persons  126  or attendees  128  are not checked in for the scheduled event, then event management system  110  may repeat the functions of blocks  506  and  508  to continue communicating with the present person  126  or attendee  128  until additional persons  126  or attendees  128  check in. 
     If other persons  126  or attendees  128  are checked in for the scheduled event, then event management system  110  determines whether to send a communication to checked in persons  126  and attendees  128  the scheduled event as indicated in a block  512 . Event management system  110  processes the information of block  502  and any additional communication or information received from one or more checked in persons  126  or attendees  128 . Event management system  110  determines whether to send a communication to checked in persons  126  and attendees  128  using the received information, any additional communications or information received from one or more checked in persons  126  or attendees  128 , registered event specification  142 , and/or event endpoint information and policies  146 . 
     If event management system  110  decides to send a communication to checked in persons  126  and attendees  128 , event management system  110  provides the communication to the checked in persons  126  and attendees  128  as indicated in a block  514 . Event management system  110  may also asynchronously provide the communication to other persons  126  and/or attendees  128  of the scheduled event when the persons  126  and/or attendees  128  check in. Event management system  110  may select the communication of block  514  in accordance with policies corresponding to the scheduled event as expressed in registered event specification  142  and/or event endpoint information and policies  146  or default settings. 
     Event management system  110  may repeat the functions of blocks  512  and  514  any suitable number of times to provide communications between to the scheduled event. At each step, event management system  110  selects appropriate communications to be provided based on information received from persons  126  and attendees  128 , registered event specification  142 , dynamic event context  144 , and event endpoint information and policies  146 . Event management system  110  may configure the communications in any suitable format and the format may correspond to a type of device  136  or  168  with which event management system  110  is communicating. Examples of communications include text messages, email, status indicators, audio, video, and communications that include a selectable function for use by a person  126  or attendee  128 . 
     Persons  126  and attendees  128  communicate with event management system  110  using respective input/output devices  136  and  168  from any suitable location.  FIGS. 6A-6C  are block diagrams illustrating embodiments of communicating with persons  126  and attendees  128  who are associated with a scheduled event.  FIGS. 6A-6C  illustrate at least three possible locations where persons  126  and attendees  128  may provide communications to and receive communications from event management system  110 . 
     In the embodiment of  FIG. 6A , attendee  128  accesses an input/output device  168 ( 1 ) (e.g., an interactive touchpoint or touchpad display) of an event endpoint  120  to communicate with event management system  110 . In the embodiment of  FIG. 6A , event endpoint  120  includes a conference room  602  and a hallway or vestibule  604  outside of conference room  602  as indicated by a barrier  606 . Barrier  606  may be a wall, a door, a corridor, or other suitable physical structure or space that separates conference room  602  from hallway or vestibule  604 . Input/output device  168 ( 1 ) is located in hallway or vestibule  604  adjacent to or otherwise nearby conference room  602 . Input/output device  168 ( 1 ) is associated with event endpoint  120  with a physical connection (e.g., network connection  134 ) or other information that specifies the physical arrangement of input/output device  168 ( 1 ) in event endpoint  120 . Accordingly, attendee  128  may use input/output device  168 ( 1 ) without substantially interrupting (visually or audibly) an event taking place in conference room  602 . In particular, attendee  128  may use input/output device  168 ( 1 ) without substantially interrupting an output or substantially disturbing a reception of a set of media streams  124  to a set of attendees of an in progress event in conference room  602 . Attendee  128  uses input/output device  168 ( 1 ) in conjunction with event management system  110  to communicate with other persons  126  and/or attendees  128  of the scheduled event as indicated by arrow  129 . 
     Audio/video devices  162  of endpoint  120  that provide media streams  124  to attendees  122  and/or capture media streams  124  from attendees  122  are located inside conference room  602 . Input/output device  168 ( 1 ) is located outside conference room  602 . Although other components of endpoint  120  are shown as being inside conference room  602  in the embodiment of  FIG. 6A , some or all of these components may be located outside of or adjacent to conference room  602  in other embodiments (e.g., in a control room (not shown)). 
     In the embodiment of  FIG. 6B , person  126  accesses an input/output device  136  (e.g., a mobile device) to communicate with event management system  110 . In the embodiment of  FIG. 6B , event endpoint  120  resides at an endpoint location  612 . Person  126  uses input/output device  168 ( 1 ) from any other location  610  that may be remotely located from or in close proximity to endpoint location  612 . Input/output device  136  has no physical relationship with endpoint location  612  or event endpoint  120  in the embodiment of  FIG. 6B . Input/output device  136  may form a virtual association with endpoint location  612  or event endpoint  120  through communications with event management system  110 . Person  126  may use input/output device  136 , as indicated by arrow  137 , in conjunction with event management system  110  to communicate with attendees  122  of an event in endpoint location  612 . Person  126  uses input/output device  136  in conjunction with event management system  110  to communicate with other persons  126  at other locations and/or attendees  128  at event endpoints  120  of the scheduled event as indicated by arrow  137 . 
     In the embodiment of  FIG. 6C , attendee  128  accesses any of input/output devices  168 ( 1 )- 168 (Q) (e.g., an interactive touchpoint or touchpad display) of event endpoint  120  to communicate with event management system  110  prior to the scheduled event commencing. Attendee  128  uses an input/output device  168 , as indicated by arrow  129 , in conjunction with event management system  110  to communicate with other attendees  128  of the scheduled event at other event endpoint  120  (not shown in  FIG. 6C ) and other persons  126  of the scheduled event not at event endpoints  120 . 
     Event management system  110  may provide any suitable type of communications between persons  126  and attendees  128 . For example, event management system  110  may provide persons  126  and attendees  128  with communications that describe the status of the scheduled event, the status of other in-progress or scheduled events, communications from parties associated with other events, or communications with functions that allow a person  126  or attendee  128  to cause communications to be sent to other persons  126  and attendees  128  of the scheduled event. The communications may begin in response to a person  126  or attendee  128  checking in for the scheduled event or in response to other actions, communications, or states detected by event management system  110 . The communications provided by event management system  110  to persons  126  and attendees  128  may be selected in response to information in registered event specification  142  and/or event endpoint information and policies  146 . 
     The communications pathway may be used by attendees  128  and persons  126  of the scheduled event when one or more in-progress events overlap with the scheduled event. One or more attendees  128  may arrive at an event endpoint  120  to find that it is being used by an in-progress event. Event management system  110  may detect the overlap between an in-progress event and a scheduled event in response to an attendee  128  or person  126  checking in for the scheduled event as will now be described with reference to an example in  FIG. 7 . 
       FIG. 7  is a block diagram illustrating one embodiment of in progress events A and B managed by event management system  110  at time t 1 . In progress event A includes event endpoints  120 ( 1 )- 120 ( 4 ) at respective locations  1 - 4 , and in progress event B includes event endpoints  120 ( 5 )- 120 ( 8 ) at respective locations  5 - 8 . 
     A scheduled event is scheduled to begin at or around time t 1  and includes event endpoints  120 ( 1 ),  120 ( 3 ),  120 ( 5 ), and  120 ( 7 ). At time t 1 , scheduled event attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) have arrived at respective event endpoints  120 ( 1 ),  120 ( 3 ),  120 ( 5 ), and  120 ( 7 ) to find the endpoints in use by in progress events A and B. 
     Scheduled event attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) access respective input/output devices  168 ( 1 )( 1 ),  168 ( 3 )( 1 ),  168 ( 5 )( 1 ), and  168 ( 7 )( 1 ) as indicated by respective arrows  129 ( 1 ),  129 ( 3 ),  129 ( 5 ), and  129 ( 7 ). In the example of  FIG. 7 , input/output devices  168 ( 1 )( 1 ),  168 ( 3 )( 1 ),  168 ( 5 )( 1 ), and  168 ( 7 )( 1 ) are located outside of the respective rooms that include respective audio/video devices  162 ( 1 ),  162 ( 3 ),  162 ( 5 ), and  162 ( 7 ) of endpoints  120 ( 1 ),  120 ( 3 ),  120 ( 5 ), and  120 ( 7 ) (e.g., in hallways or vestibules) as indicated by arrows which denote both respective connections  134 ( 1 ),  134 ( 3 ),  134 ( 5 ), and  134 ( 7 ) and respective barriers  606 ( 1 ),  606 ( 3 ),  606 ( 5 ), and  606 ( 7 ) (also shown in  FIG. 6A ). 
     Scheduled event attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) check in with event management system  110  using respective input/output devices  168 ( 1 )( 1 ),  168 ( 3 )( 1 ),  168 ( 5 )( 1 ), and  168 ( 7 )( 1 ). Event management system  110  provides a communication pathway between input/output devices  168 ( 1 )( 1 ),  168 ( 3 )( 1 ),  168 ( 5 )( 1 ), and  168 ( 7 )( 1 ) to allow attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) to communicate as described above. 
     Using the communications pathway, attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) may communicate to collectively decide how to proceed with the scheduled event given the overlap with in progress events A and B. In other examples, attendees  128 ( 1 ),  128 ( 3 ),  128 ( 5 ), and  128 ( 7 ) may also communicate with other attendees  128  that are inside or outside of different endpoints  120  (e.g., as in the embodiments of  FIGS. 6A and 6C ) and/or with other persons  126  at other locations (e.g., as in the embodiment of  FIG. 6B ). 
     Subsequent to providing the communications pathway to attendees  128  and persons  126  of the scheduled event, event management system  110  may initiate the scheduled event by allocating the set of event endpoints  120  and any other resources for the scheduled event. In particular, event management system  110  may initiate the scheduled event in response to all event endpoints  120  and other resources of the scheduled event, including any event endpoints  120  that had overlapped with an in progress event, becoming available. 
     In the above embodiments, event management system  110  may include any suitable combination of hardware and software components. In one embodiment, event management system  110  includes one or more programs that is stored in any suitable type, number, and/or combination of portable or non-portable storage media (not shown) within or otherwise accessible to event management system  110 . The programs are accessible to and executable by any suitable type, number, and/or combination of processors (not shown) in event management system  110  to perform the functions described above. 
     Although specific embodiments have been illustrated and described herein for purposes of description of the preferred embodiment, it will be appreciated by those of ordinary skill in the art that a wide variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. Those with skill in the optical, mechanical, electro-mechanical, electrical, and computer arts will readily appreciate that the present invention may be implemented in a very wide variety of embodiments. This application is intended to cover any adaptations or variations of the preferred embodiments discussed herein. Therefore, it is manifestly intended that this invention be limited by the claims and the equivalents thereof.