Information processing device

Abstract

To solve the problem in which it is difficult to perform operations when an image processing device performs processing in accordance with an application running on a mobile terminal.SOLUTION: There is provided means for allowing an image processing device to perform processing in accordance with an application running on a mobile terminal when causing the mobile terminal and the image processing device to communicate with each other.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a technology for cooperation among a plurality of image processing devices. [Background technology]

[0002] In recent years, image processing devices installed in offices are increasingly equipped with a function for exchanging data with mobile terminals. For example, a technology is known in which a mobile terminal transmits print data to an MFP to execute printing processing, or image data read by a scanner of the MFP is imported into a mobile terminal. In addition, a technology is disclosed in which, when an MFP performs e-mail transmission processing, the MFP receives transmission setting information indicating transmission settings from a mobile terminal, and performs e-mail transmission processing by reflecting the received transmission setting information (Patent Document 1).

[0003] Meanwhile, in recent years, various applications have been used on mobile terminals, and it has become common for users to install the desired applications and use them on their mobile terminals. For example, there are cloud storage applications for managing document data in the cloud and photo management applications for handling photo data. These applications can be linked with the MFP to perform some of the application processing on the MFP. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2017-108338 Summary of the Invention [Problem to be solved by the invention]

[0005] However, when linking an application and an MFP as described above to import image data scanned by the MFP into the application or print image data in the application on the MFP, certain setting operations are required, and the operations may not be simple. Thus, there has been a problem in that it is difficult to operate the MFP to execute processing according to the application. [Means for solving the problem]

[0006] an information processing device capable of communicating with a terminal capable of executing an application, the information processing device acquiring information relating to cooperation between the information processing device and the terminal for executing a part of processing of the application on the information processing device through communication established between the information processing device and the terminal, the information processing device being capable of communicating with a terminal transmitting an identifier of an application being executed on the terminal, the information processing device comprising: a storage means for storing the identifier of the application in association with predetermined information for displaying a button for calling up a predetermined processing corresponding to the application; a first receiving means for receiving the identifier of the application transmitted from the terminal; a display means for displaying on a display unit a button for calling up a processing indicated by the predetermined information, based on the predetermined information stored in association with the identifier of the application received by the first receiving means; and an execution means for executing the predetermined processing, based on pressing of the button displayed on the display means. an authentication means for authenticating a user; and based on the fact that the link has been released, based on the fact that a request to delete the button transmitted from the terminal has been received, the display means deletes the button. The display means creates a button based on information of the user authenticated by the authentication means. 23. An information processing apparatus comprising: Effect of the Invention

[0007] According to the present invention, a user can execute, on the MFP, processing according to an application running on a mobile terminal, without performing complicated operations. [Brief description of the drawings]

[0008] [Figure 1]1 is a diagram illustrating a configuration of an information processing system according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing a hardware configuration of an MFP according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a block diagram showing a hardware configuration of a mobile terminal according to an embodiment of the present invention. [Figure 4] 2 is a block diagram showing a hardware configuration of a management server according to an embodiment of the present invention. FIG. [Diagram 5] FIG. 2 is a sequence diagram showing a flow of a series of processes of an information processing system according to an embodiment of the present invention. [Figure 6] 2 is a block diagram showing a software configuration of the MFP according to the embodiment of the present invention. FIG. [Figure 7] FIG. 2 is a block diagram showing a software configuration of a mobile terminal according to an embodiment of the present invention. [Figure 8] 2 is a block diagram showing a software configuration of a management server according to an embodiment of the present invention. FIG. [Figure 9(a)] 5 is a flowchart showing the processing of the MFP in an embodiment of the present invention. [Figure 9(b)] 5 is a flowchart showing processing of the MFP in an embodiment of the present invention. [Figure 9(c)] 5 is a flowchart showing processing of the MFP in an embodiment of the present invention. [Figure 9(d)] 5 is a flowchart showing processing of the MFP in an embodiment of the present invention. [Figure 9(e)] 5 is a flowchart showing processing of the MFP in an embodiment of the present invention. [Figure 10] 10 is a flowchart illustrating a process of a mobile terminal according to an embodiment of the present invention. [Figure 11] 10 is a flowchart showing a process of a management server according to an embodiment of the present invention. [Figure 12] 4 is an example of a button management table according to the embodiment of the present invention. [Figure 13]13 is an example of a mobile application linkage table according to the embodiment of the present invention. [Figure 14] 5 is an example of a menu screen displayed on an operation unit of the MFP in the embodiment of the present invention. [Figure 15] 13 is an example of a mobile application link table according to the second embodiment of the present invention. [Figure 16] 13 is an example of a button management table according to the second embodiment of the present invention. [Figure 17] 13 is an example of a menu screen displayed on an operation unit of an MFP in the second embodiment of the present invention. [Figure 18] FIG. 13 is a block diagram showing a software configuration of an MFP according to a third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The best mode for carrying out the present invention will be described below with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0010] (First embodiment) Fig. 1 is a diagram showing an example of a system configuration of an information processing system according to this embodiment. This system includes an MFP (Multi Function Peripheral) 101 as an example of an image processing apparatus connected to a LAN (Local Area Network) 110, a mobile terminal 102 wirelessly connected to the LAN 110 via a wireless access point 130, and a management server 103 and an application server 104 connected to a WAN (Wide Area Network) 120. The devices on the LAN 110 and the devices on the WAN 120 can communicate with each other through each other's networks. Fig. 1 shows an example of a typical network configuration, and each device may be connected to either the LAN 110 or the WAN 120.

[0011] The MFP 101 is an image processing apparatus having a scanner and a printer. In this embodiment, the MFP is used as an example of an image processing apparatus, but the image processing apparatus is not limited to this and may be a single-function apparatus. The MFP 101 has an application platform for adding and executing an application (hereinafter, MFP application) that runs on the apparatus. The MFP 101 also has a web browser as one of the MFP applications. Although only one MFP is illustrated, there may be multiple MFPs on the system. The mobile terminal 102 is a portable information processing apparatus, typically a smartphone or a tablet terminal. The mobile terminal 102 has an application platform for adding and executing an application (hereinafter, mobile application) that runs on the information processing apparatus. The MFP 101 and the mobile terminal 102 can directly communicate with each other by short-range wireless communication such as NFC (Near Field Communication) or Bluetooth (registered trademark) (not illustrated). The management server 103 is a server for managing the MFP 101, and holds information for displaying a menu screen on the operation unit of the MFP 101, as an example. The application server 104 is a server for providing web applications. The provided Web application is a program that runs on the application server 104. The Web application provides an operation screen of the Web application to the MFP 101 or the mobile terminal 102, and the MFP 101 or the mobile terminal 102 displays the operation screen on a Web browser. The MFP 101 or the mobile terminal 102 accesses the application server 104 to display an operation screen of the Web application 601, accept a user operation on the operation screen, and return the accepted operation content to the application server 104. In this embodiment, the management server 103 creates a button corresponding to the application running on the mobile terminal 102, and displays it on the MFP 101. The number of application servers is not limited to one, and multiple servers may be present depending on the purpose.

[0012] 2 is a block diagram showing a hardware configuration of the MFP 101. A control unit 210 including a CPU 211 controls the overall operation of the MFP 101. The CPU 211 reads out control programs stored in a ROM 212 or a HDD 214 to execute various control processes such as reading control and transmission control. The RAM 213 is used as a temporary storage area such as a main memory or work area for the CPU 211. The HDD 214 stores various programs including image data and installed MFP applications. The short-range wireless communication I / F 215 is an interface for short-range wireless communication such as NFC or Bluetooth, and communicates with the mobile terminal 102 and the like to exchange data.

