Communication terminal, communication terminal control method and program

Abstract

The object is to provide a mechanism that can simplify the setting of user information used in processing. A mobile terminal (102) can set user credentials used to log in to an image processing device and can transmit print data to the image processing device. The mobile terminal 102 performs display control to display a screen for accepting print settings for print data to be transmitted. In addition, in response to accepting a user instruction to display a screen for accepting authentication information settings as the screen for accepting print settings, the mobile terminal 102 controls to display a screen for accepting authentication information settings to be added to print data, which screen reflects the user credentials used for login.

Description

[Technical Field]

[0001] The present invention relates to a communication terminal that cooperates with an image processing device. [Background technology]

[0002] An image processing device provides a user with various functions such as a printing function, a copying function, and a file transmission function. When a user uses a function provided by an image processing device, the user needs to log in to the image processing device. A known method for a user to log in to an image forming device is to send a login request to the image forming device when a communication terminal such as a mobile terminal approaches the image processing device, thereby logging the user in to the image processing device (for example, see Patent Document 1).

[0003] Furthermore, there are image processing devices that can perform authentication printing from a security standpoint when printing based on print data received from an external device such as a PC (for example, Patent Document 2). In authentication printing, the external device generates print data including authentication information such as user authentication information, department ID, and password, and sends it to the image processing device. The image processing device determines whether the user authentication information or department ID and password added to the print data received from the external device matches the authentication information managed within the image processing device, and outputs the print data only if they match. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-66217 [Patent Document 2] Japanese Patent Application Laid-Open No. 2012-119003 Summary of the Invention [Problem to be solved by the invention]

[0005] In order to make it easier to use an image processing device from a communication terminal, it is conceivable that a vendor of the image processing device may provide a linking application for a communication terminal to link with the image processing device. Such a linking application may have multiple linking functions, such as a linking login function that allows a user to log in to the image processing device and a print function that sends print data to the image processing device.

[0006] Here, when enabling authenticated printing from a cooperative application, the user must operate the cooperative application on the communication terminal and set user authentication information as print settings to be added to the print data.

[0007] In this case, for example, even if the user has set user authentication information for login, the user must set user authentication information for authentication printing from the print setting screen, which is time-consuming.

[0008] The present invention has been made in consideration of at least one of the above problems, and one of its objectives is to provide a mechanism that can simplify the setting of authentication information required for authentication printing in a mobile terminal that communicates with an image processing device, using user information used for logging in.

[0009] Another object of the present invention is to provide a mechanism that can simplify the setting of user information used in processing. [Means for solving the problem]

[0010] In order to achieve at least one of the above objects, a mobile terminal of the present invention includes: a receiving means for receiving input of first authentication information from a user; a storage means for storing the first authentication information in response to the input of the first authentication information; The user logs in to the image processing device, and the user is able to use functions of the image processing device, including copy and send functions. memorya first transmitting means for transmitting the first authentication information to the image processing device by Bluetooth communication, and a second transmitting means for transmitting second authentication information and the print data to the image processing device in order to determine whether or not the image processing device executes printing based on the received print data, memory The first authentication information is automatically used as the second authentication information. [Effects of the Invention]

[0011] According to the present invention, it is possible to simplify the setting of authentication information required for authentication printing in a mobile terminal that communicates with an image processing apparatus by using user information used for logging in. Furthermore, according to the present invention, it becomes possible to simplify the setting of user information used in processing. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an overview of a printing system. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a communication terminal 102. [Figure 3] FIG. 2 is a diagram illustrating an example of a software configuration of a communication terminal 102. [Figure 4] FIG. 2 is a diagram illustrating an example of the hardware configuration of an MFP 101. [Figure 5] 10A and 10B are diagrams illustrating an example of a screen displayed on an operation unit of a communication terminal 102. [Figure 6] 10A and 10B are diagrams illustrating an example of a screen displayed on an operation unit of a communication terminal 102. [Figure 7] 10 is a flowchart showing the control of the communication terminal 102. [Figure 8] 10 is a flowchart showing the control of the communication terminal 102. [Figure 9] 10A and 10B are diagrams illustrating an example of a screen displayed on an operation unit of a communication terminal 102. [Figure 10] 10A and 10B are diagrams illustrating an example of a screen displayed on an operation unit of a communication terminal 102. [Figure 11] 10 is a flowchart showing the control of the communication terminal 102. [Figure 12] 10 is a flowchart showing the control of the communication terminal 102. [Figure 13] 10A and 10B are diagrams illustrating the correspondence between capability information and configuration information acquired from the MFP 101. [Figure 14] 10A and 10B are diagrams illustrating an example of a screen displayed on an operation unit of a communication terminal 102. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following describes embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0014] First Embodiment First, the configuration of a printing system according to the present invention will be described with reference to Fig. 1. The printing system according to this embodiment includes a communication terminal 102, an MFP (Multi Function Peripheral) 101, and an AP (Access Point) 103.

[0015] The communication terminal 102 is capable of performing wireless communication based on the IEEE 802.11 standard (hereinafter referred to as the 802.11 standard). When a user inputs an SSID (Service Set Identifier) ​​and a security key for connecting to the AP 103 into the communication terminal 102, the communication terminal 102 can connect to the network provided by the AP 103.

[0016] The MFP 101 is a multi-function device that has functions such as scanning, printing, and copying. When an SSID and a security key for connecting to the AP 103 are set as wireless network settings for the MFP 101, the communication terminal 102 and the MFP 101 can perform wireless communication via the AP 103. The MFP 101 can receive print data from the communication terminal 102 via wireless communication and perform printing.

[0017] Furthermore, from a security perspective, the MFP 101 of this embodiment can perform user authentication management assuming a user logs in. It can also perform department ID management, which restricts users based on a department ID and password. When a user is not logged in, the MFP 101 with user authentication management set to ON displays a login screen on the operation unit, rendering the MFP 101's functions unavailable. The MFP 101 determines whether to permit the user's login based on user authentication information (also referred to as user credentials) received from the user while the login screen is displayed. When the user's login is permitted, the MFP 101 displays a main screen (also referred to as a main menu) on the operation unit of the MFP 101. The user can use the MFP's functions, such as copy and send functions, via the main screen displayed on the operation unit. Hereinafter, in this embodiment, logging in a user and transitioning to a state in which the MFP's functions can be used via the MFP's operation unit is referred to as local login. When department management is set to ON, the MFP 101 prompts the user to enter a department ID and password on the login screen, determining whether to permit the user's login.

