TWM669397U - Diet and carlorie tracking system - Google Patents

Abstract

A diet and calorie tracking system includes a memory device for storing data and instructions and a processing circuitry electrically coupled to the memory device. The processing circuitry is configured to access the data and instructions stored in the memory device to execute the following step. A diet record is obtained from at least one of an information source and input data, and the step for obtaining the diet record includes the following steps. A food name of a food is obtained from an electronic invoice which is stored in a member carrier, and food data is obtained according to the food name. The food data is added into a diet list to generate the diet record. Cumulative caloric intake is calculated according to the diet record.

Description

Diet and Calorie Tracking System

This case relates to a diet and calorie tracking system, and more particularly to a system suitable for tracking and recording diet and calories.

In terms of population structure in recent years, the birth rate of newborns has been declining year by year, and the number of people over 65 years old has increased. We are facing an era of low birth rate and high aging. In some cases, combining health and exercise data can correspond to changes in consumer age trends.

However, most existing applications do not integrate the functions of exercise and diet recording at the same time, and data must be entered manually, which affects the user experience. Therefore, how to solve the above problems is an important issue in this field.

The present disclosure document provides a diet and calorie tracking system, which includes a memory and a processor. The memory is used to store data and instructions. The processor is electrically coupled to the memory, and the processor is used to access the data and instructions stored in the memory to execute the following steps. A diet record is obtained from at least one of an information source and input data, and the step of obtaining the diet record includes the following steps. The food name of the food is obtained from the electronic invoice details stored in the member vehicle, and the food information of the food is obtained based on the food name. The food information is added to the diet list to generate a diet record. The cumulative calorie intake is calculated based on the diet record.

In summary, the diet and calorie tracking system disclosed herein can obtain food information from the electronic invoice details stored in the member's device, thereby generating a corresponding diet record and tracking calorie intake, thereby enhancing the user experience.

The following is a detailed description of the embodiments with the accompanying diagrams, but the embodiments provided are not intended to limit the scope of the present disclosure, and the description of the structural operation is not intended to limit the execution order. Any device with equal efficacy produced by the re-combination of components is within the scope of the present disclosure. In addition, the diagrams are for illustrative purposes only and are not drawn according to the original size. For ease of understanding, the same or similar components in the following description will be illustrated with the same symbols. The terms used throughout the specification and the scope of the patent application, unless otherwise specified, generally have the ordinary meaning of each term used in this field, in the content of this disclosure, and in the special content. In addition, the terms "include", "including", "have", "contain", etc. used in this article are open terms, which means "including but not limited to". In addition, "and/or" used in this article includes any one or more items in the relevant enumerated items and all combinations thereof.

Please refer to FIG. 1 , which is a schematic diagram of a diet and calorie tracking system 100 according to some embodiments of the present disclosure. As shown in FIG. 1 , the diet and calorie tracking system 100 includes a user device 110 , a server 120 , a server 130 , and a database 150 .

In some embodiments, the user equipment 110 includes a wearable device 111 and a handheld device 112 of the user. In some embodiments, the wearable device 111 may be a smart bracelet, a smart watch, or other device that can calculate the user's calorie consumption through health data and/or body value monitoring. In some embodiments, the handheld device 112 is connected to the wearable device 111 via wireless communication to obtain the user's calorie consumption data. In some embodiments, calorie consumption includes exercise calories and static calories. In some embodiments, the handheld device 112 may be a mobile device, such as a smart phone, a tablet, a tablet computer, or other electronic device with calculation and display functions.

In some embodiments, the server 120 may be a server of a government unit (e.g., a cloud server of the Ministry of Finance), and includes an electronic invoice integration platform 122 stored therein. In some embodiments, the electronic invoice integration platform 122 is a software platform architecture for integrating services related to electronic invoices (e.g., application for mobile carrier barcodes and implementation of electronic invoices). In some embodiments, users may apply for mobile carrier barcodes as carriers for storing electronic invoices through the electronic invoice integration platform 122. In some embodiments, electronic invoices are electronic invoices, and merchants use the Internet or other electronic methods to open, transmit or receive unified invoices.

In some embodiments, the server 130 may be a server of a sales channel (e.g., FamilyMart server), which is used to store and run the application 140 provided by the sales channel (e.g., FamilyMart convenience store APP). In some embodiments, the database 150 stores a food ingredient list 152 associated with the aforementioned sales channel, and the database 150 is electrically coupled to the server 130, so that the server 130 can search for data in the food ingredient list 152.

In some embodiments, the server 142 of the application 140 running on the server 130 communicates with the client 141 of the application 140 running on the handheld device 112 to transfer data of the application 140 .

