Cross-domain collaborative interface dynamic configuration method and device and computer program product

Abstract

The invention discloses a cross-domain collaborative interface dynamic configuration method and device and a computer program product. According to the cross-domain collaborative interface dynamic configuration method, service flow priorities are determined by analyzing service layer data, and an initial interface configuration scheme is generated in combination with network state information. And when the initial scheme does not meet the transmission requirements, optimizing the interface parameters by adopting a dynamic programming algorithm, generating a new configuration scheme, and issuing the new configuration scheme to the target network management system. In the service switching process, network performance is monitored in real time, interface parameters are dynamically optimized and updated to a network management system, and intelligent management of service flow and efficient utilization of network resources are achieved. The method can adapt to different manufacturer devices and network levels, guarantees the service quality of cross-domain services, and improves the operation efficiency and reliability of an electric power communication network.

Description

Technical Field

[0001] The present invention relates to the technical field of power systems, and particularly to a method, device and computer program product for dynamically configuring cross-domain collaborative interfaces. Background Art

[0002] In the power dispatching systems at the provincial, municipal and district levels, each dispatching unit often uses network management systems of different manufacturers, which leads to coordination obstacles when switching between cross-level dispatching domains at the service layer and the transmission layer. Due to the differences in interface protocols, data formats and management strategies among heterogeneous network management systems, it is difficult for the upper and lower layer networks to achieve rapid adaptation and automatic distribution of service parameters, affecting the continuity and real-time performance of services. Especially at the critical moment of cross-level dispatching switching, the network management system needs to dynamically adjust the interface configuration according to the service priority and synchronize relevant parameters to the target domain in a timely manner, otherwise service interruption or service quality degradation may occur. At the same time, this real-time interface configuration mechanism also needs to consider the reasonable scheduling and optimal utilization of underlying communication resources to maximize the cross-domain coordination efficiency. However, current network management systems generally lack standard interfaces and protocol conversion mechanisms for heterogeneous environments, making it difficult to achieve seamless connection and rapid service switching between cross-level dispatching domains. Summary of the Invention

[0003] The technical problem to be solved by the embodiments of the present invention is to provide a method, device and computer program product for dynamically configuring cross-domain collaborative interfaces to achieve real-time configuration of interfaces between network management systems based on service priority, as well as rapid adaptation of upper and lower layer protocols and automatic distribution of parameters.

[0004] To solve the above technical problem, the present invention provides a method for dynamically configuring cross-domain collaborative interfaces, including:

[0005] Step S1, dynamically determining the priority based on the real-time service flow characteristics of the target service layer, and optimizing the transmission path according to the network topology level and traffic monitoring results;

[0006] Step S2, matching the quality of service parameters and resource constraint conditions according to the service flow priority, and generating an initial interface configuration scheme for cross-domain collaboration;

[0007] Step S3, obtaining the current network status information, and combining with the target traffic demand of the service flow, determining whether the initial interface configuration scheme meets the transmission requirements;

[0008] Step S4, if the initial interface configuration scheme does not meet the service transmission requirements, adjusting the interface parameters according to the priority level of the service flow and the network status information, and generating an optimized interface configuration scheme;

[0009] Step S5: Determine the target network management system according to the network topology structure and the target address, and send the optimized interface configuration scheme to the target network management system;

[0010] Step S6: Monitor the transmission performance indicators in real time. If a decrease in transmission performance is detected, re-obtain the network status information, dynamically optimize the optimized interface configuration scheme, and obtain the dynamically optimized interface configuration parameters;

[0011] Step S7: Update the pre-constructed parameter distribution module according to the dynamically optimized interface configuration parameters, and send the dynamically optimized interface configuration parameters to the corresponding network management system in real time.

[0012] Preferably, step S1 specifically includes:

[0013] Obtain the service flow identification code of the information source involved in the target service layer, extract the service type identification and the service urgency value from the service flow identification code, and compare with the preset service priority mapping rule to obtain the service flow priority identification;

[0014] Establish a mapping association table between the service flow identification code and the equipment manufacturer identification code, extract the target equipment manufacturer identification code through the service flow identification code, and perform positioning identification on the equipment network level according to the power communication network layering rule;

[0015] Establish a service flow volume monitoring reference value according to the equipment network level identification, and obtain the service flow operation status identification by comparing the real-time monitored service flow value with the service flow volume monitoring reference value;

[0016] Optimize the service flow transmission path through the service flow priority identification, and determine the optimal transmission path identification according to the network topology layering structure and the equipment network level identification.

[0017] Preferably, step S2 specifically includes:

[0018] Obtain the delay threshold and the bandwidth demand value from the preset service quality parameter library according to the service flow priority level identification, and obtain the resource scheduling identification code through the service quality parameter and resource scheduling threshold comparison table;

[0019] Query the manufacturer network management syntax rule library according to the resource scheduling identification code, and obtain the network level configuration parameters according to the preset protocol configuration specification to generate the service flow configuration instruction data;

[0020] Match according to the service flow configuration instruction data in the equipment interface comparison table, and obtain the interface configuration data through the equipment model parameters and port capacity parameters;

[0021] Retrieve the network interconnection rule library and the network topology relationship table according to the interface configuration data, and generate a cross-domain collaboration configuration plan through the cross-domain interconnection parameters and the protocol conversion rule library.

[0022] Preferably, the step S3 specifically includes:

[0023] Obtain the link bandwidth utilization value, the interface delay index value, and the packet loss count value according to the traffic monitoring collection points, and generate a link performance data set through the bandwidth utilization calculation function;

[0024] Read the historical interface traffic record table according to the link performance data set, and obtain the preset utilization threshold, the preset delay threshold, and the preset packet loss range through the bandwidth load monitoring function to obtain a performance threshold data set;

[0025] Extract the unit time bandwidth demand value, the delay tolerance value, and the packet loss tolerance value according to the performance threshold data set, and classify the link performance parameters through the support vector machine algorithm to obtain a performance evaluation data set;

[0026] If at least one index in the performance evaluation data set exceeds the preset range, generate a determination result that does not meet the service transmission requirements.

[0027] Preferably, the step S4 specifically includes:

[0028] Obtain the service priority parameter and the link load parameter in the network status record table according to the service flow identifier, and generate an initial service parameter set through the parameter synthesis function;