[0018] Furthermore, when printing based on print data received from an external device, the MFP 101 can also perform authentication printing from a security perspective. In authentication printing, the external device generates print data including authentication information such as user authentication information, department ID, and password, and sends the print data to the image processing device. The MFP 101 determines whether the user authentication information or department ID and password added to the print data received from the external device matches the authentication information managed within the image processing device, and outputs the print data only if they match.

[0019] The printing system of this embodiment also includes a mobile linking function that provides functions to users by linking the communication terminal 102 and the MFP 101. For example, a user who owns the communication terminal 102 can execute a linked login function that logs a specific user into the MFP 101 by bringing the communication terminal 102 close to the MFP 101. The communication terminal 102 can perform data communication with the MFP 101 using short-range wireless communication. For example, the communication terminal 102 performs data communication related to the linked login using short-range wireless communication.

[0020] The communication terminal 102 communicates with the MFP 101 via the AP 103. For example, the communication terminal 102 can send and receive print data and scan data to the MFP 101 via the AP 103. Here, the communication terminal 102 can also generate print data including authentication information so that printing can be performed on an MFP that performs authentication printing, and transmit the generated print data to the MFP.

[0021] The MFP 101 can also operate in access point mode. When operating in access point mode, the MFP 101 operates as a software access point. By connecting to a software AP provided by the MFP 101, the communication terminal 102 can perform direct wireless communication with the MFP 101 without going through a relay device such as the AP 103. By connecting to the MFP 101 using direct wireless communication with the MFP 101, the communication terminal 102 can perform various linking functions without going through the AP 103.

[0022] In this embodiment, a smartphone and a tablet PC (Personal Computer) are used as examples of communication terminals, but the present invention is not limited to these. A smartphone and a tablet PC are examples of communication terminals capable of performing short-range wireless communication, and other devices may also be used.

[0023] In addition, in this embodiment, an MFP is used as an example of an external device that cooperates with a communication terminal, but the present invention is not limited to this. For example, the present invention can be applied to a single-function printer or a 3D printer that forms a three-dimensional object.

[0024] <Communication terminal> Next, the hardware configuration of the communication terminal 102 will be described with reference to Fig. 2. A CPU (Central Processing Unit) 111 included in the control unit 110 reads out a control program stored in a ROM (Read Only Memory) 112 or storage 114 to control the communication terminal 102.

[0025] The control unit 110 includes a CPU 111, a ROM 112, a RAM (Random Access Memory) 113, a storage 114, an operation unit I / F 115, and a camera I / F 117, all connected via a bus. The control unit 110 also has a wireless LAN I / F (interface) 122 and a Bluetooth (registered trademark) I / F 123 as communication interfaces for communicating with external devices. In this embodiment, the wireless LAN I / F 122 and the Bluetooth I / F 123 are described as separate pieces of hardware, but this is not limiting. A combo chip that realizes both wireless LAN communication and Bluetooth short-range wireless communication with a single piece of hardware may be mounted to realize wireless LAN communication and Bluetooth short-range wireless communication.

[0026] The CPU 111 is a central processing unit (processor) that controls the overall operation of the control unit 110. The RAM 113 is a volatile memory that is used as a work area and a temporary storage area for expanding various control programs stored in the ROM 112 and storage 114. The ROM 112 is a nonvolatile memory that stores a boot program for the communication terminal 102 and the like. The storage 114 is a nonvolatile flash memory with a larger capacity than the RAM 113. The storage 114 stores a control program for the communication terminal 102. In addition, an OS (Operating System) 300 and a cooperative application 310, which will be described later, are also stored in the storage 114.

[0027] When the communications terminal is started up, the CPU 111 executes a boot program stored in the ROM 112. This boot program reads out the OS 300 program stored in the storage 114 and expands it on the RAM 113. After executing the boot program, the CPU 111 subsequently executes the OS 300 program expanded on the RAM 113, thereby controlling the communications terminal 102. The CPU 111 also stores data used for operations according to the control program on the RAM 113 and reads and writes the data.

[0028] In the communication terminal 102, a single CPU 111 executes each process shown in the flowcharts described below, but other configurations are also possible. For example, multiple CPUs or microprocessors (MPUs) can cooperate to execute each process shown in the flowcharts described below. Also, some of the processes can be executed using hardware circuits such as an ASIC (Application Specific Integrated Circuit). Also, some of the processes, such as generating a print preview or print data, can be executed in cooperation with a cloud service accessible via a network.

[0029] The operation unit I / F 115 connects the operation unit 116 and the control unit 110. The operation unit 116 is equipped with a touch panel capable of detecting a user's touch operation and a display panel that displays various screens. The operation unit 116 functions as a display unit that displays information and a reception unit that receives user instructions. Various screens provided by the OS 300 and the cooperative application 310 are displayed on the operation unit 116. The user can also input desired operation instructions to the communication terminal 102 by performing a touch operation on the operation unit 116 using an object such as a finger. The operation unit 116 is also equipped with hardware keys. The user can also input operation instructions to the communication terminal 102 by pressing the hardware keys.

[0030] The camera I / F 117 connects the control unit 110 to the camera 118. The camera 118 takes an image in response to an image capture instruction from the user. The photograph taken by the camera 118 is stored in a predetermined area of ​​the storage 114.

[0031] The wireless LAN I / F 122 provides a wireless client function for performing wireless communication conforming to the 802.11 standard. The wireless LAN I / F 122 also connects to an external AP to perform wireless communication conforming to the 802.11 standard. The external AP may be the MFP 101 operating in access point mode or the AP 103.

[0032] The Bluetooth I / F 123 is an interface for transmitting and receiving data to and from various peripheral devices via short-range wireless communication. In this embodiment, as an example, wireless communication compliant with Bluetooth (IEEE802.15.1), particularly Bluetooth Low Energy (hereinafter referred to as BLE), is used to execute a linked login function that logs a specific user into the MFP 101.

