WEIGHT MANAGEMENT SYSTEM

Abstract

A system and method for determining the weight gain trend of a user. The weekly weight oscillation is determined, and a future weight trend can be predicted. At least three weeks of weight oscillation trends are typically used to predict future weight trends.

Claims

1. A method for computerized generation of weight oscillation and weight trends, comprising: obtaining a plurality of outputs from a weight acquisition element to a computer processing device, wherein the weight acquisition element does not directly or indirectly convey an acquired weight measurement to a user being weighed on the weight acquisition element, further wherein the computer processing device operates in accordance with an algorithm included within an operating instruction set to store the plurality of outputs in a weight database as current weight measurements, wherein the computer processing device includes a data acquisition processor, a data storage processor, a data processing processor, and an information delivery processor; storing each of the current weight measurements as a weight data structure, the weight data structure including fields for the current weight measurement, a date of the current weight measurement, and a time of the current weight measurement; receiving, by the data processing processor, from a data storage processor a plurality of weight data structures for a week one time period; generating, by the data processing processor, an oscillation prediction model based on the plurality of weight data structures for the week one time period; predicting, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week one time period with the oscillation prediction model; updating, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week one time period; generating, by the data processing processor, a week one oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week one time period; receiving, by the data processing processor, from the data storage processor a plurality of weight data structures for a week two time period; updating, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week two time period; predicting, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week two time period using the oscillation prediction model; updating, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week two time period; generating, by the data processing processor, a week two oscillation range using the oscillation prediction model and the plurality of predicted weight values for week two; receiving, by the data processing processor, from the data storage processor a plurality of weight data structures for a week three time period; updating, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week three time period; predicting, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week three time period using the oscillation prediction model; updating, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week three time period; generating, by the data processing processor, a week three oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week three time period; wherein the week one time period, the week two time period, and the week three time period are consecutively occurring weeks, further wherein the week three time period is a current week, the week two time period is a first previous week, and the week one time period is a second previous week, wherein the week one oscillation range, the week two oscillation range, and the week three oscillation range each include an average weight point, a positive oscillation, and a negative oscillation associated with each respective week, further wherein the oscillation prediction model is continually and consecutively updated; generating, by the data processing processor, a predicted weight average momentum for a week four time period and a week five time period, wherein the week four time period and the week five time period are consecutively occurring weeks to the week one time period, the week two time period, and the week three time period, further wherein the week four time period is a first future week and the week five time period is a second future week; converting, by the data processing processor, the predicted weight average momentum for each of the week four time period and the week five time period to a weight trend; and displaying, by the information delivery processor, the weight trend and the predicted weight average momentum for each of the week four time period and the week five time period on a graphical user interface of an application on a user device of the user by an information delivery processor, wherein the weight trend is a graphical representation of a visual comparison between the predicted weight average momentum for each of the week four time period and the week five time period and the week one oscillation range, the week two oscillation range, and the week three oscillation range.

2. The method of claim 1, the method further comprising, for each current weight measurement, receiving a set of clothing information about clothing worn by the user during the current weight measurement.

3. The method of claim 2, the method further comprising, for each current weight measurement, generating by the data processing processor, an actual weight measurement based on the current weight measurement and the set of clothing information received with the current weight measurement.

4. The method of claim 3, wherein each weight data structure includes fields for the set of clothing information and the actual weight measurement.

5. The method of claim 1, wherein generating the predicted weight average momentum includes: generating a weight difference percentage for each of the week one time period, the week two time period and the week three time period; generating a predicted average weight range for each of the week four time period and the week five time period based on the average weight points for the week one time period, the week two time period and the week three time period, a week one adjustment factor, and a week two adjustment factor, wherein the week one adjustment factor and week two adjustment factor are based on the weight difference percentage generated for each week; and generating a predicted weight oscillation momentum for each of the week four time period and the week five time period based on the oscillation prediction model.

6. The method of claim 1, the method further comprising determining a hydration level of the user for each of the current weight measurements when the current weight measurement was collected within a predetermined timeframe.

7. The method of claim 1, the method further comprising: comparing a most recent current weight measurement to a prior week's weight oscillation range; and providing a notice to the user to collect a second current weight measurement when the most recent current weight measurement is outside of a threshold range or the prior week's weight oscillation range.

