A multi-level timing method for detecting missing status based on year (Y) / month (M) / day (D) parameters

By detecting missing Y/M/D parameters and using a dual-track lunar-Gregorian calendar engine, multi-level timing control is achieved. This solves the shortcomings of existing timer technologies in detecting missing year/month/day parameters and converting lunar dates. It supports precise date control and dual-mode switching, and is suitable for industrial equipment scheduling, agricultural irrigation, smart homes, and IoT devices.

CN123070906APending Publication Date: 2026-11-10蒋骐临
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510598951.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing timer technology cannot support missing year/month/day parameters, lacks lunar date conversion function, and only supports weekday-based cyclic control, making it impossible to achieve multi-level timer control.

Method used

By detecting the absence of Y/M/D parameters, the system automatically identifies the missing parameters using eight parameter combination modes. Combined with a lunar-Gregorian dual-track engine and a conflict resolution system, it achieves multi-level timing control.

Benefits of technology

It supports precise date control and is suitable for industrial equipment scheduling, agricultural irrigation, smart home and IoT devices. It enables free switching between Gregorian and Lunar calendar modes, solving the problems of mode limitations and insufficient input requirements in existing technologies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070906A_ABST
    Figure CN123070906A_ABST
Patent Text Reader

Abstract

This invention relates to a multi-level timing control system based on Y / M / D parameter gap detection, belonging to the field of intelligent timing control technology. The technical problems solved include: existing timers cannot handle partial gap combinations of year / month / day parameters; lack of a lunar calendar mode; lack of adaptability to holidays and adjusted workdays; and lack of timing control capabilities with monthly, quarterly, and annual date and time units. Key technical points: Automatic identification of multiple working modes is achieved through Y / M / D parameter combinations (such as Y empty / M set / D set); a built-in bidirectional conversion system between lunar and Gregorian calendars is implemented; a three-level priority adjudication mechanism based on year, month, and day is used to resolve instruction conflicts; all functional modules (basic timing / lunar calendar / holiday / quarterly modes) can be deployed independently or used in combination. Main applications: Scenarios requiring highly adaptable timing control, such as industrial equipment scheduling, agricultural irrigation, smart homes, and IoT devices. Abstract and attached figures: Figure 1 (system workflow diagram), showing the core control logic.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to an intelligent timing control system, and in particular to a multi-level timing method based on the detection of missing year (Y) / month (M) / day (D) parameters. It is applicable to electronic systems that require precise date control, such as industrial equipment scheduling, agricultural irrigation, smart homes, and Internet of Things devices, and supports free switching between Gregorian and Lunar calendar modes. Background Technology

[0002] Analysis of mainstream timer technologies on the market (including but not limited to weekly cycle timer products) reveals the following technical limitations: 1. Mode limitations: Only supports week-based cyclic control; 2. Input requirements: Hour, minute, and day of the week parameters must be fully set; 3. Missing Hierarchical Levels: No ability to detect missing year / month / day parameters; 4. Calendar support: Lacks lunar date conversion function.

[0003] A search revealed no existing technology that employs a multi-level timing control method by detecting the absence of Y / M / D parameters. Summary of the Invention

[0004] The core technical solutions are as follows; A[Input Parameter] --> B{Whether Y is set?} B -->|Yes| C{M set?} B -->|No| D [Daily Cycle Mode] C -->|Yes| E{Is D set?} C -->|No| F [Annual Cycle Mode - Daily Throughout the Year] E -->|Yes| G[Year / Month / Day Single-Time Mode] E -->|No| H[Annual Cycle Mode - Daily in a Certain Month] D -->|Y / M / D are all empty| I [Daily Execution] F -->|Y set / M empty / D empty| J[Execute daily throughout the year] H -->|Y set / M set / D empty| K[Execute daily in a certain month of a certain year] G -->|Y / M / D all set| L [Exact single execution]

[0005] Parameter missing detection process (see details) Figure 1 System workflow diagram).