[0029] Perform dynamic programming algorithm processing on the initial service parameter set, and calculate the bandwidth allocation matrix through the resource constraint function to obtain a resource allocation parameter set;

[0030] Calculate the weighted shortest path according to the resource allocation parameter set, and comprehensively process the link load value and the processor utilization value through the path cost function to obtain a link optimization parameter set;

[0031] Generate a queue scheduling rule according to the link optimization parameter set, and divide the service queue bandwidth ratio value and the scheduling priority serial number value through the priority mapping function to generate an optimized interface configuration plan.

[0032] Preferably, the step S5 specifically includes:

[0033] Read the node association information from the network topology database according to the target address identifier, and match the node attribution information through the management domain range table to obtain the inter-domain scheduling permission identifier and the cross-domain routing data set;

[0034] Read the inter-domain interface table using the cross-domain routing data set, calculate the routing path from the source domain to the target domain through the topology traversal function, and obtain the path configuration rules from the inter-domain link database;

[0035] Query the management domain configuration table according to the path configuration rules, determine the target network management identifier through the management permission function, and extract the network management configuration data set from the network management configuration database;

[0036] Perform protocol conversion on the network management configuration data set, judge the protocol compatibility and parameter validity through the configuration verification function. If the configuration verification result set indicates that the configuration is compliant, generate the target configuration instruction sequence.

[0037] Preferably, the step S6 specifically includes:

[0038] Obtain the link bandwidth occupancy value, data flow rate value, and transmission performance index value according to the service switching monitoring point, calculate the bandwidth utilization rate, traffic change rate, and delay jitter rate through the performance evaluation function, and generate the performance monitoring data set;

[0039] Extract the historical performance records in the performance benchmark database according to the performance monitoring data set, calculate the performance change trend through the trend analysis function, obtain the preset threshold parameters from the performance threshold rule library, and generate the performance evaluation data set;

[0040] Match the performance evaluation data set with the network resource database, calculate the processor utilization rate, memory occupancy rate, and cache usage rate through the resource occupancy function, obtain the resource limit parameters from the resource threshold rule library, and generate the resource evaluation data set;

[0041] Input the resource evaluation data set into the random forest algorithm, calculate the bandwidth adjustment recommendation value, transmission unit adjustment recommendation value, and queue length adjustment recommendation value through the parameter prediction function, and generate the configuration update data set.

[0042] Preferably, the step S7 specifically includes:

[0043] Obtain the link parameter instruction, interface parameter instruction, and protocol parameter instruction from the configuration instruction library according to the dynamic optimization parameter set, and obtain the configuration conversion data set through the parameter conversion function;

[0044] Query the manufacturer interface rule library using the configuration conversion data set, obtain the configuration interface identifier, configuration syntax rule, and configuration effective rule through the interface matching function, and obtain the configuration syntax data set from the network management syntax library;

[0045] Perform instruction normalization processing on the configuration syntax data set, extract the instruction parameters, instruction format, and instruction sequence through the instruction analysis function, and obtain the specification instruction data set from the configuration specification library;

[0046] Query the configuration timing rule library according to the described specification instruction dataset, extract the configuration sequence and execution rules through the timing control function, and obtain the execution instruction data from the execution rule library.

[0047] The present invention also provides a cross-domain collaborative interface dynamic configuration device, including:

[0048] One or more processors;

[0049] A memory;

[0050] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the one or more processors, and the one or more applications are configured to execute the cross-domain collaborative interface dynamic configuration method described above.

[0051] The present invention also provides a computer program product, including computer instructions, and the computer instructions direct a computer device to perform the operations corresponding to the method.

[0052] Implementing the present invention has the following beneficial effects: Through the intelligent cross-domain collaborative interface dynamic configuration mechanism, the present invention significantly improves the service carrying efficiency and operation and maintenance reliability of the power communication network. First, based on the multi-dimensional feature parsing and priority dynamic mapping of the service flow identification code, combined with the network topology hierarchical rules, the intelligent optimization of the service transmission path is realized to ensure the strict service quality of high-priority services; Second, by constructing a bandwidth allocation matrix through the dynamic programming algorithm and combining the weighted path calculation of the improved Dijkstra algorithm, the optimal allocation of cross-layer resources is realized under the constraint of link resources, significantly improving the network resource utilization rate; Third, the random forest algorithm is used to predict the adjustment directions of bandwidth, MTU and queue parameters in real time, and a configuration exception rollback mechanism is established to dynamically maintain the transmission stability during the service switching process, shortening the network interruption time to the millisecond level; In addition, through the protocol conversion rule library, the cross-domain collaborative configuration of multi-vendor devices is realized, and combined with the triple verification mechanism and the three-stage effective strategy, the cross-domain interface configuration efficiency is improved and the configuration error rate is reduced. The present invention can adapt to different vendor devices and network levels, ensuring the service quality of cross-domain services, improving the operation efficiency and reliability of the power communication network, and providing strong technical support for the reliable operation of the smart grid. Description of the Drawings

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0054] Figure 1 It is a schematic flowchart of a method for dynamically configuring cross - domain collaborative interfaces in Embodiment 1 of the present invention. Specific implementation manners

[0055] The descriptions of the following embodiments refer to the accompanying drawings to exemplify specific embodiments in which the present invention can be implemented.

[0056] Please refer to Figure 1 As shown, Embodiment 1 of the present invention provides a method for dynamically configuring cross - domain collaborative interfaces, including:

[0057] Step S1, dynamically determine the priority based on the real - time service flow characteristics of the target service layer, and optimize the transmission path according to the network topology level and traffic monitoring results;

[0058] Step S2, match the quality - of - service parameters and resource constraint conditions according to the service flow priority, and generate an initial interface configuration scheme for cross - domain collaboration;

[0059] Step S3, obtain the current network status information, and combine the target traffic demand of the service flow to determine whether the initial interface configuration scheme meets the transmission requirements;

[0060] Step S4, if the initial interface configuration scheme does not meet the service transmission requirements, adjust the interface parameters according to the priority level of the service flow and the network status information, and generate an optimized interface configuration scheme;

[0061] Step S5, determine the target network management system according to the network topology structure and the target address, and send the optimized interface configuration scheme to the target network management system;

[0062] Step S6, monitor the transmission performance indicators in real - time. If a decrease in transmission performance is detected, re - obtain the network status information, dynamically optimize the optimized interface configuration scheme, and obtain the dynamically optimized interface configuration parameters;

