Information processing device

Abstract

To provide a technique for further appropriately managing user operation frequency and customizing a screen further in line with user intention.SOLUTION: An information processing apparatus comprises: a display unit for displaying a display screen including one or more operation buttons; a storage unit for storing button control information including a record of the number of times the operation buttons are operated for each operation button; a drawing unit for determining a display mode for each operation button to draw the display screen using at least the button control information; and an updating unit for counting up the number of times of operations associated with the operation buttons for a first operation in the button control information, when an input to one of the operation buttons being displayed on the display screen is accepted as the first operation and if a second operation for transitioning from the display screen to another screen different from the display screen is not accepted within a predetermined time.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for an information processing device. [Background technology]

[0002] Patent Document 1 describes a technology related to a screen generating device that includes: a screen generating unit that generates a display screen having a plurality of operation buttons; an operation history recording unit that records the number of operations by a user on the display screen for each operation button within a certain period of time; a comparison unit that compares the number of operations for each operation button recorded in the operation history recording unit with a first threshold and a second threshold that is greater than the first threshold; a non-display target setting unit that sets operation buttons whose number of operations is determined by the comparison unit to be equal to or less than the first threshold as targets to be hidden; and an enlargement target setting unit that sets operation buttons whose number of operations is determined by the comparison unit to be equal to or greater than the second threshold as targets to be enlarged; and if there is an operation button that has been set as a target to be hidden by the non-display target setting unit, the screen generating unit hides the operation button on the display screen, and if there is an operation button that has been set as a target to be enlarged by the enlargement target setting unit, increases the display size of the operation button on the display screen to be larger than the standard size. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-37551 Summary of the Invention [Problem to be solved by the invention]

[0004] The above-described technology counts the number of times a user operates an operation button uniformly, and therefore, even unintentional operations such as erroneous operations are counted, which may result in an unintended change to the screen display.

[0005] An object of the present invention is to provide a technique for more appropriately managing the frequency of user operations and customizing a screen in accordance with the user's intentions. [Means for solving the problem]

[0006] The present invention includes a plurality of means for solving at least part of the above-mentioned problems, examples of which are as follows: To solve the above-mentioned problems, an information processing device according to the present invention includes a display unit that displays a display screen having one or more operation buttons, a storage unit that stores button control information including a record of the number of times the operation buttons are operated for each of the operation buttons, a drawing unit that uses at least the button control information to determine a display form for each of the operation buttons and draws the display screen, and an update unit that, when an input to one of the operation buttons displayed on the display screen is accepted as a first operation, and, if a second operation for transitioning from the display screen to a screen different from the display screen is not accepted within a predetermined time, counts up the number of operations associated with the operation button related to the first operation in the button control information. [Effects of the Invention]

[0007] According to the present invention, it is possible to more appropriately manage the frequency of user operations and perform screen customization that better suits the user's intentions. Problems, configurations, and effects other than those described above will become clear from the following description of the embodiment. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of the configuration of an information processing device. [Figure 2] FIG. 10 is a diagram illustrating an example of a data structure of button control information. [Figure 3] FIG. 10 is a diagram illustrating an example of a data structure of screen information. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing device. [Figure 5] FIG. 10 is a diagram illustrating an example of a processing flow of an operation status recording process. [Figure 6]FIG. 10 is a diagram illustrating an example of a processing flow of drawing processing. [Figure 7] FIG. 10 illustrates an example of a processing flow of a performance update process. [Figure 8] 10A and 10B are diagrams illustrating examples of display forms of operation buttons. [Figure 9] FIG. 10 is a diagram illustrating an example of counting operation buttons. [Figure 10] FIG. 10 is a diagram illustrating a modified example of the operation status recording process. [Figure 11] FIG. 10 is a diagram showing another example of counting operation buttons. DETAILED DESCRIPTION OF THE INVENTION