[0013] The operation unit I / F 216 connects the operation unit 221 and the control unit 210. The operation unit 221 is provided with a liquid crystal display unit having a touch panel function, a keyboard, and the like. The printer I / F 217 connects the printer 222 and the control unit 210. Image data to be printed by the printer 222 is transferred from the control unit 210 to the printer 222 via the printer I / F 217, and is printed on a recording medium by the printer 222. The scanner I / F 218 connects the scanner 223 and the control unit 210. The scanner 223 reads an image on a document, generates image data, and inputs the image data to the control unit 210 via the scanner I / F 218. The sensor I / F 219 connects the contact detection sensor 224 and the control unit 210. The contact detection sensor 224 is a sensor for detecting whether the mobile terminal 102 has contacted a predetermined position of the MFP 101. In this embodiment, a mobile terminal placement area (not shown) for placing a mobile terminal is prepared in MFP 101, and the placement of the mobile terminal there is detected by contact detection sensor 224. Network I / F 220 connects control unit 210 (MFP 101) to LAN 110. Network I / F 220 transmits and receives various types of information to and from other devices on LAN 110 or WAN 120.

[0014] 3 is a block diagram showing a hardware configuration of the mobile terminal 102. A control unit 310 including a CPU 311 controls the operation of the entire device. The CPU 311 reads out control programs stored in a ROM 312 or a HDD 314 and executes various control processes. The RAM 313 is used as a temporary storage area such as a main memory or a work area for the CPU 311. The flash memory 314 stores various programs and data.

[0015] The operation unit I / F 315 connects the operation unit 318 and the control unit 310. The operation unit 221 is provided with a liquid crystal display unit having a touch panel function. The short-range wireless communication I / F 316 is an interface for short-range wireless communication such as NFC or Bluetooth, and communicates with the MFP 101 and the like to exchange data. The network I / F 317 connects the control unit 310 to the WAN 120 or the LAN 101. The network I / F 316 is capable of wireless communication, and the network I / F 317 transmits and receives various information to and from other devices on the WAN 120 or the LAN 110 via wireless communication.

[0016] 4 is a block diagram showing the hardware configuration of the management server 103 and the application server 104. A control unit 410 including a CPU 411 controls the operation of the entire device. The CPU 411 reads out control programs stored in a ROM 412 or a HDD 414 to execute various control processes. A RAM 413 is used as a temporary storage area such as a main memory or a work area for the CPU 411. The HDD 414 stores various programs and data.

[0017] The display unit I / F 415 connects the display unit 418 and the control unit 410. The keyboard I / F 416 connects the keyboard 419 and the control unit 410. The CPU 411 recognizes instructions from the user via the keyboard 419, and transitions the screen displayed on the display unit 418 in accordance with the recognized instructions. The network I / F 417 connects the control unit 410 to the WAN 120 or the LAN 101. The network I / F 417 transmits and receives various information to and from other devices on the WAN 120 or the LAN 110.

[0018] Before describing the sequence diagram of FIG. 5, an outline of this embodiment will be described. An example will be described in which, when the mobile terminal 102 is placed in the mobile storage area of ​​the MFP 101 with a mobile application for managing cloud storage open or in the foreground, a button corresponding to the mobile application for managing cloud storage (here, a button for calling a web application for scanning that saves a scanned image in the cloud storage) is displayed on the MFP 101. When the mobile terminal 102 is placed in the mobile storage area of ​​the MFP 101, the mobile terminal 102 and the MFP 101 start exchanging data, and an instruction to create a button (a button for calling a web application for scanning) corresponding to the application displayed on the mobile terminal or in the foreground is transmitted from the mobile terminal 102 to the management server. The management server that receives the instruction creates a button, and the MFP 101 displays the button created by the management server 103 on the display unit. When the user presses the button displayed on the MFP 101, the MFP 101 calls the web application for scanning. When the link between the mobile terminal 102 and the MFP 101 is released, the created button is deleted from the MFP 101 and the management server.

[0019] 5 is a sequence diagram showing the flow of a series of processes performed in cooperation between the MFP 101, mobile terminal 102, management server 103, and application server 104 in this embodiment. These processes are realized by the CPU reading out and executing programs stored in the ROM, HDD, and flash memory of each device into the RAM.

[0020] First, in step S501, the MFP 101 receives a login instruction from the user and performs login processing. In step S502, the MFP 101 acquires screen information including information (information of an application to be opened when the button is pressed, etc.) of a button (hereinafter, application button) to be displayed on a menu screen from the management server 103. The application button is a button for calling various functions such as an MFP application or a Web application. In step S503, the MFP 101 displays a menu screen on the operation unit 221 based on the button information acquired from the management server 103. When the user places the mobile terminal 102 in the mobile place of the MFP 101, in step S504, the MFP 101 detects that the mobile terminal 102 has been placed by the contact detection sensor 224. In step S505, the MFP 101 transmits a beacon signal (hereinafter, link signal) for establishing communication with the mobile terminal 102 using the short-range wireless communication I / F 215. Here, Bluetooth is used as an example of short-range wireless communication.

[0021] In step S506, the mobile terminal 102 receives a link signal emitted by the MFP 101 through the short-distance wireless communication I / F 316. If the radio wave strength of the received beacon signal is equal to or greater than a predetermined value, the mobile terminal 102 determines that the MFP 101 is placed on the mobile device, establishes communication with the MFP 101, and acquires link information. The link information includes information necessary for the mobile terminal 102 to perform subsequent processing. For example, the link information includes user information (user ID) of a user who has logged in to the MFP 101, an IP address of the management server 103, and identification information of the MFP 101. In step S507, the mobile terminal 102 identifies a mobile application that is displayed on the screen of the operation unit 318 or is in the foreground. In a later flow, the mobile terminal 102 causes the MFP 101 to display an application button corresponding to the mobile application (hereinafter, this application is referred to as a target application). In step S508, the mobile terminal 102 acquires data (hereinafter, target application data) necessary for the MFP 101 to display a button corresponding to the target application from the target application. Target application data is data that the target application is opening or processing, and varies depending on the target application. For example, if the target application is a mobile application for managing cloud storage, it may be an identifier indicating the currently displayed folder, and if the target application is a word processing application, it may be print data for printing the document currently being created. There is no limit to a single target application data, and there may be multiple target application data. For example, if the target application is a word processing application, in addition to print data, the target application data may include the file name of the document to be printed.

[0022] In step S509, the mobile terminal 102 transmits the target application identifier, target application data, and link information to the management server 103, and instructs the management server 103 to create a button (hereinafter, a link button) according to the target application. In this embodiment, the management server 103 with the IP address included in the link information acquired in step S506 is used as the transmission destination, but the mobile terminal 102 may be configured to set the IP address of the management server 103 as the connection destination in advance.

[0023] In step S510, the management server 103 creates a link button using the identifier of the target application, the target application data, and the link information received from the mobile terminal 102. The link button is a type of application button, and is a button for calling an MFP application or a Web application for performing processing according to the target application from the menu screen of the MFP 101. The link button also has parameters (hereinafter, called call parameters) for calling an application for performing processing according to the target application. The call parameters are defined based on the target application data and the like. Hereinafter, in this sequence, it is assumed that the target application is a mobile application for managing cloud storage, and the target application data is an identifier indicating a folder in the cloud storage. It is also assumed that the call destination of the link button is a Web application for scanning provided by the application server 104. In other words, if the target application is a mobile application for managing cloud storage, it is expected that data scanned by the MFP will be sent to that storage, so the call destination of the link button is set to the Web application for scanning. Here, it is assumed that the call destination according to the target application is predetermined by the management server.

