Management device, management method, and program

Abstract

Provided is a management device 100 for managing a timing of disposing of a user interface, the management device 100 comprising a settings information database 122 that stores settings information on the timing, an operation detection unit 111 that detects an operation of the user interface to generate operation detection information, an operation history information database 121 that stores operation history information on the history of operations, and a management unit 112 that determines whether or not to dispose of the user interface on the basis of the settings information, the operation detection information, and the operation history information.

Description

[Technical field]

[0001] The present disclosure relates to a management device, a management method, and a program. [Background technology]

[0002] In order to prevent the spread of infectious diseases, it is important that private spaces are not contaminated. When you go out and touch public facilities, if you then touch your smartphone or earphones with your hands, your private space may become contaminated through these.

[0003] For example, Patent Document 1 discloses a technology that allows a user to operate a terminal without directly touching the terminal by utilizing a user interface equipped with a pressure-sensitive input unit in which a conductive polymer and a binder resin are coated on a fiber or fabric. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2014-228959 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, when using a user interface such as that disclosed in Patent Document 1, the user must wash the user interface appropriately at the right time. Therefore, a method of always keeping the user interface clean by disposing of it like a mask every time it is used is conceivable. However, in this method, the user must remember whether or not the user interface has been used, that is, whether or not the user interface to be used is clean. If the user forgets this, it is assumed that the user will mistakenly throw away the unused user interface, or forget to dispose of it after use. In other words, there has been a demand for disposing of the user interface at an appropriate time so that the user can always touch a clean user interface.

[0006] In view of the above circumstances, an object of the present disclosure is to provide a management device, a management method, and a program that are capable of appropriately managing the timing of disposing of a user interface. [Means for solving the problem]

[0007] A management device according to one embodiment is a management device that manages the timing of disposing of a user interface, and is characterized in that it comprises a setting information database that stores setting information regarding the timing, an operation detection unit that detects operations on the user interface and generates operation detection information, an operation history information database that stores operation history information regarding a history of the operations, and a management unit that determines whether or not to dispose of the user interface based on the setting information, the operation detection information, and the operation history information.

[0008] A management method according to one embodiment is a management method for managing the timing of disposing of a user interface, and is characterized by including the steps of: storing setting information regarding the timing; detecting the position of the user interface and generating position detection information; storing position history information regarding the history of the position; and determining whether or not to dispose of the user interface based on the setting information, the position detection information, and the position history information.

[0009] A program according to one embodiment causes a computer to function as the management device. Effect of the Invention

[0010] According to the present disclosure, it is possible to provide a management device, a management method, and a program capable of appropriately managing the timing of disposing of a user interface. [Brief description of the drawings]

[0011] [Figure 1] FIG. 2 is a diagram illustrating an example of a configuration of a management device according to the first embodiment. [Diagram 2] FIG. 4 is a diagram showing an example of each piece of data according to the first embodiment. [Diagram 3] FIG. 4 is a diagram showing an example of each piece of data according to the first embodiment. [Figure 4] 4 is a flowchart showing an example of a management method according to the first embodiment. [Diagram 5] FIG. 13 is a diagram illustrating an example of a configuration of a management device according to a first modified example. [Figure 6] FIG. 11 is a diagram showing an example of each piece of data according to Modification 1. [Figure 7] 13 is a flowchart showing an example of a management method according to Modification 1. [Figure 8] FIG. 11 is a diagram illustrating an example of a configuration of a management device according to Modification 2. [Figure 9] 13 is a flowchart showing an example of a management method according to Modification 2. [Figure 10] FIG. 11 is a diagram illustrating an example of a configuration of a management device according to a third modified example. [Figure 11] 13 is a flowchart showing an example of a management method according to Modification 3. [Figure 12] FIG. 11 is a diagram illustrating an example of a configuration of a management device according to a second embodiment. [Figure 13] FIG. 11 is a diagram showing an example of each piece of data according to the second embodiment. [Figure 14] FIG. 11 is a diagram showing an example of each piece of data according to the second embodiment. [Figure 15] 10 is a flowchart showing an example of a management method according to the second embodiment. [Figure 16] FIG. 13 is a diagram illustrating an example of a configuration of a management device according to a third embodiment. [Figure 17] 13 is a flowchart showing an example of a management method according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In principle, the same components are designated by the same reference numerals, and duplicated descriptions will be omitted.

