Network device, information processing method, and program

Abstract

To provide a technique that can appropriately manage information generated in a previous contract term.SOLUTION: A network device is a network device that can be connected to a server via a network. The network device collects log information of an event generated in the network device, accumulates the collected log information, and transmits the accumulated log information to the server via the network. The network device compares an occurrence time of the event with a contract start time of a current contract for owning the network device, and performs filtering so as not to transmit, to the server, log information of the event occurring before the contract start time, of the accumulated log information.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present disclosure relates to a technique for information processing in network devices.

Background Art

[0002] There is a demand for a service that collects log information such as events occurring in network devices such as image forming apparatuses in a storage server constructed in a cloud server and performs analysis such as prompt maintenance and failure prediction. To achieve this, it is necessary to transmit a large amount of log information to the storage server from operating network devices via the Internet at high frequency. However, in the case of an immediate transmission form in which log information is transmitted to the storage server immediately when it is generated by a network device, the number of connections increases, which causes an increase in the operation cost of the cloud. Therefore, it is common to save the log information in the network device at the time of log information generation and to take a transmission form in which a group of log information saved at an arbitrary timing is transmitted all at once.

[0003] In addition, the log information that needs to be collected may include personal information of customers using the network device. In that case, collection settings are made based on a contract regarding information collection concluded with each customer and device, and it is necessary to logically divide the storage area of the collected log information for each device with which the contract has been made even in the storage server. Therefore, the network device needs to reliably send the log information for which the collection settings have been made, and at the same time, strict management is also required to prevent the sending of log information for which the collection settings have not been made and which is outside the contract.

[0004] Patent Document 1 discloses a method in which a client device that acquires a license can also access device information (device usage history, failure history, etc.) collected during the period when the previous license contract was valid before the timing of acquiring a new license. As a result, the client device that acquires the license can collect the device information during the previous license contract period or during the invalidation period of the license without lacking the device information.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, the method disclosed in Patent Document 1 does not assume a case where the ownership of a device is changed, such as the delivery of a device from a sales organization to a customer or the transfer of a device between customers. When the same device is re-contracted with different owners, in particular, it is required to appropriately manage the information generated during the previous contract period and stored in the device.

[0007] This disclosure provides a technique capable of appropriately managing information generated during a previous contract period.

Means for Solving the Problems

[0008] A network device according to an aspect of the present disclosure is a network device that can be connected to a server via a network, and includes a collection unit that collects log information of events occurring in the network device, a storage unit that stores the collected log information, a transmission unit that transmits the stored log information to the server via the network, and a filter unit that compares the occurrence time of the event with the start time of the current contract for owning the network device and filters so as not to transmit the log information of the event that occurred before the start time of the contract to the server.

Advantages of the Invention

[0009] According to the present disclosure, information generated during a previous contract period can be appropriately managed.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Not all of the plurality of features in the embodiments of the present disclosure are essential, and the plurality of features may be arbitrarily combined. Also, the configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the illustrated configurations. In the drawings, the same reference numerals are assigned to the same or similar configurations to omit redundant descriptions.

[0012] (Configuration of the System) FIG. 1 is a diagram showing the configuration of a system according to the first embodiment. The system of this embodiment is composed of a network 100, a client terminal 101, a storage server 102, a device management server 103, a network device 104, and the like.

[0013] The network device 104 is connected to the storage server 102 and the device management server 103 via a network 100 such as the Internet. The network device 104 is a device to be managed by the management server 103. The network device 104 is, for example, an image forming device or an image processing device such as a printing device, a scanner, or a copying machine including these. Hereinafter, for convenience of explanation, the network device may be abbreviated as "device", and the device management server may also be abbreviated as "management server".

[0014] The network 100 is composed of at least one of a WAN (Wide Area Network) and a LAN (Local Area Network). For example, the Internet is used as the WAN. For example, an intranet is used as the LAN.

[0015] In FIG. 1, only one device 104 is shown, but there may be a plurality of devices 104 in the network of one customer organization. Also, a plurality of customer organization devices 104 may be connected to one storage server 102 and one management server 103. Here, the "customer organization" is an enterprise or the like that actually uses the device 104.

[0016] The client terminal 101 is a communication terminal operated by an operator of a sales organization. A web browser is installed on the client terminal 101. Here, the "sales organization" is an organization that sells and installs the device 104 to a customer organization or operates the management service by the management server 103.

[0017] A server connection application 501 (to be described later in FIG. 5) is installed on the network device 104. Then, when the network device 104 performs device registration or acquires access permission information for communicating with the storage server 102, it is connected to the management server 103 by this server connection application 501. Also, when the device 104 performs acquisition of collection settings or transmission of log information, it is connected to the storage server 102 by this server connection application 501.

[0018] The storage server 102 and the management server 103 may be physically integrated devices or separate devices. Alternatively, they may be a system that realizes cloud computing.

[0019] FIG. 2 is a diagram showing a hardware configuration common to servers in this system, such as the storage server 102 and the management server 103. These servers are referred to as server 200 in FIG. 2. The server 200 includes a controller unit 201, an operation unit 202, and a display unit 203. The controller unit 201 includes a CPU 210, a ROM 211, a RAM 212, an HDD 213, an operation unit I / F 214, a display unit I / F 215, and a network I / F 216. Each element in the controller unit 201 is connected via a system bus 217 and performs data communication with each other.