[0033] <Software Configuration of Communication Terminal 102> Next, the software configuration of the communication terminal 102 will be described with reference to Fig. 3. Fig. 3 is a functional block diagram of software that is implemented when the CPU 111 reads out a control program stored in the ROM 112 or storage 114.

[0034] The OS 300 is basic software for controlling the overall operation of the communication terminal 102 . The OS 300 is configured, for example, with Android (registered trademark) provided by Google Inc. or iOS (registered trademark) provided by Apple Inc. Various application programs can be installed in the communication terminal 102, including a cooperative application 310 described below. The OS 300 exchanges information with these applications and can change the screen displayed on the operation unit 116 according to instructions received from the applications.

[0035] The OS 300 has a framework and API for controlling the hardware of the communication terminal 102 from various applications, and provides functions for using various hardware to applications running on the OS 300. The OS 300 also controls 802.11-compliant wireless communication via the wireless LAN I / F 122 and short-range wireless communication via the Bluetooth I / F 123 according to instructions received from the applications.

[0036] The cooperative application 310 can call a function provided by the OS as an API or a framework for applications, and switch the AP to which the communication terminal 102 connects to an AP for direct connection provided by the MFP, for example.

[0037] The cooperation application 310 can store, as internal information, settings used in the cooperation function and a device list of cooperation destination MFPs. The device list stores management information for managing cooperation destination MFPs, including the device name of the external device, capability information, and connection information for connecting to the external device. The cooperation application 310 can register an external device such as an MFP in the device list by accepting a user's MFP search process or manual input. Furthermore, when the cooperation application 310 accepts a user operation to select an MFP registered in the device list from a selection screen (not shown), it changes the cooperation destination MFP to the selected MFP.

[0038] <mfp> Next, we will explain the MFP 101. Figure 4 is a block diagram showing the hardware configuration of the MFP 101. The MFP 101 has a reading function for reading an image and a printing function for printing an image on a sheet.

[0039] Control unit 130 including CPU 131 controls the overall operation of MFP 101. CPU 131 reads out a control program stored in ROM 132 or storage 134 to perform various types of control such as print control and read control. ROM 132 stores control programs executable by CPU 131. RAM 133 is the main storage memory of CPU 131, and is used as a work area or a temporary storage area for expanding commands of various control programs. The storage 134 is a storage unit that stores print data, image data, various programs, and various setting information. The storage 134 also stores an authentication management database used for user authentication management and department ID management. The authentication management database stores user credentials stored for user authentication management and combinations of department IDs and passwords stored for department ID management.

[0040] In the MFP 101 of this embodiment, one CPU 131 uses one memory (RAM 133) to realize the control described below, but other configurations are also possible. For example, the control described below can be executed by having multiple processors, RAMs, ROMs, and storages work together.

[0041] The operation unit I / F 135 connects the operation unit 136 to the control unit 130. The operation unit 136 is equipped with a liquid crystal display unit with a touch panel function, various hard keys, and the like, and functions as a display unit that displays information and a reception unit that receives user instructions. The reading unit I / F 137 connects the reading unit 138 to the control unit 130. The reading unit 138 reads an original and generates a read image. The generated read image is sent to an external device or used for printing. The printing unit I / F 139 connects the printing unit 140 to the control unit 130. The printing unit 140 prints an image on a sheet based on print data received from an external device.

[0042] The control unit 130 is also connected to a network (not shown) via a wired LAN I / F 141. The wired LAN I / F 141 transmits images and information to external devices on the network (not shown), and receives print data and information from external devices. The control unit 130 also includes a wireless LAN I / F 142 and a Bluetooth I / F 143. The wireless LAN I / F 142 provides a wireless client function for connecting to an external AP and performing wireless communication, and a software AP function in which the MFP 101 acts as an AP. The Bluetooth I / F 143 is an interface for transmitting and receiving data to and from various peripheral devices via short-range wireless communication. The MFP 101 of this embodiment communicates with the communication terminal 102 using short-range wireless communication compliant with BLE, and executes a linked login function that logs a user into the MFP 101 using the communication terminal 102.

[0043] <External linkage function> Next, we will explain the cooperative functions provided by the cooperative application 310. The cooperative application 310 has multiple cooperative functions, such as a cooperative login function that logs a user into the MFP and a print function that sends print data to the MFP.

[0044] In this embodiment, to realize the federated login function, user authentication information for federated login can be set in the federated application 310. The set user authentication information for federated login is stored in the storage 114 and is referenced as needed when the federated login function is executed or in steps of the flowcharts described later. Also, in this embodiment, to enable authenticated printing from the federated application 310, user authentication information can be set as print settings to be added to print data. The set user authentication information as print settings is stored in the storage 114 and is referenced as needed in steps of the flowcharts described later.

[0045] Here, a user who wants to use both authenticated printing using the print function and local login using the linked login function must set both user authentication information for the linked login function and user authentication information as print settings, which is time-consuming.

[0046] In consideration of the above problems, this embodiment performs control that was not fully taken into account in conventional communication terminal and MFP collaboration, thereby enabling the MFP to simplify the setting of authentication information required for authentication processing using user information used for login collaboration.

[0047] 5 and 6 are examples of screens displayed on the operation unit 116 of the communication terminal 102. The screens shown in Fig. 5(A) to (B) and Fig. 6(A) to (B) are examples of screens displayed by the cooperative application 310.

[0048] When an icon of an integrated application is selected by a user operation via an application list screen (also called a drawer) or a home screen of the communication terminal 102, the CPU 111 starts the integrated application 310. When the start-up process is completed, the integrated application 310 displays the top menu screen shown in FIG. 5(A) on the operation unit 116 of the communication terminal 102.

[0049] First, using the top menu screen, we will explain the functions of the cooperative application 310. An icon 501 is an icon used when displaying a menu bar for checking application settings, help, information, and the like.

[0050] Area 502 displays the currently selected MFP as a linked destination. In this embodiment, a case where MFP 101 is specified as the linked destination is illustrated as an example. By selecting area 502, the user can change the linked MFP or check the status and capabilities of the linked MFP. Add key 503 is a key that provides a function for registering a new MFP as a linked destination. The user can use add key 503 to register a new MFP as a linked destination. The linked application 310 stores information about the MFP that has been instructed by a user operation to be registered as a linked destination in storage 114 as a device list. An MFP registered in the device list can thereafter be selected as a linked MFP.

