Print job transmission method, and print job transmission system

Abstract

To improve usability and security related to the use of a cloud service using an image forming apparatus.SOLUTION: Provided is a print job transmission method for transmitting a print job to an image forming apparatus, the method including: a registration step of registering, by a first terminal, a print job in an input-side service device; a user authentication step of authenticating a user in a second terminal; a request transmission step of transmitting, by the second terminal, a transmission request to an output-side service device, with a success in the authentication in the user authentication step as at least one condition; and a transmission step of, upon receiving the transmission request, acquiring, by the output-side service device, the print job from the input-side service device and transmitting the print job to the image forming apparatus.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a print job sending method and a print job sending system for sending a print job to an image forming device. [Background technology]

[0002] In recent years, cloud print services, which register print jobs via a network service called a cloud and transmit the print jobs to an image forming device, have become popular. In a printing system using such a cloud print service, a user belonging to a tenant that uses the cloud print service registers an image forming device that is compatible with the cloud print service. This allows the user belonging to the tenant to use the image forming device from the cloud print service.

[0003] In this disclosure, a tenant is a service system deployed on the cloud, and has a storage area whose access is restricted to the tenant and users belonging to the tenant. For example, in the company A tenant of the cloud print service used by company A, employees working at company A are registered as users. In addition, by issuing a print-related instruction from an in-house client terminal to an image forming device under the management of company A, it becomes possible to cause the image forming device to perform printing.

[0004] In addition, with the diversification of work styles, there are more and more opportunities to print documents stored in a client terminal within the company using an image forming device installed outside the management of company A, such as at home, a shared office, a convenience store, a library, or a train station. It is also becoming possible to register an image forming device installed outside the management of company A in the cloud print service. Furthermore, client terminals are also becoming available both inside and outside the company. Such a service can be used by users belonging to a tenant of company A by associating an image forming device or client terminal installed outside the company with the cloud print service.

[0005] In printing in such a cloud print service, when a print job is accepted from a client terminal such as a personal computer, a job code for identifying the print job is issued, and the job code is notified to the client terminal. By using the job code, a user can cause the image forming device to execute printing based on the target print job. In addition, a function is provided for automatically deleting print jobs whose expiration date has passed by setting an expiration date for print jobs held by the cloud print service and their corresponding job codes.

[0006] When using a cloud print service, for example, two use cases can be envisioned: "printing using an image forming device installed in the company" (hereinafter referred to as "in-company printing") and "printing using an image forming device installed outside the company, such as in a shared office or at home" (hereinafter referred to as "outside the company printing"). Specific examples of situations in which these use cases can be applied include a case where a telecommuter prints documents to be used in work at home or a shared office, or a situation where documents to be distributed to customers are printed at home or a shared office before going out. Another conceivable situation is a case where documents to be printed at home are printed in the company in advance to check whether there are any errors in the print settings.

[0007] Thus, in a cloud print service, it is necessary to be able to access print data from both in-house and external image forming devices. Patent Document 1 discloses an example of a technology for enabling printing by linking different tenants on a cloud print service in a more suitable manner so that printing can be performed from both in-house and external image forming devices. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] JP 2022-154408 A Summary of the Invention [Problem to be solved by the invention]

[0009] Meanwhile, conventionally, such cloud print services are intended to be used so that each tenant and an image forming device cooperate with each other. Such cloud print services are configured to receive print jobs from client terminals and execute printing based on the print jobs by operating the image forming device. However, due to the diversification of work styles, particularly the spread of telecommuting, it has become necessary to print based on print jobs using smaller image forming devices installed at home or in shared offices. In this case, image forming devices that do not have an operation panel or image forming devices that have a small operation panel even if they have an operation panel are used, which makes it difficult to operate printing based on print jobs and reduces usability. In addition, with the diversification of installation locations of image forming devices, there is also a demand for improved security.

[0010] Therefore, an object of the present disclosure is to improve usability and security relating to the use of cloud services that utilize image forming apparatuses. [Means for solving the problem]

[0011] One aspect of the present disclosure is a print job transmission method for transmitting a print job to an image forming device, the print job transmission method including: a registration step in which a first terminal registers the print job in an input side service device; a user authentication step in which a second terminal authenticates a user; a request transmission step in which the second terminal transmits a transmission request to an output side service device, with at least one condition being that authentication in the user authentication step is successful; and a transmission step in which the output side service device, upon receiving the transmission request, obtains the print job from the input side service device and transmits it to the image forming device. Effect of the Invention

[0012] According to the present disclosure, it is possible to improve the usability and security of a cloud print service that uses an image forming apparatus. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a conceptual diagram showing the configuration of a system according to a first embodiment, a second embodiment, and a fourth embodiment. [Diagram 2] A block diagram showing a hardware configuration of an information processing device. [Diagram 3] Functional block diagram of information processing device [Figure 4] Table showing information stored in the work-from-home cloud print service and the home cloud print service [Diagram 5] A table showing print job related information [Figure 6] Table showing model information [Figure 7] A diagram explaining how to register a printer on an authentication server [Figure 8] A table showing an example of information used for application authentication [Figure 9] A table showing an example of information used for application authentication [Figure 10] A diagram explaining how to register a printer on a mobile device [Figure 11] Sequence diagram for explaining print job registration [Figure 12] FIG. 1 is a sequence diagram illustrating transmission of a print job to an image forming apparatus according to a first embodiment. [Figure 13] Sequence diagram to explain the preparation stage of application authentication [Figure 14] Sequence diagram to explain the operational stages of application authentication [Figure 15] Another sequence diagram to explain the operational stages of application authentication [Figure 16]A flowchart illustrating a process for registering a print job by a client terminal. [Figure 17] A diagram showing the screen displayed on the client terminal [Figure 18] FIG. 11 is a sequence diagram illustrating an example of a user authentication process in a client terminal. [Figure 19] FIG. 11 is a sequence diagram illustrating another example of the user authentication process in the client terminal. [Figure 20] Diagram showing the screen displayed on a mobile device [Figure 21] A flowchart showing an operation for switching between displaying and hiding a button on a mobile terminal. [Figure 22] Table showing model information [Diagram 23] A flowchart for explaining a process related to a request to send a print job in a mobile terminal. [Figure 24] FIG. 13 is a sequence diagram illustrating a process for deleting a print job in response to a request from a client terminal. [Diagram 25] A sequence diagram for explaining a process for deleting a print job in response to a request from a mobile terminal. [Figure 26] FIG. 11 is a sequence diagram illustrating transmission of a print job to an image forming apparatus according to a second embodiment. [Figure 27] A sequence diagram for explaining a method of user authentication on a mobile terminal. [Figure 28] FIG. 13 is a diagram showing a screen displayed by a mobile terminal for authentication in the second embodiment. [Figure 29] 1 is a table showing information that an authentication server holds for authentication in the second embodiment. [Diagram 30] FIG. 13 is a conceptual diagram showing the configuration of a system according to a third embodiment. [Diagram 31] A table showing the information held by the push notification server [Diagram 32] A table showing the information that will be pushed to your mobile device [Diagram 33] Sequence diagram to explain a method for enabling push notifications [Diagram 34] A diagram showing a screen including a QR code (registered trademark) for mobile device registration displayed on a client device. [Diagram 35] A sequence diagram for explaining a method for starting an app for requesting transmission of a print job on a mobile terminal by a push notification. [Diagram 36] A diagram showing the screen displayed on a mobile device that receives a push notification [Figure 37] A flowchart for explaining a process from when an application for requesting transmission of a print job is launched to when the application requests transmission of a print job. [Figure 38] A sequence diagram for explaining a method for performing user authentication on a client terminal. [Figure 39] A sequence diagram for explaining the method from when a mobile terminal reads a QR code (registered trademark) including a job code displayed on a client terminal to when it requests transmission of a print job. [Diagram 40] A diagram of a screen including a QR code displayed on a client device that receives a push notification [Diagram 41] A table showing information contained in the QR code displayed by a client terminal that receives a push notification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Note that the following embodiments do not limit the present disclosure according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the present disclosure.

[0015] First Embodiment <1. System configuration> An example of the system configuration of a print job transmission system according to the first embodiment will be described with reference to FIG. 1. The system shown in FIG. 1 includes a telecommuting cloud print service (also referred to as an "input cloud print service" or a "telecommuting service") 103, which is an example of a cloud print service. The telecommuting service 103 is mainly used by telecommuters, who can register print jobs from a client terminal 101 such as a personal computer (hereinafter also referred to as a "PC") used at home or in a shared office. Printing based on the registered print job is performed by the telecommuter using an image forming device 102 installed at home or in a shared office. At that time, an instruction to transmit the print job to the image forming device 102 is executed from a mobile terminal 104 such as a smartphone used by the telecommuter. The mobile terminal 104 instructs a home cloud print service (also referred to as an "output cloud print service" or a "home service") 105 to transmit the print job to the image forming device 102. In addition, in such a telecommuting service 103, the system administrator of company A can grasp the printing status (e.g., the number of printed sheets, etc.) of users who are under the management of company A and are located outside the company, such as at home or in a shared office. By using this mechanism, consumables (e.g., ink, toner, paper, etc.) of the image forming device 102 installed outside the company, such as at home or in a shared office, can be managed, and can be used for expense settlement and usage audits, etc. In addition, telecommuters can print for work without coming to the office, which is expected to improve work efficiency. Furthermore, printing via the cloud allows printing to be done safely and reliably, and the leakage of internal company information can be prevented. The telecommuting service 103 is a cloud service that realizes secure printing in such telecommuting and allows the company administrator to grasp the printing status.

[0016] The telecommuting service 103 is a cloud print service that can be used by a user (such as an employee) under the management of company A. The client terminal 101 is a client terminal such as a PC used by the user when telecommuting. The image forming device 102 is an image forming device registered by the user in the telecommuting service 103 and the home service 105. As will be described later, the image forming device 102 is registered in the telecommuting service 103 in association with user identification information. The image forming device 102 is registered in the home service 105 in association with mobile terminal identification information, which is identification information of the mobile terminal 104. The image forming device 102 is installed outside the company, such as at home. The mobile terminal 104 is a mobile terminal that can be used by the user at all times when telecommuting. The mobile terminal 104 may be under the management of company A, or may be owned by the user and outside the management of company A. The home service 105 is a schematic representation of a cloud print service capable of transmitting a print job to the image forming apparatus 102. As a part of this cloud print service, there is a service linked to the telecommuting service 103. Through this linkage, a print job registered in the telecommuting service 103 is transmitted to the image forming apparatus 102 via the home service 105 in response to an instruction from the mobile terminal 104. This allows the image forming apparatus 102 to perform printing based on the print job registered in the telecommuting service 103. In general, the telecommuting service 103 is under the management of company A, and therefore access is limited to the client terminal 101 managed by company A. Although not shown, there are cases where access to the telecommuting service 103 from home is permitted. Furthermore, the home service 105 is outside the management of company A, and can be accessed from both the client terminal 101 managed by company A and the mobile terminal 104 outside the management of company A.

[0017] 1, for convenience, company A and home are depicted separately, but the actual usage is not limited to this. For example, the client terminal 101 may be a terminal managed by company A and may be used at home. Furthermore, the client terminal 101 under the management of company A is not limited to a PC, and may be a smartphone or a tablet.

[0018] In this configuration, for example, when the telecommuting service 103 receives print job data (hereinafter also simply referred to as a "print job") from the client terminal 101, it issues a job code, which is a unique identifier for the print job.

[0019] Thereafter, when the home service 105 receives a print job transmission request and a job code from the authenticated mobile terminal 104, it obtains a print job corresponding to the job code from the telecommuting service 103. Then, the home service 105 transmits the print job to the image forming device 102.

[0020] In the following description, for convenience, the tenant of company A will also be referred to as an “intra-company tenant.” In addition, there may be multiple client terminals 101, multiple image forming apparatuses 102, and multiple mobile terminals 104.

[0021] The above-mentioned components are connected to each other so as to be able to communicate with each other via a predetermined network 100. The type of network 100 is not particularly limited as long as data can be transmitted and received between the above-mentioned components. As a specific example, the network 100 may be any of the Internet, a LAN, a WAN, a telephone line, a dedicated digital line, an ATM, and the like, or a combination of these.

[0022] In the first embodiment, the telecommuting service 103 is responsible for registering print jobs and issuing job codes. However, the configuration shown in FIG. 1 is merely an example and does not necessarily limit the configuration of the print job transmission system according to the first embodiment. As a specific example, the telecommuting service 103 may also serve as the home service 105. As another example, the home service 105 may also serve as the telecommuting service 103. In this way, the functions of two or more cloud print services among the series of cloud print services shown in FIG. 1 may be realized by one cloud print service.

[0023] With reference to FIG. 1, an example of the configuration of the print job transmission system according to the first embodiment will be further described. The system shown in FIG. 1 includes the telecommuting service 103, the client terminal 101, the image forming device 102, the mobile terminal 104, and the home service 105 illustrated in FIG. 1. In addition, the system includes an authentication server 107 for executing authentication-related processes when the telecommuting service 103 and the home service 105 are used. Furthermore, the system includes an image forming device management server (also called an "apparatus management server") 108 for executing authentication-related processes for the image forming device 102. Note that the authentication server corresponding to the telecommuting service 103 and the authentication server corresponding to the home service 105 may be separate, or may be integrated. As will be described later, the authentication server corresponding to the home service 105 may be composed of a common authentication server and a region-specific authentication server.

[0024] Authentication server 107 typically represents an authentication server used by client terminal 101 and mobile terminal 104 when accessing telecommuting service 103 and home service 105, respectively. Image forming device management server 108 typically represents an image forming device management server that executes processes related to management of image forming devices 102 that use telecommuting service 103 and home service 105.

[0025] In this configuration, the authentication server corresponding to the home service 105 aims to authenticate each application installed in the mobile terminal 104, and supports authentication using an application account ID. As long as it is a method capable of authenticating each application, it is not limited to the above method, and for example, it may support authentication using a one-time password method.

[0026] As a method for authenticating each application, for example, the mobile terminal 104 acquires model information of the image forming device 102 shown in Fig. 6 from the image forming device 102 owned by the user in order to authenticate the mobile terminal 104 itself. Then, the mobile terminal 104 transmits the model information to the authentication server 107 and requests authentication information.

[0027] Specifically, the mobile terminal 104 transmits the model name, serial number, regional information, and image forming device ID (hereinafter also referred to as "printer ID" or "printer identification information") to the authentication server 107, and requests authentication information. Upon receiving the model information of the image forming device 102, the authentication server 107 verifies that the received model information of the image forming device 102 is appropriate, and if it is confirmed that the model information is legitimate, transmits authentication information (application account ID) to the mobile terminal 104.

[0028] An example of a method for confirming that the received model information of the image forming device 102 is appropriate is realized by the authentication server 107 cooperating with the image forming device management server 108 .

[0029] For example, when the image forming device 102 is installed in a user's home, the image forming device 102 transmits model information (model name, serial number, and area information) to the image forming device management server 108 by the user's operation without delay using a communication function of the image forming device. The image forming device management server 108 receives the model information (model name, serial number, and area information of the image forming device 102 model information) and issues a printer ID corresponding to the model information. The printer ID is device identification information for uniquely identifying each image forming device. After the issuance, the mobile terminal 104 obtains the printer ID corresponding to the image forming device 102 from the image forming device management server 108 and stores it in the mobile terminal 104. Then, the mobile terminal 104 transmits the printer ID to the authentication server 107 when the authentication server 107 is used. The authentication server 107 transmits the printer ID received from the mobile terminal 104 to the image forming device management server 108. The image forming device management server 108 verifies that the received printer ID is a printer ID issued and managed by the image forming device management server 108. As a result, the authentication server 107 verifies that the received model information of the image forming device 102 is appropriate.

[0030] The image forming device management server 108 receives the model name, serial number, and area information included in the model information of the image forming device 102, and issues a printer ID. The mobile terminal 104 has the image forming device management server 108 issue a printer ID corresponding to the image forming device 102 in advance, and stores the printer ID in the mobile terminal 104.

[0031] The mobile terminal 104 requests the image forming apparatus 102 to transmit a print job registered in the telecommuting service 103 by the client terminal 101, and this request will be referred to as a "print job transmission request." When issuing a print job transmission request, the mobile terminal 104 transmits authentication information (application account ID) received and stored from the authentication server 107 to the authentication server 107 and requests an access token. Therefore, when issuing a print job transmission request, the user does not need to input authentication information into the mobile terminal 104. The authentication server 107 that has received the authentication information verifies that the received authentication information is authentication information issued and managed by the authentication server 107. If it is confirmed that the authentication information is appropriate, the authentication server 107 transmits the access token and the URL of the home service 105 to be accessed to the mobile terminal 104.

[0032] Here, in the authentication performed when issuing a print job transmission request, authentication information (application account ID) stored in the mobile terminal 104 (particularly, in an application installed in the mobile terminal) is used. This authentication information is stored only in the mobile terminal 104. This authentication information is managed so that it is not stored in other terminals such as other mobile terminals. Therefore, by using this authentication, one account is set for one application, and in this sense, this authentication is called "Account of App authentication". Also, it is abbreviated to "AOA authentication". Also, when multiple mobile terminals 104 are associated with the same image forming device 102, each application account ID is set for the application installed in each mobile terminal 104. Therefore, if different mobile terminals 104 are used to use the same image forming device 102, authentication is performed for different application account IDs. In this sense, "AOA authentication" can also be said to be "terminal authentication". Also, "application account ID" can also be said to be "terminal authentication information". Note that here, it is assumed that only one application to be authenticated is installed in the same mobile terminal 104.

