Intelligent control method and system for nasal irrigation

Abstract

The present application relates to the technical field of medical care equipment, and particularly relates to an intelligent control method and system for nasal cavity flushing. The method is applied to a nasal cavity flushing device comprising a main control, an electric quantity monitoring, a storage, a reminding and a charging interface, the remaining electric quantity is monitored in real time, and the next use time point is predicted in combination with the stored user historical use habit data; the standard electric quantity required for completing one flushing is calculated based on a preset flushing flow consumption model, and the current electric quantity, the standard electric quantity, the predicted use time point and the charging rate parameter are comprehensively considered to dynamically judge whether a charging reminding instruction needs to be generated, when it is judged that the charging reminding instruction needs to be generated, the charging prompt is sent to the user through the reminding module, it is ensured that the device has enough electric quantity to support one complete flushing flow before the next predicted use, so that the power failure in the middle of use is avoided, and the user experience and the nursing effect are improved.

Description

Technical Field

[0001] This invention relates to the field of medical care equipment technology, and in particular to an intelligent control method and system for nasal irrigation. Background Technology

[0002] Existing electric nasal irrigation devices generally have basic battery monitoring functions and typically provide low battery warnings via lights or sounds when the battery level falls below a certain threshold. However, this warning mechanism has significant limitations: it only reflects the device's immediate battery status and cannot be correlated with the user's individual usage habits or future needs. If a user sees a low battery warning but fails to charge it immediately and then uses the device at an unplanned time later, the irrigation process is still highly likely to be interrupted due to the battery running out. This not only disrupts the user experience but, for users who rely on nasal irrigation for post-operative nasal care or chronic disease treatment, may also lead to incomplete irrigation and increased risk of infection.

[0003] More importantly, existing technology lacks the ability to determine the dynamic relationship between the electricity required to complete a full wash and the user's next usage time. Its reminders are static and passive; it cannot proactively calculate whether there is sufficient time to charge between the current moment and the expected usage time, nor can it personalize risk window predictions based on the user's historical usage patterns.

[0004] Therefore, the power management strategies of existing devices are crude and unreliable, and cannot fundamentally guarantee that users can always get a complete and uninterrupted washing experience when needed; in response to this common technical deficiency, there is an urgent need for a more intelligent power prediction and control method. Summary of the Invention

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] A smart control method for nasal irrigation, applied to a nasal irrigation device including a main control module, a power monitoring module, a storage module, a reminder module, and a charging interface, characterized in that the method includes the following steps:

[0007] The power monitoring module monitors the current remaining power of the nasal irrigation device in real time.

[0008] Read user historical usage data from the storage module, wherein the user historical usage data includes at least the user's next expected usage time.

[0009] Based on a preset power consumption model for the rinsing process, the standard power required to complete one full standard rinsing process is calculated.

[0010] Based on the current remaining battery level, the standard battery level, and the next estimated usage time, combined with preset charging rate parameters, it is determined whether a charging reminder instruction needs to be generated.

[0011] When the determination result indicates that a charging reminder instruction needs to be generated, a charging reminder is sent to the user through the reminder module. The charging reminder instructs the user to charge the device before the next expected usage time to ensure that the battery power of the nasal irrigation device is sufficient to support a complete standard irrigation process at the next expected usage time.

[0012] Furthermore, the user's historical usage habit data is generated and updated through the following steps:

[0013] After each nasal irrigation device completes an irrigation process, it records the end timestamp of the current use and stores the end timestamp as a historical usage record in the storage module.

[0014] Periodically retrieve all historical usage records within a preset time window from the storage module;

[0015] Statistical analysis is performed on the timestamps contained in all historical usage records within the preset time window to calculate the user's habitual usage time pattern;

[0016] Based on the user's habitual usage time pattern and the current time, the system predicts and generates the user's next expected usage time, and stores this next expected usage time as part of the user's historical usage habit data in the storage module.

[0017] Furthermore, the criteria for determining whether a rinsing process is complete are as follows:

[0018] Monitor whether the main control module of the nasal irrigation device receives an irrigation start command initiated by the user through the operation interface;

[0019] Upon detecting the flushing start command, the flushing process is initiated and a timer is started;

[0020] During the operation of the rinsing process after it is started, it continuously monitors whether a rinsing stop command initiated by the user through the operation interface is received, or whether the rinsing process has reached the preset default rinsing time threshold.

[0021] If the flushing stop command is detected or the flushing process reaches the default flushing duration threshold, it is determined that a flushing process has ended, and the timestamp of that moment is recorded as the end timestamp of this use.

[0022] The end timestamp of the record is compared with the most recently stored historical usage record in the storage module. If the time interval between the two records is greater than the preset minimum usage interval threshold, the end timestamp of the current record is stored as a new historical usage record in the storage module; otherwise, it is considered an invalid record and is not stored.

[0023] The statistical analysis specifically includes:

[0024] The end timestamps contained in all historical usage records within the preset time window are categorized according to date and clock time.

[0025] For the same time period each day, the frequency of occurrence of the historical usage records is counted;

[0026] Based on the frequency and the time distribution pattern of the historical usage records, identify one or more high-frequency usage periods for the user each day;

[0027] One or more high-frequency usage periods and their corresponding frequency weights are collectively defined as the user's habitual usage time pattern.

[0028] Furthermore, the calculation of the standard power consumption required to complete one full standard rinsing process based on the preset power consumption model specifically includes:

[0029] The power consumption parameters per unit time of the nasal irrigation device in the standard working mode are obtained from the storage module. The standard working mode refers to the working state of a preset combination of fixed irrigation pressure and fixed irrigation flow rate.

[0030] Obtain the preset standard rinsing duration parameter corresponding to the standard rinsing process from the storage module;

[0031] The standard power consumption is calculated by multiplication based on the power consumption parameter per unit time and the preset standard rinsing duration parameter.

[0032] The method also includes the step of calculating the required power for different operating modes:

[0033] The storage module retrieves multiple non-standard operating modes supported by the nasal irrigation device, each non-standard operating mode corresponding to a different combination of irrigation pressure and irrigation flow rate.

[0034] For each of the aforementioned non-standard working modes, there are preset parameters for power consumption per unit time and recommended rinsing time.

[0035] When the main control module recognizes that the user has selected a specific non-standard working mode, it calculates the specific mode power required to complete a full rinsing process under the non-standard working mode by multiplication based on the power consumption parameters per unit time and the recommended rinsing time parameters corresponding to the mode.

[0036] Furthermore, the logic for determining whether a charging reminder instruction needs to be generated specifically includes:

[0037] Obtain the current remaining battery power and the required battery power corresponding to the user's currently selected working mode. If the user does not select a specific mode, the standard battery power is used as the required battery power.

[0038] Calculate the difference between the current remaining power and the required power, and mark this difference as the power margin;

[0039] Determine whether the battery margin is less than or equal to zero; if so, directly generate the charging reminder command.

