Link monitoring large screen display method and device, equipment and medium

Abstract

The invention relates to the technical field of data display, can be applied to business system platforms of financial science and technology, medical health and the like, and discloses a link monitoring large screen display method, device, equipment and medium, the method comprises the following steps: obtaining a plurality of visual components, performing component configuration on the plurality of visual components, and obtaining an initial configuration component library; obtaining component attributes of the initial configuration component library, and performing incremental updating on the component attributes to obtain component change attributes; obtaining an incremental component according to the component change attribute, performing component updating on the initial configuration component library by using the incremental component to obtain a target visual component library, and constructing a link monitoring large screen according to the target visual component library; obtaining link topology data, and performing link topology rendering on the link topology data to obtain target link data; and performing visual display on the target link data on the link monitoring large screen to obtain a data display result. According to the invention, high configurability and modularization of the link monitoring large screen can be realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data display, and in particular to a link monitoring large screen display method, device, equipment and medium. BACKGROUND

[0002] With the increasing complexity of Internet applications, distributed systems and microservice architectures have become mainstream, and system link monitoring is particularly important for ensuring service stability and availability. Link monitoring large screen, as an important form of link monitoring, not only reflects the health status of system links in real time, but also helps operation and maintenance personnel quickly locate abnormalities and optimize system performance.

[0003] Most existing link monitoring large screens are developed by customization or integrated with third-party visualization tools, which have many problems. First, the link monitoring visualization large screen of each project often needs to be developed according to specific business scenarios and data structures, resulting in long development cycles, high maintenance costs, and difficulty in realizing component-level reuse. Second, the existing large screen visualization lacks flexible updating capabilities in link topology, alarm display, and other dimensions, making it difficult to meet the needs of different businesses for differentiation and dynamic adjustment. Finally, for real-time rendering and interaction of large-scale link data, existing components often have performance bottlenecks or insufficient interaction design, affecting the user experience and practical value of the monitoring large screen.

[0004] For example, in the medical health field, the link monitoring large screen is a comprehensive visualization platform that integrates key link information from various distributed systems and microservice architectures in hospitals, such as data generated by integrating different electronic medical record systems, telemedicine platforms, and medical image storage and transmission systems (PACS). These systems may come from different vendors, and their data interfaces and calling logic are different. Traditional techniques require separate development of link monitoring large screens for each system, resulting in long development cycles and difficulty in quickly responding to business changes. At the same time, in the telemedicine platform, if a new department or new service is added, the link topology needs to be updated in real time, but existing technologies often do not support such dynamic adjustments, making it difficult for operation and maintenance personnel to intuitively understand the overall picture of system links and increasing the difficulty of troubleshooting.

[0005] For example, in the financial technology business field, the link monitoring large screen integrates payment components, credit approval components, risk management components, etc., and the link monitoring large screen needs to reflect key indicators such as transaction volume, success rate, and response time of each service component in real time. However, traditional techniques cannot achieve component-level reuse, resulting in wasted development resources. At the same time, business rules and processing flows in the financial field may need to be adjusted frequently, resulting in changes in link topology and monitoring requirements. Traditional techniques lack dynamic adjustment capabilities and are difficult to quickly adapt to link changes.

[0006] Therefore, how to efficiently implement high configurability and componentization of link monitoring large screens has become a problem to be solved. SUMMARY

[0007] The application provides a link monitoring large-screen display method, device, equipment and medium, which mainly aims to solve the problem of non-configurability and non-componentization of the link monitoring large screen.

[0008] In a first aspect, to achieve the above object, the application provides a link monitoring large-screen display method, which comprises the following steps: obtaining a plurality of visualization components, performing component configuration on the plurality of visualization components to obtain an initial configuration component library; obtaining component attributes of the initial configuration component library, performing incremental updating on the component attributes to obtain component change attributes; obtaining incremental components according to the component change attributes, performing component updating on the initial configuration component library by using the incremental components to obtain a target visualization component library, and constructing a link monitoring large screen according to the target visualization component library; obtaining link topology data, performing link topology rendering on the link topology data to obtain target link data; performing visual display of the target link data on the link monitoring large screen to obtain a data display result.

[0009] In a second aspect, the application further provides a link monitoring large-screen display device, which comprises: a component configuration module, configured to obtain a plurality of visualization components, perform component configuration on the plurality of visualization components to obtain an initial configuration component library; a component updating module, configured to obtain component attributes of the initial configuration component library, perform incremental updating on the component attributes to obtain component change attributes; a large-screen construction module, configured to obtain incremental components according to the component change attributes, perform component updating on the initial configuration component library by using the incremental components to obtain a target visualization component library, and construct a link monitoring large screen according to the target visualization component library; a topology rendering module, configured to obtain link topology data, perform link topology rendering on the link topology data to obtain target link data; a visual display module, configured to perform visual display of the target link data on the link monitoring large screen to obtain a data display result.

[0010] In a third aspect, the application further provides an electronic device, which comprises: at least one processor; and a memory connected with the at least one processor in communication; wherein The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the link monitoring large-screen display method described above.

[0011] In a fourth aspect, the application further provides a computer readable storage medium, wherein at least one computer program is stored in the computer readable storage medium, and the at least one computer program is executed by a processor in an electronic device to implement the link monitoring large-screen display method described above.

[0012] In the embodiment of the application, the unique identifier allocation ensures that each component has a globally unique identifier, avoids naming conflicts, and stores the component metadata and entity files in the registry center to realize centralized management and reduce maintenance costs. Through the incremental update mechanism, only the target attribute field is modified to avoid full replacement of the component configuration, significantly reduce system resource consumption, improve update efficiency, and ensure that the update request complies with the component specification and security policy through the legality verification link to prevent system crashes or data leakage caused by illegal operations. Through field mapping, data cleaning and unit conversion, data consistency is ensured, and through grid layout, responsive design and drag-and-drop tools, flexible layout of components is realized. Through attribute mapping and layout algorithms, data is converted into visual elements to improve data readability and practicality. The large-screen area division realizes the logicalization and modularization of data display, facilitates users to quickly locate key information, ensures the accuracy and consistency of data display, and realizes real-time updating and efficient interaction of data through dynamic loading, event binding and performance optimization. Users can quickly obtain link status and in-depth analysis, and realize high configurability and componentization of the link monitoring large screen. BRIEF DESCRIPTION OF DRAWINGS

