JP2018195208A - Information processing system, apparatus, and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically select an application frequently used by a user for each user. An information processing system according to an embodiment is an information processing system in which a plurality of applications are mounted and a plurality of users can log in. The information processing system includes: A first selection unit that selects a first application that is activated immediately after the target user logs in; and a control unit that activates the first application of the target user immediately after the target user logs in. [Selection] Figure 2

Description

  The present invention relates to an information processing system, apparatus, and method.

  Conventionally, an MFP (Multi-Function Peripheral) having a plurality of functions such as a copy function, a print function, a FAX function, and a scanner function has been used. In the MFP, for example, an activation button of an application (hereinafter referred to as “application”) for using each function is displayed on the touch panel. The user starts an application by touching an activation button displayed on the touch panel, and uses a desired function.

  As a method for improving the convenience of the MFP, there are known a method of setting a priority application that is automatically activated when the MFP is activated, and a method of always displaying an application activation button as a function key. According to this method, by setting an application that is frequently used by the user as the priority application or the function key application, the operation for the user to start the application can be reduced, and the convenience of the MFP can be improved. .

  However, in the conventional method described above, the administrator or user of the MFP has to select the priority application and the function key application in advance, which is troublesome.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to automatically select an application that is frequently used by a user for each user.

  An information processing system according to an embodiment is an information processing system in which a plurality of applications are mounted and a plurality of users can log in, and the target user logs in based on usage history of the plurality of applications of the target user A first selection unit that selects a first application to be started immediately after; and a control unit that starts the first application of the target user immediately after the target user logs in.

  According to each embodiment of the present invention, an application that is frequently used by a user can be automatically selected for each user.

2 is a diagram illustrating an example of a hardware configuration of an MFP. FIG. The figure which shows an example of a function structure of the operation part which concerns on 1st Embodiment. The figure which shows an example of a usage history. The figure which shows an example of the screen displayed on an operation panel. The flowchart which shows an example of the update process of usage history. The sequence diagram which shows an example of the process of the operation part immediately after the login of an object user. The figure which shows an example of a function structure of the operation part which concerns on 2nd Embodiment. The figure which shows an example of user information. The flowchart which shows an example of the selection process of a priority application. The flowchart which shows an example of the selection process of a function key application. The sequence diagram which shows an example of the process of the operation part immediately after the login of an object user. The figure which shows an example of a priority application dialog box. The figure which shows an example of a function key application dialog box. The figure which shows the other example of a function key application dialog box. The figure which shows an example of an information processing system. The figure which shows an example of the hardware constitutions of a server.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In addition, regarding the description of the specification and the drawings according to each embodiment, constituent elements having substantially the same functional configuration are denoted by the same reference numerals and overlapping description is omitted.