[0040] If the power margin is greater than zero, then the time difference from the current time point to the next expected usage time point is further calculated;

[0041] Based on the charging rate parameter and the power margin, estimate the theoretical charging time required to charge the nasal irrigation device from the current remaining power to meet the required power.

[0042] The time difference is compared with the theoretically required charging time. If the time difference is less than or equal to the theoretically required charging time, a charging reminder instruction is generated; otherwise, no charging reminder instruction is generated.

[0043] Furthermore, the specific steps for estimating the theoretically required charging time are as follows:

[0044] Obtain the charging rate parameter pre-stored in the storage module, wherein the charging rate parameter represents the amount of electricity that the charging interface can charge the nasal irrigation device per unit time.

[0045] Calculate the difference between the required power and the current remaining power to obtain the amount of power that needs to be replenished;

[0046] Divide the amount of electricity that needs to be replenished by the charging rate parameter to obtain the theoretically required charging time.

[0047] Furthermore, the step of predicting and generating the user's next expected usage time based on the user's habitual usage time pattern and the current time specifically includes:

[0048] Obtain the current time, including the current clock time and the current date;

[0049] From the user's habitual usage time patterns, find a target date that is closest to the current date and has a high-frequency usage period after the current date;

[0050] The start time of the high-frequency usage period or the specific clock time with the highest frequency statistical value within that period in the target date is determined as the next expected usage time point;

[0051] If no matching target date is found after the current date, an average usage interval is calculated based on the statistical patterns of all high-frequency usage periods in the user's habitual usage time pattern. The current time is then added to the average usage interval to obtain the next expected usage time, which is then used as the default next expected usage time.

[0052] Furthermore, the step of sending a charging reminder to the user through the reminder module specifically includes:

[0053] After the main control module generates the charging reminder command, it first determines whether the nasal irrigation device is currently in use;

[0054] If the nasal irrigation device is not currently in use, the reminder module is immediately activated to send a charging reminder to the user through at least one of visual, auditory, or tactile vibration signals.

[0055] The visual signals include, but are not limited to, illuminating indicator lights of a specific color, displaying preset prompt text or icons on the device's display screen;

[0056] After issuing the charging reminder, a reminder timing cycle is initiated;

[0057] If the charging interface is detected to be connected to an external power source during the reminder timing period, the charging reminder will be stopped immediately and a valid response event will be recorded.

[0058] If no charging connection is detected after the reminder timing period ends, the reminder will be temporarily stopped and the judgment process will be repeated after a preset silent interval. If the conditions for generating a charging reminder command are met again, a new reminder timing period will be initiated.

[0059] If the nasal irrigation device is currently in use, the main control module temporarily stores the charging reminder instruction and continuously monitors the end of the current usage process;

[0060] Once the current usage process is detected to have ended, immediately check the temporary storage status of the charging reminder instruction;

[0061] If the charging reminder command is valid, the reminder module will be activated to issue the charging reminder after a preset delay after the end of the usage process, so as to avoid interfering with the user's current usage experience.

[0062] Furthermore, the method also includes a step of dynamically calibrating the next expected usage time point:

[0063] The storage module records the time when each charging reminder command is generated and the time when the user actually connects to charge.

[0064] Once a user is detected to actually connect to charging, the time interval between generating a charging reminder command and the actual charging connection is calculated and marked as the actual response delay.

[0065] The actual response delay is compared with a preset expected response delay threshold;

[0066] If the actual response delay is greater than the expected response delay threshold in multiple consecutive instances, it is determined that the preset reminder advance amount is insufficient. The time offset parameter used to calculate the next expected usage time is automatically adjusted so that the subsequent predicted next expected usage time is earlier than the prediction result based on pure historical habit data.

[0067] Furthermore, the method also includes a backup reminder strategy for situations where the next usage time cannot be predicted:

[0068] When reading the user's historical usage habit data from the storage module, check the validity of the data at the next expected usage time.

[0069] If it is determined that the user's historical usage data is insufficient or the next expected usage time cannot be effectively predicted and generated, then the backup power threshold reminder strategy will be enabled.

[0070] Under the backup power threshold reminder strategy, the main control module continuously monitors the current remaining power and compares it with a set of preset tiered power thresholds;

[0071] When the current remaining battery power drops to the first threshold in the stepped battery power threshold, a first-level charging reminder is generated and issued. The reminder content is a general prompt.

[0072] When the current remaining battery power continues to drop to the second-level threshold, which is a lower level in the tiered battery power threshold, a second-level charging reminder is generated and issued. This reminder is an emphasis reminder, and its frequency or intensity is higher than that of the first-level charging reminder.

[0073] According to a second aspect of the present invention, the present invention claims protection for an intelligent control system for nasal irrigation, comprising:

[0074] One or more processors;

[0075] A memory having stored one or more programs that, when executed by one or more processors, cause the one or more processors to implement the intelligent control method for nasal irrigation.

[0076] This invention relates to the field of medical and nursing equipment technology, and in particular to an intelligent control method and system for nasal irrigation. The method is applied to a nasal irrigation device that includes a main controller, power monitoring, storage, reminder, and charging interface. It monitors the remaining power in real time and predicts the next usage time based on stored user history data. Based on a preset power consumption model for the irrigation process, it calculates the standard power required to complete one irrigation cycle. Then, considering the current power level, standard power level, predicted usage time, and charging rate parameters, it dynamically determines whether a charging reminder is needed. When this is determined, a charging reminder is sent to the user through the reminder module, ensuring that the device has sufficient power to support a complete irrigation cycle before the next expected use, thereby avoiding power outages during use and improving user experience and nursing effectiveness. Attached Figure Description

[0077] Figure 1 A flowchart illustrating the operation of an intelligent control method for nasal irrigation as claimed in an embodiment of the present invention;

[0078] Figure 2 A second flowchart of a smart control method for nasal irrigation claimed in an embodiment of the present invention;

[0079] Figure 3 A third flowchart of a smart control method for nasal irrigation claimed in an embodiment of the present invention;

[0080] Figure 4 The fourth flowchart is shown for a smart control method for nasal irrigation claimed in an embodiment of the present invention. Detailed Implementation

[0081] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0082] The terms "first," "second," and "third" in this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of those features. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications in the embodiments of this application, such as up, down, left, right, front, back, etc., are only used to explain the relative positional relationships and movements between components in a specific orientation as shown in the accompanying drawings. If the specific orientation changes, the directional indications will change accordingly. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0083] References to embodiments herein mean that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0084] According to a first embodiment of the present invention, the present invention claims protection for an intelligent control method for nasal irrigation, applied to a nasal irrigation device including a main control module, a power monitoring module, a storage module, a reminder module, and a charging interface, as described above. Figure 1 The method includes the following steps:

[0085] The power monitoring module monitors the current remaining power of the nasal irrigation device in real time.

[0086] Read user historical usage data from the storage module, wherein the user historical usage data includes at least the user's next expected usage time.