[0013] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the application. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0014] Figure 1 An application environment diagram of a link monitoring large-screen display method in an embodiment of the application; Figure 2 A flowchart of a link monitoring large-screen display method provided by an embodiment of the application; Figure 3 A flowchart of constructing a link monitoring large screen according to a target visual component library provided by an embodiment of the application; Figure 4A module schematic diagram of a link monitoring large-screen display device provided by an embodiment of the present application is provided. Figure 5 A structure schematic diagram of an electronic device for implementing a link monitoring large-screen display method provided by an embodiment of the present application is provided. Figure 6 Another structure schematic diagram of an electronic device for implementing a link monitoring large-screen display method provided by an embodiment of the present application is provided.

[0015] The purposes, functional features and advantages of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0016] In order to make the person skilled in the art better understand the technical solutions of the present disclosure, and to fully understand and implement the implementation process of the present disclosure how to apply technical means to solve technical problems and achieve corresponding technical effects, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, not all embodiments. The embodiments of the present disclosure and each feature in the embodiments can be combined with each other without conflict, and the technical solutions formed thereby are all within the protection scope of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative labor shall fall within the scope of protection of the present disclosure.

[0017] It should be noted that the terms "first", "second" and the like in the specification and claims of the present disclosure and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present disclosure described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, device, product or apparatus that includes a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or apparatus.

[0018] The execution subject of the link monitoring large screen display method includes, but is not limited to, at least one of electronic devices capable of being configured to execute the device provided in the embodiments of the present application, such as a server and a terminal. In other words, the link monitoring large screen display method can be executed by software or hardware installed in a terminal device or a server device. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster. The server can be a stand-alone server or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content distribution networks (CDN), and basic cloud computing services such as big data and artificial intelligence platforms.

[0019] The link monitoring large screen display method provided in the embodiments of the present application can be applied in an application environment as shown in Figure 1 . In the application environment, a client communicates with a server through a network. The server can obtain a plurality of visual components and component attributes through the client, and assign a unique identifier to ensure that each component has a globally unique identifier, avoid naming conflicts, and store component metadata and entity files in a registration center to realize centralized management and reduce maintenance costs. Through an incremental update mechanism, only the target attribute field is modified to avoid replacing the component configuration in full, significantly reduce system resource consumption, improve update efficiency, and ensure that the update request complies with the component specification and security policy to prevent system crashes or data leaks caused by illegal operations. Through field mapping, data cleaning, and unit conversion, data consistency is ensured, and through grid layout, responsive design, and drag-and-drop tools, flexible layout of components is realized. Through attribute mapping and layout algorithms, data is converted into visual elements to improve data readability and practicality. The large screen area division realizes the logicalization and modularization of data display, facilitates users to quickly locate key information, ensures the accuracy and consistency of data display, and realizes real-time updating and efficient interaction of data through dynamic loading, event binding, and performance optimization. Users can quickly obtain link status and in-depth analysis, realize high configurability and componentization of the link monitoring large screen, and finally output the data display result to the client for feedback. The client can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by a stand-alone server or a server cluster composed of multiple servers. The present application will be described in detail below through specific embodiments.

[0020] Referring to Figure 2 , a flowchart of a link monitoring large screen display method provided in an embodiment of the present application is shown. In the embodiment, the link monitoring large screen display method includes: S1, acquire a plurality of visualization components, component configuration is carried out on the plurality of visualization components, and an initial configuration component library is obtained.

[0021] In the embodiment of the application, the visualization component is a software module or code unit designed to realize data visualization, which usually presents data characteristics and laws in a graphical manner, covering types such as charts (such as column chart, line chart, pie chart), maps, dashboards, etc.

[0022] In the embodiment of the application, the code file (such as JavaScript library) of the open source visualization library can be introduced to directly call the pre-defined component interface to obtain the related visualization component; or the commercial software can be subscribed or purchased to utilize the provided visualization component library and development tools; or the visualization component can be implemented from zero based on the front-end framework (such as React, Vue) or graphics library (such as Three.js).

[0023] Exemplarily, in the medical health scene, the types of visualization components include resource monitoring components for displaying the use of wards, the occupancy rate and maintenance status of equipment (such as CT machines, ventilators, etc.) in real time; personnel scheduling components for showing the work arrangement, duty table and workload of medical staff to assist managers in optimizing scheduling; financial monitoring components for updating the income, expenditure and cost data of the hospital in real time to support budget adjustment and financial risk warning.

[0024] Specifically, commercial tools can be used to support multi-dimensional data analysis and visualization, which are suitable for hospital resource management, patient data analysis, etc.; support column chart, line chart, map, etc., which are suitable for trend analysis and geographical distribution display of medical data.

[0025] Exemplarily, in the financial technology scene, the types of visualization components include sales performance analysis components for displaying sales data of different products and regions to support trend analysis and comparison; customer analysis components for analyzing customer behavior, preference and risk level to support precision marketing and risk management; market risk monitoring components for real-time display of market fluctuations and investment portfolio performance to support risk warning and strategy adjustment.

[0026] Specifically, open source libraries can be used to integrate related visualization components, which are applied to create basic financial data charts (such as line chart, column chart), support multiple chart types and interactive functions, and are suitable for advanced visualization of financial data; three-dimensional financial business visualization management tools can also be developed based on front-end frameworks and graphics libraries to support the state monitoring and operation and maintenance management of devices such as outlets, vaults and ATMs.

