JP2007148782A - Peripheral equipment management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To achieve detailed access control of peripheral equipment in each user including an equipment operation condition in time of job execution, in the peripheral equipment receiving and processing a job by including a peripheral equipment control command in a job execution permit not capable of being browsed or edited by a user. <P>SOLUTION: This peripheral equipment management system allows achievement of the detailed access control by processing the equipment control command determined by access control information in each the user except for the one designated by the user. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a peripheral device control system including a peripheral device and an information processing apparatus that perform peripheral device control via a network, in particular, job access control using a directory server.

In the prior art, according to Japanese Patent Application Laid-Open No. 2002-202945, a peripheral device management system is presented that enables unified access control by obtaining a job execution permit from a directory server and attaching it to a job. ing.
JP 2002-202945 A

  However, the prior art has the following problems.

  The job execution permit includes information for identifying the user such as a user ID and information such as the maximum printable number of the user, but does not include designation of device control to be performed when the user executes the job. For this reason, when the peripheral device receives and processes a job with a job execution certificate, no operation other than device control specified by the user can be performed. For example, regarding a job executed by a specific user as a policy of the peripheral device management system, it has been difficult to realize control such as saving a job log with a thumbnail without specifying the user.

  In addition, the peripheral device can change the device control for each user by inquiring the directory server about the device control to be executed with respect to the user using the user ID included in the job execution permit. After receiving and analyzing the job, the device makes an inquiry to the directory server and performs job processing based on the result. For this reason, there is a problem that it takes extra time to start job processing, and it takes time to obtain job output.

  Further, as a method for restricting access to functions, a technique for restricting job functions executable by a user for each peripheral device by managing the user for each peripheral device and holding the access control information of the user is known. However, in an environment where a large number of peripheral devices are connected via a network, it is possible for an administrator to maintain access control information for each peripheral device used by the user. This increases the management burden of managing information, and it is necessary for the user to search for a peripheral device that can be used due to a difference in functions that can be used by the peripheral device. Furthermore, since access control for the same user is individually managed by peripheral devices, there is a risk that consistency of access control may not be achieved in the entire peripheral device management system including a plurality of peripheral devices.

  In addition, in order to perform detailed access control for each user, conventionally, driver software or the like identifies the user, and accesses the peripheral device to the user by inquiring access control information before sending a job from the information processing device to the peripheral device. Control is done. However, in recent years, specifications of peripheral device control commands have been released to those other than peripheral device developers, and it is possible to control peripheral devices by developing driver software not only by peripheral device developers but also by users and third parties. If access control to a device is performed by a user or a third party, it may be difficult to perform unified access control.

  Furthermore, in the prior art, the peripheral device control command cannot be included as a user access control condition indicated by the job execution permit, and the peripheral device that received the job must process the user who transmitted the job. Limited to the specified device control command.

  In view of the above points, in the present invention, by including a peripheral device control command in a job execution permit that cannot be viewed or edited by the user, other than that specified by the user in the peripheral device that receives and processes the job A peripheral device management system capable of processing and executing a device control command determined by access control information for each user is provided.

  In the first invention according to the present invention, the information processing device is configured by an information processing device, a directory server, and a peripheral device connected via a network, and the peripheral device transmits a job transmitted from the information processing device via the network. In the peripheral device management system for processing, the information processing apparatus issues an issue request means for sending an issuance request for a job execution permit to the directory server prior to sending a job, and a job execution permit obtained by the issue request means A job sending means for sending the job with the job attached, and the directory server receives a job execution permit issuing request from the information processing apparatus and issues a job execution permit issuing means. And the peripheral device analyzes the job transmitted from the information processing apparatus and analyzes the job execution. A job analysis unit for identifying a line permit, a job execution permit analysis unit for analyzing the identified job execution permit, and a control unit that operates according to a control command included in the job execution permit. Features.

  In the second invention according to the present invention, the directory server has means for holding job execution permission information for each user, and the job execution permit issuing means has job execution permission information held by the directory server. And generating means for generating a job execution permit, and encryption means for encrypting the generated job execution permit.

  In a third invention according to the present invention, the directory server has means for acquiring job execution permission information for each user from the outside through a network, and the job execution certificate issuing means is a job acquired by the acquisition means. And generating means for generating a job execution permit according to the execution permission information, and encrypting means for encrypting the generated job execution permit.

  In a fourth invention according to the present invention, the job execution permit analysis means included in the peripheral device includes a decryption means for the encrypted job execution permit.

  In a fifth aspect of the present invention, the job execution permit includes a device control command executed by a peripheral device when executing the job and information indicating a parameter of the command.

  In a sixth aspect of the present invention, the job execution permission information for each user held by the directory server or acquired from the outside includes a device control command executed by a peripheral device when executing the job, and the command It includes information indicating parameters.

  According to a seventh aspect of the present invention, the device control command included in the job execution permit is a command for setting job attributes.

  According to an eighth aspect of the present invention, the device control command included in the job execution permit is a command for setting a device attribute.

  As described above, in the first invention according to the present invention, the information processing device is configured by the information processing device, the directory server, and the peripheral device connected via the network, and the peripheral device is configured by the information processing device via the network. In the peripheral device management system for processing a job transmitted from the server, the information processing apparatus includes an issue request unit that transmits a request for issuing a job execution permit to the directory server prior to job transmission, and the issue request unit. A job transmitting means for transmitting the job with the obtained job execution permit attached, and the directory server receives a job execution permit issuance request from the information processing apparatus and issues a job execution permit An execution permit issuing means, and the peripheral device transmits a job transmitted from the information processing apparatus. Job analyzing means for analyzing and identifying the job execution permit, job execution permit analyzing means for analyzing the identified job execution permit, and control means for operating according to a control command included in the job execution permit By having the peripheral device analyze the received job, the peripheral device appropriately processes only the job whose setting is permitted for the user who has executed the job, and the user Device control commands included in unspecified job execution permits can be executed.

  In the second invention according to the present invention, the directory server has means for holding job execution permission information for each user, and the job execution permit issuing means has job execution permission information held by the directory server. The job execution permission according to the job execution permission information for each user held by the directory server by having the generation means for generating the job execution permit according to the above and the encryption means for encrypting the generated job execution permit A certificate can be generated, further encrypted, and transmitted to the information processing apparatus to issue an effective job execution permit that is difficult for the information processing apparatus to falsify.

  In a third invention according to the present invention, the directory server has means for acquiring job execution permission information for each user from the outside through a network, and the job execution certificate issuing means is a job acquired by the acquisition means. And generating the job execution permit according to the execution permission information and the encryption means for encrypting the generated job execution permit, so that the directory server externally transmits the job execution permission information for each user through the network. An effective job execution permit that is difficult to falsify by generating a job execution permit according to the acquired job execution permission information for each user, further encrypting it, and sending it to the information processing apparatus Can be issued.

  In a fourth invention according to the present invention, the job execution permit analysis means included in the peripheral device includes a decryption means for decrypting the encrypted job execution permit, so that the peripheral device can execute the encrypted job execution. It is possible to decrypt the permit and execute a job according to the contents of the job execution permit.

  In the fifth invention according to the present invention, the job execution permit includes a device control command executed by the peripheral device when executing the job and information indicating a parameter of the command, whereby the peripheral device When the job is executed, the device control command included in the job execution permit can be processed.

  In a sixth aspect of the present invention, the job execution permission information for each user held by the directory server or acquired from the outside includes a device control command executed by a peripheral device when executing the job, and the command By including information indicating parameters, the directory server can execute an apparatus control command when executing the job based on the job execution permission information held or externally acquired by the directory server when issuing the job execution permit. And information indicating the parameters of the command can be included in the job execution permit.

  In a seventh invention according to the present invention, the device control command included in the job execution permit is a command for setting job attributes, so that the peripheral device can execute a job permitted by the job execution permit. At the time of execution, job attributes can be set by the device control command.

  In an eighth invention according to the present invention, the device control command included in the job execution permit is a command for setting an attribute of the device, so that the peripheral device can execute a job permitted by the job execution permit. At the time of execution, the attribute of the device can be set by the device control command.

  Next, details of the present invention will be described in accordance with the description of the embodiments.

  FIG. 1 shows an example of the configuration of a peripheral device management system showing an embodiment of the present invention.

  In FIG. 1, an MFP 101 is a peripheral device connected to the network 110 to be managed in the peripheral device management system, and can process a print job, a scanner job, a copy job, a FAX transmission job, a FAX reception job, and a scanned image transmission job. A multi-function peripheral. In the present invention, the peripheral device constituting the peripheral device management system may be an MFP such as 101, a printer, a FAX or a scanner, or a peripheral device that can be connected to a network other than that. .

  PC 102 and PC 103 indicate information processing apparatuses connected to the network 110 such as a personal computer used when the user uses the peripheral device management system. Driver software, applications, and the like operate and send a job to the MFP 101 via the network. And job management.

  The DS 104 is a directory server that manages user information, PCs, and other device information in the management domain, and is configured using an information processing apparatus such as a PC or server. Hereinafter, information management as a function of the directory server may be performed by, for example, Active Directory, or may be configured using other directory server software.

  In this embodiment, in FIG. 1, the user uses the PC 102 or PC 103 to input a user name or password registered in advance in the DS 104, performs personal authentication, logs in, and then uses the PC to make a desired request. Set the job attributes and submit the job.

  The DS 104 can register and hold user information and device management information, refer to the user information and device management information held in response to a request from the PC 102 or PC 103, and if necessary, user information or device management information. To manage users and devices. Further, user authentication is performed in response to a request from the PC 102 or the PC 103 and the result is notified, or a job execution permit is generated and transmitted. In this embodiment, a peripheral device management system in which a directory server manages users, peripheral devices, and information processing apparatuses will be described. However, the directory server communicates with other directory servers connected via the network 110 to communicate with another directory server. An embodiment that performs user management and device management by referring to, acquiring, and updating user information or device management information directly managed by the server is also possible.

  Further, the PC 102 and the PC 103 communicate with the MFP 101 via the network 110, send a job submitted by the user to the MFP 101, and request job processing. These devices communicate with each other and operate by transmitting / receiving user information, device information, job data, and the like, thereby operating the peripheral device management system.

  FIG. 2 shows the overall configuration of a peripheral device representing an embodiment of the present invention.

  In FIG. 2, reference numeral 201 denotes a controller for controlling peripheral devices, and has a hardware configuration as shown in FIG. Reference numeral 202 denotes a communication interface for the controller 201 to communicate with the outside of the peripheral device, and may be, for example, an IEEE 1284 interface or other communication interface. A scanner engine 203 is controlled by the controller 201. A printer engine 204 is controlled by the controller 201 and may be, for example, a laser beam printer, an ink jet printer, or other printers. Reference numeral 205 denotes a FAX board for realizing a FAX function such as communication control at the time of image transmission / reception, and is controlled by the controller 201. A user interface 206 includes an LCD display and a keyboard, and displays information from the controller 201 and transmits an instruction from the user to the controller 201. The user transmits a job to the controller 201 using the PC 102 or the PC 103 connected via the network 110 by the user interface 206 or the communication interface 202.

  The peripheral device having the above configuration allows the printer engine 204 to be selected to issue a print job. In addition, the printer engine 204 and the scanner engine 203 are selected, and a copy job can be issued. In addition, the printer engine 204, the scanner engine 203, and the FAX board 205 are selected, and a FAX reception job and a FAX transmission job can be issued. Further, the scanner engine is selected, and a scan image transmission job can be issued.

  FIG. 3 is a schematic diagram showing a hardware configuration centering on the controller 201 of FIG. 2 includes the CPU 301, the RAM 302, the LCD 303, the keyboard 304, the ROM 305, the communication interface 306, the scanner engine 307, the printer engine 308, the FAX board 309, and the DISK 310 in FIG. Are connected to each other via a system bus 320. A program for controlling the controller 201 in FIG. 2 is stored in the ROM 305 or the DISK 310, read to the RAM 302 as necessary, and executed by the CPU 301. In addition to the control program, the ROM 305 and the DISK 310 store peripheral information, attribute information indicating functions and states of jobs processed by the peripheral equipment, job data to be output, and the like. In addition, the CPU 301 performs display through the LCD 303 and receives a user instruction from the keyboard 304. Further, the CPU 301 communicates with the outside through the communication interface 306.

  In the present embodiment, unless otherwise specified, in the peripheral device of FIG. 2, the CPU 301 receives user input from the keyboard 304 via the system bus 320, and the RAM 302, LCD 303, ROM 305, communication interface 306, The scanner engine 307, printer engine 308, FAX board 309, and DISK 310 are controlled and executed.

  FIG. 4 shows a hardware configuration of the information processing apparatus indicated by the PC 102, PC 103, and DS 104 in FIG.

  In FIG. 4, a CPU 401, a RAM 402, a CRT 403, a keyboard 404, a ROM 405, a DISK 406, and a communication interface 407 are connected to each other via a system bus 420. A program for controlling the information processing apparatus is stored in the ROM 405 or the DISK 406, read to the RAM 402 as necessary, and executed by the CPU 401. The CPU 401 communicates with the outside through the communication interface 407. The communication interface 407 may be a network interface or a wireless communication interface such as IEEE1394 or USB.

  In the present embodiment, in the information processing apparatus shown in FIG. 4, the CPU 401 receives user input from the keyboard 404 via the system bus 420, and the RAM 402, CRT 403, ROM 405, DISK 406, and communication interface 407. Control and implement.

  FIG. 5 shows an example of a series of processing sequences in which the PC 102 or PC 103, DS 104, and MFP 101 constituting the peripheral device management system in this embodiment communicate with each other to perform job processing. In FIG. 5, a PC 501 corresponds to the PC 102 or PC 103 in FIG. 1, a DS 502 corresponds to the DS 104, and an MFP 503 corresponds to the MFP 101. In response to the message 504, the user inputs a user ID and password via the PC 501, and attempts to log in. The PC 501 transmits a login request to the DS 502 according to the input from the user. Details of the processing of the message 504 will be described with reference to FIG. Next, in the message 505, if the DS 502 processes the login request and the login is successful, the login success notification is notified to the PC 501. If the login fails, a login failure notification is sent to the PC 501. Next, in the message 506, the PC 501 transmits a request to issue a job execution permit for the user who has successfully logged in to the DS 502. Note that the message transmission of 506 may be executed in response to the user login success notification of the message 505, or may be executed at an arbitrary timing prior to the job transmission by the message 508. Details of the processing of the message 506 will be described with reference to FIG. In the message 507, the job execution permit generated by the DS 502 is transmitted to the PC 501. Details of the processing of the message 507 will be described with reference to FIG. In the next message 508, the PC 501 transmits the job attached with the job execution permit received from the DS 502 in the message 507 to the MFP 503. Details of the processing of the message 508 will be described with reference to FIG. Next, in the message 509, the job received by the MFP 503 is analyzed and executed, and the result is sent to the PC 501 as a job end notification to complete a series of job processing sequences. Details of the processing of the message 509 will be described with reference to FIG.

  FIG. 6 shows an example of the configuration of execution permission information for each user held by the DS 104 in this embodiment. In FIG. 6, reference numerals 601 to 604 denote user IDs of user information managed by the DS 104, and hold access control information for each user ID. This access control information may be access control information for each existing device, but in this embodiment, it is assumed that the access control information is common to existing devices. For example, if it is permitted by the access control information of the color printing function, job execution is permitted for all devices capable of color printing managed by the DS 104. Unlike the present embodiment, in the embodiment for managing the access control information for each device, the access control information as shown in the present embodiment is held for each device and the access control is performed. For example, it is possible to limit users who can use a specific peripheral device.

  Each column will be described below. A column 610 indicates a user ID. A user managed by the DS 104 is identified by this user ID. A column 611 indicates access control information for the color printing function. A user whose column 611 is TRUE indicates that the use is permitted for the color printing function, and a user who is FALSE is not permitted for the color printing function. It shows that. A column 612 indicates access control information for the staple function, and a column 612 indicates that a user who is TRUE is permitted to use the staple function, and a user who is FALSE indicates that the user is not permitted to use the staple function. . A column 613 indicates access control information for the scan function. A column 613 indicates that a user who is TRUE is permitted to use the scan function, and a user who is FALSE indicates that the user is not permitted to use the scan function. . Column 614 shows access control information of an image transmission function that stores an image generated by scanning and transmits it by a method such as mail attachment. Column 614 indicates that a user who is TRUE is permitted to use the image transmission function. A user who is FALSE indicates that the use of the image transmission function is not permitted.

  In FIG. 6, the access control information for each function indicates permission or disapproval by TRUE or FALSE, but the access control information for each user managed by the DS 104 is not necessarily limited to this. For example, an embodiment may be used in which values such as PDF, JPEG, PostScript, and LIPS are listed for available document data formats, and values that can be set by the user as job attributes are listed. Further, the access control information may be an embodiment indicating a user-settable value range or upper limit value such as the maximum number of printed sheets of a job. Further, the functions subject to access control shown in FIG. 6 are color printing, color copying, color printing, stapling, scanning, sending scanned image by e-mail, storing scanned image in the device file box, or storing in the device file box. For example, image printing, FAX transmission, or FAX reception.

  The access control information also includes device control commands and parameter specifications for recording logs with thumbnails and setting job attributes and device attributes as responsibilities to be executed by peripheral devices during job execution. Some of them have

  FIG. 7 is a diagram illustrating an example of a configuration of a job that the information processing apparatus transmits to a peripheral device via a network. In FIG. 7, attribute information 700 of the job execution permit indicates attribute information regarding the job execution permit 701, information on the presence / absence of encryption, the encryption method when encrypted, and the digital signature by DS104. Contains information about the hash function used for. The MFP 101 can analyze the job execution permit by referring to the attribute information of the job execution permit. The job execution permit 701 is job execution permission information issued by the DS 104 according to the request of the PC 102 or 103 for the user, and includes a user ID and the like. In some embodiments, the job execution permit 701 is encrypted so that it cannot be browsed by the user, or is electronically signed so that it cannot be edited. Details of the job execution permit will be described with reference to FIG. An attribute list 702 is a list of job attributes indicating job characteristics and types. Details of job attributes will be described later. Job data 703 indicates the document data itself of the job to be executed. For example, document data or image data expressed in a page description language. Next, details of the attribute list 702 will be described. Columns 711 and 712 show details of the attribute list 702, and show attribute names and attribute values, respectively. The column 711 may be anything that identifies an attribute. For example, a numeric attribute identification number, a character string, or other attribute identifier may be used. A column 712 indicates attribute values indicated by the column 711. In the list of attributes constituting the job shown in FIG. 7, the client job identifier 721 for identifying the job generated in the MFP 101 by the PC 102 or PC 103 is “1234”, and the job name 723 set by the PC 102 or PC 103 is “Patent specification”, job type 725 is “print job”, color printing 727 is “Yes”, paper selection 729 is “A4”, and double-sided printing 731 is “front side printing”. Respectively. By using the job attribute list 702, the PC 102 or PC 103 can set details such as the characteristics and types of the job to be transmitted to the MFP 101 and executed.

  FIG. 8 shows an example of the configuration of a job execution permit generated and issued by the directory server in response to a job execution permit issuance request from the information processing apparatus, and corresponds to 701 in FIG. In FIG. 8, a user ID 801 indicates an ID for identifying a user who is the object of this job execution permit. The job execution permit is valid only for the user indicated by the user ID. Job execution permission information 802 indicates job execution permission information related to a user who is a target of the job execution permit indicated by the user ID 801. Details of the job execution permission information will be described with reference to FIG. The expiration date information 803 indicates information regarding the expiration date of the job execution permit. For example, the date and time, the serial number, and the issue date and time are set and issued to prevent unauthorized use due to reuse of the job execution permit shown in FIG. The digital signature 804 of the DS 104 indicates a data string for proving that it is a job execution certificate issued by the DS 104 that is an issuer in order to detect the alteration of the job execution certificate shown in FIG. For example, the hash value of the entire job execution permit is taken, the hash value is encrypted with a secret key known only by the DS 104, and the result is attached. Since data encrypted with the DS104 private key can be decrypted only with the corresponding DS104 public key, if the public key is a public key corresponding to the DS104 private key, the MFP 101 calculates from the received job execution permit. By comparing the hash value with the decrypted hash value, it can be confirmed that the job execution permit has not been altered. In the present embodiment, the job execution permit includes a session key for performing encrypted communication with the PC 102 or the PC 103 in addition to 801 to 803 in FIG. 8 and a user certificate. May be. The configuration from 801 to 803 may be a configuration in which the digital signature 804 of the DS 104 is attached after being encrypted with an encryption key that the MFP 101 can decrypt.

  FIG. 9 is a flowchart showing the flow of processing in which the PC 501 logs in the user in FIG. In step 901, the PC 501 allows the user to input a user ID and a password and accepts a user login request. It is assumed that the user ID and password are registered in advance in the DS 502. In step 902, the PC 501 transmits the user ID and password input in step 901 to the DS 502, and transmits an authentication request for the user. In step 902, the PC 501 may send the user ID and password itself to the DS 502. However, since it is a security problem to send the password via the network, it is numerical information calculated from the user ID and password. There may be. In this case, the DS 502 compares the received user ID and numerical information with numerical information calculated from the user ID and password of the user registered in advance. Next, in step 903, if the user authentication result from the DS 502 is received and the authentication result is successful, the process proceeds to step 904. If the authentication result is unsuccessful, the process proceeds to step 905. In step 904, the user is notified of successful login and the login process is terminated. In step 905, the user is notified that the login has failed and the login process is terminated.

  FIG. 10 is a flowchart showing a flow of processing in which the PC 501 requests the DS 502 to issue a job execution permit prior to job transmission in FIG. In FIG. 10, in step 1001, the PC 501 extracts a job execution permission request item necessary immediately after the user logs in or immediately before the user issues the job. If it is immediately after the user logs in, attributes of all executable jobs are extracted, and if it is immediately before the job is issued, attributes necessary for setting the job to be issued are extracted. In step 1002, the job execution permission request item extracted in step 1001 is designated, and a job execution permission issuance request is transmitted to the DS 502. At this time, if the request item for job execution permission is not designated, it indicates that the request is for issuing a job execution certificate indicating all executable jobs. In step 1003, the job execution permit transmitted from the DS 502 in response to the job execution permit issuance request transmitted in step 1002 is received and stored, and the job execution permit request process is terminated.

  FIG. 11 is a flowchart showing a processing flow in which the DS 502 issues a job execution permit in response to a request from the PC 501 in FIG. In FIG. 11, in step 1101, a job execution permit issuance request from the PC 501 is received and stored. In step 1102, the contents of the job execution permit issuance request received in step 1101 are analyzed to create necessary job execution permission items. In step 1103, the job execution permission information held by the DS 502 is acquired, and the process proceeds to the next step. Details of the job execution permission information are described in FIG. In step 1104, the job execution permission information is searched with the user ID of the user to determine whether the user has job execution permission information. If there is job execution permission information, the flow proceeds to step 1105 as job execution permission, and if there is no job execution permission information, the flow proceeds to step 1106 as job execution disapproval. In step 1105, the requested job execution permit is generated by comparing the job execution permission information of the user with the issue request content analyzed in step 1102. In step 1107, the job execution permit generated in step 1105 is encrypted. The encryption may be encryption that is difficult for the PC 501 to decrypt and the MFP 503 can decrypt, for example, encryption using the public key of the MFP 503. Further, an embodiment in which the encryption in step 1107 is not performed may be used as necessary. In step 1108, the digital signature of the DS 502 itself is applied to the entire generated job execution permit to prove that the issued job execution permit is issued by the DS 104 and to prevent tampering. In step 1109, the job execution permit that has been generated and electronically signed is transmitted to the requesting PC 501, and the job execution permit issuance process is terminated. In step 1106, since the user is not permitted to execute the job, a job execution certificate generation failure notification is transmitted to the requesting PC 501 and the job execution certificate issuance process is terminated.

  FIG. 12 is a flowchart showing a flow of processing in which the PC 501 acquires a job execution permit in response to a user operation and issues a job. In step 1201, the PC 501 determines whether or not a job execution permit necessary for issuing a job corresponding to the user's operation has been acquired in advance. If it has not been acquired, the process proceeds to step 1202, and if it has been acquired, the process proceeds to step 1203. In step 1202, the process as shown in FIG. 7 is performed to obtain a job execution permit necessary for issuing a job according to the user's operation, the job execution permit is obtained, and the process proceeds to step 1203. move on. In step 1203, a job to be transmitted to the MFP 503 for processing is generated. However, appropriate attributes have not yet been set at the time of generation. In step 1204, appropriate attributes are set for the job generated in step 1203 according to the user's operation. Details of the attributes to be set are as shown in FIG. In step 1205, the job execution permit acquired in advance or the job execution permit acquired in step 1202 is attached to the job in which appropriate attributes are set in step 1204. In step 1206, the job is generated up to step 1205, an appropriate attribute is set, and a job attached with a job issuance permit is transmitted to the MFP 501, and the process ends. Through the above processing, the PC 501 transmits a job with a job execution permit to the MFP 503.

  FIG. 13 is a flowchart of processing executed when the MFP 503 receives a job. In FIG. 13, in step 1301, the job transmitted from the PC 501 by the process as shown in FIG. 12 is received and held. In step 1302, the job received in step 1301 is analyzed and a job execution permit is taken out. The job execution permit is obtained by the PC 501 in FIG. 12 from the DS 502 and attached to the job, and the configuration is as shown in FIG. In step 1303, the job execution permit taken out in step 1302 is analyzed, and the contents of the job execution permit are read. In step 1304, the content of the job execution permit read in step 1303 is compared with the attribute of the received job, and whether or not the attribute of the job can be set and whether or not a settable value is specified. Judging. In step 1305, if the job attribute is the content permitted by the attached job execution permit based on the comparison and determination in step 1304, it is determined that the received job is permitted to proceed to step 1306. If it does not match the content permitted by the job execution certificate, the process proceeds to step 1308 because the execution is not permitted. In step 1306, it is determined whether a device execution command is included in the job execution permit. If the device control command is not included, the job can be processed according to the job attribute, and the process advances to step 1308. If a device control command is included, it is necessary to process the device control command prior to job processing and satisfy the job execution permission condition, and the process advances to step 1307. In step 1307, the device control command as shown in FIG. 15 is processed and the process proceeds to the next step 1308. Details of the processing of the device control command in step 1307 will be described with reference to FIG. In step 1308, the job is processed according to the device attribute and the job attribute to obtain the designated output. For example, in the case of a print job, a print job that is input by the user using the PC 501 is output. In step 1309, the PC 501 is notified that the processing of the job has been completed, and the processing ends. On the other hand, in step 1310, the PC 501 is notified that the execution of the job has been rejected, and the process ends.

  FIG. 14 is an example of job execution permission information included in the job execution permit indicated by 802 in FIG. The job execution permission information includes an output permission number indicated by 1401, an execution permission function indicated by 1402, and a device control command indicated by 1403. The job execution permission information may be configured to include all of these, or may be configured to include either the permitted number of sheets, the permitted function, or the device control command. Reference numerals 1404 to 1407 denote examples of device control commands indicated by 1403. 1404 indicates that the E-mail notification is set to ON as a job attribute by the SetJob command, and admin@abc.com is set as the destination of the E-mail notification as a job attribute by the SetJob command. When the MFP 503 executes the job including the job execution certificate by processing the device control command 1404, it indicates that the user's job has been processed by admini@abc.com together with the user ID and job type. Notify the address by e-mail. As a result, the recipient of the E-mail notification can detect that the user has executed an unauthorized job and can measure the frequency of job execution in real time. Can be suppressed. Reference numeral 1405 indicates that the log with thumbnail is set to ON as a job attribute by the SetJob command. When the MFP 503 executes a job including the job execution permit by processing the device control command 1405, the MFP 503 generates a thumbnail of an image to be output together with the user ID, job type, and the like, and holds it as a log of the executed job To do. As a result, if logs with thumbnails are held for all jobs, a large storage area of a medium such as DISK indicated by 310 in FIG. 3 is required. The log can be held, and the area of the holding medium can be saved. Further, in the case of the embodiment in which the job execution permit is encrypted, it is impossible for the user to detect whether or not the job to be executed is held as a log with a thumbnail, so that unauthorized output of the user can be suppressed. . Reference numeral 1406 indicates that the output instruction waiting printing is set to ON as a job attribute by the SetJob command. When the MFP 503 executes the job including the job execution permit by processing the device control command 1406, the MFP 503 executes the job in the output instruction waiting mode. In a job in the output instruction waiting mode, after generating a job, the job is temporarily held in the MFP 503 and waits for an output instruction from the outside. When the user operates the MFP 503 to give an output instruction, the held job is output. By performing output instruction waiting printing, the printed matter output by the user is not taken away by mistake before going to the MFP 503, and the executed user can surely obtain the printed matter. In addition, as another output instruction waiting print, it is possible to instruct the job execution permit to input an output instruction by inputting a password.

  Reference numeral 1407 indicates that the color output is set to OFF as a job attribute by the SetJob command. When the MFP 503 executes the job including the job execution certificate by processing the device control command 1407, the MFP 503 sets the color output attribute of the job to OFF and does not output it in color. This prevents the color output from being set to OFF by the device control command in the job execution permit even when the user has set the color output as the job attribute as shown in FIG. Can do.

  FIG. 15 shows a processing flow when the MFP 503 shown in step 1307 of FIG. 13 receives a job and analyzes the job execution permit, and a device control command is included in the job execution permit. The details of the device control command are as described in FIG. In FIG. 15, in step 1501, the device control command included in the job execution permit is analyzed to acquire the command type and command parameter, and the process proceeds to the next step 1502. In step 1502, it is determined whether or not the command type is SetJob for setting job attributes. If it is a SetJob command, the process proceeds to step 1503. If the command type is not SetJob, the process proceeds to step 1504. In step 1503, the job attribute is set with the value specified by the SetJob command. For example, if color printing is specified as OFF by the SetJob command, color printing that is a job attribute is set to OFF. If job attributes are set, the process advances to step 1507. In step 1504, it is determined whether or not the command type is Set for setting the attribute of the device. If it is a Set command, the process proceeds to Step 1505. If the command type is not the Set command, the process proceeds to step 1506. In step 1505, the attribute of the device is set with a value specified by the Set command. For example, if a new user ID is specified for the registered user ID by the Set command, the new user ID specified by the Set command is set to the registered user ID that is an attribute of the device. If the attribute of the device is set, the process proceeds to step 1507. In step 1506, since the device control command is other than the SetJob command or the Set command, processing corresponding to the command is performed. For example, a process for temporarily stopping the device or a process for specifying a complete disk format for completely erasing data remaining in the disk 310 after the job is executed can be considered. When the device control command is processed, the process proceeds to step 1507. In step 1507, it is determined whether there is any device control command included in the job execution permit that has not been processed. If there is a command that has not been processed, the unprocessed command is determined. Then, the process proceeds to step 1501. If no command processing is performed, all device control commands included in the job execution permit have been processed, and the device control command processing in the job execution permit is completed.