[0051] The cooperative application 310 can execute various cooperative functions in cooperation with an MFP (e.g., MFP 101) designated as a cooperative destination. The document key 504 is a key used when sending image data or document data stored in the communication terminal to the cooperative destination MFP and printing it. The scan key 505 is a key used when executing a scan cooperative function that scans an original in the cooperative destination MFP and imports the scanned data into the storage 114 of the communication terminal. The capture key 506 is a key used when capturing an image of a document, whiteboard, etc. using the camera 118. The panel login key 507 is a key used when executing a cooperative login function that logs a specific user into the MFP.

[0052] Next, the setting of user authentication information for the login function, which is required to use the linked login function, will be described. When communication terminal 102 detects that icon 501 has been selected by the user, it displays a menu bar (not shown). When the user performs an operation to set up an app from the menu bar, the screen transitions to a setting screen for linked application 310.

[0053] The cooperative application 310 has many setting items. Therefore, it is difficult to configure all settings on the same screen. Therefore, a transition to a separate setting screen is made for each setting item or function, and individual settings are configured. When a user performs a setting operation for the cooperative login function from the setting screen, the communication terminal 102 displays a setting screen for user authentication information for login.

[0054] FIG. 5(B) shows an example of a screen for setting user authentication information for login. A user can set user information to be used in the federated login function via the screen shown in FIG. 5(B). 511 denotes an item for setting user credentials to be used in the federated login function. A user can select each item to set user authentication information (user name, password, and domain name). The set user authentication information is stored in the storage 114 and is referenced as appropriate in the flowchart described below. Toggle button 512 is a toggle button for setting whether or not to use the same user information when printing. When a user instruction to change the toggle button to ON is received, the communication terminal 102 changes the handover setting to enabled. When the toggle button is set to OFF, the handover setting is changed to disabled.

[0055] When the takeover settings are enabled, it becomes possible to take over the user authentication information set in item 511 as authentication information as print settings in the print function, which is a linked function separate from the login function (details will be described later). When detecting that the Complete button has been selected, the CPU 111 stores the user authentication information set in item 511 and the takeover settings changed by operating the toggle button in the storage 114. The settings stored in the storage 114 will be referred to as appropriate in the flowcharts described later.

[0056] Next, the print function will be described. When CPU 111 detects that document key 504 has been selected by the user, the display transitions to a document selection screen. FIG. 6A shows an example of the document selection screen displayed after the document key has been selected. The selection screen shown in FIG. 6A displays a list of documents held on communication terminal 102. When CPU 111 detects that information indicating a document, such as item 601 displayed on the selection screen, has been selected, the display transitions to a preview screen on operation unit 116. FIG. 6B shows an example of the preview screen. CPU 111 displays a preview image in area 611 of the preview screen, allowing the user to confirm the print content. The preview image displayed in area 611 is generated based on document data selected on the selection screen. The preview image may be generated by CPU 111, or may be generated by requesting a cloud service (not shown) to generate the preview image.

[0057] Area 613 is an area that displays print settings that are set for print data to be sent to the MFP. Area 613 also functions as a display item for transitioning to a print setting screen. By selecting area 613, the user can make detailed print settings. On the print setting screen, it is possible to set print settings such as the output paper size and number of copies, as well as authentication information to be used for authenticated printing. A print key 614 is a key used when printing a selected document.

[0058] Next, specific control for simplifying the setting of authentication information required for authentication processing using user information used for login federation will be described with reference to the flowcharts of FIGS. 7 and 8 are flowcharts showing the control of the communication terminal 102. FIG.

[0059] 7 and 8 are realized by the CPU 111 reading into the RAM 113 a program for implementing each control module stored in the ROM 112 or the storage 114 and executing the program. Note that the processing shown in the flowcharts is realized mainly by the cooperative application 310 in cooperation with the OS 300, which is a control program. Note that when clearly indicating the control program that is the main driver of each operation, each operation will be described with the OS 300 or the cooperative application 310 as the main driver.

[0060] FIG. 8 is a flowchart showing the operation of the communication terminal 102 when an icon of a cooperative application is selected via the drawer or home screen of the communication terminal 102.

[0061] In S701, CPU 111 displays a top menu screen on operation unit 116. In S702, CPU 111 determines whether a user instruction to use the linked login function has been accepted. If a user instruction to use the linked login function has been accepted, the process proceeds to S703; if a user instruction to use the linked login function has not been accepted, the process proceeds to S704. A user operation to use the linked login function is, for example, an operation to select key 507 displayed on the top menu screen in FIG. 5(A).

[0062] In S703, the CPU 111 executes a federated login process for the MFP. Specifically, when the CPU 111 detects that it has approached the MFP 101 based on the radio wave strength of the BLE communication or the like, it communicates with the MFP via short-range wireless communication and transmits a login request. The login request includes user authentication information for the federated login function stored in the storage 114. The MFP 101 determines whether to permit the user's login based on the login request received from the communication terminal. Note that the MFP 101 that has permitted login from the communication terminal displays a main screen (not shown) on the operation unit 136. The user can use each function of the MFP 101 (such as a copy function or a scan data transmission function) via the main screen displayed on the operation unit 136.

[0063] In this way, the user can log in to the MFP 101 simply by bringing the communication terminal 102 close to the MFP 101. This function allows the user to log in to the MFP simply by holding their own communication terminal over the MFP. This reduces the effort required to enter a user ID and password when logging in to the MFP. Note that, although the present embodiment uses local login as an example of the linked login function, the linked login function is not limited to this. For example, the linked login function may be a login (referred to as remote login) for realizing remote access for accessing resources provided by the MFP 101 from the communication terminal 102.

[0064] In S703, when the linked login process is completed, the CPU 111 changes the screen displayed on the operation unit 116 to the top menu screen, and the process returns to S701.

[0065] In S704, CPU 111 determines whether a user instruction to use the print function has been accepted. If a user instruction to use the print function has been accepted, the process proceeds to S705. If a user instruction to use the print function has not been accepted, the process proceeds to S706. A user operation to use the print function is, for example, an operation of selecting key 504 displayed on the top menu screen of FIG. 5(A).