[0013] [First embodiment] <Configuration of management device> An example of the configuration of a management device according to the first embodiment will be described with reference to FIGS. 1 to 3. FIG.

[0014] The management device 100 is a device that manages the timing of disposing of a user interface (UI). A user can operate, for example, a notebook PC (personal computer), a mobile terminal such as a smartphone, a tablet terminal, etc., via the UI. The UI is not particularly limited in form as long as it is at least disposable. Examples of the UI include a cloth-like touch panel type device that can be attached and detached to clothing, and a string type device wound around a bobbin.

[0015] The location of the management device 100 is not particularly limited, and the management device 100 may be built into a notebook PC, a mobile terminal, a tablet terminal, or the like, or may be connected to these devices in a wired or wireless manner so as to be able to communicate with them. Alternatively, the management device 100 may be connected to a UI in a wired or wireless manner so as to be able to communicate with them.

[0016] The management device 100 includes a control unit 110 and a storage unit 120 .

[0017] The control unit 110 may be configured with dedicated hardware, or may be configured with a general-purpose processor or a processor specialized for a specific process. The control unit 110 includes an operation detection unit 111 and a management unit 112.

[0018] The storage unit 120 includes one or more memories, and may include, for example, a semiconductor memory, a magnetic memory, an optical memory, etc. Each memory included in the storage unit 120 may function, for example, as a main memory device, an auxiliary memory device, or a cache memory. Each memory does not necessarily need to be provided inside the management device 100, and may be configured to be provided outside the management device 100. The storage unit 120 stores any information used in the operation of the management device 100. In addition, the storage unit 120 stores, for example, various programs or data. The storage unit 120 includes an operation history information database 121 and a setting information database 122.

[0019] The operation history information database 121 stores operation history information regarding the history of operations on the UI. The operation history information is information input from the operation detection unit 111. As shown in FIG. 2, the operation history information is information indicating an "operation type" including, for example, the start of a touch operation on the UI and the end of a touch operation on the UI. In addition, the operation history information is information indicating a "time" including, for example, the time when the touch operation on the UI started "2021-03-26 17:28:31" and the time when the touch operation on the UI ended "2021-03-26 17:28:34".

[0020] The setting information database 122 stores setting information regarding the timing of disposing of the UI. The setting information is information that is set in advance. As shown in Fig. 3, the setting information is information indicating "parameters" including, for example, the number of touch operations on the UI and the elapsed time from the end of the touch operation on the UI. The setting information is also information indicating "thresholds" including, for example, "one or more times" which is the number of touch operations on the UI and "five minutes or more" which is the elapsed time from the end of the touch operation on the UI.

[0021] The operation detection unit 111 detects an operation on the UI and generates operation detection information. The operation detection unit 111 outputs the operation detection information to the management unit 112. The operation detection unit 111 also stores the operation detection information in the operation history information database 121. An operation on the UI means an operation at least in a state where the user is in contact with the UI, such as a user pressing the UI, a user scrolling the UI, a user pinching the UI, or a user pulling the UI.

[0022] The management unit 112 determines whether or not to dispose of the UI based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121.

[0023] The management device 100 according to the first embodiment determines whether or not to dispose of a UI based on setting information, operation detection information, and operation history information. By applying the management device 100, it is possible to appropriately manage the timing of disposing of a UI, so that a user can use a UI in a clean state.

[0024] In addition, since it is possible to avoid conventional problems such as the user having to remember whether or not the UI has been touched, the user having to always throw away the UI when he or she forgets whether or not he or she has used the UI, which is costly, and the user having to clean the UI from time to time, the user can always touch a UI in a clean state without depending on the user's memory regarding the use of the UI, the difference in awareness of cleanliness between different users, etc., it is possible to realize a management device 100 that is effective in infection control.

[0025] <Management method> An example of a management method according to the first embodiment will be described with reference to FIG.

[0026] In step 101, the setting information database 122 stores setting information regarding the timing of disposing the UI.

[0027] In step 102, the operation detection unit 111 detects an operation on the UI and generates operation detection information. The operation detection unit 111 outputs the operation detection information to the management unit 112.

[0028] In step 103, the operation history information database 121 stores operation history information relating to the history of operations on the UI.

[0029] In step 104, the management unit 112 determines whether or not to dispose of the UI based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121.

[0030] By applying the management method according to the first embodiment, it is possible to appropriately manage the timing of disposing of a UI.

[0031] [Variation 1] <Configuration of management device> An example of the configuration of a management device 100A according to the first modification will be described with reference to FIG. 5 or FIG.