8. A system for computerized generation of weight oscillation and weight trends, comprising: a computer processing device, the computer processing device including: a memory comprising computer readable instructions; a data acquisition processor, a data storage processor, a data processing processor, and an information delivery processor, each configured to read the computer readable instructions that when executed causes the system to: obtain a plurality of outputs from a weight acquisition element to a computer processing device, wherein the weight acquisition element does not directly or indirectly convey an acquired weight measurement to a user being weighed on the weight acquisition element, further wherein the computer processing device operates in accordance with an algorithm included within an operating instruction set to store the plurality of outputs in a weight database as current weight measurements, wherein the computer processing device includes a data acquisition processor, a data storage processor, a data processing processor, and an information delivery processor; store each of the current weight measurements as a weight data structure, the weight data structure including fields for the current weight measurement, a date of the current weight measurement, and a time of the current weight measurement; receive, by the data processing processor, from a data storage processor a plurality of weight data structures for a week one time period; generate, by the data processing processor, an oscillation prediction model based on the plurality of weight data structures for the week one time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week one time period with the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week one time period; generate, by the data processing processor, a week one oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week one time period; receive, by the data processing processor, from the data storage processor a plurality of weight data structures for a week two time period; update, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week two time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week two time period using the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week two time period; generate, by the data processing processor, a week two oscillation range using the oscillation prediction model and the plurality of predicted weight values for week two; receive, by the data processing processor, from the data storage processor a plurality of weight data structures for a week three time period; update, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week three time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week three time period using the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week three time period; generate, by the data processing processor, a week three oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week three time period; wherein the week one time period, the week two time period, and the week three time period are consecutively occurring weeks, further wherein the week three time period is a current week, the week two time period is a first previous week, and the week one time period is a second previous week, wherein the week one oscillation range, the week two oscillation range, and the week three oscillation range each include an average weight point, a positive oscillation, and a negative oscillation associated with each respective week, further wherein the oscillation prediction model is continually and consecutively updated; generate, by the data processing processor, a predicted weight average momentum for a week four time period and a week five time period, wherein the week four time period and the week five time period are consecutively occurring weeks to the week one time period, the week two time period, and the week three time period, further wherein the week four time period is a first future week and the week five time period is a second future week; convert, by the data processing processor, the predicted weight average momentum for each of the week four time period and the week five time period to a weight trend; and display, by the information delivery processor, the weight trend and the predicted weight average momentum for each of the week four time period and the week five time period on a graphical user interface of an application on a user device of the user by an information delivery processor, wherein the weight trend is a graphical representation of a visual comparison between the predicted weight average momentum for each of the week four time period and the week five time period and the week one oscillation range, the week two oscillation range, and the week three oscillation range.

9. The system of claim 8, wherein the system is further caused to, for each current weight measurement, receive a set of clothing information about clothing worn by the user during the current weight measurement.

10. The system of claim 9, wherein the system is further caused to, for each current weight measurement, generate by the data processing processor, an actual weight measurement based on the current weight measurement and the set of clothing information received with the current weight measurement.

11. The system of claim 10, wherein each weight data structure includes fields for the set of clothing information and the actual weight measurement.

12. The system of claim 8, wherein generating the predicted weight average momentum includes causing the system to: generate a weight difference percentage for each of the week one time period, the week two time period and the week three time period; generate a predicted average weight range for each of the week four time period and the week five time period based on the average weight points for the week one time period, the week two time period and the week three time period, a week one adjustment factor, and a week two adjustment factor, wherein the week one adjustment factor and week two adjustment factor are based on the weight difference percentage generated for each week; and generate a predicted weight oscillation momentum for each of the week four time period and the week five time period based on the oscillation prediction model.

13. The system of claim 8, wherein the system is further caused to determine a hydration level of the user for each of the current weight measurements when the current weight measurement was collected within a predetermined timeframe.

14. The system of claim 8, wherein the system is further caused to: compare a most recent current weight measurement to a prior week's weight oscillation range; and provide a notice to the user to collect a second current weight measurement when the most recent current weight measurement is outside of a threshold range or the prior week's weight oscillation range.

15. A non-transitory computer readable medium comprising computer readable code to computerized generation of weight oscillation and weight trends on a system that when executed by a processor, causes the system to: obtain a plurality of outputs from a weight acquisition element to a computer processing device, wherein the weight acquisition element does not directly or indirectly convey an acquired weight measurement to a user being weighed on the weight acquisition element, further wherein the computer processing device operates in accordance with an algorithm included within an operating instruction set to store the plurality of outputs in a weight database as current weight measurements, wherein the computer processing device includes a data acquisition processor, a data storage processor, a data processing processor, and an information delivery processor; store each of the current weight measurements as a weight data structure, the weight data structure including fields for the current weight measurement, a date of the current weight measurement, and a time of the current weight measurement; receive, by the data processing processor, from a data storage processor a plurality of weight data structures for a week one time period; generate, by the data processing processor, an oscillation prediction model based on the plurality of weight data structures for the week one time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week one time period with the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week one time period; generate, by the data processing processor, a week one oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week one time period; receive, by the data processing processor, from the data storage processor a plurality of weight data structures for a week two time period; update, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week two time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week two time period using the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week two time period; generate, by the data processing processor, a week two oscillation range using the oscillation prediction model and the plurality of predicted weight values for week two; receive, by the data processing processor, from the data storage processor a plurality of weight data structures for a week three time period; update, by the data processing processor, the oscillation prediction model based on the plurality of weight data structures for the week three time period; predict, by the data processing processor, a plurality of predicted weight values for each of a plurality of intervals between each weight data structure for the week three time period using the oscillation prediction model; update, by the data processing processor, the oscillation prediction model based on the plurality of predicted weight values for the week three time period; generate, by the data processing processor, a week three oscillation range using the oscillation prediction model and the plurality of predicted weight values for the week three time period; wherein the week one time period, the week two time period, and the week three time period are consecutively occurring weeks, further wherein the week three time period is a current week, the week two time period is a first previous week, and the week one time period is a second previous week, wherein the week one oscillation range, the week two oscillation range, and the week three oscillation range each include an average weight point, a positive oscillation, and a negative oscillation associated with each respective week, further wherein the oscillation prediction model is continually and consecutively updated; generate, by the data processing processor, a predicted weight average momentum for a week four time period and a week five time period, wherein the week four time period and the week five time period are consecutively occurring weeks to the week one time period, the week two time period, and the week three time period, further wherein the week four time period is a first future week and the week five time period is a second future week; convert, by the data processing processor, the predicted weight average momentum for each of the week four time period and the week five time period to a weight trend; and display, by the information delivery processor, the weight trend and the predicted weight average momentum for each of the week four time period and the week five time period on a graphical user interface of an application on a user device of the user by an information delivery processor, wherein the weight trend is a graphical representation of a visual comparison between the predicted weight average momentum for each of the week four time period and the week five time period and the week one oscillation range, the week two oscillation range, and the week three oscillation range.

