JP2001282663A - Device, method, and system for device management - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device, a method, and a system for device management which can make a device execute a job accompanied by various settings through simple operations. SOLUTION: A document-processing system comprises multifunction devices (101 (108) which are connected to a network 109 and perform specific document processing, a document-processing server 103 which manages specific document processing by the devices 101 (108), and clients 104 and 105 which request the server 103 to perform desired document processing. The client 104 registers setting information for making the devices 101 (108) perform the desired document processing as a template, and according to the setting information of the registered template, the document processing by the devices 101 (108) is managed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a device management apparatus, a device management method, and a device management system.

[0002]

2. Description of the Related Art With the spread of network environments in offices, OA devices such as facsimile machines, printers, and the like have been used by being connected to a network.

In such an office environment, a plurality of devices capable of facsimile transmission / reception, printing or scanning of documents, clients such as personal computers for using them, and a server for managing them are installed on the same network. And a document processing system has been constructed.

According to the above-described document processing system, a processing command for a document specified by a client is stored in a processing queue of a server and then processed by a device on a network.

[0005]

However, in the above-mentioned conventional document processing system, the operation has become complicated in recent years, and even if a series of unique jobs are not set again, various settings must be made. In addition, operability was troublesome.

[0006] A job performed by a client can be processed only by an operation on the client.
What requires processing from the device side, such as a scanning operation, requires both device setting and client setting, which is cumbersome.

[0007] For a job that can be operated from the client, if the power of the client is turned off, the power of the client must be turned on.
There is also a demand for simple operation using only devices.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and provides a device management apparatus, a device management method, and a device management system that allow a device to execute a job with various settings with a simple operation. The purpose is to provide.

[0009]

According to one aspect of the present invention, there is provided a device management apparatus for causing a device on a network to execute a requested job in response to a job request from a client on the network. Management means for managing information on the capability of the device; information managed by the management means; and generation means for generating a job template for the device based on an instruction from the client; and a generated job. It is characterized by comprising transmitting means for transmitting a template to the device, and notifying means for notifying the client or the device of information for identifying the generated job template.

According to another aspect of the present invention, there is provided a device management method for causing a device on a network to execute a requested job in response to a job request from a client on the network. A management step of managing information relating to the capability of the client; a generation step of generating a job template for the device based on information managed by the management unit and an instruction from the client; A transmitting step of transmitting the job template; and a notifying step of notifying the client or the device of information for identifying the generated job template.

Further, in order to achieve the above object, the present invention provides a device which is connected to a network and executes a job, a device management apparatus for causing the device to execute a job, and A device management system including a requesting client, a registration unit for registering setting information for causing the device to perform a desired job as a job template, and the device based on the registered job template setting information. Management means for managing the execution of a job by

[0012]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a schematic diagram showing a connection form of the document processing system in the embodiment. In the figure, 10
Reference numeral 1 denotes a multifunction device connected to a network.
A facsimile machine capable of performing scanning and printing will be described as an example. Reference numeral 102 denotes a network adapter, which is a dedicated network adapter for connecting the multifunction device 101 to a network.
The adapter 102 performs protocol processing with the document processing server on the network and data transfer processing between the multifunction device and the document processing server.

In the present embodiment, the above functions are realized by a network adapter. However, these functions can be performed by the multifunction device main body. In that case, the network adapter is unnecessary.

Reference numeral 103 denotes a document processing server, which sends an FA to an information processing apparatus (client) on the network.
FAX to provide X service and print service
It manages various service queues such as a transmission queue, a FAX reception queue, and a print queue. Reference numerals 104 and 105 denote client machines for requesting the document processing server 103 for services such as network facsimile and network print.

Reference numeral 106 denotes a file server which performs file management and the like for the entire network. 107 and 108 are another network adapter and a multi-function device connected to this system. A network 109 is described as a LAN in this embodiment.

FIG. 2 is a schematic diagram showing the configuration of the multifunction device according to the embodiment. The multifunction device (101 or 108 shown in FIG. 1)
1 includes a facsimile copy control unit that controls facsimile communication and copying of an original image, and a printer I / F control unit that controls an external I / F and interprets a printer description language and develops an image in 2002. Printer I / F control unit 2002
Is provided on an independent board, and is detachably connected to the system bus of the facsimile copy control unit 2001.

In FIG. 2, reference numeral 201 denotes a system control unit (CPU), which controls the entire multifunction device via a system bus 215. 202 is ROM
And stores a control program and a control code of the CPU 201, an operating system (OS) program, and the like. 203 is a RAM, which is an SRAM
And the like, and an ID (identifier) unique to the system of the present embodiment is stored. The RAM 203 also stores program variables, setting values registered by the operator, management data of the apparatus, and various work buffers. 2
An image memory 04 is constituted by a DRAM or the like, and stores image data.

In this embodiment, it is assumed that various programs stored in the ROM 202 are controlled by software such as scheduling and task switches under the management of the OS stored in the ROM 202.

An operation unit 205 includes various keys and LE.
D, LCD, etc., for performing various input operations by the operator and displaying the operation status of the facsimile machine. A resolution conversion processing unit 206 performs millimeter-inch resolution conversion, enlargement / reduction processing, and the like. 20
Reference numeral 7 denotes a reading control unit, which includes a CS image sensor and a document transport mechanism, optically reads a document using the CS image sensor, converts the document into electrical image data, and outputs the data. Reference numeral 208 denotes an image processing unit, and the reading control unit 20
The image data read in step 7 is subjected to various types of image processing such as binarization processing and halftone processing to output high-definition image data. The processed image data is encoded according to a predetermined encoding method via an encoding / decoding processing unit 212 described later, and is stored in the image memory 204.

Reference numeral 209 denotes an external memory, which is a recording medium such as a magnetic disk, and can store image data, data described in a printer description language, an application program executed by the CPU 201, and the like.

Reference numeral 210 denotes a communication control unit which comprises a MODEM or the like and controls modulation and demodulation of facsimile transmission / reception signals. Reference numeral 211 denotes an NCU (network control device) which sends a selection signal (dial pulse or tone dialer) to an analog communication line (PSTN) 220,
It detects a call signal and performs line control such as automatic incoming call control. When sending a facsimile, the image memory 2
The image data stored in 04 is decoded by an encoding / decoding processing unit 212 described later, and a resolution conversion processing unit 206 performs millimeter-inch resolution conversion, enlargement / reduction processing, and the like.
The resolution-converted image data is subjected to encoding processing by the communication code decoding processing unit in the communication control unit 210 according to the capability of the transmission destination, and transmission control is performed.

Reference numeral 212 denotes an encoding / decoding processing unit, which encodes image data according to a predetermined encoding method and decodes the encoded image data. A recording control unit 213 includes a recording image processing control unit that performs a smoothing process and the like, a printer main control unit that outputs image data to a printer described below, and the like. In the recording control unit 213, the image data to be recorded is decoded by the encoding / decoding processing unit 212, and various image processing such as smoothing processing and recording density correction processing is performed by the recording image processing control unit to convert the image data into high-definition image data. Are output to a printer 214 described later. A printer 214 is a page printer in the present embodiment.

Reference numeral 216 denotes an interface (I / F) control unit, which is used to connect to the network (LAN) 109.
7) to perform interface control. In the present embodiment, a bidirectional parallel interface (IEEE)
E1284). The network adapter 102 (107) is connected to the LAN 109, and can receive a remote operation request for transmission, printing, and the like from the document processing server 103 on the LAN 109.

