Methods and systems for interactive weight management

Abstract

A computer implemented method for interactive weight management that includes generating a number of sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n based on a current weight C.sub.w, a desired weight loss amount (ΔW), a desired weight D.sub.w, a curve tension r, and a timeframe (τ) in which the weight loss amount (ΔW) is to be achieved, wherein the timeframe (τ) includes a number (n) of time periods that each correspond with a pair of successive ones of the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n. The method includes sending the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the number (n) of time periods to a weight measuring device that is associated with a user. Based on the condition W.sub.a1>g.sub.i<W.sub.a2 or based on the condition $W_{a1}<\frac{g_i+g_{i+1}}{2}\mathrm{and}{W}_{a2}<\frac{g_{i+1}+g_{i+2}}{2},$
new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are generated and are updated in the weighing device.

Claims

1. A method of communicating weight loss sub-goal weights and measured weights over a network, comprising: providing a memory that is accessible by a server with one or more processors, wherein information for a user is stored on the memory that includes a number (n) of time periods that are consecutive within an overall weight loss timeframe (τ) and weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n that includes an assigned sub-goal weight for an end of each one of a corresponding one of the number (n) of time periods; receiving, by the server, a measured weight W.sub.a for the user from a weighing device; determining, by the server, by comparing a time that the measured weight W.sub.a was received by the server to the number (n) of time periods that are consecutive within the overall weight loss timeframe (τ), a current one of the number (n) of time periods that corresponds to the time that the measured weight W.sub.a was received by the server, storing, in the memory, the measured weight W.sub.a and the current one of the number (n) of time periods in which the measured weight was received; determining, by the server, if the measured weight W.sub.a is the first measured weight W.sub.a received during the current one of the number (n) of time periods, and if the measured weight W.sub.a is the first measured weight W.sub.a received during the current one of the number (n) of time periods, storing, in the memory, one of the measured weights W.sub.a received during a preceding one of the number (n) of time periods as a representative measured weight W.sub.a for the preceding one of the number (n) of time periods; sending, by the server via the network, the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods to one or more user devices that are associated with the user; displaying, on a graphical user interface or display screen of the one or more user devices, numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods; comparing, by the server, the representative measured weight W.sub.a for the preceding one of the number (n) of time periods to an average of the assigned weight loss sub-goal weight for the preceding one of the number (n) of time periods and an assigned weight loss sub-goal weight for the second preceding one of the number (n) of time periods, and comparing, by the server, a second representative measured weight W.sub.a for the second preceding one of the number (n) of time periods to an average of the assigned weight loss sub-goal weight for the second preceding one of the number (n) of time periods and an assigned weight loss sub-goal weight for a third preceding one of the number (n) of time periods, wherein the third preceding one of the number (n) of time periods is consecutive with and before the second preceding one of the number (n) of time periods, and the second preceding one of the number (n) of time periods is consecutive with and before the preceding one of the number (n) of time periods, and if the representative measured weight W.sub.a is less than the average of the assigned weight loss sub-goal weight for the preceding one of the number (n) of time periods and the assigned weight loss sub-goal weight for the second preceding one of the number (n) of time periods, and if the second representative measured weight W.sub.a is less than the average of the assigned weight loss sub-goal weight for the second preceding one of the number (n) of time periods and the assigned weight loss sub-goal weight for the third preceding one of the number (n) of time periods, sending, by the server via the network, a first notification to the one or more user devices that indicates that the user is exceeding the assigned weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and that new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n will be assigned for the user, wherein the first notification is an alphanumeric message selected from a group that includes a text message, a push notification and/or an email message.

2. The method of claim 1, wherein the first notification comprises one or more of an image, a chart, a URL, or a video.

3. The method of claim 1, further comprising: generating, by the server, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n for the user; sending, by the server via the network, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to the one or more user devices that are associated with the user; and displaying, on a graphical user interface or display screen of the one or more user devices, numerical values for the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

4. The method of claim 3, further comprising: sending, by the server via the network, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to a weighing device associated with the user; and displaying, on a display screen of the weighing device, numerical values for the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

5. The method of claim 1, wherein displaying, on a graphical user interface or display screen of the one or more user devices further comprises displaying the numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods as a line chart or a bar chart, wherein the number (n) of time periods within the overall weight loss timeframe (τ) are displayed graphically on an x-axis of the line chart or the bar chart with the numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods are displayed graphically on a y-axis of the line chart or the bar chart.

6. The method of claim 1, further comprising: sending, by the server via the network, the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods to a weighing device associated with the user; and displaying, on a display screen of the weighing device, numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods.

7. The method of claim 6, wherein displaying, on the display screen of the weighing device, further comprises displaying the numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods as a line chart or a bar chart, wherein the number (n) of time periods within the overall weight loss timeframe (τ) are displayed graphically on an x-axis of the line chart or the bar chart with the numerical values for the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the numerical values for the representative measured weight W.sub.a for each one of the number (n) of time periods that are before the current one of the number (n) of time periods are displayed graphically on a y-axis of the line chart or the bar chart.

8. The method of claim 1, where storing, in the memory, one of the measured weights W.sub.a received during the preceding one of the number (n) of time periods further comprises: storing, in the memory, a last one of the measured weights W.sub.a received during the preceding one of the number (n) of time periods as the representative measured weight W.sub.a for the preceding one of the number (n) of time periods.

9. The method of claim 8, further comprising: comparing, by the server, the representative measured weight W.sub.a for the preceding one of the number (n) of time periods to a second representative measured weight W.sub.a for a second preceding one of the number (n) of time periods that is consecutive with and before the preceding one of the number (n) of time periods, and if the representative measured weight W.sub.a and the second representative measured weight W.sub.a are both greater than the assigned weight loss sub-goal weight for the end of the second preceding one of the number (n) of time periods, sending, by the server via the network, a second notification to the one or more user devices that indicates the user is lagging behind and is not meeting the weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and that new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n will be assigned for the user, wherein the second notification is an alphanumeric message selected from a group that includes a text message, a push notification and/or an email message.

10. The method of claim 9, wherein the second notification comprises one or more of an image, a chart, a URL, or a video.

11. The method of claim 9, further comprising: generating, by the server, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n for the user; sending, by the server via the network, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to the one or more user devices that are associated with the user; and displaying, on the graphical user interface or display screen of the one or more user devices, numerical values for the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

12. The method of claim 9, further comprising: generating, by the server, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n for the user; sending, by the server via the network, the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to a weighing device associated with the user; and displaying, on a display screen of the weighing device, numerical values for the new weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

13. The method of claim 1, further comprising: comparing, by the server, the measured weight W.sub.a to the assigned sub-goal weight that corresponds with the end of a corresponding one of the number (n) of time periods that is a last one of the number (n) of time periods, and if the measured weight W.sub.a is equal to or less than the assigned sub-goal weight for the end of the last one of the number (n) of time periods, sending, by the server via the network, a third notification to the one or more user devices that indicates the user has achieved a desired weight that is the assigned sub-goal weight for the end of the last one of the number (n) of time periods and that new maintenance mode weight loss sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n will be assigned for the user, wherein the third notification is an alphanumeric message selected from a group that includes a text message, a push notification and/or an email message.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts. The features of the various illustrated embodiments can be combined unless they exclude each other. Embodiments are depicted in the drawings and are detailed in the description which follows.

(2) FIG. 1 shows the overall system architecture in which weighing device is integrated and communicates with the cloud server, sends the current weight and receives sub-goals and overall performance and displays on its screen. FIG. 1 also shows how user gets feedback on mobile devices and desktop. FIG. 1 also demonstrate how the users reach accountability circle and its features.

(3) FIG. 2 depicts a pictorial view of sub-goals determination, using the formula stated in Equation (6). Input parameters are ΔW, τ, and r.