[0024] In step S511, the management server 103 receives the instruction to create a linked button from the mobile terminal 102 and notifies the MFP 101 that an update to the button information has occurred.

[0025] In step S512, MFP 101, which has received the button update notification, acquires screen information including application button information from management server 103. The acquired application button information also includes information on the link button created by management server 103 in step S510. In step S513, MFP 101 updates the menu screen displayed on operation unit 221 to the latest state based on the screen information including the application button information acquired from management server 103. At this time, MFP 101 displays the link button created by management server 103 in step S510 on the menu screen as one of the application buttons to be displayed. Here, MFP 101 acquires screen information including application button information, but is not limited to this, and may acquire only information on the link button created in step S510 and update the menu screen using that information.

[0026] Next, in step S514, when the user presses the link button, MFP 101 detects that the user has pressed the link button displayed on the menu screen. In step S515, MFP 101 uses a web browser to access a web application for scanning that is the call destination of the link button and is provided by application server 104. Note that in this sequence, a link button is displayed on MFP 101, and the call destination is accessed by the user pressing the link button, but this is not limited to the above. It is also possible to automatically launch a web browser and access the call destination when link button information is acquired in S512.

[0027] The MFP 101 communicates with the application server 104 multiple times as necessary to process the Web application for scanning. In step S516, the MFP 101 performs scanning in response to an instruction from the Web application for scanning. In step S517, the MFP 101 sends the results of the scan and the scanned image data to the application server 104.

[0028] In step S518, the application server 104 uploads the received image data to the cloud indicated by the target application (a mobile application for managing cloud storage). The upload destination at this time is indicated by the identifier of the folder in the cloud storage indicated by the target application data.

[0029] In step S519, the MFP 101 notifies the mobile terminal 102 that execution of the link button has been completed.

[0030] In step S520, in the mobile terminal 102 that has received the notification from the MFP 101, the target application (a mobile application for managing cloud storage) performs a predetermined process after the execution of the link button is completed. Here, the display of the file list screen in the cloud storage is updated to the latest state, and is displayed so that the image data uploaded in step S518 is reflected. The predetermined process after the execution of the link button is completed differs for each target application. For example, if the target application is an address book application, when the link button is executed, the MFP 101 may send data to the destination displayed on the mobile terminal 102, and a predetermined process after the execution is completed may display on the mobile terminal 102 that the data has been sent.

[0031] Next, in step S521, when the user removes the mobile terminal 102 from the mobile terminal storage area, the MFP 101 detects that the mobile terminal 102 has left the mobile terminal storage area by the contact detection sensor 224. In step S522, the MFP 101 transmits a request to cancel the linkage to the mobile terminal 102. Here, canceling the linkage means that communication between the MFP 101 and the mobile terminal 102 is cut off. Note that there are multiple patterns of conditions under which the MFP 101 transmits the linkage cancellation request to the mobile terminal 102, and "when it is detected that the mobile terminal 102 has left the mobile terminal storage area" is one example of the timing of transmission. Other patterns include, for example, "when it is detected that the user has logged out" and "when there has been no user operation for a certain period of time." The mobile terminal 102 that has received the linkage cancellation request cuts off communication with the MFP 101.

[0032] In step S523, the mobile terminal 102 that has received the request to cancel the linkage instructs the management server 103 to delete the linkage button.

[0033] In step S524, upon receiving the deletion instruction, the management server 103 deletes the linked button created in step S510. In step S525, the management server 103 notifies the MFP 101 that an update to the button information has occurred.

[0034] In step S526, MFP 101, having received the button update notification, acquires application button information from management server 103. In step S527, MFP 101 updates the menu screen displayed on operation unit 221 to the latest state based on the button information acquired from management server 103. Because the button information acquired in step S526 does not include information on the linked button, the linked button has disappeared from the menu screen after updating to the latest state.

[0035] In this sequence, the mobile terminal 102 is placed in the mobile storage area of ​​the MFP 101, and the link button is created. However, the mobile terminal 102 does not necessarily have to be placed in the storage area. Any configuration is acceptable as long as the mobile terminal 102 and the MFP 101 can exchange data. For example, the mobile terminal 102 and the MFP 101 may establish Bluetooth communication before the subsequent processing proceeds, or the mobile terminal 102 and the MFP 101 may exchange wireless LAN information through the established Bluetooth communication and establish wireless LAN communication using the information before the subsequent processing proceeds. When NFC communication is used, the mobile terminal 102 may receive wireless LAN connection information from the MFP 101 using NFC, and establish wireless LAN communication with the MFP 101 using the wireless LAN connection information before the processing proceeds.

[0036] According to the sequence of FIG. 5, when the mobile terminal 102 and the MFP 101 communicate with each other, the MFP 101 can execute processing according to an application displayed on the screen of the mobile terminal 101 or in the foreground.

[0037] 6 is a diagram showing the software configuration of the MFP 101 of this embodiment, which is a functional block diagram in which the CPU 211 reads out programs stored in the ROM 212 and HDD 214 of the MFP 101, stores them in the RAM 213, and executes them.

[0038] A login management unit 601 manages user authentication in the MFP 101. A menu display unit 602 displays a menu screen on the operation unit 221. The menu display unit 602 displays application buttons for calling MFP applications and Web applications on the menu screen. The menu display unit 602 acquires information on the application buttons to be displayed from the management server 103.

[0039] The Web browser 603 accesses a Web server and displays Web content.

[0040] The mobile terminal linking unit 604 performs processing for linking with a mobile terminal. For example, the mobile terminal linking unit 604 detects that the mobile terminal has been placed in the mobile storage area using the contact detection sensor 224, and communicates with the mobile terminal using the short-range wireless communication I / F 215.

[0041] A scan function providing unit 605 provides a scan function and an API (Application Programming Interface) for calling the scan function to an MFP application or a Web application. A print function providing unit 606 provides a print function and an API for calling the print function to an MFP application or a Web application.

[0042] The MFP application management unit 607 is a software platform for running MFP applications on the MFP 101. Fig. 6 shows a state in which two MFP applications, a sending MFP application 608 and a printing MFP application 609, are installed. The sending MFP application 608 is an MFP application that transmits scanned image data to the outside via the LAN 110. The printing MFP application 609 is an MFP application that prints print data received from the outside. 608 and 609 are examples of MFP applications, and other MFP applications may be installed.

[0043] Note that MFP 101 may include other functions not shown.

[0044] 7 is a diagram showing the software configuration of the mobile terminal 102 of this embodiment. It is a functional block diagram in which the CPU 311 reads out programs stored in the ROM 312 and flash memory 314 of the mobile terminal 102 into the RAM 313 and executes them.

[0045] A cooperation signal receiving unit 701 receives a beacon signal (cooperation signal) via the short-range wireless communication I / F 316, and calls a mobile application corresponding to the cooperation signal. In this embodiment, the mobile application corresponding to the cooperation signal transmitted by the MFP 101 is an MFP cooperation management application 703.

[0046] The mobile application management unit 702 is a software platform for running mobile applications on the mobile terminal 102. Fig. 7 shows a state in which five mobile applications 703 to 707 are installed.

[0047] The MFP cooperation management application 703 performs processing for cooperation between the MFP and a target application, such as identifying a target application that cooperates with the MFP and instructing the management server 103 to create a cooperation button.

[0048] Cloud document management application 704 is a mobile application for operating a cloud storage service that manages document data from a mobile terminal. Cloud photo management application 705 is a mobile application for operating a cloud storage service that manages photo data from a mobile terminal. Address book application 706 is a mobile application for managing contacts, and manages names, phone numbers, and email addresses as contacts. Document creation application 707 is a mobile application for creating document data. Applications 704 to 707 other than MFP cooperation management application 703 are examples of mobile applications, and other mobile applications may be installed.