[0087] Based on a preset power consumption model for the rinsing process, the standard power required to complete one full standard rinsing process is calculated.

[0088] Based on the current remaining battery level, the standard battery level, and the next estimated usage time, combined with preset charging rate parameters, it is determined whether a charging reminder instruction needs to be generated.

[0089] When the determination result indicates that a charging reminder instruction needs to be generated, a charging reminder is sent to the user through the reminder module. The charging reminder instructs the user to charge the device before the next expected usage time to ensure that the battery power of the nasal irrigation device is sufficient to support a complete standard irrigation process at the next expected usage time.

[0090] In this embodiment, the power monitoring module periodically samples and measures the battery voltage and current of the nasal irrigation device and transmits the measured raw electrical parameters to the main control module. After receiving the raw electrical parameters, the main control module calls the preset power conversion rule to convert the raw electrical parameters into a current remaining power percentage value that represents the available energy of the device, and writes the percentage value into the first storage area specified in the storage module in real time.

[0091] The main control module sends a data read request to the storage module. The storage module retrieves the pre-recorded and updated user history usage habit dataset from its internal second storage area and returns the dataset to the main control module. The main control module parses the user history usage habit dataset and extracts the key information contained therein. The key information includes at least one predicted next usage time generated by the system.

[0092] The main control module accesses the third storage area of ​​the storage module to obtain a preset set of power consumption model parameters for the rinsing process. Based on this set of model parameters, the main control module executes calculation logic, which explicitly calculates a power consumption value representing a complete rinsing process from start to finish with a preset duration and preset power output, and defines this power consumption value as the standard power consumption value.

[0093] The main control module synchronously acquires the current remaining battery percentage, the next estimated usage time, and the standard power consumption value. Subsequently, the main control module reads a predefined charging rate parameter from the storage module. This parameter represents the amount of power that the charging interface can replenish to the device per unit time when connected to a standard power source. Based on all the above parameters, the main control module runs a judgment logic sequence. The core purpose of this logic sequence is to determine whether the user needs to be prompted to charge before the next estimated usage time arrives, so as to ensure that the available battery power of the device is not lower than the standard power consumption value at that time, and thus outputs a binary judgment result of whether a reminder is needed or not.

[0094] When the output of the logic sequence indicates that a reminder is needed, the main control module generates a structured charging reminder instruction data packet and sends it to the reminder module. Upon receiving the charging reminder instruction data packet, the reminder module, based on the instruction code contained within the data packet, drives its hardware unit to generate at least one physical signal that can be perceived by the user. The physical signal is emitted continuously or intermittently until a preset stop condition is reached. The purpose is to inform the user that the charging interface should be connected to an external power source before the next expected usage time.

[0095] Furthermore, referring to Figure 2 The user's historical usage habit data is generated and updated through the following steps:

[0096] After each nasal irrigation device completes an irrigation process, it records the end timestamp of the current use and stores the end timestamp as a historical usage record in the storage module.

[0097] Periodically retrieve all historical usage records within a preset time window from the storage module;

[0098] Statistical analysis is performed on the timestamps contained in all historical usage records within the preset time window to calculate the user's habitual usage time pattern;

[0099] Based on the user's habitual usage time pattern and the current time, the system predicts and generates the user's next expected usage time, and stores this next expected usage time as part of the user's historical usage habit data in the storage module.

[0100] In this embodiment, after each use of the nasal irrigation device is considered valid, the main control module immediately obtains the current precise date and time information from the real-time clock unit inside the device, generates a timestamp, and temporarily caches the timestamp as a new data entry.

[0101] The main control module compares the newly cached timestamp data entry with the most recent historical usage timestamp already stored in the second storage area of ​​the storage module, and calculates the interval between the two. If the interval is longer than a preset interval threshold used to distinguish between continuous and independent usage events, the new timestamp data entry is appended to the end of the record queue in the second storage area as a valid independent usage record. Otherwise, the new timestamp data entry is discarded to avoid data pollution caused by repeated operations in a short period of time.

[0102] The main control module is triggered by a fixed calendar cycle, such as once every 24 hours, to start a data analysis task. In this task, the main control module reads all valid independent usage records in the second storage area within the past preset analysis time window.

[0103] The data analysis task performs structured processing on all read timestamps. First, it categorizes them by day of the week. Then, within each day category, the 24 hours of a day are divided into multiple statistical time period units of equal or unequal length. For each statistical time period unit, the total number of times the event timestamp falls into that unit is calculated for all dates within the analysis time window.

[0104] Based on the total number of occurrences in each statistical time period, the main control module applies a set of selection rules, such as setting a frequency threshold or selecting the top N time periods with the highest frequency, to identify one or more habitual usage time periods of the user.

[0105] The main control module runs a prediction algorithm based on the latest identified habitual usage time period and the current date and time. This algorithm takes into account factors such as the pattern of the day of the week and the habitual time period closest to the current time to calculate the time point of the next most likely usage event. The calculated time point is then used as the next expected usage time point and updated to the user's historical usage habit dataset.

[0106] Furthermore, the criteria for determining whether a rinsing process is complete are as follows:

[0107] Monitor whether the main control module of the nasal irrigation device receives an irrigation start command initiated by the user through the operation interface;

[0108] Upon detecting the flushing start command, the flushing process is initiated and a timer is started;

[0109] During the operation of the rinsing process after it is started, it continuously monitors whether a rinsing stop command initiated by the user through the operation interface is received, or whether the rinsing process has reached the preset default rinsing time threshold.

[0110] If the flushing stop command is detected or the flushing process reaches the default flushing duration threshold, it is determined that a flushing process has ended, and the timestamp of that moment is recorded as the end timestamp of this use.

[0111] The end timestamp of the record is compared with the most recently stored historical usage record in the storage module. If the time interval between the two records is greater than the preset minimum usage interval threshold, the end timestamp of the current record is stored as a new historical usage record in the storage module; otherwise, it is considered an invalid record and is not stored.

[0112] The statistical analysis specifically includes:

[0113] The end timestamps contained in all historical usage records within the preset time window are categorized according to date and clock time.

[0114] For the same time period each day, the frequency of occurrence of the historical usage records is counted;

[0115] Based on the frequency and the time distribution pattern of the historical usage records, identify one or more high-frequency usage periods for the user each day;

[0116] One or more high-frequency usage periods and their corresponding frequency weights are collectively defined as the user's habitual usage time pattern.

[0117] In this embodiment, the main control module continuously monitors input signals from the device's physical buttons or touchscreen. When it detects a specific signal combination that is predefined as a flushing start, it determines that the user has initiated a usage request. The main control module immediately records this event and sets a usage status flag inside the device to true.

[0118] When the status flag is true during use, the main control module simultaneously starts two parallel monitoring threads: the first monitoring thread continuously listens for whether an input signal related to the rinsing stop is triggered; the second monitoring thread starts a countdown timer, the initial duration of which is set to a preset default rinsing duration threshold, which is a fixed value read from the storage module, representing the recommended maximum duration of a regular rinsing.

