JP5540593B2 - Control apparatus, image processing apparatus, control method, and program - Google Patents

Description

  The present invention relates to a control device incorporated in a device to reduce the number of times that the device in the power saving state receives a request through the network and returns from the power saving state to save power, its control method, and its control The present invention relates to a computer-readable program for realizing the method, and further to an image processing apparatus incorporating the control device.

  In recent years, many energy-saving devices have emerged in order to suppress mass consumption of limited energy resources and prevent deterioration of the natural environment such as global warming. Many PCs and MFPs (Multi Function Peripherals) are also provided with an energy saving mode, and such devices are set to shift to a power saving state when job processing is not performed for a certain period. The device that has shifted to the power saving state accepts a request from the network and returns from the power saving state when a job needs to be processed.

  The transition to the power saving state in the energy saving mode is performed by stopping the power supply to most devices such as the CPU and HDD while the current parameters and the like are stored in the memory. At this time, since the data of the state in which the OS is activated is held, the OS is not restarted at the time of restoration, and can be restored as it is to the state before suspension.

  The more modules whose power supply is stopped in the energy saving mode, the longer it takes to recover from the power saving state. In addition, since the hardware modules and software modules that make up the product are closely related, the return time differs for each model. For this reason, in a network environment in which a plurality of devices are connected to the network, a client device that searches for the connection status and operation status of the devices cannot uniquely determine the timeout time that is the upper limit of the search response time. If this timeout time is set short, devices that could not be recovered from the power saving state within the timeout time will not be displayed in the search results.

  On the other hand, if the timeout time is set to be long, even if there is no device to be searched, it must be determined, which takes extra time.

  Therefore, before switching to the energy saving mode, information that can specify the return time from the energy saving mode is notified to the information processing device connected via the network, and the information processing device starts up to the device equipped with the energy saving mode. There has been proposed a technique for transmitting a processing request to a device equipped with an energy saving mode after a return time has elapsed after transmitting the request (see Patent Document 1). With this technology, when an information processing device communicates with another device having an energy saving mode, even if the other device is in the energy saving mode, it can communicate more efficiently in consideration of the return time from the energy saving mode. Can do.

  When a device receives an event monitoring request through the network, when an event occurs in the device, the event is notified to the event monitoring destination that transmitted the request. At this time, the device can manage event monitoring requests from a plurality of event monitoring destinations using an event management table or the like. The WS-Eventing protocol used on the Web service is a protocol used for registration and notification of this event. In WS-Eventing, the first monitoring request command is called Subscribe and the second and subsequent monitoring request commands are called Renew. In the event management table or the like, an effective period can be set for each event monitoring destination. The purpose of this is to effectively use the resource of the device for event monitoring by deleting the event monitoring destination whose validity period has expired. Therefore, the event monitoring destination updates the validity period by sending a monitoring request again before the validity period expires. Note that the concept of a valid period tends to exist in a request notified from a network, not limited to device monitoring.

  Such a monitoring request is transmitted about once every 30 minutes in a PC equipped with Windows (registered trademark) Vista, so that even if the device shifts to the power saving state, the monitoring request is restored immediately. It is not preferable from the viewpoint of energy saving.

  In many cases, the IP address is assigned by the DHCP server in the network to which the device belongs. In this case, in order to effectively use the IP address, a lease period is generally set, and the period is often set with about 2 to 8 hours as a guide. This is because the daily work time is set as a guide. This also requires a return from the power saving state.

  When a device belongs to an IPv6 environment, a stateless IPv6 address is often used. This address is created by the device based on a RA (Router Advertisement) prefix from a router for connecting to another network. The RA is a multicast packet periodically transmitted from the router, and is transmitted once every several hours. Therefore, this also requires a return from the power saving state.

  Therefore, there is a demand for an apparatus and a method that can suppress the power consumption by reducing the return of the device from the power saving state as much as possible.

  In order to solve the above-described problem, the present invention adjusts the effective period of a response when an event monitoring request or a remonitoring request is received, and reduces the number of times the remonitoring request is received. Thereby, the return from the power saving state of the device can be reduced and power consumption can be suppressed.

  That is, according to the present invention, a control device that receives an event monitoring request from an external device and notifies the event when the event occurs is used to control event monitoring, and has an effective period from the external device. In response to receiving the event monitoring request, the power state of each device in the device is confirmed, and a determination means for determining whether or not the device shifts to the power saving state, A control device is provided that includes a notification unit that returns a response in which the valid period is changed to an external device and transmits a re-monitoring request based on the changed valid period.

  The monitoring request and the re-monitoring request do not know when and where they come from, and even if the valid period is extended, there is a possibility that the monitoring request will come randomly and return from the power saving state. Therefore, the notifying unit adjusts each valid period so that the reception times of re-monitoring requests transmitted from a plurality of external apparatuses are all the same, and returns a response having each adjusted valid period to each external apparatus. Configure as follows. Thereby, the return timing from a power saving state can be concentrated, and the frequency | count of return from a power saving state can be reduced.

  If there are many event monitoring destinations and the validity period is extended so that they are all at the same time, many event monitoring destinations will access the device at the same time. Monitoring may not be established. Therefore, the notifying unit adjusts each effective period so that the reception times of remonitoring requests transmitted from a plurality of external devices are shifted by a preset time interval, and sends a response having each adjusted effective period to each external Configure to return to device. As a result, re-monitoring can be reliably established.

  Further, the notifying unit can notify the external device of the power saving state transition event in response to the transition to the power saving state, and can prevent the external device from transmitting an event monitoring request. Thereby, the return from the power saving state by the remonitoring request is not performed, and the power consumption of the device can be suppressed.

  In response to the fact that the device has returned from the power saving state for some reason, the notification means can notify the external device of a power saving state cancellation event and cause an event monitoring request to be transmitted. Thereby, the re-monitoring request can be resumed.

  According to the present invention, an image processing apparatus including the above-described control apparatus and capable of shifting to a power saving state communicating with an external apparatus, a method for controlling event monitoring by the above-described control apparatus, and a computer for realizing the method It is also possible to provide a readable program.

  In response to receiving an event monitoring request having a valid period from an external device, this control method checks the power state of each device in the device and determines whether the device shifts to a power saving state. And a step of returning a response in which the valid period is changed to the external device and transmitting a re-monitoring request based on the changed valid period when it is determined to shift.

  In addition to including processing performed by each means included in the control device as a processing step, this method also includes a step for detecting an abnormality of the device and a response to an inquiry from an external device, so that an external device is not returned. A step of stopping the event monitoring.

  According to the present invention, it is possible to suppress power consumption by minimizing the return of the device from the power saving state.

