JPH11120136A - Information processor, method therefor and storage medium stored with program therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow other devices to easily execute processing by giving instruction similarily to a present device. SOLUTION: This information processor is provided with a client 102 that produces a request in response to an operation from a user, sends it to the present device or a server 103 on other devices, receives operation screen information and presents it to the user, the server 103 that interprets the request, adds a job to a database 104, generates operation screen information and sends it to the client 102 and a daemon 105 which supervises the database 104, detects an executable job and executes printing, sending and notification.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus and method, and a storage medium storing the program.

[0002]

2. Description of the Related Art In a conventional information processing apparatus, a peripheral device receiving an instruction from a host device executes a process under the control of the host device.

[0003]

However, in order to set processing for the apparatus and execute the processing when the execution conditions are satisfied, especially when a plurality of processings can be executed, the execution of the processing is executed. There was a problem that control and management became complicated. Further, the processing is set for other devices,
To execute the process when the execution condition is satisfied, there is a problem that management becomes complicated. In particular, complicated control is required to execute a process for an operation on the device itself and a process instructed by another device.

[0004]

According to the present invention, a request is generated and transmitted to an information processing apparatus in accordance with an operation from a user, and operation screen information is received. Client means for presenting to a user by means of a server, server means for interpreting the request and adding processing target information to a database, generating operation screen information and transmitting it to the client means, and monitoring and executing the database Executing means for detecting and executing the processing target information.

According to another aspect, in an information processing method, a request is generated in a client unit in accordance with an operation from a user and transmitted to a server unit, and the request is interpreted and processed in the server unit. Add the target information to the database, generate the operation screen information in the server unit, transmit it to the client unit, receive the operation screen information in the client unit, present it to the user, and execute the database in the execution unit Detects and executes process target information that can be monitored and executed.

According to another aspect, a client generates and transmits a request to a storage medium capable of storing a program according to an operation from a user, receives operation screen information, and presents the operation screen information to the user. A program, a server program for interpreting the request and adding processing target information to a database, generating operation screen information and transmitting the operation screen information to the client program, and monitoring the database to detect executable processing target information. And an execution program to be executed.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram showing a functional configuration of the embodiment, and shows a relationship among a user 101, a client 102, a server 103, a database 104, and a 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.

The user 101 performs some operation on the client 1
When the request is made to 02, the client 102 generates a request corresponding to the operation and transmits it to the server 103. Server 103
Interprets the received request, exchanges it with the database 104, and performs processing such as addition / deletion of a Job and acquisition of data. As a result, if necessary, the corresponding HT
An ML 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.

Jobs stored in the database 104 are monitored by a daemon 105, and the daemon 105 executes processes such as printing, transmission, and notification corresponding to the Job whose execution conditions are satisfied.

FIG. 2 is a diagram showing details of the functional configuration of the present embodiment.

The client component 102 includes an operation unit 201 and two Web browsers 202 and 203.
The user operation performed via the operation unit 201 is the Web Brows
The request is converted into a request by the er 202 and 203 and transmitted to the server component 103.

The server component 103 is a Web Server
204, Device Manager 205, Request Manager 207,
It is composed of a Command analysis / processing unit 208. The request sent from the client component 102 is
204 received by Device Manager 205 or Req
It is passed to the uest manager 207.

A device manager 205 acquires the status of the printer 206 and controls the printer. The request manager 207 converts the request into a processing command and passes it to the command analysis / processing unit 208.

The command analysis / processing unit 208 executes processing corresponding to the specified processing command, accesses the database 104 via the database manager 209, and
Add / update.

On the other hand, Daemon 105
It accesses the database 104 via the manager 209 and checks whether there is a Job that satisfies the execution conditions, and if so, executes the corresponding processing.

FIG. 3 is a diagram for explaining a flow of information corresponding to a user operation.

The client component 102 receives a user operation as input information, generates a request,
Send to server component 103.

The server component 103 interprets the received request, exchanges it with the database 104 via the database manager 209, and performs processing such as addition / deletion of a Job and acquisition of data. In addition, the printer manager 205 exchanges data with the printer 206 via the device manager 205 to perform processing such as obtaining the status of the printer. As a result, if necessary, the corresponding display instruction (HTML
Page) and sends it to the client 102.

The client 102 receives the display command (H
TML page) to the user to encourage new operations.

The Job stored in the database 104 is monitored by the daemon 105 via the database manager 209, and executes processes such as printing, transmission, and notification corresponding to the Job whose execution conditions are satisfied.

FIG. 4 is a diagram showing the flow of processing from receiving a user's input until processing of a corresponding command is executed.

When a user performs an operation, the operation unit 201 converts the operation instruction data into corresponding operation instruction data. For example, an operation performed by the user using a keyboard or a mouse is converted into information that can be handled by the information processing device, such as a corresponding key code and mouse movement information.

After that, the Web Browser 202 receiving the converted operation instruction data 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 to “select a specific button” is created.

The Web Server 204 receiving the above request,
Pass the received data to Request Manager 207, and
The uest manager 207 converts the command 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 a button for printing" is converted to a processing command of "execute processing corresponding to selection of a button for printing" and executed. You.

FIG. 5 is a diagram showing the flow of processing up to displaying information to the user in response to the result of the actually performed processing and the change in the status of the printer.

Request manager receiving the processing result
207 passes the corresponding operation instruction data to Web Server 204. Similarly, the device manager 205 that has detected a change in the status of the printer 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, this is realized by converting information to be displayed on the screen into data such as HTML. Similarly, the status of the printer is realized by converting information to be displayed on the screen into data such as HTML.

Web Serv receiving the above operation instruction data
er 204 sends data to Web Browser 202
In the wser 202, it is displayed to the user by actually displaying it on a display operation unit such as a touch panel.

FIG. 5 is a diagram showing the flow of processing and data until information is displayed to the user in response to the result of the processing actually performed or a change in the status of the printer.

Request manager receiving the processing result
207 passes the corresponding operation instruction data to Web Server 204. Similarly, the device manager 205 that has detected a change in the status of the printer 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, this is realized by converting information to be displayed on the screen into data such as HTML. Similarly, the status of the printer is realized by converting information to be displayed on the screen into data such as HTML.

Web Serv receiving the above operation instruction data
er 204 sends data to Web Browsers 202 and 203,
b In Browser 202, an operation screen is actually displayed on a display operation unit such as a touch panel, and is displayed to the user. Web Browser203
Displays the status of the printer.