[0119] During the rinsing process, the main control module monitors the output of the two monitoring threads in real time: if the first monitoring thread reports receiving a rinsing stop signal, the main control module immediately records a user-initiated stop event and prepares to terminate the process; if the second monitoring thread reports that the countdown timer has reached zero, the main control module records a duration threshold event and prepares to terminate the process. The occurrence of either of these events will trigger the termination determination phase.

[0120] When the end determination phase is triggered, the main control module first controls the power unit to stop working, then sets the in-use status flag to false, and finally obtains the precise time from the real-time clock unit to generate a process end timestamp.

[0121] To ensure data validity, before storing the process end timestamp, the main control module performs a deduplication verification: it calculates the difference between the current process end timestamp and the end timestamp of the latest historical usage record already recorded in the second storage area. The main control module reads a parameter called the minimum usage interval threshold from the storage module. This parameter defines the theoretically shortest allowed time interval between two independent usage events. If the calculated time difference is greater than the minimum usage interval threshold, the main control module determines that the current usage event is a new, independent, and valid usage event, and treats the generated process end timestamp as a new data entry, proceeding with subsequent processing according to the rules in step S220. If the calculated time difference is less than or equal to the threshold, the main control module determines that the current usage may be a mis-continuation or invalid operation of the previous usage, thus discarding the generated process end timestamp and not including it in the historical record.

[0122] Furthermore, the structured processing and statistical analysis are completed through the following detailed sequence of sub-steps:

[0123] After the main control module reads the original timestamp list from the second storage area, it first creates an empty multidimensional data structure. The first-level index of this structure is the day of the week, and the second-level index is multiple consecutive time slots obtained by dividing a day into 24 hours.

[0124] The main control module iterates through each raw timestamp, extracts the day of the week information and the specific hour and minute information corresponding to that timestamp, and assigns it to a specific time slot under the corresponding day of the week based on its hour and minute information.

[0125] After completing the traversal and classification of all timestamps, the main control module counts the number of timestamps falling into each time slot for each day of the week, and obtains the raw count for that time slot.

[0126] The main control module takes into account that the analysis time window may contain different numbers of the same days of the week. To ensure fair comparison, it standardizes the raw counts of each time slot: it calculates the total number of days that a specific target day of the week actually appears within the analysis time window; then it divides the raw count of that time slot by the total number of days to obtain a daily average frequency.

[0127] The main control module associates and stores each time slot with its corresponding daily average frequency. Then, it applies filtering criteria: comparing the daily average frequency with a preset frequency threshold, and / or sorting all time slots from highest to lowest daily average frequency.

[0128] According to preset rules, such as selecting all time slots whose daily average frequency exceeds a frequency threshold, or selecting the top N time slots after sorting, the main control module officially marks these selected time slots as high-frequency usage periods. Each high-frequency usage period records its corresponding day of the week, start time, end time, and calculated daily average frequency. This set of high-frequency usage periods constitutes the user habit usage time pattern used to describe the user's periodic usage behavior.

[0129] Furthermore, the calculation of the standard power consumption required to complete one full standard rinsing process based on the preset power consumption model specifically includes:

[0130] The power consumption parameters per unit time of the nasal irrigation device in the standard working mode are obtained from the storage module. The standard working mode refers to the working state of a preset combination of fixed irrigation pressure and fixed irrigation flow rate.

[0131] Obtain the preset standard rinsing duration parameter corresponding to the standard rinsing process from the storage module;

[0132] The standard power consumption is calculated by multiplication based on the power consumption parameter per unit time and the preset standard rinsing duration parameter.

[0133] The method also includes the step of calculating the required power for different operating modes:

[0134] The storage module retrieves multiple non-standard operating modes supported by the nasal irrigation device, each non-standard operating mode corresponding to a different combination of irrigation pressure and irrigation flow rate.

[0135] For each of the aforementioned non-standard working modes, there are preset parameters for power consumption per unit time and recommended rinsing time.

[0136] When the main control module recognizes that the user has selected a specific non-standard working mode, it calculates the specific mode power required to complete a full rinsing process under the non-standard working mode by multiplication based on the power consumption parameters per unit time and the recommended rinsing time parameters corresponding to the mode.

[0137] In this embodiment, a set of core performance parameters of the device in standard operating mode is pre-stored in the third storage area of ​​the storage module. This standard operating mode refers to a factory-preset combination of fixed flushing pressure and fixed flushing flow rate that cannot be modified by the user through the regular interface. The core performance parameters include: the average operating current of the drive motor under rated load in standard operating mode, and the standard operating voltage of the device's power supply circuit.

[0138] Based on the average operating current value and the standard operating voltage value, the main control module calculates their product to obtain the average instantaneous power value of the equipment's power system during operation in the standard operating mode.

[0139] The third storage area also stores a parameter called preset standard rinse duration, which represents the recommended continuous run time to complete a standard rinse process that is considered complete and meets basic cleaning needs.

[0140] The main control module performs calculations: multiplying the average instantaneous power value by the preset standard flushing time to obtain a theoretical energy consumption value. Then, based on the battery's nominal capacity, the main control module converts this theoretical energy consumption value into a percentage value of the battery's total capacity. This percentage value is ultimately defined as the standard power consumption value and stored in memory as a reference parameter for subsequent steps.

[0141] Phase Two: Preparation for Extended Power Calculation to Support Non-Standard Operating Modes

[0142] The third storage area of ​​the storage module also stores a working mode configuration table, which lists all user-selectable non-standard working modes supported by the nasal irrigation device in addition to the standard mode. Each non-standard working mode has a unique mode identifier in the table, and is associated with its specific irrigation pressure level configuration and irrigation flow rate setting configuration.

[0143] For each non-standard operating mode listed in the operating mode configuration table, the third storage area stores a set of calibrated electrical parameters. These electrical parameters are obtained by running the device in the specific non-standard operating mode during the pre-shipment testing phase, measuring and recording the characteristic operating current curve of its drive motor, and then calculating the average operating current value in that mode.

[0144] Similarly, for each non-standard operating mode, the third storage area also stores a recommended flushing duration parameter. This parameter is a recommended duration set by professionals to achieve the desired flushing effect based on the pressure and flow characteristics of that mode, and it may differ from the duration of the standard mode.

[0145] When the main control module detects through the user interface that the user has selected a specific non-standard working mode, it will look up the mode identifier corresponding to the mode in the working mode configuration table, and read the corresponding average working current value and recommended flushing time from the third storage area accordingly.

[0146] The main control module uses the average operating current value read from this non-standard operating mode, combined with the standard operating voltage value of the device's power supply circuit, to calculate the average instantaneous power value for this mode. Then, it multiplies this average instantaneous power value by the recommended flushing time corresponding to this mode to obtain the theoretical energy consumption value for this mode, and finally converts it into a percentage of battery capacity. This value is defined as the specific mode power consumption value for this non-standard operating mode.

