Projector device management system

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority from U.S. Provisional Patent Application Serial No. 60/370,704 of Steve Murtha, De Tran, James D. Wenban, Alan Cossitt, and Joe Castaldi for a SYSTEM AND METHOD FOR CONTROLLING A PROJECTOR OVER A NETWORK, filed Apr. 5, 2002, the disclosure of which is hereby incorporated by reference.

TECHNICAL FIELD

[0002] The present invention relates a system for managing a plurality of projector devices over a network.

BACKGROUND OF THE INVENTION

[0003] In recent years, projector devices, such as digital projectors, have found increased popularity as a tool for the presentation of content to an audience. These projector devices are typically used to project a computer-generated presentation onto a viewing surface, and allow a user to easily present high-quality, professional appearing images to audiences of a range of sizes. As a result, these projector devices are now often found as permanent fixtures in conference rooms and other meeting facilities.

[0004] Some entities, such as businesses and schools, may have a plurality of projector devices installed multiple physical locations, for example, in different conference rooms, different buildings, or even different cities, states and/or countries. The administration of such an arrangement of projector devices may be a difficult and time-consuming task. For example, it may be difficult to keep track of whether the lamps on all the projector devices are functional, or whether any projector devices have been stolen or moved. Such problems may cause significant delays to a user who wishes to use a selected projector device if not remedied ahead of time. However, manually checking each projector device at regular enough intervals to ensure reliable operation may take a significant amount of employee time.

[0005] Similar problems may arise regarding administrative control of a plurality of projector devices. For example, where the ability to change projector device settings is not restricted, a later user of a selected projector device may have to change the settings left by a prior user before presenting content with the projector device. Furthermore, a user may forget to turn a projector device off, thus effectively reducing the life of the projector device lamp.

SUMMARY OF THE INVENTION

[0006] One aspect of the present invention provides a system for managing a plurality of network-enabled projector devices over a computer network. The system includes a projector manager linked to a computer network, wherein the projector manager is configured to monitor over the network a status of a selected feature of a selected projector device, and to change the status of the selected feature when requested. The system also includes a projector manager controller linked to the computer network, wherein the projector manager controller is configured to request the projector manager to perform at least one of the functions of reporting the status of the selected feature and requesting the selected projector device to change the status of the selected feature.

[0007] Another aspect of the present invention provides a system for administrating a plurality of projector devices over a computer network. The system includes server software stored on a recordable medium linked to the network, wherein the server software is executable by a server computing device to communicate with a selected projector device over the network to detect a status of the selected projector device and to change the status of the selected projector device when directed, and administrative client software stored on a recordable medium linked to the network, wherein the administrative client software is executable by a client computing device to permit the user to direct the server computing device to communicate with the selected projector device.

[0008] Yet another aspect of the present invention provides a method for remotely controlling a network-enabled projector device, wherein the projector device is connected to a computer network that includes a client computing device and a server computing device. The method includes sending a first message from the client computing device to the server computing device directing the server to request the projector device to perform a selected function, and upon receiving the first message at the server computing device, sending a second message from the server computing device to the projector device requesting the projector device to perform the selected function.

[0009] A further aspect of the present invention provides a method of automatically alerting of a changed state of a projector device linked to a computer network, the network including a server computing device in communication with the projector device over the network and a client computing device in communication with the server computing device over the network. The method comprises detecting a current state of the projector device via the server computing device, comparing the current state of the projector device with a preselected condition, and if the current state of the projector device meets the preselected condition, then sending a message from the server computing device to the client computing device to alert of the current state of the projector device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010]FIG. 1 is a schematic depiction of an exemplary embodiment of a projector device management system according to the present invention.

[0011]FIG. 2 is a block diagram of the projector device management system of FIG. 1.

[0012]FIG. 3 is a view of an exemplary user interface of a projector manager controller according to an embodiment of the present invention.

[0013]FIG. 4 is a view of an exemplary master services sub-screen of the embodiment of FIG. 3.

[0014]FIG. 5 is a view of an exemplary administration service sub-screen of the embodiment of FIG. 3.

[0015]FIG. 6 is a view of an exemplary default shutdown scheduling sub-screen of the embodiment of FIG. 3.

[0016]FIG. 7 is a view of an exemplary new user addition sub-screen of the embodiment of FIG. 3.

[0017]FIG. 8 is a view of an exemplary event notification configuration sub-screen of the embodiment of FIG. 3.

[0018]FIG. 9 is a view of an exemplary event description sub-screen of the embodiment of FIG. 3.

[0019]FIG. 10 is a view of an exemplary projector model properties sub-screen of the embodiment of FIG. 3.

[0020]FIG. 11 is a view of an exemplary projector device addition sub-screen of the embodiment of FIG. 3.

[0021]FIG. 12 is a view of an exemplary individual projector device properties sub-screen of the embodiment of FIG. 3.

[0022]FIG. 13 is a view of an exemplary projector device status sub-screen of the embodiment of FIG. 3.

[0023]FIG. 14 is a view of an exemplary projector device identification sub-screen of the embodiment of FIG. 3.

[0024]FIG. 15 is a view of an exemplary multiple projector device settings sub-screen of the embodiment of FIG. 3.

[0025]FIG. 16 is a view of an exemplary new location addition sub-screen of the embodiment of FIG. 3.

[0026]FIG. 17 is a flow diagram of a method of remotely controlling a network-enabled projector device according to an embodiment of the present invention.

[0027]FIG. 18 is a block diagram of an exemplary message format suitable for use with the embodiment of FIG. 17.

[0028]FIG. 19 is a block diagram of a second exemplary message format suitable for use with the embodiment of FIG. 17.

[0029]FIG. 20 is a block diagram of an example query/response transaction according to the embodiment of FIG. 17.

[0030]FIG. 21 is a block diagram of an example command/response transaction according to the embodiment of FIG. 17.

[0031]FIG. 22 is a flow diagram of a method of automatically alerting of a changed state of a projector device according to another embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] One embodiment of a projector device management system according to the present invention is shown generally at <b>10</b> in FIG. 1 as a plurality of network-enabled projector devices <b>12</b>, <b>16</b> connected to a computer network <b>14</b>. Some projector devices <b>12</b> may have built-in networking capabilities that allow them to communicate directly over network <b>14</b> with other network devices. Other projector devices, as illustrated at <b>16</b>, may be may not have built-in networking capabilities. In this case, projector device <b>16</b> may be connected to network <b>14</b> via a network adaptor device <b>18</b> disposed between the projector device and the network that enables the projector device to communicate over the network. Examples of suitable adaptor devices <b>18</b> include, but are not limited to, hardware adaptor devices available from the Lantronix Corporation, such as the Lantronix UDS-10 network adaptor, and software adaptors, such as the Win32 Client and the C13 Client, both for personal computers (PCs) running a Microsoft Windows operating system.

[0033] A server computing device <b>20</b> is also connected to network <b>14</b>. Server computing device <b>20</b> includes software, firmware and/or hardware configured to communicate with projector devices <b>12</b> and <b>16</b> to allow the projector devices to be controlled, monitored and managed from a remote location. For example, server computing device <b>20</b> may be configured to poll each projector device <b>12</b>, <b>16</b> for information regarding the current status of each projector device, and to store the most recent status information from each projector device so that a user can access the most recent status information of a selected projector device at will. Furthermore, server computing device <b>20</b> may be configured to allow the status of some projector device features and/or functions to be changed over the network.

