Device management system and method
The device management system addresses the challenge of adapting to changing device statuses by prioritizing and highlighting updates or abnormalities in image forming apparatuses, ensuring user awareness and prompt action.
Patent Information
- Application Number
- JP2023076889
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-08
- Publication Date
- 2024-11-20
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing device management systems struggle to flexibly adapt to changes in the operating status of image forming apparatuses, leading to potential updates being overlooked.
A device management system that displays detailed device information for each network device, allowing user interactions and automatically updates the display order based on changes in device status, highlighting devices with abnormalities or updates.
Ensures that updated or abnormal devices are easily identifiable, preventing oversight and facilitating timely user response.
Smart Images

Figure 2024161823000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a device management system and method. [Background technology]
[0002] Conventionally, device management tasks such as management of consumables related to image forming devices and inquiries when a failure occurs are performed by a device administrator in charge of device management tasks using device management web services, applications, etc. Since the operating status of image forming devices changes from moment to moment, there is a possibility that a new image forming device requiring attention may be added while checking and dealing with the status of image forming devices requiring attention, starting with those with high priority. In addition, there is a possibility that a problem related to an image forming device may be resolved by someone other than the device administrator.
[0003] Given this background, for example, Patent Document 1 discloses a method for switching the page transition destination when a document is updated and the number of pages is increased, as display control when content to be displayed is added or updated. This method can handle the cases where content to be displayed is added and where content to be displayed is updated. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2017-10565 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, with the above-mentioned method, the parts to be updated are uniquely determined, making it difficult to flexibly respond to changes in the device's operating status, and there is a risk that the user will overlook an update.
[0006] Therefore, an object of the present invention is to provide a device management system and method that can clearly present image forming devices with updated operating status when checking the operating status of multiple image forming devices that require attention. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems, the device management system of the present invention is a device management system that provides a screen that displays detailed device information for each of a plurality of network devices to be managed, and is characterized in having a control means that accepts user operations and executes an abnormal device details display process that displays details of a network device in which an abnormality is occurring based on the user operations. Effect of the Invention
[0008] According to the present invention, when checking the operational statuses of a plurality of image forming devices that require attention, it is possible to present in an easy-to-understand manner the image forming devices whose operational statuses have been updated. [Brief description of the drawings]
[0009] [Figure 1] 1 is a block diagram showing an example of a configuration of a device management system according to a first embodiment and a second embodiment of the present invention. [Diagram 2] FIG. 4 is a sequence diagram showing an example of processing according to the first and second embodiments of the present invention. [Diagram 3] FIG. 4 is a diagram illustrating an example of an operation information management database for a device according to the first and second embodiments of the present invention. [Figure 4] 11 is a flowchart illustrating an example of device operation information update processing according to the first and second embodiments of the present invention. [Diagram 5] 11 is a flowchart showing an example of a device list display process according to the first and second embodiments of the present invention. [Figure 6]10 is a flowchart illustrating an example of an abnormal device details display process according to the first embodiment of the present invention. [Figure 7] 11 is a flowchart showing an example of a display order list update process according to the first and second embodiments of the present invention. [Figure 8] FIG. 11 is a diagram showing an example of a device list screen according to the first and second embodiments of the present invention. [Figure 9] FIG. 11 is a diagram showing an example of a display order list according to the first and second embodiments of the present invention. [Figure 10] FIG. 13 is a diagram showing an example of a device details screen for continuously displaying abnormal devices according to the first and second embodiments of the present invention. [Figure 11] FIG. 11 is a diagram showing an example of a device details screen according to the first and second embodiments of the present invention. [Figure 12] FIG. 11 is a diagram illustrating an example of a flowchart showing abnormal device details display processing according to the second embodiment of the present invention. [Figure 13] FIG. 11 is a diagram showing an example of a pop-up screen according to the second embodiment of the present invention. [Figure 14] FIG. 11 is a diagram showing an example of a display order list according to the second embodiment of the present invention. [Figure 15] FIG. 11 is a diagram showing an example of a pop-up screen according to the second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, the embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the present invention, and not all of the combinations of features described in the embodiments are essential to the solution of the present invention. Note that the same components are given the same reference numbers and descriptions are omitted.
[0011] The device management system according to the embodiment provides a screen that displays detailed device information for each of a plurality of network devices that are targets of management. The device management system also includes a control unit that receives an operation by a user and executes an abnormal device details display process that displays details of a network device in which an abnormality has occurred based on the operation by the user.
[0012] The control means also obtains a device operation information list indicating the operation status of the network device at least twice at different times and checks whether or not a difference occurs between the two device operation information lists.The control means then checks the update contents of the device operation information list for the network device for which the occurrence of a difference has been confirmed.
[0013] Furthermore, when the control means confirms that a difference has occurred due to a change in the operating status of a network device from a normal state to an abnormal state, the control means executes the following process: In other words, in such a case, the control means adds the network device, in which a difference has occurred due to a change in the operating status from a normal state to an abnormal state, to the end of a display order list indicating the order in which the network device is displayed on the display unit.
[0014] Furthermore, when the control means confirms that the operational statuses of the network devices have been updated, the control means updates the display order list indicating the order in which the network devices in which a difference has occurred are to be displayed on the display unit.
[0015] Furthermore, the device management system according to the embodiment may include an updated device management means and an unconfirmed device notification means. The updated device management means manages network devices so that a network device in which a difference has occurred can be determined. The unconfirmed device notification means notifies the user that a network device in which a difference has occurred while a device details screen showing details of the network device is displayed and that a network device that has not been confirmed by the user exists.
[0016] A specific example of the above-mentioned device management system will be described below with reference to the drawings.
[0017] <Device Management System Overview> Fig. 1 is a block diagram showing an example of the configuration of a device management system according to the first and second embodiments of the present invention. As shown in Fig. 1, the device management system includes printing apparatuses 100-105, a host computer 191, a device management server 160, and a web server 170 (which may be a cloud server). These are connected to a network 190 such as a LAN (Local Area Network) so as to be able to communicate with each other.
[0018] In the first embodiment, a description will be given on the assumption that a multifunction printer (MFP) that integrates multiple functions such as a print function, a read function, and a FAX function is used as the printing devices 100 to 105. A plurality of printing devices, host computers, and servers may be connected, and other devices may also be connected. Furthermore, the network 190 may be a wired network, a wireless network, or a combination of these.
[0019] The printing device 100 includes a control device 110 , a reader device 120 , a printer device 130 , an operation unit 140 , and a storage device 150 .
[0020] The control device 110 is a control board (controller) that performs overall control of the printing device 100. The control device 110 includes a CPU (Central Processing Unit) 111, a ROM (Read Only Memory) 112, a RAM (Random Access Memory) 113, an image processing unit 114, and rendering hardware (HW) 115.
[0021] The CPU 111 controls each block in the control device 110 via a system bus (not shown). For example, the CPU 111 executes the functions of the printing device 100 by reading and executing a program stored in the ROM 112, the RAM 113, the storage device 150, or another storage medium. The ROM 112 stores, for example, a control program, a table required for executing the functions of the printing device 100, setting data, etc. The RAM 113 is used, for example, as a work memory for the CPU 111.
[0022] The image processing unit 114 performs various image processing such as conversion, correction, editing, compression / decompression, etc., on the read image data generated by the reader device 120, image data received from the outside, etc. The image processing unit 114 may be realized by hardware or software. The rendering HW 115 is hardware that performs rendering processing at high speed based on intermediate data and generates an image for print output.
[0023] The storage device 150 stores, for example, device information such as image data, modes, licenses, etc., address book, user information such as customization, etc. The reader device 120 has a scanner engine configuration, and optically reads an automatic document feeder (ADF) set on a document table (not shown) or a document fed from the automatic document feeder, and generates read image data. The printer device 130 has a printer engine configuration compatible with various recording methods such as electrophotography and inkjet recording, and forms an image on a recording medium.
[0024] For example, in the case of an electrophotographic system, there are consumable parts such as a developing unit, a drum, an intermediate transfer belt (ITB), a fixing unit, a paper feed roller of a paper feed stage, etc. Operation unit 140 has operation keys for accepting user operations and a liquid crystal panel for displaying various settings and a user interface screen, and outputs information such as accepted user operations to control device 110.
[0025] 1, the printing device 100 may include other configurations depending on the executable functions of the printing device 100. For example, the printing device 100 may include a configuration required to execute a fax (FAX) function and a configuration enabling short-range wireless communication.
[0026] It should be noted that the printing devices 101 to 105 have the same internal configuration as the printing device 100, and therefore the description thereof will be omitted.
[0027] The host computer 191 includes a control device 198, an operation unit 195, a storage device 196, and a display unit 197. The control device 198 is a control board (controller) that performs overall control of the host computer 191. The control device 198 includes a CPU 192, a ROM 193, and a RAM 194.
[0028] The CPU 192 controls each block in the control device 198 via a system bus (not shown). For example, the CPU 192 executes the functions of the host computer 191 by reading and executing a program stored in the ROM 193, the RAM 194, the storage device 196, or another storage medium.
[0029] The ROM 193 stores, for example, various control programs such as an operating system (OS) program, tables necessary for executing the functions of the host computer 191, setting data, etc. The RAM 194 is used, for example, as a work memory for the CPU 192. The storage device 196 stores, for example, various application programs, data, user information, device information, etc. The operation unit 195 includes a keyboard, a pointing device, etc. for receiving user operations, and outputs information such as the received user operations to the control device 198. The display unit 197 is, for example, a liquid crystal display, and displays various user interface screens, information, etc.
[0030] Description of the device management server 160 and web server 170 will be omitted because their internal configurations are similar to those of the host computer 191. A service runs on the device management server 160 that collects information on the operating status of the printing devices 100 to 105. Various services run on the web server 170, such as a device management service and a printing device billing information management service.
[0031] Here, the device management service is assumed to be a web application that runs on a web browser of the host computer 191 or the like. Data required for the device management service may be provided upon request from a client application dedicated to the device management service that runs on the host computer 191. Furthermore, the device management server 160 and the web server 170 may be a single server.
[0032] A specific embodiment will be described below by taking the device management system having the above-mentioned configuration as an example.
[0033] First Embodiment Fig. 2 is a sequence diagram showing an example of processing according to the first and second embodiments of the present invention. Fig. 2 is a sequence diagram showing an example of processing executed by the host computer 191, device management server 160, Web server 170, and printing devices 100-105 according to the first embodiment. Details of each process will be described below assuming that the device operation information update process (steps P201 and P203), device list display process (step P202), and device details display process (step P204) have been processed in this manner.
[0034] Fig. 4 is a flowchart showing an example of a device operation information update process according to the first and second embodiments of the present invention. The process in Fig. 4 is realized by the CPU 192 of the device management server 160 reading a program stored in the ROM 193 into the RAM 194 and executing it. The process in Fig. 4 is started when operation information is updated in any of the printing devices 100 to 105 by transmitting the operation information to the device management server 160. Here, the transmission of the operation information may be in the form of periodic transmission at a fixed time interval.
[0035] In step S401, CPU 192 receives operation information from any of printing apparatuses 100 to 105, and notifies the receiving result indicating that the information has been received normally.
[0036] In step S402, the CPU 192 updates a device operation information management database (DB) stored in the storage device 196 based on the received operation information, and ends this process.
[0037] FIG. 3 is a diagram showing an example of a device operation information management database according to the first and second embodiments of the present invention. Specifically, FIG. 3 shows information managed in the device operation information management DB, and the information includes a printer name 300, a device ID 301, operation information 302, an installation location 303, a last update date and time 304, and a device owner 305. The device operation information list is a snapshot of information at an arbitrary point in time. FIG. 3(A) shows an example of information at the time when step P201 is completed. FIG. 3(B) shows an example of information at the time when step P203 is completed. In the information shown in FIG. 3(B), the information of the printing devices 101 and 104 has been updated.
[0038] Fig. 5 is a flowchart showing an example of a device list display process according to the first and second embodiments of the present invention. The process in Fig. 5 is realized by CPU 192 of web server 170 reading a program stored in ROM 193 into RAM 194 and executing it. The process in Fig. 5 is started when a user (device administrator) specifies the URL of a device list screen on a web browser running on CPU 192 of host computer 191.
[0039] In step S501, the CPU 192 accepts an input of user authentication information from a user and executes user authentication processing. Here, the following description will be given on the assumption that the user authentication of User A has been successfully processed.
[0040] In step S502, CPU 192 obtains an operation information list of devices managed by the user authenticated in step S501 from device management server 160. The device operation information list at this point is, for example, the information shown in Fig. 3(A), that is, the information at the time when step P201 is completed.
[0041] In step S503, the CPU 192 generates a device list screen based on the acquired device operation information list, and displays it on the display unit 197. Fig. 8 is a diagram showing an example of the device list screen according to the first and second embodiments of the present invention. A device list screen 800 displays a user name 801, a screen generation date and time 802, a device list 803, a device details check button 804, an abnormal device check button 805, and a close button 806.
[0042] User name 801 is the user name included in the user information authenticated in step S501. Screen generation date and time 802 displays the date and time when device list screen 800 was generated, and indicates that the device operation status as of this date and time is displayed. Device list 803 displays device operation status with higher priority at the top, making it easier for the user to check. Here, the order of priority is service errors that require an inquiry to a support service, operator errors that require a response from the device administrator, warnings that indicate that the device is operating but in an abnormal state, and good, which indicates that the device is operating normally.
[0043] In step S504, CPU 192 accepts an operation from the user via operation unit 195. Device details confirmation buttons 804 correspond to each printing device. If any of the device details confirmation buttons 804 is selected, CPU 192 advances the process to step S505. Here, CPU 192 may advance the process to step S505 if the display area of each printing device in device list 803 is selected instead of device details confirmation button 804. If abnormal device confirmation button 805 is selected, CPU 192 advances the process to step S506. Furthermore, if close button 806 is selected, CPU 192 closes the screen display and ends this process.
[0044] In step S505, the CPU 192 acquires detailed information about the printing device selected in step S504 from the device management server 160, and generates a device details screen based on the acquired detailed information and displays it on the display unit 197.
[0045] FIG. 11 is a diagram showing an example of a device details screen according to the first and second embodiments of the present invention. In the explanation using FIG. 11, it is assumed that the printing device 105 is selected. On the device details screen 1100, a user name 1101, a screen generation date and time 1102, device information 1103, a device operation status 1104, device operation status details 1105, a close button 1106, and a return to device list button 1107 are displayed. Here, the CPU 192 accepts an operation from the user via the operation unit 195. By selecting the close button 1106, the screen display is closed and this process is terminated. By selecting the return to device list button 1107, the process returns to step S502 and a device list screen (not shown) is displayed.
[0046] In step S506, CPU 192 executes abnormal device details display processing. Fig. 6 is a flowchart showing an example of abnormal device details display processing according to the first embodiment of the present invention. The processing in Fig. 6 is realized by CPU 192 of web server 170 reading a program stored in ROM 193 into RAM 194 and executing it.
[0047] In step S601, CPU 192 accepts information on the device to be displayed and the device operation information list. In the following explanation, if the process proceeds to step S601 from step S504 without passing through step S505 or step S506, the device operation information list will remain the information acquired in step S502. In the following explanation, it will be assumed that in such a case, printing device 100 determined to have the highest priority in step S503 is specified as the device to be displayed.
[0048] In step S602, the CPU 192 executes a display order list update process. Fig. 7 is a flowchart showing an example of a display order list update process according to the first and second embodiments of the present invention. The process in Fig. 7 is realized by the CPU 192 of the web server 170 reading a program stored in the ROM 193 into the RAM 194 and executing it.
[0049] In step S701, the CPU 192 checks whether or not a display order list has already been created. If the CPU 192 checks that a display order list has not been created, the process proceeds to step S702. On the other hand, if the CPU 192 checks that a display order list has been created, the process ends.
[0050] In step S702, the CPU 192 creates a display order list based on the device operation information list. FIG. 9 is a diagram showing an example of a display order list according to the first and second embodiments of the present invention. The display order list is made up of information such as a display order 900, a device ID 901, device operation information 902, and management information 903. Since the CPU 192 holds the device operation information list shown in FIG. 3A at this point, it creates the display order list shown in FIG. 9A. In the display order 900, numbers are assigned in descending order of priority of the operation status in the device operation information list. In the management information 903, information "under confirmation" is registered for the printing device 100 that is the device to be displayed in step S601, and information "unconfirmed" is registered for the other printing devices.
[0051] In step S703, CPU 192 again acquires an operation information list of devices managed by the user authenticated in step S501 from device management server 160. The device operation information list at this point is shown in Fig. 3(B), which is the device operation information list at the time when step P203 is completed.
[0052] In step S704, CPU 192 compares the device operation information list it holds with the device operation information list acquired again in step S703 to check whether there is a difference. If CPU 192 checks that there is a difference, it proceeds to step S705. On the other hand, if CPU 192 checks that there is no difference, it ends the display order list update process if there is no difference.
[0053] In step S705, CPU 192 checks the update contents of each printing device for which there is a difference, in descending order of priority of the operation status in the device operation information list reacquired in step S703. CPU 192 then advances the process to step S706 for a printing device that has been added to the display order list because its operation status has changed from a good state. On the other hand, CPU 192 advances the process to step S707 for a printing device that is on the display order list and whose operation status has been updated.
[0054] In step S706, the CPU 192 adds information about the printing device to the end of the display order list, and assigns the display order number 900. The CPU 192 then registers in the management information 903 information of “unconfirmed” or “newly added”.
[0055] In step S707, the CPU 192 updates the information in the operational status 902 of the printing device in the display order list, and additionally registers information of “information update” in the management information 903.
[0056] In step S708, the CPU 192 checks whether the display order list update process has been completed for all printing devices that have differences. If the CPU 192 checks that the display order list update process has not been completed for all printing devices that have differences, the process proceeds to step S705. On the other hand, if the CPU 192 checks that the display order list update process has been completed for all printing devices that have differences, the display order list update process ends. Note that the display order list at the time when the display order list update process ends is, for example, the display order list shown in FIG. 9B.
[0057] In step S603, the CPU 192 acquires from the device management server 160 detailed information about the printing device that is the display target device in step S601.
[0058] In step S604, the CPU 192 generates a device details screen based on the display order list updated in step S602 and the detailed information of the printing device acquired in step S603, and displays the device details screen on the display unit 197. When displaying the device details screen, the CPU 192 deletes the "unconfirmed" information from the management information 903 of the printing device in the display order list. Fig. 10 is a diagram showing an example of a device details screen for continuous display of abnormal devices according to the first and second embodiments of the present invention. Figs. 10(A), 10(B), 10(C), and 10(D) all show device details screens of printing devices listed in the display order list updated in step S602.
[0059] Displayed on the device details screen 1000 are a user name 1001, a screen creation date and time 1002, device information 1003, a device operation status 1004, device operation status details 1005, a close button 1006, and a return to device list button 1007. Furthermore, displayed on the device details screen 1000 are a help button 1008, a next button 1009, a previous button 1010, an update display 1011, and a confirmation complete button 1012.
[0060] A help button 1008 is provided to assist with operations such as making inquiries to a call center, ordering consumables, and displaying manuals for treatment, in accordance with the contents of the device operating status 1004. An update display 1011 is displayed on a printing device whose management information 903 in the display order list is "newly added" or "information updated", and highlights the update. In this embodiment, text indicating that an update has been made is displayed, but the background color of the screen may be changed, or a pop-up may be displayed to indicate that an update has been made. A confirmation completion button 1012 is displayed on the device details screen of the printing device at the end of the display order list.
[0061] In step S605, the CPU 192 accepts an operation from the user via the operation unit 195. In response to the selection of the close button 1106, the CPU 192 closes the screen display and ends this process. If the return to device list button 1107 or the confirmation completion button 1012 is selected, the CPU 192 returns the process to step S502 and displays a device list screen (not shown). If the help button 1008 is selected, the CPU 192 displays a screen (not shown) as a separate screen. The screen (not shown) is a screen for assisting the operation. If the next button 1009 or previous button 1010 is selected, the CPU 192 switches the device to be displayed based on the display order list and advances the process to step S601.
[0062] Note that steps S505 and S506 and the process shown in FIG. 6 may be realized by a UI frame part (extension program) acquired from the device management server 160 and installed in the web server.
[0063] As described above, the device management system according to the first embodiment adds additional printing devices that require confirmation to the end by controlling the display based on the display order list that is updated with each screen transition when continuously checking detailed information of abnormal devices. Therefore, when the user is checking the operational status of multiple printing devices that require action, the device management system according to the first embodiment presents the printing devices whose operational status has been updated to the user in an easy-to-understand format, thereby preventing the user from overlooking the printing devices. Furthermore, the device management system according to the first embodiment highlights the printing devices whose operational status has been updated, making it easier for the user to be aware of changes since the device list was displayed.
[0064] Second Embodiment In the description of the second embodiment, the differences from the first embodiment will be mainly described, and descriptions of the same contents as in the first embodiment will be omitted as appropriate.
[0065] Fig. 12 is a diagram showing an example of a flowchart showing abnormal device detail display processing according to the second embodiment of the present invention. Specifically, Fig. 12 shows a flowchart showing abnormal device detail display processing in the web server 170. This abnormal device detail display processing is shown in step P204. The processing shown in Fig. 12 is realized by the CPU 192 of the web server 170 reading a program stored in the ROM 193 into the RAM 194 and executing it. Steps S1201, S1202, S1205, and S1206 shown in Fig. 12 are the same or similar processing as steps S601, S602, S603, and S604 shown in Fig. 6, respectively.
[0066] In step S1205, the CPU 192 acquires detailed information about the display target device in step S1201.
[0067] In step S1206, the CPU 192 generates a device details screen based on the display order list updated in step S1202 and the detailed information acquired in step S1205, and displays the device details screen on the display unit 197. The CPU 192 then displays a pop-up screen on the display unit 197 based on the updated contents of the display order list created in step S1202, and accepts an operation for updating the display control from the user via the operation unit 195. If there is no update to the display order list, the CPU 192 advances the process to step S1203. Fig. 13 is a diagram showing an example of a pop-up screen according to the second embodiment of the present invention.
[0068] 13A is a pop-up screen for a "newly added" device, and displays information and operating status of the newly added device on screen 1300. If Yes button 1301 is selected, which instructs the user to check the details immediately, rather than in the order of the display order list, CPU 192 advances the process to step S1207. On the other hand, if the No button is selected, CPU 192 advances the process to step S1203.
[0069] 13B shows a pop-up screen relating to an "information update" device for which an error has been resolved, and displays information about the device for which the error has been resolved on screen 1303. If OK button 1304 is selected, CPU 192 advances the process to step S1207.
[0070] In step S1207, CPU 192 accepts an operation from the user via operation unit 195. If close button 1106 is selected, CPU 192 closes the screen display and ends this process. If return to device list button 1107 or confirmation complete button 1012 is selected, CPU 192 advances the process to step S1208. If help button 1008 is selected, CPU 192 displays a separate screen, not shown, which is a screen for assisting the operation. If next button 1009 or previous button 1010 is selected, CPU 192 switches the device to be displayed based on the display order list, and advances the process to step S1201.
[0071] Furthermore, in response to a user operation, the CPU 192 updates the display order list acquired in step S1204. In response to the selection of a Yes button 1301, the CPU 192 places the newly added device in the display order of the "checking" devices, and shifts the display order of the devices thereafter. On the other hand, in response to the selection of an OK button 1304, the CPU 192 deletes the device whose error has been resolved from the display order list.
[0072] In step S1208, if there is an unconfirmed device, CPU 192 displays a pop-up screen. Fig. 15 is a diagram showing an example of a pop-up screen according to the second embodiment of the present invention. Specifically, Fig. 15 shows an example of a pop-up screen display, with "unconfirmed" device information displayed on screen 1500. If CPU 192 receives an operation indicating confirmation from the user with OK button 1501 via operation unit 195, CPU 192 advances the process to step S502 and displays a device list screen (not shown). Note that if there is no unconfirmed device, CPU 192 advances the process to step S502 without displaying the pop-up screen, and displays a device list screen (not shown).
[0073] <Other embodiments> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a recording medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit for implementing one or more of the functions, such as an ASIC (Application Specific Integrated Circuit).
[0074] The above describes preferred embodiments of the present invention. However, the present invention is not limited to the above-described embodiments. In other words, the present invention includes embodiments in which various modifications have been made based on the gist of the present invention, and these embodiments are not excluded from the scope of the present invention. [Explanation of symbols]
[0075] 100 Printing device 101~105 Printing device 110 Control device 111 CPU 112 ROM 113 RAM 114 Image processing section 115 Rendering HW 120 Reader Device 130 Printer device 140 Operation section 150 Storage device 160 Device Management Server 170 Web Servers 190 LAN 191 Host Computer 192 CPU 193 ROM 194 RAM 195 Operation section 196 Storage device 197 Operation section 198 Control Device
Claims
1. 1. A device management system that provides a screen for displaying detailed device information for each of a plurality of network devices to be managed, comprising: A control means for receiving an operation by a user and executing an abnormal device details display process for displaying details of a network device in which an abnormality has occurred based on the operation by the user. A device management system comprising:
2. The control means obtains a device operation information list indicating the operation status of a network device at least twice at different times, checks whether or not a difference occurs between the two device operation information lists, and checks the updated contents of the device operation information list for the network device for which the occurrence of the difference is confirmed. The device management system according to claim 1 .
3. When it is confirmed that the difference occurs because the operational status of the network device has changed from a normal state to an abnormal state, the control means adds the network device in which the difference occurs because the operational status has changed from a normal state to an abnormal state to the end of a display order list indicating an order in which the network device is to be displayed on a display unit. The device management system according to claim 2 .
4. When it is confirmed that the operation status of the network device has been updated, the control means updates a display order list indicating an order in which the network device in which the difference has occurred is displayed on a display unit. The device management system according to claim 2 .
5. an update device management means for managing network devices so as to be able to determine the network device in which the difference has occurred; an unconfirmed device notifying means for notifying a user of the existence of a network device in which the difference has occurred while a device details screen showing details of the network device is being displayed and which has not been confirmed by the user; 5. The device management system according to claim 2, further comprising:
6. 1. A method for providing a screen for displaying detailed device information for each of a plurality of network devices to be managed, comprising: The method receives an operation by a user, and executes an abnormal device details display process that displays details of a network device in which an abnormality has occurred based on the operation by the user. A method comprising:
Citation Information
Patent Citations
Incremental page transitions on electronic paper displays
JP2017010565A