FIG. 6 shows a plurality of devices (device A and
FIG. 3 is a diagram illustrating a relationship between functions between the devices (referred to as 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. The device A and the device B have a client component 102, a server component 103, and a daemon 105, respectively. However, here, assuming that the user is on the device A side, the client component 102 of the device B is omitted.

Here, assuming that the user has performed an operation on the device A, operation information of the user is acquired by the operation unit 201 as input information, and is passed as a request to the device manager 205 and the request manager 207 of the server component 103.

The device manager 205 responds to a request from the user by acquiring the status of the printer 206 or the like. The request manager 207 controls the printer by the print control unit 601 according to the type of request, and analyzes more detailed information by the command analysis processing unit 208 to execute corresponding processing.

As a result, if necessary, the format of the information is converted by using the conversion control unit 603, and various processes are executed via the control unit 602. Here, if it is determined that job management is necessary, the database 104 is added / updated via the database manager 209, and if it is determined that display is required, display is performed by the display control unit 604.
If it is determined that notification is necessary, the notification control unit 605
Notify by

On the other hand, Daemon 105 periodically
And if there is a Job whose execution condition is satisfied, the corresponding process is executed.

If it is determined that the processing is not completed in the device A, a request is transmitted to the device B, and the request manager 207 of the device B executes the corresponding processing. For example, in the case of printing a file on the device B, the printing unit 607 executes a printing process using a corresponding application. In the case of Mail access, Mail
Access is performed by the control unit 608 using a corresponding application. In addition, it is realized by using a corresponding application such as reference to schedule information.

Further, it is possible to access the Job stored in the Database 104 of the device B.

FIG. 7 is a system configuration diagram according to this embodiment.

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 to the user and receives an instruction from the user. The scanner 704 and the multifunction device 705 also have the same input / output operation unit. The scanner 704 optically reads data printed on paper or the like, and the multifunction device 705 includes a printer 702 and a scanner.
It has 704 functions. Personal computer 7
In step 06, documents and images are created, and personal data such as user mails and schedules are managed.

FIG. 8 is a functional block diagram of the printer according to the present embodiment.

Referring to FIG. 8, 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 a character using a displayed keyboard by touching the display surface. It can be carried out. Note that a normal display and keyboard may be prepared instead of the touch panel 801.

The CPU 802 executes various programs including a processing procedure described later with reference to a flowchart, and controls each unit of the apparatus connected by the system bus 808. Printing unit 8
03 prints data on paper or the like. The communication unit 804 transmits and receives data including commands and statuses to and from a desktop, a scanner, and other printers via a network.

The ROM 805 stores fixed data and programs. The RAM 806 temporarily stores data and programs. Hard disk drive (HDD) 807
Can permanently store programs and data, and are used as the database described above. The system bus 808 is
Each unit of the above-described device is connected, and used as a medium for transmitting and receiving data, addresses, and control signals between the devices. Various programs including the processing procedures described later with reference to the flowcharts may be stored in the ROM 805 or the HDD 807.
May be loaded into the RAM 806 prior to the process or during the execution of the process as necessary.

FIG. 9 is a flowchart showing a starting sequence when the power is turned on, and shows a starting sequence when the user turns on the machine. In step S901, the user turns off the power.
When turned on, the OS starts in step S902, and then
The web server starts in S903. Next, the client starts in step S904, and finally the daemon starts in step S905.

FIG. 10 is a flowchart showing the operation of the client component. When the client starts up, a web browser object is created in step S1001, and a request is issued to the server component in step S1002 to instruct creation of an HTML page (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 in step S1004, an input from the user is waited for. Then, a corresponding process is performed according to a user input. User request exit
If so, the system is shut down in step S1006 and the process ends. If the user's request is to be processed on the client side, it is processed in step S1009, and the system again waits for the user's input. If processing should 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. After that, the system is again in a state of waiting for a user's input.

FIG. 11 is a flowchart showing the processing procedure of the server component in response to a client request.

The server component determines in step S1101
In step S1102, a request from the client is obtained, and the request is analyzed, and processing corresponding to the request is performed. OpeningScr
In response to the request to display een, the printer status is acquired in step S1104. For Cancel All Jobs, in step S1105, a function CancelA described later with reference to FIG.
Call the llPrinterJobs () function to cancel all Jobs. Step for Cancel / Pause / Restart request
In step S1106, a SetPrinterJobsStatus () function is called to set the Job to the specified Status.

In response to any of the above requests, an HTML page corresponding to the request is created in step S1107.
Sends the HTML page to the client component and ends the processing.

The case where the request is “login” or “logout” will be described later with reference to FIG. The request is `` Goto Other Devic
e "and" Goto Desktop "will be described later with reference to FIG. Requests are "Search", "Help", "Receive Job / Re
In the case of "ceive Notification", it will be described later with reference to FIG. Requests are "Print", "Send", "Delete", "Resched
ule ”and“ Preview ”will be described later with reference to FIG.

FIG. 12 is a flowchart showing the processing procedure of CancelAllPrinterjobs. The prototype is DWORD
CancelAllPrinterjobs ().

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. A specific printer is opened in step S1202, and the status of each Job is set to cancel in step S1203. Then, in step S1204, the printer is closed. Do this until all Jobs are set to cancel.

FIG. 13 is a flowchart showing the processing procedure of GetAllPrinterjobs. The prototype is Int GetA
llPrinterjobs (pInfo).

First, in step S1301, an effective printer, print server, domain, print, and provider are enumerated using the EnumPrinter () function. Step S130
Open one of the objects listed in step 2 and use the EnumJob () function in step S1303 to
b is enumerated, and the printer is closed in step S1304.
This operation is performed for all objects.

FIG. 14 is a flowchart showing the SetPrinterJobStatus processing procedure. The prototype is Int Se
tPrinterJobStatus (pPrinterName, JobId, Status).

First, in step S1401, the designated Job is acquired from the spool using the GetJob function. Step S
In 1402, a specific printer in which the job exists is opened, and in step S1403, the status of the job is set to a specified value. In step S1404, the printer is finally closed and the process ends.

FIG. 15 shows that the client request is “login”.
It is a flowchart which shows the processing procedure of the server when it is "logout".

When the request is "login", first, a login verb and a remote device list are obtained in step S1502, and a user name is obtained in step S1503. Step S15
In 04, GetUserId () is called to obtain a valid Job list for the user, and a corresponding HTML page is created in step S1505, and at the same time, details of the user and Job are stored in the hidden area in step S1506.

On the other hand, in the case of a Logout request, step S1
At 507, it is checked whether the remote device list is empty.
Create an en page. If not empty, login verb = Di in the next device in step S1508 until the list is empty.
Login with sconnect and repeat deleting the device from the remote device list in step S1509. That is, all the devices in the remote device list are logged out. When the list is empty, Openin
Create a gScreen page.

In both cases of Login and logout, the created page is transmitted to the client component in step S1511, and the process ends.

FIG. 16 shows that the client request is “Goto Oth
13 is a flowchart illustrating a processing procedure of the server when the server is “er Device” and “Goto Desktop”.

If the request is Goto Other Device, the device name and device address are acquired in step S1602. G
In the case of oto Desktop, the desktop address is obtained in step S1603. Then, in step S1604, the device is added to the remote device list, and in step S160
5. Create a login verb. Login verb is Device or Des
In the case of ktop, Print, Send, Delete, Reschedule, log in to the device by the Login verb in step S1607, and in the case of Device or Desktop, create the opening screen HTML page in step S1608, and
For end, Delete, Reschedule, step S1609,
1610, 1611, 1612, PrintJob, Send Job, De
Create an HTML page for lete Job and Reschedule Job screens. If the login verb is Disconnect, the user logs out of the device in step S1613 and returns to step S1614.
To remove the device from the remote device list,
In step S1615, an HTML page for the opening screen is created. Finally, in step S1616, the page is sent to the client step component, and the process ends.

FIG. 17 shows that the client request is “Search”
It is a flowchart which shows the processing procedure of the server when it is "Help" and "Receive Job / ReceiveNotification".

In the case of a search request, a search parameter is obtained in step S1702, and a search is executed in step S1703. In step S1704, the search result HTM is obtained from the execution result.
Create an L page. In the case of a Help request, a help context parameter is obtained in step S1705, and step S170
Create the corresponding help screen HTML page in 6.
In either case, in step S1707, the generated HTML page is transmitted to the client component, and the process ends.

When the type of request is Receive Job / Notification
In step S1708, the data buffer is read, and in step S1709, if the buffer is a Receive Job,
To the IdAnalyze () function described with reference to FIG. 18, Receive Notif
ication, IdAnalyzeNotify explained in Figure 20
To finish.

FIG. 18 is a flowchart showing the processing procedure of IdAnalyze. Here, the job interpreted as line data from another device is interpreted. This Job, in addition to DB,
Executed by the daemon module.

First, in step S1801, the Demarshal function is called, demarshal is performed, and the buffer object is made valid. Next, in step S1802, the compressed data is
By decoding and expanding using the ata function,
Data is valid for each row. Dem again in step S1803
Call the arshal function to validate the message object. Finally, in step S1804, Receive described later with reference to FIG.
Call Job function (DUMMY) and add Job to DB.

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.

In practice, these functions are read from the row buffer sent by SendJob in step S1901,
Dump the temporary file in S1902. This file name is passed to the CGI module IDExtn.Exe in step S1903. This is done by reading the file name in step S1904 and acquiring data. In order to send data to the CGI application in step S1905, this module
Use et client call.

FIG. 20 is a flowchart showing the processing procedure of IdAnalyzeNotify. Interpret Notifications passed as line data from other similar devices. This noti
fication is added to the processing and notification is performed by the daemon module.

In practice, in step S2001, the Demarshal function is called, demarshal is performed, and the buffer object is made valid. Next, in step S2002, the compressed data is Unf
By decoding and expanding using the ormatData function, the data becomes effective row by row. Step S2003
Then call the Demarshal function again to enable the message object. Finally, in step S2004, the ReceiveHttpNotification function described later with reference to FIG.
Add to DB.

FIG. 21 is a flowchart showing the processing procedure of ReceiveHttpNotification. The prototype is Vo
id CIDAction :: RecieveHttpNotification (poNotify).

This function is for receiving a notification sent by the HTTP protocol. Even if the device does not support the requested notification method, the target device can be finally notified using the intermediate device.

In step S2101, the receiver name and address of Notification and the notification method are checked. In step S2102,
Determine if this device is the intended device to receive notifications or only acts as a waypoint to pass notifications to other devices.

If this device is the final target value, a temporary file is created in step S2103, and
At 2104, a notification message is written therein.
Also, in step S2105, f
Create and overwrite the ixed file "pollfile" (the file that the daemon polls). In step S2107, the command line parameters of the notification module (module for displaying and creating a message) are specified in this file, and the notification is performed using the notification method specified in step S2107.

If this device is an intermediate device,
In step S2108, it is checked whether this device has a capability of issuing a notification.
Notificati to the specified device in the specified way
Send on. If the device does not have the capability to issue a notification, the notification is sent to another intermediate point via the HTTP protocol in step S2112.

FIG. 22 shows that the client's request is “Prin
It is a flowchart which shows the processing procedure of the server when it is "t""Send""Delete""Reschedule""Preview".

In the case of these five requests, first, in step S2201, the user ID, JobID, and ActionID are obtained.

In the case of a Print request, in step S2203, the printing time and location are obtained, and in step S2204, a notification list is obtained. In step S2205, the function PrintJob () is called to execute printing.

In the case of a Send request, the transmission time and location are obtained in step S2206, and a notification list is obtained in step S2207. In step S2208, the function SendJob () is called to execute transmission.

In the case of a Delete request, Cancel in step S2209
Call the lAction () function and delete the Job.

In the case of a Reschedule request, at step S2210 R
Call the escheduleAction function to change the schedule.

In the case of a Preview request, the form
Convert Job to JPG or GIF format using at conversion library.

In all of the above requests, step S2212
Then, a corresponding HTML page is created, the HTML page is transmitted to the client component in step S2213, and the process ends.

FIG. 23 is a flowchart showing the processing procedure of PrintJob. The prototype is void CIDAction :: P
rintJob (ActionId, NotifyList). The input parameters are the specified Action ID and the user's Notification setting list, and the Job is printed immediately on this device.

When the Action ID is Print / Hold, the Action attributes (Print time, Notification, etc.) are modified to the current time and a new Notification. When ActionID is Send,
A new Action is created in the DB. This is the other PrintActi associated with this Job that this user is holding
Depends on whether on is present. After the Job is printed, the ActionStatus will be "done" and this Action will be part of the user's History.

First, in step S2301, a record is pulled out and the details of the action are checked. Step S2302
Then, it is checked whether the old Action is held, and this information is stored in step S2303. In step S2304, this Ac
Get JobData required for the option. In step S2305, the entry in the database is modified to be “printing”. This is to prevent the daemon module from executing this record.

In steps S2307 and S2308, a new record is created or an existing record is modified. For example, if the previous action was Print / Hold, the record was modified, and if the previous action was Send,
If there is no PrintAction for which the user is holding the Job, a new record is created. new / old ActionID
Is returned (subject to conditions).

In step S2309, the Notificatio is unconditionally
n Status becomes False. In step S2310, this newAct
Add notification to ionID and change user type to "Don't
care "(ie, there is no sender or recipient).

In step S2311, the job is sent to the print queue for printing using Spooler API Calls.
In step S2312, the entry is corrected as “printing succeeded” or “end”. In step S2313, the Print ActionStatu
Set NotificationStatus according to s.

FIG. 24 is a flowchart showing the processing procedure of SendJob. The prototype is Void CIDAction :: Se
ndJob (bsendjobToDatabase, ActionId, roJobMessage).

A new Job is transmitted to a specified “existing” Job or a specified receiver / device list. The transmission sends one copy to one device. In this case, if there are multiple receivers, it means that a copy of the Job is shared. Since information of all other receivers is also sent, Jo from other devices
It is also possible to access b. Job is sent using the HTTP protocol.

In practice, in step S2401, it is checked whether the Job has an ActionId or a new Job. ActionId
If exists, in step S2402, the attribute of the Action is acquired, and in step S2403, the Action type is set to Hol.
Check if it is d. If it is a Hold Job, the information that the Hold Job has been accessed is stored in step S2404.

Next, when this information is specified to go to the DB, in step S2406 SendJob () is called, and
Store all information about the sender (sender, receiver, etc.) in the DB. Then, in step S2407, the time is checked to determine whether or not to transmit “now”. If not, the process is terminated and the daemon module waits for transmission. When sending now, in step S2408,
Execute transmission and end.

FIG. 25 is a flowchart showing a procedure for executing transmission by SendJob ().

First, EditAction () is called, and ActionStatus
Is set to active. Next, it processes the list of receivers to get the user name, device name, and device URL address. Format conversion is performed for the receiver device. This is performed using a suitable image conversion library. The message data is converted into a byte string, and further compressed and encoded. This data is transmitted using the HTTP protocol, and the ActionStatus is set to done. Action is added as a part of the user's history, and notification status is set to success / f depending on the transmission status.
Set to ail. Job accessed from Held List j
Set Status to indicate ob (Step S250
1-2511).

FIG. 26 is a flowchart showing the CancelJob processing procedure. The prototype is Void CIDAction ::
CancelJob (dwActionId).

This function cancels the specified Action. Specifically, in step S2601, Actio
Get the attribute of n, read the CancelAction () function,
Mark ion as canceled. If the Action is in the Hold list, it is added to part of the user's history in step S2603, and if it is part of the user's history, the entry is deleted in step S2604. If the Action is Hold, in step S2606, n
The otification condition is set to “Accessing Hold Job”. If the user is a receiver on this device, the process ends as it is. If the user is on another device, the user logs in to this device in step S2608, and in step S2609, sets details for the cancel action. In step S2610, a SendJob () function is called to send this information to the actual device, and the transmission is executed. As a result, the action is canceled.

FIG. 27 is a flowchart showing the SendNotification processing procedure. The prototype is Void CIDAc
tion :: SendNotification (dwActionId).

This function is a function for performing actual notification. Notification types, such as Popup, notify 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, the notification is sent to the specified intermediate device and retransmitted. This function is only performed when the "now" nitification must be sent. In this case, NotificationStatus is Do
Set to ne so that the daemon module does not poll.

In practice, first, in step S2701, the notification method is checked. If the notification method is a popup window or a voice message, data is transmitted using the http protocol in step S2703. If the method is telephone, etc., step S2
In step 705, it is checked whether the device has a notification capability. If the device has the capability, in step S2704, notification is performed by the designated method. If the device does not have the capability, an intermediate point is checked in step S2706. This waypoint supports the specified publishing mechanism. Step S2
At 707, the notification message and its details are transmitted to the intermediate device using the HTTP protocol. Email, fax,
It can also respond to pagers.

FIG. 28 is a diagram showing the correspondence between information input to the server and processing. The corresponding processing is summarized.

Here, Print Job, Send Job, Cancel Jo
b, Send Notification, Receive HTTP Notification
Is controlled by the control unit 602. This module is the main module at the back end of the printer, "Print Job now, right now.""Print Job later, now.""Job right away, right now." Print. "
"Print the Job later in a different place.""Send the Job to another device now or later.""Change the schedule.""Cancel the Job Action." Set the type (voice, pop-up window, phone, E-mail, fax), "Receive notification", "Get or set device status".

This module covers the DB module in such a way that the DB and its calls are transparent to the modules (GUI module, Daemon module, etc.) that use it.

FIG. 29 is a flowchart showing a processing procedure from the start of the daemon 105.

The daemon module 105 continually polls the DB and files, and executes registered actions and operations to be executed later. In all of these cases, an entry is created in the DB.

First, in step S2901, a thread for performing 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 S2902).
905).

If the Action is Print, step S
In 2906, the printing is executed by calling the PrintJob () function. Acti
If on is Send, in step S2908, Construct
After calling SendMessage () and creating a message, the SendJob () function is called in step S2909 to execute transmission.

If Action is Hold, step S2
Call CancelJob () function in 907 to cancel Job.

After these processes, at step S2910 notif
Examine ication.

FIG. 30 shows the notification of the daemon module.
It is a flowchart which shows a processing procedure.

First, in step S3001, it is determined whether there is a notification to be issued from this device by the function Po.
Check by calling llNotify (). Noti to be issued
If fication exists, in step S3002, SendN
Read the otification () function and issue a notification. Notificat
If there is no ion, the existence of the application file is checked in step S3003.

If the file exists, step S3
At 005, after reading the command line parameters from this file, delete this file. Launch the ShowNotify.Exe module and pass command line parameters.

Finally, in the case of PullPrint, step S
In step 3007, the PrintOcx.EXE file is started. In the case of Schedule, the DataDumo.Exe file is started in step S3008.

FIG. 31 is a diagram showing the relationship between the type of job handled by the daemon and the corresponding process.

FIG. 32 is a flowchart showing the processing procedure of PrintPrinterJob. The prototype is Int PrintP
rinterJob (pPrinterName, pDocumentName, pVoid, Bufsiz
e).

This function prints that the Job is spooled in the printer. Actually, the designated printer is opened, the fact that the Job is spooled to the printer is notified, the data is written to the printer, and the printer is closed (step S3201).
~ 3204).