[0020] The CPU 210 (Central Processing Unit) controls the entire server 200. The CPU 210 starts the OS (Operating System) by means of a boot program stored in the ROM 211. Also, on this OS, the CPU 210 executes an application program stored in the HDD 213, thereby performing various processes.

[0021] The ROM (Read Only Memory) 211 is a non-volatile storage area that stores various data such as the basic control program of the server 200, the OS (Operating System), and applications. The basic control program includes a boot program.

[0022] The RAM (Random Access Memory) 212 is a volatile storage area and is used as a temporary storage area and a work area when the CPU 210 performs various processes. The CPU 210 expands various control programs stored in the ROM 211 and the HDD 213 in the RAM 212.

[0023] The HDD (Hard Disk Drive) 213 is a non-volatile large-capacity storage unit. The HDD 213 stores data such as application programs, setting values, and log information collected from the device 104 on the network 100. In this embodiment, the HDD 213 is described as an example of the storage unit, but it is not limited to this, and an SSD (Solid State Drive) may also be used, or a device that can read / write data by loading an external medium such as a memory card may also be used.

[0024] The operation unit 202 is, for example, a pointing device (such as a mouse, a touch panel, etc.), an operation button, a keyboard, etc., and receives operations, inputs, and instructions from the user. The operation unit I / F 214 is an interface with the operation unit 202 and sends information input by the user through the operation unit 202 to the CPU 210.

[0025] The display unit 203 is, for example, a liquid crystal display, a touch panel, or the like, and displays images and various types of data. The display unit I / F 215 outputs data to be displayed on the display unit 203 to the display unit 203. The operation unit 202 and the display unit 203 may be integrally configured as a touch panel or the like.

[0026] The network I / F 216 is connected to the network 100 and performs input / output of information between the device 104, the client terminal 101, and other servers on the network 100 via the network 100.

[0027] Note that the configuration of the server 200 described with reference to FIG. 2 is an example when the server 200 is realized by an information processing apparatus such as a general computer, and is not limited thereto. For example, the server 200 may not include the operation unit 202, the display unit 203, the operation unit I / F 214, and / or the display unit I / F 215.

[0028] FIG. 3 is a diagram showing an outline of the main hardware configuration of the network device 104. For example, the device 104 will be described as a multifunction device. The device 104 includes an information processing controller unit 302, a printer controller unit 303, a scanner controller unit 305, a printer 304, a scanner 306, and an operation unit 301.

[0029] The information processing controller unit 302 is a controller that comprehensively controls information processing related to the operation of the device 104. A detailed description of the information processing controller unit 302 will be given later with reference to FIG. 4. The operation unit 301, the printer controller unit 303, and the scanner controller unit 305 are connected to the information processing controller unit 302.

[0030] The operation unit 301 includes a display device and an input device, displays various information to the user, and receives operations, inputs, and instructions from the user. The display device is, for example, a liquid crystal display or a touch panel. The input device is, for example, a pointing device (such as a touch pad, a touch panel, etc.), operation buttons, a keyboard, etc. In this embodiment, a case where the device 104 includes a touch panel as the operation unit 301 will be described as an example. By associating the input coordinates and the display coordinates on the touch panel, a GUI can be configured as if the user can directly operate the screen displayed on the touch panel.

[0031] The printer 304 is an image output device that forms an image according to print data received from the outside and outputs it to paper, or optically reads the original image set on the scanner 306 and outputs it to paper. The printer controller unit 303 controls the printer 304.

[0032] The scanner 306 is an image input device that optically reads a document and generates an electronic file (scan data) based on the scan. The scanner controller unit 305 controls the scanner 306.

[0033] FIG. 4 is a diagram showing the configuration of the information processing controller unit 302 of the device 104. The information processing controller unit 302 includes a CPU 401, a ROM 402, a RAM 403, an HDD 404, a network I / F 405, an operation unit I / F 406, an image processing unit 407, a device controller I / F 408, and a power management unit 409. Each element in the information processing controller unit 302 is connected via a system bus 410 and performs data communication with each other.

[0034] The CPU 401 controls the entire device 104. The CPU 401 starts the OS by the boot program stored in the ROM 402 and executes the application program stored in the HDD 404 on the OS, thereby executing various processes described later.

[0035] The ROM 402 is a non-volatile memory area that stores various data such as the basic control program of the device 104, the OS (Operating System), and applications. The basic control program includes a boot program.

[0036] The RAM 403 is a volatile memory area and is used as a temporary storage area and a work area when the CPU 401 performs various processes. Also, the RAM 403 provides an image memory area for temporarily storing image data. The CPU 401 expands various control programs stored in the ROM 402 and the HDD 404 into the RAM 403. The CPU 401 realizes the functions of each block shown in FIG. 5 and executes the processes described later by executing the programs stored in the readable storage medium.

[0037] The HDD 404 is a non-volatile large-capacity storage unit. Application programs, image data, various setting values, histories, etc. are stored in the HDD 404. In this embodiment, the HDD 404 is described as an example of the storage unit, but it is not limited thereto, and an SSD or a device capable of reading / writing data by loading an external medium such as a memory card may also be used.

[0038] The network I / F 405 is connected to the network 100 and performs input / output of information with each device on the network 100, such as the storage server 102 and the management server 103, via the network 100.

[0039] The operation unit I / F 406 is an interface with the operation unit 301. The operation unit I / F 406 sends the information input by the user through the operation unit 301 to the CPU 401, and outputs the data to be displayed on the operation unit 301 to the operation unit 301.