(4) FIG. 3 shows the sub-goals in W.sub.τ plane for ΔW=50 pounds, τ=20 weeks, and r=0.25. FIG. 3 depicts more weight loss in early sub-goals as compared to the trailing sub-goals.

(5) FIG. 4 demonstrates the sub-goals reassignment condition. The reassignment condition is governed by Equation (11), in which user lags behind the assigned sub-goals. After detecting this condition, the sub-goals are reassigned using updated ΔW, r, and τ.

(6) FIG. 5 shows an example in which user does not meet sub-goals several times but the user is maintaining the pace. Every time the user crosses one sub-goal. Therefore, the user does not need new sub-goals.

(7) FIG. 6 demonstrates the sub-goals reassignment condition. The reassignment condition is governed by equation (12), in which user leaps ahead the assigned sub-goals, after detecting this condition the sub-goals are reassigned per equations (13) and (6).

(8) FIG. 7 depicts the flow chart of the algorithm for determining the sub-goals, detecting lagging behind or leaping ahead conditions and reassignment of the sub-goals.

(9) FIG. 8 illustrates embodiments of curve tension, which governs the weight loss distribution in W.sub.τ plane.

(10) FIG. 9 depicts a portion of the user's dashboard where the system shows the target (suggested) sub-goals and how the user is achieving the sub-goals in a plot of the sub-goals and the achieved goals.

(11) FIG. 10 shows the weighing device screen which is displayed on the dashboard as well. It shows the user's overall progress, how far the user is from the sub-goal, current BMI and current weight.

(12) FIG. 11 depicts the concept of accountability circle, where an accountability group has access to all of its member's dashboards, access of group message board and how they can use the system messages service to communicate with one another.

(13) FIG. 12 shows the quick feedback mechanism. Based on the current weight cloud server sends the users a feedback on their performance and sends the weighing device new sub-goals (if needed) and overall performance.

(14) FIG. 13 shows the flow chart of an algorithm for detecting the lagging and the leaping forward conditions in achieving the sub-goals. After detecting the conditions of lagging or leaping forward, ΔW, τ, and r are adjusted appropriately and fed to the sub-goal generation formula.

(15) FIG. 14 shows the overall flow of the communication among the user's devices, the weighing device (scale) and the weight management services. The Weight Management Services are comprised of User Registration Service, Weight Device Application Programming Interface Service, Sub-goal Generation Service, User Performance Assessment Service, User Notification Service, and User Information Storage Service.

DETAILED DESCRIPTION

(16) In the embodiments illustrated herein, a system is described for effective weight management which provides a framework for cognizant individuals and individuals who have little exposure to weight management knowledge. The system includes a weight measuring intelligent wirelessly connected device, a cloud server to which the device can communicate, and a hand-held mobile device. In various embodiments, algorithms and data reside on one or more cloud servers or cloud-based platforms. In operation, the server pushes an individual's weight loss interim sub-goals to a weight measuring device where the goals are displayed on a Graphical User Interface (GUI) on the device for the individual. In one embodiment, the user device is a mobile device which can receive immediate feedback from the server in regard to the current status of the individual's weight loss progress and also can also access an individual's dashboard residing on the server. In one embodiment, the dashboard is displayed on a GUI of a device such as a mobile device. An individual can view the dashboard and communicate with the server through a common computing device with a screen. In one embodiment, the dashboard is displayed on a GUI of a wireless or cellular connected device such as a cellular phone 110, a tablet 112, a WiFi enabled phone, a wireless or cellular connected weighing device 102, a laptop computer 116 or a desktop computer 118.

(17) In the illustrated embodiments, the weight management system described herein provides an intelligent framework in which individuals are provided with weight loss sub-goals to be achieved, where the current weight loss sub-goals are displayed on the weighing device and/or other user devices as described above. If the individual cannot keep with the current series of sub-goals, or if the sub-goals are too easy to achieve, the weight management system detects this behavior and assigns the individual another set of sub-goals until the individual reaches his/her desired target weight goal. After the individual reaches his/her target weight, the weight management system places the individual on a long-term weight maintenance plan.

(18) In the illustrated embodiments, the intelligent weighing device is an integral part of the weight management system. The device displays to the individual his/her current sub-goal, the individual's standing in reaching the sub-goal, and the overall achievement in reaching the target weight, along with current weight and Body Mass Index (BMI).

(19) In yet another aspect, the system provides a framework in which the individual can choose a desired target weight and the time period in which the desired weight is to be achieved.

(20) In yet another aspect, if the individual sets unrealistic goals in terms of target weight and the time to reach the target weight, the system suggests a realistic target weight loss goal and corresponding interim weight loss sub-goals for the time in which the desired target weight is to be achieved. It is left to individual's discretion if he/she accepts the new target weight loss goal and corresponding interim weight loss sub-goals recommended by the weight management system or keeps his/her previous weight loss goal and the time in which he/she desires to reach the target weight.

(21) In yet another aspect, the system provides a quick feedback to the individual, corrective or reinforcing based on the individual's progress.

(22) In yet another aspect, if the individual insists on his/her prescribed target weight and time, the system accepts it and provide to the individual most suitable sub-goals.

(23) In yet another aspect, if the individual has not weighed himself/herself within a unit of time selected by the individual (e.g., one week), the system sends reminders to the individual to persuade him/her to step on the device for weighing.

(24) In yet another aspect of the weight management system, the system provides accountability framework to the individual before the system itself, friends and family. In various embodiments, Friends and family can be located remotely.

(25) When Individuals realize and attempt to lose their weight, they commonly focus on diet and physical activity, which of course are the key for losing weight. These facts are known to human for decades, yet the overall weight epidemic is ever increasing. It does not mean people don't attempt to lose weight, they do, and the weight loss market of $66 billion clearly demonstrates this. What is missing an effective framework which guides and assists people in reaching their desired target weight. People tend to start a weight loss program with a high level of enthusiasm, but get lost in their pursuit of achieving their target weight. The first issue is people tend to set a large goal to reach, which may take quite a long a time, where the probability of getting lost during the pursuit of the target weight is high. Secondly, when people become a bit uninterested, or fed up, they tend not to weigh themselves often enough and their weight drifts upwards to higher numbers.

(26) In another embodiment, the weight management system provides an accountability framework, referred to herein as an accountability circle. Individuals can get lost on their path to achieving their desired target weight when they are not accountable to any entity. Self-accountability is no accountability. An effective accountability framework is provided by the weight management system that allows individuals to choose their accountability circle members.

(27) In another embodiment, the weight management system provides individuals with their most suitable sub-goals, an accountability mechanism, and timely feedback and coaching to enable the individuals to remedy any current issues that they may have with their weight loss effort. In the absence of this feedback and instant coaching, an individual or user is more likely to lose focus and lose interest.

(28) FIG. 1 illustrates a system architecture at 100 in which weighing device 102 is integrated and communicates with the cloud server 106 via a network 104. Weighing device 102 is a weight scale and is configured to send the current weight of a user to weight management service 108 hosted on cloud server 106 and receive sub-goals and overall performance information. In some embodiments, weighing device 102 is able to display the sub-goal and performance information on a screen display that is located on weighing device 102. FIG. 1 illustrates additional embodiments of how users are able to receive feedback information from weight management service 108, on mobile devices and desktop computers. The feedback information may include sub-goals, overall performance, and body composition by percentage or weight of muscle, fats, bones, and water hydration information, along with constructive feedback and further instructions needed to reach their target weight. FIG. 1 illustrates a cellular phone 110, a tablet 112, a WiFi enabled phone 114, a laptop computer 116 and a desktop computer 118. In various embodiments, these mobile devices and desktop computers are able to communicate via wireless router 120 with cloud server 106 and weight management service 108.