[0034] Server computing device <b>20</b> may be configured to allow the monitoring and/or change of the status of any suitable projector device feature or function over network <b>14</b>. Examples of features that may be both monitored and changed over network <b>14</b> include, but are not limited to, the status of a power switch (on/off), current image source, whether the projector device is configured for ceiling- or table-mounting, and whether the projector device is configured to be in rear projection mode. Examples of features that may be monitored, but not necessarily changed, over network <b>14</b> include, but are not limited to, remaining lamp hours, status of the projector device cooling fan (operational/not operational), projector device temperature (below threshold/above threshold), projector device model name, projector device firmware revision number, and projector device serial number.

[0035] Besides allowing the status of various projector device functions to be monitored, server computing device <b>20</b> may also be configured to send an alert to another network device whenever a change in a selected status is detected. For example, if server computing device <b>20</b> polls a projector device for its status and finds that the projector device lamp has burned out, the server computing device may send a message to another network device to alert a selected user or administrator of the change in lamp status. Likewise, if server computing device <b>20</b> is unable to establish a connection with a selected projector device, indicating that the selected projector device is no longer connected to the network, the server computing device may send a message to another network device to alert the selected user or administrator that the projector device has been disconnected from the network, or possibly stolen.

[0036] System <b>10</b> also includes one or more client computing devices <b>22</b>. Three client computing devices <b>22</b> are shown in the depicted embodiment. Client computing devices <b>22</b> are configured to allow users to interact with server computing device <b>20</b> to manage projector devices <b>12</b> and <b>16</b> from locations remote from the server computing device. Moreover, the use of client computing devices <b>22</b> allows more than one user at a time to interact with server computing device <b>20</b>.

[0037]FIG. 2 shows generally at <b>30</b> a block diagram of an exemplary architecture of a projector management system according to the present invention. System <b>30</b> includes a projector manager <b>32</b>, typically implemented as software on server computing device <b>20</b>, configured to interact with a projector manager controller <b>34</b>, which is typically implemented as software on client computing devices <b>22</b>. Projector manager <b>32</b> is also configured to interact with software in network adaptor <b>18</b> and network-enabled projector devices <b>12</b> to perform any desired projector device management tasks, including, but not limited to, the monitoring and control functions listed above. This is described in more detail below. While only two projector devices are shown connected to projector manager <b>32</b> in the depicted embodiment, any other desired number of projector devices, and typically all projector devices within an entity, may be connected to the projector manager.

[0038] Projector manager <b>32</b> may have any suitable architecture for interacting in a desired manner with projector manager controller <b>34</b>, projector devices <b>12</b> and <b>16</b>, and network adaptor <b>18</b>. One example of a suitable architecture is shown in FIG. 2. In the depicted embodiment, projector manager <b>32</b> includes three major components: a set of services <b>36</b> configured to perform the functional aspects of projector management, a set of translators <b>38</b> to translate queries and commands sent from the projector manager to projector devices that utilize a command language different than that of projector manager <b>32</b>, and a database <b>40</b> to store information related to the projector devices, approved users, etc. It will be appreciated that the term “service” as used herein denotes a program or process that performs a certain function, and may have any desired form and operate in any desired operating environment. For example, services <b>36</b> of the present invention, when implemented in the environment of a Microsoft WINDOWS NT operating system, may take the form of NT services, which are executables that communicate and interface with the NT operating system in a known manner.

[0039] The various processes that are used to interact with the projector devices, network adaptors and projector manager controller <b>34</b> are organized into four services <b>36</b> in the exemplary architecture of FIG. 2. These four services may be described as a “locator” service <b>42</b>, an “administration” service <b>44</b>, a “directory” service <b>46</b> and a “telnet” service <b>48</b>.

[0040] Locator service <b>42</b> is responsible for locating various “resources” on the system, such as the other services and, indirectly, any projector devices <b>12</b>, <b>16</b> connected to projector manager <b>32</b>. Locator service <b>42</b> thus may serve as the central communications controller for projector management system <b>30</b>. Locator service <b>42</b> also may be configured to keep track of registered users and store their access rights, typically in database <b>40</b>. Thus, locator service <b>42</b> also may be configured to control the logon function of projector manager <b>32</b>, and to prevent unregistered users from gaining access to the projector manager.

[0041] Locator service <b>42</b> allows all components in projector management system <b>30</b> to be configured with a single “reference point” (for example, a DNS/WINS computer name or static IP address), regardless of how many devices or servers are connected to the projector management system. Thus, in a large entity with many projector devices, more than one administration service <b>44</b> may be run on different server computing devices, and locator service <b>42</b> may direct different projector devices <b>12</b>, <b>16</b>, network adaptors <b>18</b>, and/or projector manager controllers <b>34</b> to the different administration services for the most efficient use of system resources. Likewise, more than one directory service <b>46</b> and telnet service <b>48</b> may also be run on different server computing devices.

[0042] The use of multiple server computing devices running multiple administration services <b>44</b> may offer various advantages in some situations. Some examples are as follows. First, where the number of projector devices within an entity is large (for example, 100+), locator service <b>42</b> may be configured to divide the projector load between two or more administration services <b>44</b> on separate server computing devices. This load balancing function may be performed either dynamically or statically based upon network attributes such as IP subnet, etc. Second, in an entity with multiple physical locations, the installation of an administration service <b>44</b> at each physical site may help to minimize network traffic between sites. In this manner, a projector device <b>12</b> or network adaptor <b>18</b> may query locator service <b>42</b> to determine which administration service <b>44</b> to use, after which all communication between that projector device or network adaptor and its corresponding administration service may occur within the same site. Third, in a multiple administration service implementation, user privileges may be assigned on a per server basis. This may allow one individual to monitor projector devices in one building while another monitors projector devices in another building. Similarly, a network administrator could limit the access of selected users to one or more specific servers.

[0043] Administration service <b>44</b> may be configured to perform functions related to the administrative aspects of projector device management. For example, administration service <b>44</b> may be configured to poll projector devices <b>12</b>, <b>16</b> to determine their current state, to set projector device parameters when directed by a user, and to implement features that are automatically performed in the background, for example, auto-shutdown and theft detection routines. Administration service <b>44</b> may also be configured to synthesize projector device “events.” A projector device event is a condition, such as the reported bulb life reaching or exceeding a predetermined threshold, that requires action or intervention by a user. Administration service <b>44</b> may maintain a log of events for review at the user's convenience. Administration service <b>44</b> may also send an email notification of some or all events for more immediate response.

