Function execution device

Abstract

In a function execution device configured to allow specific functions to be executed not only by direct user operation but also via wireless communication with an external source, the execution of those specific functions can be appropriately restricted. [Solution] The function execution device 10 can communicate wirelessly with the wireless communication device 7 within the communication area. The function execution device 10 displays a tabbed screen, and each tab displays a function object to which a function is associated. Each tab is set to either a shared attribute or a personal attribute. When the function execution device 10 obtains the device ID from the wireless communication device 7 via wireless communication, it executes the function for which the object ID that has a specific correspondence with that device ID is registered. However, if that function is registered in the personal attribute tab, the function will not be executed.

Description

Technical Field

[0001] The present invention relates to a technique for executing a registered function according to a user's operation.

Background Art

[0002] Patent Document 1 below discloses an image processing apparatus configured to be able to execute a predetermined process (for example, a scan process) associated with a shortcut button only by causing a card to be read by a card reader without operating the shortcut button.

[0003] When the image processing apparatus disclosed in Patent Document 1 is shared by a plurality of users, it is convenient to be configured as follows, for example. That is, each of a plurality of shortcut buttons is arranged on one of a plurality of tab screens in tab form. The display unit selectively displays one of the plurality of tab screens. Each of the plurality of tabs is set to a shared attribute or a personal attribute. When a specific user is not logged in, only the tab with the shared attribute is displayed without displaying the tab with the personal attribute. The tab with the personal attribute is displayed only when the specific user corresponding to the tab is logged in.

[0004] By configuring the image processing apparatus 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, it becomes possible by arranging a shortcut button (hereinafter referred to as a "user-limited button") for which operation is to be allowed only to a specific user on a tab with a personal attribute corresponding to the specific user, or by setting the tab on which the user-limited button is arranged to a tab with a personal attribute corresponding to the specific user.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

[0006] However, if certain processes associated with user-restricted buttons can also be executed by having the aforementioned card read by a card reader, the following problems arise.

[0007] In other words, for example, suppose a shortcut button associated with a specific process that can be executed via a card is changed to a user-restricted button by changing the attribute of the tab on which that shortcut button is located to a personal attribute corresponding to that specific user. In this case, since the user-restricted button will no longer be displayed unless that specific user is logged in, it is possible to prevent unspecified users other than that specific user from operating that user-restricted button.

[0008] However, even if the user-restricted button is not displayed and the user cannot operate it, if they have the card, any unspecified user can use that card to execute the specific action associated with that user-restricted button.

[0009] This invention has been made in view of the above problems, and provides a specific function that can be directly operated by the user. In addition to the above, the objective is to enable appropriate restriction of the execution of a specific function in a function execution device that is configured to also be able to perform actions via wireless communication with an external source. [Means for solving the problem]

[0010] The functional execution device of the present invention comprises 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 when a wireless communication device having a specific device ID is located within a communication area.

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

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

[0013] The control unit further executes a first function execution process, a device ID acquisition process, and a second function execution process. The first function execution process is the process of executing the function associated with the selected function object when a function object displayed on the display unit is selected via the input unit.

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

[0015] In a function execution device configured in this way, even if a device ID corresponding to an ID-corresponding object is obtained, if that ID-corresponding object is registered in the personal tab, the function corresponding to that ID-corresponding object will not be executed. Therefore, by registering the ID-corresponding object in the personal tab, it becomes possible to appropriately restrict the execution of the function corresponding to that ID-corresponding object. [Brief explanation of the drawing]

[0016] [Figure 1] This is an explanatory diagram showing the schematic configuration of an information processing system according to an embodiment. [Figure 2] This is an explanatory diagram showing an example of a waiting screen when the user is not logged in and all tabs are set to the shared attribute. [Figure 3] This is an explanatory diagram showing the icon data table. [Figure 4] (a) is an explanatory diagram showing the tab settings table, and (b) is an explanatory diagram showing the tab attribute settings screen. [Figure 5] This is an explanatory diagram showing the user management data table. [Figure 6] (a) is an explanatory diagram showing an example of screen transitions when attempting to launch a card launch shortcut registered in the Personal tab from an NFC card in General Mode, and (b) is an explanatory diagram showing an example of screen transitions when attempting to launch a card launch shortcut registered in the Personal tab (however, the Home tab of the logged-in user) from an NFC card in Personal Mode. [Figure 7] This diagram illustrates an example of screen transitions when attempting to launch a card launch shortcut registered in the Personal tab and not performing external access from an NFC card while in general mode. [Figure 8] This is an explanatory diagram showing an example of screen transitions when the attribute of a tab containing a registered card launch shortcut is changed from shared to personal. [Figure 9] This is a flowchart of the main process. [Figure 10]It is a flowchart showing the access rightless handling process of S210 in the main process of FIG. 9. [Figure 11] It is a flowchart showing the tab setting change confirmation process of S240 in the main process of FIG. 9.