In some embodiments, the food ingredient list 152 at least includes food information of each product/food sold by the aforementioned sales channel (e.g., product name, nutritional composition table (e.g., calories, carbohydrates, protein, and fat) and/or production and sales history). In some embodiments, the food ingredient list 152 also includes food information of each food sold by an external sales channel. The food information associated with the external sales channel can be food information (e.g., product name, calories, carbohydrates, protein, fat, and/or origin, etc.) of each product sold by each sales channel registered on the food landing platform provided by a government unit (e.g., Taipei City Government).

In some embodiments, the application 140 includes a client 141 program running on the handheld device 112 and a server 142 program running on the server 130. In some embodiments, the client 141 of the application 140 communicates with the server 142 of the application 140 via the network 160 to transmit data. In some embodiments, the client 141 of the application 140 is used to display the content (e.g., graphical user interface, text, image, etc.) of the application 140 on the handheld device 112 and interact with the user.

The handheld device 112, the servers 120 and 130 transmit data/communicate with each other via the network 160. In some embodiments, the handheld device 112, the servers 120 and 130 each communicate wirelessly via a wireless communication (eg, at least one of a wireless wide area network and a wireless local area network) module/device.

Please refer to FIG. 2A. FIG. 2A is a schematic diagram of a handheld device 112 according to some embodiments of the present disclosure. In some embodiments, the handheld device 112 in FIG. 2A corresponds to the handheld device 112 in FIG. 1. As shown in FIG. 2A, the handheld device 112 includes a wireless communication module 222, a memory device 223, a camera 224, a touch screen 225, and a processing circuit 226.

In some embodiments, the wireless communication module 222 may be at least one of a wireless wide area network module (e.g., a 4G/5G communication module) and a wireless local area network module (e.g., a Bluetooth module, a Wi-Fi module). In some embodiments, the handheld device 112 can wirelessly communicate with the wearable device 111 through the wireless communication module 222, thereby receiving the user's health data (e.g., the user's sports data, body value data, and calorie consumption and other health information of the user) from the wearable device 111. In some embodiments, the handheld device 112 can communicate with the server 130 through the network 160 through the wireless communication module 222, thereby transmitting the data of the application 140.

In some embodiments, the client 141 of the application 140 is stored in the memory device 223 of the handheld device 112 for access to data and instructions by the processing circuit 226. In some embodiments, the memory device 223 can be implemented by dynamic memory, static memory, hard disk and/or flash memory. In some embodiments, the processing circuit 226 can be implemented by a central processing unit, a graphics processing unit, a tensor processing unit, a dedicated integrated circuit or any equivalent processing circuit.

In some embodiments, the camera 224 is used to capture images. In some embodiments, the camera 224 can be implemented by a CMOS image sensor, a photocoupled device, or other devices with light sensing capabilities.

Please refer to FIG. 2B, which is a schematic diagram of a server 130 according to some embodiments of the present disclosure. In some embodiments, the server 130 in FIG. 2B corresponds to the server 130 in FIG. 1. As shown in FIG. 2B, the handheld device 112 includes a wireless communication module 222, a memory device 223, a camera 224, a touch screen 225, and a processing circuit 226.

In some embodiments, the wireless communication module 232 may be a wireless local area network module (eg, a Bluetooth module, a Wi-Fi module). The server 130 can receive data from the handheld device 112 via the network 160 through the wireless communication module 232 and transmit the data to the handheld device 112.

In some embodiments, the server side 142 of the application 140 is stored in the memory device 233 for access and execution by the processing circuit 236. In some embodiments, the server side 142 of the application 140 includes a calorie calculation module 243, a vehicle barcode binding module 244, and a programming interface 245.

In some embodiments, the calorie calculation module 243 is used to calculate calories according to the user's diet and activities (e.g., cumulative calorie intake, calorie consumption, and calorie surplus in a cycle).

In some embodiments, the carrier barcode binding module 244 provides a function of binding the mobile phone carrier barcode held by the user with the member information, and after the binding is completed, the aforementioned sales channel will provide the member barcode as a carrier for storing electronic invoices.

In some embodiments, the programming interface 245 includes a graphical user interface of the application 140 , which includes a plurality of buttons and display contents for user operation.

In some embodiments, the user data 250 is stored in the memory device 233 for access by the processing circuit 236. In some embodiments, the user data 250 includes member data 251, health data 252, diet record 253 and diet plan 254.

In some embodiments, the member information 251 includes the user's member account, member password, and member barcode.

In some embodiments, health data 252 includes the user's basic information, calorie intake goal, activity status, and calorie consumption.

In some embodiments, the diet record 253 includes a user's diet list, cumulative calorie intake, and calorie balance in a period.