[0040] The image processing unit 407 performs various image processes on the images output to the printer 304 and the images acquired by the scanner 306. Examples of the various image processes include processes such as image rotation, image compression, resolution conversion, color space conversion, and gradation conversion.

[0041] The device controller I / F 408 is connected to the printer controller unit 303 and the scanner controller unit 305. The device controller I / F 408 controls the input / output of data between the printer controller unit 303 and the scanner controller unit 305 and the CPU 401. Also, the device controller I / F 408 performs synchronous / asynchronous conversion of image data.

[0042] The power management unit 409 controls the power supply of the device 104. As a specific example, the power management unit 409 controls not only on / off control but also transition to a power-saving state other than the normal power-on state and return to the normal state.

[0043] In addition, in FIGS. 2 and 4, not only the CPUs 210 and 401 but also a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array) may be used. Alternatively, an ASIC (Application Specific Integrated Circuit) may be used, or a DSP (Digital Signal Processor) may be used.

[0044] FIG. 5 is a diagram showing the software configuration of the network device 104. The functions of each block shown in the figure are realized by the CPU 401 expanding and executing the programs stored in the ROM 402 and the HDD 404 in the RAM 403. In the device 104, in addition to the software that realizes the functions of a general information processing device using a network and a memory storage, the software that realizes the functions of a multifunction device such as scanning and printing operates.

[0045] Device 104 includes a user interface 5061, a functional application 5062, a job control unit 5063, a power control unit 5064, an error control unit 5065, and a history / setting retention unit 5066. Further, device 104 includes a log information collection unit 505, a first buffer 541, a second buffer 542, a third buffer 543, a server connection application 501, and a collection setting retention unit 507.

[0046] The server connection application 501 includes a log information transmission unit 511, an identification information retention unit 512, a management server connection management unit 513, a collection setting acquisition unit 518, and a storage server communication unit 519.

[0047] The management server connection management unit 513 performs a process of registering device 104 with the management server 103 using a registration code. The registration code is input, for example, by the user via the user interface 5061. By being registered with the management server 103, the management server connection management unit 513 acquires device identification information and stores the device identification information in the identification information retention unit 512. The device identification information is unique identification information for identifying the device. Device 104 can establish a connection with the management server 103 or the storage server 102 using this device identification information. The identification information may be abbreviated as "identification information" hereinafter.

[0048] The identification information retention unit 512 stores the identification information. The identification information retention unit 512 stores the identification information in the form of a file, for example, in the HDD 404.

[0049] The storage server communication unit 519 performs communication processing of the log information transmission unit 511 and the collection setting acquisition unit 518 to the storage server. Before communicating with the storage server 102, the storage server communication unit 519 uses the identification information stored in the identification information retention unit 512 to acquire access permission information to the storage server 102 from the management server 103.

[0050] When the storage server communication unit 519 receives a notification of owner change upon obtaining access permission information from the management server 103, it conveys the notification to the management server connection management unit 513. The owner is the owner of the device 104. When the management server connection management unit 513 receives a notification of owner change from the storage server communication unit 519, it communicates with the management server 103 to cancel the current device registration and register the device 104, which is the own device, as the device of the new owner. After that, the management server connection management unit 513 obtains the identification information as the device of the new owner. If the obtained identification information is different from the identification information stored in the identification information holding unit 512, it is overwritten and stored in the identification information holding unit 512.

[0051] The user interface 5061 displays a screen for the user to operate on the operation unit 301 and conveys the user's operation via the operation unit 301 to the software.

[0052] The function application 5062 operates the application functions of the multifunction device. The application functions of the multifunction device include a plurality of functions such as copying, printing, and email transmission, and the function application 5062 is provided for each application function. That is, the device 104 has a plurality of function applications 5062. The function application 5062 operates the application functions of the multifunction device triggered by an instruction from the user via the operation unit 301 or data reception via the network I / F 405.

[0053] The job control unit 5063 receives an instruction from the function application 5062 and controls the printer controller unit 303 and the scanner controller unit 305 to execute printing and scanning.

[0054] The power control unit 5064 controls the power management unit 409 in conjunction with the state of the software in the device 104. As a specific example, the power control unit 5064 controls the transition between the normal power-on state and the power-saving state according to the state of the software.

[0055] The error control unit 5065 detects abnormal states that occur in each unit within the device 104, such as the job control unit 5063, the printer controller unit 303, and the scanner controller unit 305. Also, according to the abnormal state, the error control unit 5065 controls the operating status of the device 104 by instructing, for example, the termination or degradation of the application or the entire system.

[0056] The history / setting retention unit 5066 manages non-volatile information within the device 104. Specific examples include that the history / setting retention unit 5066 retains settings necessary for controlling the multifunction device or jobs, and summarizes and stores the user's operation history, job execution results, and / or occurrence of errors. Also, the history / setting retention unit 5066 retains log information to be left for analysis and debugging when system failures occur. The entity of the non-volatile data managed by the history / setting retention unit 5066 is stored in the HDD 404.

[0057] The log information collection unit 505 collects data such as the operating status of the device 104 for transmission to the storage server 102 and stores it in the form of log information. Specifically, the log information collection unit 505 monitors events within the device 104, collects target data according to the collection conditions specified by the server connection application 501, and normalizes the collected data in the form of log information for transmission to the storage server 102. The log information collection unit 505 selectively stores the normalized log information in either the first buffer 541 or the second buffer 542.

