JP7816464B2 - Function Execution Device - Google Patents

Description

The present disclosure relates to a technology for executing a registered function in response to a user operation.

Patent Document 1 below discloses an image processing device that is configured to enable a specific process (e.g., a scan process) associated with a shortcut button to be executed simply by having a card reader read a card, without having to operate the shortcut button.

When the image processing device disclosed in Patent Document 1 is shared by a plurality of users, it is convenient if it is configured as follows, for example.
That is, each of the multiple shortcut buttons is arranged on one of multiple tab screens in tab format. One of the multiple tab screens is selectively displayed on the display unit. Each of the multiple tabs is set to a shared attribute or a personal attribute. When a specific user is not logged in, the personal attribute tab is not displayed and only the shared attribute tab is displayed. The personal attribute tab is displayed only when the specific user corresponding to that tab is logged in.

By configuring an image processing device in this way, it is possible, for example, to allow only specific users to operate a shortcut button associated with a specific process. Specifically, this is possible by placing a shortcut button that you want only specific users to be able to operate (hereinafter referred to as a "user-only button") on a tab with personal attributes corresponding to that specific user, or by setting the tab on which that user-only button is placed to be a tab with personal attributes corresponding to that specific user.

JP 2016-010059 A

However, if the specific process associated with the user-only button can also be performed by reading the aforementioned card with a card reader, the following problem arises:

For example, suppose that in order to make a shortcut button associated with a specific process that can be executed by a card into a user-only button, the attributes of the tab on which the shortcut button is located are changed to personal attributes corresponding to that specific user. In this case, the user-only button will no longer be displayed unless that specific user logs in, preventing unspecified users other than that specific user from operating the user-only button.

However, even if the user-only button is not displayed and cannot be operated, if the card is available, any user can still use the card to perform the specific process associated with the user-only button.

In consideration of the above-mentioned problems , the present disclosure provides a function execution device that is configured to be able to execute a specific function not only by direct operation by a user but also via wireless communication with the outside, and that is provided with a configuration that enables the execution of the specific function to be appropriately restricted.

A first exemplary function performing device according to an embodiment of the present invention includes a display unit, an input unit, a communication unit, and a control unit, and the communication unit is capable of performing wireless communication with a wireless communication device having a specific device ID in response to the wireless communication device being placed within a communication coverage area.

The control unit executes a general mode display process. The general mode display process is a process for displaying a general mode standby screen on the display unit. The general mode standby screen is a screen that includes a shared tab, which is a tab set to the shared attribute, among multiple tabs each set to the shared attribute or the personal attribute, but does not include a personal tab, which is a tab set to the personal attribute.

Each of the multiple tabs is configured to allow registration of a functional object, which is an image associated with a function to be executed. The functional object is configured to allow registration of a specific object ID. The general mode standby screen shows one shared tab selected, and includes the functional objects registered in that selected shared tab.

The control unit further executes a first function execution process, a device ID acquisition process, and a second function execution process.
The first function execution process is a process of executing a function associated with a functional object displayed on the display unit in response to the selection of the functional object via the input unit.

The device ID acquisition process is a process of acquiring a device ID from a wireless communication device through wireless communication by a communication unit.
The second function execution process is a process executed in response to the device ID being acquired by the device ID acquisition process. In the second function execution process, the control unit executes a function associated with an ID-corresponding object if the ID-corresponding object is registered in the shared tab, and does not execute a function associated with the ID-corresponding object if the ID-corresponding object is registered in the personal tab. The ID-corresponding object is the function object in which an object ID that has a specific correspondence with the acquired device ID is registered.

In a function executing device configured in this manner, even if a device ID corresponding to an ID-corresponding object is acquired, if the ID-corresponding object is registered in the personal tab, the function corresponding to the ID-corresponding object will not be executed. Therefore, by registering an ID-corresponding object in the personal tab, it is possible to appropriately restrict the execution of the function corresponding to the ID-corresponding object.
A second exemplary function execution device according to an embodiment of the present invention includes a short-range wireless communication unit, a control unit, a memory, and a function execution unit.
The short-range wireless communication unit can detect wireless communication devices located within a short distance that can be communicated with by the short-range wireless communication unit. The control unit can store a plurality of pieces of shortcut information in a memory. Each piece of shortcut information has pre-registered therein a function to be executed by the function execution unit and a setting value used to execute the function.
The control unit, in response to a requirement that a wireless communication device is detected by the short-range wireless communication unit and that the detected wireless communication device corresponds to any one of the plurality of pieces of shortcut information stored in the memory,
If login is not required to execute the function registered in the corresponding shortcut information, the function execution unit executes the function registered in the corresponding shortcut information in accordance with the setting value registered in the corresponding shortcut information;
When login is required to execute the function registered in the corresponding shortcut information, the function registered in the corresponding shortcut information according to the setting value registered in the corresponding shortcut information is not executed by the function execution unit.

FIG. 1 is an explanatory diagram illustrating a schematic configuration of an information processing system according to an embodiment. FIG. 10 is an explanatory diagram showing an example of a standby screen when a user is not logged in and all tabs are set to the shared attribute. FIG. 10 is an explanatory diagram illustrating an icon data table. 1A is an explanatory diagram showing a tab setting table, and FIG. 1B is an explanatory diagram showing a tab attribute setting screen. FIG. 10 is an explanatory diagram illustrating a user management data table. (a) is an explanatory diagram showing an example of screen transitions when attempting to launch a card launch shortcut registered in the personal tab from an NFC card in general mode, and (b) is an explanatory diagram showing an example of screen transitions when attempting to launch a card launch shortcut registered in the personal tab (but the home tab of the logged-in user) from an NFC card in personal mode. 10 is an explanatory diagram showing an example of screen transitions when an attempt is made to activate a card activation shortcut that is registered in the personal tab and does not perform external access from an NFC card in general mode. FIG. 10A and 10B are explanatory diagrams showing an example of a screen transition when the attribute of a tab in which a card activation shortcut is registered is changed from shared to personal; 10 is a flowchart showing a main process. 10 is a flowchart showing the no-access-right handling process in S210 in the main process of FIG. 9; 10 is a flowchart showing a tab setting change confirmation process in S240 in the main process of FIG. 9;

Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings.
1. Embodiment
(1) Overview of Information Processing System The information processing system 1 of this embodiment shown in FIG. 1 includes an image processing device 10 and an information processing device 20. The image processing device 10 and the information processing device 20 are capable of mutual data communication via a network 3. The network 3 may be any network. For example, the network 3 may be a wired network or a wireless network. Furthermore, whether wired or wireless, the specific communication method may be any communication method.

