阅读说明：本技术 图像形成设备、打印系统、控制方法及存储介质 (Image forming apparatus, printing system, control method, and storage medium ) 是由 金田健 金本好司 饭田利彦 金井康赖 于 2018-12-19 设计创作，主要内容包括：MFP(101)存储用于在打印数据中共同地设置与图像形成有关的多个设置内容的设置信息。MFP(101)进行控制,以使得响应于接受到经由经认证用户进行的操作所发出的用于将设置信息登记在图像形成装置中的登记请求,将设置信息登记在存储部件中使得所存储的设置信息具有使用经认证用户的识别信息能够参考设置信息的数据结构。响应于接受到来自打印客户端的包括用户的识别信息的用以获取用户可以使用的与图像信息有关的属性信息的请求,MFP(101)基于所述识别信息获取用户使用的设置信息,并发送包括该设置信息的属性信息。(An MFP (101) stores setting information for collectively setting a plurality of setting contents related to image formation in print data. The MFP (101) controls so that, in response to accepting a registration request issued via an operation by an authenticated user to register setting information in the image forming apparatus, the setting information is registered in the storage means so that the stored setting information has a data structure in which the setting information can be referred to using identification information of the authenticated user. In response to accepting a request from a print client to acquire attribute information about image information that can be used by a user, including identification information of the user, an MFP (101) acquires setting information used by the user based on the identification information, and transmits the attribute information including the setting information.)

1. An image forming apparatus, comprising:

a storage section configured to store setting information for collectively setting a plurality of setting contents related to image formation in print data;

a registration section configured to register the setting information in the storage section so that the stored setting information has a data structure that enables the setting information to be referred to using identification information of an authenticated user, in response to accepting a registration request issued via an operation of the authenticated user to register the setting information in the image forming apparatus; and

a transmission section configured to acquire, in response to reception of a first acquisition request including identification information of a user from a print client via a network to acquire attribute information relating to image formation that enables the user to use, setting information used by the user from the setting information stored in the storage section based on the identification information, and transmit the attribute information including the setting information.

2. The image forming apparatus according to claim 1, wherein the print client is a print client that transmits a print job to the image forming apparatus using an IPP (internet printing protocol).

3. The image forming apparatus according to claim 1 or 2, wherein the transmission means is configured to transmit the attribute information including the setting information that enables reference without user authentication, in response to acceptance of a second acquisition request to acquire the attribute information relating to image formation from the print client via the network, which is different from the first acquisition request.

4. The image forming apparatus according to claim 3, wherein the setting information that is made referable without user authentication is registered by a user having an administrative authority of the image forming apparatus.

5. The image forming apparatus according to claim 3 or 4, wherein the attribute information transmitted in response to receiving the first acquisition request further includes setting information that enables reference without user authentication.

6. The image forming apparatus according to any one of claims 1 to 4, further comprising a management section configured to manage a user who uses the image forming apparatus, wherein,

the management section manages the user by associating the user with a group,

the registration means registers the setting information in association with a group identified based on identification information of the authenticated user, an

The transmission means identifies a group of users based on identification information included in a first acquisition request for acquiring attribute information related to image formation that enables the users to use, and transmits attribute information including setting information stored in association with the group.

7. The image forming apparatus according to any one of claims 1 to 6, wherein even in a case where the registration means accepts a registration request for registering the setting information from the authenticated user, the registration means does not register the setting information in response to the registration request in a case where the number of registered setting information for use by the user reaches a predetermined upper limit.

8. The image forming apparatus according to any one of claims 1 to 7, further comprising a notification section configured to issue a predetermined notification when the number of registered setting information for use by the authenticated user reaches a predetermined upper limit upon accepting a registration request for registering the setting information from the user.

9. The image forming apparatus according to any one of claims 1 to 8, further comprising:

a reception section configured to receive print data from a print client via a network; and

an image forming section configured to form an image on a sheet based on the print data received by the receiving section.

10. The image forming apparatus according to any one of claims 1 to 8, further comprising a Web server, wherein,

the Web server is configured to provide a Web page for registering the setting information to a Web browser.

11. The image forming apparatus according to claim 10,

the first acquisition request is sent from the print client using IPP, an Internet print protocol, and

wherein the image forming apparatus further includes a control section configured to, in a case where the image forming apparatus is not set to enable printing using the print client, control such that the Web page is not provided even in a case where an HTTP request for accessing the Web page for registering the setting information is accepted from the Web browser.

12. A printing system comprising an image forming apparatus and a communication terminal, wherein the image forming apparatus comprises:

a storage section configured to store setting information for collectively setting a plurality of setting contents related to image formation in print data;

a registration section configured to register the setting information in the storage section so that the stored setting information has a data structure that enables the setting information to be referred to using identification information of an authenticated user, in response to accepting a registration request issued via an operation of the authenticated user to register the setting information in the image forming apparatus; and

a first transmission section configured to acquire setting information used by a user from the setting information stored in the storage section based on identification information in response to reception of a first acquisition request including the identification information of the user from the communication terminal via a network to acquire the attribute information related to image formation that is enabled to be used by the user, and transmit the attribute information including the setting information,

the communication terminal includes:

a display control section configured to display a print setting screen on an operation unit;

a second transmission section configured to transmit, to the image forming apparatus, a registration request for registering setting information based on the print setting made via the print setting screen, in response to acceptance of a predetermined user operation; and

a third transmission section configured to transmit, to the image forming apparatus, a first acquisition request for acquiring attribute information relating to image formation that enables a user to use, including identification information of the user.

13. The printing system according to claim 12, wherein each component included in the communication device is implemented by a specific print client application embedded in an OS of the communication device.

14. A control method of an image forming apparatus, the control method comprising:

storing and controlling so that, in response to acceptance of a registration request for registering, in the image forming apparatus, setting information for collectively setting a plurality of setting contents related to image formation in print data based on an operation performed by an authenticated user, the setting information is stored in a storage unit so that the stored setting information has a data structure that enables the setting information to be referred to using identification information of the authenticated user; and

the transmission is performed such that, in response to acceptance of a first acquisition request including identification information of a user from a print client via a network to acquire attribute information relating to image formation that enables the user to use, setting information used by the user is acquired from the setting information stored in the storage unit based on the identification information, and the attribute information including the setting information is transmitted.

15. A computer-readable storage medium storing a program for causing a computer to execute the method of controlling the image forming apparatus according to claim 14.

Technical Field

The present invention relates to an image forming apparatus, a printing system, a control method, and a storage medium configured to receive data and form an image.

Background

In a conventionally known image forming apparatus, print data is received from a communication apparatus via a network, and an image is formed on a sheet based on the received print data. It is also known to generate print data to be transmitted to image forming apparatuses using a printer driver (or a print application) designed to use each image forming apparatus.

Further, in recent years, it has been known to generate print data without using a printer driver (or a print application) designed to use each image forming apparatus. For example, a manner is known for generating print data by a general-purpose print client provided as a function of an Operating System (OS) of a communication apparatus or a general-purpose print client provided by a print server on the cloud, and transmitting the print data to an image forming apparatus. In such a general-purpose print client, a mechanism for printing based on a network protocol (IPP: internet print protocol) for causing an image forming apparatus to perform printing is realized. The print processing is realized by performing communication between the image forming apparatus and the communication apparatus according to the protocol.

For example, patent document 1 discloses the following: when an image is selected on the screen of the communication apparatus and printing of the image is instructed, a search for nearby image forming apparatuses is performed, and the retrieved image forming apparatuses are displayed in a list. Further, it is described that a protocol suitable for transmitting image data is selected based on protocol information supported by the selected image forming apparatus, and the image data for printing is transmitted using the selected protocol.

Reference list

Patent document

Patent document 1: japanese patent laid-open publication No. 2013-187571

Disclosure of Invention

Problems to be solved by the invention

In PWG (printer workgroup), IPP specifications are being developed, and print preset functions for providing enhanced convenience to users in print clients based on IPP are being discussed. In print presets (IPP presets) of the specifications being developed by the PWG, a name is given to a set of combinations of print setting items and print setting values. Using the print presets makes it possible to collectively reflect various setting items such as double-sided printing, color setting, and/or bookbinding setting in the print settings, and thus it is possible to provide high convenience to the user.

Such a print preset may be stored in a storage area or the like of the image forming apparatus in advance, and may be provided to a print client that cooperates with the image forming apparatus.

The print presets suitable for use by the user may differ from user to user depending on the user's preference or the job in which the user participates. In order to provide improved convenience to users, if print presets for respective users are stored only in an image forming apparatus, the total size of print preset data stored in the image forming apparatus may be enormous. In this case, if all the print presets stored in the image forming apparatus are provided to the print client, it may be difficult for the user to find a desired print preset from among a large number of print presets.

In order to cope with the above situation, it is possible to allow registration of the print preset in the image forming apparatus in a range lower than the upper limit of the print preset number, thereby preventing the setting from becoming complicated. However, the problem in this case is that it is impossible to cover all the print presets for the user to use.

The present invention has been made in view of at least one of the above problems. An object of the present invention is to provide a mechanism that stores correspondence information between a user and a print preset, thereby making it possible to appropriately provide a notification of the print preset used by the user to a communication device using a print client. Another object of the present invention is to provide a mechanism capable of appropriately registering a print preset based on an operation of an authenticated user.

