JP6296852B2 - Network device, network device control method, and program - Google Patents

Description

  The present invention relates to log storage control in a network device that communicates with a management server that manages setting values of the network device.

  In recent years, setting values of network devices such as multifunction peripherals may be managed by a server connected via a network, and these setting values may be distributed from the server to the multifunction peripheral. Processing such as distribution of setting values is performed using network communication, and the processing result is stored as log information on both the server side and the multifunction device side. The log information stored at this time needs to be sufficient to be able to correspond to both log information when the log information is confirmed later.

  However, on the MFP side, the capacity of the area for storing log information is often smaller than the storage area on the server side. Therefore, it is necessary to compress and save the log information to the minimum log information that can be handled with the server side. Patent Document 1 discloses such a log information compression technique.

JP 2008-262287 A

  The technology described in Patent Document 1 prevents the loss of important initial error logs by storing the initial log in the overwriting-prohibited area of the communication error log and storing subsequent logs in the overwritable area. That's it. However, since whether to save the log is not controlled according to the contents of the log information, important error logs saved after the initial error can be overwritten by other error logs and lost. There is sex. Further, since a configuration in which a plurality of log information storage areas exist is essential, this technique cannot be applied when the network device cannot realize such a configuration.

  The present invention has been made to solve the above problems. An object of the present invention is to provide a mechanism that allows a network device to store a minimum amount of log information that can be handled with the management server, regardless of the configuration of the log information storage area of the network device that is the target of log storage. Is to provide.

  The present invention is a network device that manages, as master data, a plurality of setting values to be set in a plurality of network devices, and communicates with a management server that manages configuration information of each network device. Control means for controlling recording of the log to the storage device of the network device, request means for requesting a setting value to be set to the management server, and master data for the management server Requesting means for requesting a change of a setting value to be reflected on the request, and when the control means does not have a setting value to be set based on the request, the request is not recorded and the request is not recorded. If the category of the setting value to be set based on the user is a user-related setting, a log regarding the request is recorded, and if the request is made, the log Characterized in that it records a log on Lai.

  According to the present invention, it is possible to save the minimum log information that can be handled with the management server, regardless of the configuration of the log information storage area of the network device that is the log save target.

1 is a system configuration diagram of an entire set value synchronization system of the present invention. The block diagram which illustrates the hardware constitutions of a management server. 2 is a block diagram illustrating a hardware configuration of a multifunction machine. FIG. The figure which illustrates the structure of the master data managed by the management server. The figure which illustrates the structure of each database contained in master data. The figure which illustrates the structure of each database contained in master data. 2 is a diagram illustrating a configuration of a setting value DB stored in a multifunction machine. FIG. FIG. 6 is a diagram illustrating a display example of a communication log left by a management server and a multifunction peripheral. 3 is a diagram illustrating a software configuration of the multifunction machine according to the first embodiment. FIG. 3 is a flowchart illustrating log information storage processing of the multifunction machine according to the first embodiment. The flowchart which shows a GET log holding | maintenance determination process in detail. The flowchart which shows the holding | maintenance determination process at the time of Warning in detail. The flowchart which shows the holding | maintenance determination process at the time of Error in detail. The figure which illustrates the setting screen of an acquisition log output flag. The figure which shows the example of a display of log information in the case of outputting log information temporarily. The figure for demonstrating the recording conditions of log information. FIG. 4 is a diagram illustrating a software configuration of a multifunction machine according to a second embodiment. 9 is a flowchart illustrating log information storage processing of the multifunction machine according to the second embodiment. The figure which illustrates the setting screen of the log output flag for development.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

FIG. 1 is a system configuration diagram illustrating an entire network device setting value synchronization system according to an embodiment of the present invention.
As shown in FIG. 1, a management server 110 and a plurality of multifunction devices 120 are connected to the network 100. The network 100 may be any type of network such as an intranet or the Internet.

  The management server 110 manages master data of setting values of a plurality of MFPs including the MFPs 120a and 120b. When the master data is changed, the management server 110 notifies the MFP 120a, the MFP 120b, etc. of the change information via the network 100. When the management server 110 receives setting value change information from the multifunction peripheral 120a, the multifunction peripheral 120b, etc., the management server 110 changes the value of the master data managed by itself.

  The multifunction device 120 such as the multifunction device 120a and the multifunction device 120b is a network device that realizes a plurality of types of functions, such as copying, scanning, and FAX, and stores therein setting values used when executing these functions. Yes. When these setting values are changed, the multifunction peripheral 120 notifies the management server 110 of the change information via the network 100. In addition, when the MFP 120 receives the change information of the master data of the setting value from the management server 110, the MFP 120 changes the value of the setting value stored by itself.

  Depending on the setting value, there is a device that synchronizes values between a plurality of multifunction devices such as the multifunction device 120a and the multifunction device 120b. Regarding these setting values, when there is a change in the master data on the management server 110, the management server 110 notifies both the multifunction device 120a and the multifunction device 120b of change information of the setting value. In addition, when there is a change in the setting value of either the MFP 120a or the MFP 120b, the change information is first notified from the changed MFP 120 to the management server 110, and thereafter, via the management server 110. The change information is also notified to other multifunction devices 120.

  In FIG. 1, two multifunction devices, the multifunction device 120a and the multifunction device 120b, are illustrated as multifunction devices for which the management server 110 manages setting values, but three or more multifunction devices may be used. In the present embodiment, an example in which the management server 110 manages setting values of the multifunction device will be described. However, devices for which the management server 110 manages setting values are not limited to multifunction devices, but other than multifunction devices. Network devices. Detailed descriptions of the management server 110 and the multifunction machine 120 will be described later.

