Network interface dynamic configuration methods, electronic devices, storage media and program products

Abstract

This application discloses a method for dynamic configuration of a network interface, an electronic device, a storage medium, and a program product, relating to the field of computer technology. The method includes acquiring a user interface configuration model and target terminal device characteristics, parsing model units to construct a semantic tree and responsive configuration objects, combining device characteristics and preset layout strategies to complete interface transformation and obtain adaptive component instances, and achieving incremental rendering through a virtual interface node tree. By standardizing the model to abstract and unify the interface configuration logic, achieving accurate terminal matching through multi-terminal adaptation rules, and reducing redundant operations through an incremental update mechanism, this method breaks through the limitations of traditional development and solves the problems of poor consistency in multi-terminal adaptation of network interfaces, high development and maintenance costs, and low update response efficiency. It achieves the technical effects of improving interface adaptation accuracy and development efficiency, reducing resource consumption, and optimizing user interaction experience.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a network interface dynamic configuration method, an electronic device, a storage medium and a program product. BACKGROUND

[0002] Network interface development mainly relies on developers to manually write related codes to build interfaces. In order to realize multi-terminal adaptation, multiple sets of responsive codes or different component libraries need to be written. The low-code or no-code platforms that have appeared on the market mainly complete interface building through generating static templates. The mainstream front-end frameworks form independent ecologies respectively, and the components under different frameworks cannot be directly reused. When the technology stack is migrated or mixed development, development resources need to be repeatedly invested.

[0003] The network interface development technology related to the related art has the problems of high development and maintenance cost, poor consistency of multi-terminal adaptation, insufficient cross-framework compatibility and difficulty in dynamically responding to changes in business requirements. SUMMARY

[0004] The present application provides a network interface dynamic configuration method, an electronic device, a storage medium and a program product to at least solve the problem of poor consistency of multi-terminal adaptation in network interface development in the related art.

[0005] The present application provides a network interface dynamic configuration method, comprising:

[0006] obtaining an interface configuration model of a current user and device characteristics of a target terminal, the interface configuration model comprising a plurality of model units;

[0007] analyzing the model units of the interface configuration model respectively, constructing a semantic tree through cross-unit merging and inheritance chain association, and generating a responsive configuration object, the responsive configuration object being structured configuration data generated by extracting breakpoint configuration parameters of a style model in the model units and responsive style rules of a component;

[0008] performing interface conversion according to the semantic tree, the responsive configuration object, the device characteristics and a preset layout strategy library, to obtain a component instance set matched with the target terminal;

[0009] constructing a virtual interface node tree through the component instance set, each virtual node of the virtual interface node tree corresponding to a component instance;

[0010] incrementally rendering the interface based on the virtual interface node tree to obtain a target interface.

[0011] The present application also provides a network interface dynamic configuration device, comprising:

[0012] An acquisition module is configured to acquire an interface configuration model of a current user and device features of a target terminal, the interface configuration model comprising a plurality of model units;

[0013] An analysis module is configured to analyze the model units of the interface configuration model respectively, construct a semantic tree through cross-unit merging and inheritance chain association, and generate a responsive configuration object, the responsive configuration object being structured configuration data generated by extracting breakpoint configuration parameters of a style model in the model units and responsive style rules of a component;

[0014] A conversion module is configured to perform interface conversion according to the semantic tree, the responsive configuration object, the device features, and a preset layout strategy library, to obtain a component instance set matching the target terminal;

[0015] A construction module is configured to construct a virtual interface node tree through the component instance set, each virtual node of the virtual interface node tree corresponding to a component instance;

[0016] A rendering module is configured to perform incremental rendering on the interface based on the virtual interface node tree to obtain a target interface.

[0017] The application further provides an electronic device, comprising a memory configured to store a computer program and a processor configured to execute the computer program to implement the steps of any of the network interface dynamic configuration methods.

[0018] The application further provides a computer-readable storage medium, which stores a computer program, wherein the computer program is executed by a processor to implement the steps of any of the network interface dynamic configuration methods.

[0019] The application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of any of the network interface dynamic configuration methods.

[0020] The network interface dynamic configuration method, the electronic device, the storage medium, and the program product provided by the application can solve the technical problems of poor consistency of multi-terminal adaptation, insufficient cross-framework compatibility, slow response to changes in business requirements, and high development and maintenance costs in related technologies by standardizing and abstracting core elements such as interface structure, interactive behavior, data binding, and style theme using a unified interface configuration model, dynamically adapting and converting components in combination with device features of a target terminal and preset layout strategies, and optimizing the interface update process through virtual node tree construction and incremental rendering mechanism, thereby improving the network interface development efficiency, reducing the system maintenance cost, ensuring the consistency of multi-terminal presentation, and achieving the technical effects of rapid response to business requirements. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. Obviously, the drawings described in the following are only some of the embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort based on these drawings.

[0022] Figure 1 The flowchart of the network interface dynamic configuration method provided by the embodiments of the present application;

[0023] Figure 2 The structural diagram of the network interface dynamic configuration device provided by the embodiments of the present application;

[0024] Figure 3 The structural diagram of the electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0025] The technical solutions in the embodiments of the present application will be clearly and completely described in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, other embodiments obtained by those skilled in the art without any creative effort fall within the protection scope of the present application.

[0026] It should be noted that, in the description of the present application, the terms "comprise", "contain" or any other variants thereof are intended to cover the non-exclusive inclusion, so that the process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. The terms "first", "second" and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence.

[0027] First, the terms involved in the present application are explained:

[0028] Interface configuration model: refers to a structured data set used to define the complete form and interaction logic of a network interface, which contains multiple model units divided according to functional boundaries, and integrates core configuration information such as structure, behavior, data and style of the interface.

[0029] Model unit: refers to an independent configuration module formed by splitting according to the preset interface functional boundaries, each module contains a structure model, a behavior model, a data model and a style model, and can realize modular management and reuse.

[0030] Structural Model: Refers to the structured data that describes the hierarchical relationship of interface components, component types, attribute parameters, and sub-node distribution information, providing the basic structural framework for interface building.

[0031] Behavior Model: Refers to the configuration data that defines the interaction logic of interface components, including event response methods, condition triggering rules, and state switching logic, which standardizes the interaction behavior of components.

[0032] Data Model: Refers to the configuration data that establishes the association between interface components and backend data, clearly defining data interface addresses, data request methods, data binding paths, and automatic loading configurations, realizing the linkage between interface and backend data.

[0033] Style Model: Refers to the configuration data that defines the visual representation of the interface, including theme attributes, breakpoint configuration parameters, responsive style rules, and custom style configurations, ensuring the visual consistency of the interface across multiple terminals.

[0034] Semantic Tree: Refers to the structured semantic carrier formed by merging and associating the model units of interface configuration models, clearly defining the hierarchical relationship and core configuration of each element of the interface, providing a basis for subsequent interface conversion.

[0035] Local Sub-Semantic Tree: Refers to the hierarchical semantic fragment formed after a single model unit is parsed, and multiple local sub-semantic trees can be merged into a complete semantic tree through association rules.

[0036] Responsive Configuration Object: Refers to the structured configuration data generated based on the breakpoint configuration parameters of the style model and the responsive style rules of the component, including terminal identification, size threshold, and component style mapping relationship, supporting multi-terminal style adaptation.

[0037] Device Characteristics: Refers to the hardware and operating environment parameters of the target terminal, including screen size, input method, device type, and pixel ratio, providing a basis for terminal adaptation.

[0038] Device Feature Vector: Refers to the standardized vector formed after the device feature parameters of the target terminal are quantized, used for matching and filtering with the preset layout strategy library.

[0039] Pre-set Layout Strategy Library: Refers to the pre-constructed resource set that stores multi-terminal adaptation layout schemes, each layout strategy contains component library identification, layout conversion rules, style scaling parameters, and trigger conditions.

[0040] Target Layout Strategy: Refers to the layout scheme that is completely matched with the device characteristics of the target terminal and has the highest priority, selected from the pre-set layout strategy library, guiding the terminal adaptation conversion of the interface.

[0041] Component instance set: refers to the mapping of semantic nodes to target terminal-specific components and the completion of attribute configuration based on semantic trees, responsive configuration objects, and target layout strategies, forming a component instance cluster with executability and terminal adaptability.

[0042] Virtual interface node tree: refers to a virtual hierarchical structure built based on the component instance set, with each virtual node corresponding to a component instance, encapsulating the component's identification, attributes, and event binding information, providing an intermediate carrier for interface rendering.

[0043] Incremental rendering: refers to the process of converting virtual interface node trees into real interface nodes and completing mounting during the first rendering, and only updating and replacing real nodes for the subset of virtual nodes affected by data changes or user interactions, which can improve update efficiency.

