A remote technical support method and system

Abstract

The application discloses a remote technical support method and system, and relates to the technical field of remote operation and maintenance of industrial Internet of Things.The method comprises the following steps: establishing a remote communication link, collecting running state and link jitter data, and constructing an initial support baseline;calculating a state evolution rate value, and marking an abnormal terminal when the value exceeds a threshold;according to the state evolution rate value and the link jitter data, calling a candidate support instruction from a strategy library;calculating an instruction completeness value of the candidate instruction on the link, and selecting a target support instruction corresponding to the maximum value;issuing the target instruction according to a transmission time sequence constraint and collecting returned final running state data;calculating a state transition value, and only when the value falls within an allowed transition range and the instruction completeness value meets a completeness condition threshold, updating the initial support baseline.The application can effectively improve the accuracy and reliability of remote technical support, reduce the maintenance response time delay of abnormal terminals, and guarantee the stable operation of on-site equipment.

Description

Technical Field

[0001] This invention relates to the field of remote operation and maintenance technology for the Industrial Internet of Things (IIoT), and in particular to a remote technical support method and system. Background Technology

[0002] In Industrial Internet of Things (IIoT) applications, a large number of production devices are distributed across different regions, and their operational status monitoring and fault maintenance heavily rely on remote communication links. Existing remote technical support solutions mostly adopt fixed-cycle inspections or passive response modes, making it difficult to adaptively adjust strategies based on the real-time evolution trends of equipment status and the quality of communication links. When the operating status of the target terminal changes abruptly, traditional methods cannot promptly identify the anomaly and match the optimal support strategy. In scenarios with significant link transmission jitter, the complete delivery of support commands is difficult to guarantee, resulting in a lack of effective quantitative judgment criteria for terminal execution feedback and baseline updates. This leads to problems such as delayed technical support response, strategy mismatch, and baseline drift, seriously affecting the continuous and stable operation of field equipment.

[0003] In existing technologies, remote equipment operation and maintenance typically includes steps such as collecting equipment status data, identifying anomalies, matching support strategies, issuing commands, and providing feedback verification. However, these steps are mostly executed independently, failing to form a link quality adaptive closed loop that integrates link transmission jitter data with the terminal's operational status evolution rate in multiple stages. This makes it difficult to balance the urgency of terminal anomalies with the constraints of link transmission throughout the entire link process, including strategy selection, command optimization, transmission timing adaptation, and baseline update determination. Consequently, technical problems such as high command transmission failure rate, high baseline update misjudgment rate, and large maintenance response latency occur in jittery link scenarios. Summary of the Invention

[0004] This invention proposes a remote technical support method, comprising: S1. The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through the link, stores them in the local data pool according to the timestamp, and pre-sets the remote support strategy library, state evolution rate threshold, allowed transition range, complete condition threshold and transmission timing constraints to construct the initial support baseline of the remote technical support method. S2. Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of the running state data of adjacent timestamps. When the value exceeds the threshold, the target terminal is marked as an abnormal terminal. S3. For abnormal terminals, the system selects driving factors based on the strategy generated by weighted fusion of state evolution rate value and link transmission jitter data, matches and retrieves several candidate support instructions from the remote support strategy library, and gathers them into a candidate instruction set. The candidate support instructions include instruction packet length instruction set. S4. Calculate the ratio between the instruction packet length of each candidate supported instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data. Map the instruction completeness value of each candidate supported instruction according to the relative sorting relationship of each ratio, and determine the candidate supported instruction with the largest instruction completeness value as the target supported instruction. S5. Calculate the transmission timing constraint parameters based on the link transmission jitter data, and send the target support instruction to the abnormal terminal through the remote communication link according to the transmission timing constraint parameters. Collect the final running status data returned by the abnormal terminal after execution, and record the instruction integrity value corresponding to the target support instruction. S6. Calculate the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, write the final running state data into the local data pool to update the initial support baseline; otherwise, keep the initial support baseline unchanged.

[0005] The remote technical support method described above includes the following sub-steps: The system establishes a remote communication link with the target terminal, collects the target terminal's operational status data and link transmission jitter data via this link, stores these data in a local data pool according to timestamps, and pre-sets a remote support strategy library, state evolution rate threshold, allowed transition range, integrity condition threshold, and transmission timing constraints to construct the initial support baseline for the remote technical support method. Multidimensional operational status data is collected by an industrial sensor array deployed on the target terminal. At the same time, link transmission jitter data is collected through the network diagnostic interface of the remote communication link. The multidimensional operational status data and the link transmission jitter data are aligned with a unified timestamp and written into the local data pool. Read historical technical support records from the remote support strategy library and extract the characteristics of state evolution patterns and strategy execution feedback information; Based on the characteristics of state evolution, a state evolution rate threshold is set. Based on the policy execution feedback information, the allowable transition range, complete condition threshold, and transmission timing constraints are set. The above parameters are associated with and stored with the current data in the local data pool to construct an initial support baseline.

[0006] The remote technical support method described above, wherein, based on a state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of adjacent timestamp running state data, and when the value exceeds the threshold, the target terminal is marked as an abnormal terminal, including the following sub-steps: Read multi-dimensional operational status data corresponding to adjacent timestamps from the local data pool, and calculate the difference in operational status data of each dimension between adjacent timestamps; The state evolution rate value is obtained by weighting and summing the difference changes of each dimension according to the preset dimension weight coefficients and then dividing by the time interval between adjacent timestamps. The state evolution rate value is compared with the state evolution rate threshold in the initial support baseline. When the state evolution rate value is greater than the threshold, the target terminal is marked as an abnormal terminal.

[0007] As described above, in a remote technical support method for abnormal terminals, the system selects driving factors based on a strategy generated by weighted fusion of state evolution rate value and link transmission jitter data, matches and retrieves several candidate support instructions from the remote support strategy library, and aggregates them into a candidate instruction set. The candidate support instructions include an instruction packet length instruction set, and includes the following sub-steps: The state evolution rate value of the abnormal terminal is weighted and fused with the jitter amplitude value and jitter frequency value in the link transmission jitter data according to a preset weight to generate a strategy screening driving factor. Based on the strategy selection of driving factors, a strategy matching search is performed in the remote support strategy library. The index range of driving factors corresponding to each historical support strategy in the remote support strategy library is matched with the driving factors selected by the current strategy. Multiple historical support strategies whose index range of driving factors includes the driving factors selected by the current strategy are extracted. The instruction configuration information corresponding to each historical support strategy is analyzed, and candidate support instructions containing the instruction packet length are extracted and compiled into a candidate instruction set.

