JP7589786B2 - Function execution device - Google Patents

Description

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

The following Patent Document 1 discloses an image processing device that is configured to be able to execute a specific process (e.g., a scan process) associated with a shortcut button simply by having a card reader read the card, without operating the shortcut button.

When the image processing device disclosed in Japanese Patent Laid-Open No. 2003-233691 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 the image processing device in this manner, it is possible, for example, to allow only a specific user to operate a shortcut button associated with a specific process. Specifically, this is made possible by placing a shortcut button that you want only a specific user 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 the 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 executed by reading the aforementioned card with a card reader, the following problem arises.

That is, 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 not be displayed unless that specific user logs in, so it is possible to prevent 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 execute the specific process associated with the user-only button.

In consideration of the above problems , the present disclosure provides a function execution device that is configured to enable a specific function to be executed 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 executing device according to an embodiment of the present invention includes a display unit, an input unit, a communication unit, and a control unit. 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 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 a shared attribute, among multiple tabs each set to a shared attribute or a personal attribute, and does not include a personal tab, which is a tab set to a personal attribute.

Each of the multiple tabs is configured to allow a functional object, which is an image associated with a function to be executed, to be registered. The functional object is configured to allow a specific object ID to be registered. The general mode standby screen shows one shared tab in a selected state, and includes the functional object registered in the 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 executing process is a process for 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 when the ID-corresponding object is registered in a shared tab, and does not execute a function associated with the ID-corresponding object when the ID-corresponding object is registered in a personal tab. The ID-corresponding object is the functional object in which an object ID that has a specific correspondence with the acquired device ID is registered.

In the 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 is not executed. Therefore, by registering the 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 is capable of detecting a wireless communication device located in 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 a memory. Each of the plurality of pieces of shortcut information indicates a shortcut function. A setting value used for executing the shortcut function is preset for the shortcut function.
The control unit is further capable of executing a wireless compatible shortcut execution process.
The wireless-compatible shortcut execution process causes the function execution unit to execute a shortcut function indicated in the shortcut information in accordance with a setting value set for the shortcut function.
The second shortcut execution process is
In response to a wireless communication device being detected by the short-range wireless communication unit and the detected wireless communication device corresponding to any one of the plurality of pieces of shortcut information stored in the memory,
If a wireless-enabled shortcut function, which is a shortcut function indicated in the corresponding shortcut information, is not associated with a specific user, the wireless-enabled shortcut function is executed by the function execution unit in accordance with a setting value set in the wireless-enabled shortcut function;
When the wireless-enabled shortcut function is associated with a specific user, the function execution unit is not caused to execute the wireless-enabled shortcut function.

FIG. 1 is an explanatory diagram illustrating a schematic configuration of an information processing system according to an embodiment. FIG. 13 is an explanatory diagram showing an example of a standby screen when a user is not logged in and all tabs are set to a shared attribute. FIG. 11 is an explanatory diagram illustrating an icon data table. 3A is an explanatory diagram showing a tab setting table, and FIG. 3B is an explanatory diagram showing a tab attribute setting screen. FIG. 4 is an explanatory diagram illustrating a user management data table. FIG. 1A 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; FIG. 1B 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. 13 is an explanatory diagram showing an example of screen transition when attempting to activate a card activation shortcut that is registered in the personal tab and does not perform external access from an NFC card in normal mode. FIG. 13 is an explanatory diagram showing an example of a screen transition when the attribute of a tab in which a card launch shortcut is registered is changed from shared to personal; FIG. 13 is a flowchart showing a main process. 10 is a flowchart showing a 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 of 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 data communication with each other through a network 3. The network 3 may be any network. The network 3 may be, for example, a wired network or a wireless network. Furthermore, in both wired and wireless communication, 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 for reading an image of an original document and generating image data of the read image. The print function is a function for printing an image on a sheet-like recording paper. The copy function is a function for printing an image read by the scan function by the print function. The fax function is for 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 has, for example, a CPU. The storage unit 12 has, for example, a semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory. That is, the image processing device 10 of this embodiment has a microcomputer including a CPU and a semiconductor memory.