FIG. 2 is a block diagram illustrating a hardware configuration of the management server 110.
The management server 110 includes a controller unit 200, an operation unit 220, and a display unit 230. The controller unit 200 includes a CPU (Central Processing Unit) 203, and the CPU 203 activates an OS (Operating System) by a boot program stored in a ROM (Read Only Memory) 206. The CPU 203 executes application programs stored in an HDD (Hard Disk Drive) 205 on the OS, thereby executing various processes. A RAM (Random Access Memory) 204 is used as a work area of the CPU 203. The HDD 205 stores the application program, master data of setting values of the multifunction machine 120, and the like. Details regarding the master data management method will be described later. Instead of the HDD 205, another storage device such as an SSD (Solid State Drive) may be provided.

  An operation unit I / F 201, a display unit I / F 202, and a network I / F 207 are connected to the CPU 203 through the system bus 210 together with the ROM 206 and the RAM 204. The operation unit I / F 201 is an interface with the operation unit 220 including a mouse, a keyboard, and the like, and sends information input by the user through the operation unit 220 to the CPU 203. The display unit I / F 202 is an interface with the display unit 230 including a display and outputs image data to be displayed on the display unit 230 to the display unit 230. A network I / F 207 is a network interface, is connected to the network 100, and inputs / outputs information to / from each device on the network 100 via the network 100.

FIG. 3 is a block diagram illustrating a hardware configuration of the multifunction machine 120.
The multi function device 120 includes a controller unit 300, an operation unit 320, a scanner 330, and a printer 340. The controller unit 300 is connected to an operation unit 320 and is also connected to a scanner 330 that is an image input device and a printer 340 that is an image output device.

  The controller unit 300 includes a CPU 302, and the CPU 302 starts up the OS by a boot program stored in the ROM 306. The CPU 302 executes application programs stored in the HDD 305 on this OS, thereby executing various processes. A RAM 303 is used as a work area of the CPU 302. The RAM 303 provides a work area and an image memory area for temporarily storing image data. The HDD 305 stores the application program, image data, and various setting values. A setting value management method in the multifunction machine 120 will be described later. Instead of the HDD 305, another storage device such as an SSD (Solid State Drive) may be provided.

  An operation unit I / F 301, a device I / F 304, a network I / F 307, and an image processing unit 308 are connected to the CPU 302 via a system bus 310, along with a ROM 306 and a RAM 303. The operation unit I / F 301 is an interface with the operation unit 320 having a touch panel, and outputs image data to be displayed on the operation unit 320 to the operation unit 320. In addition, the operation unit I / F 301 sends information input by the user through the operation unit 320 to the CPU 302. A scanner 330 and a printer 340 are connected to the device I / F 304, and the device I / F 304 performs synchronous / asynchronous conversion of image data. A network I / F 307 is a network interface, is connected to the network 100, and inputs / outputs information to / from each device on the network 100 via the network 100. The image processing unit 308 performs processing such as input image processing from the scanner 330, output image processing to the printer 340, image rotation, image compression, resolution conversion, color space conversion, and gradation conversion.

FIG. 4 is a diagram illustrating a configuration of master data managed by the management server 110.
The master data 401 is configured from a database (DB) such as a setting value management DB 410, a common setting value DB 411, a device management DB 412, an individual setting value DB 413, a configuration information DB 414, a user information DB 415, and a user setting value DB 416. Is done.

  5A and 5B are diagrams illustrating the configuration of each database included in the master data 401. FIG. Hereinafter, it demonstrates individually.

FIG. 5A (a) is a diagram illustrating data stored in the setting value management DB 410.
The setting value management DB 410 is a database that stores metadata regarding each setting value managed by the management server 110. The setting value management DB 410 includes a key identifier for identifying a setting value when communicating with the MFP 120, a UI display wording that is a wording to be presented to the user, an initial value, a value range, an applicable model / firmware version, Stores display conditions for setting values.

  Each setting value managed by the setting value management DB 410 depends on the model of the multifunction device 120 and the firmware version, and whether or not the setting value exists. The value range and initial value of the setting value may differ. In the example shown in FIG. 5A (a), the setting value represented by the key identifier “settings.pattern” is present in all individuals in model A and model B, but the firmware version is 3 in model C. This means that it exists only in individuals after .01. In addition, the setting value represented by the key identifier “settings.density” indicates that the initial value and value range of the setting value differ depending on the version of the installed firmware in the model B. For example, in version 2.01 or later, the initial value of the setting value is “5” and the value range is “0-10”, and in version 1.9 or earlier, the initial value of the setting value is “3” and the value range is “0-6”. It represents that.

FIG. 5A (b) is a diagram illustrating data stored in the common setting value DB 411.
The common setting value DB 411 is a database that manages device setting values (setting values of device-related settings) that share and synchronize values among all of the multiple MFPs 120 that manage setting values by the management server 110. The common setting value DB 411 stores a key identifier, a value corresponding to the identifier, and the last update date and time of the setting value. This key identifier is an identifier having the same system as the key identifier of the setting value management DB 410.

FIG. 5A (c) is a diagram illustrating data stored in the individual setting value DB 413.
The individual setting value DB 413 is a database that manages device setting values (setting values of device-related settings) having different values in each of the plurality of multifunction peripherals 120 that manage setting values by the management server 110. It is assumed that a plurality of individual setting value DBs 413 exist corresponding to the individual MFPs. The individual setting value DB 413 stores a key identifier, a value corresponding to the identifier, and the last update date and time of the setting value. This key identifier is an identifier having the same system as the key identifier of the setting value management DB 410.