FIG. 33 is a flowchart showing the Sendjob processing procedure.

In step S3301, it is checked whether the job to be sent is new or existing in the database. If the job is a new job, its details are added to the database in step S3303. In step S3311, the job Sen
Check der and Receiver in the same way. 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.

When an existing job is sent, the action to Sender is checked. If the Action is Send and the status is Todo or Active, change the Action's Whentodo time to the new time when the JobMessage was created.
In step S3313, if the Action is Send and has already been executed, a new Action is added to the database. Ac
If Option is not Send, Ac entered in this job
is created in the database.

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. Acti
When on is Hold and ActionStatus is Todo, Send Action
And change the WhenTodo time to the new time when the JobMessage was created. If ActionStatus is not Todo, create a new record with Action as Send and
Set TodoTime to the new time specified in JobMessage.

FIG. 34 is a flowchart showing the processing procedure of ReceivejobData.

First, in step S3400, "Deny Jobs From"
Look at the check item "Person / Device", and if the job is from the sender set here, step S341
At 7, reject the job. This item is set by the administrator.

FIG. 134 is a diagram showing a setting screen for setting rejection of a job. In the figure, "Deny Jobs Fro
An identifier of a user to be denied is set in "m Person". A device to be denied is set in "Deny Jobs From Device". Further, as described in the instruction setting described later with reference to FIG. I do.

The expiration date and the type of processing to be rejected may be set. Looking at the check items set as described above, the Jo
The permission / non-permission of the reception of b is determined, and if permitted, the reception processing is performed.

It is assumed that the received job is a new job or an existing job.

If a new job is received, a new entry is added to the job details in step S3402. S
If the ender does not exist, an entry of the Sender is added in step S3404. Action and Notificatio in step S3405
Also add ns. If Sender exists, step S3
Add notifications at 406. If there is no Receiver, it is added in step S3408. Step S3409
Then add the Receiver action.

If an existing job is received, check the job's Receiver. If Receiver exists,
When having the same Action as received,
The Action status is canceled and a new record is created. If the Action on the Receiver has a different Action than the one received, the new entry will be
Added for Notifications may also be added in some cases. Action status is set to Todo, except when Usertype is different.

FIG. 35 is a flowchart showing the processing procedure of GetListOfJobAttribute.

Check all jobs of the user at the specified location and return all details of the job of the user. There are two jobs, Heldjobs and 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).

FIG. 36 is a flowchart showing the processing procedure of PollJob.

When the User type is Receiver and the ActionStatus is
In Todo, search for WhenTodo is shorter than the current system time (steps S3601 to 3605). If a Job exists, the details of the Job are acquired, data is set in the ActionSet, and TRUE is returned (steps S3606 to 3608). If there is no Job, FALSE is returned (step S3609).

FIG. 37 is a flowchart showing the processing procedure of PollNotify.

When CanNotify is TRUE and WhereToNotify is TR
The UE searches for the first record in which WhenToNotify is shorter than the current system time (steps S3701 to 3705). When the record exists, get the notification details,
Data is set in NotificationSet and TRUE is returned (steps S3706 to 3708). If no record exists, FALSE is returned (step S3709).

FIG. 38 is a flowchart showing the CancelAction processing procedure.

First, a record having the specified ActionID is searched. If the record exists, the same ActionId
Is searched, and its size is checked (steps S3801 to 3804). Job whose size is set by the administrator
If smaller than SizeLimit, in step S3805, Ac
Check tionStatus. If this ActionStatus is Done or the job size is more than JobSizeLimit, Action
The status is changed to Deleted, and the record is deleted (steps S3807 to 3808). Otherwise, the action status is canceled in step S3806. Then, in step S3809, all the Notifs corresponding to the ActionID
Delete ication.

FIG. 39 is a flowchart showing the processing procedure of EditAction.

The record having the specified ActionID is searched, and when the record is found, the action status is converted into the received parameter (steps S3901 to S390).
3).

FIG. 40 is a flowchart showing the processing procedure of EditAction. The prototype is different from that described with reference to FIG.

A record having the specified ActionID is searched, and if the Action of the record matches the Action of the ActionID and the Action status is pending, the
The on status is converted into the received parameter (steps S4001 to 4006). If there is no corresponding record, a new Action is added in step S4004.

FIG. 41 is a flowchart showing the processing procedure of RescheduleAction.

A record having the specified ActionID is searched. The corresponding record is found, and the Action Status is done
If not, it converts WhenTodo to the received NewTime (steps S4101 to 4104).

FIG. 42 is a flowchart showing the procedure of RescheduleAction. The prototype is different from that described with reference to FIG.

In step S4201, a record having the specified Action ID is searched. The record is found and Us
If the erTypes match, the action status is changed to cancel, and a new record whose action status is Todo is added (steps S4201 to 4204). If the record is not found, check for the existence of the user. If user is found, pick UserID. If not, add new user and pick UserID. This UserID
(Steps S4206-420)
9).

FIG. 43 is a diagram showing the processing procedure of RescheduleAction. The prototype is different from that described with reference to FIGS.

