An operating component management method and device

Abstract

This invention discloses a method and apparatus for managing operational components, relating to the field of computer technology. One specific embodiment of the method includes: responding to a user opening an application page, sending a request to the backend based on the page identifier to receive the display priority order of operational components corresponding to the page identifier and the configuration information of each operational component returned by the backend; retrieving the display mode of each operational component from the cache, adjusting the display priority order based on the display mode to obtain a new display priority order; and adding the configuration information of each operational component sequentially to the node container of the application according to the new display priority order, and displaying it at the top of the page using the specified display mode. This embodiment accurately obtains the configuration of operational components through page identifiers and intelligently adjusts the display priority, achieving personalized and precise delivery and efficient unified management of operational component configuration information, significantly improving user experience and operational efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for managing operational components. Background Technology

[0002] In mobile application development, operational components (such as pop-ups, overlays, and announcements) are crucial for enhancing user engagement. Currently, especially in the HarmonyOS operating system, traditional operational components primarily employ a decentralized management approach: each page or business module within the same application develops and maintains its own operational components independently. This approach leads to low development efficiency, severe code redundancy, and the repeated implementation of the same operational component across different pages or business modules, resulting in significant repetitive work and wasted resources. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide an operational component management method and apparatus, which can at least solve the problems of low development efficiency, serious code redundancy, repetitive work, and resource waste in the prior art.

[0004] To achieve the above objectives, according to one aspect of the present invention, an operational component management method is provided, comprising: In response to the user's operation of opening the application page, a request is sent to the backend according to the page identifier of the page to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend; The display methods of each operational component are obtained from the cache, and the display priority order is adjusted based on the display methods to obtain a new display priority order; According to the new display priority order, the configuration information of each operation component is added to the node container of the application in sequence, and displayed at the top of the page using the display method.

[0005] To achieve the above objectives, according to another aspect of the present invention, an operational component management and control device is provided, comprising: The request module is used to respond to the user's operation of opening the application page, and send a request to the backend according to the page identifier of the page, so as to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend. The adjustment module is used to obtain the display mode of each operation component from the cache, and adjust the display priority order based on the display mode to obtain a new display priority order; The display module is used to add the configuration information of each operation component to the node container of the application in sequence according to the new display priority order, and display it at the top of the page using the display method.

[0006] To achieve the above objectives, according to another aspect of the present invention, an electronic device for managing operational components is provided.

[0007] The electronic device of this invention includes: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement any of the above-described operational component management methods.

[0008] To achieve the above objectives, according to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements any of the above-described operational component management methods.

[0009] To achieve the above objectives, according to another aspect of the present invention, a computing program product is provided. One such computing program product includes a computer program that, when executed by a processor, implements the operational component management method provided in this embodiment of the invention.

[0010] According to the solution provided by the present invention, one embodiment of the invention has the following advantages or beneficial effects: It achieves intelligent and unified scheduling and display of operational components: personalized operational configurations are accurately obtained through page identifiers, and the display priority order is dynamically optimized in combination with component display methods, ensuring priority concurrent display of disordered components and sequential progressive display of ordered components, thereby maximizing display efficiency while improving user perception. This mechanism not only enables flexible configuration and dynamic adjustment of operational strategies, but also avoids the problems of redundant construction and resource waste of operational components caused by traditional decentralized development through unified node container management, significantly improving the management efficiency of operational components and the quality of user experience.

[0011] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0012] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein: Figure 1 This is a schematic diagram of the main process of unified registration of operation components according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the architecture for unified registration of operational components; Figure 3 This is a flowchart illustrating an operational component management method according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the main modules of an operation component management and control device according to an embodiment of the present invention; Figure 5 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied; Figure 6 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention, such as a mobile device or server. Detailed Implementation