[0058] The collection of data within the device 104 by the log information collection unit 505 will be described. The log information collection unit 505 collects data within the device 104 according to the log information collection settings stored in the collection setting retention unit 507 described later. For example, the log information collection unit 505 monitors state transitions that occur in modules that spontaneously issue events (e.g., the user interface 5061 to the history / setting retention unit 5066) and collects state transition data in real time.

[0059] The log information collection unit 505 normalizes the collected data in the device 104 into the format of log information and stores it in the first buffer 541, the second buffer 542, or both. The normalization is performed using a general-purpose format such as JSON (JavaScript Object Notation) in order to make the collected data in a format suitable for transmission to the storage server 102.

[0060] In addition to basic information such as the ID of the log information, the event name, the occurrence time of the event, and the serial number of the device, various additional information is added depending on the type of the event to the log information. The additional information is collected by the log information collection unit 505 from the states of each module in the device 104 and the contents held in the non-volatile area. Also, the conditions for determining whether to store the data collected by the log information collection unit 505 in the first buffer 541, the second buffer 542, or both are as follows. That is, it depends on the collection setting information stored in the collection setting holding unit 507 and the internal judgment of the log information collection unit 505.

[0061] When the log information collection unit 505 stores the log information specified as a trigger for the batch transmission timing as a collection setting of the log information in the second buffer 542, it generates trigger information and stores this in the third buffer 543. Based on the trigger information stored in the third buffer 543, the batch transmission of the log information from the second buffer 542 is executed. The batch transmission means that when a plurality of log information is accumulated, they are transmitted together (substantially at the same time).

[0062] Also, the log information collection unit 505 has a timer function internally, and stores trigger information even in the case of periodic transmission according to the collection settings stored in the collection setting holding unit 507. The trigger information includes the event name of the transmission target, the occurrence time of the transmission trigger (i.e., the transmission time), information on the accumulation area of the log information by the second buffer 542 (for example, path information in the HDD 404), etc. The trigger information is stored in a general-purpose format such as JSON.

[0063] The log information collection unit 505 is an example of a collection means for collecting log information on events occurring within the network device 104.

[0064] The first buffer 541 and the second buffer 542 hold the log information normalized by the log information collection unit 505. The first buffer 541 and the second buffer 542 are on the HDD 404. The data stored in the first buffer 541 (mainly messages including the collected log information) can be immediately transmitted to the storage server 102 by the log information transmission unit 511. The data stored in the second buffer 542 (mainly messages including the collected log information) can be batch-transmitted to the storage server at a predetermined timing according to the above trigger information by the log information transmission unit 511. The second buffer 542 is an example of an accumulation means.

[0065] As described above, the third buffer 543 holds the trigger information generated by the log information collection unit 505. The third buffer 543 is on the HDD 404.

[0066] The log information transmission unit 511 monitors the updates of the first buffer 541 and the third buffer 543. When the log information transmission unit 511 detects the update, it reads the log information from the first buffer 541 or the second buffer 542 and transmits the log information to the storage server 102 via the storage server communication unit 519. The log information transmission unit 511 is an example of a transmission means for transmitting the accumulated log information to the server via the network 100.

[0067] Immediately before transmitting the log information to the storage server 102, the storage server communication unit 519 makes a request to the storage server 102 to obtain upload area information (information regarding the upload area) and obtains the information necessary for transmitting the log information. The upload area information includes path information such as a URL necessary for determining the transmission destination of the log information and a part thereof.

[0068] When the log information transmission unit 511 detects the storage of new log information in the first buffer 541, it reads out the newly stored log information in the first buffer 541 and transmits it to the storage server 102 via the storage server communication unit 519.

[0069] Also, when the log information transmission unit 511 detects the storage of new trigger information in the third buffer 543, it reads out the new trigger information from the third buffer 543. Then, the log information transmission unit 511 reads out the newly stored log information group after the previous batch transmission in the second buffer 542 specified by the path included in the read trigger information, and transmits it to the storage server 102 via the storage server communication unit 519. At this time, the transmission of log information whose event occurrence time included in the log information for which transmission has been attempted is earlier than the storage time of the identification information in the identification information holding unit 512 is excluded. This is because they are log information generated during a contract period different from the current owner of the network device. In this case, the log information transmission unit 511 can function as an example of filtering means for filtering so as not to transmit the log information of events occurring before the contract start time to the server.

[0070] The collection setting acquisition unit 518 receives the log information collection setting from the storage server 102 via the storage server communication unit 519, and stores the received collection setting in the collection setting holding unit 507. Here, the log information collection setting indicates definition information on which data among the data in the device 104 is to be sent to the storage server 102 at what timing. The log information collection setting is acquired as a collection file.

[0071] The collection setting holding unit 507 holds information indicating the log information collection setting. The log information collection setting is stored in the form of a file. The collection setting holding unit 507 is on the HDD 404. The log information collection unit 505 stores the log information in the first buffer 541 or the second buffer 542 and stores the trigger information in the third buffer 543 according to the log information collection setting stored in the collection setting holding unit 507.

[0072] FIG. 6 is a block diagram showing the software configurations of the storage server 102 and the management server 103. The functions of each block are realized by the CPU 401 of each server expanding and executing the programs stored in the ROM 402 and the HDD 404 in the RAM 403.

[0073] The device registration management unit 611 manages the identification information of any device owned by a specific owner, and performs registration and deregistration processing of any device 104 owned by the specific owner for the specific owner. Further, the device registration management unit 611 issues identification information at the time of registration of the device 104, and registers collection settings in accordance with the content of the information collection contract concluded between the owner and the sales organization in the collection setting management unit 621.