[0033] In contrast, authentication in which one account is given to one user is called "One Account for One Person Authentication," or "OAO Authentication" for short.

[0034] In the first embodiment, the authentication server 107 is capable of performing both AOA authentication and OAO authentication. When performing AOA authentication, the authentication server 107 functions as a terminal authentication server, and when performing OAO authentication, the authentication server 107 functions as a user authentication server.

[0035] Thereafter, the mobile terminal 104 accesses the home service 105 using the access token received from the authentication server 107 and the URL of the home service 105 to be accessed. The home service 105 that has received the access token transmits the access token to the authentication server 107. The authentication server 107 confirms that the received access token is one that has been issued and is managed by the authentication server 107. When it is confirmed that the access token is appropriate, the home service 105 is notified of this fact. Upon receiving this notification, the home service 105 transmits screen data to the mobile terminal 104. As a specific example, data of a screen 2020 as shown in FIG. 20(b) may be transmitted. Based on the received data of the screen 2020, the mobile terminal 104 can present the screen 2020 to the user.

[0036] It should be noted that there may be multiple client terminals 101, multiple image forming apparatuses 102, and multiple mobile terminals 104.

[0037] The above-mentioned components are connected to each other so as to be able to communicate with each other via a predetermined network 100. The type of network 100 is not particularly limited as long as data can be transmitted and received between the above-mentioned components. As a specific example, the network 100 may be any of the Internet, a LAN, a WAN, a telephone line, a dedicated digital line, an ATM, and the like, or a combination of these.

[0038] In the first embodiment, the authentication server 107 and the image forming device management server 108 are realized as separate cloud services so that the authentication server 107 cooperates with the image forming device management server 108 to issue authentication information. Meanwhile, the configuration shown in FIG. 1 is merely an example, and does not necessarily limit the configuration of the print job transmission system according to the first embodiment. As a specific example, the authentication server 107 may also serve as the image forming device management server 108. In this manner, the functions of two or more cloud services among the series of cloud services shown in FIG. 1 may be realized by one cloud service. Also, the authentication server 107 and the image forming device management server 108 may use different authentication servers and image forming device management servers depending on the region.

[0039] <2. Hardware configuration of information processing device> An example of a hardware configuration of an information processing device 200 constituting a system according to an embodiment of the present disclosure will be described with reference to FIG. 2. The information processing device 200 according to the first embodiment includes a processor 201 such as a central processing unit (CPU), a random access memory (RAM) 202, and a read only memory (ROM) 203. The information processing device 200 also includes an auxiliary storage device 204 and a network I / F 207. The information processing device 200 may also include at least one of an input device 205 and an output device 206. The information processing device 200 may also include an imaging device 208. The processor 201, the RAM 202, the ROM 203, the auxiliary storage device 204, the input device 205, the output device 206, the network I / F 207, and the imaging device 208 are connected to each other via a bus 209.

[0040] The processor 201 is a central processing unit that controls various operations of the information processing device 200. For example, the processor 201 may control the operation of the entire information processing device 200. The RAM 202 is a main storage memory of the processor 201, and is used as a work area or a temporary storage area for expanding various programs. The ROM 203 stores programs (e.g., BIOS) for the processor 201 to control the operation of the information processing device 200. The auxiliary storage device 204 stores programs such as an OS (Operating System) that is basic software, various applications, and various data. The auxiliary storage device 204 can be realized, for example, by a non-volatile memory such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The input device 205 is a device for receiving instructions from a user. The input device 205 can be realized, for example, by an operation device such as a pointing device such as a mouse, a keyboard, or a touch panel. The output device 206 is a device for presenting various information to a user. The output device 206 can be realized by a display device such as a display that presents information to a user by displaying various display information, screens, etc. The network I / F 207 is an interface that is connected to a predetermined network (e.g., a LAN or the Internet) and communicates with external devices via the network. The imaging device 208 is a device that converts an image captured by an imaging element into digital data. The digital data is temporarily stored in the RAM 202. The digital data is then converted by a program executed by the processor 201 so as to conform to a predetermined image format, and is stored in the auxiliary storage device 204 as image data.

[0041] The above-mentioned configuration is merely an example and does not necessarily limit the hardware configuration of the information processing device 200. As a specific example, some of the multiple components included in the information processing device 200 described above (for example, at least one of the input device 205 and the output device 206) may be externally attached to the outside of the information processing device 200.

[0042] Moreover, the functional configuration and processing described below are realized by a desired information processing device 200 loading a program stored in the ROM 203 or the auxiliary storage device 204 onto the RAM 202 and then executing the program.

[0043] <3. Functional configuration of information processing device> With reference to FIG. 3, an example of the functional configuration of an information processing device constituting the print job transmission system according to the first embodiment will be described, focusing in particular on the configuration related to the provision of the telecommuting service 103 and the home service 105. The telecommuting service 103 and the home service 105 may be configured by different information processing devices, or a plurality of cloud print services may be provided by one information processing device. For convenience, the following description focuses on the case where the information processing device 300 executes various processes related to the provision of the telecommuting service 103, but the same is essentially true when the home service 105 is provided. The description will be given of the configuration of the information processing device 300 when executing various processes for the telecommuting service 103, but the configuration of the information processing device 300 when executing various processes for the home service 105 is also similar.

[0044] The information processing device 300 includes a setting management unit 301, a print job management unit 302, a communication unit 303, an authentication control unit 304, a storage unit 305, and a UI control unit 306. The information processing device 300 is basically configured based on the information processing device 200 having the hardware configuration shown in Fig. 2. In other words, the information processing device 300 can function as an input side service device, which is an information processing device equipped with a server for providing the telecommuting service 103. Similarly, the information processing device 300 can also function as an output side service device, which is an information processing device equipped with a server for providing the home service 105.

[0045] The setting management unit 301 retains setting information related to various functions of the telecommuting service 103 by storing it in a predetermined storage area (e.g., the RAM 203, the auxiliary storage device 204, etc.), and reads out the setting information from the storage area at a desired opportunity. The setting information includes, for example, tenant information and print job information related to registered print jobs (e.g., the expiration date of a print job, etc.).

[0046] For example, Fig. 4(a) and Fig. 4(b) show an example of setting information for a cloud print service. Specifically, Fig. 4(a) shows an example of setting information for an in-house tenant (e.g., a tenant of company A) of the telecommuting service 103. Fig. 4(b) shows an example of setting information for the home service 105.

[0047] First, an example of the setting information of an internal tenant of the telecommuting service 103 shown in Fig. 4(a) will be described. "Own tenant information" is information for identifying an internal tenant (e.g., the tenant of company A), and for example, information such as a URL may be set. In the example shown in Fig. 4(a), "http: / / companyA.com" is set as the own tenant information. Note that the type of information set as the own tenant information is not particularly limited as long as it is possible to identify an internal tenant, and for example, an identifier such as a tenant ID may be set.

[0048] The "linked cloud print service information" is information for identifying the home service 105 that is used as a destination of a print job by the telecommuting service 103 associated with an internal tenant. For example, information such as a URL may be set as the "linked cloud print service information." In the example shown in FIG. 4(a), "http: / / cps.com" is set as the linked cloud print service information. Note that the type of information set as the linked cloud print service information is not particularly limited as long as it is possible to identify the linked cloud print service, and for example, an identifier such as a cloud print service ID may be set.

[0049] The "deadline setting information" is an example of print job information, and is the expiration setting information for determining the expiration date of a print job held by the cloud print service. In the example shown in FIG. 4(a), "10 minutes" is set as the expiration setting information. This setting value has a value for determining the expiration date of information related to a print job held by the cloud print service, and is a setting value that is commonly applied to all tenants, not just to Company A's tenant.

[0050] Next, an example of the setting information of the home service 105 shown in Fig. 4(b) will be described. The "cloud print service information" is information for identifying the home service 105, and information such as a URL may be set. In the example shown in Fig. 4(b), "http: / / cps.com" is set as the cloud print service information. Note that the type of information set as the cloud print service information is not particularly limited as long as it is possible to identify the cloud print service, similar to the example of the in-house tenant shown in Fig. 4(a).

[0051] The print job management unit 302 acquires information related to a print job from another device (e.g., the client terminal 101 or the mobile terminal 104, etc.) and stores the information in a predetermined storage area (e.g., the storage unit 305, etc.). The print job management unit 302 may also acquire information related to a print job from a cloud print service (e.g., the telecommuting service 103, etc.) and store the information in a predetermined storage area.

[0052] The print job management unit 302 corresponding to the telecommuting service 103 may determine whether or not a print job received from another device (e.g., the client terminal 101, etc.) is permitted to be printed outside the company using a cloud print service. The print job management unit 302 may also issue permission information related to the execution of the print job.

[0053] When a print job management unit 302 corresponding to the home service 105 receives a print job transmission request specifying a job code from the mobile terminal 104, it acquires the corresponding print job from the telecommuting service 103. The print job management unit 302 corresponding to the home service 105 may transmit the acquired print job to the image forming device 102. Note that the printer ID for identifying the image forming device 102 is acquired from the authentication information used in the AOA authentication described above.

[0054] For example, Figures 5(a) and 5(b) show an example of a print job and information related to the print job that the cloud print service stores in a specified storage area. Specifically, Figure 5(a) shows an example of a print job and information related to the print job that the cloud print service corresponding to an internal tenant (e.g., the telecommuting service 103) stores in a specified storage area. Also, Figure 5(b) shows an example of information related to the print job that the home service 105 stores in a specified storage area.

[0055] First, an example of a print job and information related to the print job stored in a specified storage area by a cloud print service corresponding to an internal tenant, as shown in Fig. 5(a), will be described. The series of information shown in Fig. 5(a) is generated, for example, for each print job and stored in a specified storage area. For convenience, each piece of information will be described below assuming that the information shown in Fig. 5(a) is managed by the telecommuting service 103.

[0056] The "print job ID" is identification information (ID value) that is uniquely assigned by the telecommuting service 103 to manage print jobs and information related to the print jobs.

[0057] A "job code" is issued by the telecommuting service 103 for each print job in order to allow the telecommuting service 103 and the home service 105 to cooperate with each other. This job code is used, for example, to specify a print job to be printed by the image forming device 102. Note that the job code is issued to the print job so that there is no duplication not only within a tenant but also between tenants. However, this is not necessarily the case.

[0058] "Print job data" is data of the print job itself, for example, binary data. As a specific example, the print job data is data that complies with PDL (Page Description Language), PDF (Portable Document Format), JPEG, etc. Furthermore, instead of the data of the print job itself, information for accessing a document stored in an external storage (for example, an address, etc.) may be set as the "print job data".

[0059] The "print job execution result" is information according to the result of the print job being executed by the image forming device 102. In the example shown in FIG. 5(a), "OK" is set as the print job execution result, indicating that printing was executed normally. This print job execution result is, for example, information that the telecommuting service 103 receives from the home service 105 together with the job code. If an error occurs during printing, for example, an error code or the like may be set as the print job execution result. In addition, the print job execution result may include either color printing or monochrome printing, the number of pages and the number of copies, billing information, and the like. In addition, information regarding the date and time when printing was executed, the location, and the like may be included in the print job execution result.

[0060] Next, an example of information related to a print job that the home service 105 stores in a predetermined memory area will be described, which is shown in Fig. 5(b). The series of information shown in Fig. 5(b) is stored, for example, in a predetermined memory area. This predetermined memory area is generated for each print job every time the home service 105 receives a print job. The memory area corresponding to one print job has a size sufficient to store information related to one print job.

[0061] The "print job ID", "job code", and "print job execution result" are the same as those shown in FIG. 5(a), so a duplicated explanation will be omitted.

[0062] The "print job sender" is information for identifying the cloud print service (e.g., the telecommuting service 103) that sent information about the print job to the home service 105, and may be set to information such as a URL. In the example shown in Fig. 5(b), "http: / / companyA.com" is set as the print job sender.

[0063] The communication unit 303 transmits and receives various data to and from other devices (e.g., the client terminal 101, the image forming device 102, and the mobile terminal 104). For example, the communication unit 303 may receive a print job or a request to execute a print job from another device. The communication unit 303 may also receive various processing requests from other cloud print services and transmit information according to the processing results to the other cloud print services.

[0064] The authentication control unit 304 executes various processes related to user management. The authentication control unit 304 may store information about a user added in response to an instruction from a tenant administrator in a predetermined storage area (for example, the storage unit 305 described later). As another example, the authentication control unit 304 may manage information about a user by cooperating with an external authentication service.

[0065] The storage unit 305 stores various data. For example, the storage unit 305 may store various data in response to a request from the print job management unit 302 or the authentication control unit 304.

[0066] The UI control unit 306 executes reception of input from a user in response to a request from another device (for example, the client terminal 101, the image forming device 102, and the mobile terminal 104). The UI control unit 306 also executes processing for generating and outputting a UI for realizing the presentation of various information to a user. As a specific example, the UI control unit 306 may generate a screen in response to a request from a browser operating on the client terminal 101 or the mobile terminal 104. Then, the UI control unit 306 may transmit the screen (or data related to the output of the screen) to the client terminal 101 or the mobile terminal 104 via the communication unit 303. As a result, the screen generated by the UI control unit 306 is presented to the user via the browser operating on the client terminal 101 or the mobile terminal 104. The screen is, for example, a screen as will be described separately later with reference to FIG. 17.

[0067] Next, referring to Fig. 3, an example of the functional configuration of an information processing device constituting the print job transmission system according to the first embodiment will be described, focusing in particular on the configuration related to the provision of the client terminal 101 and the mobile terminal 104. Note that the client terminal 101 and the mobile terminal 104 may be configured by different information processing devices, or may be provided by a single information processing device. Note that, for convenience, the following description will focus on the case where the information processing device 300 executes various processes related to the provision of the mobile terminal 104, but the same is essentially true when the client terminal 101 is provided.

[0068] The setting management unit 301 holds setting information related to various functions of applications installed to utilize the telecommuting service 103 and the home service 105 by storing it in a specified storage area. Here, the specified storage area is, for example, the RAM 202, the auxiliary storage device 204, etc. Then, the setting management unit 301 reads the setting information from the storage area at a desired opportunity. The setting information includes, for example, model information of the image forming device 102 (for example, the model name of the image forming device 102 and a printer ID for uniquely identifying the image forming device 102, etc.).

[0069] For example, Fig. 6 shows an example of model information of the image forming device 102. "Model name" is information indicating the name of the image forming device 102. In the example shown in Fig. 6, "Printer A" is set as the model name. Note that the information set as the model name is not particularly limited as long as it is possible to identify the type of the image forming device 102, and an identifier such as a model ID may be set.

[0070] The "serial number" is information for identifying the image forming apparatus 102. In the example shown in Fig. 6, "KWRY850203" is set as the serial number. Note that the information set as the serial number is not particularly limited as long as it is possible to identify the image forming apparatus 102, and any format may be used.

[0071] The "MAC address" is information for identifying the image forming apparatus in the second layer of the OSI reference model. In the example shown in Fig. 6, "00-11-22-1C-DD-EE" is set as the MAC address.

[0072] The "region information" is information for identifying the region in which the image forming apparatus 102 is installed. In the example shown in Fig. 6, "United States" is set as the region information. Note that the information set as the region information is not particularly limited as long as it is possible to identify the region, and an identifier such as a region ID may be set.

[0073] The "printer ID" is information for the telecommuting service 103 and the home service 105 to uniquely identify the image forming device 102. In the example shown in FIG. 6, "kwryyaaioa" is set as the printer ID. The printer ID is information for identifying the image forming device 102 registered in the telecommuting service 103 and the home service 105, and is information commonly applied to each cloud print service. The printer ID may be managed and issued in cooperation with a printer ID management service provided by the image forming device management server 108.

[0074] The print job management unit 302 acquires information related to the image forming apparatus 102 from the image forming apparatus 102, and stores the information in a predetermined storage area (for example, the storage unit 305, etc.). The print job management unit 302 may also determine whether the image forming apparatus 102 supports the telecommuting service 103 and the home service 105, using the information related to the image forming apparatus 102 received from the image forming apparatus 102. The print job management unit 302 may transmit the information related to the image forming apparatus 102 received from the image forming apparatus 102 to the telecommuting service 103 and the home service 105. The information related to the image forming apparatus 102 to be transmitted is the same as the information described with reference to FIG. 6, and the home service 105 stores the same information as that in FIG. 6 in a predetermined storage area.

[0075] The communication unit 303 transmits and receives various data to and from other devices (e.g., the image forming apparatus 102, the telecommuting service 103, and the home service 105). For example, the communication unit 303 may receive information related to the image forming apparatus 102 from the image forming apparatus 102. The communication unit 303 may also receive various processing requests from the telecommuting service 103 and the home service 105, and transmit information according to the processing results to the cloud print service.

[0076] The authentication control unit 304 executes various processes related to user management. The authentication control unit 304 may generate information about users who use the telecommuting service 103 and the home service 105, and store the information in a predetermined storage area (for example, the storage unit 305 described later). As another example, the authentication control unit 304 may manage information about users by cooperating with an external authentication service.

[0077] The storage unit 305 stores various data. For example, the storage unit 305 may store various data in response to a request from the print job management unit 302.

[0078] The UI control unit 306 executes processing for receiving input from a user and generating and outputting a UI for realizing the presentation of various information to the user in response to a request from another device. Here, the other devices are, for example, the image forming device 102, the telecommuting service 103, and the home service 105. As a specific example, the UI control unit 306 may receive a screen (or data related to the output of the screen) generated by the telecommuting service 103 or the home service 105 via the communication unit 303. As a result, the UI control unit 306 presents the received screen to the user via a browser running on the mobile terminal 104.