[0013] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0014] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in this disclosed technical solution all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0015] In the HarmonyOS operating system, traditional operational components primarily employ a decentralized management approach: each page or business module within the same application independently develops and maintains its own operational components (such as pop-ups, overlays, and announcements). Furthermore, in existing technologies, developers typically integrate the display logic of operational components directly into each page, controlling their display and hiding through page-level state management. This existing approach suffers from the following significant drawbacks: 1. Low development efficiency and serious resource waste. Independent development of operational components for each page and business module within the same application results in a large amount of repetitive work. Similar pop-ups and overlays are repeatedly implemented on different pages, leading to code redundancy and wasted development resources. Different development teams may develop operational components with similar functions but different implementations, lacking unified standards and specifications.

[0016] 2. Disorganized management and high maintenance costs. The decentralized management model makes it difficult to unify and control operational strategies, and operations personnel cannot formulate and execute unified operational strategies from a global perspective. When adjustments to operational strategies or problem fixes are needed, modifications must be made separately on multiple pages and modules, resulting in high maintenance costs and a high risk of errors.

[0017] 3. Limitations of the technical architecture. Under the state-driven UI architecture of HarmonyOS, the traditional command-based UI operation method is limited. It cannot directly obtain the root layout and insert view components like in the Android system, which makes the unified operation and component management across pages more difficult.

[0018] See Figure 1 The diagram shows the main flowchart of a unified registration system for operational components provided by an embodiment of the present invention, which includes the following steps: S101: In response to the application's startup operation, deploy a node container in the application's root navigation container to carry operational component configuration information; S102: Configure a preset stacked layout logic for the node container; wherein, the stacked layout logic is used to overlay a display layer on the application interface to display the operation component configuration information; S103: Determine the currently available operational components in the application, and obtain and cache the display methods pre-configured for each operational component.

[0019] This implementation describes system initialization and component registration operations. This solution is primarily applied to the HarmonyOS operating system scenario, where the applications are running on HarmonyOS, such as Application 1, Application 2, Application 3, etc. These applications can all utilize this solution to achieve centralized management of operational components. HarmonyOS refers to Harmony5 and above.

[0020] Applications typically integrate multiple business modules, each corresponding to multiple pages. Existing technologies require these business modules and pages to have their own independently developed and managed operational components. This solution abandons this approach, instead setting up a unified management and control system for operational components (hereinafter referred to as the unified management system) within the application, which, combined with the backend management system, enables centralized management and control of these operational components.

[0021] For steps S101 and S102, when the application starts (including restarting after shutdown), the unified management and control system within the application also starts. After startup, the unified management and control system first creates a NodeContainer (node ​​container) placeholder component in the application's root Navigation (i.e., root navigation container). This NodeContainer is a container component provided by the HarmonyOS operating system, serving as a container for carrying operational component configuration information. The NodeContainer performs dynamic operations through the NodeController (i.e., node controller). If the NodeContainer is viewed as a canvas, the NodeController is the paintbrush on that canvas.

[0022] The configuration information for operational components includes images, text, links, etc., and there are no restrictions on this. Considering that the display of operational components, such as pop-ups, should not affect the display of the original page content, a dedicated display layer needs to be set up at the top of the page to display the component configuration information. To address this requirement, the developers configured cascading layout code (i.e., cascading layout logic) for the NodeContainer placeholder component. By executing this cascading layout code, a display layer can be overlaid on the application interface to display the operational component configuration information carried by the NodeContainer placeholder component at the top of the application interface.

[0023] In summary, the unified management and control system deploys NodeContainer in the root Navigation, forming a stacked layout with other pages, which allows the configuration information of operational components to be displayed on top of any page.

[0024] For step S103, the unified management and control system further determines the currently available operational components in the application's operational component library and obtains and caches the display methods pre-configured for each operational component. Specifically, it can obtain the component identifiers of these operational components and retrieve the pre-configured display method for each component identifier. The display method can be either ordered or unordered, thus operational components can be divided into ordered components and unordered components. Ordered components need to be displayed sequentially, while multiple unordered components can be displayed simultaneously. The mapping relationship between component identifiers and display methods is then registered with the unified management and control system.