Means for solving the problems

To achieve at least one of the above objects, the present invention provides an image forming apparatus comprising: a storage section configured to store setting information for collectively setting a plurality of setting contents related to image formation; a registration section configured to register the setting information in the storage section so that the stored setting information has a data structure that enables the setting information to be referred to using identification information of an authenticated user, in response to accepting a registration request issued via an operation of the authenticated user to register the setting information in the image forming apparatus; and a transmission section configured to acquire, in response to reception of a first acquisition request for acquiring attribute information relating to image formation, which is usable by a user, including identification information of the user from a communication apparatus, setting information used by the user from the setting information stored in the storage section based on the identification information, and transmit the attribute information including the setting information.

ADVANTAGEOUS EFFECTS OF INVENTION

According to the present invention, correspondence information between a user and a print preset is stored, so that a notification of the print preset used by the user can be appropriately provided to a communication device using a print client. In aspects of the present invention, a mechanism for appropriately registering a print preset based on an operation of an authenticated user may be provided.

Drawings

The accompanying drawings, which are incorporated in and form a part of the specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the invention.

Fig. 1 is a diagram illustrating an example of an image forming system.

Fig. 2 is a diagram showing an example of the hardware configuration of the MFP 101.

Fig. 3 is a diagram showing an example of the software configuration of the MFP 101.

Fig. 4 is a diagram showing an example of the hardware structure of the communication device 102.

Fig. 5 is a sequence diagram showing an example of a processing procedure in the image forming system.

Fig. 6 is a sequence diagram showing an example of a processing procedure in the image forming system.

Fig. 7A is a diagram showing an example of setting information stored in the MFP 101.

Fig. 7B is a diagram showing an example of setting information stored in the MFP 101.

Fig. 7C is a diagram showing an example of the setting information stored in the MFP 101.

Fig. 8A is a diagram showing an example of a request for attribute information and an example of a response.

Fig. 8B is a diagram showing an example of a request for attribute information and an example of a response.

Fig. 9 is a diagram showing an example of print data generated by the communication device 102.

Fig. 10A is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 10B is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 10C is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 11A is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 11B is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 11C is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 11D is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12A is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12B is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12C is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12D is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12E is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12F is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 12G is a diagram showing an example of a screen displayed on the operation unit of the communication device 102.

Fig. 13 is a flowchart showing an example of control of the communication device 102.

Fig. 14 is a flowchart showing an example of control of the communication device 102.

Fig. 15 is a flowchart showing an example of control of the communication device 102.

Fig. 16 is a flowchart showing an example of control of the MFP 101.

Fig. 17 is a flowchart illustrating an example of control of the MFP 101.

Fig. 18 is a flowchart showing an example of control of the MFP 101.

Detailed Description

The invention is described below with reference to embodiments in conjunction with the accompanying drawings. It should be noted that the following examples do not limit the invention as defined in the claims. It should also be noted that not all combinations of features described in the embodiments are necessary to implement the invention.

< first embodiment >

First, referring to fig. 1, the structure of an image forming system according to the present invention is explained below. The image forming system according to the present embodiment includes communication devices 102a to 102c, an MFP (multi function peripheral) 101, and an AP (access point) 103. The MFP101, the AP 103, and the communication device 102c are connected to the network 100 so that they are allowed to communicate with each other. In the present embodiment, the MFP101 is described as an example of an image forming apparatus. Further, the communication devices 102a to 102b and the communication device 102c are described as examples of the communication devices. In the present embodiment described below, a case where the communication device 102a is a tablet terminal, the communication device 102b is a mobile terminal such as a smartphone, and the communication apparatus 102c is a PC (personal computer) is described by way of example.

The communication devices 102a and 102b can communicate with each other via the AP 103 and the MFP101 on the network 100. The communication device 102c is connected to the network 100 via a LAN cable, and therefore the communication device 102c can communicate with a device such as the MFP101 on the network 100. In the present embodiment, the above results are described as an example of the image forming system, but the present invention is not limited to this structure. It is sufficient if at least one communication apparatus and the image forming apparatus are communicatively connected to each other via a network. The communication via the AP 103 is, for example, wireless communication based on IEEE 802.11 series. Note that the communication device 102 and the MFP101 can directly communicate with each other by Direct wireless communication via an ad hoc network such as Wi-Fi Direct (registered trademark) or Wi-Fi Aware (registered trademark).

First, the MFP101 will be explained. The MFP101 has a reading function of reading an image on an original and a printing function of printing an image on a sheet. The MFP101 can execute print processing based on print data received via a network.

Fig. 2 is a diagram showing an example of the hardware configuration of the MFP 101. The MFP101 has a reading function for reading an image on a sheet and a printing function for printing the image on the sheet. In addition, the MFP101 has other functions such as a file transmission function for transmitting an image to an external communication apparatus.

Although the MFP101 is described as an example of the image forming apparatus according to the present embodiment, the image forming apparatus is not limited to the MFP 101. For example, the present embodiment can be applied to a printing apparatus such as an SFP (single function peripheral) or the like which is usable without a reading function.

A control unit 110 including a CPU (central processing unit) 111 controls the operation of the entire MFP 101. The CPU111 reads out a control program stored in a ROM (read only memory) 112 or a storage device 114, and performs various controls such as print control and read control. The ROM 112 stores a control program executable by the CPU 111. A RAM (random access memory) 113 is a main memory used by the CPU111 as a work area or a temporary storage area in which various control programs are loaded. The storage device 114 stores print data, image data, various programs, and various setting information. In the present embodiment, an auxiliary storage device such as an HDD (hard disk drive) or the like is assumed as the storage device 114, but a nonvolatile memory such as an SDD (solid state drive) or the like may be used instead of the HDD. Note that the above-described hardware units such as the CPU111, the ROM 112, and the RAM113 constitute a so-called computer.

In the MFP101 according to the present embodiment, it is assumed that one CPU111 executes various processes described later with reference to the flowcharts using one memory (RAM113), but these processes may be executed in other manners. For example, various processes described later with reference to the flowcharts can be cooperatively executed among a plurality of CPUs, RAMs, ROMs, and storage devices. Note that part of these processes may be performed by using a hardware circuit such as an ASIC (application specific integrated circuit) or an FPGA (field programmable gate array).

An operation unit interface (I/F)115 connects the operation unit 116 and the control unit 110. The operation unit 116 includes a liquid crystal display unit having a touch panel function, and various hard keys and the like, thereby functioning as a display unit for displaying information and a receiving unit for receiving an instruction issued by a user.

The reading unit I/F117 connects the reading unit 118 and the control unit 110. The reading unit 118 reads an original and generates a read image. The generated read image is stored in the storage device 114 or the RAM 113. The read image generated by the reading unit 118 is transmitted to a communication apparatus or used to print an image on a sheet.

The image processing unit 124 includes a RIP (raster image processing) for converting print data received via a network into print image data. The image processing unit 124 may also perform resolution conversion and correction processing on the image. In the present embodiment, it is assumed that the image processing unit 124 is implemented by a hardware circuit (such as an ASIC or FPGA), but this is by way of example and not limitation. For example, the MFP101 may include a processor for image processing, and the processor may execute an image processing program, thereby realizing image processing and print data conversion processing. In this case, a flowchart to be described later is realized in cooperation between the image processing processor and the CPU 111. Further, the CPU111 can execute a program for performing image processing to perform image processing and print data rasterization processing. Note that image processing may be performed by any one of these combinations.

The printing unit I/F119 connects the printing unit 120 and the control unit 110. A print image generated by the analysis of the print data by the image processing unit 124 is transmitted from the control unit 110 to the print unit 120 via the print unit I/F119. The printing unit 120 receives a control command and a print image via the control unit 110, and prints the image on a sheet fed from a paper feed cassette (not shown) based on the image. The printing method used by the printing unit 120 may be an electrophotographic method or an inkjet method, or may be another printing method such as a thermal transfer method. The sheet processing unit I/F121 connects the control unit 110 and the sheet processing unit 122. The sheet processing unit 122 receives a control command from the CPU111, and performs post-processing on sheets printed by the printing unit 120 according to the control command. For example, post-processing includes aligning, perforating, and/or stapling a plurality of sheets, and the like. The post-processing function and post-processing capability of the sheet processing unit 122 are notified to the control unit 110 via the sheet processing unit I/F121 in advance (e.g., at the time of MFP startup), and the notified information is stored in the storage device 114 or the RAM 113.

The control unit 110 is also connected to the network 100 via a communication unit I/F123. The communication unit I/F123 transmits images and information to the communication apparatuses on the network 100, and receives print data and information from the communication apparatuses on the network 100.

Next, the hardware structure of the communication device 102 is explained with reference to fig. 3. Fig. 3 is a diagram showing a hardware configuration of the communication device 102.

The CPU131 included in the control unit 130 reads a control program stored in the ROM 132 or the storage device 134, and controls the communication apparatus 102.

The control unit 130 includes a CPU131, a ROM 132, a RAM133, a storage device 134, a communication unit I/F143, and an operation unit I/F135 connected to the bus.

The CPU131 is a central processing unit (processor) that controls the overall operation of the control unit 130. The RAM133 is a volatile memory, and is used as a work area and a temporary storage area where various control programs stored in the ROM 132 and the storage device 134 are loaded.

