Information processing system, user terminal, server and program

Abstract

To provide a mechanism that makes it possible to easily display, on a user terminal, a setting screen corresponding to a printer that a user desires even when the user does not know an IP address or a device name of the printer to which the user wants to output a print job.SOLUTION: An information processing system comprises a user terminal and a server that transmits a print job registered from the user terminal to a printer selected as an output destination. The server is provided with a function of performing information notification for identifying the printer used by a user who operates the user terminal to log in to a printing service, as a response to an inquiry from the user terminal. The user terminal is provided with a function of displaying a first setting screen corresponding to the printer identified by the information obtained from the server.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to an information processing system, a user terminal, a server, and a program. [Background technology]

[0002] Cloud-based printing services are now available, allowing users to freely print documents stored on a cloud server from any printing device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-124791 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the number and types of printing devices managed by cloud servers are greater than those in local environments, making it difficult for users who do not know the IP (Internet Protocol) addresses or device names of their printing devices to simply select a specific printing device from the driver selection field.

[0005] The present invention aims to enable a user to easily display a setting screen corresponding to a desired printing device on a user terminal even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job. [Means for solving the problem]

[0006] The invention described in claim 1 is an information processing system comprising a user terminal and a server that sends a print job registered from the user terminal to a printing device selected as an output destination, wherein the server notifies the user operating the user terminal of information identifying the printing device used to log in to a printing service in response to an inquiry from the user terminal, and the user terminal displays a first setting screen corresponding to the printing device identified by the information obtained from the server. The invention described in claim 2 is an information processing system described in claim 1, in which, when the user terminal receives a document printing operation, it displays a second setting screen common to multiple printing devices as an initial screen, and when it receives an operation to switch to the first setting screen on the second setting screen, it sends the inquiry to the server. The invention described in claim 3 is an information processing system described in claim 2, in which, if there is a setting to fix the setting screen to be displayed as the first setting screen, the user terminal displays the setting screen set as the fixed target after accepting the switching operation. A fourth aspect of the present invention is the information processing system according to the first aspect, wherein the user terminal transmits the inquiry to the server when a print operation for a document is received. A fifth aspect of the present invention is the information processing system according to the first aspect, wherein the user terminal generates an icon for calling up the first setting screen when a predetermined condition is met. The invention described in claim 6 is an information processing system described in claim 1, in which, when the server detects a new login to the printing service, it updates the combination list of the printing device used for the login and the user who logged in through that printing device. The invention described in claim 7 is an information processing system described in claim 6, in which, if there are multiple records of the printing device used to log in for the user corresponding to the inquiry, the server notifies the user terminal of information identifying the printing device corresponding to the last login. The invention described in claim 8 is an information processing system described in claim 1, in which, when the server detects a new login from the printing device, it causes the printing device to display a screen inquiring about the generation of an icon for calling up the first setting screen corresponding to the printing device from which the login originated on the user terminal. The invention described in claim 9 is a user terminal that registers a print job to a server by specifying a printing device as the output destination, and has one or more processors, wherein the one or more processors query the server for information identifying the printing device used by the user operating the user terminal to log in to the printing service, and display a first setting screen corresponding to the printing device identified by the information obtained from the server. The invention described in claim 10 is a server that sends a print job registered from a user terminal to a printing device designated as an output destination, and has one or more processors, and in response to an inquiry from the user terminal, the one or more processors notify information identifying the printing device used by the user operating the user terminal to log in to the printing service. The invention described in claim 11 is a program for enabling a computer that functions as a user terminal that specifies a printing device as the output destination and registers a print job on a server to perform the following functions: querying the server for information identifying the printing device used by the user operating the user terminal to log in to the printing service; and displaying a first setting screen corresponding to the printing device identified by the information obtained from the server. The invention described in claim 12 is a program for realizing the function of notifying a computer functioning as a server that sends a print job registered from a user terminal to a printing device designated as the output destination, in response to an inquiry from the user terminal, of information identifying the printing device used by the user operating the user terminal to log in to the printing service. [Effects of the Invention]

[0007] According to the invention described in claim 1, even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the invention of claim 2, if the user wishes, the setting screen of the printing device that the user used to log in can be displayed. According to the invention of claim 3, even if a user has used multiple printing devices to log in, the setting screen desired by the user can be displayed. According to the invention of claim 4, the setting screen corresponding to the printing device used by the user to log in can be displayed as the initial screen. According to the invention of claim 5, by generating an icon corresponding to the printing device used by the user to log in, it is possible to easily read out the setting screen corresponding to the printing device that is the output destination. According to the invention of claim 6, a setting screen corresponding to one or more printing devices used by the user for login can be displayed on the user terminal. According to the seventh aspect of the present invention, a setting screen corresponding to the printing device that the user last used to log in can be displayed on the user terminal. According to the invention as set forth in claim 8, it is possible to easily call up a setting screen corresponding to the printing device from which output is desired. According to the invention described in claim 9, even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the invention described in claim 10, even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the invention described in claim 11, even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the invention described in claim 12, even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates a cloud printing system. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a server. [Figure 3] FIG. 10 is a diagram illustrating an example of the data structure of a login list. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of a user terminal. [Figure 5] FIG. 1 illustrates an example of the hardware configuration of a printing device having an image reading function. [Figure 6] FIG. 2 is a diagram illustrating user actions until a print job is registered in the first embodiment. [Figure 7] FIG. 10 is a diagram illustrating an example of a processing sequence according to the first embodiment regarding initial registration of a print job. [Figure 8] FIG. 10 is a diagram illustrating updating of the login list by overwriting and saving. [Figure 9] FIG. 10 is a diagram illustrating updating of the login list by additional storage. [Figure 10] 10A and 10B are diagrams illustrating examples of display of a menu screen and a common driver setting screen. [Figure 11] FIG. 10 is a diagram illustrating an example of a setting screen for a dedicated driver corresponding to the printing device that was last logged in. [Figure 12] 10A and 10B are diagrams illustrating an example of user behavior after registration of a print job. [Figure 13] FIG. 10 is a diagram illustrating an example of a processing sequence according to the first embodiment regarding the execution of a registered print job. [Figure 14] FIG. 10 is a diagram illustrating an example of user behavior until a print job is registered. [Figure 15]FIG. 10 is a diagram illustrating an example of a processing sequence according to the second embodiment regarding the initial registration of a print job. [Figure 16] FIG. 10 is a diagram illustrating an example of a setting screen for a dedicated driver corresponding to the printing device that was last logged in. [Figure 17] FIG. 10 is a diagram illustrating an example of a hardware configuration of a user terminal according to the second embodiment. [Figure 18] FIG. 10 is a diagram illustrating an example of a processing sequence when, after enabling fixed settings on a setting screen of a dedicated driver corresponding to a printing device, another printing device is used to log in to a cloud printing service and further register a print job. [Figure 19] FIG. 10 is a diagram illustrating updating of the login list by overwriting and saving. [Figure 20] FIG. 10 is a diagram illustrating updating of the login list by additional storage. [Figure 21] 10A and 10B are diagrams illustrating the difference between setting screens depending on whether or not fixed settings are made; [Figure 22] FIG. 10 is a diagram illustrating another example of a processing sequence when, after enabling fixed settings on the setting screen of a dedicated driver corresponding to a printing device, another printing device logs in to a cloud printing service and further registers a print job. [Figure 23] 10A and 10B are diagrams illustrating another example of the display of the common driver setting screen. [Figure 24] FIG. 10 is a diagram illustrating an example of a processing sequence according to the third embodiment regarding the initial registration of a print job. [Figure 25] FIG. 10 is a diagram illustrating an example of an inquiry screen displayed on an operation panel. [Figure 26] FIG. 11 is a diagram illustrating an example of the data structure of a login list used in the third embodiment. [Figure 27] FIG. 11 is a diagram illustrating a display example of a menu screen in the third embodiment. [Figure 28] FIG. 11 is a diagram illustrating a display example of a common driver setting screen in the third embodiment. [Figure 29] FIG. 10 is a diagram illustrating another example of a processing sequence related to the initial registration of a print job. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. <First Embodiment> <System configuration> 1 is a diagram illustrating a cloud printing system 1. The cloud printing system 1 is composed of a server 10 that provides cloud printing services, a user terminal 20 operated by a user, and a printing device 30 connected to a cloud network N. The cloud printing system 1 here is an example of an information processing system.