[0027] In the embodiment of the application, the component configuration on the plurality of visualization components to obtain the initial configuration component library comprises: Assigning a unique identifier to each of the plurality of visualization components to generate component identification information; Format checking the visualization components according to the component identification information to obtain a candidate component set; Extracting metadata from each component in the candidate component set to obtain a component metadata set; Building a corresponding component index according to the component metadata set, associating the component metadata set with the corresponding candidate component set using the component index, and storing the associated candidate component in a preset component registry center; Adjusting the component layout of the components stored in the component registry center to obtain an initial configuration component library.

[0028] In detail, a unique identifier is generated for each visualization component to ensure the uniqueness and traceability of the component. A 128-bit unique identifier can be generated for each component using a UUID generation algorithm (such as UUIDv4) to ensure uniqueness across systems and environments. A composite identifier is generated by combining component type, version number, developer information, etc. to facilitate classification and management.

[0029] Specifically, a UUID can be generated using a programming language built-in library (such as the uuid module of Python), and the mapping relationship between the identifier and the component is stored through a configuration file or a database field to generate component identification information.

[0030] In the embodiments of the present application, it is verified whether the component conforms to the preset registration specification to ensure the compatibility and integrability of the component, the metadata structure (such as name, version, dependency, interface definition, etc.) and format requirements (such as JSONSchema) of the component are defined, and a format checking tool library is used to check whether the component metadata conforms to the Schema definition, or the component code is analyzed through AST (Abstract Syntax Tree) to check whether it conforms to the coding specification.

[0031] Specifically, by reading the component metadata file (such as component.json), the verification tool is used to check whether the metadata field is complete and the type is correct, and the components that pass the verification are added to the candidate set, otherwise the error log is recorded to obtain the candidate component set (the list of components that pass the verification).

[0032] In detail, key information is extracted from the candidate components to facilitate subsequent indexing and retrieval. The metadata includes component name, version, description, dependency, supported interaction mode (such as click, drag), data format requirement, etc. The metadata is extracted by parsing the component configuration file (such as JSON, YAML), and the component attributes are extracted through the reflection mechanism at runtime.

[0033] Among them, the extracted metadata set is standardized, including unified metadata format (such as converting all dates to ISO 8601 standard).

[0034] In detail, the association relationship between metadata and components is established, supporting fast retrieval and dynamic loading, creating indexes for metadata fields in relational databases (such as MySQL) or NoSQL databases, using Redis to store the mapping relationship between component ID and metadata, and storing component files and metadata files in a unified directory structure.

[0035] Specifically, the component layout adjustment aims to optimize the display and interaction of components in the initial configuration component library; components can be displayed in groups according to component types (such as charts, maps) and functions (such as analysis, monitoring), or sorted according to usage frequency and importance to obtain an initial configuration component library (a set of components that users can directly use).

[0036] In the embodiment of the application, through unique identifier allocation, it is ensured that each component has a globally unique identifier, avoiding naming conflicts and facilitating version management and problem tracking; format verification based on preset specifications can detect component defects (such as interface mismatch, missing dependencies) in advance, reducing runtime errors; after indexing the extracted metadata (such as component type, function label), fast retrieval is supported; storing component metadata and entity files in the registry center for centralized management reduces maintenance costs.

[0037] S2, obtain the component attribute of the initial configuration component library, and perform incremental update on the component attribute to obtain a component changed attribute.

[0038] In the embodiment of the application, the component attribute refers to a parameter set describing the characteristics, behaviors and functions of the visual component, used to define the appearance, interaction mode, data input / output requirements, etc. of the component.

[0039] Among them, the basic attribute includes component name, version, type (such as chart, map), developer information, the function attribute includes supported interaction mode (such as click, zoom), data format requirement (such as JSON, CSV), rendering performance index (such as loading time), the business attribute includes applicable scene (such as medical monitoring, financial analysis), associated business rule (such as data permission control).

[0040] In the embodiment of the application, the purpose of obtaining the component attribute is to realize dynamic configuration, automatic testing and system integration of the component, which can extract attribute information by parsing metadata in component configuration files or code; read and parse files using built-in libraries of programming languages; also can dynamically obtain attributes at runtime through the API or interface provided by the component; efficient acquisition and management of component attributes can be realized, providing support for system integration, dynamic configuration and performance optimization.

[0041] For example, in a medical health system, visualization components are used to display patient data, medical device monitoring information, etc., which need to meet high precision, real-time and compliance requirements. Component attributes are obtained to achieve dynamic configuration, data validation and compliance verification.

[0042] For example, a patient vital sign monitoring component displays real-time patient heart rate, blood pressure, blood oxygen, etc. The component attribute is obtained by file parsing of the component configuration file. Specifically, the json module of Python is used to parse the file, extract relevant attributes, and perform data validation to ensure that the component complies with medical data privacy regulations.

[0043] For example, a medical device status monitoring component displays the running status and alarm information of medical devices (such as ventilators and monitors). The component attribute is stored in the Nacos configuration center, the alarm threshold of the component is dynamically updated, and the monitoring interface of the corresponding device is dynamically loaded. When the ventilator pressure exceeds 30, the component automatically triggers an alarm and displays the alarm history record. The nurse station can view the status of all devices in real time and quickly locate the faulty device.

[0044] For example, in a financial technology system, visualization components are used to display transaction data, risk indicators, etc., which need to meet high security, real-time and scalability requirements. Component attributes are obtained to achieve dynamic risk control, data encryption and performance optimization.

[0045] For example, a real-time transaction monitoring component is used to display real-time stock, foreign exchange, etc. transaction data, and supports transaction risk early warning. The JSON file is parsed using the Jackson library of Java to extract relevant component attributes for risk control rule configuration to ensure that data transmission complies with security standards.