[0079] <4. Registration of image forming devices to various servers> 7, a method for registering the image forming device 102 in the image forming device management server 108 and the authentication server 107 will be described. Here, the authentication server 107 is described as being compatible with both the telecommuting service 103 and the home service 105, but separate authentication servers may be compatible with each service.

[0080] First, the image forming device 102 is registered in the image forming device management server 108. When registering, the image forming device 102 transmits its own serial number and MAC address to the image forming device management server 108. The image forming device management server 108 assigns a printer ID to the set of the serial number and MAC address and transmits it to the image forming device 102. The image forming device 102 saves the printer ID in its own device. The image forming device management server 108 also acquires model information corresponding to the serial number and transmits the model information to the image forming device 102. The image forming device 102 also saves the model information in its own device.

[0081] Next, the image forming device 102 is registered in the telecommuting service 103. That is, the printer ID and the user account ID (user account identification information) are associated and registered in the telecommuting service 103. This allows the user to use the telecommuting service 103 after OAO authentication. The telecommuting service 103 can also obtain the printer ID corresponding to the user account ID used in the OAO authentication. Note that, when registering, the authentication server corresponding to the telecommuting service 103 checks whether the image forming device 102 identified by the printer ID has been properly registered in the image forming device management server 108. Only when this is confirmed, is the printer ID associated and the user account ID registered in the telecommuting service 103.

[0082] In relation to AOA authentication, information such as that shown in FIG. 8 is stored in the authentication server corresponding to the home service 105.

[0083] Referring to FIG. 8, "application account information" is information issued by the authentication server for each cloud print application (also called "application") 2000 (FIG. 20) installed in the mobile terminal 104 that accesses the authentication server. As the application account information, for example, information such as an application account ID is set. In the example shown in FIG. 8, "aa001" is set as the account information.

[0084] The "application account authentication information" is information issued by the authentication server for each application 2000 of the mobile terminal that accesses the authentication server, and information such as a password is set. In the example shown in Fig. 8, "password001" is set as the application account authentication information.

[0085] The "model name", "serial number", "MAC address", "area information", and "printer ID" are the same as the printer ID of the image forming apparatus 102 described with reference to FIG.

[0086] In this manner, the storage unit 305 of the authentication server can store the application account authentication information and the model information of the image forming apparatus in association with each other.

[0087] In this way, the printer ID and the application account ID are registered in association with each other in the authentication server corresponding to the home service 105. When performing registration, the authentication server corresponding to the home service 105 checks whether the image forming device 102 specified by the printer ID is properly registered in the image forming device management server 108. Only when the check is successful, the application account ID and the printer ID of the image forming device 102 are registered in association with each other in the authentication server corresponding to the home service 105. This allows the user to use the home service 105 by going through AOA authentication and satisfying a predetermined condition. Also, the home service 105 can obtain the printer ID corresponding to the application account ID used in the AOA authentication. As will be described later, when AOA authentication is enabled, the home service 105 can obtain the printer ID every time AOA authentication is performed. Therefore, the home service 105 can specify the image forming device 102 to be used for cloud printing by using the printer ID obtained from the AOA authentication. Normally, a printer ID needs to be registered in advance to use the home service 105, but if AOA authentication is enabled, this registration is not necessary.

[0088] A user installs the image forming apparatus 102 at, for example, his / her home and then performs initial settings. The image forming apparatus 102 is first registered in the image forming apparatus management server 108 by the user performing a predetermined operation on the user interface of the image forming apparatus 102. The image forming apparatus 102 may also be registered in the image forming apparatus management server 108 by the user performing a predetermined operation on the user interface of an information processing apparatus connected to the image forming apparatus 102, for example, via a home LAN. At this time, the image forming apparatus 102 transmits the serial number and MAC address of the image forming apparatus 102 to the image forming apparatus management server 108, and the image forming apparatus management server 108 issues a printer ID for the set of the serial number and the MAC address. The image forming apparatus 102 can be registered in the information processing apparatus connected to the image forming apparatus 102 via the home LAN by the serial number and MAC address of the image forming apparatus 102. The image forming apparatus 102 can also be registered in the information processing apparatus connected to the image forming apparatus 102 via the home LAN by the printer ID. The image forming device management server 108 has a database for storing model information (model name, serial number, regional information, cloud print support information (also referred to as "support information")) for each model of the image forming device 102. Therefore, the model information can be associated with a printer ID associated with the serial number and MAC address of the image forming device 102 and stored or transmitted. The regional information may be associated in advance with the serial number of the image forming device 102, or may be set based on the region where the image forming device 102 is installed.

[0089] Furthermore, when the client terminal 101 accesses the telecommuting service 103 by a user operation, the client terminal 101 first performs OAO authentication. If the OAO authentication is successful, a web page (not shown) of the telecommuting service 103 is displayed on the client terminal 101. By pressing a printer registration button arranged on the web page, a web page (not shown) for registering the image forming device 102 to the telecommuting service 103 is displayed. The user inputs a printer ID into the registration web page. The user account ID used in the OAO authentication and the printer ID input into the registration web page are sent to an authentication server for the telecommuting service 103. The printer ID and the user account ID are then associated with each other and registered in the telecommuting service 103. As will be described later, in the OAO authentication before the client terminal 101 registers a print job in the telecommuting service 103, the client terminal 101 transmits the user account ID to the telecommuting service 103. This makes it possible to specify the image forming device 102 identified by the printer ID associated with the user account ID as the destination of the print job. By the above registration, the OAO authentication information (user account ID, password) and the printer ID are stored in association with each other in the telecommuting service 103.

[0090] <5. Registering the image forming device to the mobile device> In relation to AOA authentication, information such as that shown in FIG. 9 is stored in the mobile terminal 104.

[0091] 9, the "model name", "serial number", "MAC address", "regional information", "application account ID", and "application account authentication information" are similar to the information held by the authentication server corresponding to the home service 105 in relation to AOA authentication. The mobile terminal 104 does not hold a "printer ID". The "common authentication server access information" and the "regional authentication server access information" are information for accessing the common authentication server and the region-specific authentication server, respectively.

[0092] "Access information of common authentication server" is access information of the global common authentication server 107A. "Access information of area-specific authentication server" is access information of the area-specific authentication server 107B received from the common authentication server 107A.

[0093] When a user performs a predetermined operation on the mobile terminal 104, the image forming device 102 can be registered in the mobile terminal 104 connected to the image forming device 102 via a home LAN using the serial number and MAC address of the image forming device 102. The image forming device 102 can also be registered in the mobile terminal 104 using a printer ID.

[0094] 10, in S1001, the image forming device 102 is registered in the mobile terminal 104 so that the image forming device 102 can be used from the mobile terminal 104 in a home local area network (LAN), for example. This corresponds to "Registration in local area network" shown in FIG. 7. This registration enables a "Print photo" button 2013, a "Print document" button 2014, and a "Scan" button 2015 arranged on a screen 2010 shown in FIG. 20. That is, for example, it becomes possible to print photos and documents stored in the mobile terminal 104 by the image forming device 102 in response to an instruction from the mobile terminal 104. Also, it becomes possible to scan documents by the image forming device 102 and store them in the mobile terminal 104 in response to an instruction from the mobile terminal 104.

[0095] Also, in S1002, a printer ID, which is identification information of the image forming apparatus 102, is associated with a user account ID, which is identification information of the user, and registered in the telecommuting service 103. This corresponds to the "OAO registration" shown in FIG. 7. Also, in S1002, a printer ID is associated with an application account ID and registered in the home service 105. This corresponds to the "AOA registration" shown in FIG. 7. As a result, a print job registered in the telecommuting service 103 from the client terminal 101 can be sent to the image forming apparatus 102 via the telecommuting service 103 and the home service 105 in response to an instruction from the mobile terminal 104. Details of S1002 will be described later.

[0096] <6. Overall process flow> 11 and 12, an example of a processing sequence for transmitting a print job to the image forming apparatus 102 based on a transmission instruction from a user will be described. In this processing sequence, the client terminal 101, the image forming apparatus 102, the telecommuting service 103, the mobile terminal 104, and the home service 105 work together.

[0097] 11, in S1101, the client terminal 101 performs OAO authentication to use the telecommuting service 103. During OAO authentication, the user inputs a user account ID and password to the client terminal 101. During OAO authentication, the telecommuting service 103 acquires a printer ID that corresponds to the user account ID.

[0098] In S1103, the client terminal 101 checks whether the OAO authentication has been successful, and if successful, proceeds to S1105.

[0099] In S1105, the client terminal 101 transmits a print job registration request to the telecommuting service 103. The print job and the user account ID are attached to the print job registration request.

[0100] In S1107, the telecommuting service 103 issues a job code to be assigned to the print job attached to the job registration request received in S1105.

[0101] In S1109, the telecommuting service 103 stores the print job attached to the job registration request received in S1105, the printer ID acquired in the OAO authentication in S1101, and the job code issued in S1107 in association with each other.

[0102] In S1111, the telecommuting service 103 notifies the client terminal 101 of the job code.

[0103] In S1113, the client terminal 101 displays the job code on the screen.

[0104] 12, in S1117, the user presses a start button displayed by an application running on the mobile terminal 104 (for example, the “Telework Cloud Print Service” button 2011 on the screen 2010 shown in FIG. 20).

[0105] In S1119, the mobile terminal 104 performs AOA authentication to use the home service 105. During AOA authentication, the user does not need to input an application account ID to the mobile terminal 104, and the application transmits the application account ID (see FIG. 9) stored in the mobile terminal 104 to the authentication server. Furthermore, during AOA authentication, the home service 105 obtains a printer ID from the authentication server 107.

[0106] In S1121, it is confirmed whether or not the AOA authentication has been successful, and if successful, the process proceeds to S1123.

[0107] In S1123, the mobile terminal 104 accepts input of a job code by the user. It is assumed that the user sees the job code displayed on the screen of the client terminal 101 in S1113 and inputs it into the mobile terminal 104. Steps replacing S1123 will be described in the third and fourth embodiments.

[0108] In S1125, the mobile terminal 104 requests the home service 105 to send the print job by attaching the job code accepted in S1123.

[0109] In S1127, the home service 105 transmits a print job transmission request to the telecommuting service 103. Here, the print job transmission request is accompanied by the job code received in S1125 and the printer ID acquired in the AOA authentication in S1119.

[0110] In S1129, the telecommuting service 103 verifies the job code and printer ID attached to the print job transmission request received in S1127. In this verification, the job code and printer ID saved in S1111 are used. In other words, it is confirmed that the set of job code and printer ID attached to the print job transmission request received in S1127 matches the set of job code and printer ID saved in S1109.

[0111] In S1131, it is confirmed whether or not the verification has been successful, and if successful, the process proceeds to S1133.

[0112] In S1133, the telecommuting service 103 acquires the print job saved in S1109 using the job code and printer ID attached to the job transmission request received in S1127 as keys.

[0113] In S1135, the telecommuting service 103 transmits to the home service 105 the print job acquired in S1133 and the job code and printer ID attached to the job transmission request received in S1127.

[0114] In S1137, the home service 105 transmits the print job and the job code received in S1135 to the image forming device 102 identified by the printer ID received in S1135.

[0115] In S1139, the image forming apparatus 102 executes printing based on the print job received in S1137.

[0116] In S1141, the image forming apparatus 102 sends the print job execution result together with the job code to the home service 105. The print job execution result includes result information indicating whether printing was successful or not.

[0117] In S1143, the home service 105 transfers the print job execution result to the telecommuting service 103.

[0118] In S1145, the telecommuting service 103 stores the result information received in S1143.

[0119] It is also possible to set an expiration date for the print job, and store information indicating the expiration date together with the print job in step S1109, and to check in step S1131 whether the expiration date has passed.

[0120] <7. AOA authentication on mobile devices> The processing shown in Figures 13 to 15 starts when, for example, the "Telecommuting Services" button 2011 on the screen 2010 in Figure 20(a) is pressed. In Figure 13, this pressing is indicated by pressing the Start button (S1300). Pressing the Start button is premised on the fact that the processing from S1101 to S1113 has already been executed.

[0121] 13 to 15 are executed in response to, for example, an instruction from a user via a display unit or an input device of the mobile terminal 104, or an instruction from a user received by an application installed on the mobile terminal 104. In the following description, it is assumed that the application 2000 and a browser are used to receive an instruction from a user. In this case, the browser may operate as a part of the application 2000, or may operate as an external application different from the application 2000.

[0122] In S1301, in response to pressing of the "Telecommuting Service" button 2011 on the screen 2010, the authentication control unit 304 of the mobile terminal 104 checks whether or not it has already received authentication information from the regional authentication server 107B and stored it in the storage unit 305. Specifically, it checks whether or not authentication information corresponding to the image forming apparatus 102 registered in the application 2000 is stored in the storage unit 305 of the mobile terminal 104. If the authentication information is stored in the storage unit 305 of the mobile terminal 104, the process proceeds to S1401, and if the authentication information is not stored, the process proceeds to S1302. Note that the authentication information here includes the printer ID, application account ID, application account authentication information, access information (e.g., URL, etc.) of the common authentication server 107A, and access information (e.g., URL, etc.) of the regional authentication server 107B, as shown in FIG. 9.

[0123] In S1302, the authentication control unit 304 of the mobile terminal 104 requests the printer ID of the image forming device 102 registered in the application 2000 from the image forming device management server 108 via the communication unit 303. This request includes, for example, the model name, serial number, MAC address, and area information of the image forming device 102 registered in the application 2000.

[0124] In step S1303 , the image forming apparatus management server 108 transmits the printer ID of the image forming apparatus 102 registered in the application 2000 to the mobile terminal 104 .

[0125] In S1304, the authentication control unit 304 of the mobile terminal 104 starts communication with the common authentication server 107A via the communication unit 303. Specifically, the authentication control unit 304 transmits the printer ID received in S1303 to the common authentication server 107A. Note that the access information for the common authentication server 107A may be held in advance by the application 2000, or may be acquired by the application 2000 from an external source.

[0126] In S1305, the authentication control unit 304 of the common authentication server 107A transmits to the mobile terminal 104 access information (for example, a URL such as https: / / us.oauth) of the regional authentication server 107B to be communicated with.

[0127] In S1306, the authentication control unit 304 of the mobile terminal 104 uses the access information received in S1305 to request issuance of authentication information to the regional authentication server 107B via the communication unit 303. Specifically, the mobile terminal 104 transmits the printer ID to the regional authentication server 107B, and requests issuance of the application account ID and application account authentication information described above with reference to FIG.

[0128] In S1307, the authentication control unit 304 of the regional authentication server 107B requests the image forming device management server 108 to confirm whether the printer ID received from the mobile terminal 104 is appropriate. Specifically, the request is made to confirm whether the printer ID was issued by the image forming device management server 108. In the first embodiment, it is assumed that the printer ID is appropriate.

[0129] In S1308, the image forming device management server 108 transmits a message to the regional authentication server 107B indicating that the printer ID was appropriate. Specifically, the image forming device management server 108 transmits information indicating that the printer ID received in S1307 was issued by the image forming device management server 108 to the regional authentication server 107B.

[0130] In S1309, the authentication control unit 304 of the regional authentication server 107B generates an application account ID and application account authentication information in association with the printer ID received from the mobile terminal 104, and stores them in the storage unit 305 of the regional authentication server 107B. Note that, as shown in Fig. 8, model information of the image forming device 102 ("model name", "serial number", "MAC address", and "region information") may also be stored. Therefore, it can be said that the application account ID is issued in association with the printer ID.

[0131] In S1310, the authentication control unit 304 of the authentication server 107 transmits the application account ID and the application account authentication information generated in S1309 to the mobile terminal 104.

[0132] In S1311, the authentication control unit 304 of the mobile terminal 104 stores the access information of the regional authentication server 107B received in S1305 in the storage unit 305 of the mobile terminal 104. The authentication control unit 304 of the mobile terminal 104 also stores the application account ID and application account authentication information received in S1310 in the storage unit 305 of the mobile terminal 104. Specifically, the authentication control unit 304 of the mobile terminal 104 stores the following information in the storage unit 305 of the mobile terminal 104. This information includes part of the information included in the model information of the image forming apparatus 102 selected by the application 2000, the application account ID, the application account authentication information, and the access information of the regional authentication server 107B. Here, the part of the information included in the model information is the model name, the serial number, and the region information.

[0133] In the above explanation, an application account ID and application account authentication information are issued and stored in area-specific authentication server 107B and storage unit 305 of mobile terminal 104. In this case, AOA authentication is performed using the application account ID and application account authentication information. However, this is not limited, and the application account authentication information may be omitted.

[0134] The processes from S1302 to S1311 are preparation processes for AOA authentication. These preparation processes may be performed when AOA authentication is performed for the first time, or may be performed after the image forming apparatus 102 is registered in the application 2000.

[0135] From S1311, processing continues to S1401 shown in FIG.

[0136] In S1401, the mobile terminal 104 reads out the authentication information (particularly the application account ID and the application account authentication information) stored in S1311.

[0137] In S1402, the authentication control unit 304 of the mobile terminal 104 requests the regional authentication server 107B to transmit access information with an access token. When requesting transmission of the access information with an access token, the information stored in the storage unit 305 of the mobile terminal 104 in S1311 is transmitted to the regional authentication server 107B. Here, the information stored in the storage unit 305 of the mobile terminal 104 in S1309 is the application account ID, the application account authentication information, and the identifier of the home service 105 to be accessed (access destination ID, etc.). Note that the application 2000 holds the identifier of the home service 105 in advance. Alternatively, the application 2000 may obtain the identifier of the home service 105 from outside before S1402.

