Monitoring method and device for equipment production process, storage medium and electronic equipment

By predicting the time interval required for equipment testing, the problem of low monitoring accuracy in equipment production is solved, and the timeliness and efficiency of equipment testing is improved.

CN118938820APending Publication Date: 2024-11-12INSPUR SUZHOU INTELLIGENT TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202410977738.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The monitoring methods of existing equipment production processes have problems with low monitoring accuracy, which leads to failures during equipment testing that cannot be detected in time, inefficient and prone to missed inspections.

Method used

By obtaining the expected test time interval corresponding to the specified test operation of the equipment being tested, the time interval required for the equipment to complete the test operation is predicted based on the previous test time series, and monitoring is carried out within the expected time interval, early warning is issued when it is not completed, and monitoring is improved accuracy.

Benefits of technology

It improves the monitoring accuracy of the equipment production process, ensures timely detection and early warning of the equipment testing process, reduces the cost of fault expansion and repair, and improves production efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938820A_ABST
    Figure CN118938820A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an equipment production process monitoring method and device, a storage medium and electronic equipment, and the method comprises the steps: obtaining an expected test time interval corresponding to a specified test operation of tested equipment, the expected test time interval is a time interval in which the test time required by the tested equipment to complete the specified test operation is predicted based on a historical test time sequence, and the historical test time in the historical test time sequence is the actual test time of the reference equipment with the same type as the tested equipment to complete the specified test operation; on the basis of the expected test time interval, monitoring the test time when the tested equipment executes the specified test operation; and when it is not monitored that the tested device completes the specified test operation within the expected test time interval, performing early warning on the tested device. According to the invention, the problem of low monitoring accuracy of the monitoring method of the equipment production process in the related technology is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of equipment testing technology, and more specifically, to a monitoring method and device for an equipment production process, a storage medium, and an electronic device. Background Art

[0002] The manufacturing process of equipment covers multiple links including design, assembly, diagnosis, testing, quality inspection and delivery. After the equipment is assembled, a series of tests are required to ensure that it meets the quality standards required by the market.

[0003] In the related art, the equipment testing process is often monitored by manual inspection. Manual inspection is usually carried out at fixed time intervals and cannot achieve real-time monitoring, resulting in some faults in the equipment testing process not being discovered in time. In addition, the efficiency of manual inspection is low, and when the inspectors are tired, it is easy to miss the inspection.

[0004] Therefore, the monitoring method of the equipment production process in the related art has the problem of low monitoring accuracy. Summary of the invention

[0005] The embodiments of the present application provide a monitoring method and device for a device production process, a storage medium, and an electronic device, so as to at least solve the problem of low control accuracy in the monitoring method for a device production process in the related art.

[0006] According to one aspect of an embodiment of the present application, a method for monitoring a device production process is provided, comprising: a device testing process applied to a device under test, wherein the device production process of the device under test includes the device testing process; comprising: obtaining an expected test time interval corresponding to a specified test operation of the device under test, wherein the expected test time interval is a time interval in which a test time required for the device under test to complete the specified test operation is predicted based on a historical test time series, and the historical test time in the historical test time series is an actual test time for a reference device of the same type as the device under test to complete the specified test operation; monitoring the test time for the device under test to perform the specified test operation based on the expected test time interval; and issuing an early warning to the device under test if the device under test is not monitored to complete the specified test operation within the expected test time interval.

[0007] According to another aspect of an embodiment of the present application, a monitoring device for a device production process is provided, comprising: a device testing process applied to a device under test, wherein the device production process of the device under test includes the device testing process; comprising: an acquisition unit, used to acquire an expected test time interval corresponding to a specified test operation of the device under test, wherein the expected test time interval is a time interval in which a test time required for the device under test to complete the specified test operation is predicted based on a historical test time series, and the historical test time in the historical test time series is an actual test time for a reference device of the same type as the device under test to complete the specified test operation; a first monitoring unit, used to monitor the test time for the device under test to perform the specified test operation based on the expected test time interval; and an early warning unit, used to issue an early warning to the device under test when the device under test is not monitored to complete the specified test operation within the expected test time interval.

[0008] According to another aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in any of the above method embodiments.

[0009] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when executed.

[0010] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0011] Through the present application, an expected test time interval corresponding to a specified test operation of a device not under test is obtained, wherein the expected test time interval is a time interval in which the test time required for the device under test to complete the specified test operation is predicted based on a historical test time series, and the historical test time in the historical test time series is the actual test time for a reference device of the same type as the device not under test to complete the specified test operation; the test time for the device under test to perform the specified test operation is monitored based on the expected test time interval; if the device under test is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the device under test, because the expected test time interval is a time interval in which the test time required for the device under test to complete the specified test operation is predicted based on the actual test time for the reference device to complete the specified test operation, therefore, the expected test time can more accurately reflect the time required for the device under test to complete the specified test operation, and monitoring based on the expected test time interval can accurately determine the state of the device under test, thereby solving the problem of low monitoring accuracy in the monitoring method of the equipment production process in the related art, and improving the accuracy of the monitoring process of the device under test. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 It is a hardware environment diagram of an optional method for monitoring a device production process according to an embodiment of the present application.