(29) In various embodiments, network 104 communications channels can include, but are not limited to, local area networks (LANs), wide area networks (WAN), wireless local area networks (WLAN), WiFi networks, Third Generation (3G), Fourth Generation (4G), or Fifth Generation (5G) mobile telecommunications network, or any combination of these. In other embodiments, other suitable types of networks may be used. In various embodiments, suitable communications or communications channels can include short message service (SMS) notifications, push notifications, email message communications, chat service, or any suitable web-based service. FIG. 1 also demonstrates how users are able to access their accountability circle and the dashboard and messaging features that the accountability circle provides (see also, FIG. 11).

(30) In the illustrated embodiments, individuals can sign up for the weight management service 108 where they are asked for information such as age and height. They can enter their target weight and associated time limit as well. If a user does not enter the optional information of target weight and associated time frame to lose the weight, the weight management service will generate a target weight and the time required to reach the target weight.

(31) The weighing device 102 is used to acquire the current and subsequent weights reading. As an individual steps on the scale 102, his/her weight is uploaded to the cloud server 106. The weight management service 108 on cloud server 106 determines whether the sub-goals for the individual are already determined. In other embodiments, two or more scales 102′ may be used. In embodiments where the user has a measured weight W.sub.a, that is heavier than the maximum weight that scale 102 can handle accurately, one additional scale 102′ is used and the user may step on two scales, scale 102 and scale 102′, and the user's current measured weight W.sub.a will be obtained by summing the weight from scale 102 with the weight from scale 102′ (see also, FIGS. 7 and 13).

(32) In the illustrated embodiments, if the individual is a new user or is beginning the weight loss process, the weight management service 108 determines the sub-goals based on the individual's requirements. If the individual has not provided a target weight, an ideal weight is estimated using an average (combination) of G. J. Hamwi Formula (1964), B. J. Devine Formula (1974), D. Robinson Formula (1983), and D. R. Miller Formula (1983).

(33) According to the combined formula, the ideal weight in pounds for an adult is:
W.sub.men,ideal=113.5+4.5×(height in inches−60)
W.sub.women,ideal=106.5+4.15×(height in inches−60)

(34) The estimated ideal weight is determined by the weight management service and shared with the individual. If the individual agrees with the suggested target weight determined by the weight management service, the weight management service uses the suggested target weight as the desired weight to be achieved for the individual. If the individual does not agree, the individual needs to provide a desired weight to the weight management service. The estimated ideal weight is designated as the Desired Weight.

(35) Definitions:

(36) C.sub.w=Current Weight

(37) D.sub.w=Desired Weight

(38) ΔW=Required weight drop=C.sub.w−D.sub.w

(39) τ=Time in which D.sub.w is to be achieved

(40) n=number of time units in progress (by default units are weeks)

(41) r=Weight loss distribution (curve tension), this describes the distribution of weight loss from start to end. Examples shown in FIG. 8.

(42) In the illustrated embodiments, curve tension is applied as described herein is used for interactive weight management by weight management service 108. FIG. 8 shows various path the individual may follow to reach the same target weight in the same time period. The behavior of distribution is dictated by r, the curve tension. FIG. 8 represents various examples for r=2.0 to r=0.001. People do not necessarily lose the same amount of weight in every time period. Generally, people lose more weight in the beginning than towards the end of a given time period during their weight loss effort. Due to a number of factors, often times, the last several pounds can be the most difficult to lose. The concept of curve tension, as described in the embodiments herein, has been found to be very meaningful and accurate in the formulation of weight loss sub-goals or for weight management in general.

(43) In the illustrated embodiments, if the user has provided a desired weight D.sub.w, and a time period τ in which D.sub.w is to be achieved, the system proceeds with the determination of the weight loss sub-goals. In the determination of the sub-goals, ΔW, r, and τ are the input variables used by the weight management service. In the illustrated embodiments, the sub-goal determination formula is as follows:

(44) Anytime weight, W.sub.r, during weight loss period is modeled as
W.sub.r=ΔWe.sup.−rn+D.sub.w  (1)

(45) In the illustrated embodiments, when applying the concept of curve tension, weight loss is modeled around e.sup.−x due to the non-linearity of the weight loss function by an individual. The weight loss function has been found to not to be linear with time, thus a straight line or linear model will not accurately reflect the weight loss function. This is because at the beginning of the weight loss process, people or users tend to lose weight easily and quickly, and when close to a desired weight, people tend to find that the last several pounds are more difficult to lose. In the embodiments illustrated herein, the long tail of the function e.sup.−x is eliminated by restricting the function to operate before long tail begins.

(46) In one exemplary embodiment, weight loss equation (2) is utilizing e.sup.−2 functionality. The weight loss is modeled as

(47) $W_l=\frac{\Delta {\mathrm{We}}^{-rn}}{1-e^{-2}}$
and transitioning the working area within ΔW:

(48) $\begin{array}{cc}{W}_l=\frac{\Delta {\mathrm{We}}^{-rn}}{1-e^{-2}}-\Delta W\frac{e^{-2}}{1-e^{-2}}& \left(2\right)\end{array}$

(49) In one exemplary embodiment, weight loss equation (3) is utilizing e.sup.−3 functionality. The weight loss is modeled as

(50) $W_l=\frac{\Delta {\mathrm{We}}^{-\mathrm{rn}}}{1-e^{-3}}$
and transitioning the working area within ΔW:

(51) $\begin{array}{cc}{W}_l=\frac{\Delta {\mathrm{We}}^{-\mathrm{rn}}}{1-e^{-3}}-\Delta W\frac{e^{-3}}{1-e^{-3}}& \left(3\right)\end{array}$

(52) After generalization of (2) and (3) in terms of τ, the generic formula for weight loss is:

(53) $\begin{array}{cc}{W}_l=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-\mathrm{rn}}{10}}-e^{-\frac{r\tau }{10}}\right),n=\left\{0,1,2,\mathrm{.Math.}\tau \right\}\mathrm{and}\tau ,r=\ne 0& \left(4\right)\end{array}$

(54) In embodiments where the user has not provided τ, the time in which D.sub.w is to be achieved, τ can be determined as follows:

(55) $\begin{array}{cc}\tau =\frac{\Delta W}{1.5}& \left(5\right)\end{array}$

(56) In the embodiments described herein, T and r are dynamically adjusted and get tuned based on the user's performance in terms of meeting their weight loss sub-goals.

(57) Sub-goals are determined using the weight drop formula as follows:

(58) 0$\begin{array}{cc}{W}_l=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-rn}{10}}-e^{-\frac{r\tau }{10}}\right),=\left\{0,1,2,\mathrm{.Math.}\tau \right\},W_i\mathrm{for}n=0\equiv \Delta W& \left(6\right)\end{array}$

(59) In the illustrated embodiments, based on user's input, r and τ are set. In other embodiments, n is not an integer value. In some embodiments, r is automatically set to r=0.25, and r is adjusted adaptively during the weight loss effort if sub-goals are not met or if sub-goals are met well in advance. In some embodiments, if τ is not provided by the user, it is determined by equation (5).

(60) In the illustrated embodiments, the sub-goals are set as follows:

(61) First sub-goal g.sub.1: g.sub.0 to g.sub.1, where g.sub.0>g.sub.1,

(62) Second sub-goal g.sub.2: g.sub.1 to g.sub.2, where g.sub.1>g.sub.2,

(63) Last sub-goal g.sub.n: g.sub.n−1 to g.sub.n, where g.sub.n−1>g.sub.n, where n≥2 and is any suitable number.