[0008] The remote technical support method described above includes the following sub-steps: calculating the ratio between the instruction packet length of each candidate support instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data; mapping the instruction completeness value of each candidate support instruction according to the relative ranking relationship of each ratio; and determining the candidate support instruction with the largest instruction completeness value as the target support instruction. Obtain the instruction packet length of each candidate supported instruction in the candidate instruction set, and calculate the adaptation ratio between the length of each instruction packet and the jitter amplitude value in the link transmission jitter data to obtain the link adaptation ratio value of each candidate supported instruction. Based on the relative order of the link adaptation ratio values ​​of each candidate supported instruction in the candidate instruction set, and combined with the preset integrity mapping relationship, the instruction integrity value of each candidate supported instruction is determined. The instruction integrity values ​​of each candidate support instruction are sorted in descending order. The candidate support instruction corresponding to the instruction integrity value at the top of the list is determined as the target support instruction, and its instruction packet length and instruction integrity value are recorded.

[0009] The remote technical support method described above includes the following sub-steps: calculating transmission timing constraint parameters based on link transmission jitter data; sending the target support instruction to the abnormal terminal via the remote communication link according to the transmission timing constraint parameters; collecting the final running status data returned by the abnormal terminal after execution; and recording the instruction integrity value corresponding to the target support instruction. The transmission timing constraint parameters are calculated based on the jitter amplitude and jitter duration in the jitter data of the link transmission. The transmission timing constraint parameters include the minimum transmission interval between adjacent data packets and the retransmission timeout time. The target support instruction is split into multiple data packets according to the minimum transmission interval between adjacent data packets in the transmission timing constraint parameters. The retransmission waiting time of each data packet is set according to the retransmission timeout time in the transmission timing constraint parameters. The data packets are then sent to the abnormal terminal in sequence via the remote communication link. The abnormal terminal receives all data packets, reassembles them, and then executes the target support instruction. Receive the final running status data returned after the abnormal terminal executes, associate the final running status data with the instruction integrity value of the target supported instruction, and store it in the local data pool.

[0010] The remote technical support method described above includes calculating the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowable transition range and the instruction integrity value meets the integrity condition threshold, is the final running state data written to the local data pool to update the initial support baseline; otherwise, the initial support baseline remains unchanged. This method includes the following sub-steps: Read the multidimensional initial running status data corresponding to the initial support baseline from the local data pool, calculate the absolute value of the difference between the final running status data and the initial running status data in each dimension, and sum them according to the preset dimension weight coefficients to obtain the state transition value. Determine whether the state transition value falls within the allowed transition range, and at the same time determine whether the instruction integrity value meets the integrity condition threshold. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool, and the initial running state data in the initial support baseline is replaced with the final running state data to complete the update of the initial support baseline; otherwise, the initial support baseline remains unchanged.

[0011] The present invention also proposes a remote technical support system, comprising: Communication and Baseline Construction Module: The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through this link, stores them in the local data pool according to timestamps, and pre-sets a remote support strategy library, state evolution rate threshold, allowed transition range, complete condition threshold and transmission timing constraints to construct the initial support baseline for remote technical support methods. Anomaly detection module: Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of the running state data of adjacent timestamps. When the value exceeds the threshold, the target terminal is marked as an abnormal terminal. Strategy matching and instruction selection module: For abnormal terminals, the system uses a strategy screening driving factor generated by weighted fusion of state evolution rate value and link transmission jitter data to match and retrieve several candidate support instructions from the remote support strategy library, which are then aggregated into a candidate instruction set. The candidate support instructions include instruction packet length instruction set; the ratio between the instruction packet length of each candidate support instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data is calculated; the instruction completeness value of each candidate support instruction is mapped according to the relative ranking relationship of each ratio; and the candidate support instruction with the largest instruction completeness value is determined as the target support instruction. Command issuance and feedback acquisition module: Calculates transmission timing constraint parameters based on link transmission jitter data, issues the target supported command to the abnormal terminal via remote communication link according to the transmission timing constraint parameters, collects the final running status data returned by the abnormal terminal after execution, and records the command integrity value corresponding to the target supported command; Baseline update determination module: Calculates the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool to update the initial support baseline; otherwise, the initial support baseline remains unchanged.

[0012] The beneficial effects achieved by this invention are as follows: This invention incorporates link transmission jitter data into the entire remote technical support process, forming an adaptive closed loop for link quality. The system uses a weighted fusion strategy based on state evolution rate values ​​and link jitter data to select driving factors, balancing the urgency of terminal anomalies with the degree of link transmission constraints when retrieving candidate instructions. It obtains instruction completeness values ​​by mapping the ratio of instruction packet length to jitter amplitude, and uses relative sorting relationships to eliminate absolute dimensional differences under different link scenarios, selecting the optimal target support instruction. Based on link jitter, it dynamically calculates transmission timing constraint parameters and adaptively completes instruction issuance to improve link quality. Finally, it uses both instruction completeness and state transition amount as conditions to determine baseline updates, supplemented by an anomaly marking and logging mechanism to avoid misjudgments and invalid baseline updates caused by transmission distortion.

[0013] This solution addresses the pain point of correct strategies but transmission failures in remote support, improving the accuracy, reliability, and response efficiency of technical support, and ensuring stable equipment operation. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0015] Figure 1 This is a flowchart of a remote technical support method provided in an embodiment of this application.

[0016] Figure 2 This is a schematic diagram of a remote technical support system provided in an embodiment of this application. Detailed Implementation