[0009] An information processing device according to an embodiment of the present invention will be described below with reference to the drawings. Note that Figures 1 to 11 do not show the entire configuration of the information processing device according to the present invention, and for ease of understanding, some of the configuration has been omitted as appropriate. In the following embodiments, when necessary for convenience, the description will be divided into multiple sections or embodiments. However, unless otherwise specified, they are not unrelated to each other, and one is related to the other as a partial or complete modification, detail, supplementary explanation, etc.

[0010] Furthermore, in the following embodiments, when referring to the number of elements (including the number, numerical value, amount, range, etc.), unless otherwise specified or when it is clearly limited to a specific number in principle, it is not limited to that specific number and may be more or less than the specific number.

[0011] Furthermore, it goes without saying that in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless otherwise specified or considered to be clearly essential in principle.

[0012] Similarly, in the following embodiments, when referring to the shapes, positional relationships, etc. of components, etc., it is intended to include those that are substantially similar or similar to those shapes, etc., unless otherwise specified or when it is clearly considered that this is not the case in principle. The same applies to numerical values and ranges.

[0013] In all the drawings for explaining the embodiments, the same components are generally designated by the same reference numerals, and repeated explanations may be omitted. In the following embodiments, when it is said that "consists of A," "is made of A," "has A," or "includes A," it goes without saying that it does not exclude other elements, unless it is specifically stated that only those elements are included.

[0014] Similarly, in the following embodiments, when referring to the shape, positional relationship, etc. of components, etc., it is intended to include things that are substantially similar or approximate to those shapes, etc., unless otherwise specified or when it is clearly considered otherwise in principle.

[0015] [Embodiment 1] In this embodiment, an example of an information processing device 100 mounted on a vehicle that customizes a screen in response to operations by a vehicle user is shown. However, it goes without saying that the information processing device 100 is not limited to vehicles and can be applied to any moving body such as a train, electric train, boat, or ferry. Furthermore, the information processing device 100 can also be applied to an office information processing device, a smartphone, various IT (Information Technology) devices in the home, and even a home game console.

[0016] 1 is a diagram showing an example of the configuration of an information processing device. The information processing device 100 has at least a processing unit 110 and a storage unit 120. The processing unit 110 includes an input control unit 111, a display unit 112, a drawing unit 113, a timing unit 114, and an update unit 115. The storage unit 120 stores button control information 121 and screen information 122.

[0017] FIG. 2 is a diagram showing an example of the data structure of button control information. In the button control information 121, for each button ID 121a, an operation count 121b, hatching 121c, non-display 121d, related button 121e, and related screen 121f are stored in association with each other. An identifier that uniquely identifies an operation button is stored in the button ID 121a. Note that in this embodiment, a button refers to a general operation button, including both a button that accepts input through software processing and a physical button as hardware. An operation button is a button that, when it accepts input, triggers an action involving a screen transition or a pop-up display.

[0018] The operation count 121b stores information specifying the number of times the operation button identified by the button ID 121a has been operated. The hatching 121c stores information specifying whether the operation button identified by the button ID 121a is displayed in a highlighted manner. The non-display 121d stores information specifying whether the operation button identified by the button ID 121a is displayed in a hidden manner. The associated button 121e stores information specifying an operation button related to the operation button identified by the button ID 121a, specifically, an operation button that realizes a function subordinate to the operation button identified by the button ID 121a. For example, if the operation button identified by the button ID 121a is a music play button, the associated button 121e stores information specifying a volume button or the like that is realized on the same screen when music is played. The associated screen 121f stores information specifying a screen including the operation button identified by the button ID 121a.

[0019] 3 is a diagram showing an example of the data structure of screen information. In the screen information 122, a display history time 122b, a layout 122c, and related buttons 122d are stored in association with each other for each screen ID 122a. An identifier that uniquely identifies the screen is stored in the screen ID 122a.