Embodiments of the Invention

[0017] Hereinafter, embodiments 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 apparatus 10 and an information processing apparatus 20. The image processing apparatus 10 and the information processing apparatus 20 can communicate with each other via a network 3. The network 3 may be any network. The network 3 may be, for example, a wired network or a wireless network. Also, in either the wired or wireless case, the specific communication method may be any communication method.

[0018] (2) Configuration of the Image Processing Apparatus The image processing apparatus 10 has a plurality of functions such as, for example, a scan function, a print function, a copy function, and a fax function. The scan function is a function of reading an image of a document and generating image data of the read image. The print function is a function of printing an image on a sheet-like recording paper. The copy function is a function of printing the 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 apparatus 10 includes a control unit 11, a storage 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, and these are connected to each other via a bus 5.

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

[0021] The control unit 11 implements various functions by executing a program stored in a non-transitional tangible recording medium. In this embodiment, the storage unit 12 corresponds to the non-transitional tangible recording medium storing the program. It should be noted that the various functions implemented by the control unit 11 are not limited to implementation by program execution (i.e., software processing), and some or all of them may be implemented using one or more hardware components.

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

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

[0024] The touch panel 14a, which is superimposed on the image display area of ​​the display unit 13, can detect instruction operations performed by touch or proximity of an indicator to the image display area. That is, when an instruction operation is performed on the image display area by an indicator, the touch panel 14a is configured to output position information indicating the instruction position, which is the location where the instruction operation is being performed. The touch panel 14a in this embodiment is configured to output position information continuously or periodically while an instruction operation is being performed by an indicator.

[0025] The touch panel 14a may be configured to detect only contact as an instruction operation, or to detect only proximity, or to detect 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 an instruction operation has been performed on the indicator, the position of the instruction if an instruction operation has been performed, and at least one specific operation performed on the indicator if an instruction operation has been performed.

[0027] Specific operations that the control unit 11 can detect include, for example, tap operations, flick operations, and drag operations. A tap operation is an operation in which an instruction is made by an instruction object, and then the instruction object is lifted from the same position. Various specific forms of the instruction object capable of performing an instruction operation are conceivable, and may be, for example, a fingertip or a specific instruction device such as a stylus pen.

[0028] The reading unit 15 is equipped with an image sensor and reads the image on the document in which the image is recorded, 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 that uses inkjet technology or electrophotographic technology, and is capable of printing images on sheet-like recording paper. The short-range wireless communication unit 17 communicates wirelessly with other wireless communication devices located near the image processing device 10 using a specific wireless communication method. The specific wireless communication method can be any wireless communication method; in this embodiment, for example, it is 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 communicate wirelessly with other wireless communication devices located within its communication area. The communication area may be, for example, an area within a predetermined distance (e.g., several tens of centimeters) from a predetermined proximity surface on the surface of the housing of the image processing device 10 near the location where the short-range wireless communication unit 17 is mounted.

[0031] Other wireless communication devices that the short-range wireless communication unit 17 can wirelessly communicate include the NFC card 7 shown in Figure 1. The NFC card 7 is a rectangular, thin card. Inside the NFC card 7 are an antenna 7a, a communication circuit 7b, and a storage unit 7c. The device performs wireless communication based on the NFC communication standard via antenna 7a. The memory unit 7c stores the unique card ID of the NFC card 7. The communication circuit 7b is configured to wirelessly transmit the card ID stored in the memory unit 7c to an external source.