[0025] This approach primarily considers the display method, meaning that the configuration information of all operational components in the application can be displayed using a unified layout corresponding to the type. In one optimization approach, in addition to the display method, the type also needs to be considered. In this solution, various operational components are registered to the unified management system through type pre-registration, including but not limited to Type 1: native pop-up component, Type 2: function pop-up component, Type 3: guide bar component, Type 4: floating layer component, Type 5: announcement component, and other custom types. See details... Figure 2 As shown. In this case, the mapping relationship between component identifier, type, and display method needs to be registered with the unified management and control system.

[0026] The method provided in the above embodiments facilitates the standardized display of subsequent operational components by creating a node container and configuring the cascading layout logic in the root navigation container when the application starts. Furthermore, by uniformly registering the display methods and types of all available operational components, it avoids the repetitive work and resource waste caused by independently developing operational components for each page in existing technologies. This lays the foundation for the dynamic display and priority adjustment of subsequent component configuration information, thereby significantly improving development efficiency and user experience.

[0027] See Figure 3The diagram shows the main flowchart of an operational component management method provided by an embodiment of the present invention, which includes the following steps: S301: In response to the user's operation of opening the application page, a request is sent to the backend according to the page identifier of the page to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend; S302: Obtain the display method of each operation component from the cache, adjust the display priority order based on the display method, and obtain a new display priority order; S303: According to the new display priority order, the configuration information of each operation component is added to the node container of the application in sequence, and displayed at the top of the page using the display method.

[0028] For step S301, when a page in the application is loaded, i.e., after the page is opened, the page code of that page is loaded first, and the page is rendered based on the page code. During this process, the page sends its own page identifier to the unified management and control system. After receiving the page identifier, the data layer of the unified management and control system generates a request based on the page identifier and sends it to the backend management system to obtain the operation component identifier corresponding to the page identifier, the configuration information corresponding to the operation component identifier, and the display priority order of these operation components (such as pre-configured by operations personnel).

[0029] As an optimization method, filtering can also be performed based on user attribute information and user behavior data to select operational component configuration information that is compatible with user attribute information and user behavior data. This operation can be completed by the backend management system or the unified management system, with the backend management system being the preferred method. For example, if user attribute information determines that a user is a new user, then operational components related to the new user gift pack can be recommended; or, if it is determined that a user has recently been interested in Fund A but has not purchased it, then corresponding operational components can be used to guide the user to purchase Fund A.

[0030] Existing technologies also suffer from the following problems: poor user experience and frequent user interruptions. Due to the lack of a unified frequency control management mechanism, the operational components of each page run independently. Users may encounter frequent pop-ups during use, meaning that each time a user enters a page, a unique operational pop-up may be triggered, causing excessive interruption and seriously affecting the user experience and the overall quality of the application.

[0031] To address this issue, operators can pre-configure frequency control policies for each operational component in the backend management system, or configure frequency control policies for similar operational components; the specific method is not limited. The operational component types obtained from the aforementioned unified management system can be synchronized to the backend management system for reference. Frequency control policies are used to control the frequency at which a certain type or operational component is displayed on a page or the entire application. For example, a pop-up-type operational component can be set to be displayed a maximum of three times per day for a single user. Therefore, in addition to returning the above information, the backend management system can also return the frequency control policies for each operational component, so that the display timing (including time period control, interval control, and other time dimensions) and display frequency of each operational component can be controlled based on the frequency control policies to prevent excessive user disturbance.

[0032] For step S302, after receiving the operation component identifier, configuration information, and display priority order (which may also include frequency control strategy) from the back-end management system, the data layer of the unified management system generates a corresponding operation component display task for each operation component and sends the task to the logic layer of the unified management system.

[0033] The data layer or logic layer can obtain the display methods (and types) of these operational components from the cache of the unified management and control system. The task scheduling module of the logic layer performs task scheduling based on the display methods of the operational components and the following rules: First, all unordered component tasks are arranged at the front, and these unordered components can be displayed simultaneously; then, for the remaining ordered components, the display priority of each ordered component is determined according to the original display priority order; finally, the display priorities of the unordered components and ordered components are arranged in order to obtain a new display priority order.