(2) Configuration of Image Processing Device The image processing device 10 has multiple functions, such as a scan function, a print function, a copy function, and a fax function. The scan function is a function of reading an image of an original document and generating image data of the read image. The print function is a function of printing an image on a sheet of recording paper. The copy function is a function of printing an image read by the scan function by the print function. The fax function is a function of sending and receiving facsimile data.

As shown in FIG. 1, the image processing device 10 includes a control unit 11, a memory unit 12, a display unit 13, an input unit 14, a reading unit 15, a printing unit 16, a short-range wireless communication unit 17, a first communication unit 18, and a second communication unit 19, which are interconnected via a bus 5.

The control unit 11 includes, for example, a CPU. The storage unit 12 includes, for example, semiconductor memory such as ROM, RAM, NVRAM, or flash memory. In other words, the image processing device 10 of this embodiment includes a microcomputer including a CPU and semiconductor memory.

The control unit 11 realizes various functions by executing programs stored on a non-transient physical recording medium. In this embodiment, the storage unit 12 corresponds to the non-transient physical recording medium on which the programs are stored. Note that the various functions realized by the control unit 11 are not limited to being realized by executing programs (i.e., by software processing), and some or all of them may be realized using one or more pieces of hardware.

The storage unit 12 stores data for the various screens shown in Figures 2, 6 to 8. The storage unit 12 also stores data for the icon data table shown in Figure 3, data for the tab settings table shown in Figure 4(a), data for the user management data table shown in Figure 5, and the main processing programs shown in Figures 9 to 11.

The display unit 13 has a display device for displaying various types of information. The display unit 13 of this embodiment has a display 13a as a display device.
The input unit 14 has an input device for receiving various input operations. The input unit 14 of this embodiment has a touch panel 14 a as an input device. The touch panel 14 a is superimposed on an image display area of the display device of the display unit 13, where an image is displayed.

The touch panel 14a, which is superimposed on the image display area of the display unit 13, is capable of detecting pointing operations made by contact with or proximity to an indicator on the image display area. In other words, when an indicator is used to make a pointing operation on the image display area, the touch panel 14a is configured to be able to output position information indicating the pointing position where the pointing operation is being made. The touch panel 14a of this embodiment is configured to output position information continuously or periodically while an pointing operation is being made by the indicator.

Note that the touch panel 14a may be configured to detect only contact as a pointing operation, or only proximity, or both contact and proximity.

The control unit 11 acquires position information output from the touch panel 14a, and based on the acquired position information, can detect whether or not a pointing operation has been performed by the indicator, the pointing position if a pointing operation has been performed, and at least one type of specific operation by the indicator if a pointing operation has been performed.

Specific operations that can be detected by the control unit 11 include, for example, tapping, flicking, and dragging. A tapping operation is an operation in which a pointing operation is performed with an indicator and then the indicator is released from the same position. There are various possible specific forms of indicators that can perform pointing operations, and for example, the indicator may be a fingertip or a specific pointing device such as a stylus pen.

The reading unit 15 is equipped with an image sensor, reads an image recorded on a document, and generates image data for the read image. The image sensor may be, for example, a CCD image sensor or a CMOS image sensor.

The printing unit 16 has a printing mechanism using inkjet technology or electrophotography technology, and is capable of printing images on sheet-like recording paper.
The short-range wireless communication unit 17 performs wireless communication using a specific wireless communication method with other wireless communication devices located near the image processing device 10. The specific wireless communication method may be any wireless communication method, and in this embodiment, it is, for example, a wireless communication method based on the NFC communication standard. NFC is an abbreviation for Near Field Communication.

The short-range wireless communication unit 17 is controlled by the control unit 11. The short-range wireless communication unit 17 can communicate wirelessly with other wireless communication devices that are present within the communication area of the short-range wireless communication unit 17. The communication area may be, for example, an area within a predetermined distance (e.g., several dozen centimeters) from a predetermined area of the surface of the housing of the image processing device 10 near the position where the short-range wireless communication unit 17 is mounted.

Other wireless communication devices with which the short-range wireless communication unit 17 can communicate wirelessly include the NFC card 7 shown in FIG. 1. The NFC card 7 is a rectangular, thin card. The NFC card 7 includes an antenna 7a, a communication circuit 7b, and a storage unit 7c. The communication circuit 7b
performs wireless communication based on the NFC communication standard via the antenna 7a. The memory unit 7c stores a card ID unique to the NFC card 7. The communication circuit 7b is configured to be able to wirelessly transmit the card ID stored in the memory unit 7c to an external device.

When the NFC card 7 is placed within the aforementioned communication area of the image processing device 10, i.e., when the NFC card 7 and the short-range wireless communication unit 17 of the image processing device 10 are positioned so that they can communicate wirelessly, wireless communication is carried out between the short-range wireless communication unit 17 and the NFC card 7 (more specifically, the communication circuit 7b) in accordance with a specific procedure. Through this wireless communication, the card ID of the NFC card 7 is sent to the image processing device 10, and the control unit 11 of the image processing device 10 acquires the card ID via the short-range wireless communication unit 17. Note that in the following description, "holding" the NFC card 7 over the image processing device 10 means placing the NFC card 7 within the aforementioned communication area of the image processing device 10.

The first communication unit 18 is a communication interface for connecting the image processing device 10 to the network 3. The image processing device 10 may be capable of wired or wireless data communication with various information processing devices such as personal computers, smartphones, and tablet devices via the first communication unit 18. The image processing device 10 may also be connected to the Internet via the first communication unit 18 and be capable of data communication with various other servers and information processing devices via the Internet.

The second communication unit 19 is an interface unit for communicating with external devices via a communication line 150. In this embodiment, the communication line 150 connected to the second communication unit 19 is, for example, a public telephone network. In the fax function, facsimile data is basically sent and received via the second communication unit 19.

Although not shown in the figure, the image processing device 10 is equipped with a media interface. Various types of storage media, such as USB flash memory, can be removably attached to the media interface. The media interface controls the writing and reading of data to the attached storage media.

(3) Configuration of Information Processing Device The information processing device 20 is any of various information processing terminals, such as a personal computer, a tablet terminal, a smartphone, etc. As shown in FIG. 1 , the information processing device 20 includes a control unit 21, a storage unit 22, an input unit 23, a display unit 24, and a communication unit 25.

The control unit 21 includes, for example, a CPU. The storage unit 22 includes, for example, semiconductor memory such as ROM, RAM, NVRAM, and flash memory. In other words, the information processing device 20 of this embodiment is equipped with a microcomputer including a CPU and semiconductor memory. Various software and data are stored in the storage unit 22.