[0138] In S1403, the regional authentication server 107B checks whether the application account ID and application account authentication information received from the mobile terminal 104 are appropriate. Specifically, it checks whether the received application account ID and application account authentication information match the application account ID and application account authentication information stored in S1309. Note that in the first embodiment, it is assumed that the application account ID and application account authentication information are appropriate.

[0139] In S1404, the authentication control unit 304 of the authentication server 107 transmits information for accessing the home service 105 indicated by the identifier received from the mobile terminal 104 in S1402 to the mobile terminal 104. Here, the information for accessing the home service 105 indicated by the identifier is access information with an access token (for example, a URL with an access token).

[0140] That is, the authentication control unit 304 of the regional authentication server 107B receives the identifier of the home service 105 to be accessed from the mobile terminal in S1402. Then, the authentication control unit 304 of the regional authentication server 107B generates access information with the access token by adding the access token to the access information (e.g., a URL) corresponding to the identifier, and transmits this to the mobile terminal 104. Note that the access token is stored in the regional authentication server 107B in association with the application account ID, and is later used to check the validity of the access token transmitted in S1406.

[0141] At the first access to the home service 105, the processes from S1301 to S1311 and the processes from S1401 to S1404 are executed, and then the process of S1405 is executed. As shown in FIG. 15, at the second or subsequent access, the processes from S1500 to S1502 are executed. Here, S1500 corresponds to S1300, the processes from S1502 to S1505 correspond to S1405 to S1408, and S1506 corresponds to S1410. S1501 is a step for reading out the URL with the access token stored at S1409. Note that the access token has a lifespan, and if the lifespan has expired, an error is returned to the mobile terminal 104 in response to S1502. In this case, the mobile terminal 104 re-executes the processes from S1401 to S1410.

[0142] In S1405, the authentication control unit 304 of the mobile terminal 104 uses the access information with the access token received in S1404 to access the home cloud service 105. In the first embodiment, the authentication control unit 304 of the mobile terminal 104 transmits the access token to the home service 105 to access the home service 105.

[0143] In S1406, the authentication control unit 304 of the home service 105 checks whether the access token received from the mobile terminal 104 is appropriate. Specifically, the access token received from the mobile terminal 104 in S1405 is sent to the authentication server 107, and the authentication server 107 checks whether the access token is an access token issued by the authentication server 107 and is within the validity period. In the first embodiment, the description will be given on the assumption that the access token has been confirmed to be appropriate.

[0144] In S1407, the regional authentication server 107B transmits to the home service 105 a message indicating that the access token was appropriate. Specifically, it transmits to the home service 105 information indicating that the access token received in S1406 was issued by the authentication server 107. Also, in S1407, the regional authentication server 107B transmits the printer ID to the home service 105. Note that the regional authentication server 107B associates the URL with the access token, the authentication information, and the printer ID with each other.

[0145] In S1408, the authentication control unit 304 of the home service 105 transmits to the mobile terminal 104 a screen provided by the home service 105 (for example, screen 2020 (FIG. 20(b))) and data related to the screen.

[0146] In S1410, the UI control unit 306 of the mobile terminal 104 displays a screen provided by the home service 105 (for example, screen 2020 (FIG. 20(b))) on the screen of the mobile terminal 104. At this time, the UI control unit 306 of the mobile terminal 104 uses the screen and data related to the screen received from the home service 105 in S1408.

[0147] After the screen is displayed, the process proceeds to S1123 (FIG. 12).

[0148] By using this authentication process, it is possible to determine whether or not there is a regional authentication server 107B that supports the region from which the access originates.

[0149] Specifically, in S1302, the authentication control unit 304 of the common authentication server 107A compares the region information received from the mobile terminal 104 with a target country list held by the common authentication server 107A. If the region information is included in the target country list, the authentication control unit 304 of the common authentication server 107A determines that the region indicated by the region information is a region supported by any of the region-specific authentication servers 107B, and proceeds to S1303. If the region information is not included in the target country list held by the common authentication server 107A, the authentication control unit 304 determines that the region indicated by the region information is a region not supported by any of the region-specific authentication servers 107B, and ends the process.

[0150] Therefore, according to the first embodiment, the following process may be executed prior to S1410 or S1506, which displays a screen for requesting transmission of a print job to the image forming apparatus 102. That is, when requesting a URL with an access token from the regional authentication server 107B in S1402, only predetermined information registered in the application 2000 may be sent. Here, the predetermined information is the application account ID corresponding to the image forming apparatus 102, the application account authentication information, and the identifier (access destination ID, etc.) of the home service 105 to be accessed. Furthermore, the application account ID and the application account authentication information have already been saved in the storage unit 305 of the mobile terminal 104 in S1311. As already mentioned, the application account authentication information may be omitted.

[0151] Therefore, when the user simply presses the "Telework Service" button 2011 displayed on the screen 2010 (FIG. 20(a)), authentication to the image forming device 102 is automatically performed. Then, a screen 2020 for requesting transmission of a print job to the image forming device 102 is displayed.

[0152] Furthermore, even when the client terminal 101 is used, if a process that does not require authentication of an individual user is to be executed, the AOA authentication described in the first embodiment can be used. Specifically, even when the client terminal 101 is used, if the process requires sending a print job to the image forming device 102 using a job code, the AOA authentication described in the first embodiment can be used.

[0153] Such AOA authentication can improve the usability and security of an authentication system in a process of sending a print job to the image forming device 102 using the mobile terminal 104. In addition, such AOA authentication can be realized by a combination of the application 2000, the image forming device 102, the authentication server 107, and the image forming device management server 108.

[0154] Such AOA authentication is effective when the mobile terminal 104 does not need to authenticate individual users when sending a print job to the image forming device 102 using a job code.

[0155] On the other hand, when a print job is registered or an image forming apparatus 102 is registered in the client terminal 101, each individual user is authenticated by using OAO authentication that utilizes a user account ID and a password.

[0156] By using this method, the number of operations related to authentication by the user can be reduced when a print job is sent to the image forming device 102 using the mobile terminal 104, thereby further improving the usability and security of the authentication system.

[0157] <8. Registering a print job on a client terminal> 16 and 17, an example of a process for registering a print job by a terminal such as the client terminal 101 or the mobile terminal 104 will be described. For convenience, the following will focus on a tenant of company A and describe an example of a process by the client terminal 101 when the client terminal 101 transmits a print job to the telecommuting service 103.

[0158] 16 is executed in response to, for example, instructions from a user via a display device or input device of the client terminal 101, or instructions from a user received by an application installed on the client terminal 101. In the following explanation, it is assumed that a browser is used to receive instructions from a user. Specifically, based on the URL "http: / / companyA.com" corresponding to the telecommuting service 103 that is entered in the URL input field of the browser, the top screen of a UI related to the use of the telecommuting service 103 is displayed.

[0159] 17A shows an example of the top screen 1700. The screen 1700 is a screen for accepting input of information related to user authentication.

[0160] The input area 1701 is an area for accepting input of a user account ID (user identification information) for identifying the user from the user. The input area 1702 is an area for accepting input of a password used for authenticating the user from the user.

[0161] Button 1703 is a button for receiving an instruction from the user to execute user authentication based on the user account ID entered in input area 1701 and the password entered in input area 1702. In contrast, button 1704 is a button for receiving an instruction from the user to stop using telecommuting service 103.

[0162] In S1601, the client terminal 101 accepts that a user account ID and a password are input into input fields 1701 and 1702 of a screen 1700, respectively, and that a button 1703 is pressed. Then, the client terminal 101 transmits the user account ID and the password to the telecommuting service 103. The authentication control unit 304 of the telecommuting service 103 executes a process related to OAO authentication of the user corresponding to the user account ID based on the user account ID and password transmitted from the client terminal 101. At this time, the authentication control unit 304 of the telecommuting service 103 may request the OAO authentication of the user to a predetermined authentication service. If the OAO authentication of the user is successful in the process of S1601, a screen 1710 shown in FIG. 17(b) is presented via the browser. Specifically, the client terminal 101 accesses the telecommuting service 103 to acquire data of the screen 1710, and presents the screen 1710 to the user based on the data.

[0163] 17B shows an example of a menu screen for receiving an instruction from a user to display a screen that serves as a user interface for utilizing various functions. Item 1711 is an item for receiving an instruction from a user to display a screen associated with a function related to registering a print job. Item 1712 is an item for receiving an instruction from a user to display a screen associated with a function related to checking a registered print job. Item 1713 is an item for receiving an instruction from a user to display a screen associated with a function related to checking and changing various settings.

[0164] In S1602, the client terminal 101 accepts designation of a document to be printed from the user. Specifically, when an item 1711 is designated on screen 1710 displayed in S1601, the client terminal 101 accesses the telecommuting service 103 to acquire data of a screen related to registering a print job. The client terminal 101 then presents screen 1720 to the user based on the data. The client terminal 101 then accepts designation of a document to be printed from the user via screen 1720.

[0165] A screen 1720 shown in FIG. 17(c) shows an example of a screen for receiving an instruction from a user regarding the designation of a document to be printed.

[0166] Input area 1721 is an input area for receiving, from the user, the designation of the document to be printed. The designation of the document is received, for example, by dragging and dropping the data (file, etc.) of the target document into input area 1721 using an input device such as a mouse pointer. Of course, as long as it is possible to identify the data of the target document, the method of designating the data is not limited. Hereinafter, the information input into input area 1721 will be referred to as "document-specific information."

[0167] The button 1722 is a button for receiving an instruction from the user to register a print job for printing a document identified by the document identification information. The button 1723 is a button for receiving an instruction from the user to cancel the registration of the print job.

[0168] In S1603, the client terminal 101 accepts an instruction to register a print job based on the information entered on screen 1720. Specifically, when button 1722 is pressed, the client terminal 101 transmits the information entered in input area 1721 to the telecommuting service 103. This requests the telecommuting service 103 to register the print job. S1603 corresponds to S1105 shown in Fig. 11, and the process continues from S1603 to S1107.

[0169] A screen 1730 shown in FIG. 17(d) shows an example of a screen related to the notification of the job code (S1111). That is, the screen 1730 is displayed by displaying the job code in S1113 shown in FIG. 11. The screen 1730 is transmitted from the telecommuting service 103 to the client terminal 101 in the notification of the job code in S1111 shown in FIG. 11. The transmission of the screen 1730 may be by http or by email using smtp. The issued job code is displayed on the screen 1730. In addition to the job code, the screen 1730 may also display, for example, the expiration date of the print job and the file name of the document specified via the screen 1720. As the expiration date, for example, the date and time when the time of the "expiration date setting information" in FIG. 4(b) has elapsed from the date when the process related to the registration of the print job shown in FIG. 16 (S1603) was executed is presented. As a specific example, in the example shown in Fig. 17(d), a print job is registered at 19:00 on Nov. 8, 2022. Then, 10 minutes later (the value of the deadline setting information shown in Fig. 4(b)), 19:10 on Nov. 8, 2022, is set as the expiration date of the print job.

[0170] <9. OAO authentication on client terminal> Fig. 18 is a sequence diagram showing an example of OAO authentication processing in the client terminal 101. OAO authentication is executed in S1000 before the client terminal 101 starts processing for submitting a print job to the telecommuting service 103 as shown in Fig. 11. The OAO authentication shown in Fig. 18 uses encryption and decryption of a challenge using a key pair. Also, biometric authentication in the client terminal 101 is used.

[0171] Referring to FIG. 18, first, in S1801, the client terminal 101 transmits to the authentication server 107 a user account ID, which is identification information for identifying a user.

[0172] Next, in S1802, authentication server 107 determines the authentication method. If authentication server 107 does not store a public key corresponding to the user account ID, it proceeds to S1803, and if it stores such a public key, it proceeds to S1807.

[0173] In S1807, the authentication server 107 transmits a challenge to the client terminal 101.

[0174] In S1808, the client terminal 101 accepts the input of biometric authentication information.

[0175] In S1809, the client terminal 101 accesses the private key.

[0176] In S1810, the client terminal 101 encrypts the challenge received in S1807 by signing it with the private key accessed in S1809.

[0177] In S1811, the client terminal 101 transmits the challenge signed in S1810 to the authentication server 107.

[0178] In S1812, the authentication server 107 verifies the signed challenge using the public key stored in S1806.

[0179] In S1813, the authentication server 107 transmits the verification result to the client terminal 101.

[0180] In S1814, the client terminal 101 displays a post-authentication screen.

[0181] If the authentication is successful, the print job can be registered in the telecommuting service 103 via a screen for registering a print job in the client terminal 101 .

[0182] As already explained, if a public key corresponding to the user account ID is not stored in S1802, the process proceeds to S1803, and in S1803, the authentication server 107 sends a registration instruction to the client terminal 101.

[0183] In S1804, the client terminal 101 generates a key pair of a private key and a public key, and holds the private key.

[0184] In S1805, the client terminal 101 transmits the public key to the authentication server 107.

[0185] In S1806, the authentication server 107 stores the public key.

[0186] When the process has been executed up to S1806, the process proceeds to S1807. The process from S1807 onwards is carried out in the case where the public key corresponding to the user account ID is stored in S1802.

[0187] Fig. 19 is a sequence diagram showing another example of the process of user authentication (OAO authentication) in the client terminal 101. In the OAO authentication shown in Fig. 19, encryption and decryption of a challenge using a key pair is used. Also, biometric authentication in the mobile terminal 104 is used.

[0188] 19, first, in S1901, the client terminal 101 transmits to the authentication server 107 a user account ID, which is identification information for identifying a user.

[0189] Next, in S1902, authentication server 107 determines the authentication method. If authentication server 107 does not store a public key corresponding to the user identification information, it proceeds to S1903, and if it stores such a public key, it proceeds to S1909.

[0190] In S1909, the authentication server 107 transmits an authentication request to the mobile terminal 104.

[0191] At S1910, the mobile terminal 104 obtains the challenge.

[0192] In S1911, the mobile terminal 104 accepts input of biometric authentication information.

[0193] At S1912, the mobile terminal 104 accesses the private key.

[0194] In S1913, the mobile terminal 104 encrypts the challenge acquired in S1910 by signing it with the private key accessed in S1912.

[0195] In S1914, the mobile terminal 104 sends the signed challenge to the authentication server 107.

[0196] In S1915, the authentication server 107 verifies the signed challenge using the public key stored in S1908.

[0197] In S1916, the authentication server 107 transmits the verification result to the client terminal 101.

[0198] In S1917, the client terminal 101 displays a post-authentication screen.

[0199] If the authentication is successful, the print job can be registered in the telecommuting service 103 via a screen for registering a print job in the client terminal 101 .

[0200] As already explained, if a public key corresponding to the user account ID is not stored in S1902, the process proceeds to S1903, where the authentication server 107 sends a registration prompt to the client terminal 101.

[0201] In S1904, the client terminal 101 displays a registration prompting screen.

[0202] In S1905, the mobile terminal 104 accesses a registration WEB page. Note that S1905 is executed when the user views the registration prompting screen and performs an operation on the mobile terminal 104 in response to the screen.

[0203] In S1906, the mobile terminal 104 generates a key pair of a private key and a public key, and holds the private key.

[0204] In S1907, the mobile terminal 104 transmits the public key to the authentication server 107.

[0205] In S1908, the authentication server 107 stores the public key.

[0206] When the process has been executed up to S1908, the process proceeds to S1909. The process from S1909 onwards is carried out in the case where the public key corresponding to the user account ID has been stored in S1902.

[0207] As the OAO authentication in the client terminal 101, OAO authentication using a PUSH notification, which will be described with reference to FIG. 35 in the third embodiment, may be used.

[0208] <10. Controlling whether to show or hide buttons on mobile devices> A method for controlling the display / non-display of a button in the mobile terminal 104 will be described with reference to FIGS.

[0209] A screen 2010 shown in Fig. 20(a) is a main screen displayed by the application 2000. A screen 2020 shown in Fig. 20(b) is based on image data sent from the home service 105 to the mobile terminal 104 in the above-mentioned S1408 (Fig. 14) or S1505 (Fig. 15). The screen 2020 shown in Fig. 20(b) is displayed on the screen of the mobile terminal 104 in the above-mentioned S1410 (Fig. 14) or S1506 (Fig. 15).

[0210] The icon and model name of the image forming device 102 registered in the application 2000 are displayed at the top of the screen 2010. Also arranged on the screen 2010 are a "telework cloud print service" button 2011 and a "register for home cloud print service" button 2012. Furthermore, arranged on the screen 2010 are a "print photo" button 2013, a "print document" button 2014, and a "scan" button 2015. Note that the "register for home cloud print service" button 2012 may be arranged on a separate screen not shown.

[0211] The "telecommuting cloud print service" button 2011 is a button for activating a function in which the mobile terminal 104 sends a print job transmission request in the telecommuting service 103. When the "telecommuting cloud print service" button 2011 is pressed, AOA authentication is performed. If predetermined conditions are met after the AOA authentication, this function is activated and a screen 2020 is displayed.

[0212] The “Register to home cloud print service” button 2012 is a button for further registering the image forming device 102 registered in the application 2000 to the home service 105 .

[0213] The "Print Photo" button 2013, the "Print Document" button 2014, and the "Scan" button 2015 have already been explained, so duplicate explanations will be omitted.

[0214] The screen 2020 has an input area 2021 for inputting a job code, an "OK" button 2022, and a "Cancel" button 2023 arranged thereon. The user inputs the job code in the input area 2021 in S1123 (FIG. 12) and presses the "OK" button 2022. Then, in S1125 (FIG. 12), a print job transmission request accompanied by the job code input in the input area 2021 is transmitted to the home service 105. If the user presses the "Cancel" button 2023, the transmission of the print job transmission request is cancelled in advance.

