Method and System for Third-Party Tool Docking, Operation and Maintenance, and Control of Independent Websites

Abstract

The present invention relates to the field of independent website operation, specifically to a method and system for the docking, operation and maintenance, and control of third-party tools for independent websites. The thread support requirement information of the task execution end of the independent website is determined from the task execution thread log, and the target thread that needs to be docked with the third-party tool is identified based on this; based on the operation status of the virtual nodes allowed to be accessed by the target thread within the independent website, the connection relationship between the target thread and the virtual nodes is determined, and a virtual node connection layout is generated; based on the execution time domain characteristic information of all target threads, the bandwidth configuration of the virtual nodes is adjusted, and the third-party tool is called to connect to the triggered virtual nodes to ensure the accurate docking of the third-party tool with the target thread; based on the working behavior information of the third-party tool, it is judged whether the third-party tool has abnormal behavior, and the permissions and / or connections of the third-party tool are controlled to prevent the third-party tool from making unauthorized operations on the independent website and improve the operation safety of the independent website.

Description

Technical Field

[0001] The present invention relates to the technical field of independent station operation, and in particular to a method and system for operation, maintenance and management of independent stations using third-party tools. Background Art

[0002] An independent website is a completely independent website that is built and operated by the enterprise independently, including an independent server, website program and a separate domain name. Independent websites need to process a large amount of enterprise data during operation. Usually, independent websites rely on their own servers to complete data processing tasks, ensuring the independence and security of data processing of independent websites. In actual operation, in order to meet the needs of different data processing scenarios or the independent website itself cannot implement a specific data processing mode, third-party tools are needed to assist in the execution of data processing tasks. Third-party tools are usually software tools that can perform specific data processing operations and can be called by different independent websites. In the development process of third-party tools, it is inevitable that there will be backdoor defects. When an independent website calls and connects to a third-party tool, there may be a problem of being invaded by a backdoor attack, which reduces the operational security of the independent website. For this reason, it is of great significance to operate and monitor the third-party tools during the process of the independent website calling and connecting to the third-party tools to prevent the third-party tools from making unauthorized operations on the independent website, which is of great significance to maintaining the security of the independent website. Summary of the invention

[0003] In view of the defects existing in the prior art, the present invention provides an independent station third-party tool docking operation, maintenance and management method and system, which determines the thread support demand information of the task execution end of the independent station from the task execution thread log, thereby identifying the target thread that needs to be docked with the third-party tool and accurately locating the third-party tool docking object; based on the operation status of the virtual node allowed to be accessed by the target thread in the independent station, determines the connection relationship between the target thread and the virtual node, generates a virtual node connection layout, and locates the third-party tool docking; based on the execution time domain feature information of all target threads, adjusts the bandwidth configuration of the virtual node, and calls the third-party tool to connect to the triggered virtual node, to ensure the accurate docking of the third-party tool with the target thread, and improves the data processing efficiency of the target thread; based on the work behavior information of the third-party tool, determines whether the third-party tool has abnormal behavior, and performs permission and / or connection management on the third-party tool to prevent the third-party tool from making unauthorized operations on the independent station, thereby improving the operation security of the independent station.

[0004] The present invention provides a third-party tool docking operation, maintenance and management method for an independent station, including the following steps:

[0005] Step S1, monitor the task execution end of the independent station to obtain the task execution thread log of the independent station; analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with third-party tools;

[0006] Step S2, perform virtual node matching identification on all target threads to determine the virtual nodes allowed to be accessed by each of all target threads within the independent station; based on the operation status of the virtual nodes allowed to be accessed by all target threads, determine the connection relationship between all target threads and the virtual nodes, and generate a virtual node connection layout for all target threads;

[0007] Step S3, based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of all virtual nodes under the virtual node connection layout; identify the virtual nodes triggered inside the virtual node connection layout, so as to call a third-party tool to connect to the triggered virtual node;

[0008] Step S4, monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool; based on the working behavior information, determine whether the third-party tool has abnormal behavior, so as to perform permission and / or connection control on the third-party tool.

[0009] In an embodiment disclosed in the present application, in the step S1, monitor the task execution end of the independent station to obtain the task execution thread log of the independent station; analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with third-party tools, including:

[0010] Analyze the task creation log of the independent station to obtain the new task creation trend information of the independent station; wherein, the new task creation trend information includes the change trend of the number of new tasks created by the independent station per unit time and the change trend of the distribution quantity of the created new tasks among all task execution ends within the independent station;

[0011] Based on the new task creation trend information, identify the task execution ends in an effective operation state within the independent station; monitor the task execution ends in the effective operation state to obtain the task execution thread logs of the task execution ends;

[0012] Analyze the task execution thread log to determine the computing resource requirement information of each of all the threads allocated to the task execution end during the execution process, and use this as the thread execution requirement information; based on the computing resource requirement information, determine whether the independent station can provide the computing resources required by the thread; if not, then determine the thread as the target thread that needs to be docked with a third-party tool.

[0013] In an embodiment disclosed in the present application, in the step S2, perform virtual node matching recognition on all target threads to determine the virtual nodes allowed to be accessed by each of all target threads within the independent station; based on the operating states of the virtual nodes allowed to be accessed by all target threads, determine the connection relationships between all target threads and the virtual nodes, and generate a virtual node connection layout for all target threads, including:

[0014] Identify all the connection links between each of all target threads and all virtual nodes within the independent station, determine the probabilities of all connection links occurring interruption interference events, and then based on the probabilities of the interruption interference events, determine the virtual nodes allowed to be accessed by each of all target threads within the independent station;

[0015] Compare the available operating bandwidths of the virtual nodes allowed to be accessed by each of all target threads and the estimated data processing amounts of each of all target threads to determine the matching connection relationships between all target threads and all the virtual nodes allowed to be accessed, thereby generating a virtual node connection layout for all target threads.