The display unit 24 has a display device capable of displaying images, such as a liquid crystal display or an organic EL display.
The input unit 23 has input devices for receiving various input operations. The input devices of the input unit 23 include, for example, a keyboard, a mouse, a touch panel, etc. The touch panel is superimposed on the image display area of the display device of the display unit 24.

The communication unit 25 is a communication interface for communicating with external devices via the network 3. The information processing device 20 can communicate data with the image processing device 10 via the communication unit 25.

(4) Description of the standby screen Next, among the various screens displayed on the display unit 13 of the image processing device 10, the standby screen 40 in particular will be described with reference to Fig. 2. When the control unit 11 of the image processing device 10 is started up, it performs a predetermined initial process and then displays the standby screen 40 shown in Fig. 2 on the display unit 13.

The standby screen 40 is a tabbed screen with one or more tabs. The number and type of tabs displayed on the standby screen 40 may vary depending on the user mode (described below) or the logged-in user. Figure 2 shows an example of the standby screen 40 when the user mode is set to the general mode. Figure 2 also shows an example in which, of the multiple tabs, the first tab 31, the second tab 32, the third tab 33, and the fourth tab 34 are displayed.

Each of the multiple tabs is associated with a separate tab screen. The standby screen 40 displays a tab screen corresponding to one of the displayed tabs that is selected. The selected tab is displayed in a different manner from the other tabs.

The standby screen 40 shown on the left of Figure 2 shows an example in which the first tab 31, named "Basic 1," is selected and displayed in a different manner from the other tabs (e.g., a different color, a different size, etc.). The standby screen 40 shown on the right of Figure 2 shows an example in which the third tab 33, named "Custom 1," is selected and displayed in a different manner from the other tabs.

In this embodiment, the tabs on the standby screen 40 are arranged to the right. That is, the tabs are arranged sequentially to the right. The arrangement order of the tabs in this arrangement direction is basically in accordance with the specified order described below, i.e., ascending order of the specified order.

In this embodiment, a maximum of, for example, four tabs can be displayed simultaneously on the standby screen 40. The total number of tabs Nt can be any number, but in this embodiment, the total number of tabs Nt is greater than four, which is the maximum number of tabs that can be displayed simultaneously on the standby screen 40.

On the standby screen 40, a left button 38 and a right button 39 are displayed near both ends of the area where the tabs are displayed. If there are five or more tabs and four of them are displayed, selecting the left button 38 or the right button 39 scrolls the tabs to the left or right, thereby displaying tabs that are not displayed. Note that the selection operation may be any operation, and in this embodiment, it is, for example, a tap operation.

When you want to switch from the tab screen of the currently selected tab to the tab screen of another tab, for example, simply select the tab you want to switch to. When you select a tab other than the currently selected tab, the selected tab becomes selected, and the tab screen corresponding to the newly selected tab is displayed on the standby screen 40. For example, when the first tab 31 is selected as shown on the left of FIG. 2, selecting the third tab 33 causes the third tab 33 to become selected as shown on the right of FIG. 2, and the third tab screen 60 corresponding to the third tab 33 is displayed on the standby screen 40. Conversely, when the first tab 31 is selected on the standby screen 40 shown on the right of FIG. 2, the first tab 31 becomes selected as shown on the left of FIG. 2, and the first tab screen 50 corresponding to the first tab 31 is displayed on the standby screen 40.

The memory unit 12 stores various information necessary to display the standby screen 40, as well as information regarding the processing to be performed when various input operations are performed on the standby screen 40 via the input unit 14.

Multiple icons are registered in each tab, and each tab screen is an image on which the multiple icons registered in the corresponding tab are arranged. In this embodiment, for example, eight icons are registered in one tab, and the corresponding eight icons are arranged on each tab screen.

That is, as shown on the left side of Figure 2, the first tab screen 50 corresponding to the first tab 31 displays the first icon 51 to the eighth icon 58 registered in the first tab 31. As shown on the right side of Figure 2, the third tab screen 60 corresponding to the third tab 33 displays the seventeenth icon 61 to the twenty-fourth icon 68 registered in the third tab 33. Each icon includes its name. The specific type of each icon can be changed.

Each icon is associated with a specific function. When the user selects one of the icons, the specific function associated with that icon is executed.

In the first tab screen 50 shown on the left of Figure 2, for example, the first icon 51 is associated with a specific fax function, the second icon 52 is associated with a specific copy function, and the third icon 53 is associated with a specific scan function. The fourth icon 54 and the eighth icon 58 are unregistered icons with no specific function associated with them. The user can associate a specific function with these unregistered icons by registering the specific function. Explanation of the fifth icon 55 to the seventh icon 57 will be omitted.

In the third tab screen 60 shown on the right of Figure 2, for example, the 17th icon 61 is associated with a specific copy function, the 18th icon 62 and the 19th icon 63 are associated with a specific fax function, and the 20th icon 64 and the 21st icon 65 are associated with a specific scan function. The 22nd icon 66 to the 24th icon 68 are unregistered icons.

The specific functions associated with the 17th icon 61 to the 21st icon 65 on the third tab screen 60 are all shortcut functions. Shortcut functions are functions that are registered at the user's discretion. Shortcut functions are set to execute specific functions according to preset settings. The user can register a shortcut function to an unregistered icon by performing a specified shortcut registration operation on that icon. At that time, the user can also set the name of the shortcut function as desired. The user can also change the content of a registered shortcut function, or cancel the registration and make the icon an unregistered icon. Note that an icon associated with a shortcut function will also be referred to as a shortcut icon below.

In this embodiment, shortcut functions are further classified into two types: normal shortcut functions and one-touch shortcut functions. Normal shortcut functions are configured so that when the corresponding shortcut icon is selected, the registered shortcut function is not immediately started, but rather at least one additional input operation by the user is required.

In this embodiment, when a shortcut icon corresponding to a normal shortcut function is selected, a predetermined confirmation screen is displayed. The user can confirm or change the settings of the shortcut function via the confirmation screen. After the confirmation screen is displayed, if the user performs a specific execution start operation, the registered shortcut function will be started.

On the other hand, the one-touch shortcut function is configured so that when the corresponding shortcut icon is selected, the registered shortcut function is started and completed without requiring any further input by the user.

As shown on the right side of Figure 2, shortcut icons on the standby screen 40 are marked with a normal mark 46 or a one-touch mark 47. The 17th icon 61, 19th icon 63, and 20th icon 64, which have the normal mark 46 marked, are shortcut icons associated with the normal shortcut function. The 18th icon 62 and 21st icon 65, which have the one-touch mark 47 marked, are shortcut icons associated with the one-touch shortcut function.