[0020] The actual display time 122b stores information specifying the actual time that the screen specified by the screen ID 122a has been displayed. The layout 122c stores information specifying layout data to be applied to the screen specified by the screen ID 122a. The related buttons 122d store information specifying operation buttons related to the screen specified by the screen ID 122a, specifically, information specifying operation buttons that the screen specified by the screen ID 122a has. For example, if the screen specified by the screen ID 122a is a music playback screen, the related buttons 122d store information specifying a song selection button, a play / stop button, etc. that are realized on the same screen during music playback. However, the related buttons are not limited to this, and may be any buttons that are related to each other.

[0021] The input control unit 111 detects input to an operation button. Specifically, the input control unit 111 detects input by a user, mainly touch input via a touch panel, and identifies the input coordinates and input type (tap, long tap, flick, pinch, etc.). Alternatively, the input control unit 111 accepts input by a user via a hardware button (for example, a button for controlling volume).

[0022] The display unit 112 displays a display screen having one or more operation buttons. The display screen is drawn by the drawing unit 113, which will be described later. Usually, the display screen has one or more operation buttons including a back button for returning the screen transition to the state before the transition.

[0023] The drawing unit 113 determines a display mode for each operation button using at least the button control information 121 and draws the display screen. Specifically, the drawing unit 113 changes the display mode for each operation button so that if the operation button is to be hatched, it is displayed by hatching or other highlighting. If the operation button is to be hidden, the drawing unit 113 changes the display mode so that the operation button is not displayed, i.e., is made invisible. The drawing unit 113 also determines a display mode for each operation button using the button control information 121 and the screen information 122 and draws the display screen. More specifically, for an operation button included in a display screen whose display time is equal to or longer than a predetermined first threshold, the drawing unit 113 draws the display screen by highlighting the operation button if the number of times the operation button is operated is less than a predetermined second threshold. In this case, the first threshold varies depending on the usage time of the information processing device 100, and the second threshold varies depending on the total number of times the operation buttons included in the display screen to which the operation button belongs.

[0024] When the timer unit 114 receives a request, it starts timing and responds to the request by reporting the amount of time that has elapsed since the start of timing. When a predetermined period of time has elapsed, the timer unit 114 notifies the user that a predetermined period of time has elapsed.

[0025] The update unit 115 counts up the number of times an operation button is operated. Specifically, when an input to one of the operation buttons displayed on the display screen is accepted as a first operation, and a second operation for transitioning from the display screen to another screen different from the display screen is not accepted within a predetermined time, the update unit 115 counts up the number of times the operation associated with the operation button related to the first operation in the button control information.

[0026] Recently, in-vehicle information processing devices such as navigation systems have become more sophisticated, and as a result, the number of operation buttons on each operation screen tends to increase. However, an increase in the number of operation buttons can lead to a decrease in operability, posing a risk of reducing user convenience.

[0027] In view of the above, the information processing device 100 ensures user convenience by hiding unused operation buttons from the operation screen and also hiding operation buttons subordinate to them. Furthermore, by determining whether a user has performed an operation erroneously and not reflecting this in the operation history, the display of operation buttons is changed to more accurately reflect the user's usage status. Furthermore, since the criterion for whether an operation button is being used or not is dependent on other operation buttons on the same screen, it may be inappropriate to determine the criterion based only on the number of times a single operation button is operated. Therefore, it is considered more appropriate to vary the criterion depending on the user's usage behavior, and therefore it is better to reflect the operation status of other operation buttons on the same screen as the criterion.

[0028] 4 is a diagram showing an example of the hardware configuration of an information processing device. The information processing device 100 can be realized by a general information processing device including a processor (for example, a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit)) 101, a memory 102 such as a RAM (Random Access Memory), a storage device 103 such as a hard disk drive (HDD) or an SSD (Solid State Drive), a communication device 104 that serves as an interface for connecting communications via a network, a display 105, a touch panel 106, and a bus that connects these devices together.

[0029] The above-described functional units of the processing unit 110, namely, the input control unit 111, the display unit 112, the drawing unit 113, the timing unit 114, and the update unit 115, are constructed by the processor 101 reading and executing a predetermined program. Therefore, the memory 102 or the storage device 103 stores a program for realizing the processing of each functional unit. The program is then loaded into the memory 102 at the time of execution, and causes the processor 101 to perform the processing.