In some embodiments, the diet plan 254 includes food recommendations for the next time period. In some embodiments, the diet plan 254 is generated based on the calorie surplus in the diet record 253.

In some embodiments, the memory device 233 may be implemented by a dynamic memory, a static memory, a hard disk and/or a flash memory. In some embodiments, the processing circuit 236 may be implemented by a central processing unit, a graphics processing unit, a tensor processing unit, a dedicated integrated circuit or any equivalent processing circuit.

Please refer to FIG. 1 and FIG. 3. FIG. 3 is a schematic diagram of a member vehicle 310 according to some embodiments of the present disclosure. In some embodiments, the application 140 is an application of a sales channel (e.g., an application of FamilyMart). After the user downloads the application and applies for membership, the user can use the service of the application 140. In some embodiments, after the user binds the barcode of the mobile vehicle held by the user to the member information, the electronic invoice can be stored in the member vehicle 310. In some embodiments, the member vehicle 310 is provided/generated by the aforementioned sales channel. In some embodiments, the member vehicle 310 corresponds to a member account, which includes at least one of a member serial number 312 (e.g., a serial number consisting of numbers and/or symbols) and a member barcode 314. In some embodiments, the member vehicle 310 can be displayed by the handheld device 112. In some embodiments, when the user presents the member vehicle 310, the clerk can deposit the electronic receipt into the member vehicle 310 by entering the member serial number 312 or scanning the member barcode 314.

In some embodiments, the elements of the homepage of the application 140 include a member barcode button, and when the user clicks the member barcode button, the page shown in Figure 3 is entered. In this way, the clerk of the aforementioned sales channel can scan the member vehicle 310 provided by the user to open and upload an electronic invoice.

In some embodiments, the application 140 is synchronized with the electronic invoice integration platform 122 to obtain the detailed information of the electronic invoice stored in the barcode of a user's membership vehicle 310 and/or mobile vehicle. In some embodiments, the user can view the consumption record on the page of the account book of the application 140. In some embodiments, the consumption record includes the detailed information of the electronic invoice stored in the barcode of the user's membership vehicle 310 and/or mobile vehicle.

Please refer to FIG. 1 and FIG. 4A. FIG. 4A is a schematic diagram of a diet and calorie tracking method 400 according to some embodiments of the present disclosure. As shown in FIG. 4A, the diet and calorie tracking method 400 includes steps 410-460. In some embodiments, steps 410-450 can be executed by the processing circuit 236 in the server 130 of FIG. 2B accessing instructions and data in the memory device 233.

In step 410, a diet record is obtained from at least one of an information source and input data. In some embodiments, the electronic invoice details automatically import the food name and its food information. In some embodiments, the information source can be, for example, the electronic invoice integration platform 122. In some embodiments, based on the mobile phone carrier barcode that has been bound to the member information, the application 140 can record the electronic invoice stored in the member carrier and/or the mobile phone carrier barcode, and automatically import the food name and its food information into the diet record based on the electronic invoice details. In some embodiments, the input data can be data related to food ingredients (e.g., food name, portion size, and calories) generated by user text input or images taken by the user.

In step 420, a cumulative calorie intake is calculated based on the diet record. In some embodiments, the cumulative calorie intake may be the sum of the calorie amounts of the diet items of the user over a period of time, and the period of time may be, for example, from 0:00 a.m. on a day to the current time point, from the first day of a week to the current time point, or from the first day of a month to the current time point.

In step 430, a calorie consumption estimated by a wearable device is obtained. In some embodiments, the wearable device 111 has a calorie consumption monitoring function. In some embodiments, the wearable device 111 has a function of sensing the user's sports data, health data and/or body value data and estimating the user's calorie consumption based on the aforementioned data. In some embodiments, the handheld device 112 maintains a communication connection with the wearable device 111 via Bluetooth to obtain the user's calorie consumption in real time.

In step 440, a calorie intake target is obtained. In some embodiments, the application 140 provides a questionnaire page for the user to input basic health information (e.g., weight, height, age, gender, etc.) and lifestyle, so as to calculate the BMI value based on the health information, and calculate the calorie intake target based on the BMI value and the user's lifestyle.

In step 450, a calorie surplus is calculated based on the calorie intake target, the calorie consumption, and the cumulative calorie intake. In some embodiments, the application 140 is executed to subtract the cumulative calorie intake from the sum of the calorie intake target and the calorie consumption to obtain the calorie surplus.

In step 460, the calorie balance is displayed by a user device. In some embodiments, the user device 110 may be a handheld device 112. In some embodiments, the ratio of the calorie balance to the calorie intake goal may be presented by a donut chart.