[0044] First rendering interface: refers to the initial interface formed after converting virtual interface node trees into real interface nodes and mounting them to the preset container during the first rendering, providing a basic interface carrier for subsequent incremental updates.

[0045] Change set: refers to the subset of target virtual nodes affected by data changes or user interaction events identified in the virtual interface node tree, which is the core processing object of incremental rendering.

[0046] Update notification: refers to the message issued by the configuration center to inform the interface of the need for updates, including model update notifications and layout strategy update notifications, carrying update type, target identification, and version number information.

[0047] Target identification: refers to the identification information in the update notification used to locate the update object, including the identification code of the model unit or the layout strategy identification.

[0048] Version compatibility verification: refers to the verification process of determining whether the update version and the current running version can work together according to the preset rules, used to avoid version conflicts.

[0049] Preset interface design specification: refers to the standardized file that restricts the appearance, structure layout, component usage, and interaction logic of the interface, providing a unified design basis for interface configuration model generation.

[0050] Preset interaction logic rules: refers to the set of predefined criteria that define the behavior of interface components, providing a standard basis for the generation of behavior models.

[0051] Preset component library: refers to the pre-built resource library that stores various reusable interface components, including components for different technology stacks and different terminal types, supporting the generation of component instances.

[0052] The mapping relationship table refers to a prepared table for establishing the corresponding relationship between the semantic node type and the specific component in the preset component library, and provides a rule basis for the mapping of the semantic node to the component.

[0053] Cache updating refers to an operation of updating the model unit, the layout strategy and the corresponding semantic tree and component instance set to the cache system and recording the update timestamp and version information, which can improve the subsequent access and update efficiency.

[0054] The application concept is around the efficient implementation demand of the dynamic configuration of the network interface, takes the standardized model abstraction as the core, obtains the user exclusive interface configuration model containing multiple model units and the characteristics of the target terminal device, analyzes the model units, constructs a semantic tree by means of cross-unit merging and inheritance chain association, synchronously generates a responsive configuration object, combines the semantic tree, the responsive configuration object, the device characteristics and the preset layout strategy library to complete the interface conversion to obtain a terminal adapted component instance set, constructs a virtual interface node tree based on the set, and finally outputs the whole process design of the target interface through incremental rendering, breaks the inherent mode of the traditional network interface development, such as the tedious code writing, the fragmentation of multi-terminal adaptation and the low update efficiency, realizes the unified definition of the interface, the multi-terminal self-adaptive adaptation and the efficient dynamic update, and fundamentally optimizes the whole link process of the network interface development and maintenance.

[0055] In order to enable the person skilled in the art to better understand the application scheme, the application will be further described in detail below in combination with the drawings and specific embodiments.

[0056] Figure 1 The flowchart of the network interface dynamic configuration method provided by the embodiments of the application is shown in Figure 1 As shown in the figure, the embodiments of the application provide a network interface dynamic configuration method, and the method is described in detail as follows.

[0057] Step S101: obtaining the interface configuration model of the current user and the device characteristics of the target terminal, the interface configuration model containing multiple model units.

[0058] Specifically, based on the user individualization demand and the terminal adaptation basis, the structured interface configuration model matched with the user role and the business demand is obtained from the configuration center through the preset data acquisition mechanism, and the hardware and running environment related parameters of the target terminal are collected, wherein the interface configuration model is split into multiple independent model units according to the functional boundary to realize modular management. The core input data is provided for the subsequent interface analysis, adaptation and rendering process, which ensures that the interface configuration meets the user demand and adapts to the target terminal, and the modularized model unit design lays a foundation for the subsequent step-by-step processing. The limitation of the universal interface configuration is effectively avoided, the individualization of the interface configuration and the terminal specificity are realized, and the adjustment cost caused by the data loss or mismatch in the subsequent process is reduced.

[0059] Step S102: The model units of the interface configuration model are parsed respectively, a semantic tree is constructed through cross-unit merging and inheritance chain association, and a responsive configuration object is generated. The responsive configuration object is structured configuration data generated by extracting breakpoint configuration parameters of a style model and responsive style rules of a component in the model unit during the parsing process of the model unit.

[0060] Specifically, according to a preset parsing rule, the structure, data, behavior and style information of each model unit are extracted and structured, the association relationship between the units is established through cross-unit root node reference and inheritance chain rule to construct a complete semantic tree, and responsive parameters are extracted from the model unit and standardized to generate a responsive configuration object. The data format of the responsive configuration object is standardized and adapted to subsequent multi-terminal style matching logic, providing directly usable configuration basis for subsequent style adaptation combined with the characteristics of the target terminal device.

[0061] The abstract interface configuration model is converted into a computer-recognizable structured semantic carrier, the hierarchical relationship and interaction logic of each element of the interface are determined, and standardized configuration basis is provided for multi-terminal style adaptation. The structured parsing and associated integration of the interface configuration model are realized, the execution efficiency of subsequent interface conversion is improved, and conditions are provided for multi-terminal adaptive layout.

[0062] Step S103: Interface conversion is performed according to the semantic tree, the responsive configuration object, the device characteristics and the preset layout strategy library, to obtain a component instance set matched with the target terminal.

[0063] Specifically, based on the device characteristic parameters of the target terminal and the preset layout strategy library, the optimal adaptation strategy is selected, the hierarchical structure of the semantic tree and the style rules of the responsive configuration object are combined, the mapping of the semantic nodes to the target terminal dedicated components, the structure adjustment and the attribute configuration are completed, and a component instance set is formed. The structured semantic tree is converted into an executable component instance conforming to the characteristics of the target terminal, the conversion of the interface from abstract semantic description to terminal dedicated component is realized, the core problem of multi-terminal adaptation is solved, the high adaptability of the component instance to the target terminal is ensured, the problem of separate code writing in traditional multi-terminal development is solved, and the consistency of cross-terminal interface is improved.

[0064] Step S104: A virtual interface node tree is constructed through the component instance set, and each virtual node of the virtual interface node tree corresponds to a component instance.

[0065] Specifically, according to the association relationship of each component in the component instance set, a corresponding virtual node hierarchical structure is constructed, and the identification, attribute, event binding and other information of each component instance are encapsulated into the corresponding virtual node to form a complete virtual interface node tree. By constructing the intermediate carrier between the component instance and the real interface, an operable virtual structure is provided for subsequent rendering operations, and the centralized management of component information is realized through the encapsulation of the virtual node. The operation complexity of the real interface is simplified, accurate node positioning basis is provided for subsequent incremental rendering, and resource consumption of directly operating the real interface is reduced.

[0066] Step S105: performing incremental rendering on the interface based on the virtual interface node tree to obtain a target interface.

[0067] Specifically, the virtual interface node tree is batch-converted into real interface nodes and mounted during the first rendering, and subsequently, by monitoring data changes and user interaction events, the affected virtual nodes are located to form a change set with the minimum number, and only the virtual nodes corresponding to the change set are converted and updated to replace the real interface nodes. The initial drawing and dynamic updating of the interface are realized, the resource waste caused by full rendering is avoided through the incremental updating mechanism, and the efficiency of interface updating is ensured. The interface first-screen rendering speed and dynamic updating response efficiency are significantly improved, system resource occupation is reduced, and the user's interaction experience is optimized.

[0068] The network interface dynamic configuration method provided by the embodiment of the application standardizes and abstracts the core elements such as interface structure, interaction behavior, data binding and style theme through a unified interface configuration model, realizes dynamic adaptation and conversion of components in combination with the characteristics of the target terminal device and the preset layout strategy, and optimizes the interface updating process through the virtual node tree construction and incremental rendering mechanism, thereby fundamentally solving the problems of separate code writing for multiple terminals, non-reusable cross-framework components and interface updating dependent on full redrawing in traditional development. Therefore, the technical problems of poor consistency of multiple-terminal adaptation, insufficient cross-framework compatibility, lagging response to changes in business requirements and high development and maintenance costs in related technologies can be solved, and the effects of improving the network interface development efficiency, reducing the system maintenance cost, ensuring the consistency of multiple-terminal presentation and realizing the rapid response to business requirements can be achieved.

[0069] The embodiment details the process of obtaining the interface configuration model of the current user in the above embodiment. The model unit is obtained according to the preset interface function boundary division. The specific implementation mode of the process includes the following steps:

[0070] Step a1: obtaining the role permission, business scenario requirement and preset interface design specification of the current user.

[0071] Specifically, based on user identity recognition and demand analysis, the role permission information of the current user, the functional requirements corresponding to the specific business scenarios, and the unified interface design specifications formulated within the industry or within the enterprise are obtained through the preset data collection channel, providing basic input basis for subsequent interface model construction. The constraint conditions and requirements of interface configuration are clarified to ensure that the generated interface model meets the user's operation permissions and business demands, and meets the design standards, avoiding demand deviation or specification conflicts, clearly defining the boundaries for the generation of subsequent models, reducing the model adjustment cost caused by unclear requirements or inconsistent specifications, and improving the accuracy of interface configuration.