[0016] In an embodiment disclosed in the present application, in the step S3, based on the execution time domain feature information of all target threads, adjust the bandwidth configurations of all virtual nodes subordinate to the virtual node connection layout; identify the virtual nodes triggered inside the virtual node connection layout, and then call a third-party tool to connect to the triggered virtual nodes, including:

[0017] Obtain the execution occupation time interval information of each of all target threads at the task execution end, and based on the execution occupation time interval information, determine the execution time axis relationship information of all target threads, and use this as the execution time domain feature information; based on the execution time domain feature information, perform connection overlap time interval recognition on all virtual nodes subordinate to the virtual node connection layout to obtain the longest duration length corresponding to each virtual node connecting two or more target threads simultaneously; then based on the longest duration length, adjust the available bandwidth allocation value of each virtual node;

[0018] Identify the instruction flow for all virtual nodes within the virtual node connection layout, and determine whether the virtual node has received a preset instruction code within a preset time interval. If so, determine that the virtual node is triggered; if not, determine that the virtual node is not triggered. Then, based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node.

[0019] In an embodiment disclosed in the present application, in step S4, monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool; based on the working behavior information, determine whether the third-party tool has abnormal behavior, so as to perform permission and / or connection control on the third-party tool, including:

[0020] Monitor the third-party tool connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tool, which is used as the working behavior information; wherein, the data reading and editing behavior information includes the access interval information of the third-party tool reading data from the target thread through the virtual node and the editing type information of the read data.

[0021] Based on the working behavior information, determine whether the third-party tool has an illegal access to an unauthorized interval behavior and / or an illegal tampering behavior with the read data; when an illegal access to an unauthorized interval behavior occurs, change the data reading permission of the third-party tool for the target thread; when an illegal tampering behavior with the read data occurs, interrupt the connection between the third-party tool and the virtual node.

[0022] The present invention also provides a third-party tool docking operation and maintenance and control system for an independent website, including:

[0023] A task execution end monitoring module, used to monitor the independent website at the task execution end to obtain the task execution thread log of the independent website;

[0024] A target thread identification module, used to analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with a third-party tool;

[0025] A virtual node matching and identification module, used to perform virtual node matching and identification on all target threads to determine the virtual nodes allowed to access each of all target threads within the independent website;

[0026] A virtual node connection layout generation module, used to determine the connection relationship between all target threads and virtual nodes based on the operating status of the virtual nodes allowed to access by all target threads, and generate a virtual node connection layout for all target threads;

[0027] A virtual node bandwidth configuration module, configured to adjust the bandwidth configuration of all virtual nodes subordinate to the virtual node connection layout based on the execution time domain feature information of all target threads;

[0028] A third-party tool connection module, configured to identify the virtual nodes triggered inside the virtual node connection layout, so as to retrieve a third-party tool and connect it to the triggered virtual nodes;

[0029] A third-party tool monitoring module, configured to monitor the third-party tools connected to the triggered virtual nodes to obtain the working behavior information of the third-party tools;

[0030] A third-party tool management and control module, configured to determine whether the third-party tools have abnormal behaviors based on the working behavior information, so as to perform permission and / or connection management and control on the third-party tools.

[0031] In an embodiment disclosed in the present application, the task execution end monitoring module is configured to monitor the task execution end of the independent station to obtain the task execution thread log of the independent station, including:

[0032] Analyze the task creation log of the independent station to obtain the new task creation trend information of the independent station; wherein, the new task creation trend information includes the change trend of the number of new tasks created by the independent station per unit time and the change trend of the distribution quantity of the created new tasks among all task execution ends inside the independent station;

[0033] Based on the new task creation trend information, identify the task execution ends in the effective operation state inside the independent station; monitor the task execution ends in the effective operation state to obtain the task execution thread log of the task execution ends;

[0034] The target thread identification module is configured to analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with a third-party tool, including:

[0035] Analyze the task execution thread log to determine the operation resource requirement information of each of all the threads assigned to the task execution end during the execution process, and use this as the thread execution requirement information; based on the operation resource requirement information, determine whether the independent station can provide the operation resources required by the thread; if not, then determine the thread as a target thread that needs to be docked with a third-party tool.

[0036] In an embodiment disclosed in the present application, the virtual node matching and identification module is configured to perform virtual node matching and identification on all target threads to determine the virtual nodes allowed to be accessed by each of all target threads inside the independent station, including:

[0037] Identify all the connection links between each of the target threads and all the virtual nodes within the independent station, determine the probability of interruption interference events occurring in all the connection links, and then based on the probability of the interruption interference events, determine the virtual nodes that each of the target threads is allowed to access within the independent station;

[0038] The virtual node connection layout generation module is configured to determine the connection relationships between all the target threads and the virtual nodes based on the operating states of the virtual nodes that all the target threads are allowed to access, and generate a virtual node connection layout for all the target threads, including:

[0039] Compare the respective available operating bandwidths of the virtual nodes that all the target threads are allowed to access and the respective estimated data processing amounts of all the target threads to determine the matching connection relationships between all the target threads and all the virtual nodes allowed to access, so as to generate a virtual node connection layout for all the target threads.

[0040] In an embodiment disclosed in the present application, the virtual node bandwidth configuration module is configured to adjust the bandwidth configurations of all the virtual nodes subordinate to the virtual node connection layout based on the execution time domain characteristic information of all the target threads, including:

[0041] Obtain the execution occupation time interval information of each of the target threads at the task execution end, and based on the execution occupation time interval information, determine the execution time axis relationship information of all the target threads, and use this as the execution time domain characteristic information; based on the execution time domain characteristic information, identify the connection overlapping time intervals of all the virtual nodes subordinate to the virtual node connection layout to obtain the longest duration length corresponding to each virtual node connecting two or more target threads; and then based on the longest duration length, adjust the available bandwidth allocation value of each virtual node;