The figure which illustrated the network system which consists of a some apparatus connected to the network in 1st embodiment. The figure which illustrated the software configuration and hardware configuration of the apparatus in 1st embodiment. The figure which illustrated the composition of the network control part and the power management part. The figure which illustrated the message of the Subscribe request in WS-Eventing protocol. The figure which illustrated the message of SubscribeResponse. The figure which illustrated another message of SubscribeResponse. The figure which illustrated the notification message when the event with respect to a Subscribe request generate | occur | produced. The sequence diagram which showed the flow of the process between the apparatus between the Subscriber and the apparatus which generate | occur | produces an event at the time of receiving a Subscribe request and a Renew request, and the process performed in the apparatus. The internal sequence of an apparatus performed when an event occurs, and an external sequence diagram. The figure which illustrated the event management table which an event management part holds. The sequence diagram which showed the flow of the process which performs the process with respect to a Subscribe request and a Renew request, the notification of a power saving state transfer event, and the notification of a power saving state cancellation | release event. The sequence diagram which showed the flow of the process which inquires an apparatus state from Subscriber in a power saving state. The figure which showed the example which synchronizes a Renew request so that an effective period may be adjusted so that the reception time of the Renew request from several Subscribers may become substantially the same, and may reduce the return timing from the power saving state by a Renew request. The figure which illustrated the event management table in each timing. The figure which showed the example which adjusts a valid period so that the reception time of the Renew request from several Subscribers may shift | deviate slightly, and reduces the return timing from the power saving state by a Renew request. The figure which illustrated the event management table in each timing. The figure which showed the flow of the process which produces | generates and returns a response after determining valid time. The figure which showed the flow of a process in the case of synchronizing a Renew request and adjusting a valid time so that the reception time of the Renew request from several Subscribers may become substantially the same, and shifting a Renew request slightly. The figure which illustrated the module configuration on the side which monitors equipment. The figure which illustrated the flow of the process which the side which monitors an apparatus performs. The figure which shows the structural example of the network system of 2nd embodiment. The figure which illustrated the software configuration and hardware configuration of the apparatus in 2nd embodiment. It is a sequence diagram for demonstrating the process sequence of the search process of the widget by a provider application.

  FIG. 1 is a diagram illustrating a network system including a plurality of devices connected to a network such as the Internet or an intranet according to the first embodiment. In FIG. 1, a plurality of PCs 10 to 16 and the device 17 can communicate with each other. For example, the PCs 10 to 16 send a request to the device 17 and the device 17 returns a response to the request.

  Requests sent by the PCs 10 to 16 are issued before the expiration of an event monitoring request for requesting notification when an event occurs, an event registration request for registering an event to be monitored, and an effective period for event monitoring. There is an event remonitoring request. The event is notified when the device shifts to or returns to the power saving state, or when an error occurs. The PCs 10 to 16 send an event registration request and a monitoring request to the device 17 in order to monitor events occurring in the device 17.

  The PCs 10-16 send a request, receive a response to the request, a memory that stores a program, a processor that reads and executes the program from the memory, a network I / O that connects to the network and performs data communication with the network In addition, an input device for inputting data and the like, and a display device for displaying work contents, current status, and the like are provided.

  Here, PCs 10 to 16 other than the device 17 are used. However, the present invention is not limited to the PC, and any apparatus capable of performing communication via a network may be used. It can also be a device.

  With reference to FIG. 2, the software configuration and hardware configuration of the device 17 will be described. The software configuration can be broadly divided into an application part and a platform part. The application unit performs processing specific to user services related to image forming processing such as a printer, copy, fax, and scanner. The application unit includes a printer application 20 that is a page description language and a printer application, a copy application 21 that is a copy application, a fax application 22 that is a facsimile application, and a scanner application 23 that is a scanner application. And a network file application 24 which is an application for network files.

  The platform unit provides basic functions commonly used by applications, and OS / Kernel 30 including an OS that manages the entire device, a kernel that implements the basic functions of the OS, and processing requests from the application unit And various control units that generate acquisition requests for various resources such as hardware. The OS / Kernel 30 also includes a network processing unit below a socket that combines an IP address and a port number. Various control units include a system control unit 31, a memory control unit 32, an engine control unit 33, a fax control unit 34, an operation control unit 35, a distribution control unit 36, a network control unit 37, a security control unit 38, a power management unit 39, and the like. Consists of

  The platform unit is configured to have an application program interface (API) 40 that can receive a processing request from the application unit using a predefined function.

  The system control unit 31 included in the platform unit performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control.

  The memory control unit 32 performs memory control such as acquisition and release of memories such as the NVRAM 62 and the RAM 65, and compression and expansion of image data. The engine control unit 33 performs engine control of hardware resources not shown in FIG. The fax control unit 34 is connected to an analog public telephone network (GSTN) I / F 68, transmits / receives facsimiles using the GSTN network from each application layer of the system controller, and registers / registers various facsimile data managed in a backup memory. An API for performing quoting, facsimile reading, and facsimile reception printing is provided.

  The operation control unit 35 controls an operation panel serving as information transmission means between the operator and the main body control. The distribution control unit 36 performs data management, data processing, and the like for transmission / reception with other devices. The network control unit 37 is connected to a network I / F 66 such as Ethernet (registered trademark), provides a service that can be commonly used for applications that require the network I / O, and receives data received from the network according to each protocol. Are distributed to each application, and mediation is performed when data from each application is transmitted to the network.

  The security control unit 38 provides security services to the application unit and each control unit. For example, encryption or decryption processing is performed. The power management unit 39 monitors the electrical state of the CPU 63 and other hardware resources, and manages and monitors the power saving state in other control units and application units. The power management unit 39 operates in close association with the OS / Kernel 30.

  The SOAP / XML processing unit 50 encodes / decodes a SOAP / XML message. The SOAP / XML processing unit 50 can be used from both the application unit and the platform unit. The SOAP / XML processing unit 50 is normally provided in a library format, but may be in a process format such as an application or a control unit.

  The CPU 63 controls the entire device 17, functions as each control unit of the platform unit, and executes each application of the application unit that uses each control unit. Note that each control unit and each application shown in FIG. 2 do not need to include all of them depending on the device configuration, and may include only a part thereof. The device 17 includes an HDD 61 for storing software programs such as applications, a ROM 64 for storing initialization programs and boot loaders, an external device I / F 67 for communicating with external devices, challenge response authentication, and the like. A secure device 60 that performs cryptographic processing is provided. The secure device 60 includes an IC chip and the like.

  FIG. 3 is a diagram illustrating the configuration of the network control unit and the power management unit. In FIG. 3, an application and SOAP / XML processing unit 50 are also shown. Here, the application is the printer application 20. The network control unit and the power management unit function as a determination unit that determines whether or not to shift to the power saving state and a notification unit that returns a response.

  The network control unit 37 includes a network overall control unit 37a that supervises overall network control, a network communication unit 37b that exchanges messages and data with other applications and other control units, an HTTP control unit 37c, and a WS-Eventing protocol. A WS-Eventing processing unit 37d for processing, a protocol control unit 37e for processing various protocols (FTP, Port9100 LPR, etc.) other than HTTP, and an event management unit 37f for managing events.

  The power management unit 39 is a power source control unit 39a that controls the entire power control, a power communication unit 39b that exchanges messages and data with other applications and other control units, and power sources of devices such as hardware resources. It is composed of a hardware management unit 39c that checks the status. The application 20 includes an overall application control unit 20a that supervises overall application control, an application communication unit 20b that exchanges messages and data with other applications and other control units, and an event detection unit 20c that detects events. It is configured.

  When an event monitoring request having a valid period is sent from an external device such as the PCs 10 to 16 connected to the network shown in FIG. 1 using the WS-Eventing protocol, the WS-Eventing processing unit 37d performs processing. A Subscribe request in the WS-Eventing protocol will be described with reference to FIG. The Subscribe request shown in FIG. 4 is a request that an event monitoring destination (Subscriber), which is an external device, has registered PrinterStatusEvent, and wants to be notified when PrinterStatus changes. In this request, 30 minutes is requested as an effective period (effective time in the Expires field).

  The validity period is updated in response to this request. At this time, the power management unit 39 determines whether or not to shift to the power saving state, and if it is determined to shift, the validity period is extended and updated. Returns a response with the valid period data. Details of this processing will be described later, and here, SubscribeResponse returned by the device 17 in response to the Subscribe request will be described. FIG. 5 shows an example of a SubscribeResponse message. In the response shown in FIG. 5, it is determined that there is no transition to the power saving state, and the response is updated with the same effective period of 30 minutes as the request and includes the effective period.