[0072] Step a2: generating a structure model based on role permissions, business scenario requirements, and preset interface design specifications, the structure model including component types, hierarchical relationships, attribute parameters, and sub-node distribution information of components in the interface.

[0073] Specifically, according to the obtained role permissions, business scenario requirements, and preset interface design specifications, the abstract requirements and specifications are converted into a concrete structure framework containing component types, hierarchical relationships, attribute parameters, and sub-node distribution information through structured modeling, forming a structure model.

[0074] By building the basic structural framework of the interface, the organization form and attributes of each element in the interface are clarified, providing a carrier and basis for the construction of subsequent behavior models, data models, and style models. The standardization and normalization of interface structure are realized, making the hierarchical relationship and component configuration of the interface clear and traceable, providing support for subsequent modular development and maintenance.

[0075] Step a3: associating each component in the structure model with corresponding event response modes, condition trigger rules, and state switching logic according to preset interaction logic rules, generating a behavior model.

[0076] Specifically, based on the preset interaction logic rule library, each component in the structure model is matched with corresponding event response modes, condition trigger rules, and state switching logic, and a behavior model describing the interaction behavior of the component is generated through rule association mechanism. The behavior of the component in different scenarios is clarified, making the interface have interactive functions that meet user expectations, realizing the standardized configuration of interaction logic, improving the consistency and standardization of interface interaction behavior, and reducing the user operation efficiency caused by chaotic interaction logic.

[0077] Step a4: associating components with corresponding data interface addresses, data request modes, data binding paths, and automatic loading configurations of the backend according to the data requirements of the components, constructing a data model.

[0078] Specifically, by analyzing the data requirements of each component in the structural model, the component is associated with the corresponding data source of the backend according to the data mapping rule, and the data interface address, request method, data binding path and automatic loading configuration are determined to build a data model that connects the interface and the backend data link.

[0079] By establishing the correspondence between the interface component and the backend data, a standardized path for data acquisition and updating is provided for the component, and dynamic linkage of interface data is realized. The data docking process is effectively standardized to ensure accurate acquisition and real-time updating of interface data, reduce errors in data transmission and processing, and improve the stability of data interaction.

[0080] Step a5: Based on the preset theme style specification, multi-terminal breakpoint parameters and component style rules, assign corresponding theme attributes, breakpoint configuration parameters, responsive style rules and custom style configurations to the component to obtain a style model.

[0081] Specifically, based on the preset theme style specification, multi-terminal breakpoint parameters and component style rules, and combined with the functional attributes and display requirements of the component, the corresponding theme attributes, breakpoint configuration parameters, responsive style rules and custom style configurations are assigned to each component to form a unified style model. The visual style of the interface is unified, the style of the component under different terminal devices is clear, the consistency and multi-terminal adaptability of the visual presentation of the interface are ensured; the interface style is standardized and multi-terminal adaptive, the visual experience of the interface is improved, and the development and maintenance cost of multi-terminal style adaptation is reduced.

[0082] Step a6: Integrate the structural model, behavior model, data model and style model to obtain a model unit of the interface configuration model.

[0083] Specifically, the model unit contains root node reference identifiers and inheritance chain association identifiers required for cross-unit association. By modular integration, the structural model, behavior model, data model and style model are dimensionally fused, and the scattered interface elements are encapsulated into an independent model unit to realize modularization of interface functions. By integrating the structure, behavior, data and style of the interface to form an independent module with complete functional attributes, the management, reuse and updating of the model are facilitated, the modularization degree and maintainability of the model are improved, and a foundation is laid for subsequent on-demand loading and incremental updating of model units.

[0084] After integrating the interface configuration model into a model unit, it further includes: according to the preset model unit integrity rule, checking the component hierarchy integrity of the structural model, the event response logic legality of the behavior model, the data interface effectiveness of the data model and the responsiveness rule specification of the style model; if there is a verification exception, mark the abnormal dimension and return to the corresponding model generation step for correction.

[0085] Step a7: return to the step of generating a structure model based on role permissions, business scenario requirements and preset interface design specifications until the required multiple model units for building the interface configuration model are obtained.

[0086] Specifically, based on the function boundary division of the interface, the generation and integration steps of the structure model and subsequent models are repeatedly executed through iteration to gradually build a model unit set covering the interface function modules. It is ensured that the generated model units can comprehensively cover the functional requirements of the interface, form a complete function module system, meet the configuration requirements of complex interfaces, realize comprehensive coverage and fine splitting of interface functions, avoid function omission or module redundancy, and improve the flexibility and expansibility of interface configuration.

[0087] Step a8: integrate the model units across units to obtain an interface configuration model.

[0088] Specifically, according to the preset cross-unit association rules, the association relationship and interaction logic between each model unit are analyzed, and the scattered model units are integrated into a unified and cooperative interface configuration model through integration algorithm, so as to ensure the function cooperation and data intercommunication of each unit. The integration of model units realizes the combination of each function module, forms a complete interface configuration system, and provides unified input for subsequent interface analysis and rendering. It ensures the cooperative work and data linkage of each function module of the interface, ensures the integrity and consistency of the interface configuration model, and improves the overall operation stability of the interface.

[0089] After the interface configuration model is integrated, it also includes: based on the preset cross-unit association rules, checking the rationality of the dependency relationship between different model units, data interface call conflicts and style theme consistency; if there is a cooperation conflict, a conflict report is generated and the association logic of the model unit is adjusted until the integrated interface configuration model passes the verification. The verification improves the stability of the interface configuration model.

[0090] The embodiments of the present application realize the modularization, standardization and refinement of the network interface configuration through the process of obtaining core requirements and specifications, generating structure, behavior, data and style models in steps, integrating model units, iteratively improving unit set, and integrating complete model across units. It breaks through the limitations of dispersed elements, difficult maintenance and complex multi-terminal adaptation in traditional interface development, significantly improves the maintainability, expandability and multi-terminal adaptation capability of interface configuration, and at the same time reduces the development cost and response cycle of requirement changes.

[0091] In some optional embodiments, it also includes:

[0092] Step a11, according to the preset unit priority, filtering out the core model unit from the multiple model units of the interface configuration model and marking.

[0093] Specifically, according to the preset unit priority, the plurality of model units in the interface configuration model are sorted, the core model unit is screened out, and the core attribute marking is completed through the identification mechanism. The loading priority level of the model unit is clear, which provides a basis for the subsequent hierarchical loading strategy, ensures that the core configuration resource is acquired first, avoids the first screen rendering delay caused by the chaotic loading order, and improves the response efficiency of interface initialization.

[0094] Step a12, a mapping relationship table of routing and non-core model units is established to determine the model units corresponding to different routes; when a user triggers route jumping is detected, the front end dynamically locates and acquires the model unit corresponding to the route based on the mapping relationship table.

[0095] Specifically, by establishing a structured mapping relationship between the routing address and the non-core model unit, the model unit to which the structure, behavior, data and style configuration of different routes belong is determined; the route jump event triggered by the user is captured through the route monitoring mechanism, and the corresponding model unit is dynamically acquired based on the mapping relationship table. The precise association between the route and the model unit is realized, the redundant loading of the non-core model unit can be avoided through high-priority asynchronous loading, the resource loading amount in the initialization stage is reduced, the network transmission and memory occupation cost is reduced, the response speed of interface rendering during route jumping is improved, and the smoothness of interface switching is ensured.

[0096] Step a13: Real-time collection of user operation data and combination of historical behavior data to establish a behavior prediction model; the function module that the user may access subsequently is determined through the prediction model, and the preloading operation of the corresponding model unit is triggered to cache the high-order configuration data to the local in advance.

[0097] Specifically, by real-time monitoring of user operation data combined with historical behavior data set, a behavior prediction model is constructed through data analysis; based on the prediction model, the function module that the user may access subsequently is predicted, the preloading process of the corresponding model unit is triggered, and the related high-order configuration data is cached to the local storage. The configuration resources corresponding to the potential needs of the user are reserved in advance, the configuration acquisition waiting time of subsequent operation is shortened, the intelligent prediction of configuration loading is realized, the configuration loading delay when the user accesses the subsequent function is reduced, the smoothness of the interaction process is improved, and the coherence and convenience of the user operation experience are enhanced.

[0098] Step a14: Constructing a runtime model cache pool to identify and store the model units that have been successfully loaded according to the unique identification code; when the same model unit needs to be acquired subsequently, it is directly called from the cache pool.