[0049] Note that the mobile terminal 102 may include other functions not shown.

[0050] 8 is a diagram showing the software configuration of the management server 103 of this embodiment. It is a functional block diagram in which a CPU 411 reads out programs stored in a ROM 412 and HDD 414 of the management server 103 into a RAM 413 and executes the programs.

[0051] A button management unit 801 manages application buttons to be displayed on a menu screen of the MFP 101. For example, the button management unit 801 notifies the MFP 101 of updates to the application buttons, and transmits information about the application buttons to the MFP 101 in response to a request from the MFP 101. A button management table 802 is a table that manages information necessary for executing applications and the like linked to application buttons.

[0052] Fig. 12 shows an example of a button management table 802 according to the embodiment. Fig. 12(a) is an example of the button management table 802 at the time of step S502 in the sequence diagram of Fig. 5. Fig. 12(b) and Fig. 12(c) are examples of records of linked buttons created in step S510 in the sequence diagram of Fig. 5.

[0053] The button management table 802 has eight columns, 1201 to 1208.

[0054] ButtonID 1201 defines an identifier for uniquely identifying an application button. The ButtonID 1201 column is also an identifier for uniquely specifying a row in a table. In the following explanation, the value of the ButtonID 1201 column will be used to specify a row in a table. For example, a row whose ButtonID 1201 column value is "b001" will be described as "row b001."

[0055] The ButtonType1202 column is a column that defines the type of application button. The ButtonType1202 column can have three values: "Shared," "Personal," and "MobileLink." "Shared" indicates that the application button is an application button that can be used by any user (hereinafter, "shared button"). "Personal" indicates that the application button is an application button that is associated with a specific user (hereinafter, "personal button"). Shared buttons and personal buttons are application buttons that can be added or deleted by the administrator or user of the MFP101. "MobileLink" indicates that the application button is an association button. An association button is a button that is associated with a specific user, but unlike a personal button, an association button is a temporary button that exists only when the MFP101 and mobile terminal 102 are associated with each other, and is therefore distinguished from a personal button.

[0056] The ButtonName 1203 column is a column that defines the name of the app button. The TargetType 1204 column is a column that defines the type of application that will be called up by the app button. The TargetType 1204 column can take two values: "MFP" and "Web". "MFP" indicates that the application that will be called up by the app button is an MFP application. "Web" indicates that the application that will be called up by the app button is a Web application.

[0057] The ButtonTarget 1205 column is a column that defines the destination of the application button. If the TargetType 1204 column is "MFP", the ButtonTarget 1205 column defines the executable file of the MFP application. If the TargetType 1204 column is "Web", the ButtonTarget 1205 column defines the URL of the Web application. The ButtonParameter 1206 column defines the parameters to be added when calling the application defined in the ButtonTarget 1205 column. For example, if the button is a "Send email to business partner", parameters such as the recipient's email address are added.

[0058] The ViewOrder 1207 column defines the display order of the application buttons on the menu screen of the MFP 101. The display order is from the lowest number to the highest number. Note that in the records of the link button created by linking with the mobile terminal (FIGS. 12(b) and 12(c)), the value is set to -1 so that the button is displayed first.

[0059] The UserID 1208 column defines the user who owns the app button. In the case of a share button, there is no owner user, so the UserID 1208 column is blank.

[0060] Returning to the explanation of FIG. 8, the mobile application cooperation unit 803 cooperates with the mobile application of the mobile terminal 102. For example, a cooperation button is created or deleted according to an instruction from the mobile terminal 102. The mobile application cooperation table 804 is a table that manages information for creating a cooperation button corresponding to a target application. For example, if the target application is a mobile application for managing cloud storage, it is expected that data scanned by the MFP will be sent to that storage, so the table is for previously associating the destination of the cooperation button with a Web application for scanning.

[0061] 13 shows an example of a mobile application link table 804 according to this embodiment. The mobile application link table 804 has eight columns, 1301 to 1308.

[0062] ID1301 is an identifier for uniquely identifying a row in a table. In the following explanation, the value of the ID1301 column will be used to specify a row in a table. For example, a row whose ID1301 column value is "m001" will be described as "row m001."

[0063] The MobileAppID 1302 column defines the identifier of the mobile application. The ButtonName 1303 column defines the name of the link button to be created. It is possible to define variables in the ButtonName 1303 column. In this case, the string surrounded by "%" symbols is the variable. When the link button is created, the variable is replaced with the string that corresponds to the variable. For example, "%email%" is defined as a variable in the ButtonName 1303 column in row m003, and this is replaced with the email address included in the target app data obtained from the target application when the link button is created.

[0064] The TargetType 1304 column is a column that defines the type of application that will be called up by the application button. The ButtonTarget 1305 column is a column that defines the application that will be called up by the application button. The application that the user is expected to use as the target application is determined in advance. The ButtonParameter 1306 column defines parameters to be added when calling up the application defined in the ButtonTarget 1305 column. For example, if the application that will be called up is to execute printing as in the m004 column, the print setting parameters apply.

[0065] A MobileParamName 1307 column is a parameter that is added before column 1308 among the parameters that are added when calling the application defined in column ButtonTarget 1305. A MobileParamKey 1308 column defines a key for extracting a value corresponding to the parameter defined in column MobileParamName 1307 from the target application data acquired from the target application. The parameters defined in column 1308 change dynamically depending on the application data. As an example, in the case of "scan and save to WebDrive" in row m001, it indicates that the save destination ("destination" in column 1307) is the current path indicated by the target application data ("current path" in column 1308). In this way, when the WebDrive application is currently displayed on the mobile terminal 102, column 1308 defines a key for extracting an identifier indicating a folder in WebDrive. FIG. 13 shows an example of one parameter whose value changes depending on the target application, but there may be multiple parameters whose values ​​change depending on the target application. In this case, multiple columns similar to the MobileParamName 1307 column and the MobileParamKey 1308 column may be prepared, or a separate table may be prepared.

[0066] 9(a) to 9(e) are flowcharts for explaining the processing of the MFP 101 in this embodiment. The CPU 211 reads a program stored in the ROM 212 and HDD 214 of the MFP 101 into the RAM 213 and executes the program, thereby executing each step of the flowcharts in FIG. 9(a) to 9(e). Note that, although an example in which BLE (Bluetooth Low Energy) is used as short-range wireless communication is described in this embodiment, other short-range wireless communication such as NFC may also be used. Also, in this embodiment, an example in which the MFP 101 operates as a peripheral and the mobile terminal 102 operates as a central as a terminal for short-range wireless communication in BLE is described.

[0067] Fig. 9(a) is a flowchart for explaining the processing from the login processing to the display of the menu screen of the MFP 101. The flowchart in Fig. 9(a) corresponds to the processing of the MFP 101 in steps S501 to S503 in the sequence diagram in Fig. 5.

[0068] In step S901, the login management unit 601 receives a login instruction from the user and performs user authentication. The authentication method may be authentication using an IC card, or authentication may be performed by having the user input a user name and password on the MFP 101. User authentication is not necessarily required, and if the MFP 101 is configured so that user authentication is not required, processing may start from step S903 without logging in. In that case, if an identifier for identifying the user is required in the subsequent processing, a predetermined identifier (for example, "GUEST") may be used.

[0069] In step S902, if the login management unit 601 succeeds in the user authentication, the process proceeds to step S903, and if the user authentication fails, the login management unit 601 displays an error in step S910 and ends the process.

[0070] In step S903, the menu display unit 602 transmits a request to acquire application button information to the button management unit 801 of the management server 103. At this time, the menu display unit 602 includes in the acquisition request the user ID of the user authenticated in step S901 in order to acquire only information about the application button corresponding to the logged-in user.