The ROM 132 is a nonvolatile memory in which a boot program and the like of the communication apparatus are stored. The storage device 134 is a nonvolatile flash memory having a larger capacity than the RAM 133. The storage device 134 stores a control program of the communication apparatus 102. Further, an OS (operating system) for controlling the entire communication apparatus 102 and a print client compliant with IPP (internet print protocol) are also stored in the storage device 134.

The CPU131 executes the OS program and the print client program loaded in the RAM133 to control the communication apparatus. Note that the above-described hardware units such as the CPU131, the ROM 132, and the RAM133 constitute a so-called computer.

In the communication device 102, it is assumed that one CPU131 executes various processes described later with reference to the flowcharts, but these processes may be executed in other manners. For example, a plurality of processors may cooperate with each other to execute various processes shown in flowcharts described later.

The operation unit I/F135 connects the operation unit 136 and the control unit 130. The operation unit 136 includes a touch panel capable of detecting a touch operation performed by a user, and a display panel for displaying various screens. The operation unit 136 functions as a display unit for displaying information and as a receiving unit for receiving an instruction issued by a user. Various screens provided by the OS or the print client are displayed on the operation unit 136. The user is allowed to input a desired operation instruction to the communication device 102 by performing a touch operation on the operation unit 136 using an object such as a finger or the like. The operation unit 136 may include hardware keys. In this case, the user is allowed to input an operation instruction to the communication device 102 by pressing a hardware key.

The communication unit I/F143 is an interface for communicating with a communication device. For example, in the case where the communication device is the tablet terminal 102a or the smartphone 102b, data may be transmitted/received to/from the communication device on the network 100 via the AP 103. In the case where the communication apparatus is the PC 102c, the communication apparatus may be configured to transmit/receive data to/from a communication device on the network 100 via a LAN cable.

As described above, each communication device 102 stores therein a program (also referred to as a print client application) for realizing the print client function. It is assumed that a program for realizing the function of the print client is installed in the communication device 102 via an application server (not shown), or that a program for realizing the function of the print client is incorporated as a basic function of the OS.

< software configuration of MFP101 >

Fig. 4 is a diagram showing an example of the software configuration of the MFP101 according to the present embodiment.

The MFP101 has a Web server 416 that provides a Web server function, and Web services (414 and 415) that operate on the Web server to provide certain services.

When Web server 416 receives an HTTP request via HTTP (hypertext transfer protocol) communication, Web server 416 distributes the request to a Web service specified by the request, and controls so that the Web service provides the specified service. The Web server 416 determines a Web service to which the request is to be allocated based on a port number and a URL (uniform resource locator) included in the request.

The IPP service 414 is a Web service that provides an external terminal such as a communication device with a Web-based printing service compliant with IPP. The IPP service 414 has a function of notifying the communication device of attribute information of the MFP101 (information indicating the printing capability and post-processing capability of the MFP101 and print presets), and a function of receiving print data conforming to the IPP from the communication device and transmitting the received print data to the print job generation unit 402. Further, the IPP service 414 has a function of accepting a print preset registration request from the IPP-compliant print client and registering a print preset in the setting storage unit 403 (details regarding the print preset will be described later).

The remote UI service 415 is a Web service that provides a remote user interface function for performing device setting and management of the MFP101 via an external Web browser. By using the remote UI service 415 from the Web browser or the like of the communication apparatus 102c, a user such as an administrator can check or change various device settings of the MFP101 on a display of a PC or the like. In the present embodiment, it is assumed that at least the change of the setting related to the IPP and the change of the setting related to the print preset (IPP preset) can be performed by accessing the remote UI service 415 from the Web browser.

The UI control unit 401 controls a screen displayed on the operation unit 116. For example, the UI control unit 401 acquires information about the status of a print job being processed from the job control unit 408, and displays the processing status of the print job on the operation unit 116. The UI control unit 401 can also display a screen for registering and managing print presets on the operation unit 116.

The print job generation unit 402 registers a new job in the job control unit 408 based on print data received via the IPP service 414, and issues a request for starting print processing. Further, the print job generation unit 402 transfers the received print data to the data reception control unit 406.

When the print job generation unit 402 generates a print job, the attribute of the print job is stored in the job attribute storage unit 409.

The user information storage unit 404 stores information related to the user. The information on the user includes authentication information (a credential such as a user ID or a password) for authenticating the user, and function information for restricting functions permitted to be used on the MFP101 for each user.

The print preset storage unit 405 provides functions for managing, updating, referring to, and storing print presets stored in the MFP 101. The IPP service 414 and the remote UI service 415 may refer to or update the print presets stored in the print preset storage unit 405, and may register new print presets.

The data reception control unit 406 is a buffer of the print data received by the print job generation unit 402, and temporarily stores the received data in the storage device 114 for each print job. When the execution preparation of the specific print job is completed, the job control unit 408 instructs the PDL analysis unit 407 to perform PDL analysis processing for the specific print job. The PDL analysis unit 407 requests the data reception control unit 406 to provide print data corresponding to a specific print job. The data reception control unit 406 transfers print data corresponding to a specific print job to the PDL analysis unit 407.

The PDL analysis unit 407 generates intermediate data from attribute information (relating to settings such as the number of copies, Nup, color mode, and/or post-processing) stored in the job attribute storage unit 409 in relation to print data corresponding to a specific print job. The generated intermediate data is transferred to the RIP control unit 412. The RIP control unit 412 performs conversion of intermediate data into a raster image in cooperation with the RIP provided in the image processing unit 124. The print control unit 410 acquires the raster image generated by the RIP control unit 412, and performs CMYK color separation on the acquired raster image. The print control unit 410 transfers the resulting color-separated print image to the engine control unit 413. The engine control unit 413 operates in cooperation with the printing unit 120 and the sheet processing unit 122, including forming an image on a sheet based on print images of each CMYK and/or performing post-processing such as stapling and the like on the sheet after the image has been formed.

< printing Preset >

Next, the print presetting is explained. In order to provide improved user convenience in a print client based on IPP, print presets are being discussed in PWG (print workgroup). In print presets (IPP presets) of the specifications being developed by the PWG, names are given to sets of print setting items and print setting values. Using the print presets makes it possible to collectively reflect the values of various setting items (also referred to as setting contents) such as double-sided printing, color setting, and/or bookbinding setting in the print settings, and thus it is possible to provide high convenience to the user.

In the present embodiment, the print preset is stored in advance in a storage area of the image forming apparatus such as the print preset storage unit 405, and is supplied to the print client operating in cooperation with the image forming apparatus. The print client conforming to the IPP can acquire a print preset from the MFP101 and use it for the print setting on the client side.

The print presets suitable for use by the user may differ among users according to the user's preference or the work in which the user participates. For example, a user who frequently prints a distribution for a presentation may want to use print presets such as "a 4, 2 in 1, double-sided, and stapling at two positions of the long side of a sheet". On the other hand, for example, a user who frequently prints a drawing may want to use a print preset such as "a 3, monochrome, single-sided, no post-processing", or the like.

In order to provide increased convenience to users, if print presets that each user wants to use are stored only in the image forming apparatus, the total size of print preset data stored in the image forming apparatus may be enormous. In this case, even if the print preset is provided to the print client, it may be difficult for the user to find a desired print preset from among a large number of print presets.

By setting the upper limit of the number of print presets that can be registered in the image forming apparatus, the above-described operational difficulty can be avoided. However, in this case, there may arise a problem that a reduction in the number of generated registerable print presets may make it difficult to cover all the print presets desired by the user.

In view of at least one of the above-described problems, the present embodiment provides a mechanism in which correspondence relationship information indicating a correspondence relationship between a user and a print preset is stored, and the print preset used by the user is correctly notified to a communication device using a print client. In addition, the present embodiment provides a mechanism that allows print presets to be appropriately registered based on an operation of an authenticated user.

The following describes the mechanism of notification, utilization, and registration of print presets according to the present embodiment. Fig. 5 and 6 are sequence diagrams showing examples of communication between the communication device 102 and the MFP101, respectively.

Fig. 5 is a diagram showing an example of a sequence in which, by way of example, user authentication is performed with a print client, and print presets customized for each user are acquired and used. On the other hand, fig. 6 is a sequence diagram showing a case where the common print preset is acquired and used without performing user authentication with the print client.

< registration of print Preset by Administrator >

First, registration management of common print presets is explained. The administrator of the MFP101 can access a print preset management screen provided by the remote UI service via a Web browser provided on the communication device 102 c. The administrator performs a setting operation (500) related to print presetting via a management screen displayed on the Web browser. The communication device 102c transmits a request to update or register the print preset based on the setting operation performed in 500 (501).

Upon receiving a request to update or register a print preset, the remote UI service 415 of the MFP101 updates the print preset managed by the print preset storage unit 405 or newly registers the print preset in the storage unit 405 (502).

Next, management of print presets using the remote UI service 415 is explained with reference to fig. 10. Fig. 10 is a diagram illustrating an example of a screen displayed on the operation unit 136 of the communication device 102 based on a Web page provided by the remote UI service 415. Fig. 10A to 10C show examples of the setting screen after login authentication of a user having an administrative authority is performed via a login screen (not shown). The user having the administrator authority is allowed to make various device settings via a screen provided by the remote UI service 415. Fig. 10A and 10B illustrate setting screens related to IPP printing in the job setting of the MFP 101. In the present embodiment, the screen is configured such that the setting screen for IPP printing can be transitioned to the print preset registration screen.