[0074] The information collection contract is a contract concluded between the owner of the device 104 and the sales organization that mainly sells the device 104. In addition to selling the device, the sales organization may also operate the cloud service associated with the device. Specifically, the information collection contract is a contract for the sales organization to upload personal information including how to use the device to the storage server 102 on the cloud managed by the sales organization. How to use the device includes information such as "when, on what type of paper, how much ink, what size, and how many sheets were printed" generated and recorded in the device. Further, the information collection contract is strictly managed, such as storing the personal information uploaded by the sales organization in a logically exclusive area so that no one other than the current owner of the device can view it.

[0075] In this embodiment, the contract starts with the consent of both the sales organization and the device owner. For example, using the device registration key issued by the sales organization, device registration is performed from the device installed at the owner to the management server 103 managed by the sales organization, and the timing when the device identification information is replied is the start of the contract. The contract start time when the identification information is replied to the management server connection management unit 513 and the time when the identification information is saved from the management server connection management unit 513 to the identification information holding unit 512 are considered to have a sufficiently short time difference. Therefore, the save time of the identification information is treated as the contract start time.

[0076] The device connection management unit 612 performs a process of returning access permission information in response to a request for obtaining access permission information for the storage server 102 from the storage server communication unit 519. Also, before returning the access permission information, the device connection management unit 612 inquires the device registration management unit 611 about the status of the identification information included in the acquisition request. And when there is an instruction to change the owner associated with the device 104, the device connection management unit 612 returns a notice of owner change instead of the access permission information.

[0077] The collection setting management unit 621 manages the collection settings for each registered identification information from the device registration management unit 611. Also, the collection setting management unit 621 returns the collection settings associated with the identification information included in the acquisition request in response to a request for obtaining collection settings from the storage server communication unit 519.

[0078] The upload area management unit 622 manages the upload areas for the log information for each identification information in the storage server 102 and performs a response process for a request for obtaining upload area information from the storage server communication unit 519. When performing the response process for the request for obtaining upload area information, the upload area management unit 622 confirms the identification information included in the acquisition request and newly secures an upload area 623 assigned to the identification information.

[0079] The upload area 623 holds the log information transmitted from the device 104. The upload area 623 is on the HDD 213 within the storage server 102, and the log information is stored in the form of files or as data on a database.

[0080] The upload area 623 is logically secured as an exclusive area for each device owner (each contract). For example, for the same device 104, in order to separate the upload areas 623 for the previous owner and the new owner respectively, logical areas of the upload area (A) 623a and the upload area (B) 623b are secured. The upload area 623 may be secured as a logically exclusive area for each piece of identification information and for each owner.

[0081] Note that in the hardware configuration of the storage server 102, if there are multiple writable non-volatile storage devices corresponding to the HDD 213 etc., the log information for each piece of identification information may be physically secured in an exclusive area on separate storage devices.

[0082] (Processing in the system) Next, with reference to FIGS. 7 to 14, the software processing in the system will be described. Here, when the registration of the owner of the device 104 is changed from the sales organization to the customer organization, it is explained that the log information of the device as the sales organization stored in the second buffer 542 in the device 104 is not transmitted to the upload area for the customer organization. This processing is realized by the CPUs 210 and 401 reading out programs corresponding to the processing content from the ROMs 211 and 402 (or the HDDs 213 and 404) respectively, loading them into the RAMs 212 and 403, and executing them.

[0083] Figures 7 and 8 are sequence diagrams showing the processes until device registration is performed for a device owned by a sales organization for operation confirmation and the like, and collection of log information in the device 104 is started. The parts where the lifetime in the figure is activated indicate that data is registered and stored. The arrows indicating instructions, responses, and data transfer are connected by A to F between Figures 7 and 8.

[0084] Processes for registering the device 104 with the server are performed in S701 to S703. First, in S701, an operator of the sales organization inputs a device registration key of the sales organization to the management server connection management unit 513 via the user interface 5560 of the device 104 or the like. The management server connection management unit 513 receives the input of the registration key from the device 104 and performs device registration as a device of the sales organization to the device registration management unit 611. The device registration management unit 611 records the device identification information in the identification information management table shown in Table A below. The management server connection management unit 513 acquires the identification information as a device of the sales organization as a response to this device registration request.

[0085] Table A shows an example of the identification information management table managed by the device registration management unit 611. (Table A) TIFF2025109492000002.tif34165

[0086] The "device registration key" is key information that is unique within the management server 103 and in which one device registration key has a correspondence with one owner. The "device identification information" is ID information for uniquely identifying a device within the management server 103 and the storage server 102.

[0087] In S702, the device registration management unit 611 registers collection settings as a device of the sales organization with the collection setting management unit 621. The collection setting management unit 621 records the collection settings in the collection setting management table shown in Table B below.

[0088] Table B shows an example of the collection setting management table managed by the collection setting management unit 621. (Table B) TIFF2025109492000003.tif30165

[0089] The "device identification information" is information equivalent to the "device identification information" in Table A. The "log information to be collected" is information indicating the types of log information to be collected by the log information collection unit 505 in the device 104 corresponding to this device identification information. The "batch transmission timing trigger" is information indicating the timing at which the log information collection unit 505 generates trigger information in the third buffer 543. For example, there are triggers generated at the time of regular transmission of log information and triggers generated when specific log information is generated.

[0090] In S703, the management server connection management unit 513 saves the identification information of the device of the sales organization obtained in S701 to the identification information holding unit 512.