FIG. 5B (d) is a diagram illustrating the contents of device configuration information (device configuration information) for each MFP managed by the configuration information DB 414.
The configuration information DB 414 is a database for storing and managing a plurality of device configuration information, and a plurality of configuration information DBs 414 exist corresponding to the individual MFPs. This device configuration information includes an individual identifier for identifying the individual MFP 120, a model name, a firmware version, license information indicating available functions, accessories, and the like. The license information represents information on a license already installed in the multifunction machine 120. The accessory represents information on an optional device attached to the multifunction device 120. The model name, firmware version, license, and the like have the same system as that stored in the setting value management DB 410.

FIG. 5B (e) is a diagram illustrating data stored in the user information DB 415.
The user information DB 415 is a database for managing information (user information) related to users who use the multifunction machine 120. The user information DB 415 stores a user ID for uniquely identifying the user, a user name input by the user at the time of login, and the like.

FIG. 5B (f) is a diagram illustrating data stored in the user set value DB 416.
The user setting value DB 416 is a database for managing setting values (user setting values (setting values for user related settings)) for each user that can be used by each user who uses the multifunction device 120. The user setting value DB 416 stores a user ID for uniquely identifying the user, a key identifier for uniquely identifying the setting value, the content of the setting value, and the last update date and time of the setting value. The user ID has the same system as that in the user information DB 415.

  The device management DB 412 is a database for managing individual identifiers of the individual MFPs 120 whose setting values are managed by the management server 110, although details are not shown. The management server 110 uses each database of the master data 401 as described above, setting values that are different in each of the multifunction devices 120 to be managed, setting values common to all the multifunction devices 120 to be managed, It is possible to collectively manage metadata of setting values themselves.

FIG. 6 is a diagram illustrating an example of the configuration of the setting value DB 601 stored in the HDD 305 of the multifunction machine 120.
The setting value DB 601 is a database that stores setting values used in the multifunction machine 120. The setting value stored in the setting value DB 601 is composed of elements such as a key identifier for identifying the setting value, a value of the setting value, a UI display word, an initial value, a value range, and a display condition. These elements are managed in the same system as that managed by the master data 401. When the setting value is changed in the management server 110 or the MFP 120, the setting value is synchronized by communicating at least the data of “key identifier” and the data of “value” among the data shown in FIG. To do.

  The setting value synchronization processing described above is performed by the management server 110 and the multifunction peripheral 120 communicating via the network 100. At this time, the contents of the communication performed are left as communication logs in each device.

FIG. 7 is a diagram illustrating a display example of communication logs left by the management server 110 and the multifunction peripheral 120.
As shown in FIG. 7, a display example of a communication log includes a log level (level) indicating a communication result, a communication date (date), a processing content, a connection destination URL, and a communication method (Method) indicating an access method to the URL. Consists of.

  The log level includes “Normal” indicating that the log indicates communication success, “Warning” indicating that the log indicates a communication failure due to a temporary factor (that is, a retryable failure), and a permanent factor There are three types of “Error” indicating that the log indicates a communication failure due to (that is, a failure that cannot be retried), and different levels are output depending on the communication result. The communication date and time indicates the date and time when the corresponding network communication process is executed. The processing content includes information indicating a data type (set value category) to be subjected to communication processing and a data size to be subjected to communication processing. The information indicating the data type corresponds to information indicating whether the data to be subjected to communication processing is “device configuration information”, “device setting value”, or “user setting value”. The data size to be subjected to communication processing corresponds to information indicating the size of data transmitted or received by communication processing. The URL indicates location information of data accessed by communication. The communication method indicates a method for accessing the target data indicated by the URL. The types of access methods include “GET”, “PUT”, “POST”, “DELETE”, “HEAD”, and the like. “GET” represents a data acquisition request. “PUT” represents a data update request (request to change setting values to be reflected in master data). “POST” represents a request for new data creation. “DELETE” represents a data deletion request. “HEAD” represents data existence confirmation. The communication log may include, for example, information such as the number of retries in the case of “Warning” as retry information of the communication process.

  The display contents of the communication log and the configuration of the communication log contents are not limited to those shown in FIG. The means for displaying the communication log is also a display unit of the operation unit 320 of the multifunction device 120, even if it is a Web browser of an information processing apparatus (such as a personal computer) that can communicate with the multifunction device 120 or the management server 110. There is no particular limitation.

