Function execution device

Abstract

To make it possible to appropriately restrict execution of a specific function in a function execution device configured to be able to execute the specific function not only by a user's direct operation but also going through wireless communication with the outside.SOLUTION: A function execution device 10 can wirelessly communicate with a wireless communication device 7 within a communication possible area. The function execution device 10 has a tab-formatted screen displayed and each tab has a function object associated with a function displayed. Each tab is set to a shared attribute or a personal attribute. When the function execution device 10 acquires a device ID from the wireless communication device 7 through wireless communication, the function execution device executes a function in which an object ID having a specific correspondence relationship with the device ID is registered. However, when the function is registered with a tab with the personal attribute, the function is not executed.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for executing a registered function in response to a user operation. [Background technology]

[0002] The following Patent Document 1 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 the need to operate the shortcut button.

[0003] 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.

[0004] By configuring the image processing device in this way, for example, it becomes possible to allow only a specific user to operate a shortcut button associated with a specific process. Specifically, this is made possible by arranging a shortcut button that is to be allowed to be operated only by a specific user (hereinafter referred to as a "user-limited button") on a tab with personal attributes corresponding to the specific user, or by setting the tab on which the user-limited button is arranged to a tab with personal attributes corresponding to the specific user. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2016-010059 A Summary of the Invention [Problem to be solved by the invention]

[0006] However, if the specific process associated with the user-limited button can also be executed by having the card reader read the above-mentioned card, the following problem occurs.

[0007] That is, for example, assume that in order to make a shortcut button associated with a specific process that can be executed by a card into a user-limited button, the attribute of the tab on which the shortcut button is located is changed to a personal attribute corresponding to the specific user. In this case, the user-limited button is not displayed unless the specific user logs in, so that it is possible to prevent unspecified users other than the specific user from operating the user-limited button.

[0008] However, even if the user-only button is not displayed and cannot be operated, if the card is available, any unspecified user can use the card to execute a specific process associated with the user-only button.

[0009] The present invention has been made in consideration of the above problems, and provides a method for enabling a user to directly operate a specific function. The present invention aims to provide a function executing device that is configured to be able to execute a specific function not only via a specific function but also via wireless communication with an external device, and to appropriately restrict the execution of the specific function. [Means for solving the problem]

[0010] The function executing device 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.

[0011] 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 that is a tab set to the shared attribute among a plurality of tabs each set to the shared attribute or the personal attribute, and does not include a personal tab that is a tab set to the personal attribute.

[0012] Each of the plurality of 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 includes a shared tab in a selected state, and the functional object registered in the selected shared tab.

[0013] The control unit further executes a first function executing process, a device ID obtaining process, and a second function executing 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.

[0014] 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 the 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 functional object in which an object ID having a specific correspondence with the acquired device ID is registered.

[0015] In the function execution 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. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 is an explanatory diagram illustrating a schematic configuration of an information processing system according to an embodiment. [Diagram 2] 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. [Diagram 3] FIG. 11 is an explanatory diagram illustrating an icon data table. [Figure 4] FIG. 4A is an explanatory diagram showing a tab setting table, and FIG. 4B is an explanatory diagram showing a tab attribute setting screen. [Diagram 5] FIG. 4 is an explanatory diagram illustrating a user management data table. [Figure 6] 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, and 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. [Figure 7] 11 is an explanatory diagram showing an example of screen transitions when attempting to launch a card launch shortcut that is registered in the personal tab and does not perform external access from an NFC card in general mode. FIG. [Figure 8] 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. [Figure 9] 13 is a flowchart showing a main process. [Figure 10]10 is a flowchart showing no access right handling processing in S210 in the main processing in FIG. 9. [Figure 11] 10 is a flowchart showing the tab setting change confirmation process of S240 in the main process of FIG. 9. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [1. Embodiment] (1) Overview of the information processing system The information processing system 1 of the present 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 through 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, in both wired and wireless communication, the specific communication method may be any communication method.