Please refer to Figures 4A to 4D. Figures 4B to 4D are schematic diagrams of steps 410-1, 410-2, and 410-3 included in step 410 of a diet and calorie tracking method 400 according to some embodiments of the present disclosure. In some embodiments, step 410-1 includes steps 11-14, step 410-2 includes steps 21-25, and step 410-3 includes steps 31-34. In some embodiments, steps 11-14 in step 410-1, steps 21-25 in step 410-2, and steps 31-34 in step 410-3 can be executed by the processing circuit 236 in the server 130 of FIG. 2B accessing instructions and data in the memory device 233.

In some embodiments, step 410-1 corresponds to the operation of automatically importing food names and corresponding food information into the diet record based on the electronic invoice details. For a better understanding of the operation of step 410-1, please refer to FIG. 1, FIG. 4B, and FIG. 5 to FIG. 6. FIG. 5 is a schematic diagram of electronic invoice details 500 according to some embodiments of the present disclosure. FIG. 6 is a schematic diagram of a diet record 610 according to some embodiments of the present disclosure.

In step 11, the electronic invoice details stored in the member's vehicle are obtained from the information source. In some embodiments, the information source may be, for example, the electronic invoice integration platform 122 shown in FIG. 1. In some embodiments, when the user has bound the mobile vehicle barcode to the member information, the application 140 can obtain and present the electronic invoice details 500 stored in the member's vehicle, as shown in FIG. 5. In some embodiments, the application 140 can also obtain the electronic invoice details stored in the mobile vehicle barcode, but the present disclosure is not limited thereto.

In step 12, the food name and an invoice date are obtained from the electronic invoice details. In some embodiments, the electronic invoice details 500 include a store name 502, an invoice date, and product transaction information 506 and 508, as shown in FIG. 5. In some embodiments, the store name 502 may be a store name of a sales channel (e.g., FamilyMart sales channel) providing the application 140 or a store name of an external sales channel, but the present disclosure is not limited thereto. In some embodiments, the transaction information 506 and 508 each include the food name, quantity, and amount of the food. In some embodiments, the food name may be, for example, the name of a branded food product in transaction information 506 (e.g., OO toast, where "OO" is the brand name) or the name of a common food sold by the sales channel in transaction information 508 (e.g., medium iced latte).

In step 13, a food ingredient list associated with a sales channel is used to map the food name of the food to the food data. In some embodiments, the food ingredient list 152 includes food data (e.g., product name, nutritional composition table (e.g., calories, carbohydrates, protein and fat) and/or production and sales history) of each food sold by the sales channel (e.g., FamilyMart sales channel) providing the application 140. For example, the food name (e.g., 00 toast) in the transaction information 506 is mapped to food data (e.g., 350 kcal/piece, 42 grams of carbohydrates/piece, GI value level, sodium and fat content level) using the food ingredient list 152 to obtain the food data of 00 toast, thereby generating the food entry 621 of 00 toast, as shown in FIG. 6 . For another example, the food name (e.g., medium iced latte) in the transaction information 508 is mapped to food data (e.g., 176 kcal/cup, GI value level, sodium and fat content level) using the food ingredient list 152 to obtain the food data of the medium iced latte sold by the sales channel, thereby generating the food entry 622 for the medium iced latte, as shown in FIG. 6 .

In some embodiments, the food ingredient list 152 further includes food information (e.g., product name, calories, carbohydrates, protein, and fat information) of each product sold in each sales channel registered on the food landing platform provided by a government unit (e.g., Taipei City Government). In this case, the user can also obtain the food information of the food in the external sales channel by searching the food ingredient list 152 for the food in the electronic invoice details generated by the consumption in an external sales channel, thereby generating a food item for the food, and automatically importing the food item into the diet list 620.

In step 14, the food data is added to the diet record according to the invoice date. In some embodiments, according to the invoice date in the electronic invoice details 500 of FIG. 5, the food item 621 containing the food data is automatically added/imported into the diet list 620 of the day in the diet record 610, as shown in FIG. 6.

In some embodiments, the portion size and/or number of portions in the food items 621 and 622 in the diet list 620 can be adjusted, and when the portion size and/or number of portions are adjusted, the food information (e.g., calorie content, carbohydrate content) will also be adjusted accordingly. In some embodiments, the user can remove some of the food items 621 and 622 in the diet list 620 according to his actual diet.

Therefore, based on the food data recorded in the diet list 620 of the day in the diet record 610 (for example, the nutritional components of each food), the cumulative calorie intake 632 and the intake of related components 634 (for example, carbohydrates, proteins and fats) before the current time point of the day can be calculated.