[0042] The third-party tool connection module is configured to identify the virtual nodes triggered inside the virtual node connection layout, and thus call a third-party tool to connect to the triggered virtual nodes, including:

[0043] Perform instruction stream identification on all the virtual nodes inside the virtual node connection layout, and determine whether the virtual node receives a preset instruction code within a preset time interval. If so, determine that the virtual node is triggered; if not, determine that the virtual node is not triggered; and then based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node.

[0044] In an embodiment disclosed in the present application, the third-party tool monitoring module is configured to monitor the third-party tools connected to the triggered virtual nodes to obtain the working behavior information of the third-party tools, including:

[0045] Monitor the third-party tools connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tools, and use this as the work behavior information; wherein, the data reading and editing behavior information includes the access range information of the third-party tools reading data from the target thread through the virtual node and the editing type information of the read data.

[0046] The third-party tool control module is used to determine whether the third-party tool has abnormal behavior based on the work behavior information, so as to perform permission and / or connection control on the third-party tool, including:

[0047] Based on the work behavior information, determine whether the third-party tool has an illegal access to unauthorized range behavior and / or an illegal tampering behavior on the read data; when an illegal access to unauthorized range behavior occurs, change the data reading permission of the third-party tool for the target thread; when an illegal tampering behavior on the read data occurs, interrupt the connection between the third-party tool and the virtual node.

[0048] Compared with the prior art, the method and system for docking, operation and maintenance, and control of third-party tools of the independent station determine the thread support requirement information of the task execution end of the independent station from the task execution thread log, so as to identify the target thread that needs to be docked with the third-party tool, and accurately locate the docking object of the third-party tool; based on the operation status of the virtual node allowed to be accessed by the target thread in the independent station, determine the connection relationship between the target thread and the virtual node, generate a virtual node connection layout, and locate for the third-party tool docking; based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of the virtual node, and call the third-party tool to connect to the triggered virtual node to ensure the accurate docking of the third-party tool and the target thread, improve the data processing efficiency of the target thread; based on the work behavior information of the third-party tool, determine whether the third-party tool has abnormal behavior, and perform permission and / or connection control on the third-party tool to avoid unauthorized operations of the third-party tool on the independent station and improve the operation safety of the independent station.

[0049] Other features and advantages of the present invention will be described in the following specification, and, in part, will be obvious from the specification, or will be understood by implementing the present invention. The objectives and other advantages of the present invention can be realized and obtained by the structures specifically pointed out in the written specification, claims, and drawings.

[0050] The technical solution of the present invention will be further described in detail below with reference to the drawings and embodiments. Description of the Drawings

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

[0052] Figure 1 It is a schematic flowchart of the method for docking, operation and maintenance, and control of third-party tools for an independent website provided by the present invention;

[0053] Figure 2 It is a schematic framework diagram of the system for docking, operation and maintenance, and control of third-party tools for an independent website provided by the present invention. Specific embodiments

[0054] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0055] Refer to Figure 1 , which is a schematic flowchart of the method for docking, operation and maintenance, and control of third-party tools for an independent website provided by the embodiments of the present invention. The method for docking, operation and maintenance, and control of third-party tools for the independent website includes:

[0056] Step S1, monitor the task execution end of the independent website to obtain the task execution thread log of the independent website; analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with third-party tools;

[0057] Step S2, perform virtual node matching and identification on all target threads to determine the virtual nodes allowed to be accessed by each of all target threads in the independent website; based on the operation status of the virtual nodes allowed to be accessed by all target threads, determine the connection relationship between all target threads and the virtual nodes, and generate a virtual node connection layout for all target threads;

[0058] Step S3, based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of all virtual nodes under the virtual node connection layout; identify the virtual nodes triggered inside the virtual node connection layout, so as to call third-party tools to connect to the triggered virtual nodes;

[0059] Step S4: Monitor the third-party tools connected to the triggered virtual nodes to obtain the working behavior information of the third-party tools; based on the working behavior information, determine whether the third-party tools have abnormal behaviors, so as to perform permission and / or connection control on the third-party tools.

[0060] The method for docking, operation and maintenance, and control of the third-party tools of the independent website determines the thread support requirement information of the task execution end of the independent website from the task execution thread log, so as to identify the target threads that need to be docked with the third-party tools and accurately locate the docking objects of the third-party tools; based on the operation status of the virtual nodes allowed to be accessed by the target threads within the independent website, determine the connection relationship between the target threads and the virtual nodes, generate a virtual node connection layout, and locate for the docking of the third-party tools; based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of the virtual nodes, and call the third-party tools to connect to the triggered virtual nodes to ensure the accurate docking of the third-party tools and the target threads, and improve the data processing efficiency of the target threads; based on the working behavior information of the third-party tools, determine whether the third-party tools have abnormal behaviors, and perform permission and / or connection control on the third-party tools to prevent the third-party tools from making unauthorized operations on the independent website and improve the operation safety of the independent website.

[0061] Preferably, in this step S1, monitor the task execution end of the independent website to obtain the task execution thread log of the independent website; analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with the third-party tools, including:

[0062] Analyze the task creation log of the independent website to obtain the new task creation trend information of the independent website; among them, the new task creation trend information includes the change trend of the number of new tasks created per unit time of the independent website and the change trend of the distribution quantity of the created new tasks among all task execution ends within the independent website.

[0063] Based on the new task creation trend information, identify the task execution ends in the effective operation state within the independent website; monitor the task execution ends in the effective operation state to obtain the task execution thread log of the task execution ends.

[0064] Analyze the task execution thread log to determine the operation resource requirement information of all the threads assigned to the task execution end during their respective execution processes, and use this as the thread execution requirement information; based on the operation resource requirement information, determine whether the independent website can provide the operation resources required by the thread; if not, determine the thread as a target thread that needs to be docked with the third-party tool.