[0030] The button control information 121 and the screen information 122 are realized by the memory 102 or the storage device 103 .

[0031] 5 is a diagram showing an example of a processing flow of the operation status recording process. The operation status recording process is started when the information processing device 100 is activated to be operable. In this embodiment, since the information processing device 100 is an in-vehicle device, it is activated to be operable when the accessory power of the vehicle in which it is installed is turned on (ACC_ON).

[0032] First, the drawing unit 113 performs a drawing process (step S001), which will be described later. Specifically, the drawing unit 113 draws a screen corresponding to the screen ID of the currently displayed object according to the layout 122c, and arranges and draws buttons having operation button IDs included in the related buttons 122d. For the operation buttons, the drawing unit 113 determines the display mode by referring to the button control information 121 and draws them.

[0033] Then, the input control unit 111 determines whether a button operation has been performed (step S002). Specifically, the input control unit 111 determines whether an input has been made to an operation button on the screen, and whether the input has been a tap or a long tap, thereby determining whether a button operation has been performed.

[0034] If a button operation has been performed (if "Yes" in step S002), the update unit 115 determines whether or not an operation has been replaced within a predetermined time (for example, within 2 seconds) (step S003). Specifically, the update unit 115 obtains, via the input control unit 111, whether or not a tap or a long tap has been performed on an operation button different from the button operation detected in step S002. If a tap or a long tap has been performed on a different operation button, the update unit 115 determines that an operation has been replaced.

[0035] If there is no operation change ("No" in step S003), the update unit 115 counts up the operation button (step S004). Specifically, the update unit 115 counts up the operation button for which input was accepted in step S002, assuming that the operation button has been operated. Then, the drawing unit 113 returns control to step S001, and draws the screen to which the transition is made in response to the operation button.

[0036] If an operation has been replaced ("Yes" in step S003), the update unit 115 counts up the number of times the operation button has been replaced (step S005). Specifically, the update unit 115 counts up the number of times the operation button has been replaced, assuming that an operation has been performed on the replaced operation button. In other words, the update unit 115 assumes that the replaced operation button was an unintentional erroneous operation, and does not count up the number of times the operation button has been replaced. Then, the drawing unit 113 returns control to step S001, and draws the screen to which the screen will transition in response to the replaced operation button.

[0037] If no button operation has been performed ("No" in step S002), the update unit 115 determines whether or not a function is being executed (step S006). Specifically, the update unit 115 determines whether or not an output is being generated during activation of a predetermined function provided by the information processing device 100 (for example, a route guidance function, a video playback function, a music playback function, a tuner playback function, or other function provided to the user by a predetermined software program). If the function is not being executed ("No" in step S006), the drawing unit 113 returns control to step S002.

[0038] If a function is being executed (if "Yes" in step S006), the update unit 115 counts up all of the operation buttons that are the transition source of the current screen (step S007). This is because if a function is being executed, it is necessary to record that the operation buttons are being used regardless of the transition source by counting up all of the operation buttons that are the transition source in the same way.

[0039] Then, the update unit 115 determines whether or not shutdown of the information processing device 100 has started (step S008). If shutdown has not started ("No" in step S008), the drawing unit 113 returns control to step S001 and performs refresh drawing of the current screen.

[0040] If shutdown has been initiated ("Yes" in step S008), the update unit 115 performs a performance update process (step S009), which will be described later. Then, the update unit 115 ends the operation status recording process.

[0041] The above is the flow of the operation status recording process. According to the operation status recording process, when an operation is accepted for an operation button that involves a screen transition or a pop-up display, an operation history can be acquired while eliminating erroneous operations.

[0042] 6 is a diagram showing an example of a processing flow of the drawing processing. The drawing processing starts in step S001 of the operation status recording processing.

[0043] First, the drawing unit 113 acquires button control information and screen information (step S101). Specifically, the drawing unit 113 reads out the button control information 121 and the screen information 122.