[0091] In S704, the collection setting acquisition unit 518 acquires the collection settings of the device of the sales organization registered in the collection setting management unit 621 in S702, triggered by the end of S703.

[0092] In S705, the collection setting acquisition unit 518 saves the collection settings of the device of the sales organization obtained in S704 to the collection setting holding unit 507.

[0093] In S706, the log information collection unit 505 detects that the collection settings of the device of the sales organization have been saved to the collection setting holding unit 507 in S705, and starts acquiring log information according to the collection settings.

[0094] In S707, when the log information collection unit 505 detects the occurrence of an event such as a state transition of the user interface 5560, etc., it normalizes the log information. As described above, the module for generating an event is not limited to the user interface 5560 only, and there are also the function application 5062 to the history / setting holding unit 5066. Then, the log information collection unit 505 stores the normalized log information in the second buffer 542 as the log information (1) of the device of the sales organization.

[0095] FIGS. 9 and 10 are sequence diagrams showing the processing until the owner of the device 104 is changed from the sales organization to the customer organization and the collection of log information in the device 104 owned by the customer organization is started. The places where the lifetime in the figure is activated represent that data is registered and stored. As a prerequisite for FIGS. 9 and 10, the progress of the sequences in FIGS. 7 and 8 is required.

[0096] In S801 to S805, processing for registering (changing the registration) the device 104 to the server is performed. First, in S801, an operator of the sales organization registers an instruction to change the owner of the device 104 to the customer organization via the browser of the client terminal 101 to the device registration management unit 611. The device registration management unit 611 records the device owner change instruction in the owner change management table shown in Table C below.

[0097] Table C shows an example of the collection setting management table managed by the collection setting management unit 621. (Table C) TIFF2025109492000004.tif27165

[0098] The "device identification information" is information equivalent to the "device identification information" in Table A. The "destination owner device registration key" is information equivalent to the "device registration key" in Table A.

[0099] At S802, the server connection application 501 requests the acquisition of access permission information for the first time to communicate with the storage server 102 after S801. Specifically, when the storage server communication unit 519 requests the acquisition of access permission information from the device connection management unit 612, the device connection management unit 612 confirms the owner change instruction with the device registration management unit 611. Since the owner change instruction is recorded at S801, the device connection management unit 612 transmits the change destination owner device registration key (Table C) as an owner change instruction instead of access permission information to the management server connection management unit 513.

[0100] When notified of the owner change from the device connection management unit 612 at S802, at S803, the management server connection management unit 513 registers this device as a customer organization's device. Specifically, the management server connection management unit 513 uses the change destination owner device registration key transmitted at S802 to register the device with the device registration management unit 611. The management server connection management unit 513 acquires identification information as a customer organization's device as a response to this device registration request.

[0101] Mainly at S701, S703, S803, S805, etc., the management server connection management unit 513 can function as an example of a registration means for registering the network device 104 with the server.

[0102] At S804, the device registration management unit 611 registers the collection settings as a customer organization's device with the collection settings management unit 621.

[0103] At S805, the management server connection management unit 513 saves the identification information acquired from the device registration management unit 611 at S803 to the identification information holding unit 512.

[0104] In S806, similar to S704, the collection setting acquisition unit 518 acquires the collection settings associated with the device 104 from the collection setting management unit 621. In S804, the collection settings for the devices of the customer organization are registered in the collection setting management unit 621. Therefore, the collection settings acquired by the collection setting acquisition unit 518 in S806 are also the collection settings for the devices of the customer organization.

[0105] In S807, the collection setting acquisition unit 518 saves the collection settings for the devices of the customer organization acquired in S806 in the collection setting holding unit 507.

[0106] In S808, the log information collection unit 505 detects that the collection settings for the devices of the customer organization are saved in the collection setting holding unit 507, and starts acquiring log information according to the collection settings.

[0107] In S809, similar to S707, when the log information collection unit 505 detects the occurrence of an event such as a state transition of the user interface 5560, etc., it normalizes the log information. Then, the log information collection unit 505 saves it as log information (2) for the devices of the customer organization in the second buffer 542.

[0108] Figures 11 and 12 are sequence diagrams showing the processing from the saving of the trigger information created at the timing set in the collection settings to the transmission of the log information (2) for the devices of the customer organization to the upload area 623 for the customer organization. The upload area for the customer organization is, for example, the upload area 623b in Figure 6, and the one for the previous owner of the device is the upload area 623a. The parts where the lifetime in the figure is activated represent that the data is registered and saved. As a prerequisite for Figures 11 and 12, the progress of the sequences in Figures 9 and 10 is required.

[0109] In S901, the trigger information generated by the log information collection unit 505 at the timing set in the collection setting is stored in the third buffer 543. There are roughly two patterns in the timing when the trigger information is generated by the log information collection unit 505. One is the timing when the log information designated as the trigger for the batch transmission timing in the collection setting is stored by the log information collection unit 505 in the second buffer 542. The other is the timing when the internal timer in the log information collection unit 505 fires (the time of the internal timer reaches the designated time) determined by the collection setting.

[0110] In S902, the log information transmission unit 511 detects that the trigger information is stored in the third buffer 543. Then, the log information transmission unit 511 acquires the newly stored trigger information from the third buffer 543.

[0111] In S903, based on the path information written in the trigger information acquired in S902, the log information transmission unit 511 reads the untransmitted log information from the second buffer 542. As shown in FIGS. 7 to 10, in the second buffer 542, the log information (1) of the device of the sales organization and the log information (2) of the device of the customer organization are stored as untransmitted log information. Therefore, in the cases of the examples in FIGS. 11 and 12, the log information transmission unit 511 reads these two pieces of log information (1) and (2).