[0071] In step S904, the menu display unit 602 receives application button information from the button management unit 801 of the management server 103 as a response to the acquisition request. The application button information received here is information managed by the button management unit 801 in the button management table 802. For example, if the user ID of the logged-in user is "u001", the application button information received is information on a total of six application buttons: five shared buttons defined on lines b001 to b005, and one personal button defined on line b101 for which the user ID is u001.

[0072] In step S905, the menu display unit 602 displays a menu screen on the operation unit 221 based on the received application button information.

[0073] An example of the menu screen is shown in Fig. 14. Fig. 14(a) is an example of the menu screen displayed in step S905 when the user ID of the user logged in to MFP 101 is "u001". On the menu screen, a total of six application buttons, including five shared buttons defined in rows b001 to b005 and one personal button defined in row b101, are displayed in the order defined in the ViewOrder1207 column. Fig. 14(b) and Fig. 14(c) are examples of the menu screen after the link button has been created, and will be described later in conjunction with the flowchart in Fig. 9(c).

[0074] Returning to the explanation of Fig. 9(a), in step S906, the menu display unit 602 establishes a WebSocket connection so as to receive notification from the management server 103 that the application button information has been updated, and ends the process. Notification using WebSocket is one example of a means for detecting an update to the application button information, and other means may be used, such as a polling method in which the menu display unit 602 periodically inquires of the management server 103. In order for the management server 103 to identify the MFP that issues the notification, the management server 103 may acquire MFP identification information from the mobile terminal 102.

[0075] Fig. 9(b) is a flowchart for explaining a process in which the MFP 101 detects that the mobile terminal 102 has been placed in the mobile terminal storage area and cooperates with the mobile terminal. The flowchart in Fig. 9(b) corresponds to the process of the MFP 101 in steps S504 to S506 in the sequence diagram in Fig. 5.

[0076] In step S920, the mobile terminal linking unit 604 detects, via the contact detection sensor 224, that the mobile terminal has been placed in the mobile terminal storage area.

[0077] In step S921, the mobile terminal linking unit 604 transmits a BLE advertising packet as a linking signal for linking with the mobile terminal 102, using the short-range wireless communication I / F 215. In step S922, the mobile terminal linking unit 604 waits for a connection request for short-range wireless communication from the mobile terminal 102. If there is no connection request from the mobile terminal 102, the mobile terminal linking unit 604 returns to step S921 and transmits a linking signal again. If there is a connection request from the mobile terminal 102, the mobile terminal linking unit 604 proceeds to step S923.

[0078] In step S923, the mobile terminal link unit 604 receives a connection request from the mobile terminal 102 and establishes a connection with the mobile terminal 102. Hereinafter, unless otherwise specified, it is assumed that communication between the MFP 101 and the mobile terminal 102 is performed using short-range wireless communication.

[0079] In step S924, after the collaboration, the mobile terminal collaboration unit 604 receives from the mobile terminal 102 an instruction (notification request) to send a notification required for the processing of this embodiment to the mobile terminal 102. In this embodiment, the notifications required for the processing of this embodiment are two notifications: "completion of execution of collaboration button" and "request to cancel collaboration."

[0080] In step S925, the mobile terminal linking unit 604 receives a request to acquire linking information from the mobile terminal 102. The linking information is information necessary for the mobile terminal 102 to link with the MFP 101, such as the user ID of the user logged in to the MFP 101, the IP address of the management server 103, and the identifier of the MFP 101. In step S926, the mobile terminal linking unit 604 sends the linking information to the mobile terminal 102 as a response to step S925, and ends the process.

[0081] Fig. 9(c) is a flowchart for explaining the processing in which MFP 101 updates the menu screen upon receiving a notification of update of button information from management server 103. Moreover, the flowchart in Fig. 9(c) corresponds to the processing of MFP 101 in steps S511 to S513 and steps S525 to S527 in the sequence diagram in Fig. 5.

[0082] In step S930, the menu display unit 602 receives a notification from the management server 103 that an update of the button information has occurred. In step S931, the menu display unit 602 transmits an application button information acquisition request to the button management unit 801 of the management server 103. In step S932, the menu display unit 602 receives application button information from the button management unit 801 of the management server 103 as a response to the acquisition request. In step S933, the menu display unit 602 displays a menu screen on the operation unit 221 based on the received application button information, and ends the process.

[0083] 14(b) and 14(c) are examples of the menu screen after the link button has been created (step S513 in the sequence diagram of FIG. 5). FIG. 14(b) is an example of the user "u001", and in addition to the application button displayed in FIG. 14(a), the link button defined in line b201 of FIG. 12 has been added. FIG. 14(c) is an example of the user "u002". The link button defined in line b202, the share button defined in lines b001 to b005, and the personal button defined in line b111 are displayed.

[0084] The link button is displayed at the top in accordance with the ViewOrder column 1207. Also, as shown in Fig. 14(b) and Fig. 14(c), the link button may be displayed differently from the personal buttons and share buttons other than the link button so that it is clear that the link button is a newly created application button.

[0085] 9(d) is a flowchart for explaining execution processing of an application button in the MFP 101. The flowchart in FIG. 9(d) corresponds to the processing of the MFP 101 in steps S514 to S519 in the sequence diagram in FIG.

[0086] In step S940, the menu display unit 602 detects that the user has pressed an application button. In step S941, the menu display unit 602 checks the TargetType information of the application button pressed by the user. If the TargetType is Web, the menu display unit 602 proceeds to step S942, and if it is MFP, the menu display unit 602 proceeds to step S945.

[0087] In step S942, the menu display unit 602 calls the Web browser 603 to access the Web application. The access destination is a URL obtained by adding the ButtonParameter 1206 column as a query to the URL defined in the ButtonTarget 1205 column. As an example, the following description will be given assuming that the Web application called here is a scanning Web application provided by the application server 104. Scanning is just an example, and Web applications having other functions such as printing and faxing may also be called.

[0088] In step S943, the Web browser 603 accepts a user operation through the operation unit 221, and proceeds with the operation of the Web application while communicating with the application server 104 multiple times as necessary. In step S944, the scan function providing unit 605 performs scanning in response to a call instruction from the Web application. In step S945, the scan function providing unit 605 sends the scan execution result and scanned image data to the application server 104, and the process proceeds to step S950.

[0089] In step S946 following step S941, the menu display unit 602 calls an MFP application corresponding to the application button pressed by the user. Specifically, the parameters in the ButtonParameter 1206 column are assigned to the executable file defined in the ButtonTarget 1205 column and called. As an example, the following description will be given assuming that the MFP application called here is the print MFP application 609. Printing is just an example, and MFP applications having other functions such as scanning and faxing may also be called.

[0090] In step S947, the print MFP application 609 accepts a user operation via the operation unit 221, and performs processing as an application, such as displaying a setting screen or previewing a document as necessary. In step S948, the print MFP application 609 executes printing using the print function providing unit 606, and the process proceeds to step S950.

[0091] In step S950, the menu display unit 602 checks the ButtonType of the executed application button and determines whether the executed application button is a link button. If the executed application button is a link button, the menu display unit 602 proceeds to step S951, and if not, ends the process.

[0092] In step S951, the mobile terminal linking unit 604 checks whether or not the notification request of step S924 has been received from the mobile terminal 102. If the notification request has been received, the mobile terminal linking unit 604 proceeds to step S952, otherwise, the mobile terminal linking unit 604 ends the process. In step S952, the mobile terminal linking unit 604 notifies the mobile terminal 102 that the execution of the link button has been completed, and ends the process.