[0044] Then, the drawing unit 113 identifies the buttons included in the display screen (step S102). Specifically, the drawing unit 113 reads out the button IDs of the operation buttons associated with the screen ID of the display target from the associated buttons 122d.

[0045] Then, the drawing unit 113 performs the processes of steps S104 to S107 for each of the operation buttons included in the display screen (steps S103 and S108).

[0046] The drawing unit 113 determines whether the non-display flag is set to "Y (Yes)" (step S104). Specifically, the drawing unit 113 refers to the button control information 121 and determines whether the value of the non-display 121d related to the target button ID 121a is "Y (Yes)". If the non-display flag is set to "Y (Yes)" (if "Yes" in step S104), the drawing unit 113 draws the operation button with a non-display attribute or does not display it, and proceeds to step S108 to set the next operation button as the target button.

[0047] If the non-display flag is set to "N (No)" ("No" in step S104), the drawing unit 113 determines whether the hatching flag is set to "Y (Yes)" (step S105). Specifically, the drawing unit 113 refers to the button control information 121 and determines whether the value of the hatching 121c related to the target button ID 121a is "Y (Yes)".

[0048] If the hatching flag is set to "N (No)" ("No" in step S105), the drawing unit 113 draws the operation button in a standard display mode (step S106). For example, the standard display mode is a default display mode that conforms to the layout information of the screen. Then, the drawing unit 113 advances the control to step S108 and sets the next operation button as the target button.

[0049] If the hatching flag is set to "Y (Yes)" ("Yes" in step S105), the drawing unit 113 draws the operation button in an emphasis display mode (step S107). For example, the emphasis display mode is a display mode in which the display of the operation button is changed to superimpose a figure in a hatched manner. Note that this is not limited to this, and for example, the saturation of the display color may be reduced. Then, the drawing unit 113 advances the control to step S108 and sets the next operation button as the target button.

[0050] Then, the timing unit 114 starts timing the display time of the display screen (step S109).

[0051] The above is the flow of the drawing process. According to the drawing process, when drawing the screen, operation buttons that are to be hatched in the button control information 121 can be drawn as hatched, and operation buttons that are to be hidden can be drawn as hidden.

[0052] 7 is a diagram showing an example of the process flow of the performance update process, which starts in step S009 of the operation status recording process.

[0053] First, update unit 115 determines whether the tallying period has elapsed (step S201). Specifically, update unit 115 requests date and time information from clock unit 114 and determines whether a predetermined tallying period (for example, one week) has elapsed since the start of the current tallying period. If the tallying period has not elapsed ("No" in step S201), update unit 115 advances control to step S203.

[0054] If the counting period has elapsed (if "Yes" in step S201), the update unit 115 clears the screen display time and the button operation count for the previous period (step S202). Specifically, the update unit 115 clears the operation count 121b of the button control information 121 to zero, and clears the display record time 122b of the screen information 122 to zero.

[0055] Then, the update unit 115 sums up the screen display times for a predetermined period (step S203). Specifically, the update unit 115 sums up the screen display times for each display screen for the current aggregation period, and stores the sum in the actual display time 122b.

[0056] Then, the update unit 115 selects buttons to be hidden from the hatched buttons (step S204). Specifically, the update unit 115 extracts operation buttons for which the value of hatching 121c of the button control information 121 is "Y (Yes)" and the value of hidden 121d is "N (No)", and further sets, as hidden buttons, operation buttons for which the display screens to which the extracted operation buttons belong are "frequently displayed screens". Specifically, the update unit 115 determines that a display screen that satisfies the following condition (1) is a "frequently displayed screen".

[0057] Condition (1) The actual display time 122b of the target display screen for one week is 10% or more of the cumulative time from "ACC_ON" to "ACC_OFF" (i.e., approximately from getting on to getting off) for the same period.

