A secure large-screen cross-platform multi-screen real-time linkage system

Abstract

The present invention provides a system for real-time linkage of multiple screens across multiple platforms for security large-screen display, which belongs to the field of large-screen display technology. The present invention includes two types of hardware: each independent platform and a main control platform. VPN tunnels and websocket services are deployed on the main control platform, and the main control platform establishes two-way communication with each independent platform through VPN tunnel technology and websocket services. The request and response data are uniformly managed by the Web front-end controller, which saves resources as much as possible and realizes the linkage of multi-screen display components. Safe and reliable two-way communication is established between each independent platform and the main control platform through the websocket module and VPN tunnel, realizing the linkage of secure large-screen cross-platform display components.

Description

Technical Field

[0001] The present invention relates to the field of large-screen display technology, and in particular to a secure large-screen cross-platform multi-screen real-time linkage system. Background Art

[0002] A security product typically needs to be deployed on multiple independent platforms, with data visualization displayed on security dashboards. During the presentation, multiple dashboards must display different content and implement linkage. If the presentation involves data exchange, real-time interaction, or other forms of collaborative work across multiple platforms, cross-platform linkage is essential, and data security must be guaranteed throughout the entire process.

[0003] However, in related technologies, each time the large-screen content is switched, it is necessary to resend a request to obtain data, and recalculate, organize, and render the data on the display component, which affects the performance of the large screen; when large-screen displays are performed simultaneously on different platforms and need to be linked, they cannot be automatically linked in real time and can only be operated manually, which affects the timeliness of the large-screen display; when obtaining data, most of the existing technologies can already control permissions based on the request source to achieve differentiated data display, but cannot achieve cross-platform permission control, and security and reliability are reduced. Summary of the Invention

[0004] To address the above technical issues, the present invention provides a system for secure large-screen, cross-platform, multi-screen real-time linkage. Through a series of data communications between the large-screen display terminals, Web front-end controllers, and back-end servers of each independent platform and the master control platform, the timeliness of cross-platform, multi-screen real-time linkage displays is improved. The Web front-end controller reduces the number of front-end and back-end calls, speeding up data rendering of front-end display components and reducing the pressure on back-end services. VPN tunnels and permission control enhance the security and reliability of large-screen displays.

[0005] The technical solution of the present invention is:

[0006] A secure large-screen, cross-platform, multi-screen real-time linkage system, including two hardware types: independent platforms and a master control platform. VPN tunnels and websocket services are deployed on the master control platform, which establishes two-way communication with each independent platform through VPN tunnel technology and websocket services. The following software is deployed on each independent platform:

[0007] 1. Large screen control terminal: used to pass request information to the Web front-end controller, obtain the returned response results processed by the Web front-end controller, and render data to the large screen display component;

[0008] 2. Web front-end controller: Receives request information transmitted by the large-screen control terminal, determines the type of request information through the store status tree module, and sends it to the websocket service module, the background server, or directly returns the response result data; the websocket service module communicates with the main control platform in two directions through VPN tunnel technology; the data processing algorithm module is used to calculate and organize the response result data returned by the background server, store it in the store status tree module, and return the calculated response result data.

[0009] 3. The backend server is used to receive request information sent by the Web front-end controller and return response result data through permission control and API interface.

[0010] Further,

[0011] The store state tree module includes the following concepts: store: represents the singleton state tree; state: represents a state of the singleton state tree; getters: methods for obtaining a state state; mutations: methods for modifying a state state; actions: methods for asynchronously modifying the state state;

[0012] The state is obtained through the getter method, and the state is modified using the mutations and actions methods. The data operated by getters, mutations and actions realizes the two-way binding of data, and the corresponding visual display components of the page will undergo corresponding display changes.

[0013] Further,

[0014] The data processing algorithm module processes the data returned by the data API interface into data in the data source format required by each display component type. This module includes several algorithms.

[0015] The data processing flow is as follows:

[0016] (1) The data processing algorithm module first receives the raw data returned from the API interface; parses the received raw data and converts it into a data structure that the module can process;

[0017] (2) Use a field matching algorithm to ensure that the fields in the data match the fields expected by the display component;

[0018] (3) According to the requirements of the display component, use the filtering algorithm to filter the data and remove the data that does not meet the requirements;

[0019] (4) Sort the data using a sorting algorithm according to the sorting requirements of the display component;

[0020] (5) Use mathematical algorithms to perform necessary calculations on the data according to the needs of the display components;

[0021] (6) Convert the processed data into the data source format required by the display component;

[0022] (7) Output the formatted data to the presentation component for display.

[0023] Further,

[0024] The workflow of the permission control module is as follows:

[0025] (1) First, the source of the request is verified. The source of the request usually contains the identification information of the request initiator. This information is carried along with the request when it is sent to the system and is used to identify the source and initiator of the request. The permission control module checks the validity and authenticity of this information to ensure that the request comes from a legitimate initiator.

[0026] (2) After verifying the request source, the permission control module will further obtain the cross-platform permission level. This permission level is returned by the main control platform through the VPN tunnel and represents the access permission level of the request initiator in the cross-platform environment.

[0027] (3) After obtaining the request source and cross-platform permission level, a comprehensive assessment will be conducted to determine whether the request initiator has the right to access specific data resources, as well as the data dimensions and content that can be accessed, based on the preset permission rules and policies;

[0028] (4) Based on the comprehensive evaluation results of permissions, the permission control module restricts the response data;

[0029] For data resources that are not authorized to be accessed, the module will directly reject the request and will not return any data;

[0030] For data resources that are authorized to be accessed, the module will limit the dimensions and content of the response data based on the permission level.

[0031] Going further,

[0032] The overall workflow includes the following steps:

[0033] Step 1: First, confirm whether this demonstration requires cross-platform linkage. If it is confirmed that cross-platform linkage is required, start the websocket service module of the Web front-end controller to realize real-time data interaction. According to the specific requirements of the project, configure the port and address parameters of the websocket service and initialize the relevant service modules. When starting the websocket service, use the SSL / TLS protocol to encrypt the transmitted data and set the access control list (ACL) to limit which clients can connect to the websocket service. At the same time, monitor the heartbeat to ensure the connection status. If no response is received within the predetermined time, it is considered that the connection has been disconnected and appropriate processing measures are taken;

[0034] Step 2: The large-screen display client sends a JSON-formatted request to the web front-end controller based on the component currently being operated by the user or the preset display logic. This request contains not only basic display chart information but also two key pieces of information: the display component ID and the request source. The display component ID is a unique identifier for a specific component on the large screen, used to distinguish different display contents.

[0035] The request source is used to identify the source of the request, which may be a manual trigger by the user, a scheduled task, or a data update push. Different sources require different processing logic or permission verification.

[0036] Step 3: After receiving the request, the Web front-end controller first determines the type of request information through the store state tree module and performs different processing. The request information is divided into the following three types and processing methods:

[0037] 1) If it is determined that the websocket service module has been started and the pre-made component ID that needs cross-platform linkage is matched, the request is sent to the websocket service and then to the main control platform through the VPN tunnel. VPN tunnel technology allows remote users to securely access internal network resources through public networks. It uses encryption and tunneling technology to protect the confidentiality and integrity of data. The network administrator participates in and assists in configuring the network parameters and authentication information of both parties. The main control platform receives the request and processes it, queries the relevant display component information that needs to be linked to the large screen of other platforms, and organizes the relevant result data into JSON format data and returns it. The result data only contains the display component ID, the request conditions of the data source, and the cross-platform permission level. The response result data is sent to the store state tree module of each independent platform that needs cross-platform linkage through the VPN tunnel and websocket service for further processing;