[0017] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] Example 1 like Figure 1 As shown in the figure, an embodiment of this application provides a remote technical support method, including: Step S1: The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through the link, stores them in the local data pool according to the timestamp, and pre-sets the remote support strategy library, state evolution rate threshold, allowed transition range, complete condition threshold and transmission timing constraints to construct the initial support baseline of the remote technical support method. Specifically, multi-dimensional operational status data is collected by an industrial sensor array deployed on the target terminal, and link transmission jitter data is obtained through the network diagnostic interface of the remote communication link. Both types of data are aligned with a unified timestamp and stored in a local data pool. Historical technical support records are read from a pre-set remote support strategy library, and state evolution patterns and strategy execution feedback information are extracted. Based on the extracted patterns, a state evolution rate threshold is set, and based on the feedback information, allowable transition ranges, integrity condition thresholds, and transmission timing constraints are set. These parameters are then associated with and stored with the current data in the local data pool to form an initial support baseline. This process includes the following sub-steps: Step S11: Collect multi-dimensional operating status data through the industrial sensor array deployed on the target terminal, and at the same time collect link transmission jitter data through the network diagnostic interface of the remote communication link. Align the multi-dimensional operating status data and the link transmission jitter data with a unified timestamp and write them into the local data pool. The system deploys sensor acquisition units at key measurement points of the target terminal. These units include temperature, vibration, current, and voltage sensors. Each sensor synchronously acquires its corresponding operating status parameters at a preset sampling period, forming multi-dimensional operating status data. Simultaneously, the system sends probe messages to the peer of the link and receives response messages according to a preset diagnostic period via the network diagnostic interface of the remote communication link. The deviation of the round-trip time delay is recorded as the jitter amplitude value, and the number of jitter amplitude changes per unit time is recorded as the jitter frequency value.

[0019] When collecting the two types of data mentioned above, the system assigns a unified timestamp label based on the system clock to each data set. It also strictly aligns the multi-dimensional operational status data with the link transmission jitter data according to the timestamp, eliminating clock deviations introduced by asynchronous collection times. The aligned data is then written to the local data pool in chronological order. The local data pool uses a circular buffer structure, storing all data within a preset time period in chronological order. When the storage space reaches its limit, the system automatically overwrites the oldest historical data to maintain continuous updates to the data pool.

[0020] Step S12: Read historical technical support records from the remote support strategy library and extract the characteristics of state evolution and strategy execution feedback information; Based on the sequence of state evolution rate values ​​within each sliding time window under historical normal operating conditions, the upper 95th percentile is taken as the state evolution rate threshold. The system sets the allowable transition range based on the lower and upper quantiles of the state transition value distribution in historical successful support cases, sets the completeness condition threshold based on the historical complete instruction transmission statistics ratio, and sets the transmission timing constraint calculation parameters based on the extreme values ​​of link jitter statistics. These thresholds, ranges, and parameters are associated and stored with the current operating status data in the local data pool to form the initial support baseline.

[0021] Step S13: Set the state evolution rate threshold according to the characteristics of state evolution law, set the allowable transition range, complete condition threshold and transmission timing constraints according to the policy execution feedback information, and store the above parameters with the current data in the local data pool to build the initial support baseline. Based on the extracted state evolution characteristics, the differential change of each dimension is calculated window by window for the multidimensional operating state data of each sampling time under historical normal operating conditions. The weighted sum is obtained by dividing by the corresponding time interval according to the preset dimension weight coefficient, and the historical state evolution rate value sequence is obtained. The 95th percentile of this sequence is taken as the state evolution rate threshold to distinguish between normal operation fluctuations and abnormal state jumps of the terminal.

[0022] Step S2: Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of the running state data of adjacent timestamps. When the value exceeds the threshold, the target terminal is marked as an abnormal terminal. Specifically, multi-dimensional operational status data corresponding to adjacent timestamps are read from the local data pool, the differential change of each dimension is calculated, and the state evolution rate value is obtained by weighting and summing according to the preset dimension weight coefficients and dividing by the time interval. This value is compared with the state evolution rate threshold in the initial support baseline. If it exceeds the threshold, the target terminal is marked as an abnormal terminal. The specific steps include the following: Step S21: Read the multi-dimensional running status data corresponding to adjacent timestamps from the local data pool, and calculate the difference in running status data of each dimension between adjacent timestamps; Based on the current acquisition time, the system extracts two sets of multi-dimensional operational status data from the local data pool, including the current time and the previous adjacent time. For each set of data, the system extracts corresponding values ​​according to dimensions such as temperature, vibration, current, and voltage. The system calculates the difference between adjacent timestamps for each dimension to obtain the instantaneous change amplitude of the operational status data for each dimension.

[0023] Step S22: Sum the difference changes of each dimension according to the preset dimension weight coefficients, and then divide by the time interval between adjacent timestamps to obtain the state evolution rate value. Based on the impact of each operational state dimension of the target terminal on the overall system stability, a corresponding weight coefficient is pre-assigned to each dimension. Dimensions with a greater impact on terminal stability are assigned higher weight coefficients, while those with a smaller impact are assigned lower weight coefficients. The system multiplies the differential changes of each dimension by their respective weight coefficients and then sums them to obtain a weighted differential sum. The time interval between adjacent timestamps is read, and the state evolution rate is expressed using the following formula: in, This represents the state evolution rate value; The time interval between adjacent timestamps is determined by the difference between two adjacent sampling times recorded by the system clock; This represents the total number of dimensions in the multidimensional operational status data; Indicates the first Preset dimension weight coefficients; Indicates the first Dimensional operational status data at time The sampled values; Indicates the first The average differential change of dimensional operation status data under historical normal operating conditions; It represents the smallest positive number that is not divisible by zero.

[0024] Step S23: Compare the state evolution rate value with the state evolution rate threshold in the initial support baseline. When the state evolution rate value is greater than the threshold, mark the target terminal as an abnormal terminal. The system reads the state evolution rate threshold stored in the initial support baseline and compares the state evolution rate value calculated in step S22 with this threshold. If the state evolution rate value is greater than the state evolution rate threshold, it indicates that the change in the operating state of the target terminal between adjacent sampling times exceeds the maximum fluctuation range under historical normal operating conditions, i.e., the terminal has experienced an abnormal state transition. The target terminal is marked as an abnormal terminal, and the subsequent candidate support instruction matching and screening process is triggered. If the state evolution rate value does not exceed the state evolution rate threshold, it is determined that the current operating state of the target terminal is within the normal fluctuation range, and the normal monitoring state is maintained.