[0066] In S705, the CPU 111 executes print processing to transmit print data to the MFP 101. Details of the print processing will be described later with reference to the flowchart in FIG.

[0067] Next, in S706, CPU 111 determines whether an instruction to terminate the application has been received. If an instruction to terminate the application has been received, CPU 111 stops execution of cooperative application 310, transitions the screen displayed on operation unit 116 to a home screen provided by the home application of OS 300, and ends the series of control. On the other hand, if an instruction to terminate the application has not been received, the process returns to S701.

[0068] Although not described in the flowchart of FIG. 7, when the CPU 111 receives a user instruction to use another function, it executes the other function based on the user instruction. For example, the CPU 111 can execute a scan cooperation function in which the MFP 101 and the communication terminal 102 cooperate to scan a paper document and transmit or save it. Also, for example, the CPU 111 can execute an imaging function using the camera 118.

[0069] In this way, with the cooperative application 310 running, the user can execute various functions including the cooperative login function and the printing function.

[0070] Next, the print processing will be described with reference to the flowchart in Fig. 8. In S800, CPU 111 accepts a document selection and displays a preview screen of the document whose selection has been accepted.

[0071] In S801, the CPU 111 determines whether a print setting instruction has been received. If a print setting instruction has been received, the process proceeds to S802. If a print setting instruction has not been received, the process proceeds to S812. The print setting instruction is, for example, a user instruction to select the area 613 illustrated in FIG. 6B.

[0072] In S802, the CPU 111 displays a print setting screen. Fig. 9 is a diagram showing an example of a screen displayed on the operation unit 116 of the communication terminal 102. Figs. 9(A) to 9(D) show examples of screens related to the print function, and Fig. 9(A) shows an example of the print setting screen.

[0073] A user can edit various print settings via the print setting screen. Items 901 and 902 are print setting items. Item 901 is an item selected when setting authentication information for authenticated printing as a print setting. When the CPU 111 receives the selection of item 901, it displays an authentication function management screen, an example of which is shown in FIG. 9B.

[0074] The user can select the authentication method to be used when sending print data via the management screen. Figure 9(B) shows an example in which user authentication that adds user authentication information to print data is selected.

[0075] "Do not use" is the key to select when not using authentication printing. "Department ID Management" is the key to use when assigning a department ID and password to the print data to be sent. The user uses the department ID management key when changing the settings to perform authentication printing using a department ID.

[0076] The user authentication key 912 is a key used when assigning user authentication information to print data to be transmitted. When the CPU 111 detects that the user authentication key 912 has been selected, it switches the screen displayed on the operation unit 116 to a setting screen for setting user authentication information. FIG. 9C illustrates an example of the setting screen for setting user authentication. The user can set a username 921 and a password 922 to be used for authentication printing via the setting screen. Furthermore, the user can set whether or not to confirm the authentication setting when printing via a toggle button 923. When the communication terminal 102 receives a user instruction to change the toggle button to ON, it changes the confirmation setting to enabled. Furthermore, when the toggle button is set to OFF, it changes the confirmation setting to disabled. When the confirmation setting is enabled, it becomes possible to perform a confirmation process when printing (details will be described in steps S805 and S806). The changed confirmation setting is stored in the storage 114 and is referred to as appropriate in the flowcharts described below.

[0077] Furthermore, an output method key 901 is a key used when changing the output format. When the CPU 111 detects that the key 901 has been selected, the screen displayed on the operation unit 116 transitions to a selection screen for selecting an output format, as shown in FIG. 9D. FIG. 9D illustrates an example in which print is selected. A user name 931 and a domain name 932 can be set on the output method selection screen. These settings are used to count the number of prints per user and to identify the print queue when performing reservation printing. As such, as shown in FIGS. 9C and 9D, there are cases in which user authentication information and information identifying the user are set in the print settings set for print data. Steps S803 and subsequent steps will explain a mechanism for simplifying the setting of user authentication information and information identifying the user in these cases.

[0078] 8, in S803, CPU 111 determines whether an instruction to display a print setting screen having input fields for user information has been given. If an instruction to display a screen having input fields for user information has been given, the process proceeds to S804. If an instruction to display a screen having input fields for user information has not been given, the process proceeds to S812. Note that an instruction to display a screen having input fields for user information is a user instruction to transition to a screen requiring input of user information, such as items 912 and 902 in FIG. 9.

[0079] In S804, the CPU 111 determines whether or not a setting has been made to carry over login user information to printing. If the carry-over setting has been enabled, the process proceeds to S806, and if the carry-over setting has not been enabled, the process proceeds to S805. In S805, the CPU 111 acquires user information stored for print settings.

[0080] In S806, the CPU 111 acquires user authentication information for login stored in the storage 114. In S807, the CPU 111 determines whether or not user authentication information has been set based on the user authentication information acquired in S906. If the user authentication information has been set, the process proceeds to S909. If the user authentication information has not been set (for example, if the acquired user authentication information is blank or NULL), the process proceeds to S808. In S808, the CPU 111 acquires the terminal name set in the OS 300 as user information. Specifically, the cooperative application 310 calls a function for acquiring the terminal name of the communication terminal 102 and queries the OS 300 about the terminal name. In response to the query, the OS 300 returns the terminal name to the cooperative application 310. Note that, in this embodiment, the terminal name is used as an example, but this is not limiting. For example, the account name of the terminal owner may be acquired.

[0081] In step S809, the CPU 111 displays a screen reflecting the acquired user information. First, a case where login user authentication information is acquired will be described. In this case, as illustrated in FIGS. 9C and 9D, the user information set in FIG. 5B is reflected. Therefore, when a print setting screen having a field for displaying user information is displayed, it is possible to reflect login user information used in another linkage function. This eliminates the need for the user to set the same user information (user name, password, domain name) in multiple places, thereby simplifying the setting. Furthermore, when login user authentication information is not set, the terminal name, the account name of the terminal owner, and the like can be acquired and reflected. Furthermore, if the handover setting is disabled, it is possible to intentionally prevent handover.

[0082] In S810, CPU 111 determines whether a completion instruction has been received. If a completion instruction has been received, the process proceeds to S911. If a completion instruction has not been received, the process waits for a user operation. The completion instruction is, for example, a user instruction to select a display item displayed in the upper left of the screen to return to the previous screen.

