Multi-platform intelligent interface adaptation and rendering optimization method and system

Abstract

The application discloses a kind of multi-platform-oriented intelligent interface adaptation and rendering optimization method and system, belong to interface rendering technical field.The method is first obtained and parses interface description information, extracts the hierarchical structure and constraint relationship of interface element, obtains abstract description feature;Adaptive layout mapping is carried out based on the environmental characteristic parameter of target platform, under the constraint of keeping the relative position relationship of interface element unchanged, dynamically adjust space occupation and display priority, obtain the layout scheme after platform adaptation;Determine resource consumption node according to interface element distribution characteristics, determine hierarchical rendering strategy by analyzing visibility state and update frequency characteristics;Layout scheme and rendering strategy are applied to rendering execution process to generate output;Collect performance feedback data to adaptively update space occupation and rendering strategy.The application realizes the automatic adaptation and rendering performance optimization of cross-platform interface, improves the multi-platform interface rendering efficiency and user experience.

Description

Technical Field

[0001] This invention relates to the field of interface rendering technology, and in particular to an intelligent interface adaptation and rendering optimization method and system for multiple platforms. Background Technology

[0002] With the rapid development of mobile internet and smart terminal devices, applications need to run on a variety of different platforms and devices, including mobile phones, tablets, smart TVs, and in-vehicle terminals. Different platforms differ significantly in screen size, resolution, operating system, and hardware performance, posing a serious challenge to application interface adaptation and rendering. Traditional interface development methods typically require designing and implementing interfaces separately for each platform, which is not only costly to develop but also difficult to maintain, making it hard to guarantee a consistent user experience across different platforms.

[0003] To address the challenges of cross-platform interface development, the industry has proposed various technical solutions. Some solutions employ declarative interface description languages, generating interface code for different platforms through a unified interface description file. Others utilize virtualization technology to simulate a unified runtime environment across different platforms. Additionally, there are web-based cross-platform solutions that achieve cross-platform interface display through browser kernels. Regarding rendering optimization, existing technologies primarily focus on optimizing the graphics rendering pipeline, reducing draw calls, and GPU acceleration to improve the smoothness and responsiveness of interface rendering.

[0004] However, existing technologies still have the following shortcomings:

[0005] Existing interface adaptation solutions mostly use fixed layout mapping rules, which cannot be intelligently adjusted according to the actual environmental characteristics of the target platform. When dealing with devices with large differences in screen size and performance parameters, simple scaling or fixed breakpoint adaptation often results in unreasonable arrangement of interface elements, incomplete display of some content or excessive crowding, making it difficult to make full use of the display space of different platforms, affecting the user experience and the aesthetics of the interface.

[0006] Existing rendering optimization techniques lack the ability to deeply analyze and differentiate the characteristics of interface elements. Most rendering solutions adopt a uniform rendering strategy for all interface elements, failing to perform targeted optimization based on the visibility, update frequency, complexity, and other characteristics of interface elements. This one-size-fits-all approach results in unnecessary resource consumption, especially on performance-constrained mobile devices, where rendering performance bottlenecks can easily occur, leading to interface lag and excessive power consumption.

[0007] Existing technologies lack adaptive optimization mechanisms based on runtime performance feedback. Interface adaptation and rendering strategies are typically determined at application startup and remain unchanged, failing to dynamically adjust based on actual performance and resource status during operation. When devices are in different usage scenarios or load states, fixed strategies struggle to guarantee optimal performance and cannot achieve a dynamic balance between interface display quality and system resource consumption. Summary of the Invention

[0008] The embodiments of the present invention provide an intelligent interface adaptation and rendering optimization method and system for multiple platforms, which can at least solve some of the problems existing in the prior art.

[0009] A first aspect of this invention provides an intelligent interface adaptation and rendering optimization method for multiple platforms, comprising:

[0010] Obtain interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements;

[0011] Based on the environmental characteristic parameters of the target platform, the interface elements in the abstract description features are adaptively laid out and mapped. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform.

[0012] Based on the distribution characteristics of interface elements in the layout scheme adapted to the platform, the resource consumption nodes in the rendering process are determined;

[0013] For the resource consumption nodes, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements;

[0014] The platform-adapted layout scheme and the layered rendering strategy are applied to the rendering execution process of the target platform to generate rendering output;

[0015] The performance feedback data in the rendering execution process is collected, and the space usage and the layered rendering strategy are adaptively updated using the performance feedback data.

[0016] Obtain interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract descriptive features of interface elements, including:

[0017] Parse the identifiers and attribute definitions of interface elements in the interface description information to determine the initial mapping table of interface elements;

[0018] Traverse the interface elements in the initial mapping table, identify the parent-child containment relationship and sibling parallel relationship between interface elements, and determine the hierarchical structure tree of interface elements by tracing the nesting depth and containment path of interface elements;

[0019] The position constraints, size constraints, and alignment constraints between interface elements are extracted from the interface description information. The position constraints are used to indicate the relative positional relationship of interface elements, the size constraints are used to indicate the space occupancy relationship of interface elements, and the alignment constraints are used to indicate the boundary alignment relationship of interface elements.

[0020] The position constraints, size constraints, and alignment constraints are mapped to the corresponding nodes in the hierarchical structure tree to determine the constraint relationship graph.

[0021] Based on the hierarchical structure tree and the constraint relationship graph, the interface elements are abstracted, and the specific attributes of the interface elements are converted into functional descriptions to obtain the abstract descriptive features of the interface elements.

[0022] Based on the environmental characteristic parameters of the target platform, the interface elements in the abstract descriptive features are adaptively laid out and mapped. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a platform-adapted layout scheme, including:

[0023] The available space boundary and rendering capability threshold of the display area are determined from the environmental characteristic parameters;

[0024] Based on the hierarchical structure and constraint relationships of the interface elements in the abstract description features, determine the set of relative positional constraints between the interface elements;

[0025] Based on the multi-dimensional constraint solution relationship, the available space boundary and the set of relative position constraints are transformed into a set of constraint equations for spatial layout;

[0026] Calculate the functional importance and interaction frequency of each interface element in the abstract description features, and assign display priority weights to each interface element based on the functional importance and interaction frequency.

[0027] The display priority weight is introduced as a priority coefficient for space allocation into the constraint equation set. By solving the constraint equation set, the space occupancy of interface elements is compressed and adjusted to obtain the solved interface element space allocation result.

[0028] Based on the rendering capability threshold, the renderability of the solved interface element space allocation result is verified, and the rendering accuracy and rendering content of each interface element are adjusted to generate a layout scheme adapted to the platform.

[0029] Calculate the functional importance and interaction frequency of each interface element in the abstract description features, and assign display priority weights to each interface element based on the functional importance and interaction frequency, including:

[0030] Based on the abstract description features, the functional role identifiers of each interface element are determined. The critical path position of the interface element in the business process is determined according to the functional role identifiers. A functional contribution mark is determined for the interface element, and the functional contribution mark indicates whether the interface element is located on the target path.

[0031] Analyze the dependencies between interface elements in the abstract description features to determine the basic interface elements that other interface elements depend on;

[0032] Based on the functional contribution markers and the dependency relationships between the basic interface elements, the functional importance of each interface element is obtained;

[0033] Obtain historical interaction record data, count the cumulative number of times each interface element in the historical interaction record data is operated within a unit time period, and calculate the interaction frequency of each interface element;

[0034] The interaction frequency is subjected to time decay processing, and the time-weighted interaction frequency is determined based on the distance between the time of the interaction and the current time.

[0035] The display priority weight of each interface element is obtained by weighting and integrating the functional importance of each interface element with the time-weighted interaction frequency.

[0036] Based on the distribution characteristics of interface elements in the layout scheme adapted to the platform, the resource consumption nodes in the rendering process are determined, including:

[0037] The rendering attributes of each interface element are determined from the layout scheme adapted to the platform.