Reference numeral 217 denotes a printer formatter.
The control is performed to develop the page description language received via the AN 109 into image data, and is used when performing print control from the information processing apparatus. In the present embodiment, the printer formatter 217 includes the I / F control unit 2
16 is connected to the recording control unit 213 directly without passing through the system bus 215, and
14 is assumed to be printed.

The multifunction device 101 (1)
08) and remote operations such as transmission to another facsimile apparatus connected by the communication line 220, printing by the printer 214, data registration, and the like.
This is performed by transmitting parameters, data, and the like from the network adapter 102 (107) to the multifunction device 101 (108) via the I / F control unit 216.

FIG. 3 is a diagram showing a data structure of a transmission job queue managed on the document processing server 103.
The data in the transmission job queue is stored in the document processing server 10.
3 is stored in a hard disk (HD), and data management is performed by a program operating on the document processing server 103.

In FIG. 3, reference numeral 301 denotes a transmission queue management table pointer, which stores an address to a transmission job queue management table 3001 for managing a transmission job queue. The transmission job queue management table is prepared for each device (multifunction device) that provides a facsimile transmission service.
It is composed of five data items up to 306, each of which manages a job queue. Further, in the present embodiment, it is possible to prepare a table corresponding to the service provided by each device, include valid / invalid information, and have a plurality of tables.

Reference numeral 302 denotes a NEXT pointer, which stores an address to the next transmission job queue management table 3002, and can manage the transmission job queue as long as the storage capacity of the document processing server 103 permits. In the transmission job queue management table, the value of the NEXT pointer 302 is
It shall be terminated by NULL code. Three
03 is a transmission queue ID, which is given a unique value in this system. A device ID 304 stores an ID of a device corresponding to the transmission job queue. This device ID is also given a unique one in this system, and in this embodiment, the network address of the device is used as this value. Reference numeral 305 denotes a valid / invalid flag. If this flag is set to invalid, the queue becomes unusable and cannot be seen by the user. 306
Is a job management table pointer, which stores an address to job data 3003 requested by a client, which will be described later.

The job data 3003 is composed of eight data, and is managed in the same manner as the job queue management data.