Fig. 10A is a setting screen for a case where the device settings of the MFP101 are set so that IPP printing is not used. The display item 1002 is a key for making a transition to a print preset registration screen. In the case where the setting is made such that IPP printing is not used, there is no need to register a print preset to be used in IPP, and hence the item 1002 is ashed. In addition, input in input fields such as a printer name field and a description field is also configured to be disabled.

It should be noted that the form of the Web page displayed in the case of IPP printing is not limited to the above example. For example, the provided Web page may not include a display item corresponding to 1002, a label of "manage preset", a description thereof.

The user is allowed to change the setting of whether to perform IPP printing by selecting the check box of the display item 1001. Upon receiving the HTTP request generated by the change instruction issued by the user, the remote UI service 415 returns a Web page corresponding to the screen illustrated in fig. 10B to the communication device 102 c. Further, the remote UI service 415 changes the device setting of the MFP 101. More specifically, the setting of printing without IPP (IPP printing is not permitted) is changed to the setting of printing with IPP.

The Web browser of the communication device 102c draws the screen illustrated in fig. 10B based on the Web page received as a response to the HTTP request. In a case where the setting is changed to cause the MFP101 to print using IPP as a result of the above processing, a display item for registering a print preset regarding IPP is enabled. The effect of this processing is to further emphasize that the print preset is allowed to be set.

In the present embodiment, the case where the screen is transitioned from fig. 10A to fig. 10B in cooperation with the remote UI service 415 is described above. This is by way of example and not limitation. For example, a script may be executed on a Web browser of the communication device 102 to dynamically switch between displaying the display item 1002 and displaying the display item 1003. A display item 1003 shown in fig. 10B is a key for shifting to a print preset registration screen. As shown in fig. 10B, the display item 1003 is displayed in a normal state (not grayed out). Upon receiving the HTTP request generated as a result of the user selecting the display item 1003, the remote UI service 415 returns a Web page corresponding to the screen illustrated in fig. 10C to the communication apparatus 102C. Fig. 10C includes an area 1004 indicating the name of the print preset, a button 1005 for editing the print preset, and a button 1006 for deleting the print preset. The administrator is allowed to register print presets for common use on the MFP101 via the management screen shown in fig. 10C. For example, in order to reduce the printing cost, a printing preset specifying, for example, "2 in 1, duplex, monochrome" may be registered in advance, and the user may be prompted to use the printing preset. Although not explicitly shown in fig. 10C, the administrator can also register, edit, and delete the print presets registered by the authenticated user via the management screen.

The print preset registered in the registration process described above with reference to fig. 10 is stored in the print preset storage unit 405. Fig. 7A to 7C are diagrams for explaining the relationship between information stored in the print preset storage unit 405 and a user. The setting item 701 is a setting item included in the print preset. The attribute values 702 are values of respective items defined in respective print presets.

In the present embodiment, an item 704 and an item 705 for storing identification information for determining a print preset used by a user are provided in addition to a name 703 and a setting item 706 constituting the print preset. An item 704 is a field for describing information for identifying whether the print preset is common (i.e., whether the print preset is a standard preset or a personal preset). In this column, "standard" or "user" is described. Item 705 is a column for identifying the owner of the print preset. That is, in this column, the owner of the print preset is described. The standard preset allows any user reference, thus storing "Guest" in item 705. On the other hand, identification information for identifying the user is stored in the individual preset. Using these items 704 and 705, the print preset to be sent to the print client can be narrowed down.

In the present embodiment, the user identifier (user ID) is registered in association with the personal preset, so that the owner of the print preset can be identified, but this is by way of example and not limitation. For example, in the case where a plurality of users are managed in association with a group, print presets may be stored for each group. A modification is explained below with reference to fig. 7B and 7C. Fig. 7C shows an example of items of the user DB used in the case where user authentication is performed on the MFP 101. In this example, the user having the user ID "Suzuki" belongs to the "Accounting" group, and the users having the user IDs "Tanaka" and "Sato" belong to the "Sales" group. The user DB may be stored in the MFP101 or in an authentication server (not shown). In the case where the user DB is stored in the authentication server, the authentication server performs user authentication in response to receiving a user authentication request.

In the present modification, as shown in fig. 7B, the individual preset is registered in association with the group identifier 707. By associating the user with the print presets used by the user in this manner, the print presets can be shared by the groups despite the reduced granularity of customization as compared to the case where individual presets are used. Users belonging to the same group often relate to the same service. For example, users belonging to the "Sales" group are likely to frequently print distribution material to be presented to customers. In this case, the print presets may be shared in the group. Whether the print preset is associated with a group or a user can be set in advance as the device setting of the MFP 101. These device settings are stored in the storage device 114 or the like. In this case, the MFP101 may change the settings based on the usage environment regarding whether the personal preset is registered for each user or the registered group preset for each group according to the settings stored in the storage device.

The print preset storage unit 405 stores information in a format such that reference to print presets is allowed based on information identifying a user. The data structure used herein may be a relational database or NoSQL.

< acquisition of printing Preset >

Referring again to fig. 5, the cooperation with the print client is explained. The user of the communication device 102 performs a user operation to start the print client via the operation unit 136 of the communication device 102 (503). When the communication apparatus 102 accepts a user operation to start a print client, the communication apparatus 102 broadcasts a search request for searching for a printer or an image forming apparatus located nearby (504). For example, the search request may be issued using mDNS (multicast domain name service) or the like. This operation is not performed in the case where the printer is not registered. In the case where a usable printer is registered in advance, the screen transitions to a print setting screen in 519.

Upon receiving the search request, the MFP101 transmits a response to the search (505). When the communication device 102 receives a response from a printer such as the MFP101, the communication device 102 transmits a request for acquiring printer attribute information including information indicating the capability of the user and/or print presets for public use (506). In the case where a plurality of printers are found, or in the case where the printers are to be confirmed, a selection screen (not shown) may be displayed so that a request can be sent to the printer selected via the selection screen.

Here, it is assumed that the communication device 102 transmits a Get request to the MFP101 using a Get-Printer-Attributes command defined in IPP. For simplicity of explanation, printer attribute information including information indicating printer capability and/or print presets for common use will be referred to as attribute information (for common use) or common attribute information. Note that the MFP101 may issue common attribute information in which the version of the function for use by the guest user is limited.

When the MFP101 receives a Get-Printer-Attributes request for acquiring Printer attribute information, the MFP101 transmits the attribute information of the MFP101 as a response to the request (507). The attribute information acquired based on the acquisition request is explained below with reference to fig. 8. Fig. 8A shows an example of information 801 transmitted as an acquisition request and an example of attribute information 802 obtained as a response to the acquisition request.

The attribute information 802 includes capability information indicating the capability of the MFP101 in terms of printing and post-processing, and also includes preset information 804 serving as standard preset information. The MFP101 generates capability information based on information indicating the capability of the MFP101 (e.g., supported color modes, paper types, post-processing, and the like). Further, the capability information includes information on whether to support a function restricted or customized for each user. In the case where the device setting of the MFP101 specifies the enablement of the user authentication function, the MFP101 describes, in the capability information, operations that it supports limiting or customizing functions for respective users. On the other hand, in the case where it is set that the user authentication function is not used, the capability information does not include a description indicating that the operation is supported. For example, "Get-User-Printer-Attributes" is used as an operation for restricting or customizing functions for each User.

Based on the print presets stored in the print preset storage unit 405, preset information 804 including a list of print presets for common use is generated. The MFP101 transmits attribute information (for public use) 802 including the generated capability information and preset information to the communication device 102.

Referring again to fig. 5, in response to receiving the attribute information (for public use), the communication device 102 updates the printer attribute information (508). As a result of this processing, the print client of the communication device 102 can display a print setting screen suitable for the printer capability and use the received print preset for the guest.

In the case where the returned response indicates that "Get-User-Printer-Attributes" is supported, control in the following sequence is performed as described below. Note that in the case where the returned response indicates that "Get-User-Printer-Attributes" is not supported, the communication apparatus 102 skips the processing in 509 to 518 and enters the print setting sequence (in 519 and subsequent steps).

Subsequently, the communication device 102 transmits a request for acquiring printer attribute information including information on the restriction and customization of the functions of each user to the MFP101 (509). Note that it is assumed here that the acquisition request to acquire the Printer attribute information including the function restriction information and the customization information of each User is transmitted to the MFP101 using the Get-User-Printer-Attributes command of which specification is being developed by the PWG. Hereinafter, for the sake of simplifying the description, printer attribute information including function restriction information and customization information of each user is referred to as attribute information (for personal users) or personal attribute information.

When the MFP101 receives an acquisition request for attribute information (for personal use), the MFP101 transmits a user authentication request by HTTP. For example, the authentication request may be issued using known BASIC authentication or Digest authentication. In this authentication process, data flowing through the communication path may be encrypted by TLS (using IPPS). Note that, in the case where an authentication session is established between the MFP101 and the communication apparatus, the processes of 510 to 515 are skipped. The MFP101 temporarily stores the user ID as a session variable associated with a session ID for managing a session in the RAM113 or the storage device 114. This makes it possible to identify the user who sent the request including the session ID. Further, based on the session ID, it may be determined that the function restriction information or the customization information to be transmitted is information defined for a specific user. That is, in the present embodiment, the session ID included in the request received from the communication device 102 is used as identification information for identifying the user.