[0025] Step S3: For abnormal terminals, the system filters driving factors based on the strategy generated by weighted fusion of state evolution rate value and link transmission jitter data, matches and retrieves several candidate support instructions from the remote support strategy library, and gathers them into a candidate instruction set. The candidate support instructions include instruction packet length instruction set. Specifically, the state evolution rate value of the abnormal terminal is weighted and fused with the jitter amplitude value and jitter frequency value in the link transmission jitter data according to a preset weight to generate a strategy screening driving factor. This driving factor is then matched with the driving factor index range corresponding to each historical support strategy in the remote support strategy library. Historical support strategies whose index range contains the current driving factor are extracted, their instruction configuration information is parsed, and candidate support instructions containing the instruction packet length are extracted and aggregated into a candidate instruction set. The specific steps include the following: Step S31: The state evolution rate value of the abnormal terminal is weighted and fused with the jitter amplitude value and jitter frequency value in the link transmission jitter data according to a preset weight to generate a strategy screening driving factor; The system reads the state evolution rate value corresponding to the abnormal terminal from the local data pool, and simultaneously extracts the jitter amplitude and frequency values ​​of the current link from the link transmission jitter data. The system presets fusion weight coefficients for these three parameters, with each weight coefficient determined based on its importance in characterizing the urgency of the terminal abnormality and the constraint of link transmission. Specifically, the weight coefficient for the state evolution rate value reflects the impact of the speed of terminal state deterioration on strategy selection; the weight coefficient for the jitter amplitude value reflects the constraint of instantaneous link fluctuations on the transmission of large data packet commands; and the weight coefficient for the jitter frequency value reflects the impact of the frequency of link fluctuations on the continuous transmission of commands. The following formula represents the strategy selection driving factor: in, This indicates the strategy for selecting driving factors; This represents the preset fusion weighting coefficients, which are pre-calibrated by technical personnel based on the importance of each parameter in characterizing the urgency of terminal anomalies and the degree of link transmission constraints, and satisfy the following conditions: ; This represents the state evolution rate value of the abnormal terminal; The reference saturation threshold representing the state evolution rate is determined by the statistical upper quartile of the state evolution rate values ​​in historical failure cases; This represents the jitter amplitude value in the jitter data transmitted over the link; A reference saturation threshold representing the jitter amplitude; This represents the jitter frequency value in the jitter data transmitted through the link. The reference saturation threshold represents the jitter frequency.

[0026] Step S32: Based on the strategy selection of driving factors, perform strategy matching and retrieval in the remote support strategy library, match the index range of driving factors corresponding to each historical support strategy in the remote support strategy library with the current strategy selection of driving factors, and extract multiple historical support strategies whose index range of driving factors includes the current strategy selection of driving factors. Each historical support strategy stored in the remote support strategy library is pre-associated with a driving factor index range. This index range is defined by the minimum and maximum values ​​of the driving factors corresponding to the strategy in historical successful application cases, reflecting the range of abnormal urgency and link conditions to which the strategy is applicable. The driving factors selected in step S31 are sequentially compared with the driving factor index ranges of each historical support strategy to determine whether the current driving factor falls between the lower and upper limits of the range. If it does, the historical support strategy is marked as a matching strategy. After traversing all historical support strategies, the system extracts all historical support strategies whose driving factor index ranges contain the current strategy's selected driving factor as matching results.

[0027] Step S33: Parse the instruction configuration information corresponding to each historical support strategy, extract candidate support instructions containing instruction packet length, and collect them into a candidate instruction set; The system reads the instruction configuration information corresponding to each matching strategy, including the operation content of the specific supported instructions for that strategy, the instruction's data packet length, and the parameter configuration required for instruction execution. The system extracts the instruction packet length from the instruction configuration information of each matching strategy and includes the corresponding supported instructions in the candidate supported instructions. All extracted candidate supported instructions are compiled into a candidate instruction set. Each candidate supported instruction in the set is associated with and its instruction packet length information, for use in subsequent steps to calculate the link adaptation ratio and instruction integrity value.

[0028] Step S4: Calculate the ratio between the instruction packet length of each candidate supported instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data. Map the instruction completeness value of each candidate supported instruction according to the relative sorting relationship of each ratio, and determine the candidate supported instruction with the largest instruction completeness value as the target supported instruction. Specifically, the instruction packet length of each candidate supported instruction in the candidate instruction set is obtained, and an adaptation ratio is calculated with the jitter amplitude value in the link transmission jitter data to obtain the link adaptation ratio value of each candidate supported instruction. Based on the relative order of each link adaptation ratio value in the candidate instruction set, and combined with the preset integrity mapping relationship, the instruction integrity value of each candidate supported instruction is determined. The candidate supported instruction with the largest integrity value is determined as the target supported instruction, and its instruction packet length and instruction integrity value are recorded. The specific steps include the following: Step S41: Obtain the instruction packet length of each candidate supported instruction in the candidate instruction set, and calculate the adaptation ratio value between the length of each instruction packet and the jitter amplitude value in the link transmission jitter data to obtain the link adaptation ratio value of each candidate supported instruction. The instruction packet length corresponding to each candidate supported instruction is read one by one from the candidate instruction set, while the current jitter amplitude value is read from the link transmission jitter data. The link adaptation ratio value of each candidate supported instruction is calculated, whereby the link adaptation ratio value is determined by the ratio of the instruction packet length of the candidate supported instruction to the link jitter amplitude value. This link adaptation ratio value quantifies, in numerical form, the impact of the packet size of the candidate instruction on transmission integrity under a given link jitter amplitude. The larger the ratio, the less susceptible the instruction packet length is to fragmentation loss due to jitter interference relative to the current link jitter conditions.