[0065] In the above technical solution, during the operation of the independent website, in order to complete different data processing, different data processing tasks will be created, and the created data processing tasks will be assigned to different task execution ends under the independent website. Generally speaking, the higher the task processing efficiency and the higher the task processing accuracy of the task execution end, the more data processing tasks it will be assigned. Correspondingly, the probability that the task execution end needs to connect to a third-party tool during the process of processing the corresponding data processing task is higher. In order to ensure that the task execution end of the independent website can accurately and timely connect to the third-party tool during the process of processing the corresponding data processing task, analyze the task creation log of the independent website to obtain the new task creation trend information of the independent website, so as to accurately identify and characterize the change trend of the number of new tasks created by the independent website per unit time and the change trend of the allocation data of the created new tasks among all task execution ends within the independent website. Then, based on this new task creation trend information, predict the number of new tasks assigned to each task execution end within the independent website per unit time. When the number of new tasks assigned exceeds the preset quantity threshold, determine that the corresponding task execution end is in an effective operation state; otherwise, determine that the corresponding task execution end is not in an effective operation state. And monitor the task execution ends in the effective operation state to obtain the task execution thread logs of the task execution ends; among them, the task execution thread logs include all thread records corresponding to the processing of each new task received by the task execution end. Also, analyze the task execution thread logs to determine the computing resource requirement information of all threads assigned to the task execution end during the execution process, that is, the computing resources required by each thread during the execution process. Compare the computing resource requirement information with the currently available computing resource information of the independent website to determine whether the independent website can provide the type and quantity of computing resources required by the thread; if not, determine that the thread needs to connect to a third-party tool to provide additional computing resources to ensure that the thread (i.e., the target thread) can obtain effective auxiliary execution by the third-party tool subsequently.

[0066] Preferably, in this step S2, perform virtual node matching and identification on all target threads to determine the virtual nodes allowed to be accessed by all target threads within the independent website; based on the operation states of the virtual nodes allowed to be accessed by all target threads, determine the connection relationships between all target threads and the virtual nodes, and generate a virtual node connection layout for all target threads, including:

[0067] Identify all connection links between all target threads and all virtual nodes within the independent website, determine the probability of all connection links occurring interruption interference events, and then based on the probability of the interruption interference events, determine the virtual nodes allowed to be accessed by all target threads within the independent website;

[0068] Compare the respective operating available bandwidths of all virtual nodes allowed to be accessed by all target threads and the respective estimated data processing amounts of all target threads to determine the matching connection relationships between all target threads and all virtual nodes allowed to be accessed, thereby generating a virtual node connection layout for all target threads.

[0069] In the above technical solution, an independent site contains several virtual nodes, and each virtual node can be used to connect a target thread to a third-party tool and serve as a connection intermediary between the target thread and the third-party tool. Due to the instability of the connection link between the target thread and the virtual node, the terminal connected to the virtual node may be interfered, and there is a corresponding upper limit to the operating available bandwidth of each virtual node itself. To ensure that the target thread can obtain a stable connection with the virtual node and thus achieve a reliable connection with the third-party tool, identify all connection links between each target thread and all virtual nodes within the independent site, and thereby determine the probability of interruption interference events occurring in each connection link. If the probability is less than a preset probability threshold, the corresponding virtual node is determined as the virtual node allowed to be accessed by the target thread within the independent site to ensure the connection stability and continuity between the target thread and the corresponding virtual node. Also, compare the respective operating available bandwidths of all virtual nodes allowed to be accessed by all target threads and the respective estimated data processing amounts of all target threads to achieve the matching correspondence between the target threads and the virtual nodes allowed to be accessed, thereby determining the matching connection relationships between all target threads and all virtual nodes allowed to be accessed, and thus generating a virtual node connection layout for all target threads. In this way, the virtual node connection layout can globally represent the connection correspondence between all target threads and all virtual nodes allowed to be accessed.

[0070] Preferably, in this step S3, based on the execution time domain characteristic information of all target threads, adjust the bandwidth configurations of all virtual nodes subordinate to the virtual node connection layout; identify the virtual nodes triggered within the virtual node connection layout, and thereby call the third-party tool to connect to the triggered virtual nodes, including:

[0071] Obtain the execution occupation time interval information of each target thread at the task execution end, and based on the execution occupation time interval information, determine the execution time axis relationship information of all target threads, and use this as the execution time domain characteristic information; based on the execution time domain characteristic information, identify the connection overlap time intervals of all virtual nodes subordinate to the virtual node connection layout to obtain the longest duration length corresponding to each virtual node connecting two or more target threads simultaneously; then based on the longest duration length, adjust the available bandwidth allocation value of each virtual node.

[0072] Identify the instruction flow for all virtual nodes within the virtual node connection layout, and determine whether the virtual node has received a preset instruction code within a preset time interval. If so, determine that the virtual node is triggered; if not, determine that the virtual node is not triggered. Then, based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node.

[0073] In the above technical solution, during the operation of the independent station, internal virtual nodes may be connected to multiple target threads at the same time, so as to provide corresponding third-party tool docking for multiple target threads. At this time, the same virtual node needs to handle the third-party tool docking requirements of multiple target threads. To ensure that in the above situation, the virtual node can provide stable and continuous third-party tool docking services for all connected target threads, based on the execution occupancy time interval information of all target threads at the task execution end, determine the execution time axis relationship information of all target threads. Then, based on this execution time axis relationship information, identify the connection overlap time interval for all virtual nodes subordinate to the virtual node connection layout, and obtain the longest duration length corresponding to each virtual node connecting two or more target threads at the same time, so as to adjust the available bandwidth allocation value of each virtual node, ensuring that when the virtual node connects multiple target threads at the same time period, it can provide sufficient bandwidth connections for all target threads. Also, identify the instruction flow for all virtual nodes within the virtual node connection layout, and determine whether the virtual node has received a preset instruction code within a preset time interval to identify the triggered virtual nodes within the virtual node connection layout. Then, based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node, ensuring that the target thread obtains a reliable third-party tool docking service.