[0063] Step S7, update the pre - constructed parameter distribution module according to the dynamically optimized interface configuration parameters, and send the dynamically optimized interface configuration parameters to the corresponding network management system in real - time.

[0064] Specifically, in the embodiment of the present invention, analyze the current service flow data of the target service layer to obtain the service type and urgency degree, determine the priority level of the service flow according to the preset priority mapping rule, and record the information source and target device information involved in the service flow at the same time. The target device information includes the device manufacturer and the power communication network level. Thus, Step S1 specifically includes:

[0065] Step S11, Dynamic determination of business flow priority: Obtain the business flow identification code of the information sources involved in the target business layer, and extract the business type identifier and business urgency value from this business flow identification code. At the same time, record the information sources and target device information involved in the business flow. The target device information includes the device manufacturer and the power communication network level.

[0066] The structure definition of the business flow identification code is as follows: The first four digits represent the business source type (production type / management type / scheduling type), the middle six digits represent the business urgency value, and the last six digits are the business processing serial number. Through the preset business priority mapping rule (when the urgency value > 800000, it is mapped to the highest priority identifier, and the priority is divided into ten levels), compare the business type identifier with the urgency value to generate the business flow priority identifier.

[0067] Step S12, Device level mapping and network location: Establish a mapping association table between the business flow identification code and the device manufacturer identifier. The table stores the corresponding relationship between the device manufacturer code (such as the specific coding format of manufacturer A / B) and the business flow identification code.

[0068] After extracting the target device manufacturer identifier through the business flow identification code, locate and identify the device network level according to the power communication network layering rule (three levels: access layer, aggregation layer, core layer). The network topology hierarchical structure is divided into provincial, municipal, and county-level nodes according to geographical location. Combine the device network level identifier to determine the business flow distribution path.

[0069] Step S13, Traffic benchmark monitoring and status evaluation: Establish a business traffic monitoring benchmark value according to the device network level identifier. The benchmark value is obtained based on historical business data statistics (the monitoring window period is 300 seconds).

[0070] Real-time monitor the business traffic value and dynamically compare it with the benchmark value: When the business traffic value exceeds 150% of the benchmark value, it is determined as an abnormal state, and a business flow operation status identifier is generated. If the business flow operation status identifier shows an abnormality, then by detecting the business traffic threshold level and resource occupancy ratio, update the business flow priority identifier according to the preset threshold rule. Resource occupancy ratio monitoring is executed synchronously, using three indicators: CPU usage rate, memory occupancy rate, and link bandwidth occupancy rate. If any indicator exceeds 75%, trigger the priority update mechanism (reduce the original priority identifier value by two levels).

[0071] Step S14, Dynamic optimization of the transmission path

[0072] Optimize the transmission path based on the business flow priority identifier: According to the network topology hierarchical structure (provincial / municipal / county node levels) and the device network level identifier (access layer / aggregation layer / core layer), use the shortest path algorithm to calculate the transmission path with the fewest hops between nodes, and generate the optimal transmission path identifier.

[0073] The business traffic allocation ratio is dynamically adjusted according to the type of business source: production - type business accounts for 60% of the total bandwidth (rate ≥ 100 Mbps), management - type accounts for 25% (rate ≥ 50 Mbps), and scheduling - type accounts for 15% (rate ≥ 80 Mbps). The threshold rule for inter - network interconnection degree sets the cross - regional transmission delay ≤ 200 ms. If the data transmission rate does not meet the threshold requirement, a service - flow transmission control identifier is generated and the bandwidth is re - allocated.

[0074] Step S15, exception handling and resource re - allocation:

[0075] When the service - flow operation status identifier is abnormal or the priority changes, a dynamic adjustment mechanism is triggered: According to the business - traffic classification rules (the business - traffic classification rules classify service - flows into three levels: high, medium, and low. The high - level service - flow threshold is 500 Mbps, the medium - level is 300 Mbps, and the low - level is 100 Mbps), network resources are re - allocated to give priority to ensuring the transmission quality of high - level service - flows. When it is detected that the service - flow priority changes, the transmission path is synchronously updated and network resources (such as CPU / memory / link - bandwidth quotas) are adjusted to ensure the continuous and stable transmission of the service - flow.

[0076] Furthermore, in the embodiments of the present invention, according to the priority level of the service - flow, the service - quality requirements and resource occupancy of the service - flow are determined, and according to the configuration syntax of different manufacturers' network management systems and the protocol configurations of different power communication network levels, the interface type and interface protocol corresponding to the service - flow are matched, and an initial interface configuration scheme including the interface information required for cross - domain collaboration is generated. Thus, step S2 specifically includes:

[0077] Step S21, service - quality parameter matching and resource - scheduling identifier generation: According to the service - flow priority - level identifier, the delay threshold and bandwidth demand value are obtained from the preset service - quality parameter library, and the resource - scheduling identification code is obtained through the service - quality parameter and resource - scheduling threshold comparison table.

[0078] Specifically, according to the service - flow priority - level identifier (such as dispatching and command - type / protection and control - type / management information - type), the delay threshold, packet - loss rate threshold, and bandwidth demand value are obtained from the preset service - quality parameter library. The specific parameter standards are:

[0079] For dispatching and command - type services, the delay ≤ 20 ms, the packet - loss rate ≤ 0.01%, and the bandwidth ≥ 10 Mbps;

[0080] For protection and control - type, the delay ≤ 4 ms, the packet - loss rate ≤ 0.001%, and the bandwidth ≥ 2 Mbps;

[0081] For management information - type, the delay ≤ 100 ms, the packet - loss rate ≤ 0.1%, and the bandwidth ≥ 1 Mbps.

[0082] Generate a resource scheduling identification code through a comparison table of service quality parameters and resource scheduling thresholds (including the upper limits of processor occupancy rate, memory occupancy rate, and link bandwidth occupancy rate).

[0083] Step S22, generating manufacturer-differentiated configuration instructions: Query the manufacturer's network management syntax rule library according to the resource scheduling identification code, obtain network layer configuration parameters based on the preset protocol configuration specifications, and generate service flow configuration instruction data.