[0029] Step S42: Based on the relative sorting relationship of the link adaptation ratio of each candidate supported instruction in the candidate instruction set, and combined with the preset integrity mapping relationship, determine the instruction integrity value of each candidate supported instruction. The link adaptation ratios of each candidate supported instruction in the candidate instruction set are sorted in descending order to obtain the ranking of each ratio within the candidate instruction set. Based on a preset integrity mapping relationship, each ranking is mapped to the corresponding instruction integrity value. The instruction integrity value of each candidate supported instruction is expressed by the following formula: in, Indicates the first The instruction completeness value of each candidate supporting instruction; Indicates the lower limit of the instruction integrity value; Indicates the upper limit of instruction integrity value; This represents the kurtosis control coefficient, and The value of and the size of the candidate instruction set Positive correlation The larger The larger the value, the better to maintain the integrity and distinguishability of the sorting front instruction among a large number of candidate instructions; Indicates the total number of candidate supported instructions in the candidate instruction set; Indicates the first The link adaptation ratio of each candidate support instruction is ranked in the candidate instruction set.

[0030] The discrete sorting positions are mapped to a continuous integrity range using an exponential function. A higher sorting position indicates a larger link adaptation ratio, better adaptation between instruction packet length and link jitter amplitude, and a higher corresponding instruction integrity value. Simultaneously, through... By controlling the steepness of the mapping curve, the influence of the difference in the size of different candidate instruction sets on the dimension of the completeness value is eliminated, so that the instruction completeness value can accurately reflect the relative superiority and inferiority relationship between each candidate instruction under any candidate instruction set size.

[0031] Step S43: Sort the instruction integrity values ​​of each candidate support instruction in descending order, determine the candidate support instruction corresponding to the instruction integrity value at the top of the list as the target support instruction, and record its instruction packet length and instruction integrity value. Sort all candidate support instructions in the candidate instruction set in descending order of instruction integrity value. Select the candidate support instruction with the highest integrity value at the top of the sorted list as the target support instruction. Record the instruction packet length and instruction integrity value corresponding to the target support instruction in the local data pool.

[0032] Step S5: Calculate the transmission timing constraint parameters based on the link transmission jitter data, send the target support instruction to the abnormal terminal via the remote communication link according to the transmission timing constraint parameters, collect the final running status data returned by the abnormal terminal after execution, and record the instruction integrity value corresponding to the target support instruction. Specifically, based on the jitter amplitude and duration in the jitter data transmitted through the link, transmission timing constraint parameters are calculated, including the minimum transmission interval between adjacent data packets and the retransmission timeout. The target support instruction is split into multiple data packets according to this maximum burst transmission interval, and the retransmission waiting time for each data packet is set according to the retransmission timeout. These packets are then sequentially sent to the abnormal terminal via the remote communication link. The terminal receives all data packets, reassembles them, and executes them. The final running status data returned by the abnormal terminal after execution is received and associated with the instruction integrity value of the target support instruction, stored in the local data pool. This process includes the following sub-steps: Step S51: Calculate the transmission timing constraint parameters based on the jitter amplitude value and jitter duration in the link transmission jitter data. The transmission timing constraint parameters include the minimum transmission interval between adjacent data packets and the retransmission timeout time. The current jitter amplitude, jitter duration, and jitter frequency are read from the link transmission jitter data. The jitter duration characterizes the length of time the link remains in a high-jitter state. Based on these parameters, the link's fluctuation characteristics in the time dimension are evaluated, and the transmission timing constraints applicable to the current link condition are calculated. The minimum transmission interval between adjacent data packets is expressed by the following formula: in, Indicates the minimum interval between adjacent data packets; This represents the minimum allowed transmission interval, which is determined by the physical transmission capacity of the communication link; This represents the proportional adjustment coefficient; The jitter amplitude value in the jitter data transmitted through the link is obtained by step S11; This represents the power-law exponent, used to adjust the rate of increase of the transmission interval under long-term jitter. The duration of the jitter is indicated by statistics obtained from the network diagnostic interface in step S11. Indicates the base time unit; This represents the power-law adjustment parameter, used to control the rate at which the transmission interval increases with the duration of jitter.

[0033] The greater the amplitude and the longer the duration of the shaking, the better. The larger the setting value, the more the logarithmic compression term avoids linear explosion of the transmission interval when the jitter duration is too long, enabling the transmission process of the target support command to adaptively adapt to the time-varying jitter characteristics of the current link.

[0034] The retransmission timeout period is expressed by the following formula: in, Indicates the retransmission timeout period; Indicates the minimum retransmission timeout; This represents the proportional adjustment coefficient; Indicates the duration of the jitter; Represents the hyperbolic cosine function; Indicates the amplitude of jitter; A reference saturation threshold representing the jitter amplitude; This represents the jitter frequency correction factor; Indicates the jitter frequency value; This indicates a reference value for the jitter frequency; It represents the smallest positive number that is not divisible by zero.

[0035] The retransmission timeout is related to the statistical extreme value of the link jitter duration, ensuring that the retransmission timeout covers the duration of the link jitter and avoiding invalid retransmissions triggered by brief link recovery delays. The system outputs the minimum transmission interval between adjacent data packets and the retransmission timeout as transmission timing constraint parameters.

[0036] Step S52: According to the minimum transmission interval between adjacent data packets in the transmission timing constraint parameters, the target support instruction is split into multiple data packets. The retransmission waiting time of each data packet is set according to the retransmission timeout time in the transmission timing constraint parameters. The data packets are then sent to the abnormal terminal in sequence through the remote communication link. The abnormal terminal receives all data packets, reassembles them, and then executes the target support instruction. Based on the total data volume of the target support command and the maximum payload length of a single transmission on the remote communication link, it is split into multiple data packets. Each data packet carries a sequence number identifier and a total packet count identifier for reassembly by the terminal upon receipt. The transmission time of each data packet is controlled according to the minimum transmission interval between adjacent data packets, ensuring that the transmission time interval between adjacent data packets is not less than the maximum burst transmission interval value. A retransmission waiting time is set for each data packet, which is equal to the retransmission timeout. If no acknowledgment response is received from the abnormal terminal within this time limit after the data packet is sent, the system automatically triggers the retransmission of the data packet. The data packets are sequentially sent to the abnormal terminal via the remote communication link. After receiving all data packets, the abnormal terminal verifies and reassembles them according to the sequence number identifier and total packet count identifier carried in the data packets, recovers the complete target support command, and executes the corresponding support operation.