[0058] Then, when an operation button belonging to a display screen that satisfies the above condition (1) is extracted, the update unit 115 further sets the non-display 121d of the operation button to "Y (Yes)" if the operation button is an operation button that is not "frequently operated." Specifically, the update unit 115 determines whether the operation count 121b of the operation button satisfies the following condition (2), and if so, determines that the operation button is not "frequently operated." Note that the above condition (1) is not limited to this, and the following condition (1') may also be used. Condition (1'): The actual display time 122b of the target display screen for one week is 10% or more of the cumulative time of "parking brake off" (i.e., approximately from departure to stop) for the same period.

[0059] Condition (2) The operation button is less than half the total average of the operation count 121b of other buttons belonging to the display screen to which the operation button belongs.

[0060] Then, the update unit 115 selects a button to cancel hatching from the hatched buttons (step S205). Specifically, the update unit 115 extracts operation buttons for which the value of hatching 121c of the button control information 121 is "Y (Yes)" and the value of non-hatching 121d is "N (No)", and further sets the hatching 121c of the extracted operation button to "N (No)" for the operation button that has been operated at least once during the current aggregation period.

[0061] Then, the update unit 115 selects buttons to be hatched from the buttons that are not to be hatched (step S206). Specifically, the update unit 115 extracts operation buttons for which the value of the hatching 121c of the button control information 121 is "N (No)" and the value of the non-display 121d is "N (No)", and further sets the hatching 121c of the operation button to "Y (Yes)" for the operation button that satisfies the above conditions (1) and (2).

[0062] The above is the flow of the performance update process. The performance update process can update the information necessary to draw operation buttons that meet predetermined criteria as hatched or hidden when drawing the screen. In order to make hidden buttons displayable again, a reset button for clearing both the hatched 121c and hidden 121d values to "N (No)" can be provided on the top screen or setting screen of the menu (not shown), thereby returning the display state of the operation buttons to their initial state.

[0063] 8 is a diagram showing an example of the display form of operation buttons. In an initial screen display 400, address search 401, phone search 402, and name search 403 are displayed as operation buttons. If address search 401 and name search 403 are unused (no operation) during the collection period, then in the collection period one period later, the unused operation buttons are displayed as hatched address search 411 and hatched name search 413, as shown in screen display 410 after one period has passed. If hatched address search 411 is used and hatched name search 413 is not subsequently used, then in the collection period two periods later, address search 401 and phone search 402 will be displayed normally, and the unused name search operation button will be hidden, as shown in screen display 420 after two periods have passed.

[0064] Fig. 9 is a diagram showing an example of counting operation buttons. In steps S003 to S005 of the operation status recording process, if there is an operation instruction to transition to another screen within a predetermined time before the screen transition, it is determined that "an operation change has occurred within the predetermined time." This situation will be specifically described with reference to Fig. 9.

[0065] 9, as in FIG. 8, it is assumed that address search 401, phone search 402, and name search 403 are displayed as operation buttons on screen display 400 in the initial state. In a situation where the operation button for address search 401 is touched on screen display 400, and then, within 2 seconds (when no screen transition has occurred yet), the operation button for name search 403 is touched subsequently, resulting in transition to screen 450 for the name search function, the operation input to the operation button for address search 401 is not recorded (not counted), but the operation input to the operation button for name search 403 is recorded (counted). This corresponds to the case where an operation change has occurred in step S003 of the operation status recording process (if "Yes" is selected in S003), and the touch input to the operation button for address search 401 is considered to have been an erroneous operation.

[0066] Furthermore, the number of times an operation is performed may be counted up for an operation button, not limited to a touch input to an operation button, even when an operation is performed using a smartphone or the like as an input device. Specifically, when a smartphone or the like and the information processing device 100 are connected to each other so as to be able to communicate with each other via wire or wirelessly, if the information processing device 100 is provided with a function for automatically executing a function within the smartphone (music playback, etc.), the number of times an operation is performed may be counted up for an operation button that starts the corresponding function of the information processing device 100.