[0112] In S904, the log information read by the log information transmission unit 511 is transmitted. As an internal process of S904, the log information transmission unit 511 reads the identification information from the identification information holding unit 512. Then, the log information transmission unit 511 compares the storage time of the identification information with the generation time of each piece of log information read from the second buffer 542, and excludes the log information having a generation time earlier than the storage time of the identification information from the transmission target. In the examples of FIGS. 11 and 12, the generation time of the log information (1) of the device of the sales organization is earlier than the storage time of the device identification information stored in the identification information holding unit 512. Therefore, this log information (1) is excluded from the transmission target, and the transmission of the log information (2) of the device of the customer organization is started.

[0113] In S905, the storage server communication unit 519 acquires access permission information from the device connection management unit 612. This access permission information is for transmitting the log information (2) as a device of the customer organization whose transmission was started in S904 to the storage server 102.

[0114] In S906, the storage server communication unit 519 uses the access permission information acquired in S905 to acquire upload area information from the upload area management unit 622. Specifically, the storage server communication unit 519 acquires it by transmitting a request for acquiring upload area information. The upload area management unit 622 confirms the identification information included in the request for acquiring upload area information received from the storage server communication unit 519. If the upload area 623 for the corresponding customer organization is not secured, the upload area management unit 622 newly secures the upload area 623b for the customer organization.

[0115] In S907, the storage server communication unit 519 uploads the log information (2) as a device of the customer organization to the upload area 623b by using the access permission information acquired in S905 and the upload area information acquired in S906.

[0116] FIG. 13 and FIG. 14 are flowcharts showing the batch transmission process of the log information stored in the second buffer 542, which is executed by the device 104. Specifically, the processes in FIG. 13 and FIG. 14 correspond to the processes from S902 to S907 in FIG. 11 and FIG. 12. This process is realized by the CPU 401 reading a program corresponding to the processing content from the ROM 402 or the HDD 404, loading it into the RAM 403, and executing it.

[0117] In S1001, the log information transmission unit 511 acquires the trigger information detected for saving in S902 from the third buffer 543.

[0118] In S1002, the log information transmission unit 511 refers to the area information of the second buffer 542 included in the trigger information acquired in S1001 and accesses the second buffer 542. Then, the log information transmission unit 511 determines whether one or more pieces of new log information that have not been processed are included in the second buffer 542.

[0119] If one or more pieces of new log information are included, in S903, the log information transmission unit 511 reads the new log information. If one or more pieces of new log information are not included, since there is no content to be transmitted, the batch transmission process ends.

[0120] In S1004, the log information transmission unit 511 acquires the storage time when the device identification information was stored in the identification information holding unit 512 in S805.

[0121] In S1005, the log information transmission unit 511 acquires any one piece of log information that has not been acquired (not acquired in the past S1005) from the group of new log information acquired from the second buffer 542 in S903.

[0122] In S1006, the log information transmission unit 511 determines whether the generation time of the log information acquired in S1005 is earlier than the storage time of the identification information acquired in S1004.

[0123] If the result in S1006 is Yes, in S1007, the log information transmission unit 511 registers the log information as not being a transmission target in the log information transmission target table that is temporarily generated only during the period of this batch transmission process. If the result in S1006 is No, in S1015, the log information transmission unit 511 registers the log information as a transmission target in the log information transmission target table.

[0124] Table D shows an example of the log information transmission target table that the log information transmission unit 511 temporarily generates only during the batch transmission process. (Table D) TIFF2025109492000005.tif31165

[0125] The "log information ID" is identification information that is unique during the batch transmission process within the log information transmission unit 511 and is associated with one piece of log information. The "transmission target type" is flag information that identifies whether the log information corresponding to the log information ID is a transmission target. The value is a binary value of "transmission target" or "non-transmission target".

[0126] In S1008, the log information transmission unit 511 determines whether there is log information in the new log information group acquired in S903 for which the generation time has not been compared at the time of S1008 in the past. If Yes in S1008, the log information transmission unit 511 performs the process of S1005.

[0127] If No in S1008, the log information transmission unit 511 assumes that the log information transmission target table is completed, sends the log information transmission target table and the new log information group acquired in S903 to the storage server communication unit 519, and performs the processes of S905 and S906. The description of the processing contents of S905 and S906 is omitted as described above.

[0128] In S1011, the storage server communication unit 519 acquires any one piece of log information from the new log information group acquired from the second buffer 542 in S903 that has not been acquired in the past at S1011.

[0129] In S1012, the storage server communication unit 519 refers to the log information transmission target table and determines whether the one piece of log information acquired in S1011 is a transmission target.

[0130] If Yes in S1012, in S1013, the storage server communication unit 519 transmits the target log information to the upload area 623b for the customer organization using the access permission information acquired in S905 and the upload area information acquired in S906.

[0131] If No in S1012, in S1014, the storage server communication unit 519 determines whether there is log information in the new log information group acquired in S903 for which the determination of S1012 has not been made.

[0132] If the answer is Yes in S1014, the storage server communication unit 519 performs the process of S1011. If the answer is No in S1014, this batch transmission process ends.