[0037] Step S53: Receive the final running status data returned after the abnormal terminal executes, and associate the final running status data with the instruction integrity value of the target supported instruction and store it in the local data pool. After the target support instruction is executed on the abnormal terminal, the terminal collects multi-dimensional operational status data again and uploads this data to the system via a remote communication link as the final operational status data. After receiving the final operational status data, the system establishes a correlation between it and the instruction integrity value corresponding to the target support instruction recorded in step S43, and stores them together in the local data pool using a unified timestamp as an index.

[0038] Step S6: Calculate the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowable transition range and the instruction integrity value meets the integrity condition threshold, write the final running state data into the local data pool to update the initial support baseline; otherwise, keep the initial support baseline unchanged. Specifically, the multi-dimensional initial running status data corresponding to the initial support baseline is read from the local data pool. The absolute value of the difference between the final running status data and the initial running status data in each dimension is calculated, and the values ​​are weighted and summed according to preset dimension weight coefficients to obtain the state transition value. Simultaneously, it is determined whether the transition value falls within the allowable transition range and whether the instruction integrity value meets the integrity condition threshold. Only when both conditions are met is the final running status data written to the local data pool, replacing the initial running status data in the initial support baseline, thus completing the baseline update; otherwise, the original baseline remains unchanged. This process includes the following sub-steps: Step S61: Read the multi-dimensional initial running status data corresponding to the initial support baseline from the local data pool, calculate the absolute value of the difference between the final running status data and the initial running status data in each dimension, and sum them according to the preset dimension weight coefficient to obtain the state transition value. The multi-dimensional initial operating state data corresponding to the initial support baseline stored in step S1 is read from the local data pool, and the final operating state data stored in step S53 is also read. The absolute values ​​of the differences between the two sets of data are calculated one by one according to dimensions such as temperature, vibration, current, and voltage to obtain the change magnitude of each dimension. Based on the degree of influence of each dimension on terminal stability, a weighted sum of the absolute values ​​of the differences in each dimension is performed using preset dimension weighting coefficients. The state transition magnitude is expressed by the following formula: in, This represents the value of a state transition. This represents the total number of dimensions in the multidimensional operational status data; Indicates the index parameter; Indicates the first Preset dimension weight coefficients; Indicates the first The final operational status data of the dimension; Indicates the first Initial running status data of the dimension; Indicates the first Standard deviation of maintenance status data under historical normal operating conditions; It represents the smallest positive number that is not divisible by zero.

[0039] Step S62: Determine whether the state transition value falls within the allowed transition range, and at the same time determine whether the instruction integrity value meets the integrity condition threshold. The system reads the upper and lower limits of the pre-set allowed transition range from the initial support baseline and determines whether the state transition value calculated in step S61 is greater than or equal to the lower limit and less than or equal to the upper limit. Simultaneously, the system reads the instruction integrity value corresponding to this support process from the local data pool and compares it with the preset integrity condition threshold in the initial support baseline to determine whether the instruction integrity value is greater than or equal to the integrity condition threshold. These two conditions together constitute the admission criteria for baseline updates. The allowed transition range ensures that the state change is within a reasonable and valid range, excluding state abrupt changes caused by abnormal interference; the integrity condition threshold ensures reliable transmission, excluding execution failures caused by corrupted instruction transmission.

[0040] Step S63: Only when the state transition value falls within the allowable transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool, and the initial running state data in the initial support baseline is replaced with the final running state data to complete the update of the initial support baseline; otherwise, the initial support baseline remains unchanged. If both judgment conditions in step S62 are met, the remote support process is considered valid. This means the target support command was successfully executed on the abnormal terminal, the terminal state underwent a reasonable transition within the expected range, and the command maintained sufficient integrity during transmission. The received final operating status data is written to the storage area of ​​the initial support baseline in the local data pool, replacing the original initial operating status data. If either of the above judgment conditions is not met, the support process is deemed abnormal. The system discards the collected final operating status data, maintains all parameters in the original initial support baseline unchanged, and records an anomaly log for the next round of remote support.