[0099] Specifically, by constructing a runtime model cache pool, a unique identification code is assigned to a successfully loaded model unit, and storage and index management of the model unit are completed through an identification mapping mechanism; when a same model unit needs to be obtained subsequently, the model unit is directly called from the cache pool through identification retrieval, and a repeated loading request does not need to be initiated. By establishing a model unit reuse mechanism, resource consumption caused by repeated loading and parsing is avoided, secondary acquisition efficiency of the model unit is improved, fast calling of the model unit is realized, system resource occupation and network transmission overhead are reduced, repeated parsing time consumption is reduced, and response speed of interface loading and updating is further optimized.

[0100] The embodiment of the application solves the problems of sequence disorder, resource redundancy and response delay in the traditional loading mode by constructing a hierarchical, intelligent and efficient model unit acquisition system, significantly improves the pertinence, intelligence and efficiency of model unit loading, reduces system resource consumption and network overhead, and guarantees the fluency and response speed of interface initialization, route switching and subsequent interaction.

[0101] The embodiment details the process of parsing the model units of the interface configuration model in the above embodiment, constructing a semantic tree through cross-unit merging and inheritance chain association, and simultaneously generating a responsive configuration object, and the specific implementation mode of the process includes the following steps:

[0102] Step b1, creating a semantic node corresponding to the component according to the hierarchical relationship, component type, attribute parameter and subnode distribution information of the component.

[0103] Specifically, according to the hierarchical relationship, component type, attribute parameter and subnode distribution information of the component, the structured information of the component is converted into a computer-recognizable semantic layer node carrier according to a preset semantic node creation rule, and the corresponding association between the component and the semantic node is established.

[0104] By objectifying the dispersed component information into standardized semantic nodes, a basic unit is provided for subsequent construction of a semantic tree, semantic conversion of component information is realized, conversion from concrete description to semantic expression of component information is completed, the component information has a unified processing dimension, and the standardization and efficiency of subsequent semantic tree construction are improved.

[0105] Step b2, creating a local sub-semantic tree corresponding to the model unit based on the mapping relationship between the semantic node and the hierarchical relationship of the component.

[0106] Specifically, based on the mapping correspondence of the semantic node and the component hierarchical relationship, the semantic nodes in the same model unit are sequentially arranged and associated according to the hierarchical organization rule to form a local sub-semantic tree with a hierarchical structure. By building the semantic structure framework of a single model unit and clearly defining the hierarchical association of the semantic nodes in the model unit, the structured integration of the semantic information of the model unit is realized, the semantic information of the single model unit presents a clear hierarchical system, a structured basis is provided for subsequent merging of the semantic trees across units, and the complexity of the integration across units is reduced.

[0107] Step b3, according to the preset root node reference rule and inheritance chain association rule, the local sub-semantic tree is merged across units to form a semantic tree.

[0108] Specifically, based on the root node reference identifier and the inheritance chain association identifier of the model unit, the cross-unit merging is performed. By identifying the association relationship between different local sub-semantic trees, multiple local sub-semantic trees are integrated into a complete semantic tree based on rule matching and association fusion algorithm. The organic connection of the semantic information of different functional modules is realized, a unified semantic structure covering the entire interface configuration model is constructed, a semantic tree with global association is formed, the collaborative consistency of the semantic information of each functional module of the interface is ensured, and a complete semantic basis is provided for subsequent interface conversion.

[0109] After the semantic tree is formed, the mapping consistency of the semantic nodes and the core information of the model unit can be verified by comparing the hierarchical structure of the semantic tree with the functional boundary division of the original interface configuration model, and the logical correctness of the inheritance chain association is checked. If there is a parsing deviation, the model unit parsing step is retraced for reprocessing to ensure that the semantic tree can accurately reflect the core requirements of the interface configuration model.

[0110] Step b4, obtaining breakpoint configuration parameters and responsive style rules of components from the style model of the model unit.

[0111] Specifically, based on the structured data format of the style model, the breakpoint configuration parameters and the responsive style rules of the components used for multi-terminal adaptation are accurately filtered from the style model through the preset information extraction rule. By separating the core data required for multi-terminal style adaptation, the key information required for responsive adaptation is accurately obtained, irrelevant data interference is avoided, and a data foundation is laid for subsequent standardized processing of responsive configuration.

[0112] Step b5, standardizing the breakpoint configuration parameters to obtain size division thresholds and priority orders of multiple terminals.

[0113] Specifically, by standardizing the format of the breakpoint configuration parameters, based on a preset terminal type classification rule, size division thresholds corresponding to each terminal and a unified priority sorting rule are generated. Through standardization processing, the extracted breakpoint configuration parameters are formatted and threshold sorted, the size division standards corresponding to different terminals are determined, the priority order of each size threshold is determined, the size division basis of multiple terminals is unified, and the differences in breakpoint configuration in different model units are eliminated, providing a unified standard for cross-terminal association of responsive style rules; the standardization and unification of breakpoint configuration are realized, ensuring the consistency of multi-terminal size judgment, and improving the accuracy of subsequent responsive style adaptation.

[0114] Step b6, the responsive style rules are classified and associated according to the types of multiple terminals, and a responsive configuration object containing terminal identification, size threshold, and component style mapping relationship is generated.

[0115] Specifically, according to the standardized terminal size division threshold and priority order, the responsive style rules of the component are classified, matched and associated according to the terminal type, and a standardized responsive configuration object containing terminal identification, size threshold and component style mapping relationship is constructed. By establishing the corresponding association of responsive style and terminal type and size threshold, a standardized responsive adaptation basis is formed, the component style rules in different terminal scenarios are determined, a responsive configuration object with a unified format is generated, clear rule guidance is provided for subsequent multi-terminal style adaptation of the interface, and the efficiency and consistency of multi-terminal style adaptation are improved.

[0116] The embodiment of the application realizes semantic analysis of the interface configuration model and standardized generation of responsive configuration by creating semantic nodes, constructing local sub-semantic trees, merging complete semantic trees across units, extracting responsive parameters, standardizing breakpoint configurations, and generating responsive configuration objects, solves the problems of dispersed semantic information and non-uniform responsive configuration in the traditional analysis process, improves the completeness of semantic analysis and the standardization of responsive configuration, and provides semantic and configuration support for subsequent multi-terminal adaptation and efficient conversion of interfaces.

[0117] The embodiment details the process of interface conversion according to the semantic tree, responsive configuration object, device characteristics, and preset layout strategy library in the above embodiment to obtain a component instance set matching the target terminal, and the specific implementation mode of the process includes the following steps:

[0118] Step c1, the device characteristics of the target terminal are analyzed to generate a device characteristic vector.

[0119] Specifically, by device feature analysis, the screen size, input method, device type and pixel ratio and other parameters of the target terminal are extracted and quantized, and the scattered device feature parameters are converted into a standardized vector form to form a device feature vector. By converting the abstract device features into structured data that can be operated by a computer, the core adaptation requirements of the target terminal are determined, the standardized representation of device features is realized, the differences in terminal feature description are eliminated, and the efficiency and accuracy of subsequent layout strategy matching are improved.

[0120] Step c2, matching the device feature vector with the preset layout strategy library to obtain a target layout strategy, which includes component library identification, layout conversion rule and style scaling parameter.

[0121] Specifically, by vector matching, the generated device feature vector is logically compared with the trigger conditions of each layout strategy in the preset layout strategy library, and the target layout strategy matching the device feature vector is selected. The strategy scheme suitable for the target terminal is determined, the corresponding component library, layout conversion rule and style scaling parameter are determined, the direction guidance for subsequent interface conversion is provided, the blindness of strategy selection is avoided, the foundation for subsequent component mapping and structure adjustment is laid, and the pertinence of interface adaptation is ensured.

[0122] Step c3, calling the corresponding component type and the mapping relationship table of components in the preset component library based on the component library identification.

[0123] Specifically, according to the component library identification in the target layout strategy, the mapping relationship table of the component type corresponding to the identification and the components in the library is extracted from the preset component resource library through the component library calling interface. The association between semantic nodes and specific component libraries is established, and the source of target components corresponding to different semantic nodes is determined, which provides a rule basis for the mapping of semantic nodes to components.

[0124] Step c4, mapping each semantic node of the semantic tree to a target component type according to the mapping relationship table.

[0125] Specifically, according to the rules in the mapping relationship table, the semantic nodes in the semantic tree are traversed, and each semantic node is matched to a specific component type in the target component library according to the rules, completing the conversion of semantic nodes to component types. Abstract semantic description is converted into concrete component types, and accurate correspondence between semantic nodes and component types is established to ensure consistency between component types and semantic requirements.

[0126] Step c5, structure adjustment of the mapped semantic nodes according to the responsive configuration object and the layout conversion rule, including terminal adaptation conversion of container layout form, navigation mode and form layout.