When registering a shortcut function to an icon on the tab screen, users can choose whether to register it as a regular shortcut function or a one-touch shortcut function.

Furthermore, by performing a specific card registration operation, the user can register a card ID to any shortcut icon, i.e., register the card ID to the shortcut function corresponding to that shortcut icon. A shortcut function to which a card ID is registered is hereinafter referred to as a card activation shortcut.

The card registration operation may be any operation. For example, the card ID may be registered by the user inputting it via the input unit 14. Alternatively, for example, the card ID may be automatically read and registered via wireless communication by holding the NFC card 7 over the image processing device 10.

When a card ID is registered in a shortcut function, information indicating that a card ID has been registered is displayed on the shortcut icon corresponding to that card activation shortcut. The information indicating that a card ID has been registered can be any information, and in this embodiment, it is the text "(NFC card)," for example. In the standby screen 40 shown on the right of Figure 2, the shortcut functions corresponding to the 17th icon 61 and the 19th icon 63 are card activation shortcuts.

Information about each icon is registered in the icon data table shown in Figure 3. The icon data table stores multiple pieces of information for each icon, including the registered card ID, the function corresponding to that icon (i.e., the main function that is executed when that icon is selected), a card activation permission flag, and the tab to which it belongs.

In the example of Figure 3, the card ID "87654321" is registered in the 17th icon 61 of the third tab 33, and the card ID "12345678" is registered in the 19th icon 63 of the third tab 33. The card activation permission flag is referenced in S200, which will be described later.

The tabs displayed on the standby screen 40 are managed in the tab settings table shown in Figure 4(a). The tab settings table lists Nt tabs (e.g., eight in this embodiment) in a specified order. In this embodiment, the specified order is, for example, the order of the first to eighth tabs, as shown in Figure 4(a).

An attribute is set for each tab. In this embodiment, the attribute is set to either shared or personal. The attribute of a tab can be changed arbitrarily for each tab. FIG. 4A shows an example in which the attribute of the first tab 31 is set to shared, and the attributes of the other tabs are set to personal.

A tab name is set for each tab. The tab name is displayed for each tab when the tab is displayed on the standby screen 40. The tab name can be changed arbitrarily for each tab.
The tab setting table, the icon data table (see FIG. 3) described above, and the user management data table (see FIG. 5) described below may be stored in advance in, for example, the storage unit 12 of the image processing device 10. In this case, the image processing device 10 may allow the user to customize each table stored in the storage unit 12 as desired.

Furthermore, each table may be acquired at a specific timing from another device, such as the information processing device 20, and stored in the storage unit 12. Specifically, for example, the information processing device 20 may be configured to allow each table to be customized as desired. Then, upon startup, the control unit 11 of the image processing device 10 may acquire each table from the information processing device 20 via the network 3 and store it in the storage unit 12, and perform various processes such as displaying the standby screen 40 based on each stored table. After acquiring and storing each table after startup, the control unit 11 may also acquire each table from the information processing device 20 at a specific timing and update each table stored in the storage unit 12.

An example of a method for changing tab attributes will be described with reference to FIG. 4(b). When a specific operation for changing tab attributes is performed on the information processing device 20, the tab attribute setting screen 8 shown in FIG. 4(b) is displayed on the display unit 24 of the information processing device 20. The tab attribute setting screen 8 lists each tab, and displays a shared or personal radio button for each tab. The user can change the tab attributes as desired by selecting one of the radio buttons. Note that the tab attribute setting screen 8 in FIG. 4(b) or a similar screen may be displayed on the image processing device 10, allowing the tab attributes to be changed on the image processing device 10.

The standby screen 40 shown in Figure 2 shows an example in which the first tab 31 to the fourth tab 34 all have shared attributes. On the other hand, the standby screen 40 shown in Figures 6 and 7 shows an example of a standby screen based on the tab setting table in Figure 4(a), i.e., an example in which the first tab 31 has shared attributes and all other tabs have personal attributes. The standby screen 40 shown on the left of Figure 8 shows an example in which the first tab 31 and the third tab 33 have shared attributes and all other tabs have personal attributes. The standby screen 40 shown in the bottom right of Figure 8 shows an example in which the first tab 31 has shared attributes and all other tabs have personal attributes.

In addition, in the image processing device 10, the user mode is set to either general mode or personal mode. Personal mode is set when one of the pre-registered users (hereinafter referred to as a "registered user") logs in by performing a specified user authentication operation. In other words, when a registered user logs in, the personal mode corresponding to that registered user is set. General mode is a user mode in which no registered users are logged in. In other words, general mode is a user mode that can be set by any user without requiring authentication processing such as password entry.

Registered users can be registered directly on the image processing device 10 or indirectly via an external device such as the information processing device 20. For example, the information processing device 20 manages the user management data table shown in FIG. 5. Registered users are registered in the user management data table. In addition, a personal home tab can be registered for each registered user in the user management data table. When the information processing device 20 performs the registration process for a registered user, that registered user is added to the user management data table. Furthermore, a personal home tab can be registered for that registered user at will.

The user management data table shown in Figure 5 illustrates an example in which eight users, User 01 to User 08, are registered as registered users. Also shown is an example in which the first tab is registered as User 01's personal home tab, the second tab is registered as User 02's personal home tab, the third tab is registered as User 03's personal home tab, and the fourth tab is registered as User 04's personal home tab, while none of the four users, User 05 to User 08, have a personal home tab registered. Personal home tabs can be registered as either shared or personal tabs.

Registered users log in by executing a predetermined authentication process, which includes, for example, inputting user authentication information (e.g., a password) specific to the registered user via the input unit 14.

The tabs displayed on the standby screen 40 differ depending on whether the user mode is general mode or personal mode. Furthermore, even in personal mode, the tabs displayed on the standby screen 40 differ depending on which registered user is logged in.

As shown in FIG. 2, the standby screen 40 displays a user switching interface 45. The user switching interface 45 is an image that the user selects (e.g., taps) to switch user modes.

The user switching interface 45 displays information indicating the current user mode. In this embodiment, when the user mode is set to the general mode, the user switching interface 45 displays the text "General" indicating that the mode is general, as shown in Figures 2, 6(a), 7, and 8. When the user mode is set to the personal mode, the user switching interface 45 displays text indicating the logged-in user, as shown in Figure 6(b).

When the user switching interface 45 is selected, a user mode selection screen (not shown) for selecting a user mode is displayed on the display unit 13. The user mode selection screen displays options for general mode and each registered user. When general mode is selected, the user mode is set to general mode.

In general mode, the standby screen 40 displays tabs with the shared attribute, and one of these tabs is selected. In general mode, tabs with the personal attribute are not displayed.