<First Embodiment>
The information processing apparatus according to the first embodiment will be described with reference to FIGS. The information processing apparatus according to the present embodiment is an apparatus that has a plurality of functions that can be used by a user and that is equipped with an application for using each function and that allows a plurality of users to log in. The information processing apparatus can be, for example, an MFP, a printer, a copier, a FAX, a scanner, an electronic information board, a digital camera, or the like. Hereinafter, the information processing apparatus according to the present embodiment will be described using an example in which the information processing apparatus is an MFP.

  The MFP 1 according to the present embodiment has a plurality of functions such as a copy function, a print function, a FAX function, and a scanner function, and an application for using each of these functions is installed. A plurality of users who can log in are registered in the MFP 1.

  First, the hardware configuration of the MPF 1 according to the present embodiment will be described. FIG. 1 is a diagram illustrating an example of a hardware configuration of the MFP 1. The MFP 1 in FIG. 1 includes a main body 10 that realizes each function of the MFP 1 and an operation unit 20 that receives an input corresponding to a user operation.

  The main body 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an HDD (Hard Disk Drive) 14, a communication I / F 15, and a connection I / F 16 And an engine unit 17 and a system bus 18.

  The CPU 11 controls the overall operation of the main body 10 by executing a program, and realizes the function of the main body 10.

  The ROM 12 stores various data, an OS (Operating System) of the main body 10 executed by the CPU 11, and various applications (AP).

  The RAM 13 provides a work area for the CPU 11.

  The HDD 14 stores various data. The HDD 14 may store the OS of the main body 10 executed by the CPU 11 and various applications (AP).

  The communication I / F 15 is an interface for connecting the main body 10 to a network such as a LAN (Local Area Network) or the Internet. The main body 10 communicates with an external device on the network via the communication I / F 15.

  The connection I / F 16 is an interface for connecting the main body 10 and the operation unit 20. The main body 10 communicates with the operation unit 20 via the connection I / F 16.

  The engine unit 17 is hardware that executes general-purpose processing for realizing a copy function, a print function, a FAX function, a scanner function, and the like. The engine unit 17 includes a printing device, a scanner device, a transport device, an ADF (Auto Document Feeder), and the like.

  The system bus 18 interconnects the CPU 11, ROM 12, RAM 13, HDD 14, communication I / F 15, connection I / F 16, and engine unit 17.

  The operation unit 20 includes a CPU 21, a ROM 22, a RAM 23, a flash memory 24, a communication I / F 25, a connection I / F 26, an operation panel 27, and a system bus 28.

  The CPU 21 executes the program to control the overall operation of the operation unit 20 and realize the function of the operation unit 20.

  The ROM 22 stores various data, the OS of the operation unit 20 executed by the CPU 21, and various applications (AP). The applications stored in the ROM 22 include applications for the user to use the copy function, print function, FAX function, and scanner function.

  The RAM 23 provides a work area for the CPU 21.

  The flash memory 24 stores various data. The flash memory 24 may store the OS of the operation unit 20 executed by the CPU 21 and various applications (AP). The application stored in the flash memory 24 may include an application for the user to use a copy function, a print function, a FAX function, and a scanner function.

  The communication I / F 25 is an interface for connecting the operation unit 20 to a network such as a LAN or the Internet. The operation unit 20 communicates with an external device on the network via the communication I / F 25.

  The connection I / F 26 is an interface for connecting the operation unit 20 and the main body 10. The operation unit 20 communicates with the main body 10 via the connection I / F 26.

  The operation panel 27 is an input / output device in which a touch panel as an input device and a display as a display device are integrated. Operation panel 27 accepts various types of input by a user's touch operation and displays various types of information (information corresponding to the accepted input, information indicating the operation status of MFP 1, information indicating a setting state, and the like).

  The system bus 28 connects the CPU 21, ROM 22, RAM 23, flash memory 24, communication I / F 25, connection I / F 26, and operation panel 27 to each other.

  In the example of FIG. 1, the MPF 1 includes the main body 10 and the operation unit 20, but the main body 10 and the operation unit 20 may be integrated. The MFP 1 may also include an input device such as a hardware key and a display device such as a lamp.

  Next, a functional configuration of the operation unit 20 according to the present embodiment will be described. FIG. 2 is a diagram illustrating an example of a functional configuration of the operation unit 20 according to the present embodiment. 2 includes an operation reception unit 101, an authentication unit 102, a control unit 103, a usage history storage unit 104, a priority application selection unit (first selection unit) 105, and a function key selection unit (first 2 selection unit) 106. Each of these functional configurations is realized by the CPU 21 executing a program and cooperating with each hardware configuration.

  The operation reception unit 101 receives a user operation on the operation unit 20 and inputs information corresponding to the received operation to the operation unit 20.

  The authentication unit 102 executes authentication processing based on authentication information input from the user. The authentication information includes a user ID and a password. The user ID is user identification information. The authentication unit 102 logs in the user when the authentication is successful, and does not log in the user when the authentication fails.

  The control unit 103 controls the overall operation of the operation unit 20. For example, the control unit 103 activates an application, displays a screen corresponding to the application, updates a usage history, and the like. Details of the operation of the control unit 103 will be described later.

  The usage history storage unit 104 stores the usage history of each application for a predetermined period of each user registered as a loginable user. The usage history includes the usage frequency during login for each application and the usage frequency immediately after login for each application. The usage frequency may be the number of usages or usage time.

  FIG. 3 is a diagram illustrating an example of a usage history of a certain user. In the example of FIG. 3, the usage frequency is the number of usages, and the operation unit 20 includes applications named “Easy Copy”, “Easy Scan”, “Browser”, “Printer”, and “Fax”. Yes. For example, the usage count during login of “Gently Copy” is 123 times, of which the usage count immediately after login is 35 times. The usage history storage unit 104 stores a usage history as shown in FIG. 3 in association with a user ID for each user.

  The priority application selection unit 105 selects a priority application (first application) to be activated immediately after login of the target user based on the usage history of the user who logs in to the MFP 1 (hereinafter referred to as “target user”).

  The priority application selection unit 105 selects, for example, an application having the highest usage frequency immediately after login as a priority application. In this case, in the example of FIG. 3, “easy copy” having the maximum number of use (35 times) immediately after login is selected as the priority application.

  Further, the priority application selection unit 105 may select, as a priority application, an application having the highest ratio of the use frequency immediately after login to the use frequency during login. In this case, in the example of FIG. 3, the “printer” having the maximum (10/15) ratio of the number of usages immediately after login to the number of usages during login is selected as the priority application.

  In addition, the priority application selection unit 105 sets, as a priority application, an application that satisfies a predetermined condition among applications having the highest usage frequency immediately after login and applications having the highest ratio of usage frequency immediately after login to the usage frequency during login. You may choose. As the predetermined condition, for example, the ratio of the usage frequency immediately after login to the usage frequency during login is equal to or higher than a threshold (for example, 80%).

  By selecting the priority application as described above, the priority application selection unit 105 can select, as the priority application, an application that is likely to be used immediately after the target user logs in. In the present embodiment, the priority application selected by the priority application selection unit 105 is started immediately after the target user logs in, thereby reducing the operation for starting the application used by the target user and improving the convenience of the MFP 1. it can.

  Note that the priority application selection unit 105 may learn, as a priority application, an application that is likely to be used immediately after login by the target user based on the usage history of the target user. As a learning method, any learning method such as support vector machine (SVM), clustering, neural network, and decision tree can be used. In this way, by learning the priority application based on the usage history of the target user, the priority application selection unit 105 can select the priority application in consideration of changes in the usage frequency for each application. As a result, the priority application selection unit 105 can select a priority application that is more likely to be used immediately after the target user logs in.

  Based on the usage history of the target user, the function key selection unit 106 selects one or a plurality of function key applications (second applications) displayed using the start button as a function key during the login of the target user. The function key is a button that is always displayed on the screen without depending on the application being used during login of the target user. Hereinafter, the function key is referred to as FK.

  Here, FIG. 4 is a diagram illustrating an example of a screen displayed on the operation panel 27 of the operation unit 20. In the example of FIG. 4, the screen includes a header area A1, an application area A2, and a footer area A3.

  The header area A1 is an upper area of the screen. In the example of FIG. 4, in the header area A1, a copy button, a scan button, and a fax button are displayed as FKs that are always displayed during login of the target user. The copy button is an app start button for using the copy function, the scan button is an app start button for using the scan function, and the fax button is an app start for using the fax function. Button. In the example of FIG. 4, three FKs are displayed in the header area A1, but the number of FKs displayed in the header area A1 can be arbitrarily set. Further, at least a part of the FK may be displayed in the footer area A3.

  The application area A2 is an area for displaying a screen corresponding to the application being used by the target user. In the example of FIG. 4, the target user is using an application (browser) for selecting a function (application) to be used, and an application activation button (for each selectable function) is displayed in the application area A2. A copy button, a scan button, a fax button, and a printer button).

  The footer area A3 is an area at the bottom of the screen. In the example of FIG. 4, a status confirmation button, a home button, and a stop button are displayed in the footer area A3 as basic operation keys that are always displayed during use of the MPF 1. The status confirmation button is a button for displaying a status confirmation screen for displaying the status of the MFP 1. The home button is a button for displaying a home screen. The stop button is a button for stopping the job being executed. In the example of FIG. 4, three basic operation keys are displayed in the footer area A3, but the number of basic operation keys displayed in the footer area A3 can be arbitrarily set. Further, the basic operation keys are not limited to the example of FIG. Further, at least a part of the basic operation keys may be displayed in the header area A1.

  For example, the FK selection unit 106 selects N apps as FK apps in descending order of use frequency during login. In the case of N = 2, in the example of FIG. 3, “friendly copy” having the maximum number of uses (123 times) and “fax” having the second largest number of uses (50 times) are selected as FK applications. The

  Further, the FK selection unit 106 may select N or less apps whose use frequency during login is greater than or equal to a threshold as FK apps. When N = 2 and the threshold for the number of uses is 100 times, in the example of FIG. 3, “easy copy” having the number of uses (132 times) equal to or greater than the threshold (100 times) is selected as the FK application.

  Further, the FK selection unit 106 may select an application that satisfies a predetermined condition from among the applications that are frequently used during login, as the FK application. As the predetermined condition, for example, the ratio of the usage frequency during login is equal to or higher than a threshold value (for example, 50%).

  By selecting the FK application as described above, the FK selection unit 106 can select an application that is likely to be used by the target user during login as the FK application. In the present embodiment, the activation button of the FK application selected by the FK selection unit 106 is always displayed as FK, thereby reducing the operation for starting the application used by the target user during login, and the convenience of the MFP 1 Can be improved.

  Note that the FK selection unit 106 may learn, as an FK application, an application that is likely to be used during login by the target user based on the usage history of the target user. As a learning method, any learning method such as support vector machine (SVM), clustering, neural network, and decision tree can be used. In this way, by learning the FK application based on the usage history of the target user, the FK selection unit 106 can select the FK application in consideration of changes in the usage frequency for each application. As a result, the FK selection unit 106 can select an FK application that is more likely to be used by the target user during login.

  Moreover, it is preferable that the FK selection unit 106 selects an application different from the priority application as the FK application. This is because the application selected as the priority application is activated immediately after the target user logs in, and thus the target user is unlikely to operate the FK to activate the application.

  Next, processing of the operation unit 20 according to the present embodiment will be described. FIG. 5 is a flowchart illustrating an example of usage history update processing. The operation unit 20 performs the process of FIG. 5 every time the target user performs an application activation operation (touching the activation button).

  When the target user touches the start button of the application, the operation reception unit 101 receives the operation (step S101). An application touched with the start button is referred to as a target application. The operation reception unit 101 requests the control unit 103 to start the target application.

  When requested to activate the target application, the control unit 103 activates the target application (step S102). When the target application is activated immediately after login of the target user (YES in step S103), that is, when the target application is an application started immediately after login, the control unit 103 immediately after login of the target application of the target user The use frequency is updated (step S104). Specifically, when the usage frequency is the usage count, the control unit 103 increases the usage count immediately after login of the target application of the target user by one.

  Thereafter, the control unit 103 updates the usage frequency during login of the target application of the target user (step S105). Specifically, when the usage frequency is the usage count, the control unit 103 increases the usage count during login of the target application of the target user by one.

  On the other hand, when the target application is not immediately after login of the target user (NO in step S103), that is, when the target application is not an application started immediately after login, the control unit 103 is logging in the target application of the target user. The usage frequency is updated (step S105). Specifically, when the usage frequency is the usage count, the control unit 103 increases the usage count during login of the target application of the target user by one.

  FIG. 6 is a sequence diagram illustrating an example of processing of the operation unit 20 immediately after the target user logs in. The operation unit 20 executes the process of FIG. 6 every time the target user performs an authentication operation. The authentication operation is, for example, input of authentication information by the target user and touch of a login button. When the operation unit 20 includes an IC (Integrated Circuit) card reader, the authentication operation may be holding the IC card having authentication information over the IC card reader.

  When the target user inputs authentication information and touches a login button displayed on the screen, the operation reception unit 101 receives the operation and requests the authentication unit 102 to authenticate the target user (step S201). At this time, the operation reception unit 101 passes authentication information input from the target user to the authentication unit 102.

  When the authentication unit 102 is requested to authenticate the target user, the authentication unit 102 performs authentication processing by determining whether the authentication information input by the user matches the authentication information of the registered user stored in advance (step S202). . If the authentication of the target user is successful, the authentication unit 102 logs the target user into the MFP 1. Further, the authentication unit 102 notifies the control unit 103 of the fact that the authentication has been successful and the user ID of the target user (step S203). If the authentication of the target user fails, the authentication unit 102 may display on the screen that the authentication failed without logging the target user into the MFP 1.

  When notified that the authentication is successful, the control unit 103 requests the priority application selection unit 105 to select a priority application (step S204). At this time, the control unit 103 notifies the priority application selection unit 105 of the user ID of the target user.

  When requested to select a priority application, the priority application selection unit 105 requests the usage history of the target user from the usage history storage unit 104 (step S205). At this time, the priority application selection unit 105 notifies the usage history storage unit 104 of the user ID of the target user.

  When the usage history of the target user is requested, the usage history storage unit 104 extracts the usage history of the target user from the usage histories of the plurality of users based on the notified user ID, and uses the target user. The history is passed to the priority application selection unit 105 (step S206).

  Upon receiving the usage history of the target user, the priority application selection unit 105 selects a priority application based on the received usage history (step S207). The method for selecting the priority application is as described above. Thereafter, the priority application selection unit 105 notifies the control unit 103 of the selected priority application (step S208).

  When notified of the priority application, the control unit 103 activates the notified priority application and causes the home screen of the priority application to be displayed on the screen (application area A2) (step S209). The control unit 103 may update the usage frequency immediately after the priority application is logged in after the priority application is activated.

  In addition, when notified that the authentication is successful, the control unit 103 requests the FK selection unit 106 to select an FK application (step S210). At this time, the control unit 103 notifies the FK selection unit 106 of the user ID of the target user.

  When requested to select the FK application, the FK selection unit 106 requests the usage history of the target user from the usage history storage unit 104 (step S211). At this time, the FK selection unit 106 notifies the usage history storage unit 104 of the user ID of the target user.

  When the usage history of the target user is requested, the usage history storage unit 104 extracts the usage history of the target user from the usage histories of the plurality of users based on the notified user ID, and uses the target user. The history is passed to the FK selection unit 106 (step S212).

  Upon receiving the usage history of the target user, the FK selection unit 106 selects an FK application based on the received usage history (step S213). The method for selecting the FK application is as described above. Thereafter, the FK selection unit 106 notifies the control unit 103 of the selected FK application (step S214).

  When notified of the FK application, the control unit 103 displays the notified activation button of the FK application on the screen (header area A1) as FK (step S215).

  Through the above processing, when the target user logs in, a screen is displayed on the operation panel 27 in a state where the priority application selected by the priority application selection unit 105 is activated. The home area of the priority application is displayed in the application area A2 of the screen, and the activation button of the FK application selected by the FK selection unit 106 is displayed in the header area A1.

  As described above, according to the present embodiment, the operation unit 20 can automatically select, for each target user, an app that is frequently used by the target user as a priority app or an FK app. Thereby, the target user can use an application with high usage frequency from a screen displayed immediately after login, or can start up by touching FK. As a result, the operation for the target user to start the application can be reduced, and the convenience of the MFP 1 can be improved.

  Further, as in the example of FIG. 6, the priority application selecting unit 105 can select a priority application based on the latest usage history of the target user by selecting the priority application every time the target user logs in. Thereby, the priority application selection part 105 can select accurately an application with high usage frequency of a target user as a priority application.

  Further, as in the example of FIG. 6, the FK selection unit 106 can select the FK application based on the latest usage history of the target user by selecting the FK application every time the target user logs in. Thereby, the FK selection part 106 can select an application with high use frequency of an object user with high accuracy as an FK application.

  In the present embodiment, steps S204 to S209 and steps S210 to S215 in FIG. 6 may be executed in the reverse order or may be executed in parallel.

  Further, the priority application selection unit 105 and the FK selection unit 106 may select and store the priority application and the FK application in advance. Thereby, since the process of step S205-S207 of FIG. 6, S211-S213 can be abbreviate | omitted, the process at the time of login of an object user can be shortened.