[0067] The above is an example of an embodiment of the present invention. According to the information processing device of this embodiment, it is possible to more appropriately manage the frequency of user operations and customize the screen to better suit the user's intentions. Furthermore, according to the information processing device of this embodiment, it is possible to hide buttons that are operated infrequently on a screen that is displayed frequently.

[0068] However, the present invention is not limited to the above-described embodiment, and various modifications can be made to the above-described embodiment within the scope of the technical concept of the present invention.

[0069] For example, in the operation status recording process shown in Fig. 5 of the above embodiment, if an operation is replaced within a predetermined time after a button operation is detected (after "Yes" in step S002) and before a screen transition, the count of the operation button is incremented for the replaced operation button, but this is not limited to this. For example, if, within the predetermined time after a screen transition, the user returns to the display screen before the transition or performs another function in the same category (for example, starting a tuner playback function from a music playback function in the audio category), the other function or the screen to which the user returned may be treated as the execution of the function intended by the user.

[0070] That is, when the update unit 115 receives an input to one of the operation buttons displayed on a first display screen as a first operation, if the update unit 115 does not receive a second operation for transitioning to a screen different from the second display screen, which is a transition destination of the first operation, within a predetermined time, the update unit 115 may count up the number of operations associated with the operation button related to the first operation in the button control information 121. Such a modified example will be described with reference to FIGS.

[0071] [Modification] Figure 10 shows a modification of the operation status recording process. The modification of the operation status recording process is basically the same as the operation status recording process, so the following description will focus on the differences.

[0072] Specifically, immediately after detecting an input to an operation button in step S002 (if "Yes" in step S002), the update unit 115 performs a drawing process on the display screen to which the screen is transitioned by the operation button (step S011). That is, the screen transition is performed.

[0073] Then, the update unit 115 determines whether or not there is a button operation for transitioning to another screen within a predetermined time (for example, within 2 seconds) after the display screen is displayed (step S012). Specifically, the update unit 115 acquires, via the input control unit 111, whether or not a tap or a long tap has been made on an operation button that activates an action involving a screen transition or a pop-up display. If a tap or a long tap has been made on a different operation button, the update unit 115 determines that there has been a button operation for transitioning to another screen.

[0074] If a button operation for transitioning to another screen has been performed ("Yes" in step S012), the update unit 115 counts up the operation button for transitioning to another screen (step S013). Specifically, the update unit 115 considers that an operation button for which a button operation for transitioning to another screen has been performed has been operated, and counts it. In other words, the update unit 115 considers that the operation button for which input was detected in step S002 was an unintended operation, and does not count up. Then, the drawing unit 113 returns control to step S001, and draws the screen to which transition is made by the operation button for transitioning to another screen.

[0075] If there is no button operation to transition to another screen within the predetermined time ("No" in step S012), the update unit 115 counts up the operation button (step S014). Specifically, the update unit 115 considers that the operation button for which input was accepted in step S002 has been operated, and counts it. Then, the drawing unit 113 returns the control to step S002 and accepts input to the operation button.

[0076] Also, unlike the first embodiment, in which shutdown has not been initiated in step S008 of the operation status recording process ("No" in step S008), the drawing unit 113 returns control to step S001 and performs refresh drawing of the current screen. That is, the drawing unit 113 returns control to step S002 and accepts input to the operation buttons (step S015).

[0077] The above is a modified example of the operation status recording process. According to this example of processing, if, within a predetermined time after a screen transition, the user returns to the display screen before the transition or performs another function in the same category (for example, starting a tuner playback function from a music playback function in the audio category), the other function or the screen to which the user returned can be treated as the execution of the function intended by the user.

[0078] Fig. 11 is a diagram showing another example of counting operation buttons. Specifically, in steps S012 to S014 of the operation status recording process in another example of the operation status recording process, if there is an operation instruction to transition to another screen within a predetermined time after a screen transition, it is determined that "a button operation to transition to another screen has been performed." This situation will be specifically described using Fig. 11.