[0046] In the embodiment of the application, the component attribute is incrementally updated to obtain a component change attribute, comprising: An attribute increment request is obtained, the attribute increment request is parsed to obtain a set of to-be-updated attribute identifiers and a set of to-be-updated attribute change values; The set of to-be-updated attribute identifiers is subjected to legality verification to obtain a set of valid change attribute identifiers; A set of to-be-updated attribute key-value pairs is generated according to the set of valid change attribute identifiers; A target attribute field is determined according to the set of to-be-updated attribute key-value pairs, and the target attribute field is incrementally updated according to the set of to-be-updated attribute change values to obtain a component change attribute.

[0047] In detail, the attribute identifier to be updated and the change value are extracted from the external request, and an incremental update request (such as a PUT or PATCH request) of the client is received through a request receiving tool; in a distributed system, the incremental update request is received through a message queue such as Kafka; and the request body is parsed into an object by using a JSON parsing library.

[0048] Specifically, the attribute identifier to be updated and the change value of the attribute to be updated are extracted from the parsed object, a set of attribute identifiers to be updated and a set of change values of attributes to be updated are formed, and it is ensured that the attribute identifier to be updated is a legal attribute supported by the component.

[0049] The white list check can be used, that is, a pre-defined attribute list is maintained, the set of attribute identifiers to be updated is traversed, and it is checked whether each identifier exists in the white list, and whether the current user has the permission to update some attributes.

[0050] The data type check can also be performed, that is, the format of the attribute value is verified through a regular expression, so that a set of valid change attribute identifiers is output, the valid attribute identifiers and the change values are organized as key-value pairs, and subsequent updating is facilitated.

[0051] Specifically, a hash table is used to store the mapping relationship between the attribute identifier and the change value, and the attribute identifier is converted according to the type to output a set of attribute key-value pairs to be updated.

[0052] In detail, the attribute field of the component is updated according to the set of key-value pairs, the attribute field of the component class is obtained through reflection at runtime, if the component attribute is stored in a database, the field is updated using an ORM framework; the value of the target field can be directly replaced (which is suitable for most scenarios), for complex attributes (such as nested objects), the new and old values are merged (such as updating a field in a nested object), and an updated component attribute set is obtained.

[0053] In the embodiment of the application, through the incremental update mechanism, only the target attribute field is modified, full replacement of the component configuration is avoided, system resource consumption (such as CPU and memory occupation) is significantly reduced, and the update efficiency is improved; the legality verification link ensures that the update request conforms to the component specification and the security policy, and prevents system crashes or data leakage caused by illegal operations; the dynamic generation of the key-value pair set supports flexible expansion of new attributes, without the need to modify the underlying code, and high configurability is achieved.

[0054] S3, according to the component change attribute, an incremental component is obtained, the initial configuration component library is updated by using the incremental component, a target visual component library is obtained, and a link monitoring large screen is constructed according to the target visual component library.

[0055] In the embodiment of the application, component instances are dynamically generated or updated according to component change attributes, while resource consumption and system overhead are minimized; by analyzing component change attributes (such as adding fields and modifying configurations), component instances are dynamically generated or updated.

[0056] Specifically, component fields are located and modified according to attribute identification at runtime without recompiling codes, new dependencies (such as data sources and service interfaces) are dynamically injected according to change attributes by using a framework such as Spring, and different component instances, i.e., incremental components, are generated according to change attributes by a factory class.

[0057] In the embodiment of the application, the initial configuration component library is updated by using the incremental components to obtain a target visual component library, which includes the following steps. A component interface protocol is determined according to the incremental components. Component dependency analysis is performed on the incremental components to obtain a component dependency graph. According to the component dependency graph, component integration processing is performed on the initial configuration component library by using the component interface protocol to obtain an intermediate state component library. The intermediate state component library is tested for inter-component compatibility to obtain a target visual component library.

[0058] In detail, the interaction mode of the incremental component and other components in the component library is determined to ensure interface compatibility, a component interface is defined by using a standard protocol such as API to ensure that the communication mode of the incremental component and existing components is consistent, or an interface document is generated by using a tool such as OpenAPI to clearly define the input and output parameters, data format, and calling mode of the interface.

[0059] A version number (such as v1.0 and v2.0) is assigned to the component interface to ensure that the interface version of the incremental component is compatible with other components in the component library, and a Mock tool is used to simulate interface calling to verify whether the interface of the incremental component meets the expectation.

[0060] Specifically, the dependency relationship between the incremental component and other components is determined to avoid integration failure due to missing dependencies, a tool such as SonarQube can be used to analyze the code dependency of the component to extract dependent libraries, modules, or other components, or an APM (application performance monitoring) tool can be used to monitor the calling relationship of the component to identify dynamic dependencies.

[0061] The application can use a graph database such as Neo4j to store component dependency relationships to form a visual dependency graph to clearly determine the direct and indirect dependencies of each component; according to the interface protocol and the dependency relationship, the incremental component is integrated into the initial configuration component library to form an intermediate state.

[0062] In detail, the incremental component is integrated into the component library as a plug-in, and the component is dynamically loaded and unloaded through a plug-in manager; in the micro-service architecture, the incremental component is registered in the service grid through service registration such as Eureka, and the dependencies required by the incremental component are automatically injected according to a dependency graph using a framework such as Spring.

[0063] Specifically, the compatibility of each component in the intermediate state component library is verified to ensure the stability and availability of the target visual component library; the compatibility test types include functional compatibility test, performance compatibility test and data compatibility test, the functional compatibility test is used to verify whether the functional interaction between components meets the expectation (such as whether the incremental component correctly calls the interface of other components); the performance compatibility test verifies whether the performance of the integrated component meets the requirements through load testing such as JMeter; the data compatibility test verifies whether the data format and transmission method between components are consistent (such as JSON, XML).