[0032] The management device 100A according to the first modification is different from the management device 100 according to the first embodiment in that the management device 100 according to the first embodiment does not include a notification unit and a notification setting information database, whereas the management device 100A according to the first modification includes a notification unit and a notification setting information database. Since the other configurations are the same, repeated explanations will be omitted.

[0033] The management device 100A includes a control unit 110A and a storage unit 120A. The control unit 110A includes an operation detection unit 111, a management unit 112, and a notification unit 113. The storage unit 120A includes an operation history information database 121, a setting information database 122, and a notification setting information database 123.

[0034] The notification setting information database 123 stores notification setting information related to notification contents for notifying the outside that it is time to dispose of the UI. The notification setting information is information that is set in advance. As shown in FIG. 6, the notification setting information is information indicating a "notification type" including, for example, "sound", "vibration", "color", etc. The notification setting information is also information indicating a "notification pattern" including, for example, "notification sound 1", "vibration 2", "red", etc. Note that the notification setting information is not limited to these pieces of information, and for example, the information indicating the "notification type" may be "light", and the information indicating the "notification pattern" may be "flashing of LED lamp", etc.

[0035] The management unit 112 determines whether or not to make the UI disposable based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121, and outputs the determination result to the notification unit 113. For example, when the management unit 112 determines that the UI is disposable, it outputs a determination result indicating that it is time to make the UI disposable to the notification unit 113. For example, when the management unit 112 determines that the UI is not disposable, it outputs a determination result indicating that it is not time to make the UI disposable to the notification unit 113.

[0036] When the management unit 112 determines that the UI is to be discarded, the notification unit 113 executes the set notification content based on the notification setting information stored in the notification setting information database 123 to notify the outside that it is time to discard the UI. The configuration of the notification unit 113 is not particularly limited. The notification unit 113 may be, for example, a speaker, a vibration device, or an LED lamp mounted on a mobile terminal. The notification unit 113 may be, for example, an application device mounted on the UI. The notification unit 113 may be, for example, sunglasses worn by a user.

[0037] For example, when the notification unit 113 is a speaker, when a determination result indicating that it is time to dispose of the UI is input from the management unit 112, the notification unit 113 plays notification sound 1, and when a determination result indicating that it is not time to dispose of the UI is input from the management unit 112, the notification unit 113 does not output any sound.

[0038] For example, if the notification unit 113 is a vibration device, when a determination result indicating that it is time to discard the UI is input from the management unit 112, the notification unit 113 vibrates with vibration 2, and when a determination result indicating that it is not time to discard the UI is input from the management unit 112, the notification unit 113 does not vibrate.

[0039] For example, when the notification unit 113 is an application device, when a determination result indicating that it is time to dispose of the UI is input from the management unit 112, the notification unit 113 discolors the cloth or string, which is the UI, to red using temperature-sensitive ink, and when a determination result indicating that it is not time to dispose of the UI is input from the management unit 112, the notification unit 113 does not discolor the cloth or string, which is the UI.

[0040] The management device 100A according to the first modification determines whether or not to dispose of a UI based on the setting information, the operation detection information, and the operation history information, and when it is determined that the UI is disposable, notifies the outside that it is time to dispose of the UI. By applying the management device 100, it is possible to appropriately manage the timing to dispose of a UI and notify the outside, so that the user can use a UI in a clean state.

[0041] <Management method> An example of a management method according to the first modification will be described with reference to FIG.

[0042] In step 101, the setting information database 122 stores setting information regarding the timing of disposing the UI.

[0043] In step 102, the notification setting information database 123 stores notification setting information relating to notification contents for notifying an external device that it is time to dispose of the UI.

[0044] In step 103, the operation detection unit 111 detects an operation on the UI and generates operation detection information. The operation detection unit 111 outputs the operation detection information to the management unit 112.

[0045] In step 104, the operation history information database 121 stores operation history information relating to the history of operations on the UI.

[0046] In step 105, the management unit 112 determines whether or not the UI is disposable, based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121. Then, the management unit 112 outputs the determination result to the notification unit 113.

[0047] In step 106, if the determination result input from the management unit 112 indicates that it is time to discard the UI, the notification unit 113 executes the set notification content based on the notification setting information stored in the notification setting information database 123 to notify the outside that it is time to discard the UI.

[0048] By applying the management method according to the first modification, it is possible to appropriately manage the timing of disposing of the UI and notify the outside.