[0038] The graphics complexity features in the rendering attributes are analyzed, the nesting depth of graphics operations of interface elements containing multi-level superposition operations is calculated, and the number of combinations of transformation operations of interface elements containing nonlinear transformation operations is calculated.

[0039] Based on the nesting depth and the number of combinations, interface elements whose graphics computation load exceeds a preset complexity judgment benchmark are marked as complex graphics computation nodes;

[0040] Analyze the dynamic change characteristics in the rendering attributes, record the event response frequency of interface elements that trigger content updates in response to user input events, and record the update cycle parameters of interface elements that automatically update content at fixed cycles;

[0041] Based on the event response frequency and the update cycle parameter, the expected number of times each interface element will undergo content updates within a unit time period is calculated, and interface elements whose expected number of updates exceeds a preset frequency judgment benchmark are marked as frequent update nodes;

[0042] The complex graphics processing node and the frequently updated node are designated as the resource-consuming nodes.

[0043] For the resource-consuming nodes, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements, including:

[0044] Obtain the visibility status of each interface element in the resource consumption node under the current display state;

[0045] Based on the visibility status, it is determined whether there is spatial overlap between each interface element and the display area. For interface elements that have spatial overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes.

[0046] For interface elements that spatially overlap with the display area, calculate their visible and invisible areas within the display area;

[0047] Region clipping is performed based on the visible and invisible regions, excluding the invisible regions from the rendering processing objects, and setting the rendering priority parameters of the interface elements in the visible regions to the rendering priority parameters corresponding to their resource consumption node types;

[0048] For interface elements that do not overlap with the display area, their rendering priority parameter is set to the minimum value;

[0049] Obtain the update frequency characteristics of each interface element in the resource consumption node, and allocate rendering resource quotas to each interface element according to the update frequency characteristics and the rendering priority parameter.

[0050] The layered rendering strategy is generated based on the rendering priority parameters and rendering resource quotas of each interface element.

[0051] Based on the visibility status, it is determined whether each interface element overlaps with the display area. For interface elements that overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes, including:

[0052] Based on the boundary coordinates of the display area and the position coordinates and spatial dimensions of each interface element in the visibility state, the spatial intersection of the spatial occupied area of ​​the interface element and the display area is calculated.

[0053] Determine whether the spatial intersection is an empty set. If it is, determine that there is no spatial overlap between the interface elements and the display area, and set the first rendering priority parameter; otherwise...

[0054] Determine if there is spatial overlap between the interface element and the display area, and determine whether the interface element is a complex graphics operation node based on the node type identifier of the interface element that has spatial overlap with the display area.

[0055] If it is a complex graphics operation node, set the second rendering priority parameter; otherwise, determine whether the interface element is a frequently updated node. If it is a frequently updated node, set the third rendering priority parameter.

[0056] Wherein, the value of the second rendering priority parameter is greater than the value of the third rendering priority parameter, and the value of the first rendering priority parameter is less than the value of the third rendering priority parameter.

[0057] A second aspect of this invention provides an intelligent interface adaptation and rendering optimization system for multiple platforms, comprising:

[0058] The first unit is used to acquire interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements;

[0059] The second unit is used to perform adaptive layout mapping on the interface elements in the abstract description features based on the environmental feature parameters of the target platform. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform.

[0060] The third unit is used to determine the resource consumption nodes in the rendering process based on the distribution characteristics of interface elements in the layout scheme adapted to the platform.

[0061] The fourth unit is used to determine a layered rendering strategy for the resource consumption nodes by analyzing the visibility status and update frequency characteristics of interface elements;

[0062] The fifth unit is used to apply the platform-adapted layout scheme and the layered rendering strategy to the rendering execution process of the target platform to generate rendering output;

[0063] The sixth unit is used to collect performance feedback data in the rendering execution process and to adaptively update the space usage and the layered rendering strategy using the performance feedback data.

[0064] A third aspect of the present invention provides an electronic device, comprising:

[0065] processor;

[0066] Memory used to store processor-executable instructions;

[0067] The processor is configured to invoke instructions stored in the memory to execute the aforementioned method.

[0068] A fourth aspect of the present invention provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the aforementioned method.

[0069] This invention acquires and parses interface description information, extracts the hierarchical structure and constraint relationships of interface elements to form abstract description features, and can achieve unified expression of interface elements and cross-platform compatibility. It solves the problem of repeated interface development for different platforms in traditional methods, improves the efficiency and reusability of interface development, and reduces the development cost of multi-platform adaptation.

[0070] This invention performs adaptive layout mapping based on the environmental characteristic parameters of the target platform. Under the constraint of maintaining the relative positional relationship of interface elements, it dynamically adjusts the space occupation and display priority, and determines the layered rendering strategy by combining the visibility status and update frequency characteristics of interface elements. It can intelligently allocate resources according to the hardware capabilities and display characteristics of different platforms, effectively reducing resource consumption during the rendering process and improving the smoothness of interface rendering and user experience.

[0071] This invention collects performance feedback data from the rendering execution process and adaptively updates space usage and layered rendering strategies, forming a closed-loop optimization mechanism. This enables continuous optimization of rendering performance based on actual operating conditions, improving adaptability to different usage scenarios and device states, and ensuring that the interface maintains good display effects and operating performance in various platform environments. Attached Figure Description

[0072] Figure 1 This is a flowchart illustrating the intelligent interface adaptation and rendering optimization method for multiple platforms according to an embodiment of the present invention.

[0073] Figure 2 This is a schematic diagram illustrating the process of determining rendering priority parameters according to an embodiment of the present invention. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0075] The technical solution of the present invention will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0076] Figure 1 This is a flowchart illustrating the intelligent interface adaptation and rendering optimization method for multiple platforms according to an embodiment of the present invention. Figure 1 As shown, the method includes:

[0077] Obtain interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements;

[0078] Based on the environmental characteristic parameters of the target platform, the interface elements in the abstract description features are adaptively laid out and mapped. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform.

[0079] Based on the distribution characteristics of interface elements in the layout scheme adapted to the platform, the resource consumption nodes in the rendering process are determined;

[0080] For the resource consumption nodes, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements;

[0081] The platform-adapted layout scheme and the layered rendering strategy are applied to the rendering execution process of the target platform to generate rendering output;

[0082] The performance feedback data in the rendering execution process is collected, and the space usage and the layered rendering strategy are adaptively updated using the performance feedback data.

[0083] In one optional implementation, interface description information is obtained, the interface description information is parsed, the hierarchical structure and constraint relationships of interface elements are extracted, and abstract descriptive features of interface elements are obtained, including:

[0084] Parse the identifiers and attribute definitions of interface elements in the interface description information to determine the initial mapping table of interface elements;

[0085] Traverse the interface elements in the initial mapping table, identify the parent-child containment relationship and sibling parallel relationship between interface elements, and determine the hierarchical structure tree of interface elements by tracing the nesting depth and containment path of interface elements;

[0086] The position constraints, size constraints, and alignment constraints between interface elements are extracted from the interface description information. The position constraints are used to indicate the relative positional relationship of interface elements, the size constraints are used to indicate the space occupancy relationship of interface elements, and the alignment constraints are used to indicate the boundary alignment relationship of interface elements.

[0087] The position constraints, size constraints, and alignment constraints are mapped to the corresponding nodes in the hierarchical structure tree to determine the constraint relationship graph.

[0088] Based on the hierarchical structure tree and the constraint relationship graph, the interface elements are abstracted, and the specific attributes of the interface elements are converted into functional descriptions to obtain the abstract descriptive features of the interface elements.

[0089] During the processing of interface description information, the system receives an XML or JSON-formatted interface description file containing definitions of interface elements. This description information includes complete definitions of all visual components in the interface, including declarative descriptions of interface elements such as buttons, text boxes, image views, and layout containers. The parsing engine reads the byte stream of the interface description file and converts the file content into operable data structures using a DOM parser or SAX parser. During parsing, the engine identifies the tag name of each interface element node; for example, the Button tag represents a button element, the TextView tag represents a text display element, and the LinearLayout tag represents a linear layout container.