For example, if the attribute of all tabs is shared, then all tabs (however, a maximum of four tabs can be displayed simultaneously) will be displayed on the standby screen 40 in normal mode, as shown in FIG. 2. Also, for example, if only the first tab 31 has the shared attribute, then the first tab 31 will be displayed on the standby screen 40 in normal mode, as shown in FIGS. 6(a) and 7, etc.

On the other hand, when a registered user is selected on the user mode selection screen, an authentication screen (not shown) is displayed to perform authentication processing. When valid user authentication information corresponding to the selected registered user is entered via this authentication screen, authentication is successful, i.e., the user is logged in, and the user mode is set to the personal mode of the selected registered user.

In personal mode, the personal home tab of the corresponding registered user is obtained from the user management data table (see FIG. 5 ), and the personal home tab is displayed on the standby screen 40. For example, when user 03 logs in, the standby screen 40 displays the third tab 33, which is the personal home tab of user 03, as shown in FIG. 6B. In this embodiment, in personal mode, tabs with personal attributes other than the personal home tab of the logged-in user are not displayed, and tabs with shared attributes are not displayed unless they are the personal home tab of the logged-in user. However, in personal mode, a tab with shared attributes may also be displayed in addition to the personal home tab of the logged-in user.

(5) Execution of Function by NFC Card Next, an example of screen transition when the NFC card 7 is held over the device to execute a card activation shortcut will be described.

When the attributes of each tab are set as shown in Figure 4(a) and the user mode is set to general mode, the standby screen 40 shown in Figure 6(a) is displayed on the display unit 13. In this case, the third tab 33, in which a card startup shortcut is registered, is not displayed.

Here, let's assume that an NFC card 7 with a card ID of "12345678" is held over the device. In this case, the card launch shortcut corresponding to this card ID is not registered in any tab that can be displayed in general mode. That is, the card launch shortcut corresponding to this card ID is the shortcut function corresponding to the 19th icon 63, which is registered in the third tab 33, which is not currently displayed. Therefore, the card launch shortcut corresponding to this card ID is not executed, and the no access right notification screen 70 shown in FIG. 6(a) is displayed on the display unit 13. The no access right notification screen 70 displays a message 71 indicating that a card launch shortcut corresponding to the NFC card 7 is not registered in any tab that can be displayed in general mode; in other words, the user does not have access right to the corresponding card launch shortcut and it cannot be executed.

On the other hand, for example, if user 03 logs in and the user mode is set to personal mode, the standby screen 40 shown in FIG. 6(b) is displayed on the display unit 13. In this case, since user 03's personal home tab is the third tab 33 (see FIG. 5), the standby screen 40 displays the third tab 33 and no other tabs. The third tab 33 also has a card launch shortcut registered that corresponds to card ID "12345678," and includes the 19th icon 63 that corresponds to that card launch shortcut.

Therefore, when an NFC card 7 with card ID "12345678" is held over the device, the corresponding card activation shortcut, i.e., the shortcut function corresponding to the 19th icon 63, is executed. While the card activation shortcut is being executed, the execution screen 73 shown in FIG. 6(b) is displayed on the display unit 13. The execution screen 73 includes a message indicating that the shortcut function is being executed.

In this way, if a card launch shortcut corresponding to the card ID of the NFC card 7 held over the image processing device 10 is not registered in the general attribute tab, the card launch shortcut will not be executed unless a registered user who has the tab on which the card launch shortcut is registered as their personal home tab is logged in.

However, in this embodiment, when an NFC card 7 is held over the device, if the corresponding card launch shortcut is registered in a personal attribute tab and a registered user who has the registered tab as their personal home tab is not logged in, the card launch shortcut may be executed if certain executable conditions are met.

In this embodiment, for example, condition A and condition B are set as the specific executable conditions.
If at least one of the conditions A and B is satisfied, it is determined that a specific executable condition is met.

Condition A is that the card launch shortcut is a function that does not include processing for transmitting information via wired or wireless connection to a device other than the image processing device 10. Therefore, a card launch shortcut that includes a fax function, such as the card launch shortcut corresponding to the 19th icon 63, does not satisfy condition A. On the other hand, the card launch shortcut corresponding to the 17th icon 61, for example, is a function that prints an image of a document scanned by the image processing device 10 on the image processing device 10, and does not include processing for transmitting information outside the image processing device 10, and therefore satisfies condition A.

Condition B is that the card launch shortcut is a one-touch shortcut function. Therefore, the card launch shortcuts corresponding to the 17th icon 61 and the 19th icon 63 are both normal shortcut functions, and therefore do not satisfy condition B. However, if the shortcut function corresponding to the 18th icon 62 were a card launch shortcut, it would satisfy condition B.

For example, as shown in FIG. 7, when the user mode is set to general mode and only the first tab 31 is displayed on the display unit 13, an NFC card 7 with a card ID of "87654321" is held over the device. In this case, the tabs displayed in general mode do not include a card activation shortcut with that card ID registered, so the card activation shortcut corresponding to that card ID will not generally be executed. However, the card activation shortcut corresponding to that card ID, i.e., the card activation shortcut corresponding to the 17th icon 61, satisfies condition A. Therefore, the NFC card activation confirmation screen 75 shown in FIG. 7 is displayed on the display unit 13.

The NFC card startup confirmation screen 75 is a screen that asks the user whether or not to execute the card startup shortcut. The NFC card startup confirmation screen 75 displays a confirmation message 76, an OK button 77, and a NO button 78.

The content of the confirmation message 76 differs depending on whether condition A or condition B is met. In other words, the content of the confirmation message 76 will depend on which condition is met. Figure 7 shows an example in which a confirmation message 76 corresponding to condition A is displayed in response to condition A being met.

If the NO button 78 is selected on the NFC card activation confirmation screen 75, the card activation shortcut will not be executed. On the other hand, if the OK button 77 is selected, the card activation permission flag is set to ON, and the standby screen 40 is displayed again on the display unit 13. Note that all card activation permission flags are set to OFF by default, and are set to ON when the execution conditions are met.

After that, when the same NFC card 7 is held up again, the card activation permission flag for the corresponding card activation shortcut is set to on, so that card activation shortcut is executed. During execution, the execution screen 80 is displayed, as shown in Figure 7.

The card activation permission flag may be set to off again at a specific timing, or once set to on, may remain on permanently unless a specific flag initialization process is performed. When the card activation permission flag is set to off again at a specific timing, the specific timing may be any timing. For example, the flag may be set to off after the card activation shortcut is executed a predetermined number of times. Also, for example, the flag may be set to off after a certain time has elapsed since it was set to on.