[0041] Example 2 like Figure 2 As shown, Embodiment 2 of this application provides a remote technical support system, including: Communication and Baseline Construction Module 21: The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through this link, stores them in a local data pool according to timestamps, and pre-sets a remote support strategy library, state evolution rate threshold, allowed transition range, integrity condition threshold, and transmission timing constraints to construct the initial support baseline for remote technical support methods; including the following sub-modules: Data acquisition and alignment submodule 211: Collects multi-dimensional operating status data through an industrial sensor array deployed on the target terminal, and simultaneously collects link transmission jitter data through the network diagnostic interface of the remote communication link. The multi-dimensional operating status data and the link transmission jitter data are aligned with a unified timestamp and written into the local data pool. Historical record reading and feature extraction submodule 212: Reads historical technical support records from the remote support strategy library, extracts state evolution pattern features and strategy execution feedback information; Baseline parameter setting and construction submodule 213: Set the state evolution rate threshold according to the characteristics of state evolution law, set the allowable transition range, complete condition threshold and transmission timing constraints according to policy execution feedback information, associate and store the above parameters with the current data in the local data pool, and construct the initial support baseline; Anomaly Detection Module 22: Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of adjacent timestamp running state data. When this value exceeds the threshold, the target terminal is marked as an abnormal terminal; it includes the following sub-modules: Differential Change Calculation Submodule 221: Reads multi-dimensional running status data corresponding to adjacent timestamps from the local data pool and calculates the differential change of running status data in each dimension between adjacent timestamps; State evolution rate calculation submodule 222: The state evolution rate value is obtained by weighting and summing the difference changes of each dimension according to the preset dimension weight coefficient and then dividing by the time interval between adjacent timestamps. Anomaly marking and determination submodule 223: compares the state evolution rate value with the state evolution rate threshold in the initial support baseline. When the state evolution rate value is greater than the threshold, the target terminal is marked as an abnormal terminal. Strategy Matching and Instruction Optimization Module 23: For abnormal terminals, the system uses a strategy screening driving factor generated by weighted fusion of state evolution rate value and link transmission jitter data to match and retrieve several candidate support instructions from the remote support strategy library, which are then aggregated into a candidate instruction set. The candidate support instructions include instruction packet length instructions. The system calculates the ratio between the instruction packet length of each candidate support instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data. Based on the relative ranking relationship of each ratio, the system maps the instruction completeness value of each candidate support instruction, and determines the candidate support instruction with the largest instruction completeness value as the target support instruction. This module includes the following sub-modules: Strategy screening driver factor generation submodule 231: The state evolution rate value of the abnormal terminal is weighted and fused with the jitter amplitude value and jitter frequency value in the link transmission jitter data according to a preset weight to generate the strategy screening driver factor; Strategy matching and retrieval submodule 232: Based on the strategy selection driving factor, perform strategy matching and retrieval in the remote support strategy library, match the index range of the driving factor corresponding to each historical support strategy in the remote support strategy library with the current strategy selection driving factor, and extract multiple historical support strategies whose driving factor index range contains the current strategy selection driving factor. Candidate instruction aggregation submodule 233: parses the instruction configuration information corresponding to each historical supported strategy, extracts candidate supported instructions including instruction packet length, and aggregates them into a candidate instruction set; Link adaptation ratio calculation submodule 234: obtains the instruction packet length of each candidate supported instruction in the candidate instruction set, calculates the adaptation ratio between the length of each instruction packet and the jitter amplitude value in the link transmission jitter data, and obtains the link adaptation ratio value of each candidate supported instruction. Instruction integrity value determination submodule 235: Based on the relative sorting relationship of the link adaptation ratio of each candidate supported instruction in the candidate instruction set, and combined with the preset integrity mapping relationship, determine the instruction integrity value of each candidate supported instruction; Target Support Instruction Determination Submodule 236: Sort the instruction completeness values ​​of each candidate support instruction in descending order, determine the candidate support instruction corresponding to the instruction completeness value at the top of the list as the target support instruction, and record its instruction packet length and instruction completeness value; Command Issuance and Feedback Acquisition Module 24: Calculates transmission timing constraint parameters based on link transmission jitter data, issues the target support command to the abnormal terminal via the remote communication link according to the transmission timing constraint parameters, collects the final running status data returned by the abnormal terminal after execution, and records the command integrity value corresponding to the target support command; includes the following sub-modules: Timing parameter generation submodule 241: Calculates transmission timing constraint parameters based on the jitter amplitude value and jitter duration in the link transmission jitter data. The transmission timing constraint parameters include the minimum transmission interval between adjacent data packets and the retransmission timeout time. Instruction splitting and distribution submodule 242: The target support instruction is split into multiple data packets according to the minimum transmission interval between adjacent data packets in the transmission timing constraint parameters. The retransmission waiting time of each data packet is set according to the retransmission timeout time in the transmission timing constraint parameters. The instructions are then distributed to the abnormal terminal in sequence via the remote communication link. The abnormal terminal receives all data packets, reassembles them, and then executes the target support instruction. Final status data receiving and storage submodule 243: Receives the final running status data returned after the abnormal terminal is executed, and associates the final running status data with the instruction integrity value of the target supported instruction and stores it in the local data pool; Baseline Update Determination Module 25: Calculates the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowable transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool to update the initial support baseline; otherwise, the initial support baseline remains unchanged. This includes the following sub-modules: State transition value calculation submodule 251: Reads the multi-dimensional initial running state data corresponding to the initial support baseline from the local data pool, calculates the absolute value of the difference between the final running state data and the initial running state data in each dimension, and obtains the state transition value by weighting and summing according to the preset dimension weight coefficients. Dual-condition determination submodule 252: Determines whether the state transition value falls within the allowed transition range, and at the same time determines whether the instruction integrity value meets the integrity condition threshold. Baseline update execution submodule 253: Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool, and the initial running state data in the initial support baseline is replaced with the final running state data to complete the update of the initial support baseline; otherwise, the initial support baseline remains unchanged.

Claims

1. A remote technical support method, characterized in that, include: S1. The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through the link, stores them in the local data pool according to the timestamp, and pre-sets the remote support strategy library, state evolution rate threshold, allowed transition range, complete condition threshold and transmission timing constraints to construct the initial support baseline of the remote technical support method. S2. Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of the running state data of adjacent timestamps. When the value exceeds the threshold, the target terminal is marked as an abnormal terminal. S3. For abnormal terminals, the system selects driving factors based on the strategy generated by weighted fusion of state evolution rate value and link transmission jitter data, matches and retrieves several candidate support instructions from the remote support strategy library, and gathers them into a candidate instruction set. The candidate support instructions include instruction packet length instruction set. S4. Calculate the ratio between the instruction packet length of each candidate supported instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data. Map the instruction completeness value of each candidate supported instruction according to the relative sorting relationship of each ratio, and determine the candidate supported instruction with the largest instruction completeness value as the target supported instruction. S5. Calculate the transmission timing constraint parameters based on the link transmission jitter data, and send the target support instruction to the abnormal terminal through the remote communication link according to the transmission timing constraint parameters. Collect the final running status data returned by the abnormal terminal after execution, and record the instruction integrity value corresponding to the target support instruction. S6. Calculate the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, write the final running state data into the local data pool to update the initial support baseline; otherwise, keep the initial support baseline unchanged.

2. The remote technical support method according to claim 1, characterized in that, The system establishes a remote communication link with the target terminal, collects the target terminal's operational status data and link transmission jitter data through this link, stores them in a local data pool according to timestamps, and pre-sets a remote support strategy library, state evolution rate threshold, allowed transition range, integrity condition threshold, and transmission timing constraints to construct an initial support baseline for the remote technical support method, including the following sub-steps: Multidimensional operational status data is collected by an industrial sensor array deployed on the target terminal. At the same time, link transmission jitter data is collected through the network diagnostic interface of the remote communication link. The multidimensional operational status data and the link transmission jitter data are aligned with a unified timestamp and written into the local data pool. Read historical technical support records from the remote support strategy library, and extract the characteristics of state evolution patterns and strategy execution feedback information; Based on the characteristics of state evolution, a state evolution rate threshold is set. Based on the policy execution feedback information, the allowable transition range, complete condition threshold, and transmission timing constraints are set. The above parameters are associated with and stored with the current data in the local data pool to construct an initial support baseline.