Search for a record having the specified ActionID. When the record is found, check the Action status and Action. Action matches ActionID,
If the Action status is pending and not completed, change the WhenTodo time to a new time. All Notificati of ActionID
Delete on and add a new Notification (Step S43
01-4302, 4304-4308). If the record is not found, in step S4303, a new action whose action status is Todo is added, and the WhenTodo time is changed to a new time.

FIG. 44 is a flowchart showing the processing procedure of AddNotification.

Add a new record to Notification. Generated From parameter
Check to create a new entry for this.

FIG. 45 is a flowchart showing the processing procedure of AddInstruction.

When a ReceiveJob or SendJob occurs, the setting of Instruction is called up. First, in step S4501, the existence of the specified UserId on the database is confirmed, and if not, the process ends. If it exists, a record is obtained from the instruction list in step S4502, and a new instruction is added to this user in step S4503.

Instruction is the Instructi of the database.
Add Instruction to the on table. Associated Action
And the Notification given when the Instruction is satisfied
Is reflected in the Action table and the Notification table (steps S4504 to 4506).

In both the case of the Receive job and the case of the Send job, when the instruction for generating them is satisfied, a record acting as a template for generating a new Action and a new Notification is added to the Action table and the Notification table.

FIG. 46 is a flowchart showing the GetInstruction processing procedure.

This function is composed of ReceiveJobData and SendJobDa
Called by ta. First, in Step 4601, Instruct
Action type is Recei for all records in the ion table
Check if it is ve or Send, and the specified Action
Get all instructions of type In step S4602, JobMess
Check the details in age (values set as instructions) and use these values to see if the instruction can or cannot be executed. To check the validity of Instruction, a check function (described later) is used. Instruction
Is valid, the Id is added to the list in step S4603, and in step S4603, when processing has been completed for all instructions, a list of finally valid InstructionId is returned.

FIG. 47 is a flowchart showing the processing procedure of ExecutionInstruction. This function is called ReceiveJo
Called by bData and SendJobData. Find the records in the Action and Notification tables. These records are executed in accordance with 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).

Dummy a set by instruction
Search the Action table for ction. These d
A new appropriate record is added based on the ummy actions, and the action is executed.

Dummy n set by Instruction
Search for otification. These dummy notif
new appropriate records are added based on the ication, and n
otification is performed.

FIG. 89 is a flowchart showing the processing procedure of ResetInstructions. The prototype is Void Res
etInstructions (dwUserId, pInstructionList).

First, all commands of the specified UserId are searched, and the obtained command and all Acti corresponding to the command are searched.
On and Notificatioin are deleted (steps S8901 to 8905).
Then add the new instruction passed in the instruction list
(Step S8906).

FIG. 90 is a flowchart showing the processing procedure of DeleteAllInstructions. The prototype is Void
DeleteAllInstructions (dwUserId).

Search for all instructions of the specified UserId,
Searched command and all Action, N corresponding to the command
The otificatioin is deleted (steps S9001 to 9005).

FIG. 91 is a flowchart showing the DeleteInstructions processing procedure. The prototype is Void Del
eteInstructions (dwInstructionId).

The instruction of the designated InstrumentId is searched, and the searched instruction and Action, Not corresponding to the instruction are searched.
The ificatioin is deleted (steps S9101 to 9104).

FIG. 92 is a flowchart showing the processing procedure of GetInstructionDetails. The prototype is Void
GetInstructionDetails (dwUserId).

The command of the designated UserId is searched, and the searched command and the Action, Notificatioi corresponding to the command are searched.
The details of n are returned as a list (steps S9201 to 9208).

FIG. 93 is a flowchart showing the Check processing procedure. The prototype is Bool Check (nJobChk,
JobNameConnector, nDeviceChk, DeviceConnector, nPe
rsonChk, PerconConnector, nTimeChk, TimeConnector,
nStatusChk, nStatusCode).

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).

FIG. 94 is a flowchart showing the GetJobData processing procedure. The prototype is Void GetJobData
(dwJobId, poJobMessage).

The job of the designated JobId is searched, and the details of the Job are set in the JobMessage (steps S9401 to 9403).

FIG. 95 is a flowchart showing the processing procedure of GetJobAttributes. The prototype is Void GetJo
It is bAttributes (dwJobId, poJobMessage).

[0171] The Job of the specified JobId is searched, and the details of the Job are set in JobMessage. Job Sender and Receive
The details of r and the details of the related Action are searched, and the details are set in JobMessage (steps S9501 to 9505).

FIG. 96 is a flowchart showing the processing procedure of GetActionAttributes. The prototype is Void G
etActionAttributes (dwActionId, poActionMessage).

An action of the specified ActionId is searched, and Ac is retrieved.
Set the Action details in the ActionMessage. Also Send of Job
The user names and addresses of er and Receiver are Sender and Recei
Set to ver's ActionMessage (steps S9601 to 960
Five).

FIG. 97 is a flowchart showing the DeleteJob processing procedure. The prototype is Void DeleteJob (d
wUsrLd, dwJobId).

In step S9701, an action of the specified UserId having the specified JobId is searched. If an action exists, 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.

If ActionStatus is already Done or Canc
If it is el, in step S9705, the Action and
Delete all relevant Notifications. Step S97
U other than the specified UserId with the specified JobId in 06
Check if there is an action of serId, if not, in step S9707, the specified UserI with the specified JobId
It is checked whether all the actions of d are already Done or Canceled. If there is no other user's action and all the actions are already Done or Canceled, step S9708
Then, delete the record of this Job from the Job table.

FIG. 98 is a flowchart showing the GetNotificationList processing procedure. The prototype is Void G
etNotificationList (nGeneratedFrom, dwId).

The designated generation location (Action / Instructi
on) and search all Notifications with the specified Id, add their details to the list, and return the list (steps S9801-9804).

FIG. 99 is a flowchart showing the SetNotificationCondition processing procedure. The prototype is Vo
id SetNotificationCondition (nGenetaredFrom, dwId, nR
esult).

Generated from the specified location (nGenerateFrom)
Searches for Notifications with the specified Id, and if created with the specified value (nResult), sets the WhereToNotify to TR
FALSE if not created with specified value in UE
(Steps S9901 to 9905).

FIG. 100 is a flowchart showing the SetNotificationCondition processing procedure. The prototype is
Void SetNotificationCondition (nGenetaredFrom, dwId,
bCanNotifyFlag, nDummy).

The designated Notificati generated from the designated location
Search for Notifications with onId, and set CanNotifyFlag to the specified value (bCanNotifyFlag) (steps S10001-1
0003).

FIG. 101 is a flowchart showing the SetNotificationStatus processing procedure. The prototype is Void
SetNotificationStatus (dwNotificationId, bNotifica
tionStatus).

Notifica with specified NotificationId
Search for Option and set Notification Status to the specified value. (Steps S10101 to 10103).

FIG. 102 is a flowchart showing the ClearHistory processing procedure. The prototype is Void ClearHi
story ().

First, in step S10201, the Action Status
And search for Done, Cancelled, Ignored, and Deleted Actions. For each of the obtained Actions, Action S
If tatus is a job of Done, the execution time is checked in step S10204. Otherwise, step S10205
Then, check the WhenTodo time. In step S10206,
These times are compared with the retention time limit of the history (Hostory). 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 one month (1 Month). As a result of the comparison, if the holding time has elapsed from the execution time or the scheduled execution time, the Action and the Job are deleted in step S10207.

FIG. 103 is a flowchart showing the processing procedure of DeleteAllPublicInfoJobs. The prototype is Vo
id DeleteAllPublicInfoJobs ().

Searching all PublicInfo Jobs, the ActionStat
Set us to ActionCancel (steps S10304-1030
Four).

FIG. 104 is a flowchart showing the processing procedure of PrintPublicInfo. The prototype is Void Print
PublicInfo (dwActionId).

Search for the Action of the specified ActionId,
Check if there is a PublicInfoJob. Add a new Action if it exists. This Action is Public
In Info, Action is Print, WhenTodo is current time, ActionSta
Set the action so that tus is Todo (step S104
01-10407).

FIG. 105 is a flowchart showing the processing procedure of SearchData. The prototype is Void SearchDat
a (dwUserId, poSearchData).

The entire Job list of the specified user is acquired, and the details are compared with the details in the Search Data object. If the details match, add a node to the new list, and finally return the new list (steps S10501 to 1050
7).

FIG. 48 is a flowchart showing a processing procedure for a client request of the server component of the desktop.

The server component determines in step S4801
Then, a client request is obtained and a corresponding process is performed. If the request is "login", first, a login verb and a remote device list are obtained, and a user password is obtained (steps S4803 to 4804). Then create an HTML page corresponding to the user, save the user password,
Send to client component to finish processing
(Steps S4805-4806, 4814).

In the case of a Print a File request, a user password and a file name to be printed are obtained. An external application is called, and a file having a specified file name is printed on a print file used by the application. This print file for output is converted into a message object, and the Job is transmitted to the first device of the remote device. Finally, a corresponding HTML page is created, transmitted to the client component, and the process ends (steps S4807 to 4813, 4814). The client's request is "Read
a Mail "and" Print a Mail "will be described later with reference to FIG. The client's request is "View Schedul
e ”and“ Print Schedule ”will be described later with reference to FIG. The client's request is "Goto Other Devic
If "e", it will be described later with reference to FIG. When the client request is “logout” and “help”,
Will be described later.

FIG. 49 is a flowchart showing a procedure for processing a request relating to mail. This is the procedure when the client request is “Read a Mail” and “Print a Mail”.

When the request is Read a Mail, first, the user password of the mail server is obtained, and a mail session is opened. After reading the specified email, close the session (steps S4902-490
Five).

In the case of a Print a Mail request, Read a Mai
l After performing the same processing as the request, write the mail to a file, create a Job message, and then send the Job to the first device in the remote device list (step S4
906-4912).

In either case, the corresponding HTML page is created at last, and the created page is transmitted to the client component (steps S4913-4914).

FIG. 50 is a flowchart showing a procedure for processing a request for a schedule. This shows the processing procedure of the desk server when the client request is “View Schedule” or “Print Schedule”.

If the request is a View Schedule, it checks whether the type of the schedule is Daily or Monthly, and acquires schedule data (steps S5002 to 5003). Request is Pri
In the case of nt Schedule, after performing the same processing as above, write the data to a print file, create a Job message, and send Jo to the first device in the remote device list.
b is transmitted (steps S5004 to 5009).