[0006] Innovative characteristics: Eight parameter combination modes are automatically recognized; (see details) Figure 2(Working mode control rule table based on Y / M / D parameters) Any combination pattern can be implemented independently as a product function; 3. Lunar-Gregorian dual-track engine (see details) Figure 3 (Lunar calendar conversion flowchart) 4. Conflict adjudication system (see details) Figure 4 (Flowchart of priority hierarchy determination for Y>M>D) Parameter missing detection process Automatically recognizes 8 input combination modes Example 1: -- / -- / 15 08:00 → Executed on the 15th of each month Parameter combination detection process For consecutive months, the system is also set to automatically be classified as a quarterly mode (weight 2). Example 2: -- / 1 / -- 08:00; -- / 2 / -- 08:00 → Combine January and February into the first quarter for execution. Lunar calendar dual-track engine Explicitly switch interfaces (weight 5) Example 8: Leap 4 / First 8 12:00 → Automatically generate dual Gregorian calendar date Conflict adjudication system Priority hierarchy Y>M>D (weight 6) Example 10: The National Day shutdown command covers the activation on the 1st of each month. Attached Figure Description

[0007] Figure 1 System workflow diagram; Figure 2 : Operating mode control rule table based on Y / M / D parameters; Figure 3 Quarterly workflow diagram; Figure 4 Flowchart of Lunar Calendar Conversion; Figure 5 Flowchart for determining the priority of Y>M>D.

[0008] Figure 6 Holiday setup flowchart. Detailed Implementation

[0009] Example 1 (Daily Mode) Input: '-- / -- / -- 08:00 open', the system recognizes it as "Y empty M empty D empty", and executes the open command at 08:00 every day (support right 1①).

[0010] Example 2 (Daily Pattern in a Certain Year) Input: '2025 / -- / -- --:--open', the system recognizes it as "Y set M empty D empty", and executes the open instruction (support weight 1 ② + weight 3) at 00:00 every day in 2025.

[0011] Example 3 (Daily Pattern in a Certain Month and Year) Input: '2025 / 01 / -- 05:30 open', the system recognizes it as "Y set M set D empty", and executes the open command at 05:30 every day in January 2025 (support right 1③).

[0012] Example 4 (a pattern for a specific day of a specific month in a specific year) Input: '2025 / -- / 29 12:00 Close', the system will automatically skip February 29 (non-leap year), and execute the close command normally on the 29th of other months (support right 1④).

[0013] Example 5 (Year, Month, Day Pattern) Input: 'Open at 06:00 on 2025 / 10 / 01', 'Close at 00:15 on 2026 / 5 / 01'. It will operate continuously from 06:00 on October 1, 2025 to 00:15 on May 1, 2026. (Supporting right 1⑤) Example 6 (Month and Day Pattern) Input: '-- / 10 / 15 12:00 Close', the system recognizes it as "Y Empty M Set D Set", the close command is executed at 12:00 on October 15th every year (support right 1⑥).

[0014] Example 7 (Quarterly Fixed Pattern) Input: '-- / 01 / -- 05:00 open 18:00 close'; '-- / 02 / -- 05:00 open 18:00 close'. At the same time, the linear transition selector is not selected. The system recognizes that January and February are the same quarter. The 05:00 open and 18:00 close instructions are executed from January 1st to the end of February each year (support weight 1⑦ + weight 2).

[0015] Example 8 (Quarterly Progressive Control) Input: '-- / 04 / -- 05:00 open 18:00 close'; '-- / 05 / -- 05:00 open 18:00 close'; '-- / 06 / -- 06:00 open 17:00 close'; '-- / 07 / -- 06:00 open 17:00 close', and select the linear transition selector, the system will perform the following actions: April and May are designated as the first quarter, and June and July as the second quarter. The trigger time is adjusted evenly on a daily basis (opening at 5:00 on April 1st and closing at 6:00 on July 31st, and closing at 18:00 on April 1st and 17:00 on July 31st) (support weight 17 + weight 2).

[0016] Example 9 (Monthly Day Pattern) Input: '-- / -- / 15 18:00 Close', the system recognizes it as "Y empty M empty D set", and executes the close command at 18:00 on the 15th of each month (support right 1⑧).

[0017] Example 10 (Self-calibration at the end of the month) Input: '-- / -- / 31 08:00 open', System response: February → 28 / 29, short month → 30, long month → 31 execute open command (support weight 4).

[0018] Example 11 (Agricultural Seasonal Irrigation Control) For the critical growth period of rice cultivation, from "Grain in Ear" to "Summer Solstice", the system executes the following automatic control process: Obtain the Gregorian calendar dates for Grain in Ear (June 5) and Summer Solstice (June 21) in 2025 from the lunar calendar database; from June 5 to June 21, the irrigation system will start precisely at 05:00-06:00 every day (the specific time is set by the user); the execution period will be recalculated the following year based on the new solar term dates (support weight 1⑥ + weight 5).