When it is determined that there is a transition to the power saving state, when the validity period is extended and updated, as shown in FIG. 6, a response in which the validity period of the SubscribeResponse is extended from 30 minutes to 40 minutes of the request and Is done. Here, it is extended to 40 minutes, but is not limited to this, and can be extended to several hours such as 2 to 8 hours. For example, this time can be set in advance and extended by the set time. However, it doesn't just mean long. As described above, since requests are periodically notified from the DHCP server or the router, there is no power saving effect even if the period is longer than the period notified from these requests.
On the other hand, when the subscriber needs to continue monitoring beyond the valid period included in the response, the Subscriber performs a Renew request, which is a re-monitoring request, before the valid period elapses to update the valid period. In response to this, the device 17 responds with RenewResponse. Note that after the validity period has not been updated, the device 17 ends the monitoring of the corresponding event.

  Since the Subscribe request here is a request for notification when the Printer Status changes, the device 17 notifies the event when any event occurs. FIG. 7 is an example of a notification message when an event (PrinterStatusEvent) for the Subscribe request shown in FIG. 4 occurs. The notification message shown in FIG. 7 is a message for notifying the situation of no toner because an event of no toner has occurred.

  With reference to FIG. 8, processing between the Subscriber 70 and the device (EventSource) 17 that generates an event when receiving a Subscribe request and a Renew request and processing performed inside the device 17 will be described in detail. When the device 17 receives a Subscribe / Renew request from the subscribe 70 that is the event monitoring destination, first, the HTTP control unit 37c in the network control unit 37 of the device 17 receives the request. The HTTP control unit 37c passes the content of the request to the WS-Eventing processing unit 37d, analyzes the content of the request by the SOAP / XML processing unit 50, and registers the registration to the event management unit 37f if it is a Subscribe request. If it is a request, confirm it. The event management unit 37f exchanges with the related application 20 as necessary. Thereafter, the event management unit 37f makes an inquiry to the power management unit 39, and the power management unit 39 confirms the power supply state of each device such as hardware resources and answers the inquiry. The event management unit 37f determines whether or not it is likely to shift to the power saving state from the response, determines the valid period for the event, and the WS-Eventing processing unit 37d processes the registration / confirmation result as a SOAP / XML process. A message is generated through the unit 50, and a response is returned to the subscriber 70 through the HTTP control unit 37c.

  In FIG. 8, the event management unit 37f makes an inquiry to the power management unit 39, but the power management unit 39 changes the power state, that is, changes to the power saving state or returns from the power saving state. Can also be notified. In this case, the event management unit 37f does not make an inquiry to the power management unit 39.

  Processing when an event occurs will be described with reference to the internal sequence and external sequence (between the event monitoring destination and the device that generates the event) of the device 17 when the event occurs shown in FIG. When the event detection unit 20c of the application 20 detects an event, the event management unit 37f receives the event and notifies the WS-Eventing processing unit 37d, and converts it into a message through the SOAP / XML processing unit 50. The WS-Eventing processing unit 37d performs notification (Notification) of the event that is messaged to the Subscriber 70 through the HTTP control unit 37c.

  The event management unit 37f holds an event management table, and manages the subscriber and the valid period, which are event monitoring destinations, using the event management table. For this reason, the event management unit 37f determines whether to extend the validity period or how much to extend depending on whether the transition to the power saving state is performed, and sends a Subscribe / Renew response including the extended validity period. Can be sent. For example, if it is found that the power saving state is entered within 5 minutes, it is determined that the effective period is extended. In addition, when a multicast packet is regularly notified from the router, the notification interval is known, so the time is extended until this notification interval or the next router notification. FIG. 10 is a diagram illustrating an example of an event management table held by the event management unit 37f. In this table, the Subscriber, the event ID, the IP address of the event monitoring destination, the contents of the event, the valid period, and the time until the valid period expires are held. The value of the time until expiration expires with the passage of time. In FIG. 10, the two tables of FIG. 10A and FIG. 10B are shown, but one table may be used.

  The content of the event can include an energy saving event in addition to “no toner”, “no paper”, and “cover open” shown in FIG. The energy saving event includes “power saving state transition” and “power saving state cancellation”. The Subscriber 70 transmits these Subscribe requests and notifies the device 17 of the power saving state transition event and the power saving state cancellation event. Can receive.

  With reference to the sequence shown in FIG. 11, a process for a Subscribe request and a Renew request, and a process for notifying a power saving state transition event and a power saving state release event will be described. The Subscriber 70 transmits a Subscribe request for notification when an event occurs. The device 17 receives the request, registers it, and returns a response indicating that it has been registered. At this time, since it does not shift to the power saving state, the response is returned without updating the time until expiration and extending the valid period. Before the valid period elapses (time until expiration becomes 0), the subscriber 70 makes an event monitoring update request by a Renew request. In response to this, the device 17 receives the update request and returns a response indicating that the update has been made. Also at this time, since the state does not shift to the power saving state, the response is returned without updating the time until expiration and extending the valid period.

  Before the valid period elapses again, the subscriber 70 makes an event monitoring update request using a Renew request. In response to this, the device 17 receives the update request and returns a response indicating that the update has been made. At this time, since it is almost planned to shift to the power saving state, a response with an extended effective period is returned.

  The Subscriber 70 also sends a request for notification to the device 17 when the device 17 shifts to the power saving state, and a request for notification when the device returns from the power saving state. When the state is shifted to the power saving state, a power saving state transition event is notified to the subscriber 70, and when the power saving state is canceled, the power saving state cancellation event is notified to the subscriber 70. For this reason, the Subscriber 70 does not transmit the Renew request during the power saving state, and resumes the transmission of the Renew request after receiving the notification of the power saving state cancellation event. During the power saving state, the event management unit 37f does not update the valid period in the event management table, and does not delete information from the event management table even if the valid period has elapsed. Thereby, the Subscriber 70 can continue to monitor the event even after the power saving state is canceled.

  With reference to FIG. 12, processing for inquiring a device state from the subscriber 70 during the power saving state will be described. Before the valid period elapses, the subscriber 70 makes an event monitoring update request through a Renew request. In response to this, the device 17 receives the update request and returns a response indicating that the update has been made. At this time, since the power saving state is not entered, a response that does not extend the valid period is returned.

  Before the valid period elapses again, the subscriber 70 makes an event monitoring update request using a Renew request. In response to this, the device 17 receives the update request and returns a response indicating that the update has been made. At this time, since a transition to the power saving state is scheduled, a response in which the valid period is extended is returned.

  The Subscriber 70 also transmits a request for notification to the device 17 when the state is shifted to the power saving state, and a request for notification when the state is returned from the power saving state. When the device 17 shifts to the power saving state, the device 17 A power saving state transition event is notified to the subscriber 70. Then, the Subscriber 70 does not transmit the Renew request until receiving the power saving state cancellation event.

  The Subscriber 70 can make an inquiry by using a command that can be handled without returning from the power saving state such as ping during the power saving state. Ping is a command for confirming whether communication with the other party is possible in the TCP / IP network. If there is a response from the device 17, the subscriber 70 determines that the device is in the power saving state. If there is no response, the subscriber 70 determines that there is an abnormality in the device 17 and stops monitoring the device.

  If there is only one event monitoring destination, it is only necessary to extend the validity period so that a Renew request is not received during the power saving state. However, if there are multiple event monitoring destinations, the Renew May receive frequent requests. This frequently returns from the power saving state, and power saving cannot be achieved.

  Therefore, the reception times of Renew requests from a plurality of event monitoring destinations are adjusted to be substantially the same, and reception of Renew requests is concentrated. Thereby, the frequency | count of return from a power saving state can be decreased. FIG. 13 shows an example in which the Renew request is synchronized so that the validity period is adjusted so that the reception times of the Renew requests from the plurality of Subscribers are substantially the same, and the return timing from the power saving state by the Renew request is reduced. FIG. Here, there are two subscribers, and the device 17 confirms the validity period of each, and adjusts the validity period so that the time when the Renew request is received from the two subscribers becomes almost the same time. The time when the Renew request is received from the subscriber 71 is referred to as the start point, with the subscriber 71 as a reference. A response is returned to the subscriber 71 with the extended new effective period C. For the subscriber 72, the difference D from the start point is taken. First, a response is returned in the provisional period (C-D), and a response is returned in the valid period C at the next response.

  FIG. 14 is a diagram illustrating an event management table at each timing. Each timing is the time of T1, T2, and T3 shown in FIG. FIG. 14A illustrates the event management table in T1 before adjustment, FIG. 14B illustrates the event management table in the provisional period T2, and FIG. 14C illustrates the event management table in T3 after adjustment. FIG. Before the adjustment shown in FIG. 14A, the Subscriber 71 requests an effective period of 15 minutes, and the Subscriber 72 requests an effective period of 10 minutes. For this reason, the time when the device 17 receives the Renew request is different. When the adjustment is started, the event management unit 37f determines 20 minutes as a new effective period, returns a response to the subscriber 71 with the extended new effective period 20 minutes, and the event monitoring table is also as shown in FIG. Update to 20 minutes.

  For the Subscriber 72, the difference when the Renew request is received from the Subscriber 71 is set as Start Point (the time difference between the time when the Renew request is received from the Subscriber 71 and the time when the Renew request is received from the Subscriber B) is taken. Here, assuming that the time difference is 2 minutes, a response is returned in the provisional period 18 minutes after subtracting from the newly determined effective period 20 minutes. At this time, the event monitoring table is also updated to 18 minutes as shown in FIG.

  By adjusting in this way, a Renew request can be received from the subscriber 71 and the subscriber 72 at substantially the same time before the expiration of the valid period. In response to these requests, the device 17 returns a response with a validity period of 20 minutes to the Subscriber 71 without changing the validity period, returns a response with a validity period of 20 minutes to the Subscriber 72, and returns an event monitoring table. Is updated to 20 minutes as shown in FIG.

  When there are many event monitoring destinations, and when Renew requests from these many event monitoring destinations are concentrated, the device 17 is accessed at the same time, a session timeout occurs for a certain request, and re-monitoring is not established. There can be. Therefore, this problem can be solved by slightly shifting the time for receiving the Renew request.

  FIG. 15 is a diagram illustrating an example in which the effective period is adjusted so that reception times of Renew requests from a plurality of Subscribers are slightly shifted, and the return timing from the power saving state due to the Renew request is decreased. Here, there are two subscribers, and the device 17 confirms the validity period of each, and adjusts the validity period so that the time of receiving the Renew request from the two subscribers slightly shifts. That is, with reference to the subscriber 71, a response is returned to the subscriber A with the extended new effective period C. For the subscriber 72, the difference D from the start point is taken, the deviation amount α is added to it, and the response is returned in the provisional period (C−D + α). At the next response, the response with the same effective period C as the response to the subscriber 71 Returns a response.

  When there are three or more monitoring destinations, the deviation amounts are set to β, γ, δ, etc., and the temporary periods are set to CD + β, CD + γ, CD + δ, etc., and different values are used for the deviation amounts. By doing in this way, Renew requests from a plurality of monitoring destinations do not collide, session timeout or the like does not occur, and re-monitoring can be established reliably.

  FIG. 16 is a diagram illustrating an event management table at each timing. Each timing is a time point of T1, T2, and T3 shown in FIG. FIG. 16A illustrates the event management table in T1 before adjustment, FIG. 16B illustrates the event management table in the provisional period T2, and FIG. 16C illustrates the event management table in T3 after adjustment. FIG. Before the adjustment shown in FIG. 16A, the subscriber 71 requests an effective period of 15 minutes, and the subscriber 72 requests an effective period of 10 minutes. For this reason, the time when the device 17 receives the Renew request is different. When the adjustment is started, the event management unit 37f determines 20 minutes as a new effective period, returns a response to the subscriber 71 with the extended new effective period 20 minutes, and the event monitoring table is also as shown in FIG. Update to 20 minutes.

  For Subscriber 72, the difference (time difference between the time when the Renew request is received from Subscriber A and the time when the Renew request is received from Subscriber B) is taken when the time when the Renew request is received from Subscriber 71 is set as Start Point. Here, assuming that the time difference is 2 minutes, it is subtracted from the newly determined effective period of 20 minutes, 1 minute is added as the amount of deviation, and a response is returned in the provisional period of 19 minutes. At this time, the event monitoring table is also updated to 19 minutes as shown in FIG.

  By adjusting in this way, the Renew request from the Subscriber 72 can be received with a delay of 1 minute from the Renew request from the Subscriber 71. In response to these requests, the device 17 returns a response with a validity period of 20 minutes to the Subscriber 71 without changing the validity period, returns a response with a validity period of 20 minutes to the Subscriber 72, and returns an event monitoring table. Is updated to 20 minutes as shown in FIG.

  FIG. 17 is a diagram showing a flow of processing for generating and returning a response after determining the valid time. First, processing is started in Step 1700, and a monitoring and update request is received from the Subscriber 70 in Step 1710. In step 1720, the power supply state is checked to determine whether or not to shift to the power saving state. If it is determined in step 1730 to shift, the valid period is extended, and if it is determined not to shift, the valid period is set. Decide not to change. In step 1740, a response including the valid period is returned to the subscriber 70, and in step 1750, the process is terminated.

  FIG. 18 is a diagram showing a processing flow when the Renew request is synchronized so as to adjust the valid time so that the reception times of the Renew requests from the plurality of Subscribers are substantially the same, and when the Renew request is slightly shifted. It is. The processing shown in FIG. 18 corresponds to the processing shown in the sequence diagrams of FIGS.

  This process is started in step 1800. First, in step 1810, the process for the Renew request, that is, the reception of the Renew request and the transmission of the RenewResponse are repeated. When the adjustment is started in step 1820, the valid period requested by all subscribers is confirmed. This can be confirmed by referring to the event monitoring table managed by the event management unit 37f.

  In step 1830, the power supply state is checked to determine whether or not to shift to the power saving state, and in step 1840, a new valid period is determined. In step 1850, a response having a new validity period is returned for the first Renew request that adopts a new validity period. In step 1860, a provisional period is calculated and a provisional period is included for subsequent Renew requests. Returns a response. In step 1870, a response having a new valid time is returned to the Renew request after the first Renew request, and the processing is ended in Step 1880.

  The configuration and processing of the device 17 on the monitoring side have been described in detail so far. The configuration and processing of the external device on the monitoring side will be described below.

  FIG. 19 is a diagram illustrating a module configuration on the side that monitors the device 17. As shown in FIG. 1, the monitoring side of the device 17 is often a PC, but may be an MFP or the like as described above. The monitoring apparatus includes an overall controller 80 that controls the entire apparatus, a network controller 82 including an HTTP controller 81, a WS-Eventing processor 83, an event manager 84, and a SOAP / XML processor. 85. Here, only the minimum necessary modules are shown, and other modules may be included as necessary. The function of each part is the same as the function of each part in the device 17.

  FIG. 20 is a diagram illustrating a flow of processing executed by the device monitoring side. When the device that monitors the device 17 is described as the PC 10, the process starts in Step 2000. In Step 2010, the PC 10 transmits a Renew request to the device 17, and in Step 2020, a response is received from the device 17. Receive. In step 2030, it is determined whether or not there is a power saving state transition notification.

  Thereafter, in step 2050, it is determined whether or not there is a power saving state cancellation notification. Determine whether. If there is a response, it is a power saving state, so the process returns to step 2040. If there is no response, the process proceeds to step 2080, where it is determined that the device 17 is abnormal and monitoring of the device 17 is stopped.

  On the other hand, if there is no power saving state transition notification in step 2030, or if there is a power saving state release notification in step 2050, the process proceeds to step 2090, sleeps for a certain time, and waits until a Renew request is transmitted in step 2010. Note that when the monitoring of the device 17 is stopped, the processing ends in step 2100.

  Next, a second embodiment will be described. FIG. 21 is a diagram illustrating a configuration example of a network system according to the second embodiment.

  In the figure, a device 17 is connected to a user terminal 120a and a user terminal 120b via a network 140 such as a LAN (Local Area Network). The device 17 is connected to user terminals 120 c and 120 d connected to a network 150 such as a LAN via a router 130. That is, the user terminals 120a and 120b belong to the same segment (same network) as the device 17, and the user terminals 120c and 120d belong to a different segment (different network) from the device 17. The user terminal 120a and the user terminal 120b are also referred to as a local terminal 120a and a local terminal 120b, respectively, and the user terminal 120c and the user terminal 120d are also referred to as a remote terminal 120c and a remote terminal 120d, respectively. “Local” means the same segment as the device 17, and “Remote” means a segment different from the device 17. Further, when the user terminals 120a, 120b, 120c, and 120d are not distinguished, they are simply referred to as “user terminals 120”. The network 140 and the network 150 may be wired or wireless.

  The user terminal 120 is a personal terminal used by the user, and is not limited to a specific device as long as it can install and execute a software program and has a communication function. Specific examples of the user terminal 120 include an information processing apparatus such as a desktop PC (Personal Computer), a notebook PC, a PDA (Personal Digital Assistance), or a mobile phone. In the present embodiment, each user terminal 120 is installed with an application program called a widget 121.

  In recent years, easy application programs called widgets or gadgets have been distributed. In the present embodiment, these application programs are called widgets 121 in the sense of application programs that can be easily installed and used (that is, not limited in terms of technical significance). In the present embodiment, the widget 121 is common in that a predetermined service (for example, a series of processing flows such as a workflow) is provided to the user by using the function of the device 17 remotely. A typical or typical process executed by the widget 121 is to cause the device 17 to execute scanning and to store the scanned image data in the user terminal 120. Note that the processing procedures (functions implemented in each widget 121) executed by each widget 121 may be different. Each widget 121 is arbitrarily activated on the user terminal 121. Therefore, the list of widgets 121 activated in the network system is extremely fluid.

  FIG. 22 is a diagram illustrating a software configuration and a hardware configuration of a device according to the second embodiment. In FIG. 22, the same parts as those in FIG.

  In the second embodiment, the device 17 has a provider application 25. The provider application 25 is an application program that executes processing for causing the device 17 to cooperate with the widget 121. For example, the provider application 25 controls processing for causing the device 17 to execute processing (such as scanning) that the widget 121 requests from the device 17. In order to realize cooperation with the widget 121, the provider application 25 searches for the provider application 25 activated on the network 140 or the network 150. Such search processing will be described.

  FIG. 23 is a sequence diagram for explaining the processing procedure of the widget search processing by the provider application.

  When the device 17 is activated, the provider application 25 clears the storage area for storing the list information of the widget 121 (hereinafter referred to as “widget list information storage unit”) in the RAM 65 (S110).

  Thereafter, the provider application 25 receives a request for registration of identification information of each remote terminal 120 from each of the remote terminals 120c and 120d (hereinafter, simply referred to as “remote terminal 120” if they are not distinguished from each other) (S120, S140). The provider application 25 records the received identification information in the RAM 65 (S130, S150). The identification information may be any information as long as it can identify each remote terminal 120 in network communication, such as an IP address or a host name. In this embodiment, an example in which an IP address is adopted as the identification information will be described.

  After step S150, the device 17 is in an operation waiting state. Thereafter, when the execution instruction of the provider application 25 is input by the user via the operation panel (S160), the provider application 25 reads (acquires) the IP address registered in the RAM 65 (S170). Subsequently, the provider application 25 clears the contents of the widget list information storage unit (S180). The clearing of the widget list information storage unit in step S180 corresponds to the initialization process before executing the search. That is, step S160 and subsequent steps are executed each time the provider application 25 is selected as an execution target while the device 17 is activated. Therefore, when the provider application 25 is selected as an execution target after the second time, the previous search result remains. This is because a correct search result cannot be displayed for a search to be executed in the future.

  Subsequently, the provider application 25 sends a search request by unicast to each acquired IP address (S190, S200). Subsequently, the provider application 25 sends a multicast search request onto the network 140, which is the same segment as the device 17 (S210, S220).

  The widget 121 activated in the user terminal 120 that has received the search request returns response information in response to the search request. The response information includes the user ID of the logged-in user, identification information (IP address) of the user terminal 120, widget attribute information, and the like. The provider application 25 receives response information for a search request by unicast or multicast, and records it in the widget list information storage unit. The provider application 25 displays the list screen of the widget 121 on the operation panel based on the response information recorded in the widget list information storage unit. The user can use the widget 121 by selecting a desired widget 121 on the list screen displayed on the list screen.

  As described above, the provider application 25 searches for the widget 121 that exists on the same segment as the device 17 using multicast, and uses unicast for the widget 121 that exists on a different segment from the device 17. Search. This is because a multicast search request does not reach another segment.

  However, in order to use unicast, the provider application 25 needs to know the IP address of the unicast destination in advance. Therefore, at least the widget 121 existing on a different segment from the device 17 periodically transmits a registration request for its own IP address (hereinafter referred to as “search destination registration request”) to the provider application 25. Steps S120 and S140 in FIG. 23 correspond to a search destination registration request. Note that the search destination registration request is periodically transmitted because the search destination registration request also has a valid period. That is, for the IP address recorded in the RAM 65 in response to the search destination registration request, the provider application 25 deletes the IP address from the RAM 65 when the valid period specified in the search destination registration request has elapsed.

  Therefore, the device 17 periodically receives a search destination registration request. The timing of the search destination registration request differs for each widget 121. In addition, a large number of widgets 121 may be activated on the network.

  If it does so, possibility that the apparatus 17 will return from a power saving state will increase, and it will become impossible to aim at a power saving appropriately.

  Therefore, in the second embodiment, the provider application 25 avoids shortening of the power saving state due to the search destination registration request by the same method as in the first embodiment.

  That is, when receiving the search destination registration request, the provider application 25 extends the valid period specified in the search destination registration request and extends the valid period when the device 17 is about to enter the power saving state. Is returned to the widget 121. The widget 121 determines the timing for transmitting the next search destination registration request based on the extended effective period.

  Further, the provider application 25 may notify each widget 121 of the transition to the power saving state or the return from the power saving state. In this case, the widget 121 stops transmission of the search destination registration request from the time when the notification of transition to the power saving state is received to the time when the widget 121 returns from the power saving state (that is, while the device 17 is in the power saving state). .

  Further, the provider application 25 may adjust the search destination registration request from each widget 121 so that they are at the same time. The adjustment method may be the same as in the first embodiment. That is, the provider application 25 determines the timing of the next search destination registration request by the widget 121 based on the validity period of the search destination registration request from a certain widget 121, and determines the other widget based on the determination result. The validity period of the search destination registration request from 121 is changed. The provider application 25 returns the validity period changed for each widget 121 to each widget 121. When the effective period is changed, the next search destination registration request from each widget 121 may be adjusted to be slightly shifted as in the first embodiment.

  By adjusting the valid period as described above by the provider application 121, it is possible to reduce the number of times the search destination registration request is received or to centralize the reception timing. As a result, the inconvenience that the period of the power saving state of the device 17 is shortened by the search destination registration request can be appropriately suppressed.

  Although the present invention has been described with the embodiments, the present invention is not limited to the above-described embodiments, and other embodiments, additions, changes, deletions, and the like may occur to those skilled in the art. It can be changed within the range that can be done, and any embodiment is included in the scope of the present invention as long as the effects of the present invention are exhibited. Therefore, the present invention can be provided as a control device, an image forming apparatus including the control device, and a program for realizing the function of the control device. This program can be provided by being stored in a recording medium such as an FD, MD, SD card, CD-ROM, or DVD-ROM.

