JP3957838B2 - Information processing apparatus and method, and storage medium storing the program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an information processing apparatus and method, and a storage medium storing the program.
[0002]
[Prior art]
In a conventional information processing apparatus, information is transmitted by a user instructing transmission at a time when transmission is desired. In addition, a transmission time is designated and transmission is performed at the designated time.
[0003]
[Problems to be solved by the invention]
However, the transmission setting once made cannot be changed. Further, another transmission process cannot be set for the information for which transmission is set.
[0004]
[Means for Solving the Problems]
In order to solve the above-described problem, according to the present invention, an information processing apparatus corresponds to execution means for executing processing object information transmission processing and printing processing, and processing object information is associated with the type of process, execution time, and execution destination. Processing target information storage means for storing information, display means for displaying a list of processing target information stored in the processing target information storage means, and processing target information selection for selecting processing target information from the processing target information list Means, processing selection means for selecting a type of processing to be performed on the selected processing target information, and a processing type in which the selected processing type is stored in association with the processing target information. It is determined whether or not they match. If they match, the setting stored in the processing target information storage means is changed in association with the processing target information. If they do not match, the processing target information is associated with the processing target information. Storage control means for adding the type, execution timing, and execution destination of the selected process, and the process target information stored in the process target information storage means in association with the process target information. Execution control means for controlling the execution means so as to execute the types of processing stored in the information storage means based on the stored execution time and execution destination.
[0005]
According to another aspect, processing target information storage means for storing processing target information in association with the type of processing, execution time and execution destination, display means, processing target information selection means, and processing selection means And the storage control means and the execution means, and the display means is stored in the processing target information storage means. A display step for displaying a list of processing target information; a processing target information selecting step for selecting processing target information from the processing target information list; and a processing selecting unit for selecting the processing target information. A process selection step for selecting a type of process to be performed on the processing target information, and a process in which the storage control unit stores the selected type of the process in association with the processing target information. It is determined whether or not the type matches, and if they match, the setting stored in the processing target information storage means in association with the processing target information is changed. A storage control step of adding the type, execution timing and execution destination of the selected process, and the execution means corresponds to the process target information stored in the process target information storage means. In addition, the method includes an execution step of executing the type of processing stored in the processing target information storage unit based on the stored execution time and execution destination.
[0006]
According to another aspect, the processing target information storage means for storing the processing target information in association with the type of processing, the execution timing, and the execution destination is stored in a storage medium storing a computer-readable program. A display step of displaying a list of processing target information stored in the processing target information storage unit on a computer capable of executing processing for transmitting and printing target information, and selecting processing target information from the list of processing target information A processing target information selection step, a processing selection step for selecting the type of processing to be executed on the selected processing target information, and the selected type of processing stored in association with the processing target information It is determined whether or not it matches the type of processing, and if it matches, the setting stored in the processing target information storage means in association with the processing target information is changed, and If not, the storage control step of adding the selected process type, execution time and execution destination in association with the process target information, and the process target information stored in the process target information storage means, A program for executing an execution step of executing the type of processing stored in the processing target information storage unit in association with the processing target information based on the stored execution time and execution destination is stored.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
[0008]
FIG. 1 is a diagram showing a functional configuration of the present embodiment, and shows a relationship among the user 101, the client 102, the server 103, the database 104, and the daemon 105. The client 102 and the server 103 may be on the same device, or may be on different devices connected via a network or the like.
[0009]
When the user 101 performs an operation on the client 102, the client 102 generates a request corresponding to the operation and transmits the request to the server 103. The server 103 interprets the received request, exchanges with the database 104, and performs processing such as adding / deleting a job and acquiring data. As a result, if necessary, a corresponding HTML page is created and transmitted to the client 102. The client 102 displays the received HTML page and prompts the user 101 for a new operation.
[0010]
The job stored in the database 104 is monitored by the daemon 105, and the daemon 105 executes processing such as printing, transmission, and notification corresponding to the job that satisfies the execution condition.
[0011]
FIG. 2 is a diagram showing details of the functional configuration of the present embodiment.
[0012]
The client component 102 includes an operation unit 201 and two Web browsers 202 and 203. User operations performed via the operation unit 201 are converted into requests by the Web browsers 202 and 203 and transmitted to the server component 103.
[0013]
The server component 103 includes a Web server 204, a device manager 205, a request manager 207, and a command analysis / processing unit 208. The request transmitted from the client component 102 is received by the Web server 204 and passed to the device manager 205 or the request manager 207.
[0014]
The device manager 205 acquires the status of the printer 206 and controls it. The Request manager 207 converts the request into a processing command and passes it to the Command analysis / processing unit 208.
[0015]
The command analysis / processing unit 208 executes processing corresponding to the instructed processing command, accesses the database 104 via the database manager 209, and adds / updates the job.
[0016]
On the other hand, the daemon 105 accesses the database 104 via the database manager 209 at regular intervals, checks whether there is a job that satisfies the execution condition, and executes the corresponding processing if it exists.
[0017]
FIG. 3 is a diagram illustrating a flow of information corresponding to a user operation.
[0018]
The client component 102 receives a user operation as input information, generates a request, and transmits the request to the server component 103.
[0019]
The server component 103 interprets the received request, exchanges with the database 104 via the database manager 209, and performs processing such as job addition / deletion and data acquisition. Also, processing such as acquiring the printer status by exchanging with the printer 206 via the device manager 205 is performed. As a result, if necessary, a corresponding display command (HTML page) is created and transmitted to the client 102.
[0020]
The client 102 displays the received display command (HTML page) to the user and prompts a new operation.
[0021]
The job stored in the database 104 is monitored by the daemon 105 via the database manager 209, and executes processing such as printing, transmission, and notification corresponding to the job that satisfies the execution condition.
[0022]
FIG. 4 is a diagram showing the flow of processing from when a user input is received until the processing of the corresponding command is executed.
[0023]
When the user performs an operation, the operation unit 201 converts it to corresponding operation instruction data. For example, an operation performed by a user using a keyboard or a mouse is converted into information that can be handled by an information processing device such as a corresponding key code or mouse movement information.
[0024]
After that, the Web Browser 202 that has received the operation instruction data converted as described above converts it into a corresponding request to the Web Server 204 and transmits it. For example, when one of the buttons displayed on the screen is selected, a request “select a specific button” is created.
[0025]
Upon receiving the request, the Web Server 204 passes the received data to the Request manager 207, which converts it into a processing command corresponding to the request and passes it to the Command analysis / processing unit 208. For example, when the user selects a button for instructing printing, the request “select button for instructing printing” is converted into a processing command “execution of processing corresponding to selection of button for instructing printing” and executed. The
[0026]
FIG. 5 is a diagram showing the flow of processing until information is displayed to the user in accordance with the result of the processing actually performed and the change in the printer status.
[0027]
Upon receiving the processing result, the Request manager 207 passes the corresponding operation instruction data to the Web Server 204. Similarly, the device manager 205 that has detected a change in the printer status passes the corresponding operation instruction data to the Web Server 204. For example, when a new operation screen is displayed to the user as a processing result, it is realized by converting information to be displayed on the screen into data such as HTML. Similarly, the printer status is realized by converting information to be displayed on the screen into data such as HTML.
[0028]
Receiving the operation instruction data, the Web Server 204 transmits the data to the Web Browser 202, and the Web Browser 202 actually displays the data on a display operation unit such as a touch panel to indicate to the user.
[0029]
FIG. 5 is a diagram showing a flow of processing and data until information is displayed to the user in response to a result of processing actually performed and a change in printer status.
[0030]
Upon receiving the processing result, the Request manager 207 passes the corresponding operation instruction data to the Web Server 204. Similarly, the device manager 205 that has detected a change in the printer status passes the corresponding operation instruction data to the Web Server 204. For example, when a new operation screen is displayed to the user as a processing result, it is realized by converting information to be displayed on the screen into data such as HTML. Similarly, the printer status is realized by converting information to be displayed on the screen into data such as HTML.
[0031]
Receiving the operation instruction data, the Web Server 204 transmits the data to the Web Browsers 202 and 203, and the Web Browser 202 actually displays an operation screen on a display operation unit such as a touch panel and presents it to the user. The Web Browser 203 displays the printer status.
[0032]
FIG. 6 is a diagram showing a functional relationship among a plurality of devices (device A and device B). Here, the device A is a printing apparatus, and the device B is a desktop personal computer that manages a user's mail and schedule. Device A and device B each have a client component 102, a server component 103, and a daemon 105. However, the client component 102 of the device B is omitted here assuming that the user is on the device A side.
[0033]
Here, if the user performs an operation on the device A, the operation information of the user is acquired as input information by the operation unit 201 and passed as a request to the device manager 205 and the request manager 207 of the server component 103.
[0034]
The device manager 205 answers the request from the user by acquiring the status of the printer 206 or the like. Further, the request manager 207 controls the printer by the print control unit 601 depending on the type of request, and further analyzes more detailed information by the command analysis processing unit 208 and executes corresponding processing.
[0035]
As a result, the information format is converted using the conversion control unit 603 as necessary, and various processes are executed via the control unit 602. If it is determined that job management is necessary, the database 104 is added or updated via the database manager 209. If it is determined that display is necessary, the display control unit 604 performs display. In addition, if it is determined that notification is necessary, the notification control unit 605 performs notification.
[0036]
On the other hand, the daemon 105 periodically monitors the database 104, and if there is a job that satisfies the execution condition, the corresponding process is executed.
[0037]
Here, when it is determined that the process is not completed in the device A, a request is transmitted to the device B, and the request manager 207 of the device B causes the corresponding process to be executed. For example, in the case of printing the file of the device B, the printing process is executed by the printing unit 607 using the corresponding application. In the case of mail access, access is performed by the mail control unit 608 using a corresponding application. In addition to this, it is realized by using a corresponding application such as reference to schedule information.
[0038]
Furthermore, it is possible to access a job stored in the database 104 of the device B.
[0039]
FIG. 7 is a system configuration diagram according to the present embodiment.
[0040]
In the figure, various devices are connected to a network 701, and data is transmitted and received via the network 701. The printer 702 prints data received via the network and has an input / output operation unit 703. The input / output operation unit 703 performs various displays for the user and receives instructions from the user. The scanner 704 and the multifunction device 705 also have similar input / output operation units. The scanner 704 optically reads data printed on paper or the like, and the multi-function device 705 has both functions of the printer 702 and the scanner 704. The personal computer 706 creates documents and images, and manages personal data such as user mails and schedules.
[0041]
FIG. 8 is a functional block diagram of the printer according to the present embodiment.
[0042]
In the figure, a touch panel 801 displays a printer status and a menu screen to the user, and allows the user to select a menu item and input characters using a displayed keyboard by touching the display surface. it can. Instead of the touch panel 801, a normal display and keyboard may be prepared.
[0043]
The CPU 802 executes various programs including processing procedures to be described later with reference to the flowchart, and controls each unit connected by the system bus 808. A printing unit 803 prints data on paper or the like. The communication unit 804 transmits / receives data including commands and status to / from a desktop, a scanner, another printer, and the like via a network.
[0044]
The ROM 805 stores fixed data and programs. The RAM 806 temporarily stores data and programs. A hard disk drive (HDD) 807 can permanently store programs and data and is used as the database described above. A system bus 808 connects the above-described units of the device, and is used as a medium for transmitting and receiving data, addresses, and control signals between the devices. Various programs including processing procedures to be described later with respect to the flowchart may be stored in the ROM 805, or may be loaded from the HDD 807 to the RAM 806 as needed prior to processing or during execution of processing.
[0045]
FIG. 9 is a flowchart showing the startup sequence when the power is turned on, and shows the startup sequence when the user turns on the machine. When the user turns on the power in step S901, the OS starts in step S902, and then the web server starts in step S903. Next, the client is activated in step S904, and finally the daemon is activated in step S905.
[0046]
FIG. 10 is a flowchart showing the operation of the client component. When the client is activated, a web browser object is created in step S1001, a request is issued to the server component in step S1002, and an HTML page creation is instructed (the page at this time is an Opening Screen). The HTML page sent from the server in response to the request is displayed in step S1003, and the user input is waited for in step S1004. Then, a corresponding process is performed by a user input. If the user's request is “exit”, the system is shut down and terminated in step S1006. If the user's request is to be processed on the client side, it is processed in step S1009 and again waits for user input. If processing is to be performed on the server side, a processing request is issued to the server component in step S1008, and an HTML page created in response to the request is received and displayed. Thereafter, it again waits for user input.
[0047]
FIG. 11 is a flowchart illustrating a processing procedure of the server component in response to a client request.
[0048]
The server component acquires the client request in step S1101, analyzes the request in step S1102, and performs processing corresponding to the request. In response to the request to display the Opening Screen, the printer status is acquired in step S1104. For Cancel All Jobs, in step S1105, a function CancelAllPrinterJobs () function described later with reference to FIG. 12 is called to cancel all jobs. In response to a Cancel / Pause / Restart request, the SetPrinterJobsStatus () function is called in step S1106 to set Job to the specified Status.
[0049]
For any of the above requests, finally, an HTML page corresponding to the request is created in step S1107, and the HTML page is transmitted to the client component in step S1108 to finish the process.
[0050]
If the request is “login” or “logout”, it will be described later with reference to FIG. If the request is “Goto Other Device” or “Goto Desktop”, it will be described later with reference to FIG. When the request is “Search”, “Help”, or “Receive Job / Receive Notification”, it will be described later with reference to FIG. When the request is “Print”, “Send”, “Delete”, “Reschedule”, or “Preview”, it will be described later with reference to FIG.
[0051]
FIG. 12 is a flowchart showing the processing procedure of CancelAllPrinterjobs. The prototype is DWORD CancelAllPrinterjobs ().
[0052]
First, in step S1201, a function GetAllPrinterJobs, which will be described later with reference to FIG. 13, is called to acquire a job from the spool. In step S1202, a specific printer is opened, and in step S1203, the status of each job is set to cancel. Thereafter, in step S1204, the printer is closed. Do this until all Jobs are set to cancel.
[0053]
FIG. 13 is a flowchart illustrating the processing procedure of GetAllPrinterjobs. The prototype is Int GetAllPrinterjobs (pInfo).
[0054]
First, in step S1301, the valid printer, print server, domain, print, and provider are enumerated using the EnumPrinter () function. One of the objects listed in step S1302 is opened, valid jobs in the spool are listed using the EnumJob () function in step S1303, and the printer is closed in step S1304. This operation is performed for all objects.
[0055]
FIG. 14 is a flowchart showing the SetPrinterJobStatus processing procedure. The prototype is Int SetPrinterJobStatus (pPrinterName, JobId, Status).
[0056]
First, in step S1401, the specified job is acquired from the spool using the GetJob function. In step S1402, a specific printer in which the job exists is opened, and in step S1403, the job status is set to a designated value. In step S1404, the printer is finally closed.
[0057]
FIG. 15 is a flowchart showing the processing procedure of the server when the client request is “login” and “logout”.
[0058]
If the request is login, first, a login verb and a remote device list are acquired in step S1502, and a user name is acquired in step S1503. In step S1504, GetUserId () is called to obtain a valid Job list for the user. In step S1505, a corresponding HTML page is created. At the same time, details of the user and the job are stored in the hidden area in step S1506.
[0059]
On the other hand, in the case of a Logout request, it is checked in step S1507 whether the remote device list is empty. If it is empty, an OpeningScreen page is created according to the status in step S1510. If it is not empty, until the list becomes empty, the next device is logged in with login verb = Disconnect in step S1508, and the device is repeatedly deleted from the remote device list in step S1509. In other words, all devices in the remote device list are logged out. When the list is empty, create an OpeningScreen page.
[0060]
In both cases of Login and logout, the created page is finally transmitted to the client component in step S1511.
[0061]
FIG. 16 is a flowchart showing the server processing procedure when the client request is “Goto Other Device” or “Goto Desktop”.
[0062]
If the request is Goto Other Device, the device name and device address are acquired in step S1602. In the case of Goto Desktop, a desktop address is acquired in step S1603. Thereafter, the device is added to the remote device list in step S1604, and a login verb is created in step S1605. If the login verb is Device or Desktop, Print, Send, Delete, Reschedule, log in to the device with the Login verb in step S1607. If the login verb is Device or Desktop, create the opening screen HTML page in step S1608. In the case of Send, Delete, and Reschedule, HTML pages of the PrintJob, Send Job, Delete Job, and Reschedule Job screens are created in steps S1609, 1610, 1611, and 1612, respectively. If the login verb is Disconnect, the device logs out from the device in step S1613, deletes the device from the remote device list in step S1614, and creates an opening screen HTML page in step S1615. Finally, in step S1616, the page is transmitted to the client step component, and the process ends.
[0063]
FIG. 17 is a flowchart showing the processing procedure of the server when the client request is “Search” “Help” “Receive Job / Receive Notification”.
[0064]
In the case of a search request, the search parameter is acquired in step S1702, and the search is executed in step S1703. In step S1704, a search result HTML page is created from the execution result. In the case of a Help request, a help context parameter is acquired in step S1705, and a corresponding help screen HTML page is created in step S1706. In either case, finally, in step S1707, the created HTML page is transmitted to the client component, and the process ends.
[0065]
If the request type is Receive Job / Notification, the data buffer is read in step S1708, and if the buffer is Receive Job in step S1709, to the IdAnalyze () function described in FIG. Then, the process is passed to IdAnalyzeNotify described with reference to FIG.
[0066]
FIG. 18 is a flowchart showing the processing procedure of IdAnalyze. Here, Job passed as line data from other devices is interpreted. This Job is executed by the daemon module in addition to the DB.
[0067]
First, in step S1801, the Demarshal function is called, demarshal is performed, and the buffer object is enabled. Next, in step S1802, the compressed data is decrypted and expanded using the UnformatData function, so that the data becomes valid in units of rows. In step S1803, the Demarshal function is called again to enable the message object. Finally, in step S1804, a ReceiveJob function (DUMMY) described later with reference to FIG. 19 is called to add the Job to the DB.
[0068]
FIG. 19 is a flowchart showing a DUMMY processing procedure. This module is a dummy of the ISAPI Extended Receive module that receives the line buffer sent by SendJob. Passed to CGI application.
[0069]
Actually, these functions in the line buffer sent by SendJob in step S1901 are read, and the temporary file is dumped in step S1902. This file name is passed to IDExtn.Exe of the CGI module in step S1903. In step S1904, the file name is read and data is acquired. To send data to the CGI application in step S1905, this module uses an internet client call.
[0070]
FIG. 20 is a flowchart showing the processing procedure of IdAnalyzeNotify. Interpret Notification passed as row data from other similar devices. In addition to processing this notification, the notification is executed by the daemon module.
[0071]
Actually, in step S2001, the Demarshal function is called, demarshal is performed, and the buffer object is enabled. Next, in step S2002, the compressed data is decoded and expanded using the UnformatData function, so that the data becomes valid in units of rows. In step S2003, the Demarshal function is called again to enable the message object. Finally, in step S2004, a ReceiveHttpNotification function described later with reference to FIG. 21 is called to add the Job to the DB.
[0072]
FIG. 21 is a flowchart showing the processing procedure of ReceiveHttpNotification. The prototype is Void CIDAction :: RecieveHttpNotification (poNotify).
[0073]
This function is a function that receives a notification sent by the HTTP protocol. Even if the device does not support the requested notification method, the intermediate device can be used to finally notify the target device.
[0074]
In step S2101, the receiver name and address of notification and the notification method are checked, and in step S2102, it is checked whether this device is a target device for receiving notification or only functions as an intermediate point for passing notification to other devices.
[0075]
If this device is the final target value, a temporary file is created in step S2103, and a notification message is written therein in step S2104. In step S2105, a fixed file “pollfile” (a file polled by the daemon) in the Windows directory is created and overwritten. In step S2107, the command line parameter of the notification module (module for displaying or creating a message) is specified in this file, and notification is performed using the notification method specified in step S2107.
[0076]
If this device is an intermediate device, it is confirmed in step S2108 whether or not this device has the capability of issuing notification. If there is, the notification is transmitted to the designated device by the designated method in step S2110. If this device does not have the capability to issue a notification, in step S2112 the notification is transmitted to another intermediate point via the HTTP protocol.
[0077]
FIG. 22 is a flowchart showing the processing procedure of the server when the client request is “Print”, “Send”, “Delete”, “Reschedule”, or “Preview”.
[0078]
In the case of these five requests, first, in step S2201, a user ID, JobID, and ActionID are acquired.
[0079]
In the case of a print request, the printing time and location are acquired in step S2203, and the notification list is acquired in step S2204. In step S2205, the function PrintJob () is called to execute printing.
[0080]
In the case of a Send request, the transmission time and location are acquired in step S2206, and the notification list is acquired in step S2207. In step S2208, the function SendJob () is called and transmitted.
[0081]
In the case of a Delete request, the CancelAction () function is called in step S2209 to delete the Job.
[0082]
In the case of a Reschedule request, the RescheduleAction function is called in step S2210 to change the schedule.
[0083]
In the case of a Preview request, the job is converted into JPG or GIF format using format conversion library in step S2211.
[0084]
In all the above requests, a corresponding HTML page is created in step S2212, and the HTML page is transmitted to the client component in step S2213, and the process ends.
[0085]
FIG. 23 is a flowchart illustrating the PrintJob processing. The prototype is void CIDAction :: PrintJob (ActionId, NotifyList). The input parameters are the specified action ID and user notification setting list, and the job is immediately printed on this device.
[0086]
When the ActionID is Print / Hold, the Action attributes (Print time, Notification, etc.) are corrected to the current time and the new Notification. When ActionID is Send, a new Action is created in the DB. This depends on whether there are other PrintActions related to this Job that this user is holding. After the Job is printed, the ActionStatus becomes “done”, and this Action becomes part of the user's history.
[0087]
First, in step S2301, a record is pulled out and the details of the action are checked. In step S2302, it is checked whether the old action is held, and this information is stored in step S2303. In step S2304, JobData necessary for this action is acquired. In step S2305, the entry in the database is corrected to be “printing”. This is to prevent the daemon module from executing this record.
[0088]
In steps S2307 and 2308, a new record is created or an existing record is corrected. For example, if the previous Action was Print / Hold, the record is modified, and if the previous Action was Send, a new record is created for that Job when the user has no Hold PrintAction. . new / old ActionID is returned (subject to conditions).
[0089]
In step S2309, Notification Status becomes False unconditionally. In step S2310, notification is added to this newActionID to set the user type to “Don't care” (that is, there is no sender or receiver).
[0090]
In step S2311, Job is sent to the print queue for printing using Spooler API Calls. In step S2312, the entry is corrected as “printing succeeded” or “finished”. In step S2313, NotificationStatus is set in accordance with the action status of printing.
[0091]
FIG. 24 is a flowchart showing the SendJob processing. The prototype is Void CIDAction :: SendJob (bsendjobToDatabase, ActionId, roJobMessage).
[0092]
Send a new Job to the specified “existing” Job or to the specified receiver / device list. By sending, one copy is sent to one device. In this case, if there are multiple receivers, the Job copy is shared. All other receiver information is also sent, so it is possible to access the Job from other devices. Job is sent using HTTP protocol.
[0093]
Actually, in step S2401, it is checked whether the job has an ActionId or a new job. If ActionId exists, the attribute of Action is acquired in Step S2402, and it is checked in Step S2403 whether the Action type is Hold. If it is a Hold Job, information that the Hold Job has been accessed is stored in step S2404.
[0094]
Next, when this information is designated to go to the DB, in step S2406, SendJob () is called, and all information related to the job (sender, receiver, etc.) is stored in the DB. After that, in step S2407, it is checked whether or not to send “now”, and if it is not sent now, the process ends and waits for the daemon module to execute transmission. When sending now, in step S2408, the transmission is executed and the process ends.
[0095]
FIG. 25 is a flowchart showing a transmission execution procedure by SendJob ().
[0096]
First, call EditAction () and set ActionStatus to active. Next, the receiver list is processed to obtain the user name, device name, and device URL address. Format conversion is performed so as to correspond to the receiver device. This is done using a suitable image conversion library. The message data is converted into a byte string, and further compressed and encoded. Send this data using the HTTP protocol and set ActionStatus to done. Furthermore, Action is added as a part of the user history, and notification status is set to success / fail depending on the transmission status. Status indicating that the job is a job accessed from the Held List is set (steps S2501 to 2511).
[0097]
FIG. 26 is a flowchart showing the CancelJob processing procedure. The prototype is Void CIDAction :: CancelJob (dwActionId).
[0098]
This function cancels the specified action. Specifically, in Step S2601, the Action attribute is acquired, the CancelAction () function is read, and the Action is marked as cancelled. If the Action is in the Hold list, it is added to a part of the user history in Step S2603, and if it is a part of the user history, the entry is deleted in Step S2604. If Action is Hold, in step S2606, the notification condition is set to “Accessing Hold Job”. If the user is a receiver on this device, the process is terminated. If the user is on another device, the user logs in to the device in step S2608, and details on the cancel action are set in step S2609. In step S2610, the SendJob () function is called to send this information to the actual device, and transmission is executed. This cancels the action.
[0099]
FIG. 27 is a flowchart showing the SendNotification processing. The prototype is Void CIDAction :: SendNotification (dwActionId).
[0100]
This function is a function that performs actual notification. Notification types such as Popup are notified by sending http. In the case of telephone or e-mail, notification is made by calling an appropriate module. If an unsupported method is specified, a notification is sent to the specified intermediate device and retransmitted. This function is only performed when a “now” nitification must be sent. In this case, NotificationStatus is set to Done so that the daemon module does not poll.
[0101]
Actually, first, a notification method is checked in step S2701, and when the method is a popup window or a voice message, data is transmitted by the http protocol in step S2703. When the method is a telephone or the like, it is checked in step S2705 whether the device has a notification capability. If the device has the capability, notification is performed in the designated method in step S2704. If the device is not capable, the intermediate point is checked in step S2706. This midpoint supports the specified issuing mechanism. In step S2707, the notification message and its details are transmitted to the intermediate device using the HTTP protocol. This method can also be used for email, fax, and pagers.
[0102]
FIG. 28 is a diagram illustrating a correspondence relationship between input information for the server and processing. The processing corresponding to it is summarized.
[0103]
Here, the control unit 602 governs Print Job, Send Job, Cancel Job, Send Notification, and Receive HTTP Notification. This module is the main module of the back end of the printer, and “Print Job Now Now.” “Print Job Here Now.” “Job Job Now in a Different Place” "Print the job later in a different location.""Send the job to another device now or later.""Change the schedule.""Cancel the job action." ”“ Set notification type (voice, pop-up window, phone, e-mail, fax). ”“ Receive notification. ”“ Get or set device status. ”
[0104]
This module covers the DB module in a form that is transparent to the DB and the module that uses it (GUI module, Daemon module, etc.).
[0105]
FIG. 29 is a flowchart showing a processing procedure after the daemon 105 is started.
[0106]
The daemon module 105 continually polls the DB and files to execute actions and operations registered to be executed later. In all these cases, entries are created in the DB.
[0107]
First, in step S2901, a thread that performs polling in an infinite loop is created, and a Job that must be executed “now” is polled. When a Job (Action) is found in the DB, its Action type is checked (steps S2902 to 2905).
[0108]
If Action is Print, in step S2906, the PrintJob () function is called and printing is executed. If the Action is Send, in step S2908, ConstructSendMessage () is called to create a message, and then in step S2909, the SendJob () function is called to execute transmission.
[0109]
If Action is Hold, the CancelJob () function is called in step S2907 to cancel the Job.
[0110]
After these processes, notification is checked in step S2910.
[0111]
FIG. 30 is a flowchart showing the Notification processing procedure of the daemon module.
[0112]
First, in step S3001, it is checked by calling the function PollNotify () whether there is a notification to be issued from this device. If there is a notification to be issued, in step S3002, the notification is issued by reading the SendNotification () function. If there is no notification, the presence of the application file is checked in step S3003.
[0113]
If the file exists, in step S3005, the command line parameters are read from the file, and then the file is deleted. Start the ShowNotify.Exe module and pass the command line parameters.
[0114]
Finally, in the case of PullPrint, the PrintOcx.EXE file is activated in step S3007, and in the case of Schedule, the DataDumo.Exe file is activated in step S3008.
[0115]
FIG. 31 shows the relationship between the types of jobs handled by the daemon and the corresponding processing.
[0116]
FIG. 32 is a flowchart showing the PrintPrinterJob processing procedure. The prototype is Int PrintPrinterJob (pPrinterName, pDocumentName, pVoid, Bufsize).
[0117]
This function prints that Job is spooled in the printer. Actually, the specified printer is opened, the printer is notified that the job is spooled, data is written to the printer, and the printer is closed (steps S3201 to 3204).
[0118]
FIG. 33 is a flowchart illustrating the Sendjob processing.
[0119]
In step S3301, it is checked whether the job to be sent is new or existing in the database. If it is a new job, the details are added to the database in step S3303. In step S3311, the Sender / Receiver of the job is similarly checked. If they exist in the database, the new Action is added to the user ID in step S3312, and for those that do not exist in the database, a new entry is added in step S3313.
[0120]
If an existing job is sent, check the action to Sender. If Action is Send and the status is Todo or Active, change When todo time of Action to the new time when JobMessage was created. In step S3313, if Action is Send and is already executed, a new Action is added to the database. If Action is not Send, the Action entered for this job is created in the database.
[0121]
In all cases, the existence of the receiver of the job is checked, and if the receiver does not exist in the database, a new entry is created. When Action is Hold and ActionStatus is Todo, change Action to Send and change WhenTodo time to the new time when JobMessage was created. If ActionStatus is not Todo, create a new record with Action Send, and set WhenTodoTime to the new time specified in JobMessage.
[0122]
FIG. 34 is a flowchart showing the processing procedure of ReceivejobData.
[0123]
First, in step S3400, the check item “Deny Jobs From Person / Device” is checked, and in the case of a job from the transmission source set here, the reception of the job is rejected in step S3417. This item is set by the administrator.
[0124]
FIG. 134 is a diagram showing a setting screen for setting job rejection. In the figure, an identifier of a user to be rejected is set in “Deny Jobs From Person”. In “Deny Jobs From Device”, a device to be rejected is set. Further, as will be described later with reference to FIG.
[0125]
The expiration date and the type of processing to be rejected may be set. By looking at the check items set as described above, it is determined whether or not to accept the job from the transmission source user or device, and if it is permitted, the receiving process is performed.
[0126]
There are two cases where the received job is a new job and an existing job.
[0127]
If a new job is received, a new entry is added to the job details at step S3402. If no Sender exists, an entry for Sender is added in step S3404. In step S3405, Action and Notifications are added in the same manner. If Sender exists, Notifications is added in Step S3406. If no Receiver exists, it is added in step S3408. In step S3409, Receiver Action is also added.
[0128]
If an existing job is received, check the receiver of the job. If Receiver is present and has the same Action as received, the previous Action status is canceled and a new record is created. A new entry is added for the Receiver when it has a different Action than the one for the Receiver. Notifications are also added in some cases. The Action status is set to Todo unless the Usertype is different.
[0129]
FIG. 35 is a flowchart showing the processing procedure of GetListOfJobAttribute.
[0130]
Check all jobs for a user at a specified location and return all details for that user's job. There are two jobs, Heldjobs or Historyjobs. The database searches for jobs by UserID and all jobs are picked up and added to the list. This list is returned (steps S3501 to 3507).
[0131]
FIG. 36 is a flowchart showing the processing procedure of PollJob.
[0132]
A search is made for a user type Receiver, ActionStatus Todo, and WhenTodo shorter than the current system time (steps S3601 to 3605). If the job exists, the details of the job are acquired, data is set in the ActionSet, and TRUE is returned (steps S3606 to 3608). If Job does not exist, FALSE is returned (step S3609).
[0133]
FIG. 37 is a flowchart showing a PollNotify processing procedure.
[0134]
The first record in which CanNotify is TRUE, WhileToNotify is TRUE, and WhenToNotify is shorter than the current system time is searched (steps S3701 to 3705). If a record exists, the details of notification are acquired, data is set in NotificationSet, and TRUE is returned (steps S3706 to 3708). If no record exists, FALSE is returned (step S3709).
[0135]
FIG. 38 is a flowchart showing the CancelAction processing.
[0136]
First, a record having the specified ActionID is searched. If the corresponding record exists, a job having the same ActionId is searched and its size is checked (steps S3801 to 3804). If the size is smaller than the JobSizeLimit set by the administrator, the ActionStatus is checked in step S3805. If this ActionStatus is Done or the job size is equal to or larger than JobSizeLimit, the ActionStatus is changed to Deleted and the record is deleted (steps S3807 to 3808). In other cases, ActionStatus is canceled in step S3806. In step S3809, all notifications corresponding to ActionID are deleted.
[0137]
FIG. 39 is a flowchart showing the EditAction processing.
[0138]
The record having the specified ActionID is searched, and when the corresponding record is found, the Action status is converted into the received parameter (steps S3901 to 3903).
[0139]
FIG. 40 is a flowchart showing the EditAction processing. The prototype is different from that described with reference to FIG.
[0140]
A record having the specified ActionID is searched, and if the Action of the corresponding record matches the ActionID Action and the Action status is pending, the Action status is converted to the received parameter (steps S4001 to 4006). If there is no corresponding record, a new action is added in step S4004.
[0141]
FIG. 41 is a flowchart showing the RescheduleAction processing.
[0142]
Search for records with the specified ActionID. If the corresponding record is found and the Action Status is not done, WhenTodo is converted to the received NewTime (steps S4101 to 4104).
[0143]
FIG. 42 is a flowchart illustrating the RescheduleAction processing. The prototype is different from that described with reference to FIG.
[0144]
In step S4201, a record having the specified ActionID is searched. If the corresponding record is found and the UserType matches, the action status is changed to cancel, and a new record with the action status Todo is added (steps S4201 to 4204). If the corresponding record is not found, check the existence of the user. If the user is found, pick the UserID. If not found, add a new user and pick the UserID. A new Action that matches this UserID is added (steps S4206 to 4209).
[0145]
FIG. 43 is a diagram showing a RescheduleAction processing procedure. The prototype is different from that described with reference to FIGS.
[0146]
Search for records with the specified ActionID. If the record is found, check the Action status and Action. If the Action matches the ActionID and the Action status is pending and not completed, the WhenTodo time is changed to a new time. All Notifications of ActionID are deleted and new Notifications are added (Steps S4301 to 4302, 4304 to 4308). If the corresponding record is not found, a new Action whose Action status is Todo is added in Step S4303, and the WhenTodo time is changed to a new time.
[0147]
FIG. 44 is a flowchart showing the AddNotification processing.
[0148]
Add a new record to Notification. Check the parameter's general information (GeneratedFrom parameter) and create a new entry for this.
[0149]
FIG. 45 is a flowchart showing the processing procedure of AddInstruction.
[0150]
When ReceieveJob or SendJob is generated, Instruction setting is invoked. First, in step S4501, the existence of the specified UserId on the database is confirmed. If it does not exist, the process is terminated. If it exists, a record is acquired from the Instruction list in Step S4502, and a new instruction is added to this User in Step S4503.
[0151]
Instruction adds Instruction to the Instruction table of the database. The associated Action and the Notification given with the Instruction are reflected in the Action table and the Notification table (steps S4504 to 4506).
[0152]
In both the Receive job and the Send job, when an instruction for generating these is satisfied, a record that acts as a template for generating a new action and a new notification is added to the action table and the notification table.
[0153]
FIG. 46 is a flowchart showing the GetInstruction processing.
[0154]
This function is called by ReceiveieveJobData and SendJobData. First, in step 4601, it is checked whether the Action type is Receive or Send for all records in the Instruction table, and all commands of the specified Action type are acquired. In step S4602, details (values set as commands) in the JobMessage are checked, and using these values, it is checked whether or not the instruction can be executed. The check function (described later) is used to check the validity of the instruction. If Instruction is valid, its Id is added to the list in step S4603. If processing is completed for all instructions in step S4603, a list of valid InstructionIds is finally returned.
[0155]
FIG. 47 is a flowchart showing the processing procedure of Execution Instruction. This function is called by ReceiveieveJobData and SendJobData. Search for records in Action and Notification tables. These records are executed according to each instruction in the instruction list, and a copy thereof is created in each table with a todo flag (set to TRUE) (steps S4701 to 4708).
[0156]
Search Action table for dummy action set by instruction. Based on these dummy actions, a new appropriate record is added and the action is executed.
[0157]
Search for dummy notification set by Instruction. A new appropriate record is added based on these dummy notifications, and notification is executed.
[0158]
FIG. 89 is a flowchart showing the ResetInstructions processing. The prototype is Void ResetInstructions (dwUserId, pInstructionList).
[0159]
First, all the instructions of the specified UserId are searched, and the obtained instruction and all Actions and Notifications corresponding to the instruction are deleted (steps S8901 to 8905). Thereafter, a new instruction passed in the instruction list is added (step S8906).
[0160]
FIG. 90 is a flowchart showing the DeleteAllInstructions processing. The prototype is Void DeleteAllInstructions (dwUserId).
[0161]
All the instructions of the specified UserId are searched, and the searched instruction and all Actions and Notifications corresponding to the instruction are deleted (steps S9001 to 9005).
[0162]
FIG. 91 is a flowchart showing the DeleteInstructions processing. The prototype is Void DeleteInstructions (dwInstructionId).
[0163]
The instruction with the specified InstrucationId is searched, and the searched instruction and the Action and Notification corresponding to the instruction are deleted (steps S9101 to 9104).
[0164]
FIG. 92 is a flowchart showing the GetInstructionDetails processing procedure. The prototype is Void GetInstructionDetails (dwUserId).
[0165]
The instruction of the specified UserId is searched, and the searched instruction and the details of Action and Notificatioin corresponding to the instruction are returned as a list (steps S9201 to 9208).
[0166]
FIG. 93 is a flowchart showing the Check processing procedure. The prototype is Bool Check (nJobChk, JobNameConnector, nDeviceChk, DeviceConnector, nPersonChk, PerconConnector, nTimeChk, TimeConnector, nStatusChk, nStatusCode).
[0167]
This function is called in GetInstrucsionIds (). It is checked whether the instruction is executable and valid. If valid, TRUE is returned, otherwise FALSE is returned (steps S9301 to 9303).
[0168]
FIG. 94 is a flowchart showing the GetJobData processing. The prototype is Void GetJobData (dwJobId, poJobMessage).
[0169]
A job with the specified JobId is searched, and the details of the job are set in JobMessage (steps S9401 to 9403).
[0170]
FIG. 95 is a flowchart showing the GetJobAttributes processing. The prototype is Void GetJobAttributes (dwJobId, poJobMessage).
[0171]
Search Job of specified JobId and set Job details in JobMessage. Further, the details of the Sender and Receiver of the Job and the details of the related Action are searched, and the details are set in JobMessage (Steps S9501 to 9505).
[0172]
FIG. 96 is a flowchart showing the GetActionAttributes processing procedure. The prototype is Void GetActionAttributes (dwActionId, poActionMessage).
[0173]
Search for the Action with the specified ActionId and set the Action details in ActionMessage. Also, the user name and address of the Sender and Receiver of the Job are set in the ActionMessage of the Sender and Receiver (Steps S9601 to 9605).
[0174]
FIG. 97 is a flowchart showing the DeleteJob processing. The prototype is Void DeleteJob (dwUsrLd, dwJobId).
[0175]
In step S9701, the Action of the specified UserId having the specified JobId is searched. If there is an action, the type of ActionStatus is checked in step S9703. If ActionStatus is Not Done, in Step S9704, ActionStatus is changed to ActionCancel, and the execution time is set to the current time.
[0176]
If the ActionStatus is already Done or Cancel, in Step S9705, the Action and all related notifications are deleted. In step S9706, it is checked whether there is an action of UserId other than the specified UserId having the specified JobId. If not, in Step S9707, all the actions of the specified UserId having the specified JobId are already Done or It is checked whether or not it is Canceled. If there is no other user's Action and all the actions are already Done or Canceled, in step S9708, the record of this Job is deleted from the Job table.
[0177]
FIG. 98 is a flowchart showing the GetNotificationList processing. The prototype is Void GetNotificationList (nGeneratedFrom, dwId).
[0178]
All notifications that are generated from the specified generation location (either Action / Instruction) and have the specified Id are searched, the details are added to the list, and the list is returned (steps S9801 to 9804).
[0179]
FIG. 99 is a flowchart showing the SetNotificationCondition processing. The prototype is Void SetNotificationCondition (nGenetaredFrom, dwId, nResult).
[0180]
Searches for Notification with the specified Id that is generated from the specified location (nGenerateFrom), and if created with the specified value (nResult), IfToToify is set to TRUE, and if not created with the specified value, FALSE (Steps S9901 to 9905).
[0181]
FIG. 100 is a flowchart illustrating the processing procedure of SetNotificationCondition. The prototype is Void SetNotificationCondition (nGenetaredFrom, dwId, bCanNotifyFlag, nDummy).
[0182]
The notification having the specified NotificationId generated from the specified location is searched, and CanNotifyFlag is set to the specified value (bCanNotifyFlag) (steps S10001 to 10003).
[0183]
FIG. 101 is a flowchart showing the SetNotificationStatus processing. The prototype is Void SetNotificationStatus (dwNotificationId, bNotificationStatus).
[0184]
Search for Notification having the specified NotificationId, and set Notification Status to the specified value. (Steps S10101 to 10103).
[0185]
FIG. 102 is a flowchart showing the ClearHistory processing procedure. The prototype is Void ClearHistory ().
[0186]
First, in step S10201, Action Status is checked to search for Done, Canceled, Ignored, and Deleted Actions. For each of the obtained Actions, if the Action Status is Done Job, the execution time is checked in Step S10204. Otherwise, in Step S10205, the WhenTodo time is checked. In step S10206, these times are compared with the history (Hostory) retention time limit. Such restrictions on jobs are set by the administrator. FIG. 133 shows an example of a setting screen for this purpose. Here, it is set to 1 month. As a result of the comparison, if the retention time limit has elapsed from the execution time or the scheduled execution time, Action and Job are deleted in step S10207.
[0187]
FIG. 103 is a flowchart showing the DeleteAllPublicInfoJobs processing procedure. The prototype is Void DeleteAllPublicInfoJobs ().
[0188]
All PublicInfo Jobs are searched and ActionStatus is set to ActionCancel (steps S10304 to 10304).
[0189]
FIG. 104 is a flowchart showing the PrintPublicInfo processing procedure. The prototype is Void PrintPublicInfo (dwActionId).
[0190]
Search for the Action with the specified ActionId and check if there is a PublicInfoJob. Add a new Action if it exists. This Action is set to PublicInfo, Action is Print, WhenTodo is the current time, and ActionStatus is Todo (Steps S10401 to 10407).
[0191]
FIG. 105 is a flowchart showing the SearchData processing procedure. The prototype is Void SearchData (dwUserId, poSearchData).
[0192]
Get all Job list of specified user and compare the details with the details in Search Data object. If the details match, add a node to the new list and finally return the new list (steps S10501 to 10507).
[0193]
FIG. 48 is a flowchart showing a processing procedure for a client request of the desktop server component.
[0194]
In step S4801, the server component acquires a client request and performs corresponding processing. When the request is login, first, a login verb and a remote device list are acquired, and a user password is acquired (steps S4803 to 4804). After that, an HTML page corresponding to the user is created, the user password is saved, and sent to the client component to finish the processing (steps S4805 to 4806, 4814).
[0195]
In the case of a Print a File request, the user password and the file name to be printed are acquired. Calls an external application and prints the file with the specified file name to the print file used by this application. Convert this output print file into a message object, and send the Job to the first device of the remote device. Finally, a corresponding HTML page is created and transmitted to the client component to finish the processing (steps S4807 to 4813, 4814). If the client request is “Read a Mail” or “Print a Mail”, it will be described later with reference to FIG. When the client request is “View Schedule” or “Print Schedule”, it will be described later with reference to FIG. When the request of the client is “Goto Other Device”, it will be described later with reference to FIG. The case where the client request is “logout” and “help” will be described later with reference to FIG.
[0196]
FIG. 49 is a flowchart showing a processing procedure for a request related to mail. This is a procedure when the client request is “Read a Mail” or “Print a Mail”.
[0197]
If the request is Read a Mail, first get the mail server user password and open a mail session. After reading the designated mail, the session is closed (steps S4902 to 4905).
[0198]
In the case of a Print a Mail request, the same processing as the Read a Mail request is performed, the mail is written to a file, a Job message is created, and then the Job is sent to the first device in the remote device list (step S4906). ~ 4912).
[0199]
In either case, an HTML page corresponding to the end is created, and the created page is transmitted to the client component, and the process ends (steps S4913 to 4914).
[0200]
FIG. 50 is a flowchart illustrating a processing procedure for a request related to a schedule. This represents the processing procedure of the desk server when the client request is “View Schedule” or “Print Schedule”.
[0201]
If the request is View Schedule, it is checked whether the schedule type is Daily or Monthly, and schedule data is acquired (steps S5002 to 5003). If the request is Print Schedule, perform the same process as above, write the data to a print file, create a Job message, and send the Job to the first device in the remote device list (steps S5004 to 5009) .
[0202]
In either case, a corresponding HTML page is created, the page is transmitted to the client component, and the process is terminated (steps S5010 to 5011).
[0203]
FIG. 51 is a flowchart showing a request processing procedure regarding another device. This represents a processing procedure of the desk server when the client request is “Goto Other Device”.
[0204]
If the request is Goto Other Device, get the device name and device address. Thereafter, the device is added to the remote device list, and a login verb is created (steps S5102 to 5104). Log in to the device with the Login verb, create the corresponding HTML page, and finally send the page to the client component. This process is the same as that described with reference to FIG.
[0205]
FIG. 52 is a flowchart showing a request processing procedure regarding logout and help. This represents the processing procedure of the desk server when the client request is “logout” or “help”.
[0206]
If it is a logout request, it is checked in step S5202 if the remote device list is empty. If it is empty, an opening screen page is created in accordance with the status in step S5205. If it is not empty, until the list becomes empty, the next device is logged in with login verb = Disconnect in step S5203, and the device is repeatedly deleted from the remote device list in step S5204. In other words, all devices in the remote device list are logged out. If the list becomes empty, an OpeningScreen page is created in step S5205.
[0207]
In the case of a Help request, a help context parameter is acquired and a corresponding help screen HTML page is created (steps S5206 to 5207).
[0208]
In either case, the created HTML page is sent to the client component to finish the process.
[0209]
FIG. 53 is a flowchart showing a processing procedure from the initial menu screen. FIG. 106 shows a screen example of the initial menu. If there are jobs in the print queue, they are displayed in a list on the status screen. As job information, a job name and a sender are displayed.
[0210]
In the initial menu, in step S5301, the user selects an item desired by the user. In step S5302, a selection item is determined, and a new screen is displayed according to the item.
[0211]
First, when the “new interaction” item is selected, in step S5303, the process proceeds to a new process (login process) described later with reference to FIG. 55, and the screen changes to the “login” screen (FIG. 112).
[0212]
When the “Print URL” item is selected, the screen changes to the “URL printing” screen (FIG. 107). In step S5311, if “Go” is selected by directly entering or referring to the URL, information is acquired and previewed in step S5312. In step S5313, the confirmed content is printed. Then return to the “Initial Menu” screen.
[0213]
If the “Public Info (public information)” item is selected, in step S5314, the process proceeds to the public information processing described later with reference to FIG. 54, and the screen changes to the “public information processing” screen (FIG. 110).
[0214]
When the “Goto Device (other device)” item is selected, a setting screen (FIG. 81) for accessing another device is displayed in step S5315. Thereafter, the processing in the case of “Device” for processing to access another device described with reference to FIG. 51 is performed.
[0215]
In this initial screen, a job in the print queue can be selected. To select a job, touch the button displayed in front of the desired job name. When “specific job” is selected in this way, a password input screen (FIG. 108) is displayed in step S5304. Here, when a password is input and matches the password assigned to the selected job, a processing setting screen (FIG. 109) for the job selected in the print queue is displayed.
[0216]
Subsequently, an action is selected for the job in step S5305. In step S5306, a time related to the action is set. When “Print later” is selected as the action, the printing time can be set. Here, the print time can be set by a specific date and time (absolute date and time), and can also be set by a relative date and time based on the elapsed time from the set time, such as “After 1 Hour”. For this setting, select items such as “1 hour later”, “2 hours later”, “6 hours later”, “Tomorrow”, “Tomorrow day”, “1 week later”, “2 weeks later”. Prepare it so that you can select from it. When setting an absolute date and time, the current date defaults to the current date, and when another date is selected, a calendar is popped up and the relevant date is touched and input. If necessary, the time is changed from the current time.
[0217]
When “Hold Here” is selected, a hold period is set. In this case, as in the case of printing later, the hold deadline can be specified by an absolute date and time, and a setting such as a hold period, for example, 1 hour (For 1 Hour) can be selected from the menu. In addition, when specifying the above absolute date and relative date and time, the touch keyboard may be displayed and a numerical value may be directly input, or the display value is counted up or down according to the number of times of a specific button. You may do it.
[0218]
Action is set and executed in accordance with the action and date / time item selected and set as described above. First, when “print later” is selected, in step S5308, the print job is deleted from the queue, registered in the list of pending jobs together with the print time, and the screen returns to the “initial menu” screen. Thereafter, printing is performed at the set time.
[0219]
If “hold” is selected, the print job is deleted from the queue in step S5309, the hold is set as an action together with the hold deadline, registered in the list of hold jobs, and the screen returns to the “initial menu” screen. After that, the job is held for the hold period, and canceled if nothing is done by the deadline.
[0220]
If “Pause / Restart Printing” is selected, printing is paused in step S5310, the screen returns to the “Initial Menu” screen, and “Restart (Pause / Restart Printing)” is selected later. Wait until the same button is pressed again. When “Cancel Printing” is selected, the print job is deleted from the queue, “Cancel” is recorded as an action of this job in the history, and the screen returns to the “Initial Menu” screen.
[0221]
FIG. 54 is a flowchart showing a public information processing procedure. The screen transition and the flow of processing when the “public information processing” item is selected in the initial menu are shown. First, in step S5401, a list of public information on the printer is displayed. FIG. 110 is a diagram showing an example in which a public information processing setting screen is displayed together with such a list of public information. What is displayed in this list is information having an attribute of public information (job having a public action) and can be printed without a password.
[0222]
If a specific job is selected from the list in step S5402, the process advances to step S5405 to perform processing for the selected job. If “From Other Device” is selected, the process advances to step S5415 to process the public information in the other device.
[0223]
In step S5405, a process for the selected job is selected. If “print” is selected, in step S5407, a print location, which will be described in detail later, is set for the normal job print processing, and if necessary, the print time is set, and the public information selected in step S5408 is printed. Execute. If “Preview” is selected, a preview is executed in step S5409, and the next process is selected in step S5410.
[0224]
When “Add (Make Job As Public Info. On Other Device)” is selected in step S5406 or S5410, a device for publishing is specified in order to publish the selected information on another device. Set to add the selected public information to the public list of the device. FIG. 111 is a diagram showing an example of a setting screen for publishing information on another device.
[0225]
In step S5412, a device address and a device name are set as addition destinations, and further, until when the information is disclosed, that is, a publication time limit is set. Also in this case, as described above, the publication deadline may be set as an absolute date or the publication period from the current time may be set. Also, if you do not want to publish immediately, you may set the date and time to start publishing. Also in this case, a relative setting such as “after one week” is possible. In order to limit the publication period, when displaying a list of public information, the set period may be checked and those outside the period may be excluded. Also, the list may be checked periodically, and items that have expired may be deleted from the list.
[0226]
On the other hand, in step S5415, in order to access another device, as described above, the setting screen (FIG. 81) for accessing the other device is displayed, and the device address and name are designated and accessed. . In step S5416, a public information list is acquired from the accessed device and displayed. Thereafter, processing is executed in the same manner as the device in the own device.
[0227]
FIG. 55 is a flowchart showing a login processing procedure. This is a process when a new process is selected in the initial menu. First, in step S5501, the “login” screen (FIG. 112) is displayed, the entered user identifier is checked, and if login is permitted, in step S5502, a job valid for the currently logged in user (processing is performed). Check if there are any pending jobs that have not been executed. If there is a job, in step S5504, a list of the jobs (FIG. 113) is displayed, and the process proceeds to processing for selecting a job to be described later with reference to FIG. 56 and performing an action. If there is no job, the main menu (FIG. 121) is displayed in step S5503, and the process proceeds from the main menu described later with reference to FIG.
[0228]
FIG. 56 is a flowchart showing a processing procedure for selecting a job and performing an action. This is the process when there is a valid Job for the user when the user logs in. In step S5601, a list of jobs held by the user is displayed. FIG. 113 is a diagram illustrating an example of a list of held jobs.
[0229]
Here, the held job includes a job scheduled to be printed at the set date and time, a job scheduled to be sent at the set date and time, and simply holds up to the set date and time (the time is There is a job that is canceled if nothing happens before it comes. The list displays the job name, sender or receiver, action type (print, send, hold), scheduled execution date and time of the action, and the like. These jobs are displayed in a display mode in which the type can be identified, such as changing the color or adding a different mark according to the type of action. In addition, jobs that have already been executed or jobs that have been canceled are recorded as a history by changing the status to “Executed” or “Cancel”, and these are also executed as necessary. Can be displayed in a list with the previous job. In this case, the display mode is changed depending on the status.
[0230]
Next, a target job is selected in step S5602, and a process (action) for the selected job is selected in step S5603. If the main menu is selected in step S5603, the process advances to step S5605 to perform processing from the main menu described later with reference to FIG. If search is selected, the process proceeds to step S5606, and a search process described later with reference to FIG. 65 is performed. If printing is selected, the process advances to step S5607 to perform print processing for the selected job, which will be described later with reference to FIG. If transmission is selected, the process advances to step S5610 to perform transmission processing of the selected job described later with reference to FIG. If preview is selected, the process advances to step S5608 to perform preview processing for the selected job, which will be described later with reference to FIG. If deletion is selected, the process advances to step S5609 to perform a deletion process for the selected job, which will be described later with reference to FIG. If a schedule is selected, the process advances to step S5611 to perform a schedule change process for the selected job, which will be described later with reference to FIG. If logout is selected, the process advances to step S5612 to perform the logout process described with reference to FIG.
[0231]
FIG. 57 is a flowchart showing the preview processing procedure of the selected job. This shows the flow of processing when previewing a job selected from the list of valid jobs. In step S5701, a preview of the selected job is executed. FIG. 114 is a diagram illustrating a screen display example of a job preview. In step S5702, processing for the selected job is selected.
[0232]
If printing is selected in step S5702, the process proceeds to step S5704, and print processing of the selected job described later with reference to FIG. 60 is performed. If transmission is selected, the process advances to step S5706 to perform transmission processing of the selected job, which will be described later with reference to FIG. If deletion is selected, the process proceeds to step S5705, and the selected job deletion process described later with reference to FIG. 58 is performed. If a schedule is selected, the process advances to step S5707 to perform a schedule change process for the selected job, which will be described later with reference to FIG. If cancel is selected, the process advances to step S5708 to return to the job list display described with reference to FIG.
[0233]
FIG. 58 is a flowchart showing the deletion processing procedure of the selected job. The flow of processing when deleting a job selected from the list of valid jobs is shown. First, in step S58001, the job is previewed together with the identification information of the job to be deleted, and the user is prompted to confirm the deletion. FIG. 115 is a diagram showing a deletion confirmation screen. If deletion is selected, job deletion is executed in step S5802. At this time, the processing described with reference to FIG. 97 is executed. In this case, since the selected job is selected from the list of held jobs, the action status is not executed, and the deleted job is recorded in the user history with a status of cancellation. Subsequently, the process proceeds to step S5803 to return to the job list display described with reference to FIG.
[0234]
FIG. 59 is a flowchart showing the procedure for changing the schedule of the selected job. The flow of processing when changing the schedule for a job selected from the list of valid jobs is shown. In step S5901, the current schedule to be changed is displayed. FIG. 116 is a diagram showing a setting screen for changing the schedule. In step S5902, the schedule is changed. Subsequently, the process proceeds to step S5903 to return to the job list display described with reference to FIG.
[0235]
FIG. 60 is a flowchart showing the print processing procedure of the selected job. It shows the flow of processing when printing for a job selected from the list of valid jobs. In step S6001, the original action type of the selected job is determined. If the original action is printing, print setting change processing described later with reference to FIG. 61 is executed. If the original action is not printing, a print setting menu is displayed in step S6002. FIG. 117 is a diagram showing an example of a print setting menu. Setting items include where to print (whether this device or another device), in the case of another device, the device name and address, and when to print.
[0236]
When printing with another apparatus, transmission is recorded as the type of action in the job history. Further, when printing with another apparatus, transmission processing may be transmitted by a send method described later, or may be transmitted by a transfer method.
[0237]
In step S6003, a process is selected. If printing is selected, the setting contents of the user are set in the apparatus in step S6005. If printing is to be performed immediately, printing is executed. Subsequently, the process proceeds to step S6006, and the display returns to the job list described with reference to FIG. If the preview is selected, the preview is executed in step S6007. After that, if printing is necessary, the process proceeds to step S6005. If notification is selected, the notification is set in step S6009, and the print setting menu is displayed again. FIG. 118 is a diagram showing an example of a notification setting screen. Notification setting items include the name of the person to be notified, notification medium (voice message, pop-up window, e-mail, telephone, fax, pager), notification destination (address, telephone number, etc.), notification opportunity (success, (When failure occurs, when accessing), and the time from notification trigger until actual notification. In addition, on this screen, it is possible to display a list of notifications including setting contents for each notification.
[0238]
FIG. 61 is a flowchart showing the procedure for changing the print setting of the selected job. The state transition and processing flow in the case where the selected job for the job is the original action type is shown.
[0239]
In step S6101, a print setting change menu is displayed. FIG. 119 is a diagram illustrating an example of a print setting change menu. In step S6102, processing for the job is selected. If “print now Also” is selected, in step S6104, a job having the print time of the selected job as the current time is added in addition to the selected job. When “Print Now” is selected, the printing time of the selected job is changed to the current time. Therefore, in these cases, printing is performed at the present time. If “Schedule” is selected, the schedule change menu shown in FIG. 116 is displayed in step S6106. In step S6107, the print schedule is changed using the menu. In either case, the process advances to step S6108 to return to the job list display described with reference to FIG.
[0240]
FIG. 62 is a flowchart showing the selected job transmission processing procedure. It shows the state transition and processing flow when sending to a job selected from a valid job list. In step S6201, the original action type of the selected job is determined. If the original action is transmission, transmission setting change processing described later with reference to FIG. 63 is executed. If the original action is not printing, a transmission setting menu is displayed in step S6202. FIG. 70 is a diagram showing an example of a transmission setting menu.
[0241]
In step S6203, settings are made and processing is selected. Set the destination and transmission time. These settings are the same as in the case of printing. If “Send” is selected as the process, the selected job is copied and transmitted in step S6205. In this case, the selected job remains in the job list. On the other hand, if “Transfer” is selected as the process, the selected job is transmitted in step S6206, and the selected job is deleted from the job list. In either case of transmission or transfer, the process proceeds to step S6209 to return to the Job list display described with reference to FIG. If notification is selected, a notification setting screen is displayed and settings are made in step S6207. After setting, return to the transmission setting menu display to select transmission or transfer.
[0242]
FIG. 63 is a flowchart showing the procedure for changing the transmission setting of the selected job. This shows the state transition and processing flow when the original action type of the selected job is transmission.
[0243]
In step S6301, a transmission setting change menu is displayed. FIG. 71 is a diagram showing an example of a transmission setting change menu. In step S6302, processing for the job is selected. If “Send Now Also” is selected, in step S6304, a job having the transmission time of the selected job as the current time is added separately from the selected job. When “Send Now” is selected, the transmission time of the selected job is changed to the current time. Therefore, in these cases, transmission is performed at the present time. If “Schedule” is selected, the schedule change menu shown in FIG. 116 is displayed in step S6106. In step S6307, the transmission schedule is changed using the menu. In either case, the process advances to step S6308 to return to the job list display described with reference to FIG. If “Modify” is selected, a correction menu is displayed in step S6309.
[0244]
FIG. 120 is a diagram showing an example of the correction menu. At this time, a list of transmission destinations is displayed. In step S6310, addition / setting of a new transmission destination, correction (deletion, change) of the transmission destination selected from the list, change of processing to be executed at the transmission destination, change of password, change of transmission time, and the like are performed. If notification is to be set, the notification setting menu is displayed and set in step S6312, and the screen returns to the correction menu. If notification is not set, return to the transmission setting change menu.
[0245]
FIG. 64 is a flowchart showing a processing procedure from the main menu. This shows the screen transition and processing flow in the main menu. In step S6401, the main menu is displayed. FIG. 121 is a diagram showing an example of the main menu. In step S6402, a process (action) is selected.
[0246]
If logout is selected in step S6402, the process advances to step S6404 to perform the logout process described with reference to FIG. If help is selected, the process advances to step S6405 to perform the help process described with reference to FIG. If search is selected, the process advances to step S6406 to perform a search process described later with reference to FIG. If printing is selected, the process advances to step S5607 to perform print processing described later with reference to FIG. If transmission is selected, the process proceeds to step S6408, and a transmission process described later with reference to FIG. 69 is performed. If deletion is selected, the process proceeds to step S6409, and a deletion process described later with reference to FIG. 75 is performed. If instruction setting is selected, the process advances to step S6410 to execute instruction setting processing described later with reference to FIG. If a schedule is selected, the process advances to step S6411 to perform a schedule change process described later with reference to FIG. If addition of public information is selected, the process proceeds to step S6412, and public information addition processing described later with reference to FIG. 66 is performed. If another device is selected, the process proceeds to step S6413, and an access process to another device described later with reference to FIG. 80 is performed. If a desktop is selected, the process proceeds to step S6414, and a desktop access process described later with reference to FIG. 80 is performed.
[0247]
FIG. 65 is a flowchart showing the search processing procedure. This shows the flow of processing when “Search” is selected from the main menu.
[0248]
In step S6501, search conditions for searching for a job are set. Search conditions can be used by the job set time, execution time, execution state, sender, etc. The search includes jobs in the history that have been executed in addition to the pending jobs. In particular, the history can be displayed by searching on the condition that the execution state has been executed (and canceled if necessary). In step S6502, a search is executed to display a list of search results. In step S6503, a job is selected from the search result, and in step S6504, processing for the selected job is selected.
[0249]
If printing is selected in step S6504, the process advances to step S6506 to perform printing processing for the selected job described with reference to FIG. If transmission is selected, the process advances to step S6509 to perform the selected job transmission process described with reference to FIG. If preview is selected, the process advances to step S6507 to perform the selected job preview process described with reference to FIG. If deletion is selected, the process advances to step S6508 to perform the deletion process for the selected job described with reference to FIG. If a schedule is selected, the process advances to step S6510 to execute the schedule change process for the selected job described with reference to FIG. If the main menu is selected, the process advances to step S6511 to perform processing from the main menu described with reference to FIG.
[0250]
FIG. 66 is a flowchart showing a procedure for adding public information. This shows the flow of processing when “Add to Public Information” is selected. In step S6601, a job to be public information is selected from the job list. In step S6602, a menu for adding to public information (FIG. 111) is displayed, and an addition destination and a publication time limit are set. The details are the same as those described in the public information processing. However, here, the objects to be disclosed are jobs in the user's job list. After setting, if an addition is instructed in step S6603, the selected job is added to the set public information list in step S6605. If cancel is selected after the process is completed, the display returns to the main menu.
[0251]
FIG. 67 is a flowchart showing a printing processing procedure. This shows the flow of processing when “Print” is selected from the main menu.
[0252]
In step S6701, the location where the job to be printed is located is selected. FIG. 122 is a diagram showing an example of a menu screen for selecting a place where a job to be printed is located. If the current device is selected, a list of print jobs for the current device is displayed in step S6703. FIG. 123 is a diagram illustrating an example of a menu for selecting a job to be printed. In step S6704, a job to be printed is selected. In step S6705, the selected job is set for printing. This is the same as described with reference to FIG.
[0253]
If another device or desktop is selected as the job location, the device address is designated in step S6706, and the login screen is downloaded from the device at that address in step S6707. In step S6708, login is executed according to this screen. If the login is successful, the login verb is printing. As described with reference to FIG. 51, in step S6710, the menu screen for selecting the job to be printed shown in FIG. 122 is downloaded. select. When printing with the current printer, the process advances to step S6711 to perform remote print processing by the printer described with reference to FIG. When printing on the desktop, the process advances to step S6712 to perform remote print processing on the desktop. If printing is to be performed by another device, the process advances to step S6713 to perform remote printing processing by another device.
[0254]
FIG. 68 is a flowchart showing a remote print processing procedure by the printer. This shows the flow of processing after login when printing on another device is designated from the main menu and the device is the same type of printer. The processing procedure is the same as that for printing a job on the current device. However, menus and lists are downloaded from the access destination device.
[0255]
FIG. 69 is a flowchart showing a transmission processing procedure. This shows the flow of screen transition and processing when “Send” is selected from the main menu.
[0256]
In step S6901, the device, the other device, or the desktop is selected as the location where the transmission target job is located. FIG. 124 is a diagram showing an example of a menu screen for selecting a place where a job to be transmitted exists. If this device is selected, a list of jobs on the device is displayed in step S6902. FIG. 125 is a diagram showing an example of a menu for selecting a job to be transmitted. In step S6903, a job to be transmitted is selected. Thereafter, the selected job transmission process described with reference to FIG. 62 is performed.
[0257]
When another device or desktop is selected as the location of the transmission target job, the device address is designated in step S6904, and the login screen is downloaded from the device at that address in step S6905. In step S6906, login is executed according to this screen. If the login is successful, the login verb is transmission. As described with reference to FIG. 51, in step S6908, the menu screen for selecting the transmission target job in FIG. 124 is downloaded. select. In the case of transmission from the printer, the process proceeds to step S6909, and remote send processing by the printer described with reference to FIG. 72 is performed. In the case of transmission from the desktop, the process proceeds to step S6910, and remote send processing by the desktop is performed. When transmitting from another device, the process proceeds to step S6911 to perform remote send processing from another device.
[0258]
FIG. 72 is a flowchart showing a remote send processing procedure by the printer. The flow of processing after login when a transmission from another device is designated from the main menu and the device is the same kind of printer is shown.
[0259]
If a job exists on the device, a list of transmission jobs is displayed in step S7202. In step S7203, a job to be transmitted is selected from the job list. In step S7204, a process is selected. Here, when the transmission process is selected, the transmission process of the selected job is performed. The procedure of this processing is the same as the transmission of the selected job on the current device described with reference to FIG. However, menus and lists are downloaded from the access destination device.
[0260]
If search is selected in step S7204, a new transmission target job is searched in step S7206. If logout is selected, the process advances to step S7207 to perform the logout process described with reference to FIG. If the main menu is selected, the display returns to the main menu display in step S7208.
[0261]
FIG. 75 is a flowchart showing the deletion processing procedure. This shows the flow of processing when delete is selected from the main menu.
[0262]
In step S7501, the device where the job to be deleted is located is selected from this device, another device, or the desktop. FIG. 73 is a diagram showing an example of a menu for selecting a device having a job to be deleted. If this device is selected, a list of jobs on the device is displayed in step S7502. FIG. 74 is a diagram showing an example of a list of deleted jobs. In step S7503, a job to be transmitted is selected. Thereafter, the deletion process of the selected job described with reference to FIG. 58 is performed.
[0263]
If another device or desktop is selected as the location of the job to be deleted, the device address is specified in step S7505, and the login screen is downloaded from the device at that address in step S7506. In step S7507, login is executed according to this screen. If the login is successful, the login verb is deleted. As described with reference to FIG. 51, in step S7509, the menu screen for selecting the job to be deleted shown in FIG. 74 is downloaded. Here, the job is selected. To do. When deleting from the printer, the process advances to step S7510 to perform remote delete processing by the printer described with reference to FIG. When deleting from a desktop, it progresses to step S7511 and performs the remote delete process by a desktop. When deleting from other devices, the process advances to step S7512 to perform remote delete processing from other devices.
[0264]
FIG. 76 is a flowchart showing a remote delete processing procedure by the printer. The flow of processing after login when a transmission from another device is designated from the main menu and the device is the same kind of printer is shown.
[0265]
If a job exists on the device, a job list is displayed in step S7601. In step S7602, a job to be deleted is selected from the job list. In step S7603, a process is selected. If the deletion process is selected, the deletion confirmation menu of FIG. 115 is displayed in step S7605, and the deletion process of the selected job is performed in step S7606. The procedure of this processing is the same as the deletion of the selected job on the current device described with reference to FIG. However, menus and lists are downloaded from the access destination device.
[0266]
If retrieval is selected in step S7604, a deletion target job is newly retrieved in step S7607. If logout is selected, the process advances to step S7608 to perform the logout process described with reference to FIG. If the main menu is selected, the display returns to the main menu display in step S7609.
[0267]
FIG. 77 is a flowchart of the instruction setting process procedure. This shows the flow of screen transition and processing when command setting is selected from the main menu. In step S7701, an instruction setting screen is displayed. FIG. 126 is a diagram showing an example of an instruction setting screen. Here, instruction execution conditions are set. Conditions include job name, device name, user name, status that triggers execution of command (when receiving job, sending, printing, status change, etc.), expiration date or duration of command (including indefinite period) ), A printer status is provided, and it is possible to set whether these are AND or OR. The current setting content is displayed as “On receiving jobs from others” shown in FIG.
[0268]
In step S7702, a process is selected. Here, if “action setting (Take Action)” is selected, the process advances to step S7704 to set an action to be performed when the set condition is satisfied. Here, printing and holding of a job can be set. Further, transmission (transfer), cancellation, etc. of the job may be set. If notification is selected, notification is set in step S7705. When the command setting is selected, the command set on the screen becomes valid. When the command deletion is selected, the command to be set on the screen is deleted. Thereafter, the process returns to the main menu in step S7707. The instruction that has passed the expiration date remains in the history as in the case of the executed job, and is deleted when a certain period passes after the expiration in the history management.
[0269]
FIG. 78 is a flowchart showing a schedule change processing procedure. This shows the flow of processing when changing the schedule is selected from the main menu.
[0270]
In step S7801, a schedule change screen is displayed, and this device, another device, or desktop is selected as the location where the job to be changed exists. FIG. 127 is a diagram showing an example of a menu for selecting a device in which a Job to be changed exists. If the current device is selected, a list of jobs on the device is displayed in step S7803. FIG. 128 is a diagram showing an example of a schedule change target Job selection screen. In step S7804, a job to be changed is selected. In step S7805, the selected job schedule described with reference to FIG. 59 is changed.
[0271]
If another device or desktop is selected as the location of the job to be changed, the device address is designated in step S7806, and the login screen is downloaded from the device at that address in step S7807. In step S7808, login is executed according to this screen. If the login is successful, the login verb is a schedule change. As described with reference to FIG. 51, the menu screen for selecting the job to be changed in FIG. 128 is downloaded in step S7810. Select a job. If the printer schedule is to be changed, the process advances to step S7811 to perform remote reschedule processing by the printer described with reference to FIG. If the desktop schedule is to be changed, the process advances to step S7812 to perform remote reschedule processing by the desktop.
[0272]
FIG. 79 is a flowchart showing the remote reschedule processing procedure. This shows the flow of processing when changing the job schedule of another device (same printer type) from the main menu.
[0273]
If there is a job on the device, a list of all jobs is displayed in step S7902. In step S7903, a process is selected. If a job is selected and a schedule change process is selected, the schedule change menu for the selected job in FIG. 116 is displayed in step S7905, and the schedule change process for the selected job is performed. The procedure of this process is the same as the change of the schedule of the selected job on the current device described with reference to FIG. However, menus and lists are downloaded from the access destination device.
[0274]
If search is selected in step S7904, a new job whose schedule is to be changed is searched for in step S7906. If logout is selected, the process advances to step S7907 to perform the logout process described with reference to FIG. If the main menu is selected, the display returns to the main menu display in step S7908.
[0275]
FIG. 80 is a flowchart showing an access processing procedure to another device. This shows the flow of processing when access to another device or access to the desktop is selected from the main menu. In step S8001, a device address is designated, and in step S8002, a login screen is downloaded from the device at that address. In step S8003, login is executed according to this screen. If the login is successful, the login verb is a device. Therefore, as described with reference to FIG. 51, in step S8005, the initial menu screen of FIG. 106 is downloaded, and the operation target device is determined. If the operation target is a printer, the process proceeds to step S8006, and other printers are processed in the same manner as the self-printer. If the operation target is a desktop, the process proceeds to step S8007, and desktop processing described later with reference to FIG. 82 is performed. If the operation target is another device, the process advances to step S8008 to process the other device.
[0276]
FIG. 82 is a flowchart showing a desktop processing procedure. It shows the screen transition of the initial screen and the flow of processing when you select your desk from Goto My Desktop from the main menu. First, in step S8201, the main menu is displayed. FIG. 129 is a diagram illustrating an example of a desktop main menu. In step S8202, a process (action) is selected.
[0277]
If file printing is selected in step S8202, the process advances to step S8204 to perform file printing processing described later with reference to FIG. If unread mail acquisition is selected, the process advances to step S8205 to perform unread mail acquisition processing described later with reference to FIG. If read mail acquisition is selected, the process advances to step S8206 to perform read mail acquisition processing described later with reference to FIG. If schedule printing is selected, the process advances to step S8207 to perform schedule printing processing. If schedule reference is selected, the process advances to step S8208 to perform schedule reference processing. If address book reference is selected, the process advances to step S8209 to perform address book reference processing. If logout is selected, the process advances to step S8210 to perform the logout process described with reference to FIG.
[0278]
FIG. 83 is a flowchart showing an unread mail processing procedure. This shows the flow of processing when an attempt is made to read unread mail by accessing his / her desk. In step S8300, an unread mail list is displayed. FIG. 85 is a diagram showing an example of an unread mail list. In step S8301, a mail to be processed is selected. In step S8302, processing for the selected mail is selected.
[0279]
If the main menu is selected in step S8302, the process returns to the desktop main menu in step S8304. If “Open” is selected, the selected mail is opened and the content is displayed in step S8305. FIG. 86 is a diagram showing a display example of the contents of mail. If the previous display or the subsequent display is selected in step S8306, the process returns to step S8305 to display the contents of the corresponding mail. When printing or deletion is selected, deletion of mail in step S8308 and printing of mail in step S8309 are executed. Even when printing or deletion is selected in step S8302, the deletion of mail in step S8308 and the printing of mail in step S8309 are executed. If print all is selected, all mails are printed in step S8310. When “read mail (Old)” is selected, read mail processing described later with reference to FIG. 84 is performed.
[0280]
Mail printing accesses your desk, retrieves mail, and prints it. As for printing, the printing destination and the like can be designated in the same manner as the above-described job printing. All mail printing accesses your desk and retrieves and prints all mail. To delete mail, access your desk and delete the mail. At that time, the deletion confirmation may be performed in the same manner as the job deletion.
[0281]
FIG. 84 is a flowchart showing a read mail processing procedure. This shows the flow of processing when an attempt is made to read a read mail by accessing his / her desk. In step S8401, an unread mail list is displayed. FIG. 87 is a diagram showing an example of a read mail list. In step S8402, a mail to be processed is selected. In step S8403, processing for the selected mail is selected.
[0282]
If the main menu is selected in step S8404, the process returns to the desktop main menu in step S8405. If “Open” is selected, the selected mail is opened and displayed in step S8406. FIG. 86 is a diagram showing a display example of the contents of mail. If the previous display or the subsequent display is selected in step S8407, the process returns to step S8406 to display the contents of the corresponding mail. When printing or deletion is selected, deletion of mail in step S8409 and printing of mail in step S8410 are executed. Even when printing or deletion is selected in step S8302, the mail deletion in step S8409 and the mail printing in step S8410 are executed. If “unread mail (Unread)” is selected, the unread mail processing described with reference to FIG. 83 is performed.
[0283]
FIG. 88 is a flowchart showing a processing procedure for file processing. This shows the flow of processing when an attempt is made to operate a file on the desktop by accessing his / her desk. In step S8801, settings for file acquisition are performed. FIG. 130 is a diagram showing an example of a setting screen for file acquisition. Here you can set the file name. In step S8802, a process to be executed for acquisition is selected.
[0284]
If search is selected in step S8802, search conditions are set in step S8803, desktop file search is executed in step S8804, and a list of files corresponding to the set conditions is displayed in step S8805. If a file list (Show All) is selected in step S8802, a list of desktop files is displayed. FIG. 131 is a diagram showing an example of desktop file list display. In step S8807, a file is selected from the search result or list display. If it is selected in this way, or if acquisition is instructed by inputting a file name in step S8802, the file is acquired from the desktop in step S8808. In step S8809, processing for this file is selected. FIG. 132 is a diagram illustrating an example of a process selection screen for an acquired file. Here, when printing is selected, the file acquired in step S8811 is printed. If transmission is selected, the acquired file is transmitted in step S8812.
[0285]
Note that the present invention may be applied to an apparatus composed of a single device or a system composed of a plurality of devices. Also, a storage medium storing software program codes for realizing the functions of the above-described embodiments is supplied to the apparatus or system, and a computer in the apparatus or system reads out and executes the program code stored in the storage medium. May be achieved.
[0286]
Further, the computer in the apparatus or system reads out and executes the program code stored in the storage medium, thereby not only directly realizing the functions of the above-described embodiments but also on the computer based on the instruction of the program code. The case where the above-described functions are realized by processing of an OS or the like that is running on is also included.
[0287]
In these cases, the storage medium storing the program code constitutes the present invention.
[0288]
【The invention's effect】
As described above, according to the present invention, there is an effect that it is possible to change the transmission timing of information waiting for transmission. In addition, there is an effect that transmission target information set with a certain transmission time can be easily transmitted at a different transmission time. Furthermore, there is an effect that the transmission destination of the information waiting for transmission can be changed.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a functional configuration of an embodiment.
FIG. 2 is a diagram showing details of a functional configuration of the present embodiment.
FIG. 3 is a diagram illustrating a flow of information corresponding to a user operation.
FIG. 4 is a diagram illustrating a flow of processing a user input as a command.
FIG. 5 is a diagram showing a flow of processing for displaying processing results and status changes to a user.
FIG. 6 is a diagram illustrating a functional relationship among a plurality of devices.
FIG. 7 is a system configuration diagram according to the present embodiment.
FIG. 8 is a functional block diagram of the printer according to the embodiment.
FIG. 9 is a flowchart showing a startup sequence when power is turned on.
FIG. 10 is a flowchart showing the operation of a client component.
FIG. 11 is a flowchart illustrating a processing procedure of a server component in response to a client request.
FIG. 12 is a flowchart illustrating a CancelAllPrinterjobs processing procedure.
FIG. 13 is a flowchart illustrating a processing procedure of GetAllPrinterjobs.
FIG. 14 is a flowchart illustrating a processing procedure of SetPrinterJobStatus.
FIG. 15 is a flowchart illustrating a processing procedure of requests “login” and “logout”.
FIG. 16 is a flowchart showing a processing procedure of requests “Goto Other Device” and “Goto Desktop”;
FIG. 17 is a flowchart illustrating a processing procedure of requests “Search”, “Help”, and “Receive Job / Receive Notification”.
FIG. 18 is a flowchart showing a processing procedure of IdAnalyze.
FIG. 19 is a flowchart showing a DUMMY processing procedure;
FIG. 20 is a flowchart illustrating a processing procedure of IdAnalyzeNotify.
FIG. 21 is a flowchart showing the processing procedure of RecieveHttpNotification.
FIG. 22 is a flowchart illustrating a processing procedure of requests “Print”, “Send”, “Delete”, “Reschedule”, and “Preview”.
FIG. 23 is a flowchart illustrating a processing procedure of PrintJob.
FIG. 24 is a flowchart illustrating a SendJob processing procedure.
FIG. 25 is a flowchart illustrating an execution procedure of transmission by SendJob.
FIG. 26 is a flowchart illustrating a CancelJob processing procedure.
FIG. 27 is a flowchart showing the SendNotification processing.
FIG. 28 is a diagram illustrating a correspondence relationship between input information for a server and processing.
FIG. 29 is a flowchart showing a processing procedure from the start of the daemon.
FIG. 30 is a flowchart showing a Notification processing procedure of a daemon module.
FIG. 31 is a diagram illustrating a relationship between a job type handled by a daemon and a corresponding process;
FIG. 32 is a flowchart illustrating a processing procedure of PrintPrinterJob.
FIG. 33 is a flowchart illustrating a Sendjob processing procedure;
FIG. 34 is a flowchart showing the processing procedure of ReceivejobData.
FIG. 35 is a flowchart showing the processing procedure of GetListOfJobAttribute.
FIG. 36 is a flowchart showing the processing procedure of PollJob.
FIG. 37 is a flowchart showing a PollNotify processing procedure.
FIG. 38 is a flowchart illustrating a CancelAction processing procedure.
FIG. 39 is a flowchart showing the EditAction processing;
FIG. 40 is a flowchart illustrating a processing procedure of EditAction.
FIG. 41 is a flowchart illustrating a RescheduleAction processing procedure.
FIG. 42 is a flowchart illustrating a RescheduleAction processing procedure.
FIG. 43 is a flowchart illustrating a RescheduleAction processing procedure.
FIG. 44 is a flowchart showing the AddNotification processing.
FIG. 45 is a flowchart showing the processing procedure of AddInstruction.
FIG. 46 is a flowchart showing the GetInstruction processing.
FIG. 47 is a flowchart showing a processing procedure of Execution Instruction.
FIG. 48 is a flowchart showing a processing procedure of a desktop server component.
FIG. 49 is a flowchart showing a processing procedure for a request related to mail.
FIG. 50 is a flowchart illustrating a request processing procedure regarding a schedule;
FIG. 51 is a flowchart showing a request processing procedure for another device;
FIG. 52 is a flowchart showing a request processing procedure regarding logout and help;
FIG. 53 is a flowchart showing a processing procedure from an initial menu screen.
FIG. 54 is a flowchart showing a public information processing procedure;
FIG. 55 is a flowchart showing a login processing procedure.
FIG. 56 is a flowchart showing a processing procedure for selecting a job and performing an action.
FIG. 57 is a flowchart showing a preview job processing procedure for a selected job.
FIG. 58 is a flowchart showing a deletion processing procedure of a selected job.
FIG. 59 is a flowchart showing a schedule change processing procedure for a selected job.
FIG. 60 is a flowchart illustrating a printing processing procedure for a selected job.
FIG. 61 is a flowchart illustrating a procedure for changing print settings of a selected job.
FIG. 62 is a flowchart showing a selection job transmission processing procedure;
FIG. 63 is a flowchart showing a procedure for changing the transmission setting of a selected job.
FIG. 64 is a flowchart showing a processing procedure from the main menu.
FIG. 65 is a flowchart showing a search processing procedure.
FIG. 66 is a flowchart showing a procedure for adding public information.
FIG. 67 is a flowchart illustrating a printing processing procedure.
FIG. 68 is a flowchart illustrating a remote print processing procedure by the printer.
FIG. 69 is a flowchart illustrating a transmission processing procedure.
FIG. 70 is a diagram illustrating an example of a transmission setting menu.
FIG. 71 is a diagram illustrating an example of a transmission setting change menu.
FIG. 72 is a flowchart showing a remote send processing procedure by the printer.
FIG. 73 is a diagram illustrating an example of a menu for selecting a device in which a job to be deleted exists;
74 is a diagram illustrating an example of a list of deleted jobs. FIG.
FIG. 75 is a flowchart showing a deletion processing procedure;
FIG. 76 is a flowchart showing a remote delete processing procedure by the printer.
FIG. 77 is a flowchart showing a command setting process procedure;
FIG. 78 is a flowchart showing a schedule change processing procedure;
FIG. 79 is a flowchart showing a remote reschedule processing procedure.
FIG. 80 is a flowchart showing an access processing procedure for another device;
FIG. 81 is a diagram showing a setting screen for accessing another device.
FIG. 82 is a flowchart showing a desktop processing procedure;
FIG. 83 is a flowchart showing an unread mail processing procedure.
FIG. 84 is a flowchart showing a read mail processing procedure.
FIG. 85 is a diagram showing an example of an unread mail list;
FIG. 86 is a diagram showing a display example of the contents of mail.
FIG. 87 is a diagram showing an example of a list of read mails.
FIG. 88 is a flowchart showing a processing procedure for file processing;
FIG. 89 is a flowchart showing the processing procedure of ResetInstructions.
FIG. 90 is a flowchart showing the DeleteAllInstructions processing sequence.
FIG. 91 is a flowchart showing the DeleteInstructions processing procedure.
FIG. 92 is a flowchart showing the GetInstructionDetails processing procedure.
FIG. 93 is a flowchart showing a Check processing procedure;
FIG. 94 is a flowchart showing a GetJobData processing procedure.
FIG. 95 is a flowchart showing the GetJobAttributes processing procedure.
FIG. 96 is a flowchart showing a GetActionAttributes processing procedure.
FIG. 97 is a flowchart showing the DeleteJob processing.
FIG. 98 is a flowchart illustrating a GetNotificationList processing procedure.
FIG. 99 is a flowchart showing the processing procedure of SetNotificationCondition.
Fig. 100 is a flowchart illustrating a processing procedure of SetNotificationCondition.
FIG. 101 is a flowchart showing a SetNotificationStatus processing procedure.
FIG. 102 is a flowchart illustrating a ClearHistory processing procedure.
FIG. 103 is a flowchart showing the DeleteAllPublicInfoJobs processing procedure.
Fig. 104 is a flowchart illustrating a process procedure of PrintPublicInfo.
Fig. 105 is a flowchart showing SearchData processing.
FIG. 106 is a diagram showing an example of an initial menu screen.
FIG. 107 is a diagram illustrating a URL print setting screen.
FIG. 108 is a diagram showing a password input screen.
FIG. 109 is a diagram illustrating a processing setting screen for a job selected in the print queue.
110 is a diagram showing a public information processing setting screen. FIG.
FIG. 111 is a diagram illustrating an example of a setting screen for publishing information on another device.
FIG. 112 is a diagram showing a login screen.
FIG. 113 is a diagram illustrating an example of a list of held jobs.
FIG. 114 is a diagram illustrating a screen display example of a job preview.
FIG. 115 is a diagram showing a deletion confirmation screen.
FIG. 116 is a diagram showing a setting screen for changing a schedule.
FIG. 117 is a diagram illustrating an example of a print setting menu.
FIG. 118 is a diagram illustrating an example of a notification setting screen.
FIG. 119 is a diagram illustrating an example of a print setting change menu.
FIG. 120 is a diagram illustrating an example of a correction menu.
FIG. 121 is a diagram illustrating an example of a main menu.
FIG. 122 is a diagram illustrating an example of a menu for selecting a place where a job to be printed exists.
FIG. 123 is a diagram illustrating an example of a menu for selecting a job to be printed.
FIG. 124 is a diagram showing an example of a menu for selecting a place where a job to be transmitted exists.
FIG. 125 is a diagram illustrating an example of a menu for selecting a transmission target job.
FIG. 126 is a diagram showing an example of an instruction setting screen.
FIG. 127 is a diagram illustrating an example of a menu for selecting a device in which a job to be changed exists;
FIG. 128 is a diagram illustrating an example of a selection screen for a job whose schedule is to be changed.
FIG. 129 is a diagram illustrating an example of a desktop main menu.
FIG. 130 is a diagram showing an example of a setting screen for file acquisition.
FIG. 131 is a diagram showing an example of a desktop file list display;
FIG. 132 is a diagram showing an example of a process selection screen for an acquired file;
FIG. 133 is a diagram showing a setting screen for setting restrictions on jobs.
FIG. 134 is a diagram showing a setting screen for setting rejection of a job.
[Explanation of symbols]
101 users
102 Client components
103 Server components
104 database
105 Daemon
201 Operation unit
202, 203 Web browser
204 Web server
205 Device manager
206 Printer
207 Request Manager
208 Command analyzer
209 Database Manager
601 Print control unit
602 control unit
603 Conversion control unit
604 Display control unit
605 Notification control unit
606 External application control unit
607 Printing Department
608 Mail control unit
701 network
702 Printer
703 Input / output operation unit
704 scanner
705 Multifunction device
706 Personal computer
801 touch panel
802 CPU
803 Printing Department
804 Communication Department
805 ROM
806 RAM
807 HDD
808 system bus

Claims (13)

Execution means for executing processing target information transmission processing and printing processing;
Processing target information storage means for storing processing target information in association with the type of processing, execution time, and execution destination;
Display means for displaying a list of processing target information stored in the processing target information storage means;
Processing target information selecting means for selecting processing target information from the list of processing target information;
Processing selection means for selecting the type of processing to be executed on the selected processing target information;
It is determined whether or not the type of the selected process matches the type of process stored in association with the process target information. If they match, the process target information storage is associated with the process target information. A storage control means for changing the setting stored in the means, and adding the type, execution timing and execution destination of the selected process in association with the processing target information if they do not match;
For the processing target information stored in the processing target information storage unit, the type of processing stored in the processing target information storage unit in association with the processing target information is determined based on the stored execution time and execution destination. And an execution control means for controlling the execution means to execute the information processing apparatus.   The information processing apparatus according to claim 1, wherein the storage control unit changes the execution timing of the selected processing target information so as to be executed immediately.   2. The time specifying means for specifying a time, wherein the storage control means changes the execution time of the selected processing target information to a time specified by the time specifying means. Information processing device.   The information processing apparatus according to claim 1, wherein the storage control unit changes the execution timing of the selected processing target information so as to be executed immediately.   The information processing apparatus according to claim 1, wherein the storage control unit can cancel execution of the selected processing target information.   A history storage unit that stores an execution history of the processing target information together with a type of processing, and the history storage unit indicates that the execution is canceled when the execution of the selected processing target information is canceled by the storage control unit; 6. The information processing apparatus according to claim 5, wherein the information processing apparatus is stored in the information processing apparatus. Processing target information storage means for storing processing target information in association with processing type, execution time and execution destination, display means, processing target information selection means, processing selection means, storage control means, and execution means An information processing method in an information processing apparatus capable of executing transmission processing and printing processing of processing target information,
A display step in which the display unit displays a list of processing target information stored in the processing target information storage unit;
A processing target information selecting step for selecting processing target information from the list of processing target information;
A process selection step in which the process selection means selects a type of process to be performed on the selected processing target information;
The storage control means determines whether or not the selected type of processing matches the type of processing stored in association with the processing target information, and if it matches , associates with the processing target information. A storage control step of changing the setting stored in the processing target information storage means, and adding the type, execution timing and execution destination of the selected process in association with the processing target information if they do not match,
The execution means stores the type of processing stored in the processing target information storage unit in association with the processing target information for the processing target information stored in the processing target information storage means. And an execution step executed based on the execution destination.   8. The information processing method according to claim 7, wherein in the storage control step, the storage control unit changes the execution timing of the selected processing target information so as to be executed immediately.   The storage control step includes a time specifying step for specifying a time, and the storage control means changes the execution time of the selected processing target information to the time specified by the time specifying step in the storage control step. The information processing method according to claim 7.   8. The information processing method according to claim 7, wherein in the storage control step, the storage control unit changes the execution timing of the selected processing target information so as to be executed immediately.   8. The information processing method according to claim 7, wherein in the storage control step, the storage control means can cancel the execution of the selected processing target information.   The storage control step includes a history storage step of storing an execution history of processing target information together with a type of processing in a history storage unit, and the storage control unit is canceled execution of the selected processing target information 12. The information processing method according to claim 11, wherein in the history storage step, the cancellation is stored in the history storage unit. A processing target information storage means for storing processing target information in association with the type of processing, execution time, and execution destination, and a computer capable of executing processing target information transmission processing and printing processing,
A display step of displaying a list of processing target information stored in the processing target information storage means;
A processing target information selection step of selecting processing target information from the list of processing target information;
A process selection step of selecting a type of process to be performed on the selected processing target information;
It is determined whether or not the type of the selected process matches the type of process stored in association with the process target information. If they match, the process target information storage is associated with the process target information. A storage control step of changing the setting stored in the means and adding the type of the selected process, the execution timing and the execution destination in association with the processing target information if they do not match,
For the processing target information stored in the processing target information storage unit, the type of processing stored in the processing target information storage unit in association with the processing target information is determined based on the stored execution time and execution destination. A storage medium storing a computer-readable program, characterized in that a program for executing the execution step is stored.

Images