In the embodiment of FIG. 6 , the page of the health assistant 600 of the application 140 includes a home button 601, an article button 602, a diary button 603, an exercise button 604, a social button 605, and a task button 606, and clicking the above buttons will enter the home page, article, diary, exercise, social network, and task pages respectively.

In some embodiments, step 410-2 corresponds to the operation of adding a food item to the diet record based on the food category identified in the image. For a better understanding of the operation of step 410-2, please refer to FIG. 1, FIG. 2A to FIG. 2B, FIG. 4C, and FIG. 7 to FIG. 8. FIG. 7 is a schematic diagram of the content displayed after the page of FIG. 6 is moved downward according to some embodiments of the present disclosure. FIG. 8 is a schematic diagram of a method for adding a food item according to an embodiment of the present disclosure.

In step 21, a food photo and a serving size are obtained. In some embodiments, when the user clicks the camera add button 708, a photo mode is entered, allowing the user to take a food photo using the camera 224 of the handheld device 112. In some embodiments, after the food photo is taken, the user can use the touch screen 225 of the handheld device 112 to input/modify the serving size of the food.

In step 22, a food category in the food photo is identified by an object recognition network. In some embodiments, the application 140 has a neural network for object detection/recognition, or other neural networks capable of identifying food categories. In some embodiments, the application 140 identifies the food category (e.g., turnip soup) in the food photo by object detection, as shown in item 802 of FIG. 8. In some embodiments, the user can use the touch screen 225 of the handheld device 112 to input/modify the identified food category.

In step 23, a calorie amount is estimated according to the food category and the portion. In some embodiments, the calorie amount of this food can be estimated according to the food category (e.g., carrot soup) and the portion (e.g., a bowl of soup), as shown in Figure 8.

In step 24, a food item is added based on the food category, the portion size, and the calorie content. In some embodiments, when the user clicks the next button, the application 140 can create a food item based on the identified food category and the estimated food data (e.g., the calorie content of turnip soup is 119 kcal).

In step 25, the food data and the food item are added to the diet list to generate the diet record. In some embodiments, the food item including the recognized food name and its food data (e.g., the calorie content of turnip soup is 119 kcal) can be added to the diet list 620 to generate/update the diet record 610.

In some embodiments, the food list 620 in the food record 610 of the application 140 includes food items 621-623. In some embodiments, the food record 610 further includes a text add button 706 for adding an item 704 and/or a photo add button 708. In some embodiments, clicking the photo add button 708 will enter the operation page of step 410-2, and clicking the text add button 706 will enter the operation page of step 410-3.

In some embodiments, step 410-3 corresponds to the operation of adding a food item to the diet record based on the text input by the user. For a better understanding of the operation of step 410-2, please refer to FIG. 1, FIG. 2A to FIG. 2B, FIG. 4D, and FIG. 9A to FIG. 9B are schematic diagrams of methods for adding a food item according to some embodiments of the present disclosure.

In step 31, at least one text input is obtained. As shown in FIG. 9A and FIG. 9B, the creation page of the food entry includes text/numeric input boxes for channel/brand name, food name, number of servings, serving size, and nutritional ingredients (e.g., calories, total fat, trans fat, etc.). In some embodiments, when the user uses the touch screen 225 of the handheld device 112 to input, the application 140 can obtain at least one text input related to the food.

In step 32, a calorie amount is generated based on the at least one text input. As shown in FIG. 9A, if the at least one text input includes information about a branded food product, the application 140 can obtain the calorie amount of the food from the branded food product information. As shown in FIG. 9B, if the at least one text input includes a common food name and portion size, the application 140 estimates the calorie amount of the food based on the common food name and portion size.

In step 33, a food entry is added based on the at least one text input and the calorie amount. As shown in FIG. 9A and FIG. 9B, when the user clicks the confirmation button, the application 140 can create a food entry based on the food information input by the user. In some embodiments, the user can also use the camera 224 to capture an image 904 of a nutrition information table of a branded food product or an image 905 of a common food through the camera button 902, and the handheld device 112 returns it to the application 140 as a record of the food ingredient data.

In step 34, the food data and the food item are added to the diet list to generate the diet record. In some embodiments, the food item including the food information input by the user can be added to the diet list 620 to generate/update the diet record 610.

Thus, through steps 410-1 to 410-3, the user can obtain a diet record that can be managed in a timeline. Thus, the application 140 can calculate the total calorie amount of the diet entry of the user within a period of time, and the period of time can be, for example, from 0:00 a.m. to the current time point, from the first day of the week to the current time point, or from the first day of the month to the current time point.