Reference numeral 307 denotes a NEXT pointer, which stores an address to the next job data 3004. The value of the NEXT pointer 307 is terminated by a NULL code. A job ID 308 is used for recognizing a job. In 309, the name of the sender is stored.
10 stores the name of the recipient, and 311 stores the address of the recipient. 312 stores the file name of the cover page. 313 stores the number of pages of the transmission image file. 314 stores the file name of the transmission image file. The cover page file and the transmission image file are transferred from the client to the document processing server 103 when the job is created, and stored in the HD of the server.

As described above, the transmission job queue manages transmission jobs requested by clients for each queue.

FIG. 4 is a diagram showing a data structure of a reception job queue managed on the document processing server 103.
The data in the reception job queue is stored in the document processing server 10.
3 is stored in a hard disk (HD), and data management is performed by a program operating on the document processing server 103.

In FIG. 4, reference numeral 401 denotes a reception queue management table pointer, which stores an address to the reception job queue management table 4001 for managing the reception job queue. The reception job queue management table is prepared for each device (multi-function device) that provides a facsimile reception service.
It is composed of five data items up to 406, each of which manages a job queue. Further, in the present embodiment, it is possible to prepare a table corresponding to the service provided by each device, include valid / invalid information, and have a plurality of tables.

Reference numeral 402 denotes a NEXT pointer, which stores an address to the next reception job queue management table 4002, and can manage the reception job queue as long as the storage capacity of the document processing server 103 permits. In the reception job queue management table, the value of the NEXT pointer 402 is
It shall be terminated by NULL code. 4
03 is a transmission queue ID, which is given a unique value in this system. A device ID 404 stores the ID of a device corresponding to the reception job queue. This device ID is also given a unique one in this system, and in this embodiment, the network address of the device is used as this value. Reference numeral 405 denotes a valid / invalid flag. If this flag is set to invalid, the queue is disabled, and the received document received by the device is not uploaded to the document processing server 103. Reference numeral 406 denotes a job management table pointer, which stores job data 400 received by a device described later.
3 is stored.

The job data 4003 is composed of four data, and is managed in the same manner as the job queue management data.

Reference numeral 407 denotes a NEXT pointer, which stores an address to the next job data 4004, and the value of the NEXT pointer 407 is terminated by a NULL code. A job ID 408 is used for recognizing a job. 409 stores the number of pages of the received image file, and 410 stores the file name of the received image file. The received image file is transferred from the device to the document processing server 103 upon reception, and the H
D.

As described above, the reception job queue manages jobs received by the device for each queue.

FIG. 5 is a diagram showing a data structure of a print job queue managed on the document processing server 103.
The print job queue data is stored in the document processing server 10.
3 is stored in a hard disk (HD), and data management is performed by a program operating on the document processing server 103.

In FIG. 5, reference numeral 501 denotes a print queue management table pointer, which stores an address to the print job queue management table 5001 for managing the print job queue. The print job queue management table is prepared for each device (multi-function device) that provides a print service, and includes five data items 502 to 506, each of which manages a job queue. In this embodiment, a table is prepared corresponding to the service provided by each device, and each table contains valid / invalid information. It is possible to have a plurality of tables.

Reference numeral 502 denotes a NEXT pointer, which stores an address to the next print job queue management table 5002, and can manage the print job queue as long as the storage capacity of the document processing server 103 permits. In the print job queue management table, the value of the NEXT pointer 502 is
It shall be terminated by NULL code. 5
03 is a print queue ID, which is given a unique value in this system. A device ID 504 stores a device ID corresponding to the print job queue. This device ID is also given a unique one in this system, and in this embodiment, the network address of the device is used as this value. Reference numeral 505 denotes a valid / invalid flag. If this flag is set to invalid, the queue becomes unusable and cannot be seen by the user. 506
Is a job management table pointer, which stores an address to job data 5003 requested by a client described later.

The job data 5003 is composed of four data, and is managed in the same manner as the job queue management data.

Reference numeral 507 denotes a NEXT pointer, which stores an address to the next job data 5004. The value of the NEXT pointer 507 is terminated by a NULL code. A job ID 508 is used for recognizing a job. 509 stores the number of pages of the print image file, and 510 stores the file name of the print image file. The print image file is transferred from the client to the document processing server 103 when the job is created, and stored in the HD of the server.

As described above, the print job queue manages a print job requested by a client for each queue.

FIG. 6 is a diagram showing a data structure of a scan job queue managed on the document processing server 103. The data of the scan job queue is stored on the hard disk (HD) of the document processing server 103, and the data management is performed by a program running on the document processing server 103.

In FIG. 6, reference numeral 601 denotes a scan queue management table pointer, which is a scan job queue management table 600 for managing a scan job queue.
1 is stored. A scan job queue management table is prepared for each device (multifunction device) that provides a scan service.
It is composed of five data items 602 to 606, each of which manages a job queue. In this embodiment, a table is prepared corresponding to the service provided by each device, and each table contains valid / invalid information. It is possible to have a plurality of tables.

