U.S. patent application number 13/730098 was filed with the patent office on 2013-07-11 for processing device.
The applicant listed for this patent is Ryo IWASAKI, Yoshifumi Kawai, Hiroshi Maeda, Daigo Uchiyama, Reiji Yukumoto. Invention is credited to Ryo IWASAKI, Yoshifumi Kawai, Hiroshi Maeda, Daigo Uchiyama, Reiji Yukumoto.
Application Number | 20130179708 13/730098 |
Document ID | / |
Family ID | 48722717 |
Filed Date | 2013-07-11 |
United States Patent
Application |
20130179708 |
Kind Code |
A1 |
IWASAKI; Ryo ; et
al. |
July 11, 2013 |
PROCESSING DEVICE
Abstract
A processing device includes a plurality of input units
configured to input a process request; a plurality of processing
units configured to execute a process corresponding to the process
request input by the plurality of input units; a power control unit
configured to transfer the processing device into a power saving
state and to transfer the processing device back to a regular state
from the power saving state; and an operation suppression control
unit configured to send an operation suppression request to the
plurality of input units and the plurality of processing units
before the power control unit transfers the processing device into
the power saving state, and to send an operation suppression
release request to the plurality of input units and the plurality
of processing units when the power control unit transfers the
processing device back to the regular state from the power saving
state.
Inventors: |
IWASAKI; Ryo; (Kanagawa,
JP) ; Yukumoto; Reiji; (Kanagawa, JP) ; Kawai;
Yoshifumi; (Kanagawa, JP) ; Maeda; Hiroshi;
(Kanagawa, JP) ; Uchiyama; Daigo; (Kanagawa,
JP) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
IWASAKI; Ryo
Yukumoto; Reiji
Kawai; Yoshifumi
Maeda; Hiroshi
Uchiyama; Daigo |
Kanagawa
Kanagawa
Kanagawa
Kanagawa
Kanagawa |
|
JP
JP
JP
JP
JP |
|
|
Family ID: |
48722717 |
Appl. No.: |
13/730098 |
Filed: |
December 28, 2012 |
Current U.S.
Class: |
713/320 |
Current CPC
Class: |
G06F 1/3234 20130101;
G06F 1/3203 20130101 |
Class at
Publication: |
713/320 |
International
Class: |
G06F 1/32 20060101
G06F001/32 |
Foreign Application Data
Date |
Code |
Application Number |
Jan 5, 2012 |
JP |
2012-000761 |
Claims
1. A processing device comprising: a plurality of input units
configured to input a process request; a plurality of processing
units configured to execute a process corresponding to the process
request input by the plurality of input units; a power control unit
configured to transfer the processing device into a power saving
state and to transfer the processing device back to a regular state
from the power saving state; and an operation suppression control
unit configured to send an operation suppression request to the
plurality of input units and the plurality of processing units
before the power control unit transfers the processing device into
the power saving state, and to send an operation suppression
release request to the plurality of input units and the plurality
of processing units when the power control unit transfers the
processing device back to the regular state from the power saving
state.
2. The processing device according to claim 1, wherein the
operation suppression control unit includes a request unit
configured to request the plurality of input units and the
plurality of processing units to end a process for which a process
request is received before the operation suppression request is
received, and request the plurality of input units and the
plurality of processing units to cancel a process for which a
process request is received after the operation suppression request
is received.
3. The processing device according to claim 2, wherein the
plurality of input units and the plurality of processing units
respectively include a response unit configured to send a response
of operation suppression to the operation suppression control unit
after ending all processes for which a process request is received
before the operation suppression request is received from the
operation suppression control unit, when the operation suppression
request is received from the operation suppression control
unit.
4. The processing device according to claim 1, wherein the
operation suppression control unit includes a request unit
configured to send the operation suppression request to the
plurality of input units and the plurality of processing units in
an order that is stored in advance.
5. The processing device according to claim 1, wherein the
operation suppression control unit includes a request unit
configured to send the operation suppression release request to the
plurality of input units and the plurality of processing units in
an order that is stored in advance.
6. The processing device according to claim 1, wherein the
operation suppression control unit includes a request unit
configured to send the operation suppression request to the
plurality of input units and the plurality of processing units
specified in advance.
7. The processing device according to claim 1, wherein the
plurality of input units and the plurality of processing units
respectively include a receiving unit configured to receive a
process request for a process specified in advance, in an operation
suppression state after the operation suppression request is
received from the operation suppression control unit.
8. The processing device according to claim 1, wherein the
plurality of input units and the plurality of processing units
respectively include a receiving unit configured to receive a
process request for a process in an operation suppression state
after the operation suppression request is received from the
operation suppression control unit, accumulate the process request
that has been received, and execute the process corresponding to
the process request that has been accumulated, when the operation
suppression release request is received from the operation
suppression control unit.
9. The processing device according to claim 7, wherein the
plurality of input units and the plurality of processing units
respectively include a control unit configured not to accumulate
same process requests in duplicate, with regard to process requests
received during the operation suppression state.
10. The processing device according to claim 2, wherein the
plurality of input units and the plurality of processing units
respectively include a cancel unit configured to determine whether
a process for which a process request is received before the
operation suppression request is received can be cancelled and
cancel a process that is determined to be possible to cancel, when
the operation suppression request is received from the operation
suppression control unit.
11. A method performed by a processing device including a plurality
of input units configured to input a process request and a
plurality of processing units configured to execute a process
corresponding to the process request input by the plurality of
input units, the method comprising: transferring the processing
device into a power saving state and transferring the processing
device back to a regular state from the power saving state; sending
an operation suppression request to the plurality of input units
and the plurality of processing units before the processing device
is transferred into the power saving state; and sending an
operation suppression release request to the plurality of input
units and the plurality of processing units when the processing
device is transferred back to the regular state from the power
saving state.
12. The method according to claim 11, wherein the sending of the
operation suppression request includes requesting the plurality of
input units and the plurality of processing units to end a process
for which a process request is received before the operation
suppression request is received, and requesting the plurality of
input units and the plurality of processing units to cancel a
process for which a process request is received after the operation
suppression request is received.
13. The method according to claim 12, further comprising: sending,
by the plurality of input units and the plurality of processing
units, a response of operation suppression after ending all
processes for which a process request is received before the
operation suppression request is received, when the operation
suppression request is received.
14. The method according to claim 11, wherein the sending of the
operation suppression request includes sending the operation
suppression request to the plurality of input units and the
plurality of processing units in an order that is stored in
advance.
15. The method according to claim 11, wherein the sending of the
operation suppression release request includes sending the
operation suppression release request to the plurality of input
units and the plurality of processing units in an order that is
stored in advance.
16. The method according to claim 11, wherein the sending of the
operation suppression request includes sending the operation
suppression request to the plurality of input units and the
plurality of processing units specified in advance.
17. The method according to claim 11, further comprising:
receiving, by the plurality of input units and the plurality of
processing units, a process request for a process specified in
advance, in an operation suppression state after the operation
suppression request is received.
18. The method according to claim 11, further comprising:
receiving, by the plurality of input units and the plurality of
processing units, a process request for a process in an operation
suppression state after the operation suppression request is
received; accumulating, by the plurality of input units and the
plurality of processing units, the process request that has been
received; and executing, by the plurality of input units and the
plurality of processing units, the process corresponding to the
process request that has been accumulated, when the operation
suppression release request is received.
19. The method according to claim 17, further comprising:
performing control, by the plurality of input units and the
plurality of processing units, not to accumulate same process
requests in duplicate with regard to process requests received
during the operation suppression state.
20. The method according to claim 12, further comprising:
determining, by the plurality of input units and the plurality of
processing units, whether a process for which a process request is
received before the operation suppression request is received can
be cancelled and cancelling a process that is determined to be
possible to cancel, when the operation suppression request is
received.
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The present invention relates to a processing device of a
projector, a facsimile machine, a scanner, a printer, a copier, and
a multifunction peripheral, etc.
[0003] 2. Description of the Related Art
[0004] In recent years, a processing device of a projector, a
facsimile machine, a scanner, a printer, a copier, and a
multifunction peripheral, etc., has a function for transferring to
an energy saving state (also referred to as a "power saving state")
that is a standby state, for the purpose of reducing power
consumption.
[0005] Conventionally, there is a processing device that displays a
message saying that the device will transfer to a standby state
after completing a job being executed, when a standby transfer
request is received while executing a function (see, for example,
patent document 1).
[0006] However, by the standby transfer method, the conventional
processing device cannot transfer to a standby state when a request
to use the function is received during the process of transferring
to the standby state. In this case, it takes time to transfer to
the standby state.
[0007] Furthermore, in the standby state, power consumption is
reduced by stopping unnecessary power supply to the device.
Therefore, when an attempt is made to transfer to the standby state
while executing a function, a failure may occur. [0008] Patent
Document 1: Japanese Laid-Open Patent Publication No.
2000-261515
SUMMARY OF THE INVENTION
[0009] The present invention provides a processing device, in which
one or more of the above-described disadvantages are
eliminated.
[0010] A preferred embodiment of the present invention provides a
processing device, which is capable of preventing failures caused
when the processing device transfers to a power saving state while
a function is being executed, and capable of quickly transferring
to a power saving state without receiving new requests while
transferring to a power saving state.
[0011] According to an aspect of the present invention, there is
provided a processing device including a plurality of input units
configured to input a process request; a plurality of processing
units configured to execute a process corresponding to the process
request input by the plurality of input units; a power control unit
configured to transfer the processing device into a power saving
state and to transfer the processing device back to a regular state
from the power saving state; and an operation suppression control
unit configured to send an operation suppression request to the
plurality of input units and the plurality of processing units
before the power control unit transfers the processing device into
the power saving state, and to send an operation suppression
release request to the plurality of input units and the plurality
of processing units when the power control unit transfers the
processing device back to the regular state from the power saving
state.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Other objects, features and advantages of the present
invention will become more apparent from the following detailed
description when read in conjunction with the accompanying
drawings, in which:
[0013] FIG. 1 is a block diagram illustrating the internal
configuration of a projector according to an embodiment of the
present invention;
[0014] FIG. 2 illustrates a configuration of a projection system
according to an embodiment of the present invention;
[0015] FIG. 3 illustrates an example of a table indicating the
respective power states of the projector shown in FIG. 1 and
contents of requests received in the respective power states at the
projector;
[0016] FIG. 4 is a sequence diagram illustrating a process
performed by the projector shown in FIG. 1 when applying operation
suppression;
[0017] FIG. 5 is a flowchart illustrating an operation suppression
process performed by the operation suppression control unit shown
in FIG. 1;
[0018] FIG. 6 is a flowchart illustrating an operation process of
modules that have received an operation suppression request from
the operation suppression control unit shown in FIG. 1;
[0019] FIG. 7 is a sequence diagram illustrating a process by the
projector shown in FIG. 1 when operation suppression is
released;
[0020] FIG. 8 is a flowchart illustrating a process when releasing
operation suppression performed by the operation suppression
control unit shown in FIG. 1;
[0021] FIG. 9 is a transition diagram illustrating states of the
projector shown in FIG. 1;
[0022] FIG. 10 is a transition diagram illustrating states of
modules of the projector shown in FIG. 1 that are operation
suppression targets;
[0023] FIG. 11 is a flowchart illustrating a process performed when
the modules of the projector that are operation suppression targets
receive a request;
[0024] FIG. 12 illustrates an example of a table held by the
operation suppression control unit shown in FIG. 1, indicating
whether a module is an operation suppression target;
[0025] FIG. 13 illustrates an example of a table held by the
modules of the projector shown in FIG. 1 that are operation
suppression targets, indicating process contents to be executed
when an operation suppression request is received;
[0026] FIG. 14 illustrates a table held by the operation
suppression control unit shown in FIG. 1, indicating whether
modules are operation suppression targets, the order of
implementing operation suppression, and the order of releasing
operation suppression;
[0027] FIG. 15 is a sequence diagram illustrating a process
performed by the projector shown in FIG. 1 when applying operation
suppression based on the table of FIG. 14;
[0028] FIG. 16 illustrates an example of a table held by the
operation suppression control unit shown in FIG. 1 indicating
whether modules are operation suppression targets, in which
information pertinent to "active standby" and information pertinent
to "regular standby" are held separately;
[0029] FIG. 17 illustrates an example of a table held by a module
shown in FIG. 1 that is an operation suppression target, indicating
whether functions can be executed in an active standby state and a
regular standby state;
[0030] FIG. 18 is a sequence diagram illustrating a process when
operation suppression is performed in an active standby state by
the projector shown in FIG. 1;
[0031] FIG. 19 is a flowchart illustrating a process performed when
modules of the projector shown in FIG. 1 that are operation
suppression targets receive a process request;
[0032] FIG. 20 is a flowchart illustrating another example of a
process performed when modules of the projector shown in FIG. 1
that are operation suppression targets receive a process
request;
[0033] FIG. 21 illustrates an example of a table held by the module
of the projector shown in FIG. 1 that is an operation suppression
target, indicating how to process each request during operation
suppression;
[0034] FIG. 22 is a flowchart of a process of executing all
requests, which have been received during operation suppression, at
the time when operation suppression is released, at the module of
the projector shown in FIG. 1 that is an operation suppression
target;
[0035] FIG. 23 is a flowchart of a process performed by the
projector shown in FIG. 1, for removing an old request when the
same request is received when accumulating requests in a queue;
[0036] FIG. 24 illustrates a configuration of a projection system
according to another embodiment of the present invention;
[0037] FIG. 25 is a block diagram of a functional configuration
inside the application controller shown in FIG. 24;
[0038] FIG. 26 is a block diagram of the functional configuration
inside the I/O controller shown in FIG. 24;
[0039] FIG. 27 illustrates an example of a table held by the I/O
job management unit shown in FIG. 25, including information
indicating whether it is possible to cancel message types;
[0040] FIG. 28 illustrates an example of a table held by the I/O
job management unit shown in FIG. 25, for managing jobs;
[0041] FIG. 29 illustrates an example of a thread state management
table held by the communication state management unit shown in FIG.
26;
[0042] FIG. 30 is a sequence diagram illustrating a process
performed until generating a job, performed by the projector shown
in FIG. 24;
[0043] FIG. 31 is a sequence diagram illustrating a process
performed until deleting a job performed by the projector shown in
FIG. 24;
[0044] FIG. 32 is a sequence diagram illustrating a process
performed until deletion of a job by cancelling the job, performed
by the projector shown in FIG. 24;
[0045] FIG. 33 is a flowchart illustrating a process performed
until the power is turned off, performed by the I/O control unit
and the I/O job management unit shown in FIG. 25;
[0046] FIG. 34 is a flowchart illustrating a cancel process
performed by the communication control unit and the communication
state management unit shown in FIG. 26;
[0047] FIG. 35 illustrates an example of a table stored and held by
the I/O job management unit shown in FIG. 25, indicating whether
cancelling is possible in the respective job states; and
[0048] FIG. 36 illustrates an example of a table stored and held by
the communication control unit shown in FIG. 26, indicating whether
cancelling is possible according to the purpose and state of the
communication thread.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0049] A description is given, with reference to the accompanying
drawings, of embodiments of the present invention.
[0050] FIG. 2 illustrates a configuration of a projection system
according to an embodiment of the present invention.
[0051] In the projection system, a plurality of personal computers
including a PC 2 are connected to a projector 1 that is an example
of a processing device via a wired or wireless network 3. The PC 2
and the projector 1 can perform data communication with each other.
PCs other than the PC 2 are not shown.
[0052] The projector 1 is a video projection device (also referred
to as an "image projection device"), and projects videos based on
projection data input from the PC 2 on a projection surface such as
a screen.
[0053] The PC 2 transmits video data to the projector 1.
[0054] In the projection system having the above configuration,
plural PCs including the PC 2 share the projector 1 and can cause
the projector 1 to project videos that are respectively held by the
PCs including the PC 2.
[0055] The projection system of FIG. 2 is one example; in another
example, another video output device or an external storage may be
further connected to the projection system.
[0056] When a request is made to transfer the power state of the
projector 1, from an on state to a standby state, while a process
is being executed inside the projector 1, and the power state is
transferred to a standby state while the process is being executed,
a failure may occur the next time the projector is started up.
[0057] A standby state is a power saving state for reducing the
power consumption by stopping the power supply to part of the
inside of the projector 1.
[0058] The projector 1 has two types of standby states, i.e.,
"active standby" and "regular standby". These states are described
in detail below.
[0059] The projector 1 according to the present embodiment performs
the following operation suppression before transferring to a
standby state, in order to prevent the projector 1 from
transferring to a standby state while a process is being
executed.
Operation Suppression
[0060] 1. With regard to a process request that is received before
receiving a request to transfer to a standby state, the
corresponding process is ended. 2. A process request received after
receiving a request to transfer to a standby state is not
executed.
[0061] Accordingly, the projector 1 according to the present
embodiment can be prevented from transferring to a standby state
while a process is being executed, by performing operation
suppression on a module for receiving requests from outside, when
transferring to a standby state.
[0062] As methods for the user to give requests to the projector 1,
the user may input user operation by using keys provided on the
main unit of the projector 1 or a remote controller (not shown in
FIG. 2), or input user operation by operating the PC 2 via the
network 3.
[0063] In the following description, a request may be received by
either of the above methods; however, a request may be received
even if only one of the above methods can be used.
[0064] Next, a description is given of the internal configuration
of the projector 1, with reference to FIG. 1.
[0065] FIG. 1 is a block diagram illustrating the internal
configuration of the projector 1 shown in FIG. 2.
[0066] The projector 1 includes an operation unit 4, a control unit
5, and a projection unit 6.
[0067] The operation unit 4 is used by the user for inputting
various kinds of operation information to the projector 1, and the
user may directly input a standby request to the projector 1.
[0068] The projection unit 6 projects images such as still images
and video images on a projection surface such as a screen, based on
image data (also referred to as "video data") sent from the PC
2.
[0069] The control unit 5 is realized by a microcomputer such as a
ROM and a RAM, and includes various function units such as a power
control unit 11, a user operation receiving unit 12, a network
communication unit 13, an operation suppression control unit 14,
and function executing units 15 through 17, which are connected to
each other by a system bus 18.
[0070] In the present embodiment, there are three function
executing units 15 through 17; however, the process described below
may be performed with more than three function executing units.
[0071] The system bus 18 connects the power control unit 11, the
user operation receiving unit 12, the network communication unit
13, the operation suppression control unit 14, and the function
executing units 15 through 17. The system bus 18 is a path through
which data communication can be performed between these units.
[0072] The power control unit 11 is a module for switching the
power state by controlling the power supplied from a power source
(not shown) of the projector 1. The power states include plural
types of states such as a regular state and a standby state, which
are described in detail below.
[0073] The power control unit 11 has a function of controlling the
projector 1 to transfer to a power saving state and for controlling
the projector 1 to return to a regular state from the power saving
state.
[0074] The user operation receiving unit 12 is a module for
receiving a request that is sent from the user by directly
operating the projector 1. The process requested by the user and
received by the user operation receiving unit 12 is performed by
the function executing units 15 through 17.
[0075] The network communication unit 13 is a module for receiving
a request sent from the PC 2 via the network 3. The process of the
request received by the network communication unit 13 is also
performed by the function executing units 15 through 17, similar to
the case of the user operation receiving unit 12.
[0076] The user operation receiving unit 12 and the network
communication unit 13 function as plural input units for inputting
process requests.
[0077] When a request for operation suppression is received from
the operation suppression control unit 14, the user operation
receiving unit 12 and the network communication unit 13 have a
function of ending all processes for which a request is received
before receiving the request for operation suppression, and then
sending a response of operation suppression to the operation
suppression control unit 14. Furthermore, the user operation
receiving unit 12 and the network communication unit 13 have a
function of receiving a request for a process that is specified in
advance, even during an operation suppression state after receiving
the above request for predetermined operation suppression from the
operation suppression control unit 14.
[0078] Furthermore, the user operation receiving unit 12 and the
network communication unit 13 have a function of receiving a
request for a process even during an operation suppression state
after receiving the above request for predetermined operation
suppression from the operation suppression control unit 14,
accumulating the received request for a process, and responding to
the accumulated request for a process when a request to release the
operation suppression is received from the operation suppression
control unit 14. The user operation receiving unit 12 and the
network communication unit 13 have a function of not accumulating
the same process requests in duplicate, with regard to requests for
processes received during the operation suppression state.
[0079] The operation suppression control unit 14 is a module for
requesting operation suppression to a module on which operation
suppression needs to be performed in response to a request for
operation suppression from the power control unit 11. When a
response, indicating that operation suppression is completed, is
received from all modules for which operation suppression has been
requested, the operation suppression control unit 14 sends a
response to the power control unit 11 indicating that the power
state can now be changed as operation suppression has been
completed.
[0080] Before the operation suppression control unit 14 controls
the power control unit 11 to cause the projector 1 to transfer to
the power saving state, the operation suppression control unit 14
has a function of sending a request for predetermined operation
suppression to the user operation receiving unit 12, the network
communication unit 13, and the function executing units 15 through
17. When the operation suppression control unit 14 controls the
power control unit 11 to cause the projector 1 to return from the
power saving state to a regular state, the operation suppression
control unit 14 has a function of implementing control to request
release of operation suppression to the user operation receiving
unit 12, the network communication unit 13, and the function
executing units 15 through 17.
[0081] Furthermore, the operation suppression control unit 14 has a
function of requesting operation suppression to the user operation
receiving unit 12, the network communication unit 13, and the
function executing units 15 through 17, to end a process for which
a request has been received before receiving the request for
predetermined operation suppression. Furthermore, the operation
suppression control unit 14 has a function of requesting operation
suppression to the user operation receiving unit 12, the network
communication unit 13, and the function executing units 15 through
17, to cancel a process for which a request is received after
receiving the request for predetermined operation suppression. The
operation suppression control unit 14 has a function of requesting
predetermined operation suppression to the user operation receiving
unit 12, the network communication unit 13, and the function
executing units 15 through 17 an order that is stored in advance.
The operation suppression control unit 14 has a function of
requesting release of predetermined operation suppression to the
user operation receiving unit 12, the network communication unit
13, and the function executing units 15 through 17 in an order that
is stored in advance. The operation suppression control unit 14 has
a function of requesting predetermined operation suppression to one
or more of the user operation receiving unit 12, the network
communication unit 13, and the function executing units 15 through
17 which are specified in advance.
[0082] The function executing units 15 through 17 are a group of
modules for executing a process in response to a request input to
the projector 1 via the network 3 or by user operation.
[0083] The function executing units 15 through 17 function as
plural processing units for executing a process corresponding to a
process request input with the input unit.
[0084] Next, a description is given of the respective power states
of the projector 1 and contents of requests received in the
respective power states at the projector 1, with reference to FIG.
3.
[0085] FIG. 3 illustrates an example of a table indicating the
respective power states of the projector 1 shown in FIG. 1 and
contents of requests received in the respective power states at the
projector 1.
[0086] For example, the table of FIG. 3 is stored by the operation
suppression control unit 14 shown in FIG. 1, and indicates the
correspondence relationship between the power states of the
projector 1 and the requests received in the respective power
states.
[0087] The power state "ON" means that power is supplied to all
units inside the projector 1 and the projector 1 is regularly
operating. Power is supplied to all units of the projector 1, and
all requests input to the projector 1 can be received.
[0088] The power state "standby" means that power supply to part of
the units inside the projector 1 is stopped. The standby state is a
power saving state in which power supply to the function executing
units 15 through 17 and the projection unit 6 is shut off.
Meanwhile, power is supplied to the power control unit 11. Power is
not supplied to the function executing units 15 through 17.
Therefore, requests other than a request to turn on the power
cannot be received. In order to receive a request to turn on the
power, power is supplied to either one or both of the user
operation receiving unit 12 and the network communication unit
13.
[0089] The power state "OFF" means that the main power supply of
the projector 1 is turned off (the projector 1 is not plugged in).
In this power state, power is not supplied anywhere in the
projector 1, and therefore no requests can be received.
[0090] With regard to the projector 1 according to the present
embodiment, a description is given of a method of performing
operation suppression when the power state transfers from "ON" to
"standby", and a method of releasing operation suppression when the
power state transfers from "standby" to "ON".
[0091] Other than the above three power states, there is also a
power state refereed to as "active standby".
[0092] In the power state of "active standby", power is supplied to
more units compared to the "standby" state, and therefore processes
can be performed for some more requests other than a request for
turning on the power.
[0093] Next, a description is given of a process when operation
suppression is performed by the projector 1.
[0094] FIG. 4 is a sequence diagram illustrating a process
performed by the projector 1 shown in FIG. 1 when applying
operation suppression. In FIG. 4, the steps are indicated as
"S".
[0095] A description is given of a process in which operation
suppression is performed on the modules of the function executing
units 15 and 16 shown in FIG. 1.
[0096] When a request to transfer to standby is received from the
user, the user operation receiving unit 12 shown in FIG. 1 sends a
standby transfer request to the power control unit 11 (step S1 in
FIG. 4).
[0097] Furthermore, although not shown in FIG. 4, when a standby
transfer request is sent form the PC 2 shown in FIG. 2 to the
projector 1 via the network 3, the network communication unit 13
sends a standby transfer request to the power control unit 11.
[0098] Next, the power control unit 11 sends an operation
suppression request for transferring to standby to the operation
suppression control unit 14 (step S2).
[0099] The operation suppression control unit 14 sends an operation
suppression request to modules that need to be subjected to
operation suppression. Here, operation suppression requests are
sent to the function executing units 15 and 16 (step S3).
Operations of the function executing units 15 and 16 that have
received the operation suppression requests are described
below.
[0100] Meanwhile, when the modules of the function executing units
15 and 16, which have received the operation suppression requests,
complete operation suppression for themselves, the function
executing units 15 and 16 report operation suppression completion
indicating that operation suppression has been completed to the
operation suppression control unit 14 (steps S4 and S5).
[0101] Then, when responses indicating operation suppression
completion are received from the function executing units 15 and
16, the operation suppression control unit 14 sends a response
indicating operation suppression completion to the power control
unit 11 (step S6). The power control unit 11 that has received this
response executes a process for transferring the power state to
standby.
[0102] Next, a description is given of a process performed when the
operation suppression control unit 14 shown in FIG. 1 performs
operation suppression.
[0103] FIG. 5 is a flowchart illustrating an operation suppression
process performed by the operation suppression control unit 14
shown in FIG. 1. This process is executed in a power on state of
the projector 1. In FIG. 5, the steps are indicated as "s".
[0104] When an operation suppression request is received from the
power control unit 11 in step S11, the process proceeds to step
S12.
[0105] In step S12, an operation suppression request is sent to all
modules that are operation suppression targets, and the process
proceeds to step S13. In this case, all modules correspond to the
function executing units 15 and 16.
[0106] In step S13, the operation suppression control unit 14 waits
for responses indicating operation suppression completion from all
of the modules to which the operation suppression request has been
sent, and the process proceeds to step S14.
[0107] In step S14, when responses indicating operation suppression
completion are received from all of the modules to which the
operation suppression request has been sent, and the process
proceeds to step S15.
[0108] In step S15, the operation suppression control unit 14
determines whether responses have been received from all modules
that are operation suppression targets. When responses are not
received from all modules (NO in step S15), the process returns to
step S13 to wait for responses indicating operation suppression
completion. When responses are received from all modules (YES
instep S15), the process proceeds to step S16.
[0109] In step S16, the operation suppression control unit 14 sends
a response indicating operation suppression completion to the power
control unit 11, and the process ends.
[0110] Next, a description is given of an operation process of
modules that have received an operation suppression request from
the operation suppression control unit 14 shown in FIG. 1, with
reference to FIG. 6.
[0111] A description is given of a process in which the modules
that have received an operation suppression request are the
function executing units 15 and 16.
[0112] FIG. 6 is a flowchart illustrating an operation process of
modules that have received an operation suppression request from
the operation suppression control unit 14 shown in FIG. 1. In FIG.
6, the steps are indicated as "S".
[0113] The function executing units 15 and 16 respectively execute
the process of steps S21 through S29.
[0114] In step S21, when an operation suppression request is
received form the operation suppression control unit 14, the
process proceeds to step S22.
[0115] In step S22, the state is changed so that no more new
requests are received, and the process proceeds to step S23.
[0116] In step S23, the module determines whether there is a
requested process that is being executed, and when there is an
executed process (YES in step S23), the process proceeds to step
S24, and when there is no executed process (NO in step S23), the
process proceeds to step S27.
[0117] In step S24, the module determines whether to complete the
executed process. When the module determines to complete the
process (YES in step S24), the process proceeds to step S25, and
when the module determines not to complete the process (NO in step
S24), the process proceeds to step S28.
[0118] In step S25, the executed process is completed, and the
process proceeds to step S26.
[0119] Meanwhile, in step S28, the executed process is canceled,
and the process proceeds to step S26.
[0120] The process of step S24 is to determine whether the executed
process takes a long time. When the process does not take a long
time, the process is completed in step S25. When the process takes
a long time, the process is cancelled by cancelling the request in
step S28.
[0121] In step S26, the model determines whether all requests
received before receiving the operation suppression request have
been completed, and when the requests are completed (YES in step
S26), the process proceeds to step S27, and when the requests are
not completed (NO in step S26), the process proceeds to step
S29.
[0122] In step S27, the module sends a response indicating
operation suppression completion to the operation suppression
control unit 14, and the process ends.
[0123] In step S29, the next request is executed, and the process
returns to step S24.
[0124] In step S26, the module determines whether all requests,
which have been received before receiving the operation suppression
request was received, have been executed, and when there are
requests that have not been processed, the module executes the
process of the request received after the completed/cancelled
request (step S29). When there are no unprocessed requests, the
process proceeds to step S27.
[0125] Next, a description is given of a process performed when the
projector 1 releases operation suppression.
[0126] FIG. 7 is a sequence diagram illustrating a process by the
projector 1 shown in FIG. 1 when operation suppression is released.
In FIG. 7, the steps are indicated as "S".
[0127] A description is given of a process of releasing operation
suppression when the function executing units 15 and 16 are in the
operation suppression state.
[0128] When a request to turn on the power is received from the
user, the user operation receiving unit 12 sends a power on request
to the power control unit 11 (step S31).
[0129] Furthermore, although not shown in FIG. 7, when the PC 2
shown in FIG. 2 sends a power on request to the projector 1 via the
network 3, the network communication unit 13 sends a power on
request to the power control unit 11.
[0130] Next, when the process for transferring to the ON power
state is completed, the power control unit 11 sends an operation
suppression release request to the operation suppression control
unit 14 (step S32).
[0131] The operation suppression control unit 14 sends an operation
suppression release request to all modules that are subjected to
operation suppression (step S33). Here, the operation suppression
release request is sent to the function executing units 15 and
16.
[0132] Meanwhile, the function executing units 15 and 16 that have
received the operation suppression release request from the
operation suppression control unit 14 respectively transfer the
states of their own modules to complete releasing operation
suppression, and reports operation suppression release completion
to the operation suppression control unit 14 (steps S34 and S35).
The states of the modules of the function executing units 15 and 16
are described below.
[0133] When a response indicating operation suppression release
completion is received from the function executing units 15 and 16,
the operation suppression control unit 14 sends a response
indicating operation suppression release completion to the power
control unit 11 (step S36).
[0134] Next, a description is given of a process when releasing
operation suppression performed by the operation suppression
control unit 14 shown in FIG. 1, with reference to FIG. 8.
[0135] FIG. 8 is a flowchart illustrating a process when releasing
operation suppression performed by the operation suppression
control unit 14 shown in FIG. 1. This process is for releasing the
operation suppression of the function executing units 15 and 16
that are being subjected to operation suppression. This process is
executed when the projector 1 is in a power on state. In FIG. 8,
the steps are indicated as "S".
[0136] In step S41, when an operation suppression release request
is received from the power control unit 11, the process proceeds to
step S42.
[0137] In step S42, an operation suppression release request is
sent to all modules that are operation suppression release targets,
and the process proceeds to step S43. In this case, all modules
correspond to the function executing units 15 and 16.
[0138] In step S43, the operation suppression control unit 14 waits
for responses indicating operation suppression release completion
from all of the modules to which the operation suppression release
request has been sent, and the process proceeds to step S44.
[0139] In step S44, when responses indicating operation suppression
release completion are received from all of the modules to which
the operation suppression release request has been sent, the
process proceeds to step S45.
[0140] In step S45, the operation suppression control unit 14
determines whether responses have been received from all modules
that are operation suppression release targets. When responses are
received from all modules (YES in step S45), the process proceeds
to step S46. When responses are not received from all modules (NO
in step S45), the process returns to step S43.
[0141] In step S46, the operation suppression control unit 14 sends
a response indicating operation suppression release completion to
the power control unit 11, and the process ends.
[0142] Next, a description is given of states of the projector 1
with reference to FIG. 9.
[0143] FIG. 9 is a transition diagram illustrating states of the
projector 1 shown in FIG. 1.
[0144] The operation suppression control unit 14 holds information
indicating that the projector 1 has transferred to the respective
states of 20 through 23 shown in FIG. 9.
[0145] The operation suppression control unit 14 causes the
projector 1 to be in the regular state denoted by 20 when the power
is turned on. When an operation suppression request is received
from the power control unit 11, the operation suppression control
unit 14 causes the projector 1 to transfer to an operation
suppression transferring state denoted by 21.
[0146] Then, when a response indicating operation suppression
completion is received from all modules that are operation
suppression targets (for example, the function executing units 15
and 16), the operation suppression control unit 14 causes the
projector 1 to transfer to an operation suppression state denoted
by 22.
[0147] Next, when an operation suppression release request is
received from the power control unit 11 while the projector 1 is
being subjected to operation suppression, the operation suppression
control unit 14 causes the projector 1 to transfer to an operation
suppression releasing state denoted by 23.
[0148] Then, when a response indicating operation suppression
release completion is received from all modules that are operation
suppression release targets (for example, the function executing
units 15 and 16), the operation suppression control unit 14 causes
the projector 1 to transfer to a regular state denoted by 20.
[0149] Next, a description is given of states of modules of the
projector 1 that are operation suppression targets, with reference
to FIG. 10.
[0150] FIG. 10 is a transition diagram illustrating states of
modules of the projector 1 shown in FIG. 1 that are operation
suppression targets.
[0151] In this example, the modules of that are operation
suppression targets are the function executing units 15 and 16.
[0152] The function executing units 15 and 16 hold information
indicating that the modules themselves have transferred to the
respective states of 30 and 31 shown in FIG. 10.
[0153] When the module is operating regularly in a state where the
power is on, the module maintains the on state denoted by 30. When
an operation suppression request for transferring to a standby
state is received from the operation suppression control unit 14,
the module transfers to a standby state denoted by 31. Furthermore,
when an operation suppression release request is received from the
operation suppression control unit 14 while the module is in the in
the standby state, the module returns to the on state denoted by
30.
[0154] Next, a description is given of a process performed when the
modules that are operation suppression targets receive a process
request.
[0155] FIG. 11 is a flowchart illustrating a process performed when
the modules of the projector 1 that are operation suppression
targets receive a request. In this process, the modules that are
operation suppression targets are the function executing units 15
and 16. In FIG. 11, the steps are indicated as "S".
[0156] When each of the function executing units 15 and 16
(modules) receives a process request in step S51, in step S52, the
module determines whether it is in an on state. When the module is
in an on state (YES in step S51), the process proceeds to step S53.
When the module is not in an on state (NO in step S51), the process
ends.
[0157] In step S53, the module executes a process for which the
request has been received, and the executed process ends.
[0158] In the process of step S52, when the module itself is in an
on state, i.e., in a regular state, the module executes the
requested process (step S53). When the module is not in an on
state, i.e., in an operation suppression state, then nothing is
performed and the process ends.
[0159] Next, with reference to FIG. 12, a description is given of a
table held by the operation suppression control unit 14 shown in
FIG. 1, indicating whether a module is an operation suppression
target.
[0160] Here, a description is given whether the function executing
units 15 through 17 are operation suppression targets.
[0161] FIG. 12 illustrates an example of a table held by the
operation suppression control unit 14 shown in FIG. 1, indicating
whether a module is an operation suppression target.
[0162] The operation suppression control unit 14 stores the table
shown in FIG. 12 in advance, and can thus identify whether the
respective modules of the function executing units 15 through 17,
are operation suppression targets by referring to the stored
table.
[0163] The table shown in FIG. 12 records information expressing
"YES" indicating that the function executing units 15 and 16 are
operation suppression targets and information expressing "NO"
indicating that the function executing unit 17 is not an operation
suppression target.
[0164] Accordingly, the operation suppression control unit 14 can
send an operation suppression request to all modules that are
operation suppression targets.
[0165] Next, with reference to FIG. 13, a description is given of a
table held by the modules that are operation suppression targets
shown in FIG. 1, indicating process contents to be executed when an
operation suppression request is received.
[0166] FIG. 13 illustrates an example of a table held by the
modules of the projector 1 shown in FIG. 1 that are operation
suppression targets, indicating process contents to be executed
when an operation suppression request is received.
[0167] In this example, a description is given of a table held by
the function executing unit 15.
[0168] The function executing unit 15 stores the table shown in
FIG. 13 in advance, and therefore when the module itself receives
an operation suppression request, the function executing unit 15
refers to the table of FIG. 13, and if function A, function C or
function D is being executed, the function executing unit 15
completes the executed function and implements operation
suppression so that subsequent requests are not executed until
operation suppression is released.
[0169] Furthermore, when the module itself receives an operation
suppression request, the function executing unit 15 refers to the
table of FIG. 13, and when function B is being executed, the
function executing unit 15 cancels the executed function B and
implements operation suppression so that subsequent requests are
not executed until operation suppression is released.
[0170] Next, with reference to FIG. 14, a description is given of a
table held by the operation suppression control unit 14 shown in
FIG. 1, indicating whether modules are operation suppression
targets, the order of implementing operation suppression, and the
order of releasing operation suppression.
[0171] In this example, a description is given on whether the user
operation receiving unit 12, the network communication unit 13, and
the function executing units 15 and 16 are operation suppression
targets, and the order of implementing operation suppression and
the order of releasing operation suppression with regard to these
modules.
[0172] FIG. 14 illustrates a table held by the operation
suppression control unit 14 shown in FIG. 1, indicating whether
modules are operation suppression targets, the order of
implementing operation suppression, and the order of releasing
operation suppression.
[0173] There may be cases where the modules to be subjected to
operation suppression are dependent on each other, and unless a
certain module is subjected to operation suppression, it may not be
possible to perform operation suppression on another module.
[0174] In such a case, in the table held by the operation
suppression control unit 14 indicating whether modules are
operation suppression targets, information indicating "the order of
operation suppression" is added.
[0175] The operation suppression control unit 14 simultaneously
sends operation suppression requests to modules having the same
value of "the order of operation suppression". When a response
indicating operation suppression completion is returned from all
modules to which the operation suppression requests have been sent,
the operation suppression control unit 14 sends an operation
suppression request to the module of the next order.
[0176] For example, according to the order of operation suppression
indicated in the table of FIG. 14, the operation suppression
control unit 14 first simultaneously sends operation suppression
requests to the user operation receiving unit 12 and the network
communication unit 13, and when responses indicating operation
suppression completion are returned from the user operation
receiving unit 12 and the network communication unit 13, the
operation suppression control unit 14 requests operation
suppression to the function executing unit 15 of the next
order.
[0177] Furthermore, when it is necessary to follow an order when
releasing operation suppression, information of "the order of
releasing operation suppression" is also added to the table held by
the operation suppression control unit 14.
[0178] The operation suppression control unit 14 simultaneously
sends operation suppression release requests to modules having the
same value of "the order of releasing operation suppression". When
a response indicating operation suppression release completion is
returned from all modules to which the operation suppression
release requests have been sent, the operation suppression control
unit 14 sends an operation suppression release request to the
module of the next order.
[0179] For example, according to the order of operation suppression
release indicated in the table of FIG. 14, the operation
suppression control unit 14 first sends an operation suppression
release request to the function executing unit 15, and when a
response indicating operation suppression release completion is
returned from the function executing unit 15, an operation
suppression release request is sent to the network communication
unit 13 of the next order, and when a response indicating operation
suppression release completion is returned from the network
communication unit 13, an operation suppression release request is
sent to the user operation receiving unit 12 of the next order.
[0180] Next, with reference to FIG. 15, a description is given of a
process performed by the projector 1 when applying operation
suppression based on the table of FIG. 14.
[0181] FIG. 15 is a sequence diagram illustrating a process
performed by the projector 1 shown in FIG. 1 when applying
operation suppression based on the table of FIG. 14. In FIG. 15,
the steps are indicated as "S".
[0182] This process is executed when the projector 1 is in a power
on state.
[0183] When a request to transfer to a standby state is received
from the user, the user operation receiving unit 12 shown in FIG. 1
sends a standby transfer request to the power control unit 11 (step
S61 in FIG. 15).
[0184] Furthermore, although not shown in FIG. 15, when the PC 2
shown in FIG. 2 sends a standby transfer request to the projector 1
via the network 3, the network communication unit 13 sends a
standby transfer request to the power control unit 11.
[0185] Next, the power control unit 11 sends an operation
suppression request for transferring to the standby state to the
operation suppression control unit 14 (step S62).
[0186] The operation suppression control unit 14 refers to the
table of FIG. 14, and sends an operation suppression request to the
modules that need to be subjected to operation suppression. In this
example, an operation suppression request is sent to the user
operation receiving unit 12, the network communication unit 13, and
the function executing unit 15. However, based on the order of
operation suppression, first, an operation suppression request is
simultaneously sent to the user operation receiving unit 12 and the
network communication unit 13 (step S63).
[0187] Meanwhile, when the modules of the user operation receiving
unit 12 and the network communication unit 13, which have received
the operation suppression requests, complete operation suppression
for themselves, the modules of the user operation receiving unit 12
and the network communication unit 13 report operation suppression
completion indicating that operation suppression has been completed
to the operation suppression control unit 14 (steps S64 and
S65).
[0188] Then, when responses indicating operation suppression
completion are received from the user operation receiving unit 12
and the network communication unit 13, the operation suppression
control unit 14 sends an operation suppression request to the
function executing unit 15 of the next order of operation
suppression (step S66). When the module of the function executing
unit 15 that has received the operation suppression request
completes operation suppression for itself, the function executing
unit 15 reports operation suppression completion indicating that
operation suppression has been completed to the operation
suppression control unit 14 (step S67).
[0189] When a response indicating operation suppression completion
is received from the function executing unit 15, the operation
suppression control unit 14 sends a response indicating operation
suppression completion to the power control unit 11 (step S68).
[0190] Then, the power control unit 11 that has received the
response executes a process for transferring the power state to a
standby state.
[0191] As described above, when it is necessary to follow an order
of applying operation suppression to the respective modules, it is
possible to follow the order.
[0192] Next, the power states of the projector 1 includes two
standby states, i.e., an "active standby" state and a "regular
standby" state.
[0193] Thus, information pertinent to "active standby" and
information pertinent to "regular standby" may be held separately
in the table held by the operation suppression control unit 14
shown in FIG. 1 indicating whether modules are operation
suppression targets. Accordingly, the operation suppression control
unit 14 can send an operation suppression request to all modules
that are operation suppression targets.
[0194] Next, with reference to FIG. 16, a description is given of a
table held by the operation suppression control unit 14 shown in
FIG. 1 indicating whether modules are operation suppression
targets, in which information pertinent to "active standby" and
information pertinent to "regular standby" are held separately. In
this example, a description is given on whether the function
executing units 15 through 17 are operation suppression
targets.
[0195] FIG. 16 illustrates an example of a table held by the
operation suppression control unit 14 shown in FIG. 1 indicating
whether modules are operation suppression targets, in which
information pertinent to "active standby" and information pertinent
to "regular standby" are held separately. In FIG. 16, regular
standby is expressed as "standby".
[0196] The operation suppression control unit 14 stores the table
shown in FIG. 16 in advance, and can thus identify whether the
respective modules of the function executing units 15 through 17,
are operation suppression targets for active standby and regular
standby by referring to the stored table.
[0197] In the table of FIG. 16, in the active standby field,
information expressing "YES" indicating that the function executing
unit 15 is an operation suppression target is recorded and
information expressing "NO" indicating that the function executing
units 16 and 17 are not operation suppression targets is
recorded.
[0198] Furthermore, in the table of FIG. 16, in the regular standby
field, information expressing "YES" indicating that the function
executing units 15 and 16 are operation suppression targets is
recorded and information expressing "NO" indicating that the
function executing unit 17 is not an operation suppression target
is recorded.
[0199] Accordingly, the operation suppression control unit 14 can
send an operation suppression request to all modules that are
operation suppression targets, in the case of active standby and
regular standby.
[0200] Furthermore, the operation suppression control unit 14 can
change the module to which an operation suppression request is to
be sent based on whether the power state is to be transferred to an
active standby state or a regular standby state.
[0201] Next, with reference to FIG. 17, a description is given of
an example of a table held by a module shown in FIG. 1 that is an
operation suppression target, indicating whether functions can be
executed in an active standby state and a regular standby
state.
[0202] FIG. 17 illustrates an example of a table held by a module
shown in FIG. 1 that is an operation suppression target, indicating
whether functions can be executed in an active standby state and a
regular standby state. In FIG. 17, regular standby is expressed as
"standby".
[0203] In this example, a description is given of a table held by
the function executing unit 15.
[0204] The function executing unit 15 stores the table shown in
FIG. 17 in advance, and therefore the function executing unit 15
can refer to this table to determine that in an active standby
state, function A and function B can be executed but function C and
function D cannot be executed.
[0205] Furthermore, the function executing unit 15 can determine
that in a regular standby state, the functions A through D cannot
be executed.
[0206] Next, with reference to FIG. 18, a description is given of a
process of applying operation suppression in an active standby
state performed by the projector 1.
[0207] FIG. 18 is a sequence diagram illustrating a process when
operation suppression is performed in an active standby state by
the projector 1 shown in FIG. 1. In FIG. 18, the steps are
indicated as "S".
[0208] This process is executed when the projector 1 is in a power
on state.
[0209] A description is given of a process in which operation
suppression is performed on the module of the function executing
unit 15 shown in FIG. 1.
[0210] When a request to transfer to active standby is received
from the user, the user operation receiving unit 12 shown in FIG. 1
sends a standby transfer request to the power control unit 11 (step
S71 in FIG. 18).
[0211] Information indicating whether to transfer to the power
state of active standby or the power state of regular standby is
attached to the standby transfer request sent from the user
operation receiving unit 12 to the power control unit 11.
Therefore, the power state to which the module is to transfer is
determined based on this information.
[0212] The power state to which the module is to transfer may be
determined by having the power control unit 11 read a set value in
the request sent from the user operation receiving unit 12 to the
power control unit 11.
[0213] Furthermore, although not shown in FIG. 18, when a standby
transfer request is sent from the PC 2 shown in FIG. 2 to the
projector 1 via the network 3, the network communication unit 13
sends a standby transfer request to the power control unit 11.
[0214] Next, the power control unit 11 sends an operation
suppression request for transferring to active standby to the
operation suppression control unit 14 (step S72).
[0215] The operation suppression control unit 14 refers to the
table of FIG. 16 and determines the operation suppression target
(step S73).
[0216] Then, the operation suppression control unit 14 sends an
operation suppression request to the module that needs to be
subjected to operation suppression. In this example, the operation
suppression request is sent to the function executing unit 15 (step
S74).
[0217] Meanwhile, when the module of the function executing unit
15, which has received the operation suppression request, completes
operation suppression for itself, the function executing unit 15
reports operation suppression completion indicating that operation
suppression has been completed to the operation suppression control
unit 14 (step S75).
[0218] Then, when a response indicating operation suppression
completion is received from the function executing unit 15, the
operation suppression control unit 14 sends a response indicating
operation suppression completion to the power control unit 11 (step
S76). The power control unit 11 that has received this response
executes a process for transferring the power state to active
standby.
[0219] Furthermore, the module that has received the operation
suppression request can recognize which power state the projector 1
is in, and can determine which function the module itself can
execute based on the information in the table of FIG. 17.
[0220] In this case, the function executing unit 15 refers to the
table of FIG. 17, and can determine that in active standby,
function A and function B can be executed but function C and
function D cannot be executed.
[0221] Next, a description is given of a process performed when a
module that is an operation suppression target receives a process
request.
[0222] FIG. 19 is a flowchart illustrating a process performed when
modules of the projector 1 shown in FIG. 1 that are operation
suppression targets receive a process request. In FIG. 19, the
steps are indicated as "S". In this process, the modules that are
operation suppression targets are the function executing units 15
and 16.
[0223] This process is executed when the projector 1 is in a power
on state.
[0224] In step S81, when the function executing units 15 and 16
receive a process request, in step S82, the function executing
units 15 and 16 determine whether the request can be executed. When
the request can be executed (YES in step S82), the process proceeds
to step S83. When the request cannot be executed (NO in step S82),
the process ends.
[0225] In step S83, the function executing units 15 and 16 execute
the requested process, and the process ends.
[0226] In the process of step S82, when the request can be executed
in the module itself in the present state, the function executing
units 15 and 16 execute the requested process (step S83).
Meanwhile, when the request cannot be executed in the module itself
in the present state, nothing is performed and the process
ends.
[0227] Next, with reference to FIG. 20, a description is given of a
process performed when a module that is an operation suppression
target receives a process. In this case, the operation suppression
includes accumulating requests in a queue.
[0228] FIG. 20 is a flowchart illustrating another example of a
process performed when modules of the projector 1 shown in FIG. 1
that are operation suppression targets receive a process request.
In FIG. 20, the steps are indicated as "S". This process is
executed when the projector 1 is in a power on state. In this
example, a description is given of a process performed by the
function executing unit 15 shown in FIG. 1.
[0229] In step S91 of FIG. 20, when the function executing unit 15
receives a process request, in step S92, the function executing
unit 15 determines how the received process request is to be
processed in the present state (of the module itself). When the
request is to be executed, the process proceeds to step S93. When
the request is to be accumulated in a queue, the process proceeds
to step S94. When the request is to be ignored, the process
ends.
[0230] In step S93, the requested process is executed, and the
process ends.
[0231] In step S94, process request is accumulated in a queue, and
the process ends.
[0232] When the module that is an operation suppression receives a
request, and there are only two methods, i.e., "execute" or
"ignore", the following is required. That is, in a case where there
is a request that cannot be executed during operation suppression,
but this request is to be executed at a timing when operation
suppression is released, the request source needs to send the
request again.
[0233] In order to avoid this, in the process shown in FIG. 20, the
module that is the operation suppression target "accumulates the
request in a queue".
[0234] As the data structure for accumulating requests, a general
queue is described; however, any kind of data structure may be
used.
[0235] Furthermore, as to the method of determining how to process
each request performed by the module that is the operation
suppression target, and the flow of processing requests accumulated
in the queue when operation suppression is released, are described
below.
[0236] Next, three methods may be taken for each request received
while a module that is an operation suppression is being subjected
to operation suppression, i.e., execute, accumulate in a queue and
execute later, or ignore.
[0237] The methods to be taken for the respective requested
functions may be held in a table by each of the modules.
[0238] FIG. 21 illustrates an example of a table held by the module
of the projector 1 shown in FIG. 1 that is an operation suppression
target, indicating how to process each request during operation
suppression.
[0239] In this example, a process performed by the function
executing unit 15 is described.
[0240] The function executing unit 15 stores the table shown in
FIG. 21 in advance, and therefore the function executing unit 15
refers to this table, and during active standby, the function
executing unit 15 executes function A, accumulates the requests for
function B and function C in a queue, and ignores and does not
execute an execution request for function D.
[0241] Furthermore, during regular standby, the function executing
unit 15 ignores and does not execute execution requests for
function A through function D.
[0242] Next, with reference to FIG. 22, a description is given of a
process of executing all requests, which have been received during
operation suppression, at the time when operation suppression is
released, at the module that is an operation suppression
target.
[0243] FIG. 22 is a flowchart of a process of executing all
requests, which have been received during operation suppression, at
the time when operation suppression is released, at the module of
the projector 1 shown in FIG. 1 that is an operation suppression
target. In FIG. 22, the steps are indicated as "S".
[0244] In this example, a description is given of a process
performed by the function executing unit 15.
[0245] This process is executed when the projector 1 is in a power
on state.
[0246] In step S101 of FIG. 22, when an operation suppression
release request is received, in step S102, the function executing
unit 15 changes the state of the module itself so that subsequent
requests can be received. In step S103, the function executing unit
15 sends a response indicating operation suppression release
completion. In step S104, the function executing unit 15 determines
whether there are any requests accumulated in a queue during
operation suppression. When there is an accumulated request (YES in
step S104), in step S105, the function executing unit 15 processes
all requests accumulated in the queue, and the process ends.
[0247] Meanwhile, when there are no requests accumulated during
operation suppression (NO in step S104), the process ends.
[0248] As described above, after returning a response to the
operation suppression control unit 14, the function executing unit
15 executes the processes accumulated in the queue, and therefore
no process requests remain unprocessed.
[0249] Next, with reference to FIG. 23, a description is given of a
process of removing an old request when the same request is
received when accumulating requests in a queue.
[0250] FIG. 23 is a flowchart of a process performed by the
projector 1 shown in FIG. 1, for removing an old request when the
same request is received when accumulating requests in a queue. In
FIG. 23, the steps are indicated as "S".
[0251] In this example, a description is given of a process
performed by the function executing unit 15.
[0252] This process is executed when the projector 1 is in a power
on state, and is executed instead of step S94 of FIG. 20.
[0253] In step S111 of FIG. 23, the function executing unit 15
determines whether there is the same request as the presently
received request in the queue. When there is a same request (YES in
step S111), the function executing unit 15 deletes the same request
from the queue in step S112, and accumulates the presently received
request in the queue in step S113, and the process ends.
[0254] Meanwhile, when there are no same requests (NO in step
S111), the function executing unit 15 accumulates the presently
received request in the queue in step S113, and the process
ends.
[0255] As described above, it is possible to prevent a case where
the same requests are accumulated in duplicate in a queue.
[0256] According to the projector 1 according to the present
embodiment, when a request to transfer to standby is received,
operation suppression is applied to a module that receives requests
from outside so that new requests are not received. Therefore, it
is possible to prevent a module from transferring to standby in a
state where execution of a requested process is not completed.
[0257] Furthermore, it is possible to quickly transfer to a standby
state without executing a process requested after a standby
transfer request is received.
[0258] Furthermore, it is possible to transfer to a standby state
after executing a process requested before receiving the standby
transfer request.
[0259] Furthermore, operation suppression can be first applied to a
module that is to be used, when there are modules in a dependency
relationship (for example, the network communication unit 13 and
the function executing units 15 through 17 shown in FIG. 1).
[0260] Furthermore, operation suppression can be first released for
a module that is to be used, when there are modules in a dependency
relationship (for example, the network communication unit 13 and
the function executing units 15 through 17 shown in FIG. 1).
[0261] Furthermore, by giving an operation suppression request only
to the requisite minimum modules, it is possible to quickly
transfer the power state.
[0262] Furthermore, even during operation suppression, when there
is a function that can be executed, it is possible to execute the
function.
[0263] Furthermore, there is no need for a user to send a request
again after operation suppression is released.
[0264] Furthermore, when a request that is the same as a request
accumulated during operation suppression is received, only the new
request is executed. Therefore, it is possible to prevent the same
process from being needlessly executed two times, so that the time
taken to execute accumulated processes is reduced.
[0265] Next, a description is given of another embodiment of the
present invention.
[0266] FIG. 24 illustrates a configuration of a projection system
according to another embodiment of the present invention.
[0267] In the projection system, a plurality of personal computers
including a PC 41 are connected to a projector 40 that is an
example of a processing device via a wired or wireless network 42.
The PC 41 and the projector 40 can perform data communication with
each other. PCs other than the PC 41 are not shown.
[0268] The projector 40 is a video projection device (also referred
to as an "image projection device"), and projects a video based on
projection data input from the PC 41 onto a projection surface such
as a screen.
[0269] The projector 40 includes an operation unit 43, a projection
unit 44, an application controller 45, and an input output (I/O)
controller 46.
[0270] The operation unit 43 includes hard keys and a remote
controller light receiving unit, and is used by the user for
inputting various kinds of operation information to the projector
40.
[0271] The projection unit 44 projects images such as still images
and video images on a projection surface such as a screen, based on
image data (also referred to as "video data") sent from the PC
41.
[0272] The application controller 45 includes microcomputers such
as a CPU, a ROM, and a RAM, and performs application-like processes
such as processing data received from the I/O controller 46 to
convert the data for passing to the projection unit 44.
[0273] The I/O controller 46 also includes microcomputers such as a
CPU, a ROM, and a RAM, and performs input output processes with the
network 42.
[0274] The application controller 45 and the I/O controller 46 are
realized by different processing chips, and respectively perform
collaborative processes.
[0275] The PC 41 sends video data to the projector 40.
[0276] FIG. 25 is a block diagram of a functional configuration
inside the application controller 45 shown in FIG. 24.
[0277] The application controller 45 includes a graphic driver unit
50, an operation control unit 51, a user interface (UI) screen
control unit 52, a power control unit 53, an image decoder unit 54,
an image file acquiring unit 55, an image file receiving unit 56, a
setting control unit 57, an I/O control unit 58, an I/O job
management unit 59, and an inter-controller connection control unit
60, which are functional units realized by a microcomputers.
[0278] The graphic driver unit 50 passes projection data to the
projection unit 44 to be projected.
[0279] The operation control unit 51 receives input from the
operation unit 43.
[0280] The UI screen control unit 52 generates a UI screen
according to input from the operation control unit 51, and displays
the UI screen.
[0281] The power control unit 53 controls power on and power off of
the application controller 45 according to UI operation. That is to
say, the power control unit 53 controls the power state of the
application controller 45.
[0282] The image decoder unit 54 decodes the image data, so that
the image data is converted into byte rows that can be
projected.
[0283] The image file acquiring unit 55 accesses the PC 41
connected to the network 42 or a server (not shown), and acquires
an image file.
[0284] The image file receiving unit 56 receives image files sent
form the PC 41 connected to the network 42, etc.
[0285] The setting control unit 57 sets and acquires various
setting values of the projector 40.
[0286] The I/O control unit 58 receives requests from the image
file acquiring unit 55 and the image file receiving unit 56, and
exchanges messages with the inter-controller connection control
unit 60, to send requests and responses to the I/O controller
46.
[0287] Furthermore, when power off is instructed from the power
control unit 53, the I/O control unit 58 waits for process
completion of a job managed by the I/O job management unit 59, so
as to transfer to a power off state at the time point when there
are no more jobs in progress.
[0288] Furthermore, when power off is instructed from the power
control unit 53, the I/O control unit 58 cancels the job managed by
the I/O job management unit 59, so as to transfer to a power off
state at the time point when there are no more jobs in
progress.
[0289] Furthermore, when power off is instructed from the power
control unit 53, the I/O control unit 58 cancels any jobs that can
be cancelled, and waits for process completion of jobs that cannot
be cancelled, so as to transfer to a power off state at the time
point when there are no more jobs in progress.
[0290] Furthermore, the I/O control unit 58 makes it possible to
cancel processes relevant to network transmission/reception, and as
for processes other than processes relevant to network
transmission/reception, process completion is waited without
cancelling these other processes.
[0291] Furthermore, when the I/O control unit 58 cancels jobs, the
I/O control unit 58 sends information of a communication thread
held in the job information to the I/O controller 46.
[0292] The I/O job management unit 59 stores and manages the state
of the job in progress implemented by the I/O control unit 58.
[0293] Furthermore, the I/O job management unit 59 holds
information indicating whether it is possible to cancel a job,
according to the type of job.
[0294] Furthermore, the I/O job management unit 59 holds
information of a communication thread used as job information.
[0295] Furthermore, the I/O job management unit 59 holds
information indicating whether a job is in a state that can be
cancelled, according to the type of job. When cancelling a job, the
state of the job at that time point is checked to determine whether
the job can be cancelled.
[0296] The inter-controller connection control unit 60 exchanges
data such as messages with the I/O controller 46.
[0297] FIG. 26 is a block diagram of the functional configuration
inside the I/O controller 46 shown in FIG. 24.
[0298] The I/O controller 46 includes an inter-controller
connection control unit 61, a function executing unit 62, a
communication control unit 63, a communication state management
unit 64, and a network connection control unit 65, which are
functional units realized by a microcomputers.
[0299] The inter-controller connection control unit 61 exchanges
data such as messages with the inter-controller connection control
unit 60 in the application controller 45 shown in FIG. 25.
[0300] The function executing unit 62 includes plural processing
units, which respectively perform the actual processes according to
messages passed from the application controller 45. That is to say,
the function executing unit 62 performs processes requested from
the application controller 45.
[0301] The communication control unit 63 accesses the network 42
using the network connection control unit 65, and controls network
transmission/reception via the network connection control unit
65.
[0302] Furthermore, the communication control unit 63 controls a
cancel process for communication of a communication thread that is
transmitted.
[0303] Furthermore, when a request to cancel a network process is
received, the communication control unit 63 executes cancellation
when it is possible to cancel the process, and waits for the
process to end without cancelling the process when it is not
possible to cancel the process.
[0304] The communication state management unit 64 stores and
manages the state of the communication thread used for network
communication. As for threads assigned for communication, the
communication state management unit 64 holds information indicating
the communication state of each thread.
[0305] Furthermore, the communication state management unit 64
holds information indicating whether each network process can be
cancelled, and holds information indicating whether the process can
be cancelled for each purpose/state of the communication threads.
When cancelling a network process, the communication state
management unit 64 cross-checks the purpose/state of a
communication thread at this time point with the held information,
and determines whether the network process can be cancelled.
[0306] The network connection control unit 65 controls the
connection of the projector shown in FIG. 24 with an external
network 42.
[0307] The operation control unit 51 shown in FIG. 25 and the
network connection control unit 65 shown in FIG. 26 function as the
input unit described above.
[0308] Furthermore, the function executing unit 62 shown in FIG. 26
functions as the processing unit described above.
[0309] Furthermore, the power control unit 53 shown in FIG. 25
functions as the power control unit described above.
[0310] Furthermore, the I/O control unit 58 shown in FIG. 25
functions as the operation suppression control unit described
above.
[0311] Next, with reference to FIG. 27, a description is given of a
table stored and held by the I/O job management unit 59 shown in
FIG. 25.
[0312] FIG. 27 illustrates an example of a table held by the I/O
job management unit 59 shown in FIG. 25, including information
indicating whether it is possible to cancel message types.
[0313] The I/O job management unit 59 stores the table shown in
FIG. 27 in advance.
[0314] This table includes message contents and whether the message
can be cancelled for each message type.
[0315] The message type is identification information (ID)
indicating the message type in the I/O controller 46.
[0316] Furthermore, the message contents are information indicating
the contents of the process performed at the I/O controller 46 for
each message type.
[0317] Furthermore, the possibility of cancelling is information
indicating whether the process of the message can be canceled in
the middle.
[0318] By referring to this table, the I/O job management unit 59
can determine whether a process can be cancelled for each message
type indicated by a job.
[0319] FIG. 28 illustrates an example of a table held by the I/O
job management unit 59 shown in FIG. 25, for managing jobs.
[0320] The I/O job management unit 59 also stores the table shown
in FIG. 28 in advance.
[0321] In this table, the thread ID, the job state, and the
receiver are registered for each message type.
[0322] The message type is identification information (ID)
indicating the message type in the I/O controller 46.
[0323] The thread ID is identification information indicating the
thread of the I/O controller 46 at which the job is executed. When
starting and cancelling a job, this thread ID needs to be
specified.
[0324] Furthermore, a job state is information indicating contents
such as the present state of the job, for example, whether a
request is being sent to the I/O controller 46 or whether a
response from the I/O controller 46 is being waited.
[0325] Furthermore, the receiver is information indicating the
functional unit that is the input output destination of the
job.
[0326] In the table of FIG. 28, as candidates of the receiver, the
setting control unit 57, the image file acquiring unit 55, and the
image file receiving unit 56 of FIG. 25 are registered.
[0327] The setting control unit 57, the image file acquiring unit
55, and the image file receiving unit 56 exchange information with
the I/O controller 46 via the I/O control unit 58 to proceed with
processes as applications.
[0328] Furthermore, when determining whether a job can be
cancelled, the I/O job management unit 59 extracts the message type
of each job, determines whether the job can be cancelled by
referring to the setting of the possibility of cancelling in the
table shown in FIG. 27, and when the job can be cancelled, the I/O
job management unit 59 specifies the thread ID of the job and
requests the I/O controller 46 to cancel the job.
[0329] Next, with reference to FIG. 29, a description is given of a
thread state management table stored and held by the communication
state management unit 64 shown in FIG. 26.
[0330] FIG. 29 illustrates an example of a thread state management
table held by the communication state management unit 64 shown in
FIG. 26.
[0331] The communication state management unit 64 stores the table
shown in FIG. 29 in advance.
[0332] In this table, the purpose, state, and user of each thread
ID are registered.
[0333] A thread ID is identification information indicating the
thread of the I/O controller 46 at which a job is executed. When
starting and cancelling a job, this thread ID needs to be
specified.
[0334] The communication state management unit 64 can identify the
thread operating in the I/O controller 46 by referring to this
table.
[0335] Next, the purpose is information indicating the
communication of a function of which the thread is in charge.
[0336] In this table, information indicating that the threads are
in charge of a HTTP server function and a HTTP client function is
recorded.
[0337] The state is information indicating the communication
process state of the thread.
[0338] The user is information indicating the functional unit of
the input output destination of the job.
[0339] It is indicated whether the session processed by the thread
is being performed with the image file acquiring unit 55 or the
image file receiving unit 56 shown in FIG. 25, which are registered
in the table of FIG. 28.
[0340] The setting control unit 57 does not perform network
communication, and thus does not appear in this table.
[0341] The contents of the table in FIG. 29 are used when returning
a response to the application controller 45.
[0342] When starting communications, a thread is specified to start
a communication process.
[0343] When executing cancellation, the communication state
management unit 64 specifies the thread ID from the application
controller 45 and cancels the process of the corresponding
thread.
[0344] Next, with reference to FIG. 30, a description is given of
an example of a process performed until generating a job, performed
by the projector 40.
[0345] FIG. 30 is a sequence diagram illustrating a process
performed until generating a job, performed by the projector 40
shown in FIG. 24. In FIG. 30, the steps are indicated as "S".
[0346] In this process, the image file acquiring unit 55 shown in
FIG. 25 sends a request for acquiring an image file, to a server
(not shown) connected to the network 42.
[0347] This process is executed when the projector 40 is in a power
on state.
[0348] In step S121 of FIG. 30, the image file acquiring unit 55
sends a network transmission request to the I/O control unit
58.
[0349] Next, in step S122, the I/O control unit 58 instructs the
I/O job management unit 59 to generate a new job.
[0350] In step S123, the I/O control unit 58 sends a message to
request network transmission to the inter-controller connection
control unit 60.
[0351] Next, in step S124, the inter-controller connection control
unit 60 in the application controller 45 transfers the message to
the inter-controller connection control unit 61 of the I/O
controller 46.
[0352] In step S125, the inter-controller connection control unit
61 of the I/O controller 46 sends the message received from the
application controller 45 to the communication control unit 63.
[0353] Next, in step S126, the communication control unit 63 causes
the communication state management unit 64 to update the
communication state of the communication thread to be used to a
transmitting state.
[0354] In step S127, the communication control unit 63 causes the
network connection control unit 65 to execute network
transmission.
[0355] In the sequence of FIG. 30, network communication is
performed, and therefore a message is passed to the communication
control unit 63 in step S125. However, depending on the type of
message, the message is passed to the function executing unit 62
shown in FIG. 26. In this case, steps S126 and S127 are not
performed.
[0356] Next, with reference to FIG. 31, a description is given of
an example of a process performed until deleting a job, performed
by the projector 40.
[0357] FIG. 31 is a sequence diagram illustrating a process
performed until deleting a job performed by the projector 40 shown
in FIG. 24. In FIG. 31, the steps are indicated as "S".
[0358] This process is executed when the projector 40 is in a power
on state.
[0359] In this process, as a continuation of the process of the
sequence shown in FIG. 30, a response of network transmission by
the image file acquiring unit 55 shown in FIG. 25 is returned.
[0360] In step S131 of FIG. 31, the network connection control unit
65 returns, to the communication control unit 63, a response of
network transmission indicating that network transmission has been
completed.
[0361] Next, in step S132, the communication control unit 63 causes
the communication state management unit 64 to update the
communication state. In this case, the state of the communication
thread that has been used is updated to transmission completed
(waiting for reception).
[0362] Subsequently, in step S133, the communication control unit
63 sends a message response to the inter-controller connection
control unit 61 by using the response of network transmission as a
response of the message received in the process of FIG. 30.
[0363] Next, in step S134, the inter-controller connection control
unit 61 of the I/O controller 46 transfers the message to the
inter-controller connection control unit 60 of the application
controller 45.
[0364] In step S135, the inter-controller connection control unit
60 sends the received message response to the I/O control unit
58.
[0365] Then, in step S136, the I/O control unit 58 deletes the job
from the I/O job management unit 59 because network transmission is
completed.
[0366] Then, in step S137, the I/O control unit 58 sends a result
for reporting that network transmission is completed, to the image
file acquiring unit 55.
[0367] Similar to the sequence of FIG. 30, network communication is
performed in the sequence of FIG. 31, and therefore the sequence
starts where the network connection control unit 65 returns a
response to the communication control unit 63 in step S131.
However, when the function executing unit 62 shown in FIG. 26 has
been performing the process, the sequence starts where the function
executing unit 62 returns a message response to the
inter-controller connection control unit 61 (corresponding to step
S133). In this case, steps S131 and S132 are not performed.
[0368] Next, with reference to FIG. 32, a description is given of
an example of a process performed until deletion of a job by
cancelling the job, performed by the projector 40.
[0369] FIG. 32 is a sequence diagram illustrating a process
performed until deleting a job by cancelling the job, performed by
the projector 40 shown in FIG. 24. In FIG. 32, the steps are
indicated as "S".
[0370] This process is executed when the projector 40 is in a power
on state.
[0371] In this process, as a continuation of the process of the
sequence shown in FIG. 30, a description is given of ending the
process by cancelling the process, instead of ending the process by
completing the process as in the case of the sequence of FIG.
31.
[0372] In step S141 of FIG. 32, the image file acquiring unit 55 of
the application controller 45 in FIG. 25 sends a request to cancel
the requested network transmission to the I/O control unit 58.
[0373] In step S142, the I/O control unit 58 confirms that there is
a job for which cancel is requested in the I/O job management unit
59.
[0374] In step S143, the I/O control unit 58 sends a cancel request
message to the inter-controller connection control unit 60.
[0375] In step S144, the inter-controller connection control unit
60 of the application controller 45 transfers the message to the
inter-controller connection control unit 61 of the I/O controller
46 shown in FIG. 26.
[0376] In step S145, the inter-controller connection control unit
61 of the I/O controller 46 sends the received message to the
communication control unit 63.
[0377] In step S146, the communication control unit 63 causes the
communication state management unit 64 to confirm the state of the
communication for which cancel is requested.
[0378] In step S147, the communication control unit 63 instructs
the network connection control unit 65 to cancel communication.
[0379] In step S148, the communication control unit 63 causes the
communication state management unit 64 to update the communication
state. In this case, the state of the thread of the cancelled
communication is updated to standby.
[0380] In step S149, the communication control unit 63 sends a
response of the message to the inter-controller connection control
unit 61 as a response of step S145.
[0381] In step S150, the message is transferred from the
inter-controller connection control unit 61 of the I/O controller
46 to the inter-controller connection control unit 60 of the
application controller 45 shown in FIG. 25.
[0382] In step S151, the inter-controller connection control unit
60 sends the received message response to the I/O control unit
58.
[0383] In step S152, the I/O control unit 58 deletes the job from
the I/O job management unit 59 because network transmission has
been cancelled.
[0384] In step S153, the I/O control unit 58 sends the cancel
result to the image file acquiring unit 55 to report that cancel
has been completed.
[0385] Next, with reference to FIG. 33, a description is given of a
process performed until the power is turned off, performed by the
I/O control unit 58 and the I/O job management unit 59 shown in
FIG. 25.
[0386] FIG. 33 is a flowchart illustrating a process performed
until the power is turned off, performed by the I/O control unit 58
and the I/O job management unit 59 shown in FIG. 25. In FIG. 33,
the steps are indicated as "S".
[0387] This process is executed when the projector 40 is in a power
on state.
[0388] In step S161, when an instruction to transfer to power off
is received from the power control unit 53 shown in FIG. 25, the
process proceeds to step s162. To the power control unit 53, an
instruction to transfer to power off is given by an operation to
the operation unit 43 such as pressing the power switch.
[0389] In step S162, the I/O control unit 58 instructs the I/O job
management unit 59 to determine whether there is a job. When there
is no job (NO in step S162), in step S169, the projector 40
transfers to power off (standby state), and the process ends. When
there is a job (YES in step S162), the process proceeds to step
S163.
[0390] In step S163, it is determined whether there is a
non-determined job for which a determination as to cancel or to
standby is not made in the I/O job management unit 59. When there
is a non-determined job (YES in step S163), the process proceeds to
step S164. When there are no non-determined jobs (NO in step S163),
i.e., when a determination has been made for all of the jobs, the
process proceeds to step S166.
[0391] In step S164, it is determined whether the job can be
cancelled. When the job cannot be cancelled (NO in step S164), the
process returns to step S163, and a determination is made for the
next job.
[0392] When the job can be cancelled (YES in step S164), in step
S165, a cancel request is issued, and the process returns to step
S163 and a determination is made for the next job.
[0393] Meanwhile, in step S166, a process completion report for
each job is received indicating that cancellation of the job is
completed or the process has been fully completed, in step S167,
the reported jobs are deleted from the I/O job management unit 59,
and the process proceeds to step S168.
[0394] In step S168, it is determined whether all jobs have been
deleted. When there is a job that has not been deleted (NO in step
S168), the process returns to step S166, and the next job is
deleted.
[0395] When all jobs have been deleted (YES in step S168), and the
deletion of all jobs has been completed and there are no jobs in
the I/O job management unit 59, in step S169, the projector
transfers to a power off state, and the process ends.
[0396] Next, with reference to FIG. 34, a description is given of a
cancel process performed by the communication control unit 63 and
the communication state management unit 64 shown in FIG. 26.
[0397] FIG. 34 is a flowchart illustrating a cancel process
performed by the communication control unit 63 and the
communication state management unit 64 shown in FIG. 26. In FIG.
34, the steps are indicated as "S".
[0398] This process is executed when the projector 40 is in a power
on state.
[0399] In step S171, when a cancel request is received from the
application controller 45, the communication control unit 63 sends
an instruction to the communication state management unit 64 and
the process proceeds to step S172.
[0400] In step S172, the communication state management unit 64
determines whether there is a thread that matches the thread ID
specified in the cancel request, and when there is a matching
thread (YES in step S172), the process proceeds to step S173.
[0401] When there is no thread that matches the thread ID specified
in the cancel request (NO in step S172), the process ends.
[0402] In step S173, the communication state management unit 64
determines whether it is possible to cancel the communication
process of the specified thread. When the communication process
cannot be cancelled (NO in step S173), the process ends. When the
process ends without cancelling the thread, the communication
continues until the process is completed. In another example, the
communication state may be divided into several stages, and after
the communication reaches a state where cancelling is possible, a
cancel request may be received again to cancel the
communication.
[0403] When the communication process can be cancelled (YES in step
S173), in step S174, the communication control unit 63 cancels the
communication process, and the process ends.
[0404] Next, a description is given of a table stored and held by
the I/O job management unit 59 shown in FIG. 25, indicating whether
cancelling is possible in the respective job states.
[0405] FIG. 35 illustrates an example of a table stored and held by
the I/O job management unit 59 shown in FIG. 25, indicating whether
cancelling is possible in the respective job states.
[0406] The I/O job management unit 59 stores the table shown in
FIG. 35 in advance.
[0407] In this table, information relevant to the job states of
each message type and whether cancelling is possible is
registered.
[0408] The message type is identification information (ID)
indicating the message type in the I/O controller 46.
[0409] The job state is information indicating the present state of
the job, for example, whether a request is being sent to the I/O
controller 46 or whether a response from the I/O controller 46 is
being waited.
[0410] The possibility of cancelling is information indicated
whether the job can be cancelled according to the message type and
job state.
[0411] The I/O control unit 58 refers to the table shown in FIG.
35, and determines whether a job can be cancelled according to the
message type and job state.
[0412] Next, a description is given of a table stored and held by
the communication control unit 63 shown in FIG. 26, indicating
whether cancelling is possible according to the purpose and state
of the communication thread.
[0413] FIG. 36 illustrates an example of a table stored and held by
the communication control unit 63 shown in FIG. 26, indicating
whether cancelling is possible according to the purpose and state
of the communication thread.
[0414] The communication control unit 63 stores the table shown in
FIG. 36 in advance.
[0415] In this table, information relevant to the state of each
purpose and whether cancelling is possible is registered.
[0416] The purpose is information indicating the communication of a
function of which the thread is in charge.
[0417] The state is information indicating the communication
process state of the thread.
[0418] The possibility of cancelling is information indicating
whether the communication thread can be cancelled at the
corresponding purpose/state.
[0419] The communication control unit 63 refers to the table shown
in FIG. 36, and when the communication control unit 63 cancels a
communication thread, the communication control unit 63 determines
whether the communication thread can be cancelled according to the
purpose and state of the communication thread.
[0420] According to the projector 40 according to the present
embodiment, when power off is instructed, a job that is not yet in
progress is cancelled, and the projector 40 transfers to power of a
the time point when there are no more jobs in progress. Therefore,
the safety in the power off process can be improved and the time
taken until power off can be reduced.
[0421] Furthermore, by cancelling jobs relevant to network
transmission/reception, the time taken to perform the power off
process can be reduced.
[0422] Furthermore, when it is safer not to cancel a job depending
on the job type, or when processing time can be reduced by not
cancelling a job, such a job is executed without being cancelled.
Therefore, the safety in the power off process can be improved and
the time taken until power off can be reduced.
[0423] In embodiments of the present invention, the specific
configurations of the respective units, the process contents, and
data formats are not limited to those described in the above
embodiment.
[0424] Furthermore, in the above embodiment, the present invention
is applied to the projectors 1 and 40.
[0425] However, the present invention is applicable to any kind of
processing device such as a fax machine, a scanner, a printer, and
a copier, as long as the device has a function of transferring the
power state to a power saving state such as a standby state.
[0426] Furthermore, the configurations described in the above
embodiment may be arbitrarily combined as long as there is no
incoherence.
[0427] According to one embodiment of the present invention, a
processing device is provided, which is capable of preventing
failures caused when the processing device transfers to a power
saving state while a function is being executed, and capable of
quickly transferring to a power saving state without receiving new
requests while transferring to a power saving state.
[0428] The processing device is not limited to the specific
embodiments described herein, and variations and modifications may
be made without departing from the scope of the present
invention.
[0429] The present application is based on Japanese Priority Patent
Application No. 2012-000761, filed on Jan. 5, 2012, the entire
contents of which are hereby incorporated herein by reference.
* * * * *