The control unit 11 realizes various functions by executing a program stored in a non-transitive physical recording medium. In this embodiment, the storage unit 12 corresponds to the non-transitive physical recording medium storing the program. Note that the various functions realized by the control unit 11 are not limited to being realized by executing a program (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 FIG. 2 and FIG. 6 to FIG. 8. The storage unit 12 also stores data for the icon data table shown in FIG. 3, data for the tab setting table shown in FIG. 4(a), data for the user management data table shown in FIG. 5, and the main processing programs shown in FIG. 9 to FIG. 11.

The display unit 13 has a display device for displaying various 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 14a as an input device. The touch panel 14a is arranged so as to be 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, can detect a pointing operation by contact or proximity of a pointer to the image display area. That is, when a pointing operation is being performed on the image display area by a pointer, the touch panel 14a is configured to be able to output position information indicating the pointing position where the pointing operation is being performed. The touch panel 14a of this embodiment is configured to output position information continuously or periodically while a pointing operation is being performed by the pointer.

The touch panel 14a may be configured to detect only contact as a pointing operation, or may be configured to detect only proximity, or may be configured to detect 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 when a pointing operation has been performed, and at least one type of specific operation by the indicator when a pointing operation has been performed.

Specific operations that the control unit 11 can detect include, for example, a tap operation, a flick operation, and a drag operation. A tap operation is an operation in which a pointing operation is performed with an indicator and then the indicator is released at the same position. There are various possible specific forms of an indicator capable of performing a pointing operation, and for example, it may be a fingertip or a specific pointing device such as a stylus pen.

The reading unit 15 includes an image sensor, reads an image recorded on a document, and generates image data of 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-shaped recording paper.
The short-range wireless communication unit 17 performs wireless communication using a specific wireless communication method with other wireless communication devices existing in the vicinity of the image processing device 10. The specific wireless communication method may be any wireless communication method, and in this embodiment, for example, is 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 perform wireless communication 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 tens of centimeters) from a nearby surface of a predetermined range near the position where the short-range wireless communication unit 17 is mounted on the surface of the housing of the image processing device 10.

Other wireless communication devices with which the short-range wireless communication unit 17 can wirelessly communicate 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.
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 as to enable wireless communication, wireless communication is performed 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 transmitted 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. 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 terminals 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 capable of data communication with various other servers and various 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, sending and receiving facsimile data is basically performed via the second communication unit 19.

Although not shown in the figure, the image processing device 10 is equipped with a media interface. The media interface is adapted to removably attach various storage media, such as a USB flash memory. 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 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 has, for example, a CPU. The storage unit 22 has, for example, a semiconductor memory such as a ROM, a RAM, an NVRAM, or a flash memory. That is, the information processing device 20 of this embodiment is equipped with a microcomputer including a CPU and a semiconductor memory. Various software and data are stored in the storage unit 22.

The display unit 24 includes a display device capable of displaying images, such as a liquid crystal display or an organic EL display.
The input unit 23 has an input device for receiving various input operations. The input device of the input unit 23 includes, for example, a keyboard, a mouse, a touch panel, etc. The touch panel is superimposed on the display area of the image on 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 perform data communication with the image processing device 10 via the communication unit 25.

(4) Description of the standby screen Next, among 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 having one or more tabs. The number and type of tabs displayed on the standby screen 40 may vary depending on the user mode, which will be described later, or depending on the logged-in user. FIG. 2 shows an example of the standby screen 40 when the user mode is set to the general mode. FIG. 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 an individual tab screen. On the standby screen 40, a tab screen corresponding to one of the displayed tabs that is in a selected state is displayed. The selected tab is displayed in a different manner from the other tabs.

The standby screen 40 shown on the left side of FIG. 2 shows an example in which a first tab 31 with the tab name "Basic 1" is selected and the first tab 31 is 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 side of FIG. 2 shows an example in which a third tab 33 with the tab name "Custom 1" is selected and the third tab 33 is displayed in a different manner from the other tabs.