Reference numeral 602 denotes a NEXT pointer which stores an address to the next scan job queue management table 6002, and can manage the scan job queue as long as the storage capacity of the document processing server 103 permits. In the scan job queue management table, it is assumed that the value of the NEXT pointer 602 is terminated by a NULL code. Reference numeral 603 denotes a scan queue ID, which is given a unique value in the present system. Reference numeral 604 denotes a device ID, which is an ID of a device corresponding to the scan job queue.
Is stored. This device ID is also given a unique one in this system, and in this embodiment, the network address of the device is used as this value. Reference numeral 605 denotes a valid / invalid flag. If this flag is set to invalid, the queue becomes unusable and cannot be seen by the user. Reference numeral 606 denotes a job management table pointer, which is used for job data 600 requested by the client.
3 is stored.

The job data 6003 is composed of four data, and is managed in the same manner as the job queue management data.

Reference numeral 607 denotes a NEXT pointer, which stores an address to the next job data 6004, and the value of the NEXT pointer 607 is terminated by a NULL code. A job ID 608 is used for recognizing a job. 609 stores the number of pages of the scanned image file, and 610 stores the file name of the scanned image file. The scanned image file is read from the device, transferred from the device to the document processing server 103, and stored in the HD of the server.

As described above, the scan job queue manages a scan job requested from a client and a scan job started from a device for each queue.

FIG. 7 is a diagram showing a data structure of a template queue managed on the document processing server 103 or the device. The data in the template job queue is stored on the hard disk (HD) of the document processing server 103.
The data management is performed by the document processing server 103 and a program operating on the device. In this embodiment, it is assumed that the template data is managed not only on the device but also on the document processing server 103.

In FIG. 7, reference numeral 701 denotes a template queue management table pointer, which is a template queue management table 700 for managing the template queue.
1 is stored. Note that the template queue management table is prepared for every device (multi-function device) connected to the document processing server 103, and includes five data items 702 to 706, each of which manages a template queue. .
In this embodiment, a table is prepared for each device, and each template has a unique ID and is managed, so that a template can be downloaded from a device by specifying an ID.

Reference numeral 702 denotes a NEXT pointer, which stores an address to the next template queue management table 7002, and stores the template queue in the document processing server 10.
3 can be managed as long as the storage capacity allows. Also,
In the template job queue management table, it is assumed that the value of the NEXT pointer 702 is terminated by a NULL code. A template queue ID 703 is given a unique value in the present system. 704 is a device I
D, the device I corresponding to the template queue
D is stored. This device ID is also given a unique one in this system, and in this embodiment, the network address of the device is used as this value. 705
Is a valid / invalid flag. If this flag is set to invalid, this queue is disabled and the template cannot be used. Reference numeral 706 denotes a template management table pointer.
3 is stored.

The template data 7003 is composed of eight data, and is managed in the same manner as the template queue management data.

Reference numeral 707 denotes a NEXT pointer which stores an address to the next template data 7004,
The value of the XT pointer 707 is terminated by a NULL code. A template ID 708 is used to recognize the template. A job type 709 stores the job type of the template. In this embodiment, it is assumed that there are job types of scan transmission / reception and printing. 710 stores the name of the sender, 711 stores the name of the recipient, and 712 stores the address of the recipient. 713 stores a file name of the cover page. The cover page file and the transmission image file are transferred from the client to the document processing server 103 when the job is created, and stored in the HD of the server. A scan mode is stored in the 714, and data stored in the 714 is used for scan setting when a template is specified from the device.

FIG. 8 is a diagram showing a data structure of a device management table managed on the document processing server 103. The data of the device management table is stored in the hard disk (HD) of the document processing server 103, and the data management is performed by a program running on the document processing server 103.

In FIG. 8, reference numeral 801 denotes a device management table pointer, which stores an address to the device management table 8001 for managing the device management table.

The device management table is composed of data as shown in the figure, and is managed in the same manner as job queue management data.

Reference numeral 802 denotes a NEXT pointer, which stores an address to the next device management table 8002.
The value of the NEXT pointer 802 is terminated by a NULL code. A device ID 803 stores a device ID unique to the present system. In the present embodiment, the network address of the device is stored. 804 stores the name of the device. This device name is displayed to the user (client) as a queue name.

In a field 805, a transmission queue ID corresponding to this device is stored. 806 stores a reception queue ID corresponding to this device. 807 stores a print queue ID corresponding to this device. 808 stores a scan queue ID corresponding to this device. 809 stores a template queue ID corresponding to this device. 810 has a transmission capability, 811
, A capability parameter such as resolution, paper size, speed, and the like are stored as reception capability, 812 as printing capability, and 813 as scanning capability, respectively.

In the device management table, various devices are managed, and a table is created corresponding to all devices. The device management table is also used in the client in the same structure. However, on the client, only those notified from the document processing server 103 are managed.

FIG. 9 shows the data structure of the user management table managed on the document processing server 103. The data in the user management table is stored in the document processing server 1.
The data is stored in a hard disk (HD) 03 and data management is performed by a program running on the document processing server 103.