[0034] Example 1: When it is necessary to display the configuration information of two operation components 1 and 2, the original display priority order is 1-2. However, operation component 2 is an unordered component, so the display priority order is adjusted to 2-1. The configuration information of operation component 2 is displayed first, and the configuration information of operation component 1 is displayed after the configuration information of operation component 2 is displayed.

[0035] Example 2: When displaying configuration information for three operational components 1, 2, and 3, the original display priority order is 1-2-3. However, operational component 2 is an unordered component, so the display priority order is adjusted to 2-1-3. During display, the configuration information of operational component 2 is shown first, followed by the configuration information of operational component 1, and finally the configuration information of operational component 3. That is, the configuration information of the next ordered component is displayed only after the configuration information of one ordered component has been displayed.

[0036] Example 3: When the configuration information of three operation components 1, 2, and 3 needs to be displayed, the original display priority order is 1-2-3. However, operation components 2 and 3 are unordered components, so the display priority order is adjusted to 2, 3-1. During display, the configuration information of operation components 2 and 3 is displayed simultaneously first, and the configuration information of operation component 1 is displayed after the first two components are displayed.

[0037] In one alternative implementation, the display priority of the first ordered component can be set to the same level as that of the unordered component.

[0038] Option 1: When it is necessary to display the configuration information of two operation components 1 and 2, the original display priority order is 1-2, and operation component 2 is an unordered component. The final display priority order is adjusted to 2 and 1, that is, the configuration information of operation components 2 and 1 are displayed at the same time.

[0039] Optional Implementation Example 2: When it is necessary to display the configuration information of three operation components 1, 2, and 3, the original display priority order is 1-2-3. However, operation component 2 is an unordered component, so the display priority order is adjusted to 2, 1-3. During display, the configuration information of operation components 2 and 1 is displayed simultaneously first, and the configuration information of operation component 3 is displayed after the first two are displayed.

[0040] Option 3: When it is necessary to display the configuration information of three operation components 1, 2, and 3, the original display priority order is 1-2-3. However, operation components 2 and 3 are unordered components. Therefore, the display priority order is adjusted to 2, 3, 1, that is, the configuration information of operation components 2, 3, and 1 are displayed simultaneously.

[0041] In step S303, the proxy layer receives the list of operation component display tasks from the logic layer. However, the proxy layer does not immediately execute the display operation of the operation component configuration information upon receiving the list; instead, it waits for specific trigger conditions to be met before displaying the information. These trigger conditions include, but are not limited to: page loading completion, page open time reaching a preset duration, user inactivity on the page (idle state), and the presence and clicking of an interactive button on the page. These trigger conditions can be adaptively modified based on the specific page and are not limited in their exact nature. When the trigger conditions are met, the page sends a scheduling instruction to the unified management system. Upon receiving this scheduling instruction, the logic layer of the unified management system forwards it to the proxy layer. The proxy layer, through the component management module of the base layer, controls the NodeController of the NodeContainer placeholder component, adding the configuration information of each operation component to the NodeContainer placeholder component according to the display priority order of the operation components in the operation component display task list, thereby displaying the configuration information of the operation component on the display layer above the page. According to the solution of the aforementioned embodiment three, the system needs to display the configuration information of operation components 2 and 3. Therefore, this solution also needs to partition the display layer according to the number of operation component configuration information to be displayed, so as to display different operation component configuration information in different areas.

[0042] In addition to basic display functions, this solution can also achieve dynamic operations on operational components in NodeContainer through the component management module of the base layer, including: 1. Update Operational Components: Refresh the displayed content of operational components. For example, if a user was initially displaying a floating component, and after the user pulls down to refresh, the server updates a certain text within that floating component, then the displayed content of that text needs to be updated. For instance, if the component displays lottery configuration information, after the user scratches the prize, the specific scratch result needs to be displayed.