[0010] A user of the cloud printing service can retrieve and execute a print job that has been previously uploaded on any printing device 30. The cloud printing service is an example of a printing service, and is available only to users who are registered as customers. 1 is a cloud server. The server 10 is composed of one or more servers. The server 10 manages the storage of print jobs uploaded from the user terminal 20 and the output of print jobs to the printing device 30 to which the user logs in.

[0011] The user terminal 20 shown in Fig. 1 is, for example, a desktop computer, a notebook computer, a tablet computer, or a smartphone. The user terminal 20 may also be a so-called wearable terminal. Wearable terminals include wristwatch-type, ring-type, and eyeglass-type terminals. Eyeglass-type wearable terminals include, for example, smart glasses and AR (Augmented Reality) glasses. 1, the user terminal 20 operated by user A is referred to as "user terminal A" or "user terminal 20A." In the following, user terminal 20 is used as a general term for user terminals 20A, 20B, etc.

[0012] The printing device 30 is a device that has at least the function of printing a document onto paper. In this sense, the printing device 30 is also called an image forming device. The printing device 30 may be a device dedicated to printing, but may also have other functions. Examples of other functions include duplicate printing (so-called copy printing), document scanning, and facsimile. The printing device 30 shown in Fig. 1 may be installed in any location, and may exist in multiple locations. In Fig. 1, different printing devices 30 are referred to as "printing device A" and "printing device 30A." Below, printing device 30 is used as a general term for printing devices 30A, 30B, 30C, 30D, 30E, 30F, etc.

[0013] <Server configuration> FIG. 2 is a diagram illustrating an example of the hardware configuration of the server 10. As shown in FIG. 2 includes a processor 11, a ROM (Read Only Memory) 12 in which a BIOS (Basic Input Output System) and the like are stored, a RAM (Random Access Memory) 13 used as a work area for the processor 11, an auxiliary storage device 14, and a communication interface 15. Each device is connected via a bus or other signal lines 16.

[0014] The processor 11 is a device that realizes various functions by executing programs. The processor 11, ROM 12, and RAM 13 function as a computer. The communication interface 15 is an interface that realizes communication with the user terminal 20 and the printing device 30. The communication interface 15 is compatible with various communication standards, such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

[0015] The auxiliary storage device 14 is configured by, for example, a hard disk device or semiconductor storage. Programs and various data are stored in the auxiliary storage device 14. The term "program" is used as a general term for the OS (=Operating System) and application programs. In this embodiment, a login list 14A is stored in the auxiliary storage device 14. The login list 14A is an example of information that identifies the printing device 30 that the user has used to log in to the cloud printing service.

[0016] FIG. 3 is a diagram illustrating an example of the data structure of the login list 14A. The login list 14A shown in Figure 3 is composed of a user ID (=identifier) ​​14A1, which is information that identifies a user, a printing device ID 14A2, which is information that identifies the printing device 30 used to log in to the cloud printing service, and a login date and time 14A3. For the user ID, for example, the user's account name, information linked to the user's registration information, the IP address of the user terminal 20, the device name of the user terminal 20, and the MAC (=Media Access Control address) address of the user terminal 20 are used. For example, the device name of the printing device 30, the IP address of the printing device 30, and the MAC address of the printing device 30 are used as the printing device ID. In the case of FIG. 3, for example, it can be seen that user A operated printing device C to log in to the cloud printing service at "2024 / 3 / 30 11:56."

[0017] <User terminal configuration> FIG. 4 is a diagram illustrating an example of the hardware configuration of the user terminal 20. As shown in FIG. 4 includes a processor 21, a ROM 22 storing the BIOS and the like, a RAM 23 used as a work area for the processor 21, an auxiliary storage device 24, a communication interface 25, a display 26, and an input device 27. Each device is connected via a bus or other signal lines 28.

[0018] The auxiliary storage device 24 is configured by, for example, a hard disk device or semiconductor storage, and stores programs and various data. In this embodiment, the auxiliary storage device 24 stores a cloud print driver 24A and a server cooperation application 24B.

[0019] The cloud print driver 24A is, for example, a print driver provided by the operator of a cloud print service. The cloud print driver 24A includes a driver corresponding to functions and restrictions common to, for example, printing devices 30A, 30B, 30C, 30D, 30E, 30F (see FIG. 1) connected to the cloud network N, and a driver corresponding to functions and restrictions specific to each individual printing device 30. In Figure 4, the former driver is shown as "Common Functions / Prohibitions," and the latter driver is shown as "Device A Exclusive Functions / Prohibitions," "Device B Exclusive Functions / Prohibitions," "Device C Exclusive Functions / Prohibitions," etc.

[0020] However, the cloud print driver 24A may be a driver that only supports functions and restrictions common to all printing devices 30. The server cooperation application 24B is an application program that realizes cooperation with the server 10 (see FIG. 1) when using the cloud printing service. For example, the server cooperation application 24B downloads the login list 14A (see FIG. 2) and controls the display of a property setting screen that is presented to the user. The display 26 is, for example, a liquid crystal display or an organic EL (Electro Luminescence) display.