[0049] [Modification 2] <Configuration of management device> An example of the configuration of a management device 100B according to the second modification will be described with reference to FIG.

[0050] The management device 100B according to the second modification is different from the management device 100 according to the first embodiment in that the management device 100 according to the first embodiment does not include a disposable execution unit, whereas the management device 100B according to the second modification includes a disposable execution unit. Since the other configurations are the same, repeated explanations will be omitted.

[0051] The management device 100B includes a control unit 110B and a storage unit 120. The control unit 110B includes an operation detection unit 111, a management unit 112, and a disposable execution unit 114. The storage unit 120 includes an operation history information database 121 and a setting information database 122.

[0052] The management unit 112 determines whether or not to make the UI disposable based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121, and outputs the determination result to the disposable execution unit 114. For example, when the management unit 112 determines that the UI is disposable, it outputs a determination result indicating that it is time to make the UI disposable to the disposable execution unit 114. For example, when the management unit 112 determines that the UI is not disposable, it outputs a determination result indicating that it is not time to make the UI disposable to the disposable execution unit 114.

[0053] When the management unit 112 determines that the UI is to be disposed of, the disposable execution unit 114 executes an operation for disposing of the UI. The configuration of the disposable execution unit 114 is not particularly limited as long as the disposable execution unit 114 is a device that can automatically dispose of the UI. The disposable execution unit 114 may be, for example, a servo motor equipped with a blade capable of cutting a string, or a robot equipped with an arm capable of winding up a cloth.

[0054] For example, if the disposable execution unit 114 is a servo motor, when the disposable execution unit 114 receives a determination result from the management unit 112 indicating that it is time to dispose of the UI, it cuts the string, which is the UI, and when the disposable execution unit 114 receives a determination result from the management unit 112 indicating that it is not time to dispose of the UI, it does not cut the string, which is the UI.

[0055] For example, if the disposable execution unit 114 is a robot arm, when a determination result indicating that it is time to dispose of the UI is input from the management unit 112, the disposable execution unit 114 rolls up the cloth that is the UI and replaces it with new cloth, and when a determination result indicating that it is not time to dispose of the UI is input from the management unit 112, the disposable execution unit 114 does not roll up the cloth that is the UI.

[0056] The management device 100B according to the second modification determines whether or not to dispose of the UI based on the setting information, the operation detection information, and the operation history information, and executes disposable of the UI when it is determined that the UI is disposable. By applying the management device 100, it is possible to appropriately manage the timing of disposing of the UI and automate the action of disposing of the UI, so that the user can use the UI in a clean state.

[0057] <Management method> An example of a management method according to the second modification will be described with reference to FIG.

[0058] In step 101, the setting information database 122 stores setting information regarding the timing of disposing the UI.

[0059] In step 102, the operation detection unit 111 detects an operation on the UI and generates operation detection information. The operation detection unit 111 outputs the operation detection information to the management unit 112.

[0060] In step 103, the operation history information database 121 stores operation history information relating to the history of operations on the UI.

[0061] In step 104, the management unit 112 determines whether or not to dispose of the UI, based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121. Then, the management unit 112 outputs the determination result to the disposable execution unit 114.

[0062] In step 105, if the determination result input from management unit 112 indicates that it is time to make the UI disposable, disposable execution unit 114 executes an operation for making the UI disposable.

[0063] By applying the management method according to the second modification, it is possible to appropriately manage the timing of disposing of a UI and automate the action of disposing of a UI.

[0064] [Modification 3] <Configuration of management device> An example of the configuration of a management device 100C according to the third modification will be described with reference to FIG.

[0065] The management device 100C according to the third modification is different from the management device 100 according to the first embodiment in that the management device 100 according to the first embodiment does not include a proximity detector, a disposable detector, and a disposable history information database, whereas the management device 100C according to the third modification is provided with a proximity detector, a disposable detector, and a disposable history information database. Since the other configurations are the same, repeated explanations will be omitted.

[0066] The management device 100C includes a control unit 110C and a storage unit 120C. The control unit 110C includes an operation detection unit 111, a management unit 112, a proximity detection unit 115, and a disposable detection unit 116. The storage unit 120C includes an operation history information database 121, a setting information database 122, and a disposable history information database 124.