[0074] Preferably, in step S4, monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool; based on this working behavior information, determine whether the third-party tool has abnormal behavior, so as to perform permission and / or connection control on the third-party tool, including:

[0075] Monitor the third-party tool connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tool as the working behavior information; among them, the data reading and editing behavior information includes the access interval information of the third-party tool reading data from the target thread through the virtual node and the editing type information of the read data.

[0076] Based on this working behavior information, determine whether the third-party tool has performed an illegal access to an unauthorized range and / or an illegal tampering behavior on the read data; when an illegal access to an unauthorized range occurs, change the data reading permission of the third-party tool for the target thread; when an illegal tampering behavior on the read data occurs, interrupt the connection between the third-party tool and the virtual node.

[0077] In the above technical solution, monitor the third-party tool connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tool, and thereby determine whether the third-party tool has performed an illegal access to an unauthorized range and / or an illegal tampering behavior on the read data, accurately identifying the data access and editing behavior during the process of the third-party tool providing services for docking with the target thread. Also, when an illegal access to an unauthorized range occurs, change the data reading permission of the third-party tool for the target thread, and when an illegal tampering behavior on the read data occurs, interrupt the connection between the third-party tool and the virtual node, performing permission and / or connection control on the third-party tool to prevent the third-party tool from performing unauthorized operations on the independent station and improving the operation security of the independent station.

[0078] Refer to Figure 2 , which is a schematic framework diagram of the third-party tool docking operation and maintenance and control system of the independent station provided by the embodiment of the present invention. The third-party tool docking operation and maintenance and control system of the independent station includes:

[0079] A task execution end monitoring module, which is used to monitor the independent station at the task execution end to obtain the task execution thread log of the independent station;

[0080] A target thread identification module, which is used to analyze the task execution thread log to determine the thread execution requirement information of the task execution end, thereby identifying all target threads that need to be docked with the third-party tool;

[0081] A virtual node matching and identification module, which is used to perform virtual node matching and identification on all target threads to determine the virtual nodes allowed to be accessed by each of all target threads within the independent station;

[0082] A virtual node connection layout generation module, which is used to determine the connection relationship between all target threads and virtual nodes based on the operation status of the virtual nodes allowed to be accessed by all target threads, and generate a virtual node connection layout for all target threads;

[0083] A virtual node bandwidth configuration module, which is used to adjust the bandwidth configuration of all virtual nodes subordinate to the virtual node connection layout based on the execution time domain characteristic information of all target threads;

[0084] A third-party tool connection module, which is used to identify the virtual nodes triggered inside the virtual node connection layout, so as to retrieve a third-party tool and connect it to the triggered virtual node;

[0085] A third-party tool monitoring module, which is used to monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool;

[0086] A third-party tool control and management module, which is used to judge whether the third-party tool has abnormal behavior based on the working behavior information, so as to perform permission and / or connection control on the third-party tool.

[0087] The third-party tool docking operation and maintenance and control system of the independent station determines the thread support requirement information of the task execution end of the independent station from the task execution thread log, so as to identify the target threads that need to be docked with the third-party tool and accurately locate the third-party tool docking object; based on the operation status of the virtual nodes allowed to be accessed by the target threads in the independent station, determine the connection relationship between the target threads and the virtual nodes, generate a virtual node connection layout, and locate for the third-party tool docking; based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of the virtual nodes, and retrieve a third-party tool and connect it to the triggered virtual node to ensure the accurate docking of the third-party tool and the target threads, and improve the data processing efficiency of the target threads; based on the working behavior information of the third-party tool, judge whether the third-party tool has abnormal behavior, and perform permission and / or connection control on the third-party tool to avoid unauthorized operations of the third-party tool on the independent station and improve the operation safety of the independent station.

[0088] Preferably, the task execution end monitoring module is used to monitor the task execution end of the independent station to obtain the task execution thread log of the independent station, including:

[0089] Analyze the task creation log of the independent station to obtain the new task creation trend information of the independent station; wherein, the new task creation trend information includes the change trend of the number of new tasks created by the independent station per unit time and the change trend of the distribution number of the created new tasks among all task execution ends in the independent station;

[0090] Based on the new task creation trend information, identify the task execution ends in the independent station that are in an effective operation state; monitor the task execution ends in the effective operation state to obtain the task execution thread log of the task execution ends;

[0091] The target thread identification module is used to analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be docked with the third-party tool, including:

[0092] Analyze the task execution thread logs of this task to determine the computing resource requirement information of each thread assigned to the task execution end of this task during the execution process, and use this as the thread execution requirement information; based on this computing resource requirement information, determine whether this independent site can provide the computing resources required by this thread; if not, then determine this thread as the target thread that needs to be docked with a third-party tool.

