An offline interactive task points management device and its control method
By using an offline interactive task points management device and a state processing path driven by a real-time clock and permission attributes, the problem of inconsistency between task status and points status in an embedded terminal when offline is solved, achieving low-power and efficient task management, and supporting flexible points query and display updates.
Patent Information
- Application Number
- CN202611338713.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-11-17
AI Technical Summary
Existing electronic task management products suffer from limited continuous availability in offline states, inconsistent task status with points status, high power consumption in resource-constrained embedded terminals, low efficiency in task list recognition, and difficulty in querying points records based on conditions.
An offline interactive task points management device is adopted, including a processor, local memory and a real-time clock. The task status is determined based on the real-time clock, and the status processing path is driven by permission attributes. The points status is updated through transactions, and low-power wake-up mechanism and partial display refresh are supported.
It achieves a closed-loop management system for task status and points in the absence of a network connection, reduces power consumption, improves the efficiency of task status judgment, ensures data consistency, and supports flexible point query and display updates.
Smart Images

Figure CN123114672A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of embedded human-computer interaction terminals, task scheduling, and local data processing technology. In particular, it relates to an offline interactive task points management device and its control method that can complete task status determination, interactive input processing, permission verification, points status update, and points transaction record management based on local time information without relying on external networks or remote servers to provide task processing results. Background Technology
[0002] Existing electronic task management products typically achieve task assignment, task confirmation, points accumulation, and reward redemption through mobile applications, web servers, or multi-terminal collaboration. While these solutions are relatively mature in terms of task and points rules, their core processing often relies on network connections, remote accounts, or external terminals, limiting their continuous availability in offline environments.
[0003] On the other hand, common task lists are often presented as static lists or loaded by date. When a task has a start time, duration, and repetition rules, the user still needs to manually search for the task to be executed, or the processor needs to use frequent polling to continuously determine task changes, which is not conducive to reducing power consumption in resource-constrained embedded terminals.
[0004] Furthermore, task status, points balance, daily statistics, and points transaction records are often written separately by different processing flows. If a power outage, reset, repeated touch, or verification process interruption occurs during the writing process, issues such as task status changes without points being updated, points being accumulated repeatedly, and inconsistencies between points transaction records and points balances may arise. Existing solutions also often treat the completion status as an irreversible final state, making it difficult to synchronously reverse the corresponding points impact in case of user misoperation or changes in the actual completion status.
[0005] Therefore, a technical solution suitable for independent embedded terminals is needed to enable task scheduling, permission verification, and points status processing to form a local closed loop on a single terminal, while improving the consistency of associated data and low-power operation capabilities while satisfying interactivity. Summary of the Invention
[0006] I. Technical problems to be solved
[0007] One objective of this invention is to provide an offline interactive task points management device and its control method to solve problems in the prior art such as the dependence of independent task terminals on external networks, low efficiency in determining the current target of dynamic time tasks, separation of permission verification path and task status processing, and easy inconsistency between task status and points status updates; and to improve the problems of low recognition efficiency of plain text to-do lists or redemption lists, and difficulty in querying points records by conditions and forming intuitive statistical results.
[0008] II. Technical Solution
[0009] To achieve the above objectives, the present invention provides an offline interactive task points management device, comprising a processor, a local memory, a real-time clock, and a user interaction module. The local memory stores multiple task records; each task record includes at least task time parameters, points parameters, and permission attributes. The processor determines the real-time task status based on the current time provided by the real-time clock and the task time parameters, and identifies the target task from among the multiple tasks. The user interaction module presents the target task and receives status change input. The processor responds to the status change input by reading the permission attributes of the target task and selects either a first status processing path or a second status processing path that includes a local authentication process. After satisfying the status change conditions of the corresponding status processing path, it generates a points change event based on the points parameters and updates the task status and local points status accordingly. For tasks valid for the current date, the user can submit completion, incomplete, or cancellation input at any time on the same day; the processor synchronously adds, replaces, deletes, or invalidates corresponding points transaction records 230, and updates the current points value in the forward or reverse direction according to the points change of the added, replaced, deleted, or invalidated records. Task records and reward item records may also include icon identifiers selected from the corresponding preset icon set, so that the user interaction module can associate the icon with the record information; the processor may also respond to query input to retrieve points transaction records 230, and present the query results or statistical information formed by the query results in the form of a list, statistical chart or a combination thereof.
[0010] In some implementations, task time parameters include start time, duration, and repetition rule. The processor generates or determines a task instance for the current date based on the current date and repetition rule, and obtains the corresponding task time window based on the start time and duration. The real-time task status may include at least several of the following states: not started, active, timed out, completed, and incomplete.
[0011] In some implementations, the processor automatically determines the target task based on the real-time task status of each task instance. When at least one incomplete task is active, the target task is selected from the active tasks first; when no active task exists, the future task with the closest start time to the current time can be selected. When multiple tasks are active simultaneously, selection can be made based on the earliest end time, earliest start time, preset priority, or a combination thereof.
[0012] In some implementations, permission attributes are used to direct the same type of status change input to different local processing paths. When the permission attribute indicates that no confirmation is required, the processor directly determines the task status change condition and submits the corresponding event; when the permission attribute indicates that confirmation is required, the processor enters a waiting verification state, outputs a local authentication interface, and only allows the submission of the status change event after successful verification.
[0013] In some implementations, the points status update adopts transactional processing. The points transaction record 230 may include a transaction identifier, a source task or task instance identifier, an event type, a points change, a points value before the transaction, a points value after the transaction, and a timestamp. Task completion, task incompleteness, reward redemption, manual adjustment, and status cancellation can all use the same points transaction data structure. The processor can determine whether the same event has been submitted by using the transaction identifier and the source identifier, thereby suppressing duplicate points changes caused by duplicate input. When the same task changes from completed to incomplete, from incomplete to completed, or returns to an unprocessed state, the processor first restores the current points value in reverse according to the points change in the original points transaction record, and then adds a replacement points transaction record according to the new task processing status, or deletes the original record or invalidates the original record when canceling. The processor can also query the points transaction record 230 according to time range, event type, source identifier, transaction status, or a combination thereof, and generate at least one query result or statistical result among points increase / decrease details, cumulative value, net change value, event count, time trend, or category distribution.
[0014] In some implementations, the processor determines the next state transition time based on the next start time of the current task instance, the next end time of the active task, the timer expiration time, etc., and configures a real-time clock wake-up accordingly. When there is no continuous interactive processing requirement, the processor enters a low-power state and is woken up at the next state transition time or when a user input event occurs.
[0015] In some embodiments, the user interaction module includes a display module for presenting the task interface and an input unit for receiving interactive input. The input unit can be integrated with the display module or set up independently. The display module can employ reflective, transmissive, semi-transparent, self-emissive, or other display principles, and can be monochrome or color, and touch-sensitive or non-touch-sensitive. In one embodiment, the processor updates the interface by selecting at least one method from full-screen update, area-based update, and differential update based on the update capability of the display module. In a specific embodiment, the display module is a reflective monochrome touch-sensitive display module.
[0016] III. Beneficial Effects
[0017] (1) Core task status judgment, permission verification and points status processing can be completed locally, and the complete task processing loop can be maintained even if the network is unavailable.
[0018] (2) The current target task is automatically determined based on the real-time clock and task time window, reducing the user's manual search for the current task in the static list, and providing clear state transition boundaries for event-driven low-power control; by associating preset icons with to-do items or reward items, the operation and time required for the user to identify list items can be reduced.
[0019] (3) Use the task’s own permission attributes to control different local state processing paths, so that the verification process is combined with the task state transition.
[0020] (4) Update task status, points balance and points transaction records 230 through transactional association, and reduce the risk of data inconsistency caused by abnormal interruption or repeated input by combining transaction uniqueness judgment; support reverse restoration of the original points when the task status changes or is canceled on the same day, and present points transaction records and statistical results in a list, statistical chart or combination thereof according to the query conditions, so as to facilitate verification of points changes and their sources.
[0021] (5) Configure wake-up according to the next state transition time, and adopt full-screen update, regional update or differential update according to the characteristics of the display module to reduce unnecessary continuous operation and display updates of resource-constrained embedded terminals. Attached Figure Description
[0022] Figure 1 This is a schematic diagram of the hardware and functional modules of an offline interactive task points management device.
[0023] Figure 2 This is a schematic diagram of the data structure for task records and task instances.
[0024] Figure 3 This is a flowchart illustrating the process of determining task instances based on the current date and repetition rules.
[0025] Figure 4 This is a flowchart illustrating the process of determining the real-time task status and target task based on the task time window.
[0026] Figure 5 This is a schematic diagram of the task state machine.
[0027] Figure 6 This is a flowchart illustrating the process of selecting a status processing path based on permission attributes.
[0028] Figure 7 This is a schematic diagram of the points transaction and associated status update process.
[0029] Figure 8 This is a schematic diagram of the process for suppressing repeated input and recovering from anomalies.
[0030] Figure 9This is a schematic diagram of a low-power wake-up process based on the next state transition moment.
[0031] Figure 10 This is a schematic diagram illustrating how to determine the display update area and update method based on differences in interface state.
[0032] Reference numerals: 100-Offline interactive task points management device; 110-Processor; 120-Local memory; 130-Real-time clock; 140-User interaction module; 150-Power management module; 160-Optional communication module; 210-Task record; 220-Task instance; 230-Points transaction record; 240-Reward item record. Detailed Implementation
[0033] The exemplary embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the following embodiments are for illustrative purposes only and not for limiting the scope of protection. Where there is no conflict, the technical features of the various embodiments can be combined with each other.
[0034] Example 1: Overall Structure of the Device
[0035] like Figure 1 As shown, the offline interactive task points management device 100 includes a processor 110, local memory 120, real-time clock 130, user interaction module 140, and power management module 150. The device may also include an optional communication module 160. The processor 110 may be a microcontroller, microprocessor, or system-on-a-chip; the local memory 120 may include on-chip flash memory, external flash memory, non-volatile memory, and runtime memory; the real-time clock 130 may be implemented by a separate RTC chip, a processor low-power clock unit, or other timing unit capable of maintaining a time base in a low-power state of the main processor.
[0036] The user interaction module 140 may include a display module and an input unit. The display module may employ reflective, transmissive, semi-transparent, self-illuminating, or other display principles, and may be monochrome or color. The input unit may be a touch sensor integrated with the display module, or it may be a separately configured button, knob, touch sensor, voice input unit, or a combination thereof. In one specific embodiment, the user interaction module 140 includes a 400×300 pixel reflective monochrome touch-sensitive display module. The specific resolution, display principle, color mode, and input method described above are merely embodiments and do not limit the scope of the invention.
[0037] The optional communication module 160 may include Wi-Fi, Bluetooth, USB, or other wired / wireless interfaces. Even with the communication module 160 configured, the "offline" aspect of this invention refers to the fact that the core task status determination, permission verification, points change, reward redemption, and points transaction record management after task creation do not require the return of task processing results from an external server or remote terminal; the communication module may be used only for backup, upgrade, export, or optional synchronization.
[0038] Example 2: Task Records and Task Examples
[0039] like Figure 2 As shown, local storage 120 stores multiple task records 210. Each task record may include a task identifier, task name, icon identifier, start time, duration, repetition rule, reward points, deduction points, permission attributes, and optional priority. The icon identifier may point to a preset set of task icons stored in local storage. Users can select an icon when creating or editing a task, and the user interaction module 140 will associate the selected task icon with the task name, time, or status information in the to-do list or target task area. The repetition rule may include daily, weekday, weekend, weekly, monthly, one-time, or a custom set of dates.
[0040] When a date changes, the device starts up, the task record is updated, or a predetermined event triggered by the real-time clock 130 occurs, the processor 110 determines the tasks valid for the current date based on the current date and repetition rules, and forms task instances 220 for the valid tasks. Task instance 220 may include an instance identifier, a source task identifier, an instance date, a start timestamp, an end timestamp, a real-time task status, a completion status, a transaction status, etc. The task instance can be actually written to memory, or it can be calculated by the processor based on the task record during runtime.
[0041] Example 3: Time Window and Current Target Task
[0042] like Figure 3 and Figure 4 As shown, for task instance i, processor 110 determines the end time Ei = Si + Di based on the start time Si and duration Di, thus obtaining the task time window [Si, Ei). The processor obtains the current time Tnow and compares Tnow with Si, Ei and the completion status of the task instance to determine the real-time task status such as not started, active, timed out, completed or not completed.
[0043] For example, Task A starts at 07:15 and lasts for 10 minutes, while Task B starts at 07:30 and lasts for 20 minutes. When the current time is 07:18 and Task A has not yet completed, Task A is active. The processor identifies Task A as the target task and automatically places it in the predetermined display position or focus position on the task interface. When no active task exists, the processor can select the task that has not yet started and whose start time is closest to the current time as the target task.
[0044] When the time windows of multiple task instances overlap, the processor may prioritize the active task with the earliest end time; if the end times are the same, the task with the earlier start time will be selected; if they are still the same, the processor may determine the priority based on preset priority, task identifier, or user-configured rules. The above rules can be replaced with other deterministic selection rules.
[0045] Example 4: Permission Attribute-Driven Task State Machine
[0046] like Figure 5 and Figure 6 As shown, the time status of a task instance can include SCHEDULED, ACTIVE, and EXPIRED, while the task processing status can include unprocessed, PENDING_AUTH, COMPLETED, MISSED, and REVERSED. The time status describes the task's time window, and the task processing status describes the result of the user's action. For tasks valid on the current date, whether or not to accept completed, incomplete, or canceled input is not necessarily limited by whether the task is currently in a SCHEDULED, ACTIVE, or EXPIRED time status.
[0047] Users can enter a completion operation for valid tasks of the current day at any time within the current date. The processor reads the permission attributes from the task record; when the permission attribute indicates that no high-level confirmation is required, the processor directly executes the completion event; when the permission attribute indicates that confirmation is required, the processor enters the PENDING_AUTH state and displays the local verification interface in the user interaction module 140. The verification interface may require input of a PIN, password, or other authentication information. Upon successful verification, a completion event is executed; if verification fails, is canceled, or times out, the task processing status before input is returned without generating new points transactions. For tasks of the current day that have been completed or marked as incomplete, users can also enter an undo operation to restore the task to an unprocessed state; tasks with permission attributes can undergo the same local verification before undoing.
[0048] In other implementations, the same or different permission attributes can be set for operations such as task incompleteness, reward redemption, and manual point adjustment, so that different events can share the local permission control mechanism.
[0049] Example 5: Unified Integral Transactions and Data Consistency
[0050] like Figure 7 As shown, the local storage 120 stores a unified points transaction record 230. The points transaction record 230 may include a transaction identifier, source type, event type, points change amount, points balance before the transaction, points balance after the transaction, timestamp, authentication status, and commit status. Committed records may remain in the first local storage area, or be migrated to the second local storage area when date, capacity, power consumption, or maintenance conditions are met; the logical data structure and reference numerals of the points transaction record 230 are maintained before and after migration.
[0051] When a task completion event meets the submission conditions, the processor generates a positive points transaction; when a task incomplete event meets the submission conditions, the processor generates a negative points transaction; when a reward redemption is successful, a reward redemption transaction is generated; when a high-privilege user performs a manual points adjustment, a manual adjustment transaction is generated; when a completed or incomplete status is revoked, the processor deletes the original points transaction record, invalidates it, or generates a revocation transaction in the opposite direction to the original points change. The above transactions use a unified data structure to maintain a traceable relationship between the current points balance, points transaction records 230, and the source events. The processor can respond to points record query input, filter points transaction records 230 according to time range, event type, source identifier, transaction status, or a combination thereof, and control the user interaction module 140 to present the filtering results in the form of a detailed list, statistical charts, or a combination of both, as well as the cumulative points, net points change, event count, time trend, or category distribution based on the filtering results. Statistical charts can be bar charts, line charts, pie charts, donut charts, or other graphics that can express statistical relationships; the specific presentation format is not limited.
[0052] In one embodiment, a task completion transaction-related update is performed as follows: the task instance's processing state changes to COMPLETED, the points balance is updated from BalanceBefore to BalanceAfter, the points earned and completed for the day are updated accordingly, and the points transaction record 230 is written to local storage. When the user subsequently cancels the completion, the processor restores the task processing state to unprocessed, deletes or invalidates the corresponding points transaction record 230, and subtracts the positive points change of that record from the current points value; if the original record had negative points, the corresponding points are added back to the current points value upon cancellation. The processor only confirms the above-mentioned related updates as valid after predetermined transaction commit conditions are met. Implementation can employ write-ahead logs, dual-zone records, commit flags, sequence numbers, checksums, or other consistency mechanisms suitable for non-volatile storage.
[0053] Example 6: Repeated Input Suppression and Abnormal Recovery
[0054] like Figure 8 As shown, the processor can establish event uniqueness relationships using task instance identifier, event type, and transaction identifier. When a completed task transaction already exists for the same task instance, repeated completion inputs do not generate a second equivalent completion transaction; when the user explicitly inputs a new processing status or cancels an input, the processor recognizes the input as a replacement or cancellation of the original integration transaction record 230, rather than a repeated input.
[0055] When the device loses power or resets during transaction processing, the processor reads the commit status of the integral transaction record 230 after restarting; for transactions that have been fully committed, the results are retained; for transactions that have not been fully committed, rollback, replay, or recalculation are performed to restore the task status, integral balance, and integral transaction record 230 to a consistent state.
[0056] Example 7: Reward Redemption and Manual Adjustment
[0057] The local storage 120 can also store reward item records 240. Each reward item record may include a reward item identifier, name, icon identifier, and required points. The icon identifier may point to a preset set of redemption icons stored in the local storage. Users can select icons when creating or editing reward items. The user interaction module 140 displays the selected redemption icon in the redemption list, associating it with the reward item name and required points. When a user selects a reward item and initiates a redemption, the processor compares the current points balance with the required points. If the conditions are met, the processor executes either a direct path or a local verification path based on the permission attributes of the operation. Upon successful execution, a reward redemption transaction with negative points is generated, and the transaction is written to the points transaction record 230 of the redemption type.
[0058] Users with high privileges can also input the reason for adjustment and the amount of change in points through the manual points adjustment interface. The processor writes the change into a manual adjustment transaction with the same structure as other points events, so that the points balance can be reconstructed or verified from a set of valid transactions.
[0059] Example 8: Low-power wake-up
[0060] like Figure 9 As shown, the processor calculates the next state transition time Tnext based on the task instance of the current date. Tnext can be the earliest of the following: the most recent start time of a task that has not yet started, the most recent end time of a currently active task, the expiration time of a running timer, or other event times that require updating the task interface.
[0061] When there are no ongoing interactive, timing, or storage operations, the processor can enter a low-power state via the power management module 150 and configure the real-time clock 130 to generate a wake-up signal in Tnext. The device can also be woken up in advance by touch, button press, charging status, or other asynchronous events. After waking up, the processor rereads the current time, recalculates only task instances that may cross state boundaries, and updates the target task.
[0062] Example 9: Partial Display Refresh
[0063] like Figure 10 As shown, when the user interaction module 140 includes a display module, the processor can save or generate the interface state before and after the update, compare the state differences of the task line, points area, time area, and daily statistics area, determine the content to be updated or the changed display area, and perform at least one of full-screen update, area-by-area update, or differential update according to the update method supported by the display module. In an implementation that supports area-by-area updates, for example, when a reflective monochrome display module is used, the processor can send update data only to the changed display area.
[0064] For example, when the completion of a task causes changes to its status icon, points balance, and the number of tasks completed that day, for display modules that support area-based updates, only the corresponding task row, points display area, and daily statistics area can be updated, without updating the unchanged task row. For display modules that do not support area-based updates or are suitable for full-screen updates, full-screen update content can be generated based on the determined differences in interface status. The above method can reduce unnecessary display data transfer and processor activity time according to the update characteristics of different display modules, and can work in conjunction with the Tnext wake-up mechanism to reduce overall power consumption.
[0065] Example 10: Sample Execution Flow
[0066] In one example, locally stored tasks include: a "wake up" task that starts at 07:00, lasts for 10 minutes, and repeats daily; a "brush teeth" task that starts at 07:15, lasts for 10 minutes, and repeats daily; a "breakfast" task that starts at 07:30, lasts for 20 minutes, and repeats daily; and a "go to school" task that starts at 08:00, lasts for several hours, and repeats on weekdays. The processor automatically determines "brush teeth" as the target task after reading the RTC at 07:18.
[0067] If the permission attribute of the "brushing teeth" task indicates that no confirmation is required, the processor will directly generate the task completion transaction and update the points after the user clicks the complete control; if the permission attribute of the "tidying the room" task indicates that confirmation is required, the user will first enter local PIN verification after clicking the complete control, and the completion transaction will only be generated after successful verification.
[0068] For the same task with both reward and deduction points, either a TASK_COMPLETE event or a TASK_MISSED event can be generated using different event modes. The former uses the reward points to form a positive point transaction, while the latter uses the deduction points to form a negative point transaction. For tasks valid for the current date, the above event inputs can be received at any time of the day without being restricted by the task's time window. Users can cancel existing completed or incomplete states, and the processor will reverse the corresponding point changes and restore the task to an unprocessed state. Users can also continue to submit new completed or incomplete inputs. Specific input methods can include different buttons, long presses, double-clicks, selections in management mode, or other interactive methods that can distinguish event types.
[0069] Other variations
[0070] This invention is not limited to scenarios involving children, families, or household chores; it can also be used for non-medical tasks other than personal habits, learning plans, and rehabilitation training, as well as for equipment maintenance, training execution, and other scenarios requiring timed tasks and quantitative status recording on a separate terminal. The points status can be represented as a score, credit value, credit limit, or other locally quantified status that can be increased or decreased by events.
[0071] Task records, task instances, and points transactions can be implemented using databases, key-value stores, structured files, circular logs, or other local data structures; local authentication can also use PINs, passwords, near-field credentials, or biometric authentication. Any core task processing that does not require external network returns of task processing results falls under the offline processing method described in this invention.
[0072] The above description is only a preferred embodiment of the present invention. Equivalent substitutions, combinations or modifications made by those skilled in the art without departing from the concept of the present invention should all fall within the protection scope defined by the claims.
Claims
1. An offline interactive task points management device, comprising a processor, local memory, a real-time clock, and a user interaction module, characterized in that: The local memory is used to store multiple task records and points transaction records. Each task record includes at least a task time parameter, a points parameter, and a permission attribute. The processor is configured to determine the real-time task status corresponding to the multiple task records based on the current time provided by the real-time clock and the task time parameter, and to determine the target task from the multiple task records based on the real-time task status. The user interaction module is used to present a task interface that includes at least the target task and to receive status change input for the target task. The processor is also configured to read the permission attributes of the target task in response to the status change input, select a first status processing path that does not require local authentication or a second status processing path that includes a local authentication process based on the permission attributes, and generate an points change event and a corresponding points transaction record based on the points parameters after the status change conditions of the corresponding status processing path are met. The task status of the target task, the points status stored in the local memory, and the points transaction record are updated in association through a single transaction. The determination of the real-time task status, the local authentication, and the single transaction can be completed locally by the device without obtaining the task processing result through an external network.
2. The apparatus according to claim 1, characterized in that, The task time parameters include start time, duration, and repetition rule. The repetition rule includes at least one of daily, weekday, weekend, weekly, monthly, and one-time. The processor determines the task instance corresponding to the current date based on the current date and the repetition rule, and determines the start time and end time of the task instance based on the start time and the duration to form a task time window. By comparing the current time with the task time window, the task instance is determined to be in an unstarted state, an active state, a timeout state, a completed state, or an incomplete state.
3. The apparatus according to claim 2, characterized in that, When at least one incomplete task instance is active, the processor determines the target task from the active task instances. When multiple incomplete task instances are active at the same time, the processor determines the target task according to at least one of the following rules: earliest end time, earliest start time, and preset priority. When there are no active task instances, the processor determines the task instance with the closest start time to the current time from the incomplete and unstarted task instances as the target task.
4. The apparatus according to claim 1, characterized in that, The user interaction module includes a display module for presenting the task interface and an input unit for receiving the status change input. The input unit is integrated with or separate from the display module. The task record also includes a task icon identifier selected from a preset task icon set. The display module associates the task icon identifier with the task name, time, or status information in the to-do list or target task area. The processor controls the display module to automatically position the target task at a predetermined display position, a predetermined visible area, or a focus position. It compares the interface state before and after the task interface update to determine the content to be updated or the changed display area. Based on the update method supported by the display module, it performs at least one of full-screen update, regional update, or differential update.
5. The apparatus according to claim 1, characterized in that, When the permission attribute is a first value, the processor enters the first state processing path and directly verifies the task state change condition after receiving the state change input; when the permission attribute is a second value, the processor enters a waiting verification state and outputs an identity verification interface, matching the received password, personal identification code or authentication data with the authentication data in the local memory. If the verification is successful, the processor enters a pending submission state; if the verification fails, the processor returns to the task state before the state change input.
6. The apparatus according to claim 1, characterized in that, The points change event includes at least a task completion event and a task incomplete event; the same task record includes a reward points value and a deducted points value. The processor selects one of the reward points value and the deducted points value as the points change amount of the points change event according to the event mode corresponding to the state change input. For a task instance valid for the current date, the processor is configured to receive a completion input, an incomplete input, or a cancellation input within the current date, causing the task processing status to change between incomplete, completed, and incomplete. When changing to a completed or incomplete state, the corresponding points transaction record is added or replaced synchronously and the current points value is updated. When canceling a completed or incomplete state, the corresponding points transaction record is deleted, the corresponding points transaction record is set to invalid, or a reverse points transaction is generated, and the current points value is updated in reverse according to the points change amount of the canceled record.
7. The apparatus according to claim 1, characterized in that, Each points transaction record includes at least four of the following: transaction identifier, source identifier, event type, points change, points value before the transaction, points value after the transaction, and timestamp. When a transaction is not completed, the processor prevents the task status, points status, and partial update results in the points transaction record from being confirmed as valid. It also determines whether the points change event corresponding to the same task instance has been committed based on at least one of the transaction identifier and the source identifier, thus preventing duplicate points changes. The processor is further configured to respond to points record query input, query the points transaction record according to at least one of the time range, event type, source identifier, and transaction status, and control the user interaction module to present the query results or statistical information based on the query results as a list, statistical chart, or a combination thereof.
8. The apparatus according to claim 7, characterized in that, The processor is further configured to perform at least one of the following operations: responding to a reward redemption input, generating a reward redemption points transaction when the current points status meets the required points conditions corresponding to the reward item record, deducting the points balance and recording the redemption history; generating a manual points adjustment transaction, and recording the manual points adjustment transaction using the same points transaction data structure as the task completion event, task incomplete event, and reward redemption event; wherein, the reward item record also includes a redemption icon identifier selected from a preset redemption icon set, and the user interaction module associates the redemption icon corresponding to the redemption icon identifier with the reward item name and required points in the redemption list.
9. The apparatus according to claim 2, characterized in that, The processor determines the next state transition time based on at least one of the next start time of the currently incomplete task instance, the next end time of the active task instance, and the timer expiration time, and configures the wake-up time of the device according to the next state transition time; when there is no user interaction or timed operation that needs to be continuously processed, the processor controls the device to enter a low-power state, and the real-time clock triggers the wake-up at the wake-up time, and after the wake-up, the real-time task state of at least one task instance is re-determined.
10. A control method for an offline interactive task points management device, applied to a terminal including a processor, local memory, a real-time clock, and a user interaction module, characterized in that, include: Multiple task records and points transaction records are stored in the local memory. Each task record includes at least task time parameters, points parameters, and permission attributes. The real-time task status corresponding to the multiple task records is determined based on the current time provided by the real-time clock and the task time parameter, and the target task is determined based on the real-time task status. The user interaction module presents the target task and receives status change input for the target task; in response to the status change input, it reads the permission attributes of the target task and selects a first status processing path that does not require local authentication or a second status processing path that requires local authentication based on the permission attributes; after the status change conditions of the corresponding status processing path are met, it generates a points change event and a corresponding points transaction record based on the points parameters, and updates the task status, local points status, and points transaction record of the target task through a single transaction; wherein the above real-time task status determination, local authentication, and single transaction processing are all completed without the need for an external network to provide task processing results.
11. The method according to claim 10, characterized in that, Also includes: Based on the repetition rules and the current date, a task instance corresponding to the current date is generated. The task time window is determined based on the start time and duration of the task instance, and the real-time task status is determined by comparing the current time with the task time window. Within the current date, complete, incomplete, or cancel inputs are received for the valid task instance of the day, causing the task processing status to change between unprocessed, completed, and incomplete. Corresponding points transaction records are added, replaced, deleted, or invalidated synchronously, and the current points value is updated in a positive or negative direction. Duplicate points changes for the same task instance are prevented based on at least one of the transaction identifier and the source identifier. The next state transition time is determined based on at least one of the next start time of the incomplete task instance, the next end time of the active task instance, and the timer expiration time, and the next wake-up time of the terminal is configured based on the next state transition time.
12. A non-transitory computer-readable storage medium having a computer program stored thereon, wherein when executed by a processor, the computer program causes the processor to perform the control method of claim 10 or 11.