[0127] Specifically, the terminal identifier, the size threshold, and the component style mapping relationship in the responsive configuration object are combined, the layout conversion rule in the target layout strategy is used to perform structure reconstruction on the mapped component type, the component structure is optimized to adapt to the display characteristics of the target terminal, the interface display adaptation problem caused by hardware differences of different terminals is solved, and the component structure is matched with the terminal scene.

[0128] In step c6, the event response mode, the condition triggering rule, the data interface address, and the data binding path corresponding to the target component are obtained from the behavior model and the data model of the model unit.

[0129] Specifically, the event response mode and the condition triggering rule corresponding to the target component are obtained from the previously constructed behavior model, and the data interface address and the data binding path are extracted from the data model. The function configuration information of the component instance is ensured to be complete, the component interaction or data linkage failure caused by missing configuration is avoided, and a foundation is laid for the function integrity of the subsequent component instance.

[0130] In step c7, the event response mode, the condition triggering rule, the data interface address, the data binding path, and the style scaling parameter are associated with the corresponding target component to generate a component instance.

[0131] Specifically, the component configuration association algorithm is used to bind the extracted event response mode, condition triggering rule, data interface address, data binding path, and style scaling parameter with the corresponding target component, and a component instance with complete functions is formed. The conversion of the component from the type to the instance is completed, the component has executability, and the component can realize the expected interaction effect and data linkage function.

[0132] In step c8, the component instances are arranged according to the hierarchical structure of the semantic tree to obtain a component instance set matched with the target terminal.

[0133] Specifically, the generated component instances are orderly organized and hierarchically arranged according to the hierarchical structure and node association relationship of the semantic tree, and a component instance set adapted to the target terminal is constructed. The component instance set with regular structure and adapted to the target terminal is formed, the smoothness of the subsequent interface construction process is ensured, and the efficiency and accuracy of the interface generation are improved.

[0134] The embodiment of the application realizes efficient conversion from abstract semantics to terminal exclusive component instance set by analyzing device feature generation vector, matching target layout strategy, calling component mapping table, semantic node mapping component type, component structure terminal adaptation, extracting function configuration information, generating component instance, and arranging to form instance set, solves the problems of component adaptation confusion and function configuration complexity in traditional multi-terminal development, significantly improves the accuracy and efficiency of interface conversion, guarantees the high adaptability of component instance and target terminal, and provides high-quality input data for subsequent virtual interface node tree construction and incremental rendering.

[0135] The embodiment details the process of constructing a virtual interface node tree from the component instance set in the above embodiment, and the specific implementation mode of the process includes the following steps:

[0136] Step d1, obtaining the component identifier, attribute configuration and parent-child component association relationship of the component instance.

[0137] Specifically, based on the structured data format of the component instance set, the core metadata such as the component identifier, attribute configuration and parent-child component association relationship are extracted from the component instance to clearly identify the identity, function attribute and hierarchical association logic of the component instance, lay a data foundation for subsequent hierarchical framework building and virtual node creation, ensure the input data of the subsequent construction steps to be accurate and complete, avoid the node tree construction deviation caused by information missing or error, and improve the stability of the overall construction process.

[0138] Step d2, establishing a hierarchical structure framework of virtual nodes according to the parent-child component association relationship.

[0139] Specifically, according to the extracted parent-child component association relationship, the hierarchical structure framework of virtual nodes is constructed by topological sorting algorithm according to the hierarchical structure organization rules, and the hierarchical position and association order of each node are clearly defined. The clear and orderly hierarchical structure benchmark is formed to reduce the structural confusion problem in the subsequent virtual node assembly process and improve the efficiency and standardization of node tree construction.

[0140] Step d3, creating corresponding virtual nodes for the component instance, and encapsulating the component identifier and attribute configuration of the component instance into the corresponding virtual nodes.

[0141] Specifically, the virtual node carrier is created for each component instance, and the component identifier and attribute configuration are injected into the virtual node through data encapsulation mechanism to realize the conversion of component instance information to virtual node data. The dispersed component information is encapsulated into a unified virtual node unit to provide an operable basic unit for subsequent node tree assembly, realize the standardized encapsulation of component information, accurately carry the component attribute and identifier in the virtual node, and guarantee that the virtual node has the core data required for subsequent assembly and rendering.

[0142] Step d4, the virtual nodes are hierarchically assembled according to the hierarchical framework to obtain an initial virtual interface node tree.

[0143] Specifically, the virtual nodes are hierarchically spliced and associated in order according to the hierarchical framework, and the scattered virtual nodes are integrated into an initial virtual interface node tree with complete hierarchical structure. The systematic integration of virtual nodes is realized, an initial virtual interface node tree structure is formed, and an initial node tree with complete hierarchical form is obtained.

[0144] Step d5, the initial virtual interface node tree is traversed and checked to check the hierarchical association accuracy and attribute configuration integrity of the virtual nodes.

[0145] Specifically, according to the requirements, a depth-first or breadth-first traversal algorithm can be used to scan the initial virtual interface node tree, and the hierarchical association logic accuracy and attribute configuration data integrity of the virtual nodes are checked according to the preset checking rules. The structure defects and data missing problems existing in the initial virtual interface node tree are identified, accurate problem positioning basis is provided for subsequent correction and optimization, and the quality of the virtual node tree is ensured.

[0146] Step d6, if the checking fails, the virtual nodes with hierarchical association errors or attribute configuration missing are obtained, and the virtual nodes are corrected or supplemented according to the information of the component instances corresponding to the virtual nodes.

[0147] Specifically, for the virtual nodes with hierarchical association errors or attribute configuration missing identified by the checking, the corresponding component instance original information is returned, and the problem nodes are optimized and improved through data supplementing, hierarchical adjusting and other correction mechanisms, so as to ensure that the virtual node tree has correct hierarchical association logic and complete attribute configuration.

[0148] Step d7, if the checking passes, a virtual interface node tree is obtained.

[0149] Specifically, when it is confirmed that the initial virtual interface node tree has passed the checking or correction and has met the preset quality standard, the qualified virtual interface node tree is output as the core input data of the subsequent interface rendering process, the input data quality of the subsequent rendering process is ensured, and it is ensured that the rendered interface structure is correct and the attributes are complete.

[0150] The embodiment of the application realizes the standardized and accurate construction of the virtual interface node tree through the processes of extracting component core information, building a hierarchical structure framework, creating and packaging virtual nodes, assembling an initial node tree, traversing and checking defects, correcting and optimizing problems, and outputting a qualified node tree, improves the construction efficiency and quality of the virtual node tree, provides high-quality structure support for the subsequent efficient incremental rendering of the interface, and ensures the consistency of the interface structure and the component instance information.

[0151] The embodiment details the process of obtaining the target interface by incrementally rendering the interface based on the virtual interface node tree in the above embodiment. The specific implementation of the process includes the following steps:

[0152] Step m1, converting the virtual nodes of the virtual interface node tree into corresponding real interface nodes.

[0153] Specifically, by converting the component identifier, attribute configuration and other information encapsulated in the virtual interface node into a real interface node that conforms to the page rendering standard, the virtual data is converted into a tangible interface element. The abstract virtual structure is converted into a real element that can be parsed by the browser, providing an operable entity for subsequent interface mounting, ensuring that the attributes and structure of the real node are consistent with the virtual node.

[0154] Step m2, according to the hierarchical structure of the virtual interface node tree, mounting the real interface nodes into the container node preset on the page to obtain the first rendering interface.

[0155] Specifically, according to the hierarchical association relationship of the virtual interface node tree, the converted real interface nodes are mounted into the container node preset on the page in the corresponding hierarchical order to realize the ordered assembly of the real nodes. The scattered real interface nodes are integrated into a complete and interactive initial interface, realizing the leap from node set to visual interface, ensuring that the hierarchical structure of the initial interface is consistent with the virtual node tree, providing a basic interface interaction carrier for users and ensuring the integrity and standardization of the initial rendering.

[0156] Step m3, real-time monitoring of data interface return data corresponding to the data model in the interface configuration model and user interaction operations to obtain data change information or interactive trigger event information.

[0157] Specifically, by continuously monitoring the change state of the data interface return data associated with the data model, and capturing the user's interaction operation on the interface, the corresponding change information and event signal are extracted. Real-time sensing of the trigger conditions required by the interface provides trigger signals and data support for the incremental update process.

[0158] Step m4, when the data change information or interactive trigger event information is monitored, the corresponding data source association path or interactive component identifier is located.

[0159] Specifically, for the monitored data change information or interactive trigger event information, the data source association path or interactive component core identifier is located through the data source path matching algorithm or component identifier association. Accurately locate the position of the interface update to avoid fuzzy positioning, improve the positioning efficiency after the update is triggered, and reduce invalid node traversal and search.

[0160] Step m5, based on the data source association path or the interactive component identifier, identifying the corresponding target virtual node subset in the virtual interface node tree to obtain the change set.