[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 near-field wireless communication unit 17 of the image processing device 10 are in a position where wireless communication is possible, wireless communication is performed between the near-field wireless communication unit 17 and the NFC card 7 (specifically the communication circuit 7b) according to 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 obtains the card ID via the near-field 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 communicate data via wired or wireless means 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 connect to the internet via the first communication unit 18 and communicate data with other various servers and various information processing devices via the internet.

[0034] 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. 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 diagram, the image processing device 10 is equipped with a media interface. Various storage media, such as a USB flash memory, can be detachably attached to the media interface. The media interface controls the 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 various types of information processing terminals, such as a personal computer, tablet terminal, or smartphone. As shown in Figure 1, the information processing device 20 comprises a control unit 21, a storage unit 22, an input unit 23, a display unit 24, and a communication unit 25.

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

[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 input devices for receiving various input operations. These input devices include, for example, a keyboard, mouse, and touch panel. The touch panel is superimposed on the image display area of ​​the display device of the display unit 24.

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

[0040] (4) Explanation of the waiting screen Next, the standby screen 40, in particular, among the various screens displayed on the display unit 13 of the image processing device 10, will be explained with reference to Figure 2. When the control unit 11 of the image processing device 10 is started up, it performs predetermined initial processing and then displays the standby screen 40 shown in Figure 2 on the display unit 13.

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

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

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

[0044] In this embodiment, the arrangement direction of each tab in the standby screen 40 is to the right. That is, each tab is arranged sequentially to the right. The arrangement order of each tab in the above arrangement direction is basically the order according to the predetermined order described later, i.e., the ascending order in the predetermined order.

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

[0046] On the standby screen 40, left button 38 and right button 39 are displayed near both ends of the area where the tabs are displayed. If there are five or more tabs and four of them are displayed, selecting either the left button 38 or the right button 39 will scroll the selected tab to the left or right, thereby displaying the tabs that are not currently displayed. Note that the selection operation can be any operation; in this embodiment, for example, it is a tap operation.

[0047] To switch from the currently selected tab's tab screen to another tab's tab screen, simply select the desired tab. When you select a tab other than the currently selected one, that tab becomes selected, and the standby screen 40 displays the tab screen corresponding to the newly selected tab. For example, as shown on the left of Figure 2, if the first tab 31 is selected, and you select the third tab 33, as shown on the right of Figure 2, the third tab 33 becomes selected, and the standby screen 40 displays the third tab screen 60 corresponding to the third tab 33. Conversely, in the standby screen 40 shown on the right of Figure 2, if you select the first tab 31, as shown on the left of Figure 2, the first tab 31 becomes selected, and the standby screen 40 displays the first tab screen 50 corresponding to the first tab 31.

[0048] Information necessary to display the standby screen 40, as well as information regarding the processing to be performed when various input operations are performed on the standby screen 40 via the input unit 14, are stored in the storage unit 12.

[0049] Each tab has multiple icons registered, 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 in each tab screen.

[0050] Specifically, as shown on the left of Figure 2, the first tab screen 50, corresponding to the first tab 31, displays the first icons 51 to 8th icons 58 registered in the first tab 31. As shown on the right of Figure 2, the third tab screen 60, corresponding to the third tab 33, displays the 17th icons 61 to 24th icons 68 registered in the third tab 33. Each icon includes its name. The specific type of each icon can be changed.

[0051] Each icon is associated with a specific function. When a user selects an icon, the specific function associated with that icon is executed.

[0052] In the first tab screen 50 illustrated on the left of Figure 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 to which no specific function is associated. Users can associate specific functions with these unregistered icons by registering those functions. The explanation for the fifth icon 55 to the seventh icon 57 is omitted.

[0053] In the third tab screen 60 illustrated on the right of Figure 2, for example, icon 17 61 is associated with a specific function in the copy function, icons 18 62 and 19 63 are associated with specific functions in the fax function, and icons 20 64 and 21 65 are associated with specific functions in the scan function. Icons 22 66 to 24 68 are unregistered icons.

[0054] The specific functions associated with icons 17 (61) through 21 (65) on the third tab screen (60) are all shortcut functions. Shortcut functions are functions that can be registered arbitrarily by the user. Shortcut functions are configured to execute specific functions according to pre-set settings. Users can register shortcut functions to unregistered icons by performing a prescribed shortcut registration operation on those unregistered icons. At that time, the name of the shortcut function can also be arbitrarily set. Users can also change the content of already registered shortcut functions or unregister them and return them to unregistered icons. Icons to which shortcut functions are associated will hereafter be referred to as shortcut icons.

[0055] In this embodiment, the shortcut function is further classified into two types: a normal shortcut function and a one-touch shortcut function. A normal shortcut function is configured such that when the corresponding shortcut icon is selected, the registered shortcut function is not immediately started, but rather at least one further input operation is required from the user.

[0056] In this embodiment, when a shortcut icon corresponding to a shortcut function is selected, a predetermined confirmation screen is displayed. The user can check or change the settings of the shortcut function through this 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 the corresponding shortcut icon is selected, the registered shortcut function is started and completed without requiring any further input from the user.

[0058] As shown on the right in Figure 2, in the standby screen 40, shortcut icons are usually marked with either a mark 46 or a one-touch mark 47. Icons 17 (61), 19 (63), and 20 (64), which are marked with a mark 46, are shortcut icons associated with the normal shortcut function. Icons 18 (62) and 21 (65), which are marked with a one-touch mark 47, are shortcut icons associated with the one-touch shortcut function.

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

[0060] Furthermore, by performing a specific card registration operation, users can register their card ID to any shortcut icon, that is, to the shortcut function corresponding to that shortcut icon. A shortcut function to which a card ID is registered will be referred to below as a card activation shortcut.

[0061] The card registration operation can be performed in any way. For example, the card ID may be registered by the user manually entering the card ID via the input unit 14. Alternatively, for example, the card ID may be automatically read and registered via wireless communication by holding the NFC card 7 over the image processing device 10.

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

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

[0064] In the example in Figure 3, card ID "87654321" is registered in icon 61, 17th in tab 33, and card ID "12345678" is registered in icon 63, 19th in 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 the tab setting table shown in Figure 4(a). The tab setting table lists Nt tabs (for example, 8 in this embodiment) in a predetermined order. In this embodiment, the predetermined order is, for example, the order of the first tab to the eighth tab, as shown in Figure 4(a).

[0066] Each tab is assigned an attribute. In this embodiment, the attribute is set to either shared or personal. The attribute of a tab can be arbitrarily changed for each tab. Figure 4(a) shows an example where the attribute of the first tab 31 is set to shared, and the attributes of the other tabs are set to personal. ru.

[0067] Additionally, each tab is assigned a tab name. The tab name is displayed on each tab when it appears on the standby screen 40. The tab name can be changed for each tab as desired. The tab settings table, the aforementioned icon data table (see Figure 3), and the user management data table (see Figure 5), described later, may be pre-stored in the storage unit 12 of the image processing device 10, for example. In this case, the user may be able to arbitrarily customize each table stored in the storage unit 12 of the image processing device 10.

[0068] Furthermore, 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 arbitrary customization of each table. When the image processing device 10 is started, the control unit 11 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 the stored tables. 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.

[0069] An example of how to change tab attributes will be explained with reference to Figure 4(b). When a specific operation to change tab attributes is performed in the information processing device 20, the tab attribute setting screen 8 shown in Figure 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 radio buttons for "shared" and "personal" are displayed for each tab. The user can change the tab attributes as they wish by selecting either radio button. Alternatively, the tab attribute setting screen 8 shown in Figure 4(b) or a similar screen may be displayed on the image processing device 10 so that the tab attributes can be changed on the image processing device 10.

[0070] Note that the standby screen 40 shown in Figure 2 shows an example where the first tab 31 to the fourth tab 34 all have shared attributes. On the other hand, the standby screens 40 shown in Figures 6 and 7 show a standby screen based on the tab setting table in Figure 4(a), that is, an example where the first tab 31 has shared attributes and all other tabs have personal attributes. The standby screen 40 shown on the left of Figure 8 shows an example where the first tab 31 and the third tab 33 have shared attributes and all other tabs have personal attributes. The standby screen 40 shown on the lower right of Figure 8 shows an example where the first tab 31 has shared attributes and all other tabs have personal attributes.

[0071] Furthermore, in the image processing device 10, the user mode can be set to either general mode or personal mode. Personal mode is set when one of the pre-registered users (hereinafter referred to as "registered user") 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. General mode is the user mode when no registered user is logged in. In other words, general mode is a user mode that can be set by all users without requiring authentication processing such as password input.

[0072] Registered users can be registered directly in the image processing device 10 or indirectly through an external device such as the information processing device 20. For example, the information processing device 20 manages the user management data table shown in Figure 5. Registered users are registered in the user management data table. In addition, it is possible to register a personal home tab for each registered user in the user management data table. When the information processing device 20 performs the registration process for a registered user, that registered user is added to the user management data table. Furthermore, a personal home tab can be optionally registered for that registered user.

[0073] The user management data table shown in Figure 5 illustrates a scenario where eight users, User 01 to User 08, are registered as registered users. It also shows an example where User 01 has the first tab registered as their personal home tab, User 02 has the second tab registered as their personal home tab, User 03 has the third tab registered as their personal home tab, User 04 has the fourth tab registered as their personal home tab, while Users 05 to User 08 do not have any personal home tabs registered. Personal home tabs can be of either shared or personal attributes.

[0074] A registered user logs in by performing a predetermined authentication process, which includes, for example, the input of user authentication information specific to the registered user (e.g., a password) via the input unit 14.

[0075] The tabs displayed on the waiting 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 waiting screen 40 differ depending on which registered user is logged in.

[0076] As shown in Figure 2, the standby screen 40 displays a user switching interface 45. The user switching interface 45 is an image that the user selects (e.g., by tapping) in order to switch user modes.

[0077] The user switching interface 45 displays information indicating the current user mode. In this embodiment, when the user mode is set to general mode, the user switching interface 45 displays the text "General" to indicate that it is general mode, as shown in Figures 2, 6(a), 7, and 8. When the user mode is set to personal mode, the user switching interface 45 displays text indicating the logged-in user, as illustrated in Figure 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 "General Mode" and each registered user as options. When "General Mode" is selected, the user mode is set to "General Mode".

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

[0080] Therefore, for example, if all tabs have shared attributes, the standby screen 40 in general mode will display all tabs (however, a maximum of 4 tabs can be displayed at the same time), as shown in Figure 2. Also, for example, if only the first tab 31 has shared attributes, the standby screen 40 in general mode will display the first tab 31, as illustrated in Figures 6(a) and 7.

[0081] On the other hand, when a registered user is selected on the user mode selection screen, an authentication screen (not shown) is displayed for authentication processing. When the correct user authentication information corresponding to the selected registered user is entered via this authentication screen, 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 personal mode, the personal home tab of the corresponding registered user is retrieved from the user management data table (see Figure 5), and that personal home tab is displayed on the waiting screen 40. For example, when user 03 logs in, the waiting screen 40 will display the user's home tab as shown in Figure 6(b). The third tab 33, which is the personal home tab of the 03, is displayed. In this embodiment, in personal mode, personal attribute tabs other than the logged-in user's personal home tab are not displayed, and tabs with the attribute "shared" are not displayed unless they are the logged-in user's personal home tab. However, in personal mode, in addition to the logged-in user's personal home tab, tabs with shared attributes may also be displayed.

[0083] (5) Function execution via NFC card Next, we will explain an example of the screen transitions when you hold NFC card 7 over the reader to execute the card activation shortcut.

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

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

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

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

[0088] Thus, 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 attributes tab, the card launch shortcut will generally not be executed unless a registered user who has the tab where the card launch shortcut is registered as their personal home tab is logged in.

[0089] However, in this embodiment, when an NFC card 7 is held over a device, even if the corresponding card launch shortcut is registered in the Personal Attributes tab and the registered user who has designated that tab as their 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 feasibility conditions are, for example, condition A and condition B. Furthermore, if at least one of condition A and condition B is met, it is determined that a specific feasibility condition has been met.

[0091] Condition A is that the card launch shortcut is a function that does not include the 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 icon 19 63, does not satisfy condition A. On the other hand, a card launch shortcut corresponding to icon 17 61, for example, is a function that prints the image of a document scanned by the image processing device 10 using the image processing device 10, and does not include the process of transmitting information outside the image processing device 10, so it satisfies condition A.

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

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

[0094] The NFC card activation confirmation screen 75 asks the user whether or not 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 confirmation message 76 differs depending on whether condition A or condition B is met. In other words, the content of confirmation message 76 corresponds to the condition that was met. Figure 7 shows an example where confirmation message 76 corresponding to condition A is displayed because condition A was met.

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

[0097] Subsequently, when the same NFC card 7 is held over the device again, the corresponding card activation shortcut is executed because the card activation permission flag for that shortcut is set to ON. During execution, the execution screen 80 is displayed as shown in Figure 7.

[0098] The card activation permission flag may be set to off again at a specific time, or once set to on, it may remain on permanently unless a specific flag initialization process is performed. If the card activation permission flag is set to off again at a specific time, that specific time can be anything. For example, it may be set to off after the card activation shortcut has been executed a certain number of times. Or, for example, after being set to on, it may remain on for a certain period of time. It may be set to off after a certain amount of time has passed.

[0099] Next, we will explain an example of screen transitions when the attribute of the tab where the card launch shortcut is registered is changed from shared to personal, referring to Figure 8. First, let's assume that the first tab 31 and the third tab 33 are set to shared attributes and the user mode is set to general mode. In this case, a waiting screen 40 is displayed, which includes the first tab 31 and the third tab 33, with one of them (for example, the first tab 31 in Figure 8) selected, as shown on the left of Figure 8. Here, the third tab 33 has a card launch shortcut registered, as shown in Figures 3 and 6(b).

[0100] In this state, if the attribute of the third tab 33 is changed from shared to personal, the personalization cancellation confirmation screen 85 shown in Figure 8 will be displayed on the display unit 13 after the change. The personalization cancellation confirmation screen 85 is a screen that asks the user whether or not to change the tab that has been changed to the personal attribute back to the shared attribute. The personalization cancellation confirmation screen 85 displays a confirmation message 86, an OK button 87, and a NO button 88. The confirmation message 86 is a message that informs the user that a card launch shortcut is registered to the tab that has been changed to the personal attribute, and asks the user whether or not to set that tab back to the shared attribute.

[0101] On the personalization deactivation confirmation screen 85, if the NO button 88 is selected, the tabs that have been changed to personal attributes remain as personal attributes. The display unit 13 then displays the standby screen 40 shown in the lower right of Figure 8, that is, the standby screen 40 showing only the first tab 31, which is the only shared tab. On the other hand, if 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 tabs 31 and 33, as shown on the left of Figure 8.

[0102] (6) Main processing Next, the main processing performed by the control unit 11 will be explained with reference to Figures 9 to 11. After startup, the control unit 11 (more specifically the CPU) performs predetermined initial processing, and then executes the main processing according to the main processing program shown in Figures 9 to 11 stored in the memory unit 12. The various screen transitions described above are realized by the control unit 11 executing the main processing.

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

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

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

[0106] If no other events occur, the process proceeds to S110. If other events occur, S230 executes the processing corresponding to the event. For example, if an icon is selected, the function corresponding to that icon is executed.

[0107] In S240, the tab setting change confirmation process is executed. Details of the tab setting change confirmation process are shown in Figure 11. Upon proceeding to the tab setting change confirmation process, S410 determines whether the tab settings have been changed by the process in S230, or in other words, whether any process has been performed that changes the contents of the tab setting change table shown in Figure 4(a). If the tab settings have not been changed, the process proceeds to S110 (Figure 9). If the tab settings have been changed, the process proceeds to S420.

[0108] In S420, the system searches for the card launch shortcut in the icon data table (see Figure 3). In S430, it determines whether or not the card launch shortcut exists. If the card launch shortcut does not exist, the system proceeds to S110 (Figure 9). If the card launch shortcut exists, the system proceeds to S440.

[0109] In S440, it is determined whether the attribute of the tab where the card launch shortcut is registered is shared or not. If it is shared, it proceeds to S110 (Figure 9); if it is personal, it proceeds to S450.

[0110] In S450, a personal warning process is performed. Specifically, the personal deactivation confirmation screen 85, as illustrated in Figure 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 it has not been selected, the process proceeds to S450; if it has been selected, the process proceeds to S110 (Figure 9). In S460, if the OK button 87 has been selected, the shared restoration process is performed in S470. Specifically, the tab of the personal attribute where the card launch shortcut is registered is set to the shared attribute. After the processing in S470, the process proceeds to S110 (Figure 9).

[0111] Returning to Figure 9, if it is determined in S120 that the NFC card 7 has been held over the reader, the process proceeds to S130. In S130, the card ID of the NFC card 7 that was held over the reader is obtained via the near-field communication unit 17. In S140, the icon data table is referenced to search for the card activation shortcut to which the obtained card ID is registered.

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

[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 in which the corresponding card launch shortcut is registered, is shared. If it is shared, the card launch shortcut is executed in S180. While it is running, the execution screen (see Figures 6, 7, etc.) is displayed.

[0114] If the tab to which the relevant card launch shortcut belongs is Personal, it will be migrated to S190. In S190, the tab to which the relevant card launch shortcut belongs is currently Logged In Determine whether it is the personal home tab of the logged-in user. If it is the logged-in user's personal home tab, execute the card launch shortcut on S180. If it is not the logged-in user's home tab, proceed to S200.

[0115] S200 determines whether the card launch permission flag for the relevant card launch shortcut is set to "on". If the card launch permission flag is set to "on", S180 executes that card launch shortcut. As mentioned above, there are various possible timings for setting the card launch permission flag to "off" after executing the card launch shortcut due to the flag being set to "on".

[0116] If the card launch permission flag is set to off in S200, the access denied handling process is executed in S210. Details of the access denied handling process in S210 are shown in Figure 10. When the process moves to the access denied handling process, S310 determines whether the relevant card launch shortcut meets specific execution conditions. Specifically, it determines whether at least one of the aforementioned conditions A and B is met. If the specific execution conditions are not met, S320 displays the access denied notification screen 70 (see Figure 6) for a certain period of time, and then proceeds to S110.

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

[0118] If the OK button 77 is selected in S340, the card activation permission flag for the corresponding card activation shortcut is changed to ON in S350, and the process proceeds to S110. This flag change ensures that the next time the same NFC card 7 is held over the reader, S200 will confirm the transaction and the card activation shortcut will be executed.

[0119] (7) Effects of the embodiment The embodiments described above provide the following effects. In other words, in the image processing device 10 of this embodiment, even if an NFC card 7 having a card ID corresponding to a registered card activation shortcut is held over the device, if that card activation shortcut is registered in the personal attributes tab, the card activation shortcut will not be executed. Therefore, it is possible to appropriately restrict the execution of card activation shortcuts.

[0120] For example, if a card launch shortcut is registered in the shared attributes tab, it is possible to restrict the use of that card launch shortcut by changing the attribute of the tab to which the card launch shortcut is registered to "personal," thereby restricting the execution of that card launch shortcut both by icon operation and by using the NFC card 7.

[0121] Furthermore, in this embodiment, even if a card launch shortcut is registered in the Personal Attributes tab, if that tab is the personal home tab of the logged-in user, the card launch shortcut can be executed by holding the NFC card 7 over it.

[0122] Furthermore, in this embodiment, even if the card launch shortcut is registered in the Personal Attributes tab, it will be executed if certain execution conditions are met. Dynamic shortcuts can be appropriately restricted according to the content of the card launch 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 fact that the card ID obtained from the NFC card 7 matches the card ID registered in the card activation shortcut corresponds to an example of a specific correspondence. 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 (Figure 7) corresponds to an example of an execution confirmation screen. The personal unlock confirmation screen 85 (Figure 8) corresponds to an example of a setting confirmation screen. Selecting the OK button 87 on the personal unlock confirmation screen 85 corresponds to an example of a shared change request.

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

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

[0126] (1) In the above embodiment, it was possible to register the card ID for the shortcut function, but it is also possible to register the card ID for functions other than the shortcut function and activate them from the NFC card 7.

[0127] (2) In the main process, the process using the card activation permission flag may be omitted. Specifically, in the access permission denied process in Figure 10, if the OK button 77 is selected in S340, the process may proceed to S180 and execute the card activation shortcut.

[0128] Furthermore, if S310 determines that the relevant card launch shortcut meets certain execution conditions, the card launch shortcut may be executed in S180 without proceeding to the processing in S330 and beyond.

[0129] (3) Processing similar to the tab setting change confirmation process of S240 may be performed during the operation to change the tab settings, rather than after the tab settings have been changed. For example, if an operation is performed to change the attribute of a tab 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 to be changed to personal, and information about that card launch shortcut. Then, if an operation is performed on that screen to indicate 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 item is not shared (i.e., personal), the following actions may be taken: Information indicating that a card launch shortcut is registered may be displayed in the Personal Attributes tab, and a screen may be displayed asking the user whether they want to delete the card launch shortcut. If the user indicates that they want to delete it, the registration of the card launch shortcut may be deleted.

[0131] (5) In the above embodiment, when the NFC card 7 was held over the reader, a card activation shortcut was executed that had a registered card ID matching the card ID obtained from the NFC card 7. However, the information registered in the card activation 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 that object ID may be linked to a specific card ID. Then, when the NFC card 7 is held over the reader, if the card ID obtained from the NFC card 7 is the card ID linked to the object ID, the card activation shortcut that has that object ID registered may be executed.

[0132] (6) The present invention is not limited to application to the image processing apparatus 10 shown in Figure 1. The present invention is applicable to any functional execution device equipped with wireless communication capabilities and configured to perform various functions.

[0133] Furthermore, the wireless communication device that the function execution device of the present invention can wirelessly communicate with is not limited to the NFC card 7 shown in the above embodiment. The function execution device of the present invention may be able to wirelessly communicate with various wireless communication devices having a specific device ID. Also, the communication method with the wireless communication device is not limited to NFC.

[0134] (7) Multiple functions of one component in the above embodiment may be realized by multiple components, or one function of one component may be realized by multiple components. Also, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, some of the configurations of the above embodiment may be omitted. Furthermore, at least some of the configurations of the above embodiment may be added to or replaced with the configurations of other above embodiments. [Explanation of symbols]

[0135] 1...Information processing system, 7...NFC card, 7a...Antenna, 7b...Communication circuit, 7c...Storage unit, 10...Image processing unit, 11...Control unit, 12...Storage unit, 13...Display unit, 14...Input unit, 17...Short-range wireless communication unit, 20...Information processing unit, 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 Icons: 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 permission notification screen, 75...NFC card activation confirmation screen, 85...Personalization deactivation confirmation screen.

Claims

1. Display unit and Input section, Communications Department and, Control unit and A functional execution device equipped with, The communication unit is configured to perform wireless communication with a wireless communication device having a specific device ID, depending on whether the wireless communication device is located within the communication area. The control unit, A general mode display process that displays a general mode standby screen on the display unit, which includes a shared tab (a tab set to the shared attribute) and does not include a personal tab (a tab set to the personal attribute), among multiple tabs, each set to either the shared attribute or the personal attribute. Execute, Each of the aforementioned tabs is configured such that a function object, which is an image associated with the function to be executed, can be registered. The aforementioned functional object is configured such that a specific object ID can be registered, The general mode standby screen includes one of the shared tabs selected and the functional objects registered in the selected shared tab. The control unit further, A first function execution process executes the function associated with the selected function object when the function object displayed on the display unit is selected via the input unit. A device ID acquisition process that acquires the device ID from the wireless communication device via the wireless communication by the communication unit, A second function execution process to be performed in response to the acquisition of the device ID by the device ID acquisition process, wherein if an ID-corresponding object, which is a function object to which the object ID having a specific correspondence relationship with the acquired device ID is registered, is registered in the shared tab, the function associated with that ID-corresponding object is executed; and if the ID-corresponding object is registered in the personal tab, the function associated with that ID-corresponding object is not executed. A function execution device that performs the necessary actions.

2. A function execution device according to claim 1, The control unit further, A login acceptance process that accepts logins from pre-registered users, A personal home tab setting process that individually sets one of the multiple tabs as the personal home tab for each registered user, When the login of the registered user is accepted by the login acceptance process, the display unit is made to display a personal mode standby screen that includes at least the personal home tab set for the registered user, but does not include any personal tabs other than the personal home tab. Execute, The control unit executes the general mode display process if none of the registered users have been accepted for login. In the second function execution process, the control unit executes the function associated with the ID-corresponding object if the ID-corresponding object is registered in the personal tab, and the registered user's login has been accepted and the personal tab is set as the registered user's personal home tab. Function execution device.

3. A function execution device according to claim 1 or claim 2, In the second function execution process, the control unit executes the function associated with the ID-corresponding object if the ID-corresponding object satisfies specific execution conditions, even if the ID-corresponding object is registered in the personal tab. Function execution device.

4. A function execution device according to claim 3, The aforementioned executable condition is that the function associated with the ID-corresponding object does not include the process of transmitting information to a device other than the function execution device. Function execution device.

5. A function execution device according to claim 3 or claim 4, Each of the aforementioned functional objects is set to either a first-type object that requires user input when the corresponding function is executed in the first functional execution process, or a second-type object that executes the corresponding function without requiring user input in the first functional execution process. The execution condition is that the ID-corresponding object is set as 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, the control unit, even if the ID-corresponding object is registered in the personal tab, displays an execution confirmation screen on the display unit to ask whether to execute the function associated with the ID-corresponding object if the ID-corresponding object satisfies specific execution conditions, and executes the function associated with the ID-corresponding object if a specific execution instruction indicating execution is input via the input unit after the display of the confirmation screen. 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 to notify information indicating that the function associated with the ID-corresponding object cannot be executed if the ID-corresponding object corresponding to the device ID obtained 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, For each of the aforementioned tabs, an attribute setting process is performed to set the tab as the shared attribute or the personal attribute, If the tab is set from the shared attribute to the personal attribute by the attribute setting process, and the tab set to the personal attribute contains the function object for which the object ID is registered, a setting confirmation display process is performed to display a setting confirmation screen on the display unit to ask whether or not to set the tab to the shared attribute. While the aforementioned settings confirmation screen is displayed, a sharing change request is received via the input unit, which requests that the tab be set to the sharing attribute. When the shared change request is received by the shared change acceptance process, an attribute change process is performed to set the tab to the shared attribute, A function execution device that performs the following actions.

9. A method for executing a function used in a function execution device capable of performing a function, The aforementioned function execution device is configured to perform wireless communication with the wireless communication device, depending on the location of the wireless communication device having a specific device ID within the communication area. The aforementioned method of executing the function is: A general mode display step that displays a general mode standby screen, which includes a shared tab (a tab set to the shared attribute) and does not include a personal tab (a tab set to the personal attribute), among multiple tabs, each set to either the shared attribute or the personal attribute. It has, Each of the aforementioned tabs is configured such that a function object, which is an image associated with the function to be executed, can be registered. The aforementioned functional object is configured such that a specific object ID can be registered, The general mode standby screen includes one of the shared tabs selected and the functional objects registered in the selected shared tab. The aforementioned method of executing the function further includes: A first function execution step, in which a function associated with the selected function object is executed when the displayed function object is selected, A device ID acquisition step of acquiring the device ID from the wireless communication device via the wireless communication, A second function execution step to be performed in response to the acquisition of the device ID by the device ID acquisition step, wherein if an ID-corresponding object, which is a function object to which the object ID having a specific correspondence relationship with the acquired device ID is registered, is registered in the shared tab, the function associated with that ID-corresponding object is executed; and if the ID-corresponding object is registered in the personal tab, the function associated with that ID-corresponding object is not executed. A method for executing a function, having the following characteristics.

10. Display unit and Input section, Communications Department and, A control unit capable of executing processing according to a program, In a function execution device equipped with the above, a function execution program that can be executed by the control unit, The communication unit is configured to perform wireless communication with a wireless communication device having a specific device ID, depending on whether the wireless communication device is located within the communication area. The function execution program is provided to the control unit, A general mode display process that displays a general mode standby screen on the display unit, which includes a shared tab (a tab set to the shared attribute) and does not include a personal tab (a tab set to the personal attribute), among multiple tabs, each set to either the shared attribute or the personal attribute. Make it run, Each of the aforementioned tabs is configured such that a function object, which is an image associated with the function to be executed, can be registered. The aforementioned functional object is configured such that a specific object ID can be registered, The general mode standby screen includes one of the shared tabs selected and the functional objects registered in the selected shared tab. The function execution program further includes the control unit, When a function object displayed on the display unit is selected via the input unit, the first unit executes the function associated with the selected function object. The function execution process and A device ID acquisition process that acquires the device ID from the wireless communication device via the wireless communication by the communication unit, A second function execution process to be performed in response to the acquisition of the device ID by the device ID acquisition process, wherein if an ID-corresponding object, which is a function object to which the object ID having a specific correspondence relationship with the acquired device ID is registered, is registered in the shared tab, the function associated with that ID-corresponding object is executed; and if the ID-corresponding object is registered in the personal tab, the function associated with that ID-corresponding object is not executed. A program that executes a function.

Images