[0067] The proximity detection unit 115 detects proximity to the UI and generates proximity detection information. The proximity detection unit 115 outputs the proximity detection information to the management unit 112. Proximity to the UI means a state in which the user and the UI are close to each other without touching each other, such as when the user's finger approaches within a distance of about several centimeters from the UI.

[0068] The management unit 112 determines, based on the operation detection information input from the operation detection unit 111 and the proximity detection information input from the proximity detection unit 115, whether the operation is to the UI or proximity to the UI.

[0069] When management unit 112 determines that the operation is on the UI, it determines whether or not to make the UI disposable based on the setting information stored in setting information database 122, the operation detection information input from operation detection unit 111, and the operation history information stored in operation history information database 121, and outputs the determination result to disposable detection unit 116. For example, when management unit 112 determines that the UI is disposable, it outputs a determination result indicating that it is time to make the UI disposable to disposable detection unit 116. For example, when management unit 112 determines that the UI is not disposable, it outputs a determination result indicating that it is not time to make the UI disposable to disposable detection unit 116.

[0070] When the management unit 112 determines that the user is approaching the UI, the management unit 112 determines whether or not the UI is disposable based on the setting information stored in the setting information database 122, the proximity detection information input from the proximity detection unit 115, and the disposable history information stored in the disposable history information database 124, and outputs the determination result to the disposable detection unit 116. For example, when the management unit 112 determines that the UI is disposable, the management unit 112 outputs a determination result indicating that it is time to dispose of the UI to the disposable detection unit 116. For example, when the management unit 112 determines that the UI is not disposable, the management unit 112 outputs a determination result indicating that it is not time to dispose of the UI to the disposable detection unit 116. By the management unit 112 determining whether or not the UI is disposable before the user touches the UI, it is possible to prevent the user from touching a UI in a dirty state.

[0071] The disposable detection unit 116 detects whether or not disposable of the UI has been executed, and outputs the detection result to the disposable history information database 124. For example, when the management unit 112 determines that the UI is to be disposable, the disposable detection unit 116 detects that disposable of the UI has been executed. For example, when the management unit 112 determines that the UI is not to be disposable, the disposable detection unit 116 detects that disposable of the UI has not been executed.

[0072] The disposable history information database 124 stores disposable history information related to the history of disposable execution of a UI. The disposable history information is information input from the disposable detection unit 116. The disposable history information is, for example, information indicating that disposable execution of a specific UI has been performed. Also, the disposable history information is, for example, information indicating that disposable execution of a specific UI has not been performed.

[0073] The management device 100C according to the third modification determines whether the operation is to the UI or the proximity to the UI based on the operation detection information and the proximity detection information. When the management device 100C determines that the operation is to the UI, it determines whether the UI is to be used as a disposable device based on the setting information, the operation detection information, and the operation history information, and when it determines that the UI is to be used as a disposable device, it detects the execution of the disposable device of the UI. Alternatively, when the management device 100C determines that the proximity to the UI is to be used as a disposable device based on the setting information, the proximity detection information, and the disposable history information, it detects the execution of the disposable device of the UI when it determines that the UI is to be used as a disposable device. By applying the management device 100C, the timing of disposable use of the UI can be appropriately managed, so that the user can use a UI in a clean state. In addition, by applying the management device 100C, it is possible to estimate that the user is about to touch the UI, and to appropriately dispose of the UI before the user touches the UI, so that even if the user forgets to dispose of the UI after using it, it is possible to prevent the user from touching a dirty UI.

[0074] <Management method> An example of a management method according to the third modification will be described with reference to FIG.

[0075] In step 101, the setting information database 122 stores setting information regarding the timing of disposing the UI.

[0076] In step 102, the operation detection unit 111 detects an operation on the UI and generates operation detection information. The operation detection unit 111 outputs the operation detection information to the management unit 112.

[0077] In step 103, the proximity detector 115 detects proximity to the UI and generates proximity detection information. The proximity detector 115 outputs the proximity detection information to the manager 112.

[0078] In step 104, the operation history information database 121 stores operation history information relating to the history of operations on the UI.

[0079] In step 105, the disposable history information database 124 stores disposable history information regarding the history of disposable executions of the UI.

[0080] In step 106, the management unit 112 determines whether the operation is to the UI or the approach to the UI based on the operation detection information and the approach detection information. If the management unit 112 determines that the operation is to the UI, it performs processing of step 107. If the management unit 112 determines that the approach is to the UI, it performs processing of step 108.