In either case, a corresponding HTML page is created, the page is transmitted to the client component, and the process ends (steps S5010 to 5011).

FIG. 51 is a flowchart showing a procedure for processing a request for another device. This shows the processing procedure of the desk server when the client request is “Goto Other Device”.

When the request is Goto Other Device, the device name and device address are obtained. Thereafter, the device is added to the remote device list, and a login verb is created (steps S5102 to 5104). The Login verb logs into the device, creates the corresponding HTML page, and finally sends the page to the client component and finishes. This process is the same as that described with reference to FIG.

FIG. 52 is a flowchart showing a processing procedure for a request relating to logout and help. This shows the processing procedure of the desk server when the client request is “logout” or “help”.

In the case of a Logout request, it is checked in step S5202 whether the remote device list is empty. If it is, in step S5205, an OpeningScreen page is created according to the status. If not, login verb = Discon to the next device in step S5203 until the list is empty
Login with nect and repeat removing the device from the remote device list in step S5204. That is, all the devices in the remote device list are logged out. When the list is empty, step S520
In 5, create an OpeningScreen page.

In the case of a Help request, a help context parameter is obtained, and a corresponding help screen HTML page is created (steps S5206 to 5207).

In both cases, the created HTML page is transmitted to the client component, and the process is terminated.

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 is a job in the print queue, a list is displayed on the status screen. As information of each job, a job name and a sender are displayed.

In the initial menu, in step S5301, the user selects his / her desired item. Step S5302
, The selection item is determined, and a new screen is displayed according to the selection item.

First, when the "new interaction" item is selected, in step S5303, the process shown in FIG.
Proceed to new processing (login processing) described later for 5
The screen changes to a “login” screen (FIG. 112).

When the “Print URL (Print URL)” item is selected, the screen changes to a “Print URL” screen (FIG. 107). In step S5311, when "Go" is selected by directly inputting or referring to the URL,
Information is acquired and previewed in S5312. Step S
At 5313, the confirmed contents are printed. Then, the screen returns to the “initial menu” screen.

[Public Info (public information)]
When an item is selected, in step S5314, the process proceeds to public information processing described later with reference to FIG. 54, and the screen transits to a “public information processing” screen (FIG. 110).

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 process of “Device” of the process of accessing another device described with reference to FIG. 51 is performed.

On this initial screen, a job in the print queue can be selected. To select a job, touch the button displayed before the desired job name. When “specific Job” is selected in this way, a password input screen (FIG. 108) is displayed in step S5304. Here, enter the password and select the selected Jo
If the password matches the password assigned to b, the processing setting screen for the job selected in the print queue (Fig. 10
9) is displayed.

Subsequently, an action for the job is selected in step S5305, and in step S5306, a time relating to the action is set. When "Print Later" is selected as the action, the printing time can be set. Here, the printing 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 “1 hour later”. For this setting, items such as “After 1 hour”, “After 2 hours”, “After 6 hours”, “Tomorrow”, “Day after tomorrow”, “After 1 week” and “After 2 weeks” Prepared so that you can select from them. If the date is set as an absolute date and time, the current date is used as a default value. To select another date, a calendar is popped up and the date is touched and input. If necessary, the time is changed from the current time.

When "Hold Here" is selected, a hold period is set. In this case as well, as in the case of printing later, the hold term can be designated by the absolute date and time, and the hold period, for example, one hour (For 1 H)
(our) can be selected from the menu. In addition, when the absolute date and time and relative date and time are specified,
A numeric value may be directly input by displaying a touch keyboard, or the displayed value may be counted up or down according to the number of times a specific button is instructed.

The Action is set and executed in accordance with the action and date and time items selected and set as described above. First, if “print later” is selected, step S5308
In, the print job is deleted from the queue and registered in the list of pending jobs along with the print time.
Return to the screen. Thereafter, at the set time, printing is performed.

If "Hold" is selected, in step S5309, the print job is deleted from the queue, hold is set as an action together with the hold time limit, registered in the hold job list, and the "initial menu" screen is displayed. Return to After that, the Job is suspended during the suspension period, and is canceled if no action is taken by the deadline.

Also, “Pause / Resta”
If “rt Printing” is selected, in step S5310, printing is temporarily stopped, the screen returns to the “initial menu” screen, and “restart (Pause / Restart) is performed later.
rt Printing) ”is selected (the same button is pressed again). "Cancel Print (Canc
el Printing) is selected, the print job is deleted from the queue, “cancel” is recorded in the history as an action of this job, and the “initial menu” is displayed.
Return to the screen.

FIG. 54 is a flowchart showing a processing procedure of public information. It shows a screen transition and a flow of processing when the “public information processing” item is selected in the initial menu. 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. The information displayed in this list is information having a public information attribute (a job having an action of disclosure), and can be printed without a password.

If a specific job is selected from the list in step S5402, the flow advances to step S5405 to perform processing on the selected job. If "From Other Device" is selected, the process advances to step S5415 to process public information in another device.

At step S5405, a process for the selected job is selected. If you select "Print",
In step S5407, setting of a printing location and a printing time if necessary, which will be described in detail later, about a normal job print process,
The printing of the public information selected in step S5408 is executed. If "preview" is selected, step S54
A preview is executed in 09, and the next process is selected in step S5410.

In step S5406 or S5410, "add (M
ake Job As PublicInfo. On Ot
her Device) ", specify a device to publish in order to publish the selected information on another device, and add a setting to add the selected publishing information to the publishing list of the device. Do. FIG.
FIG. 11 is a diagram illustrating an example of a setting screen for disclosing information on another device.

In step S5412, the address of the device and the device name are set as the addition destinations, and the time until the disclosure is made, that is, the expiration date is set. Again,
As described above, the release period may be set by the absolute date and time, or the release period from the current time may be set. If the user does not want to publish immediately, a date and time to start publishing may be set. In this case, a relative setting such as "one week later" is also possible. In order to limit the disclosure period, when the list of disclosure information is displayed, the set period may be checked and those outside the period may be excluded. Alternatively, the list may be checked periodically, and those whose period has passed may be deleted from the list.

On the other hand, in step S5415, in order to access another device, the setting screen (FIG. 81) for accessing another device is displayed as described above, and the address and name of the device are specified. Access. In step S5416, a public information list is acquired from the accessed device and displayed. After that, the process is executed in the same manner as the device in the own device.

FIG. 55 is a flowchart showing a login processing procedure. This is a process when it is selected to perform a new process in the initial menu. First, step S5501
Displays the "login" screen (FIG. 112), checks the input user identifier, and if the login is permitted, in step S5502, a job valid for the user who has just logged in (the processing has not been executed). Check if there is a job (held job). If there is a job, step S550
In step 4, the list of the jobs (FIG. 113) is displayed, and the process proceeds to a process of selecting a job and performing an action, which will be described later with reference to FIG. If there is no job, the main menu (FIG. 121) is displayed in step S5503, and the process proceeds from the main menu to be described later with reference to FIG.

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.

Here, the held job includes a job scheduled to be printed at the set date and time, a job scheduled to be transmitted at the set date and time, and simply held until the set date and time. There is a job (it will be canceled if you do nothing by that time). The list includes the job name, sender or recipient, and action type (print,
(Send, hold), scheduled action execution date and time, etc. are displayed. These jobs are displayed in a display mode in which the type can be identified, such as changing the color or attaching a different mark according to the type of the action. Note that the status of jobs that have already been executed or jobs that have been canceled can be changed by changing the status to “executed” or “cancelled”.
These are recorded as histories, and these can also be displayed in a list together with the job before execution, if necessary. In this case, the display mode is changed depending on the status.

Next, a target job is selected in step S5602, and a process (action) for the selected job is selected in step S5603. In step S5603,
If the main menu is selected, step S5605
Then, the processing from the main menu described later with reference to FIG. 64 is performed. If search is selected, step S5606
Then, 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 a 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 a selected Job, which will be described later with reference to FIG. If the preview is selected, the process advances to step S5608 to perform preview processing of the selected Job, which will be described later with reference to FIG. If deletion is selected, the flow advances to step S5609 to perform a process of deleting the selected Job, which will be described later with reference to FIG. If a schedule has been selected, the process proceeds to step S5611, and a schedule change process for the selected Job, which will be described later with reference to FIG. 59, is performed. If logout is selected, proceed to step S5612,
The logout process described with reference to FIG. 52 is performed.

FIG. 57 is a flowchart showing the preview job 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. Step S570
In step 2, a process for the selected job is selected.

If printing is selected in step S5702, the flow advances to step S5704 to make a selection J described later with reference to FIG.
Perform ob printing. If transmission is selected, the process advances to step S5706 to perform transmission processing of a selected Job, which will be described later with reference to FIG. If delete is selected, step S5
Proceeding to 705, the process of deleting the selected Job, described later with reference to FIG. 58, is performed. If a schedule is selected, step S5
Proceeding to 707, the schedule changing process of the selected Job, which will be described later with reference to FIG. If you choose to cancel,
The process advances to step S5708 to return to the display of the job list described with reference to FIG.

FIG. 58 is a flowchart showing the procedure for deleting the selected Job. J selected from the list of valid Jobs
This shows the flow of processing when deleting an ob. First, in step S58001, a preview of the job is performed 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. Here, if deletion is selected, step S5802
To delete the job. At this time, the process described with reference to FIG. 97 is performed. Here, since the selected job is selected from the list of held jobs, the action status is not executed, and the deleted job has a status of canceled and is recorded as the history of the user. Subsequently, the process advances to step S5803 to return to the display of the job list described with reference to FIG.

FIG. 59 is a flowchart showing the procedure for changing the schedule of the selected Job. It shows the flow of processing when changing the schedule for a Job selected from the list of valid Jobs. Step S5901
Displays the current schedule to be changed. Figure
116 is a diagram showing a setting screen for changing a schedule. In step S5902, the schedule is changed. Then, the process proceeds to step S5903, where J described with reference to FIG. 56 is used.
Return to the ob list display.

FIG. 60 is a flowchart showing the print processing procedure of the selected Job. J selected from the list of valid Jobs
It shows the flow of processing when printing on ob. In step S6001, the original action type of the selected job is determined. If the original action is printing, a print setting change process 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. Figure 117 shows
FIG. 6 is a diagram illustrating an example of a print setting menu. The setting items include where to print (this device or another device), in the case of another device, the device name and address, when to print, and the like.

When printing is performed by another device, transmission is recorded as the type of action in the job history. Further, when printing is performed by another apparatus, the transmission processing may be transmitted by a send method described later or may be transmitted by a transfer method.

In step S6003, a process is selected. If printing is selected, the user's settings are set in the apparatus in step S6005. If printing is to be performed immediately, printing is executed. Then, the process proceeds to step S6006, where J described with reference to FIG. 56 is used.
Return to the ob list display. If you choose preview,
A preview is executed in step S6007, and thereafter, if printing is necessary, the process proceeds to step S6005. If notification is selected, notification is set in step S6009, and the process returns to the print setting menu. FIG. 118 is a diagram illustrating an example of the notification setting screen. Notification settings include the name of the person to be notified,
Notification media (voice message, pop-up window, e-mail, telephone, fax, pager), notification destination (address, phone number, etc.), notification trigger (success, failure, access), notification trigger There is a time until notification. Further, on this screen, a list of notifications including setting contents for each notification can be displayed.

FIG. 61 is a flowchart showing the procedure for changing the print settings of the selected Job. The state transition and processing flow when the original Action type of the selected Job for the Job is print is shown.

At step S6101, a print setting change menu is displayed. FIG. 119 is a diagram illustrating an example of the print setting change menu. In step S6102, a process for the job is selected. "Print Now (Print Now A)
If “lso)” is selected, in step S6104, a job whose printing time is the current time of the selected job is added separately from the selected job. "Print at present (Print No.
If “w)” 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, step S6
At 106, the schedule change menu of FIG. 116 is displayed.
In step S6107, the print schedule is changed using the menu. In any case, subsequently, step S6108
To return to the Job list display described with reference to FIG.