[0044] Directory service <b>46</b> may be configured to perform functions related to keeping track of the physical location of all resources. The information within directory service <b>46</b> may be organized in any desired fashion. For example, directory service <b>46</b> may allow a user to build a database of conference rooms within an entity's facilities. This database may have a “flat” structure, in the form of a simple list of rooms, or may have a hierarchical structure, with location objects such as country, city, campus, building and/or floor. This allows the formation of a geographical reference for a projector device. Thus, administration service <b>44</b> may identify a networked projector device by its IP and/or MAC address, while directory service <b>46</b> allows the networked projector device to be labeled with a geographical reference. The implementation of directory service <b>46</b> as a separate service from administration service <b>44</b> may allow the implementation of scheduling capabilities that allow individual users with low privilege levels to request and/or reserve a specified projector device in a desired conference room at a specified time.

[0045] Telnet service <b>48</b> may be configured to communicate with projector devices <b>12</b>, <b>16</b> and/or network adaptors <b>18</b> that communicate via telnet protocols. Telnet service <b>48</b> may be configured to perform these functions either on its own, or in cooperation with administration service <b>44</b>.

[0046] Translators <b>38</b> are configured to translate commands and/or queries from services <b>36</b> into the native command language or languages for each of projector devices <b>12</b> and <b>16</b>, and network adaptor <b>18</b>, and to translate responses from the projector devices and network adaptor into the command language utilized by the services. Translators <b>38</b> may be configured to communicate with projector manager <b>32</b> in any desired language. One exemplary language in which translators <b>38</b> may communicate with services <b>36</b> is PCML, or projector control markup language, an XML-based language described in U.S. patent application Ser. No. ______ of James D. Wenban and Robin F. Hoeye for a Projector Control Markup Language, filed simultaneously with this application, the disclosure of which is hereby incorporated by reference. While the translators of the depicted embodiment are shown as being part of projector manager <b>32</b>, translators may instead be provided within projector devices <b>12</b>, <b>16</b> and/or network adaptor <b>18</b>, or as a separate component at any suitable point(s) along the communication path(s) between services <b>36</b> and the projector devices and network adaptor. It will be appreciated that some projector devices may be configured to utilize the same command language as projector manager <b>32</b>, and that in these instances the projector device and projector manager may communicate without the use of a translator.

[0047] Database <b>40</b> is configured to store information related to projector devices and registered users. The use of database <b>40</b> to store user and projector device information may offer several advantages over other data storage systems. For example, projector devices <b>12</b> and <b>16</b> may not always be on-line. Storing the last polled state of each projector device allows the configuration of a selected projector device to be examined even if the selected projector device cannot be directly queried. Furthermore, the use of database <b>40</b> allows information regarding the projector devices to be easily updated, and information regarding new projector device models to be easily added.

[0048] Projector manager controller <b>34</b> provides an interface with which a user may communicate with projector manager <b>32</b>. Projector manager controller <b>34</b> interacts with each service <b>36</b>, and may be responsible for obtaining data from each service <b>36</b> and combining this data into an integrated view of the entire system for the user. Thus, where system <b>30</b> utilizes an IP network, each projector manager controller <b>34</b> running (typically one per client computing device) maintains an active TCP/IP connection with each service <b>36</b>. Projector manager controller <b>34</b> may have any suitable form that provides for these capabilities. For example, where projector manager <b>32</b> is configured to operate within a WINDOWS NT operating system, projector manager controller <b>34</b> may take the form of an MMC (Microsoft Management Console) snap-in. In this implementation, the snap-in may be distributed to all users on a network who may be involved in the management of network projector devices in some capacity. This may allow multiple users to run projector manager controller <b>34</b> and connect to projector manager <b>32</b> at the same time. Likewise, projector manager controller <b>34</b> may utilize an active web page on which a user may enter commands. Such a system may be suitable for use on a wider range of operating systems, for example, UNIX- or LINUX-based systems.

[0049] Projector manager controller <b>34</b> may be configured to support multiple user privilege levels, wherein each privilege level allows a user at that privilege level to perform a different subset of functions to projector devices <b>12</b>, <b>16</b>. One exemplary scheme of privilege levels is as follows. A primary administrator of projector device management system <b>30</b> may need access to all functions of projector manager controller <b>34</b> to have the capability to fully manage the projector device management system. Thus, a first, or “administration,” privilege level, could be defined that allows a primary administrator to access and perform all available functions of projector manager controller <b>34</b>.

[0050] In some entities, more than one person may be responsible for administrating the entity's projector devices. Thus, there may be one or more secondary administrators. Through the use of a second, somewhat narrower “facilities” privilege level, these secondary administrators may be allowed to perform all of the functions of projector manager controller <b>34</b> that go to the management of projector devices, while being denied the ability to perform functions related to managing users and/or configuring projector manager <b>32</b>.

[0051] Besides the two administrative privilege levels, an even more limited “help desk” privilege level may be provided for users who may wish to have the ability to access a more limited set of functions of projector manager controller <b>34</b>. The “help desk” privilege level may allow a user to perform simple functions related to the operation of selected projector devices, such as turning a projector device off or on, but restrict the user from performing any administrative tasks.

[0052] The various functions that may be performed on projector manager <b>32</b> and projector devices <b>12</b>, <b>16</b> may be grouped into the various privilege levels in any desired manner. Table I gives an exemplary list of some possible functions of projector manager controller <b>34</b>, and an exemplary privilege level assignment for each. It will be understood that the functions and grouping of functions within each privilege group is merely exemplary, and that the functions may have any other suitable privilege assignments. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><colspec colname="2" colwidth="70PT" align="left" /><thead><row><entry /><entry namest="OFFSET" nameend="2" align="center">TABLE I</entry></row><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Administrative Function</entry><entry>Privilege Group</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>Add and/or remove servers</entry><entry>Administration</entry></row><row><entry /><entry>Configure IP addresses, server names,</entry><entry>Administration</entry></row><row><entry /><entry>TCP/IP ports</entry></row><row><entry /><entry>View current server status</entry><entry>Administration</entry></row><row><entry /><entry>Add and remove users</entry><entry>Administration</entry></row><row><entry /><entry>Set user privileges</entry><entry>Administration</entry></row><row><entry /><entry>Import and view projector device model</entry><entry>Facilities</entry></row><row><entry /><entry>information</entry></row><row><entry /><entry>Set projector device location</entry><entry>Facilities</entry></row><row><entry /><entry>Remove projector device from server</entry><entry>Facilities</entry></row><row><entry /><entry>database</entry></row><row><entry /><entry>Set event definition parameters</entry><entry>Facilities</entry></row><row><entry /><entry>(including e-mail address)</entry></row><row><entry /><entry>View event log and delete entries</entry><entry>Facilities</entry></row><row><entry /><entry>Add, remove, and edit Directory</entry><entry>Facilities</entry></row><row><entry /><entry>information</entry></row><row><entry /><entry>View current projector device list with</entry><entry>Facilities</entry></row><row><entry /><entry>projector device status information</entry></row><row><entry /><entry>Monitor projector device status in real</entry><entry>Help Desk</entry></row><row><entry /><entry>time</entry></row><row><entry /><entry>Update projector device setting,</entry><entry>Help Desk</entry></row><row><entry /><entry>including power, input source, etc.</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0053] As mentioned above, where projector manager <b>32</b> is configured to operate within a WINDOWS NT operating system, projector manager controller <b>34</b> may take the form of an MMC (Microsoft Management Console) snap-in. FIG. 3 shows, generally at <b>50</b>, an exemplary user interface for an MMC-implemented projector manager controller. Interface <b>50</b> includes a left-side window <b>52</b> that displays the overall architecture of projector manager controller <b>34</b> in the form of a hierarchical series of nodes which are selectable via an input device, such as a mouse, and a right-side window <b>54</b> that displays the sub-notes that are located within a selected node.