[0081] In step 107, the management unit 112 determines whether or not the UI is disposable, based on the setting information stored in the setting information database 122, the operation detection information input from the operation detection unit 111, and the operation history information stored in the operation history information database 121. Then, the management unit 112 outputs the determination result to the disposable detection unit 116.

[0082] In step 108, the management unit 112 determines whether or not the UI is disposable before the user touches the UI, based on the setting information stored in the setting information database 122, the proximity detection information input from the proximity detection unit 115, and the disposable history information stored in the disposable history information database 124. Then, the management unit 112 outputs the determination result to the disposable detection unit 116.

[0083] In step 109, if the determination result input from management unit 112 indicates that it is time to make the UI disposable, disposable detection unit 116 detects the execution of disposable.

[0084] By applying the management method according to Modification 3, it is possible to appropriately manage the timing of disposing of a UI. Furthermore, it is possible to prevent a user from touching a UI in a dirty state, thereby realizing a management method that is particularly effective in preventing infection.

[0085] Second Embodiment <Configuration of management device> An example of the configuration of a management device 200 according to the second embodiment will be described with reference to FIGS.

[0086] The management device 200 includes a control unit 210 and a storage unit 220. The control unit 210 includes a position detection unit 211 and a management unit 212. The storage unit 220 includes a position history information database 221 and a setting information database 222.

[0087] The location history information database 221 stores location history information related to the location history of the UI. The location history information is information input from the location detection unit 211. As shown in FIG. 13, the location history information is information indicating a "location type" including, for example, GPS (Global Positioning System) data, area data, and the like. In addition, the location history information is information indicating a "time" including, for example, the time when the UI arrived at a predetermined position, "2021-03-26 17:28:31", the time when the UI departed from a predetermined position, "2021-03-26 18:01:32", and the like.

[0088] The setting information database 222 stores setting information regarding the timing of disposing of the UI. The setting information is information that is set in advance. As shown in Fig. 14, the setting information is information indicating "parameters" including, for example, the duration that the UI stayed at a predetermined position. The setting information is also information indicating "thresholds" including, for example, "30 minutes or more" which is the duration that the UI stayed at a predetermined position.

[0089] The position detection unit 211 detects the position of the UI based on the GPS data and the area data, and generates position detection information. The position detection unit 211 outputs the position detection information to the management unit 112. The position detection unit 211 also stores the position detection information in the position history information database 221. The position of the UI means the position where the UI currently exists, such as the position of the UI when the user enters the supermarket, or the position of the UI when the user leaves the supermarket.

[0090] The management unit 212 determines whether or not the UI is disposable based on the setting information stored in the setting information database 222, the position detection information input from the position detection unit 211, and the position history information stored in the position history information database 221.

[0091] The management device 200 according to the second embodiment determines whether or not to dispose of a UI based on the setting information, the position detection information, and the position history information. By applying the management device 200, the timing of disposing of a UI can be appropriately managed, so that a user can use a UI in a clean state.

[0092] In addition, the timing to dispose of the UI can be appropriately managed according to the location of the UI, such as disposing of the UI when the user leaves a supermarket because there are many people there and the risk of infection is high, and not disposing of the UI even after the user has stayed in a park because there are few people there and the risk of infection is low. This makes it possible to realize a management device 200 that is effective in preventing infectious diseases.

[0093] <Management method> An example of a management method according to the second embodiment will be described with reference to FIG.

[0094] In step 201, the setting information database 222 stores setting information regarding the timing of disposing the UI.

[0095] In step 202, the position detection unit 211 detects the position of the UI based on the GPS data and the area data, and generates position detection information. The position detection unit 211 outputs the position detection information to the management unit 212.

[0096] In step 203, a location history information database 221 stores location history information regarding the location history of the UI.

[0097] In step 204, the management unit 212 determines whether or not to dispose of the UI based on the setting information stored in the setting information database 222, the position detection information input from the position detection unit 211, and the position history information stored in the position history information database 221.

[0098] By applying the management method according to the second embodiment, it is possible to appropriately manage the timing of disposing of a UI.

[0099] Third Embodiment <Configuration of management device> An example of the configuration of a management device according to the third embodiment will be described with reference to FIG.

[0100] The management device 300 includes a control unit 310 and a storage unit 320. The control unit 310 includes an operation detection unit 311, a position detection unit 312, and a management unit 313. The storage unit 320 includes an operation history information database 321, a position history information database 322, and a setting information database 323.

[0101] The operation history information database 321 stores operation history information relating to the history of operations on the UI. The operation history information is information input from the operation detection unit 311.

