Information processing device, average exercise amount calculation method, and display system

Abstract

According to the present invention, a storage unit stores exercise information every day for a prescribed period of time, the exercise information including the day of every instance of exercise done by a user, exercise amounts, and the days on which exercise was not done. A first calculation unit calculates a first average exercise amount per instance of exercise on the basis of an exercise amount for the prescribed period of time. A second calculation unit counts the number of instances of exercise for each interval obtained by dividing the prescribed period of time by a prescribed number of days and, on the basis of the number of instances of exercise in valid intervals found by removing intervals for which the number of instances of exercise is zero from the intervals, calculates the average number of instances of exercise per valid interval. A third calculation unit calculates a second average exercise amount per valid interval on the basis of the first average exercise amount and the average number of instances of exercise. A display control unit performs control for displaying the second average exercise amount.

Description

Information processing device, average training volume calculation method, and display system

[0001] The present disclosure relates to an information processing device, an average training amount calculation method, and a display system.

[0002] Users who train may collect and store the amount of training they have performed and use this information to understand their training status. For example, a user who runs may use a sensor device or a running app installed on their smartphone to collect and store data such as running distance and use this information to understand their training status. Average training volumes, such as average monthly and weekly training volumes, are useful for understanding the status of training. Furthermore, by comparing the average training volume with other users, the training status can be compared relatively, which is useful for understanding the user's ability and improving motivation for training.

[0003] Patent Document 1 discloses an invention in which exercise data relating to multiple individuals is collected at a central location and then displayed to a user at a desired remote location.

[0004] Japanese Patent Application Laid-Open No. 2017-217475

[0005] However, a user's training frequency may temporarily decrease due to reasons such as a temporary busy schedule at work that prevents them from finding sufficient time to train, poor health, or injury. When the training frequency decreases, the average training volume decreases. This decreased average training volume may not correspond to the user's actual ability.

[0006] However, the invention disclosed in Patent Document 1 cannot calculate an average training amount corresponding to the user's ability even if the training frequency temporarily decreases.

[0007] In one aspect, an object is to calculate an average training volume corresponding to the user's ability even when the user's training frequency temporarily drops.

[0008] An information processing device according to one aspect of the present disclosure includes a storage unit, a first calculation unit, a second calculation unit, a third calculation unit, and a display control unit. The storage unit stores training information for each day over a predetermined period, including training dates for each training session performed by a user during that day, the training volumes performed on those training dates, and non-training days on which the user did not train. The first calculation unit calculates a first average training volume, which is the average training volume per training session, based on the training volumes included in the predetermined period. The second calculation unit counts the number of training sessions on each interval day obtained by dividing the predetermined period into predetermined number of days, and calculates the average number of training sessions per valid interval day based on valid interval days, which are interval days excluding interval days with zero number of training sessions, and the number of training sessions performed on those valid interval days. The third calculation unit calculates a second average training volume, which is the average training volume per valid interval day, based on the first average training volume and the average number of training sessions. The display control unit controls the display unit to display the second average training volume as a graph.

[0009] According to one aspect of the embodiment, even if the frequency of the user's training temporarily decreases, it is possible to calculate an average training volume that corresponds to the user's ability.

[0010] FIG. 1 is a diagram illustrating an example of a schematic configuration of a display system according to an embodiment. FIG. 2 is a diagram illustrating an example of a functional configuration of a server according to an embodiment. FIG. 3 is a diagram illustrating an example of an implementation date and time, a traveled distance, and a running distance stored in basic information according to an embodiment. FIG. 4 is a diagram illustrating an example of training information according to an embodiment. FIG. 5 is a diagram illustrating an example of a dashboard screen according to an embodiment. FIG. 6A is an enlarged view of a third graph display area portion of a dashboard screen according to an embodiment. FIG. 6B is an enlarged view of the third graph display area portion of a dashboard screen according to an embodiment. FIG. 7A is a diagram illustrating another example of a display of the third graph display area of ​​a dashboard screen according to an embodiment. FIG. 7B is a diagram illustrating another example of a display of the third graph display area of ​​a dashboard screen according to an embodiment. FIG. 8 is a diagram illustrating a flow of calculating an average running distance per valid period according to an embodiment. FIG. 9 is a flowchart illustrating a flow of an average training amount calculation process according to an embodiment. FIG. 10A is a diagram illustrating another example of a display of the third graph display area portion of a dashboard screen according to an embodiment. FIG. 10B is a diagram illustrating another example of a display of the third graph display area portion of a dashboard screen according to an embodiment. FIG. 11 is a diagram illustrating an example of calculating an average running distance according to another embodiment. FIG. 12 is a diagram illustrating an example of a hardware configuration of a server according to an embodiment.

[0011] [Embodiments] Hereinafter, embodiments of an information processing device, an average training amount calculation method, and a display system according to the present disclosure will be described in detail with reference to the drawings. Note that the present disclosure is not limited to these embodiments. In the embodiments described below, identical or common parts are designated by the same reference numerals, and their description will not be repeated.

[0012] In the following embodiment, a case where the training is running will be mainly described as an example.

[0013] One of the purposes of this embodiment is to calculate an average training amount that corresponds to the user's ability even if the user's training frequency temporarily decreases.

[0014] [System Configuration] First, a display system 10 including an information processing device according to the present disclosure will be described. The display system 10 is a system that collects and stores information related to training performed by a user and provides the user with various types of information related to the training. Fig. 1 is a diagram illustrating an example of a schematic configuration of the display system 10 according to an embodiment. The display system 10 includes a server 11, a first user terminal 12, and a second user terminal 13. In this embodiment, the server 11 corresponds to the information processing device according to the present disclosure.

[0015] The server 11, the first user terminal 12, and the second user terminal 13 are communicatively connected to a network N. One aspect of the network N may be any type of communication network, whether wired or wireless, such as a mobile communication network such as a mobile phone, the Internet, a local area network (LAN), or a virtual private network (VPN). In the example of FIG. 1 , a base station N1 of a mobile communication network is provided in the network N. The first user terminal 12 is communicatively connected to the network N via the base station N1 by mobile communication. Note that the example of FIG. 1 illustrates a case where one first user terminal 12 is provided, but this is not limiting, and any number of first user terminals 12 may be provided.

[0016] The server 11 is a device that provides a web (World Wide Web) service that provides various types of information related to running to the user. The server 11 is, for example, an information processing device such as a server computer. The server 11 may be implemented as a single computer, or may be implemented by multiple computers. In this embodiment, the server 11 will be described as a single computer. The web service provided by the server 11 can be used by registering an account including a user ID (identification) and a password.

[0017] The first user terminal 12 is, for example, a mobile communication terminal such as a smartphone owned by a user. The second user terminal 13 is, for example, an information processing device such as a notebook computer or a tablet terminal owned by a user.