[0013] Figure 2 It is a flow chart of an optional method for monitoring a device production process according to an embodiment of the present application.

[0014] Figure 3 It is a schematic diagram of an optional method for monitoring the equipment production process according to an embodiment of the present application.

[0015] Figure 4 It is a structural block diagram of an optional monitoring device for the equipment production process according to an embodiment of the present application.

[0016] Figure 5 It is a structural block diagram of a computer system of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0017] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0018] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0019] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a server device of a method for monitoring a device production process according to an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 The server device includes a processor 102 (only one is shown in the figure) (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components than shown, or with different Figure 1 Different configurations are shown.

[0020] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the monitoring method of the equipment production process in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory set relative to the processor 102 process, and these process memories can be connected to the server device via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0021] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0022] Optionally, the monitoring method for the equipment production process in this embodiment may be executed by a server, where the server refers to the server as a whole, including relevant components and a processor in the server that need to execute the monitoring method for the equipment production process; the monitoring method for the equipment production process in this embodiment may also be executed by the processor 102. In some examples of this embodiment, the monitoring method for the equipment production process is described by taking execution by a server as an example.

[0023] The monitoring method of the device production process in this embodiment can be applied to the scenario of performing device testing on the device under test during the device production process of the device under test. The device under test in this embodiment can be a server, a switch, a terminal device, or a combination of other devices. In some examples of this embodiment, the device under test is described by taking a server as an example.

[0024] The production and manufacturing process of servers is a complex and highly professional process, covering multiple links such as design, assembly, diagnosis, testing, quality inspection and delivery. Each link requires strict quality control and efficient management to ensure that the final product meets customer needs and quality standards. In the modern production and manufacturing process, the application of automation technology, information management and intelligent systems has greatly improved production efficiency and product quality, and promoted the continuous progress and development of the server manufacturing industry.

[0025] During the server manufacturing process, if the equipment or system is offline, it will cause a series of problems, such as production line interruption, increased downtime, reduced production capacity, idle resources, and even cause the server products to fail to be fully tested or the test results to be inaccurate, increasing the risk of product defects and repair costs, which will affect the production progress and cause the products to be unable to be delivered to customers on time. Frequent quality problems and service failures may cause customers to lose trust in the company's products and services, affecting long-term cooperative relationships.

[0026] In this context, server manufacturing companies often introduce some intelligent systems, establish and implement effective timeout offline warning mechanisms, prevent and reduce the occurrence of equipment and system offline failures through real-time monitoring and timely response, notify relevant personnel and collaborative systems for timely processing, reduce downtime caused by failures, and improve overall production efficiency.

[0027] In the field of server manufacturing, the existing server timeout offline warning mechanism is often completed through regular manual inspections or production management systems. The regular inspection mechanism is an important means to ensure the normal operation of equipment and systems in the server manufacturing process. Through regular inspections, potential problems can be discovered in advance to prevent equipment from being offline due to failures and affecting production progress and product quality. During the inspection, production personnel need to check the connection of power lines, switches and power connectors to ensure normal power supply; check the software operation of the production system and promptly handle abnormal problems that occur during the server production process; check the server status indicator and the working status and readings of various sensors to see if they are normal.

[0028] In addition to manual inspections, production staff can also use MES (manufacturing execution system, a production information management system for the execution layer of the workshop of manufacturing enterprises, whose main functions include manufacturing data management, planning and scheduling management, production scheduling management, inventory management, quality management and other modules) or other monitoring systems to track the progress of each production task in real time, record the running time and running status. The system can set a scheduled completion time for each production task. If it is not completed within the time limit, production staff can intuitively find the abnormality through the system, and the system can also automatically issue an early warning to notify relevant personnel.

[0029] As production scale and complexity increase, the use of manual inspections to provide timeout offline warnings during server production will expose many shortcomings. Manual inspections are usually conducted at fixed time intervals and cannot be monitored in real time, which means that network offline or failures that may occur between two inspections cannot be discovered in time. Response delays may result in missing the best time to handle the problem, further expanding the scope and impact of the failure, and increasing repair costs and time. When the production scale is large, the number of devices and systems that need to be inspected is large, and it is difficult to cover all devices with limited manpower alone, resulting in low inspection efficiency. Manual inspections are also prone to missed inspections, especially when the inspectors are tired, distracted, or unfamiliar with the equipment, which places high demands on manpower.

[0030] Although using a simple monitoring system to prevent timeout offline failures can improve efficiency and accuracy to a certain extent, it also has some obvious disadvantages. The monitoring system is usually unable to automatically handle the faults found, requiring manual intervention, and cannot achieve fully automated operation and maintenance. After detecting the problem, it cannot automatically perform repair operations (such as restarting network services, retesting, etc.). In addition, with the diversity of market demand and server configuration, the monitoring system's estimated test completion time is inaccurate, which will also cause misjudgment of timeout offline situations to a certain extent. In general, a simple monitoring system still belongs to the category of passive detection, and it is difficult to meet the needs of efficient and reliable monitoring in modern complex production and manufacturing environments.