16. The non-transitory computer readable medium of claim 15, wherein the system is further caused to, for each current weight measurement, receive a set of clothing information about clothing worn by the user during the current weight measurement.

17. The non-transitory computer readable medium of claim 16, wherein the system is further caused to, for each current weight measurement, generate by the data processing processor, an actual weight measurement based on the current weight measurement and the set of clothing information received with the current weight measurement.

18. The non-transitory computer readable medium of claim 17, wherein each weight data structure includes fields for the set of clothing information and the actual weight measurement.

19. The non-transitory computer readable medium of claim 15, wherein generating the predicted weight average momentum includes further causing the system to: generate a weight difference percentage for each of the week one time period, the week two time period and the week three time period; generate a predicted average weight range for each of the week four time period and the week five time period based on the average weight points for the week one time period, the week two time period and the week three time period, a week one adjustment factor, and a week two adjustment factor, wherein the week one adjustment factor and week two adjustment factor are based on the weight difference percentage generated for each week; and generate a predicted weight oscillation momentum for each of the week four time period and the week five time period based on the oscillation prediction model.

20. The non-transitory computer readable medium of claim 15, wherein the system is further caused to determine a hydration level of the user for each of the current weight measurements when the current weight measurement was collected within a predetermined timeframe.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 provides a weight trend graph according to one aspect of the application;

[0012] FIG. 2 provides another weight trend graph according to one aspect of the application;

[0013] FIG. 3 provides an illustrative overall system view according to one aspect of the application;

[0014] FIG. 4 provides an illustrative component diagram of an illustrative weight tracking station according to one aspect of the application;

[0015] FIG. 5 provides an illustrative flow diagram for weight trend analysis according to an aspect of the application;

[0016] FIG. 6 provides another illustrative flow diagram for weight trend analysis according to another aspect of the application;

[0017] FIG. 7 provides an illustrative user interface for gathering weight information according to another aspect of the application;

[0018] FIG. 8 provides an illustrative flow diagram for an illustrative weight oscillation algorithm according to an aspect of the application;

[0019] FIG. 9 provides an illustration on weight range measurements taken over time according to aspect of the application;

[0020] FIG. 10 provides another illustrative flow diagram for an illustrative weight oscillation algorithm according to an aspect of the application;

[0021] FIG. 11 provides another illustrative flow diagram for an illustrative weight oscillation algorithm according to an aspect of the application;

[0022] FIG. 12 provides an illustration of weight trend output according to an aspect of the application;

[0023] FIG. 13 provides another illustration of weight trend output according to an aspect of the application;

[0024] FIG. 14 provides an illustration of weekly weight oscillation trends determined according to an aspect of the application; and

[0025] FIG. 15 provides an illustration of a weight measure system according to an aspect of the application.

DETAILED DESCRIPTION OF THE INVENTION

1. System Overview

[0026] Referring to FIG. 3, an overall view of a nonlimiting, exemplary depiction of the typical components of the system according to an aspect of the present application is shown. A data acquisition subsystem 1000 typically collects input from a user 10. Subsystem 1000 typically transmits data and other information to data storage subsystem 2000. Subsystem 2000 typically communicates with data processing subsystem 3000, and subsystem 3000 typically performs a variety of calculations, analytics, and other analyses upon the data. Subsystem 3000 communicates with information delivery subsystem 4000, and subsystem 4000 typically delivers information to user 10. It will be understood that while the foregoing systems are described as separate systems, it is to be recognized that implementations of such systems can be performed using one or more processors, which may be communicatively connected, and such implementations are considered to be within the scope of the description. In addition, such subsystems could be combined into one another without departing from the scope of the present application. Furthermore, the foregoing subsystems can communicate using any available communication methodologies, including both wired and wireless communications, and combinations thereof.

2. Weight/Data Acquisition

[0027] Referring now to FIG. 4, a weight tracking station 1100 according to one aspect of the present application is shown. Station 1100 provides one example of data acquisition subsystem 1000 according to an aspect of the present application. Station 1100 typically can include a scale 1110, computer processing unit 1120, touch screen monitor 1130, and camera 1140. Scale 1100 measures the weight of a user (not shown) and transmits the measured weight to processing unit 1120. In one aspect, scale 1110 communicates wirelessly with unit 1120 (e.g., using Wi-Fi or Bluetooth). In other aspects, scale 1110 can be interfaced with unit 1120 using other implementations such as wired connections. Unit 1120 is in communication with touch screen monitor 1130 and camera 1140.