[0018] The user operates the first user terminal 12 or the second user terminal 13 to access the web service of the server 11 and registers an account including a user ID and a password with the web service. The user installs an integrated app that links with the web service on the first user terminal 12 and registers the web service account with the installed integrated app.

[0019] A user owns a sensor device 14. The sensor device 14 has various built-in sensors such as a GPS (Global Positioning System) and a motion sensor, and is capable of measuring position, acceleration in three axial directions, and angular velocity in three axial directions. The sensor device 14 is connected to the first user terminal 12 via a short-range wireless line such as Bluetooth (registered trademark), and is capable of communicating with the first user terminal 12. Various operations, including starting and stopping recording, can be performed on the sensor device 14 using buttons provided on the main body or an associated app on the first user terminal 12.

[0020] When starting to run, the user operates the sensor device 14 to start recording, and then wears the sensor device 14 around their waist while running. When finishing running, the user operates the sensor device 14 to stop recording.

[0021] When a recording start operation is performed, the sensor device 14 starts measurements using various sensors, performs measurements using the various sensors at a predetermined measurement interval, and accumulates the measured measurement date and time, position, acceleration, angular velocity, and the like as measurement data. When a recording end operation is performed, the sensor device 14 ends measurements using the various sensors. The sensor device 14 considers the period from the start of recording to the end of recording as one run and individually stores the measurement data. When the sensor device 14 is able to communicate with the first user terminal 12, it transmits the measurement data to the first user terminal 12. The first user terminal 12 transmits the measurement data to the server 11 with the user ID of the registered account attached. Note that the user may carry the first user terminal 12 while running and collect and accumulate the measurement data using a link app installed on the first user terminal 12. The link app on the first user terminal 12 accumulates measurement data during running using the GPS, acceleration sensor, and gyro sensor equipped in the first user terminal 12 and transmits the measurement data to the server 11 with the user ID of the registered account attached.

[0022] The server 11 stores the measurement data received from the first user terminal 12 of each user in association with each user, and provides each user with various information related to running via a web service.

[0023] Each user accesses the server 11 and uses a web service using a first user terminal 12 and a second user terminal 13. The first user terminal 12 has a display unit 12a and displays various screens provided by the web service on the display unit 12a. The second user terminal 13 has a display unit 13a and displays various screens provided by the web service on the display unit 13a. The following mainly describes a case where a user uses the second user terminal 13 to use a web service as an example.

[0024] [Device Configuration] Next, an example of the functional configuration of the server 11 according to the embodiment will be described. Fig. 2 is a diagram schematically illustrating an example of the functional configuration of the server 11 according to the embodiment. The server 11 has a communication unit 20, a storage unit 21, and a control unit 22.

[0025] The communication unit 20 is a communication interface that communicates with the network N. The communication unit 20 transmits and receives various data to and from the first user terminal 12 via the network N.

[0026] The storage unit 21 is a storage device such as a hard disk, SSD (Solid State Drive), or optical disk that can store information. The multiple storage units 21 store various types of information. For example, the server 11 according to the embodiment includes the storage unit 21. The storage unit 21 is a storage device such as a hard disk, SSD, or optical disk. The storage unit 21 stores various types of information. For example, the storage unit 21 stores user information 30, a measurement data DB (DataBase) 31, basic information 32, form information 33, and training information 34. Note that the storage unit 21 may also store various other types of information. In this embodiment, the storage unit 21 corresponds to the storage unit of the present disclosure.

[0027] The user information 30 is data that stores various information about each user. The user information 30 stores, for each user, a user ID, a password, the user's name, and a marathon completion time. The marathon completion time is the time it takes to complete a marathon race covering a distance of 42.195 km. The marathon completion time may be entered by the user when registering an account, or may be obtained and registered from another system that stores the user's actual marathon completion time. Note that the marathon completion time is not required; for example, the marathon completion time may not be recorded in the user information 30 of a user who has never run a full marathon.

[0028] The measurement data DB 31 is a database that stores measurement data. For example, the measurement data DB 31 stores measurement data received for each user.

[0029] The basic information 32 is data that stores basic information about the running that has been performed. For example, the basic information 32 stores, for each user, the date and time of each run that the user performed, the distance traveled, the distance traveled, and the running pace.

[0030] The form information 33 is data that stores various evaluation values ​​related to the user's running form. The form information 33 stores various scores that evaluate the running form of each user while running.

[0031] The training information 34 is data that stores various information about the user's daily training for each user. For example, the training information 34 includes, for each user, the training dates for each training session the user performed during the day, the amount of training performed on each training session, and days on which the user did not perform any training. For example, the training information 34 stores the daily running distance for each user over a predetermined period of time. Details of the training information 34 will be described later.

[0032] The user information 30, basic information 32, form information 33, and training information 34 may be managed using a database.

[0033] The control unit 22 is a device that controls the entire server 11. The control unit 22 is, for example, a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). The control unit 22 has an internal memory for storing programs that define various processing procedures and control data, and executes various processes using these. The control unit 22 functions as various processing units when various programs run. For example, the control unit 22 has a storage unit 40, a first analysis unit 41, a second analysis unit 42, a generation unit 43, a display control unit 44, a reception unit 45, a first calculation unit 46, a second calculation unit 47, and a third calculation unit 48.

[0034] When the storage unit 40 receives the measurement data from the first user terminal 12, the storage unit 40 stores the measurement data in the measurement data DB 31 in association with the user ID added to the received measurement data.

[0035] The first analysis unit 41 analyzes the measurement data received from the first user terminal 12 and derives various pieces of information related to running. For example, the first analysis unit 41 analyzes the measurement data and derives the user's movement distance and running distance in one run.

[0036] Here, an example of the flow of the first analysis unit 41 deriving the travel distance and the running distance through analysis will be described.

[0037] The measurement data includes the measurement date and time, position, acceleration, and angular velocity of one run. The first analysis unit 41 determines whether the user is running or walking based on the acceleration and angular velocity. In a running state, there is a floating state in the air, where neither the right nor left foot touches the ground. On the other hand, in a walking state, either the right or left foot touches the ground, and there is no floating state. The first analysis unit 41 analyzes the acceleration and angular velocity along the time series of the measurement date and time to determine whether a floating state has occurred. If a floating state occurs within a certain period of time, the first analysis unit 41 determines that the user is running, and if there is no floating state, the first analysis unit 41 determines that the user is walking. The certain period of time is set to, for example, approximately 1 to 10 seconds, and is a time suitable for determining whether the user is running. Note that the above-described method for determining whether the user is running or walking is merely an example. The first analysis unit 41 may use other determination methods to determine whether the user is running or walking.

[0038] The first analysis unit 41 measures the distance traveled from the position information at each measurement date and time in accordance with the chronological order of the measurement date and time. In measurement data from a running session, there are successive periods of running in accordance with the chronological order of the measurement date and time. The first analysis unit 41 measures the distance traveled during periods determined to be running as the running distance in accordance with the chronological order of the measurement date and time.