In FIG. 9, reference numeral 9001 denotes a user management table. It should be noted that this table is not queue-managed like other tables, but is managed as a normal array.

Reference numeral 901 stores a user ID. 902
Is an access transmission queue table pointer, which stores an address to an accessible transmission service queue table 9002. Similarly, 903 is a reception access queue table pointer, 904 is a print access queue table pointer, and 905 is a scan access queue table pointer. A user name 906 is used to log in to the document processing server 103. 907 stores a password used at the time of login. 908 stores the name of the user, and this user name is used as the name of the sender of the cover page. 909 stores the telephone number of the user, and this information is also used for the cover page.

Access transmission queue table pointer 90
Access queue table 9002 addressed by
Manages queue IDs of various job queues accessible to the user. A NEXT pointer 910 stores an address to the next access queue table, and the value of the NEXT pointer 910 is terminated by a NULL code. A transmission queue ID 911 is stored.

As described above, the user management table is used to manage users who use the document processing server 103, and is created each time a user is added.

In the document processing system having the above configuration, a description will be given of processing at the server when a multi-function device, which is one of the devices, first logs in to the document processing server set for itself.

FIG. 10 is a flowchart showing processing of the document processing server 103 when a device logs in. First, in step S1001, the document processing server 103 accepts a login request made by a device to a server initially set in its own device. Note that the login command includes information indicated by 9001. Further, since the document processing server 103 of the present embodiment can manage a plurality of devices, it accepts a login request without limitation.

Next, upon receiving a login command, the flow advances to step S1002 to check the device management table pointer 801 shown in FIG. 8 to check the devices managed by the server 103. If the value of the pointer is NULL, there is no device currently being managed, and the process advances to step S1006 to create a new device management table 800 based on the information of the login command.
1 is created, the start address of the next device management table 8002 is stored in the NEXT pointer 802, and
NU is set in the NEXT pointer of the next device management table 8002.
Stores LL code.

Next, in step S1007, the job queue management tables 3001, 4001, 5001, 6001, 70 corresponding to the services provided by the device.
01 and the next job queue management table 300
2,4002,5002,6002,7002. Then, in step S1008, the process ends by returning a response to the login command to the device.

On the other hand, if the value of the pointer is not NULL in step S1002, step S100
Proceed to 3 to acquire the device management table indicated by the pointer and read the data. Then, step S1004
, The device I included in the login command
D is compared with the read device ID, and if they match, it is determined that the device is already under management, and the above-described step S
Proceed to 1008.

If the device IDs do not match, the flow advances to step S1005 to check the value of the NEXT pointer to compare with the next data in the management table.
If it is not NULL, the process returns to step S1003 to acquire the next management table. Also, the NEXT pointer is NULL
If so, the device that has logged in is determined to be a new device, and the process advances to step S1006 to perform the above-described table creation processing.

Next, a multi-function device, which is one of the devices, sends a job acquisition request command to perform a job such as a transmission process, a reception process, a printing process, and a scanning process. The processing of the server will be described. In the present embodiment, the processing in the document processing server 103 when the device performs the transmission processing will be described as an example.

FIG. 11 is a flowchart showing processing of the document processing server 103 when a device performs a job. First, in step S1101, the document processing server 103 receives a job acquisition request from a multifunction device, which is one of the devices. Note that the job acquisition request is issued periodically when the device is not performing operations such as communication, and the device ID is included in the command.

Next, in step S1102, the transmission queue management table pointer 301 shown in FIG. 3 is checked to check the transmission job queue managed by the server 103 that has received the job acquisition request from the device. Here, if the value of the pointer is NULL, there is no transmission job queue that is currently being managed, so that step S1 is executed.
Proceed to 110 and return a response to the device without a job.

If the value of the pointer is not NULL, the flow advances to step S1103 to acquire the transmission job queue management table (3001, 3002,...) Indicated by the pointer and read the data. Then, in step S1104, the device ID included in the data of the job acquisition request command is compared with the read device ID 304. If they match, the process advances to step S1106 to check the job management table pointer 306 of the transmission job queue management table to search for a job connected to the queue. Here, if NULL, there is no job to be processed by the device at present, so the process proceeds to step S1110, and a response is returned to the device without a job.

The job management table pointer 306
If is not NULL, the process advances to step S1107 to acquire the job data 3003 indicated by the pointer. Then, in step S1108, the job data and the image file are transferred to the device. Thereafter, when the transfer is completed, the process proceeds to step S1109, in which the job data and the image file remaining in the server 103 are deleted, and the process ends.

On the other hand, if it is determined in step S1104 that the device IDs do not match, the flow advances to step S1105.
In order to search for the next queue, the NEXT pointer 302 is checked. If it is NULL, there is no more queue to search, and the process proceeds to step S1110. If it is not NULL, the process proceeds to step S11.
Return to 03 to get the next table. When the queue management table corresponding to the device is not found, the process returns a response without a job.