[0054] Interface <b>50</b> may also include a tool bar <b>55</b> with controls that allow quick access to some commonly selected functions. For example, tool bar <b>55</b> may include a “view” control <b>101</b> that allows a user to customize the format of the arrangement and/or appearance of icons in left side window <b>52</b> and right side window <b>54</b>. User interface <b>50</b> may also include a “back” control <b>103</b> to move back one selection, a “forward” control <b>105</b> to go forward one selection, an “up” icon <b>106</b> to go up to the next highest node, a show/hide console tree icon <b>107</b> for revealing or hiding the console tree in left side window <b>52</b>, a refresh icon <b>108</b> for refreshing the information displayed by user interface <b>50</b>, an export icon <b>109</b> for exporting information from user interface <b>50</b> into an external file, and a help icon <b>111</b> that opens a help screen. While the user interface is depicted in the context of an MMC interface, it will be appreciated that the user interface may have any other suitable form. Examples of other suitable user interfaces include, but are not limited to, a Web-based interface in which a set of web pages may be used to present the same information that is depicted herein in the MMC context. The use of a Web-based interface may allow user interface <b>50</b> to be used with a larger set of operating systems than an MMC-based interface.

[0055] Referring to left-side window <b>52</b>, all nodes relating to the administration of projector devices <b>12</b>, <b>16</b> are located in a single “administration console” node <b>56</b> underneath a root console node <b>58</b>. In the depicted embodiment, administration console node <b>56</b> and root console node are labeled “console” to signify that it corresponds to a console file (a preselected set of MMC snap-in files) being run by the MMC application. However, root node <b>56</b> may have any other suitable label.

[0056] Administration console root node <b>56</b> is the node under which all functions and features of projector manager controller <b>34</b> are organized. A plurality of nodes may be provided under administration console root node <b>56</b> to help organize the various functions and features of projector manager controller <b>34</b>. In the depicted embodiment, interface <b>50</b> includes a “services” node <b>60</b>, a “users” node <b>62</b>, an “events” node <b>64</b>, a “projectors” node <b>66</b>, and a “directory” node <b>68</b>.

[0057] Selection of services node <b>60</b> in left-side window <b>52</b> causes the names of each service to appear in right-side window <b>54</b>. When services node <b>60</b> is selected, the names of the services appear under a “names” heading <b>70</b> in right-side window <b>54</b>, and a brief legend describing the purpose and/or contents of each service may also appear under a “description” heading <b>72</b> in right-side window <b>54</b>. Names heading <b>70</b> and description heading <b>72</b> appear in a general headings section <b>74</b> of right-side window <b>54</b>. Headings besides names heading <b>70</b> and description heading <b>72</b> may appear in general headings section <b>74</b> which may display different headings depending upon the node being displayed.

[0058] One or more sub-nodes may be located beneath services node <b>60</b>. In the depicted embodiment, one sub-node for each service appears beneath services node <b>60</b>. “Master services” sub-node <b>76</b> corresponds to locator service <b>42</b>, “administration services” sub-node <b>78</b> corresponds to the administration service <b>44</b>, “directory services” sub-node <b>80</b> corresponds to directory service <b>46</b>, and “telnet services” sub-node <b>82</b> corresponds to telnet service <b>48</b>. Selection of any of these service sub-nodes results in the display of information about that particular service in right-side window <b>54</b>. Examples of information that could be displayed about each service include, but are not limited to, the machine name of the server on which the selected service is located, and whether the service is currently running or is stopped. While one sub-node for each service appears under services node <b>60</b>, either more or fewer sub-nodes may appear here, depending upon how the user interface is organized.

[0059] Users node <b>62</b> also may have a plurality of sub-nodes. In the depicted embodiment, users node <b>62</b> has a sub-node for each user privilege group: an “administrators” sub-node <b>84</b>, a “facilities users” sub-node <b>86</b>, and a “help-desk users” sub-node <b>88</b>. Selection of any of sub-nodes <b>84</b>, <b>86</b> or <b>88</b> may result in the identification of individuals registered with that particular privilege level in right side window <b>54</b>.

[0060] Events node <b>64</b> may include one or more sub-nodes that are selectable to display a corresponding list of events in right side window <b>54</b>. Events may be organized under events node <b>64</b> in any desired manner. In the depicted embodiment, events node <b>64</b> includes an “event definitions” sub-node <b>90</b>, a “master event log” sub-node <b>92</b>, and a “new events” sub-node <b>94</b>. Selection of event definitions sub-node <b>90</b> may result in the display in right side window <b>54</b> of the types of event notifications supported by projector manager <b>32</b> and the email address to be contacted for an occurrence of each event. Examples of some events that may be supported include, but are not limited to, bulb life threshold, projector device theft (triggered when projector manager <b>32</b> is no longer able to communicate with a selected projector device), high temperature, clogged fan, and the receipt of a diagnostic code indicating an internal error condition from a projector device.

[0061] Master events log contains a list of all events, both new and old, that have occurred to the projection devices installed on system <b>30</b> that have not yet been deleted from the log. Selection of master event log sub-node <b>92</b> may be configured to display the complete log, or any desired subset of events. For example, master event log may be configured to display a list of all events that have occurred over a selected time period, or events that occurred only when e-mail notification was active. Events in master event log sub-node <b>92</b> may be configured to remain in the log until deleted by a user, or may be configured to be automatically deleted, for example, after the expiration of a selected time period. Furthermore, the events in listed master event log sub-node <b>92</b> may be configured to be viewable by location, event, type, date, or any other desired field to provide easy access to the data.

[0062] Whereas selection of master event log sub-node <b>92</b> typically results in the display of a list containing both new and old events, selection of new events sub-node <b>94</b> may be configured to result in the display of a log of new events that have not yet been attended to by an administrator. The list of events may include such information as the time an event occurred, the projector device on which the event occurred, the location of the projector device, and a description of the event. New events sub-node <b>94</b> may be configured to retain event notifications in the log until acted upon by an administrator, as described in more detail below.

[0063] Next, projectors node <b>66</b> may include one or more sub-nodes in which information regarding the projector devices may be accessed. Information regarding the projector devices may be organized in any desired manner. In the depicted embodiment, projectors node <b>66</b> includes a “projector models” sub-node <b>96</b>, an “installations” sub-node <b>98</b>, and a “help-desk users” sub-node <b>99</b>. Selection of projector models sub-node <b>96</b> may be configured to result in the display of a list of projector models supported by projector manager <b>32</b>, and may also be configured to result in the display of various information related to each projector model, including, but not limited to, the rated lamp life of each available projector device, the projector device and internal asset number, the hardware version, whether the projector device can be configured for ceiling mount and/or rear projection, whether the projector device supports excessive temperature reporting, filter change notification, the sending of diagnostic codes to projector manager <b>32</b>, disconnect reporting, and/or theft detection. The information related to each projector device model is typically configured to be read-only so that users can only view data for a specific projector device model. This information may be stored in files that can be periodically updated to support new projector device models.