[0039] The first analysis unit 41 identifies the date and time of running from the measurement date and time included in the measurement data. For example, the first analysis unit 41 identifies the earliest measurement date and time included in the measurement data as the date and time of running. The first analysis unit 41 also analyzes the measurement data to derive a running pace. For example, the first analysis unit 41 derives a running pace for each kilometer from the running time for each kilometer during running.

[0040] The first analysis unit 41 determines whether the user has temporarily run or has actually run based on whether the running distance is equal to or greater than a predetermined distance. The predetermined distance is set to, for example, approximately 100 m to 500 m, and is a distance appropriate for determining that the user has run. If the running distance is equal to or greater than the predetermined distance, the first analysis unit 41 determines that the user has run and stores the derived information in the basic information 32. For example, the first analysis unit 41 stores the date and time of the run, the distance traveled, the running distance, and the running pace in the basic information 32, in association with the user ID added to the analyzed measurement data. On the other hand, if the running distance is less than the predetermined distance, the first analysis unit 41 determines that the user has temporarily run and discards the derived information without storing it.

[0041] The basic information 32 stores, for each user, the running date and time, travel distance, running distance, and running pace for each run.

[0042] 3 is a diagram showing an example of the implementation date and time, travel distance, and running distance stored in the basic information 32 according to the embodiment. Fig. 3 shows an example of the implementation date and time, travel distance, and running distance of each run by a user. For example, in a record with the implementation date and time "20230716212304," the implementation date and time is 21:23:04 on July 16, 2023, the travel distance is 16,385 m, and the running distance is 16,371 m.

[0043] The second analysis unit 42 analyzes the measurement data determined by the first analysis unit 41 to be a case where running has been performed, and derives an evaluation value related to the running form. The evaluation value may be any value that can evaluate the running form. For example, the second analysis unit 42 analyzes acceleration and angular velocity along the time series of measurement dates and times, and derives a score related to the coordination of the entire body around the pelvis, a score related to the strength of movement, a score related to smooth center of gravity movement, a score related to left-right symmetry, a score related to stable posture, and a score related to low-stress ground contact.

[0044] The second analysis unit 42 stores the derived evaluation values ​​related to the running form in the form information 33. For example, the first analysis unit 41 stores in the form information 33 a score related to the coordination of the entire body around the pelvis, a score related to the strength of the movement, a score related to smooth movement of the center of gravity, a score related to left-right symmetry, a score related to stable posture, and a score related to low-stress ground contact, in association with the user ID added to the analyzed measurement data.

[0045] The generation unit 43 generates training information 34 based on the basic information 32. For example, the generation unit 43 reads, for each user, from the basic information 32, the date and time of each run and the distance traveled, which are associated with the user's user ID. The generation unit 43 identifies the date on which each run was performed based on the read date and time of each run and the distance traveled. The generation unit 43 then generates data in which the date and time of each run and the distance traveled are arranged in chronological order, along with dates other than the day on which the run was performed and distances set to zero. The generation unit 43 generates data for each user, associated with the user's user ID. The generation unit 43 stores the generated data for each user as training information 34 in the storage unit 21. The generation unit 43 generates training information 34 for each user, storing data on the days of runs performed during a predetermined period, and stores the generated training information in the storage unit 21. The predetermined period is the period of data used for running analysis. The predetermined period is determined according to the period for which running analysis is possible. For example, if analysis of runs over the past two years is possible, the predetermined period is determined to be two years.

[0046] FIG. 4 is a diagram showing an example of training information 34 according to an embodiment. FIG. 4 shows an example of the user's training information 34 for each day from April 30th to May 8th. In the training information 34, the dates from April 30th to May 8th are listed in the date field in order. The running date and time and the running distance are stored in association with the running date and time. If two runs are performed on the same day, the same date is listed twice. Furthermore, for dates other than the running days, the running date and time are left blank and the running distance is set to zero. Dates where the running date and time are left blank and the running distance is zero are non-running days.

[0047] The generation unit 43 periodically generates training information 34 for all users who use the web service from the basic information 32 and stores the generated training information 34 in the storage unit 21. For example, the generation unit 43 generates training information 34 from the basic information 32 every day and stores the generated training information 34 in the storage unit 21. As a result, the training information 34 is updated every day to the latest state that reflects the basic information 32. The storage unit 21 stores the latest training information 34 every day.

[0048] The display control unit 44 controls the display of various types of information. The display control unit 44 generates data for various types of screens, transmits the data to the first user terminal 12 and the second user terminal 13, and controls the display of various types of screens on the first user terminal 12 and the second user terminal 13.

[0049] The reception unit 45 receives various operations from various screens displayed on the first user terminal 12 and the second user terminal 13 under the control of the display control unit 44. The display control unit 44 controls the screens to be displayed on the first user terminal 12 and the second user terminal 13 in accordance with the various operations received by the reception unit 45.

[0050] For example, the display control unit 44 generates data for various screens of the web service in response to access from the first user terminal 12 and the second user terminal 13, transmits the generated screen data to the access source, and controls display of various screens on the access source. For example, the display control unit 44 displays a login screen on the access source, the second user terminal 13, in response to access from the second user terminal 13. Furthermore, when the reception unit 45 receives a login operation and the login is completed, the display control unit 44 displays the dashboard screen 100 on the second user terminal 13.

[0051] 5 is a diagram showing an example of a dashboard screen 100 according to the embodiment. The dashboard screen 100 is divided into a condition specification area 110 and a main display area 120.

[0052] The condition specification area 110 is provided with a period specification area 111 , a date input area 112 , a comparison target specification area 113 , and an update button 114 .

[0053] The period designation area 111 is an area for designating the number of days (interval days) for each of a plurality of periods for which the average mileage is to be calculated. The period designation area 111 is provided with a day button 111a, a week button 111b, and a month button 111c, and the number of days for a period can be designated using the day button 111a, the week button 111b, and the month button 111c. The day button 111a is a button for designating a period of one day. The week button 111b is a button for designating a period of seven days, which is one week. The month button is a button for designating a period of 30 days, which is one month.

[0054] The date input field 112 is an area for inputting a starting date that is the starting point of multiple periods for which the average mileage is to be calculated. If a date is input into the date input field 112, the input date is designated as the starting date, and if no date is input, the current date is designated as the starting date.

[0055] The comparison target designation area 113 is an area for designating a user to be compared. The comparison target designation area 113 has multiple check boxes 113a to 113f arranged vertically. Next to each of the check boxes 113a to 113f, "Sub" is displayed followed by a corresponding numerical value indicating the marathon completion time. For example, Sub 2.5 indicates that the marathon completion time is less than 2.5 hours (2 hours and 30 minutes), and is linked to the marathon completion time registered as user information 30.