It is a figure which shows an example of a structure of the peripheral device management system of this invention. It is a figure which shows an example of a structure of the peripheral device of this invention. It is a figure which shows an example of the hardware constitutions of the controller of FIG. It is a figure which shows an example of the hardware constitutions of the information processing apparatus of this invention, and a directory server. FIG. 3 is a diagram illustrating an example of a configuration of a job transmitted from an information processing apparatus to a peripheral device. It is a figure which shows an example of a structure of the execution permission information for every user hold | maintained at a directory server. It is an example of the sequence of the system which the peripheral device management system of this invention performs a job process. It is a figure which shows an example of a structure of a job execution permit. It is a flow of processing in which an information processing apparatus logs a user into a peripheral device management system. It is a flow of processing in which the information processing apparatus acquires a user job execution permit. It is a flow of processing in which the directory server issues a user job execution certificate. It is a flow of processing in which the information processing apparatus transmits a job to a peripheral device. It is a processing flow when a peripheral device receives a job. It is a figure which shows an example of a structure of job execution permission information. It is a flow for processing a control command included in a job execution permit of a job received by a peripheral device.

Explanation of symbols

101, 503 MFP (peripheral equipment)
102, 103, 501 PC (information processing device)
103, 502 DS (directory server)

Claims (8)

In a peripheral device management system configured by an information processing device, a directory server, and peripheral devices connected via a network, the peripheral device processes a job transmitted from the information processing device via the network.
The information processing apparatus transmits an issuance request for issuing a job execution certificate to the directory server prior to job transmission;
Job sending means for sending the job with a job execution permit obtained by the issuing request means,
The directory server has a job execution permit issuing means for receiving a job execution permit issuing request from the information processing apparatus and issuing a job execution permit;
The peripheral device analyzes a job transmitted from the information processing apparatus and identifies the job execution permit;
Job execution permit analysis means for analyzing the identified job execution permit;
A peripheral device management system, comprising: a control unit that operates according to a control command included in the job execution permit. The directory server has means for holding job execution permission information for each user;
The job execution certificate issuing unit generates a job execution certificate according to job execution permission information held by the directory server;
The peripheral device management system according to claim 1, further comprising: an encryption unit that encrypts the generated job execution permit. The directory server has means for acquiring job execution permission information for each user from the outside through a network,
The job execution permit issuing means generates a job execution permit according to job execution permission information acquired by the acquiring means,
The peripheral device management system according to claim 1, further comprising: an encryption unit that encrypts the generated job execution permit.   4. The peripheral device management system according to claim 2, wherein the job execution permit analysis unit included in the peripheral device includes a decryption unit for the encrypted job execution permit.   5. The job execution permit includes a device control command executed by a peripheral device when executing the job and information indicating a parameter of the command. Peripheral device management system.   The job execution permission information held by the directory server or acquired from the outside for each user includes a device control command executed by a peripheral device when executing the job and information indicating a parameter of the command. The peripheral device management system according to claim 5.   The peripheral device management system according to claim 5 or 6, wherein the device control command included in the job execution permit is a command for setting job attributes.   The peripheral device management system according to claim 5 or 6, wherein the device control command included in the job execution permit is a command for setting a device attribute.

Images