[0064] Selection of installations sub-node <b>98</b> may be configured to result in the display of a list of all projector devices that are installed on system <b>30</b>. A projector device may then be selected from the displayed list to view information about the selected projector device. The information regarding individual projector devices that is displayed under installations sub-node <b>98</b> may be entered by a user, or may be “discovered” by projector manager <b>32</b> when a new projector device is connected to system <b>30</b> if the new projector device is configured to announce its presence on the system upon connection to the system. Any desired information regarding a projector device may be displayed upon selecting a projector device from the displayed list. Examples of projector device information include, but are not limited to, the projector device's location, model information, current operating parameters (bulb life, input source, etc.), and asset data.

[0065] Selection of help-desk users sub-node <b>99</b> may be configured to display similar information as the selection of installations sub-node <b>98</b>, but typically displays a more limited sub-set of information restricted to the information to which access is allowed by users with a help-desk privilege level. An example of information regarding a selected projector device that may be displayed upon selection of help-desk users sub-node <b>99</b> includes information regarding whether the projector device power is on or off, a current input source, and whether a projector device is configured for table- or ceiling-mounted use. Likewise, information that is more administrative in nature, such as information regarding projector device bulb life, firmware version, serial number, etc. may be restricted from view under help-desk users sub-node <b>99</b>.

[0066] Selection of directory node <b>68</b> may be configured to result in the display of one or more organizational sub-nodes that allow the location of a selected projector device to be found based upon the physical location of the selected projector device. Thus, an administrator may view the properties of a projector device by locating within the directory node the conference room in which the projector device is kept. The sub-nodes of directory node <b>68</b> may be organized in any desired manner. In the depicted embodiment, directory node <b>68</b> includes sub-nodes arranged in a geographical manner, with a top “country” sub-node <b>100</b>, an intermediate “city” sub-node <b>102</b>, and a lower “campus” sub-node <b>104</b>. This structure may allow an administrator to quickly and easily locate and manage a projector device in a different country, city, or on a different campus.

[0067] As described above, selection of each node or sub-node displayed within user interface <b>50</b> results in the display of various information related to the selected node or sub-node. User interface <b>50</b> may also be configured to allow various functions to be performed within each node and sub-node. In the depicted embodiment, functions may be performed via the selection of an “action” control <b>110</b>. Operation of action control <b>110</b> may result in the opening of a pull-down menu (or other selection interface) that lists one or more actions related to the selected sub-node that may be performed. For example, operation of action control <b>110</b> while administration console node <b>56</b> is selected may open a sub-screen or dialog box that shows the machine name and/or IP or other network address of the locator service and the TCP/IP port used by the locator service, and also may allow these values to be changed and exported.

[0068] Operation of action control <b>110</b> while master services sub-node <b>76</b> is selected may be configured to open a dialog box that allows the location of locator service <b>42</b> to be displayed and/or set. An example of a suitable dialog box to allow control of locator service <b>42</b> is shown at <b>120</b> in FIG. 4 as a “master services properties” dialog box. Master services properties dialog box <b>120</b> includes a locator service address field <b>122</b> that allows the locator service location to be specified either by machine name or by IP address. Master services properties dialog box <b>120</b> also may include a software version field <b>124</b> that is automatically updated with software updates, and, where more than one locator service is in use, a selection box <b>126</b> that allows a user to select which locator service is the primary locator service. Master services properties dialog box <b>120</b> may also include fields allowing TCP/IP ports to be selected for various functions. In the depicted embodiment, the “master client” field allows a TCP/IP port to be selected for communication between a projector device and locator service <b>42</b>, the “admin client” field allows a port to be selected for communication between the projector device and admin service <b>44</b>, the “master MMC” field allows a port to be selected for communication between projector manager controller <b>34</b> (here, in the form of an MMC plug-in) and the locator service, and the “admin MMC” field allows a port to be selected for communication between the projector manager controller and the admin service.

[0069] Under some sub-nodes, more than one action may be available when action control <b>110</b> is operated. For example, operation of action control <b>110</b> while administration services sub-node <b>78</b> (FIG. 3) is selected may allow a user to select the IP and/or machine name address for administration service <b>44</b>, and perform functions related to the administration of all projector devices connected to projector manager <b>32</b>. An example of a suitable dialog box that allows both of these functions to be performed is shown generally in FIG. 5 at <b>130</b> as an “admin properties” dialog box. Admin properties dialog box <b>130</b> includes an administration service tab <b>132</b> and a default shutdown schedule tab <b>134</b>. Selection of the administration service tab brings an administration services sub-dialog box <b>136</b> forward, thus allowing selection of the machine name and/or IP address of the machine on which the administration services is to reside. The administration services sub-dialog box <b>136</b> may also show other information related to the administration services, including, but not limited to, the current administration service <b>44</b> software version.

[0070] On the other hand, selection of default shutdown schedule tab <b>134</b> on admin properties dialog box <b>130</b> brings a default shutdown schedule sub-dialog box <b>138</b> forward, as shown in FIG. 6. In the exemplary dialog box <b>138</b>, default shutdown schedule sub-dialog box <b>138</b> allows a default shutdown time for all of the projector devices on system <b>30</b> to be set by the day of the week via selection of desired default shutdown days from day-of-the-week (or month, etc.) field <b>140</b>, and selection of a desired shutdown time from time-selection pull-down menu <b>142</b>. The auto shutdown feature to be enabled or disabled by selecting “enable” box <b>144</b>. The selected default shutdown schedule may be overridden by setting a default shutdown schedule for individual projector devices within projectors node <b>66</b>, as described in more detail below.

[0071] The auto shutdown feature may be configured to shut down a projector device only once during a shutdown period. For example, if the selected shutdown time is 8 PM every day and the projector device is polled at 8:01 PM, the projector device will be shut down. However, if the projector device is manually turned on at 8:05 PM and is again polled at 8:06 PM, it will not be shutdown until 8:00 PM the next day.

[0072] When users node <b>62</b> is selected in left side window <b>52</b> (FIG. 3), operation of action control <b>110</b> allows properties related to the users to be changed. For example, action control <b>110</b> may allow a dialog box for adding a new user, as shown generally at <b>150</b> in FIG. 7, to be opened. New user dialog box <b>150</b> may include a “user info” field <b>152</b> for entering the name of a new user, and a “privileges” field <b>154</b> for selecting the privilege level of a new user. Operation of action control <b>110</b> while any of the users sub-nodes <b>84</b>, <b>86</b> or <b>88</b> is selected may be configured to open new user dialog box <b>150</b> to open, with the privileges level appropriate for the selected sub-node set as default. Furthermore, selection of action control <b>110</b> while a name of a user in sub-nodes <b>84</b>, <b>86</b> or <b>88</b> is selected may allow the privilege level of the selected user to be changed.