[0215] The application 2000 is basically for using the home service 105 from the mobile terminal 104. To do this, it is basically necessary to register the printer ID of the image forming device 102 registered in the application 2000 in the home service 105. For this registration, a "Register to home cloud print service" button 2012 is provided.

[0216] Furthermore, home service 105 includes a plurality of services. That is, home service 105 has a function of printing from various cloud services (Facebook, Google Drive, Dropbox, OneDrive, Box, Evernote, Google Photos, etc.), for example. Therefore, although not shown, a button for displaying a menu screen (not shown) for selecting various cloud services included in home service 105 may be provided on screen 2010, and the menu screen may be displayed when this button is pressed.

[0217] Incidentally, if the mobile terminal 104 is capable of AOA authentication, it is possible to specify the image forming device 102 to be used in the home service 105 by the printer ID associated with the application account ID used during AOA authentication. Therefore, if the mobile terminal 104 is capable of AOA authentication, it becomes unnecessary to register the printer ID of the image forming device 102 in advance in the home service 105. Therefore, it becomes unnecessary to provide the “Register for home cloud print service” button 2012 on the screen 2010.

[0218] If the mobile terminal 104 is capable of AOA authentication, the mobile terminal 104 and the image forming apparatus 102 can basically use the telecommuting service 103. Therefore, if the mobile terminal 104 is capable of AOA authentication, the "telecommuting cloud print service" button 2011 can be effectively used. Conversely, if the mobile terminal 104 is not capable of AOA authentication, there is no need to provide the "telecommuting cloud print service" button 2011.

[0219] Therefore, the display / non-display of the "telework cloud print service" button 2011 and the "register for home cloud print service" button 2012 is controlled by the method shown in FIG.

[0220] 21, when an event occurs to newly display the main screen of the application 2000 (YES in S2101), the process is executed from S2102. Note that the event occurs, for example, when the application 2000 is started so as to be executed from the start.

[0221] In S2102, the mobile terminal 104 reads the stored model information. The model information here includes, for example, model category information, region information, and AOA authentication support information, as shown in Fig. 22. The model information may additionally include information such as that shown in Fig. 6, which is not shown in Fig. 22.

[0222] The model information is acquired from the image forming device 102 during initial settings performed after installation of the image forming device 102, and is stored in the mobile terminal 104. In addition, for example, when the firmware of the image forming device 102 is updated, the model information may also be updated, so the model information stored in the mobile terminal 104 is also updated.

[0223] In S2103, the mobile terminal 104 determines whether the image forming device 102 is compatible with the home service 105 based on the model name or model category included in the model information of the image forming device 102 registered in the application 2000. For example, it is determined whether the image forming device 102 is an electrophotographic image forming device or a liquid ejection image forming device based on the model name, and if so, it is determined that the image forming device 102 is compatible with the home service 105. Alternatively, it is determined directly from the "model category information" as shown in FIG. 21 whether the image forming device 102 is an electrophotographic image forming device or a liquid ejection image forming device, and if so, it is determined that the image forming device 102 is compatible with the home service 105.

[0224] If the determination result in S2103 is NO, the process proceeds to S2104, where a setting is made to hide the “Register for home cloud print service” button 2012. Next, in S2105, a setting is made to hide the “Telework cloud print service” button 2011.

[0225] If the determination result in S2103 is YES, the process proceeds to S2106, where it is determined whether or not the image forming apparatus 102 supports AOA authentication. The determination of whether or not the image forming apparatus 102 supports AOA authentication is performed based on AOA authentication support information included in the model information.

[0226] If the determination result in S2106 is NO, the process proceeds to S2107, where a setting is made to display the “Register for home cloud print service” button 2012. Next, in S2108, a setting is made to hide the “Telework cloud print service” button 2011.

[0227] If the determination result in S2106 is YES, the process proceeds to S2109, where a setting is made to hide the “Register for home cloud print service” button 2012. Next, in S2110, a setting is made to display the “Telework cloud print service” button 2011.

[0228] In S2111 following S2105, S2108 or S2110, the main screen is drawn. In this drawing, the display / hide of each button is controlled according to the display / hide setting of the button.

[0229] When the application 2000 is updated, the criteria and the database in the application used for the determination in S2103 may change even for the same model information.

[0230] Also, the "Register for home cloud print service" button 2012 and the "Telecommuting cloud print service" button 2011 are not necessarily displayed on the same screen. For each button, the relevant steps may be executed when drawing the screen on which the button is placed. That is, for a screen on which the "Register for home cloud print service" button 2012 is placed but the "Telecommuting cloud print service" button 2011 is not placed, steps S2105, S2108, and S2110 may be omitted. Also, for a screen on which the "Register for home cloud print service" button 2012 is not placed but the "Telecommuting cloud print service" button 2011 is placed, steps S2104, S2107, and S2109 may be omitted.

[0231] <11. Processing when the "Telework Cloud Print Service" button is pressed on a mobile device> The following describes the process of enabling the print job transmission request function in the mobile terminal 104 and sending the print job transmission request when the "telework cloud print service" button 2011 is pressed on the mobile terminal 104.

[0232] 23 is executed in response to, for example, an instruction from a user via a display unit or an input device of the mobile terminal 104, or an instruction from a user accepted by an application 2000 installed in the mobile terminal 104. In the following description, it is assumed that the application 2000 and a browser are used to accept an instruction from a user.

[0233] The "Telecommuting Cloud Print Service" button (abbreviated as "Launch button" in FIG. 23) 2011 arranged in the application 2000 is pressed. As a result, in S2301, authentication related to the use of the telecommuting service 103 is executed. Specifically, AOA authentication (S1119) is performed. Note that both OAO authentication (S2601) and AOA authentication (S1119) may be performed, but this will be described in the second embodiment. When only AOA authentication is performed, the processing described with reference to FIGS. 13 to 15 is performed.

[0234] If the authentication is successful, the processes from S2302 to S2304, which have been omitted in the description with reference to Figures 13 to 15, are executed, and if a predetermined condition is satisfied, a screen 2020 for inputting a job code in S2305 is displayed on the mobile terminal 104. S2305 corresponds to S1410 shown in Figure 14 or S1506 shown in Figure 15.

[0235] In S2302, the authentication control unit 304 of the mobile terminal 104 determines whether the image forming apparatus 102 associated with the application 2000 supports a service related to a print job transmission system.

[0236] Here, what is referred to as the "print job sending system" basically refers to a linked cloud print service that performs a series of processes as shown in Figures 11 and 12. In other words, it is a linked cloud print service between a telecommuting service 103 and a home service 105. Functionally, this print job sending system sends a print job submitted by a client terminal 101 to an image forming device 102 in response to an instruction from a mobile terminal 104, and the image forming device 102 executes printing based on the print job.

[0237] An example of the method of determination in S2302 is as follows. That is, the mobile terminal 104 transmits model information of the image forming device 102 to the home service 105. Then, as a response, the mobile terminal 104 receives a list of applications, functions, or services supported by the image forming device 102 from the home service 105. Here, if a service related to a print job transmission system is included in the list received by the mobile terminal 104, the authentication control unit 304 of the mobile terminal 104 determines that the image forming device 102 supports the service related to the print job transmission system. In this case, since the determination result in S2302 is YES, the authentication control unit 304 of the mobile terminal 104 advances the process to S2303.

[0238] The mobile terminal 104 receives the list from the home service 105. If the list does not include a service related to the print job transmission system, the authentication control unit 304 of the mobile terminal 104 determines that the image forming device 102 does not support the service related to the print job transmission system. In this case, since the determination result in S2302 is NO, the authentication control unit 304 of the mobile terminal 104 skips S2303 to S2307 and advances the process to S2308.

[0239] In S2303, the authentication control unit 304 of the mobile terminal 104 checks whether or not the service related to the print job transmission system is enabled from the response received in S2302. If the service related to the print job transmission system is enabled, it is possible to use the service related to the print job transmission system. Specifically, the authentication control unit 304 of the mobile terminal 104 checks the value of a flag or the like included in the response received in S2302 indicating whether or not the service related to the print job transmission system is enabled. If the value indicates "enabled," the determination result in S2302 is YES, and the authentication control unit 304 of the mobile terminal 104 advances the process to S2305.

[0240] If the value indicates "invalid", the authentication control unit 304 of the mobile terminal 104 advances the process to S2304 since the determination result in S2302 is NO.

[0241] Here, the reasons why the service related to the print job transmission system is invalid include: The service related to the print job transmission system is set to be disabled in the home service 105. - No contract has been concluded to use the services related to the print job transmission system. etc.

[0242] Therefore, in S2304, A process for validating a service related to a print job transmission system in the home service 105 Processing to enter into a contract for using services related to the print job sending system etc. are executed.

[0243] If the validation is successful in S2304, the authentication control unit 304 of the mobile terminal 104 determines YES and proceeds to S2305, and if the validation is unsuccessful in S2304, the authentication control unit 304 determines NO and proceeds to S2308.

[0244] In S2305, the UI control unit 306 of the mobile terminal 104 presents a screen 2020 shown in Fig. 20(b) via a browser. Specifically, the mobile terminal 104 accesses the home service 105 to acquire data for the screen 2020, and presents the screen 2020 to the user based on the data.

[0245] A screen 2020 shown in FIG. 20(b) is a screen that accepts input of a job code corresponding to a desired print job from a user. An input area 2021 is an area that accepts input of a job code for identifying a print job from a user. A button 2022 is a button for accepting an instruction from a user to execute printing based on a print job based on the job code input in the input area 2021. In contrast, a button 2023 is a button for accepting an instruction from a user to cancel printing based on a print job based on the input job code.

[0246] In S2306, the print job management unit 302 of the mobile terminal 104 accepts an input of a job code corresponding to a desired print job from a user. Here, the job code input in the input area 2021 may be, for example, a job code notified in advance from the telecommuting service 103. The job code is used by the home service 105 to identify the print job. Therefore, the process related to the acceptance of the input of the job code may not necessarily be executed. As a specific example, the mobile terminal 104 may authenticate the user by accepting an input related to authentication from the user, and accept from the user a designation of a desired print job from a list of print jobs associated with the user. Alternatively, the mobile terminal 104 may authenticate the mobile terminal 104 by accepting an input related to authentication from the user, and accept from the user a designation of a desired print job from a list of print jobs associated with the mobile terminal 104. The mobile terminal 104 may authenticate the mobile terminal 104 by accepting an input related to authentication from the user, and accept from the user a designation of a desired print job from a list of print jobs associated with the mobile terminal 104.

[0247] In S2307, the print job management unit 302 of the mobile terminal 104 transmits the job code input in S2306 to the home service 105, requesting the home service 105 to transmit a print job. Specifically, when the button 2022 is pressed, the mobile terminal 104 transmits the information input in the input area 2021 to the home service 105. This requests the home service 105 to transmit a print job. Note that when the button 2023 is pressed, the information input in the input area 2021 is sent to the home service 105, and the print job identified by the job code is deleted. Specifically, the processes indicated in S2501 to S2507 are executed.

[0248] In S2308, the print job management unit 302 of the mobile terminal 104 presents the results of the series of processes to the user. Specifically, if it is determined in S2302 that the image forming apparatus 102 does not support the service related to the print job transmission system, the user is notified of this fact. Also, if the service related to the print job transmission system cannot be enabled in S2304, the user is notified of this fact. Furthermore, if the print job is normally transmitted to the image forming apparatus 102 after execution of S2307, it is also possible to present a message that the transmission has been completed normally.

[0249] S2307 corresponds to S1125 shown in FIG. 12, and thereafter, the processes from S1127 onwards are executed.

[0250] <12. Print job deletion process in response to instructions from a client terminal> The process of deleting a print job in response to an instruction from a client terminal will be described with reference to Fig. 24. The process shown in Fig. 24 is executed, for example, when button 1723 on screen 1700 is pressed. The process shown in Fig. 24 may also be executed when the expiration date shown in Fig. 4(b) has elapsed. Furthermore, the process shown in Fig. 24 may also be executed when the telecommuting service 103 receives a print job execution result indicating that printing was successful in S1143.

[0251] 24, in step S2401, in response to an instruction from a user, the client terminal 101 transmits a print job deletion request to the telecommuting service 103. The job code of the print job to be deleted is attached to this deletion request.

[0252] As a specific example, the client terminal 101 may present a screen related to a request to delete a print job to the user via a browser or the like, and accept the specification of information (e.g., a job code) related to the print job to be deleted via that screen.

[0253] As another example, the client terminal 101 may present a list of registered print jobs to the user and accept from the user a designation of a print job to be deleted from the list. In this case, the client terminal 101 may obtain information on registered print jobs from the telecommuting service 103, for example, and create the list based on the information. Also, the screen may be presented to the user when, for example, item 1712 shown on screen 1710 is designated.

[0254] In S2402, the print job management unit 302 of the telecommuting service 103 searches the storage unit 305 for print job related information (see FIG. 5A) corresponding to the print job for which the deletion request has been accepted, and proceeds to S2403. If the search fails, the process ends.

[0255] In S2403, the print job management unit 302 of the telecommuting service 103 transmits to the home service 105 a print job deletion request with the job code corresponding to the print job to be deleted attached.

[0256] In S2405, the print job management unit 302 of the home service 105 searches the storage unit 305 for print job related information (see FIG. 5B) using the job code attached to the deletion request received in S2403 as a key, and deletes the print job related information. At this time, the print job management unit 302 of the home service 105 may store information related to the target print job as history in a predetermined storage area. As a specific example, the print job management unit 302 of the home service 105 may set a flag related to the print job transmission request from the mobile terminal 104 so as not to respond to the request. In addition, for information used as history among the print job related information, a copy of the information may be stored in a predetermined storage area (for example, the storage unit 305).

[0257] In S2406, the print job management unit 302 of the home service 105 notifies the telecommuting service 103 that the deletion of the print job related information has been completed.

[0258] In S2407, the print job management unit 302 of the telecommuting service 103 deletes data corresponding to the print job specified as the deletion target. In other words, it deletes the print job related information searched for in S2402. This print job related information includes print job data corresponding to the print job as shown in FIG. 5. At this time, the print job management unit 302 of the telecommuting service 103 may store information related to the print job as a history in a predetermined storage area. As a specific example, the print job management unit 302 of the telecommuting service 103 refers to the print job related information corresponding to the print job to be deleted (see FIG. 5(a)). Then, the print job management unit 302 of the telecommuting service 103 may store a copy of the information used as a history among the referred print job related information in a predetermined storage area (for example, the storage unit 305).

[0259] <13. Processing for deleting print jobs by instructions from mobile devices> The process of deleting a print job in response to an instruction from a mobile terminal will be described with reference to FIG.

[0260] In S2501, the mobile terminal 104 transmits a print job deletion request to the home service 105 in response to an instruction from the user.

[0261] As a specific example, the mobile terminal 104 may present a screen related to a request to delete a print job to the user via a browser or the like, and accept the specification of information (e.g., a job code) related to the print job to be deleted via the screen.

[0262] As another example, the mobile terminal 104 may present a list of registered print jobs to the user and accept from the user a designation of a print job to be deleted from the list. In this case, the mobile terminal 104 may obtain information on registered print jobs from the home service 105, for example, and create the list based on the information.

[0263] In S2502, the print job management unit 302 of the home service 105 searches the storage unit 305 for print job related information (see FIG. 5B) corresponding to the print job identified by the job code attached to the deletion request. If the search fails, the process ends.

[0264] In S2503, the print job management unit 302 of the home service 105 deletes the print job related information found in S2502 (see FIG. 5B). At this time, the print job management unit 302 of the home service 105 may store information related to the target print job as history in a predetermined storage area. As a specific example, the print job management unit 302 of the home service 105 may set a flag related to the print request from the mobile terminal 104 so as not to respond to the request. In addition, for information used as history among the print job related information, a copy of the information may be stored in a predetermined storage area (for example, the storage unit 305).

[0265] In S2504, the print job management unit 302 of the home service 105 transmits to the telecommuting service 103 a print job deletion request accompanied by a job code corresponding to the print job to be deleted.

[0266] In S2505, the print job management unit 302 of the telecommuting service 103 deletes the print job related information (see FIG. 5(a)) identified by the job code attached to the print job deletion request received in S2504. At this time, the print job management unit 302 of the telecommuting service 103 may store information related to the target print job as history in a predetermined storage area. As a specific example, the print job management unit 302 of the telecommuting service 103 refers to the print job related information (see FIG. 5(a)) corresponding to the print job to be deleted. Then, the print job management unit 302 of the telecommuting service 103 may store a copy of the information used as history among the referred print job related information in a predetermined storage area (for example, the storage unit 305).

[0267] In S2506, the print job management unit 302 of the telecommuting service 103 notifies the home service 105 that the deletion of the print job has been completed.

[0268] The first embodiment uses a configuration that combines a client terminal 101, an image forming device 102, a telecommuting service 103, a mobile terminal 104, and a home service 105. According to the first embodiment, such a configuration makes it possible to improve the usability and security associated with the use of the telecommuting service 103.

[0269] <Second embodiment> The second embodiment is basically the same as the first embodiment. The second embodiment differs from the first embodiment in that the authentication performed in the mobile terminal 104 is OAO authentication and AOA authentication in the second embodiment, whereas in the first embodiment, only AOA authentication is performed.

[0270] <1. System configuration> The system configuration according to the second embodiment is similar to that shown in FIG. 1 according to the first embodiment.

[0271] <2. Overall process flow> The operations and screens of the first embodiment described in the first embodiment are basically the same in the second embodiment, so a description of the overlapping parts will be omitted.

[0272] The overall flow of the process in the first embodiment is as shown in Figures 11 and 12. In the second embodiment, the process shown in Figure 12 is replaced with the process shown in Figure 26. Therefore, the overall flow of the process in the second embodiment is as shown in Figures 11 and 26.