[0021] The input device 27 is, for example, a mouse or a keyboard. Incidentally, when the user terminal 20 is a notebook computer, a tablet computer, or a smartphone, a capacitive touch sensor having transparency that does not obstruct the visibility of the image displayed on the display 26 is used as the input device 27. A device that combines this type of touch sensor with the display 26 is called a touch panel.

[0022] <Printing device configuration> FIG. 5 is a diagram showing an example of the hardware configuration of a printing device 30 having an image reading function. The printing device 30 has a processor 31, a ROM 32 in which BIOS, firmware, etc. are stored, a RAM 33 used as a work area for the processor 31, an auxiliary storage device 34, an operation panel 35, a scanner unit 36, an image processing unit 37, a printing unit 38, and a communication interface 39.

[0023] The processor 31 is a device that realizes various functions through the execution of firmware. The processor 31, ROM 32, and RAM 33 function as a computer. The auxiliary storage device 34 is configured by, for example, a hard disk drive or semiconductor storage, and stores, for example, print jobs and document images. The operation panel 35 is configured as, for example, a touch panel. The scanner unit 36 ​​includes, for example, a light source that irradiates the document with illumination light, an image sensor that captures an image of the document, and a mechanism for transporting the document.

[0024] The image processing unit 37 is a processing unit that performs image processing such as color correction, tone correction, and the like on the image of a print job or an original document. The printing unit 38 is a mechanism that forms an image on paper using, for example, an electrophotographic method or an inkjet method. The communication interface 39 is an interface that realizes communication with the server 10 (see FIG. 1).

[0025] <Explanation of processing operation> The following describes the processing operations executed in the cloud printing system 1 (see FIG. 1) assumed in the first embodiment.

[0026] <Up until the first print job registration> <User behavior> A user who uses the cloud printing service can call up a print job uploaded to the server 10 (see FIG. 1) to any printing device 30 connected to the cloud network N and execute the print job. However, the printing devices 30 (see FIG. 1) connected to the cloud network N are not all the same model or have the same functions. For this reason, if a printing device 30 does not support the functions or restrictions specified in the print job, the user may not be able to print the image on paper as desired. For example, even if the user specifies color printing, if the printing device 30 that the user used to call the print job supports only monochrome printing, the user will only receive a monochrome printout.

[0027] To solve this problem, the user can identify in advance the printing device 30 that can perform the printing desired by the user, and then upload the print job created using the driver setting screen corresponding to the identified printing device 30 to the server 10. However, even if one wants to select a driver that corresponds to a specific printing device 30, if one does not know the IP address or device name of the specific printing device 30, it is difficult to select the specific printing device 30 in the driver selection field. Although using a common driver that can be applied to all printing devices 30 will prevent discrepancies between the settings and the printed product, the settable functions and restrictions will be limited, and as a result, the printed product will not be what the user desires.

[0028] Therefore, in this embodiment, the generation of a print job for a specific printing device 30 is supported by using the login list 14A (see FIG. 2). 6 is a diagram for explaining the actions of user A up until a print job is registered in embodiment 1. In Fig. 6, parts corresponding to those in Fig. 1 are assigned the same reference numerals. First, user A logs in to the cloud print service at time T1. Specifically, user A operates printing device 30C to log in to server 10. This login information is recorded in the login list 14A of server 10. The printing device 30C used to log in is referred to as the login source. Next, at time T2, user A operates user terminal 20A to call up the setting screen of printing device 30C and performs print settings. Thereafter, at time T3, a print job is registered in the server 10 from the user terminal 20A.

[0029] <Processing sequence> 7 is a diagram illustrating an example of a processing sequence for initial registration of a print job according to the first embodiment. Note that the symbol S in the diagram represents a step. The processing sequence shown in FIG. 7 begins in printing device 30C as described with reference to FIG. When the printing device 30C receives a login operation to the cloud printing service (step 101), it transmits authentication data to the server 10 (step 102). The authentication data is input, for example, through the operation panel 35 (see FIG. 5). If the printing device 30C is equipped with a card reader, the authentication data may be read from an IC (Integrated Circuit) card such as an employee ID card.

[0030] When the server 10 receives the authentication data, it authenticates the user (step 103), that is, it determines whether the logged-in user has the authority to use the cloud printing service. The authentication result is notified to the printing device 30C from the server 10. The printing device 30C displays the received authentication result (step 104). If the authentication is successful, the server 10 updates the login list 14A (step 105). Specifically, the fact that user A has logged in to the cloud print service from the printing device 30C is recorded. The login list 14A may record logins for which authentication has failed, in addition to logins for which authentication has been successful. In this case, the authentication results are also recorded in the login list 14A.

[0031] The login list 14A can be updated by overwriting or by adding. 8 is a diagram for explaining updating of the login list 14A by overwriting and saving. In FIG. 8, parts corresponding to those in FIG. 3 are assigned the same reference numerals. In the case of overwriting and saving, only the last login date and time for each user is recorded in the login list 14A. For this reason, in Figure 8, "2024 / 3 / 30 16:18" is recorded as the last login date and time for user A. Note that the printing device 30 used for the login operation is printing device C, the same as the previous login operation.

[0032] 9 is a diagram for explaining updating of the login list 14A by additional storage. In FIG. 9, parts corresponding to those in FIG. 3 are assigned the same reference numerals. In the case of additional storage, all login dates and times for each user are recorded in the login list 14A. For this reason, in FIG. 9, not only the date and time of the previous login of user A but also the date and time of the last login is recorded.

[0033] Returning to the explanation of Figure 7. Thereafter, the user terminal 20A accepts the selection of the print function from the file menu of the document (step 106). In other words, the user terminal 20A accepts the print operation. A document may include, for example, text data, graphics data, image data, photographic data, or a combination thereof, and the like. When the print function is selected in the function selection field 261 (see FIG. 10), the user terminal 20A accesses the server 10 via the server cooperation application 24B (see FIG. 4) and inquires about login information (step 107). In response to the inquiry, the server 10 returns the login list 14A (see FIG. 2) of the target user (step 108). In other words, the user terminal 20A acquires the login list 14A from the server 10.

[0034] Next, the user terminal 20A displays the common driver setting screen 260B (see FIG. 10) (step 109). The common driver setting screen 260B is a screen for setting functions and restrictions that are common to all printing devices 30 that can be selected in the cloud printing service. FIG. 10 is a diagram illustrating an example of the display of the menu screen 260A and the common driver setting screen 260B. The menu screen 260A shown in FIG. 10 is made up of a function selection field 261, a print execution button 262, a driver selection field 263, and a preview screen 264.