[0031] In order to at least partially solve the above problems, a method for monitoring a device production process is provided in this embodiment. Figure 2 is a flow chart of an optional method for monitoring a device production process according to an embodiment of the present application, such as Figure 2 As shown, the above method includes steps S202 to S206.

[0032] Step S202, obtaining an expected test time interval corresponding to a specified test operation of the device not being tested, wherein the expected test time interval is a time interval of the test time required for the device under test to complete the specified test operation, predicted based on a historical test time series, and the historical test time in the historical test time series is the actual test time for a reference device of the same type as the device not being tested to complete the specified test operation.

[0033] Step S204: monitoring the test time of the device under test for executing the specified test operation based on the expected test time interval.

[0034] Step S206: If the device under test is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the device under test.

[0035] See also Figure 3 , Figure 3 is a schematic diagram of an optional monitoring method for a device production process according to an embodiment of the present application, Figure 3 The UUT (unit under test) in the embodiment refers to the device under test in this embodiment. The device under test can be a server, a switch, a terminal device or a combination of other devices. In this embodiment, the device under test is described as a server. The monitoring method of the device production process in this embodiment can be executed by a server. The server corresponds to Figure 3 The application server and database server in the Figure 3 The application servers and database servers in the application server list are servers that have been tested and meet the qualified standards. Figure 3The main switch and switches shown are used to display the network topology of the equipment production line, that is, the tested equipment passes through Figure 3 The main switch is shown as well as the switch without application server and database server connections.

[0036] The specified test operations may include firmware upgrades, performance tests, and stress tests on the device under test; the expected test time interval is a time interval predicted based on the historical test time series, in which the test time required for the device under test to complete the specified test operations is located; the historical test time in the historical test time series is the actual test time for a reference device of the same type as the device under test to complete the specified test operations.

[0037] The test time of the tested device performing the specified test operation is monitored based on the expected test time interval; if the tested device is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the tested device.

[0038] The situation where the tested device is not monitored to complete the specified test operation within the expected test time interval may include the situation where the time for the tested device to complete the specified test operation exceeds the expected test time interval, the situation where the time for the tested device to complete the specified test operation is ahead of schedule and is not within the expected test time interval, and the situation where the tested device is offline.

[0039] For example, in the above situation, the warnings for the tested equipment may include timeout warnings and offline warnings. Timeout warnings mean that if a task or operation process fails to be completed within the set time range, the system will automatically issue an alarm to notify relevant personnel or systems to take corresponding measures; offline warnings mean that when the system or equipment is not online or connected as scheduled, an alarm is issued, and its purpose is to timely discover the offline status of the equipment, system or network, so as to quickly take measures to restore normal operation and ensure business continuity and data integrity.

[0040] Through the embodiments provided by the present application, an expected test time interval corresponding to a specified test operation of a device not being tested is obtained, wherein the expected test time interval is a time interval in which the test time required for the device under test to complete the specified test operation is predicted based on a historical test time series, and the historical test time in the historical test time series is the actual test time for a reference device of the same type as the device not being tested to complete the specified test operation; based on the expected test time interval, the test time for the device under test to perform the specified test operation is monitored; if the device under test is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the device under test, thereby solving the problem of low monitoring accuracy in the monitoring method of the equipment production process in the related art and improving the accuracy of the monitoring process of the device under test.

[0041] As an optional solution, obtaining an expected test time interval corresponding to a specified test operation of a device not to be tested includes:

[0042] S11, inputting the historical test time series into the time series prediction model to obtain the expected test time interval output by the time series prediction model;

[0043] Among them, the expected test time interval is predicted by the time series prediction model based on at least one of the following: historical test time series, the difference of historical test time series, the correlation between a historical test time in the historical test time series and the predicted difference before a historical test time, and the predicted difference before a historical test time is the difference between the test times predicted by the time series prediction model that do not correspond to the historical test time before a historical test time.

[0044] Optionally, the time series prediction model can be an ARIMA (Autoregressive Integrated Moving Average Model) model. Correspondingly, in this embodiment, the expected test time interval is predicted by the time series prediction model based on at least one of the following: the historical test time series, that is, the AR (autoregressive) part, which uses the past values ​​of the time series itself to predict future values; the difference of the historical test time series, that is, the I (difference) part, which makes the time series stable by calculating the difference; the correlation between the prediction errors between a historical test time and a previous historical test time in the historical test time series, and the prediction error before a historical test time is the difference between the test times predicted by the time series prediction model that does not correspond to the previous historical test time, that is, the MA (moving average) part, which uses the past prediction errors of the time series to predict future values.

[0045] For example, taking the upgrade of BMC (Baseboard Management Controller) firmware as an example, the system collects the upgrade time of the same product when upgrading the same version of BMC firmware as a data set and imports it into the ARIMA model, and then predicts the time to complete the BMC firmware upgrade, and gives an upper limit and a lower limit as dynamic thresholds. The upper limit and lower limit here correspond to the expected test time interval in this embodiment.