[0161] Specifically, based on the located data source association path or interactive component identifier as the retrieval basis, directional traversal and matching are performed in the virtual interface node tree to filter out the virtual node subset affected by the data source or component, and a change set required for updating is formed. Avoiding full-amount processing of the entire virtual interface node tree, the node scale of the updating process is reduced, unnecessary calculation and conversion overheads are reduced, the execution efficiency of the subsequent updating process is improved, and system resource occupation is reduced.

[0162] Step m6, re-conversion processing is performed on the virtual nodes in the change set to generate updated real interface node segments.

[0163] Specifically, attribute analysis, structure mapping and other conversion operations are performed again on the virtual nodes in the change set to generate real interface node segments consistent with the state of the updated virtual nodes. The updated node segments are ensured to be synchronized with the latest state of the virtual nodes, the accuracy and integrity of the updating content are ensured, interface display abnormalities caused by inconsistent conversion logics are avoided, and the updating efficiency is further improved by processing only the changed nodes.

[0164] Step m7, the real interface node segments are replaced with corresponding real interface nodes in the first rendering interface to obtain the target interface.

[0165] Specifically, the generated updated real interface node segments are accurately replaced with the corresponding old real interface nodes in the first rendering interface to complete the local incremental refreshing of the interface. Only the areas that need to be changed are refreshed to avoid re-rendering of the entire interface, the updating content is seamlessly connected with the existing interface, the response speed of the interface updating is significantly improved, resource consumption and interface lag caused by full-amount redrawing are reduced, the interface smoothness in the user interaction process is ensured, and the overall user experience is optimized.

[0166] The embodiment of the application realizes initial efficient rendering and dynamic incremental updating of the interface through the process of virtual node to real node conversion, initial mounting to generate a basic interface, real-time monitoring of updating trigger conditions, accurate positioning of the update source, filtering of the minimum change set, re-conversion to generate an updating segment, and local replacement to complete incremental refreshing, improves the efficiency of interface rendering and updating, reduces system resource occupation, ensures the accuracy and smoothness of interface updating, and optimizes the user's interactive experience.

[0167] In an optional embodiment, the following steps are further included:

[0168] Step n1, monitoring the updating notification sent by the configuration center in the running process of the target interface, the updating notification including a model updating notification and a layout strategy updating notification.

[0169] Specifically, by continuously capturing the update notification issued by the configuration center during the running of the target interface, the notification type is preliminarily identified as a model update notification or a layout strategy update notification. The update linkage between the target interface and the configuration center is established, the update demand related to the interface configuration is perceived in real time, the trigger condition for starting the subsequent update process is provided, and the real-time performance of the update is ensured.

[0170] Step n2, when receiving the update notification, extracting the update type, target identifier and version number information from the update notification, the target identifier including the identification code of the model unit or the layout strategy identifier.

[0171] Specifically, by structurally analyzing the received update notification, the core information such as the update type, the target identifier and the version number is extracted from the notification content, and the object and the version attribute of the update are determined. The rapid extraction and arrangement of the update information are realized, the deviation of the subsequent operation caused by the ambiguous information is avoided, and the accuracy of the update process is improved.

[0172] Step n3, checking the version compatibility of the version number information and the target interface currently running.

[0173] Specifically, based on the preset version compatibility rule (including main version number consistency check and secondary version number compatibility range threshold judgment), the version compatibility check is performed, and by comparing whether the main version number of the update version number and the current running version number is consistent and whether the secondary version number is within the preset compatible interval, the version compatibility state is determined. The extracted update version number is compared and analyzed with the version information corresponding to the target interface currently running, the compatibility state of the two is judged, and the problems such as interface abnormality and function failure caused by version incompatibility are avoided in advance, which provides the basis for the continuation or termination of the update process. The compatible update operation is selected to ensure the stability of the update process and reduce the system failure caused by version conflict.

[0174] Step n4, if the version is incompatible, a version conflict prompt information is generated and the update process is paused.

[0175] Specifically, when the version compatibility check result is incompatible, the abnormal processing mechanism is started, the prompt content containing the conflict version information is generated, and the pause instruction of the update process is triggered. The update operation is terminated in time, and the conflict problem is fed back through the prompt information to provide the direction for subsequent problem troubleshooting and version adjustment. The interference caused by incompatible update to the running of the target interface is effectively avoided, the normal use of the current interface is ensured, and the system failure is reduced.

[0176] Step n5, if the version is compatible, performing corresponding data acquisition operation according to the update type.

[0177] Specifically, in version compatibility, according to the extracted update type, the corresponding update data acquisition logic is matched, directional data acquisition is carried out, and accurate adaptation of the acquisition operation to the update type is ensured. By explicitly specifying the acquisition path and method of the update data, resource waste caused by indiscriminate data acquisition is avoided, accurate collection of update data is realized, the efficiency of update data acquisition is improved, network overhead caused by invalid data transmission is reduced, efficient support is provided for subsequent update processing links.

[0178] Step n6, when the update type is model update, the corresponding update model unit is acquired from the configuration center based on the identification code.

[0179] Specifically, when the update type is model update, the extracted model unit identification code is used as the retrieval basis, and the corresponding update model unit is acquired through the data access interface of the configuration center, avoiding the transmission of full model data. Reduce the data transmission cost of model update, improve the pertinence and efficiency of data acquisition.

[0180] Step n7, when the update type is layout strategy update, the corresponding update layout strategy is acquired based on the layout strategy identifier.

[0181] Specifically, when the update type is layout strategy update, based on the extracted layout strategy identifier, the corresponding update layout strategy is located and acquired from the strategy resource library of the configuration center, ensuring the accuracy of strategy acquisition. Reduce the resource consumption of layout strategy update, ensure that the updated strategy can be used in subsequent interface adaptation process in time, and improve the response speed of strategy update.

[0182] Step n8, if the update type is model update, the updated model unit is parsed to generate an updated local sub-semantic tree and a responsive configuration fragment.

[0183] Specifically, by structurally analyzing the acquired update model unit, the semantic information and responsive configuration parameters therein are extracted, and an updated local sub-semantic tree and a responsive configuration fragment are generated. The updated model unit is converted into structured data that can be used for subsequent integration, providing data support for incremental update of semantic trees and responsive configuration objects.

[0184] Step n9, based on the local sub-semantic tree and the responsive configuration fragment, the semantic tree and the responsive configuration object are incrementally replaced and updated.

[0185] Specifically, based on the updated local sub-semantic tree and the responsive configuration fragment, only the corresponding area in the original semantic tree and the relevant content in the original responsive configuration object are replaced and updated, and the unchanged part is retained. The local update of the core data structure is realized, the resource waste caused by full reconstruction is avoided, the integrity and consistency of the semantic tree and the responsive configuration object are ensured, the update efficiency of the core data structure is improved, the system resource occupation is reduced, and the subsequent interface conversion process can be executed based on the latest configuration information.

[0186] Step n10, if the update type is layout strategy update, the updated layout strategy is replaced with the corresponding strategy in the preset layout strategy library, and the strategy priority order is updated.

[0187] Specifically, the updated layout strategy is used to replace the corresponding old strategy in the preset layout strategy library, and the order of the strategy library is adjusted according to the strategy priority algorithm. By updating the strategy basis of interface adaptation, it is ensured that the latest layout strategy can be used in the subsequent interface conversion process, while the order of the strategy library is maintained.

[0188] Step n11, based on the updated semantic tree and the responsive configuration object, the updated component instance set is obtained through interface conversion.

[0189] Specifically, based on the updated semantic tree and the responsive configuration object (or the updated layout strategy library), the mapping, adaptation and configuration of semantic nodes to component instances are completed, and the updated component instance set is generated. The updated core configuration is converted into a component instance that can be used for interface construction, providing input data for the update of the virtual interface node tree, ensuring that the component instance set can reflect the latest configuration changes, and ensuring the accuracy and integrity of the subsequent interface update content.

[0190] Step n12, based on the updated component instance set, the updated virtual interface node tree is constructed.

[0191] Specifically, based on the updated component instance set, the hierarchical relationship and attribute configuration of the component instance are reanalyzed, and the updated virtual interface node tree is constructed. The precise update of the virtual interface node tree is realized, and its structure and attributes meet the latest configuration requirements, which connects the core configuration update and the interface rendering update process.

[0192] Step n13, the updated virtual interface node tree is incrementally rendered and updated, and the changed area in the target interface is updated.

[0193] Specifically, the changed region is located by local analysis on the updated virtual interface node tree, and only the changed region is subjected to the conversion and replacement operation from the virtual node to the real node to complete the local interface update. The updated configuration content is converted into visual interface changes to avoid interface lag and resource waste caused by full rendering, and efficient interface update is realized. The response speed of interface update is effectively improved, the system resource consumption is reduced, the interface fluency in the user interaction process is ensured, and the interface content is ensured to be consistent with the latest configuration.