FIG. 8 is a diagram illustrating a software configuration of the multifunction peripheral 120 in the setting value synchronization system according to the first embodiment.
A setting value management unit 801 manages setting values of the MFP 120 that are to be synchronized with the master data 401. Data types (setting value categories) to be managed in the setting value management unit 801 are “device configuration information”, “device setting value”, and “user setting value”. In addition, when the setting value is changed, the setting value management unit 801 displays information regarding the changed setting value as log information (latest log information) different from the communication log stored in the log information holding unit 806 described later. ) As a storage function. The latest log information held by this function includes the latest log level for each data type. Note that the MFP 120 may be configured not to have a function of holding the latest log information.

  The synchronization processing unit 802 performs network communication with the management server 110 and performs setting value synchronization processing. In addition, the synchronization processing unit 802 causes the log information holding unit 806, which will be described later, to hold the execution result of network communication as log information during the synchronization processing. The log output control unit 803 acquires log information held in the log information holding unit 806 by the synchronization processing unit 802 and an acquisition log output flag to be described later, and based on these contents, the log information is stored in the log information holding unit. In step 806, control is performed to determine whether to output as a communication log. The contents of this control will be described later with reference to FIGS.

  When it is determined that the log output control unit 803 outputs, the log output execution unit 804 acquires the log information held in the log information holding unit 806 and displays it on the log display unit 805 described later. The log display unit 805 receives the log information to be displayed from the log output execution unit 804, and displays the log information in the format described with reference to FIG.

  The log information holding unit 806 holds a communication log of network communication processing executed by the synchronization processing unit 802 based on an instruction from the synchronization processing unit 802. The acquisition log output flag holding unit 807 holds flag information for the log output control unit 803 to determine whether to output a communication log. The flag information is set on a setting screen shown in FIG. 13 to be described later, and is held in the acquisition log output flag holding unit 807.

  Note that the functions of the setting value management unit 801, the synchronization processing unit 802, the log output control unit 803, the log output execution unit 804, and the log display unit 805 illustrated in FIG. 8 are stored in the HDD 305 by the CPU 302 of the MFP 120. It is realized by executing the program. In addition, the log information holding unit 806 and the acquired log output flag holding unit 807 are realized as storage areas in a storage device such as the ROM 306 and the HDD 305 of the multifunction machine 120.

  FIG. 9 is a flowchart illustrating the execution procedure of the log information storage process associated with the setting value synchronization of the multifunction machine 120 according to the first embodiment. The processing of the flowcharts shown in FIG. 9 and FIGS. 10 to 12 described later is realized by the CPU 302 of the multifunction peripheral 120 executing a program stored in the ROM 306 or the HDD 305.

  First, in step S <b> 901, the synchronization processing unit 802 performs setting value synchronization processing with the management server 110. The trigger for starting the setting value synchronization process is predetermined when any setting value managed by the MFP 120 is updated, newly created, or deleted, or when the setting value is acquired from the management server 110. This is the case when the timing is reached. In the former case, the setting value management unit 801 notifies the synchronization processing unit 802 of information regarding the setting value for which update, new creation, or deletion operation has been performed, and the synchronization processing unit 802 receives the management server based on this notification. Data to be transmitted to the network 110 through the network 100 is created. In the latter case, the synchronization processing unit 802 transmits a setting value acquisition request to the management server 110 through the network 100, and generates setting value information to be synchronized with the MFP 120 based on response data from the management server 110. Then, the setting value management unit 801 is notified. After executing the synchronization processing in this way, the synchronization processing unit 802 stores the log information related to the network communication used for the synchronization processing in the log information holding unit 806, notifies the log output control unit 803 to that effect, S902 The process proceeds. Here, the log information stored in the log information holding unit 806 includes the contents described with reference to FIG. 7, that is, the log level, the communication date and time, the processing contents, the connection destination URL, and the communication method.

  In the processing after S902, the log output control unit 803 determines whether to output the communication log information stored in the log information holding unit 806 by the synchronization processing unit 802, and performs control processing. Details will be described below.

  In step S <b> 902, the log output control unit 803 first acquires the log information saved by the synchronization processing unit 802 from the log information holding unit 806. Next, the log output control unit 803 refers to the processing content and communication method of the log information, and sets the data type (device configuration information, device setting value, user setting value) that is the target of the synchronization processing corresponding to the log information. ) And a communication method (GET, PUT, POST, DELETE, HEAD). Next, the log output control unit 803 determines whether or not the current synchronization process regarding the acquired data type and communication method is the first execution after the MFP 120 is activated. For example, the log information holding unit 806 holds the log information of the synchronization process that has the same data type and communication method as the current synchronization process and is executed after the MFP 120 is started and before the current synchronization process. If not, it is determined that the current synchronization process is the first execution after activation. On the other hand, when such log information is held in the log information holding unit 806, it is determined that the current synchronization processing is not the first execution after activation.

  If it is determined that the current synchronization process is the first execution after activation (Yes in S902), the log output control unit 803 advances the process to S910. In step S910, the log output control unit 803 determines that the log information acquired in step S902 is to be output, and keeps the log information held in the log information holding unit 806 ("leave in log"). Further, the log output control unit 803 instructs the log output execution unit 804 to output log information. Upon receiving this instruction, the log output execution unit 804 acquires log information from the log information holding unit 806, displays the log information on the log display unit 805, and proceeds to S911. The multifunction device 120 reads information (for example, URL) for each data type regarding the connection destination of the synchronization processing held therein at the time of activation. For this reason, there is a possibility that these pieces of information have been changed before and after the start, and in order to take correspondence with the data communication with the management server 110, it is necessary to output the first log after the start to the data type. By controlling to leave and output the log in the procedure described in S902 and S910, the first log after startup can always be left in the log information holding unit 806 and output.

  Hereinafter, the description returns to the flow description. In step S911, the log output control unit 803 uses the latest log information (including the latest log level for each data type) held by the setting value management unit 801 as the log level and processing of the communication log for which the log output determination has been completed. Updating is performed based on the contents, and the process of this flowchart is terminated. In addition, the structure which abbreviate | omits the process of S911 may be sufficient.

  If it is determined in S902 that the current synchronization process is not the first execution after activation (No in S902), the log output control unit 803 advances the process to S903. In step S903, the log output control unit 803 refers to the “log level” from the log information acquired in step S902. If it is determined that the referenced log level is “Normal”, the log output control unit 803 advances the process to S904.

  In step S904, the log output control unit 803 refers to the “communication method” from the log information acquired in step S902, and determines whether the communication method is “HEAD”. If it is determined that the communication method is “HEAD” (Yes in S904), the log output control unit 803 advances the process to S909.

  In step S909, the log output control unit 803 determines that the log information acquired in step S902 is not output, and deletes the log information from the log information holding unit 806 ("does not leave in log"). And the process of this flowchart is complete | finished after the process of S911 mentioned above. In addition, as described in S904 and S909 above, when the HEAD method does not change the setting values of either the multifunction device 120 or the master data 401 by controlling whether or not the log information is left in the log. Therefore, no log is left and output is not performed, and log information can be reduced within a necessary range.

  If it is determined in S904 that the communication method is not “HEAD” (No in S904), the log output control unit 803 advances the process to S905. In step S905, the log output control unit 803 determines whether the communication method acquired in step S904 is “GET”. When it is determined that the communication method is not “GET” (that is, “PUT”, “POST”, or “DELETE”) (No in S905), the log output control unit 803 advances the process to S910. In S910, as described above, the log output control unit 803 determines to output the log information by leaving the log information acquired in S902 in the log information holding unit 806, and outputs the log information to the log output execution unit 804. Instruct. And the process of this flowchart is complete | finished after the process of S911 mentioned above. Log information of PUT, POST, and DELETE, which are communication methods that change the setting values of the MFP 120 and the master data 401 by executing the processing in the above steps S904, S905, and S910, always holds log information. It can be left in the part 806 and output.

  If it is determined in S905 that the communication method is “GET” (Yes in S905), the log output control unit 803 advances the process to S906. In step S906, the log output control unit 803 executes a log retention determination process (GET log retention determination process) when the communication method is GET. Details of the GET log retention determination process will be described later with reference to FIG. And the process of this flowchart is complete | finished after the process of S911 mentioned above.

  If it is determined in S903 that the log level is “Worning”, the log output control unit 803 advances the process to S907. In step S907, the log output control unit 803 executes a log log retention determination process (warning retention determination process) when the log level is “warning”. Details of the holding determination process at the time of Warning will be described later with reference to FIG. And the process of this flowchart is complete | finished after the process of S911 mentioned above.

  If the log level is determined to be “Error” in S903, the log output control unit 803 advances the process to S908. In step S908, the log output control unit 803 executes log retention determination processing (error retention determination processing) when the log level is “Error”. Details of the error hold determination process will be described later with reference to FIG. And the process of this flowchart is complete | finished after the process of S911 mentioned above.