[0090] The parsing engine extracts the attribute definitions for each UI element. These attributes are stored as key-value pairs. Typical attributes include the identifier attribute `id`, with a value of 'btn_submit' representing the unique identifier of the submit button; the width attribute with a value of 'wrap_content' indicating that the width adapts to the content; the height attribute with a value of 'match_parent' indicating that the height fills the parent container; the background attribute with a value of '#FF5733' representing the background color; and the text attribute with a value of "Confirm Operation" representing the displayed text content. An initial mapping table is created. This table is a hash table data structure, using the UI element's identifier as the key and an object containing all the element's attributes as the value. For example, the identifier 'txt_title' maps to a text element object containing attributes such as text content, font size, and color.

[0091] A depth-first traversal algorithm is used to process the UI elements in the initial mapping table. The traversal starts at the root container element in the UI description information, which is usually the top-level layout container. When the iterator accesses the root container, it checks whether the container contains child elements, and determines the parent-child relationship by reading the nesting relationship in the UI description information. For example, if a RelativeLayout container contains three Button elements and one ImageView element, then a parent-child relationship is established with RelativeLayout as the parent node and the four child elements as child nodes. During the traversal, a depth value is assigned to each UI element, with the root container having a depth value of zero, its direct child elements having a depth value of one, its secondary child elements having a depth value of two, and so on.

[0092] The system includes a path tracing mechanism to record the complete path from the root container to the current element. For example, a button element might have a path of 'RootLayout-ContentFrame-ButtonGroup-SubmitButton', indicating that the button is located within a button group container under the content frame of the root layout. When identifying sibling relationships, all child elements with the same parent node are checked and marked as sibling nodes. For instance, if a linear layout container contains five buttons, these five buttons are siblings, linked in the data structure through a linked list of sibling nodes. After the hierarchical structure tree is constructed, the root node corresponds to the root container of the interface, intermediate nodes correspond to layout containers at each level, and leaf nodes correspond to indivisible basic interface elements such as buttons, text boxes, and images.

[0093] The constraint information extraction module analyzes the layout parameter definitions in the interface description information, and extracts and identifies the positioning declarations of interface elements relative to other elements or parent containers to determine their position constraints. For example, a button's attribute contains the parameter 'layout_below' with a value of '@id / header_view', indicating that the button is below the element identified as 'header_view', recording a vertical relative position constraint between the button and 'header_view'. Another text box's attribute contains the parameter 'layout_toRightOf' with a value of '@id / icon_image', indicating that the text box is to the right of the icon element, forming a horizontal position constraint. Position constraints also include margin constraints relative to the parent container; for example, 'layout_marginTop' with a value of '16dp' indicates a density-independent pixel spacing of 16 pixels between the top of the element and the parent container or reference element.

[0094] The extraction and processing of size constraints involves defining the space occupancy declarations of UI elements. For example, an image view might have its width and height both set to 120dp, indicating that the image occupies a fixed square space. Another text container might have its width set to 0dp, with its layout weight set to 1, meaning that the element's width is distributed proportionally within the available space. Size constraints also include minimum and maximum size limits; for instance, setting 'minWidth' to 80dp guarantees the minimum width of the element, while setting 'maxHeight' to 200dp limits the maximum height. These size constraints are then converted into numerical ranges or calculation rules and stored in a constraint data structure.

[0095] Alignment constraints identify and handle the boundary alignment relationships of UI elements. For example, if a button has its 'layout_alignParentRight' property set to true, it means that the right edge of the button is aligned with the right edge of its parent container. If multiple elements have 'layout_alignBaseline' set to reference the same base element, it means that the text baselines of these elements are horizontally aligned. Alignment constraints also include center alignment; for example, 'layout_centerInParent' being true means that the element is centered both horizontally and vertically within its parent container, while 'layout_centerHorizontal' being true means it is centered only horizontally.

[0096] The process of constructing a constraint graph maps the extracted constraint information to a hierarchical structure tree. It traverses each node in the structure tree, attaching all the constraint information associated with that node. For example, the constraints attached to a button node might include: right alignment relative to its parent container, being below the element identified as `title_text`, a top margin of 16dp, width adapting to content, and a height of 48dp. The constraint graph uses a directed graph data structure, where nodes represent UI elements, edges represent constraint relationships, and edge attributes record the constraint type and parameters. For example, the edge pointing from button A to button B is labeled as "relative position constraint," and its attribute is "horizontal right margin 8dp."

[0097] The abstraction module analyzes the specific attributes of interface elements and extracts functional features. For example, an interface element with the identifier 'btn_confirm', type Button, text content "Confirm", green background, and located at the bottom of the interface, is abstracted into the following functional description: This element is the main operation trigger, performs confirmation operations, has strong visual guidance, and is located at the end of the operation flow. Another element with the identifier 'input_username', type EditText, prompt text "Please enter username", and located at the top of the interface, is abstracted as: This element is a text input receiver, used to collect user identification information, and is located at the beginning of the information collection process.

[0098] Abstract descriptive features encompass four dimensions: functional role, interaction mode, visual weight, and layout position. Functional role describes the function of an interface element within the business logic, categorized into five types: information displayer, operation trigger, data input device, content container, and navigation guide. Interaction mode describes the way users interact with elements, including click-triggered, long-press-triggered, swipe-based, text input, and selection operations. Visual weight is calculated based on the element's size, color contrast, and positional salience, categorized into high, medium, and low weight levels. High-weight elements are typically primary operation buttons or key information display areas. Layout position describes the element's location within the interface space, divided into top navigation area, middle content area, bottom operation area, left auxiliary area, and right auxiliary area. Mapping the specific attributes of each node in the hierarchical structure tree to these four dimensions of abstract feature values ​​forms a structured abstract descriptive feature dataset. This dataset provides semantic-level input information for subsequent interface adaptation and layout optimization.

[0099] In one optional implementation, the interface elements in the abstract descriptive features are adaptively laid out based on the environmental characteristic parameters of the target platform. While maintaining the relative positional relationships between interface elements, the space occupancy and display priority of the interface elements are dynamically adjusted to obtain a platform-adapted layout scheme, including:

[0100] The available space boundary and rendering capability threshold of the display area are determined from the environmental characteristic parameters;

[0101] Based on the hierarchical structure and constraint relationships of the interface elements in the abstract description features, determine the set of relative positional constraints between the interface elements;

[0102] Based on the multi-dimensional constraint solution relationship, the available space boundary and the set of relative position constraints are transformed into a set of constraint equations for spatial layout;

[0103] Calculate the functional importance and interaction frequency of each interface element in the abstract description features, and assign display priority weights to each interface element based on the functional importance and interaction frequency.

[0104] The display priority weight is introduced as a priority coefficient for space allocation into the constraint equation set. By solving the constraint equation set, the space occupancy of interface elements is compressed and adjusted to obtain the solved interface element space allocation result.

[0105] Based on the rendering capability threshold, the renderability of the solved interface element space allocation result is verified, and the rendering accuracy and rendering content of each interface element are adjusted to generate a layout scheme adapted to the platform.

[0106] In the process of implementing adaptive layout mapping for interface elements, the physical pixel size and device pixel density information of the display area are extracted from the environmental characteristic parameters of the target platform. Specifically, when the target platform is a mobile terminal, the parameters of its screen width of 1080 pixels, height of 2400 pixels, and pixel density of 480 DPI are read. At the same time, the rendering capability indicators of the device's graphics processing unit, which support a maximum texture size of 4096 pixels and can process 600 draw calls per second, are obtained. These parameters are stored as available space boundaries and rendering capability thresholds in the input parameter set for layout calculation.