[0194] In step n14, the updated model unit, layout strategy, corresponding semantic tree and component instance set are subjected to cache updating, and the updating timestamp and version information are recorded.

[0195] Specifically, according to the preset cache management rule, the updated model unit, layout strategy, corresponding semantic tree and component instance set are updated to the cache system, and the updating timestamp and version information are recorded to form a complete updating trace record. The updating cache data can effectively ensure the efficiency of subsequent access, the updating operation is traceable through the recording of the updating information, and a basis is provided for subsequent problem troubleshooting and version rollback. The response efficiency of subsequent similar updating or access can be effectively improved, the whole process of the updating operation is traceable, and the maintainability and stability of the system are enhanced.

[0196] The embodiment of the application realizes the dynamic hot updating of the target interface in running through the processes of monitoring the updating notification, analyzing and extracting information, version compatibility verification, directional acquisition of updating data, incremental updating of the core configuration, conversion and construction of the updating node tree, incremental rendering of the interface and cache updating record, significantly improves the updating response speed and resource utilization efficiency, ensures the accuracy of interface updating and the stability of system running, and enhances the maintainability and traceability of the updating operation.

[0197] Through the description of the above implementation mode, those skilled in the art can clearly understand that the method according to the above embodiment can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better implementation mode.

[0198] Figure 2 The structure schematic diagram of the network interface dynamic configuration device provided by the embodiment of the application is shown in FIG. 1. Figure 2 As shown in FIG. 1, the embodiment of the application further provides a network interface dynamic configuration device 20, which comprises:

[0199] The obtaining module 201 is configured to obtain an interface configuration model of a current user and device characteristics of a target terminal, and the interface configuration model comprises a plurality of model units.

[0200] The parsing module 202 is configured to parse the model units of the interface configuration model respectively, construct a semantic tree by cross-unit merging and inheritance chain association, and generate a responsive configuration object, wherein the responsive configuration object is structured configuration data generated by extracting breakpoint configuration parameters of a style model and responsive style rules of a component in the model unit during the parsing of the model unit;

[0201] The conversion module 203 is configured to perform interface conversion according to the semantic tree, the responsive configuration object, device characteristics, and a preset layout strategy library, to obtain a component instance set matched with the target terminal;

[0202] The construction module 204 is configured to construct a virtual interface node tree by using the component instance set, wherein each virtual node of the virtual interface node tree corresponds to a component instance;

[0203] The rendering module 205 is configured to perform incremental rendering on the interface based on the virtual interface node tree to obtain a target interface.

[0204] In a possible design, the obtaining module 201 is specifically configured to:

[0205] obtain role permissions of a current user, business scenario requirements, and a preset interface design specification;

[0206] generate a structure model based on the role permissions, the business scenario requirements, and the preset interface design specification, wherein the structure model includes component types, hierarchical relationships, attribute parameters, and sub-node distribution information of components in the interface;

[0207] associate corresponding event response manners, condition trigger rules, and state switching logics for each component in the structure model according to a preset interaction logic rule, to generate a behavior model;

[0208] associate the components with corresponding data interface addresses, data request manners, data binding paths, and automatic loading configurations of a backend according to data requirements of the components, to construct a data model;

[0209] assign corresponding theme attributes, breakpoint configuration parameters, responsive style rules, and custom style configurations to the components based on a preset theme style specification, multi-terminal breakpoint parameters, and component style rules, to obtain a style model;

[0210] integrate the structure model, the behavior model, the data model, and the style model to obtain a model unit of the interface configuration model;

[0211] return to the step of generating the structure model based on the role permissions, the business scenario requirements, and the preset interface design specification, until a plurality of model units required for constructing the interface configuration model are obtained;

[0212] integrate the model units across units to obtain the interface configuration model.

[0213] In one possible design, the parsing module 202 is specifically used for:

[0214] Based on the component's hierarchical relationship, component type, attribute parameters, and child node distribution information, create semantic nodes corresponding to the component;

[0215] A local sub-semantic tree is created based on the mapping relationship between semantic nodes and component hierarchy;

[0216] Based on the preset root node reference rules and inheritance chain association rules, the local sub-semantic trees are merged across units to form a semantic tree;

[0217] Obtain breakpoint configuration parameters and component reactive style rules from the style model of the model unit;

[0218] The breakpoint configuration parameters are standardized to obtain the size division thresholds and priority order of multiple terminals;

[0219] The responsive style rules are categorized and associated according to the types of multiple terminals, generating a responsive configuration object that includes terminal identifiers, size thresholds, and component style mapping relationships.

[0220] In one possible design, the conversion module 203 is specifically used for:

[0221] The device features of the target terminal are parsed to generate a device feature vector;

[0222] The target layout strategy is obtained by matching the device feature vector with the preset layout strategy library. The target layout strategy includes component library identifier, layout transformation rules and style scaling parameters.

[0223] Based on the component library identifier, the corresponding component type and the mapping table of components in the library are called from the preset component library;

[0224] Based on the mapping relationship table, each semantic node of the semantic tree is mapped to the target component type;

[0225] The structure of the mapped semantic nodes is adjusted according to the responsive configuration object and layout transformation rules, including terminal adaptation transformation of container layout form, navigation mode and form layout;

[0226] Obtain the event response method, condition triggering rules, data interface address, and data binding path corresponding to the target component from the behavioral model and data model of the model unit;

[0227] The event response method, condition triggering rules, data interface address, data binding path, and style scaling parameters are associated with the corresponding target component to generate a component instance;

[0228] The component instances are arranged according to the hierarchical structure of the semantic tree to obtain a set of component instances that match the target terminal.

[0229] In one possible design, module 204 is specifically used for:

[0230] Get the component identifier, attribute configuration, and parent-child component relationship of the component instance;

[0231] Establish a hierarchical structure framework for virtual nodes based on the parent-child component relationship;

[0232] Create a corresponding virtual node for the component instance, and encapsulate the component identifier and attribute configuration of the component instance into the corresponding virtual node;

[0233] The initial virtual interface node tree is obtained by assembling the virtual nodes hierarchically according to the hierarchical structure framework.

[0234] The initial virtual interface node tree is traversed and verified to check the accuracy of the hierarchical association of virtual nodes and the completeness of attribute configuration.

[0235] If the verification fails, obtain the virtual nodes with hierarchical association errors or missing attribute configurations, and correct or supplement the virtual nodes according to the information of the component instance corresponding to the virtual node.

[0236] If the verification passes, the virtual interface node tree will be obtained.

[0237] In one possible design, rendering module 205 is specifically used for:

[0238] Convert the virtual nodes of the virtual interface node tree into corresponding real interface nodes;

[0239] Based on the hierarchical structure of the virtual interface node tree, the real interface nodes are mounted to the preset container nodes of the page to obtain the first rendered interface.

[0240] Real-time monitoring of the data interface returned by the data model corresponding to the data model in the interface configuration model and user interaction operations, to obtain data change information or interaction trigger event information;

[0241] When data change information or interaction trigger event information is detected, locate the corresponding data source association path or interaction component identifier;

[0242] Based on the data source association path or interactive component identifier, the corresponding target virtual node subset is identified in the virtual interface node tree to obtain the change set;

[0243] The virtual nodes in the change set are reprocessed to generate updated real interface node fragments;

[0244] The target interface is obtained by replacing the corresponding real interface node in the first rendered interface with the real interface node fragment.

[0245] In one possible design, an update module 206 is also included, which is specifically used for:

[0246] During the operation of the target interface, monitor the update notifications sent by the configuration center, including model update notifications and layout strategy update notifications;

[0247] When an update notification is received, the update type, target identifier, and version number information are extracted from the update notification. The target identifier includes the identifier code of the model unit or the layout strategy identifier.

[0248] Verify the compatibility of the version number information with the version of the currently running target interface;

[0249] If the versions are incompatible, a version conflict warning message will be generated and the update process will be paused;

[0250] If the versions are compatible, perform the corresponding data retrieval operation based on the update type;

[0251] When the update type is model update, the corresponding updated model unit is obtained from the configuration center based on the identifier code;

[0252] When the update type is layout strategy update, the corresponding update layout strategy is obtained based on the layout strategy identifier;

[0253] If the update type is model update, the updated model unit is parsed to generate the updated local sub-semantic tree and responsive configuration fragment;

[0254] Based on local sub-semantic trees and reactive configuration fragments, incremental replacement and updates are performed on the semantic tree and reactive configuration objects;

[0255] If the update type is layout strategy update, replace the corresponding strategy in the preset layout strategy library with the updated layout strategy and update the strategy priority sorting;

[0256] The updated set of component instances is obtained by transforming the interface based on the updated semantic tree and responsive configuration object;