Please refer to Figures 10A to 10F. Figures 10A to 10F are schematic diagrams of methods for obtaining calorie intake targets according to some embodiments of the present disclosure. In some embodiments, the application 140 provides a questionnaire page such as Figures 10A to 10F for users to enter basic information, daily activity level, goals, and eating habits. In some embodiments, the basic information includes gender, birthday, height, and weight. In some embodiments, the daily activity level includes options for sedentary and light, moderate, high, and very high activities. In some embodiments, the goals include long-term goals (e.g., weight loss, weight maintenance, or weight gain), weekly goals (e.g., losing N kilograms per week), and expected weight. In some embodiments, dietary habits include vegetarian/vegetarian diet and dietary preferences/taboos.

In some embodiments, after the user completes the data setting, the application 140 will calculate the body mass index according to the basic data of the user. In some embodiments, the application 140 generates a calorie intake target (e.g., a daily calorie intake target) within a period according to at least one of the basic data, body mass index, daily activity level, goal, and eating habits. As shown in FIG. 10F, the daily calorie intake target is 1850 kcal.

Please refer to FIG. 1, FIG. 2A to FIG. 2B, and FIG. 11A to FIG. 11C. FIG. 11A to FIG. 11C are schematic diagrams of calorie consumption according to some embodiments of the present disclosure. In some embodiments, the application 140 can obtain health data provided by the wearable device 111. In some embodiments, the health data provided by the wearable device 111 includes exercise records and calorie consumption estimated based on the exercise records.

Please refer to FIG. 1 and FIG. 12. FIG. 12 is a schematic diagram of a calorie surplus in a cycle according to some embodiments of the present disclosure. In some embodiments, the application 140 calculates a calorie surplus based on a calorie intake target, calorie consumption provided by the wearable device 111, and cumulative calorie intake. In some embodiments, the handheld device 112 presents the calorie consumption 1210 and the calorie surplus 1220 calculated by the application 140 before the current time point in a cycle 1205 (e.g., daily, weekly, or monthly). In some embodiments, the value obtained by subtracting the cumulative calorie intake from the sum of the calorie intake target and the calorie consumption 1210 is the calorie surplus 1220.

Please refer to FIG. 13. FIG. 13 is a schematic diagram of a diet recommendation system 1300 according to some embodiments of the present disclosure. In some embodiments, the diet recommendation system 1300 includes the user device 110, the server 120, the server 130, and the database 150 in the diet and calorie tracking system 100. Compared with the diet and calorie tracking system 100 of FIG. 1, the diet recommendation system 1300 further includes a server 1370. In some embodiments, the server 1370 stores and runs a health data platform 1372. In some embodiments, the server 1370 communicates with the server 130 via the network 160 to obtain the user's basic information and health information. In some embodiments, the health data platform 1372 can assess the user's health status (e.g., one of overweight, moderate, and underweight) based on the user's basic information and at least one of the health data.

Please refer to FIG. 14. FIG. 14 is a schematic diagram of a diet recommendation method 1400 according to some embodiments of the present disclosure. As shown in FIG. 14, the diet recommendation method 1400 includes steps 1410-1460. In some embodiments, steps 1410-1450 correspond to steps 410-450 of the diet and calorie tracking method 400, which are not described in detail here. In some embodiments, step 1460 can be executed by the processing circuit 236 in FIG. 2B accessing instructions and data in the memory device 233.

In step 1460, at least one food is selected from a food ingredient list associated with a sales channel to form a diet plan based on the calorie surplus. In some embodiments, the at least one food is selected from one of the products sold by the sales channel. In some embodiments, a total calorie amount of the diet plan is not greater than the calorie surplus.

In some embodiments, the remaining calorie amount is an upper limit of the amount of calories recommended to the user to consume between a current time point and a reset time point. In some embodiments, the diet plan includes a food plan for at least one meal between the current time point and the reset time point. In some embodiments, the diet plan includes at least one meal in a day. In some embodiments, the diet plan includes a food plan for at least one of breakfast, lunch, dinner, and a snack. In some examples, the information of at least one food of the sales channel presented by the food plan includes food data (e.g., calorie amount, protein, carbohydrate, and fat content) of the at least one food.

In some embodiments, the application 140 selects at least one food from the food component list 152 associated with the sales channel to form a diet plan according to the user's health condition (e.g., one of overweight, moderate, and underweight) provided by the health data platform 1372. For example, if the user's health condition is obesity, the application 140 selects low-fat and high-fiber food from the food component list 152 as the at least one food. For another example, if the user's health condition is underweight, the application 140 selects high-protein food from the food component list 140 as the at least one food.