[0133] As described above, when the owner of the device 104 changes the device registration from the sales organization to the customer organization, the log information (1) as the device of the sales organization is excluded from the transmission targets in S904. As a result, the log information as the device of the sales organization stored in the second buffer 542 inside the device can be prevented from being transmitted to the upload area for the customer organization. As a result, only the log information (2) as the device of the current owner in the device whose owner has been changed can be transmitted to the upload area as the device of the current owner. That is, this system can appropriately and strictly manage the log information generated during the contract period by the previous owner, and can suppress the risk of leakage of personal information.

[0134] Also, if only the immediate processing via the first buffer 541 is used without using the second buffer 542, the number of connections to the server increases in proportion to the number of events, so the cost increases. By performing batch transmission at an arbitrary timing by the second buffer 542, such an increase in cost can be suppressed.

[0135] (Other Embodiments) Although the present disclosure has been described in detail based on its preferred embodiments, the present disclosure is not limited to the above embodiments, and various modifications are possible based on the gist of the present disclosure, and they are not excluded from the scope of the present disclosure.

[0136] For example, in the above embodiment, the start time of the contract is set to the time when the identification information is stored (for example, S703 or S805), but it is not limited to this. The start time of the contract may be any time within the period during which the process for registering the device is performed (the time when it is registered). The period during which the process for registering the device is performed is, for example, S701 to S703 or S801 to S805.

[0137] In the above embodiment, as the owner of the device 104, an example of the change of the owner from the sales organization to the customer organization was described. However, it is similarly applicable to the change of the owner from one customer organization to another customer organization, or the change of the owner within the same customer organization.

[0138] The disclosure of this embodiment includes the following configurations, methods, and programs. (Configuration 1) A network device that can be connected to a server via a network, collection means for collecting log information of events occurring within the network device; storage means for storing the collected log information; transmission means for transmitting the stored log information to the server via the network; filtering means for comparing the occurrence time of the event with the contract start time of the current contract for owning the network device, and filtering so as not to transmit to the server the log information of the event that occurred before the contract start time among the stored log information. A network device characterized by the above. (Configuration 2) further comprising registration means for performing a process for registering the network device with the server, wherein the contract start time is the time when the network device is registered with the server The network device according to Configuration 1, characterized by the above. (Configuration 3) The registration means acquires and stores identification information for identifying the network device from the server, wherein the contract start time is the time when the identification information is stored The network device according to Configuration 2, characterized by the above. (Configuration 4) further comprising request means for requesting acquisition of information regarding the upload area of the log information in the server, The registration means acquires and stores identification information for identifying the network device from the server. By transmitting the log information, the transmission means causes the server to store the log information in the upload area corresponding to the identification information secured in the server. The network device according to Configuration 2 or 3, characterized in that. (Configuration 5) The collection means generates trigger information including at least the transmission time. Based on the trigger information, the transmission means transmits the accumulated log information to the server. The network device according to any one of Configurations 1 to 4, characterized in that. (Configuration 6) The trigger information further includes at least one of the name of the event corresponding to the log information to be transmitted and information on the storage area of the log information by the storage means. The network device according to Configuration 5, characterized in that. (Configuration 7) The network device is a printing device, a scanner, or a multifunction device. The network device according to any one of Configurations 1 to 6, characterized in that. (Method) An information processing method for a network device that can be connected to a server via a network, A collection step of collecting log information of events occurring in the network device, An accumulation step of accumulating the collected log information, A transmission step of transmitting the accumulated log information to the server via the network, A filtering step of comparing the occurrence time of the event with the contract start time of the current contract for owning the network device, and filtering so as not to transmit the log information of the event that occurred before the contract start time among the accumulated log information. An information processing method, characterized in that. (Program) A program for operating a computer as the network device according to any one of Configurations 1 to 7.

Claims

1. A network device that can be connected to a server via a network, collecting means for collecting log information of events occurring within the network device; storing means for storing the collected log information; transmitting means for transmitting the stored log information to the server via the network; filtering means for comparing the occurrence time of the event with the contract start time of the current contract for owning the network device, and filtering so as not to transmit to the server the log information of the event that occurred before the contract start time among the stored log information. A network device characterized by the above.

2. further comprising registering means for performing a process for registering the network device with the server, wherein the contract start time is the time when the network device is registered with the server The network device according to claim 1, characterized by the above.

3. The registering means acquires and stores identification information for identifying the network device from the server, wherein the contract start time is the time when the identification information is stored The network device according to claim 2, characterized by the above.

4. further comprising requesting means for requesting acquisition of information regarding the upload area of the log information in the server, the registering means acquires and stores identification information for identifying the network device from the server, the transmitting means transmits the log information to cause the server to store the log information in the upload area corresponding to the identification information secured in the server. The network device according to claim 2, characterized by the above.

5. The collecting means generates trigger information including at least the transmission time, the transmitting means transmits the stored log information to the server based on the trigger information The network device according to claim 1, characterized by the above.

6. The trigger information further includes at least one of the name of the event corresponding to the log information to be transmitted and information on the storage area of the log information by the storage means. The network device according to claim 5, characterized by the above.

7. The network device is a printing device, a scanner, or a multifunction machine. The network device according to claim 1, characterized by the above.

8. An information processing method for a network device that can be connected to a server via a network, comprising: a collecting step of collecting log information of events occurring within the network device; a storing step of storing the collected log information; a transmitting step of transmitting the stored log information to the server via the network; a filtering step of comparing the occurrence time of the event with the contract start time of the current contract for owning the network device, and filtering so as not to transmit to the server the log information of the event that occurred before the contract start time among the stored log information; An information processing method characterized by the above.

9. A program for operating a computer as the network device according to any one of claims 1 to 7.

Images