When the communication device 102 receives the authentication request, the display communication device 102 displays an authentication screen (511). This authentication screen is explained by way of example with reference to the screen shown in fig. 11. Fig. 11A to 11D show examples of screens provided by a print client of a PC serving as the communication device 102 c. Fig. 11A shows an example of the authentication screen displayed at 511. The dialog 1101 is used to input user information.

In the case where the user wants to use a function customized for print preset for personal use or restricted for personal use, the user inputs authentication information (user name and password) in the input fields 1102 and 1103 and presses the confirmation button 1104 (512). In a case where the user wants to use the MFP101 with guest authority, the user presses the guest key 1105 or a cancel key.

When accepting the input of the authentication information and detecting the pressing of the confirmation button, the communication apparatus 102 transmits the authentication information to the MFP101 (513). When the MFP101 receives the authentication information, the MFP101 executes authentication processing based on the received authentication information (514). Hereinafter, a case where the user having the user ID "Suzuki" has been successfully authenticated is explained by way of example.

When the authentication is successfully passed, the MFP101 transmits information including information indicating that the authentication has been successfully passed, the session ID, and the user ID to the communication device 102 (515). Thereafter, the session ID can be used to identify the user of the communication device as long as the session is effectively managed. The communication terminal 102 stores the received user ID and session ID in the storage device 134 or the like.

Subsequently, the communication device 102 transmits an acquisition request for acquiring printer attribute information (for personal use) including the identification information to the MFP101 (516).

In the present embodiment, it is assumed that user authentication is performed using Digest authentication or BASIC authentication, but this is by way of example and not limitation. The print client may be given an access token using Oauth or the like. In this case, an acquisition request for acquiring printer attribute information (for personal use) including the access token is transmitted to the MFP 101.

When the MFP101 receives an acquisition request for printer attribute information (for personal use) including identification information (session ID), the MFP101 identifies a user who transmitted the acquisition request based on the identification information. Further, based on the function restriction information of the user and the personal print preset permitted to be used by the user, the MFP101 generates attribute information (for personal use) including the preset information. Finally, the generated attribute information (for personal use) is sent to the communication device 102 as a response to the request sent at 516 (517).

Attribute information acquired based on an acquisition request for attribute information (for personal use) is explained below with reference to fig. 8B. Fig. 8B shows an example of information 805 transmitted as an acquisition request for attribute information (for a personal user) and an example of attribute information 806 obtained as a response to the acquisition request. Although not shown in 805, the extension header of the acquisition request (HTTP request) includes a session ID as identification information. Information 808 is preset information indicating a print preset associated with "Suzuki", which is a user authenticated via the processes of 512 to 515. More specifically, "My preset-1", "My preset-2" and "My preset-3" described above with reference to fig. 7A and 7B are added. In the present embodiment, the attribute information 806 not including the common preset information is transmitted at this timing, but this is by way of example and not limitation. In addition to the individual preset information, common preset information may be added to the attribute information 806, and the resulting attribute information 806 may be transmitted.

When the communication device 102 receives the attribute information (for personal use), the communication device 102 updates the default setting of the print client. In addition, the communication device 102 updates the available print presets (518).

Through the above-described flow sequence, the attribute information of each user and the print preset customized for each user are reflected in the settings of the print client.

Upon completion of the initial setting sequence, the communication device 102 displays a print setting screen. Fig. 11B illustrates an example of a print setting screen after the initial setting is completed.

< registration of print Preset Via print client >

The list 1106 is a display item for making settings related to print presets. By using the options displayed in the list 1106, the user is allowed to perform operations such as newly registering or updating a print preset for the MFP101, reacquiring a print preset, and newly registering a print preset in the print client.

Fig. 11C shows an example of a screen displayed on the operation unit 136 in response to selection of the list 1106 in fig. 11B.

A list of print preset related functions is displayed in the pull-down list displayed in the area 1107. The following describes functions related to each print preset.

Option 1108 is an option selected as a default print preset at the time of IPP print setting in communication device 102 c. An option 1109 is an option for resetting the print preset used last time.

In addition, the present embodiment provides a mechanism for selecting frequently used print presets in short steps without traversing many hierarchies. Option 1110 is a shortcut key for easily setting frequently used print presets. Note that the present embodiment illustrates a case where there is only one option, but this is by way of example and not limitation. For example, a plurality of frequently used print presets (e.g., three print presets) may be displayed. In this case, the preset names are displayed as tabs of the corresponding options, so that the options can be distinguished by the preset names.

The option 1111 is an option for generating a print preset based on the current print setting and registering it in the print client. Unlike the option 1111, the option 1112 is an option for registering the current print setting in the communication destination printer (e.g., the MFP 101). When selection of the option 1111 or 1112 is detected, the screen transitions to the screen shown in fig. 11D in which input of a new preset name is allowed. An input field 1117 for inputting a preset name is displayed on the screen of fig. 11D, thereby allowing the user to set the preset name. When the confirmation key is pressed, print preset registration processing (details will be described later) is performed.

Option 1113 is an option for displaying all currently available print presets. Here, all the print presets include a print preset stored locally (in the print client) and a print preset acquired from a printer such as the MFP 101. Option 1114 is an option for newly creating a print preset. In this case, for example, the print preset may be newly created via a setting wizard (not shown).

Option 1115 is an option for reacquiring the common preset. When option 1115 is selected, the communication device 102 performs processing similar to the processing of 506-508 described above with reference to FIG. 5 to update the print preset. The processing based on option 1115 differs from the processing of 506-508 in that: only the acquired print preset is updated and the capability information of the printer is not updated.

The option 1116 is an option for reacquiring the personal preset stored in the MFP 101. When option 1116 is selected, the communication device 102 performs the processing of 509-518 described above with reference to FIG. 5 to update the print presets.

Referring again to fig. 5, the print preset registration process is explained. The user performs a print preset registration operation via a screen or the like shown in fig. 11B (520). When the communication device 102 detects that a user operation for registering a print preset in the MFP101 is performed, the communication device 102 transmits a registration request for registering the print preset including identification information (session ID) (521). Here, it is assumed that the print preset registration is requested using a Set-User-Printer-Attributes command being developed by the PWG. It is noted that the above description is by way of example and not of limitation. Commands of the same purpose or similar purpose that are being discussed by the workgroup or the like may be used.

When the MFP101 receives the print preset registration request, the MFP101 executes registration processing (522). Here, if the print presets having the same name are stored in association with the user specified based on the identification information, control is performed to update the print presets. In a case where there is no print preset having the same name, a new print preset is registered in association with the user. In the case where the print preset is associated with a group as shown in fig. 7B and 7C, the print preset is registered in association with a group ID to which the user belongs. If the number of individual presets allowed to be created reaches a predetermined upper limit (for example, 5), an error notification may be issued without registering the print presets. Note that the processing performed when the upper limit is reached is not limited to the above-described example. For example, the user may be notified of the names of the registered print presets, and may select unnecessary print presets. A new print preset may be registered in place of the selected unnecessary print preset.

When the registration processing in 522 is completed, the MFP101 transmits a completion notification (523). Through the above-described processing, registration of print presets from the IPP-compliant print client can be accepted.

< use of print Preset >

Next, use of the print presets is explained. The user performs an operation (524) of selecting a print preset from a pull-down list or a print preset list screen (not shown) shown in fig. 11C. When the communication device 102 detects the selection operation, the communication device 102 updates the print setting based on a combination of the print setting item and the print setting value stored in association with the selected print preset. The print setting is reflected in the print setting screen displayed on the operation unit 136 (525). Here, by way of example, assume that "My preset-1" described above with reference to FIG. 7A or 7B is selected.

The user performs a print start operation via the screen shown in fig. 11 (526). When the communication device 102 detects the print start operation, the communication device 102 generates print data based on the current settings and transmits the generated print data to the MFP101 (527). Fig. 9 is a diagram for explaining attribute information of print data generated in response to a print start operation performed after "My preset-1" is selected. As shown in 901, print attributes such as "color, double-sided, stapling at one position at the upper left", and the like based on the print setting updated by "My preset-1" are reflected in the generated print data. In the case where the user makes other print settings after selecting the print preset, the resulting settings are reflected in the generated print data. As shown in fig. 9, the name of the user who requested printing is added to the attribute information of the print data. The name is added based on the user ID stored when authentication was successfully passed in 515. Information indicating the user ID added to the attribute information of the print data is used as necessary (for example, in the case where the MFP101 manages the number of print sheets for each user, or in the case where it is verified whether the print data satisfies the function restriction of each user).

Subsequently, the MFP101 executes printing based on the received print data (528). When the execution is completed, the MFP101 notifies the communication device 102 of the execution result of the job (529).

The sequence diagram shown in fig. 6 is for explaining processing performed in a case where the user performs an operation for requesting guest use via the screen shown in fig. 11A. The processes 603 to 611 are the same as the processes 503 to 511 shown in FIG. 5, and further description thereof will be omitted. When the user wants to use the MFP101 with guest authority, the user performs an operation of selecting the guest key 1105 shown in fig. 11A. When the communication device 102 detects an operation of selecting the guest key 1105, the communication device 102 notifies the MFP101 that the use with guest authority is selected (613). When the notification is completed, the communication device 102 shifts the screen displayed on the operation unit 136 to the print setting screen (614). Thus, in case a use with guest privileges is selected, the acquisition of attribute information (for personal use) may be skipped. The following processes 624 to 629 are the same as the processes 524 to 529 shown in fig. 5, and therefore, further description thereof is omitted.