In this embodiment, the arrangement direction of each tab on the standby screen 40 is to the right. That is, each tab is arranged in sequence to the right. The arrangement order of each tab in the above arrangement direction is basically an order according to the specified order described below, that is, ascending order in 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.

A left button 38 and a right button 39 are displayed near both ends of the area in which the tabs are displayed on the standby screen 40. If there are five or more tabs and four of them are displayed, the tabs to be displayed can be scrolled left or right by selecting the left button 38 or the right button 39, 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 currently selected tab screen to another tab screen, you can, for example, select the tab to switch to. When you select a tab other than the currently selected tab, the selected tab is 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 in FIG. 2, when the third tab 33 is selected, the third tab 33 is selected as shown on the right in 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 in FIG. 2, the first tab 31 is selected as shown on the left in FIG. 2, and the first tab screen 50 corresponding to the first tab 31 is displayed on the standby screen 40.

Various pieces of information necessary to display the standby screen 40, and information regarding the content of the processing to be executed when various input operations are performed on the standby screen 40 via the input unit 14, are stored in the memory unit 12.

Multiple icons are registered in each tab, and each tab screen is an image in 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 FIG. 2, the first tab screen 50 corresponding to the first tab 31 has the first icon 51 to the eighth icon 58 registered in the first tab 31 arranged thereon. As shown on the right side of FIG. 2, the third tab screen 60 corresponding to the third tab 33 has the seventeenth icon 61 to the twenty-fourth icon 68 registered in the third tab 33 arranged thereon. Each icon includes the name of the icon. The specific type of each icon can be changed.

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

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

In the third tab screen 60 illustrated on the right of FIG. 2, for example, the 17th icon 61 is associated with a specific function in the copy function, the 18th icon 62 and the 19th icon 63 are associated with a specific function in the fax function, and the 20th icon 64 and the 21st icon 65 are associated with a specific function in the 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. A shortcut function is a function that is registered arbitrarily by the user. A shortcut function is set to execute a specific function according to a preset setting value. A user can register a shortcut function to an unregistered icon by performing a predetermined shortcut registration operation on the unregistered icon. At that time, the user can also arbitrarily set the name of the shortcut function. In addition, a user can change the contents of a shortcut function that has already been registered, or cancel the registration to make the icon an unregistered icon. An icon associated with a shortcut function will hereinafter also be referred to as a shortcut icon.

In this embodiment, shortcut functions are further classified into two types: normal shortcut functions and one-touch shortcut functions. A normal shortcut function is configured such that when a corresponding shortcut icon is selected, the registered shortcut function is not immediately started, but at least one further 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 setting value of the shortcut function via the confirmation screen. After the confirmation screen is displayed, when the user performs a specific execution start operation, the registered shortcut function is 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 operation by the user.

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

When registering a shortcut function to an icon on the tab screen, the user can choose to register it as either a normal shortcut function or a one-touch shortcut function.

Furthermore, 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, by performing a specific card registration operation. 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 the card ID via the input unit 14. Also, 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 launch shortcut. The information indicating that a card ID has been registered may be any information, and in this embodiment, it is, for example, the text "(NFC card)." In the standby screen 40 shown on the right of FIG. 2, the shortcut functions corresponding to the 17th icon 61 and the 19th icon 63 are card launch shortcuts.

Information about each icon is registered in the icon data table shown in Figure 3. In the icon data table, multiple pieces of information are registered 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), the card activation permission flag, and the tab to which it belongs.

In the example of FIG. 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 a tab setting table shown in FIG. 4(a). In the tab setting table, Nt tabs (e.g., 8 in this embodiment) are listed in a prescribed order. In this embodiment, the prescribed order is, for example, the order of the first tab to the eighth tab, as shown in FIG. 4(a).

An attribute is set for each tab. In this embodiment, the attribute is set to shared or personal. The attribute of a tab can be changed arbitrarily for each tab. Fig. 4(a) 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.