[0084] Specifically, query the manufacturer's network management syntax rule library based on the resource scheduling identification code to adapt to the configuration syntax differences of different manufacturers' devices. For example, manufacturer A uses the command-line method for configuration (interface descriptions are digital identifiers), and manufacturer B uses the configuration unit method (interface descriptions are string identifiers). Extract network layer parameters (access layer gigabit Ethernet, aggregation layer 10-gigabit Ethernet, core layer 25G Ethernet) according to the preset protocol configuration specifications, and generate service flow configuration instruction data in combination with the resource occupancy limit values.

[0085] Step S23, matching device interface parameters: Match according to the service flow configuration instruction data in the device interface comparison table, and obtain interface configuration data through device model parameters and port capability parameters.

[0086] Specifically, match according to the service flow configuration instruction data in the device interface comparison table, and generate interface configuration data through device model parameters (port type: electrical / optical; port rate: gigabit / 10-gigabit / 25G; port mode: access mode / trunk mode) and port capability parameters. Access control parameters are restricted by source address, destination address, protocol type, and port number, and bandwidth limitation uses the token bucket algorithm (average rate = 80% of the committed bandwidth, burst rate = 120%) to achieve traffic control.

[0087] Step S24, generating cross-domain collaborative configuration: Retrieve the network interconnection rule library and network topology relationship table according to the interface configuration data, and generate a cross-domain collaborative configuration plan through cross-domain interconnection parameters and protocol conversion rule library.

[0088] Specifically, retrieve the network interconnection rule library (including inter-domain routing protocol, link bandwidth configuration, security policy) and network topology relationship table (device connection relationship and link attributes) based on the interface configuration data to generate cross-domain interface configuration data. Implement cross-vendor device interconnection through the protocol conversion rule library, specifically including: message header conversion (protocol version mapping), message body conversion (data format adaptation), control field conversion (QoS marking compatibility). Finally, generate a cross-domain collaborative configuration plan including static routes (fixed paths) and dynamic routes (fault backup paths), and issue configuration instructions to each device to complete service configuration.

[0089] Further, in the embodiments of the present invention, obtaining the current network status information, including link bandwidth utilization, interface delay, and interface packet loss rate, and combining with the target traffic requirements of the service flow, to determine whether the initial interface configuration scheme meets the service transmission requirements. If the link bandwidth utilization is higher than the preset utilization threshold, the interface delay exceeds the preset delay threshold, or the interface packet loss rate is higher than the preset packet loss range, then it does not meet the service transmission requirements. Thus, step S3 specifically includes:

[0090] Step S31, network status data collection and processing: Obtain the link bandwidth utilization value, interface delay index value, and packet loss count value according to the traffic monitoring collection points, and generate a link performance data set through the bandwidth utilization calculation function.

[0091] Specifically, the monitoring points are set according to the service traffic distribution: 1 collection point is set every 10 kilometers in the core network area, and 1 collection point is set every 5 kilometers in the access network area. The collection point statistically calculates the link bandwidth utilization every 5 minutes (triggering an alarm when it exceeds 85%), the interface delay is measured by bidirectional time delay (the detection period is 1 minute, and it is recorded when the one-way time delay > 10 ms), and the packet loss rate is detected through the packet sequence number (with a counting period of every 100 packets). A link performance data set is generated through the bandwidth utilization calculation function, delay index calculation function, and packet loss rate calculation function.

[0092] Step S32, historical threshold extraction and performance classification: Read the historical interface traffic record table according to the link performance data set, and obtain the preset utilization threshold, preset delay threshold, and preset packet loss range through the bandwidth load monitoring function to obtain the performance threshold data set.

[0093] Specifically, read the historical interface traffic record table (storing data for the recent 30 days, with a sampling point every 5 minutes), extract the preset utilization threshold (backbone link 75%, aggregation link 80%, access link 85%), preset delay threshold (real-time service ≤ 4 ms, interactive service ≤ 20 ms, ordinary service ≤ 100 ms), and preset packet loss range (real-time service ≤ 0.001%, interactive service ≤ 0.01%, ordinary service ≤ 0.1%) to generate the performance threshold data set. Combine the target traffic requirements record table to extract the bandwidth demand value per unit time, delay tolerance value, and packet loss tolerance value, and classify the link performance parameters using the support vector machine algorithm (Gaussian kernel function, feature dimension: bandwidth utilization / interface delay / packet loss rate), and divide the link status into three categories: normal, warning, and congestion.

[0094] Step S33, link status evaluation and determination: Extract the bandwidth demand value per unit time, delay tolerance value, and packet loss tolerance value according to the performance threshold data set, and classify the link performance parameters through the support vector machine algorithm to obtain the performance evaluation data set.

[0095] Specifically, compare the performance evaluation data set with the performance threshold data set, and use the threshold comparison function to determine whether the bandwidth utilization rate, interface latency, and packet loss rate exceed the limit, generating a performance over-limit data set. Calculate the link congestion index:

[0096] Real-time service weight: bandwidth 0.3 / latency 0.4 / packet loss 0.3;

[0097] Interactive service weight: bandwidth 0.4 / latency 0.3 / packet loss 0.3;

[0098] Ordinary service weight: bandwidth 0.5 / latency 0.2 / packet loss 0.3).

[0099] Divide the link load level according to the index value (light load < 0.6, medium load 0.6 - 0.8, heavy load 0.8 - 1.0, overloaded > 1.0). If any index exceeds the limit, combined with the monitoring results of the interface resource occupancy function (processor / memory / cache occupancy rate > 90% determines resource tension), generate a determination result of service transmission requirements.

[0100] Step S34, compliance decision of the configuration plan: If at least one index in the performance evaluation data set exceeds the preset range, generate a determination result that does not meet the service transmission requirements.

[0101] Specifically, when the performance over-limit data set shows that the bandwidth utilization rate, latency, or packet loss rate exceeds the preset range, and the link load level reaches heavy load or overloaded, it is determined that the initial interface configuration plan does not meet the service transmission requirements. At the same time, if the interface resource occupancy function monitors that any one of the three indicators of processor utilization rate, memory utilization rate, and cache occupancy rate exceeds 90%, it is determined that the interface resources are tense. Even if the link load level does not reach the threshold, a determination result that the configuration plan does not meet the requirements is still triggered.