[0147] Phase 3: Selection of dynamic power consumption values.

[0148] Before making a judgment, the main control module first checks the current operating mode and preparation state of the device. If the user has explicitly selected a non-standard operating mode, the main control module uses the calculated power consumption value of that mode as the required power benchmark for subsequent judgments. If the user has not made a selection or the device is in standby mode, the standard power consumption value is used by default as the required power benchmark.

[0149] Furthermore, referring to Figure 3 The logic for determining whether a charging reminder instruction needs to be generated specifically includes:

[0150] Obtain the current remaining battery power and the required battery power corresponding to the user's currently selected working mode. If the user does not select a specific mode, the standard battery power is used as the required battery power.

[0151] Calculate the difference between the current remaining power and the required power, and mark this difference as the power margin;

[0152] Determine whether the battery margin is less than or equal to zero; if so, directly generate the charging reminder command.

[0153] If the power margin is greater than zero, then the time difference from the current time point to the next expected usage time point is further calculated;

[0154] Based on the charging rate parameter and the power margin, estimate the theoretical charging time required to charge the nasal irrigation device from the current remaining power to meet the required power.

[0155] The time difference is compared with the theoretically required charging time. If the time difference is less than or equal to the theoretically required charging time, a charging reminder instruction is generated; otherwise, no charging reminder instruction is generated.

[0156] In this embodiment, the main control module obtains the current remaining battery percentage value derived from the algorithm, denoted as C_current; at the same time, according to the rules determined in the previous step, it obtains the corresponding required battery percentage value, denoted as C_required.

[0157] The main control module calculates the power difference: C_margin = C_current - C_required. This C_margin value represents the surplus power of the device at the current moment after meeting the requirements for one complete flush.

[0158] The main control module performs the first level of judgment: checking whether C_margin is less than or equal to zero. If the judgment is yes, it indicates that the current power is insufficient to support a complete flush, and there is a risk regardless of when it is used. The decision path then directly leads to the need for a reminder.

[0159] If C_margin is greater than zero, it indicates that the current battery power is sufficient, and the main control module then enters the second-level time judgment. It obtains the next estimated usage time from step S200, denoted as T_next. At the same time, it obtains the current time from the device's real-time clock, denoted as T_now.

[0160] The main control module calculates the time difference: T_delta = T_next - T_now. T_delta represents the remaining available time from now until the expected usage time.

[0161] The main control module reads the charging rate parameter from the storage module. This parameter represents the percentage of battery charge that can be delivered per minute when the charging interface is connected to the adapter power supply, and is denoted as R_charge.

[0162] The main control module calculates the theoretically required charging time: T_charge_need = (C_required - C_current + C_margin) / R_charge. In practice, since C_margin = C_current - C_required, the amount of charge needed is the positive value of -C_margin. Therefore, T_charge_need = (-C_margin) / R_charge. This calculation yields the theoretical continuous charging time required to replenish the current charge C_current to exactly reach C_required.

[0163] The main control module makes a core judgment: comparing the remaining available time T_delta with the theoretically required charging time T_charge_need. If T_delta <= T_charge_need, it means that even if charging starts now, the charging time will not be sufficient to bring the battery to a safe level by the expected usage time. Therefore, the user must be reminded to charge immediately, and the decision is that a reminder is needed. If T_delta > T_charge_need, it means there is sufficient buffer time for charging, and no reminder is needed at this stage, and the decision is that no reminder is needed.

[0164] Furthermore, the specific steps for estimating the theoretically required charging time are as follows:

[0165] Obtain the charging rate parameter pre-stored in the storage module, wherein the charging rate parameter represents the amount of electricity that the charging interface can charge the nasal irrigation device per unit time.

[0166] Calculate the difference between the required power and the current remaining power to obtain the amount of power that needs to be replenished;

[0167] Divide the amount of electricity that needs to be replenished by the charging rate parameter to obtain the theoretically required charging time.

[0168] In this embodiment, the main control module reads a charging efficiency compensation coefficient from the storage module. This coefficient is a value between 0 and 1, which is used to characterize the average loss ratio between the energy input from the charging interface and the actual energy stored in the battery.

[0169] The main control module divides the calculated original T_charge_need value by the charging efficiency compensation coefficient to obtain a larger and more conservative revised charging time estimate, T_charge_need_adj. That is: T_charge_need_adj = T_charge_need / charging efficiency compensation coefficient.

[0170] When making comparisons, the main control module uses the corrected T_charge_need_adj value instead of the original T_charge_need value. This is done to take into account the energy loss during the charging process, making the judgment conditions more stringent and ensuring that there is an extra margin when estimating the charging time. This improves the reliability of the reminder and avoids the user having insufficient power when expected due to underestimating the charging time.

[0171] Furthermore, referring to Figure 4 The step of predicting and generating the user's next expected usage time based on the user's habitual usage time pattern and the current time specifically includes:

[0172] Obtain the current time, including the current clock time and the current date;

[0173] From the user's habitual usage time patterns, find a target date that is closest to the current date and has a high-frequency usage period after the current date;

[0174] The start time of the high-frequency usage period or the specific clock time with the highest frequency statistical value within that period in the target date is determined as the next expected usage time point;

[0175] If no matching target date is found after the current date, an average usage interval is calculated based on the statistical patterns of all high-frequency usage periods in the user's habitual usage time pattern. The current time is then added to the average usage interval to obtain the next expected usage time, which is then used as the default next expected usage time.

[0176] In this embodiment, the main control module obtains the current precise date and time T_now, and parses out the corresponding day of the week information W_now and clock time H_now.

[0177] The main control module searches the established user habit usage time patterns to see if there are any time periods marked as high-frequency usage periods within a predetermined number of days, such as 7 days, starting from tomorrow (W_now+1).

[0178] If such a high-frequency usage period exists, the main control module prioritizes the target date closest to the current date as the basis for prediction. Next, it selects one of all high-frequency usage periods from that target date as the predicted usage time point. The selection strategy can be either to choose the start time of the earliest high-frequency usage period on the target date, or to choose the start time of the period with the highest historical daily average frequency among all high-frequency usage periods. This selected specific time point is then set as the next expected usage time point T_next.

[0179] If no high-frequency usage periods are found within the planned search period, such as when user history data is very sparse, the main control module will activate a backup prediction mechanism. This backup mechanism is calculated based on the timestamps of all valid historical usage records.

[0180] The backup mechanism calculates the time interval between all adjacent historical usage records and takes the average of these time intervals to obtain the average usage interval I_mean.

[0181] The main control module adds the calculated average usage interval I_mean to the current time T_now to obtain a projected future time point: T_next = T_now + I_mean. This time point serves as the default expected next usage time point when a clear habitual pattern is lacking.

[0182] Regardless of whether T_next is generated through step S263 or step S266, the main control module will perform a reasonableness check between T_next and the current system time to ensure that T_next is a future time point. If the calculation error causes T_next to be a past time point, the main control module will set T_next to a predefined future default time, such as the current time plus 24 hours.