[0064] Among them, the compatibility problems found in the test can be recorded and tracked by tools such as Jira, test reports can be generated, the compatibility status between components (such as pass, fail, warning) can be displayed, the intermediate state component library that passes the compatibility test can be marked as the target visual component library, and can be published to the production environment.

[0065] The application ensures the compatibility between components through standardized protocols and version control, avoids dependency conflicts through static and dynamic analysis tools to build a dependency graph, realizes the dynamic integration of incremental components through plug-in architecture, dependency injection and configuration management, verifies the compatibility between components through automated testing tools and CI / CD processes, and ensures the stability of the target component library.

[0066] As shown in Figure 3 In the embodiment of the application, the link monitoring large screen is constructed according to the target visual component library, which includes: Obtaining link monitoring data, performing data normalization processing on the link monitoring data to obtain target link data; Data binding between the target link data and each target visual component in the target visual component library is performed to obtain a target binding component; A component rendering engine is obtained, and the target binding component is laid out and arranged according to the component rendering engine to generate an initial link monitoring large screen view; The initial link monitoring large screen video is subjected to data connectivity test to obtain a test result; According to the test result, the initial link monitoring large screen view is optimized to obtain a target link monitoring large screen.

[0067] In detail, different sources and formats of link monitoring data are uniformly processed to ensure data consistency and availability. Link monitoring data is collected from multiple systems (such as microservices, databases, and network devices) using tools such as Fluentd, and is processed in real time using stream processing frameworks such as Flink to avoid data delays.

[0068] A unified field mapping rule is defined to ensure consistency of field names from different data sources, and data cleaning is performed on link monitoring data to remove duplicate data, null values, or abnormal values (such as negative delay times). A rule engine (such as Drools) or regular expressions is used for data cleaning.

[0069] In detail, the normalized link data is associated with the visualization component to ensure that the component can correctly display the data. According to the data requirements of the component (such as the timestamp and value fields required by the line chart), the fields of the link data are mapped to the input fields of the component. Configuration files (such as YAML, JSON) or visualization interfaces (such as panel configuration in Grafana) are used to dynamically bind data and components. Ensure that the link data types (such as integers, floating-point numbers, and strings) match the input types of the component (such as numerical types for dashboard components), and adjust the display range of the component (such as the Y-axis range of the line chart) to ensure that the data is within the visualization range of the component.

[0070] Specifically, the bound components are laid out according to requirements to generate an interactive link monitoring large-screen view. Front-end frameworks can be used to render components to support dynamic loading and updating, and visualization libraries can be integrated to provide a variety of chart types (such as topology graphs and heat maps).

[0071] Among them, layout techniques can be used to arrange components in a grid or row and column, and media queries (Media Query) or adaptive layouts can be used to ensure that the large screen displays normally at different resolutions. Visualization drag-and-drop tools are provided to allow users to customize component positions, and layout configurations are used to dynamically generate HTML / CSS to render the initial link monitoring large-screen view.

[0072] In detail, verify whether the components in the large-screen view can correctly obtain and display link data to ensure data connectivity. Check the configuration files of the components (such as data source URLs and query statements) to ensure that they are correct. Use simulated data requests (such as MockServer) or actual data sources to verify whether the components can correctly obtain data. Specifically, use tools such as Selenium to simulate user operations and check whether the components update data. Use logs (such as browser console logs and backend service logs) to locate data connectivity issues.

[0073] Among them, check whether the component displays all expected data fields, and verify whether the component can update data in real time (such as refreshing every 5 seconds). To ensure data accuracy and consistency.

[0074] In detail, according to the test results, optimize the large screen view, improve performance, availability and user experience, implement pagination loading for large data components (such as tables), reduce rendering pressure, implement lazy loading for non-critical components (such as detail panels), improve initial loading speed, use browser cache or Redis cache frequently accessed data, reduce data request times.

[0075] In the embodiment of the application, the data consistency is ensured by field mapping, data cleaning and unit conversion, the link data and the visualization component are associated by field mapping and dynamic binding, the flexible layout of the component is realized by grid layout, responsive design and drag-and-drop tool, the data acquisition and display ability of the component is verified by static and dynamic testing, and the quality of the link monitoring large screen is improved by performance optimization, availability optimization and user experience optimization.

[0076] S4, acquiring link topology data, performing link topology rendering on the link topology data to obtain target link data.

[0077] In the embodiment of the application, the method for rendering the link topology data includes data cleaning, generating node positions and connection paths by visualization mapping, constructing an initial topology graph, and obtaining target link data by icon identification processing.

[0078] In the embodiment of the application, the link topology rendering on the link topology data to obtain target link data includes: performing data cleaning on the link topology data to obtain standard link topology data; performing visualization mapping on the standard link topology data according to a preset rendering strategy to obtain link node positions and link connection paths; generating an initial link topology graph according to the link node positions and the link connection paths; performing icon identification processing on the initial link topology graph to obtain target link data.

[0079] In detail, the data cleaning is performed on the link topology data to remove noise and abnormalities in the link topology data, so as to ensure data quality, repeated link topology data is identified and deleted by a hash algorithm or rule matching (such as the same node ID), missing link attributes (such as delay time) are filled by using mean, median or adjacent node data, and abnormal values (such as negative delay time) are identified by Z-Score, IQR (interquartile range) and the like.

[0080] Specifically, the cleaned link topology data is converted into visual elements (nodes and connection paths), and the attributes of the link nodes (such as ID, type, and state) are mapped to visual attributes (such as color, shape, and size).

[0081] For example, the node types (such as servers and databases) are mapped to different colors (red for servers and blue for databases).

[0082] Among them, the node positions can be automatically calculated using algorithms such as force-directed layout, the node positions can be adjusted according to business requirements (such as core nodes being displayed in the center), and the attributes of the link connections (such as delay and bandwidth) can be mapped to visual attributes (such as line width and color depth).