[0046] Through the embodiments provided in the present application, the accuracy of the expected test time interval can be improved, thereby improving the accuracy of the monitoring method of the equipment production process.

[0047] As an optional solution, before obtaining the expected test time interval corresponding to the specified test operation of the device not to be tested, the method further includes:

[0048] S21, reading historical test data, wherein the historical test data is used to indicate the actual test time of a reference device of the same type as the device being tested to complete a specified test operation;

[0049] S22, performing a data cleaning operation on the historical test data to obtain an initial test time sequence, wherein the data cleaning operation is used to remove test data with missing values ​​in the historical test data, and the initial test time sequence is obtained by sorting the test times indicated by the cleaned historical test data in chronological order;

[0050] S23, using the specified sliding window to perform a data smoothing operation on the initial test time series to obtain a historical test time series, wherein the data smoothing operation is an operation of averaging the test time within the specified sliding window.

[0051] In order to improve the accuracy of the acquired historical test time series, in this embodiment, a data cleaning operation is performed on the read historical test data to remove data with missing values ​​in the historical test data to obtain an initial test time series, and a data smoothing operation is performed on the initial test time series using a specified sliding window to obtain a historical test time series.

[0052] Optionally, the following code can be used to implement the process from data cleaning to model prediction and adaptive adjustment.

[0053]

[0054]

[0055] In the above code, data smoothing adopts a sliding average strategy. For the read sequence, a fixed window size K (5 in this embodiment) is set, and the average values ​​of continuous subsequences from the 1st to the Kth item, the 2nd to the K+1th item, the 3rd to the K+2th item, etc. in the sequence are calculated to obtain a smoothed sequence reflecting the data trend.

[0056] Through the embodiments provided in this application, by cleaning, denoising and smoothing the collected historical test data, the data quality can be ensured and the accuracy of the monitoring method of the equipment production process can be effectively improved.

[0057] As an optional solution, the device testing process is performed after the device under test is added to the network topology of the device production line;

[0058] After the device under test is added to the network topology of the device production line, the method further includes:

[0059] S31, when determining that the tested device is added to the network topology of the device production line, monitor the device status of the tested device based on the heartbeat signal of the tested device, wherein the heartbeat signal is periodically sent by the tested device according to a specified sending period;

[0060] S32: When it is monitored that the tested device is in an offline state, an early warning is issued for the offline state of the tested device.

[0061] See also Figure 3 The network topology of the equipment production line in this embodiment is a structure that combines a star structure and a bus structure. After the tested equipment is assembled, it is placed in the work rack, powered on, and automatically added to the network topology through the deployment of the DHCP (Dynamic Host Configuration Protocol) service. The monitoring system is deployed to the application server and the database server, and the monitoring system uses the heartbeat mechanism to perform timeout offline warning, which corresponds to steps S31 to S32 in this embodiment.

[0062] After determining the network topology of the device under test added to the device production line, the device status of the device under test is monitored based on the heartbeat signal of the device under test, wherein the heartbeat signal is periodically sent by the device under test according to the specified sending cycle, and the heartbeat signal is used to indicate that the device is in normal operation. This signal usually contains the basic information and operating status of the device, which can help the monitoring system to detect device failures or abnormalities in time; when monitoring that the device under test is in an offline state, an early warning of the offline state of the device under test is issued.

[0063] Optionally, the heartbeat signal may include a device ID (Identity document, identity identification) of the device under test, a timestamp, and device status information.

[0064] Through the embodiments provided in the present application, the device status of the device under test is monitored by monitoring the heartbeat signal of the device under test, which can improve the reliability and stability of the device testing process and ensure that the device can continue to operate normally.

[0065] As an optional solution, when the network topology of the device under test is determined to be added to the device production line, the device status of the device under test is monitored based on the heartbeat signal of the device under test, including:

[0066] S41, in the case of determining that the tested device is added to the network topology of the device production line, monitoring the duration of not receiving the heartbeat signal;

[0067] S42: When the duration of not receiving the heartbeat signal is greater than or equal to a specified multiple of the specified sending period, determine that the tested device is in an offline state, where the specified multiple is a positive integer greater than or equal to 1.

[0068] Exemplarily, the sending cycle is specified to be 5 minutes, the specified multiple is 3 times, and when it is determined that the device under test is added to the network topology of the device production line, the duration of not receiving the heartbeat signal is monitored. When the duration of not receiving the heartbeat signal is greater than or equal to 3 times the specified sending cycle (i.e., greater than or equal to 15 minutes), it is determined that the device under test is in an offline state.

[0069] Through the embodiments provided in the present application, an implementation method for monitoring whether the tested device is in an offline state is provided, thereby improving the reliability of the monitoring method of the device production process.

[0070] As an optional solution, after the device under test is added to the network topology of the device production line, the method further includes:

[0071] S51, periodically sending heartbeat signals to the monitoring server according to the specified sending period, and waiting to receive confirmation signals returned by the monitoring server that do not correspond to each heartbeat signal;

[0072] S52, when the number of heartbeat signals for which corresponding confirmation signals have not been received is greater than or equal to a specified number threshold, detecting the device status of the device under test;

[0073] S53, when it is detected that the tested device is in a fault state, automatically repair the tested device according to a preset set of self-repair operations, wherein the set of self-repair operations includes at least one of the following: reconnection, configuration recovery, and automatic restart.

[0074] For example, the sending cycle is specified as 5 minutes, and the quantity threshold is specified as 3; the monitoring server is used to receive the heartbeat signal, record the received signal, and perform status determination. The monitoring server corresponds to Figure 3 The application server shown; the tested device sends a heartbeat signal to the monitoring server every 5 minutes. If the tested device is in normal status, the monitoring server will send a confirmation signal to the sending end (tested device). When the number of heartbeat signals without receiving the corresponding confirmation signal is greater than or equal to 3 times, the device status of the tested device is detected; when it is detected that the tested device is in a fault state, the early warning mechanism is triggered, and the tested device is automatically repaired according to a preset set of self-repair operations, wherein the set of self-repair operations includes at least one of the following: reconnection, configuration recovery, and automatic restart.

[0075] The following code simply simulates the situation where the monitoring server fails to receive the heartbeat signal of the tested device and triggers an early warning.

[0076]

[0077] Optionally, when it is detected that the tested device has timed out and has not responded, the monitoring system notifies the operation and maintenance personnel through SMS, email, and pop-up windows on the interface to promptly check the status of the tested device and handle the fault. If the tested device times out and goes offline, it may be that the tested device has crashed. This kind of fault requires the operation and maintenance personnel to check the running status of the tested device, analyze the problem based on the retained logs, and handle the fault; it is more likely to be a network connection failure, which can be solved by the tested device restarting the network service, or the operation and maintenance personnel replacing the network port.

[0078] Through the embodiments provided in this application, the production efficiency and product quality of the equipment production process can be effectively improved through real-time monitoring, timely warning, rapid response and automatic repair.

[0079] As an optional solution, when the device under test is detected to be in a fault state, the device under test is automatically repaired according to a preset set of self-repair operations, including:

[0080] S61, when it is detected that the tested device is in a fault state, restart the network service to try to rejoin the network topology of the device production line, and after the network service restart is completed, resend the heartbeat signal to the monitoring server;

[0081] S62, after the heartbeat signal is resent to the monitoring server, if the number of heartbeat signals for which the corresponding confirmation signal is not received is greater than or equal to the specified number threshold, use the latest configuration file or the specified configuration file in the regularly backed-up configuration files to perform configuration recovery on the tested device to try to restore the running state of the tested device;

[0082] S63, after the network service is restarted and the configuration of the tested device is restored, if the tested device is still in a fault state, start a health check;

[0083] S64, when the health check is completed and the tested device does not have a specified fault that causes production interruption, automatically restart the tested device to try to restore the operating state of the tested device;

[0084] The health check includes at least one of the following:

[0085] Read the sensor information of the device under test, and check whether the device parameters of the hardware device of the device under test are abnormal according to the read sensor information;

[0086] Export the system event log of the device under test and check whether there are any abnormal warnings;

[0087] Check whether the link status of the hardware device of the device under test is abnormal.

[0088] It should be noted that the device parameters of the hardware device of the tested device in this embodiment may include at least part of temperature, voltage, and rotation speed (for fans); the system event log refers to the SEL (System Event Log, system time recorder) and IDL (Interface Definition Language) log of the BMC.

[0089] When it is detected that the tested device is in a faulty state, the network service is restarted to try to rejoin the network topology of the device production line, and after the network service is restarted, the heartbeat signal is resent to the monitoring server; specifically, after the tested device detects that it is offline, it attempts to restart the network service to restore network communication, and after the restart is complete, it sends a heartbeat signal to the server again. If the network returns to normal, production diagnosis continues.

[0090] After the heartbeat signal is resent to the monitoring server, if the number of heartbeat signals for which the corresponding confirmation signal is not received is greater than or equal to the specified number threshold, the latest configuration file or the specified configuration file in the regularly backed-up configuration files is used to perform configuration recovery on the tested device to try to restore the operating status of the tested device. Specifically, the tested device regularly backs up the configuration file during the production process, and performs version management on the configuration file, recording the historical versions and production nodes of each configuration change. When a fault occurs, the latest or pre-specified version is selected for recovery to try to restore the status of the tested device, quickly solve the problem, and restore the normal operation of the tested device.

[0091] After restarting the network service and restoring the configuration of the tested device, if the tested device is still in a faulty state, start a health check; after the health check is completed and the tested device does not have a specified fault that causes production interruption, automatically restart the tested device to try to restore the operating status of the tested device; specifically, if restarting the network service or restoring the configuration cannot solve the fault, the tested device starts a health check, reads sensor information, and checks whether the temperature, voltage, fan speed, etc. of each hardware are abnormal; exports the system log, BMC's SEL and IDL logs, and checks whether there are abnormal alarms; checks whether the link status of each hardware device is abnormal. After the above checks are completed, if the tested device itself does not have a major fault that causes production interruption, the current production diagnosis link is recorded, and then automatically restarted to try to restore the operating status.