[0056] Check box 113a is an area for specifying, as a comparison target, a user who will complete the marathon in less than two hours and 30 minutes. Check box 113b is an area for specifying, as a comparison target, a user who will complete the marathon in 2 hours and 30 minutes or more but less than three hours. Check box 113c is an area for specifying, as a comparison target, a user who will complete the marathon in 3 hours or more but less than 3 hours and 30 minutes. Check box 113d is an area for specifying, as a comparison target, a user who will complete the marathon in 3 hours and 30 minutes or more but less than four hours. Check box 113e is an area for specifying, as a comparison target, a user who will complete the marathon in 4 hours or more but less than 4 hours and 30 minutes. Check box 113f is an area for specifying, as a comparison target, a user who will complete the marathon in 4 hours and more but less than 5 hours.

[0057] Each of the check boxes 113a to 113f can be individually switched between a checked state and an unchecked state. A checked state of the check boxes 113a to 113f indicates a specified state, and an unchecked state indicates an unspecified state. For example, if the check box 113a for Sub2.5 is checked, only the information of users whose recorded marathon completion time in the user information 30 is less than 2 hours and 30 minutes can be displayed.

[0058] The update button 114 is a button for issuing an instruction to update the main display area 120 based on the conditions specified in the period specification area 111 , the date input area 112 , and the comparison target specification area 113 .

[0059] When the update button 114 is selected, the dashboard screen 100 according to the embodiment displays in the main display area 120 information about seven consecutive periods in the past, starting from the starting date specified in the date input area 112, with the number of days specified in the period specification area 111 being one period. For example, the example in FIG. 5 shows a case where the month button 111c in the period specification area 111 is selected and "2023 / 07 / 01" is entered in the date input area 112. The main display area 120 displays information about seven consecutive periods of 30 days in the past, starting from July 1, 2023, with one period being 30 days, equivalent to one month.

[0060] The main display area 120 is provided with a first graph display area 121 , a period-based information display area 122 , a second graph display area 123 , a radar chart display area 124 , and a third graph display area 125 .

[0061] In the first graph display area 121, the average running pace for each period is displayed as "pace" in graph 121a. The total running distance for each period is displayed as "running distance" in bar graph 121b. The first graph display area 121 also displays the change in the cumulative running distance, which is the sum of the running distances for each period in the order of the periods, as "cumulative distance" in graph 123c.

[0062] The period-specific information display area 122 displays, for each period, the number of times of running in each period, the highest running pace, the average running pace, the lowest running pace, the total distance traveled in the period, and the cumulative distance traveled in each period when the distance traveled throughout each period is accumulated.

[0063] The average values ​​of the evaluation scores for the running form within each period are displayed in a graph in the second graph display area 123. For example, the average values ​​of the score for the coordination of the whole body around the pelvis, the score for the strength of the movement, the score for the smooth shift of the center of gravity, the score for the symmetry of the left and right, the score for the stable posture, and the score for the low-stress landing within each period are displayed in a graph in the second graph display area 123.

[0064] The radar chart display area 124 displays, in the form of a radar chart, the average values ​​of the evaluation values ​​related to running form for each period. For example, the radar chart display area 124 displays, in the form of a radar chart, the average values ​​of the score related to whole-body coordination around the pelvis, the score related to strength of movement, the score related to smooth center of gravity movement, the score related to left-right symmetry, the score related to stable posture, and the score related to low-stress ground contact. The radar chart display area 124 is provided with a left button 124a and a right button 124b. The radar chart display area 124 allows the user to switch the period displayed on the radar chart using the left button 124a and the right button 124b.

[0065] The third graph display area 125 displays a graph of the average mileage calculated by averaging the mileage for each of seven consecutive periods from the starting date for the logged-in user and the comparison user specified in the comparison user specification area 113. The graph in the example of FIG. 5 displays the distribution of the ratio of the number of users for each average mileage using bars 125a, with the average mileage on the horizontal axis and the ratio (percentage) on the vertical axis. The example of FIG. 5 shows a case where the month button 111c in the period specification area 111 is selected to display the distribution of the ratio of the number of users for each average mileage for one month (30 days). The shape of the distribution of the ratio of the number of users changes little with changes in the number of users to be displayed in the graph. For example, the distribution of the ratio of the number of users can appropriately represent the distribution of users for each average mileage even when the number of users to be displayed in the graph is small.

[0066] This allows the user to easily understand the distribution of users by average mileage, regardless of the number of users for whom the graph is displayed. The server 11 can display the distribution of users by average mileage in a manner that allows the user to easily understand, regardless of the number of users for whom the graph is displayed.

[0067] The graph displayed in third graph display area 125 displays the position of the logged-in user's average mileage. In the example of Fig. 5, the position of the logged-in user's average mileage is displayed as "Your mileage."

[0068] This allows the user to understand their own ability from the position of their own average running distance within the distribution. The server 11 can display the position of the user's average running distance within the distribution so that the user can easily understand it. The user can understand their own training status from the position of their own average running distance within the distribution, which helps to increase their motivation for training. For example, if the user's own average running distance is relatively low in the distribution, the user can understand that other users are training more than the user and that they should increase their training, which can increase their motivation for running. Furthermore, if the user's own average running distance is relatively high in the distribution, the user can understand that the user is training sufficiently, which can increase their motivation for running.

[0069] 6A and 6B are enlarged views of the third graph display area 125 of the dashboard screen 100 according to the embodiment.

[0070] The pattern of the bars 125a of the graph changes for each user to be compared specified in the comparison target specification area 113, and the composition ratio of each user to be compared is displayed in a distinguishable manner. The third graph display area 125 displays, at the top, a pattern that corresponds to the user to be compared specified in the comparison target specification area 113.

[0071] In the third graph display area 125, when any bar 125a of the average running distance is selected, a balloon area 125b is displayed from the selected bar 125a as shown in Fig. 6B. The composition ratio of each user to be compared for the selected bar 125a is displayed in the balloon area 125b.

[0072] This allows the user to understand the composition ratio of each average mileage for each user being compared. The server 11 can display the composition ratio of each average mileage for each user being compared so that the user can easily understand it.

[0073] On the dashboard screen 100, the number of days for the period can be changed using a period specification area 111. Also, on the dashboard screen 100, the starting date can be changed using a date input area 112. Also, on the dashboard screen 100, the user to be compared can be changed using check boxes 113a to 113f in a comparison target specification area 113.

[0074] The reception unit 45 receives a specification of the number of days for the period in a period specification area 111. The reception unit 45 also receives a specification of a starting date in a date input area 112. The reception unit 45 also receives a specification of a user to be compared in check boxes 113a to 113f. The reception unit 45 receives an instruction to update the dashboard screen 100 by operating an update button 114. In this embodiment, the reception unit 45 corresponds to the first reception unit and the second reception unit of the present disclosure.