FIG. 62 is a flowchart showing the transmission processing procedure of the selected Job. Job selected from the valid Job list
3 shows a state transition and a flow of processing when transmission is performed to the server. In step S6201, the original action type of the selected job is determined. When the original action is transmission, a transmission setting change process 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 illustrating an example of the transmission setting menu.

In step S6203, settings are made and a process is selected. Settings are made for the transmission destination and transmission time. These settings are the same as in the case of printing. If transmission (Send) is selected as the process, step S6205
, The selected job is copied and transmitted. In this case, the selected job remains in the job list. On the other hand, if the 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 both cases of transmission and transfer, subsequently, step S620
Proceed to 9 to return to the Job list display described with reference to FIG.
If notification is selected, a notification setting screen is displayed and setting is performed in step S6207. After the setting, the display returns to the transmission setting menu for selection of transmission and transfer.

FIG. 63 is a flowchart showing the procedure for changing the transmission setting of the selected Job. This is the selected Jo
It shows the state transition and the flow of processing when the original Action type of b is transmission.

In step S6301, a transmission setting change menu is displayed. FIG. 71 is a diagram illustrating an example of the transmission setting change menu. In step S6302, a process for the job is selected. "Send Now (Send Now Als
If “o)” is selected, in step S6304, a job whose transmission time is the current time of the selected job 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, in step S6106,
The schedule change menu of FIG. 116 is displayed. In step S6307, the transmission schedule is changed using the menu. In any case, the process proceeds to step S6308, and returns to the Job list display described with reference to FIG. If “Modify” is selected, a correction menu is displayed in step S6309.

FIG. 120 is a diagram showing an example of the correction menu. At this time, a list of destinations is displayed. Step S631
In 0, addition / setting of a new destination, modification (deletion, change) of the destination selected from the list, change of processing to be executed at the destination, change of the password, change of the transmission timing, and the like are performed. When setting the notification, the notification setting menu is displayed and the setting is performed in step S6312, and the process returns to the correction menu. If the notification is not set, the display returns to the transmission setting change menu.

FIG. 64 is a flowchart showing the processing procedure from the main menu. This shows the screen transition in the main menu and the flow of processing. In step S6401, a main menu is displayed. FIG. 121 is a diagram showing an example of the main menu. In step S6402, a process (action) is selected.

If logout is selected in step S6402, the flow 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, step S6
Proceeding to 406, search processing described later with reference to FIG. 65 is performed. If the printing is selected, the process proceeds to step S5607, and FIG.
, A printing process described later is performed. If transmission is selected, the process advances to step S6408 to perform transmission processing described later with reference to FIG. If delete is selected, step
Proceeding to S6409, a deletion process described later with reference to FIG. 75 is performed.
If the instruction setting has been selected, the flow advances to step S6410 to execute the instruction setting processing described later with reference to FIG. If a schedule has been selected, the flow advances to step S6411 to perform a schedule change process described later with reference to FIG. If the addition of public information is selected, step S6
Proceeding to 412, a process of adding public information described later with reference to FIG. 66 is performed. If another device is selected, step
Proceeding to S6413, access processing to another device described later with reference to FIG. 80 is performed. If a desktop is selected, the process advances to step S6414 to perform a desktop access process described later with reference to FIG.

FIG. 65 is a flowchart showing a search processing procedure. This shows the flow of processing when “search” is selected from the main menu.

In step S6501, search conditions for searching for a job are set. The search condition can be used by the setting time, execution time, execution state, sender, and the like of the job. The search includes not only the pending job but also the executed job in the history. In particular, a history can be displayed if a search is performed on the condition that the execution state has been executed (or, if necessary, cancelled). A search is executed in step S6502, and a list of search results is displayed. In step S6503, a job is selected from the search results, and
At 6504, a process for the selected job is selected.

If printing has been selected in step S6504, the flow advances to step S6506 to select selection J described in FIG.
Perform ob printing. If transmission is selected, the process advances to step S6509 to perform the transmission process of the selected Job described with reference to FIG. If the preview is selected, the process advances to step S6507 to perform the preview processing of the selected Job described with reference to FIG. If deletion is selected, the process advances to step S6508 to perform the process of deleting the selected job described with reference to FIG. If a schedule has been selected, the process advances to step S6510 to perform the process of changing the schedule of the selected Job described with reference to FIG. If the main menu is selected, the flow advances to step S6511 to perform the processing from the main menu described with reference to FIG.

FIG. 66 is a flowchart showing a procedure for processing for adding to the public information. This shows the flow of processing when "addition to public information" is selected. In step S6601, a job to be made public information is selected from the job list. In step S6602, a menu for adding to the public information (FIG. 111) is displayed, and the adding destination and the public expiration date are set. The details are the same as those described in the processing of public information. However, in this case, the targets to be disclosed are the jobs in the user's job list. After setting, step S66
When an addition is instructed in 03, the selected job is added to the set public information list in step S6605. After the processing is completed, if cancel is selected, the display returns to the main menu.

FIG. 67 is a flowchart showing the printing procedure. This shows the flow of processing when "print" is selected from the main menu.

In step S6701, the location of the job to be printed is selected. FIG. 122 is a diagram illustrating an example of a menu screen for selecting a location of a job to be printed. If the current device is selected, step S6703
To display a list of print jobs for the current device. Figure 1
FIG. 23 illustrates 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, printing of the selected job is set. This is the same as that described with reference to FIG.

If another device or desktop is selected as the location of the job, in step S6706
A device address is specified, and in step S6707, a login screen is downloaded from the device at that address. In step S6708, login is executed according to this screen. If you can login, login ver
Since b is printing, as described with reference to FIG. 51, in step S6710, a menu screen for selecting a job to be printed in FIG. 122 is downloaded, and a printing device is selected here. If printing is to be performed with the current printer, the flow advances to step S6711 to perform a remote print process using the printer described with reference to FIG. If printing is to be performed on the desktop, the flow advances to step S6712 to perform remote printing processing on the desktop. If printing is performed by another device, the process advances to step S6713 to perform remote print processing by another device.

FIG. 68 is a flowchart showing the remote print processing procedure by the printer. This shows the flow of processing after logging in when printing with 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, the menus and lists are downloaded from the access destination device.

FIG. 69 is a flowchart showing the transmission processing procedure. This shows the screen transition and the flow of processing when "Send" is selected from the main menu.

In step S6901, the location of the job to be transmitted is selected from this device, another device or desktop. FIG. 124 is a diagram illustrating an example of a menu screen for selecting a location of a job to be transmitted. When this device is selected, in step S6902,
View a list of jobs on the device. 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 transmission process of the selected job described with reference to FIG. 62 is performed.

If another device or desktop is selected as the location of the job to be transmitted, step S
At 6904, the address of the device is specified, and step S6905
To download the login screen from the device at that address. In step S6906, login is executed according to this screen. If the login is successful, the login verb is transmission, and as described with reference to FIG. 51, at step S6908, a menu screen for selecting a job to be transmitted in FIG. 124 is downloaded. select. When transmitting from the printer, the flow advances to step S6909 to perform remote send processing by the printer described with reference to FIG. If transmission is to be performed from the desktop, the process advances to step S6910 to perform remote send processing using the desktop. When transmitting from another device, the process advances to step S6911 to perform remote send processing from another device.

FIG. 72 is a flowchart showing the remote send processing procedure by the printer. This shows the flow of processing after logging in when transmission from another device is designated from the main menu and the device is the same type of printer.

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 transmission processing is selected, transmission processing 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, the menus and lists are downloaded from the access destination device.

If search is selected in step S7204, a new job to be transmitted is searched in step S7206. If logout is selected, step S7207
Then, the logout process described with reference to FIG. 52 is performed.
If the main menu is selected, step S7208
Then, the display returns to the main menu.

FIG. 75 is a flow chart showing the deletion processing procedure. This shows the flow of processing when selecting “delete” from the main menu.

In step S7501, the location of the job to be deleted is selected from this device, another device or desktop. FIG. 73 is a diagram illustrating an example of a menu for selecting a device including 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 illustrating an example of a list of deleted Jobs. In step S7503, a job to be transmitted is selected. Thereafter, the process of deleting the selected job described with reference to FIG. 58 is performed.

If another device or desktop is selected as the location of the job to be deleted, step S
At 7505, the device address is specified, and step S7506
To download the login screen from the device at that address. In step S7507, login is executed according to this screen. If the login is successful, the login verb is to be deleted. As described with reference to FIG. 51, in step S7509, the menu screen for selecting the job to be deleted in FIG. 74 is downloaded, and the job is selected here. I do. If it is to be deleted from the printer, the flow advances to step S7510 to perform remote delete processing by the printer described with reference to FIG. To delete from the desktop, the process advances to step S7511 to perform remote delete processing using the desktop. When deleting from another device, the process advances to step S7512 to perform a remote delete process from another device.