[0273] 12 and 26, the second embodiment is different from the first embodiment in that OAO authentication (S2601) is added before AOA authentication (S1119). Note that OAO authentication (S2601) may be added after AOA authentication (S1119).

[0274] <3. OAO authentication on mobile devices> The OAO authentication (S2601) shown in FIG. 26 will be described in detail with reference to FIG.

[0275] 27 is executed in response to, for example, an instruction from a user via a display device or an input device of the mobile terminal 104, or an instruction from a user accepted by an application installed in the mobile terminal 104. In the following description, it is assumed that the application 2000 is used to accept an instruction from a user.

[0276] Specifically, the application 2000 accesses the URL "http: / / companyA.com" corresponding to the telecommuting service 103. Then, the top screen of the UI related to the use of the telecommuting service 103 downloaded from the URL by the application 2000 is displayed.

[0277] For example, a screen 2800 shown in Fig. 28(a) is an example of the top screen. The screen 2800 is a screen for accepting input of information related to user authentication.

[0278] An input area 2801 is an area for accepting input of a user account ID for identifying the user from the user.

[0279] Button 2802 is a button for receiving an instruction from the user relating to determining the authentication method of the user based on the user account ID input in input area 2801. In contrast, button 2803 is a button for receiving an instruction from the user relating to stopping the use of telecommuting service 103.

[0280] In S2701, when a user account ID is input in an input field 2801 on a screen 2800 and a button 2802 is pressed, the mobile terminal 104 transmits the user account ID to the authentication server 107.

[0281] In S2702, the authentication control unit 304 of the authentication server 107 executes a process for determining an authentication method for a user corresponding to the user account ID based on the user account ID transmitted from the mobile terminal 104. Specifically, it is confirmed whether or not the account second authentication information of the user corresponding to the user account ID is stored in the storage unit 305 of the authentication server 107. At this time, if the account second authentication information corresponding to the user account ID is stored, the authentication process is executed by an authentication method using the account second authentication information (for example, a public key cryptography method, etc.). Also, if the account second authentication information corresponding to the user account ID is not stored, the authentication process is executed by an authentication method using the account authentication information (for example, a password method, etc.). As another method, the mobile terminal 104 of the user may be identified by a telephone number or an email address, and the authentication process may be executed by a one-time password method, or the authentication process may be executed by using both the password method and the one-time password method. Furthermore, the account second authentication information may be registered. In the second embodiment, since the account second authentication information is set, it is determined that authentication should be performed using an authentication method using the account second authentication information (for example, public key cryptography, etc.).

[0282] In S2703, the authentication control unit 304 of the authentication server 107 transmits authentication string data (for example, a challenge) to the mobile terminal 104.

[0283] In S2704, in response to receiving the challenge in S2703, the UI control unit 306 of the mobile terminal 104 presents a screen 2810 shown in Fig. 28(b) and enters a state in which the UI control unit 306 is ready to accept input of information related to authentication by the user. The screen 2810 is displayed on the mobile terminal 104 via the application 2000, for example.

[0284] 28(b) is a screen for accepting input of information related to user authentication. The screen 2810 indicates that biometric authentication (for example, fingerprint authentication or face authentication) is required for the user. The biometric authentication is required when accessing highly confidential information in the mobile terminal 104, and in the second embodiment, is required to access the user's private key stored in the storage unit 305 of the mobile terminal 104.

[0285] In S2705, if the biometric authentication by the user is successful, the authentication control unit 304 of the mobile terminal 104 accesses the private key stored in the storage unit 305 of the mobile terminal 104.

[0286] In S2706, the authentication control unit 304 of the mobile terminal 104 signs the authentication string data received from the authentication server 107 using the private key stored in the storage unit 305 of the mobile terminal 104 accessed in S2705.

[0287] In S2707, the authentication control unit 304 of the mobile terminal 104 transmits to the authentication server 107 the authentication string data (for example, the signed challenge) signed in S2706.

[0288] In S2708, the authentication control unit 304 of the authentication server 107 verifies the authentication string data (for example, a signed challenge) received from the mobile terminal 104 using the public key. The public key used here is stored in the storage unit 305 of the authentication server 107 so as to correspond to the user account ID, as shown in FIG. 29. Specifically, if the received authentication string data (for example, a signed challenge) can be decrypted using the public key, it is determined that the authentication has been successful. Similarly, if the received authentication string data (for example, a signed challenge) cannot be decrypted using the public key, it is determined that the authentication has failed. At this time, the authentication control unit 304 of the authentication server 107 may request authentication of the user from a predetermined authentication service.

[0289] In S2709, in response to the authentication string data (e.g., the signed challenge) being verified in S2708, the authentication control unit 304 of the authentication server 107 transmits an authentication result to the mobile terminal 104. Note that in the second embodiment, it is assumed that the authentication string data (e.g., the signed challenge) is successfully verified and the user is successfully authenticated.

[0290] In S2710, the UI control unit 306 of the mobile terminal 104 presents a screen 2020 shown in FIG. 20(b) via the application 2000. Specifically, the mobile terminal 104 accesses the telecommuting service 103 to acquire data for the screen 2020, and presents the screen 2020 to the user based on the data. Note that in the second embodiment, the screen 2020 is presented as a screen when the verification of the authentication string data (e.g., a signed challenge) is successful, but when the verification of the authentication string data (e.g., a signed challenge) fails, a screen 2800 is presented. In this case, the screen 2800 is presented including a message indicating that authentication has failed and therefore authentication is required again.

[0291] The authentication server that performs the OAO authentication may store the printer ID in association with the user account ID. That is, for example, the authentication server may hold information in which the application account ID and application account authentication information in the information shown in FIG. 8 are replaced with a user account ID and user account authentication information. Then, for the OAO authentication, a process similar to the process related to the AOA authentication shown in FIG. 13 to FIG. 15 may be performed. Then, in that process, the application account ID and application account authentication information included in the authentication information may be replaced with a user account ID and user account authentication information. In this way, even if the AOA authentication (S1119) in the mobile terminal 104 is omitted from the process shown in FIG. 26, the printer ID can be obtained by using the user account ID used in the OAO authentication as a key. Therefore, OAO authentication (S2601) may be used instead of the AOA authentication (S1119).

[0292] In the above, an example has been described in which a user inputs a user account ID into input field 2801 provided on screen 2800 shown in Fig. 28(a), but this is not limiting. For example, the telecommuting service 103 may send a push notification of the user account ID to the mobile terminal 104, and the screen 2800 may be displayed with the user account ID input into input field 2801. Pressing of button 2802 may also be automated, and display of screen 2800 may be omitted. This can save the user the trouble of inputting a user account ID.

[0293] <Third embodiment> The third embodiment is basically the same as the first embodiment. In the first embodiment, the user inputs a job code to the mobile terminal 104. In contrast, in the third embodiment, the job code is notified by push from the telecommuting service 103 to the mobile terminal 104. Therefore, in the third embodiment, the user does not need to input the job code to the mobile terminal 104.

[0294] <1. System configuration> The system configuration according to the third embodiment is shown in Fig. 30. As is clear from a comparison of Fig. 30 with Fig. 1 showing the system configuration according to the first embodiment, the system configuration of the third embodiment is constructed by adding a push notification server 106 to the system configuration of the first embodiment. As will be described later, the telecommuting service 103 pushes a job code to the mobile terminal 104 via the push notification server 106.

[0295] <2. Overall process flow> The operations and screens of the first embodiment are basically the same as those of the third embodiment, so duplicated explanations will be omitted.

[0296] <3. Registration process for push notifications> The print job management unit 302 of the push notification server 106 acquires information related to push notification delivery from another device (for example, the telecommuting service 103) and stores the information in a predetermined storage area. As shown in FIG. 31, the information includes user identification information and mobile terminal identification information. In the example shown in FIG. 31, the user's email address is used as the user identification information, and the device token of the mobile terminal 104 is used as the mobile terminal identification information. The device token here is used as identification information of the notification destination device in the push notification service. Examples of the push notification service include the Apple push notification service and Firebase cloud messaging.

[0297] The user identification information is not particularly limited as long as it is possible to identify the user, and for example, an identifier such as a user account ID may be set. The type of information set as the mobile terminal identification information is not particularly limited as long as it is possible to identify the user's device, and for example, an identifier such as a device ID may be set. The mobile terminal identification information may be associated with an application used when issuing the identification information of the mobile terminal. In this case, the mobile terminal identification information is different for each application installed in the mobile terminal 104. The device identification information shown in FIG. 31 may be issued by the application 2000 installed in the mobile terminal 104, for example, and may be information associated with the application 2000. A plurality of mobile terminal identification information may be set for one user. In that case, each mobile terminal identification information is assigned to each mobile terminal 104 owned by the user.

[0298] The print job management unit 302 of the push notification server 106 receives a push notification delivery instruction from the telecommuting service 103, and transmits a push notification to the mobile terminal 104 in accordance with the instruction. The push notification includes, for example, display message information, operation information, and associated information, as shown in FIG.

[0299] The "display message information" is information about a message to be displayed on the mobile terminal 104 when the mobile terminal 104 receives a push notification, and includes, for example, a code for displaying a message to be notified to the user. In the example shown in Fig. 32, "A print job has been registered. Do you want to print? Job code: 850203" is set as the display message information.

[0300] The "operation information" is information about an operation to be executed by the mobile terminal 104 when it receives a push notification, and for example, information about an operation executable by an application associated with the push notification may be set. In the example shown in FIG. 32, "Release:PrintJob" is set as the operation information. In this example, the operation information specifies that the mobile terminal 104 performs an operation to send a print job transmission request to the home service 105 when it receives a push notification. Note that the type of information set as the operation information may be any type that is capable of identifying an operation executable by an application associated with the push notification. Therefore, for example, an identifier such as an operation ID may be set as the operation information.

[0301] The "associated information" is information that the mobile terminal 104 can refer to when the mobile terminal 104 executes the operation set in the "operation information". For example, information that an application associated with a push notification refers to when executing the operation set in the "operation information" may be set in the "associated information". In the example shown in FIG. 32, "JobCode:850203" is set as the associated information. In this example, the associated information specifies that "850203" should be attached as a job code to the print job transmission request.

[0302] The communication unit 303 of the push notification server 106 transmits and receives various data to and from other devices (e.g., the telecommuting service 103, the mobile terminal 104, etc.). For example, the communication unit 303 of the push notification server 106 may receive user identification information and mobile terminal identification information from the telecommuting service 103. The communication unit 303 of the push notification server 106 may also receive a push notification delivery instruction from the telecommuting service 103, and transmit a push notification to the mobile terminal 104 in response to the instruction.

[0303] The authentication control unit 304 of the push notification server 106 executes various processes related to authentication for communicating with other devices. The authentication control unit 304 of the push notification server 106 may store information about a user received in response to an instruction from the telecommuting service 103 in a predetermined storage area (for example, the storage unit 305). As another example, the authentication control unit 304 of the push notification server 106 may manage authentication information by cooperating with an external authentication service.

[0304] The storage unit 305 of the push notification server 106 stores various data. For example, the storage unit 305 of the push notification server 106 may store various data in response to a request from the print job management unit 302 or the authentication control unit 304.

[0305] In response to a request from an administrator, the UI control unit 306 of the push notification server 106 executes processing related to receiving user identification information and mobile terminal identification information, and outputting a UI for realizing the presentation of a push notification to a user. As a specific example, the UI control unit 306 of the push notification server 106 may generate a screen for managing push notification delivery in response to a request from a management terminal (not shown). Then, the UI control unit 306 of the push notification server 106 may transmit the screen (or data related to the output of the screen) to the management terminal via the communication unit 303. As a result, the screen generated by the UI control unit 306 of the push notification server 106 is presented to the administrator via the management terminal.

[0306] An example of a registration process for push notification will be described with reference to Fig. 33 and Fig. 34. Fig. 33 shows a telecommuting service 103, a push notification server 106, a mobile terminal 104, and a client terminal 101. Among these, an input side service device, which is an information processing device equipped with a server for providing the telecommuting service 103, functions as a notification source device, and the mobile terminal 104 functions as a notification destination terminal. The telecommuting cloud print service 103 requests the push notification server 106 to send a push notification via the input side service device, which is the notification source device. In response to this request, the push notification server 106 transmits a push notification to the mobile terminal 104, which is the notification destination terminal. In preparation for this, data as shown in Fig. 31 is registered in the push notification server 106 by the method shown in Fig. 33. The client terminal 101 functions as an intermediary terminal during this registration. During this registration, the telecommuting service 103, the push notification server 106, the mobile terminal 104, and the client terminal 101 shown in Fig. 33 function as a registration system.

[0307] Referring to FIG. 33, in S3301, the print job management unit 302 of the telecommuting service 103 requests the push notification server 106 to transmit information indicating whether the device token of the mobile terminal 104 of the user who registered the print job has been registered.

[0308] In S3302, the print job management unit 302 of the push notification server 106 transmits, as a response to the request in S3301, information indicating whether the device token of the user's mobile terminal 104 has been registered to the telecommuting service 103.

[0309] As another example of a method for determining whether or not a push notification can be sent to the mobile terminal 104 of the user who registered the print job, the telecommuting service 103 may store a setting value for the determination. In this case, the telecommuting service 103 can determine whether or not a push notification can be sent to the mobile terminal 104 of the user without communicating with the push notification server 106.

[0310] In S3303, the print job management unit 302 of the telecommuting service 103 determines whether or not a push notification can be delivered to the user's mobile terminal 104. To make this determination, the print job management unit 302 of the telecommuting service 103 uses information indicating whether or not the device token of the user's mobile terminal 104 received in S3302 has been registered. If it is determined that the device token has not been registered, the process proceeds to S3304.

[0311] In S3304, the telecommuting service 103 transmits a push notification registration code display request to the client terminal 101. The push notification registration code display request includes the job code assigned to the print job registered by the user and the push notification registration code.

[0312] In S3305, the UI control unit 306 of the client terminal 101 displays a screen 3400 shown in Fig. 34. Although not shown, specifically, the client terminal 101 accesses the telecommuting service 103 to acquire basic data for the screen 3400. The client terminal 101 then presents the screen 3400 to the user based on the basic data and the job code and push notification registration code received in S3304. However, in S3304, the telecommuting service 103 may also transmit the basic data to the client terminal 101. In that case, in S3305, the client terminal 101 presents the screen 3400 to the user based on the basic data, job code, and push notification registration code received in S3304.

[0313] A screen 3400 shown in FIG. 34 shows an example of a screen related to notification of a job code, and is presented to a user by the client terminal 101 in S3305. In addition to the contents of the screen 1730 shown in FIG. 17(d), the screen 3400 presents a QR code (registered trademark) 3401 with a push notification registration code embedded therein. The screen 3400 may be presented, for example, via a medium such as email. That is, an email may be sent to the user's email address, and the screen 3400 may be included in the email body. Note that the screen 3400 may be displayed even if the print job management unit 302 of the telecommuting service 103 determines in S3303 that a device token for push notification delivery has been registered. In this way, it is possible to register a terminal other than the registered mobile terminal 104 as a mobile terminal to which push notification is to be delivered.

[0314] It should be noted that if registration for push notification is performed independently in advance, there is no need to transmit the job code in S3304, and the screen shown in FIG. 34 does not include information regarding the job code.

[0315] In S3306, the mobile terminal 104 reads the QR code (registered trademark) 3401 included in the screen 3400 displayed on the display unit of the client terminal 101 using the imaging device 208 of the mobile terminal 104. The mobile terminal 104 extracts the push notification registration code embedded in the QR code (registered trademark) 3401 and starts the application 2000. Specifically, the push notification registration code includes a URL scheme for identifying and starting the application 2000, and the mobile terminal 104 that reads this URL scheme starts the application 2000. The URL scheme also includes a character string for executing a push notification registration function, and the push notification registration function can be executed together with the start of the application 2000. Note that after reading the push notification registration code, the mobile terminal 104 may start the application 2000 via a browser instead of directly starting the application 2000. In this case, the push notification registration code includes the URL of a page to be accessed by the browser. The browser may display an explanation regarding push notification registration and include a URL link to an application store for downloading the application 2000. Such processing is effective in cases where the application 2000 is not installed on the mobile terminal 104. Note that the browser may include a URL scheme for launching the application 2000.

[0316] In S3307, the mobile terminal 104 executes a push notification registration function. Specifically, the print job management unit 302 of the mobile terminal 104 acquires a device token, which is a unique identifier for uniquely identifying the mobile terminal 104. Then, a registration request with the device token attached is sent to the telecommuting service 103. The device token can also be acquired by the communication unit 303 of the mobile terminal 104 communicating with a push notification service (not shown). As another example, if a valid device token has already been stored in the storage unit 305 of the mobile terminal 104, the device token can also be used. Note that when S3307 is executed, S1000 can also be executed as authentication processing for the telecommuting service 103.

[0317] In response to the registration request received in S3307, the telecommuting service 103 transmits a registration request to the push notification server 106 in S3308. The registration request transmitted in S3308 includes the user's email address and the device token attached to the registration request received in S3308.

[0318] In S3309, the print job management unit 302 of the push notification server 106 associates the email address and the device token attached to the registration request received in S3308 with each other, and stores them in the storage unit 305 of the push notification server 106. This completes pre-registration for push notification.

[0319] The registration process shown in FIG. 33 may be performed before a push notification is actually performed, or may be performed when the first push notification is performed, as described below.