[0035] In the function selection column 261, for example, a "Back" button, a "Home" button, a "New" button, an "Open" button, a "Save" button, and a "Print" button are arranged. A menu screen 260A shown in FIG. 10 represents a display screen after the "Print" button in the function selection field 261 is operated. The driver selection column 263 displays selectable drivers for individual printing devices 30 (e.g., "Device A," "Device B," etc.) and drivers corresponding to functions and restrictions common to all printing devices 30 (e.g., "Common to all devices") Incidentally, the square at the beginning of each row is an icon corresponding to an individual driver. In the driver selection column 263 shown in FIG. 10, the driver with the device name "common to all devices" is selected, which is indicated by shading.

[0036] The common driver setting screen 260B is displayed when a driver with a device name "Common to all devices" is selected in the driver selection field 263. The common driver setting screen 260B is an example of a second setting screen. The common driver setting screen 260B is also an example of an initial screen. A common driver setting screen 260B shown in FIG. 10 has a common property setting field 265, a "dedicated mode" button 266, and an "OK" button 267 arranged thereon. In the common property setting field 265, it is possible to set functions and prohibitions that are common to all printing devices. The "dedicated mode" button 266 is a button for switching the display to the setting screen 260C (see FIG. 11) corresponding to the printing device 30 to which the user last logged in. For example, by operating the "dedicated mode" button 266, the setting screen 260B is switched to the setting screen 260C of the printing device 30C. When the "OK" button 267 is operated, the property settings are confirmed and the screen returns to the menu screen 260A.

[0037] Returning to the explanation of Figure 7. 7, the user terminal 20A accepts switching to a dedicated driver setting screen while displaying the common driver setting screen 260B (see FIG. 10) (step 110). Specifically, the user terminal 20A accepts operation of the "dedicated mode" button 266 (see FIG. 10). In this case, the user terminal 20A displays a setting screen 260C (see FIG. 11) dedicated to the printing device 30C that the user last logged in to (step 111). The printing device 30C that the user last logged in to can be identified from the login list 14A (see FIG. 3).

[0038] 11 is a diagram illustrating an example of a dedicated driver setting screen corresponding to the printing device that was last logged in. In FIG. 11, parts corresponding to those in FIG. 10 are denoted by the same reference numerals. A common driver setting screen 260B is displayed in the upper part of Fig. 11, and a dedicated driver setting screen 260C corresponding to the printing device 30C that was last logged in is displayed in the lower part of Fig. 11. The dedicated driver setting screen 260C here is an example of a first setting screen. The dedicated driver setting screen 260C shown in FIG. 11 has a setting field 268 for the properties of the printing device C, a "Common Mode" button 269, and an "OK" button 267 arranged thereon.

[0039] In the setting field 268 for the printer C, settings relating to functions and prohibitions specific to the printer C can be made. The "Common Mode" button 269 is a button for switching the display to a common driver setting screen 260B. When the "OK" button 267 is operated, the property settings are confirmed and the screen returns to the menu screen 260A (see FIG. 10).

[0040] Returning to the explanation of Figure 7. In the case of FIG. 7, the user terminal 20A accepts the operation of the print execution button 262 (see FIG. 10) on the menu screen 260A (see FIG. 10) (step 112). Thereafter, the user terminal 20A transmits the print job to the server 10 (step 113). The server 10 registers the received print job (step 114). This completes the processing operations up to the registration of the print job.

[0041] If the user wishes to register other print jobs, the user can simply repeat steps 106 to 114. Incidentally, the user can set the print job using the common driver setting screen 260B (see FIG. 11), or can set the properties using the setting screen of a specific dedicated driver specified in the driver selection field 263 (see FIG. 10).

[0042] <Executing registered print jobs> <User behavior> 12 is a diagram for explaining an example of user behavior after registering a print job. In FIG. 12, parts corresponding to those in FIG. 6 are denoted by the same reference numerals. First, at time T4, user A moves to printing device 30C. After that, user A operates printing device 30C to log in to server 10 and call up the print job that user A registered. The print job in this case is an unexecuted print job. Note that the driver used to set up the print job does not matter.

[0043] Therefore, not only print jobs set by a dedicated driver corresponding to the printing device 30C used for login, but also print jobs set by a dedicated driver corresponding to another printing device 30 (e.g., printing device 30A) and print jobs set by a common driver are displayed. At the next time point T5, the specific print job designated by user A is called from server 10 to printing device 30C. Thereafter, at time T6, printing is performed by the printing device 30C.

[0044] <Processing sequence> 13 is a diagram illustrating an example of a processing sequence relating to the execution of a registered print job in the first embodiment. In Fig. 13, parts corresponding to those in Fig. 7 are assigned the same reference numerals. 13 also starts when the printing device 30C accepts a login operation to the cloud printing service (step 101). Note that the processing up to step 105 is the same as the processing sequence shown in FIG. If the authentication is successful, user A can request a print job list via the operation panel 35 (see FIG. 5) of the printing device 30C. In FIG. 13, after step 104, printing device 30C accepts a display of the print job list (step 201).

[0045] In this case, the printing device 30C requests the server 10 for a print job list (step 202). In response to the request from the printing device 30C, the server 10 returns a print job list related to the logged-in user A (step 203). Printing device 30C displays the received print job list (step 204) and accepts execution of a print job from user A (step 205). The number of print jobs accepted for execution is not limited to one, and may be multiple. In response to the request from printing device 30C, server 10 transmits the specified print job (step 206). Thereafter, the printing device 30C executes printing in accordance with the received print job (step 207).

[0046] <Summary> When adopting the cloud printing system 1 (see FIG. 1) described in this embodiment, a user can call up the dedicated driver setting screen 260C (see FIG. 11) corresponding to the printing device 30 that the user wishes to use for output, simply by operating the "dedicated mode" button 266 (see FIG. 11) provided on the common driver setting screen 260B (see FIG. 11).

[0047] In other words, even if the user does not know the IP address or device name of the printing device 30 to which the user wants to output a print job, if the user operates the specific printing device 30 to log in to the cloud printing service immediately before setting the properties, the user can set the properties on the setting screen 260C of the dedicated driver corresponding to the specific printing device 30.

[0048] As a result, compared to when properties are set on the common driver setting screen 260B, the number of configurable functions and types of prohibited characters is increased, making it possible to print in the style desired by the user. If the item the user wants to set is not included in the displayed dedicated driver setting screen 260C, the user can simply move to another printing device 30 and repeat the process of logging in to the cloud printing service. Although this increases the amount of work required for moving, it makes it possible to find a printing device 30 that includes the item the user wants to set, even if the user does not know the IP address or device name.