Further, 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 arbitrarily changed 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, for example, in the storage unit 12 of the image processing device 10. In this case, in the image processing device 10, the user may be able to customize each table stored in the storage unit 12 as desired.

In addition, each table may be acquired at a specific acquisition 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, when started up, 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. Even after acquiring and storing each table after startup, the control unit 11 may 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, a 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 a shared and personal radio button is displayed for each tab. The user can arbitrarily change the attributes of a tab 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 so that the attributes of the tab can be changed on the image processing device 10.

The standby screen 40 shown in FIG. 2 shows an example where the first tab 31 to the fourth tab 34 are all shared attributes. On the other hand, the standby screen 40 shown in FIG. 6 and FIG. 7 shows an example where the standby screen is based on the tab setting table in FIG. 4(a), that is, where the first tab 31 is shared attributes and all other tabs are personal attributes. The standby screen 40 shown on the left of FIG. 8 shows an example where the first tab 31 and the third tab 33 are shared attributes and all other tabs are personal attributes. The standby screen 40 shown on the bottom right of FIG. 8 shows an example where the first tab 31 is shared attributes and all other tabs are personal attributes.

In addition, in the image processing device 10, the user mode is set to the general mode or the personal mode. The personal mode is set when any of the pre-registered users (hereinafter referred to as "registered users") logs in by performing a specified user authentication operation. That is, when any registered user logs in, the personal mode corresponding to that registered user is set. The general mode is a user mode in which no registered user is logged in. In other words, the 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 in 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 a 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 a registration process for a registered user is performed in the information processing device 20, 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. In addition, the first tab is registered as the personal home tab of User 01, the second tab is registered as the personal home tab of User 02, the third tab is registered as the personal home tab of User 03, and the fourth tab is registered as the personal home tab of User 04, while none of the four users, User 05 to User 08, have a personal home tab registered. Both shared and personal attribute tabs can be registered as personal home tabs.

A registered user logs in by, for example, executing a predetermined authentication process that includes 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, a user switching interface 45 is displayed on the standby screen 40. The user switching interface 45 is an image that is selected (e.g., tapped) by the user to switch the user mode.

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 general mode is selected, 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 the general mode and each registered user as options. When the general mode is selected, the user mode is set to the general mode.

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

Therefore, for example, if the attributes of all tabs are shared, all tabs (however, a maximum of four tabs can be displayed at the same time) are displayed on the standby screen 40 in the normal mode, as shown in FIG. 2. Also, for example, if only the first tab 31 has a shared attribute, the first tab 31 is displayed on the standby screen 40 in the normal mode, as shown in FIG. 6(a) and FIG. 7, etc.

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

In the 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 a third tab 33, which is the personal home tab of user 03, as shown in FIG. 6B. In this embodiment, in the 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 the personal mode, in addition to the personal home tab of the logged-in user, a tab with shared attributes may also be displayed.

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

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

Now, assume that an NFC card 7 with a card ID of "12345678" is held up. In this case, the card launch shortcut corresponding to this card ID is not registered in any tab that can be displayed in the general mode. That is, the card launch shortcut corresponding to this card ID is a shortcut function corresponding to the 19th icon 63, which is registered in the third tab 33 that 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 the card launch shortcut corresponding to the NFC card 7 is not registered in any tab that can be displayed in the general mode, in other words, that the user does not have access right to the relevant card launch shortcut and cannot execute it.

On the other hand, for example, when 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 the personal home tab of user 03 is the third tab 33 (see FIG. 5), the standby screen 40 displays the third tab 33 and no other tabs. And, the third tab 33 has a card launch shortcut corresponding to the card ID "12345678" registered, and includes the 19th icon 63 corresponding to that card launch shortcut.

Therefore, when an NFC card 7 with a card ID of "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, an 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 in which the card launch shortcut is registered as their personal home tab is logged in.

However, in this embodiment, when the 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 a personal home tab is not logged in, the card launch shortcut may be executed if certain executable conditions are met.

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