[0102] Furthermore, if the initial interface configuration plan does not meet the service transmission requirements, then according to the priority level of the service flow and the network status information, adjust the interface bandwidth and packet size parameters through the dynamic programming algorithm according to the configuration constraints of different vendor network management systems, generating an optimized interface configuration plan. The plan includes the adjusted interface bandwidth, packet size, and queue scheduling strategy. Thus, step S4 specifically includes:

[0103] Step S41, service parameter synthesis and resource allocation: Obtain the service priority parameter and the link load parameter in the network status record table according to the service flow identifier, and generate an initial service parameter set through the parameter synthesis function.

[0104] Specifically, obtain service priority parameters (dispatching and command class = 1, protection and control class = 2, management information class = 3), bandwidth demand parameters (dispatching class 10 Mbps / protection class 2 Mbps / management class 1 Mbps), and packet size parameters (dispatching class 128 bytes / protection class 256 bytes / management class 512 bytes) according to the service flow identifier. Combine the link load parameters (bandwidth utilization / delay / packet loss rate), processor utilization parameters, and cache occupancy parameters in the network status record table, and generate an initial service parameter set through a parameter synthesis function.

[0105] Step S42, optimize bandwidth allocation using the dynamic programming algorithm: Perform dynamic programming algorithm processing on the initial service parameter set, and calculate the bandwidth allocation matrix through a resource constraint function to obtain a resource allocation parameter set.

[0106] Specifically, use the dynamic programming algorithm to construct a bandwidth allocation matrix. The rows of the matrix represent different priority services (3 classes), the columns represent the available bandwidth values (with an upper limit of 80% of the link physical bandwidth), and the matrix elements record the benefit values of the allocation scheme. Limit the packet size adjustment range (64 - 1500 bytes) and queue priority adjustment interval (1 - 8 levels) through a resource constraint function to generate a resource allocation parameter set.

[0107] Step S43, calculate the weighted path and optimize the link: Calculate the weighted shortest path according to the resource allocation parameter set, and comprehensively process the link load value and processor utilization value through a path cost function to obtain a link optimization parameter set.

[0108] Specifically, based on the resource allocation parameter set, use the improved Dijkstra algorithm to calculate the weighted shortest path. The path cost function combines the link load value (weight 0.4), processor utilization (weight 0.3), and cache occupancy rate (weight 0.3) to generate a link optimization parameter set.

[0109] Step S44, generate queue scheduling rules and adapt to the manufacturer: Generate queue scheduling rules according to the link optimization parameter set, and divide the bandwidth ratio value and scheduling priority serial number value of the service queue through a priority mapping function to generate an optimized interface configuration scheme.

[0110] Among them, generate queue scheduling rules according to the link optimization parameter set:

[0111] Priority mapping: Service priority 1 → queue 1 (strict priority, accounting for 40% of the bandwidth), priority 2 → queue 2 (weighted round-robin, accounting for 30%), priority 3 → queue 3 (weighted round-robin, accounting for 30%).

[0112] Manufacturer Configuration Adaptation: Extract parameter rules from the manufacturer's network management configuration library through a configuration syntax parsing function (such as the command line format "bandwidth number kbps" of manufacturer A and the XML format of manufacturer B), and generate a device configuration script. The syntax conversion function converts the unified intermediate format into manufacturer-specific instructions, and generates the final interface configuration scheme after verifying the compliance of parameters (range / conflict check).

[0113] Furthermore, in the embodiment of the present invention, according to the network topology structure and the preset management scope of the network management system, a cross-domain scheduling mechanism is preset, and according to the target address carried by the service flow and the network topology information, the target network management system is determined, and the optimized interface configuration scheme is sent to the target network management system to trigger the interface protocol adaptation module to complete the matching of the link layer and network layer protocols and the configuration of interface parameters. Therefore, step S5 specifically includes:

[0114] Step S51, Cross-Domain Routing Path Calculation: Read node association information from the network topology database according to the target address identifier, match the node attribution information through the management domain scope table, and obtain the inter-domain scheduling permission identifier and the cross-domain routing data set.

[0115] Specifically, read node association information (physical link type, bandwidth, delay) from the network topology database according to the service flow target address identifier (6-bit province / city / county code, such as "Province 02, City 05, County 03"), match the node attribution information through the management domain scope table, obtain the inter-domain scheduling permission identifier (full permission / partial permission / read-only permission) from the cross-domain scheduling rule library, and generate a cross-domain routing data set. Use the cross-domain routing data set to read the inter-domain interface table (recording the source domain identifier, target domain identifier, interface physical address, and protocol type), calculate the shortest path from the source domain to the target domain through the breadth-first search algorithm, and extract the path configuration rules (routing protocol configuration, security policy configuration, bandwidth limit configuration) from the inter-domain link database to generate a cross-domain link data set.

[0116] Step S52, Target Network Management System Identification and Configuration Extraction: Use the cross-domain routing data set to read the inter-domain interface table, calculate the routing path from the source domain to the target domain through the topology traversal function, and obtain the path configuration rules from the inter-domain link database.

[0117] Specifically, query the management domain configuration table (including domain level, domain scope, and management permissions) based on the cross-domain link dataset, and determine the target network management identifier (8-digit number, the first 4 digits are the management domain number + the last 4 digits are the network management node number) through the management permission function. Extract the configuration rules from the network management configuration database to generate a network management configuration dataset. The protocol adaptation rule table defines the protocol mapping rules for devices of different manufacturers: link layer parameters (MAC address format, VLAN tag, traffic control method) and network layer parameters (IP format, routing protocol type, QoS marking method). Extract the protocol parameters through the adaptation mapping function to generate a protocol adaptation dataset.

[0118] Step S53, protocol conversion and configuration verification: Query the management domain configuration table according to the path configuration rules, determine the target network management identifier through the management permission function, and extract the network management configuration dataset from the network management configuration database.

[0119] Specifically, perform protocol conversion on the interface configuration scheme and the protocol adaptation dataset, and generate the target interface configuration instruction through the protocol parameter mapping table (recording the corresponding relationship between parameters of different protocol versions). The configuration instruction specification table defines the configuration command format (such as CLI / XML), the parameter value range, and the execution order. Perform triple compliance checks using the standardized configuration dataset:

[0120] Protocol compatibility: Verify whether the protocol versions of the source and target devices match;

[0121] Parameter validity: Check whether the configuration parameters are within the allowed range (such as bandwidth ≤ 80% of the physical link);