[0075] When the display control unit 44 accepts an operation of the update button 114, it updates the dashboard screen 100. The display control unit 44 treats the number of days specified in the period specification area 111 as one period and displays information about seven consecutive periods from the starting date specified in the date input area 112 in the first graph display area 121, the period-specific information display area 122, the second graph display area 123, and the radar chart display area 124. The display control unit 44 also displays a graph in the third graph display area 125 showing the distribution of average mileage, which is the average of the mileage for each of the seven consecutive periods from the starting date specified in the date input area 112.

[0076] 7A is a diagram showing another example of the display in the third graph display area 125 of the dashboard screen 100 according to the embodiment. FIG. 7A illustrates a case where the month button 111c in the period specification area 111 is selected to set one period to 30 days, and only the Sub3 checkbox 113b among the checkboxes 113a to 113f is checked, thereby setting the user to be compared to the Sub3 user. The period specification area 111 displays the distribution of the average mileage for one month (30 days) for the logged-in user and the Sub3 user using bars 125a. The period specification area 111 also displays the position of the logged-in user's average mileage for one month (30 days) as "Your Mileage."

[0077] 7B is a diagram showing another example of the display in the third graph display area 125 of the dashboard screen 100 according to the embodiment. FIG. 7B illustrates a case where the week button 111b in the period specification area 111 is selected to set one period to seven days, and only the Sub4 check box 113d among the check boxes 113a to 113f is checked, thereby setting the user to be compared to the Sub4 user. The period specification area 111 displays the distribution of the average mileage over one week (7 days) for the logged-in user and the Sub4 user using bars 125a. The period specification area 111 also displays the position of the logged-in user's average mileage over one week (7 days) as "Your Mileage."

[0078] However, for example, if a user's running frequency temporarily decreases due to a temporary busy schedule at work, the average running distance decreases. This decreased average running distance may not correspond to the user's actual running ability.

[0079] Therefore, in this embodiment, the average travel distance is calculated as follows.

[0080] The first calculation unit 46 calculates the average running distance per running session from the running distances of each of the seven consecutive running periods from the specified starting date based on the training information 34 .

[0081] The second calculation unit 47 counts the number of times running occurred in each of the seven periods. The second calculation unit 47 determines the period, excluding any period in which the number of times running occurred zero, as a valid period, and calculates the average number of times running occurred per valid period based on the number of times running occurred during the valid period. For example, the second calculation unit 47 identifies, among the seven periods, a period in which the number of times running occurred is one or more as a valid period. The second calculation unit 47 calculates the average number of times running occurred per valid period from the number of times running occurred during the identified valid period among the seven periods.

[0082] The third calculation unit 48 calculates the average running distance per valid period based on the average running distance per running session calculated by the first calculation unit 46 and the average number of running sessions per valid period calculated by the second calculation unit 47. For example, the third calculation unit 48 calculates the average running distance per valid period by multiplying the average running distance per running session by the average number of running sessions per valid period.

[0083] The first calculation unit 46 uses the user information 30 to identify the user ID of the user to be compared, which is specified in the comparison target designation area 113. In this embodiment, the first calculation unit 46 identifies the user ID of a user who satisfies the marathon completion time condition specified in the check boxes 113a to 113f. The first calculation unit 46 reads data corresponding to the user IDs of the logged-in user and the compared user from the training information 34, and calculates the average running distance per running session for each of the logged-in user and the compared user. The second calculation unit 47 calculates the average number of runs per valid period for each of the logged-in user and the compared user. The third calculation unit 48 calculates the average running distance per valid period for each of the logged-in user and the compared user.

[0084] The display control unit 44 controls the display of each user's average mileage per valid period as a graph in the third graph display area 125 of the dashboard screen 100, and displays the position of the logged-in user's average mileage per valid period.

[0085] Here, an example of calculating the average running distance per valid period will be described in brief. FIG. 8 is a diagram illustrating the flow of calculating the average running distance per valid period according to an embodiment. FIG. 8 illustrates an example in which one period is seven days (one week), and the average running distance is calculated for seven consecutive seven-day periods. In FIG. 8, the seven consecutive seven-day periods are shown as Week 1 to Week 7. FIG. 8 shows an example of the number of runs, which is the number of times a user ran from Week 1 to Week 7, and the running distance per week. The user's running frequency varies, and the number of runs in Weeks 3 and 5 is zero.

[0086] The first calculation unit 46 calculates the average distance traveled per running session over seven periods (weeks 1 to 7). In the example of FIG. 8 , the total number of runs over weeks 1 to 7 is 21 (= 4 + 8 + 0 + 1 + 0 + 2 + 6). The total distance traveled over the runs over weeks 1 to 7 is 96 km (= 12 + 32 + 0 + 10 + 0 + 12 + 30). Therefore, the average distance traveled per running session is calculated to be 4.57 km / session (= 96 / 21).

[0087] The second calculation unit 47 counts the number of times running occurred in each of the seven periods (weeks 1 to 7). The second calculation unit 47 determines the period, excluding any period in which the number of times running occurred, as the valid period. In the example of FIG. 8 , the number of times running occurred in weeks 3 and 5 is zero, so weeks 1, 2, 4, 6, and 7 are determined as the valid period. The second calculation unit 47 calculates the average number of times running occurred per valid period based on the number of times running occurred during the valid period. In the example of FIG. 8 , the total number of times running occurred during weeks 1, 2, 4, 6, and 7 is 21 (= 4 + 8 + 1 + 2 + 6). There are five valid periods. Therefore, the number of times running occurred during the valid period is calculated to be 4.2 (= 21 / 5).

[0088] The third calculation unit 48 calculates the average running distance per valid period based on the average running distance per running session (4.57 km / session) calculated by the first calculation unit 46 and the average number of running sessions per valid period calculated by the second calculation unit 47. Specifically, the third calculation unit 48 calculates the average running distance per valid period by multiplying the average running distance per running session by the average number of running sessions per valid period. In the example of Fig. 8, the average running distance per valid period is calculated to be 19.2 km (= 4.57 x 4.2).

[0089] A comparative example will now be described. In this comparative example, the average running distance over seven periods (weeks 1 to 7) is calculated. The average number of runs over weeks 1 to 7 is three (= 21 / 7). In this comparative example, the average running distance over weeks 1 to 7 is calculated as 13.7 km (= 4.57 x 3) from the average running distance per run (4.57 km / run) and the average number of runs over weeks 1 to 7.

[0090] The calculation method of the comparative example includes the third and fifth weeks in which the number of runs is zero, resulting in a lower average running distance. This lowered average running distance may not correspond to the user's actual ability.