[0083] In S811, the CPU 111 updates the user information for print settings. It is assumed that the user information for print settings is stored in the storage 114. When the print settings on the screen including the user information settings described in S804 to S811 are completed, the CPU 111 returns to S802 and waits for acceptance of other print settings.

[0084] Next, in S812, CPU 111 determines whether a print instruction has been received. If a print instruction has been received, the process proceeds to S813. If a print instruction has not been received, the process returns to S801. Note that a print instruction may be received, for example, by pressing print key 614 as illustrated in FIG. 6B. Note that it is also possible to determine that a print instruction has been received in other ways. For example, it may be determined that a print instruction has been received when MFP 101 and communication terminal 102 come close to each other while the screen of FIG. 6B is displayed. It may also be determined that a print instruction has been received when communication terminal 102 detects a shake gesture or the like while the screen of FIG. 6B is displayed.

[0085] In S813, the CPU 111 determines whether to perform confirmation before transmission. If the print setting requiring authentication has been configured and the confirmation setting has been set to valid, the CPU 111 proceeds to S814. On the other hand, if the print setting requiring authentication has not been configured or if the print setting requiring authentication has been configured but the confirmation setting has been set to invalid, the CPU 111 skips S814 and proceeds to S815.

[0086] 10 shows an example of a confirmation screen displayed by the cooperative application 310 on the operation unit 116 of the communication terminal 102. In step S815, the CPU 111 displays a confirmation screen for the user authentication information.

[0087] The user can confirm the user authentication information via the confirmation screen. The user can also modify the user authentication information via the confirmation screen. For example, if the user ID 1001 has been set but the password 1002 has not been set in advance, the user can enter the password via this screen. When the CPU 111 receives a user instruction to complete the confirmation, the process proceeds to step S815.

[0088] In S815, CPU 111 generates print data based on the print settings and the data of the document selected in S800. When the generation of the print data is complete, the print data is sent to the linked MFP, and the series of processes ends. In this embodiment, the print data is sent to the linked MFP using wireless communication compliant with IEEE 802.11. The print data may be transmitted wirelessly via AP 103, or may be transmitted wirelessly via a software AP provided by MFP 101. Alternatively, direct wireless communication using Wi-Fi Direct (registered trademark) may be established to transmit the print data via P2P wireless communication, or the print data may be transmitted via P2P wireless communication using Wi-Fi Aware (registered trademark).

[0089] If the print settings are configured to include user authentication information in the print data, the print data will include the user authentication information (user ID and password).If the print settings are configured to include a department ID in the print data, the print data will include the department ID and password.

[0090] As described above, in this embodiment, the setting of authentication information required for authenticated printing can be simplified by using user information used for login federation in a mobile terminal that is linked to an image processing apparatus. In addition, because it is possible to set whether to enable the handover setting, it is also possible to operate the image processing apparatus so that user authentication information for login federation is not inherited.

[0091] In this embodiment, the case where the user authentication information for login federation is taken over at the timings shown in S804 to S808 is illustrated, but the present invention is not limited to this. For example, at the timing when the setting of user authentication information for login linkage is completed, the user authentication information as print settings and the information indicating the user may be overwritten and updated. In this case, the CPU 111 makes the same determination as in S804 at the timing when the completion key is selected via the setting screen illustrated in FIG. 5(B). When the carry-over setting is not set to be effective, control is performed so as not to overwrite the user information as print settings. On the other hand, when the carry-over setting is set to be effective, the CPU 111 overwrites and updates the user authentication information as print settings and the information indicating the user stored in the storage 114 based on the user authentication information acquired in S807 or S808. Thus, the user authentication information as print settings can also be updated at the timing when the update of the user authentication information for login linkage is performed. When adopting the above update form, the CPU 111 reads out the user authentication information as print settings and the information indicating the user stored in the storage 114 and reflects them on the setting screen in accordance with receiving an instruction to transition to a screen having an input item for user information.

[0092] <Second Embodiment> Next, a second embodiment of the present invention will be described. In the first embodiment, an example of carrying over the user authentication information for the linked login function to the print settings of the printing function has been described. In the second embodiment, in addition to the control of the first embodiment, control based on the capability information of the linked MFP will be described. Based on the authentication function supported by the MFP and the settings related to the authentication function of the MFP, control is performed so as to appropriately switch the display UI regarding authentication printing when performing print settings.

[0093] In the second embodiment, the hardware configuration of the prerequisite device is the same as that of the first embodiment. For the same configuration as that of the first embodiment, detailed description will be omitted.

[0094] <Acquisition Process of MFP Capability Information> First, acquisition of the MFP's capability information and change of the linked MFP will be described. As described above, the communications terminal 102 stores in the storage 114 a device list that stores management information of MFPs that are to be linked.

[0095] The communications terminal 102 acquires the capability information of the MFP when registering a new MFP as a collaboration destination, when receiving a user instruction to update the capability information of a registered collaboration destination to the latest state, or in other cases. The acquired capability information of the MFP 101 is stored in a device list. The communications terminal 102 acquires, as capability information, printing capabilities such as output paper size, color / monochrome settings, and the presence or absence of a post-processing function, as well as information on the MFP's user management functions. In this embodiment, the information on the user management functions acquired as capability information from the MFP is used to appropriately switch the display UI related to authentication printing.

[0096] Specific control will be described using the flowcharts of Figures 11 and 12. Each operation (step) shown in the flowcharts of Figures 11 and 12 is realized by the CPU 111 reading into the RAM 113 a program for realizing each control module stored in the ROM 112 or storage 114 and executing the program.

[0097] 11 is a flowchart for explaining the control in communication terminal 102 when an event occurs that requires switching the display UI. For example, in this embodiment, when a new MFP is registered as a collaboration destination, the configuration information for configuring the display UI is updated based on capability information acquired from the new MFP. Also, when a user instruction to update the collaboration destination capability information to the latest state is received, the capability information is acquired again from the MFP, and the configuration information for configuring the display UI is updated. Also, when an instruction to change the collaboration destination is received, the configuration information for configuring the display UI is updated based on the capability information of the MFP that will become the collaboration destination after the change.

[0098] In S1101, the CPU 111 determines whether an instruction to acquire or update management information has been received. If an instruction to acquire or update management information has been received, the process proceeds to S1102, and if an instruction to acquire or update management information has not been received, the process proceeds to S1103.