Next, the processing of the server when the user receives a queue information acquisition request sent from the client in order to register a template will be described.

FIG. 12 is a flowchart showing processing in the document processing server 103 when a user registers a template. First, when a user performs a template registration operation, it is necessary to know which device can be used. Therefore, the client sends a queue information acquisition request to the document processing server 103. The acquisition request command includes a user ID.

In step S1201, when the document processing server 103 receives this request, the process proceeds to step S120.
The process proceeds to step S2, where the value of the access queue table pointer of the corresponding user ID is checked from the user management table 9001 shown in FIG. The queue to be checked here changes according to the requested service. In the case of the transmission service, the access transmission queue table pointer 902 is checked. If the value of the pointer is NULL, there is no queue that can be accessed by the user, so the process proceeds to step S1211 and ends.

If the value of the pointer is not NULL, the flow advances to step S1203 to obtain an access queue table pointer (for example, 902 in the case of transmission) indicated by the pointer, and in step S1204, reads out the transmission queue ID 911 in the table. Next, step S1205
In order to acquire the information of the device corresponding to the read transmission queue ID 911, it is checked whether or not the device management table pointer 801 shown in FIG. 8 is NULL. If the pointer is NULL, there is no device managed by the system, and the process advances to step S1211.
The process ends after responding to the client with the device list information.

If the value of the pointer is not NULL, the flow advances to step S1206 to acquire a device management table pointed to by the pointer and read the value. In step S1207, it is checked whether the transmission queue ID read in step S1204 and the transmission queue ID registered in the device management table match. Here, if they match, the device can be used by the user, and the process advances to step S1208 to set device information in the device list as data for responding to the client. The process advances to step S1210 to acquire the next transmission queue ID described later.

On the other hand, if there is no match in the above step S1207, the flow advances to step S1209 to acquire the next device management table, and the value of the NEXT pointer is checked. Here, if the pointer is not NULL, the process returns to step S1206, and the above processing is repeated. If the NEXT pointer is NULL, it is determined that there is no device corresponding to the transmission queue ID, and the value of the NEXT pointer in the access queue table shown in FIG. Check. If the value of the NEXT pointer is not NULL, the process returns to step S1203 to acquire the next access queue table. If NULL, step S1211
The process is returned to the client with the device list information created in the processing up to the present, and the processing ends.

Then, the client creates a device management table shown in FIG. 8 based on the device list information sent, displays the available devices and their capabilities to the user, and causes the user to create a template based on the information. Is possible. However, when the valid / invalid flag is set to invalid, the display is not performed. Further, in the document processing system according to the present embodiment, a scan template can be created, and thus the same processing is performed when a scan template is created.

FIG. 13 is a diagram showing a screen for setting a transmission job template on the client. In the example shown in FIG. 13, as the transmission job template, the destination name and FAX number 1301, the sender name and FAX number 1
302, FAX list 1303, device capability 1304,
Although a reading resolution 1305 and a reading mode 1306 are described, the following are also described as parameters in addition to them. (1) Subaddress data and password data to be transmitted to the other receiver (for example, those conforming to ITU-T Recommendation T.30). The partner receiver transfers the received image data to a destination corresponding to the received sub-address data, or confidentially receives the image data in a memory box corresponding to the sub-address data. The password data is used when extracting the confidentially received image data from the memory box. (2) Information on whether or not to request reception notification from the other receiver, the method of reception notification (e-mail, FAX, voice notification by telephone), and reception notification destination information. These pieces of information are notified to the other receiver by, for example, a salutation protocol or the like. (3) Information indicating the action to take when the other receiver is busy, whether to redial to the same destination, or to transfer the transmission to an alternative destination. In the former case, the number of redials,
A redial interval is further added, and in the latter case, alternative destination information is added. (4) Information on whether or not to notify the transmission result. Notification destination information when notifying. After the transmission job ends, the device notifies the result of the transmission job based on this information.

As shown in FIG. 13, a list of devices managed by the server 103 that can process a transmission job is displayed in the FAX list on the setting screen. A desired device can be selected.

When the server 103 generates the job template setting screen for the device selected in the list, the server 103 determines whether each item that can be registered in the job template is valid or invalid by using the device management table of the target device. On the basis of the determination, a measure (for example, gray-out display or the like) is performed so that the user cannot specify an invalid item.

Thus, the user can know the capability of the device. Also, after selecting the desired device,
By making further detailed settings and pressing a registration button 1307, a client sends a template registration request to the server 103, and a template registration completion screen is displayed on the client as shown in FIG.

FIG. 15 is a flowchart showing the processing of the document processing server 103 when receiving a template registration request from a client. First, step S15
At 01, the document processing server 103 receives a template registration request including template registration data sent from the client. The template registration request includes the device ID and information registered in the template data (for example, 7003, 7004,...) Shown in FIG.