Condition A is that the card launch shortcut is a function that does not include a process of 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 using the image processing device 10, and does not include a process of 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 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 the 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 the general mode do not include a card launch shortcut with the card ID registered, so the card launch shortcut corresponding to that card ID is not executed. However, the card launch shortcut corresponding to that card ID, i.e., the card launch shortcut corresponding to the 17th icon 61, satisfies condition A. Therefore, the NFC card launch 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 depends on the condition that 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.

When the NO button 78 is selected on the NFC card activation confirmation screen 75, the card activation shortcut is not executed. On the other hand, when 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 executable conditions are met.

After that, when the same NFC card 7 is held up again, the card launch shortcut is executed because the card launch permission flag of the corresponding card launch shortcut is set to on. During execution, the execution screen 80 is displayed as shown in FIG. 7.

The card activation permission flag may be set to off again at a specific timing, or once set to on, may be permanently maintained on 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 card activation permission flag may be set to off when the card activation shortcut is executed a predetermined number of times. Also, for example, the card activation permission flag may be set to off when a certain time has passed after being 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 in Fig. 8, a standby screen 40 is displayed that includes the first tab 31 and the third tab 33, and one of them (for example, the first tab 31 in Fig. 8) is in a selected state. Here, a card startup shortcut is registered in the third tab 33, as shown in Figs. 3 and 6(b).

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

When the NO button 88 is selected on the personal release confirmation screen 85, the tabs that have been changed to personal attributes are maintained as they are. The display unit 13 then displays the standby screen 40 shown in the lower right of FIG. 8, that is, 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 including the two shared attribute tabs 31, 33, as shown on the left of FIG. 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 (specifically the CPU) executes a predetermined initial processing, and then executes the main processing according to the main processing program of 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 process, in S110, the control unit 11 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, the control unit 11 causes the standby screen 40 corresponding to the general mode (see, for example, FIG. 6(a)) to be displayed based on the tab setting table (see FIG. 4(a)).

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

If the NFC card 7 is not held up, the process proceeds to S220. In S220, it is determined whether any other events have occurred other than the NFC card 7 being held up. 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 to an icon, a request to change the attributes of a tab, a request to log in or out by the user, a request to change various setting values, and the like.

If no other event has occurred, the process proceeds to S110. If another event has occurred, the process according to the event that has occurred is executed in S230. For example, if an icon is selected, the function corresponding to that icon is executed.

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

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

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

In S450, a personal warning process 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 return 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 the process of 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 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 or not a corresponding card activation shortcut exists, i.e., a shortcut function in which the acquired card ID is registered. If a corresponding card activation shortcut does not exist, in S160, a notification screen indicating that there is no corresponding shortcut (not shown) 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 for making the user aware that there is no card activation shortcut corresponding to the card ID of the NFC card 7 being held over.

If a corresponding card launch shortcut exists in S150, the process proceeds to S170. In S170, it is determined 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. During execution, 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 startup permission flag of the corresponding card startup shortcut is set to on. If the card startup permission flag is set to on, in S180, the card startup shortcut is executed. As described above, there are various possible timings for setting the card startup permission flag to off after the card startup shortcut is executed due to the card startup permission flag being set to on.

If the card activation permission flag is set to off in S200, no access right handling process is executed in S210. Details of the no access right handling process in S210 are as shown in FIG. 10. When moving to the no access right handling process, in S310, it is determined whether the corresponding card activation shortcut satisfies a specific executable condition. Specifically, it is determined whether at least one of the above-mentioned condition A and condition B is satisfied. If the specific executable condition is not satisfied, in S320, a no access right notification screen 70 (see FIG. 6) is displayed for a certain period of time, and then the process moves 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 FIG. 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, and if not, the process proceeds to S330, and if selected, the process proceeds to S110.

If the OK button 77 is selected in S340, the card activation permission flag of 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 up again, a positive determination is made in S200 and the card activation shortcut is executed.