(64) FIG. 2 illustrates an embodiment of sub-goal determination using equation (10) as described above. Input parameters for equation (10) are ΔW, τ, n and r. FIG. 2 illustrates a weight loss timeline in a horizontal direction at 202, where the total time between g.sub.0 and g.sub.n is equal to τ as indicated, where τ is the total time in which the desired weight loss ΔW is to be achieved, and where each sub-goal weight g.sub.0, g.sub.1, . . . g.sub.n is determined by adding the desired weight D.sub.n, to the weight calculated by equation (10). FIG. 2 also illustrates sub-goal weights, g.sub.0, g.sub.1, . . . g.sub.n along the horizontal timeline 202, where each successive sub-goal weight is less than a previous sub-goal weight (see also, Table 2). The sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n represent a sub-goal weight for the end of a specific time period (e.g., 204,206, 208, 210). The sub-goal weight g.sub.0 corresponds with a weight at the beginning of the first time period 204. In the illustrated embodiment, the sub-goal weight g.sub.0 at the beginning of the first time period 204 corresponds with the current weight c the sub-goal weight g.sub.1 represents the sub-goal weight at the end of the first time period 204, and the sub-goal weight g.sub.n represents the sub-goal weight at end of the last time period 104. In the illustrated embodiment, the sub-goal weight at the end of the time period τ corresponds with the desired weight D.sub.w. In some embodiments, a larger sub-goal is made combing two or more consecutive sub-goals. In other embodiments, the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n can represent a sub-goal weight for another part of a specific time period (204,206, 208, 210), such as at the beginning of the time period (204,206, 208, 210) or in the middle of the time period (204,206, 208, 210).

(65) In the illustrated embodiment, the values of n for g.sub.1, g.sub.2, . . . g.sub.n correspond with the end of a time period (e.g., 204,206, 208, 210) where a user's weight is measured by weighing device 102 and compared to the assigned sub-goal weight g.sub.i for that time period. In one embodiment, if τ=20 weeks and n represents a time period in weeks, the time period 204 between g.sub.0 and g.sub.1 is equal to one week and the value of g.sub.1 at the end of the first time week (n=1) is equal to the sub-goal weight g.sub.1 at the end of the first week. In one embodiment, if τ=20 weeks and n represents a time period in weeks, the time period 206 between g.sub.1 and g.sub.2 is equal to one week and the value of g.sub.2 at the end of the second time period 206 after two weeks have passed (n=2) is equal to the sub-goal weight g.sub.2 at the end of the second week.

(66) In the illustrated embodiment, weight loss W.sub.l is determined by using equation (6) above for W.sub.0, W.sub.1, . . . W.sub.n and adding the result of equation (6) to the desired weight D.sub.w as follows:

(67) $\begin{array}{cc}{g}_0=W_0+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{0}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w=C_w& \left(7\right)\\ g_1=W_1+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-r}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w& \left(8\right)\\ g_2=W_2+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-2r}{10}}-e^{\frac{-r\tau }{10}}\right)+D_w& \left(9\right)\\ g_n=W_n+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-\mathrm{nr}}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w=D_w& \left(10\right)\end{array}$

(68) In the illustrated embodiment, the measured weight W.sub.a, of a user is determined by weighing device 102 and is illustrated in FIGS. 4-6 as W.sub.a. During each time period, multiple weights may be taken within a time period and communicated to weight management service 108 via network 106. However, the last the measured weight W.sub.a within a time period (e.g., 204,206, 208, 210) that is communicated to weight management service 108 is the measured weight W.sub.a used by weight management service 108 for determination of reassignment of sub-goals g.sub.0, g.sub.1, . . . g.sub.n. For example, for time period 204 from assigned sub-goal g.sub.0 to assigned sub-goal g.sub.1, the last measured weight is indicated as W.sub.a1. In other embodiments, the measured weight W.sub.a used by weight management service 108 for determination of reassignment of sub-goals g.sub.0, g.sub.1, . . . g.sub.n. can be the first measured weight within a time period (e.g., 204,206, 208, 210), or can be the average or median measured weight within a time period (e.g., 204,206, 208, 210).

(69) In the illustrated embodiments, FIGS. 4, 5 and 6 illustrate placement of measured weights W.sub.a, along the weight loss timeline that correspond to the value of W.sub.a, relative to the value of the assigned sub-goals g.sub.0, g.sub.1, . . . g.sub.n. For example, if measured weight W.sub.a1 is greater than the assigned sub-goal g.sub.1 for the time period 204 where n=1 (e.g., user did not meet goal weight), the measured weight W.sub.a1 will be shown to the left of the assigned sub-goal g.sub.1 as W.sub.a1 is greater than g.sub.1. In some embodiments, the placement of W.sub.a1 corresponds to a value represented by equation (10) (see also, FIG. 3).

(70) FIG. 3 illustrates an embodiment at 300 of sub-goals W.sub.0, W.sub.1, . . . W.sub.20 generated by weight management service 108 for weight loss relative to desired weight loss ΔW is using equation (6) above in which ΔW=50 pounds, τ=20 weeks and set to r=0.25. The time, τ, is illustrated along the horizontal axis in units of weeks and weight is illustrated along the vertical axis in units of pounds.

(71) In the illustrated embodiment, curve 302 illustrates numerical values of weight loss sub-goals W.sub.0, W.sub.1, . . . W.sub.20 for which ΔW=50 pounds and illustrates an embodiment with curve tension set to r=0.25 where the weight loss for early sub-goals is greater that for trailing or later sub-goals near 20 weeks. FIG. 3 illustrates the sum of the weight loss goals for the first five weeks from week 0 to week 5 (50 pounds−35.1 pounds=14.9 pounds), is greater than the weight loss goals for the last five weeks from week 15 to week 20 (10.3 pounds−0 pounds=10.3 pounds).

(72) In the illustrated embodiment, FIG. 3 illustrates weight loss sub-goals W.sub.0, W.sub.1, . . . W.sub.n to achieve the weight drop ΔW, where ΔW is equal to the current weight C.sub.w minus the desired weight D.sub.w. Table 1 corresponds with FIG. 3 and illustrates an embodiment of values for W.sub.0, W.sub.1, . . . W.sub.20 for ΔW=50 Lbs., r=0.25, and τ=20 weeks for curve 302 as follows:

(73) TABLE-US-00001 TABLE 1 W.sub.0 50.0 W.sub.1 46.8 W.sub.2 43.8 W.sub.3 40.8 W.sub.4 37.9 W.sub.5 35.1 W.sub.6 32.3 W.sub.7 29.6 W.sub.8 27.0 W.sub.9 24.4 W.sub.10 21.9 W.sub.11 19.5 W.sub.12 17.1 W.sub.13 14.7 W.sub.14 12.5 W.sub.15 10.3 W.sub.16 8.1 W.sub.17 6.0 W.sub.18 4.0 W.sub.19 2.0 W.sub.20 0

(74) In the illustrated embodiment, FIG. 3 illustrates weight loss sub-goals weight loss sub-goals W.sub.0, W.sub.1, . . . W.sub.n to achieve the weight drop ΔW, where ΔW is equal to the current weight C.sub.w minus the desired weight D.sub.w. The weight loss W.sub.1 is set by using equation (6) above for W.sub.0, W.sub.1, . . . W.sub.n as follows:

(75) $\begin{array}{cc}{g}_0=W_0+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{0}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w=C_w& \left(7\right)\\ g_1=W_1+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-r}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w& \left(8\right)\\ g_2=W_2+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-2r}{10}}-e^{\frac{-r\tau }{10}}\right)+D_w& \left(9\right)\\ g_n=W_n+D_w=\frac{\Delta W}{1-e^{-\frac{r\tau }{10}}}\left(e^{\frac{-\mathrm{nr}}{10}}-e^{-\frac{r\tau }{10}}\right)+D_w=D_w& \left(10\right)\end{array}$

(76) Adding D.sub.w to {W.sub.0, W.sub.1, W.sub.2, . . . W.sub.20} as illustrated by equations (7)-(10) yields the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n shown in Table 2. Table 2 illustrates an embodiment of values for g.sub.0, g.sub.1, . . . g.sub.20, for D.sub.w=190 where ΔW=50 pounds, τ=20 weeks, n=1 week and r=0.25 as follows