[0093] In the above technical solution, during the operation of the independent site, in order to complete different data processing, different data processing tasks will be created, and the created data processing tasks will be assigned to different task execution ends under the independent site. Generally speaking, the higher the task processing efficiency and the higher the task processing accuracy of the task execution end, the more data processing tasks it is assigned, and correspondingly, the higher the probability that the task execution end needs to be docked with a third-party tool during the process of processing the corresponding data processing tasks. In order to ensure that the task execution end of the independent site can accurately and timely dock with a third-party tool during the process of processing the corresponding data processing tasks, analyze the task creation logs of the independent site to obtain the new task creation trend information of the independent site, so as to accurately identify and represent the change trend of the number of new tasks created by the independent site per unit time and the change trend of the allocation data of the created new tasks to all task execution ends within the independent site. Then, based on this new task creation trend information, predict the number of new tasks assigned to each task execution end within the independent site per unit time. When the number of new tasks assigned exceeds the preset quantity threshold, determine the corresponding task execution end as being in an effective operation state; otherwise, determine the corresponding task execution end as not being in an effective operation state. And monitor the task execution ends in the effective operation state to obtain the task execution thread logs of the task execution ends; among them, the task execution thread logs include all thread records corresponding to each new task received by the task execution end during the processing process. Also, analyze the task execution thread logs to determine the computing resource requirement information of each thread assigned to the task execution end during the execution process, that is, the computing resources that each thread needs to use during the execution process. Compare this computing resource requirement information with the currently available computing resource information of the independent site to determine whether the independent site can provide the type and quantity of computing resources required by this thread; if not, then determine that this thread needs to be docked with a third-party tool to provide additional computing resources to ensure that this thread (i.e., the target thread) can obtain effective auxiliary execution by the third-party tool subsequently.

[0094] Preferably, the virtual node matching and recognition module is used to perform virtual node matching and recognition on all target threads to determine the virtual nodes allowed to be accessed by each target thread within this independent site, including:

[0095] Identify all the connection links between each of the target threads and all the virtual nodes within the independent station, determine the probability of interruption interference events occurring in all the connection links, and then based on the probability of the interruption interference events, determine the virtual nodes that each of the target threads is allowed to access within the independent station;

[0096] The virtual node connection layout generation module is used to determine the connection relationships between all the target threads and the virtual nodes based on the operating states of the virtual nodes that all the target threads are allowed to access, and generate a virtual node connection layout for all the target threads, including:

[0097] Compare the operating available bandwidths of the virtual nodes that all the target threads are allowed to access and the estimated data processing amounts of all the target threads respectively, determine the matching connection relationships between all the target threads and all the allowed-access virtual nodes, so as to generate a virtual node connection layout for all the target threads.

[0098] In the above technical solution, the independent station contains several virtual nodes, and each virtual node can be used to connect the target thread with a third-party tool and serve as a connection intermediary between the target thread and the third-party tool. Since the connection links between the target thread and the virtual node are unstable, the terminals connected to the virtual node are likely to be interfered, and there is a corresponding upper limit to the operating available bandwidth of each virtual node itself. In order to ensure that the target thread can obtain a stable connection with the virtual node and thus achieve a reliable connection with the third-party tool, identify all the connection links between each of the target threads and all the virtual nodes within the independent station, and thereby determine the probability of interruption interference events occurring in all the connection links respectively. If the probability is less than the preset probability threshold, then determine the corresponding virtual node as the virtual node that the target thread is allowed to access within the independent station to ensure the connection stability and continuity between the target thread and the corresponding virtual node. Also, compare the operating available bandwidths of the virtual nodes that all the target threads are allowed to access and the estimated data processing amounts of all the target threads respectively to achieve the matching correspondence between the target threads and the allowed-access virtual nodes, and thereby determine the matching connection relationships between all the target threads and all the allowed-access virtual nodes, so as to generate a virtual node connection layout for all the target threads. In this way, the virtual node connection layout can globally represent the connection correspondence between all the target threads and all the allowed-access virtual nodes.

[0099] Preferably, the virtual node bandwidth configuration module is used to adjust the bandwidth configurations of all the virtual nodes subordinate to the virtual node connection layout based on the execution time domain characteristic information of all the target threads, including:

[0100] Obtain the execution occupancy time interval information of each of all target threads at the task execution end. Based on this execution occupancy time interval information, determine the execution time axis relationship information of all target threads, and use this as the execution time domain feature information; based on this execution time domain feature information, identify the connection overlapping time intervals of all virtual nodes subordinate to the virtual node connection layout, and obtain the longest duration length corresponding to each virtual node connected to two or more target threads; then based on this longest duration length, adjust the available bandwidth allocation value of each virtual node.

[0101] The third-party tool connection module is used to identify the virtual nodes triggered inside the virtual node connection layout, and thus call a third-party tool to connect to the triggered virtual node, including:

[0102] Perform instruction flow identification on all virtual nodes inside the virtual node connection layout, and determine whether the virtual node receives a preset instruction code within a preset time interval. If so, determine that the virtual node is triggered; if not, determine that the virtual node is not triggered; then based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node.

[0103] In the above technical solution, during the operation of the independent station, internal virtual nodes may be connected to multiple target threads at the same time, so as to provide corresponding third-party tool docking for multiple target threads. At this time, the same virtual node needs to handle the third-party tool docking requirements of multiple target threads. To ensure that in the above situation, the virtual node can provide stable and continuous third-party tool docking services for all connected target threads, based on the execution occupancy time interval information of each of all target threads at the task execution end, determine the execution time axis relationship information of all target threads, and then based on this execution time axis relationship information, identify the connection overlapping time intervals of all virtual nodes subordinate to the virtual node connection layout, and obtain the longest duration length corresponding to each virtual node connected to two or more target threads, and use this to adjust the available bandwidth allocation value of each virtual node to ensure that when the virtual node is connected to multiple target threads at the same time period, it can provide sufficient bandwidth connections for all target threads. Also, perform instruction flow identification on all virtual nodes inside the virtual node connection layout, and determine whether the virtual node receives a preset instruction code within a preset time interval, so as to identify the virtual nodes triggered inside the virtual node connection layout, and then based on the preset instruction code received by the triggered virtual node, call a third-party tool to connect to the triggered virtual node to ensure that the target thread obtains a reliable third-party tool docking service.

[0104] Preferably, the third-party tool monitoring module is used to monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool, including:

[0105] Monitor the third-party tool connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tool, and use this as the work behavior information; wherein, the data reading and editing behavior information includes the access interval information for the third-party tool to read data from the target thread through the virtual node and the editing type information for the read data.