[0122] Permission compliance: Determine whether the operation exceeds the inter-domain scheduling permission.

[0123] If the verification passes, generate a target configuration instruction sequence; if it fails, trigger the rollback mechanism.

[0124] Step S54, configuration instruction issuance and execution: Perform protocol conversion on the network management configuration dataset, and judge the protocol compatibility and parameter validity through the configuration verification function. If the configuration verification result set indicates that the configuration is compliant, generate a target configuration instruction sequence.

[0125] Specifically, the configuration instruction sequence is arranged according to the preset execution order (basic configuration → extended configuration → associated configuration), and the trigger condition (time trigger / event trigger / manual trigger) is determined through the scheduling trigger table. The time trigger is set during the off-peak business period, the event trigger is based on the network performance monitoring results (such as latency exceeding the threshold), and the manual trigger is started by the operation and maintenance personnel's instructions. The verified configuration instructions are issued to the target network management node to complete the interface parameter configuration and protocol adaptation (such as MAC address conversion, QoS marking synchronization).

[0126] Further, during the service switching process, the link bandwidth occupancy and the interface data stream rate are monitored in real time. If it is detected that the service transmission performance deteriorates, the network status information is retrieved again, and the interface configuration parameters are dynamically optimized in combination with the optimized interface configuration scheme. The interface configuration parameters include bandwidth, maximum transmission unit, and queue length. Accordingly, step S6 specifically includes:

[0127] Step S61, transmission performance monitoring and data set generation: According to the service switching monitoring points, obtain the link bandwidth occupancy value, data stream rate value, and transmission performance index value. Calculate the bandwidth utilization rate, traffic change rate, and delay jitter rate through the performance evaluation function, and generate a performance monitoring data set. Extract the historical performance records in the performance benchmark database according to the performance monitoring data set, calculate the performance change trend through the trend analysis function, and obtain the preset threshold parameters from the performance threshold rule library to generate a performance evaluation data set.

[0128] Specifically, the link bandwidth occupancy value (sampled every 5 minutes, warning triggered when the utilization rate > 85%), data stream rate value (recording events when the sudden increase exceeds 80% of the interface rated bandwidth), and transmission performance index (abnormal marked when the delay > 10ms / packet loss rate > 0.1% / jitter > 5ms) are collected in real time through the service switching monitoring points. Calculate the bandwidth utilization rate, traffic change rate, and delay jitter rate through the performance evaluation function to generate a performance monitoring data set. The performance benchmark database stores the historical performance data of the past 30 days (baseline value per hour), calculates the performance change trend using the moving average method, and obtains the differential warning threshold from the performance threshold rule library (triggered when the performance of the dispatching and command class drops by 5% / protection and control class drops by 3% / management information class drops by 10%) to generate a performance evaluation data set.

[0129] Step S62: Resource status evaluation and parameter prediction: Match the performance evaluation data set with the network resource database, calculate the processor utilization rate, memory occupancy rate, and cache usage rate through the resource occupancy function, and obtain the resource limit parameters from the resource threshold rule library to generate a resource evaluation data set.

[0130] Specifically, match the performance evaluation data set with the network resource database, monitor the processor utilization rate (> 80% warning), memory occupancy rate (> 75% warning), and cache usage rate (> 70% warning) through the resource occupancy function to generate a resource evaluation data set. The resource threshold rule library sets the resource limit parameters (such as CPU usage rate ≤ 90%). Input the resource evaluation data set into the random forest algorithm (input features: performance trend / resource status / service traffic characteristics; output: bandwidth adjustment value / MTU adjustment value / queue length adjustment value) to predict parameter adjustment suggestions:

[0131] Bandwidth adjustment: The amplitude ≤ 20% of the current value

[0132] MTU Adjustment: 64 - 1500 byte range

[0133] Queue length: 100 - 1000 packet range.

[0134] Step S63, Configuration Update and Execution Verification: Input the resource evaluation data set into the random forest algorithm, calculate the bandwidth adjustment recommendation value, transmission unit adjustment recommendation value, and queue length adjustment recommendation value through the parameter prediction function, and generate a configuration update data set.

[0135] Specifically, read the configuration constraint rule library according to the parameter adjustment recommendation, judge the compliance through the parameter verification function (such as bandwidth ≤ 80% of the physical link), and generate a configuration update data set. The configuration instruction sequence is generated in a fixed order (bandwidth → MTU → queue length), and the format and permission compliance are checked through the instruction verification function. The execution monitoring function records the configuration distribution process (time consumption / result). If performance deterioration (decrease > 20%), resource exhaustion (any index > 90%), or configuration conflict (parameters are incompatible) is detected, trigger the rollback mechanism: revoke the instructions in the reverse order and restore to the state before the update.

[0136] Furthermore, according to the dynamically optimized interface configuration parameters, the embodiment of the present invention updates the pre - constructed parameter distribution module. The parameter distribution module selects the configuration method according to the configuration interfaces of different vendor network management systems, and distributes the updated interface parameters to the corresponding network management systems in real time through a preset script. Thus, step S7 specifically includes:

[0137] Step S71, Parameter Conversion and Vendor Adaptation: Obtain the link parameter instruction, interface parameter instruction, and protocol parameter instruction from the configuration instruction library according to the dynamically optimized parameter set, and obtain the configuration conversion data set through the parameter conversion function.

[0138] Specifically, obtain the link parameters (bandwidth / delay threshold / jitter threshold), interface parameters (MTU / cache depth / queue length), and protocol parameters (protocol type / version / options) from the configuration instruction library according to the dynamically optimized parameter set, and map the vendor - specific rules through the parameter conversion function. For example: Vendor A maps "bandwidth" to "bw" (CLI command - line format), and Vendor B converts the bandwidth unit to kilobits per second (XML configuration unit format). After generating the configuration conversion data set, query the vendor interface rule library to obtain the configuration interface identifier (8 - character, format: 2 - digit device type+4 - digit device number+2 - digit interface number), configuration syntax rule (Ethernet interface CLI / SDH interface configuration unit / PDH interface message mode), and effective rule (take effect immediately / take effect at a scheduled time / take effect under conditions), and form a configuration syntax data set.