[0049] Furthermore, in the case of the cloud printing system 1 described in this embodiment, a user can simply log in to the cloud printing service using the printing device 30 they want to use, and the dedicated driver settings screen 260C corresponding to the printing device 30 they used to log in can be reliably displayed. This makes it possible to eliminate printing failures caused by inconsistencies between the dedicated driver settings screen used to set up the print job and the functions and restrictions supported by the printing device 30 used for the print job.

[0050] <Embodiment 2> In this embodiment, a modification of the first embodiment will be described. Therefore, the cloud printing system 1 (see FIG. 1) assumed in the second embodiment is common to the cloud printing system 1 described in the first embodiment. Furthermore, the hardware configurations of the server 10 (see FIG. 1), user terminal 20 (see FIG. 1), and printing device 30 (see FIG. 1) assumed in the second embodiment are also the same as those in the first embodiment. The difference is in the processing contents of the cloud print driver 24A (see FIG. 4) and the server cooperation application 24B (see FIG. 4).

[0051] <Explanation of processing operation> The following describes the processing operations executed in the cloud printing system 1 (see FIG. 1) assumed in the second embodiment.

[0052] <Up until the first print job registration> <User behavior> 14 is a diagram for explaining an example of user actions up to the time when a print job is registered. In FIG. 14, parts corresponding to those in FIG. 6 are denoted by the same reference numerals. In the case of Figure 14, the actions of user A from time T1 to time T3 are the same as those in Figure 6. That is, user A sets properties on the setting screen of the dedicated driver corresponding to printing device 30C that has logged in to the cloud printing service.

[0053] Note that user A logs in to the cloud print service through printing device 30F at time T4. This login is performed, for example, when printing device 30F is closest to user A's current location. In this case, too, by operating the "dedicated mode" button 266 (see FIG. 11), it is possible to easily call up the dedicated driver setting screen 260C (see FIG. 11) corresponding to the printing device 30F.

[0054] However, there may be a case where the user wants to execute a print job on the printing device 30C that he or she previously logged in to. In such a case, in the cloud printing system 1 described in the first embodiment, it is necessary to move from the printing device 30F to the printing device 30C and log in to the cloud printing service. In this embodiment, a mechanism will be described that allows the user to easily call up the dedicated driver setting screen corresponding to the printing device 30C that is normally used at any time.

[0055] <Processing sequence> 15 is a diagram illustrating an example of a processing sequence for initial registration of a print job according to the second embodiment. In Fig. 15, parts corresponding to those in Fig. 7 are assigned the same reference numerals. In the processing sequence shown in Figure 15, a process (step 301) is added between step 111 and step 112 in which user terminal 20A accepts a fixation operation on setting screen 260C (see Figure 11) of printing device C (i.e., printing device 30C). The other processing operations are the same as those in the first embodiment.

[0056] For this fixing operation, the "fix" button 270 (see FIG. 16) is used. 16 is a diagram illustrating an example of a dedicated driver setting screen corresponding to the printing device that was last logged in. In FIG. 16, parts corresponding to those in FIG. 11 are assigned the same reference numerals. In the case of FIG. 16, a "Fix" button 270 has been added. The "Fix" button 270 is a toggle switch, and when the button is operated while the fixed settings are enabled, the fixed settings are switched to an invalid state, and when the button is operated while the fixed settings are disabled, the fixed settings are switched to an valid state.

[0057] If the fixed settings are enabled, when the "Dedicated Mode" button 266 (see FIG. 11) is operated on the common driver settings screen 260B (see FIG. 11), the dedicated driver settings screen for the printing device for which the fixed settings are enabled is displayed in preference to the dedicated driver corresponding to the printing device for which the last login is confirmed. Fig. 17 is a diagram illustrating an example of the hardware configuration of the user terminal 20 according to the second embodiment. In Fig. 17, parts corresponding to those in Fig. 4 are assigned the same reference numerals. 17, fixed driver information 24C is added to the auxiliary storage device 24. Information identifying a dedicated driver for which fixed settings are valid is recorded in the fixed driver information 24C. For example, a device name and an IP address are recorded in the fixed driver information 24C.

[0058] <Registering a print job after fixed settings> <Processing sequence 1> FIG. 18 is a diagram illustrating an example of a processing sequence when, after enabling the fixed settings on the setting screen 260D (see FIG. 16) of the dedicated driver corresponding to the printing device 30C, another printing device 30F logs in to the cloud printing service and further registers a print job. In FIG. 18, parts corresponding to those in FIG. 7 are denoted by the same reference numerals. In the case of FIG. 18, after the printing device 30F accepts a login operation to the cloud printing service (step 101), it transmits authentication data to the server 10 (step 102). In FIG. 7, the printing device 30C receives a login operation to the cloud printing service.

[0059] Thereafter, the server 10 authenticates the received authentication data (step 103) and returns the authentication result to the printing device 30F. The printing device 30F displays the received authentication result (step 104). If the authentication is successful, the server 10 updates the login list 14A (step 105). The above processing is the same as that shown in FIG. 15, except that data is sent and received between the printer 30F and the server 10.

[0060] 19 is a diagram for explaining updating of the login list 14A by overwriting and saving. In FIG. 19, parts corresponding to those in FIG. 8 are denoted by the same reference numerals. In the case of FIG. 19, the printing device 30F used for the login operation is recorded in association with user A. 20 is a diagram for explaining updating of the login list 14A by additional storage. In FIG. 20, parts corresponding to those in FIG. 9 are denoted by the same reference numerals. In the case of FIG. 20, the printing device 30F used in the login operation is recorded in association with user A.

[0061] Returning to the description of FIG. Thereafter, user A operates user terminal 20A and accepts the selection of the print function from the file menu of the document (step 106). In the case of Fig. 18, the user terminal 20A that has detected the selection of the print function checks whether or not there are fixed settings on the setting screen (step 401). "Presence" of fixed settings means that the fixed settings are valid. On the other hand, "absence" of fixed settings means that the fixed settings are invalid. In the case of FIG. 18, after checking whether or not there is a fixed setting in step 401, the login list 14A (see FIG. 3) is read from the server 10 (steps 107 and 108).

[0062] Thereafter, the user terminal 20A displays the common driver setting screen 260B (see FIG. 11) (step 109), and then accepts switching to the dedicated driver setting screen (step 110). In the case of FIG. 18, the user terminal 20A displays a dedicated driver setting screen depending on whether or not there is a fixed setting (step 402). FIG. 21 is a diagram illustrating the difference between the setting screens depending on whether or not fixed settings are present. If there is no fixed setting, the dedicated driver setting screen 260C corresponding to the printing device 30F (see FIG. 14) that was last logged in is displayed. This display is the same as in the first embodiment.