[0073] When events node <b>64</b> (FIG. 3), or any of events sub-nodes <b>90</b>-<b>94</b> is selected, operation of action control <b>110</b> may be configured to allow actions related to the definition of events and sending of events notices to be performed. For example, when a particular event type under events definition sub-node <b>90</b> is selected, operation of action control <b>110</b> may be configured to open a dialog box that allows the configuration of e-mail notification for the selected event to be configured. An example of an event configuration dialog box is shown generally at <b>160</b> in FIG. 8. Event configuration dialog box <b>160</b> may include an “event type” field <b>162</b> that defines the event controlled by dialog box <b>160</b>. Typically, there is an event type dialog box for each event supported by projector manager <b>32</b>. In the depicted embodiment, event type field <b>162</b> indicates that the event type controlled by event configuration dialog box <b>160</b> is a “low lamp life event” that indicates when a preselected remaining (or expired) lamp life threshold has passed. Event configuration dialog box <b>160</b> also may include a notification field <b>164</b> that allows selection of a user to whom notification of the low lamp life event is to be sent. Notification field <b>164</b> may also be configured to allow the e-mail notification feature to be enabled or disabled by the selection of an enablement box <b>166</b>.

[0074] Besides allowing a notification email address to be selected, event configuration dialog box <b>160</b> also may include, where appropriate, fields configured to allow event parameters to be set. For example, in the depicted embodiment, event configuration dialog box <b>160</b> includes an event parameter field <b>168</b> that allows a “remaining lamp life hours” threshold that triggers notification to be set.

[0075] As described above, when a new event occurs, the event may be logged into both master event log <b>92</b> and new event log <b>94</b> (FIG. 3). Selection of the new event in either of these event logs, and then operation of action control <b>110</b>, may be configured to open an event description dialog box, shown generally at <b>170</b> in FIG. 9. Event description dialog box <b>170</b> may include an information field <b>172</b> that sets forth information regarding the event. Examples of information regarding the event included in information field <b>172</b> include, but are not limited to, event type (“low lamp threshold”), the date on which the event occurred, the model number of the projector device on which the event occurred, the location of the projector device on which the event occurred, and a description of the event.

[0076] Event description dialog box <b>170</b> may also include an event status field <b>174</b> that allows new events and old events to be distinguished. New events and old events may be distinguished in any desired manner. In the depicted embodiment, event status field <b>174</b> includes a check box <b>176</b> (or other suitable mechanism) that signifies whether the event has been handled. The event may remain in new events log <b>94</b> until check box <b>176</b> is checked by an administrator or user in charge of handling that particular event. After taking care of the event, the administrator or user may put a check in check box <b>176</b> indicating that the event has been handled, causing the event to be removed from new events log <b>94</b>.

[0077] When projectors node <b>66</b> (FIG. 3), or any of projectors sub-nodes <b>96</b>-<b>99</b> is selected, operation of action control <b>110</b> may be configured to allow actions related to projector device setup and control to be performed. For example, when projector models node <b>96</b> is selected, operation of action control <b>110</b> may be configured to allow information related to new projector device models to be imported into projector manager <b>32</b>, thus permitting compatibility with new projector device models as they arrive. Information regarding the properties and capabilities of a selected projector device model (for example, whether a projector device model can store and/or report a serial number, asset number, bulb life, hardware version, overheating, filter change notify, diagnostic codes, disconnect, theft detection, parameter lockout capabilities/settings, ceiling mount capabilities/settings, rear projection capabilities/settings, etc.) may also be accessed from projector models sub-node <b>96</b>. This information may be displayed in any suitable format, for example, by a model information dialog box such as that shown generally at <b>176</b> in FIG. 10. Model information dialog box <b>176</b> may include a general field <b>178</b> giving such information as the model name and rated lamp life, and may also include a capabilities field <b>179</b> listing the capabilities of the selected projector device.

[0078] Selection of projectors installations sub-node <b>98</b> (FIG. 3), combined with operation of action control <b>110</b>, may be configured to allow new projector devices to be added to database <b>40</b> in projector manager <b>32</b>. New projector devices may be added to database <b>40</b> in any suitable manner. One example is shown generally at <b>180</b> in FIG. 11 as an “add a projector” dialog box. “Add a projector” dialog box <b>180</b> may include an IP address field <b>182</b> where a user or administrator with the correct privilege level may enter the network address of the new projector device (or network adapter), a projector model field <b>184</b> where the user or administrator may enter the model of the projector device, and a projector location field <b>186</b> where the user or administrator may enter the geographical location of the projector device. Any other suitable information in addition to the IP address, projector device model, and projector device location may be entered while adding a new projector device. In the embodiment depicted in FIG. 11, “add a projector” dialog box includes a “next” button <b>188</b> that allows a user to open a second dialog box (not shown) to enter information related to a new projector device installation. Examples of further information related to a new projector device installation that may be entered in a second dialog box (not shown) include, but are not limited to, information related to a default shutdown schedule for the new projector device. This information may be entered into a second dialog box (not shown) that is similar to that shown in FIG. 6 for the overall system default shutdown schedule, and may be configured to permit the selected projector device to override the overall system default shutdown schedule.

[0079] In some embodiments of the present invention, projector devices <b>12</b>, <b>16</b>, and/or network adaptor <b>18</b> may be configured to contact locator service <b>42</b> automatically upon being connected to system <b>30</b>. In these embodiments, a projector device being connected to system <b>30</b> needs to know only the IP address (or DNS name) and port of the locator service <b>42</b> that is responsible for controlling the projector device. In these embodiments, the projector device first creates a socket connection with locator service <b>42</b>. The projector device then sends locator scrvice <b>42</b> a message asking for the IP address and port of the administration service <b>44</b> that will administer the projector device. Locator service <b>42</b> responds by sending the projector device a message containing this information. The projector device then opens a connection, for example, a socket connection, to administration service <b>44</b> and sends the administration service a message to begin polling. This message contains the projector device's IP address and port. If administration service <b>44</b> is willing to accept the projector device (the administration service may refuse to poll a projector device, for example, if the device model is not supported by the administration service), the administration service sends an accept message to the projector device that contains a “lease period.” The lease period tells the projector device that administration service <b>44</b> will poll the projector device before the lease period expires. If administration service <b>44</b> fails to poll the projector device before the end of the lease period, the projector device may be configured to try one or more times to restart the polling process. If this fails, the projector device may be configured to go back to locator service <b>42</b> and restart the process anew. Once administration service <b>44</b> accepts a projector device, it may begin to poll the projector device.

[0080] When installations sub-node <b>98</b> is selected in left side window <b>52</b> (FIG. 3), projector manager controller <b>34</b> may be configured to display a list of projector devices installed on system <b>30</b> in right side window <b>54</b>. Selection of any projector device from the list, followed by operation of action control <b>110</b>, may be configured to display information related to the selected projector device. Any suitable information regarding the selected projector device may be displayed. One example of information regarding a selected projector device that may be displayed is shown in FIG. 12 as projector information dialog box <b>190</b>. Projector information dialog box <b>190</b> includes a general information sub-dialog box <b>192</b> that includes such information as the IP address (or other network address), the model number, the location, the software/firmware version, and the MAC (Media Access Control) address of the selected projector device. Furthermore, projector information dialog box <b>190</b> may include other sub-dialog boxes containing other information on the selected projector device, such as a shutdown schedule sub-dialog box, viewable by selection of tab <b>194</b> that displays the shutdown schedule of the selected projector device.