[0093] Fig. 9(e) is a flowchart for explaining a process in which the MFP 101 detects that the mobile terminal 102 has left the mobile terminal storage area and notifies the mobile terminal 102. The flowchart in Fig. 9(e) corresponds to the process of the MFP 101 in steps S521 to S522 in the sequence diagram in Fig. 5.

[0094] In step S960, the mobile terminal linking unit 604 detects that the mobile terminal 102 has left the mobile terminal storage area by the contact detection sensor 224. In step S961, the mobile terminal linking unit 604 checks whether or not the notification request of step S924 has been received from the mobile terminal 102. If the notification request has been received, the mobile terminal linking unit 604 proceeds to step S962, and if not, ends the process. In step S962, the mobile terminal linking unit 604 notifies the mobile terminal 102 of a request to cancel linkage, and ends the process.

[0095] Note that FIG. 9(e) illustrates an example of the timing for notifying the mobile terminal 102 of a request to cancel the linkage when it is detected that the mobile terminal 102 has left the mobile terminal storage area. However, similar processing is performed when notifying the mobile terminal 102 of a request to cancel the linkage at other times.

[0096] For example, instead of "detecting that the mobile terminal 102 has left the mobile parking area" in step S960, "detecting that the user has logged out" and then the subsequent processes are performed. Similarly, instead of "detecting that the mobile terminal 102 has left the mobile parking area" in step S960, "detecting that no user operation has been performed for a certain period of time" and then the subsequent processes are performed.

[0097] The effects of the flowcharts in Figures 9(a) to (e) are shown below. After the MFP 101 links with the mobile terminal 102, it obtains link button information from the management server and displays the link button. It is possible to issue instructions to execute or delete the link button.

[0098] Fig. 10 is a flowchart for explaining the processing of the mobile terminal 102 in this embodiment. The CPU 311 reads out a program stored in the ROM 312 and flash memory 314 of the mobile terminal 102 into the RAM 313 and executes the program, thereby executing each step of the flowchart in Fig. 10.

[0099] Fig. 10(a) is a flowchart for explaining the processing from when the mobile terminal 102 receives a link signal from the MFP 101 to when it instructs the management server 103 to create a link button. The flowchart in Fig. 10(a) corresponds to the processing of the mobile terminal 102 in steps S505 to S509 in the sequence diagram in Fig. 5.

[0100] In step S1001, the cooperation signal receiving unit 701 receives a BLE advertising packet using the short-range wireless communication I / F 316. In step S1002, the cooperation signal receiving unit 701 checks an identifier (UUID) included in the received advertising packet and determines whether the signal is a cooperation signal issued by the MFP. If the received signal is a cooperation signal, the cooperation signal receiving unit 701 proceeds to step S1003, and if not, ends the process.

[0101] In step S1003, the cooperation signal receiving unit 701 calls the MFP cooperation management application 703 in the background so that screen switching does not occur on the operation unit 318.

[0102] In step S1004, if the radio wave strength of the received advertising packet is equal to or greater than a predetermined value, it is assumed that the mobile terminal 102 is placed in the mobile storage area of ​​the MFP 101, and the MFP cooperation management application 703 requests a short-range wireless communication connection to the MFP 101 using the short-range wireless communication I / F 316. In step S1005, the MFP cooperation management application 703 waits for the establishment of a short-range wireless communication connection with the MFP 101, and if the connection is established, the process proceeds to step S1006. Hereafter, unless otherwise specified, it is assumed that communication between the MFP 101 and the mobile terminal 102 is performed using short-range wireless communication.

[0103] In step S1006, the MFP cooperation management application 703 instructs the MFP 101 (notification request) to send a notification required for post-cooperation processing to the mobile terminal 102. In this embodiment, the notifications required for cooperation are two notifications: "completion of execution of cooperation button" and "request to cancel cooperation."

[0104] In step S1007, the MFP cooperation management application 703 transmits a request to acquire cooperation information to the MFP 101. The cooperation information is information necessary for the mobile terminal 102 to cooperate with the MFP 101, such as the user ID of the user logged in to the MFP 101, the IP address of the management server 103, and identification information of the MFP 101. In step S1008, the MFP cooperation management application 703 receives the cooperation information from the MFP 101 as a response to step S1007.

[0105] In step S1009, the MFP cooperation management application 703 identifies a mobile application that is displayed on the screen of the operation unit 318 or is in the foreground. In step S1010, the MFP cooperation management application 703 determines whether the identified mobile application is a target for cooperation with the MFP 101 based on whether the identified mobile application responds to a predetermined inquiry. If the identified mobile application is a target for cooperation, the MFP cooperation management application 703 advances the process to step S1011, and if not, ends the process. The method of determining whether the application is a target for cooperation is one example, and other methods may be used for the determination. For example, a list of mobile applications that are targets for cooperation may be held in advance on the mobile terminal 102, or an inquiry may be made to the management server 103. Hereinafter, the mobile application identified in step S1009 is referred to as a target application.

[0106] In step S1011, the MFP cooperation management application 703 makes an inquiry to the target application and acquires target application data from the target application. The target application data is data required when the target application cooperates with the MFP 101, and differs depending on the target application. For example, in the case of a mobile application for managing cloud storage, the target application data may be an identifier indicating a currently displayed folder, and in the case of a document creation application, the target application data may be print data for printing a document currently being created. The target application data is not limited to a single piece of data, and may be multiple pieces of data. Also, the target application data may be acquired only when the target application is a target for cooperation with the MFP.

[0107] In step S1012, the MFP cooperation management application 703 transmits the target application identifier, target application data, user ID, identification information of the MFP 101, etc. to the mobile application cooperation unit 803 of the management server 103, and instructs the creation of a cooperation button. In this embodiment, the management server 103 with the IP address included in the cooperation information acquired in step S1008 is used as the connection destination, but the MFP cooperation management application 703 may be configured to previously set the IP address of the management server 103 as the connection destination.

[0108] In step S1013, the MFP cooperation management application 703 receives the cooperation button creation result from the mobile application cooperation unit 803 of the management server 103 as a response to step S1012, and ends the process. The creation result includes whether the creation was successful, the identifier (Button ID 1201) of the created cooperation button, and the like.

[0109] Fig. 10(b) is a flowchart for explaining the processing performed by the mobile terminal 102 when the mobile terminal 102 receives a notification of completion of execution of a link button from the MFP 101. The flowchart in Fig. 10(b) corresponds to the processing performed by the mobile terminal 102 in steps S519 to S520 in the sequence diagram in Fig. 5.

[0110] In step S1020, the MFP cooperation management application 703 receives a notification that execution of the cooperation button has been completed from the MFP 101. In step S1020, the MFP cooperation management application 703 instructs the target application to perform processing after execution of the cooperation button has been completed.

[0111] In step S1022, the target application that has received the instruction performs processing after the link button is executed. The processing required after the link button is executed differs for each target application. For example, if the target application is the address book application 706, it displays a message that the message has been sent to the displayed destination. Also, if the target application is the cloud document management mobile application 704, it updates the display of the file list screen to the latest state so that the image data uploaded to the cloud by the MFP 101 is reflected.

[0112] Fig. 10(c) is a flowchart for explaining processing when the mobile terminal 102 receives a request to cancel cooperation from the MFP 101. The flowchart in Fig. 10(c) corresponds to the processing of the mobile terminal 102 in steps S522 to S523 in the sequence diagram in Fig. 5.

[0113] In step S1030, the MFP cooperation management application 703 receives a request to cancel cooperation from the MFP 101.

[0114] In step S1031 , the MFP cooperation management application 703 closes the short-range wireless communication connection with the MFP 101 .