Please refer to FIG. 15, which is a schematic diagram of a dashboard page of an application 140 according to some embodiments of the present disclosure. As shown in FIG. 15, the application 140 will present the recommended foods 1504 and 1506 in the aforementioned diet plan. In some examples, if the current time point is close to the dinner time, the recommended foods 1504 and 1506 in the aforementioned diet plan will meet the needs of a full meal, and the calories of the recommended foods 1504 and 1506 are not greater than the user's calorie surplus. In some embodiments, the application 140 will recommend health products 1508 based on the user's basic information, health status, and browsing information. In some embodiments, if the user's calorie balance is non-negative every day of the week, the application 140 will present a periodic task reward 1502.

Please refer to FIG. 16A and FIG. 16B. FIG. 16A and FIG. 16B are schematic diagrams of a task page of an application 140 according to some embodiments of the present disclosure. As shown in FIG. 16A, the application 140 presents general task information 1602 (e.g., unboxing tasks, tasting tasks). As shown in FIG. 16B, the application 140 presents exclusive task information 1604 (e.g., completing a one-week diet plan) based on the user's basic information and health status.

Please refer to Figures 17A to 17B. Figures 17A to 17B are schematic diagrams of question-and-answer solutions provided by application 140 according to some embodiments of the present disclosure. As shown in Figure 17A, the social page of application 140 includes a nutritionist's column and an online consultation button. In some embodiments, the user can click the online consultation button to open a dialog box to consult with the nutritionist, and the dialog box can be reopened in the message button 1710 later. In some embodiments, the message button 1710 includes multiple dialog boxes, including an AI dialog box, and the user clicks the AI dialog box to ask questions with the health AI assistant. For example, users can ask the health AI assistant for nutrition information, product information about sales channels, health information, and other health or product-related information.

Please refer to FIG. 18. FIG. 18 is a schematic diagram of an article page of an application 140 according to some embodiments of the present disclosure. In some embodiments, the application 140 presents different types of articles such as diet, exercise, health, spirituality, maturity, reading time, courses, columns, etc. In some embodiments, the application 140 also collects the pages browsed by the user and records them as user data.

In summary, the diet and calorie tracking system 100 disclosed herein can automatically add food items to the diet record based on the food items in the electronic invoice details, and calculate the user's cumulative calorie intake according to the diet record. The diet recommendation system 1300 disclosed herein can calculate the calorie surplus according to the user's cumulative calorie intake, calorie intake target, and calorie consumption, and select at least one food from the food ingredient list associated with the sales channel according to the calorie surplus to form a diet plan. In this way, the diet and calorie tracking system 100 and the diet recommendation system 1300 disclosed herein can enhance the user experience.

Although the present disclosure has been disclosed in the above implementation form, it is not intended to limit the present disclosure. Any person with ordinary knowledge in the art can make various changes and modifications without departing from the spirit and scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be defined by the scope of the attached patent application.

In order to make the above and other purposes, features, advantages and embodiments of the present disclosure more clearly understandable, the attached symbols are explained as follows: 100: Diet and calorie tracking system 110: User equipment 111: Wearable device 112: Handheld device 120: Server 122: Electronic invoice integration platform 130: Server 140: Application 141: Client 142: Server side 150: Database 152: Food ingredient list 160: Network 222,232: Wireless communication module 223,233:Memory device 224:Camera 225:Touch screen 226,236:Processing circuit 243:Calorie calculation module 244:Carrier barcode binding module 245:Programming interface 250:User information 251:Member information 252:Health information 253:Diet record 254:Diet plan 310:Membership vehicle 312:Membership serial number 314:Membership barcode 400:Diet and calorie tracking method 410~460:Steps 410-1, 410-2, 410-3: Steps 11~14,21~25,31~34: Steps 500: Electronic invoice details 502: Store name 506,508: Transaction information 600: Health assistant 601: Home button 602: Article button 603: Diary button 604: Exercise button 605: Social button 606: Task button 610: Diet record 620: Diet list 621~623: Food items 632: Cumulative calorie intake 634 Related ingredient intake 704: To be added 706: Text add button 708: Photo add button 802: Item 902: Photo button 904,905: Image 1205: Cycle 1210: Calorie consumption 1220: Calorie balance 1300: Diet recommendation system 1370: Server 1372: Health data platform 1400: Diet recommendation method 1410~1460: Steps 1502: Cycle task rewards 1504,1506: Recommended foods 1508: Health products 1602: General task information 1604: Exclusive task information 1710: Message button