[0063] On the other hand, if there are fixed settings, the dedicated driver setting screen 260D (see FIG. 16) corresponding to the printing device 30C (see FIG. 14) for which the fixed settings have been enabled using the "Fixed" button 270 (see FIG. 16) is displayed. In this case, the dedicated driver setting screen 260D for which the fixed settings have been enabled is displayed regardless of the printing device 30F to which user A last logged in. Therefore, user A does not need to go to printing device 30C and log in to the cloud printing service in order to be able to read the dedicated driver setting screen 260D corresponding to printing device 30C from the “Dedicated Mode” button 266 (see FIG. 11).

[0064] Returning to the description of FIG. After the settings are made on the displayed setting screen 260C, the user terminal 20A accepts the operation of the print execution button 262 on the menu screen 260A (see FIG. 10) (step 112). Thereafter, the user terminal 20A transmits the print job to the server 10 (step 113). Meanwhile, the server 10 registers the received print job (step 114).

[0065] <Processing sequence 2> The display of the setting screen 260D described above can also be realized by a different processing sequence. 22 is a diagram illustrating another example of a processing sequence in which, after enabling the fixed settings on the setting screen 260D (see FIG. 16) of the dedicated driver corresponding to the printing device 30C, another printing device 30F logs in to the cloud printing service and further registers a print job. In FIG. 22, parts corresponding to those in FIG. 18 are denoted by the same reference numerals.

[0066] In the case of FIG. 22, the processing operations up to step 106 are the same as those in FIG. However, in FIG. 22, if it is confirmed in step 401 that a fixed setting exists, the common driver setting screen 260B (see FIG. 11) is displayed (step 109) without requesting the login list 14A (see FIG. 3) from the server 10, and then a switch to the dedicated driver setting screen is accepted (step 110).

[0067] In the case of FIG. 22, the fixed setting is "Yes", so the user terminal 20A displays the setting screen 260D of the dedicated driver corresponding to the printing device 30C for which the fixed setting is available (step 403). Thereafter, the user terminal 20A accepts operation of the print execution button 262 on the menu screen 260A (see FIG. 10) (step 112). Thereafter, the user terminal 20A transmits the print job to the server 10 (step 113). Meanwhile, the server 10 registers the received print job (step 114). In FIG. 22, if there is no fixed setting in step 401, the user terminal 20A executes the processing operations from step 107 onward in FIG. 15 in order.

[0068] <Summary> When the cloud printing system 1 (see FIG. 1) described in this embodiment is adopted, the user can display the dedicated driver setting screen corresponding to the printing device 30C for which fixed settings are enabled, instead of the dedicated driver setting screen corresponding to the printing device 30F for which the user last logged in, simply by operating the "dedicated mode" button 266. With this function, even if for temporary reasons you log in to the cloud printing service using a printing device 30F that is different from the printing device 30C that you normally use, you can immediately call up the settings screen for the dedicated driver corresponding to the printing device 30C by operating the "dedicated mode" button 266.

[0069] In the above-described system, there may be cases where a user wants to print using a function or prohibition that is supported by printing device 30F but not supported by printing device 30C. In this case, if the user temporarily disables the fixed settings for printing device 30C and then logs in to server 10 from printing device 30F, the user can easily access the settings screen for printing device 30F, the IP address and device name of which the user does not know. Furthermore, after a user has finished printing using printing device 30F, they can move back to printing device 30C and log in to the cloud printing service to call up the settings screen corresponding to printing device 30C, whose IP address and device name they do not know, and enable the fixed settings again.

[0070] However, this system requires the user to move the temporary print job to the regular print device 30C after the temporary print job has been completed. Therefore, from the common driver setting screen 260B (see Figure 11), it is possible to select between calling up the dedicated driver setting screen corresponding to the printing device 30F where the last login was performed, and calling up the dedicated driver setting screen corresponding to the printing device 30C where the fixed setting is enabled.

[0071] FIG. 23 is a diagram illustrating another example of the common driver setting screen 260B. In FIG. 23, parts corresponding to those in FIG. 11 are denoted by the same reference numerals. A "Fixed Mode" button 271 has been added to the setting screen 260B shown in FIG. The "Fixed Mode" button 271 here is a button for calling up a setting screen for a dedicated driver corresponding to the printing device 30C for which fixed settings are valid. The "dedicated mode" button 266 is a button for calling up a setting screen for the dedicated driver corresponding to the printing device 30F where the last login was performed.

[0072] By providing these two buttons, user A can freely select which setting screen to display. Therefore, even if you want to print on a regular printing device 30C after printing on a printing device 30F that supports special functions and prohibitions, you can call up the setting screen 260D of the dedicated driver that corresponds to the regular printing device 30C without having to log in to the cloud printing service again from the printing device 30C.

[0073] <Third Embodiment> In this embodiment, a modification of the first embodiment will also be described. Therefore, the cloud printing system 1 (see FIG. 1) assumed in the second embodiment is common to the cloud printing system 1 described in the first embodiment. Furthermore, the hardware configurations of the server 10 (see FIG. 1), user terminal 20 (see FIG. 1), and printing device 30 (see FIG. 1) assumed in the second embodiment are also the same as those in the first embodiment. The differences are in two points: the processing contents of the cloud print driver 24A (see FIG. 4) and the server cooperation application 24B (see FIG. 4), and the processing contents of the server 10.

[0074] <Explanation of processing operation> The following describes the processing operations executed in the cloud printing system 1 (see FIG. 1) assumed in the third embodiment.

[0075] <Up until the first print job registration> <Processing sequence> 24 is a diagram illustrating an example of a processing sequence for initial registration of a print job according to the third embodiment. In FIG. 24, parts corresponding to those in FIG. 7 are assigned the same reference numerals. In the processing sequence shown in FIG. 24, after updating the login list 14A (see FIG. 3), the server 10 inquires of the user about the generation of a dedicated icon in the printing device 30C (step 501). Upon receiving the inquiry, the printing device 30C displays the inquiry screen 350 (see FIG. 25) on the operation panel 35 (step 502).

[0076] FIG. 25 is a diagram illustrating an example of an inquiry screen 350 displayed on the operation panel 35. As shown in FIG. The inquiry screen 350 shown in FIG. 25 is composed of an inquiry statement 351, a “Yes” button 352, and a “No” button 353. In the case of Figure 25, query 351 displays "Do you want to generate an icon on the client to call this printing device?". User A, seeing this display, operates "Yes" button 352 or "No" button 353. Detection of operation of "Yes" button 352 is an example of a case where a predetermined condition is satisfied.

[0077] Returning to the explanation of FIG. The printing device 30C transmits a response to the inquiry to the server 10 (step 503). The server 10 updates the login list 14A in response to the response (step 504). Fig. 26 is a diagram illustrating an example of the data structure of the login list 14A used in the third embodiment. In Fig. 26, parts corresponding to those in Fig. 3 are assigned the same reference numerals. An icon generation setting 14A4 has been added to the login list 14A shown in FIG. In the case of FIG. 26, user A has set icon generation for printing devices 30C and 30F, but has not set icon generation for printing device 30D.