[0081] Operation of action control <b>110</b> while installations sub-node <b>98</b> (FIG. 3) is selected may be configured to display projector device status information, and may also be configured to allow the change of various projector device settings. It will be appreciated that many of the functions described below may also be accessed from help desk sub-node <b>99</b>, where the privilege levels of the functions permit.

[0082]FIG. 13 shows generally at <b>200</b> an example of a projector information and properties dialog box that displays various status information regarding a particular projector device, and also allows a user or administrator to change selected projector device settings. Projector information and properties dialog box <b>200</b> includes a last reported status sub-dialog box <b>202</b> that sets forth the status of thc selected projector device the last time the selected device was polled by projector manager <b>32</b>. Last-reported status sub-dialog box <b>202</b> may include any suitable information about the selected projector device. In the depicted embodiment, last-reported status sub-dialog box <b>202</b> includes a user-changeable settings field <b>204</b> that sets forth the current image source for the selected projector device, the image orientation, and the power status. These settings may be changed by entering the desired setting in sub-dialog box <b>202</b> and then selecting either the “OK” tab <b>206</b> (which closes the dialog box) or the “Apply” tab <b>208</b> (which leaves the dialog box open). Selection of either of these tabs may be configured to cause projector manager controller <b>34</b> to send a message to projector manager <b>32</b>, directing the projector manager to send a message to the selected projector device to implement the desired status changes. Selection of “Cancel” tab <b>209</b> closes the dialog box without sending a message to projector manager <b>32</b>.

[0083] Projector information and properties dialog box <b>200</b> also may include an identification sub-dialog box <b>214</b>, which is shown in FIG. 14. Identification sub-dialog box <b>214</b> may include a projector field <b>216</b> that sets forth the serial number of the selected projector device, and may also include an asset number field so that an administrator can assign an internal asset number to the selected projector device. Identification sub-dialog box <b>214</b> may also include a set of user-defined fields <b>216</b> that allow a user or administrator to store comments regarding the selected projector device in database <b>40</b>.

[0084] Projector manager controller <b>34</b> may also be configured to allow settings of a plurality of projector devices to be observed and/or changed at the same time, for example, by selecting multiple projector devices from installations sub-node <b>98</b> (FIG. 3), and then operating action control <b>110</b>. FIG. 15 shows generally at <b>220</b> an example of a multiple projector settings dialog box. Multiple projector settings dialog box <b>220</b> may include a settings field <b>222</b> that allows a selected setting to be changed simultaneously for each of the plurality of projector devices. In the depicted embodiment, “power on” and “power off” controls appear in settings field <b>222</b>, but any other suitable control may also be included in the settings field. Multiple projector settings dialogue box <b>220</b> also may include a projectors field <b>224</b> that lists each of the selected projector devices to be affected by operation of the control in settings field <b>222</b>.

[0085] Operation of action control <b>110</b> while directory node <b>68</b> (FIG. 3) is selected may be configured to allow a user to add new sub-locations to directory node <b>68</b>, and thus customize the structure of location nodes underneath directory node <b>68</b> to match the geographical, corporate or other structure of the user's entity. FIG. 16 shows generally at <b>230</b> an example of a new location dialog box that allows a new location to be added to directory node <b>68</b>. New location dialog box <b>230</b> includes a parent node field <b>232</b> that shows the sub-node of directory node in which the new location is to be created. Typically, a user selects the sub-node in which the new location is to be created by selecting the desired sub-node in left side window <b>52</b> of user interface <b>50</b>, but parent node field <b>232</b> may also be configured to accept the manual entry of a parent node for the new location if desired. New location dialog box <b>230</b> also includes a new location name field <b>234</b> that allows the user to assign a name to the new location. Once the name of the new location has been entered, selecting finish button <b>236</b> creates the new location.

[0086] The commands and queries described above each involve communication between projector manager controller <b>34</b>, projector manager <b>32</b>, and projector devices <b>12</b>, <b>16</b> and/or network adaptor <b>18</b>. Projector manager controller <b>34</b> and projector manager <b>32</b> may be configured to communicate in any desired manner. One suitable manner of communication follows the general steps shown generally at <b>300</b> in FIG. 17. Communication method <b>300</b> includes first accepting input, at <b>302</b>, from a user at projector manager controller <b>34</b>. Projector manager controller then sends, at <b>304</b>, a first message to projector manager <b>32</b>. The first message is configured to direct projector manager <b>32</b> to send a selected query or command to a selected projector device. Next, projector manager <b>32</b> receives, at <b>306</b>, the first message, and then sends, at <b>308</b>, a second message to the projector device. The second message is configured to query the projector device of its current state, to command the projector device to change its current state, and/or other such functions related to the management and control of the projector device.

[0087] The user input may be accepted at the projector manager controller in any suitable manner. Examples of suitable methods of accepting user input at the projector manager controller include, but are not limited to, the use of a graphical user interface that utilizes dialog boxes into which the user may enter commands, or an active web page on which a user may enter commands. Projector manager controller <b>34</b> typically sends the first message to administration service <b>44</b>, though it may send it to another service if desired.

[0088] In some embodiments of the invention, projector devices <b>12</b>, <b>16</b> and/or network adaptor <b>18</b> may not be able to accept more than one connection at a time. Thus, in these embodiments, administration service <b>44</b> may first remove the selected projector device from its polling loop before sending the second message to the selected projector device. This may be accomplished by waiting until the completion of a polling thread, and then opening a socket connection to the selected projector device before another polling thread is started.

[0089] The first and second messages may have any suitable format. For example, the second message may be sent as a PCML command or query, as described above. Likewise, in some embodiments of the present invention, the first message is a binary message that is transmitted through a TCP/IP socket that is opened by projector manager controller <b>34</b> when the projector manager controller connects to projector manager <b>32</b>. One suitable message format is shown generally at <b>310</b> in FIG. 18. Message <b>310</b> includes three sections or elements: a message header <b>312</b>, a message results section <b>314</b>, and a message body <b>315</b>. Message body <b>315</b> may include a fixed portion <b>316</b> and a variable portion <b>318</b>, as described in more detail below.

[0090] Message header <b>312</b> may contain one or more fields that describe the overall message. For example, in the depicted embodiment, message header <b>312</b> contains a field for the message length <b>320</b>. Message length field may give the total size of the message, and is useful for reading messages by the receiving party. The message length field may be read first, which allows messages to be sent that span multiple TCP/IP packets, as well as situations where two or more messages are sent as part of the same TCP/IP packet.

[0091] Message header <b>312</b> may also contain a field for the message type <b>322</b>. Message type field <b>322</b> may be used to identify the type of the message via a numerical field that matches a pre-defined message type that is stored within projector manager <b>32</b> and/or projector manager controller.

[0092] Message header <b>312</b> also may contain a field for the message ID <b>324</b>. Message ID field <b>324</b> may contain a sequential number assigned to the packet upon transmittal. This number may allow a packet to be re-transmitted upon error, and also allow messages and responses to be matched up if necessary. Message header <b>312</b> also may contain a message version field <b>326</b>, which may indicate the version of the header file that the message was generated against. Additionally, message results section <b>314</b> of message <b>310</b> may include a code indicating whether a message is a response to a query or command.