[0115] In step S1032, the MFP cooperation management application 703 determines whether or not a cooperation button is present. The presence or absence of a cooperation button is determined based on the results of steps S1012 to S1013 in the flowchart in Fig. 10(a). If a cooperation button is present, the MFP cooperation management application 703 proceeds to step S1303, and if no cooperation button is present, the MFP cooperation management application 703 ends the process.

[0116] In step S1033, the MFP cooperation management application 703 passes the user ID and the identifier of the cooperation button to the button management unit 801 of the management server 103, and instructs the deletion of the cooperation button. In step S1034, the MFP cooperation management application 703 receives a deletion result from the button management unit 801 of the management server 103 as a response to step S1032, and ends the process.

[0117] Note that the flowchart in FIG. 10(c) shows the processing when a request to cancel linkage is received from MFP 101, but the same processing (processing from step S1032 onward) is performed when the short-range wireless communication connection with MFP 101 is closed for some reason.

[0118] Fig. 11 is a flowchart for explaining the processing of the management server 103 in this embodiment. The CPU 411 reads out a program stored in the ROM 412 and HDD 414 of the management server 103 into the RAM 413 and executes the program, thereby executing each step of the flowchart in Fig. 11.

[0119] Fig. 11(a) is a flowchart for explaining the processing when the management server 103 receives a request to obtain application button information from the MFP 101. The flowchart in Fig. 11(a) corresponds to the processing of the management server 103 in each step S502, step S512, and step S526 in the sequence diagram in Fig. 5.

[0120] In step S1101, the button management unit 801 receives a request to obtain application button information from the MFP 101. The request includes a user ID.

[0121] In step S1102, the button management unit 801 refers to the button management table 802 and extracts application button information corresponding to the user ID included in the acquisition request. For example, if the user ID is "u001", the application button information to be extracted is information on a total of six application buttons: five shared buttons defined in rows b001 to b005 and one personal button defined in row b101. In addition, if a linked button has already been created, information on the linked button in row b201 is also extracted.

[0122] In step S1103, the button management unit 801 transmits information about the extracted application button as a response to step S1101 to the MFP 101, and ends the process.

[0123] Fig. 11(b) is a flowchart for explaining the processing when the management server 103 receives an instruction to create a link button from the mobile terminal 102. The flowchart in Fig. 11(b) corresponds to the processing of the management server 103 in steps S509 to S511 in the sequence diagram in Fig. 5.

[0124] In step S1110, the mobile application cooperation unit 803 receives an instruction to create a cooperation button from the mobile terminal 102. The creation instruction includes an identifier of the target application, target application data, a user ID, and identification information of the MFP 101.

[0125] In step S1111, the mobile application cooperation unit 803 extracts information corresponding to the target application from the mobile application cooperation table 804. Specifically, it extracts a record in which the value of the MobileAppID 1302 column is the same as the identifier of the target application included in the creation instruction. For example, if the identifier of the target application is "WebDrive", the m001 row is obtained as the extraction result.

[0126] In step S1112, the mobile application cooperation unit 803 determines whether or not the information corresponding to the target application was extracted in step S1111. If the cooperation information was extracted, the mobile application cooperation unit 803 proceeds to step S1113, and if the cooperation information was not extracted, the mobile application cooperation unit 803 responds with an error to the mobile terminal 102 in step S1120 and ends the process.

[0127] In step S1113, the mobile application cooperation unit 803 generates information for registering the cooperation button in the button management table 802, based on the creation instruction received in step S1110 and the corresponding information extracted in step S1111.

[0128] In step S1114, the button management unit 801 registers information about the generated linked button in the button management table 802. For example, if the creation instruction received in step S1110 is for a target application identifier “WebDrive”, target application data “current path= / my / folder”, and user ID “u001”, then b201 rows are created in the button management table 802.

[0129] ButtonID 1201 is assigned by button management unit 801. ButtonType 1202 is set to "MobileLink" indicating that it is a link button. ButtonName 1203 is set to a value obtained by replacing the variable of ButtonName 1303 in mobile application link table 804 with the value of the target application data. TargetType 1204 is set to the value of TargetType 1304 in mobile application link table 804. ButtonTarget 1205 is set to the value of ButtonTarget 1305 in mobile application link table 804. ButtonParameter 1206 is set to a value obtained by replacing the value of ButtonParameter 1306, the value of MobileParamName 1307, and MobileParameKey 1308 in mobile application link table 804 with the target application data. ViewOrder 1207 is set to "-1" so that the link button is displayed at the top of the menu screen of MFP 101. UserID 1208 is set to the user ID included in the creation instruction received in step S1110.

[0130] In this embodiment, the mobile application linkage table 804 is used to create the linkage button, but it is also possible to create a linkage button without using the mobile application linkage table 804. For example, the target application data acquired from the target application by the MFP linkage management application 703 in step S1011 in FIG. 10(a) may be configured to include all information required to register a linkage button in the button management table 802.

[0131] In step S1115, the mobile application cooperation unit 803 notifies the mobile terminal 102 of the creation result of the cooperation button as a response to step S1110. The creation result includes whether the creation was successful, the identifier (Button ID 1201) of the created cooperation button, and the like.

[0132] In step S1116, the button management unit 801 notifies the MFP 101 that the button information has been updated, and ends the process.

[0133] Fig. 11(c) is a flowchart for explaining processing when the management server 103 receives an instruction to delete a link button from the mobile terminal 102. The flowchart in Fig. 11(c) corresponds to the processing of the management server 103 in steps S523 to S525 in the sequence diagram in Fig. 5.

[0134] In step S1130, the button management unit 801 receives an instruction to delete the linked button from the mobile terminal 102. The deletion instruction includes the identifier of the linked button and the user ID. In step S1131, the button management unit 801 determines whether or not information of the linked button corresponding to the deletion instruction exists in the button management table 802. Specifically, the button management unit 801 determines whether or not there is a record whose ButtonID 1201 matches the value of the identifier of the linked button received in step S1130. If information of the linked button exists, the button management unit 801 proceeds to step S1132, and if not, in step S1140, the button management unit 801 responds to the mobile terminal 102 that there was no button to delete and ends the process.

[0135] In step S1132, the button management unit 801 deletes from the button management table 802 the record of the linked button corresponding to the deletion instruction received in step S1130.

[0136] In step S1133, the mobile application cooperation unit 803 notifies the mobile terminal 102 of the deletion result of the cooperation button as a response to step S1130. In step S1134, the button management unit 801 notifies the MFP 101 that the button information has been updated, and ends the process.

[0137] As described above, the procedure described in this embodiment does not require complicated procedures, and the user can simply place the mobile terminal in a designated place to execute a function displayed on the screen of the mobile terminal or corresponding to a mobile application in the foreground on the MFP. Note that in this embodiment, a configuration in which a user logs in to the MFP 101 is shown, but it is not necessary to log in to the MFP 101, and the process may proceed as a "guest" and the link button may be displayed without using a user ID. In addition, in this embodiment, the mobile terminal instructs the creation of the link button, but this is not limited to this, and the MFP 101 may instruct the creation of the link button. In this case, the mobile terminal 102 notifies the MFP 101 of the target application and target application data, and the MFP 101 issues an instruction to create a link button to the management server based on the notified information.

[0138] Second Embodiment In the first embodiment, an example has been described in which one link button is created according to a mobile application displayed on the screen of the mobile terminal 102 or in the foreground. However, depending on the mobile application, the link button to be created may differ depending on the state of the application. Also, there may be cases where it is better to create not only one but multiple link buttons. A specific example will be shown in which the target application is a cloud photo management application. When the mobile terminal 102 displays a cloud path, it is expected that an image scanned by the MFP 101 will be saved in the path. On the other hand, when the mobile terminal 102 displays document data saved in the cloud, it is expected that the document data will be printed by the MFP 101. In this way, even for the same application, the link button to be created may be changed depending on the state of the application.