[0018] (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.

[0019] 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.

[0020] The control unit 11 includes, for example, a CPU. The storage unit 12 includes, for example, a semiconductor memory such as a ROM, a RAM, an NVRAM, a flash memory, etc. That is, the image processing device 10 of this embodiment includes a microcomputer including a CPU and a semiconductor memory.

[0021] The control unit 11 realizes various functions by executing a program stored in a non-transitive substantial recording medium. In this embodiment, the storage unit 12 corresponds to the non-transitive substantial 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.

[0022] The storage unit 12 stores data of various screens shown in Fig. 2, and Fig. 6 to Fig. 8. The storage unit 12 also stores data of the icon data table shown in Fig. 3, data of the tab setting table shown in Fig. 4(a), data of the user management data table shown in Fig. 5, and main processing programs shown in Fig. 9 to Fig. 11.

[0023] 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.

[0024] The touch panel 14a arranged superimposed on the image display area of ​​the display unit 13 can detect a pointing operation by a pointer touching or approaching the image display area. That is, the touch panel 14a is configured to be able to output position information indicating a pointing position where a pointing operation is being performed when a pointing operation is being performed by a pointer on the image display area. The touch panel 14a of this embodiment is configured to output position information continuously or periodically while a pointing operation is being performed by a pointer.

[0025] The touch panel 14a may be configured to be capable of detecting only contact as an instruction operation, or may be configured to be capable of detecting only proximity, or may be configured to be capable of detecting both contact and proximity.

[0026] 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 is being performed, and at least one type of specific operation by the indicator when a pointing operation is being performed.

[0027] The specific operations detectable by the control unit 11 include, for example, a tap operation, a flick operation, a drag operation, etc. A tap operation is an operation in which a pointing operation is performed with a pointing object and then the pointing object is released at the same position. There are various possible specific forms of the pointing object capable of performing the pointing operation, and for example, the pointing object may be a fingertip or a specific pointing device such as a stylus pen.

[0028] 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.

[0029] 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-distance wireless communication unit 17 performs wireless communication with other wireless communication devices existing in the vicinity of the image processing device 10 using a specific wireless communication method. 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.

[0030] 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 exist within a 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 in 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.

[0031] 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. 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.

[0032] When the NFC card 7 is placed within the aforementioned communication area of ​​the image processing device 10, that is, 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.

[0033] 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.

[0034] The second communication unit 19 is an interface unit for communicating with an external device through 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. The transmission and reception of facsimile data in the fax function is basically performed via the second communication unit 19.

[0035] Although not shown in the drawings, the image processing device 10 includes a media interface. Various storage media, such as a USB flash memory, are removably attached to the media interface. The media interface controls writing and reading of data to and from the attached storage media.

[0036] (3) Configuration of the information processing device The information processing device 20 is, for example, any of various information processing terminals such as a personal computer, a tablet terminal, a smartphone, etc. 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, as shown in FIG.

[0037] The control unit 21 includes, for example, a CPU. The storage unit 22 includes, 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 the present embodiment includes a microcomputer including a CPU and a semiconductor memory. The storage unit 22 stores various software and data.

[0038] 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 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.

[0039] The communication unit 25 is a communication interface for communicating with an external device through the network 3. The information processing device 20 can perform data communication with the image processing device 10 via the communication unit 25.

[0040] (4) Explanation 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.

[0041] The standby screen 40 is a tab-format screen having one or more tabs. The number and types of tabs displayed on the standby screen 40 may vary depending on the user mode described below 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 a first tab 31, a second tab 32, a third tab 33, and a fourth tab 34 are displayed out of the multiple tabs.

[0042] Each of the multiple tabs is associated with an individual tab screen. A tab screen corresponding to one of the displayed tabs that is in a selected state is displayed on the standby screen 40. The selected tab is displayed in a different manner from the other tabs.

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

[0044] In this embodiment, the arrangement direction of the tabs on the standby screen 40 is the right direction. That is, the tabs are arranged in order in the right direction. The arrangement order of the tabs in the arrangement direction is basically an order according to a specified order described later, that is, ascending order in the specified order.

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

[0046] 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. When 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.

[0047] When a user wishes to switch from the tab screen of the currently selected tab to the tab screen of another tab, the user may, for example, select the tab to be switched to. When a user selects a tab other than the currently selected tab, the selected tab is placed in the selected state, 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 placed in the selected state as shown on the left in FIG. 2, when the third tab 33 is selected, the third tab 33 is placed in the selected state 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 placed in the selected state 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.

[0048] Various information required to display the standby screen 40, information regarding the contents of the processing to be executed when various input operations are performed on the standby screen 40 via the input unit 14, and the like are stored in the memory unit 12.

[0049] A plurality of icons are registered in each tab, and each tab screen is an image in which the plurality of 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.

[0050] That is, as shown on the left in Fig. 2, a first tab screen 50 corresponding to the first tab 31 has a first icon 51 to an eighth icon 58 registered in the first tab 31 arranged thereon. As shown on the right in Fig. 2, a third tab screen 60 corresponding to the third tab 33 has a seventeenth icon 61 to a 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.

[0051] Each icon is associated with a specific function, and when a user selects any of the icons, the specific function associated with that icon is executed.

[0052] In the first tab screen 50 illustrated on the left side 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 to associate the specific function with them. Explanation of the fifth icon 55 to the seventh icon 57 will be omitted.

[0053] 2, for example, a specific function in the copy function is associated with the 17th icon 61, a specific function in the fax function is associated with the 18th icon 62 and the 19th icon 63, and a specific function in the scan function is associated with the 20th icon 64 and the 21st icon 65. The 22nd icon 66 to the 24th icon 68 are unregistered icons.

[0054] The specific functions associated with the 17th icon 61 to the 21st icon 65 on the third tab screen 60 are all shortcut functions. The shortcut functions are functions that are registered arbitrarily by the user. The 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 predetermined shortcut registration operation on the unregistered icon. At that time, the name of the shortcut function can also be arbitrarily set. In addition, the 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. Hereinafter, an icon associated with a shortcut function will also be referred to as a shortcut icon.

[0055] In this embodiment, the shortcut functions are further classified into two types: normal shortcut functions and one-touch shortcut functions. The 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.

[0056] 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.

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

[0058] 2, on the standby screen 40, a normal mark 46 or a one-touch mark 47 is added to the shortcut icons. 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.

[0059] When registering a shortcut function to an icon on the tab screen, the user can arbitrarily select whether to register the shortcut function as a normal shortcut function or a one-touch shortcut function.

[0060] Furthermore, the user can register a card ID to any shortcut icon, that is, register the card ID to a shortcut function corresponding to the 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.

[0061] 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 by holding the NFC card 7 over the image processing device 10 via wireless communication.

[0062] When a card ID is registered in the shortcut function, information indicating that the card ID is registered is displayed on the shortcut icon corresponding to the card activation shortcut. The information indicating that the card ID is 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 activation shortcuts.

[0063] Information on each icon is registered in the icon data table shown in Fig. 3. In the icon data table, a plurality of pieces of information are registered for each icon, including the registered card ID, the function corresponding to the icon (i.e., the main function executed when the icon is selected), a card activation permission flag, and the tab to which the icon belongs.

[0064] 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.

[0065] 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. The prescribed order in this embodiment is, for example, the order of the 1st tab to the 8th tab, as shown in Fig. 4(a).

[0066] 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. 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. do.

[0067] 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 in, for example, 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.

[0068] Also, each table may be acquired from another device such as the information processing device 20 at a specific acquisition timing and stored in the storage unit 12. Specifically, for example, the information processing device 20 may be configured to allow each table to be arbitrarily customized. Then, when started, 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 starting, 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.

[0069] 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 in 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 screen similar thereto may be displayed on the image processing device 10 so that the attributes of the tabs can be changed on the image processing device 10.

[0070] 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 of Fig. 4(a), that is, the first tab 31 is a shared attribute and the other tabs are all personal attributes. The standby screen 40 shown on the left side of Fig. 8 shows an example where the first tab 31 and the third tab 33 are shared attributes and the other tabs are all personal attributes. The standby screen 40 shown on the bottom right of Fig. 8 shows an example where the first tab 31 is a shared attribute and the other tabs are all personal attributes.

[0071] 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 predetermined 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 input.

[0072] The 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. The 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, the registered user is added to the user management data table. In addition, a personal home tab can be registered for the registered user at will.

[0073] The user management data table shown in Fig. 5 illustrates an example in which eight users, user 01 to user 08, are registered as registered users. Also, an example is shown in which a first tab is registered as the personal home tab of user 01, a second tab is registered as the personal home tab of user 02, a third tab is registered as the personal home tab of user 03, a fourth tab is registered as the personal home tab of user 04, and no personal home tab is registered for any of the four users, user 05 to user 08. As for the personal home tab, a tab with either shared or personal attribute can be registered.

[0074] The login of a registered user is performed by executing a predetermined authentication process including inputting user authentication information (for example, a password) specific to the registered user via the input unit 14, for example.

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

[0076] 2, a user switching interface 45 is displayed on the standby screen 40. The user switching interface 45 is an image that is selected (for example, tapped) by the user to switch the user mode.

[0077] 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 the general mode, as shown in Fig. 2, Fig. 6(a), Fig. 7, and Fig. 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 Fig. 6(b).

[0078] 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.

[0079] In the general mode, the standby screen 40 displays tabs with the attribute "shared," and one of the tabs is in a selected state. In the general mode, the tabs with the attribute "personal" are not displayed.

[0080] Therefore, for example, if the attributes of all the tabs are shared, all the 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 the shared attribute, the first tab 31 is displayed on the standby screen 40 in the normal mode, as shown in Figs. 6(a) and 7.

[0081] 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 regular user authentication information corresponding to the selected registered user is input 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.

[0082] 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 the user's home tab as shown in FIG. 6(b). In the personal mode, a third tab 33, which is the personal home tab of the logged-in user, is displayed. 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 except when 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.

[0083] (5) Executing functions using NFC cards Next, an example of screen transition when NFC card 7 is held over to execute a card activation shortcut will be described.

[0084] When the attributes of each tab are set as shown in Fig. 4(a) and 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.

[0085] Here, for example, it is assumed 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 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 the tab that can be displayed in the general mode, in other words, that the user does not have the access right to the corresponding card launch shortcut and cannot execute it.

[0086] On the other hand, for example, when user 03 logs in and the user mode is set to the 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 third tab 33 is displayed on the standby screen 40, and other tabs are not displayed. And, the third tab 33 has a card launch shortcut corresponding to the card ID "12345678" registered therein, and includes the 19th icon 63 corresponding to the card launch shortcut.

[0087] Therefore, when an NFC card 7 with a card ID of "12345678" is held over the NFC card 7, the corresponding card activation shortcut, i.e., the shortcut function corresponding to the 19th icon 63, is executed. During the execution of the card activation shortcut, 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.

[0088] 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 a general attribute tab, the card launch shortcut will not be executed, except when a registered user who has the tab in which the card launch shortcut is registered as his or her personal home tab is logged in.

[0089] However, in this embodiment, when NFC card 7 is held over, if a 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.

[0090] 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 met.

[0091] Condition A is that the card launch shortcut is a function that does not include a process of transmitting information via a 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 to the outside of the image processing device 10, and therefore satisfies condition A.

[0092] Condition B is that the card activation shortcut is a one-touch shortcut function. Therefore, the card activation 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 activation shortcut, condition B would be satisfied.

[0093] 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 therein, 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, an NFC card launch confirmation screen 75 shown in Fig. 7 is displayed on the display unit 13.

[0094] The NFC card activation confirmation screen 75 is a screen for asking the user whether or not it is OK to execute the card activation shortcut. The NFC card activation confirmation screen 75 displays a confirmation message 76, an OK button 77, and a NO button 78.

[0095] 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. Fig. 7 shows an example in which a confirmation message 76 corresponding to condition A is displayed in response to condition A being met.

[0096] 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 the card activation permission flags are all set to OFF by default, and are set to ON when the executable conditions are met.

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

[0098] 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 after the card activation shortcut is executed a predetermined number of times. Also, for example, after being set to on, the card activation permission flag may be set to off after a certain number of times. It may be set to off if the time has elapsed.

[0099] Next, 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 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, one of which (for example, the first tab 31 in Fig. 8) is in a selected state. Here, a card activation shortcut is registered in the third tab 33, as shown in Figs. 3 and 6(b).

[0100] In this state, when 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 return the tab changed to the personal attribute to the shared attribute again. 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 notifying the user that a card activation shortcut is registered in the tab changed to the personal attribute, and for asking the user whether or not to set the tab to the shared attribute again.

[0101] When the NO button 88 is selected on the personal release confirmation screen 85, the tabs changed to the personal attributes are maintained as they are. Then, the display unit 13 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 changed to the personal attributes are changed to the shared attributes. Then, the display unit 13 displays the standby screen 40 including the two tabs 31 and 33 with the shared attributes, as shown on the left of Fig. 8.

[0102] (6) Main processing Next, the main processing executed by the control unit 11 will be described with reference to Fig. 9 to Fig. 11. After starting up, the control unit 11 (more specifically, the CPU) executes a predetermined initial processing, and then executes the main processing according to the main processing program of Fig. 9 to Fig. 11 stored in the storage unit 12. The above-mentioned various screen transitions are realized by the control unit 11 executing the main processing.

[0103] 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 normal mode. Therefore, in S110, the control unit 11 causes the standby screen 40 corresponding to the normal mode (for example, see FIG. 6(a)) to be displayed based on the tab setting table (see FIG. 4(a)).

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

[0105] If the NFC card 7 is not held over, the process proceeds to S220. In S220, it is determined whether or not an event other than the holding of the NFC card 7 has occurred. The other events include, for example, an icon being selected, a tab being selected, an operation requesting new registration of a shortcut function for an unregistered icon being performed, an operation requesting registration of a card ID for an icon being performed, an operation requesting change of attributes of a tab being performed, an operation requesting login or logout by the user being performed, an operation requesting change of various setting values ​​being performed, and the like.

[0106] 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 has been selected, a function corresponding to that icon is executed.

[0107] 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.

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

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

[0110] In S450, a personal warning process is performed. Specifically, the personal release confirmation screen 85 illustrated 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, it is determined in S480 whether the NO button 88 has been selected, and if not, the process proceeds to S450, and if selected, the process proceeds to S110 (FIG. 9). In S460, if the OK button 87 has been selected, the shared return process is performed in S470. Specifically, the tab of the personal attribute 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).