[0107] The hierarchical structure of interface elements in the abstract descriptive features is analyzed, identifying three main container elements: the navigation bar, content area, and toolbar, and their contained child elements. For the navigation bar container, three child elements are identified: title text, back button, and menu button. The relative positional relationships of these elements are extracted from the descriptive features: the back button is located 16 pixels from the left margin of the navigation bar, the title text is located at the horizontal center of the navigation bar, and the menu button is located 16 pixels from the right margin of the navigation bar. These relative positional relationships are converted into constraints and stored, including the spacing constraint between the back button and the left edge of the navigation bar, the centering constraint of the title text, and the spacing constraint between the menu button and the right edge of the navigation bar.

[0108] Construct a spatial constraint network between interface elements, representing the position of each element as its offset relative to its parent container and its own size parameters. For image display elements and text description elements in the content area, establish vertical order constraints: the distance between the bottom edge of an image display element and the top edge of a text description element is 24 pixels, and the distance between the bottom edge of a text description element and the top edge of the next image display element is 32 pixels. Convert the available space boundaries into numerical range constraints: the horizontal position plus the width of all interface elements must not exceed 1080 pixels, and the vertical position plus the height must not exceed 2400 pixels.

[0109] Analyzing the functional attribute tags of each interface element in the abstract description features, a functional importance value of 95 was assigned to the confirmation button, marked as a core operation, and a functional importance value of 40 was assigned to the prompt text, marked as auxiliary information. Historical interaction data of the interface elements was analyzed; the confirmation button accounted for 38% of the total number of clicks in past use, therefore its interaction frequency value was set to 38, while the interaction frequency value of decorative icons used only for display was set to 5. A weighted average was calculated between the functional importance value and the interaction frequency value, with a functional importance weight coefficient set to 0.6 and an interaction frequency weight coefficient set to 0.4. The calculated display priority weight of the confirmation button was 72, and the display priority weight of the prompt text was 26.

[0110] The display priority weight is incorporated into the space allocation calculation process. When the available space is insufficient to accommodate the original size of all interface elements, the size of the interface elements is compressed and adjusted. Specifically, the sum of the original sizes of all interface elements is calculated to be 2680 pixels, exceeding the available vertical space by 2400 pixels (280 pixels in total). The compressibility of each element is calculated based on the reciprocal of the display priority weight. The size compression ratio of the confirmation button (display priority weight 72) is 0.05, and the size compression ratio of the prompt text (display priority weight 26) is 0.18. The original height of the prompt text (120 pixels) is compressed to 98 pixels, and the original height of the confirmation button (80 pixels) is compressed to 76 pixels. By performing differentiated compression on each interface element according to its priority weight, the adjusted space allocation result is obtained, with the total height of all elements adjusted to 2398 pixels, satisfying the available space constraint.

[0111] The rendering performance of the adjusted layout scheme was evaluated based on rendering capability thresholds. The current layout contains a total of 45 UI elements, of which 23 require independent drawing layers. The number of draw calls required to complete one frame of rendering was calculated to be 23, which does not exceed the device's supported threshold of 600 draw calls per second. For high-resolution image elements in the layout scheme, their original size was found to be 3000 pixels by 4000 pixels, exceeding the device's maximum texture size limit of 4096 pixels. The rendering precision of this image element was downgraded, and the actual size of the loaded image resource was adjusted to 1080 pixels by 1440 pixels to ensure it does not exceed the texture size limit. The rendering content of background elements containing complex gradient effects was simplified, reducing the original three-layer gradient transition to a two-layer gradient transition, thus reducing the computational complexity of the fragment shader. After renderability verification and adjustment, a complete layout scheme data structure containing the position coordinates, size parameters, and rendering configuration of all interface elements is generated. This layout scheme achieves space occupancy optimization and rendering performance adaptation for the target platform while maintaining the relative positional relationship between interface elements.

[0112] In one optional implementation, the functional importance and interaction frequency of each interface element in the abstract description features are calculated, and based on the functional importance and interaction frequency, a display priority weight is assigned to each interface element, including:

[0113] Based on the abstract description features, the functional role identifiers of each interface element are determined. The critical path position of the interface element in the business process is determined according to the functional role identifiers. A functional contribution mark is determined for the interface element, and the functional contribution mark indicates whether the interface element is located on the target path.

[0114] Analyze the dependencies between interface elements in the abstract description features to determine the basic interface elements that other interface elements depend on;

[0115] Based on the functional contribution markers and the dependency relationships between the basic interface elements, the functional importance of each interface element is obtained;

[0116] Obtain historical interaction record data, count the cumulative number of times each interface element in the historical interaction record data is operated within a unit time period, and calculate the interaction frequency of each interface element;

[0117] The interaction frequency is subjected to time decay processing, and the time-weighted interaction frequency is determined based on the distance between the time of the interaction and the current time.

[0118] The display priority weight of each interface element is obtained by weighting and integrating the functional importance of each interface element with the time-weighted interaction frequency.

[0119] Based on the metadata information contained in the abstract features of the interface description, the functional roles of each interface element are identified. Taking the product details page of an e-commerce application as an example, this page includes multiple interface elements such as a product image display area, a price display label, a "Buy Now" button, an "Add to Cart" button, a product details text area, a user review list, and a recommended product list. By parsing the abstract description features through the semantic analysis module, the functional role of the "Buy Now" button is identified as a "transaction trigger," the functional role of the product image display area is identified as an "information displayer," and the functional role of the price display label is identified as a "key information prompter."

[0120] After identifying functional roles, a directed graph model of the business process is constructed. Nodes represent interface elements, and edges represent business flow relationships. For e-commerce shopping scenarios, the key path from product browsing to transaction completion is identified as: product image display area, price display label, "Buy Now" button, and payment confirmation interface. All paths in the business process graph are traversed, and the contribution value of each path to the business objective is calculated. For interface elements located on the shortest path from user entry to completion of the core business objective, their functional contribution value is marked as one, indicating that the element is located on the target path. The "Buy Now" button, because it directly triggers the purchase behavior, has a functional contribution value of one. While the recommended product list also exists on the page, it is not on the core purchase path, and its functional contribution value is 0.3.

[0121] By parsing the dependency descriptors in the abstract descriptive features, a dependency network of interface elements is constructed. Dependencies include three types: data dependency, layout dependency, and interaction dependency. On the product details page, the availability of the "Buy Now" button depends on the product inventory quantity tag, which is the base element it depends on. The number of times each interface element is depended on by other elements is counted. The product image display area is depended on by five elements: the price tag, the buy button, and the details description, with a dependency count of five. Elements with a dependency count exceeding a threshold of three are identified as base interface elements. These base elements play a fundamental supporting role in interface rendering and interaction logic.

[0122] The function importance value is calculated by combining the function contribution marker value and the dependency count value. Specifically, the function contribution marker value is multiplied by a first weighting coefficient (e.g., 0.6), and the normalized dependency count value is multiplied by a second weighting coefficient (e.g., 0.4). The sum of these two values ​​gives the function importance. For the "Buy Now" button, its function contribution marker value is 1, its dependency count value is 2, and after normalization, it is 0.4, resulting in a function importance value of 0.76. For the product image display area, its function contribution marker value is 0.8, its dependency count value is 5, and after normalization, it is 1, resulting in a function importance value of 0.88.

[0123] Historical interaction data from the past 90 days was extracted from the database. Each record includes fields such as user ID, interface element ID, operation type, and operation timestamp. The cumulative number of operations on each interface element within a 24-hour time period was calculated. In the historical data of the product details page, the "Buy Now" button was clicked 800 times, the product image display area was viewed 1200 times, and the user review list was expanded and viewed 400 times within a certain 24-hour period. Dividing the cumulative number of clicks by the total exposure count of the interface element yielded a preliminary interaction frequency value. The "Buy Now" button was exposed 2000 times within this period, resulting in an interaction frequency of 0.4.