[0183] Furthermore, the step of sending a charging reminder to the user through the reminder module specifically includes:

[0184] After the main control module generates the charging reminder command, it first determines whether the nasal irrigation device is currently in use;

[0185] If the nasal irrigation device is not currently in use, the reminder module is immediately activated to send a charging reminder to the user through at least one of visual, auditory, or tactile vibration signals.

[0186] The visual signals include, but are not limited to, illuminating indicator lights of a specific color, displaying preset prompt text or icons on the device's display screen;

[0187] After issuing the charging reminder, a reminder timing cycle is initiated;

[0188] If the charging interface is detected to be connected to an external power source during the reminder timing period, the charging reminder will be stopped immediately and a valid response event will be recorded.

[0189] If no charging connection is detected after the reminder timing period ends, the reminder will be temporarily stopped and the judgment process will be repeated after a preset silent interval. If the conditions for generating a charging reminder command are met again, a new reminder timing period will be initiated.

[0190] If the nasal irrigation device is currently in use, the main control module temporarily stores the charging reminder instruction and continuously monitors the end of the current usage process;

[0191] Once the current usage process is detected to have ended, immediately check the temporary storage status of the charging reminder instruction;

[0192] If the charging reminder command is valid, the reminder module will be activated to issue the charging reminder after a preset delay after the end of the usage process, so as to avoid interfering with the user's current usage experience.

[0193] In this embodiment, after the main control module generates a charging reminder command, it does not immediately send it to the reminder module. Instead, it first queries the device's current operating status register to determine what stage of operation the nasal irrigation device is currently in.

[0194] If the operating status register indicates that the device is currently in an idle or standby state, i.e., no rinsing process is being performed, the main control module enters the immediate reminder sub-process.

[0195] In the immediate reminder sub-process, the main control module first constructs a primary reminder command and sends it to the reminder module. Based on the command, the reminder module activates its first-level reminder mechanism: for example, controlling a monochrome LED to flash at a preset slow frequency, such as once per second, and in a preset color, such as yellow.

[0196] The main control module simultaneously starts a first-level reminder duration timer, for example, set to 30 seconds. During these 30 seconds, the main control module continuously monitors the electrical connection status of the charging interface.

[0197] If a valid power source is detected at the charging port during the first-level reminder duration, the main control module determines that the user has responded to the reminder and immediately sends a stop reminder command to the reminder module. The LED light stops flashing, and the entire reminder process successfully ends. The main control module may optionally record one successful response event.

[0198] If no charging connection is detected after the first-level reminder period ends, the main control module determines that the user may have missed or ignored the primary reminder, and then escalates the reminder intensity. It constructs a second-level reminder command and sends it.

[0199] After receiving the secondary reminder instruction, the reminder module adds a second-level reminder method while keeping the LED flashing: for example, activating the buzzer to emit an intermittent, high-pitched beeping sound in sync with the LED flashing.

[0200] The main control module initiates a second-level reminder duration timer, which may be shorter than the first level, for example, 15 seconds. During this upgrade reminder, the charging connection continues to be monitored.

[0201] If a charging connection is detected during the second-level reminder period, all reminders will be stopped immediately. If no connection is found by the end of the second-level reminder period, the main control module will temporarily stop all reminders and enter a silent period to avoid continuously disturbing the user. Simultaneously, the main control module will record this reminder cycle as unresponsive.

[0202] Once the silent period begins, the main control module starts a silent period timer, for example, for 10 minutes. During this period, even if the judgment logic still outputs that a reminder is needed, the reminder module will no longer be triggered.

[0203] After the silent period ends, the main control module automatically returns to retrieve the latest current battery level, time, and other information, and executes a new round of judgment logic. If the new judgment result still indicates that a reminder is needed, it restarts, initiating a new round of reminder loops, which may include first-level and second-level reminders. This reminder-silence-re-judgment-re-reminder loop will continue until the user no longer needs a reminder regarding charging or battery status.

[0204] If the device status check reveals that it is currently in the flushing operation state, the main control module will enter the delayed reminder sub-process.

[0205] In the delayed reminder sub-process, the main control module temporarily stores the generated charging reminder instruction in a dedicated instruction buffer and sets an internal flag indicating that a delayed reminder is pending execution. However, it does not send any instructions to the reminder module at this time to ensure that the user's current rinsing experience is not interrupted.

[0206] The main control module continuously monitors the end of the rinsing process. When the end of the process is detected, the main control module first clears the "in use" status flag.

[0207] After the process is completed, the main control module does not immediately process the delay reminder. Instead, it starts a short operation completion buffer timer, such as 5 seconds, to give the user a short time to complete the operation and avoid the reminder being too abrupt.

[0208] When the operation is completed and the buffer timer expires, the main control module checks whether there are any temporarily stored charging reminder instructions in the instruction buffer and whether the delayed reminder execution flag is true.

[0209] If a valid delayed reminder instruction is confirmed, the main control module retrieves the instruction from the instruction buffer and executes the reminder operation according to the immediate reminder sub-process. If the instruction buffer is empty or the flag is false, the process ends directly without any reminder.

[0210] Furthermore, the method also includes a step of dynamically calibrating the next expected usage time point:

[0211] The storage module records the time when each charging reminder command is generated and the time when the user actually connects to charge.

[0212] Once a user is detected to actually connect to charging, the time interval between generating a charging reminder command and the actual charging connection is calculated and marked as the actual response delay.

[0213] The actual response delay is compared with a preset expected response delay threshold;

[0214] If the actual response delay is greater than the expected response delay threshold in multiple consecutive instances, it is determined that the preset reminder advance amount is insufficient. The time offset parameter used to calculate the next expected usage time is automatically adjusted so that the subsequent predicted next expected usage time is earlier than the prediction result based on pure historical habit data.

[0215] In this embodiment, each time the main control module generates a charging reminder command in step S500, in addition to sending the command to the reminder module, it also records a log entry in a dedicated log area allocated in the storage module. This entry includes at least the precise timestamp T_alert of the reminder command generation.

[0216] When the power monitoring module or charging management circuit detects that the charging interface has been successfully connected to an external power source and has started charging effectively, it will send a charging start event signal to the main control module.

[0217] Upon receiving a charging start event signal, the main control module immediately retrieves the current timestamp from the real-time clock, denoted as T_charge_start. Subsequently, the main control module searches the dedicated log area for the most recently recorded alert log entry that is not yet associated with a charging event, and retrieves its T_alert.

[0218] The main control module calculates the user's response delay: T_response_delay = T_charge_start - T_alert. This value represents the time elapsed from when the system issues an alert to when the user actually performs the charging operation.

[0219] The main control module maintains a sliding window list that records the most recent N, for example, 5, T_response_delay values. Each time a new T_response_delay is calculated, it is added to the end of the list. If the list length exceeds N, the oldest value is removed.