3. The remote technical support method according to claim 1, characterized in that, Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of adjacent timestamp running state data. When this value exceeds the threshold, the target terminal is marked as an abnormal terminal, including the following sub-steps: Read multi-dimensional operational status data corresponding to adjacent timestamps from the local data pool, and calculate the difference in operational status data of each dimension between adjacent timestamps; The state evolution rate value is obtained by weighting and summing the difference changes of each dimension according to the preset dimension weight coefficients and then dividing by the time interval between adjacent timestamps. The state evolution rate value is compared with the state evolution rate threshold in the initial support baseline. When the state evolution rate value is greater than the threshold, the target terminal is marked as an abnormal terminal.

4. The remote technical support method according to claim 1, characterized in that, For abnormal terminals, the system filters driving factors based on a strategy generated by weighted fusion of state evolution rate value and link transmission jitter data. It then retrieves several candidate support instructions from the remote support policy library and aggregates them into a candidate instruction set. The candidate support instructions include a set of instruction packets with lengths, and include the following sub-steps: The state evolution rate value of the abnormal terminal is weighted and fused with the jitter amplitude value and jitter frequency value in the link transmission jitter data according to a preset weight to generate a strategy screening driving factor. Based on the strategy selection of driving factors, a strategy matching search is performed in the remote support strategy library. The index range of driving factors corresponding to each historical support strategy in the remote support strategy library is matched with the driving factors selected by the current strategy. Multiple historical support strategies whose index range of driving factors includes the driving factors selected by the current strategy are extracted. The instruction configuration information corresponding to each historical support strategy is analyzed, and candidate support instructions containing the instruction packet length are extracted and compiled into a candidate instruction set.

5. The remote technical support method according to claim 1, characterized in that, Calculate the ratio between the instruction packet length of each candidate supported instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data. Map the instruction completeness value of each candidate supported instruction according to the relative ranking relationship of each ratio. Determine the candidate supported instruction with the largest instruction completeness value as the target supported instruction. This includes the following sub-steps: Obtain the instruction packet length of each candidate supported instruction in the candidate instruction set, and calculate the adaptation ratio between the length of each instruction packet and the jitter amplitude value in the link transmission jitter data to obtain the link adaptation ratio value of each candidate supported instruction. Based on the relative order of the link adaptation ratio values ​​of each candidate supported instruction in the candidate instruction set, and combined with the preset integrity mapping relationship, the instruction integrity value of each candidate supported instruction is determined. The instruction integrity values ​​of each candidate support instruction are sorted in descending order. The candidate support instruction corresponding to the instruction integrity value at the top of the list is determined as the target support instruction, and its instruction packet length and instruction integrity value are recorded.

6. The remote technical support method according to claim 1, characterized in that, Calculate transmission timing constraint parameters based on link transmission jitter data, and send the target support command to the abnormal terminal via the remote communication link according to the transmission timing constraint parameters. Collect the final running status data returned by the abnormal terminal after execution, and record the command integrity value corresponding to the target support command. This includes the following sub-steps: The transmission timing constraint parameters are calculated based on the jitter amplitude and jitter duration in the jitter data of the link transmission. The transmission timing constraint parameters include the minimum transmission interval between adjacent data packets and the retransmission timeout time. The target support instruction is split into multiple data packets according to the minimum transmission interval between adjacent data packets in the transmission timing constraint parameters. The retransmission waiting time of each data packet is set according to the retransmission timeout time in the transmission timing constraint parameters. The data packets are then sent to the abnormal terminal in sequence via the remote communication link. The abnormal terminal receives all data packets, reassembles them, and then executes the target support instruction. Receive the final running status data returned after the abnormal terminal executes, associate the final running status data with the instruction integrity value of the target supported instruction, and store it in the local data pool.

7. The remote technical support method according to claim 1, characterized in that, Calculate the state transition value between the final running state data and the initial running state data. Only if the state transition value falls within the allowable transition range and the instruction integrity value meets the integrity condition threshold, write the final running state data to the local data pool to update the initial support baseline; otherwise, maintain the initial support baseline unchanged. This includes the following sub-steps: Read the multidimensional initial running status data corresponding to the initial support baseline from the local data pool, calculate the absolute value of the difference between the final running status data and the initial running status data in each dimension, and sum them according to the preset dimension weight coefficients to obtain the state transition value. Determine whether the state transition value falls within the allowed transition range, and at the same time determine whether the instruction integrity value meets the integrity condition threshold. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool, and the initial running state data in the initial support baseline is replaced with the final running state data to complete the update of the initial support baseline. Otherwise, maintain the initial support baseline.

8. A remote technical support system, characterized in that, include: Communication and Baseline Construction Module: The system establishes a remote communication link with the target terminal, collects the target terminal's operating status data and link transmission jitter data through this link, stores them in the local data pool according to timestamps, and pre-sets a remote support strategy library, state evolution rate threshold, allowed transition range, complete condition threshold and transmission timing constraints to construct the initial support baseline for remote technical support methods. Anomaly detection module: Based on the state evolution rate threshold in the initial support baseline, the system calculates the state evolution rate value of the running state data of adjacent timestamps. When the value exceeds the threshold, the target terminal is marked as an abnormal terminal. Strategy matching and instruction selection module: For abnormal terminals, the system uses a strategy screening driving factor generated by weighted fusion of state evolution rate value and link transmission jitter data to match and retrieve several candidate support instructions from the remote support strategy library, which are then aggregated into a candidate instruction set. The candidate support instructions include instruction packet length instruction set; the ratio between the instruction packet length of each candidate support instruction in the candidate instruction set and the jitter amplitude value in the link transmission jitter data is calculated; the instruction completeness value of each candidate support instruction is mapped according to the relative ranking relationship of each ratio; and the candidate support instruction with the largest instruction completeness value is determined as the target support instruction. Command issuance and feedback acquisition module: Calculates transmission timing constraint parameters based on link transmission jitter data, issues the target supported command to the abnormal terminal via remote communication link according to the transmission timing constraint parameters, collects the final running status data returned by the abnormal terminal after execution, and records the command integrity value corresponding to the target supported command; Baseline update determination module: Calculates the state transition value between the final running state data and the initial running state data. Only when the state transition value falls within the allowed transition range and the instruction integrity value meets the integrity condition threshold, the final running state data is written to the local data pool to update the initial support baseline; otherwise, the initial support baseline remains unchanged.

Images