[0043] 2. Delete operational components: Remove the specified operational component from the NodeContainer. For example: If the user manually swipes away to remove the configuration information of operational component 2 after it has been displayed, then the configuration information of operational component 2 needs to be removed from the NodeContainer.

[0044] 3. Modify operational components: Update the attributes and states of existing operational components. For example, if the phone was originally in light mode, and the user switches to dark mode after sunset, the attributes of the displayed operational components need to be updated according to the current color mode, such as adjusting the font color to make it softer and less glaring. This mechanism can respond to changes in the application's operating environment, updating the attributes of each operational component based on the changed operating environment, and re-rendering the relevant attributes of the currently displayed operational components, thereby achieving a better user experience.

[0045] It is understood that the specific values ​​listed in the above hypothetical description of the control of operational components are merely illustrative examples and not restrictive. In practice, other values ​​can be set according to needs. Similarly, the specific values ​​listed in the subsequent embodiments are also just examples and are not the only limitation.

[0046] The method provided in the above embodiments achieves intelligent and unified scheduling and display of operational components: it accurately obtains personalized operational configurations through page identifiers and dynamically optimizes the display priority order by combining component display methods, ensuring the priority concurrent display of unordered components and the sequential progressive display of ordered components, thereby maximizing display efficiency while improving user perception. This mechanism not only enables flexible configuration and dynamic adjustment of operational strategies, but also avoids the problems of redundant construction and resource waste of operational components caused by traditional decentralized development through unified node container management, significantly improving the management efficiency of operational components and the quality of user experience.

[0047] In one optional implementation, the unified management and control system incorporates a lifecycle management module at the infrastructure layer. This module comprehensively monitors the entire lifecycle status of operational components, including key nodes such as component creation, display, hiding, and destruction. It can capture and record component status changes in real time and transmit this information to the backend management system, providing accurate data support for subsequent data statistical analysis, user behavior research, and operational effectiveness evaluation. Furthermore, when a component malfunctions or user interaction is detected, the module can quickly respond and trigger corresponding processing mechanisms to ensure system stability and the continuity of user experience.

[0048] In another optional implementation, the logic layer integrates an anomaly reporting module, specifically responsible for collecting and reporting various anomaly information generated during the operation of the unified management system. This module can capture runtime issues such as system errors, component loading failures, and network anomalies in real time, and promptly report detailed anomaly logs and error information to the monitoring center. This anomaly data provides important data support for system performance optimization, fault diagnosis, and stability improvement, helping the operations and maintenance team quickly locate the root cause of problems and develop targeted solutions.

[0049] This invention aims to solve the technical problems of fragmented management of operational components, low development efficiency, and poor user experience in existing technologies, and provides a unified management and control method for operational components based on the HarmonyOS operating system. This solution has the following beneficial effects: 1. Unified Registration Management, Improved Development Efficiency: By establishing a unified management and control system within the application, a complete registration and management system for operational component types is created. This allows for the unified registration and centralized management of all available operational components within the application, effectively avoiding redundant development. The system predefines multiple standard component types (such as types 1-5), enabling the standardization and efficient reuse of operational components across different business scenarios. This mechanism is deeply integrated with the backend management system, supporting the unified formulation, flexible adjustment, and dynamic distribution of operational strategies.

[0050] 2. Overcoming system limitations and achieving globally unified display: Breaking through the technical limitations of HarmonyOS's state-driven UI, by deploying NodeContainer placeholder components in the root Navigation, unified display and management of operational components across any page is achieved. Its core lies in fully utilizing the dynamic operation characteristics and layered layout logic of NodeContainer, allowing operational components to completely break free from the limitations of specific pages, truly achieving globally unified management across pages.

[0051] 3. Intelligent scheduling strategy to optimize user experience: By distinguishing between ordered and unordered components, intelligent scheduling of operational component display priorities based on component characteristics is achieved. Unordered components support parallel synchronous display, while ordered components are displayed sequentially according to priority. This mechanism not only fully guarantees the user's visual experience and interactive feel but also maximizes operational efficiency, achieving coordinated and orderly display among various operational components.