Next, an example of a screen transition when the attribute of a tab in which a card activation shortcut is registered is changed from shared to personal will be described with reference to FIG.
First, assume that the first tab 31 and the third tab 33 are set to the shared attribute and the user mode is set to the general mode. In this case, as shown on the left side of Fig. 8, a standby screen 40 including the first tab 31 and the third tab 33, one of which (for example, the first tab 31 in Fig. 8) is selected, is displayed. Here, a card activation shortcut is registered in the third tab 33, as shown in Figs. 3 and 6(b).

If the attribute of the third tab 33 is changed from shared to personal in this state, the display unit 13 will display the personal release confirmation screen 85 shown in FIG. 8 after the change. The personal release confirmation screen 85 is a screen for asking the user whether or not to change the tab whose attribute has been changed to personal back to shared. The personal release confirmation screen 85 displays a confirmation message 86, an OK button 87, and a NO button 88. The confirmation message 86 informs the user that a card activation shortcut has been registered to the tab whose attribute has been changed to personal, and asks the user whether or not to set the tab to shared again.

When the NO button 88 is selected on the personal release confirmation screen 85, the tabs that have been changed to personal attributes remain as personal attributes. The display unit 13 then displays the standby screen 40 shown in the lower right of Figure 8, i.e., the standby screen 40 displaying only the first tab 31, which is the only shared tab. On the other hand, when the OK button 87 is selected, the tabs that have been changed to personal attributes are changed to shared attributes. The display unit 13 then displays the standby screen 40, which includes the two shared tabs 31 and 33, as shown on the left of Figure 8.

(6) Main Processing Next, the main processing executed by the control unit 11 will be described with reference to Figures 9 to 11. After starting up, the control unit 11 (more specifically, the CPU) executes predetermined initial processing, and then executes the main processing in accordance with the main processing program shown in Figures 9 to 11 stored in the storage unit 12. The various screen transitions described above are realized by the control unit 11 executing the main processing.

When the control unit 11 starts the main processing, in S110, it causes the display unit 13 to display the standby screen 40. After startup, the control unit 11 sets the user mode to the general mode. Therefore, in S110, it causes the standby screen 40 corresponding to the general mode (see, for example, Figure 6(a)) to be displayed based on the tab setting table (see Figure 4(a)).

In S120, it is determined whether the NFC card 7 has been held over the device. When the NFC card 7 is held over the device, the aforementioned wireless communication between the NFC card 7 and the short-range wireless communication unit 17 is performed, allowing the control unit 11 to detect that the NFC card 7 has been held over the device and to obtain the card ID from the NFC card 7.

If the NFC card 7 is not held over, the process proceeds to S220. In S220, it is determined whether any other events have occurred other than the NFC card 7 being held over. Other events include, for example, an icon being selected, a tab being selected, a request to register a new shortcut function for an unregistered icon, a request to register a card ID for an icon, a request to change the attributes of a tab, a request to log in or log out by the user, a request to change various setting values, etc.

If no other events have occurred, proceed to S110. If another event has occurred, in S230, processing corresponding to the event that has occurred is executed. For example, if an icon is selected, the function corresponding to that icon is executed.

In S240, the tab setting change confirmation process is executed. Details of the tab setting change confirmation process are shown in Figure 11. When the process proceeds to the tab setting change confirmation process, in S410 it is determined whether the tab setting has been changed by the process of S230, in other words, whether processing has been performed that would change the contents of the tab setting change table shown in Figure 4(a). If the tab setting has not been changed, the process proceeds to S110 (Figure 9). If the tab setting has been changed, the process proceeds to S420.

In S420, a card launch shortcut is searched for in the icon data table (see Figure 3). In S430, it is determined whether a card launch shortcut exists. If a card launch shortcut does not exist, the process proceeds to S110 (Figure 9). If a card launch shortcut exists, the process proceeds to S440.

In S440, it is determined whether the attribute of the tab on which the card launch shortcut is registered is shared. If it is shared, the process proceeds to S110 (Figure 9); if it is personal, the process proceeds to S450.

In S450, personal warning processing is performed. Specifically, the personal release confirmation screen 85 shown in FIG. 8 is displayed. In S460, it is determined whether the OK button 87 has been selected. If the OK button 87 has not been selected, in S480 it is determined whether the NO button 88 has been selected. If not, the process proceeds to S450; if selected, the process proceeds to S110 (FIG. 9). If the OK button 87 has been selected in S460, the shared restoration process is performed in S470. Specifically, the personal attribute tab in which the card activation shortcut is registered is set to the shared attribute. After processing in S470, the process proceeds to S110 (FIG. 9).

Returning to FIG. 9, if it is determined in S120 that the NFC card 7 has been held over the device, the process proceeds to S130. In S130, the card ID of the held NFC card 7 is obtained via the short-range wireless communication unit 17. In S140, the icon data table is referenced to search for a card activation shortcut in which the obtained card ID is registered.

In S150, it is determined whether a corresponding card activation shortcut, i.e., a shortcut function for which the acquired card ID is registered, exists. If a corresponding card activation shortcut does not exist, in S160, a notification screen (not shown) indicating that there is no corresponding shortcut is displayed for a certain period of time, and then the process proceeds to S110. The notification screen indicating that there is no corresponding shortcut is a screen that notifies the user that there is no card activation shortcut corresponding to the card ID of the NFC card 7 that is being held over the device.

If a corresponding card launch shortcut is found in S150, the process proceeds to S170. In S170, a determination is made as to whether the tab to which the corresponding card launch shortcut belongs, i.e., the attribute of the tab to which the corresponding card launch shortcut is registered, is shared. If it is shared, the card launch shortcut is executed in S180. While the shortcut is being executed, an execution screen (see Figures 6, 7, etc.) is displayed.

If the tab to which the corresponding card launch shortcut belongs is personal, the process proceeds to S190. In S190, it is determined whether the tab to which the corresponding card launch shortcut belongs is the personal home tab of the currently logged-in user. If it is the personal home tab of the logged-in user, the card launch shortcut is executed in S180. If it is not the home tab of the logged-in user, the process proceeds to S200.

In S200, it is determined whether the card activation permission flag for the corresponding card activation shortcut is set to on. If the card activation permission flag is set to on, in S180, the card activation shortcut is executed. Note that, as mentioned above, there are various possible timings for setting the card activation permission flag to off after the card activation shortcut is executed because the card activation permission flag is set to on.