[0078] Returning to the explanation of FIG. In the present embodiment as well, after logging in to the cloud print service from the printing device 30C, the user terminal 20A accepts the selection of a print function from the document file menu (step 106). When the print function is selected, the user terminal 20A accesses the server through the server cooperation application 24B (see FIG. 4) and inquires about login information (step 107). In response to the inquiry, the server 10 returns the login list 14A (see FIG. 2) of the target user (step 108).

[0079] The user terminal 20A generates a dedicated icon for the printing device 30 for which an icon generation setting has been made, and displays it in the driver selection field 263 (step 601). 27 is a diagram illustrating a display example of a menu screen 260A in embodiment 3. In FIG. 27, parts corresponding to those in FIG. 10 are assigned the same reference numerals. 27, the icons for printing device 30C and printing device 30F, for which icon generation settings are available, have been added to driver selection field 263. Note that in Fig. 27, the icons and device names are displayed as a set. The icons corresponding to the specific printing devices 30C and 30F created in response to instructions from user A are placed directly below the icon corresponding to the common driver, as shown in FIG.

[0080] In this embodiment, the design, display color, and other display modes of the icons corresponding to the specific printing devices 30C and 30F are made distinguishable from the default icons, allowing the user to easily identify the icons corresponding to the printing devices 30C and 30F that the user has instructed to be generated. The two icons corresponding to the printing devices 30C and 30F are not generated at the same time, so it is possible to identify the correspondence between the newly added icons and the specific printing devices 30C and 30F.

[0081] Returning to the explanation of FIG. When a specific icon is selected, the user terminal 20A displays a setting screen for the corresponding dedicated driver (step 602). For example, when the icon corresponding to the printing device 30C is selected, the user terminal 20A displays a setting screen for the driver corresponding to the printing device 30C. Furthermore, when an icon corresponding to a common driver is selected, the user terminal 20A displays a common driver setting screen 260B (see FIG. 10). Thereafter, when the user terminal 20A accepts an operation of the print execution button 262 on the menu screen 260A (see FIG. 10) (step 112), it transmits a print job to the server 10 (step 113). Meanwhile, the server 10 registers the received print job (step 114).

[0082] <Summary> When the cloud printing system 1 (see FIG. 1) described in this embodiment is employed, it becomes possible for a user to easily find the icon of the printing device 30 that the user has instructed to create at a higher position in the driver selection field 263. For example, the icon that User A has instructed to create is placed directly below the icon corresponding to the common driver. Therefore, even if a large number of icons are displayed in the driver selection field 263, the user A can easily call up the setting screen for the driver corresponding to the printing device 30C or 30F that he or she wants to use.

[0083] In the above-described system, the icon generated in response to an instruction from user A is displayed in driver selection field 263, but it may also be displayed as one form of an operation button on common driver setting screen 260B. 28 is a diagram illustrating a display example of a common driver setting screen 260B in embodiment 3. In FIG. 28, parts corresponding to those in FIG. 10 are assigned the same reference numerals. The setting screen 260B shown in FIG. 28 has added a "Device C Icon" button 272, which is an icon for calling up a dedicated driver corresponding to printing device 30C, and a "Device F Icon" button 273, which is an icon for calling up a dedicated driver corresponding to printing device 30F. By adopting this display format, user A can easily distinguish between the icon that he or she has instructed to be generated and the icon that has been displayed in the driver selection field 263 from the beginning.

[0084] <Other embodiments> (1) Although the embodiments of the present invention have been described above, the technical scope of the present invention is not limited to the scope of the above-described embodiments. It is clear from the claims that various modifications and improvements to the above-described embodiments are also included in the technical scope of the present invention.

[0085] (2) In the above description of the embodiment, the server 10, the user terminal 20, and the printing device 30 are connected to the cloud network N, but these terminals may also be connected to a LAN (=Local Area Network).

[0086] (3) In the above-described embodiment, the login list 14A is requested from the server 10 when the print function is selected in the file menu. However, the login list 14A (see FIG. 3) may also be requested from the server 10 when the “dedicated mode” button 266 (see FIG. 11) is operated on the common driver setting screen 260B (see FIG. 11). That is, an inquiry requesting the login list 14A may be sent to the server 10 only when the user wishes to display the dedicated driver setting screen corresponding to the printing device 30 to which the user last logged in.

[0087] 29 is a diagram illustrating another example of a processing sequence relating to the initial registration of a print job. In FIG. 29, parts corresponding to those in FIG. 7 are assigned the same reference numerals. In the case of FIG. 29, steps 109 and 110 are executed after step 106 is executed, and then steps 107 and 108 are executed. That is, in FIG. 29, when an operation to switch to the dedicated driver setting screen is accepted on the common driver setting screen 260B, the user terminal 20A inquires about login information from the server 10, and the login list 14A of the target user is returned.

[0088] (4) In the above-described embodiment, in step 108 (see FIG. 7), the login list 14A is returned from the server 10 to the user terminal 20A, but it is also possible to notify only information that identifies the printing device 30 to which user A, who operates the user terminal 20A, last logged in. That is, even if there are multiple records of login dates and times linked to user A, as in the case of the additional login list 14A, it is also possible to notify only the device name and IP address corresponding to the last login.

[0089] (5) In the above-described embodiment, when user A instructs the creation of an icon at the stage of logging in to the cloud printing service, a dedicated icon is created to identify the printing device 30 currently being operated. However, the icon may be automatically created if the number or frequency of login operations exceeds a predetermined standard. Exceeding the standard here is an example of a case where a predetermined condition is satisfied.

[0090] (6) The processor in the above-described embodiments refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPUs (=Central Processing Units)) as well as dedicated processors (e.g., GPUs (=Graphical Processing Units), ASICs (=Application Specific Integrated Circuits), FPGAs (=Field Programmable Gate Arrays), programmable logic devices, etc.). Furthermore, the operations of the processor in each of the above-described embodiments may be performed by a single processor alone, or may be performed by multiple processors located in physically separate locations in cooperation with each other. Furthermore, the order in which the operations of the processors are performed is not limited to the order described in each of the above-described embodiments, and may be changed individually.