FIG. 76 is a flowchart showing the remote delete processing procedure by the printer. This shows the flow of processing after logging in when transmission from another device is designated from the main menu and the device is the same type of printer.

If a job exists on the device, a list of jobs 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. Here, if the deletion process is selected, the process proceeds to step S7605.
A deletion confirmation menu of 115 is displayed, and step S7606
Then, the selected job is deleted. 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, the menus and lists are downloaded from the access destination device.

If search is selected in step S7604, a new job to be deleted is searched in step S7607. If logout is selected, step S7608
Then, the logout process described with reference to FIG. 52 is performed.
If the main menu is selected, step S7609
Then, the display returns to the main menu.

FIG. 77 is a flow chart showing a procedure for setting an instruction. This shows a screen transition and a processing flow when the setting of an instruction is selected from the main menu. In step S7701, an instruction setting screen is displayed.
FIG. 126 is a diagram illustrating an example of the command setting screen. Here, the execution condition of the instruction is set. The conditions include a job name, a device name, a user name, a situation that triggers execution of an instruction (eg, when a job is received, being transmitted, when printing, and a status change), and an expiration date or a period (including an indefinite period) of the instruction. ), Printer status is provided and these AN
D or OR can also be set. `` On receiv
ing jobs from others "is displayed.

In step S7702, a process is selected. Here, “Action setting (Take Action)
If “n)” is selected, the process advances to step S7704 to set an action to be performed when the set condition is satisfied. Here, print and hold of the job can be set.
Further, transmission (transfer), cancellation, and the like of a job may be set. When the notification is selected, the notification is set in step S7705. When the instruction setting is selected, the instruction set on the screen becomes valid. If you choose to delete the instruction,
The instruction to be set on the screen is deleted. Then, in step S7707, the process returns to the main menu. An instruction whose expiration date has passed remains in the history similarly to the executed job, and is deleted when a certain period of time has passed after the expiration date in the history management.

FIG. 78 is a flow chart showing the schedule change processing procedure. This shows the flow of processing when the change of schedule is selected from the main menu.

In step S7801, a schedule change screen is displayed, and the place where the job to be changed is located is selected from this device, another device or desktop. FIG. 127 is a diagram illustrating an example of a menu for selecting a device including a Job to be changed. If the current device is selected, a list of jobs on the device is displayed in step S7803. FIG. 128 is a diagram illustrating an example of a selection screen of a job whose schedule is to be changed. Step S7804
To select a job to be changed. Step S7805
Then, the schedule of the selected job described with reference to FIG. 59 is changed.

If another device or desktop is selected as the location of the job to be changed, step S
In step 7806, the device address is specified, and in step S7807
To download the login screen from the device at that address. In step S7808, login is executed according to this screen. If the login is successful, the login verb is a schedule change, and as described with reference to FIG. 51, in step S7810, a menu screen for selecting a job whose schedule is to be changed in FIG. 128 is downloaded. Select a job. If the schedule of the printer is to be changed, step S7811 is executed.
Then, the remote rescheduling process by the printer described with reference to FIG. 79 is performed. If the desktop schedule is to be changed, the flow advances to step S7812 to perform a remote rescheduling process using the desktop.

FIG. 79 is a flowchart showing the remote reschedule processing procedure. The flow of processing when the change of the job schedule of another device (the same type of printer) is selected from the main menu is shown.

If a job exists on the device, the entire list of jobs is displayed in step S7902. In step S7903, a process is selected. If the user selects a job and selects the process of changing the schedule, in step S7905, a menu for changing the schedule of the selected job in FIG. 116 is displayed, and the process of changing the schedule of 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, the menus and lists are downloaded from the access destination device.

If search is selected in step S7904, a new job whose schedule is to be changed is searched in step S7906. If logout is selected,
Proceeding to step S7907, the logout process described with reference to FIG. 52 is performed. If the main menu is selected,
In step S7908, the display returns to the main menu.

FIG. 80 is a flow chart showing the procedure for accessing 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, the device address is specified,
In step S8002, a login screen is downloaded from the device at the address. In step S8003, login is executed according to this screen. If the login is successful, the login verb is a device.
As described above, 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 advances to step S8006 to perform processing of another printer in the same manner as the own printer. If the operation target is a desktop, the process advances to step S8007 to perform desktop processing described later with reference to FIG. If the operation target is another device, the process advances to step S8008 to perform processing of another device.

FIG. 82 is a flowchart showing the processing procedure of the desktop. Goto My Desk from the main menu
Shows the screen transition of the initial screen and the flow of processing when the user selects his / her desk on top. First, in step S8201,
Display the main menu. FIG. 129 is a diagram illustrating an example of the desktop main menu. In step S8202,
Select a process (action).

If file printing is selected in step S8202, the flow advances to step S8204 to perform file printing processing described later with reference to FIG. If acquisition of unread mail is selected, the process advances to step S8205 to perform unread mail acquisition processing described later with reference to FIG. If acquisition of read mail is selected, the flow 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 a schedule printing process. If schedule reference has been selected, the process advances to step S8208 to perform schedule reference processing. If the address book reference has been selected, the process advances to step S8209 to perform address book reference processing. If logout is selected, step S8210
Then, the logout process described with reference to FIG. 52 is performed.

FIG. 83 is a flowchart showing the unread mail processing procedure. This shows the flow of processing when the user accesses his / her desk and tries to read unread mail. In step S8300, a list of unread mail 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, a process for the selected mail is selected.

If the main menu is selected in step S8302, the process returns to the desktop main menu in step S8304. If "Open" is selected,
In step S8305, the selected mail is opened to display the contents. FIG. 86 is a diagram showing a display example of the contents of a 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. If print or delete is selected, delete the mail in step S8308 and step S8309, respectively.
Is printed. If printing or deletion is selected in step S8302,
In step S8309, the mail is deleted, and the mail is printed in step S8309. If all printing is selected, step S831
At 0, all mail is printed. "Read mail (Ol
If “d)” is selected, the read mail process described later with reference to FIG. 84 is performed.

In the mail printing, the user accesses his / her desk, obtains the mail, and prints the mail. As for printing, a print destination and the like can be designated in the same manner as in the above-described job printing. All mail printing accesses your desk to get and print all mail. To delete an email, access your desk and delete the email. At this time, confirmation of the deletion may be performed in the same manner as the deletion of the job.

FIG. 84 is a flow chart showing the read mail processing procedure. This shows the flow of processing when the user accesses his / her desk and tries to read a read mail. In step S8401, an unread mail list is displayed. FIG. 87 is a diagram illustrating an example of a list of read mails. In step S8402, a mail to be processed is selected.
In step S8403, a process for the selected mail is selected.

If the main menu is selected in step S8404, the process returns to the desktop main menu in step S8405. If "Open" is selected,
In step S8406, the selected mail is opened and its contents are displayed. FIG. 86 is a diagram showing a display example of the contents of a 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. If print or delete is selected, delete the mail in step S8409 and step S8410, respectively.
Is printed. If printing or deletion is selected in step S8302,
The deletion of the mail of No. 9 and the printing of the mail of Step S8410 are executed. When “unread mail (Unread)” is selected, the processing of the unread mail described with reference to FIG. 83 is performed.

FIG. 88 is a flowchart showing the processing procedure of file processing. This shows the flow of processing when accessing one's desk and trying to operate on files on the desktop. In step S8801,
Perform settings for file acquisition. FIG. 130 is a diagram showing an example of a setting screen for acquiring a file. Here, a file name can be set. In step S8802,
Select the process to be performed for acquisition.

If search is selected in step S8802, search conditions are set in step S8803, and in step S8804,
Perform a search for files on the desktop and step S880
In 5, a list of files corresponding to the setting conditions is displayed. In step S8802, a file list (Show Al
When l) is selected, a list of files on the desktop is displayed. FIG. 131 is a diagram illustrating an example of a list display of files on the desktop. In step S8807, a file is selected from the search result or the list display. If selected in this way, or if instructing acquisition by entering the file name in step S8802,
In S8808, the file is obtained from the desktop. In step S8809, a process for this file is selected. FIG. 132 is a diagram illustrating an example of a process selection screen for an acquired file. If printing is selected here, the file acquired in step S8811 is printed. If transmission is selected, the acquired file is transmitted in step S8812.

The present invention may be applied to an apparatus composed of a single device or a system composed of a plurality of devices. Further, a storage medium storing a program code of software for realizing the functions of the above-described embodiments is supplied to an apparatus or a system, and a computer in the apparatus or the system reads out and executes the program code stored in the storage medium. May be achieved by:

Further, the computer of the apparatus or the system reads out and executes the program code stored in the storage medium, thereby not only directly realizing the functions of the above-described embodiment, but also based on the instructions of the program code. The case where the above-described functions are realized by processing of an OS or the like running on a computer is also included.

In these cases, the storage medium storing the program code constitutes the present invention.

[0288]

As described above, according to the present invention,
There is an effect that management of setting and execution of processing is facilitated. In addition, there is an effect that it is easy to instruct other devices to execute processing in the same manner as the own device.

[Brief description of the drawings]

FIG. 1 is a diagram showing a functional configuration of an embodiment.

FIG. 2 is a diagram illustrating details of a functional configuration of the embodiment.

FIG. 3 is a diagram illustrating a flow of information corresponding to a user operation.

FIG. 4 is a diagram showing a flow of processing a user input as a command.

FIG. 5 is a diagram showing a flow of processing for displaying a processing result and a status change to a user.

FIG. 6 is a diagram illustrating a functional relationship between a plurality of devices.

FIG. 7 is a system configuration diagram according to the embodiment.

FIG. 8 is a functional block diagram of the printer according to the embodiment.

FIG. 9 is a flowchart showing a startup sequence at the time of power-on.

FIG. 10 is a flowchart showing the operation of the 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 processing procedure of CancelAllPrinterjobs.

FIG. 13 is a flowchart illustrating a processing procedure of GetAllPrinterjobs.

FIG. 14 is a flowchart illustrating a SetPrinterJobStatus processing procedure.