[0092] Optionally, after performing the automatic repair operation, continue to monitor the device status to verify the repair effect. If the repair fails, try again or upgrade to manual processing.

[0093] Optionally, after the tested device is powered on, it automatically joins the network topology of the production line. When it is detected that the tested device is in an offline state or a faulty state, an early warning of the offline state of the tested device can be issued, and the tested device can be automatically repaired. At the same time, early warning information can also be sent to other tested devices that are not connected to the tested device.

[0094] Here, the connection between the device under test and other devices under test can be through a switch, for example, see Figure 3 , corresponding to Figure 3 The connection mode between the three tested devices connected to a switch in the example can be that the tested devices under one switch can exchange information with each other through the switch, or can exchange information based on the main switch, that is, the tested devices under the same main switch can exchange information with each other through the main switch; the connection mode between the tested device and other tested devices can also be that the tested device sends warning information to the monitoring server (when the tested device is not in an offline state), and the monitoring server sends the warning information to other tested devices that are not connected to the monitoring server, for example, see Figure 3 , corresponding to Figure 3 In the connection mode between the tested device and the application server and the database server, the tested device can send warning information to other tested devices that are not connected to the application server and the database server through the application server and the database server.

[0095] It can be understood that by designing a coordinated response mechanism between multiple tested devices, it can be ensured that when a tested device fails, other devices of the same type can adjust their operating status, intervene in repairs in advance, and maintain overall production stability.

[0096] Through the embodiments provided in the present application, when it is detected that the tested device is in a fault state, the tested device can perform automatic repair operations in a timely manner, thereby improving the reliability and stability of the equipment production process.

[0097] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0098] In this embodiment, a monitoring device for a production process of an equipment is also provided, and the device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made are not repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0099] Figure 4 is a structural block diagram of an optional monitoring device for a device production process according to an embodiment of the present application, such as Figure 4 As shown, the device is applied to the equipment testing process of the tested equipment. The equipment production process of the tested equipment includes the equipment testing process. The device includes an acquisition unit 402, a first monitoring unit 404 and an early warning unit 406.

[0100] An acquisition unit 402 is used to acquire an expected test time interval corresponding to a specified test operation of the device not under test, wherein the expected test time interval is a time interval of the test time required for the device under test to complete the specified test operation, which is predicted based on a historical test time series, and the historical test time in the historical test time series is an actual test time for a reference device of the same type as the device not under test to complete the specified test operation;

[0101] A first monitoring unit 404 monitors the test time of the device under test performing a specified test operation based on the expected test time interval;

[0102] The early warning unit 406 is used to issue an early warning to the device under test when the device under test fails to complete the specified test operation within the expected test time interval.

[0103] It should be noted that the acquisition unit 402 in this embodiment can be used to execute the above step S202, the first monitoring unit 404 in this embodiment can be used to execute the above step S204, and the early warning unit 406 in this embodiment can be used to execute the above step S206.

[0104] Through the embodiments provided by the present application, an expected test time interval corresponding to a specified test operation of a device not being tested is obtained, wherein the expected test time interval is a time interval in which the test time required for the device under test to complete the specified test operation is predicted based on a historical test time series, and the historical test time in the historical test time series is the actual test time for a reference device of the same type as the device not being tested to complete the specified test operation; based on the expected test time interval, the test time for the device under test to perform the specified test operation is monitored; if the device under test is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the device under test, thereby solving the problem of low monitoring accuracy in the monitoring method of the equipment production process in the related art and improving the accuracy of the monitoring process of the device under test.

[0105] Optionally, the acquisition unit includes:

[0106] An input module is used to input the historical test time series into the time series prediction model to obtain the expected test time interval output by the time series prediction model;

[0107] Among them, the expected test time interval is predicted by the time series prediction model based on at least one of the following: historical test time series, the difference of historical test time series, the correlation between a historical test time in the historical test time series and the predicted difference before a historical test time, and the predicted difference before a historical test time is the difference between the test times predicted by the time series prediction model that do not correspond to the historical test time before a historical test time.

[0108] Optionally, the device further comprises:

[0109] A reading unit, used for reading historical test data before obtaining an expected test time interval corresponding to a specified test operation of the device not under test, wherein the historical test data is used to indicate an actual test time for a reference device of the same type as the device not under test to complete the specified test operation;

[0110] A cleaning unit, used to perform a data cleaning operation on the historical test data to obtain an initial test time sequence, wherein the data cleaning operation is used to remove test data with missing values ​​in the historical test data, and the initial test time sequence is obtained by sorting the test times indicated by the cleaned historical test data in chronological order;

[0111] The smoothing unit is used to perform a data smoothing operation on the initial test time series using a specified sliding window to obtain a historical test time series, wherein the data smoothing operation is an operation of taking the average value of the test time within the specified sliding window.