[0091] On the other hand, the calculation method of this embodiment can calculate an average running distance that corresponds to the user's ability even if the user's running frequency temporarily decreases because the user is unable to train for a certain period of time due to various reasons such as injury or poor health. For example, the calculation method of this embodiment can calculate an average running distance that corresponds to the user's ability from weeks 1, 2, 4, 6, and 7, even if the training frequency temporarily decreases and the number of runs in weeks 3 and 5 becomes zero, as shown in Figure 8.

[0092] [Average Training Amount Calculation Process] Next, the flow of the average training amount calculation process for calculating and displaying an average training amount will be described with reference to Fig. 9. Fig. 9 is a flowchart showing the flow of the average training amount calculation process according to the embodiment. The average training amount calculation process according to the embodiment is executed when the update button 114 on the dashboard screen 100 is operated. Note that the following mainly describes the process for controlling the display of the third graph display area 125 on the dashboard screen 100.

[0093] The reception unit 45 receives the specification of various conditions from the condition specification area 110 of the dashboard screen 100 (step S10). For example, the reception unit 45 receives the specification of the number of days for the period (interval days) from the period specification area 111. The reception unit 45 also receives the specification of a starting date from the date input area 112. The reception unit 45 also receives the specification of users to be compared from the checkboxes 113a to 113f.

[0094] The first calculation unit 46 calculates the average distance traveled per running session for seven consecutive periods from the specified starting date, with the specified number of days (interval days) as one period, based on the training information 34 (step S11). The first calculation unit 46 calculates the average distance traveled per running session for each user, for the logged-in user and the specified comparison users.

[0095] The second calculation unit 47 counts the number of times of running in each of the seven periods, determines the period remaining after excluding the period in which the number of times of running was zero from the seven periods as the valid period, and calculates the average number of times of running per valid period based on the number of times of running performed during the valid period (step S12). The second calculation unit 47 calculates the average number of times of running per valid period for each user, for the logged-in user and the comparison user.

[0096] The third calculation unit 48 calculates the average running distance per valid period based on the average running distance per running session calculated by the first calculation unit 46 and the average number of running sessions per valid period calculated by the second calculation unit 47 (step S13). The third calculation unit 48 calculates the average running distance per valid period for each user, including the logged-in user and the comparison user.

[0097] The display control unit 44 displays the average mileage per valid period of each user as a graph in the third graph display area 125 of the dashboard screen 100, and controls to display the position of the average mileage per valid period of the logged-in user (step S14), and then ends the processing.

[0098] Other Embodiments In the above embodiment, the third graph display area 125 displays the distribution of the ratio of the number of users as a graph. However, the technology of the present disclosure is not limited to this example. The graph may be any graph related to the average mileage. For example, the graph may be a graph of the distribution of the number of users for each average mileage, or a graph of the distribution based on the probability density for each average mileage. FIG. 10A is a diagram illustrating another example of the display of the third graph display area 125 of the dashboard screen 100 according to the embodiment. FIG. 10A illustrates a case in which the display control unit 44 controls the display of the distribution of the number of users as a graph in the third graph display area 125. The graph in the example of FIG. 10A displays the distribution of the number of users for each average mileage using bars 125c, with the average mileage on the horizontal axis and the number of users on the vertical axis. The graph displays the positions of the average mileage of logged-in users. This allows the user to easily understand the distribution of the number of users for each average mileage. The server 11 can display the distribution of the number of users for each average mileage in a manner that allows the user to easily understand the distribution of the number of users for each average mileage. FIG. 10B illustrates another example of the display of the third graph display area 125 of the dashboard screen 100 according to the embodiment. FIG. 10B illustrates a case in which the display control unit 44 performs control to estimate a probability density for each average mileage from the number of users for each average mileage using kernel density estimation and display the probability density for each average mileage as a graph in the third graph display area 125. The graph in the example of FIG. 10B displays the distribution of the probability density for each average mileage as a curve 125d, with the average mileage on the horizontal axis and the probability density on the vertical axis. Kernel density estimation estimates the probability density for each average mileage as a continuous distribution, so that a reasonable probability density can be estimated even for average mileages where the number of users is zero. This allows the user to understand the percentage of users for each average mileage. For example, the user can understand the percentage of users for average mileages where the number of users was actually zero. The server 11 can display the percentage of users for each average mileage so that the user can easily understand the percentage of users.

[0099] In the above embodiment, an example has been described in which a graph of average mileage is displayed in the third graph display area 125 of the dashboard screen 100. However, the technology of the present disclosure is not limited to this. The screen that displays the graph of average mileage may have any screen configuration.

[0100] In the above embodiment, the period specification area 111 is provided with a day button 111a, a week button 111b, and a month button 111c, and the number of days in the period (interval days) is specified as 1, 7, or 30 days. However, the technology disclosed herein is not limited to this. The number of days in the period may be specified as any number of days.

[0101] In the above embodiment, an example has been described in which information about seven consecutive past periods starting from a starting date is displayed on the dashboard screen 100. However, the technology of the present disclosure is not limited to this. The number of periods may be changeable. For example, the number of periods may be specified as a natural number equal to or greater than two. The number of periods may also vary depending on the number of days in the period. For example, consecutive past periods may be defined by dividing a specific period into ranges that satisfy a specified number of days.

[0102] Here, an example of calculating an average running distance will be described. FIG. 11 is a diagram illustrating an example of calculating an average running distance according to another embodiment. FIG. 11 shows training information 34 for each day from April 30th to May 8th for the user shown in FIG. 4. FIG. 11 shows ranges A to D for the period from April 30th to May 8th, with the number of days (interval days) in the period being 1 to 4 days, and the dates being divided into days. Range A shows the periods from April 30th to May 8th divided into one-day intervals. Range B shows the periods from April 30th to May 8th divided into two-day intervals. Range C shows the periods from April 30th to May 8th divided into three-day intervals. Range D shows the periods from April 30th to May 8th divided into three-day intervals. The periods are determined by dividing April 30th to May 8th into ranges that satisfy the number of days: 1, 2, 3, and 4 days.

[0103] For example, assuming that the number of days in a period is one day, and the average daily running distance from April 30th to May 8th is to be calculated, the first calculation unit 46 calculates the average running distance per running session from April 30th to May 8th. In the example of FIG. 11 , the total running distance of the five running sessions from April 30th to May 8th is 60,900 m, so the average running distance per session is calculated as 12,180 m / session (= 60,900 / 5). The second calculation unit 47 defines the valid period as the period shown in range A excluding periods with zero running sessions, and calculates the average number of running sessions per valid period based on the number of running sessions performed during the valid period. In the example of FIG. 11 , the valid periods are May 8th, May 4th, May 2nd, and April 30th, each of which has a running session count of one or more. The total number of running sessions in the four valid periods is five (= 1 + 1 + 2 + 1). Therefore, the average number of running sessions per valid period is calculated as 1.25 (= 5 / 4). The third calculation unit 48 calculates the average daily running distance by multiplying the average running distance per running session by the average number of running sessions per valid period. In the example of Fig. 11, the average daily running distance is calculated to be 15,225 m (= 12,180 x 1.25).