[0083] For example, high-delay connection paths are mapped to red thick lines, and low-delay paths are mapped to green thin lines.

[0084] In detail, the mapped nodes and connection paths are combined into an initial visual topology graph, the nodes and connection paths are rendered through graph rendering technology, and interactive support is provided, the drag function allows the user to drag the nodes to adjust the topology graph layout, the zoom function supports zooming in and out of the topology graph to facilitate viewing details or the overall structure, and the rendering overhead is reduced.

[0085] Specifically, the initial topology graph is optimized and labeled, text labels (such as node ID and IP address) are added to the nodes to facilitate user identification, icons (such as warning icons indicating abnormal nodes) are overlaid on the nodes, arrows are added to the connection paths to indicate data flow direction, and colors or animations (such as flashing) are used to identify connection states (such as normal, congested, and interrupted); the optimized topology graph data is exported in a standard format (such as JSON and SVG) for subsequent use or storage.

[0086] In the embodiments of the present application, data quality is ensured through deduplication, missing value filling, and outlier detection, data is converted into visual elements (nodes and connection paths) through attribute mapping and layout algorithms, an initial topology graph is generated through a graphics library and interactive functions, and the readability and practicality of the topology graph are optimized.

[0087] S5, visualizing the target link data on the link monitoring large screen to obtain a data display result.

[0088] In the embodiments of the present application, the large screen area is divided, the data dimensions are matched with the display area, and the final data display result is generated through interactive enhancement processing.

[0089] In the embodiments of the present application, the visualizing of the target link data on the link monitoring large screen to obtain a data display result comprises: The link monitoring large screen is divided into a large screen area to obtain a plurality of visual display areas; According to the target link data and the visual display area, a target display area corresponding to each data dimension is determined; A visual configuration item of the target display area is obtained, and the target link data is interactively enhanced according to the visual configuration item to obtain a data display result.

[0090] In detail, the link monitoring large screen is divided into a plurality of logical areas to classify and display link data of different dimensions. Layout technology is used to divide the large screen into uniform grid areas (such as 2x2, 3x3 grid), the large screen is divided into functional areas (such as "core node monitoring area", "link delay analysis area", "alarm information display area") according to business requirements, and media query (Media Query) or adaptive layout technology is used to ensure that the area division is reasonable under different resolutions.

[0091] Specifically, link data of different dimensions is allocated to appropriate large screen areas to ensure the logicality and consistency of data display. According to the attributes of link data (such as node state, delay time, bandwidth utilization), classification is performed, and the display priority of each data dimension is determined through business rules (such as core node priority display).

[0092] The application uses a rule engine (such as Drools) to allocate data to areas according to predefined rules (such as "data with delay time > 100ms is displayed in the alarm area"), and dynamically maps data dimensions and display areas through configuration files or visualization tools.

[0093] In detail, the interactivity and visualization effect of data are enhanced through configuration items to improve user experience. According to the characteristics of the data, appropriate chart types (such as line chart, column chart, topology chart) are selected, interactive functions (such as clicking on a node to expand details, zooming, filtering) are defined, and color, font, animation and other style attributes are configured to enhance the visual effect.

[0094] In the embodiment of the application, the large screen area division realizes the logicalization and modularization of data display, which facilitates users to quickly locate key information. The intelligent matching of data dimensions and display areas ensures the accuracy and consistency of data display. Interactive enhancement processing realizes real-time updating and efficient interaction of data through dynamic loading, event binding and performance optimization. Users can quickly obtain link status and in-depth analysis, and realize high configurability and componentization of the link monitoring large screen.

[0095] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution. The execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiment of the application.

[0096] As Figure 4 shown, is an embodiment of the present application provides a kind of link monitoring large screen display device function module diagram.

[0097] In the present disclosure embodiment, a kind of link monitoring large screen display device is provided, and the link monitoring large screen display device described above is one-to-one correspondence with the link monitoring large screen display method of above embodiment.As Figure 4 As shown in the figure, the link monitoring large screen display device 100 can be installed in electronic equipment, according to the function realized, the link monitoring large screen display device 100 includes component configuration module 101, component update module 102, large screen construction module 103, topology rendering module 104 and visualization display module 105.According to the function realized, the link monitoring large screen display device 100 includes component configuration module 101, component update module 102, large screen construction module 103, topology rendering module 104 and visualization display module 105.The detailed description of each function module is as follows: Component configuration module, for obtaining a plurality of visualization components, component configuration is carried out to the plurality of visualization components, and the initial configuration component library is obtained; Component update module, for obtaining the component attribute of the initial configuration component library, the component attribute is incrementally updated, and the component change attribute is obtained; Large screen construction module, for obtaining the incremental component according to the component change attribute, the initial configuration component library is updated by using the incremental component, and the target visualization component library is obtained, and the link monitoring large screen is constructed according to the target visualization component library; Topology rendering module, for obtaining link topology data, link topology rendering is carried out to the link topology data, and the target link data is obtained; Visualization display module, for visualizing the target link data on the link monitoring large screen, and obtaining data display result.

[0098] In an embodiment, when the component configuration module 101 is executed to the plurality of visualization components, the initial configuration component library is obtained, for: A plurality of the visualization components are uniquely identified and assigned, and component identification information is generated; According to the component identification information, the visualization components are format checked, and a candidate component set is obtained; Metadata extraction is carried out to each component in the candidate component set, and a component metadata set is obtained; According to the component metadata set, the corresponding component index is constructed, the component metadata set is associated with the corresponding candidate component set by using the component index, and the associated candidate component is stored in the preset component registration center; The component layout adjustment is carried out to the component stored in the component registration center, and the initial configuration component library is obtained.

