Appeal 2007-0589
Application 09/852,959
16. In Boulter, rather than generate and transmit a complete
description of the status screen to the management station each time device
status changes, a set of device state information in the form of an HTML file
is transmitted, e.g., from a remotely located device monitor to the
management system. (Paragraph [0017]).
17. Boulter states that the updating of device-status information is
relatively efficient and can be done periodically or whenever a change in
device status is detected. (Paragraph [0018]).
18. In Boulter, display updates are depicted in the mimic upon
detection of a change in device status or at periodic, e.g., pre-selected
intervals. By selecting the interval between device updates to be small, a
change in device status is illustrated soon after it occurs. (Paragraph
[0030]).
19. In Boulter, mimic updates are accomplished by generating,
transmitting, and using sets of HTML files that contain device state
information, e.g., represented as a set of encoded values, as opposed to
transmitting a description of an entire mimic. (Paragraph [0056]).
20. Boulter contemplates that mimic sub-images automatically update
as a device status changes or at set periodic intervals without the need for
intervention by a user of the management system. (Paragraph [0057]).
21. In Boulter, while the process of updating a display mimic has
generally been described as being performed in response to an updated
request generated by management system 102, it is to be understood that
such updates may be initiated by monitoring system 118. Indeed, those
update requests that the monitoring system 118 initiates may take place only
6
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next
Last modified: September 9, 2013