[0139] Step S72, Instruction Standardization and Timing Control: Query the manufacturer interface rule library using the configuration conversion data set, obtain the configuration interface identifier, configuration syntax rules, and configuration effectiveness rules through the interface matching function, and obtain the configuration syntax data set from the network management syntax library.

[0140] Specifically, perform instruction standardization processing on the configuration syntax data set: Instruction parameters are described using key-value pairs, and the instruction format includes an instruction header (operation type), an instruction body (parameter list), and an instruction tail (check code). Extract the instruction sequence through the instruction analysis function and sort it according to the configuration dependency relationship (basic configuration → extended configuration → associated configuration). Query the configuration timing rule library and use the timing control function to generate an execution sequence (such as configuring the bandwidth first and then adjusting the MTU) to generate a standardized instruction data set.

[0141] Step S73, Parameter Verification and Script Generation: Perform instruction standardization processing on the configuration syntax data set, extract instruction parameters, instruction formats, and instruction sequences through the instruction analysis function, and obtain the standardized instruction data set from the configuration specification library.

[0142] Specifically, perform triple checks through the parameter verification function:

[0143] Syntax Verification: Determine whether the instruction format conforms to the manufacturer's specifications (such as the CLI instruction header format);

[0144] Value Verification: Verify whether the parameter is within the allowable range (such as bandwidth ≤ 80% of the physical link);

[0145] Association Verification: Check the dependency relationship between parameters (such as the queue length matching the cache depth).

[0146] After passing the verification, extract the template from the script template library (header description / variable definition / execution command / result processing), and generate a manufacturer-adapted configuration script using the template replacement method (such as replacing "bw = 1000kbps" with the script of manufacturer A).

[0147] Step S74, Configuration Delivery and Exception Rollback: Query the configuration timing rule library according to the standardized instruction data set, extract the configuration order and execution rules through the timing control function, and obtain the execution instruction data set from the execution rule library.

[0148] Specifically, issue configuration instructions according to the trigger conditions (time / event / manual trigger) of the execution rule library, and record the delivery time, duration, and result through the execution monitoring function. If an exception is detected (performance degradation > 20% / resource exhaustion / configuration conflict), trigger the rollback mechanism:

[0149] Rollback Trigger: Extract the rollback conditions and operation sequences according to the rollback rule library;

[0150] Instruction revocation: Roll back in the reverse order of the configured instructions (e.g., first revoke the queue length configuration and then restore the bandwidth).

[0151] Status restoration: The rollback verification rule ensures that the parameters are restored to the state before the update.

[0152] Corresponding to the cross-domain collaborative interface dynamic configuration method described in the foregoing Embodiment 1 of the present invention, Embodiment 2 of the present invention further provides a cross-domain collaborative interface dynamic configuration device, including:

[0153] One or more processors;

[0154] A memory;

[0155] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the one or more processors, and the one or more applications are configured to execute the cross-domain collaborative interface dynamic configuration method described in the foregoing Embodiment 1 of the present invention.

[0156] Corresponding to the cross-domain collaborative interface dynamic configuration method described in the foregoing Embodiment 1 of the present invention, Embodiment 3 of the present invention further provides a computer program product, including computer instructions, and the computer instructions direct a computer device to perform operations corresponding to the cross-domain collaborative interface dynamic configuration method described in the foregoing Embodiment 1 of the present invention.

[0157] Preferably, the processor may be a Central Processing Unit (CPU), or may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may also be any conventional processor. The processor is the control center of the device and connects various parts of the device through various interfaces and lines.

[0158] The memory mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function, etc., and the data storage area can store relevant data, etc. In addition, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a SmartMedia Card (SMC), a Secure Digital (SD) card, a Flash Card, etc., or the memory can also be other volatile solid-state storage devices.

[0159] It should be noted that the above device may include but is not limited to a processor and a memory, which can be understood by those skilled in the art.

[0160] Regarding the working principle and process of the above embodiments, refer to the description of Embodiment 1 of the present invention above, and details will not be repeated here.

[0161] It can be seen from the above description that compared with the prior art, the beneficial effects of the present invention are as follows: Through the intelligent cross-domain collaborative interface dynamic configuration mechanism, the present invention significantly improves the service carrying efficiency and operation and maintenance reliability of the power communication network. First, based on the multi-dimensional feature parsing and priority dynamic mapping of the service flow identification code, combined with the network topology hierarchical rules, the intelligent optimization of the service transmission path is realized to ensure the strict service quality of high-priority services; Second, by constructing a bandwidth allocation matrix through the dynamic programming algorithm and combining the weighted path calculation of the improved Dijkstra algorithm, the optimal allocation of cross-layer resources is realized under the constraint of link resources, significantly improving the network resource utilization rate; Third, the random forest algorithm is used to predict the adjustment direction of bandwidth, MTU and queue parameters in real time, and a configuration exception rollback mechanism is established to dynamically maintain the transmission stability during the service switching process, shortening the network interruption time to the millisecond level; In addition, through the protocol conversion rule library, the cross-domain collaborative configuration of multi-vendor devices is realized, combined with the triple verification mechanism and the three-stage effective strategy, improving the cross-domain interface configuration efficiency and reducing the configuration error rate. The present invention can adapt to different vendor devices and network levels, ensuring the service quality of cross-domain services, improving the operation efficiency and reliability of the power communication network, and providing strong technical support for the reliable operation of the smart grid.

[0162] The above-disclosed are only the preferred embodiments of the present invention, and of course, the scope of the rights of the present invention cannot be limited thereby. Therefore, equivalent changes made according to the claims of the present invention still fall within the scope covered by the present invention.

Claims

1. A cross-domain collaborative interface dynamic configuration method, characterized in that, Including: Step S1: Dynamically determine the priority based on the real-time service flow characteristics of the target service layer, and optimize the transmission path according to the network topology hierarchy and traffic monitoring results; Step S2: Match the quality of service parameters and resource constraint conditions according to the service flow priority, and generate an initial interface configuration plan for cross-domain collaboration; Step S3: Obtain the current network status information, and combine it with the target traffic demand of the service flow to determine whether the initial interface configuration plan meets the transmission requirements; Step S4: If the initial interface configuration plan does not meet the service transmission requirements, adjust the interface parameters according to the priority level of the service flow and the network status information, and generate an optimized interface configuration plan; Step S5: Determine the target network management system according to the network topology structure and the target address, and send the optimized interface configuration plan to the target network management system; Step S6: Real-time monitor the transmission performance indicators. If a decrease in transmission performance is detected, re-obtain the network status information, dynamically optimize the optimized interface configuration plan, and obtain the dynamically optimized interface configuration parameters; Step S7: Update the pre-constructed parameter distribution module according to the dynamically optimized interface configuration parameters, and send the dynamically optimized interface configuration parameters to the corresponding network management system in real time.