[0124] Interaction frequency is subject to time decay to reflect the timeliness of user behavior. The 90-day observation window is divided into 9 time periods, each lasting 10 days. Interactions closer to the current time are assigned a higher time decay coefficient. For interactions 0 to 10 days ago, the time decay coefficient is set to 1; for interactions 10 to 20 days ago, it is set to 0.9; for interactions 20 to 30 days ago, it is set to 0.8, and so on, with the oldest interactions 80 to 90 days ago having a time decay coefficient of 0.2. The interaction frequency within each time period is multiplied by the corresponding time decay coefficient, and then summed to obtain the time-weighted interaction frequency. The "Buy Now" button has an interaction frequency of 0.45 in the last 10 days, corresponding to a weight of 1; its interaction frequency in the last 10 to 20 days is 0.42, corresponding to a weight of 0.9. After weighted summation, the time-weighted interaction frequency is 0.41.

[0125] The display priority weight is calculated by weighting and fusing functional importance with time-weighted interaction frequency. During the fusion process, the fusion weight for functional importance is set to 0.55, and the fusion weight for time-weighted interaction frequency is set to 0.45, based on the application scenario. For the "Buy Now" button, its functional importance is 0.76, its time-weighted interaction frequency is 0.41, and its display priority weight is calculated to be 0.6. For the product image display area, its functional importance is 0.88, its time-weighted interaction frequency is 0.65, and its display priority weight is calculated as 0.88 × 0.55 + 0.65 × 0.45, resulting in 0.78. All interface elements are then sorted according to the calculated display priority weights, with elements having higher weight values ​​receiving higher priority in interface adaptation and resource allocation.

[0126] In one optional implementation, resource consumption nodes during the rendering process are determined based on the distribution characteristics of interface elements in the platform-adapted layout scheme, including:

[0127] The rendering attributes of each interface element are determined from the layout scheme adapted to the platform.

[0128] The graphics complexity features in the rendering attributes are analyzed, the nesting depth of graphics operations of interface elements containing multi-level superposition operations is calculated, and the number of combinations of transformation operations of interface elements containing nonlinear transformation operations is calculated.

[0129] Based on the nesting depth and the number of combinations, interface elements whose graphics computation load exceeds a preset complexity judgment benchmark are marked as complex graphics computation nodes;

[0130] Analyze the dynamic change characteristics in the rendering attributes, record the event response frequency of interface elements that trigger content updates in response to user input events, and record the update cycle parameters of interface elements that automatically update content at fixed cycles;

[0131] Based on the event response frequency and the update cycle parameter, the expected number of times each interface element will undergo content updates within a unit time period is calculated, and interface elements whose expected number of updates exceeds a preset frequency judgment benchmark are marked as frequent update nodes;

[0132] The complex graphics processing node and the frequently updated node are designated as the resource-consuming nodes.

[0133] After the layout scheme is generated and adapted to the platform, it is necessary to extract the rendering attributes of all interface elements in the layout scheme. Specifically, the interface element tree structure of the layout scheme is traversed, and the attribute information stored in the layout data structure for each interface element is read. This attribute information includes the drawing instruction set, layer configuration parameters, transformation matrix data, blending mode settings, transparency values, and animation configurations of the interface element. For example, in an interface containing product display cards, when extracting the rendering attributes of a product image element, it will record the rendering characteristics used by the image element, such as rounded corners, shadow effects, scaling transformations, and fade-in animations. These characteristics constitute the complete set of rendering attributes of the interface element.

[0134] Based on the extracted rendering attributes, a graphics complexity feature analysis is performed to construct a graphics operation dependency graph. In this graph, each node represents a basic graphics operation, and edges represent dependencies between operations. For a given UI element, starting from its final output pixel result, all intermediate computation steps required to generate that result are traced backward along the dependency graph. When it is found that the input of one computation step comes from the output of another, this relationship is marked as one level of nesting. The nesting depth of the UI element is calculated by finding the longest path from the starting point to the ending point. For example, if a user avatar element requires first circularly cropping the original image to obtain intermediate result A, then applying a border to intermediate result A to obtain intermediate result B, and finally applying an outer glow effect to intermediate result B to obtain the final display result, then the nesting depth of this avatar element is three levels.

[0135] For UI elements involving nonlinear transformation operations, analyze their transformation operation sequences and categorize rotation, tilt, perspective, non-uniform scaling, and curved path transformations as nonlinear transformation types. Traverse the transformation operation list of each UI element and count the number of nonlinear transformation operations it contains. When multiple nonlinear transformations need to be applied in combination, record the number of combinations. For example, if an animated control needs to apply both rotation and perspective transformations simultaneously during display, the number of nonlinear transformation combinations for that control is two. If the control also needs to move along a Bézier curve path, the number of combinations increases to three.

[0136] Maintain a complexity assessment benchmark configuration table, which is pre-set based on the graphics processing capabilities of the target device. For high-performance devices, the table sets the threshold for nesting depth to five levels and the threshold for the number of nonlinear transformation combinations to four levels. For medium-performance devices, the threshold for nesting depth is set to three levels and the threshold for the number of transformation combinations is set to two levels. Calculate the graphics computation load score for each interface element. This score is obtained by multiplying the nesting depth by a level weight coefficient and adding the product of the number of nonlinear transformation combinations and a transformation weight coefficient. When the score of an interface element exceeds the threshold set in the configuration table for the current device type, the interface element is marked as a complex graphics computation node, and a special identifier is added to its data structure.

[0137] During the dynamic change characteristic analysis phase, the event listener configuration of each UI element is examined. For UI elements that trigger content updates in response to user input events, interaction records for this type of UI element are retrieved from the application's historical runtime data. By statistically analyzing the number of times users triggered related events for this element in typical past usage scenarios and the corresponding time spans, the event response frequency of this element is calculated. For example, if a search box element shows in historical data that a user triggered an average of 50 text change events during a one-minute input process, then the event response frequency of this search box is recorded as 0.83 times per second. For list item elements within a scrolling container, if more than 20 position update events are triggered within one second when the user scrolls quickly, their high-frequency response characteristics are recorded accordingly.

[0138] For UI elements that automatically update content at fixed intervals, the timer parameters or animation frame rate settings in their configuration data are read. For example, if a progress bar element is configured to update its progress value every 100 milliseconds, its update period parameter is recorded as 100 milliseconds. If a carousel component is set to switch images every 3 seconds, its update period parameter is 3000 milliseconds. For elements that execute continuous animations, the update period is calculated based on the animation's frame rate configuration; for example, an animation of 60 frames per second corresponds to an update period of approximately 16.7 milliseconds.

[0139] A standard unit time period is selected as the statistical benchmark, typically 1 second. For UI elements that respond to user events, their event response frequency is directly used as the expected number of updates. For UI elements that update at a fixed period, the expected number of updates per second is obtained by dividing the millisecond value of 1 second by the millisecond value of the update period parameter. For example, a progress bar with an update period of 100 milliseconds has an expected update frequency of 10 times per second. For UI elements that have both event response and periodic update characteristics, the expected number of updates for both types is summed.

[0140] In the frequency determination benchmark configuration, a threshold parameter is set. For high-performance devices, the frequency determination benchmark is set to 15 updates per second. For low-performance devices, this benchmark is reduced to 5 updates per second. When the expected number of updates for a certain interface element exceeds the frequency determination benchmark corresponding to the current device, that element is marked as a frequent update node. For example, in a real-time data monitoring interface, the stock price display label is configured to update 20 times per second. This update frequency exceeds the benchmark value of 15 times, and therefore it is marked as a frequent update node.

[0141] All UI elements marked as complex graphics computation nodes and those marked as frequently updated nodes are collected into a resource consumption node list. Each entry in this list records the UI element's identifier, its resource consumption type, its specific complexity or update frequency, and its position in the UI layout tree. This method enables precise location and classification of resource consumption nodes during the rendering process, providing crucial decision-making support for subsequent rendering optimization strategies.