FIG. 15 is a flowchart showing a processing procedure of requests “login” and “logout”.

FIG. 16: Requests “Goto Other Device” “Goto Deskto”
It is a flowchart which shows the processing procedure of "p".

FIG. 17: Requests “Search”, “Help”, “Receive Job / Re
It is a flowchart which shows the processing procedure of "ceive Notification."

FIG. 18 is a flowchart illustrating 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 illustrating a processing procedure of ReceiveHttpNotification.

FIG. 22 shows requests “Print”, “Send”, “Delete”, and “Resched”
It is a flowchart which shows the processing procedure of "ule" and "Preview."

FIG. 23 is a flowchart illustrating a print job processing procedure.

FIG. 24 is a flowchart illustrating a processing procedure of SendJob.

FIG. 25 is a flowchart showing a procedure for executing transmission by SendJob.

FIG. 26 is a flowchart illustrating a CancelJob processing procedure.

FIG. 27 is a flowchart illustrating a SendNotification processing procedure.

FIG. 28 is a diagram illustrating the correspondence between input information to a server and processing.

FIG. 29 is a flowchart illustrating a processing procedure from the activation of a daemon.

FIG. 30 is a flowchart illustrating 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 illustrating a procedure of ReceivejobData.

FIG. 35 is a flowchart showing a processing procedure of GetListOfJobAttribute.

FIG. 36 is a flowchart illustrating a processing procedure of PollJob.

FIG. 37 is a flowchart showing a PollNotify processing procedure.

FIG. 38 is a flowchart showing the CancelAction processing procedure.

FIG. 39 is a flowchart showing a processing procedure of EditAction.

FIG. 40 is a flowchart showing a processing procedure of EditAction.

FIG. 41 is a flowchart showing the processing procedure of RescheduleAction.

FIG. 42 is a flowchart showing the processing procedure of RescheduleAction.

FIG. 43 is a flowchart showing the RescheduleAction processing procedure.

FIG. 44 is a flowchart showing the processing procedure of AddNotification.

FIG. 45 is a flowchart showing the processing procedure of AddInstruction.

FIG. 46 is a flowchart showing the GetInstruction processing procedure.

FIG. 47 is a flowchart showing a processing procedure of ExecutionInstruction.

FIG. 48 is a flowchart showing a processing procedure of a server component of the desktop.

FIG. 49 is a flowchart showing a processing procedure of a request for mail.

FIG. 50 is a flowchart showing a processing procedure of a request for a schedule.

FIG. 51 is a flowchart showing a processing procedure of a request for another device.

FIG. 52 is a flowchart showing a processing procedure of a request for logout and help.

FIG. 53 is a flowchart showing a processing procedure from an initial menu screen.

FIG. 54 is a flowchart showing a processing procedure of public information.

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 processing procedure of a selected Job.

FIG. 58 is a flowchart showing a deletion job procedure of a selected Job.

FIG. 59 is a flowchart showing a schedule change processing procedure of a selected Job.

FIG. 60 is a flowchart illustrating a print processing procedure of a selected Job.

FIG. 61 is a flowchart illustrating a print setting change processing procedure of a selected Job.

FIG. 62 is a flowchart illustrating a transmission processing procedure of a selected Job.

FIG. 63 is a flowchart showing a procedure for changing a transmission setting of a selected Job.

FIG. 64 is a flowchart showing a processing procedure from a main menu.

FIG. 65 is a flowchart showing a search processing procedure.

FIG. 66 is a flowchart showing a procedure for adding to public information.

FIG. 67 is a flowchart illustrating a print processing procedure.

FIG. 68 is a flowchart showing a remote print processing procedure by the printer.

FIG. 69 is a flowchart showing 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 including a Job to be deleted;

FIG. 74 is a diagram illustrating an example of a list of deleted Jobs.

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 procedure of a command setting process.

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 a procedure of an access process to 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 flow chart showing a read mail processing procedure.

FIG. 85 is a diagram showing an example of a list of unread mail.

FIG. 86 is a diagram illustrating a display example of the content of a mail.

FIG. 87 is a diagram showing an example of a read mail list.

FIG. 88 is a flowchart showing a processing procedure of file processing.

FIG. 89 is a flowchart showing the procedure of ResetInstructions.

FIG. 90 is a flowchart showing the processing procedure of DeleteAllInstructions.

FIG. 91 is a flowchart showing the DeleteInstructions processing procedure.

FIG. 92 is a flowchart showing the processing procedure of GetInstructionDetails.

FIG. 93 is a flowchart showing the Check processing procedure.

FIG. 94 is a flowchart showing the GetJobData processing procedure.

FIG. 95 is a flowchart showing the GetJobAttributes processing procedure.

FIG. 96 is a flowchart showing the processing procedure of GetActionAttributes.

FIG. 97 is a flowchart showing the DeleteJob processing procedure.

FIG. 98 is a flowchart showing the GetNotificationList processing procedure.

FIG. 99 is a flowchart showing the SetNotificationCondition processing procedure.

FIG. 100 is a flowchart showing the SetNotificationCondition processing procedure.

FIG. 101 is a flowchart showing the SetNotificationStatus processing procedure.

FIG. 102 is a flowchart showing the ClearHistory processing procedure.

FIG. 103 is a flowchart showing the processing procedure of DeleteAllPublicInfoJobs.

FIG. 104 is a flowchart showing the processing procedure of PrintPublicInfo.

Fig. 105 is a flowchart showing the processing procedure of SearchData.

FIG. 106 is a diagram showing a screen example of an initial menu.

FIG. 107 is a diagram showing 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.

FIG. 110 is a diagram showing a public information processing setting screen.

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 location of a job to be printed.

FIG. 123 is a diagram illustrating an example of a menu for selecting a job to be printed.

FIG. 124 is a diagram illustrating an example of a menu for selecting a location of a job to be transmitted.

FIG. 125 is a diagram illustrating an example of a menu for selecting a job to be transmitted.

FIG. 126 is a diagram illustrating an example of a command setting screen.

Fig. 127 is a diagram illustrating an example of a menu for selecting a device including a Job to be changed.

FIG. 128 is a diagram illustrating an example of a selection screen of 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 illustrating an example of a setting screen for acquiring a file.

FIG. 131 is a diagram illustrating an example of a list display of files on the desktop.

FIG. 132 is a diagram illustrating an example of a process selection screen for an acquisition file.

FIG. 133 is a diagram illustrating a setting screen for setting restrictions on a job.

FIG. 134 is a diagram illustrating a setting screen for setting rejection of a job.

[Explanation of symbols]

 101 user 102 client component 103 server component 104 database 105 daemon 201 operation unit 202, 203 web browser 204 web server 205 device manager 206 printer 207 request manager 208 command analysis unit 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 unit 608 Mail control unit 701 Network 702 Printer 703 Input / output operation unit 704 Scanner 705 Multi-function device 706 Personal computer 801 Touch panel 802 CPU 803 Printing unit 804 Communication unit 805 ROM 806 RAM 807 HDD 808 Temubasu

Claims (17)

[Claims] 1. A client means for generating and transmitting a request in response to an operation from a user, receiving operation screen information and presenting it to a user, and interpreting the request to add processing target information to a database. An information processing apparatus comprising: a server unit that generates operation screen information and transmits the generated operation screen information to the client unit; and an execution unit that monitors the database and detects and executes executable processing target information. . 2. The method according to claim 1, wherein the database stores the processing target information in association with an execution timing, and the execution unit executes the processing target information that has reached the execution timing as executable processing target information. The information processing apparatus according to claim 1. 3. The database stores the processing target information in association with an expiration date, and the execution unit deletes the processing target information whose expiration date has passed as deletable processing target information. The information processing apparatus according to claim 1. 4. The method according to claim 1, wherein the server generates the operation screen in an HTML format, and the client generates an operation screen in an HTML format.
2. The information processing apparatus according to claim 1, wherein the operation screen is displayed in a format. 5. The information processing apparatus according to claim 4, wherein said server means generates a status screen representing a status of the apparatus in an HTML format and transmits the generated status screen to said client means. 6. The client device according to claim 1, wherein said client means is a first browser means for displaying said operation screen in HTML format,
6. The information processing apparatus according to claim 5, further comprising a second browser for displaying the status screen in ML format. 7. The client device can transmit the generated request to a server device of another device, and can receive operation screen information from the server device of the other device. The information processing apparatus according to claim 1, wherein 8. The apparatus according to claim 1, wherein said server means is capable of receiving a request from a client means of another apparatus, and capable of transmitting operation screen information to a client means of said other apparatus. An information processing apparatus according to claim 1. 9. A request is generated by a client unit in response to an operation from a user and transmitted to a server unit. The request is interpreted by the server unit and processing target information is added to a database. Generates operation screen information and sends it to the client unit. The client unit receives the operation screen information and presents it to the user. The execution unit monitors the database and detects executable process target information. And an information processing method. 10. The database stores the processing target information in association with the execution timing, and the execution unit executes the processing target information that has reached the execution timing as executable processing target information. The information processing apparatus according to claim 9, wherein 11. The database stores the processing target information in association with an expiration date, and the execution unit deletes the processing target information that has passed the expiration date as deletable processing target information. The information processing apparatus according to claim 9, wherein 12. The server unit generates the operation screen in HTML format, and the client unit generates the operation screen in HTML.
The information processing apparatus according to claim 9, wherein the operation screen is displayed in a format. 13. The information processing apparatus according to claim 12, wherein the server generates a status screen representing the status of the apparatus in an HTML format and transmits the generated status screen to the client. 14. The client unit, comprising:
Displaying the L-format operation screen by a first browser;
14. The information processing apparatus according to claim 13, wherein the status screen in HTML format is displayed by a second browser. 15. The client unit can transmit the generated request to a server unit of another device, and can receive operation screen information from the server unit of the other device. 10. The information processing apparatus according to claim 9, wherein 16. The server according to claim 9, wherein a request can be received from a client of another device, and operation screen information can be transmitted to a client of the other device. An information processing apparatus according to claim 1. 17. A client program for generating and transmitting a request in response to an operation from a user, receiving operation screen information and presenting the request to a user, and interpreting the request and adding processing target information to a database. A program storage for storing a server program for generating operation screen information and transmitting it to the client program, and an execution program for monitoring the database and detecting and executing executable processing target information. Possible storage medium.