The sequences in fig. 5 and 6 are explained above by way of example with reference to a screen (fig. 11) provided by a print client of a PC serving as the communication device 102 c. However, in the case where the communication device 102 is a smartphone or a tablet terminal, the structure of the screen of the print client of the communication device 102 may be appropriately modified in consideration of the screen size and the touch operation. Even for an IPP-compliant print client, the screen structure differs depending on the type of client. A modification of the screen display on the print client of the smartphone or tablet terminal is described below with reference to fig. 12. Note that description of display items that produce the same effects as the functions described above with reference to fig. 11 is omitted.

< display screens on smartphone and tablet terminal >

The modified screen is described below with reference to the processing in the sequence diagram shown in fig. 5 as appropriate. Fig. 12A shows a menu screen provided by the OS of the communication apparatus. The menu screen is a function provided by the OS. The menu screen can be called from various applications (e.g., memo application) and used for sending a message or an email or the like and for printing.

When the communication device 102 detects an operation of pressing the print key 1201, the communication device 102 transitions to a print setting screen illustrated in fig. 12B. The print client generates a preview image based on data to be printed received from various applications, and displays the preview image as shown in fig. 12B.

Fig. 12B shows, by way of example, a case where a printer is not selected. When the communication device 102 detects that the option 1202 is selected, the communication device 102 transitions to a screen for executing the printer search processing, and starts 504 the indicated printer search request. Fig. 12C shows an example of a screen displaying the search result. Note that in the example of fig. 12C, it is assumed by way of example that a search response is returned from the MFP101, and the IPP printer name "PrinterXXX (printer XXX)" of the MFP101 included in the search response is displayed as a search result.

When the communication device 102 detects that the option 1203 in fig. 12C is selected, the communication device 102 performs the processing in 506 in fig. 5 and subsequent processing. The authentication screen shown in fig. 12D is the same as the authentication screen shown in fig. 11B, and therefore further description thereof is omitted. Fig. 12E shows an example of the print setting screen displayed in the processing 519.

Option 1206 is an option for selecting a print preset. The area 1207 is used to display information indicating a selection status preset for printing. Fig. 12E shows an example in which the print presets are not set.

When the communication device 102 detects that the option 1206 is selected, the screen related to the print preset in fig. 12F is opened. In the case where the communication apparatus is a smartphone, a tablet device, or the like, the display area is limited, and therefore, the pull-down list is inconvenient. To cope with the above situation, when any one item is selected, a single setting screen for only the selected item is opened, thereby providing convenience to the user. The processing performed by the user via the screen in fig. 12F is the same as the processing performed in 1107 in fig. 11C, and therefore further description thereof is omitted.

Note that in the present embodiment, when the option 1206 is selected, the screen transitions to the screen illustrated in fig. 12C. However, this is by way of example and not of limitation. When option 1206 is selected, the communication device 102 may transition to a screen displaying a list of print presets. These print preset lists are appropriately rearranged according to the frequency of use and the like, and are displayed so that the user is allowed to select in a highly convenient manner. By this processing, even on a tablet terminal or a smartphone or the like having a small display area, it is possible to call up the print preset more easily and with a smaller number of operation steps. In this case, a screen for registering or reacquiring the print preset may be displayed so that the screen can be reached by transition from a screen (for example, a setting menu screen) in another layer.

Fig. 12G illustrates an example of a print setting screen after the print preset is set. Here, by way of example, assume that "My preset-2" is selected. In the region 1213, information indicating that "My preset-2" is selected is displayed. After the user selects the print preset, if the user further modifies the settings, the user may be notified of the result. In this case, for example, a message such as "My preset-2 (modified)" or the like may be displayed.

Next, a control method for realizing notification, utilization, and registration of print presets according to the present embodiment is described below with reference to flowcharts shown in fig. 13 to 18.

< control of communication apparatus 102 >

First, the operation of the communication device 102 is explained. Fig. 13 to 15 are flowcharts showing control of the communication apparatus 102. The operations (steps) shown in the flowcharts of fig. 13 to 15 are realized by the CPU131 by reading a program for realizing each control module stored in the ROM 132 or the storage device 134 into the RAM133 and executing the program. Note that each function shown in the flowchart provided by the OS 310 is implemented in cooperation with a program module for implementing a print client.

Fig. 13 is a flowchart showing a process executed in response to accepting an operation to start the print client by the user. In S1301, the CPU131 determines whether or not the startup processing is to be executed. The printer is allowed to be registered in advance in a print client used on a PC or the like. In the case where the printer has been registered in advance, it is determined that the acquisition process is not executed at the time of startup. If it is determined that the startup processing is to be executed, the process proceeds to S1302. However, in the case where it is determined that the startup processing is not to be executed, the process proceeds to S1316.

In S1302, the CPU131 transmits a printer search request via the communication unit I/F143. In S1303, the CPU131 transmits an attribute information (for public use) acquisition request to the printer (e.g., MFP101) found as a result of the printer search request. Here, it is assumed that the CPU131 sends the acquisition request to the MFP101 using the Get-Printer-Attributes command defined in the IPP. Note that as described above with reference to fig. 11 and 12, in the case where a plurality of printers are found, the request in S1302 may be transmitted in response to a printer being selected by a user operation.

In S1304, the CPU131 updates or newly saves the printer attribute information and the print presets based on the attribute information obtained as a response to the request transmitted in S1303. Here, in a case where there is a saved print preset in which the attribute value of the name and the attribute value of the owner are the same as those of the received print preset, the CPU131 updates the saved print preset with a new print preset. On the other hand, in the case where the attribute value of the name or the attribute value of the owner does not coincide, the print preset is newly saved.

In S1305, the CPU131 determines whether the printer supports function restriction or customization for each user based on the attribute information received in S1304. In the case where function restriction or customization for each user is supported, the process proceeds to S1306. However, in the case where the function restriction or customization for each user is not supported, the process proceeds to S1316.

In S1306, the CPU131 determines whether a session with the other party is maintained. In the case of maintaining the session, the authentication processing in S1307 to S1312 is skipped, and the process proceeds to S1314. On the other hand, when the session with the other party is not maintained, the CPU131 advances the process to S1307.

In S1307, the CPU131 sends a request for acquiring printer attribute information (for personal use) to the communicating communication apparatus. Here, it is assumed that the CPU131 sends the acquisition request to the MFP101 using a command such as Get-User-Printer-Attributes being developed by the PWG. At the timing of executing S1306, the session with the communication partner has not been established yet, and therefore an acquisition request not including identification information (session ID) is transmitted. In response to this request, the printer such as the MFP101 transmits a user authentication request described in 510 of fig. 5.

In S1308, in response to the user authentication request received as a response to the request in S1307, the CPU131 displays an authentication screen for inputting authentication information and accepts an input operation of the authentication information. For the authentication screen, for example, a user information input screen shown in fig. 11A or 12D is used.

In S1309, the CPU131 determines the type of the instruction relating to authentication. In the case where the cancel key is selected, the CPU131 advances the process to S1316. In the case where the guest key is selected, the process proceeds to S1310. In the case where the confirm key is selected, the CPU131 advances the process to S1311.

In S1310, the CPU131 notifies the printer of the guest usage, and advances the process to S1316.

In S1311, the CPU131 transmits the authentication information accepted in S1308 to the printer (e.g., MFP 101). Upon receiving the authentication information, the MFP101 performs authentication described in 514 of fig. 5, and notifies the communication apparatus 102 of the result.

In S1312, the CPU131 determines whether the authentication result based on the authentication information transmitted in S1311 is successful. In the case where the authentication is successful, the process proceeds to S1314. However, in the case where the authentication is unsuccessful (authentication fails), the process returns to S1308 and waits for the input operation of the authentication information to be performed again. If the authentication is successful, a session establishment process is performed. As a result of the session establishment processing, the communication device 102 receives a session ID from the printer (MFP101) that is communicating.

In S1314, the CPU131 sends a request for acquiring printer attribute information (for personal use) including identification information (session ID) to the communicating printer. At the timing of S1314, the session with the communication partner has already been established, and therefore an acquisition request including the identification information (session ID) described in the HTTP extension header is transmitted. Upon receiving an acquisition request for attribute information (for personal use) including identification information (session ID), the printer (MFP101) that is communicating responds to the acquisition request by returning the attribute information (for personal use) of the printer described above in 517 of fig. 5.

In S1315, the CPU131 updates the printer attribute information and the print presets based on the attribute information (for personal use) obtained as a response to the request in S1314. The CPU131 updates the saved print preset with a new print preset according to the print preset in which the attribute value of the name and the attribute value of the owner saved in the print client are the same as the attribute value of the name and the attribute value of the owner in the received print preset. On the other hand, in the case where the attribute value of the name or the attribute value of the owner does not coincide, the print preset is newly saved.

Subsequently, in S1316, the CPU131 determines whether an operation related to print setting is accepted. In the case where an operation related to print setting is accepted, the process advances to S1317. However, in a case where an operation related to print setting is not accepted, the process advances to S1318. Note that the operation related to the print setting is, for example, a print preset selection operation, a print setting change operation (for example, changing from color to monochrome), or the like.