[0079] 11, it is assumed that operation buttons for music playback 501, tuner 502, and video playback 503 are displayed on screen display 500. In a situation where a touch input is made to the operation button for music playback 501 on screen display 500, and then, two seconds after music playback display screen 510 is displayed, an operation button for tuner 515 that activates a tuner screen is subsequently touched, resulting in a transition to tuner screen 520, the operation input to the operation button for music playback 501 is not recorded (counted), but the operation input to the operation button for tuner 515 is recorded (counted). This corresponds to the case where a button operation for transitioning to another screen has been performed in step S012 of the operation status recording process of the modified example (if "Yes" in S012), and the touch input to the operation button for music playback 501 is deemed to have been an unintended operation.

[0080] The above is a modified example of an embodiment of the present invention. The information processing device according to this modified example allows for more appropriate management of a user's operation frequency and allows for screen customization that better matches the user's intentions. Furthermore, even if another function is activated within a predetermined time after a screen transition, the operation frequency can be appropriately detected. In other words, the information processing device according to this modified example can be said to include: a display unit that displays a display screen having one or more operation buttons; a memory unit that stores button control information including, for each operation button, a record of the number of times the operation button is operated; a drawing unit that uses at least the button control information to determine a display form for each operation button and draws the display screen; and an update unit that, when accepting an input to one of the operation buttons displayed on a first display screen as a first operation, counts up the number of operations associated with the operation button associated with the first operation in the button control information if a second display screen transitioned to by the first operation does not accept a second operation to transition to a screen different from the second display screen within a predetermined time.

[0081] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in memory, a recording device such as a hard disk or SSD, or a recording medium such as an IC card, SD card, or DVD.

[0082] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0083] 100: information processing device, 110: processing unit, 111: input control unit, 112: display unit, 113: drawing unit, 114: timing unit, 115: update unit, 120: storage unit, 121: button control information, 122: screen information.

Claims

1. a display unit that displays a display screen having one or more operation buttons; a storage unit that stores button control information including a record of the number of times the operation button is operated for each of the operation buttons; a drawing unit that uses at least the button control information to determine a display form for each of the operation buttons and draws the display screen; an updating unit that, when accepting an input to one of the operation buttons displayed on the display screen as a first operation, counts up the number of operations associated with the operation button related to the first operation in the button control information if a second operation for transitioning from the display screen to a screen different from the display screen is not accepted within a predetermined time, and counts up the number of operations associated with the operation button related to the second operation in the button control information if a second operation for transitioning from the display screen to a screen different from the display screen is accepted within a predetermined time; An information processing device comprising:

2. 2. The information processing device according to claim 1, The operation button is a button that, when it receives an input, activates an operation involving a screen transition or a pop-up display.

1. An information processing device comprising:

3. 3. The information processing device according to claim 1, a display unit that displays a display screen having one or more operation buttons; a storage unit that stores button control information including a record of the number of times the operation button is operated for each of the operation buttons; a drawing unit that uses at least the button control information to determine a display form for each of the operation buttons and draws the display screen; an update unit that, when accepting an input to one of the operation buttons displayed on the display screen as a first operation, counts up the number of operations associated with the operation button related to the first operation in the button control information if a second operation for transitioning from the display screen to a screen different from the display screen is not accepted within a predetermined time; Equipped with the storage unit stores screen information including a record of the display time of the display screen for each of the display screens; the drawing unit uses the button control information and the screen information to determine a display form for each of the operation buttons and draws the display screen.

1. An information processing device comprising:

4. 4. The information processing device according to claim 3, the drawing unit draws the display screen with the operation button highlighted when the number of times the operation button has been operated falls below a predetermined second threshold, for the operation button on the display screen whose display time is equal to or longer than a predetermined first threshold; 1. An information processing device comprising:

5. 5. The information processing device according to claim 4, the first threshold value varies depending on the usage time of the information processing device; 1. An information processing device comprising:

6. 6. The information processing device according to claim 4, the second threshold value varies depending on the total number of times the operation button is operated that is included in the display screen to which the operation button belongs; 1. An information processing device comprising:

Images