The server 10 that has received the above registration request
3 checks the template queue management table pointer 701 shown in FIG. 7 in step S1502 to check the template being managed. here,
If the value of the pointer is NULL, there is no device currently being managed, and the process advances to step S1506 to create a new template management table 7001 based on the information of the template registration request, and store the next template management table in the NEXT pointer 702. The head address of the next template management table 7002 is stored.
Store NULL code in NEXT pointer.

Next, in step S107, template data 707 to 714 are created, and the NEXT pointer 7
In 07, an address to the next template data 7004 is set. Then, in step S1508, the created template data is downloaded to the device. The template data managed on the device is used when an ID is input from the panel of the device.

Next, in step S1509, the template ID is sent as a response to the template registration request.
Is returned to the client, and the process ends.

On the other hand, if the value of the template queue management table pointer 701 is not NULL in step S1502, the flow advances to step S1503, and the template management table 70 indicated by the pointer 701 is reached.
01 is obtained and the value is read. Then, step S15
In 04, the device ID included in the template registration request is compared with the read device ID 704, and if they match, it is determined that the device is already under management, and the process proceeds to step S1507.

If the device IDs do not match, the flow advances to step S1505 to compare the data with the next data in the template management table, and checks the value of the NEXT pointer 702. If the value of the NEXT pointer 702 is not NULL, the process returns to step S1503 to acquire the next template management table (7002,...). If the NEXT pointer 702 is NULL, the device that has issued the template registration request is determined to be a device requiring a new management table, and the process advances to step S1506 to execute the above-described template management table creation, template data creation, and template download. Then, the template ID is returned to the client as a response, and the process ends.

Next, the processing of the document processing server 103 when the multifunction device 101 (108), which is one of the devices, sends a template acquisition request command by designating a template ID from the operation panel will be described.

FIG. 16 shows the document processing server 103 when a template acquisition request command is received from a device.
6 is a flowchart showing the processing of FIG. First, step S
In step 1601, the document processing server 103 receives a template acquisition request command sent from a device. The template acquisition request command is issued when a template ID is specified from the operation panel of the device.
D and the template ID are included, and the input of the template ID is assumed to have been performed using the numeric keypad on the device.

Here, the server 103 that has received the template acquisition request command checks the template queue management table pointer 701 shown in FIG. 7 in step S1602 to check the managed template. Here, if the value of the pointer 701 is NULL, there is no device currently being managed, so that step S
Proceed to 1610, return a response without a template, and end.

If the value of the pointer 701 is not NULL, the flow advances to step S1603 to acquire the template queue management table 7001 indicated by the pointer 701 and read the value. In step S1604, the device ID included in the data of the template acquisition request command is compared with the read device ID 704, and if they match, the process proceeds to step S1606.
Search for templates connected to the queue. In other words, the template management table pointer 706 is checked. If NULL, the process proceeds to step S1610 because there is no managed template, and a response is returned to the device without the template.

If the template management table pointer 706 is not NULL, the flow advances to step S1607, and the template data 700 indicated by the pointer 706 is read.
Get 3 Then, in step S1608,
The template ID included in the data of the acquisition request command is compared with the read template ID 708. If they do not match, the process advances to step S1609 to check the value of the NEXT pointer 707 to read the next data. If the NEXT pointer 707 is not NULL, the process returns to step S1607, the next data is read again, and the above processing is repeated.
If it is LL, the process proceeds to step S1610, and since there is no managed template, a response is returned to the device without the template. If the template IDs match in step S1608, step S16
Proceed to 11 to transfer the template data to the device,
The process ends. Thereby, the device creates template data based on the transferred data, and registers the template in the server.

On the other hand, if the device IDs do not match in step S1604, step S1605
To go to and find the next queue, use the NEXT pointer 702
Is checked, and if the NEXT pointer 702 is NULL, the process advances to step S1610 to return a response without a template and end. If the NEXT pointer 702 is not NULL, the process returns to step SS1603, and the above-described process of acquiring the next table is repeated.

As described above, according to the embodiment,
Clients for requesting facsimile transmission jobs and print jobs, receiving reception jobs and scan jobs, servers for managing various requested jobs, and processing and processing jobs connected to the same network. Or a document processing system comprising a device for registering a job created by itself on a server, the device includes a storage unit for storing a unique ID in the system, and a unit for storing a job template, The server includes means for managing the job for each of the unique ID and the processing service, the client includes means for registering the template, and the device generates the job according to the stored template, thereby making it possible to input the template ID. Process can be simplified, Scan improve the usability of the expected.

Also, by displaying the capability of the device, a template corresponding to the capability can be created.

The present invention can be applied to a system composed of a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), and can be applied to a single device (for example, a copier, a facsimile). Device).

An object of the present invention is to supply a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and to provide a computer (CPU or MP) of the system or apparatus.
It goes without saying that U) can also be achieved by reading and executing the program code stored in the storage medium.

In this case, the program code itself read from the storage medium implements the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.