In S1317, the CPU131 executes print setting processing. The print setting processing is described in detail below with reference to a flowchart shown in fig. 14. In S1401, the CPU131 determines whether a print preset selection operation is accepted. In the case where the print preset selection operation is accepted, the process advances to step S1402. However, in a case where the print preset selection operation is not accepted, the process advances to step S1404.

In S1402, the CPU131 updates the print settings based on the selected print preset. For example, in the case where the selected print preset is "My preset-1", settings such as "color, duplex printing, binding of a product at one position in the upper left corner", and the like are reflected in the print settings. In S1403, the CPU131 updates the display screen based on the current print setting. Upon completion of the update of the display screen, the process advances to S1301. In the case where the user has set the print setting before selecting the print preset, the user may be notified that the currently set print setting is to be discarded. In this case, the CPU131 inquires of the user whether to select confirmation or cancel via the operation unit 136. In the case where it is detected that the confirmation is selected, the change of the print setting is made in S1402. In the case of selection cancellation, the process proceeds to S1301 without changing the setting based on the print preset.

In S1404, the CPU131 determines whether a user operation for changing print settings is accepted. In the case where a user operation to change the print setting is accepted, the process advances to step S1405. However, in a case where a user operation to change the print setting is not accepted, the process advances to step S1301.

In S1404, the CPU131 reflects the change of the print setting based on the user operation, and updates the display of the operation screen according to the change. When the change and update processing is completed, the processing proceeds to S1301.

Referring to fig. 13 again, in S1318, the CPU131 determines whether a print preset editing operation is accepted. In the case where the print preset editing operation is accepted, the process advances to S1319. However, in a case where the print preset editing operation is not accepted, the process advances to S1320.

In S1319, the CPU131 performs print preset editing processing based on the print preset editing operation. Here, the print preset editing operation refers to the print preset downloading operation or the print preset registering operation described above with reference to fig. 10. The print preset editing operation is described in detail below with reference to a flowchart shown in fig. 15.

In S1501, the CPU131 determines whether a user operation for downloading a personal preset is accepted. In the case where a User operation for downloading the personal preset is accepted, the CPU131 advances the process to S1306 to acquire and reflect the print Attributes of the Printer (for personal use) using a command such as Get-User-Printer-Attributes. On the other hand, in a case where a user operation for downloading the individual preset is not accepted, the CPU131 advances the process to S1502.

In S1502, the CPU131 determines whether a user operation for downloading a common preset is accepted. In the case where a user operation for downloading the common preset is accepted, the process advances to step S1503. However, in a case where a user operation for downloading the common preset is not accepted, the process advances to step S1507.

In step S1503, the CPU131 sends a request for acquiring printer attribute information (for public use) to the printer (e.g., MFP101) being selected. Upon receiving a request to acquire printer attribute information (for public use), a printer such as the MFP101 transmits the printer attribute information (for public use) as a response.

In S1504, the CPU131 determines whether the attribute information stored in association with the printer being selected is attribute information customized for the user. In the case where the attribute information is customized for the user, the process proceeds to S1505. However, in a case where the attribute information is not customized for the user, the process proceeds to S1506.

In S1505, the CPU131 extracts a print preset that can be used with the print capability having the limited function for personal use, based on the print preset included in the received attribute information (for public use). Thereafter, the extracted print preset is registered or updated as a print preset used by the print client. This processing is exceptional processing for suppressing setting of a print preset including an attribute that is not permitted to be used with an authority given to the user. When the print preset registration or update process is completed, the process advances to S1301.

In S1506, the CPU131 registers or updates the printer attribute information and the print preset based on the received attribute information. When the registration or update is completed, the CPU131 returns the process to S1301.

In S1507, the CPU131 determines whether a user operation for registering a print preset is accepted. In the case where a user operation for registering a print preset in the printer is accepted, the process advances to step S1508. However, in a case where a user operation for registering a print preset in the printer is not accepted, the process advances to step S1509.

In S1508, the CPU131 generates print preset data based on print settings made via the print setting screen, and transmits a registration request for registering the print preset to the selected printer. It is assumed that the request includes identification information (session ID). It is also assumed that the print preset registration is requested using the Set-User-Printer-Attributes command being developed by the PWG. It is noted that the above description is by way of example and not of limitation. Commands of the same purpose or similar purpose that are being discussed by the workgroup or the like may be used. When the update processing is completed, the processing proceeds to S1301.

In S1509, the CPU131 determines whether a user operation for registering a print preset in the client is accepted. In the case where a user operation for registering a print preset in the client is accepted, the process advances to step S1510. However, in a case where a user operation for registering a print preset in the client is not accepted, the process advances to step S1301.

In S1510, the CPU131 generates print preset data based on the print setting made via the print setting screen, and registers the print preset data in a print preset list managed by the print client. When the registration processing is completed, the CPU131 advances the processing to S1301.

Referring to fig. 13 again, in S1320, the CPU131 determines whether a print start instruction is accepted. When the print start instruction is received, the process proceeds to S1321. However, in a case where the print start instruction is not accepted, the process returns to S1301 and waits for another operation.

In S1321, the CPU131 generates print data based on the print setting and the print data to be printed. Note that it is assumed that print data to be printed is received from the print application when the print client starts up.

In S1322, the CPU131 transmits the print data generated in S1321 to the printer (e.g., MFP101) being selected. In S1323, the CPU131 performs processing for re-determining the print preset priority. This processing is used for display control of option 1110 shown in fig. 11 and display control on the selection screen for selecting a print preset from the print preset list. This makes it possible to display the print presets frequently used by the user in the region of high visibility.

< control of MFP101 >

Next, the operation of the MFP101 is explained. FIGS. 16 to 18 are flowcharts showing control of the MFP 101. The operations (steps) shown in the flowcharts of fig. 16 to 18 are realized by the CPU111 reading a program for realizing each control module stored in the ROM 112 or the storage device 114 into the RAM113 and executing the program. In the present embodiment, the print processing and the data transmission/reception processing and the like are realized in cooperation with hardware for realizing each I/F and each function. Note that in the case where it is desired to clearly indicate a software module in charge of actual processing in the following description, the name of such a software module for controlling the CPU to execute processing is explicitly indicated, and the processing will be described as being performed by the software module rather than the CPU.

The flowchart in fig. 16 shows processing executed when the power of the MFP101 is turned on and the MFP101 is started up in the normal mode.

In S1601, the CPU111 determines whether a request for printer attribute information (for public use) is received from an external device such as the communication device 102. In the case where a request for printer attribute information (for public use) is received, the process advances to step S1602. However, in a case where a request for printer attribute information (for public use) is not received, the process advances to step S1605.

In S1602, the CPU111 acquires a preset for use by the guest user. When the IPP service 414 receives a request via a Get-Printer-Attributes command or the like, the IPP service 414 accesses the print preset storage unit 405 to acquire a print preset in which "standard" is set in the category 704.

In S1603, the CPU111 acquires printer capability information. More specifically, the IPP service 414 acquires capability information of the print unit and the sheet processing unit described in the storage device 114 and the like. The capability information includes, for example, printing capability and post-processing capability. Note that the acquisition timing is not limited to the acquisition timing in the above example. For example, the capability information may be obtained when the IPP service 414 is started, and the IPP service 414 may maintain the capability information internally.

In S1604, the CPU111 creates printer attribute information (for public use) based on the information acquired in S1602 and S1603. Subsequently, in response to a request received from an external device (e.g., the communication device 102), the CPU111 transmits printer attribute information (for public use) to the external device. The IPP service 414 generates a response regarding the printer attribute information as shown at 802 in fig. 8A based on the acquired data. The generated response is transmitted to the external device via the Web server 416. When the transmission is completed, the CPU131 advances the process to S1601.

In S1605, the CPU111 determines whether a request for printer attribute information (for personal use) not including identification information is received. In the case where a request for attribute information (for personal use) of a printer that does not include identification information is received, the process proceeds to S1606. On the other hand, in a case where a request for attribute information (for personal use) of a printer that does not include identification information is not received, the process proceeds to S1611. Note that the request here is issued using a Get-User-Printer-Attributes command or the like. When Web server 416 receives the request, Web server 416 checks whether the request includes a valid session ID managed by Web server 416. In the case where such a session ID is not included, the Web server 416 determines that the request does not include identification information. In the case where the request includes a valid session ID managed by the Web server 416, the Web server determines that the identification information is included.

In S1606, the CPU111 determines whether the device setting specifies the use of the user authentication function. In the case where the device setting designates the use of the user authentication function, the process advances to step S1607. However, in a case where the device setting does not specify the use of the user authentication function, the process advances to step S1602. This processing is exceptional processing for considering a case where the MFP101 does not use the user authentication function.

In S1607, the CPU111 issues a user authentication request to the communication apparatus from which the attribute information (for personal use) acquisition request is received. In S1608, the CPU111 receives authentication information from the communication device. In S1609, the CPU111 authenticates the user based on the authentication information, and determines whether the authentication has successfully passed. In the case where the authentication server is located outside the apparatus, the MFP101 transmits authentication information to the authentication server and inquires whether authentication is passed. In the case where the authentication is successfully passed, the process proceeds to S1610. However, in the case where the authentication fails, the process returns to S1607, and the user authentication request is retransmitted.