[0019] Example 12 (Y / M / D parameter priority) Settings: -- / -- / 25 09:00-10:00 (Monthly self-check) 2024 / 12 / 25 09:00-17:00 (Annual Maintenance) Execution logic: Maintenance will be performed from 09:00 to 17:00 on December 25th.

[0020] Example 13 (Agricultural Irrigation and Weather API Linkage) Settings: -- / -- / -- 06:00 (Execute daily) System response: 1. Identify as a daily execution mode and generate a daily execution queue at 06:00; 2. Integration with the weather API: Automatically skip irrigation during rainy days; Support weight 1① + weight 3 (skip in case of anomalies).

[0021] Example 14 (Holiday Working Mode) Settings: -- / 10 / 01-07 08:00 on 17:00 off, enable holiday selector; System response: Recognizing it as a holiday work mode, an execution queue is generated daily from 08:00 to 17:00 between October 1st and 7th (support weight 7).

[0022] Example 15 (No working mode on holidays) Settings: -- / -- / -- 08:00 on 17:00 off, -- / 10 / 01-07 --:--, enable holiday selector; System response: If the system is identified as operating in a holiday mode, a full shutdown execution queue will be generated between October 1st and 7th.

[0023] Example 16 (Holiday Compensation Mechanism) Settings: -- / -- / -- 08:00 on 17:00 off, 2025 / 05 / 01-04 --:--, 2025 / 04 / 27 08:00 on 17:00 off, 2025 / 05 / 11 08:00 on 17:00 off, enable holiday selector; Setup instructions: The official workdays for compensating for the holiday are April 27th and May 11th. By adding these two days as compensating workdays, the final effect of the system will be as follows: No work between May 1st and 4th (May 1st holiday), normal rest on Saturdays April 26th and May 10th (no work on weekends in holiday mode), and normal work hours from 8:00 to 17:00 on April 27th and May 11th (compensating workdays for compensating for the holiday).

[0024] Example 17 (Implementation of Holiday Control in IoT Scenarios) Settings: -- / -- / -- Turn on at 08:00 and turn off at 17:00; Enable holiday selector. The system backend calls the cloud server's holiday data and automatically configures the data for rest days and adjusted workdays, so that the system works from 8:00 to 17:00 on weekdays and adjusted workdays, and does not work on holidays.

[0025] Example 18 (Multi-mode combined operation) Simultaneously set: -- / -- / -- 08:00 open 17:00 close, -- / -- / 16 07:00 open 18:00 close, 2026 / 12 / -- 06:00 open 19:00 close; Operational results: In December 2026, the system will operate from 6:00 to 19:00; on the 16th of each month except December 2026, the system will operate from 07:00 to 18:00; and on the 16th of each other month except December 2026, the system will operate from 08:00 to 17:00. Modular Functionality Implementation Description

[0026] The technical solution of this system, through its flexible architecture combining Y / M / D parameters, naturally supports the following productization methods: 1. Separability of technical modules

[0027] Each functional module is based on a unified parameter parsing engine, but can be deployed independently: Basic working module Products that can independently achieve functions such as daily, monthly, yearly, or specified date and time work by arbitrarily combining Y / M / D parameters.

[0028] Lunar Calendar Module This product only implements a Y-space / M-space / D-space (lunar calendar date) and a Gregorian calendar conversion engine, and is suitable for products with functions such as religious festival management systems and traditional solar term agricultural equipment control.

[0029] Holiday module It only implements Y setting / M setting / D setting and Y setting / M setting / D setting (holidays) + Y empty / M empty / D empty HH:MM (normal working hours), and is suitable for products that require holiday functions, such as shopping mall business hours control systems and government agency duty scheduling.

[0030] Quarterly mode module By using Y-set / M-space / D-space, quarterly divisions (e.g., Q1 = January-March) can be achieved, generating progressive or fixed-time quarterly execution plans. This is suitable for products that require smooth transition of lighting control time by quarter, or industrial equipment that executes different on / off times by quarter.

[0031] Flexibility of commercial implementation The same technical solution can be adapted to product needs at different levels. For example, the Y / M / D vacancy mechanism is adapted to daily industrial control needs; the Y / M / D vacancy mechanism + lunar calendar mechanism is adapted to agricultural irrigation and animal husbandry needs; and the Y / M / D vacancy mechanism + holiday mechanism is adapted to enterprise-level and commercial-level needs.

[0032] The modular design of this system provides tiered implementation schemes for different application scenarios. Whether it is a household appliance that only needs basic timing function or an industrial control system that needs to handle the complex cross-determination of lunar holidays, it can be realized by adapting to the Y / M / D parameter combination hierarchy in this technical solution. The loose coupling between modules ensures that the technical solution can be deployed as a whole or split and applied as needed.