[0112] Optionally, the device testing process is performed after the device under test is added to the network topology of the device production line;

[0113] The device also includes:

[0114] a second monitoring unit, configured to monitor the device state of the device under test based on a heartbeat signal of the device under test after the device under test is added to the network topology of the device production line and when it is determined that the device under test is added to the network topology of the device production line, wherein the heartbeat signal is periodically sent by the device under test according to a specified sending period;

[0115] The early warning unit is used to warn the offline state of the tested device when monitoring that the tested device is in an offline state.

[0116] Optionally, the second monitoring unit includes:

[0117] A monitoring module, used to monitor the duration of not receiving the heartbeat signal when determining the network topology of the device under test added to the device production line;

[0118] The determination module is used to determine that the tested device is in an offline state when the duration of not receiving the heartbeat signal is greater than or equal to a specified multiple of the specified sending period, wherein the specified multiple is a positive integer greater than or equal to 1.

[0119] Optionally, the device further comprises:

[0120] The execution unit is used to periodically send heartbeat signals to the monitoring server according to a specified sending period after the tested device is added to the network topology of the device production line, and wait to receive a confirmation signal corresponding to each heartbeat signal returned by the monitoring server;

[0121] A detection unit, configured to detect the device status of the device under test when the number of heartbeat signals for which the corresponding confirmation signals are not received is greater than or equal to a specified number threshold;

[0122] The repair unit is used to automatically repair the tested device according to a preset set of self-repair operations when detecting that the tested device is in a fault state, wherein the set of self-repair operations includes at least one of the following: reconnection, configuration recovery, and automatic restart.

[0123] Optionally, the repair unit includes:

[0124] An execution module, used to restart the network service when detecting that the tested device is in a fault state, so as to try to rejoin the network topology of the device production line, and resend a heartbeat signal to the monitoring server after the network service restart is completed;

[0125] A recovery module, configured to, when the number of heartbeat signals for which corresponding confirmation signals have not been received after the heartbeat signals are resent to the monitoring server is greater than or equal to a specified number threshold, use the latest configuration file or a specified configuration file in the regularly backed-up configuration files to perform configuration recovery on the tested device, so as to try to restore the running state of the tested device;

[0126] A check module is used to start a health check if the device under test is still in a faulty state after restarting the network service and restoring the configuration of the device under test;

[0127] The restart module is used to automatically restart the device under test after the health check is completed and there is no specified fault that causes production interruption in the device under test, in order to try to restore the operating status of the device under test;

[0128] The health check includes at least one of the following:

[0129] Read the sensor information of the device under test, and check whether the device parameters of the hardware device of the device under test are abnormal according to the read sensor information;

[0130] Export the system event log of the device under test and check whether there are any abnormal warnings;

[0131] Check whether the link status of the hardware device of the device under test is abnormal.

[0132] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules are located in different processors in any combination.

[0133] According to another aspect of the present application, a computer program product is also provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the above method. Figure 5 The computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processor 501, various functions provided by the embodiments of the present application are executed. The serial numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0134] refer to Figure 5 , Figure 5 It is a structural block diagram of a computer system of an optional electronic device according to an embodiment of the present application.

[0135] Figure 5The computer system structure block diagram of the electronic device used to implement the embodiment of the present application is schematically shown. Figure 5 As shown, the computer system 500 includes a central processing unit 501 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 502 (ROM) or the program loaded from the storage part 508 to the random access memory 503 (RAM). Various programs and data required for system operation are also stored in the random access memory 503. The central processing unit 501, the read-only memory 502 and the random access memory 503 are connected to each other through a bus 504. The input / output interface 505 (Input / Output interface, i.e., I / O interface) is also connected to the bus 504.

[0136] The following components are connected to the input / output interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the input / output interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

[0137] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processor 501, various functions defined in the system of the present application are executed.

[0138] It should be noted that Figure 5 The computer system 500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0139] According to another aspect of the present application, a computer-readable storage medium is provided. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above method.

[0140] Optionally, in the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0141] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, which may include: a flash drive, a ROM (Read-Only Memory), a RAM (Random Access Memory), a disk or an optical disk, etc.

[0142] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which can be personal computers, servers or network devices, etc.) to perform all or part of the steps of the methods of various embodiments of the present application.

[0143] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0144] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical functional division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0145] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0146] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0147] The above are only preferred implementations of the present application. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be considered within the scope of protection of the present application.

Claims

1. A method for monitoring a production process of an equipment, characterized in that: The device testing process applied to the device under test, wherein the device production process of the device under test includes the device testing process; comprising: Obtaining an expected test time interval corresponding to a specified test operation of the device under test, wherein the expected test time interval is a time interval of a test time required for the device under test to complete the specified test operation, predicted based on a historical test time series, and the historical test time in the historical test time series is an actual test time for a reference device of the same type as the device under test to complete the specified test operation; Monitoring the test time of the device under test performing the specified test operation based on the expected test time interval; When the device under test is not monitored to complete the specified test operation within the expected test time interval, an early warning is issued to the device under test.