[0093] Fixed portion <b>316</b> of message body <b>315</b> may contain a set of fields specific to the message being sent. This may be implemented as a structure for each message type, and all of the structures may then be merged to form fixed portion <b>316</b>. Examples of fields that may be included in fixed portion <b>316</b> include, but are not limited to, logon information, user type, user rights, a variable portion offset field, and a variable portion length field. The variable portion offset field may contain a value corresponding to the offset from the beginning of the message body to the start of the variable field, while the variable portion length field may contain the total length of the variable field, to help the message receiver determine the starting position variable portion <b>318</b> of message body <b>315</b>.

[0094] Variable portion <b>318</b> of message body <b>315</b> contains the actual content of the message. For example, where message <b>310</b> is sent to log a user onto system <b>30</b>, the letters in the user's name are contained within variable portion <b>318</b>.

[0095] As described above, some messages may include commands to be performed on more than one projector device, or may include more than one command to be performed on a selected projector device. In these situations, the message sent at <b>302</b> may have a different format than that of message <b>310</b>. FIG. 19 shows generally at <b>330</b> an example of a suitable message format for sending multiple commands and/or queries (collectively referred to as objects) in a single message. Message <b>330</b> includes a message header <b>332</b> similar to that described above for message <b>310</b>, a message results section <b>334</b> for returning the results of the message, and a message body <b>336</b>. However, message body <b>336</b> is formatted as an object list. Thus, message body may include an object list header <b>338</b> that contains such information as the object list length <b>340</b>, the number of objects contained within object list <b>342</b>, and the object list type <b>344</b>, which contains information regarding the type of objects contained within message <b>330</b>.

[0096] Object list header <b>338</b> may include an object list offset field <b>348</b> and an object list length field <b>350</b> to help calculate the location of the start of first object <b>352</b>. Likewise first object <b>352</b> may include an object length header <b>354</b> that gives the length of the first object. Thus, first object length header <b>354</b> can be used to calculate the starting location of second object <b>356</b>. Second object <b>356</b> itself has a header that may allow the starting location of the next object to be selected. Thus, the starting location of each nth object <b>358</b> can be calculated from the header of the prior object.

[0097] Object list header <b>338</b> also may include an object list action section <b>346</b>, which may indicate what type of action is to be performed on the object list. Examples of actions that may be performed include query, add, delete, and update. For example, when a user enters a request at projector manager controller <b>34</b> to get a list of current users and their privilege levels, object list action section <b>346</b> may indicate that the action is a query. Likewise, where a user enters a list of names to be added or removed from a users list, or a list of names for which the privilege level is to be changed, object list action section may indicate that the action is an add, delete, or update action, respectively. Each name in the list is typically included in message <b>330</b> as a separate object.

[0098] Projector manager <b>32</b> may be configured to acknowledge each message that originates at projector manager controller <b>34</b> with a response message. The message/response pair may fall into either of two categories based upon the direction of information flow. When information is transferred from projector manager <b>32</b> to projector manager controller <b>34</b>, the transaction may be referred to as a query/response transaction. Likewise, when information is transferred from projector manager controller <b>34</b> to projector manager <b>32</b>, the transaction may be referred to as a command/response transaction.

[0099]FIG. 20 shows a block diagram of an exemplary query/response transaction, and FIG. 21 shows a block diagram of an exemplary command/response transaction. Referring first to FIG. 20, query <b>360</b> has the format of message <b>310</b>. Because no information is transferred in query <b>360</b>, the query contains no message body. However, response <b>362</b> to query <b>360</b> does include a message body, indicated at <b>364</b>, as information is being returned in response to the query. Also, message type section <b>365</b> may include an indication that the message is a response message. Furthermore, message results section, indicated at <b>366</b>, may include a results code to indicate that the message is a response, in addition to the results of the query.

[0100]FIG. 21 shows a block diagram of a command/response message transaction. Because information is being sent to projector manager <b>32</b> in command <b>370</b>, the command includes a message body <b>372</b> containing information relevant to the command. However, response <b>374</b> to command <b>370</b> includes no message body, as no information is returned in the response. As with response <b>362</b> of FIG. 20, response <b>374</b> may include a message type section <b>376</b> that is set to indicate that the message is a response, and also may include a message results section <b>378</b> that indicates the results of the command.

[0101] As described above, projector manager <b>32</b> may be configured to detect events that occur to projector devices <b>12</b>, <b>16</b>, and to alert a selected user or administrator via e-mail (or other suitable method) when an event occurs. FIG. 22 shows generally at <b>400</b> a flow diagram depicting the general steps involved in monitoring a selected projector device <b>12</b>, <b>16</b> for an event. First, projector manager <b>32</b> detects the current state of the projector device at <b>402</b>. Detecting the current state of the projector device is typically performed by querying the projector device for the current state of a selected projector function or feature. Examples of suitable functions or features to detect include, but are not limited to the remaining lamp life, whether power to the projector device is on or off, whether the projector device is connected or disconnected to the network, whether the cooling fan is clogged, and other similar features and/or functions.

[0102] After detecting the current state of the projector device at <b>402</b>, the current state returned by the projector device is compared to a preselected condition at <b>404</b> to see if the current state meets the preselected condition. The preselected condition may correspond to any suitable state or value for the selected feature or function. For example, where the current number of remaining lamp hours is detected at <b>402</b>, the preselected condition may correspond to a threshold number of remaining hours. Likewise, where the operability of the cooling fan of a selected projector device is detected at <b>402</b>, the preselected condition may correspond to a state in which the fan is not operating properly, or where the temperature of the projector device exceeds a threshold temperature.

[0103] If comparison of the current state of the projector device and the preselected condition at <b>406</b> shows that the current state does not meet the condition, then the current state of the projector device is again polled at <b>402</b>. However, if the current state of the projector device is determined to meet the preselected condition, an event has occurred. In this case, projector manager <b>32</b> sends an alert message at <b>408</b> to the user or administrator designated to receive alerts corresponding to the particular event, and the event may be recorded in new event log <b>94</b>.

[0104] While various alternative embodiments and arrangements for a projector device management system have been shown and described above, it will be appreciated by those skilled in the art that numerous other embodiments, arrangements and modifications are possible and are within the scope of the invention. Thus, although the present invention has been disclosed in specific embodiments thereof, the specific embodiments are not to be considered in a limiting sense, because numerous variations are possible. The subject matter of the invention includes all novel and nonobvious combinations and subcombinations of the various elements, features, functions, and/or properties disclosed herein.

[0105] The following claims particularly point out certain combinations and subcombinations regarded as novel and nonobvious. These claims may refer to “an” element or “a first” element or the equivalent thereof. Such claims should be understood to include incorporation of one or more such elements, neither requiring nor excluding two or more such elements. Other combinations and subcombinations of features, functions, elements, and/or properties may be claimed through amendment of the present claims or through presentation of new claims in this or a related application. Such claims, whether broader, narrower, equal, or different in scope to the original claims, also are regarded as included within the subject matter of the invention of the present disclosure.