Second Embodiment
An MFP 1 according to the second embodiment will be described with reference to FIGS. In the first embodiment, the case where the usage history of the target user is stored in the usage history storage unit 104 has been described. In contrast, in the present embodiment, a case where the usage history of the target user is not necessarily stored in the usage history storage unit 104 will be described. Note that the hardware configuration of the MFP 1 according to the present embodiment is the same as that of the first embodiment.

  FIG. 7 is a diagram illustrating an example of a functional configuration of the operation unit 20 according to the present embodiment. The operation unit 20 in FIG. 7 includes a user information storage unit 107. Other configurations are the same as those of the first embodiment.

  The user information storage unit 107 stores user information of each user registered as a user who can use the MFP 1. The user information includes a user ID and attribute information. The attribute information is arbitrary information indicating the user's attribute and includes the user's affiliation, job title, and the like.

  FIG. 8 is a diagram illustrating an example of user information. Each record in FIG. 8 corresponds to user information of each user. In the example of FIG. 8, the user information includes a user ID, a user name, and affiliation (attribute information). For example, in the record on the first line, the user ID is U001, the user name is A, and the affiliation is the personnel department. The user information is not limited to the example of FIG. The user information may include a plurality of types of attribute information.

  FIG. 9 is a flowchart illustrating an example of priority application selection processing. The processing in FIG. 9 corresponds to the processing in steps S205 to S207 in FIG. Therefore, when the priority application selection unit 105 is requested by the control unit 103 to select a priority application, the priority application selection unit 105 starts the process of FIG.

  When the selection of the priority application is requested by the control unit 103, the priority application selection unit 105 requests the usage history of the target user from the usage history storage unit 104 (step S301). At this time, the priority application selection unit 105 notifies the usage history storage unit 104 of the user ID of the target user.

  When the usage history of the target user is requested, the usage history storage unit 104 extracts the usage history of the target user from the usage histories of a plurality of users based on the notified user ID. When there is a usage history of the target user (YES in step S302), the usage history storage unit 104 extracts the usage history of the target user and passes the usage history of the target user to the priority application selection unit 105 (step S311).

  Upon receiving the usage history of the target user, the priority application selection unit 105 selects a priority application based on the received usage history (step S312). The method for selecting the priority application is as described above. Thereafter, the priority application selection unit 105 notifies the control unit 103 of the selected priority application.

  On the other hand, when there is no usage history of the target user (NO in step S302), the usage history storage unit 104 notifies the priority application selection unit 105 to that effect. As a case where the usage history of the target user does not exist, a case where the target user logs in to the MFP 1 for the first time, a case where the usage history stored in the usage history storage unit 104 is reset, or the like can be considered.

  When notified that there is no usage history of the target user, the priority application selection unit 105 requests the user ID of the user with the same attribute from the user information storage unit 107 (step S303). At this time, the priority application selection unit 105 notifies the user information storage unit 107 of the user ID of the target user.

  The attribute same user is another user having the same attribute information as the target user. In the example of FIG. 8, when the user A is the target user, the user D having the same attribute information (affiliation = HR) as the user A is the same attribute user.

  When the user ID of the user with the same attribute is requested, the user information storage unit 107 extracts and extracts the user ID of the user with the same attribute from the user IDs of the plurality of users based on the notified user ID. The user ID of the same attribute user is passed to the priority application selection unit 105 (step S304). The user information storage unit 107 may pass the user IDs of all users with the same attribute to the priority application selection unit 105 or may pass the user IDs of some users with the same attribute to the priority application selection unit 105.

  Upon receiving the user ID of the same attribute user from the user information storage unit 107, the priority application selection unit 105 requests the usage history storage unit 104 for the usage history of the same attribute user (step S305). At this time, the priority application selection unit 105 notifies the usage history storage unit 104 of the user ID of the same attribute user.

  When the usage history of the user with the same attribute is requested, the usage history storage unit 104 extracts the usage history of the user with the same attribute from the usage histories of the plurality of users based on the notified user ID. When there is a usage history of the same attribute user (YES in step S306), the usage history storage unit 104 extracts the usage history of the same attribute user and passes the usage history of the same attribute user to the priority application selection unit 105 (step S306). S311).

  Upon receiving the usage history of the same attribute user, the priority application selection unit 105 selects a priority application based on the received usage history (step S312). The method for selecting the priority application is as described above. Thereafter, the priority application selection unit 105 notifies the control unit 103 of the selected priority application.

  In general, it is considered that the usage tendency of the application of the target user and the same attribute user is similar. Therefore, as described above, by selecting the priority application of the target user based on the usage history of the same attribute user, the priority application selection unit 105 can select an application that is likely to be used by the target user as the priority application. .

  On the other hand, when there is no usage history of users with the same attribute (NO in step S306), the usage history storage unit 104 notifies the priority application selection unit 105 to that effect. As a case where there is no usage history of a user with the same attribute, a case where a user with the same attribute has never logged in to the MFP 1 or a case where the usage history stored in the usage history storage unit 104 is reset can be considered.

  When notified that there is no usage history of the same attribute user, the priority application selection unit 105 requests the user information storage unit 107 for the user ID of the attribute similar user (step S307). At this time, the priority application selection unit 105 notifies the user information storage unit 107 of the user ID of the target user.

  An attribute-similar user is another user having attribute information similar to the target user. In the example of FIG. 8, when the user A is the target user and the human resources department and the accounting department are similar, the user B having attribute information (affiliation = accounting department) similar to the user A is an attribute similar user. The similarity relationship of attribute information is set in advance and stored in the user information storage unit 107.

  When the user ID of the attribute similar user is requested, the user information storage unit 107 extracts and extracts the user ID of the attribute similar user from the user IDs of the plurality of users based on the notified user ID. The user ID of the attribute-similar user is passed to the priority application selection unit 105 (step S308). The user information storage unit 107 may pass the user IDs of all attribute-similar users to the priority application selection unit 105, or may pass the user IDs of some attribute-similar users to the priority application selection unit 105.

  Upon receiving the user ID of the attribute similar user from the user information storage unit 107, the priority application selection unit 105 requests the usage history of the attribute similar user from the usage history storage unit 104 (step S309). At this time, the priority application selection unit 105 notifies the usage history storage unit 104 of the user ID of the attribute similar user.

  When the usage history of the attribute similar user is requested, the usage history storage unit 104 extracts the usage history of the attribute similar user from the usage history of the plurality of users based on the notified user ID. If there is a usage history of the attribute similar user (YES in step S310), the usage history storage unit 104 extracts the usage history of the attribute similar user and passes the usage history of the attribute similar user to the priority application selection unit 105 (step) S311).

  Upon receiving the usage history of the attribute-similar user, the priority application selection unit 105 selects a priority application based on the received usage history (step S312). The method for selecting the priority application is as described above. Thereafter, the priority application selection unit 105 notifies the control unit 103 of the selected priority application.

  In general, it is considered that the application usage tendency of the target user and the attribute similar user is similar. Therefore, as described above, by selecting the priority application of the target user based on the usage history of the attribute similar user, the priority application selection unit 105 can select an application that is likely to be used by the target user as the priority application. .

  On the other hand, when there is no usage history of the attribute similar user (NO in step S310), the usage history storage unit 104 notifies the priority application selection unit 105 to that effect. As a case where there is no usage history of the attribute-similar user, a case where the attribute-similar user has never logged in to the MFP 1 or a case where the usage history stored in the usage history storage unit 104 is reset can be considered.

  When notified that there is no usage history of the attribute-similar user, the priority application selection unit 105 selects the default application as the priority application (step S313). The default application is an application preset as a default value of the priority application. The default application is set by the administrator or user of the MFP 1. Thereafter, the priority application selection unit 105 notifies the control unit 103 of the selected priority application.

  FIG. 10 is a flowchart illustrating an example of FK application selection processing. The process in FIG. 10 corresponds to the processes in steps S211 to S213 in FIG. Therefore, when FK selection unit 106 is requested by controller 103 to select an FK application, it starts the process of FIG.

  When the selection of the FK application is requested from the control unit 103, the FK selection unit 106 requests the usage history of the target user from the usage history storage unit 104 (step S401). At this time, the FK selection unit 106 notifies the usage history storage unit 104 of the user ID of the target user.

  When the usage history of the target user is requested, the usage history storage unit 104 extracts the usage history of the target user from the usage histories of a plurality of users based on the notified user ID. When there is a usage history of the target user (YES in step S402), the usage history storage unit 104 extracts the usage history of the target user and passes the usage history of the target user to the FK selection unit 106 (step S411).

  Upon receiving the usage history of the target user, the FK selection unit 106 selects an FK application based on the received usage history (step S412). The method for selecting the FK application is as described above. Thereafter, the FK selection unit 106 notifies the control unit 103 of the selected FK application.

  On the other hand, when there is no usage history of the target user (NO in step S402), the usage history storage unit 104 notifies the FK selection unit 106 to that effect. As a case where the usage history of the target user does not exist, a case where the target user logs in to the MFP 1 for the first time, a case where the usage history stored in the usage history storage unit 104 is reset, or the like can be considered.

  When notified that there is no usage history of the target user, the FK selection unit 106 requests the user information storage unit 107 for the user ID of the same attribute user (step S403). At this time, the FK selection unit 106 notifies the user information storage unit 107 of the user ID of the target user.

  The attribute same user is another user having the same attribute information as the target user. In the example of FIG. 8, when the user A is the target user, the user D having the same attribute information (affiliation = HR) as the user A is the same attribute user.

  When the user ID of the user with the same attribute is requested, the user information storage unit 107 extracts and extracts the user ID of the user with the same attribute from the user IDs of the plurality of users based on the notified user ID. The user ID of the same attribute user is passed to the FK selection unit 106 (step S404). The user information storage unit 107 may pass user IDs of all users with the same attribute to the FK selection unit 106, or may pass user IDs of some users with the same attribute to the FK selection unit 106.

  When the FK selection unit 106 receives the user ID of the user with the same attribute from the user information storage unit 107, the FK selection unit 106 requests the usage history of the user with the same attribute from the usage history storage unit 104 (step S405). At this time, the FK selection unit 106 notifies the usage history storage unit 104 of the user ID of the same attribute user.

  When the usage history of the user with the same attribute is requested, the usage history storage unit 104 extracts the usage history of the user with the same attribute from the usage histories of the plurality of users based on the notified user ID. When there is a usage history of the same attribute user (YES in step S406), the usage history storage unit 104 extracts the usage history of the same attribute user and passes the usage history of the same attribute user to the FK selection unit 106 (step S411). ).

  Upon receiving the usage history of the same attribute user, the FK selection unit 106 selects an FK application based on the received usage history (step S412). The method for selecting the FK application is as described above. Thereafter, the FK selection unit 106 notifies the control unit 103 of the selected FK application.

  In general, it is considered that the usage tendency of the application of the target user and the same attribute user is similar. Therefore, as described above, by selecting the FK application of the target user based on the usage history of the same attribute user, the FK selection unit 106 can select an application that is highly likely to be used by the target user as the FK application.

  On the other hand, when there is no usage history of users with the same attribute (NO in step S406), the usage history storage unit 104 notifies the FK selection unit 106 to that effect. As a case where there is no usage history of a user with the same attribute, a case where a user with the same attribute has never logged in to the MFP 1 or a case where the usage history stored in the usage history storage unit 104 is reset can be considered.

  When notified that there is no usage history of the same attribute user, the FK selection unit 106 requests the user information storage unit 107 for the user ID of the attribute similar user (step S407). At this time, the FK selection unit 106 notifies the user information storage unit 107 of the user ID of the target user.

  An attribute-similar user is another user having attribute information similar to the target user. In the example of FIG. 8, when the user A is the target user and the human resources department and the accounting department are similar, the user B having attribute information (affiliation = accounting department) similar to the user A is an attribute similar user. The similarity relationship of attribute information is set in advance and stored in the user information storage unit 107.

  When the user ID of the attribute similar user is requested, the user information storage unit 107 extracts and extracts the user ID of the attribute similar user from the user IDs of the plurality of users based on the notified user ID. The user ID of the attribute similar user is passed to the FK selection unit 106 (step S408). The user information storage unit 107 may pass the user IDs of all the attribute similar users to the FK selection unit 106 or may pass the user IDs of some attribute similar users to the FK selection unit 106.

  Upon receiving the user ID of the attribute similar user from the user information storage unit 107, the FK selection unit 106 requests the usage history of the attribute similar user from the usage history storage unit 104 (step S409). At this time, the FK selection unit 106 notifies the usage history storage unit 104 of the user ID of the attribute similar user.

  When the usage history of the attribute similar user is requested, the usage history storage unit 104 extracts the usage history of the attribute similar user from the usage history of the plurality of users based on the notified user ID. When there is a usage history of the attribute similar user (YES in step S410), the usage history storage unit 104 extracts the usage history of the attribute similar user and passes the usage history of the attribute similar user to the FK selection unit 106 (step S411). ).

  Upon receiving the usage history of the attribute-similar user, the FK selection unit 106 selects an FK application based on the received usage history (step S412). The method for selecting the FK application is as described above. Thereafter, the FK selection unit 106 notifies the control unit 103 of the selected FK application.

  In general, it is considered that the application usage tendency of the target user and the attribute similar user is similar. Therefore, as described above, by selecting the FK application of the target user based on the usage history of the attribute-similar user, the FK selection unit 106 can select an application that is highly likely to be used by the target user as the FK application.

  On the other hand, when there is no usage history of the attribute similar user (NO in step S410), the usage history storage unit 104 notifies the FK selection unit 106 to that effect. As a case where there is no usage history of the attribute-similar user, a case where the attribute-similar user has never logged in to the MFP 1 or a case where the usage history stored in the usage history storage unit 104 is reset can be considered.

  When notified that there is no usage history of the attribute-similar user, the FK selection unit 106 selects a default application as the FK application (step S413). The default application is an application preset as a default value of the FK application. The default application is set by the administrator or user of the MFP 1. Thereafter, the FK selection unit 106 notifies the control unit 103 of the selected FK application.

  As described above, according to the present embodiment, when there is no usage history of the target user, the priority application or the FK application is selected based on the usage history of the same attribute user or the similar attribute user. Thereby, even if there is no usage history of the target user, an application that is highly likely to be used by the target user can be selected as a priority application or an FK application.