[0104] For example, if the period is two days long and the two-day average running distance from April 30th to May 8th is to be calculated, the first calculation unit 46 calculates the average running distance per running session from April 30th to May 8th. The average running distance per session is calculated to be 12,180 m. The second calculation unit 47 defines the valid period as the period shown in range B, excluding periods with zero running counts, and calculates the average number of runs per valid period based on the number of runs performed during the valid period. In the example of FIG. 11 , the valid periods are May 8th to May 7th, May 4th to May 3rd, and May 2nd to May 1st, each of which has a running count of one or more. The total number of runs in the three valid periods is four (= 1 + 1 + 2). Therefore, the average number of runs per valid period is calculated to be 1.33 (≒ 4 / 3). The third calculation unit 48 calculates the two-day average running distance by multiplying the average running distance per running session by the average number of runs per valid period. In the example of FIG. 11, the average distance traveled over two days is calculated to be 16,199.4 m (= 12,180 x 1.33).

[0105] For example, if the period is three days long and the average running distance over three days from April 30th to May 8th is to be calculated, the first calculation unit 46 calculates the average running distance per running session from April 30th to May 8th. The average running distance per session is calculated to be 12,180 m. The second calculation unit 47 defines the valid period as the period indicated by range C, excluding periods with zero running times, and calculates the average number of runs per valid period based on the number of runs performed during that valid period. In the example of FIG. 11 , the valid periods are May 8th to May 6th, May 5th to May 3rd, and May 2nd to April 30th, each of which has a running time count of one or more. The total number of runs over the three valid periods is five (= 1 + 1 + 3). Therefore, the average number of runs per valid period is calculated to be 1.67 (≈ 5 / 3). The third calculation unit 48 calculates the average three-day running distance by multiplying the average running distance per running session by the average number of runs per valid period. In the example of FIG. 11, the average distance traveled over three days is calculated to be 20,340.6 m (=12,180×1.67).

[0106] For example, if the period is four days long and the average running distance over four days from April 30th to May 8th is to be calculated, the first calculation unit 46 calculates the average running distance per running session from April 30th to May 8th. The average running distance per session is calculated to be 12,180 m. The second calculation unit 47 defines the valid period as the period indicated by range D, excluding periods in which the number of runs is zero, and calculates the average number of runs per valid period based on the number of runs performed during that valid period. In the example of FIG. 11 , the valid periods are May 8th to May 5th and May 4th to May 1st, where the number of runs is one or more. The total number of runs in the two valid periods is four (= 1 + 3). Therefore, the average number of runs per valid period is calculated to be two (= 4 / 2). The third calculation unit 48 calculates the average running distance over four days by multiplying the average running distance per running session by the average number of runs per valid period. In the example of FIG. 11, the average distance traveled over four days is calculated to be 20,360 m (=12,180×2).

[0107] In the above embodiment, an example has been described in which the dashboard screen 100 including a graph of average mileage is displayed on the second user terminal 13. However, the technology of the present disclosure is not limited to this. The display control unit 44 may generate data for a screen including a graph of average mileage that corresponds to the display size of the display unit 12a of the first user terminal 12, transmit the data to the first user terminal 12, and perform control to display the screen including the graph of average mileage on the first user terminal 12.

[0108] In the above embodiment, the case where the training amount for running is the running distance has been described as an example. However, the technology of the present disclosure is not limited to this. The training amount may be any value that represents the amount of exercise performed by running. For example, the training amount may be the distance, time, load, calorie consumption, or number of steps when running. The running distance may be any distance measured during running. The running distance may be the running distance in this embodiment or the travel distance. Note that the load when running is, for example, the total value of the landing impact for each step while running (landing impact for each step x number of steps).

[0109] In the above embodiment, the training is described as running. However, the technology of the present disclosure is not limited to this. The training may be a sport or exercise other than running. The technology of the present disclosure can be applied to any sport or exercise that the user can perform continuously to maintain or improve their health and physical strength. For example, the training may be swimming, cycling, strength training, etc.

[0110] [Effects of the Embodiment] As described above, the server 11 (information processing device) includes a storage unit 21, a first calculation unit 46, a second calculation unit 47, a third calculation unit 48, and a display control unit 44. The storage unit 21 stores training information 34 for each training session performed by the user during a given day, including the training dates, the training volumes performed on the training dates, and the non-training days on which the user did not train, for a given period of time. The first calculation unit 46 calculates a first average training volume, which is the average training volume per training session, based on the training volumes included in the given period. The second calculation unit 47 counts the number of training sessions on each interval day obtained by dividing the given period into predetermined number of days, and calculates the average number of training sessions per valid interval day based on valid interval days, which are interval days excluding interval days with zero number of training sessions, and the number of training sessions performed on the valid interval days. The third calculation unit 48 calculates a second average training volume, which is the average training volume per valid interval day, based on the first average training volume and the average number of training sessions. The display control unit 44 controls the display of the second average training amount as a graph on a display unit (for example, the display unit 12a of the first user terminal 12 or the display unit 13a of the second user terminal 13).

[0111] This allows the server 11 (information processing device) to calculate the average training volume corresponding to the user's ability even if the user's training frequency temporarily drops.

[0112] Furthermore, the training is running. This allows the server 11 to calculate the average training volume corresponding to the user's ability even if the frequency of the user's running temporarily decreases.

[0113] The amount of training is any one of the distance, time, load, calorie consumption, and number of steps when running. This allows the server 11 to calculate the average value of any one of the distance, time, load, calorie consumption, and number of steps that corresponds to the user's ability, even if the user's running frequency temporarily decreases.

[0114] The amount of training is the distance traveled when running. This allows the server 11 to calculate the average running distance corresponding to the user's ability even if the frequency of the user's running temporarily decreases.

[0115] Furthermore, training is considered to have been performed when the user has run a predetermined distance or more. This allows the server 11 to calculate the average training volume from the training volume of the user running a predetermined distance or more.

[0116] Furthermore, the training information 34 includes, for each of multiple users including the first user, training dates, the amount of training performed on the training dates, and non-training days over a predetermined period. The first calculation unit 46 calculates a first average training amount for each of the multiple users. The second calculation unit 47 calculates the average number of training sessions for each of the multiple users. The third calculation unit 48 calculates a second average training amount for each of the multiple users. The display control unit 44 displays a graph showing the distribution of the second average training amounts for the multiple users and also displays the position of the second average training amount for the first user on the graph. This allows the server 11 to display the distribution of users by average running distance so that the user can easily understand it. The server 11 can also display the position of the user's average running distance within the distribution so that the user can easily understand it.