[0142] In one optional implementation, for the resource-consuming node, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements, including:

[0143] Obtain the visibility status of each interface element in the resource consumption node under the current display state;

[0144] Based on the visibility status, it is determined whether there is spatial overlap between each interface element and the display area. For interface elements that have spatial overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes.

[0145] For interface elements that spatially overlap with the display area, calculate their visible and invisible areas within the display area;

[0146] Region clipping is performed based on the visible and invisible regions, excluding the invisible regions from the rendering processing objects, and setting the rendering priority parameters of the interface elements in the visible regions to the rendering priority parameters corresponding to their resource consumption node types;

[0147] For interface elements that do not overlap with the display area, their rendering priority parameter is set to the minimum value;

[0148] Obtain the update frequency characteristics of each interface element in the resource consumption node, and allocate rendering resource quotas to each interface element according to the update frequency characteristics and the rendering priority parameter.

[0149] The layered rendering strategy is generated based on the rendering priority parameters and rendering resource quotas of each interface element.

[0150] In determining the layered rendering strategy for resource-consuming nodes, the visibility status information of interface elements in all resource-consuming nodes at the current frame is obtained through the interface rendering engine. This visibility status information includes the screen coordinates of the interface elements, the element's layer depth value, the opacity value, and the occlusion relationship identifier. Specifically, each resource-consuming node in the rendering tree structure is traversed, and the layout parameters of its bound interface elements are read. These layout parameters include the top-left corner coordinates, the element's width value, the element's height value, and the z-axis layer index. For example, a video playback control contained in an animation playback node has its top-left corner coordinates at 320 pixels horizontally and 180 pixels vertically on the display screen, a width of 640 pixels, a height of 360 pixels, a z-axis layer index of 15, and an opacity value of 255 (the value for a completely opaque state).

[0151] The obtained interface element position information is compared with the boundary parameters of the current display area to determine their spatial relationship. The boundary parameters of the display area are determined by the effective display range of the device screen, including a starting horizontal coordinate of 0 pixels, a starting vertical coordinate of 0 pixels, an ending horizontal coordinate of 1080 pixels, and an ending vertical coordinate of 1920 pixels. The judgment logic determines the spatial overlap state by comparing the numerical relationship between the boundary coordinates of the interface element and the boundary coordinates of the display area. If the right boundary horizontal coordinate of the interface element is greater than the left boundary horizontal coordinate of the display area, and the left boundary horizontal coordinate of the interface element is less than the right boundary horizontal coordinate of the display area, and the lower boundary vertical coordinate of the interface element is greater than the upper boundary vertical coordinate of the display area, and the upper boundary vertical coordinate of the interface element is less than the lower boundary vertical coordinate of the display area, then it is determined that the interface element and the display area have spatial overlap.

[0152] For interface elements determined to have spatial overlap with the display area, the type identifier of the resource consumption node to which the element belongs is further queried. The type identifier is obtained through the node attribute table, which records a Boolean value indicating whether the node is a complex graphics computation node or a frequently updated node. The criteria for determining a complex graphics computation node are that the node consumes more than 8 milliseconds of graphics processor computation time in a single rendering cycle, or involves more than 10,000 vertices. The criteria for determining a frequently updated node are that the node triggers redraw operations more than 7 times in 10 consecutive rendering frames. For example, a particle effect rendering node with a single frame processing time of 12 milliseconds and 15,000 vertices is marked as a complex graphics computation node, and its initial rendering priority parameter is set to a value of 85. A real-time data refresh list node triggers 9 redraws in the statistical period and is marked as a frequently updated node, and its initial rendering priority parameter is set to a value of 78.

[0153] For interface elements that spatially overlap with the display area, a visible area calculation is performed. During this calculation, the complete rectangular area of ​​the interface element is intersected with the rectangular boundary of the display area to obtain the actual visible rectangular area. The left boundary of the visible area is the larger of the left boundary of the interface element and the left boundary of the display area; the right boundary is the smaller of the right boundary of the interface element and the right boundary of the display area; the top boundary is the larger of the top boundary of the interface element and the top boundary of the display area; and the bottom boundary is the smaller of the bottom boundary of the interface element and the bottom boundary of the display area. For example, if the complete area of ​​an interface element is from -200 pixels horizontally to 400 pixels horizontally and from 100 pixels vertically to 500 pixels vertically, after the intersection calculation with the display area, the visible area is determined to be from 0 pixels horizontally to 400 pixels horizontally and from 100 pixels vertically to 500 pixels vertically, while the invisible area is from -200 pixels horizontally to 0 pixels horizontally.

[0154] The region clipping module generates a clipping mask data structure based on the calculated visible and invisible regions. This data structure contains a set of pixel coordinates that need to participate in rendering and a set of pixel coordinates that need to be skipped from rendering. For the UI elements in the example above, the clipping mask marks all pixels within a horizontal range of -200 pixels to 0 pixels as skipped from rendering; these pixels will not be submitted to the graphics rendering pipeline. UI elements within the visible region receive their corresponding rendering priority parameters based on their resource consumption node type. Visible elements of complex graphics operation nodes are assigned rendering priority parameters in the range of 80 to 90; visible elements of frequently updated nodes are assigned rendering priority parameters in the range of 70 to 80; and visible elements of ordinary nodes are assigned rendering priority parameters in the range of 50 to 70.

[0155] For UI elements that do not overlap with the display area, their rendering priority parameter is directly set to the minimum value of 5. Although these elements exist in the rendering tree structure, since they are completely outside the display area, they do not need to be allocated actual rendering resources during the rendering process of the current frame. For example, a floating button element located outside the display area at the bottom of the screen, with position coordinates of 2100 to 2200 pixels vertically, completely exceeding the 1920-pixel vertical boundary of the display area, has its rendering priority parameter set to 5 and will be temporarily suspended during the resource allocation phase.

[0156] The update frequency statistics module continuously monitors content change events for each UI element. This module maintains a sliding statistics window with a time window of 500 milliseconds, recording the number of content updates triggered by each UI element within this time window. Content update events include changes in element pixel data, style attribute changes, and geometric transformation operations. The statistical data is converted into update frequency characteristic values, calculated by dividing the number of updates within the statistics window by the window duration to obtain the number of updates per second. For example, if a dynamic chart element triggers 15 data refreshes within 500 milliseconds, its update frequency characteristic value is 30 times per second. If a static background element does not trigger any updates within the statistics window, its update frequency characteristic value is 0 times per second.

[0157] The rendering resource quota allocator calculates the rendering resource quota that each UI element should receive based on the rendering priority parameter and update frequency characteristic value. The rendering resource quota includes the graphics processor time slice length, the video memory buffer size, and the rendering queue priority order position. For an element with a rendering priority parameter of 85 and an update frequency of 30 times per second, the allocator calculates that its available graphics processor time per frame is 10 milliseconds, the video memory buffer space is 4 megabytes, and its rendering queue order position is 3rd. For an element with a rendering priority parameter of 55 and an update frequency of 5 times per second, its available graphics processor time per frame is 3 milliseconds, the video memory buffer space is 1 megabyte, and its rendering queue order position is 12th.

[0158] The layered rendering strategy generator integrates the rendering priority parameters and rendering resource quota information of all interface elements to construct a multi-level rendering task queue. This queue is arranged from high to low priority parameters, with elements having a rendering priority parameter range of 80 to 90 assigned to the high-priority rendering layer, elements with a priority parameter range of 60 to 80 assigned to the medium-priority rendering layer, and elements with a priority parameter below 60 assigned to the low-priority rendering layer. When executing rendering frames, the rendering engine processes the rendering tasks of the high-priority, medium-priority, and low-priority rendering layers sequentially to ensure that critical interface elements receive sufficient rendering resources.