FIG. 10 is a flowchart showing in detail the GET log retention determination process shown in S906 of FIG.
First, in S1001, the log output control unit 803 determines the data type to be synchronized acquired in S902 of FIG. Since the MFP 120 does not GET device configuration information from the management server 110, the determination in S1001 does not include “device configuration information”, and determines whether it is “device setting value” or “user setting value”. Do. If it is determined that the synchronization target data type is “device setting value”, the log output control unit 803 advances the process to S1002.

  In step S <b> 1002, the log output control unit 803 acquires an acquisition log output flag from the acquisition log output flag holding unit 807. The acquisition log output flag is a flag for determining whether or not to output log information when a device setting value is acquired from the management server 110 by GET. Hereinafter, a method for setting the acquisition log output flag will be described with reference to FIG.

FIG. 13 is a diagram illustrating an acquisition log output flag setting screen.
In the setting screen as shown in FIG. 13 displayed on the operation unit 320, when the user presses the “valid” button 1301 to make it “valid” and presses the OK button 1303 in this “valid” state, A communication log can be output when a device setting value is acquired. That is, the CPU 203 stores “ON” in the acquisition log output flag holding unit 807 as the value of the acquisition log output flag. On the other hand, when the “invalid” button 1302 is pressed to enter the “invalid” state, and the OK button 1303 is pressed in this “invalid” state, the communication log can be prevented from being output when the device setting value is GET. That is, the CPU 203 stores “OFF” as the value of the acquisition log output flag in the acquisition log output flag holding unit 807.

  Hereinafter, the description returns to the flowchart. When the log output control unit 803 determines that the acquired log output flag is “invalid” in S1002 (in the case of “OFF” in S1002), the log output control unit 803 advances the process to S1004. In S1004, the log output control unit 803 performs the same processing as S909 in FIG. 9 and returns the processing to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG. According to the procedures of S1002 and S1004, the information regarding the changed device setting value as described above is not left in the log information holding unit 806 and can be prevented from being output. As a result, the log information can be reduced within a necessary range, information regarding the changed device setting value can be left only in the setting value management unit 801, and the communication log stored in the log information holding unit 806 Can be reduced.

  On the other hand, when it is determined in S1002 that the acquired log output flag is “valid” (in the case of “ON” in S1002), the log output control unit 803 advances the process to S1003. Also, when it is determined in S1001 that the data type to be synchronized is “user set value”, the log output control unit 803 advances the process to S1003.

  In S1003, the log output control unit 803 refers to the processing content from the log information acquired in S902 in FIG. 9, and the difference data (setting value information to be synchronized) of the setting values to be subjected to the synchronization processing is received from the management server 110. It is determined whether it is included in the received data. For example, this determination determines that the data to be synchronized is included if the received data size included in the processing content of the log information is greater than or equal to a predetermined threshold, and is not included otherwise. Judgment is performed.

  When it is determined in S1003 that the difference data is not included (No in S1003), the log output control unit 803 advances the process to S1004. Then, after the processing of S1004 and S911 of FIG. 9, the processing of the flowchart of FIG.

  On the other hand, when it is determined in S1003 that difference data is included (Yes in S1003), the log output control unit 803 advances the process to S1005. In step S1005, the log output control unit 803 performs the same process as in step S910 in FIG. 9, performs control so as to leave a log, and returns the process to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG. As described above, the log information is stored depending on whether or not the set value information to be synchronized is included in the data acquired by the GET, and whether or not the log information is output is controlled, so that the set value of the MFP 120 can be changed. Only when it occurs, it is possible to leave the communication log in the log information holding unit 806 and output it.