[0099] In an embodiment, the component update module 102, when performing incremental update on the component attributes to obtain component changed attributes, is configured to: obtain an attribute increment request, parse the attribute increment request to obtain a set of to-be-updated attribute identifiers and a set of to-be-updated attribute changed values; perform legality verification on the set of to-be-updated attribute identifiers to obtain a set of valid changed attribute identifiers; generate a set of to-be-updated attribute key-value pairs according to the set of valid changed attribute identifiers; determine a target attribute field according to the set of to-be-updated attribute key-value pairs, and perform incremental update on the target attribute field according to the set of to-be-updated attribute changed values to obtain component changed attributes.

[0100] In an embodiment, the large-screen construction module 103, when performing component update on the initial configuration component library by using the incremental component to obtain a target visual component library, is configured to: determine a component interface protocol according to the incremental component; perform component dependency analysis on the incremental component to obtain a component dependency graph; perform component integration processing on the initial configuration component library by using the component interface protocol according to the component dependency graph to obtain an intermediate state component library; perform inter-component compatibility testing on the intermediate state component library to obtain a target visual component library.

[0101] In an embodiment, the large-screen construction module 103, when constructing a link monitoring large screen according to the target visual component library, is configured to: obtain link monitoring data, and perform data normalization processing on the link monitoring data to obtain target link data; perform data binding between the target link data and each target visual component in the target visual component library to obtain a target binding component; obtain a component rendering engine, and perform layout arrangement on the target binding component according to the component rendering engine to generate an initial link monitoring large screen view; perform data connectivity testing on the initial link monitoring large screen view to obtain a test result; perform large screen optimization on the initial link monitoring large screen view according to the test result to obtain a target link monitoring large screen.

[0102] In an embodiment, the topology rendering module 104, when performing link topology rendering on the link topology data to obtain target link data, is configured to: perform data cleaning on the link topology data to obtain standard link topology data; According to a preset rendering strategy, the standard link topology data is visually mapped to obtain link node positions and link connection paths; An initial link topology graph is generated according to the link node positions and the link connection paths. The initial link topology graph is subjected to graph identification processing to obtain target link data.

[0103] In an embodiment, the visual display module 105, when performing visual display of the target link data on the link monitoring large screen to obtain data display results, is configured to: The link monitoring large screen is subjected to large screen region division to obtain a plurality of visual display regions; According to the target link data and the visual display regions, target display regions corresponding to each data dimension are determined; Visual configuration items of the target display regions are obtained, and the target link data is subjected to interactive enhancement processing according to the visual configuration items to obtain data display results.

[0104] In the present application, specific limitations of the link monitoring large screen display device can be referred to the limitations of the link monitoring large screen display method in the foregoing, and will not be repeated here. Each module in the link monitoring large screen display device described above can be realized by software, hardware and combinations thereof, in whole or in part. Each module described above can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to each module.

[0105] In one embodiment, a computer device is provided, which can be a server, and an internal structure diagram thereof can be as shown in Figure 5 The computer device includes a processor, a memory, a network interface and a database connected through a system bus. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium, an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is configured to communicate with an external client through a network connection. The computer program is executed by the processor to implement the functions or steps of the link monitoring large screen display method server side.

[0106] In one embodiment, a computer device is provided, which can be a client, and an internal structure diagram thereof can be as shown in Figure 6As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with the external server through the network connection. The computer program is executed by the processor to realize the functions or steps of the client side of the link monitoring large screen display method.

[0107] In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the computer program to implement the following steps: Obtaining a plurality of visualization components, performing component configuration on the plurality of visualization components to obtain an initial configuration component library; Obtaining component attributes of the initial configuration component library, performing incremental updating on the component attributes to obtain component change attributes; According to the component change attributes, obtaining incremental components, using the incremental components to update the initial configuration component library to obtain a target visualization component library, and constructing a link monitoring large screen according to the target visualization component library; Obtaining link topology data, performing link topology rendering on the link topology data to obtain target link data; Visualizing the target link data on the link monitoring large screen to obtain a data display result.

[0108] In several embodiments provided by the present application, it should be understood that the disclosed devices and apparatuses can be implemented in other ways. For example, the above-described system embodiments are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, another division manner can be adopted.

[0109] In addition, each functional module in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically independently, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware, or in the form of hardware plus software functional module.

[0110] Therefore, embodiments should be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are intended to be embraced therein. No reference is intended to be made to any disclaimer, unless the following language appear in the claims: "except as claimed...

[0111] In some embodiments of the present embodiment, a computer readable storage medium is provided, and a computer program is stored on the computer readable storage medium, wherein the computer program is executed by a processor to implement the steps of the method described in the above embodiment.

[0112] The readable storage medium described in the present application stores a computer program, and the computer program can implement the following when executed by a processor of an electronic device: Obtain a plurality of visualization components, perform component configuration on the plurality of visualization components to obtain an initial configuration component library; Obtain component attributes of the initial configuration component library, perform incremental updating on the component attributes to obtain component change attributes; According to the component change attributes, obtain incremental components, perform component updating on the initial configuration component library by using the incremental components to obtain a target visualization component library, and construct a link monitoring large screen according to the target visualization component library; Obtain link topology data, perform link topology rendering on the link topology data to obtain target link data; Visualize the target link data on the link monitoring large screen to obtain a data display result.

[0113] It should be noted that the functions or steps that the computer readable storage medium or the computer device can implement correspond to the descriptions of the server side and the client side in the foregoing method embodiment. To avoid repetition, they will not be described one by one here.

[0114] The computer readable storage medium can also store at least one computer executable program / instruction, such as computer readable instructions. The computer readable storage medium includes, but is not limited to, for example, volatile memory and / or non-volatile memory. The volatile memory may, for example, include random access memory (RAM) and / or cache memory, etc. The computer readable storage medium may, for example, include read-only memory (ROM), hard disk, flash memory, etc. For example, the non-transitory computer readable storage medium can be connected to a computing device such as a computer, and then when the computing device runs the computer readable instructions stored on the computer readable storage medium, the various methods described above can be performed.