[0102] The position history information database 322 stores position history information relating to the position history of the UI. The position history information is information input from the position detection unit 312.

[0103] The setting information database 323 stores setting information related to the timing of disposing of the UI. The setting information is information that is set in advance.

[0104] The operation detection unit 311 detects an operation on the UI and generates operation detection information. The operation detection unit 311 outputs the operation detection information to the management unit 313. In addition, the operation detection unit 311 stores the operation detection information in the operation history information database 321.

[0105] The position detection unit 312 detects the position of the UI based on the GPS data and the area data, and generates position detection information. The position detection unit 312 outputs the position detection information to the management unit 313. The position detection unit 312 also stores the position detection information in the position history information database 322.

[0106] The management unit 313 determines whether or not to dispose of the UI based on the setting information stored in the setting information database 323, the operation detection information input from the operation detection unit 311, the operation history information stored in the operation history information database 321, the position detection information input from the position detection unit 312, and the position history information stored in the position history information database 322.

[0107] For example, the management unit 313 determines that the UI is disposable when it determines that the UI is disposable based on the setting information stored in the setting information database 323, the operation detection information input from the operation detection unit 311, and the operation history information stored in the operation history information database 321, and also determines that the UI is disposable based on the setting information stored in the setting information database 323, the position detection information input from the position detection unit 312, and the position history information stored in the position history information database 322. In other words, the management unit 313 determines that the UI is disposable when it determines that both the operation condition and the position condition are satisfied.

[0108] For example, the management unit 313 determines that the UI is disposable when it determines that the UI is disposable based on the setting information stored in the setting information database 323, the operation detection information input from the operation detection unit 311, and the operation history information stored in the operation history information database 321, or when it determines that the UI is disposable based on the setting information stored in the setting information database 323, the position detection information input from the position detection unit 312, and the position history information stored in the position history information database 322. That is, the management unit 313 determines that the UI is disposable when it determines that the operation condition is satisfied but the position condition is not satisfied. Alternatively, the management unit 313 determines that the UI is disposable when it determines that the operation condition is not satisfied but the position condition is satisfied.

[0109] The management device 300 according to the third embodiment determines whether or not to dispose of a UI based on setting information, operation detection information, operation history information, position detection information, and position history information. By applying the management device 300, the timing of disposing of a UI can be appropriately managed, so that a user can use a UI in a clean state.

[0110] <Management method> An example of a management method according to the third embodiment will be described with reference to FIG.

[0111] In step 301, the setting information database 323 stores setting information regarding the timing of disposing the UI.

[0112] In step 302, the operation detection unit 311 detects an operation on the UI and generates operation detection information. The operation detection unit 311 outputs the operation detection information to the management unit 313.

[0113] In step 303, the position detection unit 312 detects the position of the UI based on the GPS data and the area data, and generates position detection information. The position detection unit 312 outputs the position detection information to the management unit 313.

[0114] In step 304, the operation history information database 321 stores operation history information relating to the history of operations on the UI.

[0115] In step 305, a location history information database 322 stores location history information regarding the location history of the UI.

[0116] In step 306, the management unit 313 determines whether or not to dispose of the UI based on the setting information stored in the setting information database 323, the operation detection information input from the operation detection unit 311, the operation history information stored in the operation history information database 321, the position detection information input from the position detection unit 312, and the position history information stored in the position history information database 322.

[0117] By applying the management method according to the third embodiment, it is possible to appropriately manage the timing for disposing of a UI.

[0118] <Modification> The present invention is not limited to the above-mentioned embodiment and modified examples. For example, the above-mentioned various processes may be executed not only in chronological order as described, but also in parallel or individually depending on the processing capacity of the device executing the processes or as necessary. In addition, appropriate modifications are possible within the scope of the present invention.

[0119] <Programs and recording media> It is also possible to use a computer capable of executing program instructions to function as the above-mentioned embodiment and modified examples. Here, the computer may be a general-purpose computer, a dedicated computer, a workstation, a PC (Personal Computer), an electronic notepad, or the like. The program instructions may be program code, code segments, or the like for executing a required task. The processor functioning as the control unit 110, 110A, 110B, 110C, 210, 310 may be a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), a SoC (System on a Chip), or the like, and may be composed of multiple processors of the same type or different types. The control unit 110, 110A, 110B, 110C, 210, 310 reads a program from the storage unit 120, 120A, 120C, 220, 320, and executes the program to control each of the above-mentioned components and perform various arithmetic processing. At least a part of these processing contents may be realized by hardware.