[0091] <Additional Notes> (((1))) An information processing system comprising a user terminal and a server that transmits print jobs registered from the user terminal to a printing device selected as an output destination, wherein the server notifies the user operating the user terminal of information identifying the printing device used to log in to a printing service in response to an inquiry from the user terminal, and the user terminal displays a first setting screen corresponding to the printing device identified by the information obtained from the server. (((2))) The information processing system described in (((1)))), wherein, when the user terminal receives a document printing operation, it displays a second setting screen common to multiple printing devices as an initial screen, and when it receives an operation to switch to the first setting screen on the second setting screen, it sends the inquiry to the server. (((3))) The information processing system described in (((2)))), wherein, if there is a setting to fix the setting screen to be displayed as the first setting screen, the user terminal displays the setting screen set as the fixed target after accepting the switching operation. (((4))) The information processing system according to any one of ((1))) to ((3))), wherein the user terminal transmits the inquiry to the server when a print operation for a document is received. (((5))) The information processing system according to any one of (((1))) to (((4))), wherein the user terminal generates an icon for calling up the first setting screen when a predetermined condition is satisfied. (((6))) An information processing system described in any one of (((1))) to (((5))), wherein when the server detects a new login to the printing service, it updates a combination list of the printing device used for the login and the user who logged in through that printing device. (((7))) The information processing system described in (((6))), wherein if there are multiple records of the printing device used to log in for the user corresponding to the inquiry, the server notifies the user terminal of information identifying the printing device corresponding to the last login. (((8))) The information processing system described in any one of (((1))) to (((7))), wherein when the server detects a new login from the printing device, it causes the printing device to display a screen inquiring about the generation of an icon for calling up the first setting screen corresponding to the printing device from which the login originated on the user terminal.

[0092] (((9))) A user terminal that registers a print job to a server by specifying a printing device as the output destination, the user terminal having one or more processors, wherein the one or more processors query the server for information identifying the printing device used by the user operating the user terminal to log in to a printing service, and displays a first setting screen corresponding to the printing device identified by the information obtained from the server. (((10))) A server that sends a print job registered from a user terminal to a printing device designated as the output destination, the server having one or more processors, wherein the one or more processors notify information identifying the printing device used by the user operating the user terminal to log in to the printing service in response to an inquiry from the user terminal. (((11))) A program for enabling a computer that functions as a user terminal that specifies a printing device as the output destination and registers a print job on a server to perform the following functions: querying the server for information identifying the printing device used by the user operating the user terminal to log in to the printing service; and displaying a first setting screen corresponding to the printing device identified by the information obtained from the server. (((12))) A program for enabling a computer that functions as a server that sends print jobs registered from a user terminal to a designated printing device as the output destination to notify the computer of information identifying the printing device used by the user operating the user terminal to log in to the printing service in response to an inquiry from the user terminal.

[0093] According to the information processing system of (((1))), even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the information processing system of (((2))), if the user wishes, the setting screen of the printing device that the user used to log in can be displayed. According to the information processing system of (((3))), even if a user has logged in to multiple printing devices, the user's desired setting screen can be displayed. According to the information processing system of (((4))), the setting screen corresponding to the printing device used by the user to log in can be displayed as the initial screen. According to the information processing system of (((5))), it is possible to easily read out the setting screen corresponding to the printing device that is the output destination by generating an icon corresponding to the printing device that the user used to log in. According to the information processing system of (((6))), a setting screen corresponding to one or more printing devices used by the user to log in can be displayed on the user terminal. According to the information processing system of (((7))), the setting screen corresponding to the printing device that the user last used to log in can be displayed on the user terminal. According to the information processing system of (((8))), it is easy to call up a setting screen corresponding to the printing device to which output is desired. According to the information processing system of (((9))), even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the gloss reading system of (((10))), even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the program (((11))), even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. According to the program (((12))), even if the user does not know the IP address or device name of the printing device to which the user wants to output a print job, the setting screen corresponding to the desired printing device can be easily displayed on the user terminal. [Explanation of symbols]

[0094] 1...cloud printing system, 10...server, 11, 21, 31...processor, 12, 22, 32...ROM, 13, 23, 33...RAM, 14, 24, 34...auxiliary storage device, 14A...login list, 15, 25, 39...communication interface, 20, 20A, 20B...user terminal, 24A...cloud print driver, 24B...server linkage application, 24C...fixed driver information, 26...display, 27...input device, 30, 30A, 30B, 30C, 30D, 30E, 30F...printing device, 35...operation panel, 36...scanner unit, 37...image processing unit, 38...printing unit

Claims

1. An information processing system including a user terminal and a server that transmits a print job registered from the user terminal to a printing device selected as an output destination, the server notifies, in response to an inquiry from the user terminal, information for identifying the printing device used by the user operating the user terminal to log in to the printing service; the user terminal displays a first setting screen corresponding to the printing device identified by the information acquired from the server; Information processing system.

2. The user terminal When a print operation for a document is received, a second setting screen common to the plurality of printing devices is displayed as an initial screen; When an operation to switch to the first setting screen is accepted on the second setting screen, the inquiry is sent to the server. The information processing system according to claim 1 .

3. The user terminal If there is a setting to fix the setting screen to be displayed as the first setting screen, after the switching operation is accepted, the operation screen set as the fixed target is displayed. The information processing system according to claim 2 .

4. The user terminal When a print operation for a document is received, the query is sent to the server. The information processing system according to claim 1 .

5. The user terminal generating an icon for calling the first setting screen when a predetermined condition is satisfied; The information processing system according to claim 1 .

6. The server When a new login to the printing service is detected, a list of combinations of the printing device used for the login and the user who logged in through the printing device is updated. The information processing system according to claim 1 .

7. The server If there are multiple records of the printing device used for login for the user corresponding to the inquiry, notify the user terminal of information identifying the printing device corresponding to the last login. The information processing system according to claim 6.

8. The server When a new login from the printing device is detected, a screen is displayed on the printing device inquiring about generation of an icon for calling the first setting screen corresponding to the printing device from which the login has originated on the user terminal. The information processing system according to claim 1 .

9. A user terminal that registers a print job to a server by specifying a printing device as an output destination, having one or more processors; the one or more processors: a user who operates the user terminal inquires of the server about information that identifies the printing device used to log in to the printing service; displaying a first setting screen corresponding to the printing device identified by the information acquired from the server; User terminal.

10. A server that transmits a print job registered from a user terminal to a printing device designated as an output destination, having one or more processors, the one or more processors: In response to the inquiry from the user terminal, the user operating the user terminal notifies the user of information identifying the printing device used to log in to the printing service. server.

11. A computer that functions as a user terminal that specifies a printing device as an output destination and registers a print job on a server, a function of inquiring of the server about information identifying the printing device used by the user operating the user terminal to log in to the printing service; a function of displaying a first setting screen corresponding to the printing device identified by the information acquired from the server; A program to achieve this.

12. A computer that functions as a server that transmits print jobs registered from a user terminal to a printing device designated as an output destination, A function of notifying, in response to an inquiry from the user terminal, information that identifies the printing device that the user operating the user terminal used to log in to the printing service. A program to achieve this.

Images