In order to make the above and other purposes, features, advantages and embodiments of the present disclosure more clearly understandable, the attached drawings are described as follows: FIG. 1 is a schematic diagram of a diet and calorie tracking system according to some embodiments of the present disclosure. FIG. 2A is a schematic diagram of a handheld device according to some embodiments of the present disclosure. FIG. 2B is a schematic diagram of a server according to some embodiments of the present disclosure. FIG. 3 is a schematic diagram of a member vehicle according to some embodiments of the present disclosure. FIG. 4A is a schematic diagram of a diet and calorie tracking method according to some embodiments of the present disclosure. FIG. 4B to FIG. 4D are schematic diagrams of steps 410-1, 410-2 and 410-3 included in step 410 of the diet and calorie tracking method according to some embodiments of the present disclosure. FIG. 5 is a schematic diagram of electronic invoice details according to some embodiments of the present disclosure. Figure 6 is a schematic diagram of a diet record according to some embodiments of the present disclosure. Figure 7 is a schematic diagram of the content displayed after the page of Figure 6 is moved downward according to some embodiments of the present disclosure. Figure 8 is a schematic diagram of a method for adding a new food item according to an embodiment of the present disclosure. Figures 9A and 9B are schematic diagrams of a method for adding a new food item according to some embodiments of the present disclosure. Figures 10A to 10F are schematic diagrams of a method for obtaining a calorie intake target according to some embodiments of the present disclosure. Figures 11A to 11C are schematic diagrams of calorie consumption according to some embodiments of the present disclosure. Figure 12 is a schematic diagram of the remaining calories within a cycle according to some embodiments of the present disclosure. Figure 13 is a schematic diagram of a diet recommendation system according to some embodiments of the present disclosure. FIG. 14 is a schematic diagram of a diet recommendation method according to some embodiments of the present disclosure. FIG. 15 is a schematic diagram of a dashboard page of an application according to some embodiments of the present disclosure. FIG. 16A to FIG. 16B are schematic diagrams of a task page of an application according to some embodiments of the present disclosure. FIG. 17A to FIG. 17B are schematic diagrams of a question-and-answer solution provided by an application according to some embodiments of the present disclosure. FIG. 18 is a schematic diagram of an article page of an application according to some embodiments of the present disclosure.

100:Diet and calorie tracking system

110: User equipment

111: Wearable devices

112: Handheld device

120: Server

122: Electronic invoice integration platform

130: Server

140: Applications

141: Client

142: Server side

150: Database

152: List of food ingredients

160: Internet

Claims (9)

A diet and calorie tracking system, comprising: A memory device for storing data and a plurality of instructions; and A processing circuit electrically coupled to the memory device, and the processing circuit is used to access the data and the instructions stored in the memory device to execute: Obtaining a diet record from at least one of an information source and input data, and the steps of obtaining the diet record include: Obtaining a food name of a food from an electronic invoice detail stored in a member's vehicle, and obtaining food information of the food according to the food name; Adding the food information to a diet list to generate the diet record; and Based on the diet record, the cumulative calorie intake is calculated. A diet and calorie tracking system as described in claim 1, wherein the processing circuit is further used to perform: Obtaining the electronic invoice details stored in the member's vehicle from the information source; Obtaining the food name and an invoice date from the electronic invoice details; Mapping the food name of the food to the food data using a food ingredient list associated with a sales channel; and Adding the food data to the diet record based on the invoice date. A diet and calorie tracking system as described in claim 2, wherein the food ingredient list associated with the sales channel includes information on the name, calories, carbohydrates, protein, and fat of each of the multiple products sold by the sales channel. A diet and calorie tracking system as described in claim 2, wherein the member vehicle is generated by the sales channel and wherein the member vehicle is a member account. A diet and calorie tracking system as described in claim 1, wherein the food name corresponds to the name of a brand food product or the name of a common food. A diet and calorie tracking system as described in claim 1, wherein the processing circuit is further used to perform: Obtain a food photo and a serving size; Identify a food category in the food photo through an object recognition network; Estimate a calorie amount based on the food category and the serving size; Add a food item based on the food category, the serving size, and the calorie amount; and Add the food data and the food item to the diet list to generate the diet record. A diet and calorie tracking system as described in claim 1, wherein the processing circuit is further used to perform: Obtain at least one text input; Generate a calorie amount based on the at least one text input; and Add a food item based on the at least one text input and the calorie amount; and Add the food data and the food item to the diet list to generate the diet record. A diet and calorie tracking system as described in claim 7, wherein the processing circuit is further used to perform: If the at least one text input includes information about a brand of food product, the step of obtaining the calorie amount further includes: Obtaining the calorie amount from the information about the brand of food product; and If the at least one text input includes a common food name and serving size, the step of obtaining the calorie amount further includes: Estimating the calorie amount based on the common food name and serving size. A diet and calorie tracking system as described in claim 1, wherein the processing circuit is further used to perform: Obtaining a calorie consumption estimated by a wearable device; Obtaining a calorie intake target; and Calculating a calorie surplus based on the calorie intake target, the calorie consumption, and the cumulative calorie intake.