[0111] 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.

[0112] In S150, it is determined whether or not a corresponding card activation shortcut, i.e., a shortcut function in 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 for making the user recognize that there is no card activation shortcut corresponding to the card ID of the NFC card 7 being held over.

[0113] 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 FIG. 6, FIG. 7, etc.) is displayed.

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

[0115] In S200, it is determined whether or not 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, the card startup shortcut is executed in S180. As described above, various timings are possible 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.

[0116] 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 the process proceeds 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 proceeds to S110.

[0117] If certain executable conditions are met in S310, the process proceeds to S330. In S330, an 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.

[0118] 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. Due to this flag change, the next time the same NFC card 7 is held over again, a positive determination is made in S200 and the card activation shortcut is executed.

[0119] (7) Effects of the embodiment According to the embodiment described above, 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 launch shortcut is held over the device, if the card launch shortcut is registered in the personal attribute tab, the card launch shortcut will not be executed. This makes it possible to appropriately restrict the execution of the card launch shortcut.

[0120] For example, if a card launch shortcut is registered in a tab with shared attributes, in order to restrict the use of the card launch shortcut, the attributes of the tab in which the card launch shortcut is registered can be changed to personal, making it possible to restrict the execution of the card launch shortcut both by icon operation and by NFC card 7.

[0121] Furthermore, 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.

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