As a storage medium for supplying the program code, for example, a floppy (registered trademark) disk,
Hard disk, optical disk, magneto-optical disk, CD-
A ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, and the like can be used.

When the computer executes the readout program code, not only the functions of the above-described embodiment are realized, but also the OS (Operating System) running on the computer based on the instruction of the program code. ) May perform some or all of the actual processing, and the processing may realize the functions of the above-described embodiments.

Further, after the program code read from the storage medium is written into a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, based on the instruction of the program code, It goes without saying that the CPU included in the function expansion board or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

[0110]

As described above, according to the present invention,
Jobs with various settings can be executed by the device with a simple operation, and user convenience can be improved.

[Brief description of the drawings]

FIG. 1 is a schematic diagram illustrating a connection mode of a document processing system according to an embodiment.

FIG. 2 is a schematic diagram illustrating a configuration of a multifunction device according to an embodiment.

FIG. 3 is a diagram showing a data configuration of a transmission job queue managed on the document processing server 103.

FIG. 4 is a diagram showing a data configuration of a reception job queue managed on the document processing server 103.

FIG. 5 is a diagram showing a data configuration of a print job queue managed on the document processing server 103.

FIG. 6 is a diagram showing a data configuration of a scan job queue managed on the document processing server 103.

FIG. 7 illustrates a data configuration of a template queue managed on the document processing server 103 or a device.

FIG. 8 is a diagram showing a data configuration of a device management table managed on the document processing server 103.

FIG. 9 is a diagram showing a data configuration of a user management table managed on the document processing server 103.

FIG. 10 is a flowchart showing processing of the document processing server 103 when a device logs in.

FIG. 11 is a flowchart illustrating processing of the document processing server 103 when a device performs a job.

FIG. 12 is a flowchart showing processing in the document processing server 103 when a user registers a template.

FIG. 13 is a diagram showing a screen for setting a transmission job template on a client.

FIG. 14 is a diagram showing a template registration completion screen on the client.

FIG. 15 is a flowchart showing processing of the document processing server 103 when receiving a template registration request from a client.

FIG. 16 is a flowchart showing processing of the document processing server 103 when receiving a template acquisition request command from a device.

[Explanation of symbols]

 101 Multifunction device 102 Network adapter 103 Document processing server 104 Client 105 Client 106 File server 107 Network adapter 108 Multifunction device 109 Network (LAN) 201 CPU 202 ROM 203 RAM 204 Image memory 205 Operation unit 206 Resolution conversion processing unit 207 Reading control Unit 208 image processing control unit 209 external memory 210 communication control unit 211 NCU 212 code decoding processing unit 213 recording control unit 214 printer 215 system bus 216 I / F control unit 217 printer formatter

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] June 28, 2001 (2001.6.2
8)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Claims

[Correction method] Change

[Correction contents]

[Claims]

Claims (8)

[Claims] 1. A device management apparatus for causing a device on a network to execute a requested job in response to a job request from a client on a network, wherein the management unit manages information on the capability of the device. Generating means for generating a job template for the device based on information managed by the managing means and instructions from the client; transmitting means for transmitting the generated job template to the device; and the generated job Notification means for notifying the client or the device of information for identifying a template. 2. A device management method for causing a device on the network to execute a requested job in response to a job request from a client on the network, comprising: a management step of managing information on the capability of the device; A generation step of generating a job template for the device based on the information managed by the management unit and an instruction from the client; a transmission step of transmitting the generated job template to the device; A notification step of notifying the client or the device of information for identifying a template. 3. A computer-readable storage medium storing a program executed by a computer of a device management apparatus for causing a device on the network to execute a requested job in response to a job request from a client on the network. A management step of managing information relating to the capability of the device; a generation step of generating a job template for the device based on information managed by the management unit and an instruction from the client; and a generated job. A storage medium storing a program for executing a transmitting step of transmitting a template to the device; and a notifying step of notifying the client or the device of information for identifying the generated job template. . 4. A device management system connected to a network and configured to execute a job, a device management apparatus that causes the device to execute a job, and a client that requests the device management apparatus for a job. A registration unit that registers setting information for causing the device to perform a desired job as a job template, a management unit that manages execution of a job by the device based on the setting information of the registered job template, A device management system comprising: 5. The apparatus according to claim 4, further comprising a display unit for displaying a capability of the device, wherein the registration unit registers the job template according to the capability displayed on the display unit. Device management system as described. 6. The device management system according to claim 4, further comprising a step of displaying whether setting information that can be registered as said job template is valid or invalid. 7. The device management system according to claim 4, wherein the setting information includes at least a device list, a capability, a reading resolution, and a reading mode when the document processing is a document transmission. 8. The setting information further includes a subaddress to be transmitted, a password, information on whether or not to request a receipt notification,
Information indicating the method of receiving notification, whether to redial if the other machine is busy or transfer to an alternative destination,
The device management system according to claim 7, further comprising information indicating whether to notify the transmission result information and notification destination information.