[0033] It should be noted that, based on the teachings of the above-mentioned Y / M / D parameter combinations, those skilled in the art can flexibly select single or combined functional modules to implement specific products, and such implementation methods are all within the foreseeable scope of this technical solution.

Claims

1. A multi-level timing method for detecting missing status based on year (Y) / month (M) / day (D) parameters, characterized in that... include: (1) Parameter receiving module, used to receive parameter combinations including year (Y), month (M), date (D) and working time (H:MM), where Y / M / D are optional parameters; (2) Status detection module, used to identify the missing setting status of Y / M / D parameters; (3) The mode execution module activates the corresponding 8 control modes based on the parameter missing status: The eight control modes can be deployed individually or used in combination as independent functional modules, including: If no settings are set for the year / month / day (Y empty, M empty, D empty), execute daily H:MM timed control; When only the year is set (Y is set, M is empty, D is empty), execute the daily H:MM timed control for year Y; When the year and month are set (Y is set, M is set, D is left blank), the daily H:MM timed control for year M month is executed. When the year and date are set (Y set, M empty, D set), the timed control of Y year, month, D day, H:MM is executed. When the settings are set for the year / month / day (Y setting, M setting, D setting), execute a single trigger on year Y, month M, day D; When the month and date are set (Y empty M set D set), the timed control is executed every year M month D day H:MM; When only the month is set (Y empty, M empty, D empty), the daily H:MM timed control is executed every year in the M month; When only the date is set (Y empty, M empty, D set), timed control is executed on the D day of each month of each year; (4) Lunar calendar processing module, which realizes calendar conversion through the following steps: a) Receive lunar calendar input and verify its validity; b) Invoke the pre-stored leap month rules to perform date mapping; c) Output the Gregorian calendar date execution queue.

2. The method according to claim 1, characterized in that: The annual cycle mode includes a quarterly control strategy. When the same H:MM parameter is set for ≥2 consecutive months, a progressive or fixed-time quarterly execution plan is generated.

3. The method according to claim 1, characterized in that: The working time parameter (H:MM) supports default value handling logic, including: (1) When the parameter is left blank, the default value is 00:00; (2) Skip the trigger when a specific symbol is entered.

4. The method according to claim 1, characterized in that: The monthly cycle mode uses a month-end date backtracking algorithm to handle abnormal dates across months and works in conjunction with a leap year corrector to adjust the February date.

5. The method according to claim 1, characterized in that: The lunar calendar processing module includes: (1) Distributed databases with leap month markers; (2) Lunar calendar input interface that requires explicit activation by the user.

6. The method according to claim 1, characterized in that: When commands conflict, the hierarchical decision priority is set according to the parameters Y>M>D, regardless of the order of user input.

7. The method according to claim 1, characterized in that, Holiday control can be achieved through the following methods: (1) Convert holidays into Y / M / D parameter combinations, including: Fixed holidays (Y-space / M-space / D-space): (e.g., New Year's Day holiday on January 1st); Floating holidays (Y-design / M-design / D-design): (e.g., the Spring Festival holiday from the 30th day of the twelfth lunar month to the 7th day of the first lunar month); Customize holiday rules: Type 1 (Y-design / M-design / D-design): (e.g., company anniversary date); Type 2 (Y empty / M empty / D set): (e.g., companies give employees a holiday at the end of each month); Determining work schedule during holidays: Activate holiday mode using the explicit holiday selector: If the command is Y / M / D --:--, the system will determine that it is in holiday non-working mode and will not work during holidays. If the instruction is Y / M / D HH:MM, the system determines it to be a holiday work mode, and the working time during the holiday period is HH:MM. Dynamic adjudication system: If non-holiday mode commands and holiday mode commands overlap, the holiday mode commands will be executed first. If the instruction is -- / -- / -- HH:MM, combined with Y / M / D --:--, and the holiday selector is turned on, then weekends and holidays will be automatically skipped, and the daily HH:MM work instruction will be executed at other times. (4) Compensation mechanism for compensatory time off: The Y / M / D+workday marking parameter combination is used to mark the dates before and after holidays as workdays. For workdays that are not close to holidays, the marking of workdays and working hours can be specified by setting Y / M / D HH:MM; or, when connected to the network, the server can be called to request or related APIs to mark workdays, and work tasks will be performed on the marked dates.