If the card activation permission flag is set to OFF in S200, no access right handling processing is executed in S210. Details of the no access right handling processing in S210 are shown in Figure 10. When proceeding to the no access right handling processing, in S310 it is determined whether the corresponding card activation shortcut satisfies specific executable conditions. Specifically, it is determined whether at least one of the aforementioned conditions A and B is satisfied. If the specific executable conditions are not satisfied, in S320 a no access right notification screen 70 (see Figure 6) is displayed for a certain period of time, and then the process proceeds to S110.

If certain executable conditions are met in S310, the process proceeds to S330. In S330, the NFC card startup confirmation screen 75 (see Figure 7) is displayed. In S340, it is determined whether the OK button 77 has been selected. If the OK button 77 has not been selected, it is determined in S360 whether the NO button 78 has been selected. If not, the process proceeds to S330; if selected, the process proceeds to S110.

If the OK button 77 is selected in S340, the card activation permission flag for the corresponding card activation shortcut is changed to ON in S350, and the process proceeds to S110. As a result of this flag change, the next time the same NFC card 7 is held over the NFC card again, a positive determination is made in S200 and the card activation shortcut is executed.

(7) Effects of the Embodiments According to the above-described embodiments, the following effects are achieved.
That is, in the image processing device 10 of this embodiment, even if an NFC card 7 having a card ID corresponding to a registered card activation shortcut is held over the device, if the card activation shortcut is registered in the personal attributes tab, the card activation shortcut will not be executed. This makes it possible to appropriately restrict the execution of card activation shortcuts.

For example, if a card launch shortcut is registered in a tab with shared attributes, in order to restrict the use of that card launch shortcut, the attributes of the tab in which the card launch shortcut is registered can be changed to personal, thereby restricting the execution of that card launch shortcut both through icon operations and through the NFC card 7.

In addition, in this embodiment, even if a card launch shortcut is registered in a personal attribute tab, if that tab is the personal home tab of the logged-in user, the card launch shortcut can be executed by holding the NFC card 7 over it.

Furthermore, in this embodiment, even if a card activation shortcut is registered in the personal attribute tab, it will be executed if certain executable conditions are met. Therefore, card activation shortcuts can be appropriately restricted according to the content of the card activation shortcut.

In this embodiment, the image processing device 10 corresponds to an example of a function executing device. The short-range wireless communication unit 17 corresponds to an example of a communication unit. The NFC card 7 corresponds to an example of a wireless communication device. The card ID corresponds to an example of a device ID and an object ID. A match between the card ID acquired from the NFC card 7 and the card ID registered in the card activation shortcut corresponds to an example of a specific correspondence. Each shortcut icon corresponding to a shortcut function corresponds to an example of a function object. A shortcut icon corresponding to a normal shortcut function corresponds to an example of a first-type object, and a shortcut icon corresponding to a one-touch shortcut function corresponds to an example of a second-type object. The NFC card activation confirmation screen 75 (Figure 7) corresponds to an example of an execution confirmation screen. The personal release confirmation screen 85 (Figure 8) corresponds to an example of a settings confirmation screen. Selecting the OK button 87 on the personal release confirmation screen 85 corresponds to an example of a sharing change request.

Furthermore, the processing of S110 corresponds to an example of general mode display processing and personal mode display processing. The processing of S130 corresponds to an example of device ID acquisition processing. The processing of S180 corresponds to an example of second function execution processing. The processing of S230 corresponds to an example of first function execution processing, login acceptance processing, personal home tab setting processing, and attribute setting processing. The processing of S320 corresponds to an example of notification processing. The processing of S450 corresponds to an example of setting confirmation display processing. The processing of S460 corresponds to an example of sharing change acceptance processing. The processing of S470 corresponds to an example of attribute change processing.

2. Other Embodiments
Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

(1) In the above embodiment, a card ID could be registered for a shortcut function, but it is also possible to register a card ID for functions other than shortcut functions so that they can be activated from the NFC card 7.

(2) In the main processing, the processing using the card activation permission flag may be omitted. Specifically, in the no access right handling processing of FIG. 10, if the OK button 77 is selected in S340, the processing may proceed to S180 and the card activation shortcut may be executed.

Also, if it is determined in S310 that the relevant card launch shortcut satisfies certain executable conditions, the card launch shortcut may be executed in S180 without proceeding to S330.

(3) A process similar to the tab setting change confirmation process of S240 may be executed while the tab setting change operation is being performed, rather than after the tab setting change has been performed. For example, when an operation is performed to change the tab attribute from shared to personal, a screen may be displayed asking the user whether or not to change the attribute to personal before the attribute is actually changed. At that time, it may be displayed that a card launch shortcut is registered for the tab whose attribute is being changed to personal, and information about that card launch shortcut. Then, when an operation is performed on that screen indicating that it is okay to change the attribute to personal, the attribute may be changed to personal.

(4) If it is determined in S440 of Fig. 11 that the attribute of the tab to which the card launch shortcut is registered is not shared (i.e., personal), the following processing may be performed, for example. That is, information indicating that a card launch shortcut is registered in a tab with personal attributes may be displayed, and a screen may be displayed asking the user whether or not to delete the card launch shortcut. Then, if an operation indicating that deletion is permitted is performed, the registration of the card launch shortcut may be deleted.

(5) In the above embodiment, when the NFC card 7 was held over the device, a card launch shortcut was executed that had a registered card ID that matched the card ID acquired from the NFC card 7. However, the information registered in the card launch shortcut to enable launch from the NFC card 7 does not have to be the card ID itself. For example, a unique object ID may be registered in the shortcut function, and that object ID may be linked to a specific card ID. Then, when the NFC card 7 is held over the device, if the card ID acquired from the NFC card 7 is the card ID linked to the object ID, the card launch shortcut that has that object ID registered may be executed.

(6) The present disclosure is not limited to application to the image processing device 10 shown in Fig. 1. The present disclosure is applicable to any function executing device that has a wireless communication function and is configured to be able to execute various functions.

Furthermore, the wireless communication device with which the function performing device of the present disclosure can wirelessly communicate is not limited to the NFC card 7 described in the above embodiment. The function performing device of the present disclosure may be capable of wireless communication with various wireless communication devices having a specific device ID. Furthermore, the communication method with the wireless communication device is not limited to NFC.

(7) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

1...information processing system, 7...NFC card, 7a...antenna, 7b...communication circuit, 7c...storage unit, 10...image processing device, 11...control unit, 12...storage unit, 13...display unit, 14...input unit, 17...near-field wireless communication unit, 20...information processing device, 31...first tab, 32...second tab, 33...third tab, 34...fourth tab, 40...standby screen, 50...first tab screen, 51...first icon, 52...second icon, 53...third icon, 54...fourth icon, 55...5th icon, 56...6th icon, 57...7th icon, 58...8th icon, 60...3rd tab screen, 61...17th icon, 62...18th icon, 63...19th icon, 64...20th icon, 65...21st icon, 66...22nd icon, 67...23rd icon, 68...24th icon, 70...no access rights notification screen, 75...NFC card activation confirmation screen, 85...personal deactivation confirmation screen.