[0159] In one optional implementation, based on the visibility state, it is determined whether each interface element has spatial overlap with the display area. For interface elements that have spatial overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes, including:

[0160] Based on the boundary coordinates of the display area and the position coordinates and spatial dimensions of each interface element in the visibility state, the spatial intersection of the spatial occupied area of ​​the interface element and the display area is calculated.

[0161] Determine whether the spatial intersection is an empty set. If it is, determine that there is no spatial overlap between the interface elements and the display area, and set the first rendering priority parameter; otherwise...

[0162] Determine if there is spatial overlap between the interface element and the display area, and determine whether the interface element is a complex graphics operation node based on the node type identifier of the interface element that has spatial overlap with the display area.

[0163] If it is a complex graphics operation node, set the second rendering priority parameter; otherwise, determine whether the interface element is a frequently updated node. If it is a frequently updated node, set the third rendering priority parameter.

[0164] Wherein, the value of the second rendering priority parameter is greater than the value of the third rendering priority parameter, and the value of the first rendering priority parameter is less than the value of the third rendering priority parameter.

[0165] Figure 2 This is a schematic diagram illustrating the process of determining rendering priority parameters according to an embodiment of the present invention. Figure 2 As shown, in the interface rendering system, after obtaining the visibility status data of all interface elements, the spatial overlap detection and rendering priority allocation operation is started. First, the boundary coordinate information of the display area is extracted. Assuming that the display area is a rectangular area, its upper left corner coordinates are x-coordinate 0 and y-coordinate 0, and its lower right corner coordinates are x-coordinate 1920 and y-coordinate 1080. This display area represents the visible range of the current device screen.

[0166] The position coordinates and spatial dimensions of the first interface element are read from the visibility status data. The top-left corner of this interface element is at x=100 and y=200, its width is 300 pixels, and its height is 400 pixels. The spatial area occupied by this interface element is calculated, and its bottom-right corner is determined to be at x=400 and y=600. The spatial intersection of the interface element's spatial area and the display area is calculated as follows: the larger of the x=100 of the left boundary of the interface element and the x=0 of the left boundary of the display area is taken as the left boundary of the intersection area; the smaller of the x=400 of the right boundary of the interface element and the x=1920 of the right boundary of the display area is taken as the right boundary of the intersection area; the larger of the y=200 of the top boundary of the interface element and the y=0 of the top boundary of the display area is taken as the top boundary of the intersection area; and the smaller of the y=600 of the bottom boundary of the interface element and the y=1080 of the bottom boundary of the display area is taken as the bottom boundary of the intersection area. The calculation yields the following boundary values ​​for the intersection region: left boundary at x-coordinate 100, right boundary at x-coordinate 400, upper boundary at y-coordinate 200, and lower boundary at y-coordinate 600.

[0167] To determine if the intersection region is empty, check if the x-coordinate of the right boundary is less than or equal to the x-coordinate of the left boundary, or if the y-coordinate of the lower boundary is less than or equal to the y-coordinate of the upper boundary. In this case, the x-coordinate of the right boundary (400) is greater than the x-coordinate of the left boundary (100), and the y-coordinate of the lower boundary (600) is greater than the y-coordinate of the upper boundary (200). Therefore, the intersection region is not empty, and it is determined that the interface element and the display area have spatial overlap.

[0168] The node type information is read from the node type identifier field of the interface element. This field stores the string 'ComplexGraphics', indicating that the interface element is a complex graphics operation node. It is then checked whether the node type identifier matches a list of identifiers for complex graphics operation nodes, which includes preset identifiers such as 'ComplexGraphics', '3DModel', and 'ShaderEffect'. Since the node type identifier of this interface element exactly matches 'ComplexGraphics' in the list, it is confirmed that the interface element is a complex graphics operation node. A second rendering priority parameter is then set for this interface element, with a specific value of 90.

[0169] Continuing with the second UI element, its top-left corner has coordinates of 2000 x, 500 y, a width of 200 pixels, and a height of 300 pixels. The bottom-right corner is calculated to be 2200 x, 800 y. Spatial intersection is calculated, taking the larger of the left boundary x of the UI element (2000) and the left boundary x of the display area (0), and the smaller of the right boundary x of the UI element (2200) and the right boundary x of the display area (1920). Since the right boundary x of the intersection area (1920) is less than the left boundary x of the intersection area (2000), the intersection area is determined to be empty. This indicates that the UI element and the display area do not overlap spatially, and a first rendering priority parameter of 10 is assigned to this UI element.

[0170] The third interface element is processed. Its top-left corner coordinates are 500 x, 300 y, with a width of 400 pixels and a height of 200 pixels. Spatial intersection calculations determine that this interface element overlaps with the display area. The node type identifier of this interface element is read as 'StaticImage', which does not match any item in the complex graphics operation node identifier list. Further checks are performed to determine if this interface element is a frequently updated node. Its update frequency attribute value is read as 60 times per second. This update frequency is compared with a preset threshold of 30 times per second. Since the actual update frequency exceeds the threshold, this interface element is confirmed as a frequently updated node. A third rendering priority parameter is set for this interface element, with a specific value of 50.

[0171] The fourth interface element is processed. Its top-left corner has coordinates of 800 x, 400 y, a width of 300 pixels, and a height of 250 pixels. Spatial intersection calculations show that this interface element overlaps with the display area. The node type of this element is identified as 'TextLabel', which is not a complex graphics operation node. The update frequency attribute of this element is read as 5 times per second, which is lower than the preset threshold of 30 times per second. Therefore, this element is neither a complex graphics operation node nor a frequently updated node. A default rendering priority parameter is set for this element, specifically a value of 30, which falls between the first rendering priority parameter of 10 and the third rendering priority parameter of 50.

[0172] After setting the rendering priority parameters for all interface elements, the interface elements with larger rendering priority parameter values ​​are placed at the front of the rendering queue to ensure that complex graphics operation nodes get rendering resources first, followed by frequently updated nodes, while interface elements that do not overlap with the display area are arranged at the end of the rendering queue or even temporarily skip the rendering operation, thereby achieving efficient allocation and utilization of rendering resources.

[0173] The intelligent interface adaptation and rendering optimization system for multiple platforms according to embodiments of the present invention includes:

[0174] The first unit is used to acquire interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements;

[0175] The second unit is used to perform adaptive layout mapping on the interface elements in the abstract description features based on the environmental feature parameters of the target platform. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform.

[0176] The third unit is used to determine the resource consumption nodes in the rendering process based on the distribution characteristics of interface elements in the layout scheme adapted to the platform.

[0177] The fourth unit is used to determine a layered rendering strategy for the resource consumption nodes by analyzing the visibility status and update frequency characteristics of interface elements;

[0178] The fifth unit is used to apply the platform-adapted layout scheme and the layered rendering strategy to the rendering execution process of the target platform to generate rendering output;

[0179] The sixth unit is used to collect performance feedback data in the rendering execution process and to adaptively update the space usage and the layered rendering strategy using the performance feedback data.

[0180] A third aspect of the present invention provides an electronic device, comprising:

[0181] processor;

[0182] Memory used to store processor-executable instructions;

[0183] The processor is configured to invoke instructions stored in the memory to execute the aforementioned method.

[0184] A fourth aspect of the present invention provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the aforementioned method.

[0185] This invention can be a method, apparatus, system, and / or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for performing various aspects of the invention.