[0320] <4. Push notification of job code to mobile device> A case will be described where the process from S3301 in Fig. 33 is started every time a job code is push-notified to the mobile terminal 104. In this case, when the first push notification is made, all the processes shown in Fig. 33 are executed before proceeding to the process shown in Fig. 35. Also, when the second or subsequent push notification is made, the processes from S3301 to S3303 shown in Fig. 33 are executed before proceeding to the process shown in Fig. 35. However, when it is determined in S3303 that push notification delivery is possible, information relating to this is stored in a flag, and thereafter, S3301 and S3302 may be omitted.

[0321] 35, in S3501, the print job management unit 302 of the telecommuting service 103 sends a push notification request to the push notification server 106. The push notification request is accompanied by information to be included in the push notification and user identification information for identifying the user who registered the print job. The "information to be included in the push notification" is the "display message information," "operation information," and "accompanying information" described with reference to FIG. 32. The "user identification information" is, for example, the user's email address. Note that the job code to be included in the "display message information" and the job code to be sent as the "accompanying information" were generated by the telecommuting service 103 in S1107 (FIG. 11).

[0322] In S3502, the print job management unit 302 of the push notification server 106 searches the information stored in the storage unit 305 of the push notification server 106 for a device token associated with the email address received in S3501.

[0323] In S3503, the print job management unit 302 of the push notification server 106 uses the device token searched for in S3502 to send a push notification to the mobile terminal 104. Therefore, by having the push notification server 106 intervene between the telecommuting service 103 and the mobile terminal 104, the job code is notified from the telecommuting service 103 to the mobile terminal 104. The push notification includes, for example, "display message information," "operation information," and "accompanying information" shown in Fig. 32. Note that if multiple device tokens are detected in S3502, that is, if multiple mobile terminals are associated with the user, the push notification may be sent to all of the searched mobile terminals.

[0324] In S3504, the UI control unit 306 of the mobile terminal 104 displays the "display message information" included in the received push notification on the screen of the mobile terminal 104, and becomes ready to accept a press operation on the message.

[0325] In S3505, in response to pressing the push notification button in S3504, the print job management unit 302 of the mobile terminal 104 starts the application 2000 associated with the push notification and executes the process indicated by the “operation information” included in the push notification. In other words, the print job transmission request including the job code is transmitted to the home service 105.

[0326] A screen 3600 shown in Fig. 36 illustrates an example of a screen that the mobile terminal 104 displays on the display unit in response to a push notification. This screen is displayed in S3504. The screen 3600 includes display message information included in the push notification received in S3503 in a display area 3601. Fig. 36 illustrates an example in which a message "A print job has been registered. Do you want to print? Job code: 850203", which is included as display message information in the push notification, is displayed in the display area 3601. When the display area 3601 of the screen 3600 is pressed by the user, the print job management unit 302 of the mobile terminal 104 starts the application 2000 associated with the push notification.

[0327] After starting the application 2000, the print job management unit 302 of the mobile terminal 104 executes the operation indicated by the "operation information" included in the push notification received in S3503. As described above with reference to FIG. 32, in the third embodiment, "ReleasePrintJob" is included as the operation information. Therefore, the print job management unit 302 of the mobile terminal 104 executes the operation related to sending a print job transmission request to the home service 105, which is the operation associated with the operation information "ReleasePrintJob". Specifically, the process of S2305 to S2307 and S2308 described above with reference to FIG. 23 is executed.

[0328] As described above, the push notification registration function may be executed when a print job is registered in the telecommuting service 103, but the timing for executing the push notification registration function is not limited to this. For example, in response to pressing the "telecommuting cloud print service" button 2011 in FIG. 20, a menu related to the telecommuting service 103 is displayed. It is also possible to allow the user to select a menu related to "push notification registration" from the displayed menu. In this case, in response to the selection of the menu related to "push notification registration", the mobile terminal 104 executes the process shown in FIG. 33.

[0329] In this way, by using push notification, it is possible to further improve the usability and security of the process of sending a print job to the image forming apparatus 102 using the mobile terminal 104.

[0330] <5. Request sending process by mobile device when screen is tapped due to push notification> Further improvements in usability and security are required for the process of transmitting a print job to the image forming apparatus 102 using the mobile terminal 104. In the third embodiment, a method for further improving the usability and security of the process of transmitting a print job to the image forming apparatus 102 using the mobile terminal 104 by using a push notification will be described with reference to Fig. 37 .

[0331] 37, an example of a request sending process by the mobile terminal 104 when a screen in response to a push notification is tapped on the mobile terminal 104 will be described. That is, an example of a process in a state in which the mobile terminal 104 has received a push notification will be described. Specifically, an example of a process after the process of S3504 is completed will be described.

[0332] When the push notification received in S3503 is pressed in S3504, in S3701, the print job management unit 302 of the mobile terminal 104 starts the application 2000 associated with the push notification. Then, the application 2000 processes the information included in the notification. In S3702, using the job code indicated by the "accompanying information" included in the push notification, it is determined whether or not the "print job transmission function" that is the processing indicated by the "operation information" exists. Here, if the information corresponding to the "print job transmission function" does not exist, since the notification is for performing an operation other than the print job transmission, this operation ends, and the desired operation is performed by another determination process. On the other hand, if the "print job transmission function" exists, in S3703, the UI control unit 306 of the mobile terminal 104 presents the screen 2020 shown in FIG. 20(b) via the started application 2000. Specifically, the mobile terminal 104 accesses the home service 105 to acquire data of the screen 2020, and presents the screen 2020 to the user based on the data.

[0333] In S3704, the print job management unit 302 of the mobile terminal 104 determines whether or not information related to the job code is present from the "accompanying information" included in the push notification pressed in S3504. If it is determined in S3704 that information related to the job code is not present, in S3705 the application accepts manual input of the job code on the screen 2020. Here, a dialogue or the like may be additionally displayed to prompt the user to input the job code. On the other hand, if information related to the job code is included in the "accompanying information" included in the push notification, the job code is obtained and the process proceeds to S3706. In the third embodiment, one major feature is that it is determined whether information related to the "print job transmission function" or "job code" is included in the push notification, and either the process of S3705 or the process of S3706 is selected.

[0334] In S3706, the print job management unit 302 of the mobile terminal 104 inputs the job code acquired in S3703 into the input field 2021.

[0335] In S3707, the print job management unit 302 of the mobile terminal 104 attaches the job code whose input was accepted in S3705 or S3706 and sends a print job transmission request to the home service 105. Specifically, when button 2022 is pressed, the mobile terminal 104 attaches the job code entered in input field 2021 and sends the print job transmission request to the home service 105. Note that when button 2023 is pressed, a request for deleting the print job is sent to the home service 105, attaching the job code entered in input field 2021. As a result, the print job identified by the job code is deleted.

[0336] S3707 corresponds to S1125 shown in FIG. 12, and the processes from S1127 onwards are executed thereafter. Although not described here, processes corresponding to the processes from S2301 to S2304 shown in FIG. 23 may be executed between S3701 and S3702. Similarly, processes corresponding to S2308 may be executed after S3707, and the results of the process may be presented to the user. In the third embodiment, an application is started in S3701, and a screen transition on the application is performed in S3703, etc., but it is also possible to execute all processes in the background so that the user does not see them. In such a case, the user may be notified of the completion of the process or an error by means of another notification or toast output.

[0337] In this way, by using the push notification, it is possible to omit the user's input operation of the job code, and it is possible to further improve the usability and security of the process of transmitting a print job to the image forming apparatus 102 using the mobile terminal 104.

[0338] <6. OAO authentication on client terminal> 11, it has been described that OAO authentication is performed in order for the client terminal 101 to log in to the telecommuting service 103 before submitting a print job from the client terminal 101 to the telecommuting service 103. Details of OAO authentication will be described below with reference to FIG.

[0339] In S3801, the client terminal 101 displays a screen 2800 shown in Fig. 28. When the user inputs a user account ID in an input field 2801 and presses a button 2802, the client terminal 101 transmits the user account ID to the authentication server 107 in S3801.

[0340] In S3802, the authentication control unit 304 of the authentication server 107 executes a process for determining an authentication method for a user corresponding to the user account ID based on the user account ID transmitted from the client terminal 101. Specifically, it is confirmed whether or not the account second authentication information (for example, the public key shown in FIG. 29) of the user corresponding to the user account ID is stored in the storage unit 305 of the authentication server 107. At this time, if the account second authentication information corresponding to the user account ID is stored, the process proceeds to S3809, and the authentication process is executed by an authentication method using the account second authentication information (for example, a public key cryptography method, etc.). If the account second authentication information corresponding to the user account ID is not stored, the process proceeds to S3803, and the registration process of the account second authentication information is executed. Note that, if the account second authentication information is not used, the authentication process may be executed by an authentication method using the account authentication information (for example, a password method, etc.). As another method, the user's mobile terminal 104 may be identified by a telephone number or email address, and the authentication process may be performed using a one-time password method, or the authentication process may be performed using a combination of the password method and the one-time password method.

[0341] In S3803, the authentication control unit 304 of the authentication server 107 requests the push notification server 106 to deliver a notification to the user's mobile terminal 104, which induces the user to register second authentication information for the account. User identification information such as an email address may be attached to the request in order to identify the user's mobile terminal 104. The authentication control unit 304 of the authentication server 107 also cooperates with the telecommuting service 103 as necessary. For example, the authentication server 107 may request the push notification server 106 to deliver a notification to induce the user to register second authentication information for the account, via the telecommuting service 103. Note that, if information about the user is not stored in the storage unit 305 of the push notification server 106, the user's mobile terminal 104 may be identified by authentication using a one-time password method using a telephone number or an email address. Then, the mobile terminal 104 may be induced to register second authentication information for the account.

[0342] In S3804, the print job management unit 302 of the push notification server 106 transmits a notification to the user's mobile terminal 104 to induce registration of the second authentication information of the account. Specifically, the print job management unit 302 identifies the mobile terminal 104 by mobile terminal identification information such as a device token associated with the user account ID (or user identification information such as an email address) received from the authentication server 107 (or the telecommuting service 103). Then, a push notification to induce registration of the second authentication information of the account is delivered to the mobile terminal 104. Examples of information included in the push notification at that time include display message information "You can generate a key and use a more secure authentication method" and operation information "MakeKey". Note that authentication string data (e.g., a challenge, etc.) may be included as accompanying information of the delivered push notification.

[0343] In S3805, the authentication control unit 304 of the mobile terminal 104 generates a key pair of a private key and a public key in response to receiving the notification inviting the user to register second authentication information for the account. If authentication string data (e.g., a challenge) is included as information accompanying the received push notification, the authentication string data is signed using the generated private key.

[0344] In S3806, the authentication control unit 304 of the mobile terminal 104 transmits the public key generated in S3805 to the authentication server 107. At this time, if there is signed authentication string data (for example, a signed challenge, etc.) in S3805, the signed authentication string data may also be transmitted to the authentication server 107.

[0345] In S3807, the mobile terminal 104 stores the private key generated in S3805.

[0346] In S3808, authentication control unit 304 of authentication server 107 associates the public key received in S3806 with the user account ID received in S3801 and stores it in storage unit 305 of authentication server 107. At this time, if signed authentication string data has also been received in S3806, the signed authentication string data may be verified using the received public key, and the public key may be stored in storage unit 305 of authentication server 107 only if the verification is successful.

[0347] In S3809, the authentication control unit 304 of the authentication server 107 requests the push notification server 106 to deliver a notification inviting authentication using the account second authentication information to the user's mobile terminal 104. At this time, the authentication control unit 304 of the authentication server 107 transmits authentication string data (e.g., a challenge, etc.) to the push notification server 106. The authentication control unit 304 of the authentication server 107 cooperates with the telecommuting service 103 as necessary. For example, the authentication server 107 may request the push notification server 106 to deliver a notification inviting authentication using the account second authentication information via the telecommuting service 103. If information about the user is not stored in the storage unit 305 of the push notification server 106, the user's mobile terminal 104 may be identified by authentication using a one-time password method using a telephone number or an email address. Then, the mobile terminal 104 may be induced to authenticate using the account second authentication information.

[0348] In S3810, the print job management unit 302 of the push notification server 106 transmits a push notification including authentication string data (e.g., a challenge) as accompanying information to the mobile terminal 104. Specifically, the print job management unit 302 identifies the mobile terminal by mobile terminal identification information such as a device token associated with a user account ID (or user identification information such as an email address) received from the authentication server 107 (or the telecommuting service 103). Then, a push notification is delivered to the mobile terminal 104 to induce authentication using the account second authentication information. Examples of information included in the push notification at this time include display message information "Authenticate using a key?" and operation information "OauthByKey".

[0349] In S3811, in response to receiving the notification inviting authentication using the account second authentication information, the authentication control unit 304 of the mobile terminal 104 acquires authentication string data (for example, a challenge) from the associated information of the notification.

[0350] In S3812, in response to receiving the challenge in S3811, the UI control unit 306 of the mobile terminal 104 presents a screen 2810 shown in Fig. 28(b) and enters a state in which the UI control unit 306 is ready to accept input of information related to authentication by the user. This screen 2810 is displayed on the mobile terminal 104 via, for example, the application 2000.

[0351] 28(b) is a screen for accepting input of information related to user authentication. The screen 2810 indicates that biometric authentication (e.g., fingerprint authentication, face authentication, etc.) is required for the user. The biometric authentication is required when accessing highly confidential information in the mobile terminal 104, and in the third embodiment, is required to access the user's private key stored in the storage unit 305 of the mobile terminal 104.

[0352] In S3813 , if the biometric authentication by the user is successful, the authentication control unit 304 of the mobile terminal 104 accesses the private key stored in the storage unit 305 of the mobile terminal 104 .

[0353] In S3814 , the authentication control unit 304 of the mobile terminal 104 signs the authentication string data received from the authentication server 107 by using the private key stored in the storage unit 305 of the mobile terminal 104 .

[0354] In S3815, the authentication control unit 304 of the mobile terminal 104 transmits to the authentication server 107 the authentication string data (for example, the signed challenge) signed in S3814.

[0355] In S3816, the authentication control unit 304 of the authentication server 107 verifies the authentication string data (e.g., a signed challenge) received from the mobile terminal 104 by using a public key corresponding to the user name stored in the storage unit 305 of the authentication server 107. Specifically, if the received authentication string data (e.g., a signed challenge) can be decrypted using the public key, it is determined that the authentication is successful. Similarly, if the received authentication string data (e.g., a signed challenge) cannot be decrypted using the public key, it is determined that the authentication is unsuccessful. At this time, the authentication control unit 304 of the authentication server 107 may request the authentication of the user from a predetermined authentication service.

[0356] In S3817, in response to the authentication string data (e.g., the signed challenge) being verified in S3816, the authentication control unit 304 of the authentication server 107 transmits an authentication result to the mobile terminal 104. Note that in the third embodiment, it is assumed that the authentication string data (e.g., the signed challenge) is successfully verified and the user is successfully authenticated.

[0357] In S3818, the UI control unit 306 of the mobile terminal 104 presents a screen 1720 shown in Fig. 17(c) via the application 2000. Specifically, the mobile terminal 104 accesses the telecommuting service 103 to acquire data for the screen 1720, and presents the screen 1720 to the user based on the data. Note that in the third embodiment, the screen 1720 is presented as a screen when the verification of the authentication string data (e.g., a signed challenge) is successful, but when the verification of the authentication string data (e.g., a signed challenge) fails, a screen 2800 is presented. In this case, the screen 2800 is presented including a message indicating that authentication has failed and therefore authentication is required again.

[0358] <7.Other> In the third embodiment, only AOA authentication (S1119) may be performed in the mobile terminal 104 as in the first embodiment, or both OAO authentication (S2601) and AOA authentication (S1119) may be performed as in the second embodiment. Also, only OAO authentication (S2601) may be performed in the mobile terminal 104.

[0359] According to the third embodiment, it is possible to achieve further improvements in usability and security in the process of registering a print job using the client terminal 101 and sending the print job to the image forming apparatus 102 using the mobile terminal 104.

[0360] <Fourth embodiment> The fourth embodiment is basically the same as the first embodiment. In the first embodiment, the user inputs a job code into the mobile terminal 104. In contrast, in the fourth embodiment, the client terminal 101 displays a QR code (registered trademark) in which the job code is embedded. Then, the mobile terminal 104 reads the QR code (registered trademark) to obtain the job code. Therefore, in the fourth embodiment, the user does not need to input a job code into the mobile terminal 104.

[0361] <1. System configuration> The system configuration according to the fourth embodiment is similar to that shown in FIG. 1 according to the first embodiment.

[0362] <2. Overall process flow> The operations and screens of the first embodiment are basically the same as those of the fourth embodiment, so the explanation of the overlapping parts will be omitted. In particular, the process up to registering a print job in the telecommuting service 103 by the client terminal 101 is the same as that of the first embodiment, so the overlapping explanation of that process will be omitted.

[0363] <3. Overall flow of processing related to QR Code (registered trademark)> An example of the processing of the print job transmission system according to the fourth embodiment will be described with reference to Fig. 39 to Fig. 41. In particular, the processing after the print job is registered in the telecommuting service 103 by the client terminal 101 will be described.

[0364] 39, in S3901, the telecommuting service 103 sends data (job code, expiration date, and name of the file to be printed by the print job) for displaying a screen 4000 as shown in Fig. 40 to the client terminal 101. Then, in S3902, the client terminal 101 displays the screen 4000 on the display unit. Note that S3901 is executed at the same timing as S1111 or around the same time, after S1107 shown in Fig. 11 is executed.

[0365] 40, a screen 4000 includes a job code expressed as a character string, an expiration date, the name of the file to be printed by the print job, and a QR code (registered trademark) 4001. Compared to Fig. 17(d), a QR code (registered trademark) 4001 has been added. By looking at screen 4000, the user can know that a print job for a document identified by the file name has been registered.