[0028] Referring now to FIG. 5, a flow diagram showing an exemplary way of collecting data from a user 10 is shown. The process is typically initiated by a user (not shown) stepping onto scale 1110 at 102 or alternatively touching touch screen monitor 1130 at 104. Processing unit 1120 then initializes camera 1140 and a quick response code (commonly called a “QR code”) is requested at 106, typically by a request using monitor 1130. The QR code is then collected at 108, typically using camera 1140. Using the QR code, user information is then retrieved at 110. Any other suitable identification information can likewise be used instead of a QR code. Other input devices and methodologies within the scope of the present application can include a mouse, a keyboard, a voice input device, a touch input device for receiving a gesture from a user, a motion input device for detecting non-touch gestures and other motions by a user, and other comparable input devices and associated processing elements capable of receiving user input from a user.

[0029] Still referring to FIG. 5, user information is typically retrieved by communicating with a database, such as a database stored on the cloud or other locations, and the user information is then provided to processing unit 1120. Other data retrieval methodologies can likewise be used. Examples of storage media used in connection with the present application include random access memory, read only memory, magnetic discs, optical discs, flash memory, virtual memory, and non-virtual memory, magnetic sets, magnetic tape, magnetic disc storage or other magnetic storage devices, or any other medium which can be used to store the desired information and that may be accessed by an instruction execution system, as well as any combination or variation thereof, or any other type of storage medium. In some implementations, the storage media can be a non-transitory storage media. In some implementations, at least a portion of the storage media may be transitory.

[0030] Still referring to FIG. 5, at 112, the user's identification is confirmed on using monitor 1130. Then, at 114 the user's weight is measured using scale 1110. In one aspect of the application, the user's weight is not displayed. At 116, the user inputs the type of clothing that is being worn by the user by selecting from several options displayed on monitor 1130.

[0031] Still referring to FIG. 5, at 118 an analysis of the user's weight is performed. This weight analysis is discussed in further detail below and an exemplary, nonlimiting example is provided in FIG. 6. Referring to FIG. 6, at 118A the user's actual weight is calculated by subtracting the clothing weight selected at 116 from the actual weight measured at 114. At 1188, the actual weight calculated in 118A is compared with the prior week's weight range. At 118C, the actual weight is compared with the last weight measurement. At 118D, the system determines whether the user is dehydrated. If the last weight measurement was taken within three (3) hours (or another suitable duration) of the current weight measurement at 114, these two measurements are compared. If the current weight at 114 is more than 300 grams (or another suitable figure) lower than the prior measurement, at 118E information is provided to the user about how much water should be ingested by the user to reach a proper hydration level, and other information can also be provided about proper hydration levels. Referring back to FIG. 5, at 122, the prior week's weight range is compared with the current weight measurement taken at 114. If the current weight is more than two percent (2%) (or another suitable percentage) higher or lower than the prior week's measurement, the user is asked to confirm the weight selection provided at 116.

[0032] Referring back to FIG. 5, at 120, optional information such as an advertising message can be displayed using monitor 1130. At 122, a message is displayed on monitor 1130 notifying the user to see the private portion of the application for details regarding the weight analysis. Following is one nonlimiting example of information that can be displayed on monitor 1130 at 122:

“Nice! This is your 4th measurement this week!
It is important to us to build your weekly weight oscillation in order to reveal your future weight trend.
Please see your results on your APP.

Thanks!”

[0033] In another aspect of the present invention, a user 10 can still utilize the present system when user 10 does not have access to weight tracking station 1100. In such circumstances, user 10 can manually enter the user weight using an app that can be downloaded directly onto user's mobile device such as a smartphone. As yet another alternative, user 10 can also log into a website integrated with the present system to input user's weight. Referring to FIG. 7, an exemplary user interface is shown that can be used to manually enter user's weight using a smart phone device. Here, user 10 will set the device 310 from which user's weight was measured, enter the date 320 and time 330 at which the weight measurement was taken, and select the clothing type 340 worn by user 10 at the time of the weight measurement. This data is then transmitted to subsystem 3000.

[0034] As another alternative, a user 10 could take weight measurements using a wi-fi enabled scale that is linked to subsystem 3000 via an Internet connection. After such weight measurement is taken, the user will typically input the same information as described with reference to FIG. 7 except that the user typically will not have to designate the scale device.

[0035] The present system typically needs three consecutive weeks of weight measurements in which weight measurement are taken on at least three different days during each week. If one of more of such measurements are not available, the present system can generate a “dummy” or “maintain weight” weight for use in connection with making the calculations and determinations described herein.

3. Weight Oscillation Calculation

[0036] Following is an explanation of an exemplary calculation that can be used to determine the weight oscillation of a user. This calculation is for purposes of illustration only and is not intended to limit the present application. This calculation typically uses data that has already been prepared in a database (typically in the cloud), and the algorithm is typically considered an object in the cloud that is separate from the database and used to calculate the weight trend. The information from multiple users can be aggregated in the database and used to prepare collective reports.