[0106] The third-party tool control module is used to judge whether the third-party tool has abnormal behavior based on the work behavior information, so as to perform permission and / or connection control on the third-party tool, including:

[0107] Based on the work behavior information, judge whether the third-party tool has an illegal access to an unauthorized interval behavior and / or an illegal tampering behavior on the read data; when the illegal access to an unauthorized interval behavior occurs, change the data reading permission of the third-party tool for the target thread; when the illegal tampering behavior on the read data occurs, interrupt the connection between the third-party tool and the virtual node.

[0108] In the above technical solution, monitor the third-party tool connected to the triggered virtual node to obtain the data reading and editing behavior information of the third-party tool, and use this to judge whether the third-party tool has an illegal access to an unauthorized interval behavior and / or an illegal tampering behavior on the read data, and accurately identify the data access and editing behavior in the process of the third-party tool providing services for docking with the target thread. Also, when the illegal access to an unauthorized interval behavior occurs, change the data reading permission of the third-party tool for the target thread, and when the illegal tampering behavior on the read data occurs, interrupt the connection between the third-party tool and the virtual node, perform permission and / or connection control on the third-party tool, avoid the third-party tool from making unauthorized operations on the independent station, and improve the operation safety of the independent station.

[0109] As can be seen from the content of the above embodiments, the method and system for docking operation and maintenance and control of third-party tools for the independent website determine the thread support requirement information of the task execution end of the independent website from the task execution thread log, so as to identify the target threads that need to be docked with third-party tools and accurately locate the docking objects of third-party tools; based on the operation status of the virtual nodes allowed to be accessed within the independent website by the target threads, determine the connection relationship between the target threads and the virtual nodes, generate a virtual node connection layout for positioning the docking of third-party tools; based on the execution time domain characteristic information of all target threads, adjust the bandwidth configuration of the virtual nodes, and call the third-party tools to connect to the triggered virtual nodes to ensure the accurate docking of the third-party tools with the target threads and improve the data processing efficiency of the target threads; based on the working behavior information of the third-party tools, determine whether the third-party tools have abnormal behaviors, and perform permission and / or connection control on the third-party tools to prevent the third-party tools from making unauthorized operations on the independent website and improve the operation safety of the independent website.

[0110] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

1. The third-party tool docking operation, maintenance and control method of the independent station is characterized by: It includes the following steps: Step S1, monitoring the task execution end of the independent station to obtain the task execution thread log of the independent station; analyzing the task execution thread log to determine the thread execution requirement information of the task execution end, thereby identifying all target threads that need to be connected with third-party tools; Step S2, performing virtual node matching and identification on all target threads, and determining the virtual nodes that all target threads are allowed to access in the independent station; Based on the operation status of the virtual nodes that all target threads are allowed to access, determine the connection relationship between all target threads and the virtual nodes, and generate a virtual node connection layout for all target threads; Step S3, based on the execution time domain feature information of all target threads, adjusting the bandwidth configuration of all virtual nodes under the virtual node connection layout; identifying the triggered virtual node inside the virtual node connection layout, so as to call a third-party tool to connect to the triggered virtual node, including obtaining the execution occupied time interval information of all target threads at the task execution end, and determining the execution time axis relationship information of all target threads based on the execution occupied time interval information, and taking it as the execution time domain feature information; Based on the execution time domain feature information, the connection overlapping time intervals of all virtual nodes under the virtual node connection layout are identified to obtain the longest duration length corresponding to each virtual node being connected to more than two target threads at the same time; based on the longest duration length, the available bandwidth allocation value of each virtual node is adjusted; the instruction stream of all virtual nodes within the virtual node connection layout is identified to determine whether the virtual node receives a preset instruction code within a preset time interval, and if so, it is determined that the virtual node is triggered; if not, it is determined that the virtual node is not triggered; based on the preset instruction code received by the triggered virtual node, a third-party tool is called to connect to the triggered virtual node; Step S4, monitoring the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool; Based on the work behavior information, it is determined whether the third-party tool has abnormal behavior, so as to perform permission and / or connection management on the third-party tool.

2. The method for operation, maintenance and control of a third-party tool for an independent station according to claim 1, characterized in that: In the step S1, the task execution end of the independent station is monitored to obtain the task execution thread log of the independent station; Analyze the task execution thread log to determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be connected with third-party tools, including: Analyze the task creation log of the independent station to obtain new task creation trend information of the independent station; wherein the new task creation trend information includes the change trend of the number of new tasks created by the independent station per unit time and the change trend of the distribution number of the created new tasks to all task execution terminals within the independent station; Based on the new task creation trend information, identify the task execution end in the independent station that is in an effective running state; monitor the task execution end in an effective running state to obtain the task execution thread log of the task execution end; Analyze the task execution thread log to determine the computing resource requirement information of all threads assigned to the task execution end during the execution process, and use this as the thread execution requirement information; based on the computing resource requirement information, determine whether the independent station can provide the computing resources required by the thread; if not, determine the thread as a target thread that needs to be connected with a third-party tool.

3. The third-party tool docking operation, maintenance and control method of an independent station according to claim 1, characterized in that: In the step S2, virtual node matching and identification are performed on all target threads to determine the virtual nodes that all target threads are allowed to access in the independent station; based on the operation status of the virtual nodes that all target threads are allowed to access, the connection relationship between all target threads and the virtual nodes is determined, and a virtual node connection layout for all target threads is generated, including: Identify all connection links between all target threads and all virtual nodes in the independent station, determine the probability of interruption interference events occurring in all connection links, and then determine the virtual nodes that all target threads are allowed to access in the independent station based on the probability of the interruption interference events; The available operating bandwidths of the virtual nodes that all target threads are allowed to access and the estimated data processing volumes of all target threads are compared to determine the matching connection relationships between all target threads and all virtual nodes that are allowed to access, thereby generating a virtual node connection layout for all target threads.