[0099] In S1102, the CPU 111 acquires capability information from the destination MFP and stores the acquired capability information in the device list. In addition to the capability information, the processing of S1102 also acquires the name of the MFP, connection information for connecting to the MFP, and the like.

[0100] Meanwhile, in S1103, it is determined whether a user instruction to change the MFP to be the linked destination has been accepted. If a user instruction to change the MFP to be the linked destination has been accepted, the process proceeds to S1104. On the other hand, if a user instruction to change the MFP to be the linked destination has not been accepted, the CPU 111 ends the process without updating the configuration information of the display UI.

[0101] In S1104, the CPU 111 changes the MFP to be the cooperation destination, and acquires the capability information of the changed MFP from the device list.

[0102] In S1105, the CPU 111 extracts information related to the authentication function from the capability information acquired in S1102 or S1104. When the extraction is complete, the process proceeds to S1106.

[0103] In S1106, the CPU 111 updates the configuration information based on the capability information related to the authentication function extracted in S1105. The specific processing in S1106 will be described with reference to the flowchart in FIG.

[0104] In S1201, CPU 111 checks the authentication functions supported by the MFP based on the extracted capability information related to the authentication functions. Fig. 13 is a diagram for explaining the correspondence between the acquired capability information and configuration information. There are various types of MFPs with which cooperation is supported by cooperation application 310, and the authentication functions supported by each MFP differ. These can be classified, as shown in information 1301, into (1) MFPs that support both department ID management and user authentication management, (2) MFPs that support only department ID management, and (3) MFPs that do not support any authentication function. In Fig. 13(A), whether or not an MFP supports an authentication function is indicated by "supported" or "not supported."

[0105] Furthermore, even if an MFP supports the authentication management function, whether or not to enable the authentication management function depends on the MFP's operational policy. Information 1302 indicates that the function is enabled as "ON" and that the function is not enabled (disabled) as "OFF." In the following steps, the configuration information for displaying the UI of the print setting screen is updated depending on which of these combinations the acquired capability information corresponds to.

[0106] Information 1303 shows information for explaining the configuration information. "○" indicates that the item is displayed so that it can be selected by the user, and "-" indicates that it is not displayed as an item. Also, "*" indicates which item is to be selected as the initial value.

[0107] 13B as configuration information in storage 114. Bit 1304 indicating whether each item is to be displayed and bit 1305 indicating an initial value are stored as configuration information. Updating of the configuration information will be described using steps S1012 and onwards.

[0108] In S1202, CPU 111 determines whether the MFP supports the authentication function based on the result of S1201. If the MFP supports any of the authentication functions, the process proceeds to S1205. If the MFP does not support any of the authentication functions, the process proceeds to S1203.

[0109] In S1203, the CPU 111 changes the initial value of the configuration information 1305 stored in the storage 114 to not be used (i.e., to 0b00). In S1204, the CPU 111 updates the configuration information 1304 so that it becomes configuration information that hides all items (i.e., updates it to 0b000). When the processing of S1204 is completed, the CPU 111 ends the series of configuration information update processes.

[0110] This processing causes communication terminal 102 to perform different control when displaying the print setting screen. A specific example will be described with reference to FIG. 14. FIG. 14 is an example of a screen displayed on operation unit 116 of communication terminal 102, and shows an example of the screen display based on configuration information. FIG. 14(A) shows an example of the screen displayed when the configuration information (i.e., 0b00000) described in S1203 to S1204 is set. When CPU 111 receives a user instruction to display the print setting screen, it references the configuration information and performs control so as not to display the item for selecting the "user management function." This processing makes it possible to hide options for configuring settings related to authentication printing, which do not require configuration on the linked MFP, if the linked MFP does not use the user management function.

[0111] Next, in S1205, it is determined whether the MFP supports user authentication based on the result of S1201. If it is determined that the MFP supports user authentication, the process proceeds to S1210. If it is determined that the MFP does not support user authentication, the process proceeds to S1206.

[0112] In S1206, CPU 111 refers to the department ID management setting in the acquired capability information. In S1207, it is determined whether or not the MFP has department ID management enabled, based on the department ID management setting referred to in S1206. If the department ID management setting is enabled (ON), the process proceeds to S1208. If the department ID management setting is disabled (OFF), the process proceeds to S1203.

[0113] In S1208, CPU 111 updates the initial value of configuration information 1305 to department ID management (i.e., 0b01). In S1209, CPU 111 updates configuration information 1304 to display the items "Not Used" and "Department ID Management" and hide "User Authentication" (i.e., updates to 0b110). When the processing of S1208 is completed, CPU 111 ends the series of configuration information update processes.

[0114] 14(D) shows an example of a screen that is displayed when the configuration information (i.e., 0b11001) described in S1208 to S1209 is set. By this processing, if the linked MFP is an MFP that uses department ID management, it is possible to hide settings related to user authentication management that cannot be accepted by the linked MFP.

[0115] Next, in S1210, CPU 111 refers to the user authentication management setting in the acquired capability information. In S1211, CPU 111 determines whether or not user authentication is enabled for the MFP based on the user authentication management setting referred to in S1210. If the user authentication management setting is enabled (ON), the process proceeds to S1214. If the user authentication management setting is disabled (OFF), the process proceeds to S1212.

[0116] In S1212, CPU 111 refers to the department ID management setting in the acquired capability information. In S1213, CPU 111 determines whether or not the MFP has department ID management enabled, based on the department ID management setting referred to in S1212. If the department ID management setting is enabled (ON), the process proceeds to S1208. If the department ID management setting is disabled (OFF), the process proceeds to S1203.

[0117] In S1214, CPU 111 refers to the department ID management setting in the acquired capability information. In S1215, CPU 111 determines whether or not the MFP has department ID management enabled, based on the department ID management setting referred to in S1214. If the department ID management setting is enabled (ON), the process proceeds to S1218. If the department ID management setting is disabled (OFF), the process proceeds to S1216.

[0118] In S1216, CPU 111 updates the initial value of configuration information 1305 to user authentication (i.e., 0b10). In S1217, CPU 111 updates configuration information 1304 to display the items "Not Used" and "User Authentication" and hide "Department ID Management" (i.e., update to 0b101). When the processing of S1216 is completed, CPU 111 ends the series of configuration information update processes.

