WO2012170005A1

WO2012170005A1 - Device redirection

Info

Publication number: WO2012170005A1
Application number: PCT/US2011/039263
Authority: WO
Inventors: James R. Cole; Mark E. Gorzynski
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2011-06-06
Filing date: 2011-06-06
Publication date: 2012-12-13

Abstract

In one implementation, an electronic message that originated from an electronic device on a local network and that specifies an intended destination is intercepted. Responsive to intercepting the electronic message, a network resource (e.g., a collaboration resource or a resource for sharing content between multiple users/devices) is identified, and the electronic device is redirected to the identified network resource.

Description

DEVICE REDIRECTION

BACKGROUND

[0001] A videocon erence between participants at two or more different sites may involve the exchange of audio/video (AN) streams between electronic devices at the two or more different sites, thereby enabling participants at the two or more different sites to hear and see one another. To supplement the videoconference, participants also may use electronic devices to access collaboration resources or other resources for sharing content across the two or more different sites.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] FIGS. 1 A-1 C are diagrams of an example of a videoconference endpoint.

[0003] FIGS. 2A and 2B are block diagrams of examples of communications systems.

[0004] FIG. 3 is a block diagram of an example of a network node.

[0005] FIGS. 4 and 5 are flowcharts of examples of processes for redirecting electronic devices.

DETAILED DESCRIPTION

[0006] When multiple participants in a videoconference are in a common geographic location, they may gather together in the same room to participate in the videoconference. For example, a videoconference may involve participants from a research and development organization who are located in both Corvallis,

Oregon and Fort Collins, Colorado, and the participants located in Corvallis may gather in a common room in Corvallis to participate in the videoconference while the participants located in Fort Collins similarly may gather in a common room in

Fort Collins to participate in the videoconference. In some cases, these rooms may be dedicated videoconference studios having multiple large-screen, high- definition display devices and sophisticated acoustical systems designed to provide a life-like and immersive experience. Alternatively, these rooms may be general purpose meeting rooms or the like in which sufficient computing, audio, and video equipment is available in order to engage in a videoconference.

[0007] A videoconference generally may involve the exchange of A V streams between electronic devices at the different participating locations, thereby enabling participants at different locations to hear and see one another. In addition to the exchange of the participant A V streams that enable the participants to see and hear one another, the overall meeting also may benefit from the participants being connected to additional network resources that enable the participants to share content (e.g., documents including spreadsheets, charts, and slide decks, photographs, previously-recorded video, other media, etc.), collaborate (e.g., concurrently edit or annotate documents or other files), and control aspects of the videoconference across their dispersed locations.

[0008] There are many different examples of network resources that enable collaboration and/or the sharing of content between multiple electronic devices concurrently. In some cases, such a resource may be implemented as a virtual room of sorts, and multiple different electronic devices can log into or otherwise access the virtual room concurrently. When multiple different electronic devices are logged into the virtual room at the same time, a common interface (with the exception, perhaps, of some device-specific or personal configurations) may be provided to each electronic device such that the same content may be viewable at each electronic device. In addition, one or more of the devices may be granted control of the shared content such that these devices are able to control the display of the shared content and/or edit the shared content. When multiple electronic devices are granted control of the shared content concurrently, multiple electronic devices may be able to control the display of the shared content and or edit the shared content concurrently. For example, one electronic device may control the portion of the content that is displayed while a second electronic device concurrently edits the shared content. Additionally or alternatively, two or more electronic devices may edit the shared content concurrently.

[0009] In some cases, rooms in which participants gather together to engage in a videoconference may be equipped with devices and other resources that enable sharing, collaboration, and videoconference control. However, participants who gather in these rooms for the purpose of participating in a videoconference also may bring with them various different types of network-ready electronic devices (e.g., laptop or notebook computers, tablet computers, netbook computers, smartphones, personal digital assistants, etc.) that they desire to be able to use to connect to and interact with the network-available resources for sharing, collaborating, and/or videoconference control. In order to facilitate this, local networks may be established for these rooms and configured such that, when a new user device connects to the local network for one of the rooms, the new user device automatically is redirected to the network-available resources, for example, without requiring advance knowledge of the network address(es) or even existence of such resources).

[0010] FIGS. 1A-1C are a series of diagrams of an example of a videoconference endpoint 100 that provide an illustration of an example of a user device being redirected to a network-available resource upon connection to a local network corresponding to the videoconference endpoint 100. As illustrated in FIGS. 1A-1C, the videoconference endpoint 100 includes a table 102 and chairs 104 for use by videoconference participants 106 while participating in a videoconference at the videoconference endpoint 100. In addition, the videoconference endpoint 100 includes display devices 108 to display video streams of videoconference participants participating in a videoconference from one or more remote locations, and cameras 110 to capture video streams of participants 106 participating in a videoconference at the videoconference endpoint 100 to transmit to one or more remote locations also participating in a videoconference. [0011] Depending on the number of different locations participating in the videoconference, each of the display devices 108 may display a video stream from a different location. For example, if endpoint 100 is located in Corvallis, and participants from Fort Collins, Marlboro, Massachusetts, and Palo Alto, California also are participating in the videoconference, display device 106(a) may display a video stream of participants from Fort Collins, display device 106(b) may display a video stream of participants from Marlboro, and display device 106(c) may display a video stream of participants from Palo Alto. Alternatively, if there are only two locations participating in the videoconference (e.g., endpoint 100 in Corvallis and Fort Collins), each of the display devices 108 may display a different video stream of different participants from Fort Collins.

[0012] The videoconference endpoint 100 also includes another display device 112 to display, among other possibilities, an interface including controls for manipulating different aspects of a videoconference at endpoint 100 (e.g., inviting other endpoints to join a videoconference, adjusting A/V quality for a videoconference, adjusting environmental aspects of the videoconference endpoint 100 such as lighting or temperature) and/or shared content or some other form of a collaboration resource that is shared across different locations participating in a videoconference.

[0013] For example, as illustrated in FIGS. 1A-1C, display device 112 is displaying an interface for a web conferencing collaboration room 114 that enables multiple different participants to log into the collaboration room and view and share content with one another. In the specific example illustrated in FIGS. 1A-1C, the interface for the web conferencing collaboration room 114 includes a pane 116 for listing the occupants who are logged into the collaboration room, a pane 118 for listing content that has been uploaded to the collaboration room for sharing with the occupants of the collaboration room, and a pane 120 for displaying some or all of the shared content uploaded to the collaboration room, for instance, in this example, a historical stock price chart. [0014] Supplementing the videoconference participant A/V streams with access to a shared and or collaborative resource such as the web conferencing collaboration room 114 illustrated in FIGS. 1A-1C may enable a more productive meeting than might be possible through the exchange of videoconference participant A V streams alone. Various different shared and/or collaboration resources can be used to supplement a videoconference in this manner. However, two specific examples of web conferencing collaboration rooms are Hewlett-Packard Co.'s Virtual Room product and Cisco Systems, Inc.'s WebEx product.

[0015] Due to the fact that display device 112 primarily is intended to display content that is other than video streams of participants in a videoconference including, for example, shared and/or collaborative content, display device 112 may be referred to variously as a secondary display device or a collaboration display device.

[0016] In addition to displays 108 and 112 and cameras 110, videoconference endpoint 100 also may include one or more loudspeakers (not shown) to render audio streams from videoconference participants participating in a videoconference from one or more remote locations and one or more microphones (not shown) to capture audio streams of videoconference participants participating in a videoconference at the videoconference endpoint 100 to transmit to one or more remote locations also participating in a videoconference.

[0017] In addition, network jacks 122 (e.g., Ethernet jacks) are available at videoconference endpoint 100 to enable videoconference participants 106 at videoconference endpoint 100 to connect electronic devices (e.g., laptop or notebook computers, tablet computers, netbook computers, smartphones, personal digital assistants, etc.) to a local network corresponding to videoconference endpoint 100 via a hardwired connection (e.g., an Ethernet cable). Although not shown in FIGS. 1A- 1C, wireless network connectivity additionally or alternatively may be available at videoconference endpoint 100 to enable videoconference participants 106 to wirelessly connect electronic devices to a local network corresponding to videoconference endpoint 100.

[0018] Enabling videoconference participants 106 at videoconference endpoint 100 to achieve network connectivity in this manner may enable the videoconference participants to access a network-available shared and/or collaborative resource that is being shared across different locations participating in a videoconference from personal electronic devices that they carry with them into the room. For instance, in the specific example illustrated in FIGS. 1A-1C, such network connectivity may enable videoconference participants 106 at videoconference endpoint 100 to access the web conference collaboration room 114 displayed on secondary display 112 from their own personal electronic devices in addition or as an alternative to relying on secondary display 112.

[0019] Referring now specifically to FIG. 1A, a videoconference involving videoconference endpoint 100 is in progress. Videoconference participant 106(a) is interacting with videoconference participants 124 at one or more remote locations who are displayed on display devices 106 while videoconference participant 106(b) is walking into the room to join the videoconference with a laptop 126 in hand. In addition, endpoint 100 is logged into a web conference collaboration room corresponding to the ongoing videoconference, and display device 112 is displaying an interface for the web conference collaboration room 114 that indicates that videoconference endpoint 100 and three other videoconference endpoints are logged into the web conference collaboration room 114 along with two other individuals who may be participants in the videoconference.

[0020] Referring now to FIG. 1B, videoconference participant 106(b) has taken a seat at table 102 and connected his laptop 126 to a local network corresponding to videoconference endpoint 100 by plugging an Ethernet cable 130 connected to laptop 126 into network jack 122. In addition, upon videoconference participant 106(b)'s opening of an Internet browser on his laptop 126 and attempting to navigate to a web page after having connected his laptop 126 to the local network corresponding to videoconference endpoint 100, the laptop 126 automatically is redirected (e.g., by a captive portal) to an alternative destination from which it is possible for videoconference participant 106(b) to log into the web conference collaboration room corresponding to the on-going videoconference and for which the interface 114 is displayed on display device 112. In particular, in the specific example illustrated in FIG. 1B, laptop 126 has been redirected to a landing page that enables videoconference participant 106(b) to log laptop 126 into the web conference collaboration room by selecting a selectable link 132.

[0021] Referring now to FIG. 1C, in response to selection of selectable link 132 by videoconference participant 106(b), laptop 126 has been logged into the web conference collaboration room such that the interface for the web conference collaboration room 114 now is displayed on both display device 112 and laptop 126. In addition, the interface for the web conference collaboration room 114 has been updated to indicate that a new occupant has entered the web conference collaboration room to reflect that videoconference participant 106(b) logged into the web conference collaboration room with laptop 126.

[0022] By virtue of having logged into the web conference collaboration room with his own laptop 126, videoconference participant 106(b) may be provided with more fine-grained or effective interaction with the content being shared by the different videoconference participants than otherwise may have been possible. In addition, because videoconference participant 106(b)'s laptop 126 automatically was redirected to the web conference collaboration room upon videoconference participant 106(b) connecting the laptop to the local network corresponding to videoconference endpoint 100, opening a web browser, and attempting to navigate to a web page, videoconference participant 106(b) was able to log into the web conference collaboration room without necessarily having prior knowledge of the network address (e.g., uniform resource locator (URL)) for the web conference collaboration room, other identifying or log-in information for the web conference collaboration room, or even the existence of the web conference collaboration room. [0023] FIG. 2A is a block diagram of an example of a communications system 200. For illustrative purposes, several elements illustrated in FIG. 2A and described below are represented as monolithic entities. However, these elements each may include and/or be implemented on numerous interconnected computing devices and/or other components that are designed to perform a set of specified operations.