4. The third-party tool docking operation, maintenance and control method of an independent station according to claim 1, characterized in that: In the step S4, the third-party tool connected to the triggered virtual node is monitored to obtain the working behavior information of the third-party tool; Based on the work behavior information, determining whether the third-party tool has abnormal behavior, thereby performing permission and / or connection management on the third-party tool, includes: Monitor the third-party tool connected to the triggered virtual node to obtain data reading and editing behavior information of the third-party tool as the work behavior information; wherein the data reading and editing behavior information includes access interval information of the third-party tool reading data from the target thread through the virtual node and editing type information of the read data; Based on the work behavior information, determine whether the third-party tool has illegally accessed an unauthorized interval and / or illegally tampered with the read data; when illegal access to an unauthorized interval occurs, change the data reading permission of the third-party tool to the target thread; when illegal tampering of the read data occurs, interrupt the connection between the third-party tool and the virtual node.

5. The third-party tool of the independent station is connected to the operation and maintenance and control system, which is characterized by: include: The task execution end monitoring module is used to monitor the task execution end of the independent station and obtain the task execution thread log of the independent station; A target thread identification module is used to analyze the task execution thread log and determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be connected with a third-party tool; A virtual node matching and identification module, used to perform virtual node matching and identification on all target threads, and determine the virtual nodes that all target threads are allowed to access in the independent station; A virtual node connection layout generation module, used to determine the connection relationship between all target threads and virtual nodes based on the operation status of the virtual nodes that all target threads are allowed to access, and generate a virtual node connection layout for all target threads; A virtual node bandwidth configuration module, used to adjust the bandwidth configuration of all virtual nodes under the virtual node connection layout based on the execution time domain characteristic information of all target threads, including obtaining the execution occupied time interval information of all target threads at the task execution end, and determining the execution time axis relationship information of all target threads based on the execution occupied time interval information, and using this as the execution time domain characteristic information; Based on the execution time domain feature information, the connection overlapping time intervals of all virtual nodes under the virtual node connection layout are identified to obtain the longest duration length corresponding to each virtual node being connected to more than two target threads at the same time; and based on the longest duration length, the available bandwidth allocation value of each virtual node is adjusted; A third-party tool connection module, used to identify the triggered virtual node within the virtual node connection layout, so as to call a third-party tool to connect to the triggered virtual node, including performing instruction stream identification on all virtual nodes within the virtual node connection layout, determining whether the virtual node receives a preset instruction code within a preset time interval, and if so, determining that the virtual node is triggered; if not, determining that the virtual node is not triggered; and then based on the preset instruction code received by the triggered virtual node, calling a third-party tool to connect to the triggered virtual node; A third-party tool monitoring module is used to monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool; The third-party tool management and control module is used to determine whether the third-party tool has abnormal behavior based on the work behavior information, so as to perform permission and / or connection management on the third-party tool.

6. The third-party tool docking operation and maintenance and control system of the independent station according to claim 5, characterized in that: The task execution end monitoring module is used to monitor the task execution end of the independent station to obtain the task execution thread log of the independent station, including: Analyze the task creation log of the independent station to obtain new task creation trend information of the independent station; wherein the new task creation trend information includes the change trend of the number of new tasks created by the independent station per unit time and the change trend of the distribution number of the created new tasks to all task execution terminals within the independent station; Based on the new task creation trend information, identify the task execution end in the independent station that is in an effective running state; monitor the task execution end in an effective running state to obtain the task execution thread log of the task execution end; The target thread identification module is used to analyze the task execution thread log and determine the thread execution requirement information of the task execution end, so as to identify all target threads that need to be connected with a third-party tool, including: Analyze the task execution thread log to determine the computing resource requirement information of all threads assigned to the task execution end during the execution process, and use this as the thread execution requirement information; based on the computing resource requirement information, determine whether the independent station can provide the computing resources required by the thread; if not, determine the thread as a target thread that needs to be connected with a third-party tool.

7. The third-party tool docking operation and maintenance and control system of the independent station according to claim 5, characterized in that: The virtual node matching and identification module is used to perform virtual node matching and identification on all target threads, and determine the virtual nodes that all target threads are allowed to access in the independent station, including: Identify all connection links between all target threads and all virtual nodes in the independent station, determine the probability of interruption interference events occurring in all connection links, and then determine the virtual nodes that all target threads are allowed to access in the independent station based on the probability of the interruption interference events; The virtual node connection layout generation module is used to determine the connection relationship between all target threads and virtual nodes based on the operation status of the virtual nodes that all target threads are allowed to access, and generate the virtual node connection layout for all target threads, including: The available operating bandwidths of the virtual nodes that all target threads are allowed to access and the estimated data processing volumes of all target threads are compared to determine the matching connection relationships between all target threads and all virtual nodes that are allowed to access, thereby generating a virtual node connection layout for all target threads.

8. The third-party tool docking operation and maintenance and control system of the independent station according to claim 5, characterized in that: The third-party tool monitoring module is used to monitor the third-party tool connected to the triggered virtual node to obtain the working behavior information of the third-party tool, including: Monitor the third-party tool connected to the triggered virtual node to obtain data reading and editing behavior information of the third-party tool as the work behavior information; wherein the data reading and editing behavior information includes access interval information of the third-party tool reading data from the target thread through the virtual node and editing type information of the read data; The third-party tool management and control module is used to determine whether the third-party tool has abnormal behavior based on the work behavior information, so as to perform permission and / or connection management on the third-party tool, including: Based on the work behavior information, determine whether the third-party tool has illegally accessed an unauthorized interval and / or illegally tampered with the read data; when illegal access to an unauthorized interval occurs, change the data reading permission of the third-party tool to the target thread; when illegal tampering of the read data occurs, interrupt the connection between the third-party tool and the virtual node.

Images