10-16 PC
17 Device 20 Printer application 20a Application overall control unit 20b Application communication unit 20c Event detection unit 21 Copy application 22 Fax application 23 Scanner application 24 Network application 25 Provider application 30 OS / Kernel
31 System control unit 32 Memory control unit 33 Engine control unit 34 Fax control unit 35 Operation control unit 36 Distribution control unit 37 Network control unit 37a Network overall control unit 37b Network communication unit 37c HTTP control unit 37d WS-Eventing processing unit 37e Protocol control Unit 37f event management unit 38 security control unit 39 power supply management unit 39a overall power supply control unit 39b power supply communication unit 39c hardware management unit 40 API
50 SOAP / XML processing unit 60 Secure device 61 HDD
62 NVRAM
63 CPU
64 ROM
65 RAM
66 Network I / F
67 External device I / F
68 GSTN I / F
70 Subscriber
80 Overall Control Unit 81 HTTP Control Unit 82 Network Control Unit 83 WS-Eventing Processing Unit 84 Event Management Unit 85 SOAP / XML Processing Units 120a, 120b, 120c, 120d User Terminal 121 Widget 130 Router 140, 150 Network

JP 2007-290178 A

Claims (15)

A control device that accepts an event monitoring request from an external device and is used in a device that notifies the event when an event occurs, and controls event monitoring,
In response to receiving an event monitoring request having a valid period from the external device, a determination unit that checks a power state of each device in the device and determines whether the device shifts to a power saving state. When,
If it is determined that the transition and transmits a request that is needed return from the power saving state periodically to the control device, wherein within a period of said request cycle from a device other than the external device A control device comprising: a notification unit that returns a response obtained by extending the valid period to an external device, and transmits a remonitoring request based on the extended valid period.   The notifying unit adjusts each valid period so that the reception times of the re-monitoring requests transmitted from the plurality of external devices are all the same time, and sends a response having each adjusted valid period to each external device. The control device according to claim 1 which returns.   The notifying unit adjusts each valid period so that reception times of the re-monitoring requests transmitted from a plurality of the external devices have a deviation within a predetermined period, and each response having each adjusted valid period is sent. The control device according to claim 1, which is returned to an external device.   The control device according to any one of claims 1 to 3, wherein a WS-Eventing protocol is used for receiving the event monitoring request and the remonitoring request, transmitting the response, and notifying the event.   The notification means notifies the external device of a power saving state transition event in response to the transition to the power saving state, and prevents the event monitoring request from being transmitted from the external device. The control device according to any one of the above.   The control device according to claim 5, wherein, in response to returning from the power saving state, the notification unit notifies the external device of a power saving state release event and transmits the event monitoring request.   An image processing apparatus comprising the control apparatus according to claim 1 and capable of shifting to a power saving state in which communication with an external apparatus is performed. A method for receiving event monitoring requests from an external device and controlling event monitoring by a control device used in a device that notifies the event when an event occurs,
In response to receiving an event monitoring request having a valid period from the external device, checking a power state of each device in the device and determining whether the device shifts to a power saving state; ,
If it is determined that the transition and transmits a request that is needed return from the power saving state periodically to the control device, wherein within a period of said request cycle from a device other than the external device Returning a response obtained by extending the valid period to an external device, and transmitting a remonitoring request based on the extended valid period.   In the transmitting step, each effective period is adjusted so that the reception times of the remonitoring requests transmitted from a plurality of the external devices are all the same time, and a response having each adjusted effective period is sent to each external device. The control method according to claim 8, wherein   In the transmitting step, each valid period is adjusted so that reception times of the re-monitoring requests transmitted from the plurality of external devices have a deviation within a predetermined period, and a response having each adjusted valid period is received. The control method according to claim 8, wherein the control method is returned to each external device.   The WS-Eventing protocol is used for reception of the event monitoring request and the remonitoring request, transmission of the response, and notification of the event, according to any one of claims 8 to 10. Control method.   12. The method according to claim 8, further comprising: notifying the external device of a power saving state transition event so that the event monitoring request is not transmitted from the external device in response to the transition to the power saving state. The control method according to claim 1.   13. The control method according to claim 12, further comprising a step of notifying the external device of a power saving state cancellation event and transmitting the event monitoring request in response to returning from the power saving state.   14. The method according to claim 8, further comprising: detecting an abnormality of the device; and causing the external device to stop event monitoring by not returning a response to an inquiry from the external device. The control method described in 1.   A computer-readable program for executing the control method according to any one of claims 8 to 14.

Images