(7) Advantages of the Embodiment According to the embodiment described above, the following advantages are obtained.
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 launch shortcut is held over the device, if the card launch shortcut is registered in the personal attributes tab, the card launch shortcut will not be executed. This makes it possible to appropriately restrict the execution of card launch shortcuts.

For example, if a card-launched shortcut is registered in a tab with shared attributes, in order to restrict the use of the card-launched shortcut, the attributes of the tab in which the card-launched shortcut is registered can be changed to personal, thereby restricting the execution of the card-launched shortcut from both execution by icon operation and execution by the NFC card 7.

In addition, in this embodiment, even if a card launch shortcut is registered in a tab with personal attributes, 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 is executed if a specific executable condition is met. Therefore, the card activation shortcut 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 execution 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. The card ID acquired from the NFC card 7 matches the card ID registered in the card activation shortcut, which corresponds to an example of a specific correspondence relationship. Each shortcut icon corresponding to each shortcut function corresponds to an example of a function object. The shortcut icon corresponding to the normal shortcut function corresponds to an example of a first type object, and the shortcut icon corresponding to the one-touch shortcut function corresponds to an example of a second type object. The NFC card activation confirmation screen 75 (FIG. 7) corresponds to an example of an execution confirmation screen. The personal release confirmation screen 85 (FIG. 8) corresponds to an example of a setting confirmation screen. Selecting the OK button 87 on the personal release confirmation screen 85 corresponds to an example of a sharing change request.

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

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 the shortcut function, but it may also be possible to register a card ID for functions other than the shortcut function and activate them from the NFC card 7.

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

Also, if it is determined in S310 that the corresponding 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 it is OK 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 the card launch shortcut. Then, when an operation is performed on that screen indicating that it is OK to change to personal, the attribute may be changed to personal.

(4) In S440 of Fig. 11, if it is determined that the attribute of the tab in which the card launch shortcut is registered is not shared (i.e., personal), for example, the following process may be performed. 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 the shortcut may be deleted is performed, the registration of the card launch shortcut may be deleted.

(5) In the above embodiment, when the NFC card 7 is held over, a card launch shortcut in which a card ID matching the card ID acquired from the NFC card 7 is registered is executed. 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, an object ID unique to the shortcut function may be registered and linked to a specific card ID. Then, when the NFC card 7 is held over and the card ID acquired from the NFC card 7 is the card ID linked to the object ID, the card launch shortcut in which the object ID is 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.

Moreover, 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 shown 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 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 unlock confirmation screen.

Claims (14)