2. The method according to claim 1, wherein The specific content of step S1 includes: Obtain the service flow identification code of the information source involved in the target service layer, extract the service type identification and service urgency value from the service flow identification code, and compare with the preset service priority mapping rule to obtain the service flow priority identification; Establish a mapping association table between the service flow identification code and the device manufacturer identification. Extract the target device manufacturer identification through the service flow identification code, and perform positioning identification on the device network level according to the power communication network layering rule; Establish a service traffic monitoring reference value according to the device network level identification, and obtain the service flow operation status identification by comparing the real-time monitored service traffic value with the service traffic monitoring reference value; Optimize the service flow transmission path through the service flow priority identification, and determine the optimal transmission path identification according to the network topology hierarchical structure and the device network level identification.

3. The method according to claim 1, wherein The specific content of step S2 includes: Obtain the delay threshold and bandwidth demand value from the preset quality of service parameter library according to the service flow priority level identification, and obtain the resource scheduling identification code through the quality of service parameter and resource scheduling threshold comparison table; Query the manufacturer network management syntax rule library according to the resource scheduling identification code, and obtain the network level configuration parameters according to the preset protocol configuration specification to generate the service flow configuration instruction data; Match according to the service flow configuration instruction data in the device interface comparison table, and obtain the interface configuration data through the device model parameter and port capacity parameter; Retrieve the network interconnection rule library and the network topology relationship table according to the interface configuration data, and generate a cross-domain collaboration configuration plan through the cross-domain interconnection parameter and the protocol conversion rule library.

4. The method according to claim 1, wherein The specific content of step S3 includes: Obtain the link bandwidth utilization rate value, interface delay index value and packet loss count value according to the traffic monitoring collection point, and generate a link performance data set through the bandwidth utilization rate calculation function; Read the historical interface traffic record table according to the link performance data set, and obtain the preset utilization threshold, preset delay threshold, and preset packet loss range through the bandwidth load monitoring function to obtain the performance threshold data set; Extract the unit time bandwidth demand value, delay tolerance value, and packet loss tolerance value according to the performance threshold data set, and classify the link performance parameters through the support vector machine algorithm to obtain the performance evaluation data set; If at least one index in the performance evaluation data set exceeds the preset range, generate a determination result that does not meet the service transmission requirements.

5. The method according to claim 1, wherein The specific steps of step S4 include: Obtain the service priority parameter and the link load parameter in the network status record table according to the service flow identifier, and generate the initial service parameter set through the parameter synthesis function; Perform dynamic programming algorithm processing on the initial service parameter set, and calculate the bandwidth allocation matrix through the resource constraint function to obtain the resource allocation parameter set; Calculate the weighted shortest path according to the resource allocation parameter set, and comprehensively process the link load value and the processor utilization value through the path cost function to obtain the link optimization parameter set; Generate the queue scheduling rule according to the link optimization parameter set, and divide the service queue bandwidth ratio value and the scheduling priority serial number value through the priority mapping function to generate the optimized interface configuration scheme.

6. The method according to claim 1, wherein The specific steps of step S5 include: Read the node association information from the network topology database according to the target address identifier, and match the node attribution information through the management domain range table to obtain the inter-domain scheduling permission identifier and the cross-domain routing data set; Read the inter-domain interface table using the cross-domain routing data set, calculate the routing path from the source domain to the target domain through the topology traversal function, and obtain the path configuration rule from the inter-domain link database; Query the management domain configuration table according to the path configuration rule, determine the target network management identifier through the management permission function, and extract the network management configuration data set from the network management configuration database; Perform protocol conversion on the network management configuration data set, and judge the protocol compatibility and parameter validity through the configuration verification function. If the configuration verification result set indicates that the configuration is compliant, generate the target configuration instruction sequence.

7. The method according to claim 1, wherein The specific steps of step S6 include: Obtain the link bandwidth occupancy value, data flow rate value, and transmission performance index value according to the service handover monitoring point, and calculate the bandwidth utilization rate, traffic change rate, and delay jitter rate through the performance evaluation function to generate the performance monitoring data set; Extract the historical performance records in the performance benchmark database according to the performance monitoring data set, calculate the performance change trend through the trend analysis function, and obtain the preset threshold parameters from the performance threshold rule library to generate the performance evaluation data set; Match the performance evaluation data set with the network resource database, calculate the processor utilization rate, memory occupancy rate, and cache usage rate through the resource occupancy function, and obtain the resource limit parameters from the resource threshold rule library to generate the resource evaluation data set; Input the resource evaluation data set into the random forest algorithm, and calculate the bandwidth adjustment suggestion value, transmission unit adjustment suggestion value, and queue length adjustment suggestion value through the parameter prediction function to generate the configuration update data set.

8. The method according to claim 1, wherein The specific steps of step S7 include: Obtain link parameter instructions, interface parameter instructions, and protocol parameter instructions from the configuration instruction library according to the dynamic optimization parameter set, and obtain the configuration conversion data set through the parameter conversion function; Query the manufacturer interface rule library using the configuration conversion data set, obtain the configuration interface identifier, configuration syntax rules, and configuration effective rules through the interface matching function, and obtain the configuration syntax data set from the network management syntax library; Perform instruction normalization processing on the configuration syntax data set, extract instruction parameters, instruction formats, and instruction sequences through the instruction analysis function, and obtain the specification instruction data set from the configuration specification library; Query the configuration timing rule library according to the specification instruction data set, extract the configuration order and execution rules through the timing control function, and obtain the execution instruction data from the execution rule library.

9. A cross-domain collaborative interface dynamic configuration device, characterized in that Comprising: One or more processors; A memory; One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the one or more processors, and the one or more applications are configured to execute the cross-domain collaborative interface dynamic configuration method according to any one of claims 1 to 8.

10. A computer program product, characterized in that, Comprising computer instructions, the computer instructions instructing the computer device to perform the operations corresponding to the method according to any one of claims 1 to 8.

Images