<Third Embodiment>
An MFP 1 according to the third embodiment will be described with reference to FIGS. In the first embodiment, the case has been described in which the application selected as the priority application by the priority application selection unit 105 is automatically set as the priority application. On the other hand, in the present embodiment, a case will be described in which it is confirmed whether the application selected by the priority application selection unit 105 as the priority application is set as the priority application. Note that the hardware configuration and functional configuration of the MFP 1 according to the present embodiment are the same as those in the first embodiment.

  FIG. 11 is a sequence diagram illustrating an example of processing of the operation unit 20 immediately after the target user logs in. The sequence diagram of FIG. 11 is equivalent to adding steps S216 and S217 between steps S208 and S209 of FIG. 6 and adding steps S218 and S219 between steps S214 and S215 of FIG. Hereinafter, the process of steps S216 to S219 will be described.

  First, steps S216 and S217 will be described. In the present embodiment, when the priority application is notified from the priority application selection unit 105 (step S208), the control unit 103 confirms with the target user whether the notified application is set as the priority application (step S216). Specifically, the control unit 103 displays on the screen of the operation panel 27 a priority application dialog box for confirming whether the notified application is set as a priority application.

  FIG. 12 is a diagram illustrating an example of the priority application dialog box. In the example of FIG. 12, it is assumed that the priority application selection unit 105 has selected “copy gently” as the priority application. In the priority application dialog box in FIG. 12, "Do you want to set" Copy gently "" as the priority application? And a YES button and a NO button are displayed. The YES button is a button for accepting the priority application setting, and the NO button is a button for rejecting the priority application setting.

  When the control unit 103 displays the priority application dialog box, the target user performs an answer operation (touching the YES button or the NO button) and answers whether or not to set the application selected by the priority application selection unit 105 as the priority application. To do. When accepting an answer operation, the operation accepting unit 101 notifies the control unit 103 of an answer (YES or NO) from the user (step S217). Thereafter, the control unit 103 sets a priority application according to the user's answer notified from the operation reception unit 101, and activates the set priority application (step S209).

  When the answer from the user is acceptance (YES) (when the user touches the YES button), the control unit 103 sets the application selected by the priority application selection unit 105 as the priority application and starts the priority application. To do. In the example of FIG. 12, “copy gently” is set as the priority application and activated.

  On the other hand, if the answer from the user is refusal (NO) (when the user touches the NO button), the control unit 103 does not set the application selected by the priority application selection unit 105 as the priority application. Maintain current settings for and launch the preferred app that is currently set.

  Next, steps S218 and S219 will be described. In the present embodiment, when notified of the FK application from the FK selection unit 106 (step S214), the control unit 103 confirms with the target user whether the notified application is set as the FK application (step S218). Specifically, the control unit 103 displays an FK application dialog box for confirming whether the notified application is set as the FK application on the screen of the operation panel 27.

  FIG. 13 is a diagram illustrating an example of the FK application dialog box. In the example of FIG. 13, it is assumed that the FK selection unit 106 has selected “easy copy” and “easy scan” as the FK application. In the FK application dialog box shown in Fig. 13, do you set "" Gently copy "and" Easy scan "to the function key application? And a YES button and a NO button are displayed. The YES button is a button for accepting the setting of the FK application, and the NO button is a button for rejecting the setting of the FK application.

  When the control unit 103 displays the FK application dialog box, the target user performs an answer operation (touching the YES button or NO button) and answers whether or not the application selected by the FK selection unit 106 is set as the FK application. . When accepting an answer operation, the operation accepting unit 101 notifies the control unit 103 of an answer (YES or NO) from the user (step S219). Thereafter, the control unit 103 sets the FK application in accordance with the user's answer notified from the operation reception unit 101, and displays the set FK application activation button as FK (step S215).

  When the answer from the user is acceptance (YES) (when the user touches the YES button), the control unit 103 sets the application selected by the FK selection unit 106 as the FK application, and activates the FK application. Is displayed as FK. In the example of FIG. 13, “copy gently” and “easy scan” are set in the FK application, and these activation buttons are displayed as FK.

  On the other hand, if the answer from the user is refusal (NO) (when the user touches the NO button), the control unit 103 does not set the application selected by the FK selection unit 106 as the FK application, The current setting is maintained, and the activation button of the FK application currently being set is displayed as FK.

  As described above, according to the present embodiment, the operation unit 20 can confirm with the target user whether the application selected by the priority application selection unit 105 as the priority application is set as the priority application. Therefore, the target user can set the app as the priority app only when the app selected by the priority app selection unit 105 as the priority app is appropriate.

  Similarly, according to the present embodiment, the operation unit 20 can confirm with the target user whether the application selected by the FK selection unit 106 as the FK application is set as the FK application. Therefore, the target user can set the application as the FK application only when the application selected by the FK selection unit 106 as the FK application is appropriate.

  In the present embodiment, the case where the control unit 103 confirms the settings of both the priority application and the FK application with the target user has been described, but only one of the settings may be confirmed with the target user.

  For example, the control unit 103 may confirm only the priority application setting with the target user and may not confirm the FK application setting with the target user. This is because the priority application is activated immediately after login, and the operability degradation when set inappropriately is larger than that of the FK application. By confirming only the priority application settings with the target user, it is possible to suppress the above-described deterioration in operability while suppressing the troublesome confirmation work.

  In the example of FIG. 11, the control unit 103 checks the setting of the priority application every time the target user logs in, but an application different from the currently set priority application is selected by the priority application selection unit 105. It may be confirmed whether the app is set as a priority app only when

  Similarly, in the example of FIG. 11, the control unit 103 checks the setting of the FK application every time the target user logs in, but an application different from the currently set FK application is selected by the FK selection unit 106. It may be confirmed whether the application is set as the FK application only when

  Further, the FK application dialog box is not limited to the example of FIG. FIG. 14 is a diagram illustrating another example of the FK application dialog box. In the FK application dialog box of FIG. 14, a message “Please select an application to be set as a function key.”, A plurality of application names that are candidates for the FK application, check boxes corresponding to each application, and OK. Button and are displayed.

  The target user can set a desired application as an FK application by selecting an application using a check box and touching an OK button. In the example of FIG. 14, “copy gently”, “easy scan”, and “printer” are selected. When the OK button is touched in this state, “copy gently”, “easy scan”, and “printer” are set in the FK application.

  It is preferable that the control unit 103 displays application names in descending order of possibility of being used by the target user. Thereby, selection of the suitable application (application with high possibility of being used by a target user) by a target user can be assisted.

  Note that the information processing apparatus according to each of the above embodiments may be realized as an information processing system including a plurality of information processing apparatuses. FIG. 15 is a diagram illustrating an example of an information processing system. The information processing system in FIG. 15 includes an operation unit 20 (MFP 1) and a server 2. The operation unit 20 includes an operation reception unit 101 and a control unit 103.

  The server 2 is a computer connected to the operation unit 20 via the communication I / F 25, and includes an authentication unit 102, a usage history storage unit 104, a priority application selection unit 105, and a function key selection unit 106. .

  FIG. 16 is a diagram illustrating an example of a hardware configuration of the server 2 according to the present embodiment. 1 includes a CPU 201, a ROM 202, a RAM 203, an HDD 204, an input device 205, a display device 206, a communication I / F 207, and a system bus 208.

  The CPU 201 executes the program to control each configuration of the server 2 and realize the function of the server 2.

  The ROM 202 stores programs (such as BIOS) executed by the CPU 201 and various data.

  The RAM 203 provides a work area for the CPU 201.

  The HDD 204 stores a program (such as an OS) executed by the CPU 201 and various data.

  The input device 205 inputs information corresponding to a user operation to the server 2. The input device 205 includes a touch panel, a keyboard, a mouse, hardware buttons, and the like.

  The display device 206 displays a screen corresponding to a user operation. The display device 206 can be a liquid crystal display, an organic EL (Electro Luminescence) display, or the like. The input device 205 and the display device 206 may be integrally configured as an operation panel.

  A communication I / F 207 connects the server 2 to a network such as the Internet or a LAN, and controls communication with an external device on the network. The server 2 communicates with an external device including the operation unit 20 via the communication I / F 207.

  A system bus 208 interconnects the CPU 201, ROM 202, RAM 203, HDD 204, input device 205, display device 206, and communication I / F 207.

  With the configuration as described above, the same processing as that of the information processing apparatus according to the first embodiment and the third embodiment can be realized by the information processing system of FIG. In addition, by providing the user information storage unit 107 in the operation unit 20 or the server 2, the same processing as that of the information processing apparatus according to the second embodiment can be realized by the information processing system. Further, the load on the operation unit 20 can be reduced, and a plurality of MFPs 1 can be managed by one server 2. In addition, distribution of each function structure is not restricted to the example of FIG. Further, the information processing system may be configured by three or more devices.

  Each function of the embodiment described above can be realized by one or a plurality of processing circuits. Here, the “processing circuit” in this specification means a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, or designed to execute each function described above. It also includes devices such as application specific integrated circuits (ASICs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), and conventional circuit modules.

  It should be noted that the present invention is not limited to the configuration shown here, such as a combination with other elements in the configuration described in the above embodiment. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