[0119] 14C shows an example of a screen that is displayed when the configuration information (i.e., 0b10110) described in S1216 to S1217 is set. By this process, if the linked MFP is an MFP that uses user authentication, it is possible to hide settings related to department ID management that cannot be accepted by the linked MFP.

[0120] In S1218, CPU 111 updates the initial value of configuration information 1305 to department ID management (i.e., 0b01). In S1219, CPU 111 updates configuration information 1304 to display all items (i.e., to 0b111). When the process of S1218 is completed, CPU 111 ends the series of configuration information update processes.

[0121] 14(B) shows an example of the screen that is displayed when the configuration information (i.e., 0b11101) described in S1218 to S1219 is set. With this processing, if the linked MFP is an MFP that uses both user authentication and department ID management, all items can be displayed so that the user can select the desired function.

[0122] As described above, this embodiment provides the following effects in addition to the effects of the first embodiment. In this embodiment, based on the capability information acquired from the linked MFP, it is possible to appropriately switch the display UI related to authentication print when making print settings based on the authentication functions supported by the linked MFP and the settings related to the MFP's authentication functions. Therefore, only the authentication functions that can be used by the linked MFP are displayed on the setting screen related to authentication print. The above control allows the user to select an authentication function without being aware of the types of authentication functions supported by the MFP or the MFP's operational policy.

[0123] 12 and updates the configuration information related to the display control of the print setting screen, the present embodiment is not limited to this. For example, a reference table for referencing the configuration information may be generated in advance using the capability information acquired from the MFP as a key, and the configuration information may be derived using the reference table.

[0124] Furthermore, in the present embodiment, an example has been given of a case in which control is performed to hide setting items that cannot be accepted by the linked MFP, but the display format is not limited to this. For example, setting items that cannot be accepted by the linked MFP may be displayed in gray out. In this case, CPU 111 displays the grayed out display items in a state in which they do not accept operations or selections by the user.

[0125] <Modification> In the first and second embodiments, the case where the user authentication information used for login is carried over (reflected) to the print settings is exemplified, but the present invention is not limited to this. For example, the cooperative application 310 may have settings for user authentication information that is commonly used in each cooperative function, and the commonly used user authentication information may be carried over to the setting screens of multiple functions.

[0126] <Other embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of each of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions. [Explanation of symbols]

[0127] 101 MFP 102 Communication terminal 111 CPU 114 Storage 123 Bluetooth I / F< / mfp>

Claims

1. a receiving means for receiving input of first authentication information from a user; a storage means for storing the first authentication information in response to the input of the first authentication information; a first transmitting means for transmitting the stored first authentication information to the image processing device via Bluetooth communication so that the user can log in to the image processing device and use functions including copy and transmission functions of the image processing device; a second transmission means for transmitting second authentication information and the print data to the image processing device in order to determine whether or not the image processing device executes printing based on the received print data; A mobile terminal, characterized in that the stored first authentication information is automatically used as the second authentication information.

2. 2. The mobile terminal according to claim 1, wherein the second transmission means transmits the input first authentication information to the image processing device to determine whether the image processing device will execute printing based on the print data.

3. 3. The mobile terminal according to claim 1, wherein the second transmission means transmits the input first authentication information to the image processing device based on an operation by the user.

4. The mobile terminal according to any one of claims 1 to 3, characterized in that the accepting means automatically uses the input first authentication information as the second authentication information without accepting further input of the first authentication information after accepting the input of the first authentication information.

5. A mobile terminal according to any one of claims 1 to 4, characterized in that the input first authentication information is transmitted to the image processing device by the first transmission means, and the image processing device determines whether or not to permit the user to log in based on the transmitted first authentication information.

6. A mobile terminal as described in any one of claims 1 to 5, characterized in that the first transmission means transmits the stored first authentication information to the image processing device via Bluetooth communication so that the user can log in to the image processing device and a screen on the operation unit of the image processing device that allows the user to use functions including copy and transmission functions of the image processing device is displayed.

7. 7. The mobile terminal according to claim 1, wherein the input first authentication information includes a username and a password.

8. A mobile terminal as described in any one of claims 1 to 7, characterized in that if the receiving means does not accept input of the first authentication information, a name set in the OS of the mobile terminal is used as the second authentication information.

9. a receiving step of receiving input of first authentication information from a user; a storage step of storing the first authentication information in response to the input of the first authentication information; a first transmission step of transmitting the stored first authentication information to the image processing device via Bluetooth communication so that the user can log in to the image processing device and use functions including copy and transmission functions of the image processing device; causing the mobile terminal to execute a second transmission step of transmitting second authentication information and the print data to the image processing device in order to determine whether or not the image processing device will execute printing based on the received print data; A program that causes the mobile terminal to automatically use the stored first authentication information as the second authentication information.

10. 10. The program according to claim 9, wherein in the second transmission step, the input first authentication information is transmitted to the image processing device to determine whether the image processing device will execute printing based on the print data.

11. 11. The program according to claim 9, wherein in the second transmission step, the input first authentication information is transmitted to the image processing device based on an operation by the user.

12. The program according to any one of claims 9 to 11, characterized in that after accepting the input of the first authentication information in the acceptance process, the mobile terminal automatically uses the input first authentication information as the second authentication information without accepting any further input of the first authentication information.

13. A program according to any one of claims 9 to 12, characterized in that the input first authentication information is transmitted to the image processing device in the first transmission step, and a determination is made in the image processing device as to whether or not to allow the user to log in based on the transmitted first authentication information.

14. A program described in any one of claims 9 to 13, characterized in that in the first transmission step, the stored first authentication information is transmitted to the image processing device via Bluetooth communication so that the user can log in to the image processing device and a screen on the operation unit of the image processing device that allows the user to use functions including the copy and transmission functions of the image processing device is displayed.

15. 15. The program according to claim 9, wherein the input first authentication information includes a user name and a password.

16. A program as described in any one of claims 9 to 15, characterized in that if input of the first authentication information is not accepted in the acceptance process, the program causes the mobile terminal to use a name set in the OS of the mobile terminal as the second authentication information.

Images