[0038] 2) Determine whether the data source required by the request is real-time updated data, and directly turn to the backend server to obtain the latest data; construct a request that complies with the data API interface specification. After receiving the request, the backend server will retrieve the corresponding data from the database based on the request parameters, or obtain data from other real-time data sources, and then encapsulate it into a standard response format. After receiving the response from the backend server, the Web front-end controller first passes it to the data processing algorithm module for cleaning, conversion, and aggregation to meet the data format and logical requirements of the front-end display component. After being processed by the data processing algorithm module, the data will be encapsulated in JSON format, stored in the store state tree module, and the display component data will be updated;

[0039] 3) Determine whether the data source required by the request is timed update data. There are two cases. If it is the first time to obtain the data source, that is, the data source does not exist in the store status tree, then its timeliness is equivalent to real-time update data. The process of updating the display component data is the same as the process in 2) above. If the data source already exists in the store status tree, then the data source is directly used to update the data of the corresponding component.

[0040] The beneficial effects of the present invention are

[0041] By using the present invention, a secure large-screen cross-platform multi-screen real-time linkage can be achieved. When large-screen displays are simultaneously performed on different platforms and linkage is required, real-time automatic linkage can be achieved without manual operation, saving manpower and improving timeliness, and reducing the risk of errors; the Web front-end controller uniformly manages the sending of requests, the receiving and sorting of response result data, and the two-way communication with the main control platform, reducing the number of front-end and back-end calls, speeding up the data rendering of the front-end display components, and reducing the pressure on the back-end service; the access authentication and encrypted tunnel of the VPN technology protect the confidentiality and integrity of the transmitted data between each independent platform and the main control platform, and at the same time adds permission control, thereby improving the security and reliability of the large-screen display. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 It is the overall working block diagram of the present invention;

[0043] Figure 2 This is a workflow diagram of the Web front-end controller. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0045] like Figure 1 As shown, the present invention provides a secure large-screen cross-platform multi-screen real-time linkage system, which includes two hardware types: each independent platform and a main control platform. Each independent platform is deployed with a large-screen display terminal, a Web front-end controller, and a background server. The method includes the following steps:

[0046] Step 1: First, confirm whether cross-platform linkage is required for this demonstration. If it is confirmed that cross-platform linkage is required, start the websocket service module of the Web front-end controller. Websocket is a network communication protocol that can perform full-duplex communication on a single TCP connection and is used to achieve real-time data interaction. According to the specific needs of the project, configure the port, address and other parameters of the websocket service and initialize the relevant service modules. This involves operations such as writing configuration files and loading dependent libraries. When starting the websocket service, considering security issues, use the SSL / TLS protocol to encrypt the transmitted data and set the access control list (ACL) to limit which clients can connect to the websocket service. At the same time, monitor the heartbeat to ensure the connection status. The heartbeat mechanism is a common method for detecting the network connection status. It sends heartbeat messages at regular intervals, which are simple timestamps, and monitors the heartbeat response from the main control platform. If no response is received for a long time, it can be considered that the connection has been disconnected and appropriate processing measures can be taken, such as reconnection and alarm.

[0047] Step 2: The large-screen display terminal will send a JSON-formatted request to the Web front-end controller based on the component currently operated by the user or the preset display logic. In addition to basic display chart information (such as data ID, chart type, configuration parameters, etc.), this request also needs to include two additional key pieces of information: the display component ID and the request source. The display component ID is a unique identifier for a specific component on the large screen, which is used to distinguish different display content. The request source is used to identify the source of the request, which may be a manual trigger by the user, a scheduled task, a data update push, etc. Different sources may require different processing logic or permission verification.

[0048] Step 3: After receiving the request, the Web front-end controller first determines the type of the request information through the store state tree module and performs different processing. The Web front-end controller's processing flow for requests and data is the core of this invention, please refer to Figure 2 , request information is divided into the following three types and processing methods after judgment:

[0049] 1. If it is determined that the websocket service module has been started and the pre-made component ID that needs cross-platform linkage is matched, the request is sent to the websocket service and then to the main control platform through the VPN tunnel. VPN (virtual private network) tunnel technology allows remote users to securely access internal network resources through public networks. It uses encryption and tunneling technologies to protect the confidentiality and integrity of data. Network administrators participate in and assist in configuring the network parameters and authentication information of both parties. The main control platform receives the request and processes it, queries the relevant display component information that needs to be linked to the large screens of other platforms, and organizes the relevant result data into JSON format data for return. In order to save service resources to the greatest extent, the result data only contains the display component ID, the request conditions of the data source, and the cross-platform permission level. The response result data is sent to the store state tree module of each independent platform that needs cross-platform linkage through the VPN tunnel and websocket service for further processing;

[0050] 2. Determine that the data source that the request needs to obtain is real-time updated data, so it will not retrieve old data from the store state tree, but will directly turn to the backend server to obtain the latest data. Build a request that complies with the data API interface specification, which usually includes specifying parameters such as the data type, range, timestamp, etc. to ensure that an accurate data set is obtained. After receiving the request, the backend server will retrieve the corresponding data from the database according to the request parameters, or obtain data from other real-time data sources (such as message queues, third-party APIs, etc.), and then encapsulate it into a standard response format. After receiving the response from the backend server, the Web front-end controller will not display it directly to the user, but will first pass it to the data processing algorithm module for cleaning, conversion, aggregation, etc. to comply with the data format and logic requirements of the front-end display component. The data processed by the data processing algorithm module will be encapsulated in JSON format, stored in the store state tree module, and the display component data will be updated;

[0051] 3. Determine whether the data source required by the request is timed update data. There are two cases. If it is the first time to obtain the data source, that is, the data source does not exist in the store status tree, then its timeliness is equivalent to real-time update data. The process of updating the display component data is the same as the process in the above 2. If the data source already exists in the store status tree, then the data source is directly used to update the data of the corresponding component.

[0052] The following are additional descriptions of the specific modules of the software on each independent platform:

[0053] 1. The store state tree module in the Web front-end controller software includes the following concepts: store: represents the singleton state tree; state: represents a state of the singleton state tree; getters: methods for obtaining a state state; mutations: methods for modifying a state state; actions: methods for asynchronously modifying the state state.

[0054] In order to ensure the security and stability of the data in the store state tree module, the state is obtained through the getter method, and the state is modified using specific mutations and actions methods. The data operated by getters, mutations and actions realizes two-way binding of data, and the corresponding visual display components of the page will undergo corresponding display changes.

[0055] 2. The data processing algorithm module in the Web front-end controller software processes the data returned by the data API interface into data in the data source format required by each display component type. This module includes multiple algorithms, such as sorting algorithms, filtering algorithms, field matching algorithms, and mathematical algorithms, to ensure data accuracy and efficiency. The data processing flow is roughly as follows:

[0056] (1) The data processing algorithm module first receives the raw data returned from the API interface; parses the received raw data and converts it into a data structure that the module can process;

[0057] (2) Use a field matching algorithm to ensure that the fields in the data match the fields expected by the display component;

[0058] (3) According to the requirements of the display component, use the filtering algorithm to filter the data and remove the data that does not meet the requirements;

[0059] (4) Sort the data using a sorting algorithm according to the sorting requirements of the display component;

[0060] (5) Use mathematical algorithms to perform necessary calculations on the data according to the needs of the display components;

[0061] (6) Convert the processed data into the data source format required by the display component;

[0062] (7) Output the formatted data to the presentation component for display.

[0063] 3. The permission control module in the backend server software is responsible for ensuring data security and access compliance. In complex application environments, especially when data needs to be shared across different platforms, the permission control module plays a particularly important role. It precisely limits the dimensions and content of response data by comprehensively evaluating the request source carried in the request information and the cross-platform permission level returned by the main control platform through the VPN tunnel. The general permission control process is as follows:

[0064] (1) The permission control module will first verify the source of the request. The request source usually contains the identification information of the request initiator, such as user ID, component ID, etc. This information will be carried together when the request is sent to the system to identify the source and initiator of the request. The permission control module will check the validity and authenticity of this information to ensure that the request comes from a legitimate initiator.

[0065] (2) After verifying the source of the request, the permission control module will further obtain the cross-platform permission level. This permission level is returned by the main control platform through the VPN tunnel. It represents the access permission level of the request initiator in the cross-platform environment. The VPN tunnel ensures the security and privacy of data transmission, so that the permission level information will not be stolen or tampered with during the transmission process.

[0066] (3) After obtaining the request source and cross-platform permission level, the permission control module will conduct a comprehensive assessment and determine whether the request initiator has the right to access specific data resources, as well as the data dimensions and content that can be accessed, based on the preset permission rules and policies. This assessment process will take into account multiple factors, such as the identity, role, and organization of the request initiator, as well as the sensitivity and importance of the data.

[0067] (4) Based on the comprehensive evaluation results of permissions, the permission control module will restrict the response data. For data resources that are not accessible, the module will directly reject the request and will not return any data. For data resources that are accessible, the module will limit the dimensions and content of the response data based on the permission level. For example, for requests with low permission levels, only a portion of the data fields or aggregated results may be obtained; for requests with high permission levels, more detailed and comprehensive data can be obtained.

[0068] The above description is only a preferred embodiment of the present invention and is only used to illustrate the technical solution of the present invention, and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included in the scope of protection of the present invention.

Claims

1. A secure large-screen cross-platform multi-screen real-time linkage system, characterized by: It includes two types of hardware: several independent platforms and a master control platform; Deploy VPN tunnels and websocket services on the master control platform, which establishes two-way communication with each independent platform through VPN tunnel technology and websocket services; Deploy the following software on each independent platform: 1) Large screen control terminal: used to pass request information to the Web front-end controller, obtain the returned response results processed by the Web front-end controller, and render data to the large screen display component; 2) Web front-end controller: Receives request information transmitted by the large-screen control terminal, determines the type of request information through the store status tree module, and sends it to the websocket service module, the backend server, or directly returns the response result data; the websocket service module communicates with the main control platform in two directions through VPN tunnel technology; the data processing algorithm module is used to calculate and organize the response result data returned by the backend server, store it in the store status tree module, and return the calculated response result data; 3) The backend server is used to receive the request information sent by the Web front-end controller and return the response result data through the permission control module and API interface.

2. The system according to claim 1, wherein: The store state tree module includes the following concepts: store: represents the singleton state tree; state: represents a state of the singleton state tree; getters: methods for obtaining a state state; mutations: methods for modifying a state state; actions: methods for asynchronously modifying the state state; The state is obtained through the getter method, and the state is modified using the mutations and actions methods. The data operated by getters, mutations and actions realizes two-way binding of data, and the corresponding visual display components of the page will undergo corresponding display changes.

3. The system according to claim 1, wherein: The data processing algorithm module processes the data returned by the data API interface into data in the data source format required by each display component type. This module includes several algorithms.

4. The system according to claim 3, characterized in that The data processing flow is as follows: (1) The data processing algorithm module first receives the raw data returned from the API interface; parses the received raw data and converts it into a data structure that can be processed by the module; (2) Use a field matching algorithm to ensure that the fields in the data match the fields expected by the display component; (3) According to the requirements of the display component, use the filtering algorithm to filter the data and remove the data that does not meet the requirements; (4) Sort the data using a sorting algorithm according to the sorting requirements of the display component; (5) Use mathematical algorithms to perform necessary calculations on the data according to the needs of the display components; (6) Convert the processed data into the data source format required by the display component; (7) Output the formatted data to the presentation component for display.