(77) TABLE-US-00002 TABLE 2 g.sub.0 240 g.sub.1 236.8 g.sub.2 233.8 g.sub.3 230.8 g.sub.4 227.9 g.sub.5 225 g.sub.6 222.3 g.sub.7 219.6 g.sub.8 217 g.sub.9 214.4 g.sub.10 211.9 g.sub.11 209.4 g.sub.12 207.1 g.sub.13 204.7 g.sub.14 202.5 g.sub.15 200.3 g.sub.16 198.1 g.sub.17 196 g.sub.18 194 g.sub.19 192 g.sub.20 190

(78) After sub-goals are determined by weight management service 108 per equation (10), and optionally using equation (5), weight management service 108 communicates the sub-goals to weighing device 102 via network 106 where the sub-goals are stored, for periodic display, on a GUI or display on weighing device 102. In various embodiments, the sub-goals may also be communicated, via network 106, to one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and/or desktop computer 118, where the sub-goals are stored, for periodic display, on a GUI or display for one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and/or desktop computer 118. FIG. 7 and FIG. 13 illustrate further embodiments of sub-goal determinations by weight management service 108.

(79) In the illustrated embodiment, if weight management service 108 determines a user cannot reach his/her desired weight D.sub.w, via one or more measured weights W.sub.a of a user that is measured by weighing device 102 and communicated to weight management service 108 via network 106, weight management service 108 determines and assigns new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and communicates the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to weighing device 102 via network 106 (see also FIGS. 4, 5, 6, 7 and 13). In various embodiments, the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n may also be communicated, via network 106, to one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and/or desktop computer 118, where the sub-goals are stored, for periodic display, on a GUI or display for one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and/or desktop computer 118.

(80) In the illustrated embodiments, when weight management service 108 determines new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are to be reassigned, in various embodiments, FIGS. 4, 5, 6, 7 and 13 illustrate methods and algorithms used to determine the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n that are communicated to weighing device 102 and/or one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118 via network 106.

(81) In two exemplary embodiments, weight management service 108 determines new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n (as illustrated in FIGS. 4, 5, 6, 7 and 13) utilizing two conditions/options: 1) Keep the time to reach the ultimate goal, τ, the same and change r to a lower value. This change in curve tension r will result in higher sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n (e.g., less weight loss between sub-goals) as determined by equation (10) with the early sub-goal weights such as g.sub.0, g.sub.1 when compared to the previous remaining sub-goal weights before reassignment of the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n. 2) Update either the desired weight D.sub.w, or τ, the time required to achieve the weight drop ΔW. Per user's choice either τ would be increased or D.sub.w would be increased to a realistic value. The condition is applied when a user is not making weight loss progress as determine by one or more of FIGS. 4, 5, 6, 7 and 13)

(82) Various embodiments of the updates and reassignment of the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are illustrated in FIG. 13. In these embodiments, sub-goal progress is monitored and new sub-goals are assigned. During the initial setup, the desired goal and time, i.e., D.sub.w and τ, would be assessed and user will be informed if D.sub.w and τ are unrealistic and will be suggested with a realistic achievable option.

(83) FIG. 4 illustrates an embodiment at 400 of a sub-goal reassignment conditions when weight management service 108 determines new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are to be reassigned. The reassignment condition utilized by weight management service 108 is governed by equation (11) and illustrates a condition where a user's measured weights W.sub.a1 for week i, and W.sub.a2 for week i+1 are greater than the assigned sub-goal weight g.sub.i for two consecutive measurement periods.

(84) In an embodiment, let W.sub.a1 be the actual weight for the sub-goal g.sub.i, and W.sub.a2 be the actual weight for the sub-goal g.sub.i+1. The following condition at (11) is utilized by weight management service 108 to determine if new sub-goal and reassignment weights g.sub.0, g.sub.1, . . . g.sub.n are communicated to weighing device 102 and/or one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118 via network 106:
W.sub.a1>g.sub.i<W.sub.a2  (11)

(85) In this embodiment, the users measured weight W.sub.a2 was expected to be at g.sub.i+1 but instead is greater than g.sub.i as shown in FIG. 4. This “lag” meets the reassignment condition set by equation (11), and is sufficient for weight management service 108 to determine and reassign new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and communicate the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n to weighing device 102 and/or one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118 via network 106. Weight management service 108 determines and reassigns the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n using updated values of ΔW, r, and τ as illustrated in FIG. 13.

(86) FIG. 5 illustrates an embodiment at 500 of a sub-goal reassignment conditions when weight management service 108 determines new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are not to be assigned. In this embodiment, via measured weights W.sub.a, of a user that is measured by weighing device 102 and communicated to weight management service 108 via network 106, weight management service 108 determines that a user is not meeting the assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n but the user is also maintaining a weight loss pace as follows. In this embodiment, weight W.sub.a1 was expected to be at g.sub.i and W.sub.a2 was expected to be at g.sub.1+1. Because measured weights W.sub.a1, W.sub.a2, W.sub.a3, W.sub.a4 are within respective time periods 502, 504, 506, 508 that correspond with sub-goal weights g.sub.i, g.sub.i+1, g.sub.i+2, g.sub.i+3, each time the user is crossing or exceeding one of the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and is maintaining pace and sub-goals are not reassigned. In this embodiment, there are no more than one measured weights W.sub.a1, W.sub.a2, W.sub.a3, W.sub.a4 within a respective time periods 502, 504, 506, 508. Thus if a user misses a sub-goal weight g.sub.i, g.sub.i+1, g.sub.i+2, g.sub.i+3 for each time period (e.g., 502, 504, 506, 508), but he/she crossed or exceeded a sub-goal weight g.sub.i, g.sub.i+1, g.sub.i+2, g.sub.i+3 each time a measured weight W.sub.a1, W.sub.a2, W.sub.a3, W.sub.a4 was taken by weight management service 108, new sub-goals are not reassigned for the user.

(87) FIG. 6 illustrates an embodiment at 600 of a sub-goal reassignment condition when weight management service 108 determines new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are to be assigned. In this embodiment, via measured weights W.sub.a of a user that is measured by weighing device 102 and communicated to weight management service 108 via network 106, weight management service 108 determines that a user is exceeding the assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n for two measurement time periods 602, 604, 606, 608. The measurement time periods 602, 604, 606, 608 are shown on a horizontal axis. The reassignment condition is governed by equation (12) and illustrates a condition where a user's measured weights, W.sub.a1 and W.sub.a2 are less than the assigned sub-goal weight g.sub.i for two consecutive two measurement time periods 602, 604, 606, 608. In FIG. 6, measured weight W.sub.a1 was expected to be at g.sub.1 but is ahead of g.sub.1 and is within time period 604, and W.sub.a2 was expected to be at g.sub.i+1 but is ahead of g.sub.1+1 and is within time period 606.

(88) The reassignment condition is determined by equation (12) and represents a situation in which user leaps ahead (e.g., loses weight more quickly) than the assigned sub-goals. After detecting this condition, the sub-goals are reassigned per equations (13) and (10).

(89) For sub-goal g.sub.i, if an individual achieves

(90) $\begin{array}{cc}{W}_{a1}<\frac{g_i+g_{i+1}}{2}\mathrm{and}{W}_{a2}<\frac{g_{i+1}+g_{i+2}}{2}& \left(12\right)\end{array}$
the individual is leaping ahead and new sub-goals need to be reassigned. In this embodiment, where the user is achieving their weight loss sub-goals ahead of time, and for two consecutive measurement time periods 602, 604, 606, 608, increasing the curve tension r will result in lower sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n (e.g., greater weight loss) with the early sub-goal weights as compared to the previous sub-goal weights before reassignment of the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

(91) In this embodiment, the reassignment parameters would be:

(92) $\begin{array}{cc}\begin{array}{c}\Delta W^{\prime }=W_{a1}-D_w\\ r^{\prime }=r+0.25\\ {\tau }^{\prime }=\tau -n\end{array})& \left(13\right)\end{array}$

(93) FIG. 7 depicts an embodiment at 700 for assigning sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n. The sub-goal assignment is performed by weight management service 108 and the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are communicated to weighing device 102 via network 104. In one embodiment, the method is executed by one or more processors located on a cloud server 106. In other embodiments, weight measurement device or scale 102 requests the cloud server 106 to send new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n if new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are required for scale 102 as shown in FIG. 1 and as discussed above. The method begins at 702. At 704, a user steps on scale 102 and the user's current measured weight W.sub.a, is uploaded by operation 704 to a weight management service 108 that is hosted on cloud server 106 and via a network 104.

(94) In embodiments where the user has a measured weight W.sub.a that is heavier than the maximum weight that scale 102 can handle accurately, the user may step on two scales, scale 102 and scale 102′, and the user's current measured weight W.sub.a will be obtained by summing the weight from scale 102 with the weight from scale 102′. In this embodiment, cloud server 106 and weight management service 108 is already aware via a notification from a user device as cellular phone 110, a tablet 112, a WiFi enabled phone 114, a wireless or cellular connected weighing device or scale 102, a laptop computer 116 or a desktop computer 118 that these two machines (scale 102 and scale 102′) are paired. In one embodiment, the serial numbers of the two scales 102 and 102′ are associated with each other. As soon as server 106 receives a measured weight W.sub.a from one of the associated scales 102, server 106 retrieves the reading of the other associated or paired scale 102′. The server 106 adds the two weights coming from scales 102 and 102′ and sends back to the screens of one or both of the scales 102 and 102′ the sum of the two weights which is the user's current measured weight W.sub.a, and may also send other information as well.

(95) In the illustrated embodiment, an operation 706 determines whether sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n have been defined for the user. Upon determining that sub-goals have not been defined, operation 708 determines whether the user has provided a desired weight D.sub.w and a time τ in which D.sub.w is to be achieved. If operation 708 determines that the user has provided a desired weight D.sub.w and a time τ in which D.sub.w is to be achieved, the operation at 712 is performed. If operation 708 determines that the user has not provided a desired weight D.sub.w and a time τ in which D.sub.w is to be achieved, operation 710 determines an ideal weight based on the equations shown in Par. [0045] and based on the user's height and current weight and the required time frame based on equation (5).

(96) Once operation 710 determines an ideal weight and required time frame based on the user's information, the operation at 712 is performed. The operation at 712 determines the parameters ΔW, τ, and r for determining sub-goals per equation (10). Once the operation at 712 determines the parameters ΔW, τ, and r for determining sub-goals, the operation at 718 is performed.

(97) If operation 706 determines that sub-goals have been defined for the user, the operation at 714 is performed. Operation 714 determines whether the user is within the sub-goal guidelines as determined by equations (11), (12). If operation 714 determines the user is within the sub-goal guidelines, the system waits for the next event at 704, where user's next measured weight W.sub.a is uploaded to the server 106 and weight management service 108 and discussed above. If operation 714 determines that the user is not within the sub-goal guidelines, the operation at 716 is performed. The operation 716 adjusts values of ΔW, τ, and r per equation (13). Once the operation at 716 has adjusted the values of ΔW, τ, and r, the operation at 718 is performed which is equation (10). Further details of embodiments of the update of ΔW, τ, and r are depicted in FIG. 13. Equation (10) is executed for n=0, 1, 2, . . . τ for the condition g.sub.i=W.sub.l+D.sub.w as illustrated with equations (7)-(10).

(98) Once the operation at 718 has executed the sub-goals equation (10), the operation at 720 is performed. Operation 720 pushes or sends the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the final target weight D.sub.w to the scale 102 from cloud server 106 via network 104. Once operation 720 pushes the sub-goals and final target weight to the scale 102, the operation at 704 is performed.

(99) FIG. 8 demonstrates an embodiment at 800 of curve tension, which governs the weight loss distribution in the W.sub.τ plane as discussed above. The higher the curve tension is (value of r), the lower the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n (e.g., greater weight loss) will be for the early sub-goal weights as compared to the previous sub-goal weights before reassignment of the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n. The higher the curve tension is (value of r), the more quickly weight loss is expected to be achieved for the earlier weeks and weight loss is expected to occur slowly for the trailing sub-goals.

(100) FIG. 8 illustrates values of r=2 at 802, r=1 at 804, r=0.5 at 806, r=0.35 at 808, r=0.25 at 810 and r=0.001 at 812. Curves 802, 804, 806, 808, 810 and 812 are determined using equation (6) above with ΔW=50 Lbs. and τ=20 weeks.

(101) FIG. 9 illustrates an embodiment of a portion of a user dashboard at 900. User dashboard 900 illustrates assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and measured weights W.sub.a provided by weight management service 108 to one or more user devices such as cellular phone 110, a tablet 112, a WiFi enabled phone 114, a wireless or cellular connected weighing device or scale 102, a laptop computer 116 or a desktop computer 118, and displayed on the GUI or display of the one or more devices. In the illustrated embodiment, an exemplary measured weight W.sub.a, at 902 for an exemplary respective time period W3 illustrated at 906 corresponds with an exemplary sub-goal weight g.sub.3 illustrated at 904 (see also, FIG. 5).

(102) FIG. 10 illustrates an embodiment of a GUI or screen at 1000 of a weighing device 102. Information displayed on the screen 1000 may also be displayed on dashboard 900 (see also, FIG. 9). Screen 1000 illustrates the user's overall progress towards the desired weight D.sub.w, the status or progress of a user from meeting their sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n, a current Body Mass Index (BMI), overall sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and the user's current measured weight W.sub.a. The screen 1000 or portions thereof may also be displayed on a GUI or display of one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118.

(103) FIG. 11 illustrates an embodiment of an accountability circle at 1100. With accountability circle 11, an accountability group 1102 (e.g., a number of users that have mutually agreed to be in the accountability circle) has access to all of its members dashboards illustrated at 1104 (see also, dashboard 900 in FIG. 9 and screen 1000 in FIG. 10) and access to a group message-board at 1106 and how they can communicate using system messages at 1108. In one embodiment, the level of information sharing in individual dashboards 1104 can be set by the user that initially set up the accountability circle and owns the account associated with one of the dashboards 1104.

(104) In the illustrated embodiment, the user is encouraged to achieve weight management accountability with friend(s) or relative(s) or acquaintance(s) and setup an accountability framework, which is accountability circle 1100. The user may share his/her one of the dashboards 1104 with others with whom he/she wants to be accountable with to form an accountability group as illustrated at 1100. During the account setup via of one of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118 using weight management service 108 via network 104 (see also, FIG. 1). With this embodiment, users are able to setup their own permissions and the degree to which they want members with in their accountability group 1102 to view their progress and their dashboard 1104. The dashboard 1104 is accessible via a device such as cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 via an app or https (Hyper Text Transfer Protocol Secure) that communicates with weight management service 108 running on cloud server 106. The dashboard 1104 is also accessible via desktop through World Wide Web using https via weight management service 108 running on cloud server 106 (see also, FIG. 11).

(105) In the illustrated embodiment, the accountability group 1102 has access to a private message board 1106 where the members of accountability group 1102 can share various information or provide positive or corrective feedback to the members of the accountability group 1102. The message board 1106 is accessible via a device such as cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 via an app or https (Hyper Text Transfer Protocol Secure) that communicates with weight management service 108 running on cloud server 106. The dashboard 1104 is also accessible via desktop through World Wide Web using https via weight management service 108 running on cloud server 106 (see also, FIG. 11).