[0220] The main control module periodically analyzes the sliding window list, for example, after every 5 valid reminder-charging events. It calculates the average Mean_delay and the maximum Max_delay of all T_response_delay values ​​in the list.

[0221] The main control module compares the calculated Mean_delay or Max_delay with a baseline expected response delay value preset in the storage module. This expected value represents how quickly the system hopes the user will respond after being alerted.

[0222] If the analysis finds that Mean_delay is consistently greater than the baseline expected value by a certain percentage, such as more than 20%, the main control module will determine that the preparation time left for the user at the next predicted usage time is insufficient, i.e., the time from the reminder to the expected usage, which often results in the user needing a long time to respond, posing a risk.

[0223] Based on this determination, the main control module generates a time offset adjustment command. This command modifies the internal parameters used to predict the time point. For example, it subtracts a safety margin from the original T_next calculated in step S263 or S266. This safety margin can be dynamically calculated based on the difference between Mean_delay and the baseline expected value, for example, set to half of that difference. This ensures that the next estimated usage time, which is used for judgment and reminders, arrives earlier than the actual usage time, giving the user more time to respond to charging.

[0224] Furthermore, the method also includes a backup reminder strategy for situations where the next usage time cannot be predicted:

[0225] When reading the user's historical usage habit data from the storage module, check the validity of the data at the next expected usage time.

[0226] If it is determined that the user's historical usage data is insufficient or the next expected usage time cannot be effectively predicted and generated, then the backup power threshold reminder strategy will be enabled.

[0227] Under the backup power threshold reminder strategy, the main control module continuously monitors the current remaining power and compares it with a set of preset tiered power thresholds;

[0228] When the current remaining battery power drops to the first threshold in the stepped battery power threshold, a first-level charging reminder is generated and issued. The reminder content is a general prompt.

[0229] When the current remaining battery power continues to drop to the second-level threshold, which is a lower level in the tiered battery power threshold, a second-level charging reminder is generated and issued. This reminder is an emphasis reminder, and its frequency or intensity is higher than that of the first-level charging reminder.

[0230] In this embodiment, each time the main control module prepares to read user history usage data, it first verifies the validity of the data. The verification includes: checking whether the data in the second storage area has been corrupted due to an abnormal power outage; checking whether the total number of historical usage records is below a minimum valid data threshold, such as 3 records; and checking whether a valid, future T_next can be successfully generated based on the existing data using an algorithm.

[0231] If any of the above checks fails, the main control module determines that the intelligent prediction mode is unavailable or unreliable, and then internally sets a flag to enable the backup strategy.

[0232] When the backup strategy flag is true, the main control module will no longer rely on the intelligent judgment logic of steps S200-S400, but will switch to a simple comparison logic based on a fixed power threshold.

[0233] Under this backup strategy, the main control module continuously monitors the current remaining battery percentage value C_current from step S100.

[0234] The main control module reads a set of preset tiered battery thresholds from the storage module. This set of thresholds includes at least two levels: a first-level alert threshold, such as 30% battery remaining, and a second-level warning threshold, such as 15% battery remaining.

[0235] The main control module compares C_current with the first-level reminder threshold. When C_current first drops to or below the first-level reminder threshold, the main control module immediately generates a general primary charging reminder command. The reminder triggered by this command may be a simple prompt without specific time suggestions, such as a fixed light signal or a short prompt sound emitted by the reminder module.

[0236] If the user ignores the initial warning and the battery continues to drop, when C_current further decreases to equal or below the lower second-level warning threshold, the main control module generates a strengthened second-level warning instruction. This instruction triggers a significantly stronger warning than the initial warning, for example, by using a more rapid flashing frequency, a louder continuous beeping sound, or both, designed to strongly alert the user that the battery is critically low.

[0237] Once a low-battery alert is triggered under the backup strategy, it typically stops under only two conditions: either the user connects to a charger, or the device shuts down due to complete battery depletion. The backup strategy does not include the silent period and cyclical checks found in the smart strategy; it only provides critical low-battery warnings until external intervention occurs.

[0238] Once the device recovers its power through charging and historical usage data is re-accumulated and meets the validity verification conditions, the main control module will automatically clear the standby strategy flag in the next judgment cycle and revert to the initial intelligent predictive control method.

[0239] According to a second embodiment of the present invention, the present invention claims protection for an intelligent control system for nasal irrigation, comprising:

[0240] One or more processors;

[0241] A memory having stored one or more programs that, when executed by one or more processors, cause the one or more processors to implement the intelligent control method for nasal irrigation.

[0242] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0243] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units. The above are merely embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made based on the description and drawings of this application, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

[0244] The specific embodiments of the invention have been described in detail above, but they are only examples, and this application is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions to the invention are also within the scope of this application. Therefore, all equivalent changes, modifications, and improvements made without departing from the spirit and principles of this application should be covered within the scope of this application.

Claims

1. A method for intelligent control of nasal irrigation, applied to a nasal irrigation device comprising a master control module, a power monitoring module, a storage module, a reminder module and a charging interface, characterized in that, The method includes the following steps: The power monitoring module monitors the current remaining power of the nasal irrigation device in real time. Read user historical usage data from the storage module, wherein the user historical usage data includes at least the user's next expected usage time. Based on a preset power consumption model for the rinsing process, the standard power required to complete one full standard rinsing process is calculated. Based on the current remaining battery level, the standard battery level, and the next estimated usage time, combined with preset charging rate parameters, it is determined whether a charging reminder instruction needs to be generated. When the determination result indicates that a charging reminder instruction needs to be generated, a charging reminder is sent to the user through the reminder module. The charging reminder instructs the user to charge the device before the next expected usage time to ensure that the nasal irrigation device has sufficient power to support a complete standard irrigation process at the next expected usage time. The method further includes a step of dynamically calibrating the next expected usage time point: The storage module records the time when each charging reminder command is generated and the time when the user actually connects to charge. Once a user is detected to actually connect to charging, the time interval between generating a charging reminder command and the actual charging connection is calculated and marked as the actual response delay. The actual response delay is compared with a preset expected response delay threshold; If the actual response delay is greater than the expected response delay threshold in multiple consecutive instances, it is determined that the preset reminder advance amount is insufficient, and the time offset parameter used to calculate the next expected usage time is automatically adjusted so that the subsequent predicted next expected usage time is earlier than the prediction result based on pure historical habit data. The method also includes a backup reminder strategy for situations where the next usage time cannot be predicted: When reading the user's historical usage habit data from the storage module, check the validity of the data at the next expected usage time. If it is determined that the user's historical usage data is insufficient or the next expected usage time cannot be effectively predicted and generated, then the backup power threshold reminder strategy will be enabled. Under the backup power threshold reminder strategy, the main control module continuously monitors the current remaining power and compares it with a set of preset tiered power thresholds; When the current remaining battery power drops to the first threshold in the stepped battery power threshold, a first-level charging reminder is generated and issued. The reminder content is a general prompt. When the current remaining battery power continues to drop to the second-level threshold, which is a lower level in the tiered battery power threshold, a second-level charging reminder is generated and issued. This reminder is an emphasis reminder, and its frequency or intensity is higher than that of the first-level charging reminder.