[0123] 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.

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

[0125] 2. Other embodiments Although the embodiment of the present invention has been described above, the present invention is not limited to the above-mentioned embodiment, and can be practiced in various modified forms.

[0126] (1) In the above embodiment, a card ID can be registered for a shortcut function. However, a card ID can also be registered for a function other than the shortcut function so that the function can be activated from the NFC card 7.

[0127] (2) In the main process, the process using the card startup permission flag may be omitted. Specifically, in the no access right handling process in 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.

[0128] Also, if it is determined in S310 that the relevant card activation shortcut satisfies a specific executable condition, the card activation shortcut may be executed in S180 without proceeding to S330.

[0129] (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, not after the tab setting change has been performed. For example, when an operation is performed to change the attribute of a tab from shared to personal, a screen may be displayed to ask 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 to be changed to personal, and information about the card launch shortcut. Then, when an operation is performed on the screen indicating that it is OK to change to personal, the attribute may be changed to personal.

[0130] (4) In S440 of Figure 11, the attribute of the tab where the card launch shortcut is registered is If it is determined that the shortcut is not shared (i.e., personal), the following process may be performed, for example. That is, information indicating that a card-activated shortcut is registered may be displayed in the personal attribute tab, and a screen may be displayed asking the user whether or not to delete the card-activated shortcut. Then, if an operation indicating that the shortcut may be deleted is performed, the registration of the card-activated shortcut may be deleted.

[0131] (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 activation 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.

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

[0133] Moreover, the wireless communication device with which the function performing device of the present invention can wirelessly communicate is not limited to the NFC card 7 shown in the above embodiment. The function performing device of the present invention 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.

[0134] (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. [Explanation of symbols]

[0135] 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

1. A display unit; An input unit; The Communications Department and A control unit; A function execution device comprising: the communication unit is configured to be able to perform 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 is a general mode display process for displaying on the display unit a general mode standby screen including a shared tab that is a tab set to the shared attribute and not including a personal tab that is a tab set to the personal attribute among a plurality of tabs each set to a shared attribute or a personal attribute; Run Each of the plurality of tabs is configured to allow a functional object, which is an image associated with a function to be executed, to be registered therein; The functional object is configured so that a specific object ID can be registered; the general mode standby screen includes one of the shared tabs in a selected state and the functional object registered in the selected shared tab, The control unit further a first function execution process for executing a function associated with a functional object displayed on the display unit in response to the functional object being selected via the input unit; a device ID acquisition process for acquiring the device ID from the wireless communication device through the wireless communication by the communication unit; a second function execution process that is executed in response to the device ID being acquired by the device ID acquisition process, and that executes a function associated with an ID corresponding object, which is a functional object in which an object ID having a specific correspondence with the acquired device ID is registered, when the ID corresponding object is registered in the shared tab, and does not execute a function associated with the ID corresponding object, when the ID corresponding object is registered in the personal tab; A function executing device that executes a function.

2. 2. A function execution device according to claim 1, The control unit further A login acceptance process for accepting logins from pre-registered users; a personal home tab setting process for setting one of the plurality of tabs as a personal home tab for each of the registered users; a personal mode display process for displaying, on the display unit, a personal mode standby screen including at least the personal home tab set for the registered user when the login of the registered user is accepted by the login acceptance process, the personal mode standby screen not including any personal tab other than the personal home tab; Run the control unit executes the general mode display process when the login of any of the registered users has not been accepted; In the second function execution process, even if the ID corresponding object is registered in the personal tab, if the login of the registered user is accepted and the personal tab is set as the personal home tab of the registered user, the control unit executes the function associated with the ID corresponding object. Function execution device.

3. 3. A function executing device according to claim 1, the control unit, in the second function execution process, executes a function associated with the ID-corresponding object when the ID-corresponding object satisfies a specific executable condition even if the ID-corresponding object is registered in the personal tab. Function execution device.

4. 4. A function executing device according to claim 3, the execution condition being that the function associated with the ID-associated object does not include a process of transmitting information to a device other than the function-executing device; Function execution device.

5. 5. A function executing device according to claim 3, further comprising: Each of the functional objects is set to either a first type object for which a user's input operation is required when a corresponding function is executed in the first function execution process, or a second type object for which a corresponding function is executed without a user's input operation in the first function execution process, the execution condition is that the ID-corresponding object is set to the second type object; Function execution device.

6. A function execution device according to any one of claims 3 to 5, In the second function execution process, even if the ID corresponding object is registered in the personal tab, if the ID corresponding object satisfies a specific executable condition, the control unit causes the display unit to display an execution confirmation screen for asking whether or not to execute a function associated with the ID corresponding object, and, after the confirmation screen is displayed, when a specific execution instruction indicating execution is input via the input unit, executes the function associated with the ID corresponding object. Function execution device.

7. A function execution device according to any one of claims 1 to 6, The control unit further executes a notification process of notifying information indicating that a function associated with the ID corresponding object cannot be executed when the ID corresponding object corresponding to the device ID acquired by the device ID acquisition process is registered in the personal tab. Function execution device.

8. A function execution device according to any one of claims 1 to 7, The control unit further an attribute setting process for setting the tab to the shared attribute or the personal attribute for each of the tabs; a setting confirmation display process for displaying a setting confirmation screen on the display unit to inquire whether or not to set the tab to the shared attribute when the tab is set to the personal attribute from the shared attribute by the attribute setting process and the functional object with the object ID registered therein is included in the tab set to the personal attribute; a sharing change receiving process for receiving, via the input unit, a sharing change request for requesting that the tab be set to the sharing attribute while the setting confirmation screen is being displayed; an attribute change process for setting the tab to the shared attribute when the sharing change request is accepted by the sharing change acceptance process; A function executing device that executes the function.

9. A function execution method for use in a function execution device capable of executing a function, comprising: the function executing device is configured to be able to execute 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 function execution method includes: a general mode display step of displaying a general mode standby screen including a shared tab which is a tab set to the shared attribute and not including a personal tab which is a tab set to the personal attribute among a plurality of tabs each set to a shared attribute or a personal attribute; having Each of the plurality of tabs is configured to allow a functional object, which is an image associated with a function to be executed, to be registered therein; The functional object is configured so that a specific object ID can be registered; the general mode standby screen includes one of the shared tabs in a selected state and the functional object registered in the selected shared tab, The function execution method further comprises: a first function executing step of executing a function associated with the selected functional object in response to the selection of the displayed functional object; a device ID acquisition step of acquiring the device ID from the wireless communication device through the wireless communication; a second function execution step executed in response to the device ID being acquired by the device ID acquisition step, the second function execution step executing a function associated with an ID corresponding object, which is a functional object in which an object ID having a specific correspondence with the acquired device ID is registered, when the ID corresponding object is registered in the shared tab, and not executing a function associated with the ID corresponding object when the ID corresponding object is registered in the personal tab; The method for performing a function includes:

10. A display unit; An input unit; The Communications Department and A control unit capable of executing processes according to a program; In a function execution device comprising: the communication unit is configured to be able to perform 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 function execution program causes the control unit to a general mode display process for displaying on the display unit a general mode standby screen including a shared tab that is a tab set to the shared attribute and not including a personal tab that is a tab set to the personal attribute among a plurality of tabs each set to a shared attribute or a personal attribute; Run the command, Each of the plurality of tabs is configured to allow a functional object, which is an image associated with a function to be executed, to be registered therein; The functional object is configured so that a specific object ID can be registered; the general mode standby screen includes one of the shared tabs in a selected state and the functional object registered in the selected shared tab, The function execution program further causes the control unit to a first function that executes a function associated with the selected functional object when the functional object displayed on the display unit is selected via the input unit; Function execution processing of a device ID acquisition process for acquiring the device ID from the wireless communication device through the wireless communication by the communication unit; a second function execution process that is executed in response to the device ID being acquired by the device ID acquisition process, and that executes a function associated with an ID corresponding object, which is a functional object in which an object ID having a specific correspondence with the acquired device ID is registered, when the ID corresponding object is registered in the shared tab, and does not execute a function associated with the ID corresponding object, when the ID corresponding object is registered in the personal tab; A function execution program that executes the function.

Images