In S1610, the CPU111 notifies the communication apparatus of the communication partner of the success of authentication. More specifically, the Web server 416 establishes a session with the communication device of the communication partner, and transmits a notification of authentication success and a session ID for managing the session. The Web server 416 stores the user ID included in the authentication information received from the communication partner as a session variable associated with the session ID. The session variable is accessible from IPP service 414. Thus, based on the session ID included in the received request, IPP service 414 may identify the user that sent the request.

In S1611, the CPU111 determines whether an acquisition request for printer attribute information (for personal use) including identification information is received. In the case where an acquisition request for printer attribute information (for personal use) including identification information is received, the process advances to step S1612. However, in a case where an acquisition request for printer attribute information (for personal use) including identification information is not received, the process advances to step S1615.

In S1612, the CPU111 extracts the preset used by the user corresponding to the identification information. More specifically, Web server 416 and IPP service 414 cooperate to identify a user ID from identification information (session ID). The IPP service 414 accesses the print preset storage unit 405 of the setting storage unit 403 to extract the print preset used by the user corresponding to the specified user ID. In the case where the print presets are managed on a user-by-user basis, the print presets used by the user are extracted based on the user ID. In the case where the print presets are managed group by group, the group to which the user belongs is identified from the user ID, and the print presets stored in association with the group are extracted.

In S1613, the CPU111 acquires the printer capability information based on the authority of the user corresponding to the identification information. More specifically, the IPP service 414 refers to the function restriction information of each user stored in the storage device 114 or the like, and acquires the function restriction information related to the user corresponding to the identification information.

In S1614, the CPU111 creates printer attribute information (for personal use) based on the acquired information, and transmits the resultant printer attribute information (for public use) as a response to the communication apparatus of the communication partner. More specifically, the IPP service 414 generates printer attribute information such as that shown at 806 in fig. 8B based on the acquired data as a response. The generated response is transmitted to the external device via the Web server 416. When the transmission is completed, the CPU131 advances the process to S1601.

In S1615, the CPU111 determines whether print data is received. In the case where the print data is received, the process advances to step S1616. However, in the case where the print data is not received, the process advances to step S1618.

In S1616, the CPU111 executes print processing and post-processing on a print sheet based on the received print data. These processes are realized by the cooperation of the modules 402, 406, 407, 408, 412, 413 and the respective I/F units and hardware units controlled by these modules. When the print processing and the post-processing are completed, the CPU111 advances the process to S1617.

In S1617, the CPU111 notifies the communication apparatus from which the print data was received of the end of printing, and advances the process to S1601.

On the other hand, in S1618, the CPU111 determines whether a request for a remote UI service is received. Upon receiving the request for the remote UI service, the Web server 416 advances the process to S1619. However, in a case where a request for a remote UI service is not received, the Web server 416 advances the process to S1620.

In S1619, the CPU111 executes processing related to the remote UI service. The specific processing is explained below with reference to fig. 17. Note that the processing illustrated in fig. 17 is mainly performed by the remote UI service 415 and the Web server 416.

In S1701, the CPU111 determines whether a request for an IPP setting screen is received. In the case where a request for an IPP setting screen is received, the process proceeds to S1702. However, in the case where a request for an IPP setting screen is not received, the process proceeds to S1707

In S1702, the CPU111 determines whether the request is from a user having an administrative authority. In the case where the request is from a user having the management authority, the process advances to step S1703. However, in the case where the request is from a user who does not have the management authority, the process advances to step S1706. Note that the user right is acquired by referring to the user right corresponding to the session ID as the identification information included in the HTTP request. In S1706, the CPU111 transmits an error notification to the communication apparatus of the communication partner, and advances the process to S1601.

In S1703, the CPU111 determines whether setting designates printing using IPP. In the case where the setting specifies printing using IPP, the process advances to S1705. However, in the case where the setting specifies that IPP printing is not to be used (IPP printing is not permitted), the process proceeds to S1704.

In S1704, the CPU111 transmits a Web page of the IPP setting screen that can transition to the preset management screen to the partner communication device. On the other hand, in step S1705, the CPU111 transmits to the partner communication apparatus a Web page of the IPP setting screen for button ashing for transition to the preset management screen.

In S1707, the CPU111 determines whether an HTTP request for a preset management screen is received. If an HTTP request for a preset management screen is received, the process proceeds to S1708. However, in a case where an HTTP request for the preset management screen is not received, the process proceeds to S1711.

In S1708, the CPU111 determines whether setting designates printing using IPP. In the case where the setting specifies printing using IPP, the process advances to S1709. However, in the case where the setting specifies that IPP printing is not to be used, the process proceeds to S1706.

In S1709, the CPU111 transmits a Web page of the preset management screen to the partner communication device. In S1710, the CPU111 receives a preset registration request generated by a user operation via the preset management screen, and registers a print preset in the storage unit 405.

More specifically, the Web server 416 receives data indicating print settings set via an input form on the management screen or the like via HTTP communication, and transmits the data to the remote UI service 415. Upon receiving the data, the remote UI service 415 generates a print preset based on the data, and registers a new preset in the print preset unit 305, or updates an existing preset.

Subsequently, in S1711, the CPU111 determines whether another HTTP request is received. If such an HTTP request is received, the process proceeds to S1712, but if such an HTTP request is not received, the process proceeds to S1601.

In S1712, the CPU111 executes other processing. The other processes may include, for example, a process for changing device settings of the MFP101 or a process for updating firmware of the MFP 101. For example, when the CPU111 receives an instruction to change the setting to the setting for printing using IPP from the external apparatus, the CPU111 executes the processing. When the execution of other processing is completed, the CPU111 advances the processing to S1601.

Referring to fig. 16 again, in S1620, the CPU111 determines whether a registration request for registering the print preset is received. The process advances to step S1621 in the case where a registration request for registering the print preset is received, but the process advances to step S1622 in the case where a registration request for registering the print preset is not received.

In S1621, the CPU111 performs processing for registering print presets. The specific processing is explained below with reference to fig. 18.

In step S1801, the CPU111 determines whether a print preset registration request including identification information is received. In the case where a print preset registration request including identification information is received, the process advances to step S1802. On the other hand, in a case where the print preset registration request including the identification information is not received (i.e., in a case where the registration request not including the identification information is received), a communication error notification is transmitted to the partner communication apparatus, and the process returns to S1601.

In S1802, the CPU111 identifies the user corresponding to the identification information added to the registration request. More specifically, IPP service 414 cooperates with Web server 416 to identify a user ID from a session ID included in the registration request.

In S1803, the CPU111 performs print preset registration processing based on the preset information included in the registration request. In this process, new registration, update, or error processing is performed. The specific processing thereof is explained in 522 of fig. 5, and thus a repetitive explanation thereof is omitted. When the registration processing is completed, the CPU111 advances the processing to S1601.

Referring to fig. 16 again, in S1622, the CPU111 determines whether or not a close instruction is received. If the close instruction is received, the process proceeds to S1623, but if the close instruction is not received, the process proceeds to S1601.

In S1623, the CPU111 performs the shutdown processing for the MFP101, and ends the series of processing.

As described above, in the present embodiment, the MFP101 as an image forming apparatus stores information indicating the correspondence between the user and the print presets. Therefore, it is possible to appropriately transmit a notification of the print preset for use by the user to the communication device using the print client. In addition, in the present embodiment, the print preset can be appropriately registered based on the operation of the authenticated user. Further, in the present embodiment, the print preset may be registered from the print client or the Web browser. Further, in the present embodiment, the print client can acquire and use the print preset stored in the image forming apparatus such as the MFP101, and can use the print preset registered in the print client by the user operation, which provides enhanced convenience. Therefore, the user can acquire the basic print preset from the MFP101 and modify the print preset to the desired print preset. This provides high convenience.

< modification example >

In the above-described embodiment, it is assumed that the identification information included in the request issued by the communication terminal 102 is a session ID or an access token, but this is by way of example and not limitation. For example, identification information such as a user ID or the like may be added to the request transmitted from the communication terminal 102 to the MFP 101. In this case, the MFP101 identifies the communication terminal user who issued the request based on the user ID included in the received request.

Further, in the above-described embodiment, the input of the authentication information is prompted in 511 and 512 of fig. 5, but this is by way of example and not limitation. For example, authentication information for IPP authentication may be stored as print client settings. More specifically, the user may input authentication information related to IPP authentication in advance via the setting screen of the print client, and the input authentication information may be stored in the storage device 134. When the communication device 102 receives the authentication request in 510, the communication device 102 may acquire the authentication information stored in the storage 134 and transmit the authentication information to the MFP101, instead of performing the processing in 511 and 512.

In the above-described embodiment, the print preset is explained. However, the application of the present invention is not limited to the print preset. For example, the present invention can be applied to presets relating to scan settings used when a communication terminal issues a scan request to the MFP101, presets relating to copy settings used when a communication terminal issues a copy request to the MFP101, and the like.

The present invention is not limited to the above-described embodiments, but various changes and modifications may be made without departing from the spirit and scope of the invention. Therefore, the following claims are appended to disclose the scope of the invention.

The present application claims priority based on japanese patent application 2017, 254234, filed on 28.12.2017, the entire contents of which are incorporated herein by reference.