A short-range wireless communication unit;
A control unit;
Memory,
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,
Each of the plurality of pieces of shortcut information indicates a shortcut function, and a setting value used for executing the shortcut function is set in advance for the shortcut function,
The control unit is further capable of performing a wireless shortcut execution process ,
The wireless shortcut execution process includes:
In response to the wireless communication device being detected by the short-range wireless communication unit and the detected wireless communication device corresponding to any one of the plurality of pieces of shortcut information stored in the memory,
when a wireless-enabled shortcut function, which is the shortcut function indicated in the corresponding shortcut information, is not associated with a specific user, cause the function execution unit to execute the wireless-enabled shortcut function according to the setting value set in the wireless-enabled shortcut function;
When the wireless-enabled shortcut function is associated with the specific user, the wireless-enabled shortcut function is not executed by the function execution unit.
Function execution device. 2. A function execution 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 one of the shortcut functions can be associated with each of the plurality of functional objects;
The control unit is further capable of performing a selection-based shortcut execution process,
The selection-based shortcut execution process includes, in response to a shortcut object being selected via the input unit, the shortcut function associated with the shortcut object, the shortcut object being arranged on the standby screen displayed on the display unit by the standby screen display process, causing the function execution unit to execute the shortcut function associated with the selected shortcut object in accordance with the setting value set for the shortcut function.
Function execution device. 3. A function executing device according to claim 2 ,
Each of the plurality of screens may be associated with a particular user;
In the wireless-compatible shortcut execution process, the control unit
When a wireless-enabled shortcut object, which is the shortcut object associated with the wireless-enabled shortcut function, is arranged on a shared screen, which is a screen to which the specific user is not associated, among the plurality of screens, the function execution unit executes the wireless-enabled shortcut function associated with the wireless-enabled shortcut object,
When the wireless-enabled shortcut object is arranged on a personal screen, which is a screen associated with the specific user among the plurality of screens, the function execution unit is not caused to execute the wireless-enabled shortcut function associated with the wireless-enabled shortcut object.
Function execution device. 4. A function executing device according to claim 3,
the control unit is capable of performing a login process for accepting logins from registered users who have been registered in advance,
In the wireless-compatible shortcut execution process, even if the wireless-compatible shortcut object is arranged on the personal screen, if the personal screen is associated with the registered user whose login is accepted by the login process, the control unit causes the function execution unit to execute the wireless-compatible shortcut function associated with the wireless-compatible shortcut object.
Function execution device. 5. A function executing device according to claim 3, further comprising:
In the wireless-compatible shortcut execution process, even if the wireless-compatible shortcut object is arranged on the personal screen, if the wireless-compatible shortcut object satisfies a specific executable condition, the control unit causes the function execution unit to execute the wireless-compatible shortcut function associated with the wireless-compatible shortcut object.
Function execution device. 6. A function executing device according to claim 5 ,
The execution condition is that the wireless-enabled shortcut function 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 6 ,
Each of the shortcut functions is set to either a first type in which an input operation via the input unit is required when the shortcut function is executed, or a second type in which the input operation is not required when the shortcut function is executed,
the execution condition is that the wireless-enabled shortcut function associated with the wireless-enabled shortcut object is set to the second type;
Function execution device. A function execution device according to any one of claims 5 to 7,
In the wireless-compatible shortcut execution process, the control unit
When the wireless-compatible shortcut object is arranged on the personal screen and the wireless-compatible shortcut object satisfies the executable condition, displaying on the display unit an execution confirmation screen inquiring whether or not to execute the wireless-compatible shortcut function associated with the wireless-compatible shortcut object,
when a specific execution instruction indicating that the wireless-enabled shortcut function is to be executed is input via the input unit after the execution confirmation screen is displayed, the wireless-enabled shortcut function is executed by the function execution unit.
Function execution device. A function execution device according to any one of claims 3 to 8,
The control unit further
a setting process for setting each of the plurality of screens to the shared screen or the personal screen;
a setting confirmation display process for displaying on the display unit a setting confirmation screen for asking whether or not to change the setting of the screen to the shared screen when the setting process has been performed to change the shared screen to the personal screen and when the changed screen includes the shortcut object associated with the shortcut function associated with the wireless communication device;
a sharing change receiving process for receiving, via the input unit, a sharing change request for requesting to change a setting of the setting confirmation screen to the shared screen while the setting confirmation screen is being displayed;
a change process for changing the setting of the screen to the shared screen when the sharing change request is accepted by the sharing change acceptance process;
A function executing device that executes the function. A function execution device according to any one of claims 1 to 9,
The control unit further executes a notification process of notifying information indicating that the wireless-compatible shortcut function cannot be executed when the wireless-compatible shortcut function is not executed by the function execution unit in the wireless-compatible shortcut execution process.
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 personal screen associated with the registered user whose login is accepted to be displayed on the display unit, but does not allow the personal screen associated with a user other than the registered user to be displayed on the display unit.
Function execution device. 12. A function execution device according to claim 11,
When the login is accepted by the login process, the control unit allows the shared screen to be displayed on the display unit in the standby screen display process.
Function execution device. A function execution device according to any one of claims 1 to 12,
The wireless communication device has a specific device ID;
The correspondence between the wireless communication device detected by the short-range wireless communication unit and the shortcut information includes a correspondence between the device ID of the detected wireless communication device and the shortcut information.
Function execution device. A function execution 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 based on the NFC short-range wireless communication standard.
Function execution device.

Images