[0120] For example, referring to FIG. 4, a program for causing a computer to execute the above-mentioned management method is a management method for managing the timing of disposing of a user interface, and includes at least a step of storing setting information regarding the timing (step 101), a step of detecting an operation on the user interface and generating operation detection information (step 102), a step of storing operation history information regarding the operation history (step 103), and a step of determining whether or not to dispose of the user interface based on the setting information, the operation detection information, and the operation history information (step 104).

[0121] The program may be recorded on a computer-readable recording medium. By using such a recording medium, the program can be installed on a computer. Here, the recording medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium may be a CD (Compact Disk)-ROM (Read-Only Memory), a DVD (Digital Versatile Disc)-ROM, a BD (Blu-ray (registered trademark) Disc)-ROM, or the like. The program may also be provided by downloading via a network.

[0122] Although the above-mentioned embodiment has been described as a representative example, it is obvious to those skilled in the art that many modifications and substitutions can be made within the spirit and scope of the present disclosure. Therefore, the present invention should not be interpreted as being limited by the above-mentioned embodiment, and various modifications and changes are possible without departing from the scope of the claims. For example, it is possible to combine multiple configuration blocks shown in the configuration diagram of the embodiment into one, or to divide one configuration block. It is also possible to combine multiple steps shown in the flow chart of the embodiment into one, or to divide one step. [Explanation of symbols]

[0123] 100,100A,100B,100C management device 110, 110A, 110B, 110C Control unit 111 Operation detection unit 112 Management Department 113 Notification Department 114 Disposable Executive Division 115 Proximity detector 116 Disposable detector 120,120A,120C storage section 121 Operation History Information Database 122 Configuration information database 123 Notification settings information database 124 Disposable History Information Database 200 Management device 210 Control section 211 Position detection unit 212 Management Department 220 Storage section 221 Location History Information Database 222 Configuration information database 300 Management device 310 Control section 311 Operation detection unit 312 Position detection unit 313 Management Department 320 Storage section 321 Operation History Information Database 322 Location History Information Database 323 Configuration information database

Claims

1. A management device for managing timing for disposing of a user interface, a setting information database that stores setting information related to the timing; a proximity detection unit that detects proximity to the user interface and generates proximity detection information; an operation history information database that stores disposable history information relating to a history of disposable execution of the user interface; a management unit that determines whether or not the user interface is disposable based on the setting information, the proximity detection information, and the disposable history information; A management device comprising:

2. A management device for managing timing for disposing of a user interface, a setting information database that stores setting information related to the timing; a position detection unit that detects a position of the user interface and generates position detection information; a location history information database that stores location history information relating to the location history; a management unit that determines whether or not the user interface is disposable based on the setting information, the position detection information, and the position history information; A management device comprising:

3. A management device for managing timing for disposing of a user interface, a setting information database that stores setting information related to the timing; an operation detection unit that detects an operation on the user interface and generates operation detection information; a position detection unit that detects a position of the user interface and generates position detection information; an operation history information database that stores operation history information relating to the history of the operation; a location history information database that stores location history information relating to the location history; a management unit that determines whether or not the user interface is disposable based on the setting information, the operation detection information, the position detection information, the operation history information, and the position history information; A management device comprising:

4. A method for managing timing for disposing of a user interface, comprising: storing setting information relating to the timing; detecting proximity to the user interface and generating proximity detection information; storing disposable history information relating to a history of disposable executions of the user interface; determining whether the user interface is disposable based on the setting information, the proximity detection information, and the disposable history information; (c) a method of administration;

5. A method for managing timing for disposing of a user interface, comprising: storing setting information relating to the timing; sensing a position of the user interface and generating position sensing information; storing location history information relating to said location history; determining whether the user interface is disposable based on the setting information, the location detection information, and the location history information; (c) a method of administration;

6. A method for managing timing for disposing of a user interface, comprising: storing setting information relating to the timing; detecting an operation on the user interface and generating operation detection information; sensing a position of the user interface and generating position sensing information; storing operation history information relating to a history of the operations; storing location history information relating to said location history; determining whether the user interface is disposable based on the setting information, the operation detection information, the position detection information, the operation history information, and the position history information; (c) a method of administration;

7. A program for causing a computer to function as the management device according to any one of claims 1 to 3.

Images