(106) Accountability group has access to messages 1108 where each member can chat interactively with others who are available via weight management service 108 and whom are members of the accountability group 1102. They can share their messages 1108 via weight management service 108 as they deem appropriate (see also, FIGS. 9 and 10). The messages 1108 may be sent via a device such as cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 via an app or https (Hyper Text Transfer Protocol Secure) that communicates with weight management service 108 running on cloud server 106. The messages 1108 are also accessible via desktop through World Wide Web using https via weight management service 108 running on cloud server 106 (see also, FIG. 11).

(107) FIG. 12 illustrates an embodiment of a quick feedback mechanism at 1200. Based on the current weight as shown on a GUI or screen 1000, the quick feedback factors can include, but are not limited to, the number of missed sub-goal weights g.sub.0, g.sub.1, . . . , g.sub.n, the number of sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n that were successively achieved, BMI, height, muscle weight, fat weight, water weight and overall weight loss performance.

(108) In the illustrated embodiment, the quick feedback information is provided through communication channel 1204 from weight management service 108, where the communication channel 1204 can include, but is not limited to, local area networks (LANs), wide area networks (WAN), wireless local area networks (WLAN), WiFi networks, Third Generation (3G), Fourth Generation (4G), or Fifth Generation (5G) mobile telecommunications network, or any combination of these (see also, FIG. 1). In the illustrated embodiment, the quick feedback information is provided to one or more of a cellular phone 110, a tablet 112, a WiFi enabled phone 114, a laptop computer 116 or a desktop computer 118 (see also, FIG. 1).

(109) As user steps on the weighing device 102, the weight is uploaded to the cloud server 106, and weight management service 108 determines if the user 1002 is succeeding in reaching the sub-goal using equation (11) and equation (12). If user 1002 is achieving sub-goals successfully, weight management service 108 sends positive reinforcing feedback to one or more of the users 1002 devices such as cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 and desktop computer 118. If user 1002 is lagging behind per equation (11), the weight management service 108 sends the user 1002 feedback urging the user 1002 to increase his/her physical activities and control the diet along with other tips and suggestions. Based on the number of goal misses and weight drift from the desired sub-goals, a proper message is sent. To assist the user with diet and physical activities, recipes for healthy food, selection of healthy food, running, walking, and weight training related messages are sent to the user 1002 based on user's choice in his/her profile.

(110) FIG. 13 depicts an embodiment at 1300 for determining if a user is achieving their assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n, or lagging behind or leaping ahead of their assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n. The method is executed by one or more processors on the cloud server 106 and weight management service 108. In other embodiments, the sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n have already been assigned, communicated to scale 102 and displayed on a GUI or display of scale 102. The method begins at 1302. At 1304, a user steps on scale 102 and the user's current measured weight W.sub.a, is uploaded by operation 1304 to weight management service 108 that is hosted on cloud server 106.

(111) In embodiments where the user is heavier than the maximum weight that scale 102 can handle accurately, the user may step on two scales, scale 102 and scale 102′, and the user's current measured weight W.sub.a is obtained by summing the weight from scale 102 with the weight from scale 102′. Cloud Server 106 already is aware through settings, registration or previous communication with scale 102 and/or scale 102′ that these two machines are paired. In one embodiment, the serial numbers of the two scales are associated with each other by weight management service 108. As soon as server 106 or weight management service 108 receives a weight reading from the scale 102, server 106 or weight management service 108 retrieves the reading of the other associated or paired scale 102′. The server 106 adds the two weights coming from scales 102 and 102′ and sends back to the GUI or screens of one or both of the scales 102 and 102′ the sum of the two weights which is the user's current measured weight W.sub.a, and may also send other information as well.

(112) In the illustrated embodiment, an operation 1306 determines whether sub-goals are met or the user is lagging behind. This determination is achieved by the condition W.sub.a1>g.sub.i<W.sub.a2 and as shown by equation (11). Upon determining that sub-goals and weights don't meet the lagging behind condition as shown at 1306 and equation (11), operation 1308 determines whether the user is leaping forward more quickly than the assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n as determined by operation 1308 and/or equation (12) (see also, FIG. 7). If operation 1308 determines that the user is not leaping forward per conditions shown in 1308, new sub-goals are not required, and the previously assigned sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n are used. If operation 1308 determines that the user is leaping forward per conditions W.sub.a1<½(g.sub.i+g.sub.i+1) and W.sub.a2<½(g.sub.i+1+g.sub.i+2) (e.g., equation (12)), a new set of updated ΔW, τ, and r values are determined by operation 1320, i.e., ΔW′=W.sub.a1−D.sub.w, r′=r+0.25, and τ′=τ−n which is equation (13). Operation 1318 takes these updated values ΔW, T, and r and re-generates the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n.

(113) If operation 1306 determines that the user is lagging behind per the condition W.sub.a1>g.sub.i<W.sub.a2, operation 1312 looks at the value of the curve tension r. If operation 1312 determines the value of r is ≤0.05, new set of ΔW, τ, and r are calculated by operation 1316. Since the user already has a lower curve tension (very close to 0), the time period in which ΔW needs to be achieved, τ, is incremented by 1 and ΔW and r are updated as follows: ΔW′=W.sub.a1−D.sub.w and r′=0.005. These updated parameters are fed to the operation at 1318. Once the operation 1318 has executed the sub-goals equation (10) as shown at 1318, the operation at 1322 is performed. Operation 1322 pushes or sends the new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and final target weight D.sub.w to the scale 102 from cloud server 106 and weight management service 108 via network 104. Once operation 1322 pushes the sub-goals and final target weight to the scale 102, the operation at 1304 is performed where the user steps on scale 102. If operation 1312 determines that the curve tension, r, is higher than 0.05, operation 1314 reduces the curve tension by 0.25. In other embodiments, the curve tension may be changed by 0.15 or other suitable values. Operation 1314 also updates ΔW and τ as: ΔW′=W.sub.a1−D.sub.w and τ′=τ−n. The updated parameters are fed to operation 1318 (performed by cloud server 106 and weight management service 108) which generates new sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n and operation 1322 pushes the updated goals and final target weight (via network 104) to the scale 102. In one embodiment, discrete values of curve tension used are 1, 0.75, 0.5, 0.25, 0.05, and 0.005. In other embodiments, other suitable values of curve tension r can be used.

(114) FIG. 14 illustrates an embodiment of an overall flow of inter-communication between a user's smart device 1401 (e.g., one or more of cellular phone 110, tablet 112, WiFi enabled phone 114, laptop 116 or desktop computer), weighing device 1402 (e.g., scale or weighing device 102), and Weight Management Services 1403 (weight management service 108 hosted on cloud server 102). In the illustrated embodiment, weight management service includes User Registration Service 14031, Weighing Device Application Programming Interface Service 14032, Sub-goal Generation Service 14033, User Performance Assessment Service 14034, User Notification Service 14035 and User Information Storage Service 14036.

(115) In the illustrated embodiment, a user identifies user information at user device 1401 and submits the user information from user device 1401 to User Registration Service 14031. In the illustrated embodiment, content is presented at user device 1401 that allows the user to provide information that includes, but is not limited to, name, address, contact information, gender, weight management objectives, preferred units for weight and height measurement, target or desired weight (D.sub.w), height, age and a weighing device serial number at 1404. The User Registration Service 14031 stores the user information and sends the user information at 1405 to User Information Storage Service 14036 for use by other services within Weight Management Service 1403. The User Information Storage Service 14036 generates an acknowledgement of the receipt of the registration at 1406 and sends the acknowledgment to the user device 1401 at 1406. In one embodiment, User device 1401 and weighing device 1402 communicate with each other using a local WiFi wireless network. In other embodiments, a cellular network may be used. In the illustrated embodiment, if the smart scale may not have a mechanism to add a WiFi SSID and password, content is presented at user device 1401 that allows a user to send the WiFi SSID and password to the weighing device 1402 at 1407. In one embodiment, the weighing device 1402 is placed in a broadcast mode that generates a broadcast channel from weighing device 1402 and the user device 1401 provides the WiFi SSID and password on the broadcast channel. Once the WiFi SSID and password are received by weighing device 1402, the broadcast channel is closed and user device 1401 and weighing device 1402 are able to communicate with each other over the WiFi network. In one embodiment, user device 1401 and weighing device 1402 can communicate over a Bluetooth network. In the illustrated embodiment, a user steps on weighing device 1402 and weighing device 1402, in response, sends the user's measured weight (W.sub.a) along with the user's identification information to Weighing Device Application Programming Interface Service 14032 at 1410. If weighing device 1402 is not able to identify the user via the user's measured weight (W.sub.a), weighing device 1402 communicates with user device 1401 to validate the user's identification information at 1408. User device 1401 communicates the user identification information at 1409 to weighing device 1402.