[0052] See Figure 4 The diagram shows the main modules of an operation component management and control device 400 provided in an embodiment of the present invention, including: The request module 401 is used to respond to the user's operation of opening the application page, and send a request to the backend according to the page identifier of the page, so as to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend. The adjustment module 402 is used to obtain the display mode of each operation component from the cache, and adjust the display priority order based on the display mode to obtain a new display priority order; Display module 403 is used to add the configuration information of each operation component to the node container of the application in sequence according to the new display priority order, and display it on the top of the page using the display method.

[0053] In the device for implementing this invention, the application runs on the HarmonyOS operating system, and the device further includes a registration module for: In response to the application's startup operation, a node container for carrying operational component configuration information is deployed in the application's root navigation container; Configure a preset stacked layout logic for the node container; wherein, the stacked layout logic is used to overlay a display layer on the application interface to display the operation component configuration information; Identify the currently available operational components in the application, and obtain and cache the display methods pre-configured for each operational component.

[0054] In the apparatus of this invention, the registration module is further configured to: acquire and cache the types pre-configured for each operating component; The display module 403 is further configured to: obtain the type of each operating component from the cache, determine the layout method corresponding to the type, and display the component on the display layer above the page using the display method and the layout method.

[0055] The apparatus for implementing the present invention further includes one or more of the following operations: In response to a user's operation to remove the configuration information of any of the displayed operational components, the configuration information of that operational component is removed from the node container; In response to a user's interactive operation on the configuration information of any of the displayed operational components, the interaction result is obtained to update the display information of the any of the operational components; In response to the detection of a change in the application's operating environment, the properties of each operating component are updated based on the changed operating environment, and the properties of the currently displayed operating components are re-rendered.

[0056] In the apparatus of this invention, the request module 401 is used for: The system acquires user attribute information and user behavior data and sends them to the backend. It then receives the display priority order of the operation components and the configuration information of each operation component, which correspond to the page identifier and match the user attribute information and user behavior data.

[0057] In the device of this invention, the display mode includes one of ordered display and disordered display, and the priority of disordered display is higher than that of ordered display. The adjustment module 402 is used for: Based on the display method, the operational components are divided into unordered components and ordered components; Set the display priority of each unordered component to the highest level; Based on the display priority order, the display priority of each ordered component is determined; Arrange the display priorities of unordered and ordered components in order to obtain a new display priority order.

[0058] In the apparatus of this invention, the adjustment module 402 is further configured to: The display priority of the ordered component with the highest display priority will be set to the same level as the unordered component.

[0059] The device for implementing the present invention further includes a frequency control module, used to: obtain the frequency control strategies of each operating component returned by the backend, and control the display timing and display frequency of each operating component based on the frequency control strategies.

[0060] Furthermore, the specific implementation details of the device described in the embodiments of the present invention have been described in detail in the above-described method, so the details will not be repeated here.

[0061] Figure 5 An exemplary system architecture 500 to which embodiments of the present invention can be applied is shown, including terminal devices 501, 502, 503, network 504, and server 505 (this is merely an example).

[0062] Terminal devices 501, 502, and 503 can be various electronic devices with displays and web browsing capabilities, and have various communication client applications installed. Users can use terminal devices 501, 502, and 503 to interact with server 505 via network 504 to receive or send messages, etc.

[0063] Network 504 is a medium used to provide a communication link between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0064] Server 505 can be a server providing various services, such as a backend management server supporting shopping websites browsed by users using terminal devices 501, 502, and 503 (this is just an example). The backend management server can analyze and process received data such as product information query requests, and feed back the processing results (e.g., target push information, product information—this is just an example) to the terminal devices. It should be noted that the method provided in this embodiment of the invention is generally executed by server 505, and correspondingly, the apparatus is generally set in server 505.