FIG. 11 is a flowchart showing in detail the holding determination process during Warning shown in S907 of FIG.
First, in S1101, the log output control unit 803 switches “Warning”, which is the log level of the log information acquired in S902 of FIG. 9, from the previous log level in the same data type and the same communication method. It is determined whether or not. In this determination, the previous log information having the same data type and communication method as the current log information acquired in S902 of FIG. 9 is acquired from the log information holding unit 806, and the previous log information is “Warning”. Depending on whether or not there is. For example, a case where the current synchronization process is a PUT process of device configuration information will be described as an example. In this case, if the PUT process of the previous device configuration information is “Warning” level, it is determined that the mode has not been switched to “Warning”. On the other hand, if the PUT process of the previous device configuration information is not “Warning” level, it is determined that the mode has been switched to Warning.

  If it is determined in S1101 that the “Warning” that is the log level of the current log information has been switched from the previous log level (Yes in S1101), the log output control unit 803 proceeds to S1105. Proceed with the process. In step S1105, the log output control unit 803 performs the same processing as in step S910 in FIG. 9, performs control so as to leave a log, and returns the processing to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG.

  On the other hand, if it is determined in S1101 that “Warning”, which is the log level of the current log information, has not been switched from the previous log level (No in S1101), the log output control unit 803 performs processing in S1102 To proceed. In step S1102, the log output control unit 803 determines whether the synchronization target data type acquired in step S902 of FIG. 9 is “device configuration information”. If it is determined that the device information is not “device configuration information” (No in S1102), the log output control unit 803 advances the process to S1104. In S1104, the log output control unit 803 performs the same processing as S909 in FIG. 9, performs control so that no log is left, and returns the processing to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG.

  On the other hand, when it is determined in S1102 that the synchronization target data type acquired in S902 of FIG. 9 is “device configuration information” (Yes in S1102), the log output control unit 803 advances the process to S1103. . In step S <b> 1103, the log output control unit 803 determines that log information is to be temporarily left, and temporarily holds the log information in the log information holding unit 806 until a predetermined condition is satisfied (“ Leave it temporarily "). Note that the case where the predetermined condition is satisfied indicates, for example, a case where the data type and the communication method are the same and a Warning level process occurs. When such a process occurs, the log output control unit 803 determines that the log information of the process is temporarily left, and the log information having the same data type and communication method determined to be temporarily left before. Is deleted from the log information holding unit 806. That is, the log information to be temporarily left is controlled so that only the latest log information is left for each data type and communication method. Further, the log output control unit 803 instructs the log output execution unit 804 to temporarily output log information. Upon receiving this instruction, the log output execution unit 804 acquires the log information from the log information holding unit 806, and instructs the log display unit 805 to display the log information in the form described with reference to FIG. Then, the log output control unit 803 returns the process to FIG. 9, and ends the process of the flowchart of FIG. 9 after the process of S911 of FIG.

FIG. 14 is a diagram showing a display example of log information by the log display unit 805 when log information is temporarily output in S1103 of FIG.
First, as shown in FIG. 14A, a Warning level device configuration information PUT process 1401, a Normal level device setting value PUT process, a Normal level user setting value PUT process, a Warning level device configuration information PUT process 1402 Assume that they are output in order. A log 1402 is temporarily displayed in S1103 of FIG. Thereafter, an example of a log display when the synchronization processing is performed by the synchronization processing unit 802 in the order of the normal level device setting value PUT process, the normal level user setting value PUT process, and the Warning level device configuration information PUT process 1403 is shown. This is shown in FIG. In FIG. 14B, since the device configuration information PUT process 1403 of the same Warning level as that of the temporary display 1402 has occurred, the display of the temporary display 1402 is deleted. 14B, the normal level device setting value PUT process, the normal level user setting value PUT process, and the Warning level device configuration information PUT process 1403 are displayed in this order. The log information of the device configuration information is temporarily displayed in the form as described above.

  The effect of performing the above-described holding determination process during Warning will be described. First, the processing is performed in the order of S1101 and S1105, and the log information switched to the Warning level is left in the log information holding unit 806, so that a log is output so that it can be understood when the synchronization processing with the management server has failed. Can do. In addition, processing is performed in the order of S1101, S1102, and S1104, and log information that is continuous Warning level log information and whose synchronization target data type is not “device configuration information” is not left in the log information holding unit 806, so that Log information held and output in the information holding unit 806 can be reduced. Further, the processing is performed in the order of S1101, S1102, and S1103, and log information that is Warning level log information whose synchronization target data type is device configuration information is temporarily left in the log information holding unit 806 and output. Control. The effect of this will be described below.

  In this case, the device configuration information includes information related to functions that can be used by the multifunction device 120 as described above with reference to FIG. 5B (d). For example, when an available function is added by newly registering a license of a function in the multifunction machine 120, the synchronization processing unit 802 executes an update process of the configuration information DB 414 in the management server 110. In this update process, the management server 110 updates the individual setting value DB 413 and the user setting value DB 416 according to the updated contents of the device configuration information. Therefore, when the synchronization processing unit 802 fails in the update process of the device configuration information, the setting value held in the individual setting value DB 413 and the user setting value DB 416 included in the master data 401 and the setting value of the multifunction device 120 are set. Inconsistency will occur. If the synchronization processing unit 802 acquires a setting value from the master data 401 and performs synchronization processing while such inconsistency occurs, the device may not operate correctly. Therefore, the synchronization processing unit 802 performs control so that the GET processing for the device setting value and the user setting value is not executed when the update processing of the device configuration information has failed. Therefore, by temporarily storing the log information in the form as shown in FIG. 14 and displaying it, the GET process of the device setting value and the user setting value is performed between 1401 and 1402 in FIG. 14A. It becomes clear that it is not. In addition, in FIG. 14B, the same can be seen between 1401 and 1403. The above is the effect obtained by performing the holding determination process at the time of Warning.

FIG. 12 is a flowchart showing in detail the error hold determination process in S908 of FIG.
First, in S1201, the log output control unit 803 switches “Error”, which is the log level of the log information acquired in S902 of FIG. 9, from the previous log level in the same data type and the same communication method. It is determined whether or not. In this determination, the previous log information having the same data type and communication method as the current log information acquired in S902 of FIG. 9 is acquired from the log information holding unit 806, and the previous log information is “Error”. Depending on whether or not there is. For example, a case where the current synchronization process is a PUT process of device configuration information will be described as an example. In this case, if the PUT process of the previous device configuration information is at the “Error” level, it is determined that the mode has not been switched to “Warning”. On the other hand, if the previous PUT process of the device configuration information is not “Error” level, it is determined that the error has been switched to Error.

  If it is determined in S1201 that “Error”, which is the log level of the current log information, has been switched from the previous log level (Yes in S1201), the log output control unit 803 proceeds to S1203. Proceed with the process. In step S1203, the log output control unit 803 performs the same processing as in step S910 in FIG. 9, performs control so as to leave a log, and returns the processing to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG.

  On the other hand, if it is determined in S1201 that “Error”, which is the log level of the current log information, has not been switched from the previous log level (No in S1201), the log output control unit 803 performs processing in S1202 To proceed. In step S1202, the log output control unit 803 performs the same processing as in step S909 in FIG. 9, performs control so as not to leave a log, and returns the processing to FIG. Then, after the process of S911 of FIG. 9, the process of the flowchart of FIG.

  The effect of performing the error hold determination process described above will be described. First, the processing is performed in the order of S1201 and S1203, and the log information that has been switched to the error level is retained and output, so that it is possible to know when a fatal failure has occurred in the synchronization processing with the management server. It can remain in the holding unit 806 and be output. Next, the processing is performed in the order of S1201 and S1202, and continuous error level log information is not left in the log information holding unit 806 (only the first error level log information is left) and is not output, so that the log information holding unit 806 is not output. Log information that is stored and output can be reduced.

The log information recording conditions in the control shown in FIGS. 9 to 12 are shown in FIG.
FIG. 15 is a diagram for explaining log information recording conditions.
In FIG. 15, “◯” indicates a case of “leaving log information”, and “×” indicates a case of “no log information is left”. “-” Indicates a case where there is no corresponding case. “Ox switchable” indicates a case where “leave log information” and “no log information” can be switched by the acquired log output flag. Further, “only when switching” indicates a case where “keep log information” only when switching to that level. For example, when the same level continues, it indicates that only the log information of the first process among the processes where the same level continues is left. Also, “when switching” and “the latest is also temporarily” indicate a case where “log information is left” when the log level is switched, and the latest log information is also “temporarily left”.

  As described above, only the minimum communication log information that can be handled with the management server 110 can be obtained by switching whether to save or output the communication log information by the control as shown in FIGS. It remains in the holding unit 806 and can be output to the log display unit 805. Thereby, not only the area for storing the communication log information (log information holding unit 806) can be minimized, but also the visibility for the user browsing the communication log information can be improved.

  In the above description, the synchronization processing unit 802 stores the log information in the log information holding unit 806, the log output control unit 803 performs the log information holding determination, and determines that no log is left. The configuration for deleting log information from the log information holding unit 806 has been described. However, the synchronization processing unit 802 stores the log information in the work area of the RAM 303, and the log output control unit 803 determines to retain the log information, and it is determined that the log is left (including temporarily left). The log information of the process may be stored (recorded) in the log information holding unit 806. In other words, the log output control unit 803 controls the recording of the processing log related to the setting value in the log information holding unit 806.

  In the first embodiment, only the minimum communication log information that can be handled by the management server 110 and the multifunction machine 120 is saved in the multifunction machine 120 to save the storage area. The structure which can also improve the visibility for the user who browses information was shown. In the second embodiment, not only the visibility for the user is improved, but also a configuration in which the developer of the multifunction device 120 can track the details of the execution result of the synchronization processing will be described. Of the system configuration, hardware configuration, software configuration, and processing procedure of the second embodiment, the description of the same components as those described in the first embodiment will be omitted, and only different ones will be described.

  FIG. 16 is a diagram illustrating a software configuration of the multifunction peripheral 120 in the setting value synchronization system according to the second embodiment. The software configuration of the second embodiment is obtained by adding a developer log output flag holding unit 1501 and a developer log holding unit 1502 to the software configuration of the first embodiment shown in FIG.

  The developer log output flag holding unit 1501 holds a developer log output flag for determining whether or not to save the communication log information of the synchronization processing performed by the synchronization processing unit 802 for the developer of the multifunction device 120. Note that the developer log output flag setting screen may be displayed on the operation unit 320 as shown in FIG. 18 to be described later, or may be another method. The developer log holding unit 1502 is a storage destination for storing a developer log according to a processing procedure described later. Hereinafter, a method for setting the developer log output flag will be described with reference to FIG.

FIG. 18 is a diagram exemplifying a developer log output flag setting screen.
When the user presses the “valid” button 1701 to make it “valid” on the setting screen shown in FIG. 18 displayed on the operation unit 320 and presses the OK button 1703 in this “valid” state, the developer The communication log can be output to the log holding unit 1502. That is, the CPU 203 stores “ON” as the value of the developer log output flag in the developer log output flag holding unit 1501. On the other hand, when the “invalid” button 1702 is pressed to be in an “invalid” state and the OK button 1703 is pressed in this “invalid” state, a communication log is not output to the developer log holding unit 1502. it can. That is, the CPU 203 stores “OFF” in the developer log output flag holding unit 1501 as the value of the developer log output flag.

  FIG. 17 is a flowchart illustrating the execution procedure of the log information storage process associated with the setting value synchronization of the MFP 120 according to the second embodiment. Note that the processing of the flowchart shown in FIG. 17 is realized by the CPU 302 of the multifunction peripheral 120 executing a program stored in the ROM 306 or the HDD 305.

  The processing procedure of the flowchart shown in FIG. 17 is obtained by adding S1601 and S1602 to the processing procedure of the first embodiment shown in FIG. 9, and the same steps as those in FIG. is there. After the synchronization processing unit 802 executes the synchronization processing in S901, in S1601, the log output control unit 803 acquires the developer log output flag from the developer log output flag holding unit 1501. Further, the log output control unit 803 determines whether or not the acquired developer log output flag is valid (that is, the development log is stored).

  If it is determined that the developer log output flag is valid (that is, the development log is stored) (Yes in S1601), the log output control unit 803 advances the process to S1602. In S1602, the log output control unit 803 instructs the log output execution unit 804 to leave the communication log information according to S901 as a developer log. Receiving this, the log output execution unit 804 causes the developer log holding unit 1502 to hold the communication log information according to S901, and proceeds to S902.

  On the other hand, when it is determined that the developer log output flag is invalid (that is, the development log is not saved) (No in S1601), the log output control unit 803 proceeds to S902 as it is. Since S902 and subsequent steps are the same as those in the first embodiment, description thereof is omitted.

  As described above, when the developer log output flag is valid, separately from the communication log compressed for the user viewing the log and stored in the log information holding unit 806, the developer log The log holding unit 1502 can hold all communication logs. As a result, the developer of the multifunction peripheral 120 can track the details of the synchronization processing. The method for the developer log holding process in S1602 is not limited. For example, the log information may be filed and stored in the HDD 305, or may be transmitted to a server that manages the log information. However, in this method, it is desirable that information held in the HDD 305 and the RAM 303, which are log information storage areas in the multifunction peripheral 120, be minimized.

  As described above, according to each embodiment, regardless of the configuration of the communication log information storage area (log information holding unit 806) of the network device such as the multifunction device 120 that is a log storage target, The minimum communication log information that can be handled can be stored on the network device side. Thereby, the problem of restriction of the communication log information storage area on the network device side can be solved.

  Therefore, the management server 110 on the network (for example, intranet, the Internet) manages the master data of the setting values for each model of the network device, and the group (organization) by periodic polling from the network device (multifunction device or printer). In a system that automatically synchronizes setting values of network devices of the same model of a customer, etc.), a log relating to synchronization processing from the management server 110 to the network device, and a request for changing setting values from the network device to the management server 110 When the log related to the server, etc. is left, the minimum communication log information that can be handled with the server side is suppressed by suppressing the log left on the network device side where the storage area for the log is limited rather than the management server 110 On the network device side It can be.