[0024] As illustrated in FIG. 2A, the communications system 200 includes a first network node 202 that defines a first local network 204 and a second network node 206 that defines a second local network 208. Each of network nodes 202 and 206 may be, for example, a network switch, a network gateway, a router, a wireless access point (WAP), or some hybrid combination thereof. Electronic devices 210 on local network 204 are communicatively connected to network node 202 by network links 212, each of which may be a wired (e.g., Ethernet) connection, a wireless connection (e.g., based on the IEEE 802.11 specification), or some combination of a wired and a wireless connection. Moreover, network node 202 operates as an interface between electronic devices 210 on local network 204 and other networks external to local network 204. In this manner, by separating local network 204 from other networks, network node 202 may be said to define local network 204. Although network node 202 is illustrated in FIG. 2A as being the only interface between devices 210 on local network 204 and other networks, in some implementations, there may be multiple different interfaces (e.g., network nodes) between devices 210 on local network 204 and one or more other networks.

[0025] Network node 202 and/or local network 204 may be said to correspond to Local Environment A 214. For example, in some implementations, Local Environment A may be a dedicated videoconference studio or a conference room outfitted with videoconference equipment, and network node 202 may be located within or in close proximity to such dedicated studio or conference room to provide devices (e.g., electronic devices 210) within such dedicated studio or conference room with local and/or external network access. In such implementations, in addition to providing network access to devices like electronic devices 210, network node 202 also may provide network access to the videoconference equipment (e.g., display devices, loudspeakers, codecs, local multipoint control unit (MCU) resources, other videoconference computing equipment, etc.). In other implementations, Local Environment A 214 may include a number of commonly-located rooms, and network node 202 may be located within one or in close proximity to one or more of such commonly-located conference rooms to provide devices within such commonly- located conference rooms with local and/or external network access. Alternatively, Local Environment A 214 may correspond to one or more commonly-located cubicles or some other area designated, either explicitly or implicitly, as being available for or dedicated to some common purpose.

[0026] As such, a unifying feature of Local Environment A 214 may be that network node 202 is located within or in close proximity to Local Environment A 214 and is available to provide devices in Local Environment A 214 with local and/or external network access. Thus, as users move into Local Environment A 214 with one or more electronic devices (e.g., electronic devices 210), these devices may gain local and/or external network access by communicatively connecting to network node 202. For example, if Local Environment A 214 is a dedicated videoconference studio or a conference room outfitted with videoconference equipment, network node 202 may be available to provide local and/or external network access to devices that users who gather within the studio or conference room for the purpose of participating in a videoconference bring with them into the studio or conference room. Continuing with this example, electronic devices 210 may represent devices that users who have gathered in Local Environment A 214 have brought with them into Local Environment A 214 and that have been communicatively connected to network node 202 by network links 212 for the purpose of acquiring local and/or external network connectivity while located within Local Environment A 214.

[0027] Similarly to electronic devices 210 on local network 204, electronic devices 216 on local network 208 are communicatively connected to network node 206 by network links 218, each of which may be a wired (e.g., Ethernet) connection, a wireless connection (e.g., based on the IEEE 802.11 specification), or some combination of a wired and a wireless connection. Moreover, network node 206 operates as an interface between electronic devices 216 on local network 208 and other networks external to local network 208. In this manner, by separating local network 208 from other networks, network node 206 may be said to define local network 208. Although network node 206 is illustrated in FIG. 2A as being the only interface between devices 216 on local network 208 and other networks, in some implementations, there may be multiple different interfaces (e.g., network nodes) between devices 216 on local network 208 and one or more other networks.

[0028] Network node 206 and/or local network 208 may be said to correspond to Local Environment B 220. For example, in some implementations, Local Environment B 220 may be a dedicated videoconference studio or a conference room outfitted with videoconference equipment, and network node 206 may be located within or in close proximity to such dedicated studio or conference room to provide devices (e.g., electronic devices 216) within such dedicated studio or conference room with local and/or external network access. In such implementations, in addition to providing network access to devices like electronic devices 216, network node 206 also may provide network access to the videoconference equipment (e.g., display devices, loudspeakers, codecs, local MCU resources, other videoconference computing equipment, etc.). In other implementations, Local Environment B 220 may include a number of commonly-located rooms and network node 206 may be located within one or in close proximity to one or more of such commonly-located conference rooms to provide devices within such commonly-located conference rooms with local and/or external network access. Alternatively, Local Environment B 220 may correspond to one or more commonly-located cubicles or some other area designated, either explicitly or implicitly, as being available for or dedicated to some common purpose. [0029] As such, a unifying feature of Local Environment B 220 may be that network node 206 is located within or in close proximity to Local Environment B 220 and is available to provide devices in Local Environment B 220 with local and/or external network access. Thus, as users move into Local Environment B 220 with one or more electronic devices (e.g., electronic devices 216), these devices may gain local and/or external network access by communicatively connecting to network node 206. For example, if Local Environment B 220 is a dedicated videoconference studio or a conference room outfitted with videoconference equipment, network node 206 may be available to provide local and/or external network access to devices that users who gather within the studio or conference room for the purpose of participating in a videoconference bring with them into the studio or conference room. Continuing with this example, electronic devices 216 may represent devices that users who have gathered in Local Environment B 220 have brought with them into Local Environment B 220 and that have been communicatively connected to network node 206 by network links 218 for the purpose of acquiring local and/or external network connectivity while located within Local Environment B 220.

[0030] Network nodes 202 and 206 both are communicatively connected to network 222. Consequently, by virtue of their communicative connection to network node 202 via network links 212, electronic devices 210 also have access to network 222. Similarly, by virtue of their communicative connection to network node 206 via network links 218, electronic devices 216 also have access to network 222. Examples of network 222 include the Internet, the World Wide Web, wide area networks (WANs) including corporate intranets, local area networks (LANs) including wireless LANs (WLANs), analog or digital wired or wireless telephone networks, radio, television, cable, satellite, and/or any other delivery mechanisms for carrying data, or any combinations thereof.

[0031] As described above, in some implementations, Local Environment A 214 may correspond to a videoconference environment that is outfitted with videoconference equipment providing functionality for conducting vkJeoconferences with remote sites and where multiple people may gather for the purpose of engaging in a videoconference employing the videoconference equipment provided within Local Environment A 214. For instance, Local Environment A 214 may be a dedicated videoconference studio such as, for example, the videooonference endpoint 100 illustrated in FIGS. 1A-1C.

[0032] In such implementations where Local Environment A 214 corresponds to a videoconference environment outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment A 214 may be communicatively coupled to network node 202, which may provide an interface between local network 204 and network 222, thereby enabling the videoconference equipment at Local Environment A 214 to connect with and facilitate videoconferences with other videoconference equipment communicatively connected to network 222. Additionally or alternatively, some or all of the videoconference equipment at Local Environment A 214 may not reside on local network 204 and may be communicatively connected to network 222 via one or more network nodes other than network node 202.

[0033] Similarly, Local Environment B 220 also may correspond to a videoconference environment that is outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites and where multiple people may gather for the purpose of engaging in a videoconference employing the videoconference equipment provided within Local Environment B 220. For instance, Local Environment B 220 may be a dedicated videoconference studio such as, for example, the videoconference endpoint 100 illustrated in FIGS. 1A-1C.

[0034] In such implementations where Local Environment B 220 corresponds to a videoconference environment outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment B 220 may be communicatively coupled to network node 206, which may provide an interface between local network 208 and network 222, thereby enabling the videoconference equipment at Local Environment B 220 to connect with and facilitate videoconferences with other videoconference equipment communicatively connected to network 222. Additionally or alternatively, some or all of the videoconference equipment at Local Environment B 220 may not reside on local network 208 and may be communicatively connected to network 222 via one or more network nodes other than network node 206.

[0035] When Local Environment A 214 and Local Environment B 220 both correspond to videoconference environments and are outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment A 214 and the videoconference equipment at Local Environment B 220 may be communicatively connected across network 222 and employed to conduct videoconferences between participants gathered at Local Environment A 214 and Local Environment B 220. In such implementations, in addition to the videoconference equipment located at Local Environment A 214 and Local Environment B 220, videoconference management system 224, also communicatively connected to network 222, also may facilitate a videoconference between participants gathered at Local Environment A 214 and participants gathered at Local Environment B 220.

[0036] Videoconference management system 224 may be implemented as one or more computing devices (e.g., servers) configured to provide videoconference management services to videoconference endpoints connected to videoconference management system 224 over network 222. The one or more computing devices on which videoconference management system 224 is implemented may have internal or external storage components storing data and programs such as an operating system and one or more application programs, for example, videoconferencing management applications. Although videoconference management system 224 is illustrated in FIG. 2A as being a centralized or remote system, in some implementations, videoconference management system 224 may be implemented in a distributed fashion across various different endpoints of a videoconferencing system. [0037] Among other features, videoconferenoe management system 224 may facilitate the scheduling and initiation of videoconferences between different endpoints, and videoconference management system 224 may include a computer- readable storage system 226 storing meeting data that includes information about scheduled and/or on-going videoconferences. For example, the meeting data stored in computer-readable storage system 226 may include a schedule of videoconferences that records, among other data, information about the different endpoints and/or participants scheduled to participate in the scheduled videoconferences. In addition, the meeting data stored in computer-readable storage system 226 also may include information about on-going videoconferences even if such meetings were not scheduled in advance. For example, if an ad hoc videoconference is initiated between various different endpoints without any advance scheduling, information about the ad hoc videoconference, including the videoconference endpoints and or participants involved, may be added to the meeting data stored in computer-readable storage system 226. As such, if a videoconference between Local Environment A 214 and Local Environment B 220 is taking place, information about the videoconference, including the fact that it involves Local Environment A 214 and Local Environment B 220, may be included within the meeting data stored in computer-readable storage system 226 irrespective of whether the videoconference was scheduled in advance.

[0038] In addition to exchanging A V videoconference streams between the videoconference equipment at Local Environment A 214 and the videoconference equipment at Local Environment B 220, participants gathered at Local Environment A 214 and Local Environment B 220 taking part in a videoconference involving Local Environment A 214 and Local Environment B 220 also may access a collaboration resource 228 that enables sharing of content between network connected devices and or collaboration between network connected devices (e.g., collaborative editing and/or annotation of content) and that also is communicatively connected to network 222. For example, electronic devices 210 at Local Environment A 214 may access collaboration resource 228 over network 222 via their communicative connection to network node 202. Similarly, electronic devices 216 at Local Environment B 220 likewise may access collaboration resource 228 over network 222 via their connection to network node 206.

[0039] Collaboration resource 228 may be implemented on one or more computing devices (e.g., servers) configured to provide collaboration tools to client devices connected to collaboration resource 228 over network 222. The one or more computing devices on which collaboration resource 228 is implemented may have internal or external storage components storing data and programs such as an operating system and one or more application programs, for example, providing collaboration tools. Furthermore, collaboration resource 228 may be one of multiple collaboration resources provided by a collaboration resource service provider. For example, collaboration resource 228 may be a web conferencing collaboration room offered by a web conferencing collaboration room service provider who provides and maintains multiple web conferencing collaboration rooms. In such implementations, certain identifying information (e.g., a meeting ID, one or more keys corresponding and/or unique to the specific web conferencing collaboration room represented by collaboration resource 228, a network address (URL) for the web conferencing collaboration room represented by collaboration resource 228, etc.) may be used to specifically identify the specific web conferencing collaboration room represented by collaboration resource 228 from among other web conferencing collaboration rooms.