[0065] It should be understood that Figure 5 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0066] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing a terminal device of the present invention. Figure 6 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0067] like Figure 6As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0068] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0069] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this invention.

[0070] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0071] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0072] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor may be described as including a request module, an adjustment module, and a display module. The names of these modules do not necessarily limit the module itself; for example, the display module may also be described as a "display module."

[0073] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to perform any of the above-described operational component management methods.

[0074] The computer program product of the present invention includes a computer program that, when executed by a processor, implements the operation component management method in the embodiments of the present invention.

[0075] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for managing and controlling operational components, characterized in that, include: In response to the user's operation of opening the application page, a request is sent to the backend according to the page identifier of the page to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend; The display methods of each operational component are obtained from the cache, and the display priority order is adjusted based on the display methods to obtain a new display priority order; According to the new display priority order, the configuration information of each operation component is added to the node container of the application in sequence, and displayed at the top of the page using the display method.

2. The method according to claim 1, characterized in that, The application runs on the HarmonyOS operating system. Before responding to the user's action of opening the application page, the method further includes: In response to the application's startup operation, a node container for carrying operational component configuration information is deployed in the application's root navigation container; Configure a preset stacked layout logic for the node container; wherein, the stacked layout logic is used to overlay a display layer on the application interface to display the operation component configuration information; Identify the currently available operational components in the application, and obtain and cache the display methods pre-configured for each operational component.

3. The method according to claim 2, characterized in that, The step of obtaining and caching the display method pre-configured for each operation component also includes: obtaining and caching the type pre-configured for each operation component; The step of displaying the components on the page using the specified display method includes: obtaining the types of each operational component from the cache, determining the layout method corresponding to the type, and displaying the components on the display layer above the page using the specified display method and the layout method.

4. The method according to any one of claims 1-3, characterized in that, After displaying the image at the top of the page using the aforementioned display method, the method further includes one or more of the following operations: In response to a user's operation to remove the configuration information of any of the displayed operational components, the configuration information of that operational component is removed from the node container; In response to a user's interactive operation on the configuration information of any of the displayed operational components, the interaction result is obtained to update the display information of the any of the operational components; In response to the detection of a change in the application's operating environment, the properties of each operating component are updated based on the changed operating environment, and the properties of the currently displayed operating components are re-rendered.

5. The method according to claim 1, characterized in that, The receiving backend returns the display priority order of the operation components corresponding to the page identifier, as well as the configuration information of each operation component, including: The system acquires user attribute information and user behavior data and sends them to the backend. It then receives the display priority order of the operation components and the configuration information of each operation component, which correspond to the page identifier and match the user attribute information and user behavior data.

6. The method according to claim 1 or 5, characterized in that, The display method includes one of ordered display and disordered display, and the priority of disordered display is higher than that of ordered display. Adjusting the display priority order based on the display method to obtain a new display priority order includes: Based on the display method, the operational components are divided into unordered components and ordered components; Set the display priority of each unordered component to the highest level; Based on the display priority order, the display priority of each ordered component is determined; Arrange the display priorities of unordered and ordered components in order to obtain a new display priority order.

7. The method according to claim 6, characterized in that, The method further includes: The display priority of the ordered component with the highest display priority will be set to the same level as the unordered component.

8. The method according to claim 1, characterized in that, The method further includes: obtaining the frequency control strategy of each operation component returned by the backend, and controlling the display timing and display frequency of each operation component based on the frequency control strategy.

9. An operational component control device, characterized in that, include: The request module is used to respond to the user's operation of opening the application page, and send a request to the backend according to the page identifier of the page, so as to receive the display priority order of the operation components corresponding to the page identifier and the configuration information of each operation component returned by the backend. The adjustment module is used to obtain the display mode of each operation component from the cache, and adjust the display priority order based on the display mode to obtain a new display priority order; The display module is used to add the configuration information of each operation component to the node container of the application in sequence according to the new display priority order, and display it at the top of the page using the display method.

10. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-8.

11. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-8.

Images