[0186] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A multi-platform oriented intelligent interface adaptation and rendering optimization method, characterized in that, include: Obtain interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements; Based on the environmental characteristic parameters of the target platform, the interface elements in the abstract description features are adaptively laid out and mapped. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform. Based on the distribution characteristics of interface elements in the layout scheme adapted to the platform, the resource consumption nodes in the rendering process are determined; For the resource consumption nodes, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements; The platform-adapted layout scheme and the layered rendering strategy are applied to the rendering execution process of the target platform to generate rendering output; Collect performance feedback data during the rendering execution process, and use the performance feedback data to adaptively update the space usage and the layered rendering strategy. The process of obtaining interface description information, parsing the interface description information, extracting the hierarchical structure and constraint relationships of interface elements, and obtaining abstract descriptive features of interface elements includes: Parse the identifiers and attribute definitions of interface elements in the interface description information to determine the initial mapping table of interface elements; Traverse the interface elements in the initial mapping table, identify the parent-child containment relationship and sibling parallel relationship between interface elements, and determine the hierarchical structure tree of interface elements by tracing the nesting depth and containment path of interface elements; The position constraints, size constraints, and alignment constraints between interface elements are extracted from the interface description information. The position constraints are used to indicate the relative positional relationship of interface elements, the size constraints are used to indicate the space occupancy relationship of interface elements, and the alignment constraints are used to indicate the boundary alignment relationship of interface elements. The position constraints, size constraints, and alignment constraints are mapped to the corresponding nodes in the hierarchical structure tree to determine the constraint relationship graph. Based on the hierarchical structure tree and the constraint relationship graph, the interface elements are abstracted, and the specific attributes of the interface elements are converted into functional descriptions to obtain the abstract description features of the interface elements. The method involves adaptively mapping the interface elements in the abstract descriptive features based on the environmental feature parameters of the target platform. Under the constraint that the relative positional relationships between interface elements remain unchanged, the method dynamically adjusts the space occupancy and display priority of the interface elements to obtain a platform-adapted layout scheme, including: The available space boundary and rendering capability threshold of the display area are determined from the environmental characteristic parameters; Based on the hierarchical structure and constraint relationships of the interface elements in the abstract description features, determine the set of relative positional constraints between the interface elements; Based on the multi-dimensional constraint solution relationship, the available space boundary and the set of relative position constraints are transformed into a set of constraint equations for spatial layout; Calculate the functional importance and interaction frequency of each interface element in the abstract description features, and assign display priority weights to each interface element based on the functional importance and interaction frequency. The display priority weight is introduced as a priority coefficient for space allocation into the constraint equation set. By solving the constraint equation set, the space occupancy of interface elements is compressed and adjusted to obtain the solved interface element space allocation result. Based on the rendering capability threshold, the renderability of the solved interface element space allocation result is verified, and the rendering accuracy and rendering content of each interface element are adjusted to generate a layout scheme adapted to the platform. The calculation of the functional importance and interaction frequency of each interface element in the abstract description features, and the allocation of display priority weights to each interface element based on the functional importance and interaction frequency, includes: Based on the abstract description features, the functional role identifiers of each interface element are determined. The critical path position of the interface element in the business process is determined according to the functional role identifiers. A functional contribution mark is determined for the interface element, and the functional contribution mark indicates whether the interface element is located on the target path. Analyze the dependencies between interface elements in the abstract description features to determine the basic interface elements that other interface elements depend on; Based on the functional contribution markers and the dependency relationships between the basic interface elements, the functional importance of each interface element is obtained; Acquire historical interaction record data, count the cumulative number of times each interface element in the historical interaction record data is operated within a unit time period, and calculate the interaction frequency of each interface element; The interaction frequency is subjected to time decay processing, and the time-weighted interaction frequency is determined based on the distance between the time of the interaction and the current time. The display priority weight of each interface element is obtained by weighting and integrating the functional importance of each interface element with the time-weighted interaction frequency.

2. The method according to claim 1, characterized in that, Based on the distribution characteristics of interface elements in the platform-adapted layout scheme, the resource consumption nodes in the rendering process are determined, including: The rendering attributes of each interface element are determined from the layout scheme adapted to the platform. The graphics complexity features in the rendering attributes are analyzed, the nesting depth of graphics operations of interface elements containing multi-level superposition operations is calculated, and the number of combinations of transformation operations of interface elements containing nonlinear transformation operations is calculated. Based on the nesting depth and the number of combinations, interface elements whose graphics computation load exceeds a preset complexity judgment benchmark are marked as complex graphics computation nodes; Analyze the dynamic change characteristics in the rendering attributes, record the event response frequency of interface elements that trigger content updates in response to user input events, and record the update cycle parameters of interface elements that automatically update content at fixed cycles; Based on the event response frequency and the update cycle parameter, the expected number of times each interface element will be updated within a unit time period is calculated, and interface elements whose expected number of updates exceeds a preset frequency judgment benchmark are marked as frequent update nodes; The complex graphics processing node and the frequently updated node are designated as the resource-consuming nodes.

3. The method according to claim 1, characterized in that, For the resource-consuming nodes, a layered rendering strategy is determined by analyzing the visibility status and update frequency characteristics of interface elements, including: Obtain the visibility status of each interface element in the resource consumption node under the current display state; Based on the visibility status, it is determined whether there is spatial overlap between each interface element and the display area. For interface elements that have spatial overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes. For interface elements that spatially overlap with the display area, calculate their visible and invisible areas within the display area; Region clipping is performed based on the visible and invisible regions, excluding the invisible regions from the rendering processing objects, and setting the rendering priority parameters of the interface elements in the visible regions to the rendering priority parameters corresponding to their resource consumption node types; For interface elements that do not overlap with the display area, their rendering priority parameter is set to the minimum value; Obtain the update frequency characteristics of each interface element in the resource consumption node, and allocate rendering resource quotas to each interface element according to the update frequency characteristics and the rendering priority parameter. The layered rendering strategy is generated based on the rendering priority parameters and rendering resource quotas of each interface element.

4. The method according to claim 3, characterized in that, Based on the visibility status, it is determined whether each interface element overlaps with the display area. For interface elements that overlap with the display area, their rendering priority parameters are determined according to whether they are complex graphics operation nodes or frequently updated nodes, including: Based on the boundary coordinates of the display area and the position coordinates and spatial dimensions of each interface element in the visibility state, the spatial intersection of the spatial occupied area of ​​the interface element and the display area is calculated. Determine whether the spatial intersection is an empty set. If it is an empty set, determine that there is no spatial overlap between the interface elements and the display area, and set the first rendering priority parameter. Otherwise, determine if there is spatial overlap between the interface element and the display area, and determine whether the interface element is a complex graphics operation node based on the node type identifier of the interface element that has spatial overlap with the display area. If it is a complex graphics operation node, set the second rendering priority parameter; otherwise, determine whether the interface element is a frequently updated node. If it is a frequently updated node, set the third rendering priority parameter. Wherein, the value of the second rendering priority parameter is greater than the value of the third rendering priority parameter, and the value of the first rendering priority parameter is less than the value of the third rendering priority parameter.

5. A multi-platform intelligent interface adaptation and rendering optimization system, used to implement the method as described in any one of claims 1-4, characterized in that, include: The first unit is used to acquire interface description information, parse the interface description information, extract the hierarchical structure and constraint relationships of interface elements, and obtain the abstract description features of interface elements; The second unit is used to perform adaptive layout mapping on the interface elements in the abstract description features based on the environmental feature parameters of the target platform. Under the constraint that the relative positional relationship between interface elements remains unchanged, the space occupation and display priority of interface elements are dynamically adjusted to obtain a layout scheme adapted to the platform. The third unit is used to determine the resource consumption nodes in the rendering process based on the distribution characteristics of interface elements in the layout scheme adapted to the platform. The fourth unit is used to determine a layered rendering strategy for the resource-consuming nodes by analyzing the visibility status and update frequency characteristics of interface elements. The fifth unit is used to apply the platform-adapted layout scheme and the layered rendering strategy to the rendering execution process of the target platform to generate rendering output; The sixth unit is used to collect performance feedback data in the rendering execution process and to adaptively update the space usage and the layered rendering strategy using the performance feedback data.

6. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to invoke instructions stored in the memory to execute the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method described in any one of claims 1 to 4.

Images