[0139] Therefore, as the second embodiment, an embodiment configured to create multiple link buttons according to a mobile application displayed on the screen of the mobile terminal 102 or in the foreground and its state will be described. Since the second embodiment is a modification of the first embodiment, only the differences will be described.

[0140] The processing of the mobile terminal 102 in the second embodiment will be described. In step S1011 in Fig. 10(a), the MFP cooperation management application 703 makes an inquiry to the target application and acquires target application data from the target application. At this time, the status of the target application is acquired as part of the target application data. Here, the status of the target application may be based on the target application data. In step S1012, the MFP cooperation management application 703 transmits the identifier of the target application, the target application data including the status of the target application, and the user ID to the mobile application cooperation unit 803 of the management server 103, and instructs the creation of a cooperation button.

[0141] Next, the processing of the management server 103 in the second embodiment will be described. In step S1110 in Fig. 11(b), the mobile application cooperation unit 803 receives an instruction to create a cooperation button from the mobile terminal 102. The creation instruction includes an identifier of the target application, target application data including the state of the target application, and a user ID. In step S1111, the mobile application cooperation unit 803 extracts information corresponding to the state of the target application from the mobile application cooperation table 804.

[0142] 15 shows a mobile application linkage table 804 in the second embodiment. The difference from the mobile application linkage table 804 in the first embodiment is that a MobileAppStatus 1501 column has been added. Columns 1301 to 1308 are the same as in the first embodiment, so their explanation will be omitted. The MobileAppStatus 1501 column is a column that defines the status of the mobile application defined in the MobileAppID 1302 column.

[0143] For example, columns m001 and m002 both define information about a link button to be created when a cloud document management application with “WebDrive” as an identifier is displayed, but column 1501 defines information about a link button that differs depending on the state of the mobile application (if the application state is “Document List Screen”, “Scan and Save” is defined, and if the application state is “Document Data Display”, “Print Document Data” is defined). Also, rows m103 and m104 define that the value of column MobileAppID1302 and the value of column MobileAppStatus1501 are the same, and multiple link buttons are created even in the same application state. Specifically, when cloud photo management application 705 with “PhotoBox” as an identifier is in album mode, two link buttons are created based on information defined in rows m103 and m104. The link button created based on information in row m103 is an application button for adding image data scanned by MFP101 to the location of the album displayed by cloud photo management application 705 on mobile terminal 102. On the other hand, the link button created based on the information on line m104 is an application button for printing, on the MFP 101, thumbnails of photos included in the album displayed by the cloud photo management application 705 on the mobile terminal 102.

[0144] Fig. 16 shows a part of the button management table 802 in the case where multiple link buttons created in the same application state are held in the second embodiment, and information on two application buttons is registered as link buttons. The button management table 802 also registers the record shown in Fig. 12(a). Row b301 is information on a link button created based on row m103 of the mobile application link table 804 shown in Fig. 15. Row b302 is information on a link button created based on row m104 of the mobile application link table 804 shown in Fig. 15.

[0145] 17 is an example of a menu screen in the second embodiment. On the menu screen, a total of eight application buttons are displayed in the order defined in the ViewOrder1207 column: two link buttons defined in rows b301 and b302, five shared buttons defined in rows b001 to b005, and one personal button defined in row b101.

[0146] As described above, by the procedure described in this embodiment, when the MFP and mobile terminal communicate with each other, the MFP becomes capable of executing processing according to the state of the mobile application displayed on the screen of the mobile terminal or in the foreground, thereby improving user convenience.

[0147] (Third embodiment) In the first and second embodiments, the system configuration is such that the management server 103 manages the application buttons displayed on the menu screen of the MFP 101. When there are multiple MFPs, there is an advantage in that the same menu screen can be displayed on all MFPs by managing the application buttons with the management server 103. However, when there is only one MFP or when the same menu screen is not used on multiple MFPs, management by the management server 103 is not necessarily required. Therefore, as the third embodiment, an embodiment without the management server 103 will be described. As the third embodiment is a modification of the first embodiment, only the differences will be described.

[0148] 18 is a diagram showing the software configuration of MFP 101 in the third embodiment. This software configuration is the same as that of MFP 101 in the first embodiment, but with the addition of software and tables of management server 103.

[0149] In the third embodiment, all of the processes that were performed by the management server 103 in the first embodiment are performed by the MFP 101. That is, the process in the flowchart of FIG.

[0150] 9B, the mobile terminal linking unit 604 sends the IP address of its own device to the mobile terminal 102 as the IP address of the management server 103. In this way, the communication that the mobile terminal 102 performed with the management server 103 in the first embodiment becomes communication with the MFP 101 in the third embodiment.

[0151] Alternatively, the communication between the mobile terminal 102 and the MFP 101 that serves as a management server may be configured to be performed directly using short-range wireless communication without using a network I / F. In that case, it is not necessary to identify the user, and it is sufficient to display a link button on the menu screen currently displayed on the MFP 101.

[0152] As described above, by the procedure described in this embodiment, even if a management server does not exist, it is possible to perform the same processing as in the first and second embodiments.

[0153] (Other embodiments) The present invention can also be realized by executing the following process, in which software (programs) that realize the functions of the above-described embodiments are supplied to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads and executes the programs.

Claims

1. An information processing device capable of communicating with a terminal capable of executing an application, the information processing device acquiring information related to cooperation between the information processing device and the terminal for executing a part of processing of the application on the information processing device through communication established between the information processing device and the terminal, the information processing device transmitting an identifier of the application being executed on the terminal, a storage means for storing an identifier of the application in association with predetermined information for displaying a button for calling a predetermined process corresponding to the application; a first receiving means for receiving an application identifier transmitted from the terminal; a display means for displaying, on a display unit, a button for invoking a process indicated by the predetermined information, based on the predetermined information stored in association with the identifier of the application received by the first receiving means; an execution means for executing the predetermined process when a button displayed on the display means is pressed; an authentication means for authenticating a user; having the display means deletes the button based on the fact that the link has been released and based on the fact that a request to delete the button transmitted from the terminal has been received; The display means creates a button based on information of the user authenticated by the authentication means.

23. An information processing apparatus comprising:

2. the terminal has a communication means for performing short-range wireless communication with the information processing device, When the signal strength of the short-range wireless communication from the information processing device received by the communication means is equal to or greater than a predetermined value, the first receiving means receives an identifier of the application transmitted from the terminal based on the acquisition of information related to cooperation.

2. The information processing apparatus according to claim 1,

3. The terminal further transmits data to be processed in an application executed on the terminal, and the predetermined processing is processing using the data.

3. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer.

4. The application running on the terminal is an application displayed on the display unit of the terminal or an application running in the foreground on the terminal.

4. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer.

5. The terminal transmits an identifier of an application running in the foreground on the terminal when the terminal and the information processing device communicate with each other.

5. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer.

6. The predetermined process is a process according to the state of an application being executed on the terminal.

6. The information processing apparatus according to claim 1,

7. The execution means executes the predetermined process using a Web browser.

7. The information processing apparatus according to claim 1,

8. At least one of user information and identification information of the information processing device is communicated between the information processing device and the terminal based on communication between the terminal and the information processing device.

8. The information processing apparatus according to claim 1,

9. When the short-range wireless communication is performed, an application for identifying an application being executed on the terminal is started on the terminal.

3. The information processing system according to claim 2.

10. The terminal transmits an identifier of the application to the information processing device.

10. The information processing apparatus according to claim 1,

Images