2. The method according to claim 1, characterized in that The obtaining of the expected test time interval corresponding to the specified test operation of the device under test includes: Inputting the historical test time series into a time series prediction model to obtain the expected test time interval output by the time series prediction model; Among them, the expected test time interval is predicted by the time series prediction model based on at least one of the following: the historical test time series, the difference of the historical test time series, the correlation between a historical test time in the historical test time series and the prediction error before the historical test time, the prediction error before the historical test time is the difference between the historical test time before the historical test time and the corresponding test time predicted by the time series prediction model.

3. The method according to claim 2, characterized in that Before acquiring the expected test time interval corresponding to the specified test operation of the device under test, the method further includes: Reading historical test data, wherein the historical test data is used to indicate an actual test time when a reference device of the same type as the device under test completes the specified test operation; Performing a data cleaning operation on the historical test data to obtain an initial test time sequence, wherein the data cleaning operation is used to remove test data with missing values ​​in the historical test data, and the initial test time sequence is obtained by sorting the test times indicated by the cleaned historical test data in chronological order; A data smoothing operation is performed on the initial test time series using a specified sliding window to obtain the historical test time series, wherein the data smoothing operation is an operation of averaging the test times within the specified sliding window.

4. The method according to any one of claims 1 to 3, characterized in that The device testing process is performed after the tested device is added to the network topology of the device production line; After the tested device is added to the network topology of the device production line, the method further includes: In the case of determining that the tested device is added to the network topology of the device production line, monitoring the device status of the tested device based on the heartbeat signal of the tested device, wherein the heartbeat signal is periodically sent by the tested device according to a specified sending period; When it is monitored that the tested device is in an offline state, an early warning is issued for the offline state of the tested device.

5. The method according to claim 4, characterized in that The step of monitoring the device status of the device under test based on the heartbeat signal of the device under test when determining that the device under test is added to the network topology of the device production line includes: In the case of determining that the tested device is added to the network topology of the device production line, monitoring the duration of not receiving the heartbeat signal; When a duration of not receiving the heartbeat signal is greater than or equal to a specified multiple of the specified sending period, it is determined that the tested device is in an offline state, wherein the specified multiple is a positive integer greater than or equal to 1.

6. The method according to claim 4, characterized in that After the tested device is added to the network topology of the device production line, the method further includes: According to the specified sending period, periodically sending the heartbeat signal to the monitoring server, and waiting to receive a confirmation signal returned by the monitoring server corresponding to each of the heartbeat signals; When the number of the heartbeat signals for which the corresponding confirmation signals are not received is greater than or equal to a specified number threshold, detecting the device status of the device under test; When it is detected that the tested device is in a fault state, the tested device is automatically repaired according to a preset set of self-repair operations, wherein the set of self-repair operations includes at least one of the following: reconnection, configuration recovery, and automatic restart.

7. The method according to claim 6, characterized in that When the device under test is detected to be in a fault state, automatically repairing the device under test according to a preset set of self-repair operations includes: When it is detected that the tested device is in a faulty state, restart the network service to try to rejoin the network topology of the device production line, and after the network service restart is completed, resend the heartbeat signal to the monitoring server; After the heartbeat signal is resent to the monitoring server, if the number of the heartbeat signals for which the corresponding confirmation signal is not received is greater than or equal to the specified number threshold, use the latest configuration file or the specified configuration file in the regularly backed-up configuration files to perform configuration recovery on the tested device to try to restore the operating state of the tested device; After restarting the network service and restoring the configuration of the tested device, if the tested device is still in a faulty state, starting a health check; When the health check is completed and the device under test does not have a specified fault that causes production interruption, automatically restart the device under test to try to restore the operating state of the device under test; The health check includes at least one of the following: Reading sensor information of the device under test, and checking whether device parameters of the hardware device of the device under test are abnormal according to the read sensor information; Export the system event log of the tested device and check whether there is any abnormal warning; Check whether the link status of the hardware device of the tested device is abnormal.

8. A monitoring device for a production process of an equipment, characterized in that: The device testing process applied to the device under test, wherein the device production process of the device under test includes the device testing process; comprising: an acquisition unit, configured to acquire an expected test time interval corresponding to a specified test operation of the device under test, wherein the expected test time interval is a time interval of a test time required for the device under test to complete the specified test operation, predicted based on a historical test time series, and the historical test time in the historical test time series is an actual test time for a reference device of the same type as the device under test to complete the specified test operation; A first monitoring unit, configured to monitor a test time for the device under test to perform the specified test operation based on the expected test time interval; The early warning unit is used to warn the device under test if the device under test is not monitored to complete the specified test operation within the expected test time interval.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer-readable storage medium includes a stored program, wherein the program executes the steps of the method according to any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Server customized configuration information automatic recovery method based on self-developed MES

    CN121092365A

  • Server customization configuration information automatic recovery method based on self-developed MES

    CN121092365B