Interface processing method and electronic atomization device
By configuring a request processing unit and an application bar component in the electronic atomization device, and adopting an event-driven approach to unify the management of system status, the problems of logical conflicts and untimely status updates in interactive pages are solved, realizing unified management and real-time updates of interface status, and improving maintainability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-20
- Publication Date
- 2026-04-07
AI Technical Summary
The interactive pages of electronic atomizing devices suffer from problems such as fragmented page event management, potential logical conflicts, untimely device status updates, and overly coupled UI, which hinders maintenance.
The electronic atomization device is equipped with a request processing unit and an application bar component. The system status is managed in a unified manner, and the interface icons are updated in an event-driven manner to achieve unified management and real-time updates, avoid logical conflicts, and decouple the UI.
It enables unified management and real-time updates of the interface status of electronic atomization devices, avoiding logical conflicts and improving maintainability and the real-time status of equipment.
Smart Images

Figure CN121807196A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of interface display technology, and in particular to an interface processing method and an electronic atomization device. Background Technology
[0002] When electronic atomizers were first introduced, they typically used an LED (Light Emitting Diode) indicator to show the device's status, such as using different colors to represent battery level or status. As electronic atomizers became more complex, simple indicator lights were no longer sufficient. Therefore, interactive pages were added to electronic atomizers to intuitively display the device's status and functions.
[0003] However, the interactive pages embedded in electronic atomization devices have problems during use, such as fragmented page event management that is prone to logical conflicts, untimely device status updates, and excessive coupling of the UI (User Interface) which makes maintenance difficult. Summary of the Invention
[0004] This application provides an interface processing method, an electronic atomizing device, an electronic device, and a computer-readable storage medium to solve or partially solve problems such as scattered page event management and easy logical conflicts in the interactive page of the electronic atomizing device, untimely device status updates, and excessive UI coupling that is not conducive to maintenance.
[0005] This application discloses an interface processing method applied to the display component of an electronic atomizing device. The display component is used to provide an interactive page. The electronic atomizing device is equipped with a request processing unit, and the interactive page has an application bar component. The application bar component includes at least two interface icons, and each interface icon corresponds to at least one system state. The method includes: The request processing unit responds to the system request and obtains the system status corresponding to the system request; The request processing unit calls the application bar component to update the interface icon based on the system request and the system status.
[0006] In some feasible implementations, the interface icon includes at least a status icon, the system request includes a status update request, and the system status includes status update data corresponding to the status update request. The request processing unit updates the interface icon by invoking the application bar component based on the system request and the system status, including: If the system request is the status update request, then the application bar component is invoked to update the status icon based on the status update data.
[0007] In some feasible implementations, the status update request includes at least one of the following: battery level change request, fuel level change request, and temperature change request; the status update data includes at least one of the following: battery level update data, fuel level update data, and temperature update data; and the status icon includes at least one of the following: battery level status icon, fuel level status icon, and temperature status icon.
[0008] In some feasible implementations, updating the status icon based on the status update data includes: Update the battery status icon according to the battery update data; And / or, update the oil level status icon based on the oil level update data; And / or, update the temperature status icon based on the temperature update data.
[0009] In some feasible implementations, the electronic atomizing device is further configured with at least one of a power management component and an oil quantity management component, and the method further includes: The current battery information of the electronic atomizing device is obtained through the power management component; If the current battery level information changes relative to the corresponding historical battery level information, battery level update data corresponding to the current battery level information is generated, and the battery level change request is triggered. And / or, The current fuel level information of the electronic atomizing device is obtained through the fuel management component. If the current fuel quantity information changes relative to the corresponding historical fuel quantity information, then fuel quantity update data corresponding to the current fuel quantity information is generated, and the fuel quantity change request is triggered.
[0010] In some feasible implementations, the interface icons include interactive icons, the system requests include user interaction events, and the method further includes: In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon.
[0011] In some feasible implementations, the interactive icon includes at least a communication status icon, and the user interaction event includes at least a communication mode switching request; In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon, including: In response to the communication mode switching request, the application bar component is invoked to update the communication status icon.
[0012] In some feasible implementations, the interactive icon includes at least a suction mode icon, and the user interaction event includes at least a suction mode switching request; In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon, including: In response to the suction mode switching request, the application bar component is invoked to update the suction mode icon.
[0013] In some feasible implementations, the interactive page includes a suction control page; The method further includes: In response to a suction trigger command, the suction control page is displayed on the interactive page; In response to the mode switching command for the inhalation control page, the inhalation mode of the electronic atomizing device is switched, and the inhalation mode switching request is triggered.
[0014] This application also discloses an electronic atomizing device, which provides an interactive page through its display component; wherein, the electronic atomizing device is equipped with a request processing unit, the interactive page has an application bar component, the application bar component includes a plurality of interface icons, each interface icon corresponds to at least one system state, and each system state is uniformly managed by the request processing unit; wherein: The request processing unit is used to respond to system requests by calling the application bar component to update the interface icon.
[0015] In some feasible implementations, the request processing unit is specifically used for: In response to a system request, obtain the system status corresponding to the system request; Based on the system request and the system status, the application bar component is invoked to update the interface icon.
[0016] In some feasible implementations, the interface icon includes at least a status icon, the system request includes a status update request, the system status includes status update data corresponding to the status update request, and the application bar component is specifically used for: If the system request is the status update request, then the status icon is updated based on the status update data.
[0017] In some feasible implementations, the status update request includes at least one of the following: battery level change request, fuel level change request, and temperature change request; the status update data includes at least one of the following: battery level update data, fuel level update data, and temperature update data; and the status icon includes at least one of the following: battery level status icon, fuel level status icon, and temperature status icon.
[0018] In some feasible implementations, the application bar component is specifically used for: Update the battery status icon according to the battery update data; And / or, update the oil level status icon based on the oil level update data; And / or, update the temperature status icon based on the temperature update data.
[0019] In some feasible implementations, the electronic atomizing device is further configured with at least one of a power management component and an oil quantity management component; wherein: The power management component is used to obtain the current power information of the electronic atomizing device at the current moment; if the current power information changes relative to the historical power information corresponding to a historical moment, power update data corresponding to the current power information is generated, and the power change request is triggered. The oil level management component is used to obtain the current oil level information of the electronic atomizing device at the current moment; if the current oil level information changes relative to the historical oil level information corresponding to the historical moment, oil level update data corresponding to the current oil level information is generated, and the oil level change request is triggered.
[0020] In some feasible implementations, the interface icons include interactive icons, the system requests include user interaction events, and the application bar component is specifically used for: In response to the user interaction event, update the interaction icon.
[0021] In some feasible implementations, the interactive icon includes at least a communication status icon, the user interaction event includes at least a communication mode switching request, and the application bar component is specifically used for: In response to the communication mode switching request, update the communication status icon.
[0022] In some feasible implementations, the interactive page includes a Bluetooth communication page, and the electronic atomization device further includes: A Bluetooth page display module is used to display the Bluetooth communication page in response to a communication trigger command for the electronic atomizing device; The Bluetooth switching module is used to switch the communication connection of the electronic atomizing device in response to the communication switching command for the Bluetooth communication page, and to trigger the communication mode switching request.
[0023] In some feasible implementations, the interactive icon includes at least a suction mode icon, the user interaction event includes at least a suction mode switching request, and the application bar component is further used for: In response to the suction mode switching request, update the suction mode icon.
[0024] In some feasible implementations, the interactive page includes a suction control page, and the device further includes: The control page display module is used to display the inhalation control page in response to the inhalation trigger command of the electronic atomizing device; The working mode switching module is used to switch the inhalation mode of the electronic atomizing device in response to the mode switching command of the inhalation control page, and to trigger the inhalation mode switching request.
[0025] In some feasible implementations, the interface icon includes a notification icon, the system request includes a message notification event, and the application bar component is specifically used for: In response to the message notification event, update the notification icon.
[0026] In some feasible implementations, the application bar component also includes interactive controls, and the device further includes: The page response module is used to respond to the trigger operation of the interactive control and perform page operations on the interactive page.
[0027] This application also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is used to store computer programs; When the processor executes a program stored in the memory, it implements the method described in the embodiments of this application.
[0028] This application also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this application.
[0029] The embodiments of this application have the following advantages: In this embodiment, an interactive page is embedded in the electronic atomizing device, allowing users to perform corresponding interactive operations. The electronic atomizing device can also be configured with a request processing unit and an application bar component embedded in the interactive page, enabling reuse between the interactive page and the application bar component and ensuring that the application bar component can be displayed on any interactive page. The application bar component includes several interface icons, each corresponding to at least one system state. Each system state is registered with the request processing unit, allowing the request processing unit to achieve unified management of all system states. During the use of the electronic atomizing device, the request processing unit can respond to system requests and call the application bar component to update the interface icons.
[0030] By constructing an application bar component and uniformly registering the system states involved in the application bar component to the request processing unit, unified management can be achieved, logical conflicts between different events can be avoided, and the event-driven approach can effectively ensure the real-time update of device status. Furthermore, by embedding the application bar component in the interactive page, there is no need to write additional drawing and response logic, thus achieving UI decoupling and improving maintainability. Attached Figure Description
[0031] Figure 1 This is a flowchart of the steps of an interface processing method provided in the embodiments of this application; Figure 2 This is a schematic diagram of the system architecture provided in the embodiments of this application; Figure 3 This is a schematic diagram of oil quantity sampling fusion provided in the embodiments of this application; Figure 4 This is a schematic diagram of power sampling fusion provided in the embodiments of this application; Figure 5 This is a schematic diagram of the interactive page provided in the embodiments of this application; Figure 6 This is a schematic diagram illustrating the relationship between component nesting and reuse provided in the embodiments of this application; Figure 7 This is a schematic diagram of the centralized event processing provided in the embodiments of this application. Detailed Implementation
[0032] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0033] As an example, electronic atomizing devices typically need to display real-time device status information, such as battery level and e-liquid level, while also supporting corresponding user interface interactions. This information is usually distributed across multiple UI pages, and the underlying implementation logic of these UI pages highly overlaps, which can easily lead to some or all of the following problems: 1. Each UI page needs to be registered independently and handle system-level events, resulting in severe code redundancy; 2. Inconsistent or conflicting event handling logic across different UI pages; 3. Device status updates need to be linked to the refresh process of each UI page, and there is no unified update mechanism; 4. The methods for detecting equipment parameters are relatively primitive, lacking automatic calibration or dynamic detection mechanisms; 5. The UI is highly coupled, which is not conducive to logical layering and module reuse.
[0034] Reference Figure 1 This document illustrates a flowchart of the steps of an interface processing method provided in an embodiment of this application. To address at least one of the aforementioned problems, this application provides an interactive page through the display component of an electronic atomizing device. Furthermore, the electronic atomizing device is equipped with a request processing unit, and the interactive page includes an application bar component. The application bar component includes at least two interface icons, each corresponding to at least one system state. Each system state is uniformly managed by the request processing unit, and may specifically include the following steps: Step 101: The request processing unit responds to the system request and obtains the system status corresponding to the system request; Step 102: The request processing unit calls the application bar component to update the interface icon based on the system request and the system status.
[0035] In this embodiment, the electronic atomizing device may embed a corresponding display component, providing an interactive page for user interaction. This interactive page can display the device status of the electronic atomizing device and support corresponding interface interactions. Users can view the real-time battery level, e-liquid level, vaping mode, Bluetooth status, and notification messages displayed on the interactive page. They can also input corresponding interactive operations to adjust the status of the electronic atomizing device. This application does not impose any limitations on these aspects.
[0036] The electronic atomization device can be configured with a request processing unit and an application bar component embedded in each interactive page. The request processing unit can uniformly manage system status update requests (such as page back events, status update requests, external notification events, interactive events, etc.), including unified registration and trigger detection. The application bar component can be a fixed target area of the interactive page. It can provide several interface icons, which can be used to display the device status of the electronic atomization device in real time or to provide corresponding interface interaction functions. Each interface icon in the application bar component can be associated with at least one system status, and each system status is registered in the request processing unit. By registering unified system statuses, status updates and interface refreshes are automatically completed under the drive of the request processing unit and application bar components, forming an "event-driven pull and view-cohesive update" interface processing mechanism. This achieves unified management, avoids logical conflicts between different events, effectively ensures the real-time nature of device status updates, and, by embedding the application bar component in the interactive page, eliminates the need to write additional drawing and response logic, achieving UI decoupling and improving maintainability.
[0037] Optionally, the application bar component can be embedded in any position of the interactive interface according to the user's needs. For example, the application bar component can be displayed as a top bar component (i.e., displayed in the top area of the interactive interface), or as a bottom bar component (i.e., displayed in the bottom area of the interactive interface), or as a sidebar component (i.e., displayed in the left or right area of the interactive interface, etc.). This application does not limit this.
[0038] In this embodiment, after embedding the application bar component into the different interactive interfaces of the electronic atomization device and registering the various system states associated with the application bar component to the request processing unit, the request processing unit can detect the system states involved in the operation of the electronic atomization device. Based on the detected system states, it can trigger corresponding system requests and call the application bar component to update the corresponding interface icons in real time. By constructing the application bar component and uniformly registering the system states involved in the application bar component to the request processing unit, unified management can be achieved, logical conflicts between different events can be avoided, and the event-driven approach effectively ensures the real-time update of the device status. Furthermore, by embedding the application bar component in the interactive page, there is no need to write additional drawing and response logic, achieving UI decoupling and improving maintainability.
[0039] The system status can include events such as status updates, user interaction events, and message notification events. Based on different events, the electronic atomization device can generate corresponding system requests, such as status update requests, interaction requests, notification requests, and mode switching requests, so that the application bar component can perform different interface processing operations according to the system status and / or the request type corresponding to the triggered system request.
[0040] In some feasible implementations, the electronic atomizing device can respond to system requests through a request processing unit, obtain the system status corresponding to the system request, and then call the application bar component to update the interface icon according to the system request and the system status. Thus, when the corresponding system status is triggered, the unified management of system status and real-time updating of status data in the embedded UI are realized based on the interface processing mechanism of "event pull-driven and view cohesive update".
[0041] The interface icons can include status icons, which can be used to display the device status of the electronic atomizing device in real time, such as the battery level, e-liquid level, and temperature. For such status update requests related to device status, the application bar component can obtain the status update data corresponding to the status update request, and then update the status icon based on the status update data. By embedding the application bar component into each interactive interface, it ensures that the status data can be accurately updated and displayed in a timely manner on any page, and also ensures UI consistency and maintenance efficiency.
[0042] Optionally, the status update request includes at least one of the following: battery level change request, fuel level change request, and temperature change request; the status update data includes at least one of the following: battery level update data, fuel level update data, and temperature update data; and the status icon includes at least one of the following: battery level status icon, fuel level status icon, and temperature status icon. During the real-time update of the status icons, the application bar component can update the battery level status icon based on the battery level update data; and / or, update the fuel level status icon based on the fuel level update data; and / or, update the temperature status icon based on the temperature update data, etc.
[0043] In addition, electronic atomizing devices can also be equipped with corresponding power management components. These components can acquire relevant power information, preprocess the power information to improve data stability, notify the application bar component to refresh the power status icon through an event mechanism, and trigger corresponding calibration logic based on device status, etc.
[0044] For example, during the process of updating the battery status icon, the current battery information of the electronic atomizing device can be obtained through the battery management component. If the current battery information changes relative to the historical battery information at a historical time, battery update data corresponding to the current battery information is generated, and a battery change request is triggered so that the application bar component can be notified to update the corresponding battery status icon in a timely manner.
[0045] Furthermore, the electronic atomizing device can also be equipped with a corresponding oil level management component. This component can acquire relevant oil level information, preprocess the oil level information to improve data stability, notify the application bar component to refresh the oil level status icon through an event mechanism, and trigger corresponding calibration logic based on device status, etc.
[0046] For example, during the process of updating the fuel level status icon, the fuel level management component can obtain the current fuel level information of the e-cigarette device at the current moment. If the current fuel level information changes relative to the historical fuel level information at a historical moment, fuel level update data corresponding to the current fuel level information is generated, and a fuel level change request is triggered. This fuel level change request is then used to notify the application bar component to update the corresponding fuel level status icon in a timely manner.
[0047] Furthermore, the update process for the temperature status icon can be referred to the description in the foregoing embodiments, and will not be repeated here.
[0048] It should be noted that the processing of system states such as battery level, fuel level, and temperature can integrate multiple sampling sources into the corresponding state management components (such as battery management components, fuel level management components, and temperature management components). Taking the battery management component as an example, it can integrate one or more sampling sources such as an ADC (Analog-to-Digital Converter), a capacitance sensor, and a fuel gauge. The sampled data can be processed using algorithms such as moving average or weighted fusion to improve data stability. For example, in a battery management component with an integrated fuel gauge, the remaining battery level of the electronic atomizer can be directly obtained through the fuel gauge. By setting a corresponding timed polling task in the underlying code, if the battery level changes, a corresponding battery level change request is triggered to update the battery level status icon in the application bar component. In a battery management component with an integrated ADC, the remaining battery level can be calculated by combining usage time or charging time. If the battery level changes, a corresponding battery level change request is triggered to update the battery level status icon in the application bar component. This application does not impose any restrictions on this.
[0049] The process of updating system statuses such as oil level and temperature can be referenced from the process of updating battery level, and will not be elaborated here. In addition, during the process of triggering calibration logic based on equipment status, after replacing the aerosol generation module, the oil level status icon can be calibrated to full oil level (i.e., 100%). Similarly, when fully charged, the battery level status icon can also be calibrated to full battery level (i.e., 100%), etc. This application does not impose any restrictions on this.
[0050] In some other feasible implementations, if the interface icons include interactive icons and the system requests include user interaction events, then when a user interaction event is triggered, the electronic atomizing device can call the application bar component to respond to the user interaction event and update the interactive icons.
[0051] The interactive icons include at least a communication status icon, and the user interaction events include at least a communication mode switching request. The application bar component can respond to the communication mode switching request and update the communication status icon. Thus, when the user inputs a corresponding interactive operation and triggers the corresponding user interaction event, the application bar component can update the displayed interactive icons in real time according to the interaction result corresponding to the interactive operation.
[0052] In some examples, the e-cigarette device may have Bluetooth communication capabilities. When the user enters a corresponding communication trigger command on the interactive page, the e-cigarette device can respond to the communication trigger command by displaying a Bluetooth communication page on the interactive page. Then, if the user enters a communication switching command, the e-cigarette device can respond to the communication switching command for the Bluetooth communication page by switching the communication connection of the e-cigarette device. Based on the interaction results during the communication switching process, a communication mode switching request can be triggered so that the application bar component can update the communication status icon in real time according to the communication mode switching request.
[0053] For example, when a user turns on Bluetooth on the Bluetooth communication page and selects the corresponding target device from the currently connectable terminal devices to establish a Bluetooth communication connection, a "Bluetooth connection event" can be triggered, and the application bar component can update the Bluetooth status icon to "connected status". Conversely, if the user turns off Bluetooth communication, a "Bluetooth off event" can be triggered, and the application bar component can update the Bluetooth status icon to "off status". Thus, based on the interface processing mechanism of "event-driven pull and view cohesive update", unified management of system status and real-time updating of status data in embedded UI are realized.
[0054] In addition, the interactive icon may also include a suction mode icon. If the user interaction event includes at least a suction mode switching request, the application bar component may respond to the suction mode switching request by calling the application bar component to update the suction mode icon.
[0055] In some examples, the e-cigarette device supports adjusting the vaping mode according to user needs. When the user enters a corresponding vaping trigger command on the interactive page, the e-cigarette device can respond to the vaping trigger command by displaying a vaping control page on the interactive page. Then, if the user enters a corresponding mode switching command, the e-cigarette device can respond to the mode switching command on the vaping control page by switching the vaping mode of the e-cigarette device. Based on the interaction results during the mode switching process, a vaping mode switching request is triggered so that the application bar component can update the vaping mode icon in real time according to the vaping mode switching request.
[0056] For example, the vaping mode can be divided into different vaping star levels. These vaping modes can be categorized based on devices, atomizing matrix, usage habits, etc. Different vaping star levels can correspond to different vaping modes. Based on the target vaping star level selected by the user on the vaping control page, the corresponding "vaping mode switching request" can be triggered. The application bar component can then dynamically update the vaping mode icon to the display style of the corresponding vaping star level. Thus, based on the interface processing mechanism of "event-driven pull and view cohesive update", unified management of system status and real-time updating of status data in the embedded UI are achieved.
[0057] In addition, the interface icons may also include notification icons. When the electronic atomizing device receives a notification message sent by an external device, the request processing unit can detect the corresponding message notification event and then notify the application bar component of the message notification event. The application bar component can respond to the message notification event by updating the notification icon, for example, by continuously flashing the notification icon and displaying the corresponding number of messages.
[0058] In addition, the application bar component may also include interactive controls, allowing users to input trigger actions for these controls. The application bar component then responds to these trigger actions by performing page operations on the interactive page. For example, interactive controls may include back controls, toggle controls, and information display controls. When a user triggers a back control, the currently displayed interactive page can be closed; when a user triggers a toggle control, the corresponding function can be turned on or off; when a user triggers an information display control, a corresponding notification message can be displayed, etc. This application does not impose any limitations on this.
[0059] It should be noted that the embodiments of this application include, but are not limited to, the examples described above. It is understood that those skilled in the art can make further settings according to actual needs under the guidance of the ideas in the embodiments of this application, and this application does not impose any restrictions on this.
[0060] In this embodiment, an interactive page is embedded in the electronic atomizing device, allowing users to perform corresponding interactive operations. The electronic atomizing device can also be configured with a request processing unit and an application bar component embedded in the interactive page, enabling reuse between the interactive page and the application bar component and ensuring that the application bar component can be displayed on any interactive page. The application bar component includes several interface icons, each corresponding to at least one system state. Each system state is registered with the request processing unit, allowing the request processing unit to achieve unified management of all system states. During the use of the electronic atomizing device, the request processing unit can respond to system requests and call the application bar component to update the interface icons.
[0061] By constructing an application bar component and uniformly registering the system states involved in the application bar component to the request processing unit, unified management can be achieved, logical conflicts between different events can be avoided, and the event-driven approach can effectively ensure the real-time update of device status. Furthermore, by embedding the application bar component in the interactive page, there is no need to write additional drawing and response logic, thus achieving UI decoupling and improving maintainability.
[0062] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the following examples are provided for illustrative purposes: As some examples, see Figure 2 This diagram illustrates the system architecture provided in this embodiment. The electronic atomizing device can be configured with an event central scheduling module, an ANCS / system notification distributor, a fuel level information acquisition and fusion module, a battery level detection and threshold warning module, a Bluetooth status display module, a working mode display module, a top bar display component, and a business page registration and management module. The event central scheduling module can be used to register system status update requests (such as battery level decrease, fuel level change, received notifications, etc.) to a unified event center, and execute the following process when an event is triggered: Automatically broadcast notifications to the top bar component; Distribute data to various functional modules (such as fuel level calibration, low battery alarm, etc.). It supports dynamic page registration or cancellation of listening, and is adapted to low-resource environments.
[0063] For modules such as the oil quantity information acquisition and fusion module and the power detection and threshold warning module, the oil quantity information acquisition and fusion module can integrate multiple sampling sources (such as ADC, capacitance sensor, metering pump feedback, etc.) and use moving average or weighted fusion algorithms to improve data stability. At the same time, it can notify the top bar display component to refresh the display control through an event mechanism, and trigger calibration logic according to the device status (such as triggering full capacity update after reloading). Similarly, the power detection and threshold warning module can also support multi-source fusion of internal ADC sampling and charging controller feedback, and has low power flashing reminder logic, etc. This application does not impose any restrictions on this.
[0064] For example, refer to Figure 3 This diagram illustrates the oil quantity sampling and fusion method provided in this embodiment. The oil quantity information acquisition and fusion module can acquire relevant oil quantity data through capacitive sensors, ADC voltage, and sensorless oil quantity estimation. The oil quantity data fusion engine performs operations such as moving average, weight calculation, and state de-jittering to output oil quantity update data such as "current oil quantity percentage," so that the corresponding oil quantity status icon can be updated in the top bar display component. Similarly, referring to... Figure 4 The power detection and threshold warning module can obtain corresponding power data through sampling methods such as battery voltage, charging IC status feedback, and historical power fitting models. It then uses a power data fusion engine to perform boundary correction on voltage and IC status, and combines historical models to predict the rate of decline, outputting the "current power percentage" so that the top bar display component can update the corresponding power status icon.
[0065] The top bar display component can serve as a modular, reusable structure, and it can respond logically under a unified event mechanism. Based on its independence and nestability, the top bar display component can be embedded into corresponding interactive pages according to actual needs. This allows for automatic status updates and interface refreshes driven by a centralized event scheduling module, achieved by registering unified system states (such as battery changes, fuel level updates, Bluetooth connection status changes, and ANCS (Apple Notification Center Service) notification arrivals). This forms an "event-driven pull + view-cohesive update" mechanism. For example, refer to... Figure 5 The diagram shows an interactive page provided in the embodiment of this application. The top bar display component 510 can display a corresponding battery icon 5101 (including icon and value, etc.), fuel level icon 5102 (including icon and value, etc.), and suction mode 5103, etc. In addition, it can also display Bluetooth status icon, notification icon, etc. (not shown in the figure).
[0066] It should be noted that for the top bar display component, the corresponding interactive pages do not need to understand the internal structure and update logic of the top bar display component. By embedding the top bar display component into the corresponding interactive page, and in conjunction with the centralized time scheduling module, a complete unified state awareness-logic judgment-component automatic response chain is formed, achieving UI decoupling. Furthermore, all state display logic is uniformly encapsulated in the top bar display component, enabling centralized maintenance and management. At the same time, for any new state items that need to be added, it can be done by registering the corresponding event and adding display processing code, which greatly improves extensibility. Moreover, all interactive pages can obtain the complete top bar functionality by nesting the top bar display component, without the need to write additional drawing and response logic.
[0067] For example, refer to Figure 6 This illustration shows a schematic diagram of the component nesting and reuse relationship provided in the embodiments of this application. For the top bar display component, it can include at least a back button, fuel level icon and value, battery level icon and value, Bluetooth status icon, working mode icon, message icon, and other extended icons. Correspondingly, the top bar display component can be embedded in a theme selection page, a suction control page, and a Bluetooth connection page. In the theme selection page, a corresponding theme preview can be displayed, and theme selection can be provided. Based on the user's theme selection, the theme display of the top bar display component can be adjusted. In the suction control page, a corresponding suction star rating can be displayed, and star rating selection can be provided. Based on the user's suction star rating selection, the display style of the working mode icon in the top bar display component can be adjusted. In the Bluetooth connection page, a Bluetooth switch function and the device name of paired devices can be provided. Based on the communication adjustment operation input by the user, the display style of the Bluetooth status icon in the top bar display component can be adjusted.
[0068] In addition, refer to Figure 7 This document illustrates a flowchart of the centralized event processing provided in this embodiment. When a system status is received, the centralized event scheduling module can take over the corresponding system status and determine the event type of the system status. If it is a battery event, the top bar display component is notified to update the battery icon and value; if it is a fuel level event, the top bar display component is notified to update the fuel level icon and value; if it is a Bluetooth status change event, the top bar display component is notified to update the Bluetooth icon; if it is a mode change event, the top bar display component is notified to update the mode icon; if it is an ANCS message notification, the top bar display component is notified to update the pop-up ANCS message notification; if it is other extended events, the top bar display component interface is called to update the UI, etc., thereby realizing an interface processing mechanism based on "event-driven pull and view cohesive update", achieving unified management of system status and real-time update of status data in the embedded UI.
[0069] In the above process, by constructing an application bar component and uniformly registering the system states involved in the application bar component to the request processing unit, unified management can be achieved, logical conflicts between different events can be avoided, and the event-driven approach can effectively ensure the real-time update of device status. Furthermore, by embedding the application bar component in the interactive page, there is no need to write additional drawing and response logic, thus achieving UI decoupling and improving maintainability.
[0070] This application also discloses an electronic atomizing device, which provides an interactive page through its display component; wherein, the electronic atomizing device is equipped with a request processing unit, the interactive page has an application bar component, the application bar component includes a plurality of interface icons, each interface icon corresponds to at least one system state, and each system state is uniformly managed by the request processing unit; wherein: The request processing unit is used to respond to system requests by calling the application bar component to update the interface icon.
[0071] In some feasible implementations, the request processing unit is specifically used for: In response to a system request, obtain the system status corresponding to the system request; Based on the system request and the system status, the application bar component is invoked to update the interface icon.
[0072] In some feasible implementations, the interface icon includes at least a status icon, the system request includes a status update request, the system status includes status update data corresponding to the status update request, and the application bar component is specifically used for: If the system request is the status update request, then the status icon is updated based on the status update data.
[0073] In some feasible implementations, the status update request includes at least one of the following: battery level change request, fuel level change request, and temperature change request; the status update data includes at least one of the following: battery level update data, fuel level update data, and temperature update data; and the status icon includes at least one of the following: battery level status icon, fuel level status icon, and temperature status icon.
[0074] In some feasible implementations, the application bar component is specifically used for: Update the battery status icon according to the battery update data; And / or, update the oil level status icon based on the oil level update data; And / or, update the temperature status icon based on the temperature update data.
[0075] In some feasible implementations, the electronic atomizing device is further configured with at least one of a power management component and an oil quantity management component; wherein: The power management component is used to obtain the current power information of the electronic atomizing device at the current moment; if the current power information changes relative to the historical power information corresponding to a historical moment, power update data corresponding to the current power information is generated, and the power change request is triggered. The oil level management component is used to obtain the current oil level information of the electronic atomizing device at the current moment; if the current oil level information changes relative to the historical oil level information corresponding to the historical moment, oil level update data corresponding to the current oil level information is generated, and the oil level change request is triggered.
[0076] In some feasible implementations, the interface icons include interactive icons, the system requests include user interaction events, and the application bar component is specifically used for: In response to the user interaction event, update the interaction icon.
[0077] In some feasible implementations, the interactive icon includes at least a communication status icon, the user interaction event includes at least a communication mode switching request, and the application bar component is specifically used for: In response to the communication mode switching request, update the communication status icon.
[0078] In some feasible implementations, the interactive page includes a Bluetooth communication page, and the device further includes: A Bluetooth page display module is used to display the Bluetooth communication page in response to a communication trigger command for the electronic atomizing device; The Bluetooth switching module is used to switch the communication connection of the electronic atomizing device in response to the communication switching command for the Bluetooth communication page, and to trigger the communication mode switching request.
[0079] In some feasible implementations, the interactive icon includes at least a suction mode icon, the user interaction event includes at least a suction mode switching request, and the application bar component is specifically used for: In response to the suction mode switching request, update the suction mode icon.
[0080] In some feasible implementations, the interactive page includes a suction control page, and the device further includes: The control page display module is used to display the inhalation control page in response to the inhalation trigger command of the electronic atomizing device; The working mode switching module is used to switch the inhalation mode of the electronic atomizing device in response to the mode switching command of the inhalation control page, and to trigger the inhalation mode switching request.
[0081] In some feasible implementations, the interface icon includes a notification icon, the system request includes a message notification event, and the application bar component is specifically used for: In response to the message notification event, update the notification icon.
[0082] In some feasible implementations, the application bar component also includes interactive controls, and the device further includes: The page response module is used to respond to the trigger operation of the interactive control and perform page operations on the interactive page.
[0083] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.
[0084] In addition, this application also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the above-described interface processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0085] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described interface processing method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0086] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.
[0087] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, EEPROM, Flash, and eMMC, etc.) containing computer-usable program code.
[0088] The interface processing method and electronic atomizing device provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. An interface processing method applied to the display component of an electronic atomizing device, characterized in that, The display component is used to provide an interactive page; the electronic atomization device is equipped with a request processing unit, and the interactive page is provided with an application bar component; the application bar component includes at least two interface icons, and each interface icon corresponds to at least one system status. The method includes: The request processing unit responds to the system request and obtains the system status corresponding to the system request; The request processing unit calls the application bar component to update the interface icon based on the system request and the system status.
2. The method according to claim 1, characterized in that, The interface icons include at least a status icon, the system request includes a status update request, and the system status includes status update data corresponding to the status update request; The request processing unit updates the interface icon by invoking the application bar component based on the system request and the system status, including: If the system request is the status update request, then the application bar component is invoked to update the status icon based on the status update data.
3. The method according to claim 2, characterized in that, The status update request includes at least one of the following: battery level change request, fuel level change request, and temperature change request; the status update data includes at least one of the following: battery level update data, fuel level update data, and temperature update data; the status icon includes at least one of the following: battery level status icon, fuel level status icon, and temperature status icon.
4. The method according to claim 3, characterized in that, Updating the status icon based on the status update data includes: Update the battery status icon according to the battery update data; And / or, update the oil level status icon based on the oil level update data; And / or, update the temperature status icon based on the temperature update data.
5. The method according to claim 4, characterized in that, The electronic atomizing device is further equipped with at least one of a power management component and an oil level management component, and the method further includes: The current battery information of the electronic atomizing device is obtained through the power management component; If the current battery level information changes relative to the corresponding historical battery level information, battery level update data corresponding to the current battery level information is generated, and the battery level change request is triggered. And / or, The current fuel level information of the electronic atomizing device is obtained through the fuel management component. If the current fuel quantity information changes relative to the corresponding historical fuel quantity information, then fuel quantity update data corresponding to the current fuel quantity information is generated, and the fuel quantity change request is triggered.
6. The method according to claim 1, characterized in that, The interface icons include interactive icons, the system requests include user interaction events, and the method further includes: In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon.
7. The method according to claim 6, characterized in that, The interactive icon includes at least a communication status icon, and the user interaction event includes at least a communication mode switching request. In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon, including: In response to the communication mode switching request, the request processing unit calls the application bar component to update the communication status icon.
8. The method according to claim 6, characterized in that, The interactive icon includes at least a suction mode icon, and the user interaction event includes at least a suction mode switching request; In response to the user interaction event, the request processing unit calls the application bar component to update the interaction icon, including: In response to the suction mode switching request, the request processing unit calls the application bar component to update the suction mode icon.
9. The method according to claim 8, characterized in that, The interactive page includes a suction control page; The method further includes: In response to a suction trigger command, the suction control page is displayed on the interactive page; In response to the mode switching command for the inhalation control page, the inhalation mode of the electronic atomizing device is switched, and the inhalation mode switching request is triggered.
10. An electronic atomizing device, characterized in that, An interactive page is provided through the display component of the electronic atomizing device; wherein, the electronic atomizing device is equipped with a request processing unit, the interactive page has an application bar component, the application bar component includes several interface icons, each interface icon corresponds to at least one system state, and each system state is uniformly managed by the request processing unit; wherein: The request processing unit is used to respond to system requests by calling the application bar component to update the interface icon.