[0366] In S3902, the client terminal 101 may display the screen 4000 shown in FIG. 40 in the same manner as when displaying the screen 3400 shown in FIG. 34. That is, the client terminal 101 may display the screen 4000 as follows. The client terminal 101 accesses the telecommuting service 103 to acquire basic data for the screen 4000. The client terminal 101 then presents the screen 4000 to the user based on the basic data, the job code, the expiration date, and the name of the file to be printed by the print job received in S3901. However, in S3901, the telecommuting service 103 may also transmit basic data for screen display to the client terminal 101. In that case, in S3902, the client terminal 101 presents the screen 4000 to the user based on the basic data, the job code, the expiration date, and the name of the file to be printed by the print job received in S3901.

[0367] The QR code (registered trademark) 4001 has embedded therein information for causing the mobile terminal 104 to execute a process for requesting the telecommuting service 103 to transmit a print job specified by the job code to the image forming apparatus 102. Hereinafter, this information will be referred to as "transmission request information."

[0368] Although the transmission request information is displayed in the form of a QR code (registered trademark) 4001 on screen 4000, it may be displayed in another format, such as a barcode, as long as the format is capable of storing the transmission request information. Screen 4000 may be presented to the user via a medium such as email, for example. Note that the process starting from S3901 may be executed only when the print job management unit 302 of the telecommuting service 103 determines that the device token of the mobile terminal 104 for push notification delivery has not been registered in the push notification server 106.

[0369] However, even if it is determined that the mobile terminal 104 is already registered, the process starting from S3901 may be executed. That is, even when a push notification is to be sent to the mobile terminal 104 in the third embodiment, the process starting from S3901 may be executed. In this manner, even if the registered mobile terminal 104 is in a state in which it cannot receive a push notification, the mobile terminal 104 can send a print job transmission request by using the transmission request information embedded in the QR code (registered trademark) 4001.

[0370] An example of information included in the transmission request information embedded in the QR code (registered trademark) 4001 will be described with reference to Fig. 41. Referring to Fig. 41, the transmission request information includes "application information", "operation information", and "accompanying information".

[0371] The "application information" is information about an application that is started on the mobile terminal 104 when the mobile terminal 104 reads the QR code (registered trademark) 4001 using the camera function. For example, a URL scheme for starting an application may be set in the "application information". The mobile terminal 104 that reads this URL scheme starts the application associated with the URL scheme. In the example shown in FIG. 41, "cloudprintapp: / / " is set as the application information. The application information is information that specifies the application 2000.

[0372] The "operation information" is information about an operation that the mobile terminal 104 executes when the QR code (registered trademark) 4001 is read, and for example, information about an operation that can be executed by an application associated by the above-mentioned application information can be set. The operation information also includes a character string for executing a function that requests transmission of a print job, and the function of requesting transmission of a print job can also be executed together with the start of the application 2000. In other words, the operation information makes it possible to move to the execution of a part related to the function of requesting transmission of a print job specified by the "operation information" in the application 2000 after the start, rather than simply starting the application 2000. In the example shown in FIG. 41, "ReleasePrintJob" is set as the operation information. Note that the type of information set as the operation information is not particularly limited as long as it is possible to specify an operation that can be executed by an application associated by the above-mentioned application information, and for example, an identifier such as an operation ID may be set.

[0373] The "associated information" is information that the mobile terminal 104 can use when executing the operation set in the "operation information". For example, the "associated information" may be set with information that is used when an application associated by the above-mentioned application information executes the operation set in the "operation information". In the example shown in FIG. 41, "JobCode:850203" is set as the associated information. In other words, "850203" is set as the job code.

[0374] In S3903, the mobile terminal 104 reads the QR code (registered trademark) 4001 displayed on the screen 4000 displayed on the client terminal 101.

[0375] In response to reading the QR code (registered trademark) 4001 displayed on the screen 4000 of the client terminal 101 in S3903, the mobile terminal 104 starts the application 2000 in S3904. Specifically, the transmission request information includes a URL scheme for identifying and starting the application 2000, and the mobile terminal 104, having read this URL scheme, starts the application 2000. The URL scheme also includes a character string for executing a function for requesting transmission of a print job (also called a "transmission request function"), and the transmission request function can be started in S3907 together with the start of the application 2000. Note that after reading the QR code (registered trademark) 4001, the mobile terminal 104 may start the application 2000 via a browser instead of directly starting the application 2000. In this case, the transmission request information embedded in the QR code (registered trademark) 4001 includes the URL of a page to be accessed by the browser. The browser can display an explanation of the print job output and include a URL link to an application store for downloading the application 2000. Such processing is effective when the application 2000 is not installed on the mobile terminal 104. Note that the browser may include a URL scheme for launching the application 2000.

[0376] In S3905, the mobile terminal 104 performs authentication.

[0377] In S3906, the mobile terminal 104 determines whether the authentication in S3905 was successful. If the authentication was not successful, the mobile terminal 104 determines NO and ends the process. For example, the application 2000 is returned to an initial state (for example, a state in which the screen 2010 is displayed) or the application 2000 is ended. If the authentication was successful, the mobile terminal 104 determines YES and advances the process to S3907.

[0378] In S3907, the mobile terminal 104 activates the transmission request function. Specifically, the print job management unit 302 of the mobile terminal 104 starts execution of the "transmission request function", which is the process indicated by the "operation information", using the job code indicated by the "accompanying information" included in the transmission request information.

[0379] In S3908, it is determined whether a job code is included as accompanying information in the transmission request information embedded in the QR code (registered trademark) 4001 read in S3903. If a job code is included, the process proceeds to S3909, and if a job code is not included, the process proceeds to S3913. Here, whether or not to include a job code may be set in advance by the user, or may be set for each print job with respect to transmission in S3901 or display in S3902.

[0380] In S3909, the UI control unit 306 of the mobile terminal 104 presents a screen via the started application 2000. The presented screen may be a standby screen (not shown), or may be the screen 2020 shown in FIG. 20(b). When presenting the standby screen, a progress indicator may be presented until the processing from S3909 to S3911 is completed, or the progress may be presented as a percentage. When presenting the screen 2020, the mobile terminal 104 accesses the home service 105 to acquire data for the screen 2020, and presents the screen 2020 to the user based on the data.

[0381] In step S3910 , the print job management unit 302 of the mobile terminal 104 acquires a job code from the “accompanying information” included in the transmission request information embedded in the QR code (registered trademark) 4001 .

[0382] In S3911, the print job management unit 302 of the mobile terminal 104 inputs the job code acquired in S3910 into the input field 2021.

[0383] In S3913, the mobile terminal 104 displays a screen 2020 shown in FIG.

[0384] In S3914, the mobile terminal 104 accepts an input of a job code in the input area 2021 of the screen 2020 by the user.

[0385] From S3911 or S3914, the process proceeds to S3912. In S3912, the print job management unit 302 of the mobile terminal 104 transmits a job code to the home service 105, and requests the home service 105 to transmit the print job to the image forming device 102. The job code here is the job code automatically input in S3911 or the job code accepted in S3914. Specifically, when the button 2022 is pressed, the mobile terminal 104 transmits a transmission request and the information input in the input area 2021 (job code) to the home service 105. This requests the home service 105 to transmit the print job to the image forming device 102.

[0386] S3912 corresponds to S1125 shown in FIG. 12, and processing continues from S3912 to S1127.

[0387] When the button 2023 is pressed, the print job identified by the job code is deleted by sending the information entered in the input area 2021 to the home service 105. Specifically, the process described with reference to FIG. 25 is executed.

[0388] Although the description is omitted in the fourth embodiment, if 3906: YES, processing equivalent to S2302 to S2304 may be executed before proceeding to S3907. Similarly, after S3912, S2308 may be executed and the processing result may be presented to the user.

[0389] In this way, it is possible to omit the user's input operation of the job code by using the QR code (registered trademark) 4001. Also, regarding the output of a print job using the mobile terminal 104, it is possible to further improve usability and security.

[0390] <4.Other> In S3905, only AOA authentication (S1119) may be performed in the mobile terminal 104 as in the first embodiment, or both OAO authentication (S2601) and AOA authentication (S1119) may be performed as in the second embodiment. Also, only OAO authentication (S2601) may be performed in the mobile terminal 104.

[0391] According to the fourth embodiment, it is possible to realize further improvements in usability and security with respect to the registration of a print job using the client terminal 101 and the output of a print job using the mobile terminal 104.

[0392] <Other embodiments> In conjunction with S1111 or in place of S1111, an email may be sent to inform the user of the job code.

[0393] Although the job code is capable of uniquely identifying a print job within a certain range, data other than the job code may be used in place of the job code as long as the data has such a function. Furthermore, for example, data that can identify a print job by combining with at least one or both of a printer ID and a user account ID may be used in place of the job code.

[0394] Furthermore, the telecommuting service 103 may request the home service 105 to generate a job code, and the home service 105 may generate the job code. In this case, the home service 105 transmits the job code to the telecommuting service 103 before S1109.

[0395] Furthermore, the home service 105 may omit acquiring the printer ID in the AOA authentication in step S1119, and the home service 105 may acquire the printer ID in another step. For example, the mobile terminal 104 may acquire the printer ID, and the mobile terminal 104 may transmit the printer ID to the home service 105.

[0396] Furthermore, the printer ID may not be sent in S1127. In this case, verification in S1129 is limited to the job code. The telecommuting service 103 may obtain the printer ID stored in S1109 using the job code as a key. Alternatively, the home service 105 may associate the job code and printer ID and store them between S1125 and S1127, and then obtain the printer ID using the job code received in S1135 as a key.

[0397] Furthermore, the telecommuting service 103 does not need to acquire the printer ID in the OAO authentication in S1101. In this case, the verification in S1129 is only the job code. Also, the telecommuting service 103 identifies the image forming device 102 to which the print job is to be sent by the printer ID received in S1127.

[0398] Furthermore, a step for changing the print settings through a user operation may be provided between S1135 and S1137.

[0399] The information processing device for realizing the functions of the telecommuting service 103 and the information processing device for realizing the functions of the home service 105 may be integrated together. In this case, message communication between the telecommuting service 103 and the home service 105 is message communication between the functional blocks.

[0400] In the above embodiment, a public key system using a private key and a public key as encryption keys is used, but a common key system using a common key as an encryption key may also be used.

[0401] <Technical Features of the Present Disclosure> The present disclosure includes the following methods and compositions.

[0402] [Method 1] A print job transmission method for transmitting a print job to an image forming device, comprising: a registration step in which a first terminal registers a print job in an input side service device; a user authentication step of authenticating a user at a second terminal; a request transmission step of transmitting a transmission request to an output side service device by the second terminal, with at least one condition being that the authentication in the user authentication step is successful; a transmission step of, when the output side service device receives the transmission request, acquiring the print job from the input side service device and transmitting the print job to the image forming device; having How to submit a print job.

[0403] [Method 2] The user authentication step includes: a step of the second terminal transmitting user identification information to a user authentication server; the user authentication server sending a challenge to the second terminal; the second terminal encrypting the challenge with a first encryption key and transmitting the encrypted challenge to the user authentication server; the user authentication server verifies the authentication result by using a second encryption key and transmits the verification result to the second terminal; 2. The print job sending method according to claim 1, further comprising:

[0404] [Method 3] The user authentication step includes: The method further comprises the step of, when the second terminal receives the challenge from the user authentication server, performing biometric authentication of the user; the second terminal encrypts the challenge with the first encryption key, on condition that the biometric authentication is successful, and transmits the encrypted challenge to the user authentication server; 3. The print job sending method according to method 2.

[0405] [Method 4] As a step executed prior to the user authentication step, said second terminal generating said first encryption key and said second encryption key; storing the first encryption key in the second terminal; storing the second encryption key in association with the user identification information in the user authentication server; Further comprising Method 3. The print job sending method according to method 3.

[0406] [Method 5] A step executed before the step of generating the first encryption key and the second encryption key by the second terminal, the first terminal transmitting the user identification information to the user authentication server; a step of the user authentication server requesting the second terminal to generate the first encryption key and the second encryption key; Further comprising 5. The print job sending method according to method 4.

[0407] [Method 6] user identification information used in authenticating the user is associated with device identification information of the image forming device; the image forming apparatus to which the print job is to be sent is identified by the apparatus identification information associated with the user identification information; 6. A print job sending method according to any one of Methods 1 to 5.

[0408] [Method 7] The method further includes a second terminal authentication step of authenticating the second terminal, In the request transmission step, the second terminal transmits the transmission request to the output side service device with an additional condition that the authentication in the second terminal authentication step is successful. 7. A print job sending method according to any one of Methods 1 to 6.

[0409] [Method 8] The transmission request is accompanied by device identification information of the image forming device associated with terminal identification information of the second terminal used in the second terminal authentication step, the image forming device to which the print job is to be sent is identified by the device identification information associated with the terminal identification information; 8. The print job sending method according to method 7.

[0410] [Method 9] a step of requesting a terminal authentication server to generate terminal identification information for authenticating the second terminal by attaching the device identification information; a step of the terminal authentication server having a device management server confirm whether the device identification information is correct; if the device management server confirms that the device identification information is valid, the terminal authentication server generates the terminal identification information in association with the device identification information; storing the terminal identification information and the device identification information in association with each other in the terminal authentication server and the second terminal; Further comprising: In the second terminal authentication step, the terminal identification information stored in the terminal authentication server and the second terminal is used. 9. The print job sending method according to method 8.

[0411] [Method 10] The input service device and the output service device are integrated together. 10. A print job sending method according to any one of Methods 1 to 9.

[0412] [composition] A print job transmission system for transmitting a print job to an image forming device, comprising: a first terminal for transmitting a print job to an input side service device; an input side service device that registers the print job received from the first terminal; a second terminal that transmits a transmission request for transmitting the print job to an output side service device, on at least one condition that user authentication for authenticating a user in the second terminal is successful; an output side service device that acquires the print job from the input side service device in response to the transmission request received from the second terminal and transmits the print job to the image forming device; Equipped with Print job submission system. [Explanation of symbols]

[0413] 101 Client terminals 102 Image forming device 103 Cloud print service for telecommuting 104 Mobile Devices 105 Home cloud print service 106 Push notification server 108 Image forming device management server 107 Authentication Server 107A Common Authentication Server 107B Regional Authentication Server

Claims

1. A print job transmission method for transmitting a print job to an image forming device, comprising: a registration step in which the first terminal registers a print job in an input side service device; a user authentication step of authenticating a user at the second terminal; a request transmission step of transmitting a transmission request to an output side service device by the second terminal on at least one condition that the authentication in the user authentication step is successful; a transmission step of, when the output side service device receives the transmission request, acquiring the print job from the input side service device and transmitting the print job to the image forming device; having How to submit a print job.

2. The user authentication step includes: transmitting user identification information from the second terminal to a user authentication server; the user authentication server sending a challenge to the second terminal; the second terminal encrypting the challenge with a first encryption key and transmitting the encrypted challenge to the user authentication server; the user authentication server performs verification using a second encryption key and transmits a verification result to the second terminal; The method of claim 1 , further comprising:

3. The user authentication step includes: The method further comprises the step of, when the second terminal receives the challenge from the user authentication server, performing biometric authentication of the user; the second terminal encrypts the challenge with the first encryption key, on condition that the biometric authentication is successful, and transmits the encrypted challenge to the user authentication server; The print job sending method according to claim 2 .

4. As a step executed prior to the user authentication step, said second terminal generating said first encryption key and said second encryption key; storing the first encryption key in the second terminal; storing the second encryption key in association with the user identification information in the user authentication server; Further comprising The print job sending method according to claim 3 .

5. A step executed before the step of generating the first encryption key and the second encryption key by the second terminal, the first terminal transmitting the user identification information to the user authentication server; a step of the user authentication server requesting the second terminal to generate the first encryption key and the second encryption key; Further comprising The print job sending method according to claim 4.

6. user identification information used in authenticating the user is associated with device identification information of the image forming device; the image forming apparatus to which the print job is to be sent is identified by the apparatus identification information associated with the user identification information; The print job sending method of claim 1 .

7. The method further includes a second terminal authentication step of authenticating the second terminal, In the request transmission step, the second terminal transmits the transmission request to the output side service device with an additional condition that the authentication in the second terminal authentication step is successful. The print job sending method of claim 1 .

8. The transmission request is accompanied by device identification information of the image forming device associated with terminal identification information of the second terminal used in the second terminal authentication step, the image forming device to which the print job is to be sent is identified by the device identification information associated with the terminal identification information; The print job sending method according to claim 7.

9. a step of requesting a terminal authentication server to generate terminal identification information for authenticating the second terminal by attaching the device identification information; a step of the terminal authentication server having a device management server confirm whether the device identification information is correct; if the device management server confirms that the device identification information is valid, the terminal authentication server generates the terminal identification information in association with the device identification information; storing the terminal identification information and the device identification information in association with each other in the terminal authentication server and the second terminal; Further comprising: In the second terminal authentication step, the terminal identification information stored in the terminal authentication server and the second terminal is used. The print job sending method of claim 8.

10. The input service device and the output service device are integrated together. The print job sending method of claim 1 .

11. A print job transmission system for transmitting a print job to an image forming device, comprising: a first terminal for transmitting a print job to an input side service device; an input side service device that registers the print job received from the first terminal; a second terminal that transmits a transmission request for transmitting the print job to an output side service device, on at least one condition that user authentication for authenticating a user at the second terminal is successful; an output side service device that acquires the print job from the input side service device in response to the transmission request received from the second terminal and transmits the print job to the image forming device; Equipped with Print job submission system.

Images