It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.
Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.
Moreover, all the structures which combined said each Example are also contained in this invention.

(Other examples)
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.
Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not. That is, the present invention includes all the combinations of the above-described embodiments and modifications thereof.

Claims (11)

A network device that manages a plurality of setting values to be set in a plurality of network devices as master data and communicates with a management server that manages configuration information of each network device,
Control means for controlling recording of the processing log related to the setting value in the storage device of the network device;
Request means for requesting a setting value to be set to the management server;
Requesting means for requesting the management server to change a setting value to be reflected in the master data;
The control means does not record a log relating to the request when there is no setting value to be set based on the request, and relates to the request when the category of the setting value to be set based on the request is a user related setting. A network device that records a log, and records a log related to the request when the request is made.   When the category of the setting value to be set based on the request is a device-related setting, the control unit controls the recording of the log related to the request according to the setting of whether to record the log related to the request. The network device according to claim 1.   The network device according to claim 1, wherein the control unit records a log of the process when the result of the process related to the setting value is switched to a result indicating failure.   The control means records only the log of the first process among the processes in which the same result is consecutive when the same result representing failure is consecutive as a result of the process related to the set value. The network device according to claim 1 or 2.   5. The network according to claim 3, wherein the result of the process related to the setting value includes a result representing success, a result representing a failure that can be retried, or a result representing a failure that cannot be retried. device.   The said control means records the log of the said process, when the process regarding the said setting value is the first process after starting of the said network device, The one of Claims 1 thru | or 5 characterized by the above-mentioned. The listed network device.   7. The configuration information of the network device according to claim 1, wherein the configuration information of the network device includes at least one of information on an optional device attached to the network device and license information. Network device.   The network device according to claim 1, wherein the network device includes a multifunction peripheral.   The contents of the log include the result of the process corresponding to the log, the date and time when the process was executed, the category of the setting value to be processed, the data size to be processed, the type of the process, the process The network device according to claim 1, wherein the retry information is included. A method of controlling a network device that manages a plurality of setting values to be set in a plurality of network devices as master data and communicates with a management server that manages configuration information of each network device,
A requesting step for requesting a setting value to be set to the management server;
A requesting step of requesting the management server to change a setting value to be reflected in the master data;
A control step for controlling the recording of the processing log related to the setting value to the storage device of the network device,
In the control step, when there is no setting value to be set based on the request, a log relating to the request is not recorded, and when the category of the setting value to be set based on the request is a user-related setting, the request is related to the request. A method for controlling a network device, comprising: recording a log and recording a log related to the request when the request is made.   The program for functioning a computer as a means of any one of Claims 1 thru | or 9.

Images