Claims (14)

A short-range wireless communication unit;
A control unit;
Memory and
a function execution unit;
A function execution device comprising:
the short-range wireless communication unit is capable of detecting a wireless communication device located within a short distance with which the short-range wireless communication unit can communicate,
the control unit is capable of storing a plurality of pieces of shortcut information in the memory,
a function to be executed by the function execution unit and a setting value used for executing the function are registered in advance in each of the plurality of pieces of shortcut information;
the control unit is capable of storing each of the plurality of pieces of shortcut information in the memory in association with the wireless communication device;
When a requirement is met that the wireless communication device is detected by the short-range wireless communication unit and shortcut information associated with the detected wireless communication device is included in the plurality of pieces of shortcut information stored in the memory, the control unit:
If login is not required to execute the function registered in the shortcut information associated with the detected wireless communication device , cause the function execution unit to execute the function registered in the shortcut information associated with the detected wireless communication device in accordance with the setting value registered in the shortcut information associated with the detected wireless communication device ;
When the login is required to execute the function registered in the shortcut information associated with the detected wireless communication device , the function execution unit is not caused to execute the function registered in the shortcut information associated with the detected wireless communication device in accordance with the setting value registered in the shortcut information associated with the detected wireless communication device .
Function execution device. 2. A function executing device according to claim 1,
an input unit;
A display unit;
Equipped with
the control unit is capable of performing a standby screen display process for displaying a standby screen on the display unit,
the standby screen includes one screen selected from a plurality of screens, a plurality of functional objects can be arranged on each of the plurality of screens, and any of the shortcut information can be associated with each of the plurality of functional objects;
the control unit further includes, in response to a selection, via the input unit, of a shortcut object that is the function object associated with the shortcut information and that is arranged on the standby screen displayed on the display unit by the standby screen display process, causing the function execution unit to execute the function registered in the shortcut information in accordance with the setting value registered in the shortcut information associated with the selected shortcut object.
Function execution device. 3. A function executing device according to claim 2,
each of the plurality of screens can be set to require the login in order to display the screen on the display unit;
In response to the requirement being met, the control unit:
When a wireless-enabled shortcut object, which is the shortcut object associated with the shortcut information associated with the detected wireless communication device, is located on a first type screen of the plurality of screens that is not set to require the login for display on the display unit, the function execution unit executes the function registered in the shortcut information associated with the wireless-enabled shortcut object in accordance with the setting value registered in the shortcut information;
When the wireless-compatible shortcut object is arranged on a second type screen among the plurality of screens that is set to require the login in order to display it on the display unit, the function executing unit is not caused to execute the function registered in the shortcut information corresponding to the wireless-compatible shortcut object in accordance with the setting value registered in the shortcut information.
Function execution device. 4. A function executing device according to claim 3,
the control unit is capable of performing a login process to accept the login,
In response to the requirement being met, even if the wireless-enabled shortcut object is arranged on the screen of the second type, if the login required to display the screen has been accepted by the login process, the control unit causes the function execution unit to execute the function registered in the shortcut information associated with the wireless-enabled shortcut object in accordance with the setting value registered in the shortcut information.
Function execution device. 5. A function executing device according to claim 3 or claim 4,
In response to the requirement being met, even if the wireless-compatible shortcut object is arranged on the screen of the second type, if the wireless-compatible shortcut object satisfies a specific executable condition, the control unit causes the function execution unit to execute the function registered in the shortcut information associated with the wireless-compatible shortcut object in accordance with the setting value registered in the shortcut information.
Function execution device. 6. A function executing device according to claim 5,
the executable condition is that the function registered in the shortcut information associated with the wireless-enabled shortcut object does not include a process of transmitting information to a device other than the function-executing device;
Function execution device. 7. A function executing device according to claim 5 or claim 6,
Each of the plurality of pieces of shortcut information is set to either a first type in which an input operation via the input unit is required when the function registered in the shortcut information is executed, or a second type in which the input operation is not required when the function registered in the shortcut information is executed,
the execution condition is that the shortcut information associated with the wireless-compatible shortcut object is set to the second type;
Function execution device. A function executing device according to any one of claims 5 to 7,
In response to the requirement being met, the control unit:
When the wireless-compatible shortcut object is arranged on the screen of the second type and the wireless-compatible shortcut object satisfies the executable condition, an execution confirmation screen is displayed on the display unit to inquire whether or not to execute the function registered in the shortcut information associated with the wireless-compatible shortcut object,
after the execution confirmation screen is displayed, when a specific execution instruction indicating that the function is to be executed is input via the input unit, the function execution unit executes the function in accordance with the setting value registered in the shortcut information.
Function execution device. A function executing device according to any one of claims 3 to 8,
The control unit further
Each of the plurality of screens can be set to the first type screen or the second type screen,
When any one of the plurality of screens is changed from the first type screen to the second type screen and the changed screen includes the wireless-enabled shortcut object, a setting confirmation screen can be displayed on the display unit to ask whether or not to change the setting of the screen to the first type screen,
a change request for changing the setting of the setting confirmation screen to the first type screen can be received via the input unit while the setting confirmation screen is being displayed;
When the change request is accepted, the screen can be changed to the first type screen.
Function execution device. A function executing device according to any one of claims 1 to 9,
and when the requirement is satisfied, the control unit further executes a notification process of notifying the function execution unit of information indicating that the function registered in the corresponding shortcut information cannot be executed, when the function execution unit is not allowed to execute the function.
Function execution device. 5. A function executing device according to claim 4,
When the login is accepted by the login process, the control unit, in the standby screen display process, allows the screen of the second type that requires the login to be displayed on the display unit to be displayed on the display unit, but does not allow the screen of the second type that requires a login different from the login to be displayed on the display unit to be displayed on the display unit.
Function execution device. 12. A function performing device according to claim 11,
When the login is accepted by the login process, the control unit allows the first type of screen to be displayed on the display unit in the standby screen display process.
Function execution device. A function executing device according to any one of claims 1 to 12,
the wireless communication device has a specific device ID;
The correspondence of the wireless communication device detected by the short-range wireless communication unit to the shortcut information includes the device ID of the detected wireless communication device being associated with the shortcut information.
Function execution device. A function executing device according to any one of claims 1 to 13,
The short-range wireless communication unit and the wireless communication device are configured to be able to perform short-range wireless communication with each other based on the NFC short-range wireless communication standard.
Function execution device.