5. The system according to claim 1, wherein: The workflow of the permission control module is as follows: (1) First, the source of the request is verified. The source of the request contains the identification information of the request initiator. This information is carried along with the request when it is sent to the system and is used to identify the source and initiator of the request. The permission control module checks the validity and authenticity of this information to ensure that the request comes from a legitimate initiator. (2) After verifying the request source, the permission control module will further obtain the cross-platform permission level. This permission level is returned by the main control platform through the VPN tunnel and represents the access permission level of the request initiator in the cross-platform environment. (3) After obtaining the request source and cross-platform permission level, a comprehensive assessment will be conducted to determine whether the request initiator has the right to access specific data resources, as well as the data dimensions and content that can be accessed, based on the preset permission rules and policies; (4) Based on the comprehensive evaluation results of permissions, the permission control module restricts the response data; For data resources that are not authorized to be accessed, the module will directly reject the request and will not return any data; For data resources that are authorized to be accessed, the module will limit the dimensions and content of the response data based on the permission level.

6. The system according to claim 1, wherein: The overall workflow includes the following steps: Step 1: First, confirm whether cross-platform linkage is required for this demonstration. If it is confirmed that cross-platform linkage is required, start the websocket service module of the web front-end controller to realize real-time data interaction. According to the specific requirements of the project, configure the port and address parameters of the websocket service and initialize the relevant service modules. When starting the websocket service, use the SSL / TLS protocol to encrypt the transmitted data and set the access control list (ACL) to limit which clients can connect to the websocket service. At the same time, monitor the heartbeat to ensure the connection status. If no response is received within the predetermined time, it is considered that the connection has been disconnected and appropriate processing measures are taken. Step 2: The large-screen display terminal sends a JSON-formatted request to the web front-end controller based on the component currently operated by the user or the preset display logic. This request contains not only basic display chart information but also two pieces of information: the display component ID and the request source. Step 3: After receiving the request, the Web front-end controller first determines the type of request information through the store state tree module and performs different processing.

7. The system according to claim 6, characterized in that The display component ID is a unique identifier for a specific component on the large screen, used to distinguish different display contents; The request source is used to identify the source of the request, including user manual triggering, scheduled tasks, and data update push. Different sources require different processing logic or permission verification.

8. The system according to claim 6, wherein: The request information is divided into the following three types and processing methods after judgment 1) If it is determined that the websocket service module has been started and the pre-made component ID that needs cross-platform linkage is matched, the request is sent to the websocket service and then to the main control platform through the VPN tunnel. VPN tunnel technology allows remote users to securely access internal network resources through public networks. It uses encryption and tunneling technology to protect the confidentiality and integrity of data. The network administrator participates in and assists in configuring the network parameters and authentication information of both parties. The main control platform receives the request and processes it, queries the relevant display component information that needs to be linked to the large screen of other platforms, and organizes the relevant result data into JSON format data and returns it. The result data only contains the display component ID, the request conditions of the data source, and the cross-platform permission level. The response result data is sent to the store state tree module of each independent platform that needs cross-platform linkage through the VPN tunnel and websocket service for further processing; 2) Determine if the data source required by the request is real-time updated data and directly turn to the backend server to obtain the latest data; construct a request that complies with the data API interface specification. After receiving the request, the backend server will retrieve the corresponding data from the database based on the request parameters, or obtain data from other real-time data sources, and then encapsulate it into a standard response format; after receiving the response from the backend server, the Web front-end controller first passes it to the data processing algorithm module for cleaning, conversion, and aggregation to meet the data format and logic requirements of the front-end display component. After being processed by the data processing algorithm module, the data is encapsulated into JSON format, stored in the store state tree module, and the display component data is updated; 3) Determine whether the data source required by the request is timed update data. There are two cases. If it is the first time to obtain the data source, that is, the data source does not exist in the store status tree, then its timeliness is equivalent to real-time update data. The process of updating the display component data is the same as the process in 2) above. If the data source already exists in the store status tree, then the data source is directly used to update the data of the corresponding component.

Images