[0117] The server 11 also includes a receiving unit 45 (first receiving unit). The receiving unit 45 receives the designation of a user to be compared. The display control unit 44 displays the distribution of the second average training amount of the user to be compared in a graph, and controls the display of the position of the second average training amount of the first user on the graph. This allows the server 11 to display the distribution of the average training amount of the designated user to be compared so that the user can easily grasp it. The server 11 also displays the position of the user's average running distance within the distribution of the designated user to be compared so that the user can easily grasp it.

[0118] The server 11 also includes a receiving unit 45 (second receiving unit). The receiving unit 45 receives a specified starting date and interval dates. The second calculation unit 47 calculates the average number of training sessions per valid interval day for each interval day obtained by dividing a predetermined period into specified interval days from the specified starting date. This allows the server 11 to calculate a second average training volume, which is the average training volume per valid interval day, for each interval day obtained by dividing the predetermined period into specified interval days from the specified starting date.

[0119] Fig. 12 is a diagram showing an example of the hardware configuration of the server 11 according to the embodiment. As shown in Fig. 12, the server 11 includes a computer including a processor 3010, a memory 3020, an input / output IF 3030, and a bus 3040. The processor 3010, the memory 3020, and the input / output IF 3030 can transmit and receive information to and from each other via the bus 3040.

[0120] The processor 3010 executes each function by reading and executing a management program stored in the memory 3020. The processor 3010 is, for example, an example of a processing circuit, and includes one or more of a CPU, a DSP (Digital Signal Processor), and a system LSI (Large Scale Integration).

[0121] The memory 3020 includes one or more of a RAM, a ROM, a flash memory, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The input / output IF 3030 includes, for example, an AD converter, a DA converter, an input / output port, etc.

[0122] Server 11 may also be configured to include a data reading unit that reads a computer-readable management program from a recording medium on which the management program is recorded. Processor 3010 controls the data reading unit to obtain the management program recorded on the recording medium from the data reading unit, and can store the obtained management program in memory 3020. The recording medium may include, for example, one or more of a non-volatile or volatile semiconductor memory, a magnetic disk, a flexible memory, an optical disk, a compact disk, and a DVD (Digital Versatile Disc).

[0123] Server 11 may also include a communication unit that receives the management program from the server via a network. In this case, processor 3010 can obtain the management program from the server via the communication unit and store the obtained management program in memory 3020.

[0124] The disclosed embodiments should be considered in all respects as illustrative and not restrictive. Indeed, the above-described embodiments may be embodied in various forms. Furthermore, the above-described embodiments may be omitted, substituted, or modified in various ways without departing from the scope and spirit of the appended claims.

[0125] REFERENCE SIGNS LIST 10 Display system 11 Server 12 First user terminal 12a Display unit 13 Second user terminal 13a Display unit 14 Sensor device 20 Communication unit 21 Memory unit 22 Control unit 30 User information 31 Measurement data DB 32 Basic information 33 Form information 34 Training information 40 Storage unit 41 First analysis unit 42 Second analysis unit 43 Generation unit 44 Display control unit 45 Reception unit 46 First calculation unit 47 Second calculation unit 48 Third calculation unit

Claims

1. An information processing device having: a memory unit that stores training information for each day over a specified period, including training dates for each training session performed by a user during a day, the amount of training performed on each training date, and non-training days on which the user did not train; a first calculation unit that calculates a first average training amount, which is an average training amount per training session, based on the training amount included in the specified period; a second calculation unit that counts the number of training sessions on each interval day obtained by dividing the specified period into a specified number of days, and calculates an average number of training sessions per valid interval day based on effective interval days, which are interval days excluding interval days on which the number of training sessions is zero, and the number of training sessions performed on the effective interval days; a third calculation unit that calculates a second average training amount, which is the average training amount per valid interval day, based on the first average training amount and the average number of training sessions; and a display control unit that controls displaying the second average training amount as a graph on a display unit.

2. The information processing device according to claim 1, wherein the training is running.

3. The information processing device according to claim 2, wherein the amount of training is any one of the distance, time, load, calorie consumption, and number of steps taken when running.

4. The information processing device according to claim 3, wherein the amount of training is a distance traveled when running.

5. The information processing device according to claim 2, wherein the training is deemed to have been performed when the user has run a predetermined distance or more.

6. The information processing device of claim 1, wherein the training information includes, for each user including a first user, the training dates, the amount of training performed on the training dates, and the non-training days over the specified period, the first calculation unit calculates the first average training amount for each of the multiple users, the second calculation unit calculates the average number of training sessions for each of the multiple users, the third calculation unit calculates the second average training amount for each of the multiple users, and the display control unit displays a distribution of the second average training amounts for the multiple users in a graph and displays the position of the second average training amount for the first user on the graph.

7. An information processing device as described in claim 6, further comprising a first reception unit that receives designation of a user to be compared, and wherein the display control unit controls displaying a distribution of the second average training volume of the user to be compared in a graph and displaying a position of the second average training volume of the first user on the graph.

8. The information processing device according to claim 7, wherein the training is running, and the display control unit displays the users to be compared on a graph, grouped according to the time it takes to complete a marathon.

9. An information processing device as described in claim 1, further comprising a second receiving unit that receives the designation of a starting date and the interval days, and the second calculation unit calculates the average number of training sessions per effective interval day for each interval day that is obtained by dividing the specified period from the designated starting date into the designated interval days.

10. A method for calculating an average training amount performed by a computer, the method comprising: calculating a first average training amount, which is an average training amount per training session, based on the training amount included in a predetermined period stored in a memory unit that stores training information every day over a predetermined period, including training dates for each training session performed by a user during a day, the amount of training performed on each training date, and non-training days on which the user did not train; counting the number of training sessions on each interval day obtained by dividing the predetermined period into a predetermined number of days; calculating the average number of training sessions per valid interval day based on effective interval days, which are interval days excluding interval days on which the number of training sessions is zero, and the number of training sessions performed on the effective interval days; calculating a second average training amount, which is the average training amount per valid interval day, based on the first average training amount and the average number of training sessions; and controlling to display the second average training amount as a graph on a display unit.

11. A display system comprising a user terminal and an information processing device, wherein the user terminal has a display unit, and the information processing device has: a memory unit that stores training information for each day over a predetermined period, including training dates for each training session performed by a user during a day, the amount of training performed on each training date, and non-training days on which the user did not train; a first calculation unit that calculates a first average training amount, which is an average training amount per training session, based on the training amount included in the predetermined period; a second calculation unit that counts the number of training sessions on each interval day obtained by dividing the predetermined period into a predetermined number of days, and calculates an average number of training sessions per valid interval day based on effective interval days, which are interval days excluding interval days on which the number of training sessions is zero, and the number of training sessions performed on the effective interval days; a third calculation unit that calculates a second average training amount, which is the average training amount per valid interval day, based on the first average training amount and the average number of training sessions; and a display control unit that controls the display of the second average training amount as a graph on the display unit.

Images