1: MFP
2: Server 10: Main body 20: Operation unit 101: Operation receiving unit 102: Authentication unit 103: Control unit 104: Usage history storage unit 105: Priority application selection unit 106: Function key selection unit 107: User information storage unit

JP 2014-59638 A

Claims (12)

An information processing system that is equipped with multiple applications and allows multiple users to log in.
A first selection unit that selects a first application to be activated immediately after the target user logs in based on a usage history of the plurality of applications of the target user;
A control unit that activates the first application of the target user immediately after the target user logs in,
An information processing system comprising: The information processing system according to claim 1, wherein the first selection unit selects the first application based on a usage frequency of the plurality of applications immediately after the target user logs in. When there is no usage history of the target user, the first selection unit selects the first application of the target user based on the usage history of another user having the same attribute information as the target user. The information processing system according to claim 1 or 2. The information processing system according to any one of claims 1 to 3, wherein the control unit confirms with the target user whether an application selected as the first application is set as the first application. When an application different from the first application being set is selected as the first application by the first selection unit, the control unit confirms with the target user whether to set the application as the first application The information processing system according to any one of claims 1 to 4. A second selection unit that selects a second application that always displays a start button during login of the target user based on the usage history of the plurality of applications of the target user;
The information processing system according to any one of claims 1 to 5, wherein the control unit always displays the activation button of the second application of the target user during login of the target user. The information processing system according to claim 6, wherein the second selection unit selects the second application based on a usage frequency of the plurality of applications during login of the target user. The information processing system according to claim 6 or 7, wherein the second selection unit selects the application different from the first application as the second application. When there is no usage history of the target user, the second selection unit selects the second application of the target user based on the usage history of another user having the same attribute information as the target user. The information processing system according to any one of claims 6 to 8. The information processing system according to any one of claims 6 to 9, wherein the control unit sets the application selected as the second application as the second application or confirms with the target user. An information processing apparatus equipped with a plurality of applications and capable of logging in by a plurality of users,
A first selection unit that selects a first application to be activated immediately after the target user logs in based on a usage history of the plurality of applications of the target user;
A control unit that activates the first application of the target user immediately after the target user logs in,
An information processing apparatus comprising: An information processing method that is executed by an information processing system in which a plurality of applications are installed and a plurality of users can log in,
A first selection step of selecting a first application to be activated immediately after the target user logs in based on the usage history of the plurality of applications of the target user;
A control step of starting the first application of the target user immediately after the target user logs in;
An information processing method comprising:

Images