JP3489222B2 - Facsimile machine - Google Patents

Description

Description: BACKGROUND OF THE INVENTION [0001] 1. Field of the Invention [0002] The present invention relates to a job management apparatus.
In particular, job requests from multiple hosts
The present invention relates to a job management device that can receive and process a job . 2. Description of the Related Art A facsimile apparatus has functions of reading an original, storing it in a memory, transmitting, receiving, and printing out. Normally, in a facsimile apparatus, processing is executed for each job by using these functions one by one. However, in the processing for each job unit, the throughput of the facsimile apparatus, that is, the operation rate is low. Therefore, there has been proposed a facsimile apparatus in which a plurality of jobs are processed simultaneously and in parallel to improve the throughput (Japanese Patent Application Laid-Open No. Sho.
1-288553). On the other hand, a facsimile apparatus can be used not only alone but also incorporated in an information processing system. For example, it is possible to configure a system that executes the transmission, reception, and printing jobs in response to requests from a plurality of host computers (hereinafter, referred to as “hosts”). [0004] When a facsimile apparatus is used in a system as described above, there are the following problems. That is, the system is configured so that the facsimile apparatus operates according to a request or command from the host.For example, when a cancel request is issued for a job request that has been registered once, the facsimile apparatus itself is used in response to the cancel request from the host. The registered job request might be interrupted. Similarly, the job request specified by the host may be canceled by the cancel request input from the input unit of the facsimile apparatus. In such a case, there has been a problem that the job request source whose job request was canceled unexpectedly cannot know the fact of the cancellation. [0005] An object of the present invention is to solve the above-mentioned problem, and when a job request is canceled, the job request source can know the fact of the cancellation.
It is to provide a job management device. Means for Solving the Problems To solve the above problems,
In order to achieve the object, the present invention employs a system in which multiple hosts
Job request that receives a job request and processes the job request.
In the processing device, the
In response to the cancel request, the received job request
Canceling means for canceling and the job request
Canceled job request that was canceled
And a notifying means for notifying the requester of (1). According to the present invention having the above characteristics , the canceling means
The job request is canceled depending on the stage in response to the cancel request.
When the cell request is made, the job request is canceled by the notification means.
The cell request is notified to the requester of the job request. The present invention will be described below in detail with reference to the drawings. FIG. 4 is a block diagram showing the configuration of the information processing system according to one embodiment of the present invention. 2, the facsimile apparatus 1 has a hardware configuration described later with reference to FIG. To the facsimile machine 1, two hosts 3, 4 and an external storage device 5 are connected via a bus 2. Further, the facsimile apparatus 1 is provided with a server 6, and the server 6 is connected to a plurality of computers 8, 9 via a LAN network 7. Further, the facsimile machine 1 is connected to other facsimile machines (hereinafter, referred to as "remote facsimile") 10, 11, and 12 by telephone lines. Next, the hardware configuration of the facsimile machine 1 will be described with reference to FIG. In the figure, each component is connected by a system bus 13. The function of each unit will be described according to job processing. For example, a case will be described in which an original supplied from the host 3 is printed according to an instruction from the host 3 and an original supplied from the host 4 is transmitted to a remote facsimile (FAX) 10 according to an instruction from the host 4. I do. First, when the instruction from the host 3 is executed, the image information of the original supplied from the host 3 is transmitted to the interface 1.
4 and stored in the storage unit 15. The stored image information is transferred to the printing unit 16, and the printing unit 16 prints the received image information. The CPU 17 manages the image information accumulation state of the document in the storage unit 15 and the printing state of the printing unit 16 and the like. Further, in order to perform the above-described printing operation, the CPU 17 issues an instruction to accumulate image information in the storage unit 15, transfer the image information to the printing unit 16, and start printing in the printing unit 16. The storage unit 15
The transfer of the image information from the printer to the printing unit 16 may be any transfer or transfer in units of pages. On the other hand, in the case of a transmission job in which the original supplied from the host 4 is transferred to the remote facsimile 10, the image information of the original is stored in the storage unit 15 via the interface 18, as in the case of the print. Then, the stored image information is transmitted from the communication control unit 19 to the telephone line and transmitted to the remote facsimile 10. In this transmission job, the states of the storage unit 15 and the communication control unit 19 are managed by the CPU 17, and the progress of the processing of the transmission job is grasped. If the transmission original is data that does not match the reception function of the remote facsimile 10, for example, the size of the recording paper, data processing is performed using the encoding / decoding unit 20, the enlargement / reduction unit 21, and the like. Can be sent to the line. In the facsimile machine 1, the above two jobs, ie, printing and transmission, can be processed simultaneously in parallel. Further, the processing status of the job request is read out from the CPU 17 by an instruction from the input unit 22 during the execution of the job, and the progress status and the function of each job, that is, the usage status of each of the printing unit 16 and the communication control unit 19 are displayed. 23. If necessary, the processing can be interrupted by an instruction from the operation of the input unit 21. Although the facsimile machine 1 is not used in the above-mentioned processing, but is used alone, the reading unit 24
To read the original. Interface 2
5 is provided for connecting the server 6. CPU
Reference numeral 17 controls the entire facsimile apparatus 1 in accordance with programs and system data stored in the ROM 26, in addition to the status monitoring. Next, the main functions of the facsimile machine 1 will be described with reference to the block diagram of FIG. In the figure, a job request from a host 100 or 101 is sent to a request analyzer 30 via a host interface 200 or 201.
0 is input. Further, a job request from the input unit 22 of the facsimile machine 1 itself is also input to the request analysis unit 300. The job request from the host 100 etc.
Given by a combination of functions. For example, when printing data supplied from the host 100 or the like at the same time as transmission, a job request including a combination of “transmission” and “print” is made. The request analysis unit 300 analyzes such a job request for each function. The analyzed function request is registered in the job management unit 400. The job management unit 400 instructs a function unit 500 including a printing unit and a communication control unit to execute a function request in order to execute a job for each function. Function management unit 6
Reference numeral 00 always manages the status of each function such as a print unit and a communication control unit of the function unit 500, and supplies the result to the job management unit 400. Therefore, the job management unit 4
00 can give an appropriate instruction to the function unit 500 based on the status of each function unit obtained from the function management unit 600 and the type of job requested. Further, since the job processing result is grasped by the job management unit 400, the notifying unit 700 can notify the host 100, 101 via the host interface 200, 201 of the processing result.
Further, the processing result of the job generated in the facsimile apparatus itself can be displayed on the display unit 23 of the facsimile apparatus 1. The processing result includes the suspension of the job request and the cancellation of the job request, and the processing in the job management unit 400 is executed based on a scheduled program or system data. FIG. 1 shows a case where there are two hosts, but the same applies to a case where a job request is received from two or more hosts. Next, the processing in the request analysis unit will be described with reference to the flowchart of FIG. In the figure, in step S1, a job request supplied from the host 100 or 101 is analyzed, and if the request includes a plurality of functions, the job request is decomposed for each function. In step S2,
It is determined whether a print request is included in the decomposed job request. If a print request is included,
Proceeding to step S3, the print request is stored in the job management section 400. If the job request is not a print request, the process proceeds to step S4, and it is determined whether the decomposed job request includes a transmission request.
If the transmission request is included, the process proceeds to step S5, and the fact that the transmission request has been made is stored in the job management unit 400. Hereinafter, similarly, in steps S6 and S7, it is determined whether or not the reception and read requests are included in the job request.
Proceeding to 8, S9, the respective requests are stored in the job management section 400. The analysis of the job request is repeatedly performed, and each time a request is detected, storage for indicating that the request has been made is performed. Other job requests (not shown) are similarly determined and instructions for processing are given, but illustration is omitted. These job requests can be executed in the order they are received,
Stored as a queue. Next, the processing of a job request from the host will be described with reference to a flowchart. here,
The print request registered in the job management unit 400 is executed from the head of the queue. First, in FIG. 6, in step S10, it is determined whether there is a "print request" based on the analysis result of the request analysis unit 300. If there is a "print request", the process proceeds to step S11. If there is no “print request”, the processing shifts to processing of another function request, for example, transmission request processing. In step S11, it is determined whether resources can be secured based on the presence or absence of a memory capacity for receiving print data, whether or not an operator is operating the print data, and the like. If the resource could not be secured, the process proceeds to step S23, where result information indicating that the resource could not be secured is registered in the job management unit 400, and the end information is notified to the host via the notification unit 700. Simultaneously with the notification of the end information, one of the stored print requests is deleted. On the other hand, if it is determined that the resources can be secured, the process proceeds to step S12, and a transfer function for receiving print data from the host is started. The processing by this transfer function will be described later with reference to FIG. In step S13, it is determined whether the printing unit 16 is in use. This can be determined by the "in use flag" indicating whether or not the print is being used by the function management unit 600. If it is not in use, the process proceeds to step S21 to secure the printing unit 16. That is, the “in use flag” is set to secure the print unit 16. On the other hand, if the printing unit 16 is in use, the process proceeds to step S14, where it is determined whether or not a waiting time is set. This determination can be made, for example, by setting predetermined system data. If the waiting time is to be set, the process proceeds to step S15, where the scheduled waiting time is set in the timer means and counting is started. When the waiting time is not set, that is, when the printing unit 16
If it waits until it becomes empty, the process proceeds to step S16, infinite or a predetermined maximum value is set in the timer means as a waiting time, and time counting is started. The reason why the infinite time is set here is to enable the operation to be restored at any time when the processing is interrupted due to a jam of the print unit 16 or the like and the processing becomes possible. In step S17, it is determined whether the set waiting time has elapsed. If the waiting time has not elapsed, the process proceeds to step S18, and it is determined whether or not the printing unit 16 has become usable. If the print section 16 is not usable, the process proceeds to step S17. Print section 1
When 6 becomes available, the process proceeds to step S20 to secure the print unit 16. In step S21, the printing unit 16 is started to print data from the host. The printing operation will be further described later with reference to FIG. In step S22, it is determined whether the data transfer and the printing have been completed. This determination is made at the end of the processing described with reference to FIGS.
Based on notification to. If the waiting time has elapsed, the determination in step S17 becomes affirmative, and the process proceeds to step S19, where the data transfer from the host is interrupted, and the process ends. Next, reception of print data from the host will be described with reference to the flowchart of FIG. In the figure, in step S30, reception of print data is started, and in step S31, the received data is stored in, for example, the storage unit 15. In step S32, it is determined whether the reception of the print data of a predetermined amount such as a page unit has been completed. If this determination is affirmative, in step S33, the job management unit 400 is notified of the end of the scheduled amount of data transfer. Further, step S3
In step 4, it is determined whether reception of all print data has been completed. If the determination is affirmative, the process advances to step S35 to notify the job management unit 400 of reception completion of all print data. Next, the printing of the print data will be described with reference to the flowchart of FIG. In the figure, in a step S40, it is determined whether or not the operation of the printing unit 16 is possible. This is for determining a state such as "no paper". In step S41, it is determined whether print data exists. If the reception of the print data has been transferred from the host for at least the scheduled unit (for example, one page), the determination is affirmative, and the process proceeds to step S42 to execute the print operation. In step S43,
It is determined whether or not the printing of the scheduled unit of data has been completed. If it is determined that the printing has been completed, the job management unit 400 is notified in step S44 that the printing of the scheduled amount of data has been completed. Further, in step S45, it is determined whether or not printing of all the print data has been completed. If the determination is affirmative, the process proceeds to step S46 to notify the job management unit 400 of the completion of printing of all the print data. Notice. Step S4
If it is determined in step 1 that there is no print data, the flow advances to step S47 to determine whether or not the scheduled time has timed out. In step S41, the print data is waited until the timeout occurs.
In step 6, the job management unit 400 is notified that printing was not possible due to no print data. If the print data is received from the host before the timeout, the process proceeds to step S42. Next, the cancel request process will be described with reference to the flowchart of FIG. By this processing, it is determined whether or not the cancel request instructed from the host or the facsimile machine itself is an acceptable request, and based on the result, the job being executed or the waiting job request is interrupted. In FIG. 5, in a step S50, it is determined whether or not there is a cancel request. In this cancel request, identification information of the cancel request source, for example, if the request source is a host, an identification number unique to the host, a job request number to be canceled, and the like are also received. If there is a cancel request, the process proceeds to step S51, and a job request to be canceled (hereinafter, referred to as “designated job”)
Is operating. If the designated job is in operation, the process proceeds to step S52, and an instruction to interrupt the active job is output to the corresponding functional unit, in this example, the print unit 16. In step S53, it is determined whether or not the interruption operation has been completed.
Proceed to 4. In step S54, the interruption by the instruction is registered in the management table of the job management unit 400.
Next, in step S55, the job request source is notified of the interruption. If it is determined in step S51 that the designated job is not in operation, the process proceeds to step S56,
The registration memory provided in the job management unit 400 is searched to determine whether the specified job is in a waiting state. If the designated job is in the waiting state, the process proceeds to step S57 to remove the designated job from the registration memory. The fact that the specified job has been removed from the registration memory is registered in the management table (step S54). Further, when it is determined that the designated job is not in the waiting state, the process proceeds to step S58, and the cancellation request source is notified that the designated job does not exist. The respective notifications are displayed by a cancel request source or a job request source display unit (display unit 23 in a facsimile apparatus).
Will be displayed. Next, the function of the job management section 400 for executing the cancel request processing will be described. The job management unit 400 has a cancel request processing function described below in addition to the function described with reference to FIG. In FIG. 3, the cancel request detecting unit 30 is a host or the input unit 2.
2 is detected. When the cancel request is detected, the identification information of the cancel request source and the job number are supplied to the designated job state determination unit 31. In the registration memory 32, the function requests analyzed by the request analysis unit 300 are registered in a queue format, and the currently executed job or the job in the waiting state can be recognized based on the registered contents. The specified job status determination section 31 searches the registration memory 32 based on the identification information and the job number, and detects whether the specified job is being executed or is in a waiting state.
Each detection signal is output to the cancel execution unit 33. When detecting the detection signal indicating that the designated job is being executed, the cancel execution unit 33 gives a job interruption instruction to the functional unit 500 (for example, the print unit 16). When detecting the detection signal in the waiting state, the cancel execution unit 33 gives an instruction to the registration memory 33 to remove the designated job in the waiting state from the waiting state. The result of the determination by the designated job state determination unit 32 is output to the notification unit 700. The notification unit 700 notifies the scheduled notification destination based on the determination result of the designated job status determination unit 32. In other words, if the specified job does not exist, the cancellation request source is notified, and if the running job is interrupted or the specified job is removed from the registration memory 32, the job that has been interrupted or removed from the memory is deleted. Notify the requester. The case where the print data from the host is printed by the print unit 16 has been described above with reference to FIGS. 6 to 9, but the transmission and reception of each job are performed similarly to the print processing. The presence / absence of a request is determined from the contents registered in the memory, and simultaneous processing can be performed by time sharing or by forming a functional module. Then, the cancel request can be given to all these processes. The determination of whether or not there is a request for a function other than the "print request" is also performed in parallel. Therefore, for example, when it is determined that there is a “transmission request”,
Regardless of the presence or absence of the “print request”, the processing for the “transmission request” is executed. By such processing, it is possible to efficiently respond to the following requests from the host. For example, it is assumed that after the host 3 issues a document print request, the host 4 subsequently issues a document print and document send request. In this case, the facsimile machine 1 activates the print unit 16 in response to a print request from the host 3. Therefore, a print request from the host 4 cannot be executed immediately. However, if the communication control unit 19 is in an idle state, it can respond to a transmission request from the host 4, and therefore the processing is first executed from the transmission request. When the processing for the print request from the host 3 is completed, the printing unit 16
Becomes empty, so that a print request from the host 4 can be executed, and processing for the request is executed. In this case, if the transmission operation is completed earlier than the printing operation, the result information may be stored in the facsimile machine 1 as information on the job of the host 4. Then, when the printing operation is completed, the transmission result information may be notified to the host 4 together with the result information. Such processing result information in the facsimile apparatus 1 is automatically notified to the host in response to a request from the host that has requested the job or at the end of the operation of each function. The facsimile apparatus is connected to the printing section 16.
The present invention can also be applied to a case where each of the above-described functions has a plurality of functions. That is, the function management unit 600 can grasp the state of each function, and the job management unit 400 can activate each function based on the state and notify the host of the processing result. As is apparent from the above description, according to the first aspect of the present invention, the canceling means cancels.
If the job request is canceled in response to the request, the job
Notifying the requestor of the job request that the request has been canceled
Be informed. Therefore, in requesting job request, even when unintentionally job request has been canceled, the fact
You can recognize the fruit .

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a functional block diagram of a main part of a facsimile apparatus showing one embodiment of the present invention. FIG. 2 is a block diagram showing a hardware configuration of the facsimile apparatus according to one embodiment of the present invention. FIG. 3 is a block diagram showing a cancel main processing function of a job management unit. FIG. 4 is a block diagram illustrating a configuration of an information processing system to which the present invention has been applied. FIG. 5 is a flowchart of job request analysis. FIG. 6 is a flowchart illustrating a print request processing procedure. FIG. 7 is a flowchart of a print data transfer process. FIG. 8 is a flowchart of a printing operation. FIG. 9 is a flowchart of a cancel request process. [Description of Signs] 30: Cancel request detection unit, 31: Designated job state determination unit, 32: Registration memory, 33: Cancel execution unit, 100, 101: Host, 300: Request analysis unit, 400: Job management unit, 500 ... Functional part, 6
00: function management unit, 700: notification unit

────────────────────────────────────────────────── ─── Continuation of front page (56) References JP-A-6-268811 (JP, A) JP-A-6-242901 (JP, A) JP-A-6-110704 (JP, A) JP-A-5-110 258027 (JP, A) JP-A-5-14580 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) H04N 1/00-1/00 108 B41J 29/00-29/70 G03G 21/00 370-540 G03G 21/02-21/04 G06F 3/09-3/12

Claims (1)

Claims: 1. A job management apparatus for receiving a job request from a plurality of hosts and processing the job request, wherein the job management apparatus receives the job request in response to a cancel request for the received job request. Canceling means for canceling the requested job, and canceling instructed from a source other than the requester of the job request.
In response to the request, the cancellation means
And a notifying unit for notifying the requester of the canceled job request that the job request has been canceled when the request has been cancelled.