[0257] Based on the updated set of component instances, construct an updated virtual interface node tree;

[0258] Incremental rendering is performed on the updated virtual interface node tree to update the changed areas in the target interface;

[0259] The updated model units, layout strategies, corresponding semantic trees, and component instance sets are cached and updated, and the update timestamp and version information are recorded.

[0260] For a description of the features in the embodiment corresponding to the network interface dynamic configuration device, please refer to the relevant description in the embodiment corresponding to the network interface dynamic configuration method, which will not be repeated here.

[0261] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 3 As shown, the electronic device 30 provided in this embodiment includes at least one processor 301 and a memory 302. Optionally, the electronic device 30 further includes a communication component 303. The processor 301, memory 302, and communication component 303 are connected via a bus.

[0262] In the specific implementation process, at least one processor 301 executes computer execution instructions stored in memory 302, causing at least one processor 301 to execute the above-described embodiment of the network interface dynamic configuration method.

[0263] The specific implementation process of processor 301 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0264] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0265] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0266] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0267] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above embodiments of the dynamic configuration method for a network interface.

[0268] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0269] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above embodiments of the dynamic configuration method for network interfaces.

[0270] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above embodiments of the network interface dynamic configuration method.

[0271] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0272] The foregoing has provided a detailed description of a dynamic configuration method for a network interface, an electronic device, a storage medium, and a program product provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for dynamic configuration of a network interface, characterized in that, The application comprises the following steps: obtaining the interface configuration model of the current user and the device characteristics of the target terminal, wherein the interface configuration model comprises multiple model units; analyzing the model units of the interface configuration model respectively, constructing a semantic tree through cross-unit merging and inheritance chain association, and generating a responsive configuration object, wherein the responsive configuration object is structured configuration data generated by extracting breakpoint configuration parameters of a style model in the model units and responsive style rules of components; performing interface conversion according to the semantic tree, the responsive configuration object, the device characteristics, and a preset layout strategy library to obtain a component instance set matched with the target terminal; constructing a virtual interface node tree through the component instance set, wherein each virtual node of the virtual interface node tree corresponds to a component instance; performing incremental rendering on the interface based on the virtual interface node tree to obtain a target interface.

2. The method of claim 1, wherein, The model units are obtained according to a preset interface function boundary division; the interface configuration model of the current user is obtained by the following steps: obtaining the role permission, business scenario demand, and preset interface design specification of the current user; generating a structure model based on the role permission, business scenario demand, and preset interface design specification, wherein the structure model comprises component types, hierarchical relationships, attribute parameters, and sub-node distribution information of components in the interface; generating a behavior model by associating corresponding event response modes, condition trigger rules, and state switching logic for each component in the structure model according to a preset interaction logic rule; associating the components with corresponding data interface addresses, data request modes, data binding paths, and automatic loading configurations of the backend according to data requirements of the components to construct a data model; allocating corresponding theme attributes, breakpoint configuration parameters, responsive style rules, and custom style configurations for the components based on a preset theme style specification, multi-terminal breakpoint parameters, and component style rules to obtain a style model; integrating the structure model, the behavior model, the data model, and the style model to obtain a model unit of the interface configuration model; returning to the step of generating a structure model based on the role permission, business scenario demand, and preset interface design specification until multiple model units required for constructing the interface configuration model are obtained; integrating the model units across units to obtain an interface configuration model.

3. The method of claim 2, wherein, The model units of the interface configuration model are analyzed respectively, and a semantic tree is constructed through cross-unit merging and inheritance chain association, and a responsive configuration object is generated, comprising the following steps: creating a semantic node corresponding to the component according to the hierarchical relationship, component type, attribute parameter, and sub-node distribution information of the component; creating a local sub-semantic tree corresponding to the model unit based on the mapping relationship between the semantic node and the component hierarchical relationship; performing cross-unit merging on the local sub-semantic tree according to a preset root node reference rule and inheritance chain association rule to form a semantic tree; obtaining breakpoint configuration parameters and responsive style rules of components from the style model of the model unit; performing standardized processing on the breakpoint configuration parameters to obtain size division thresholds and priority orders of multiple terminals; The responsive style rules are classified and associated according to the types of the terminals, and a responsive configuration object containing terminal identification, size threshold, and component style mapping relationship is generated.

4. The method of claim 1, wherein, According to the semantic tree, the responsive configuration object, the device characteristics, and the preset layout strategy library, interface conversion is performed to obtain a component instance set matched with the target terminal, including: The device characteristics of the target terminal are analyzed to generate a device characteristic vector; The device characteristic vector is matched with the preset layout strategy library to obtain a target layout strategy, which contains component library identification, layout conversion rules, and style scaling parameters; Based on the component library identification, a corresponding component type and a mapping relationship table of in-library components are called from the preset component library; According to the mapping relationship table, each semantic node of the semantic tree is mapped to a target component type; According to the responsive configuration object and the layout conversion rules, the mapped semantic nodes are structurally adjusted, including terminal adaptation conversion of container layout form, navigation mode, and form layout; From the behavior model and data model of the model unit, the event response mode, condition trigger rule, data interface address, and data binding path corresponding to the target component are obtained; The event response mode, condition trigger rule, data interface address, data binding path, and style scaling parameters are associated and configured with the corresponding target component to generate a component instance; According to the hierarchical structure of the semantic tree, the component instances are arranged to obtain a component instance set matched with the target terminal.

5. The method of claim 1, wherein, A virtual interface node tree is constructed through the component instance set, including: The component identification, attribute configuration, and parent-child component association relationship of the component instance are obtained; According to the parent-child component association relationship, a hierarchical structure framework of virtual nodes is established; The component instances are created with corresponding virtual nodes, and the component identification and attribute configuration of the component instances are encapsulated into the corresponding virtual nodes; According to the hierarchical structure framework, the virtual nodes are hierarchically assembled to obtain an initial virtual interface node tree; The initial virtual interface node tree is traversed and checked to check the hierarchical association accuracy and attribute configuration integrity of the virtual nodes; If the check fails, the virtual nodes with hierarchical association errors or missing attribute configurations are obtained, and the virtual nodes are modified or supplemented according to the information of the component instances corresponding to the virtual nodes; If the check passes, a virtual interface node tree is obtained.

6. The method of claim 1, wherein, Based on the virtual interface node tree, the interface is incrementally rendered to obtain a target interface, including: The virtual nodes of the virtual interface node tree are converted into corresponding real interface nodes; According to the hierarchical structure of the virtual interface node tree, the real interface nodes are mounted into the page preset container node to obtain a first rendering interface; Real-time monitoring of the data interface return data and user interaction operations corresponding to the data model in the interface configuration model is performed to obtain data change information or interactive trigger event information; When the data change information or interactive trigger event information is monitored, the corresponding data source association path or interactive component identification is located; Based on the data source association path or interaction component identifier, a corresponding target virtual node subset is identified in the virtual interface node tree to obtain a change set; The virtual nodes in the change set are re-converted to generate an updated real interface node segment; The real interface node segment is replaced with the corresponding real interface node in the first rendering interface to obtain a target interface.

7. The method of claim 1, wherein, Further comprising: Monitoring the update notification sent by the configuration center during the running process of the target interface, the update notification including model update notification and layout strategy update notification; When receiving the update notification, extracting the update type, target identifier and version number information from the update notification, the target identifier including the model unit identifier code or layout strategy identifier; Verifying the version number information with the version compatibility of the currently running target interface; If the versions are incompatible, generating a version conflict prompt information and pausing the update process; If the versions are compatible, performing corresponding data acquisition operations according to the update type; When the update type is model update, obtaining the corresponding updated model unit from the configuration center based on the identifier code; When the update type is layout strategy update, obtaining the corresponding updated layout strategy based on the layout strategy identifier; If the update type is model update, parsing the updated model unit to generate an updated local sub-semantic tree and a responsive configuration segment; Based on the local sub-semantic tree and the responsive configuration segment, incrementally replacing and updating the semantic tree and the responsive configuration object; If the update type is layout strategy update, replacing the updated layout strategy with the corresponding strategy in the preset layout strategy library and updating the strategy priority order; Based on the updated semantic tree and responsive configuration object, performing interface conversion to obtain an updated component instance set; Based on the updated component instance set, constructing an updated virtual interface node tree; Incrementally rendering and updating the updated virtual interface node tree to update the changed area in the target interface; Caching the updated model unit, layout strategy and corresponding semantic tree and component instance set, and recording the update timestamp and version information.

8. An electronic device, comprising: Comprise: A memory for storing a computer program; A processor for executing the computer program to implement the steps of the network interface dynamic configuration method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, wherein the computer program is executed by the processor to implement the steps of the network interface dynamic configuration method according to any one of claims 1 to 7.

10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the network interface dynamic configuration method according to any one of claims 1 to 7.

Images