(116) In the illustrated embodiment, Weighing Device Application Programming Interface Service 14032 sends an acknowledgement at 1411 to weighing device 1402 to confirm that the user's measured weight (W.sub.a) was received by Weighing Device Application Programming Interface Service 14032. Weighing Device Application Programming Interface Service 14032 sends the user's measured weight (W.sub.a) at 1412 To User Performance Assessment Service 14032. Weighing Device Application Programming Interface Service 14032 also sends the user's measured weight (W.sub.a) at 1413 to User Information Storage Service 14036. In response to the user's measured weight (W.sub.a) received at 1412 from Weighing Device Application Programming Interface Service 14032, the User Performance Assessment Service 14034 sends a sub-goal generation request at 1414 to sub-goal generation service 14033. The sub-goal generation request 1414 is sent, as determined by User Performance Assessment Service 14034, the first time a measured weight (W.sub.a) is received at 1412, if a user is lagging behind per equation (11), or when a user is achieving sub-goals g.sub.0, g.sub.1, . . . g.sub.n ahead of the assigned timeframes per equation (12).

(117) Upon receipt of the sub-goal generation request at 1414, Sub-Goal Generation Service 14033 generates content that includes assigned sub-goals g.sub.0, g.sub.1, . . . g.sub.n (see also, FIG. 9). Sub-Goal Generation Service 14033 generates the content that includes assigned sub-goals g.sub.0, g.sub.1, . . . g.sub.n using equations (5), (6), (10) and (13), and as per the equations and conditions shown in FIGS. 7 and 13. The generated sub-goals g.sub.0, g.sub.1, . . . g.sub.n include the timeframes between individual sub-goals g.sub.0, g.sub.1, . . . g.sub.n (see also, FIGS. 2-3). In the illustrated embodiment, the sub-goals g.sub.0, g.sub.1, . . . g.sub.n are generated by Sub-Goal Generation Service 14033 using equation (10). The sub-goals g.sub.0, g.sub.1, . . . g.sub.n are sent at 1415 to User Information Storage Service 14036 for storage, and to Weighing Device Application Programming Interface Service 14032 at 1416. The Weighing Device Application Programming Interface Service 14032 sends the sub-goals g.sub.0, g.sub.1, . . . g.sub.n at 1417 to weighing device 1402. Weighing device 1402 stores the sub-goals g.sub.0, g.sub.1, . . . g.sub.n received at 1417 within a memory storage device within weighing device 1402. The weighing device 1402 displays one or more of the sub-goals g.sub.0, g.sub.1, . . . g.sub.n in the associated timeframes on a GUI or display screen of the weighing device 1402.

(118) In the illustrated embodiment, the sub-goals g.sub.0, g.sub.1, . . . g.sub.n stored within weighing device 1402 are updated if the User Performance Assessment Service 14034 determines per conditions or equations (11) and (12).

(119) Upon receipt of a user's measured weight (W.sub.a) from weighing device 1402, user performance assessment service 14034 determines if the user has achieved or reached his or her desired weight (D.sub.w). If the user has achieved his or her desired weight (D.sub.w) as received at 1412 by User Performance Assessment Service 14034, the User Performance Assessment Service 14034 informs the sub-goal generation service 14033 at 1418 to generate maintenance mode sub-goals.

(120) Maintenance mode sub-goals are g.sub.n+X to g.sub.n, where X is small percentage of ΔW. In one embodiment, X=5 pounds. In other embodiments, X can be any suitable number.

(121) In the illustrated embodiment, the maintenance mode sub-goals are sent from the sub-goal generation service 14033 at 1420 to the Weighing Device Application Programming Interface Service 14032. The Weighing Device Application Programming Interface Service 14032 sends the maintenance mode sub-goals at 1421 to weighing device 1402.

(122) The User Performance Assessment Service 14034 assesses the measured weight (W.sub.a) received at 1412. If the measured weight (W.sub.a) is greater than g.sub.n+X, the user is taken out of maintenance mode and put into the normal weight loss mode and new sub-goals g.sub.0, g.sub.1, . . . g.sub.n are generated by Sub-Goal Generation Service 14034 based on measured weight (W.sub.a) and equations (5), (6), (10) and (13). The new sub-goals g.sub.0, g.sub.1, . . . g.sub.n are sent at 1415 to User Information Storage Service 14036 for storage, and to Weighing Device Application Programming Interface Service 14032 at 1416. The Weighing Device Application Programming Interface Service 14032 sends the sub-goals g.sub.0, g.sub.1, . . . g.sub.n at 1417 to weighing device 1402.

(123) Once the user has achieved his or her desired weight (D.sub.w), and in response to the user's measured weight (W.sub.a) being received at 1410 from weighing device 1402 by Weighing Device Application Programming Interface Service (or simply Application Programming Interface Service) 14032, Application Programming Interface Service 14032 sends the received measured weight (W.sub.a) at 1412 to User Performance Assessment Service 14034 and the User Performance Assessment Service 14034 informs the Sub-Goal Generation Service 14033 at 1416 to generate new maintenance mode sub-goals g.sub.n+X, g.sub.n, for the user. This process continues when weighing device 1402 sends the user's measured weight (W.sub.a) at 1410 to Weighing Device Application Programming Interface Service 14032 and User Performance Assessment Service 14034 continues to assess the measured weight (W.sub.a).

(124) In the illustrated embodiment, each time a user steps on weighing device 1402, User Notification Service 14035 generates quick feedback content that is based on the number of missed sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n, the number of sub-goal weights g.sub.0, g.sub.1, . . . g.sub.n that were successively achieved, BMI, height, muscle weight, fat weight, water weight and overall weight loss performance. User Notification Service 14035 sends a notification at 1422 that is based, at least in part, on the quick feedback content. The notification sent at 1422 can include, but is not limited to, text, pictures or images, charts, URL's, and videos.

(125) In the illustrated embodiment, User Information Storage Service 14036 provides user information or user data to the User Notification Service 14035 at 1423, the User Performance Assessment Service 14034 at 1424, and the Sub-Goal Generation Service 14033 at 1425.

(126) The detailed description is merely exemplary in nature and is not intended to limit the described embodiments or the application and uses of the described embodiments. As used herein, the word “exemplary” or “illustrative” means “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” or “illustrative” is not necessarily to be construed as preferred or advantageous over other implementations. All of the implementations described below are exemplary implementations provided to enable persons skilled in the art to make or use the embodiments of the disclosure and are not intended to limit the scope of the disclosure, which is defined by the claims. For purposes of description herein, the terms “upper”, “lower”, “left”, “rear”, “right”, “front”, “vertical”, “horizontal”, and derivatives thereof shall relate to the invention as oriented in FIGS. 1 through 13. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the inventive concepts defined in the appended claims. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.

(127) With the above range of variations and applications in mind, it should be understood that the present invention is not limited by the foregoing description, nor is it limited by the accompanying drawings. Instead, the present invention is limited only by the following claims and their legal equivalents.