[0115] In addition, the computer device can also include, but is not limited to, a data bus, an input / output (I / O) bus, a display, and an input / output device (for example, a keyboard, a mouse, a speaker, etc.), and the like.

[0116] In one embodiment, the at least one computer-executable instruction can also be compiled or composed into a software product / computer program product, wherein one or more computer-executable instructions are executed by a processor to perform the steps of various functions and / or methods in the embodiments described in the present technology.

[0117] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by a computer program instructing related hardware, and the computer program can be stored in a non-volatile computer readable storage medium. When the computer program is executed, the processes of the above-mentioned embodiments can be included. Any reference to memory, storage, database or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memory.

[0118] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is exemplified, and in actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above.

[0119] In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method can also be implemented by other means. The apparatus embodiments described above are only illustrative. For example, the flowcharts and block diagrams in the drawings show possible implementation architectures, functions and operations of the apparatus, method and computer program product according to the embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders from that shown in the drawings. It should also be noted that each block in the block diagrams and / or flowcharts, and the combination of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0120] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

[0121] It should be noted that if non-company software tools or components appear in the embodiments of the present application, they are only used for example introduction and do not represent actual use.

Claims

1. A method for displaying link monitoring data on a large screen, characterized in that, The method includes: Obtain multiple visualization components, configure the multiple visualization components, and obtain an initial configuration component library; Obtain the component properties of the initial configuration component library, perform incremental updates on the component properties, and obtain the component change properties; Incremental components are obtained based on the component change attributes. The initial configuration component library is updated using the incremental components to obtain the target visualization component library. A link monitoring dashboard is then built based on the target visualization component library. Obtain link topology data, perform link topology rendering on the link topology data, and obtain target link data; The target link data is visualized on the link monitoring screen to obtain the data display results.

2. The link monitoring large screen display method as described in claim 1, characterized in that, The step of configuring the multiple visualization components to obtain an initial configuration component library includes: Assign unique identifiers to multiple visualization components to generate component identification information; The visualization components are format-validated based on the component identification information to obtain a candidate component set. Metadata is extracted from each component in the candidate component set to obtain a component metadata set; Construct a corresponding component index based on the component metadata set, associate the component metadata set with the corresponding candidate component set using the component index, and store the associated candidate components in a preset component registration center; The component layout of the components already stored in the component registry is adjusted to obtain the initial configuration component library.

3. The link monitoring large screen display method as described in claim 1, characterized in that, The incremental update of the component attributes to obtain the component change attributes includes: Obtain the attribute increment request, parse the attribute increment request, and obtain the set of attribute identifiers to be updated and the set of attribute change values ​​to be updated; The set of attribute identifiers to be updated is validated to obtain a valid set of changed attribute identifiers; Generate a set of attribute key-value pairs to be updated based on the set of valid change attribute identifiers; The target attribute field is determined based on the set of attribute key-value pairs to be updated, and the target attribute field is incrementally updated based on the set of attribute change values ​​to be updated to obtain the component change attribute.

4. The link monitoring large screen display method as described in claim 1, characterized in that, The step of updating the initial configuration component library using the incremental component to obtain the target visualization component library includes: The component interface protocol is determined based on the incremental component; Perform component dependency analysis on the incremental components to obtain a component dependency graph; Based on the component dependency graph, the initial configuration component library is integrated using the component interface protocol to obtain an intermediate state component library. The intermediate state component library is subjected to inter-component compatibility testing to obtain the target visualization component library.

5. The link monitoring large screen display method as described in claim 1, characterized in that, The step of constructing a link monitoring dashboard based on the target visualization component library includes: Acquire link monitoring data, and perform data normalization processing on the link monitoring data to obtain target link data; The target link data is bound to each target visualization component in the target visualization component library to obtain the target bound component; Obtain the component rendering engine, and arrange the layout of the target bound component according to the component rendering engine to generate an initial link monitoring large screen view; Data connectivity tests were performed on the initial link monitoring screen video, and the test results were obtained. Based on the test results, the initial link monitoring dashboard view is optimized to obtain the target link monitoring dashboard.

6. The link monitoring large screen display method as described in claim 1, characterized in that, The step of rendering the link topology data to obtain the target link data includes: The link topology data is cleaned to obtain standard link topology data; According to the preset rendering strategy, the standard link topology data is visualized and mapped to obtain the link node locations and link connection paths. An initial link topology map is generated based on the link node locations and the link connection paths; The initial link topology map is processed with graph labeling to obtain the target link data.

7. The link monitoring large screen display method as described in claim 1, characterized in that, The step of visualizing the target link data on the link monitoring screen to obtain the data display results includes: The link monitoring screen is divided into multiple visualization display areas. Based on the target link data and the visualization display area, determine the target display area corresponding to each data dimension; Obtain the visualization configuration items of the target display area, and perform interactive enhancement processing on the target link data according to the visualization configuration items to obtain the data display result.

8. A large-screen display device for link monitoring, characterized in that, The device includes: The component configuration module is used to acquire multiple visualization components, configure the multiple visualization components, and obtain an initial configuration component library. The component update module is used to obtain the component attributes of the initial configuration component library, perform incremental updates on the component attributes, and obtain the component change attributes; The large screen construction module is used to obtain incremental components based on the component change attributes, update the initial configuration component library using the incremental components to obtain the target visualization component library, and construct the link monitoring large screen based on the target visualization component library. The topology rendering module is used to acquire link topology data, perform link topology rendering on the link topology data, and obtain target link data. The visualization module is used to visualize the target link data on the link monitoring screen and obtain the data display results.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a link monitoring large screen display method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements a link monitoring large screen display method as described in any one of claims 1 to 7.

Images