2. The intelligent control method for nasal irrigation according to claim 1, wherein, The user's historical usage habit data is generated and updated through the following steps: After each nasal irrigation device completes an irrigation process, it records the end timestamp of the current use and stores the end timestamp as a historical usage record in the storage module. Periodically retrieve all historical usage records within a preset time window from the storage module; Statistical analysis is performed on the timestamps contained in all historical usage records within the preset time window to calculate the user's habitual usage time pattern; Based on the user's habitual usage time pattern and the current time, the system predicts and generates the user's next expected usage time, and stores this next expected usage time as part of the user's historical usage habit data in the storage module.

3. The intelligent control method for nasal irrigation according to claim 2, characterized in that, The criteria for determining whether a rinsing process is complete are as follows: Monitor whether the main control module of the nasal irrigation device receives an irrigation start command initiated by the user through the operation interface; Upon detecting the flushing start command, the flushing process is initiated and a timer is started; During the operation of the rinsing process after it is started, it continuously monitors whether a rinsing stop command initiated by the user through the operation interface is received, or whether the rinsing process has reached the preset default rinsing time threshold. If the flushing stop command is detected or the flushing process reaches the default flushing duration threshold, it is determined that a flushing process has ended, and the timestamp of that moment is recorded as the end timestamp of this use. The end timestamp of the record is compared with the most recently stored historical usage record in the storage module. If the time interval between the two records is greater than the preset minimum usage interval threshold, the end timestamp of the current record is stored as a new historical usage record in the storage module; otherwise, it is considered an invalid record and is not stored. The statistical analysis specifically includes: The end timestamps contained in all historical usage records within the preset time window are categorized according to date and clock time. For the same time period each day, the frequency of occurrence of the historical usage records is counted; Based on the frequency and the time distribution pattern of the historical usage records, identify one or more high-frequency usage periods for the user each day; One or more high-frequency usage periods and their corresponding frequency weights are collectively defined as the user's habitual usage time pattern.

4. The intelligent control method for nasal irrigation according to claim 1, wherein, The standard power consumption model for the pre-set rinsing process, which calculates the standard power consumption required to complete one full standard rinsing process, specifically includes: The power consumption parameters per unit time of the nasal irrigation device in the standard working mode are obtained from the storage module. The standard working mode refers to the working state of a preset combination of fixed irrigation pressure and fixed irrigation flow rate. Obtain the preset standard rinsing duration parameter corresponding to the standard rinsing process from the storage module; The standard power consumption is calculated by multiplication based on the power consumption parameter per unit time and the preset standard rinsing duration parameter. The method also includes the step of calculating the required power for different operating modes: The storage module retrieves multiple non-standard operating modes supported by the nasal irrigation device, each non-standard operating mode corresponding to a different combination of irrigation pressure and irrigation flow rate. For each of the aforementioned non-standard working modes, there are preset parameters for power consumption per unit time and recommended rinsing time. When the main control module recognizes that the user has selected a specific non-standard working mode, it calculates the specific mode power required to complete a full rinsing process under the non-standard working mode by multiplication based on the power consumption parameters per unit time and the recommended rinsing time parameters corresponding to the mode.

5. The intelligent control method for nasal irrigation according to claim 4, wherein, The logic for determining whether a charging reminder command needs to be generated specifically includes: Obtain the current remaining battery power and the required battery power corresponding to the user's currently selected working mode. If the user does not select a specific mode, the standard battery power is used as the required battery power. Calculate the difference between the current remaining power and the required power, and mark this difference as the power margin; Determine whether the battery margin is less than or equal to zero; if so, directly generate the charging reminder command. If the power margin is greater than zero, then based on the charging rate parameter and the power margin, the theoretical charging time required for the nasal irrigation device is estimated, and the remaining available time is calculated and compared with the theoretical charging time required. If the remaining available time is less than or equal to the theoretically required charging time, then a charging reminder instruction is generated; otherwise, no charging reminder instruction is generated.

6. The intelligent control method for nasal irrigation according to claim 5, wherein, The specific steps for estimating the theoretical charging time required for the nasal irrigation device are as follows: Obtain the charging rate parameter pre-stored in the storage module, wherein the charging rate parameter represents the amount of electricity that the charging interface can charge the nasal irrigation device per unit time. Calculate the difference between the required power and the current remaining power to obtain the amount of power that needs to be replenished; Divide the amount of electricity that needs to be replenished by the charging rate parameter to obtain the theoretically required charging time.

7. The intelligent control method for nasal irrigation as claimed in claim 2, wherein, The process of predicting and generating the user's next expected usage time based on the user's habitual usage time pattern and the current time specifically includes: Obtain the current time, including the current clock time and the current date; From the user's habitual usage time patterns, find a target date that is closest to the current date and has a high-frequency usage period after the current date; The start time of the high-frequency usage period or the specific clock time with the highest frequency statistical value within that period in the target date is determined as the next expected usage time point; If no matching target date is found after the current date, an average usage interval is calculated based on the statistical patterns of all high-frequency usage periods in the user's habitual usage time pattern. The current time is then added to the average usage interval to obtain the next expected usage time, which is then used as the default next expected usage time.

8. The intelligent control method for nasal irrigation according to claim 1, wherein, The specific steps of sending a charging reminder to the user through the reminder module include: After the main control module generates the charging reminder command, it first determines whether the nasal irrigation device is currently in use; If the nasal irrigation device is not currently in use, the reminder module is immediately activated to send a charging reminder to the user through at least one of visual, auditory, or tactile vibration signals. The visual signals include, but are not limited to, illuminating indicator lights of a specific color, displaying preset prompt text or icons on the device's display screen; After issuing the charging reminder, a reminder timing cycle is initiated; If the charging interface is detected to be connected to an external power source during the reminder timing period, the charging reminder will be stopped immediately and a valid response event will be recorded. If no charging connection is detected after the reminder timing period ends, the reminder will be temporarily stopped and the judgment process will be repeated after a preset silent interval. If the conditions for generating a charging reminder command are met again, a new reminder timing period will be initiated. If the nasal irrigation device is currently in use, the main control module temporarily stores the charging reminder instruction and continuously monitors the end of the current usage process; Once the current usage process is detected to have ended, immediately check the temporary storage status of the charging reminder instruction; If the charging reminder command is valid, the reminder module will be activated to issue the charging reminder after a preset delay after the end of the usage process, so as to avoid interfering with the user's current usage experience.

9. An intelligent control system for nasal irrigation, characterized in that, include: One or more processors; A memory having stored one or more programs that, when executed by one or more processors, cause the one or more processors to implement an intelligent control method for nasal irrigation according to any one of claims 1 to 8.

Images