[0040] In some implementations, collaboration resource 228 may be associated specifically with the videoconference involving Local Environment A 214 and Local Environment B 220. Furthermore, the existence of this relationship between collaboration resource 228 and the videoconference involving Local Environment A 214 and Local Environment B 220 may be recorded in the meeting data stored in the computer-readable storage system 226 of videoconference management system 224. For example, if the videoconference involving Local Environment A 214 and Local Environment B 220 was prescheduled with videoconference management system 224, as part of the scheduling process, the fact that collaboration resource 228 was intended to be used by participants to supplement the scheduled videoconference may be recorded in the meeting data stored in computer-readable storage system 226.

[0041] Alternatively, if the videoconference involving Local Environment A 214 and Local Environment B 220 was initiated in an ad hoc manner, the existence of an on-going videoconference involving Local Environment A 214 and Local Environment B 220 may be recorded in the meeting data stored in computer-readable storage system 226 as part of the process of initiating the videoconference involving Local Environment A 214 and Local Environment B 220. In addition, at some point during the videoconference (e.g., as part of initiating the ad hoc videoconference), the relationship between the collaboration resource 228 and the on-going videoconference may be communicated to videoconference management system 224 and recorded in the meeting data stored in computer-readable storage system 226.

[0042] Network node 202 may be configured to facilitate access to collaboration resource 228 by one or more of electronic devices 210 at Local Environment A 214. For instance, continuing with the example of the videoconference involving Local Environment A 214 and Local Environment B 220, electronic devices 210 may represent electronic devices that participants in the videoconference who gathered in Local Environment A 214 brought with them into Local Environment A 214, and network node 202 may facilitate the process of connecting the electronic devices 210 that the gathered participants brought with them into Local Environment A 214 to collaboration resource 228. Similarly, electronic devices 216 may represent electronic devices that participants in the videoconference who gathered in Local Environment B 220 brought with them into Local Environment B 220, and network node 206 may facilitate the process of connecting the electronic devices 216 that the gathered participants brought with them into Local Environment B 220 to collaboration resource 228.