3.1 Weight Adjustment

[0037] Referring to FIG. 8, a flow diagram depicts the typical steps of the weight oscillation calculation. At 202, the user weight is adjusted. The following fields are typically populated in the database with information related to each weight measurement:

Weight—“weig”
Date—“date”
Time—“time”
Scale—“scal”
Shoes—“shoe”
Clothes—“clot”
Accessories—“aces”

[0038] The weight adjustment is typically calculated by subtracting from the measured weight the sum of shoes, clothes, and accessories, which can be represented by the following formulas.

Weight adjusted=wead

Wead=weig−(shoe+clothes+aces)

3.2 Calculating “WEAC”

[0039] Still referring to FIG. 8, at 202 the “WEAC” is calculated. “WEAC” is typically a non-actual weight that a first equation (f_Weac) calculates to generate a new “weight” 20 minutes between each actual weight measurements.

[00001]$\mathrm{f\_Weac}=\frac{\begin{array}{c}-1*(\left(\mathrm{Time}2*\left(\mathrm{wead}1-\mathrm{wead}2\right)\right)+\\ \left(\mathrm{wead}2*\mathrm{time}1\right)-\left(\mathrm{wead}1*\mathrm{time}2\right)\end{array}}{\left(\mathrm{time}2-\mathrm{time}1\right)}$

[0040] Referring to FIG. 9, the distance in time between measurements typically can be important because as the time duration between measurements increases, the likelihood of weight oscillation can also increase. Stated another way, as time progresses, the magnitude of weight oscillation such as 410, 420, and 430, can also typically increase as shown in FIG. 9. Following is a brief, nonlimiting explanation for the oscillations shown in FIG. 9. In one aspect, there are typically two groups of “actions” that can impact total human body weight. One group (A) is related to chemical reactions that happens inside our body and are controlled by our metabolism, which include the fat burn process for example, but also includes transpiration. Another group (B) is related to digestive and urological systems, that can accumulate weight by ingest liquids and food and can reduce weight by defecting and urinating. Considering just group A we could understand a slow weight loss between every measurement because our body need to produce energy what consumes water. Theoretically, 15 minutes after of one weight measurement is taken, a second measurement could show a very small total weight reduction, and the total body weight would be lower than the first one. Conversely, it is likewise possible that the second measurement could higher than the first one if the person drank or ate something. The present application typically has a focus on the weekly behavior. Additionally, five hours after one weight measurement, we can have a different weight measurement because of any “action” that results from a group B activity. In contrast to experimental labs, the present application typically includes considerations that just after a weight measurement, a user could go to the bathroom, or even drink water, thereby changing the weight that was just measured.

3.3 Calculating Weekly Oscillation

[0041] Referring to FIG. 8, at 206 the weekly weight oscillation is typically calculated. The calculation according to one aspect of the invention typically works with a table that contains two variables: (i) real weight collected by our application (WEAD) and (ii) non-real weight (WEAC), both of which are used to create a table of measurements every week. Starting on Monday 12:20 am and ending on Sunday 11:59 pm. Following is one example of such a table.

TABLE-US-00001 Date/time Weight Time1 wead1 Time w1 weac1 Time w2 weac2 Time w3 weac3 Time2 wead2 Time w4 weac4 Time w5 weac5 Time w6 weac6 Time3 wead3

[0042] The following equations typically can be used in connection with calculating the weekly oscillation:

Average point=(average of every weight of the week)

STD deviation=Calculation of standard deviation

STD Factor=SDF*STD Deviation

Oscil−=Average point−STD Factor

Oscil+=Average point+STD Factor

[0043] The foregoing calculations are based in part upon the observation that that humans typically have a natural total weight oscillation. In connection with this observation, the present application typically does not consider the real, or actual, minimum and maximum values of the weekly weight measurements in connection with analyzing the weekly weight oscillation of a user. Instead, according to aspect of the present application, a standard deviation factor is typically used to improve the accuracy of the model. In one aspect, a standard deviation factor (“SDF”) of 2.35781 is used in connection with the present application. In other aspects, this SDF can be less than be less than 4.0, less than 3.9, less than 3.8, less than 3.7, less than 3.6, less than 3.5, less than 3.4, less than 3.3, less than 3.2, less than 3.1, less than 3.0, less than 2.9, less than 2.8, less than 2.7, less than 2.6, less than 2.5, less than 2.4, less than 2.3, less than 2.2, less than 2.1, less than 2.0, less than 1.9, less than 1.8, less than 1.7, less than 1.6, less than 1.5, less than 1.4, less than 1.3, less than 1.2, and less than 1.0. This SDF is typically multiplied by the standard deviation of a weight data set to produce a “STD Factor,” which is used to determine the weekly weight oscillation. The weekly weight oscillation typically is a range of numbers, where the minimum value (Oscil−) is equal to Average point—STD Factor, and the maximum value (Oscil+) is Average point+STD Factor. The present application typically uses this range (i.e., the weight difference between Oscil− and Oscil+) to project the future weight range. The use of this SDF factor can improves the accuracy of the prediction model, potentially by ninety percent (90%) when compared with other methodologies such as those described in the following publications, the contents of which are incorporated herein by reference: [0044] Diana M. Thomas et al., “A Simple Model Predicting Individual Weight Change In Humans,” J. Biol. Dyn. 2011 November; 5(6): 579-599, available at www.ncbi.nlm.nih.gov/pmc/articles/PMC3975626/. [0045] LSU Pennington Biomedical Research Center Weight Loss Predictor, available online at www.pbrc.edu/research-and-faculty/calculators/weight-loss-predictor/.
The models and methodologies described in the foregoing resources are complex in comparison to the present application and the accuracy of these resources is related to the user's compliance with the protocol rules. In comparison, the present application is based upon shorter term situations that incorporates “real life” activities into the analysis.

3.4 Determining Weight Average Momentum

[0046] Still referring to FIG. 8, at 208 the weight average momentum typically is calculated. The following table identifies the values that are typically calculated using various equations in this step. In one aspect, the present application typically calculates first the “middle” point of the future weight range. After this calculation, referred to as the “AVERAGE,” the present application typically calculates the weight range. The minimum value of this range is “Oscil−1” and the maximum point “Oscil+1”. As one nonlimiting example, assuming the “Actual Week” started on Monday, December 12, “Week-1” would have started on Monday, December 5, and “Week-2” would have started on Monday, November 28.

TABLE-US-00002 Average Oscil−1 Oscil+1 Week-2 AP1 - Average ON1 - Oscillation OP1 - Oscillation point; It is the Negative; Is equal to Positive; Is equal to average of weight the Average Point the Average Point measures of this minus STD Factor of plus STD Factor of week. this week this week Week-1 AP2 - Average ON2 - Oscillation OP2 - Oscillation point; It is the Negative; Is equal to Positive; Is equal to average of weight the Average Point the Average Point measures of this minus STD Factor of plus STD Factor of week. this week this week Actual AP3 - Average ON3 - Oscillation OP3 - Oscillation Week point; It is the Negative; Is equal to Positive; Is equal to average of weight the Average Point the Average Point measures of this minus STD Factor of plus STD Factor of week. this week this week

[0047] The following equations are typically applied in this step to determine the weight average momentum.

Mm32=(AP1+AP2)/2

Mm21=(AP2+AP3)/2

AV-2=AP3

Week_f1=(((D9−D8)*4+(D8−(((D9−D8)/C16)*2.5)))+D10)/2

D9=Mm21;D8=Mm32;C16=wf1adj;D10=AP3

Week_f2=(((D10−d8)*4+(D8−(((D10−D8)/C17)*2.5)))+D12)/2

D10=AP3;D8=Mm32;C17=wf2adj;D12=Week_f1

The equation week_f1 is typically used to find the average number of the weight range at the following week (i.e., the week immediately following the actual week of the current measurement). The week_f2 equation is typically used to find the average number of the weight range at the next following week (i.e., two weeks ahead of the actual week). Using these algorithms, the application is typically capable of determining the users' weight range for the next week after the actual weight measurement and also the second week after the actual weight measurement.

[0048] In the above exemplary equation, “wf1adj” is a factor typically used to correct the projection of week 1. It is based on the percentage difference between the average points of week 3 and week 1. This difference is a “key number” that according to one aspect of the application is used for selecting the appropriate factor as shown in the following table that correlates the percentage difference to the appropriate factor. In a similar manner, “wf2adj” is a factor typically used to correct the projection of week 2. It is based on the percentage difference between the average points of week 3 and week 2.

[0049] The following tables provide a nonlimiting illustration of determining the “wf1adj” and “wf1adj2” values for use in connection with the application.

TABLE-US-00003 Weight loss speed evaluation week average loss percent Week -2 100.5759 Week -1 99.51683 1.059 1.05% Actual Week 97.81864 1.698 1.69% AV-4 + AV-2 2.757 2.74% Wf1adj 2 week-f1 97.037 0.782 0.79% AV3 + weekf1 2.48  2.49% Wf2adj 1.1

[0050] The below table provides nonlimiting illustrations for the “wf1adj” and “wf2adj” values that correspond to the percent weight loss. For example, in the above table, the week-1 weight loss percent was 2.74%, so the corresponding wf1adj value taken from the below table that corresponds to 2.74% is 2.0.

TABLE-US-00004 References Weight Loss Wf1adj Wf2adj 5.00% 2 0 1 0 4.50% 2 0 1 0 4.00% 2 0 1.1 0 3.50% 2 0 1.1 0 3.00% 2 0 1.1 0 2.50% 2 2 1.1 0 2.00% 2 0 1.1 1.1 1.95% 2 0 1.1 0 1.90% 2 0 1.1 0 1.85% 2 0 1.1 0 1.80% 2 0 1.1 0 1.75% 2 0 1.1 0 1.70% 2 0 1.1 0 1.65% 2.09 0 1.1 0 1.60% 2.17 0 1.2 0 1.55% 2.26 0 1.2 0 1.50% 2.35 0 1.2 0 1.45% 2.44 0 1.2 0 1.40% 2.52 0 1.2 0 1.35% 2.61 0 1.2 0 1.30% 2.7 0 1.2 0 1.25% 2.78 0 1.2 0 1.20% 2.87 0 1.2 0 1.15% 2.96 0 1.2 0 1.10% 3.04 0 1.2 0 1.05% 2.99 0 1.2 0 1.00% 2.99 0 1.2 0 0.95% 2.99 0 1.54 0 0.90% 2.99 0 1.54 0 0.85% 2.99 0 1.54 0 0.80% 2.99 0 1.54 0 0.75% 2.99 0 1.54 0 0.70% 2.99 0 1.54 0 0.65% 2.99 0 1.54 0 0.60% 2.99 0 1.54 0 0.55% 1 0 1.54 0 0.50% 1 0 1.54 0 0.45% 1 0 1.54 0 0.40% 1 0 1.54 0 0.35% 1 0 1.54 0 0.30% 1 0 1.54 0 0.25% 1 0 1.54 0 0.20% 1 0 1.54 0 0.15% 1 0 1.54 0 0.10% 1 0 1.54 0 0.05% 1 0 1.54 0 0.00% 1 0 1.54 0 −0.05% 1 0 0.8 0 −0.10% 1 0 0.8 0 −0.15% 1 0 0.8 0 −0.20% 1 0 0.8 0 −0.25% 1 0 0.8 0 −0.30% 1 0 0.8 0 −0.35% 1 0 0.8 0 −0.40% 1 0 0.8 0 −0.45% 1 0 0.8 0 −0.50% 1.023 0 0.821 0 −0.55% 1.046 0 0.842 0 −0.60% 1.069 0 0.863 0 −0.65% 1.092 0 0.884 0 −0.70% 1.115 0 0.905 0 −0.75% 1.138 0 0.926 0 −0.80% 1.161 0 0.947 0 −0.85% 1.184 0 0.968 0 −0.90% 1.207 0 0.989 0 −0.95% 1.23 0 1.01 0 −1.00% 1.253 0 1.031 0 −1.50% 1.276 0 1.052 0 −2.00% 1.299 0 1.073 0 −2.50% 1.322 0 1.1 0 −3.00% 1.345 0 1.1 0 −3.50% 1.368 0 1.1 0 −4.00% 1.391 0 1.1 0 −4.50% 1.414 0 1.1 0 −5.00% 1.437 0 1.1 0

3.5 Determining Weight Oscillation Momentum

[0051] Still referring to FIG. 8, at 209 the weight oscillation momentum typically is determined. The following equations are typically used in connection with making this determination.

Oscillation-week_f1=D12−(0.6*(average(difofOscil)))

Oscillation-week_f2=week_f1+(0.6*(((OP1−ON1)+(OP2−ON2)+(OP3−ON3))/3)

As explained above, an aspect of the present application is the calculation of the weekly weight ranges for a user. The equations “Oscillation-week_f1” and “Oscillation-week_f2” typically complement the “week_f1” and “week_f2” equations explained above in order to generate the future two week weight range (weight range for the first week after the week of the actual measurement, and the to the second week after the week of the actual measurement.)

[0052] The week-f1 and week-f2 equations typically result from the average point of the future weights of the “next,” or subsequent, two weeks after week 3, which could otherwise be referred to as week4 and week5. In one aspect, the present application uses “week-f1” for week 4 and “week-f2” for week 5. To calculate the weight ranges “around” these average points, the present application typically calculates the “size” of the oscillation. The calculations for “Oscillation-week_f1” and “Oscillation-week_f2” are typically used to determine this oscillation. The following equations are typically used in connection with these determination.

[0053] the minimum point of the oscillation-week_f1 is equal to {D12−[0.6*(average of the last three weekly oscillations)]};

[0054] the maximum point of the oscillation-week_f1 is equal to {D12+[0.6*(average of the last three weekly oscillations)]};

[0055] the minimum point of the oscillation-week_f2 is equal to {D13−[0.6*(average of the last three weekly oscillation)]};

[0056] the maximum point of the oscillation-week_f2 is equal to {D13+[0.6*(average of the last three weekly oscillation)]}

[0057] D13 is equal to the week-f2 calculation explained above;

[0058] “average of the last three weekly oscillations” (also referred to as “average(difofOscil)”)=(((OP1−ON1)+(OP2−ON2)+(OP3−ON3))/3)

[0059] Referring to FIGS. 10 and 11, flow diagrams providing additional context for the foregoing equations are provided.

4. Information Delivery

[0060] In another aspect of the application, information is typically provided to a user that is intended to assist the user in understanding and monitoring the user's weight trend and weight oscillation, which can be useful in managing the user's weight loss goals. In order to accomplish this, the present application typically tracks a periodic (e.g., weekly) weight range rather than tracking a specific weight number. The present application typically includes an interface that permits user to see the user's predicted weight range two weeks in advance and also typically notifies a user if the pace of user's weight gain or loss is adequate to meet the user's desired outcome, such as losing weight or gaining weight.

[0061] Referring to FIG. 12, according to another aspect of the invention, output typically is shown on the display of a mobile device 20 such as a smartphone. The weight trend shown is a graphic visualization of the weekly weight range for the current (or actual) week 230, the weekly weight range for one week prior 220 and two weeks prior 210, as well as for one week in the future 240 and two weeks in the future 250.

[0062] Referring to FIG. 13, another output 300 according to an aspect of the invention is shown. Here, a virtual needle, or pointer, 310 typically designates the portion of a scale corresponding to the user's weight loss trend. For example, needle 310 will point to portion 320 when the user is experiencing intense weight loss. In such circumstances, the user should attempt to reduce the pace at which weight is being lost. As another example, needle 310 will point to portion 330 when the user is experiencing a good weight loss pace. This signifies that the user should continue following the same behaviors and activities to continue losing weight on a good pace. Such a “good” pace typically prevents a user from hitting a “plateau” situation in which weight loss is typically stunted. Such plateaus can result in users losing motivation to stay on a weight loss program. Any other suitable display methodology can also be used to convey the weight loss or weight gain trend information to a user.

[0063] Still referring to FIG. 13, needle 310 typically will point to portion 340 when user is on a slow weight loss pace, and point to portion 350 when user is maintaining the same weight loss trending. Needle 310 will point to portion 360 when the user is experiencing a passive weight gain pace, and to portion 340 when the user is gaining weight. The calculations used to determine the weight loss trend are typically based upon the week three weight range and week five weight range. As previously explained, the present application typically expresses the “distance” between the actual weight range (week3, or the present week) and the future weight range two weeks out (also referred to herein as week5 or “week_f2”). For example, if the week-f2 has a weight range that has a maximum oscillation that is lower than the maximum oscillation for week 3, the user of the present application would typically be losing weight. If such weight loss is greater than three percent (3%), the user is typically losing weight at a more rapid pace than desired, which can result in non-sustainable weight loss.

[0064] Referring to FIG. 14, an illustrative, nonlimiting example of a user's weekly weight oscillation for week 3 and week 5 are shown. The maximum oscillation value for the week 3 range is shown at 152, and the minimum oscillation value for the week 3 range is shown at 154. The maximum oscillation value for the for week 5 range is shown at 156, and the minimum oscillation value for the for week 5 range is shown at 164. As described above, week 5 is also referred to herein as “week-f2”. Also as previously explained, the present application uses the difference between the maximum value of the weight range (e.g., maximum oscillation−Oscil+1) as a factor when determining the weight loss trend. The following table provides an example of the weight oscillation calculations that correspond to the weight trend category typically displayed to the user.

TABLE-US-00005 Category Calculation (The maximum point of the oscillation-week_f2 − maximum point of oscillation-week 3) Gaining Weight If the result is positive and bigger than 1% of the maximum point of the oscillation-week_f2 Slow gain weight/ If the result is positive but Passive weight gain smaller than 1% of the maximum point of the oscillation-week_f2 Maintaining If the result is positive but weight trend smaller than 0.5% or negative but higher than 0.5% of the maximum point of the oscillation-week_f2 Slow weight If the result is negative but loss pace lower than 1% of the maximum point of the oscillation-week_f2 Good weight If the result is negative but loss pace lower than 2.3% of the maximum point of the oscillation-week_f2 Invasive If the result is negative but weight loss higher than 2.3% of the maximum point of the oscillation-week_f2

[0065] Again referring to FIG. 14, as illustrated the week 5 (or “week f_2) maximum oscillation point 162 is greater than the week 3 maximum 152, so the present application treats the user as having gained weight. Because the week 5 maximum oscillation value 162 is more than one percent of the week three (or “week_f1”), the user is treated as having gained weight according to the present application, and the needle of FIG. 13 will point to portion 340 when the user is gaining weight.

5. Use Example

[0066] With reference to FIG. 15, an illustration of the typically overall use of the present system according to an aspect of the application is provided. This illustration is by way of example only and is not intended to limit the scope of the present application. A user 10 will typically step onto the scale 1110 of weight tracking station 1100. The weight measurement and other data collected from user 10 are typically transmitted and stored in a remote database 2000 (see FIG. 3), typically in the cloud. The resulting information calculated according to the weight trend and oscillation equations described herein are then transmitted to an app that has been downloaded on a mobile device 4000 that belongs to user 10. The information provided to user 10 typically notifies user about the weight loss trend of user 10 and whether such trend is occurring at an appropriate pace. User 10 also can obtain weight trend and other information by logging into the present system using a computer 5000 that is connected to the Internet. Computer 5000 can also typically be used to maintain the overall system by another user such as a system administrator 15 or other person. All of the information collected about the user, as well as all of the calculations and determinations concerning the user, can likewise optionally be shared with others such as healthcare providers, insurance companies, and any other desired entity.

[0067] In another aspect, statistics about weight trend and the BMI for a group of users can be shared with corporate users such as businesses, fitness centers, and healthcare facilities. Such statistics can be used to assist in tracking and monitoring the overall weight trends for different groups of people.

[0068] The functional block diagrams, operational sequences, calculations, and flow diagrams provided in the figures and throughout this application are representative of exemplary architectures, environments, and methodologies for performing novel aspects of the disclosure. While, for purposes of simplicity of explanation, the methodologies included herein may be in the form of a functional diagram, operational sequence, or flow diagram, and may be described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology can alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.

[0069] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.