[0043] In one specific example, when one of electronic devices 210 (e.g., electronic device 210(c)) is connected to network node 202, network node 202 may be configured to block some or all packets emanating from electronic device 210(c) (irrespective of the packets' destination address or port) until a Web browser executing on the electronic device 210(c) initiates an HTTP request for access to a network resource. Thereafter, upon receipt of an HTTP request for access to a network resource from the browser executing on the electronic device 210(c), irrespective of the network resource to which electronic device 210(c) is requesting access, network node 202 automatically may redirect the browser executing on the electronic device 210(c) to a redirect destination 234, which also is communicatively connected to network 222 and which provides access to collaboration resource 228.

[0044] Redirect destination 234 may be implemented on one or more computing devices (e.g., servers) that are accessible over network 222. In some implementations, redirect destination 234 may be a log-in web page for a web conferencing tool that provides access to multiple different collaboration resources (e.g., web conference collaboration rooms) including collaboration resource 228 (e.g., a particular web conference collaboration room provided by the web conferencing tool). As such, collaboration resource 228 and redirect destination 234 may be implemented across one or more common computing devices operated by or otherwise associated with the provider of a collaboration service. Alternatively, redirect destination 234 may be a web page that requests confirmation from a user of a redirected device that the user desires to access collaboration resource 228. For example, redirect destination 234 may be a web page that communicates that collaboration resource 228 is available and provides a selectable link for accessing collaboration resource 228 in the event that a user desires to access collaboration resource 228. In the event that a user is not interested in accessing collaboration resource 228, the user may be able to access alternative resources, for example, by using a Web browser to navigate away from redirect destination 234.

[0045] In implementations in which redirect destination 234 is a log-in web page for a web conferencing tool, as part of redirecting the browser executing on the electronic device 210(c) to redirect destination 234, network node 202 also may cause log-in information requested by redirect destination 234 for accessing collaboration resource 228 to be pre-populated in the appropriate fields within the login web page. In order to determine the appropriate log-in information to pre-populate in this manner, network node 202 may consult videoconference management system 224, which, based on the record of the relationship between collaboration resource 228 and the videoconference involving Local Environment A 214 and Local Environment B 220 maintained in the meeting data stored in computer-readable storage system 226, may inform network node 202 that collaboration resource 228 is associated with the videoconference and is intended to be used by participants to supplement the videoconference. In addition, videoconference management system 224 may provide network node 202 with specific log-in information for accessing collaboration resource 228 through redirect destination 234. For instance, in some cases, redirect destination 234 may request a meeting ID and or one or more keys specifically associated with collaboration resource before granting access to collaboration resource 228. In such cases, videoconference management system 224 may provide the meeting ID and/or one or more keys to network node 202, thereby enabling network node 202 to pre-populate these keys upon redirecting the browser executing on electronic device 210 to redirect destination 234.

[0046] Similarly, when one of electronic devices 216 (e.g., electronic device 216(a)) is connected to network node 206, network node 206 may be configured to block some or all packets emanating from electronic device 216(a) (irrespective of the packet's destination address or port) until a Web browser executing on the electronic device 216(a) initiates an HTTP request for access to a network resource. Thereafter, upon receipt of an HTTP request for access to a network resource from the browser executing on the electronic device 216(a), irrespective of the network resource to which electronic device 216(a) is requesting access, network node 206 automatically may redirect the browser executing on the electronic device 216(a) to redirect destination 234. As described above in connection with the automatic redirection by network node 202 of the browser executing on electronic device 210(c) to redirect destination 234, as part of redirecting the browser executing on the electronic device 216(a) to redirect destination 234, network node 206 also may cause log-in information requested by redirect destination 234 for accessing collaboration resource 228 to be pre-populated in the appropriate fields within the login web page. As also described above in connection with the automatic redirection by network node 202 of the browser executing on electronic device 210(c) to redirect destination 234, network node 206 may consult videoconference management system 224 in order to determine the appropriate log-in information to pre-populate in this manner.

[0047] A specific example of a process by which network node 202 facilitates access to collaboration resource 228 by electronic device 210(c) is now described. As illustrated in FIG. 2A, a communicative connection is established between electronic device 210(c) and network node 202 over a network link 212. This communicative connection between electronic device 210(c) and network node 202 may be established responsive to a user of electronic device 210(c) desiring to use electronic device 210(c) to access one or more network-available resources. For example, the communicative connection may be established as a consequence of the user of electronic device 210(c) connecting an Ethernet cable that provides access to network node 202 to electronic device 210(c). Alternatively, the communicative connection may be established as a consequence of an application executing on electronic device 210(c) initiating a wireless connection with network node 202 with or without manual involvement from the user of electronic device 210(c).

[0048] Following the establishment of the communicative connection between electronic device 210(c) and network node 202, electronic device 210(c) may transmit packets to network node 202, and network node 202 may block some or all packets received from electronic device 210(c) (irrespective of the packet's destination addresses) or port(s)) until network node 202 receives an HTTP request for access to a network resource, illustrated by small dashed line 1A. For example, network node 202 may receive an HTTP request for access to a network resource from electronic device 210(c) as a consequence of a user of electronic device 210(c) using a Web browser to attempt to navigate to a Web page or, alternatively, as a consequence of a user of electronic device 210(c) launching a Web browser on electronic device 210(c), and the Web browser on electronic device 210(c) then attempting to load a designated "Home" Web page.

[0049] In any event, when network node 202 receives the HTTP request illustrated by small dashed line 1A from electronic device 210(c), network node 202 intercepts the request and, as illustrated by small dashed line 2A, redirects electronic device 210(c) to redirect destination 234 (e.g., over network 222). In some implementations, network node 202 may consult with videoconference management system 224 to determine the appropriate destination to which to redirect electronic device 210(c). For example, meeting data stored in computer-readable storage system 226 may include a schedule of videoconferences and/or information about ongoing videoconferences as well as records of collaboration resources or other network destinations associated with specific ones of the scheduled and/or ongoing videoconferences. Thus, by consulting with videoconference management system 224, network node 202 may discover that collaboration resource 228 is associated with a videoconference involving Local Environment A 214 and that electronic device 210(c), therefore, is to be redirected to redirection destination 234, which will facilitate access to collaboration resource 228 by electronic device 210(c). In addition, in some implementations, the meeting data stored in computer-readable storage system 226 may include information about individual users and/or devices authorized to access collaboration resource 228. For example, only users or electronic devices known to belong to users who are invitees to the videoconference to which local collaboration resource 228 corresponds may be authorized to access collaboration resource 228. In such implementations, network node 202 may consult with videoconference management system 224 to determine whether a particular electronic device and/or user of the electronic device is authorized to access collaboration resource 228 before redirecting the electronic device and only redirect the electronic device after receiving confirmation from the videoconference management system 224 that the electronic device and/or electronic device user are authorized to access collaboration resource 228.

[0050] Furthermore, network node 202 may employ any of a variety of different techniques to accomplish the redirection of electronic device 210(c) to redirect destination 234. For example, network node 202 may forward the intercepted HTTP request to a redirect server that responds to the forwarded request with an HTTP response including an HTTP status code (e.g., status code 302) that redirects electronic device 210(c) to redirect destination 234, thereby enabling electronic device 210(c) to establish an HTTP session with redirect destination 234. Alternatively, network node 202 may employ Internet protocol (IP) redirection techniques at the Open Systems Interconnection (OSI) Layer 3 level to redirect electronic device 210(c) to redirect destination 234. In other implementations, network node 202 may cause the IP address of redirect destination 234 to be returned to electronic device 210(c) in response to a Domain Name System (DNS) query received from electronic device 210(c).

[0051] As described above, in some implementations, upon establishment of a communicative connection between electronic device 210(c) and network node 202, network node 202 may block packets received from electronic device 210(c) until network node 202 receives an HTTP request for access to a network resource from electronic device 210(c). Then, upon receipt of the HTTP request from electronic device 210(c), network node 202 may redirect electronic device 210(c) to redirect destination 234. However, in other implementations, network node 202 may handle the redirection of electronic device 210(c) to redirect destination 234 differently. For example, after a communicative connection between electronic device 210(c) and network node 202 is established, network node 202 may transmit (or alternatively block) some or all communications received from electronic device 210(c) until a communication of a particular protocol type is received at network node 202 from electronic device 210(c). Receipt of a communication from electronic device 210(c) having the particular prototype at network node 202 may trigger network node 202 to redirect electronic device 210(c) to redirect destination 234. For instance, a particular type of client application that packages outbound communications according to the particular protocol type (e.g., a protocol type unique to the client application) may be installed on electronic device 210(c). Then, when this client application causes electronic device 210(c) to transmit a communication of the particular protocol type to network node 202 (e.g., upon start-up of the client application on electronic device 210(c)), network node 202 may redirect electronic device 210(c) to redirect destination 234 in response to receipt of the communication of the particular protocol type from electronic device 210(c).

[0052] After network node 202 redirects electronic device 210(c) to redirect destination 234, redirect destination 234 then facilitates access to collaboration resource 228 by electronic device 210(c), as illustrated by small dashed line 3A. For example, redirect destination 234 may be a general tog-in page for a number of different collaboration resources, including collaboration resource 228, provided by a service provider. As part of redirecting electronic device 210(c) to redirect destination 234, network node 202 automatically may transfer the log-in information for accessing collaboration resource 228 to redirect destination 234, which, in turn, may use the login information to identify collaboration resource 228 as the specific collaboration resource provided by the service provider to which to grant access to electronic device 210(c).

[0053] Like the specific example of the process by which network node 202 facilitates access to collaboration resource 228 by electronic device 210(c) described above, a specific example of a process by which network node 206 facilitates access to collaboration resource 228 by electronic device 216(a) is now described.

[0054] As illustrated in FIG. 2A, a communicative connection is established between electronic device 216(a) and network node 206 over a network link 218. This communicative connection between electronic device 216(a) and network node 206 may be established responsive to a user of electronic device 216(a) desiring to use electronic device 216(a) to access one or more network-available resources. For example, the communicative connection may be established as a consequence of the user of electronic device 216(a) connecting an Ethernet cable that provides access to network node 206 to electronic device 216(a). Alternatively, the communicative connection may be established as a consequence of an application executing on electronic device 216(a) initiating a wireless connection with network node 206 with or without manual involvement from the user of electronic device 216(a).

[0055] Following the establishment of the communicative connection between electronic device 216(a) and network node 206, electronic device 216(a) may transmit packets to network node 206, and network node 206 may block some or all packets received from electronic device 216(a) (irrespective of the packet's destination address(es) or port(s)) until network node 206 receives an HTTP request for access to a network resource, illustrated by small dashed line 1B. For example, network node 206 may receive an HTTP request for access to a network resource from electronic device 216(a) as a consequence of a user of electronic device 216(a) using a Web browser to attempt to navigate to a Web page or, alternatively, as a consequence of a user of electronic device 216(a) launching a Web browser on electronic device 216(a), and the Web browser on electronic device 216(a) then attempting to load a designated "Home" Web page.

[0056] In any event, when network node 206 receives the HTTP request illustrated by small dashed line 1B from electronic device 216(a), network node 206 intercepts the request and, as illustrated by small dashed line 2B, redirects electronic device 216(a) to redirect destination 234 (e.g., over network 222). In some implementations, network node 206 may consult with videoconference management system 224 to determine the appropriate destination to which to redirect electronic device 216(a). For example, meeting data stored in computer-readable storage system 226 may include a schedule of videoconferences and/or information about ongoing videoconferences as well as records of collaboration resources or other network destinations associated with specific ones of the scheduled and/or ongoing videoconferences. Thus, by consulting with videoconference management system 224, network node 206 may discover that collaboration resource 228 is associated with a videoconference involving Local Environment B 220 and that electronic device 216(a), therefore, is to be redirected to redirection destination 234, which will facilitate access to collaboration resource 228 by electronic device 216(a). In addition, as discussed above, in some implementations, the meeting data stored in computer- readable storage system 226 may include information about individual users and/or devices authorized to access collaboration resource 228. In such implementations, network node 206 may consult with videoconference management system 224 to determine whether a particular electronic device and/or user of the electronic device is authorized to access collaboration resource 228 before redirecting the electronic device and only redirect the electronic device after receiving confirmation from the videoconference management system 224 that the electronic device and/or electronic device user are authorized to access collaboration resource 228.

[0057] Furthermore, network node 206 may employ any of a variety of different techniques to accomplish the redirection of electronic device 216(a) to redirect destination 234. For example, network node 206 may forward the intercepted HTTP request to a redirect server that responds to the forwarded request with an HTTP response including an HTTP status code (e.g., status code 302) that redirects electronic device 216(a) to redirect destination 234, thereby enabling electronic device 216(a) to establish an HTTP session with redirect destination 234. Alternatively, network node 206 may employ IP redirection techniques at the OSI Layer 3 level to redirect electronic device 216(a) to redirect destination 234. In other implementations, network node 206 may cause the IP address of redirect destination 234 to be returned to electronic device 216(a) in response to a DNS query received from electronic device 216(a).

[0058] As described above, in some implementations, upon establishment of a communicative connection between electronic device 216(a) and network node 206, network node 206 may block packets received from electronic device 216(a) until network node 206 receives an HTTP request for access to a network resource from electronic device 216(a). Then, upon receipt of the HTTP request from electronic device 216(a), network node 206 may redirect electronic device 216(a) to redirect destination 234. However, in other implementations, network node 206 may handle the redirection of electronic device 216(a) to redirect destination 234 differently. For example, after a communicative connection between electronic device 216(a) and network node 206 is established, network node 206 may transmit (or alternatively block) some or all communications received from electronic device 216(a) until a communication of a particular protocol type is received at network node 206 from electronic device 216(a). Receipt of a communication from electronic device 216(a) having the particular prototype at network node 206 may trigger network node 206 to redirect electronic device 216(a) to redirect destination 234. For instance, a particular type of client application that packages outbound communications according to the particular protocol type (e.g., a protocol type unique to the client application) may be installed on electronic device 216(a). Then, when this client application causes electronic device 216(a) to transmit a communication of the particular protocol type to network node 206 (e.g., upon start-up of the client application on electronic device 216(a)), network node 206 may redirect electronic device 216(a) to redirect destination 234 in response to receipt of the communication of the particular protocol type from electronic device 216(a).

[0059] After network node 206 redirects electronic device 216(a) to redirect destination 234, redirect destination 234 then facilitates access to collaboration resource 228 by electronic device 216(a), as illustrated by small dashed line 3B. For example, redirect destination 234 may be a general log-in page for a number of different collaboration resources, including collaboration resource 228, provided by a service provider. As part of redirecting electronic device 216(a) to redirect destination 234, network node 206 automatically may transfer the log-in information for accessing collaboration resource 228 to redirect destination 234, which, in turn, may use the login information to identify collaboration resource 228 as the specific collaboration resource provided by the service provider to which to grant access to electronic device 216(a).

[0060] By facilitating access to collaboration resource 228 by one or more of electronic devices 210 at Local Environment A 214 and one or more of electronic devices at Local Environment B 220 as described above, network node 202 and network node 206, respectively, may enable users of electronic devices 210 and electronic devices 216 who have gathered in Local Environment A 214 and Local Environment B to access collaboration resource 228 without having prior knowledge of information for accessing collaboration resource 228 (e.g., a meeting ID, log-in key(s), network address (URL), etc.) or even the existence of collaboration resource 228.

[0061] As illustrated in FIG. 2A, electronic devices 210(a) and 216(a) are laptop or notebook computers, electronic devices 210(b) and 216(b) are tablet computers, and electronic devices 210(c) and 216(c) are smartphones. However, network nodes 202 and 206 may be configured to enable communicative connections with any of a variety of different types of electronic devices in addition to laptop or notebook computers, tablet computers, and smartphones, including, for example, among other electronic devices, netbook computers, personal digital assistants, and desktop computers.

[0062] FIG. 2B is a block diagram of another example of a communications system 250. For illustrative purposes, several elements illustrated in FIG. 2B and described below are represented as monolithic entities. However, these elements each may include and/or be implemented on numerous interconnected computing devices and/or other components that are designed to perform a set of specified operations.

[0063] As illustrated in FIG. 2B, the communications system 250 includes a first network node 252 that defines a first local network 254 and a second network node 256 that defines a second local network 258. Each of network nodes 252 and 256 may be, for example, a network switch, a network gateway, a router, a WAP, or some hybrid combination thereof. Electronic device 260 on local network 254 is communicatively connected to network node 252 by network link 262, which may be a wired (e.g., Ethernet) connection, a wireless (e.g., based on the IEEE 802.11 specification) connection, or some combination of a wired and a wireless connection. Moreover, network node 252 operates as an interface between electronic device 260 on local network 254 and networks external to local network 254. In this manner, by separating local network 254 from other networks, network node 252 may be said to define local network 254. Although network node 252 is illustrated in FIG. 2B as being the only interface between devices on local network 254 and other networks, in some implementations, there may be multiple different interfaces (e.g., network nodes) between devices on local network 254 and one or more other networks.

[0064] Network node 252 and/or local network 254 may be said to correspond to Local Environment A 264. For example, in some implementations, Local Environment A 264 may be a dedicated videoconference studio or a conference room outfitted with videoconference equipment, and network node 252 may be located within or in close proximity to such dedicated studio or conference room to provide devices (e.g., electronic device 260) within such dedicated studio or conference room with local and/or external network access. In such implementations, in addition to providing network access to devices like electronic device 260, network node 252 also may provide network access to the videoconference equipment (e.g., display devices, loudspeakers, codecs, local MCU resources, other videoconference computing equipment, etc.). In other implementations, Local Environment A 264 may include a number of commonly-located rooms, and network node 252 may be located within one or in close proximity to one or more of such commonly-located conference rooms to provide devices within such commonly-located conference rooms with local and/or external network access. Alternatively, Local Environment A 264 may correspond to one or more commonly-located cubicles or some other area designated, either explicitly or implicitly, as being available for or dedicated to some common purpose.

[0065] As such, a unifying feature of Local Environment A 264 may be that network node 252 is located within or in close proximity to Local Environment A 264 and is available to provide devices in Local Environment A 264 with local and/or external network access. Thus, as users move into Local Environment A 264 with one or more electronic devices (e.g., electronic device 260), these devices may gain local and/or external network access by communicatively connecting to network node 252. For example, if Local Environment A 264 is a dedicated videoconference studio or a conference room outfitted with videoconference equipment, network node 252 may be available to provide local and/or external network access to devices that users who gather within the studio or conference room for the purpose of participating in a videoconference bring with them into the studio or conference room. Continuing with this example, electronic device 260 may represent a device that a user who came to Local Environment A 264 brought with him into Local Environment A 264 and that has been communicatively connected to network node 252 by network link 262 for the purpose of acquiring local and/or external network connectivity while located within Local Environment A 264.

[0066] As illustrated in FIG. 2B, local collaboration resource 266 and local redirect destination 268 also may reside on local network 254 being communicatively connected to network node 252 by network links 262. Consequently, local collaboration resource 266 may be said to correspond to or be associated with Local Environment A 264 and/or local network 254. Among other features, local collaboration resource 266 may enable sharing of content between electronic devices that concurrently access local collaboration resource 266 (e.g., electronic devices on local network 254 that access local collaboration resource 266 via network node 252) and/or collaboration (e.g., collaborative editing and or annotation of content) between electronic devices that concurrently access local collaboration resource 266 (e.g., electronic devices on local network 254 that access local collaboration resource 266 via network node 252). Consequently, users who gather in Local Environment A 264 and bring electronic devices with them into Local Environment A 264 may be able to use such electronic devices to access local collaboration resource 266 to share content and/or collaborate.

[0067] Local collaboration resource 266 may be implemented on one or more computing devices (e.g., servers) configured to provide collaboration tools to client devices connected to local collaboration resource 266 (e.g., over local network 254). The one or more computing devices on which local collaboration resource 266 is implemented may have internal or external storage components storing data and programs such as an operating system and one or more application programs, for example, providing collaboration tools. Furthermore, local collaboration resource 266 may be one of multiple local collaboration resources provided by a local collaboration application. For example, local collaboration resource 266 may be a web conferencing collaboration room provided by a local web conferencing application that provides and maintains multiple web conferencing collaboration rooms.

[0068] Network node 262 may be configured to facilitate access to local collaboration resource 266 by one or more electronic devices at Local Environment A 264 and on local network 254, for example, electronic device 260. For instance, electronic device 260 may represent an electronic device that a user carried with him into Local Environment A 264, and network node 252 may facilitate the process of connecting electronic device 260 to local collaboration resource 266. As described in greater detail below, in one specific example, when electronic device 260 is connected to network node 252, network node 252 automatically may redirect electronic device 260 to local redirect destination 268, which, in turn, may provide access to local collaboration resource 266. Redirect destination 268 may be implemented on one or more computing devices. In fact, in some implementations, local collaboration resource 266 and local redirect destination 268 may be implemented across one or more common computing devices. Furthermore, one or both of local collaboration resource 266 and local redirect destination 268 may be implemented on network node 252.

[0069] In some implementations, local redirect destination 268 may be a log-in web page for a local web conferencing application that provides access to multiple different collaboration resources (e.g., web conference collaboration rooms) including local collaboration resource 266 (e.g., a particular web conference collaboration room provided by the web conferencing tool). Alternatively, local redirect destination 268 may be a web page that requests confirmation from a user of a redirected device that the user desires to access local collaboration resource 266. For example, local redirect destination 268 may be a web page that communicates that local collaboration resource 266 is available and provides a selectable link for accessing local collaboration resource 266 in the event that a user desires to access local collaboration resource 266. In the event that a user is not interested in accessing local collaboration resource 266, the user may be able to access alternative resources, for example, by using a Web browser to navigate away from local redirect destination 268.

[0070] Similarly to electronic device 260 on local network 254, electronic device 270 on local network 258 is communicatively connected to network node 256 by a network link 272, which may be a wired (e.g., Ethernet) connection, a wireless (e.g., based on the IEEE 802.11 specification) connection, or some combination of a wired and a wireless connection. Moreover, network node 256 operates as an interface between electronic device 270 on local network 258 and other networks external to local network 258. In this manner, by separating local network 258 from other networks, network node 256 may be said to define local network 258. Although network node 256 is illustrated in FIG. 2B as being the only interface between devices on local network 258 and other networks, in some implementations, there may be multiple different interfaces (e.g., network nodes) between devices on local network 258 and one or more other networks.

[0071] Network node 256 and/or local network 258 may be said to correspond to Local Environment B 274. For example, in some implementations, Local Environment B 274 may be a dedicated videoconference studio or a conference room outfitted with videoconference equipment, and network node 256 may be located within or in close proximity to such dedicated studio or conference room to provide devices (e.g., electronic device 270) within such dedicated studio or conference room with local and/or external network access. In such implementations, in addition to providing network access to devices like electronic device 270, network node 256 also may provide network access to the videoconference equipment (e.g., display devices, loudspeakers, codecs, local MCU resources, other videoconference computing equipment, etc.). In other implementations, Local Environment B 274 may include a number of commonly-located rooms and network node 256 may be located within one or in close proximity to one or more of such commonly-located conference rooms to provide devices within such commonly-located conference rooms with local and/or external network access. Alternatively, Local Environment B 274 may correspond to one or more commonly-located cubicles or some other area designated, either explicitly or implicitly, as being available for or dedicated to some common purpose.

[0072] As such, a unifying feature of Local Environment B 274 may be that network node 256 is located within or in close proximity to Local Environment B 274 and is available to provide devices in Local Environment B 274 with local and/or external network access. Thus, as users move into Local Environment B 274 with one or more electronic devices (e.g., electronic device 270), these devices may gain local and/or external network access by communicatively connecting to network node 256. For example, if Local Environment B 274 is a dedicated videoconference studio or a conference room outfitted with videoconference equipment, network node 256 may be available to provide local and/or external network access to devices that users who gather within the studio or conference room for the purpose of participating in a videoconference bring with them into the studio or conference room. Continuing with this example, electronic device 270 may represent a device that a user who came to Local Environment B 274 brought with him into Local Environment B 274 and that has been communicatively connected to network node 256 by a network link 272 for the purpose of acquiring local and/or external network connectivity while located within Local Environment B 274.

[0073] As illustrated in FIG. 2B, local collaboration resource 276 and local redirect destination 278 also may reside on local network 258 being communicatively connected to network node 256 by network links 272. Consequently, local collaboration resource 276 may be said to correspond to or be associated with Local Environment B 274 and/or local network 258. Among other features, local collaboration resource 276 may enable sharing of content between electronic devices that concurrently access local collaboration resource 276 (e.g., electronic devices on local network 258 that access local collaboration resource 276 via network node 256) and or collaboration (e.g., collaborative editing and/or annotation of content) between electronic devices that concurrently access local collaboration resource 276 (e.g., electronic devices on local network 258 that access local collaboration resource 276 via network node 256). Consequently, users who gather in Local Environment B 274 and bring electronic devices with them into Local Environment B 274 may be able to use such electronic devices to access local collaboration resource 276 to share content and or collaborate.

[0074] Local collaboration resource 276 may be implemented on one or more computing devices (e.g., servers) configured to provide collaboration tools to client devices connected to local collaboration resource 276 (e.g., over local network 258). The one or more computing devices on which local collaboration resource 276 is implemented may have internal or external storage components storing data and programs such as an operating system and one or more application programs, for example, providing collaboration tools. Furthermore, local collaboration resource 276 may be one of multiple local collaboration resources provided by a local collaboration application. For example, local collaboration resource 276 may be a web conferencing collaboration room provided by a local web conferencing application that provides and maintains multiple web conferencing collaboration rooms.

[0075] Network node 256 may be configured to facilitate access to local collaboration resource 276 by one or more electronic devices at Local Environment B 274 and on local network 258, for example, electronic device 270. For instance, electronic device 270 may represent an electronic device that a user carried with him into Local Environment B 274, and network node 256 may facilitate the process of connecting electronic device 270 to local collaboration resource 276. As described in greater detail below, in one specific example, when electronic device 270 is connected to network node 256, network node 256 automatically may redirect electronic device 270 to local redirect destination 278, which, in turn, may provide access to local collaboration resource 276. Local redirect destination 278 may be implemented on one or more computing devices. In fact, in some implementations, local collaboration resource 276 and local redirect destination 278 may be implemented across one or more common computing devices. Furthermore, one or both of local collaboration resource 276 and local redirect destination 278 may be implemented on network node 256.

[0076] In some implementations, local redirect destination 278 may be a log-in web page for a local web conferencing application that provides access to multiple different collaboration resources (e.g., web conference collaboration rooms) including local collaboration resource 276 (e.g., a particular web conference collaboration room provided by the web conferencing tool). Alternatively, local redirect destination 278 may be a web page that requests confirmation from a user of a redirected device that the user desires to access local collaboration resource 276. For example, local redirect destination 278 may be a web page that communicates that local collaboration resource 276 is available and provides a selectable link for accessing local collaboration resource 276 in the event that a user desires to access local collaboration resource 276. In the event that a user is not interested in accessing local collaboration resource 276, the user may be able to access alternative resources, for example, by using a Web browser to navigate away from local redirect destination 278.

[0077] Network nodes 252 and 256 both are communicatively connected to network 280. Consequently, by virtue of its communicative connection to network node 252 via network link 262, electronic device 260 also has access to network 280. Similarly, by virtue of the communicative connection to network node 256 via network link 272, electronic device 270 also has access to network 280. Examples of network 280 include the Internet, the World Wide Web, wide area networks (WANs) including corporate intranets, local area networks (LANs) including wireless LANs (WLANs), analog or digital wired or wireless telephone networks, radio, television, cable, satellite, and/or any other delivery mechanisms for carrying data, or any combinations thereof.

[0078] As described above, in some implementations, Local Environment A 264 may correspond to a videoconference environment that is outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites and where multiple people may gather for the purpose of engaging in a videoconference employing the videoconference equipment provided within Local Environment A 264. For instance, Local Environment A 264 may be a dedicated videoconference studio such as, for example, the videoconference endpoint 100 illustrated in FIGS. 1A-1C.

[0079] In such implementations where Local Environment A 264 corresponds to a videoconference environment outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment A 264 may be communicatively coupled to network node 252, which may provide an interface between local network 254 and network 280, thereby enabling the videoconference equipment at Local Environment A 264 to connect with and facilitate videoconferences with other videoconference equipment communicatively connected to network 280. Additionally or alternatively, some or all of the videoconference equipment at Local Environment A 264 may not reside on local network 254 and may be communicatively connected to network 280 via one or more network nodes other than network node 252.

[0080] Similarly, Local Environment B 274 also may correspond to a videoconference environment that is outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites and where multiple people may gather for the purpose of engaging in a videoconference employing the videoconference equipment provided within Local Environment B 274. For instance, Local Environment B 274 may be a dedicated videoconference studio such as, for example, the videoconference endpoint 100 illustrated in FIGS. 1 A-1C.

[0081] In such implementations where Local Environment B 274 corresponds to a videoconference environment outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment B 274 may be communicatively coupled to network node 256, which may provide an interface between local network 258 and network 280, thereby enabling the videoconference equipment at Local Environment B 274 to connect with and facilitate videoconferences with other videoconference equipment communicatively connected to network 280. Additionally or alternatively, some or all of the videoconference equipment at Local Environment B 274 may not reside on local network 258 and may be communicatively connected to network 280 via one or more network nodes other than network node 256.

[0082] When Local Environment A 264 and Local Environment B 274 both correspond to videoconference environments and are outfitted with videoconference equipment providing functionality for conducting videoconferences with remote sites, the videoconference equipment at Local Environment A 264 and the videoconference equipment at Local Environment B 274 may be communicatively connected across network 280 and employed to conduct videoconferences between participants gathered at Local Environment A 264 and Local Environment B 274. In such implementations, in addition to the videoconference equipment located at Local Environment A 264 and Local Environment B 274, videoconference management system 282, also communicatively connected to network 280, also may facilitate a videoconference between participants gathered at Local Environment A 264 and participants gathered at Local Environment B 274.

[0083] Videoconference management system 282 may be implemented as one or more computing devices (e.g., servers) configured to provide videoconference management services to videoconference endpoints connected to videoconference management system 282 over network 280. The one or more computing devices on which videoconference management system 282 is implemented may have internal or external storage components storing data and programs such as an operating system and one or more application programs, for example, videoconferencing management applications. Although videoconference management system 282 is illustrated in FIG. 2B as being a centralized or remote system, in some implementations, videoconference management system 282 may be implemented in a distributed fashion across various different endpoints of a videoconferencing system.

[0084] Among other features, videoconference management system 282 may facilitate the scheduling and initiation of videoconferences between different endpoints and videoconference management system 282 may include a computer- readable storage system 284 storing meeting data that includes information about scheduled and/or on-going videoconferences. For example, the meeting data stored in computer-readable storage system 284 may include a schedule of videoconferences that records, among other data, information about the different endpoints and/or participants scheduled to participate in the scheduled videoconferences. In addition, the meeting data stored in computer-readable storage system 284 also may include information about on-going videoconferences even if such meetings were not scheduled in advance. For example, if an ad hoc videoconference is initiated between various different endpoints without any advance scheduling, information about the ad hoc videoconference, including the videoconference endpoints involved, may be added to the meeting data stored in computer-readable storage system 284. As such, if a videoconference between Local Environment A 264 and Local Environment B 274 is taking place, information about the videoconference, including the fact that it involves Local Environment A 264 and Local Environment B 274, may be included within the meeting data stored in computer-readable storage system 284 irrespective of whether the videoconference was scheduled in advance.

[0085] Videoconference management system 282 also may include a computer- readable storage system 286 storing endpoint data that includes information about different videoconference endpoints managed by or that otherwise have access to videoconference management system 282. For example, the endpoint data stored in computer-readable storage system 286 may include information about local network resources that are available on local networks associated with the endpoints managed by or that otherwise have access to videoconference management system 282 as well as information about individual users and/or devices that are authorized to access such local network resources. In particular, the endpoint data stored in computer-readable storage system 286 may include a record of the fact that local collaboration resource 266 and local redirect destination 268 are associated with and accessible to electronic devices on local network 254. In addition, the endpoint data stored in computer-readable storage system 286 also may include information about individual users and/or devices that are authorized to access local collaboration resource 266 and/or local redirect destination 268. Similarly, the endpoint data stored in computer-readable storage system 286 may include a record of the fact that local collaboration resource 276 and local redirect destination 278 are associated with and accessible to electronic devices on local network 258. In addition, the endpoint data stored in computer-readable storage system 286 also may include information about individual users and/or devices that are authorized to access local collaboration resource 276 and/or local redirect destination 278.

[0086] A specific example of a process by which network node 252 facilitates access to local collaboration resource 266 by electronic device 260 is now described. As illustrated in FIG. 2B, a communicative connection is established between electronic device 260 and network node 252 over a network link 262. This communicative connection between electronic device 260 and network node 252 may be established responsive to a user of electronic device 260 desiring to use electronic device 260 to access one or more network-available resources. For example, the communicative connection may be established as a consequence of the user of electronic device 260 connecting an Ethernet cable that provides access to network node 252 to electronic device 260. Alternatively, the communicative connection may be established as a consequence of an application executing on electronic device 260 initiating a wireless connection with network node 252 with or without manual involvement from the user of electronic device 260.

[0087] Following the establishment of the communicative connection between electronic device 260 and network node 252, electronic device 260 may transmit packets to network node 252, and network node 252 may block some or all packets received from electronic device 260 (irrespective of the packet's destination address(es) or port(s)) until network node 252 receives an HTTP request for access to a network resource, illustrated by small dashed line 1A. For example, network node 252 may receive an HTTP request for access to a network resource from electronic device 260 as a consequence of a user of electronic device 260 using a Web browser executing on electronic device 260 to attempt to navigate to a Web page or, alternatively, as a consequence of a user of electronic device 260 launching a Web browser on electronic device 260, and the Web browser on electronic device 260 then attempting to load a designated "Home" Web page.

[0088] In any event, when network node 252 receives the HTTP request illustrated by small dashed line 1A from electronic device 260, network node 252 intercepts the request and, as illustrated by small dashed line 2A, redirects electronic device 260 to local redirect destination 268. In some implementations, network node 252 may consult with videoconference management system 282 to determine the appropriate destination to which to redirect electronic device 260. For example, meeting data stored in computer-readable storage system 284 may include a schedule of videoconferences and/or information about ongoing videoconferences as well as records of collaboration resources or other network destinations associated with specific ones of the scheduled and/or ongoing videoconferences. Thus, by consulting with videoconference management system 282, network node 252 may discover that local collaboration resource 266 is associated with a videoconference corresponding to a time at which the HTTP request was received from electronic device 206 and, therefore, that electronic device 260 is to be redirected to local redirection destination 268, which will facilitate access to local collaboration resource 266 by electronic device 260. Additionally or alternatively, endpoint data stored in computer-readable storage system 286 may include an indication that local collaboration resource 266 is associated with network node 252 and/or with Local Environment A 264 and/or indications of individual users and/or electronic devices authorized to access local redirect destination 268 and/or local collaboration resource 266. Thus, by consulting with videoconference management system 282, network node 252 may be able to determine whether electronic device 260 and/or a user of electronic device 260 is authorized to access local redirect destination 268 and/or local collaboration resource and only redirect electronic device 260 upon receiving confirmation from videoconference management system 282 that electronic device and/or the user of electronic device 260 is authorized to access local redirect destination 268 and or local collaboration resource 266.

[0089] Furthermore, network node 252 may employ any of a variety of different techniques to accomplish the redirection of electronic device 260 to local redirect destination 268. For example, network node 252 may forward the intercepted HTTP request to a redirect server that responds to the forwarded request with an HTTP response including an HTTP status code (e.g., status code 302) that redirects electronic device 260 to local redirect destination 268, thereby enabling electronic device 260 to establish an HTTP session with local redirect destination 268. Alternatively, network node 252 may employ IP redirection techniques at the OSI Layer 3 level to redirect electronic device 260 to local redirect destination 268. In other implementations, network node 252 may cause the IP address of local redirect destination 268 to be returned to electronic device 260 in response to a DNS query received from electronic device 260.

[0090] As described above, in some implementations, upon establishment of a communicative connection between electronic device 260 and network node 252, network node 252 may block packets received from electronic device 260 until network node 252 receives an HTTP request for access to a network resource from electronic device 260. Then, upon receipt of the HTTP request from electronic device 260, network node 252 may redirect electronic device 260 to local redirect destination 268. However, in other implementations, network node 252 may handle the redirection of electronic device 260 to local redirect destination 268 differently. For example, after a communicative connection between electronic device 260 and network node 252 is established, network node 252 may transmit (or alternatively block) some or all communications received from electronic device 260 until a communication of a particular protocol type is received at network node 252 from electronic device 260. Receipt of a communication from electronic device 260 having the particular prototype at network node 252 may trigger network node 252 to redirect electronic device 260 to local redirect destination 268. For instance, a particular type of client application that packages outbound communications according to the particular protocol type (e.g., a protocol type unique to the client application) may be installed on electronic device 260. Then, when this client application causes electronic device 260 to transmit a communication of the particular protocol type to network node 252 (e.g., upon start-up of the client application on electronic device 260), network node 252 may redirect electronic device 260 to local redirect destination 268 in response to receipt of the communication of the particular protocol type from electronic device 260.

[0091] After network node 252 redirects electronic device 260 to local redirect destination 268, local redirect destination 268 then facilitates access to local collaboration resource 266 by electronic device 260, as illustrated by small dashed line 3A. For example, local redirect destination 268 may be a general log-in page for a number of different local collaboration resources, including local collaboration resource 266. As part of redirecting electronic device 260 to local redirect destination 268, network node 252 automatically may transfer the log-in information for accessing local collaboration resource 266 to local redirect destination 268, which, in turn, may use the log-in information to identify local collaboration resource 266 as the specific local collaboration resource to which to grant access to electronic device 260.

[0092] Like the specific example of the process by which network node 252 facilitates access to local collaboration resource 266 by electronic device 260 described above, a specific example of a process by which network node 256 facilitates access to local collaboration resource 276 by electronic device 270 is now described. As illustrated in FIG. 2B, a communicative connection is established between electronic device 270 and network node 256 over a network link 272. This communicative connection between electronic device 270 and network node 256 may be established responsive to a user of electronic device 270 desiring to use electronic device 270 to access one or more network-available resources. For example, the communicative connection may be established as a consequence of the user of electronic device 270 connecting an Ethernet cable that provides access to network node 256 to electronic device 270. Alternatively, the communicative connection may be established as a consequence of an application executing on electronic device 270 initiating a wireless connection with network node 256 with or without manual involvement from the user of electronic device 270.

[0093] Following the establishment of the communicative connection between electronic device 270 and network node 256, electronic device 270 may transmit packets to network node 256, and network node 256 may block some or all packets received from electronic device 256 (irrespective of the packet's destination addresses) or port(s)) until network node 256 receives an HTTP request for access to a network resource, illustrated by small dashed line 1B. For example, network node 256 may receive an HTTP request for access to a network resource from electronic device 270 as a consequence of a user of electronic device 270 using a Web browser executing on electronic device 270 to attempt to navigate to a Web page or, alternatively, as a consequence of a user of electronic device 270 launching a Web browser on electronic device 270, and the Web browser on electronic device 270 then attempting to load a designated "Home" Web page.

[0094] In any event, when network node 256 receives the HTTP request illustrated by small dashed line 1B from electronic device 270, network node 256 intercepts the request and, as illustrated by small dashed line 2B, redirects electronic device 270 to local redirect destination 278. In some implementations, network node 256 may consult with videoconference management system 282 to determine the appropriate destination to which to redirect electronic device 270. For example, meeting data stored in computer-readable storage system 284 may include a schedule of videoconferences and/or information about ongoing videoconferences as well as records of collaboration resources or other network destinations associated with specific ones of the scheduled and/or ongoing videoconferences. Thus, by consulting with videoconference management system 282, network node 256 may discover that local collaboration resource 276 is associated with a videoconference corresponding to a time at which the HTTP request was received from electronic device 270 and, therefore, that electronic device 270 is to be redirected to local redirect destination 278, which will facilitate access to local collaboration resource 276 by electronic device 270. Additionally or alternatively, endpoint data stored in computer-readable storage system 286 may include an indication that local collaboration resource 276 is associated with network node 256 and or with Local Environment B 274 and/or indications of individual users and/or electronic devices authorized to access local redirect destination 278 and/or local collaboration resource 276. Thus, by consulting with videoconference management system 282, network node 256 may be able to determine whether electronic device 270 and/or a user of electronic device 270 are authorized to access local redirect destination 278 and/or local collaboration resource 276 and only redirect electronic device 270 upon receiving confirmation from videoconference management system 282 that electronic device and/or the user of electronic device 270 is authorized to access local redirect destination 278 and/or local collaboration resource 276.

[0095] Furthermore, network node 256 may employ any of a variety of different techniques to accomplish the redirection of electronic device 270 to local redirect destination 278. For example, network node 256 may forward the intercepted HTTP request to a redirect server that responds to the forwarded request with an HTTP response including an HTTP status code (e.g., status code 302) that redirects electronic device 270 to local redirect destination 278, thereby enabling electronic device 270 to establish an HTTP session with local redirect destination 278. Alternatively, network node 256 may employ IP redirection techniques at the OSI Layer 3 level to redirect electronic device 270 to local redirect destination 278. In other implementations, network node 256 may cause the IP address of local redirect destination 278 to be returned to electronic device 270 in response to a DNS query received from electronic device 270.

[0096] As described above, in some implementations, upon establishment of a communicative connection between electronic device 270 and network node 256, network node 256 may block packets received from electronic device 270 until network node 256 receives an HTTP request for access to a network resource from electronic device 270. Then, upon receipt of the HTTP request from electronic device 270, network node 256 may redirect electronic device 270 to local redirect destination 278. However, in other implementations, network node 256 may handle the redirection of electronic device 270 to local redirect destination 278 differently. For example, after a communicative connection between electronic device 270 and network node 256 is established, network node 256 may transmit (or alternatively block) some or all communications received from electronic device 270 until a communication of a particular protocol type is received at network node 256 from electronic device 270. Receipt of a communication from electronic device 270 having the particular prototype at network node 256 may trigger network node 256 to redirect electronic device 270 to local redirect destination 278. For instance, a particular type of client application that packages outbound communications according to the particular protocol type (e.g., a protocol type unique to the client application) may be installed on electronic device 270. Then, when this client application causes electronic device 270 to transmit a communication of the particular protocol type to network node 256 (e.g., upon start-up of the client application on electronic device 270), network node 256 may redirect electronic device 270 to local redirect destination 278 in response to receipt of the communication of the particular protocol type from electronic device 270.

[0097] After network node 256 redirects electronic device 270 to local redirect destination 278, local redirect destination 278 then facilitates access to local collaboration resource 276 by electronic device 270, as illustrated by small dashed line 3B. For example, local redirect destination 278 may be a general log-in page for a number of different local collaboration resources, including local collaboration resource 276. As part of redirecting electronic device 270 to local redirect destination 278, network node 256 automatically may transfer the log-in information for accessing local collaboration resource 276 to local redirect destination 278, which, in turn, may use the fog-in information to identify local collaboration resource 276 as the specific collaboration resource to which to grant access to electronic device 270.

[0098] In some implementations, local collaboration resource 266 may be configured to capture collaborative activity engaged in by electronic devices connected to local collaboration resource 266 over local network 254 and to repackage and transmit such collaborative activity to a remote collaboration resource (not shown) (e.g., over network 280) essentially operating as a virtual client with respect to the remote collaboration resource. Similarly, local collaboration resource 276 may be configured to capture collaborative activity engaged in by electronic devices connected to local collaboration resource 276 over local network 258 and to repackage and transmit such collaborative activity to a remote collaboration resource (not shown) (e.g., over network 280) essentially operating as a virtual client with respect to the remote collaboration resource.

[0099] In such implementations where local collaboration resource 266 and local collaboration resource 276 both are configured to capture and repackage collaborative activity in this manner, local collaboration resource 266 and local collaboration resource 276 both may connect to a remote collaboration resource (not shown) as virtual clients, thereby effectively enabling electronic devices accessing local collaboration resource 266 and electronic devices accessing local collaboration resource 276 to share content and/or collaborate with one another as illustrated by large dashed line 288. Additionally or alternatively, one of local collaboration resource 266 and local collaboration resource 276 may connect to the other of local collaboration resource 266 and local collaboration resource 276 as a virtual client, thereby effectively enabling electronic devices accessing local collaboration resource 266 and electronic devices accessing local collaboration resource 276 to share content and/or collaborate with one another as illustrated by large dashed line 288.

[00100] As illustrated in FIG. 2B, electronic devices 260 and 270 are laptop or notebook computers. However, network nodes 252 and 256 may be configured to enable communicative connections with any of a variety of different types of electronic devices in addition to laptop or notebook computers, including, for example, among other types of electronic devices, tablet computers, smart phones, netbook computers, personal digital assistants, and desktop computers.

[00101] FIG. 3 is a block diagram of an example of a network node 300, such as, for example, network nodes 202 and 206 of FIG. 2A and network nodes 252 and 256 of FIG. 2B. Network node 300 may be, for example, a network switch, a network gateway, a router, a wireless access point (WAP), or some hybrid combination thereof. Network node 300 includes one or more processors 302 for executing instructions and one or more network interface controllers 304. The one or more network interface controllers 304 may include circuitry for transmitting and receiving electronic communications to and from other electronic devices over network connections.

[00102] Network node 300 also includes a network traffic routing module 306. Network traffic routing module 306 is configured to assist in the routing of electronic signals received at network node 300. For example, when an electronic signal is received at network node 300 from an electronic device on a local network, network traffic routing module may assist in transmitting the received electronic signal to its intended destination, which may reside on an external network. Similarly, when an electronic signal is received at network node 300 from an electronic device on an external network and intended for an electronic device that resides on a local network, network traffic routing module may assist in transmitting the received electronic signal to the intended electronic device on the local network.

[00103] As illustrated in FIG. 3, network node 300 also includes an interception module 308, an alternative destination lookup module 310, and a redirection module 312. In some cases, network node 300 may be configured to automatically redirect an electronic device communicatively coupled to network node 300 on a local network to an alternative destination, in such implementations, network node 300 may be configured to block some or all electronic signals received at network node 300 from the electronic device until an HTTP request intended for a particular destination is received from the electronic device at network node 300. In particular, interception module 308 may cause network node 300 to intercept electronic signals received at network node 300 from the electronic device and block such intercepted electronic signals from further transmission. When an HTTP request specifying a particular destination is received at network node 300 from the electronic device, interception module 308 may cause network node 300 to intercept the HTTP request. [00104] Then, upon determining that the intercepted signal is an HTTP request, alternative destination lookup module 310 may cause network node 300 to determine an alternative destination to which to redirect the electronic device as described throughout, and redirection module 312 may operate to cause network node 300 to redirect the electronic device to the determined alternative destination. For example, in some implementations, a particular redirect destination may be designated as corresponding to network node 300, and network node 300 may redirect the electronic device to that redirect destination as a consequence of the relationship between the redirect destination and network node 300. Alternatively, a particular redirect destination may be designated as corresponding to both the network node and a time at which the HTTP request was received from the electronic device (e.g., in association with a scheduled meeting), and network node 300 may redirect the electronic device to that redirect destination as a consequence of the relationship between the redirect destination and network node 300 and the time at which the HTTP request was received from the electronic device. Additionally or alternatively, network node 300 may redirect the electronic device to a redirect destination based upon an identity of the electronic device and/or an identity of a user of the electronic device. In some implementations, the alternative destination to which network node 300 redirects the electronic device may be located at or within network node 300 itself.

[00105] In some implementations, network traffic routing module 306, interception module 308, alternative destination lookup module 310, and/or redirection module 312 may be implemented as instructions stored in tangible, computer-readable storage media that, when executed by processor(s) 302, cause network node 300 to perform the functionality ascribed herein to the network traffic routing module 306, interception module 308, alternative destination lookup module 310, and/or redirection module 312. Additionally or alternatively, network traffic routing module 306, interception module 308, alternative destination lookup module 310, and/or redirection module 312 may be supplemented by, or implemented in, hardware, such as, for example, application-specific integrated circuits (ASICs).

[00106] FIG. 4 is a flowchart of an example of a process for redirecting electronic devices. The process illustrated in the flowchart 400 of FIG. 4 may be performed by a network node such as, for example, network nodes 202 and 206 of FIG. 2A, network nodes 252 and 256 of FIG. 2B, or network node 300 of FIG. 3. In some implementations, the network node may be associated with an environment where meetings are conducted, and the process may facilitate access to a network resource that is related to a meeting (e.g., a collaboration resource) by an electronic device brought into the environment by a meeting participant.

[00107] At 402, a message (e.g., an HTTP request) intended for a particular destination is intercepted at the network node from an electronic device. At 404, a determination is made as to whether the electronic device from which the intercepted message was received is whitelisted. For example, multiple electronic devices may be communicatively connected to the network node on a local network, and the network node may be configured to redirect only some subset of such electronic devices. Network node may intercept messages from such electronic devices, while allowing messages from the other electronic that the network node is not configured to redirect to pass on through to their intended destinations. These electronic devices for which the network node is configured to allow electronic messages to pass through without being intercepted may be considered to be whitelisted by the network node.

[00108] In one example, the network node may be associated with a videoconferencing environment and videoconference equipment for enabling videoconferences from the videoconference environment with remote sites that is communicatively connected to the network node may be whitelisted by the network node such that the network node does not redirect the videoconference equipment. In contrast, personal devices that users have brought with them into the videoconference environment and that have been connected to the network node may not be whitelisted by the network node.

[00109] If the network node determines that the electronic device from which the intercepted message was received is whitelisted, the network node may allow the message to be transmitted to its intended destination at 406, and the process then returns to 402 where the network node receives another message from an electronic device communicatively connected to the electronic device on a local network.

[00110] In contrast, if the network node determines that the electronic device from which the intercepted message was received is not whitelisted, at 408, the network node accesses meeting data (e.g., the meeting data stored in computer-readable storage system 226 of videoconference management system 224 of FIG. 2A or the meeting data stored in computer-readable storage system 284 of videoconference management system 282), for example to identify a meeting associated with the network node and that corresponds to a time at which the intercepted message was received. For instance, if the network node corresponds to a videoconference environment, the network node may access the meeting data to identify a videoconference taking place within the videoconference environment and corresponding to a time at which the message was intercepted. In addition, the accessed meeting data also may reflect information about a network resource (e.g., collaboration resource 228 of FIG. 2A, or local collaboration resources 266 and 276 of FIG. 2B) designated as corresponding to the identified meeting.

[00111] Then, at 410, the network node determines an appropriate redirect destination based on the accessed meeting data. For example, based on the accessed meeting data, the network node may determine that a meeting corresponding to the time at which the intercepted message was received is associated with the network node and that a network resource has been designated as corresponding to the identified meeting. Consequently, the network node may determine that the network resource designated as corresponding to the meeting is the appropriate redirect destination. At 412, after having determined the redirect destination, the network node redirects the electronic device to the determined redirect destination.

[00112] Thereafter, at 414, the network node temporarily whitelists the electronic device so that the electronic device is not redirected to the redirect destination again in response to future messages received by the network node from the electronic device. For example, the network node may whitelist the electronic device for the duration of the meeting determined to correspond to the time at which the intercepted message was received and to be associated with the network node. Consequently, the electronic device may be free to access both the redirect destination and one or more other network resources for the remainder of the meeting.

[00113] After the electronic device has been whitelisted, the process then returns to 402 where the network node receives another message from an electronic device communicatively connected to the network node on a local network.

[00114] FIG. 5 is a flowchart of an example of a process for redirecting electronic devices. The process illustrated in the flowchart 500 of FIG. 5 may be performed by a network node such as, for example, network nodes 202 and 206 of FIG. 2A, network nodes 252 and 256 of FIG. 2B, or network node 300 of FIG. 3. In some implementations, the network node may be associated with a particular local environment, and the process may facilitate access by an electronic device to a network resource (e.g., a local network resource) that is related to the local environment and/or the network node. Furthermore, the process may restrict access to the network resource to electronic devices and/or users authorized to access the network resource.

[00115] At 502, a message (e.g., an HTTP request) intended for a particular destination is intercepted at the network node from an electronic device. At 504, a determination is made as to whether the electronic device from which the intercepted message was received is whitelisted. If the network node determines that the electronic device from which the intercepted message was received is whitelisted, the network node may allow the message to be transmitted to its intended destination at 506, and the process then returns to 502 where the network node receives another message from an electronic device communicatively connected to the network node on a local network.

[00116] In contrast, if the network node determines that the electronic device from which the intercepted message was received is not whitelisted, the network node requests identifying information from the electronic device at 508. For example, the network node may request information identifying the electronic device itself (e.g., a media access control (MAC) address, an IP address, etc.) and/or information identifying a user of the electronic device (e.g., a user identifier and or password).

[00117] At 510, the network node receives the requested identifying information for the electronic device and/or the user of the electronic device from the electronic device and, then, at 512, the network node determines whether the electronic device and/or the user of the electronic device is authorized to access the network resource based on the received identifying information. If the network node determines that the electronic device and/or the user of the electronic device is not authorized to access the network resource, the process returns to 502 where the network node receives another message from an electronic device communicatively connected to the network node on a local network. If, however, the network node determines that the electronic device and/or the user of the electronic device is authorized to access the network resource, the network node redirects the electronic device to the network resource at 514. In some implementations, individual electronic devices and/or individual users may be authorized to access the network resource during some scheduled period of time. For example, individual electronic devices and/or individual users may be authorized to access the network resource during a scheduled meeting and, perhaps, for some predetermined time before and/or some predetermined time after the scheduled meeting. In such implementations, the network node may determine whether the electronic device and/or the user of the electronic device is authorized to access the network resource by determining whether the electronic device and/or the user of the electronic device is scheduled as being authorized to access the network resource during the time at which the message from the electronic was intercepted.

[00118] At 516, the network node temporarily whitelists the electronic device so that the electronic device is not redirected to the network resource again in response to future messages received by the network node from the electronic device. Consequently, going forward, the electronic device may be free to access both the network resource to which it was redirected and one or more other network resources. After the electronic device is temporarily wfiitelisted, the process then returns to 502 where the network node receives another message from an electronic device communicatively connected to the network node on a local network.

[00119] A number of methods, techniques, systems, and apparatuses have been described. For example, as described above, in one general aspect, a videoconference endpoint enables videoconferencing with different videoconference endpoints, and a network node that is associated with the videoconference endpoint provides an interface between a local network associated with the videoconference endpoint and another network. The network node includes an interception module to intercept an electronic message that originated from an electronic device on the local network and that specifies an intended destination. In addition, the network node includes an alternative destination lookup module to access videoconference schedule data and identify an alternative destination (that is different than the intended destination) to which to redirect the electronic device based on the accessed videoconference schedule data and a time at which the electronic message was intercepted. The network node also includes a redirection module to redirect the electronic device to the alternative destination.

[00120] Implementations may include one or more of the following features. For example, the alternative destination lookup module may be configured to identify a videoconference involving the videoconference endpoint corresponding to the time at which the electronic message was intercepted based on the accessed videoconference schedule data and to identify an alternative destination to which to redirect the electronic device by identifying an alternative destination that is associated with the identified videoconference. In some implementations, the alternative destination lookup module may be configured to identify a videoconference involving the videoconference endpoint corresponding to the time at which the electronic message was intercepted by identifying a videoconference that is scheduled for the time at which the electronic message was intercepted and that includes the videoconference endpoint. Furthermore, in some implementations, the alternative destination lookup module may be configured to receive identifying information from a user of the electronic device and to determine, based on the received identifying information and the accessed videoconference schedule data, that the user of the electronic device is scheduled to participate in the identified videoconference. In such implementations, the redirection module may be configured to redirect the electronic device to the alternative destination responsive to the alternative destination lookup module determining that the user of the electronic device is scheduled to participate in the identified videoconference. Some implementations also may include a videoconference management system. The videoconference management system may store a schedule of videoconferences involving videoconference endpoints. In such implementations, the alternative destination lookup module may be configured to access the videoconference schedule data from the videoconference management system. Additionally or alternatively, the alternative destination may provide an interface to the videoconference endpoint management system that exposes mechanisms for controlling components of the videoconference endpoint and or aspects of a videoconference with other videoconference endpoints. Furthermore, the alternative destination may be a collaboration resource that is associated with the identified videoconference and is configured to enable sharing of electronic content between participants of the identified videoconference. [00121] Implementations additionally or alternatively may include a secondary display device to display content other than video images of participants in a videoconference that is shared across the videoconference, and the videoconference endpoint may include multiple display devices to display videoconference streams that include video images of videoconference participants received from other videoconference endpoints in a videoconference. In such implementations, the alternative destination may be a collaboration resource configured to generate a graphical user interface that displays content shared across the videoconference, and the secondary display device may be configured to display the graphical user interface generated by the alternative destination during the videoconference.

[00122] In some implementations, the alternative destination may reside on the local network. In alternative implementations, the alternative destination may reside off of the local network.

[00123] In another general aspect, an electronic message that specifies an intended destination and that originated from an electronic device on a local network is intercepted. The local network is associated with a network resource that enables multiple electronic devices to access shared content concurrently, and the electronic device is redirected to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the electronic message.

[00124] Implementations may include one or more of the following features. For example, the intercepted electronic message may be an HTTP request issued by a web browser executing on the electronic device and specifying a network address of an intended destination off of the local network, and redirecting the electronic device to the network resource may include initiating an HTTP session between the electronic device and the network resource.

[00125] Additionally or alternatively, a second electronic message that is different from the first electronic message, that specifies a second intended destination, and that originated from a second electronic device on the local network that is different from the first electronic device may be intercepted. In such implementations, the second electronic device may be redirected to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the second electronic message while the first electronic device is continuing to access the network resource such that the first electronic device and the second electronic device are accessing the shared content concurrently.

[00126] In yet another general aspect, an electronic message that originated from an electronic device on a local network and that specifies an intended destination is intercepted at a network node that provides an interface between the local network and another network. In addition, responsive to intercepting the electronic message, the electronic device is redirected to an alternative destination for requesting identification information from a user of the electronic device that is different from the intended destination. Identification information then is received for the user of the electronic device as a consequence of having redirected the electronic device to the alternative destination, and, based on the received identification information for the user of the electronic device, it is determined that the user of the electronic device is authorized to access a collaboration resource that is associated with the local network and that corresponds to a videoconference associated with the local network. As a consequence of having determined that the user of the electronic device is authorized to access the collaboration resource that is associated with the local network and that corresponds to the videoconference associated with the local network, the electronic device then is enabled to access the collaboration resource that is associated with the local network and that corresponds to the videoconference associated with the local network.

[00127] Additional implementations are contemplated as well. In one general implementation, a network node defining a local network may be configured to redirect some or all electronic devices communicatively connected to the network node on the local network to a network-accessible resource (either local or external) that is designated as corresponding to the network node and/or the local network. This network-accessible resource may be a resource that facilitates collaboration and/or the sharing of content between multiple electronic devices concurrently, and, by redirecting electronic devices on the local network to such a resource, the network node may facilitate collaboration and/or sharing of content between devices on the local network. In this manner, if multiple people gather in a location (e.g., for a meeting) and bring with them electronic devices that they communicatively connect to the local network, the network node may facilitate collaboration and/or sharing of content between such electronic devices by redirecting the electronic devices to the network collaboration and/or sharing resource that is designated as corresponding to the network node and/or the local network. In some cases, access to the network collaboration and/or sharing resource may be governed by membership in a group. For example, only members of a certain group (e.g., company executives or a research and development organization) may be permitted to access the network resource.

[00128] In many of the examples described herein, electronic devices are redirected to network resources for collaborating and/or sharing content between multiple electronic devices concurrently. However, depending upon the implementation, electronic devices may be redirected to any of a number of different types of network resources in addition or as an alternative to a network resource for collaborating and/or sharing content between multiple electronic devices concurrently. For example, electronic devices may be redirected to a network resource that enables control of a videoconference (e.g., an application that controls who is invited or otherwise allowed to participate in the videoconference, which participant A/V streams are actually played in the videoconference and how they are actually played, etc.) and/or to a network resource that enables control of or provides information about a videoconference environment (e.g., an application that enables control of lighting or temperature conditions in and/or that provides schedule information for a dedicated videoconference studio such as videoconference endpoint 100 of FIGS. 1A-1C). Additionally or alternatively, electronic devices may be redirected to a file sharing resource that stores meeting artifacts for recurring meetings. Furthermore, redirection of the electronic devices may result in different menus and/or functionality being made available to the electronic devices than otherwise would be available.

[00129] The methods, techniques, systems, and apparatuses described above may be implemented in digital electronic circuitry or computer hardware, for example, by executing instructions stored in computer-readable storage media. Apparatuses implementing these techniques may include appropriate input and output devices, a computer processor, and/or a tangible computer-readable storage medium storing instructions for execution by a processor. A process implementing techniques disclosed herein may be performed by a processor executing instructions stored on a tangible computer-readable storage medium for performing desired functions by operating on input data and generating appropriate output. Suitable processors include, by way of example, both general and special purpose microprocessors. Suitable computer-readable storage devices for storing executable instructions include all forms of non-volatile memory, including, by way of example, semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as fixed, floppy, and removable disks; other magnetic media including tape; and optical media such as Compact Discs (CDs) or Digital Video Disks (DVDs). Any of the foregoing may be supplemented by, or incorporated in, specially designed application-specific integrated circuits (ASICs).

[00130] Although the operations of the disclosed techniques may be described herein as being performed in a certain order and/or in certain combinations, in some implementations, individual operations may be rearranged in a different order, combined with other operations described herein, and/or eliminated, and the desired results still may be achieved. Similarly, components in the disclosed systems may be combined in a different manner and/or replaced or supplemented by other components and the desired results still may be achieved.

Claims

WHAT IS CLAIMED IS:

1. A system comprising:

a videoconference endpoint to enable videoconferencing with different videoconference endpoints; and

a network node that is associated with the videoconference endpoint and that provides an interface between a local network associated with the

videoconference endpoint and another network, the network node including:

an interception module to intercept an electronic message that originated from an electronic device on the local network and that specifies an intended destination,

an alternative destination lookup module to access videoconference schedule data and identify an alternative destination to which to redirect the electronic device based on the accessed videoconference schedule data and a time at which the electronic message was intercepted, the alternative destination being different than the intended destination, and

a redirection module to redirect the electronic device to the alternative destination.

2. The system of claim 1 wherein the alternative destination lookup module is configured to:

identify a videoconference involving the videoconference endpoint corresponding to the time at which the electronic message was intercepted based on the accessed videoconference schedule data, and

identify an alternative destination to which to redirect the electronic device by identifying an alternative destination that is associated with the identified videoconference.

3. The system of claim 2 wherein the alternative destination lookup module is configured to identify a videoconference involving the videoconference endpoint corresponding to the time at which the electronic message was intercepted by identifying a videoconference that is scheduled for the time at which the electronic message was intercepted and that includes the videoconference endpoint.

4. The system of claim 3 wherein:

the alternative destination lookup module is further configured to:

receive identifying information from a user of the electronic device, and

determine, based on the identifying information received from the user of the electronic device and the accessed videoconference schedule data, that the user of the electronic device is scheduled to participate in the identified videoconference; and

the redirection module is configured to redirect the electronic device to the alternative destination responsive to the alternative destination lookup module determining that the user of the electronic device is scheduled to participate in the identified videoconference.

5. The system of claim 2 further comprising a videoconference management system storing a schedule of videoconferences involving

videoconference endpoints, wherein the alternative destination lookup module is configured to access the videoconference schedule data from the videoconference management system.

6. The system of claim 2 wherein the alternative destination is a collaboration resource that is associated with the identified videoconference and is configured to enable sharing of electronic content between participants of the identified videoconference.

7. The system of claim 1 further comprising a secondary display device to display content other than video images of participants in a videoconference that is shared across the videoconference, wherein:

the videoconference endpoint includes multiple display devices to display videoconference streams that include video images of videoconference participants received from other videoconference endpoints in a videoconference;

the alternative destination is a collaboration resource configured to generate a graphical user interface that displays content shared across the videoconference; and

the secondary display device is configured to display the graphical user interface generated by the alternative destination during the videoconference.

8. The system of claim 1 further comprising a videoconference endpoint management system, wherein the alternative destination provides an interface to the videoconference endpoint management system that exposes mechanisms for controlling components of the videoconference endpoint.

9. The system of claim 1 further comprising a videoconference management system, wherein the alternative destination provides an interface to the videoconference management system that exposes mechanisms for controlling aspects of a videoconference with other videoconference endpoints.

10. The system of claim 1 wherein the alternative destination resides on the local network.

11. The system of claim 1 wherein the alternative destination resides off of the local network.

12. A non-transitory computer-readable medium storing instructions that, when executed by a computing device, cause the computing device to:

intercept an electronic message that specifies an intended destination and that originated from an electronic device on a local network, the local network being associated with a network resource that enables multiple electronic devices to access shared content concurrently; and

redirect the electronic device to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the electronic message.

13. The computer-readable medium of claim 12 wherein:

the instructions that, when executed by a computing device, cause the computing device to intercept an electronic message that specifies an intended destination and that originated from an electronic device on a local network include instructions that, when executed by a computing device, cause the computing device to intercept an HTTP request issued by a web browser executing on the electronic device and specifying a network address of an intended destination off of the local network; and

the instructions that, when executed by a computing device, cause the computing device to redirect the electronic device to the network resource include instructions that, when executed by a computing device, cause the computing device to initiate an HTTP session between the electronic device and the network resource.

14. The computer-readable medium of claim 12 wherein:

the instructions that, when executed by a computing device, cause the computing device to intercept an electronic message that specifies an intended destination and that originated from an electronic device on a local network include instructions that, when executed by a computing device, cause the computing device to:

intercept a first electronic message that specifies a first intended destination and that originated from a first electronic device on the local network, and intercept a second electronic message that is different from the first electronic message, that specifies a second intended destination, and that originated from a second electronic device on the local network, the second electronic device being different from the first electronic device; and the instructions that, when executed by a computing device, cause the computing device to redirect the electronic device to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the electronic message include instructions that, when executed by a computing device, cause the computing device to:

redirect the first electronic device to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the first electronic message, and

redirect the second electronic device to the network resource that enables multiple electronic devices to access shared content concurrently responsive to intercepting the second electronic message while the first electronic device is continuing to access the network resource such that the first electronic device and the second electronic device are accessing the shared content concurrently.

15. A computer-implemented method comprising:

intercepting, at a network node that provides an interface between a local network and another network, an electronic message that originated from an electronic device on the local network and that specifies an intended destination; responsive to intercepting the electronic message, redirecting the electronic device to an alternative destination for requesting identification information from a user of the electronic device, the alternative destination being different from the intended destination;

receiving identification information for the user of the electronic device as a consequence of having redirected the electronic device to the alternative destination; determining, based on the received identification information for the user of the electronic device, that the user of the electronic device is authorized to access a collaboration resource that is associated with the local network and that corresponds to a videoconference associated with the local network; and

as a consequence of having determined that the user of the electronic device is authorized to access the collaboration resource that is associated with the local network and that corresponds to the videoconference associated with the local network, enabling the electronic device to access the collaboration resource that is associated with the local network and that corresponds to the

videoconference associated with the local network.