OLT equipment batch maintenance method, system, equipment and storage medium

Abstract

The invention relates to the technical field of software maintenance, in particular to an OLT (Optical Line Terminal) equipment batch maintenance method, system and equipment and a storage medium. The method aims at solving the problems that in the prior art, exception and interrupt processing is lacked, the function is single, and complex actual online scenes cannot be competent; and the misjudgment rate and the misoperation rate are high. Comprising the steps of obtaining a maintenance task customized and created by a user; obtaining a plurality of network elements corresponding to the maintenance task and single-disk version information of the network elements; according to the maintenance task, constructing a maintenance thread of each network element by utilizing single-disk version information, and configuring the maximum number of parallel network elements; after the maintenance task is started, the task is executed according to the maintenance thread, the maintenance progress and the abnormal information are recorded, and recorded data of the maintenance task are obtained; according to the recorded data of the maintenance task, performing weighted calculation on the maintenance task according to a preset scoring rule to obtain a maintenance score; and packaging the maintenance score and the category of the maintenance task to obtain a maintenance result.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of software maintenance, and particularly relates to an OLT device batch maintenance method, system, device and storage medium. BACKGROUND

[0002] At present, optical line terminals (OLT) of communication network access layer in passive optical network (PON) are applied more and more widely, and the number of corresponding devices and the maintenance workload (mainly including device inspection and software upgrade) also increase day by day. How to improve the maintenance efficiency and reduce the maintenance cost on the basis of ensuring the safety of data service has become a common concern of operators and device manufacturers.

[0003] In the prior art, the OLT device maintenance mode depends on manual operation. A complete manual inspection / upgrade process includes the following steps: 1. logging in the OLT device through a terminal on a communicable device; 2. querying the network element and single-disk basic information; 3. entering the corresponding query / modification / upload / decompression command in the target directory of each single-disk in a command line input mode; 4. resetting and restarting the device (if necessary); 5. completing the query and exiting the terminal; and 6. filling in a report.

[0004] The prior art has the following technical problems: 1. In the query link, a corresponding command script can be written at present to realize the query type configuration inspection of a part of fixed processes, thereby reducing a small amount of workload and the misoperation rate. However, due to the lack of exception and interruption processing and the single function, the prior art cannot cope with complex actual online scenes.

[0005] 2. The OLT device maintenance service is usually accompanied by simultaneous operation of a large number of devices in the same region. The number of terminals that can be operated by the same worker at the same time is limited, and it is necessary to log in and operate different devices one by one. In addition, the device state, version number and other information involved in the inspection or upgrade process need to be compared or judged by the naked eye of the worker, and the misjudgment and misoperation rate is high. SUMMARY

[0006] The application provides an OLT device batch maintenance method, system, device and storage medium, and aims to solve the technical problems in the prior art, such as the lack of exception and interruption processing, the single function, the inability to cope with complex actual online scenes, and the high misjudgment and misoperation rate.

[0007] The technical solution for solving the above technical problems is as follows: an OLT device batch maintenance method, comprising: obtaining a maintenance task created by a user in a self-defined manner; acquire a plurality of network elements corresponding to the maintenance task and single-disk version information of the network elements; construct a maintenance thread of each network element by using the single-disk version information according to the maintenance task, and configure a maximum number of parallel network elements; start the maintenance task, execute the task according to the maintenance thread, record maintenance progress and abnormal information, and obtain record data of the maintenance task; perform weighted calculation on the maintenance task according to a preset scoring rule based on the record data of the maintenance task, and obtain a maintenance score; encapsulate the maintenance score and the category of the maintenance task, and obtain a maintenance result.

[0008] Further, when the maintenance task is an inspection task, the user-defined inspection task is specifically obtained as follows: create an initial inspection template, which is used to support user-defined selection of one or more inspection items, set alarm conditions of each inspection item, and set a number of maximum parallel inspection threads, to obtain a content inspection template; process the content inspection template to obtain an inspection task.

[0009] Further, when the maintenance task is an upgrade task, the user-defined upgrade task is specifically obtained as follows: receive input target upgrade information; select a corresponding target upgrade package from an FTP resource server according to the target upgrade information, and obtain the upgrade task based on the target upgrade package, wherein the target upgrade package is used to upgrade a current software version to a target version; wherein the FTP resource server is pre-configured and used to manage software upgrade packages.

[0010] Further, the method further includes: match and detect the target upgrade package and single-disk version information of the network element to be upgraded; wherein the matching and detection content includes version number, compilation time and single-disk type; perform software upgrade on the single disk that passes the matching and detection.

[0011] Further, the method further includes: after the upgrade task is completed, determine whether a network element-level reset is needed according to the target upgrade package; if not, perform calculation of the maintenance score after all upgrade tasks are completed; if so, query and store basic information of all single disks in the network element based on the combination of the upgrade task id, the network element id and the single disk id as a key, to obtain first basic information; After resetting, re-query and store the basic information of all single disks in the network element, obtain second basic information, and determine whether the software version is upgraded to the target version based on the second basic information; If not upgraded to the target version, it is determined that the upgrade fails; If upgraded to the target version, compare the first basic information with the second basic information, and obtain a comparison result of whether the upgrade is successful based on a preset comparison threshold.

[0012] Further, after starting the maintenance task, the task is executed according to the maintenance thread, and the maintenance progress and abnormal information are recorded to obtain record data of the maintenance task, which specifically includes: A globally unique task identifier taskId is generated for the maintenance task, and the total number of all maintenance task items in the maintenance task is calculated; The number of completed maintenance items and the number of abnormal maintenance items are initialized to 0, and the abnormal information string errorInfo is initialized to empty; The maintenance task is grouped according to the network element to execute the maintenance task, and it is determined whether each maintenance task item is completed: If the maintenance task item is completed, the number of completed maintenance items is incremented by one; If the maintenance task item is abnormal, the number of abnormal maintenance items is incremented by one, and the abnormal information generated according to the exception is stored in the abnormal information string errorInfo; Based on the number of completed maintenance items, the number of abnormal maintenance items and the total number, the current maintenance progress is periodically calculated by a progress calculation method, and the formula of the progress calculation method is: (C+F) / N; Wherein, C represents the number of completed maintenance items, F represents the number of abnormal maintenance items, and N represents the total number.

[0013] Further, the scoring rules of the above-mentioned patrol task include: weight configuration rules, abnormal item score configuration rules and negative threshold configuration rules; The weight configuration rule is used to configure the weight of the patrol special item, and the overall quality evaluation score of the patrol task is calculated according to the weight; The abnormal item score configuration rule is used to set the deduction value for the abnormal situation in the execution of the patrol task, and the abnormal situation includes patrol error result, no valid value obtained and unsuccessful login; The negative threshold configuration rule is used to determine whether the proportion of the number of abnormal units to the total number of all units corresponding to the patrol task exceeds the preset negative threshold, if it exceeds, the patrol task score is zero; Wherein, the unit is a network element or a single disk.

[0014] In a second aspect, the present application also provides an OLT device batch maintenance system, which comprises: The task creation module is used to retrieve maintenance tasks created by the user. The network element information acquisition module is used to acquire multiple network elements corresponding to the maintenance task, as well as the single-disk version information of the network element; The task generation module is used to construct a maintenance thread for each network element based on the maintenance task and the single-disk version information, and to configure the maximum number of parallel network elements. The task recording module is used to execute the task according to the maintenance thread after the maintenance task is started, and to record the maintenance progress and exception information to obtain the record data of the maintenance task. The task score calculation module is used to calculate the maintenance score by weighting the maintenance tasks according to the recorded data of the maintenance tasks and the preset scoring rules. The result output module is used to encapsulate the maintenance score and the category of the maintenance task to obtain the maintenance result.

[0015] Thirdly, in order to solve the above-mentioned technical problems, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the OLT device batch maintenance method of the present application.

[0016] Fourthly, in order to solve the above-mentioned technical problems, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the OLT device batch maintenance method of the present application.

[0017] Compared with the prior art, the present invention has the following advantages: 1. The inspection tasks of this invention can be set through a graphical interface, making the operation more intuitive and convenient. Maintenance personnel can select specific inspection items, set inspection cycles, and adjust inspection parameters as needed. It also supports batch selection of network elements and individual boards, and allows flexible adjustment of inspection strategies for different equipment types, ensuring the comprehensiveness and relevance of the inspection work.

[0018] 2. The automated maintenance process of this invention reduces the need for manual intervention, lowers the possibility of human error, and significantly improves maintenance efficiency. For maintenance results, the system can automatically generate detailed reports (Excel, PDF, and Word formats) for easy subsequent analysis and archiving, further reducing the workload of maintenance personnel.

[0019] 3. This invention uses a timed polling method to obtain maintenance progress, ensuring users can monitor the maintenance status in real time. For any anomalies, the system records detailed anomaly information to help quickly pinpoint the cause of the problem. Furthermore, during upgrade tasks, the system accurately determines whether the upgrade was successful by comparing the device's status information before and after a reboot, increasing system reliability.

[0020] 4. The scoring rules of this invention are loaded in the form of a configuration file, which supports the customization of scoring standards according to different inspection needs.

[0021] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0022] 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 some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 A flowchart illustrating a batch maintenance method for OLT equipment according to an embodiment of the present invention is shown; Figure 2 A flowchart illustrating an inspection task according to an embodiment of the present invention is shown; Figure 3 A flowchart illustrating an upgrade task according to an embodiment of the present invention is shown; Figure 4 A schematic diagram of the structure of a batch maintenance system for OLT equipment according to an embodiment of the present invention is shown; Figure 5 A schematic diagram of an electronic device structure according to an embodiment of the present invention is shown. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, 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 embodiments of the present invention, not all embodiments. 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.

[0025] Figure 1A flowchart illustrating a batch maintenance method for OLT equipment according to an embodiment of the present invention is shown, as follows: Figure 1 As shown, an embodiment of the present invention provides a method for batch maintenance of OLT equipment, comprising: This embodiment presents a batch maintenance method for OLT devices, used in a software system comprised of multiple microservices. The software system includes: an inspection service, an upgrade service, a user and communication service, and a device information service, along with a graphical user interface. Each service is deployed independently, and some microservices can be downgraded or disabled for different usage scenarios (e.g., devices in a given area are only subject to inspection).

[0026] First, configure the inspection item information, FTP resource server, and OLT device information. Specifically, configuring the inspection item information includes: During the initial deployment of this embodiment, the following steps are performed to distribute the initial inspection item information, operation command set, and scoring rules, and to trigger the establishment of the inspection item table: Initial inspection item information, operation command set, and scoring rules can be configured via XML resource files or Excel format files. These files will be used to trigger the creation of the inspection item table, ensuring that the system can identify and process all inspection tasks and their related parameters.

[0027] In this embodiment, the inspection item information includes the inspection item type, result expression, inspection item label, and alarm conditions; The inspection items are divided into two levels. The first level includes network elements, single boards, and ports; the second level includes equipment information, environmental status, configuration status, operating status, performance status, and resource quantity. When generating inspection results, the data will be assigned to different tables / sheets based on the first level, while the second level is available for users to filter inspection items in the system's graphical interface. The inspection result expression type includes numeric, string, and boolean values. When defining inspection item information, the corresponding result type must be specified. For example, temperature and quantity related items are specified as numeric values, while enabled and disabled items are specified as boolean values. The default value is a character type. The inspection item labels are divided into main control, uplink, and line card. One inspection item can be assigned to multiple labels, and a certain inspection task involves multiple different login methods and operation command sets. Alarm conditions include judgments based on the result expression type. For numeric inspection results (including dates converted to numbers), they provide conditional formats of greater than, less than, equal to, and combinations thereof. For Boolean inspection results, they provide conditional formats of true / false results. Users define these combinations themselves when starting an inspection task in the graphical interface. Alarm conditions also include alarm status keywords, which are specially marked in the inspection results based on the status value after an alarm is triggered. Alarm statuses include: Normal, Abnormal, Not Acquired, Undefined, and Default.

[0028] In this embodiment, the operation commands are divided into basic operations and inspection operations, and the entire execution process includes multiple steps such as environment verification and command validity verification. The following is a detailed description of the process and mechanism: Basic operations include basic functions such as login, logout, reset, software and hardware information query, and fixed directory.

[0029] Inspection operations: include independent, non-reusable query / modify commands, specifically for equipment status checks.

[0030] The execution process of a single inspection command is as follows: 1. Environment verification: Ensure the execution environment meets the requirements. 2. Command validity verification: Verify whether the command is legal and valid. 3. Single command execution and return of terminal results: Execute the command on the device and obtain the results. 4. Return value parsing: Parse the data returned by the command and extract useful information. 5. Exception handling (if any): Handle any exceptions that occur during execution. 6. Return to main path: After completing the above steps, return to the main process to continue executing subsequent commands or end the current task.

[0031] A command operation set contains multiple single inspection commands, including combinations of basic operation and inspection operation commands, and encapsulates the parsing results of all steps in the form of key-value pairs. Commands consist of basic commands and custom commands. Basic commands can be obtained from the basic command set and contain all default preset information. Generally, each command set contains a varying number of basic commands and custom commands. Each custom command needs to be configured with the following information: the complete execution directory, the command start symbol, and the following information: the parsing keyword title, the command end symbol, the return value retrieval range, and whether to cache the results.

[0032] The command start and end markers are used to obtain the complete return value, which is the terminal device's command-line print return value, consisting of a single line or multiple lines of long text. Based on the set search scope (single line or multiple lines) and keyword headings, the target return value output by the terminal can be obtained.

[0033] For data that changes infrequently but is queried frequently (such as the software / hardware version number of a single disk), a caching strategy is adopted, and the cache expiration time is manually set. If the same or other inspection commands are used in subsequent inspections, the cached data is queried first; if the cache does not exist, the command is executed on the device to retrieve the data, and the cache is updated.

[0034] The following process should be followed for updating the inspection items: Newly added resource files are named in the format of "version number + date," which helps to clearly identify the content and timing of each update. Information related to each inspection item version update (such as version number, update date, and specific content) is recorded in the database for management and tracking. When the service starts, the system checks for any unloaded new version resource files. If a new version is found, the system will automatically perform an incremental update to ensure that all the latest inspection item information takes effect promptly.

[0035] The command configuration module in this embodiment provides a graphical command set generator, which allows users to easily configure the required operation command set online. Users can add or remove commands by dragging and dropping, making the operation more intuitive and convenient. Commands are divided into two parts: basic commands and custom commands. Basic commands: You can select from a set of preset basic commands. Each basic command contains default preset information and is suitable for most routine inspection tasks.

[0036] Custom commands: Allows users to create and adjust commands according to specific needs to meet more specific or complex inspection requirements.

[0037] The specific information to configure OLT devices includes: Users log in via QR code scanning through the unified authentication platform, ensuring user legitimacy and access control to system resources. After successful login, users need to specify the basic data for this service, including: Basic data source for devices: Network element information of OLT devices, which can be imported through templates or obtained online from the network management system.

[0038] Network management server IP and network management database IP: These are used to specify the server and database addresses for managing network devices.

[0039] Northbound IP: Specifies the interface address used by the network management system to communicate with other systems.

[0040] Network Management System Type: Identifies the type of network management system used to ensure proper parsing and processing of relevant data.

[0041] Login method: Defines how to log in to the target device, including authentication information such as username / password and key.

[0042] Connection test parameters: Used to verify the validity of the connection with the device and ensure that the configuration is correct.

[0043] Upgrade package download method: FTP server.

[0044] The network management system acts as a closed intranet resource server, supporting the distribution of files or parameters. Some intranet devices can achieve online calibration through gateway communication. External network devices disable the network management system's functions to ensure network security.

[0045] In this embodiment, after obtaining the data source, a single-board check needs to be performed on the network element immediately before the relevant device information is synchronized to the database. The device information data can be set to expire. When selecting a network element before the inspection / upgrade task begins, if the queried device information has expired, a single-board check will be performed immediately and the relevant data will be updated.

[0046] After completing the above configuration, the OLT equipment batch maintenance method of the present invention is executed, including: Retrieve user-defined maintenance tasks; Obtain multiple network elements corresponding to the maintenance task, as well as the single-disk version information of the network element; Based on the maintenance task, a maintenance thread for each network element is constructed using the single-disk version information, and the maximum number of parallel network elements is configured. After the maintenance task is started, the task is executed according to the maintenance thread, and the maintenance progress and exception information are recorded to obtain the maintenance task record data; Based on the recorded data of the maintenance tasks, the maintenance tasks are weighted and calculated according to the preset scoring rules to obtain the maintenance score; The maintenance score is encapsulated with the category of the maintenance task to obtain the maintenance result.

[0047] Optionally, when the maintenance task is an inspection task, obtaining the user-defined inspection task specifically involves: Create an initial inspection template to support users in selecting one or more inspection items, setting alarm conditions for each inspection item, and setting the maximum number of parallel inspection threads to obtain the content inspection template. The content inspection template is processed to obtain the inspection task.

[0048] like Figure 2 As shown in this embodiment, the generated content inspection template supports batch import and export migration. Inspection tasks can be initiated on the initialization inspection template interface. First, select the device (network element) to be inspected; the data is taken from the network element information table. Then, you can choose to execute immediately or set the task execution time (schedule). Scheduled inspection tasks can be generated once per hour, minute, and second, or batch generation is supported by manually filling in CRON expressions.

[0049] Optionally, when the maintenance task is an upgrade task, obtaining the user-defined upgrade task specifically involves: Receive the target upgrade information input; The corresponding target upgrade package is selected from the FTP resource server according to the target upgrade information, and the upgrade task is obtained based on the target upgrade package. The target upgrade package is used to upgrade the current software version to the target version. The FTP resource server is pre-configured for managing and distributing software upgrade packages.

[0050] In this embodiment, the target upgrade information includes parameters such as single disk type, upgrade package type, and compilation time.

[0051] Optional, also includes: The target upgrade package is matched and detected with the single disk version information of the network element to be upgraded; wherein, the matching and detection content includes: version number, compilation time and single disk type; Upgrade the software for disks that pass the matching test.

[0052] Optional, also includes: After the upgrade task is completed, determine whether a network element-level reset is required based on the target upgrade package. If not, the maintenance score will be calculated after all upgrade tasks have been completed. If necessary, the basic information of all single disks within the network element can be queried and stored based on the upgrade task ID, network element ID, and single disk ID as a composite key to obtain the first basic information; After resetting, the basic information of all single disks in the network element is re-queried and stored to obtain the second basic information. Based on the second basic information, it is determined whether the software version should be upgraded to the target version. If the target version is not upgraded, the upgrade is considered to have failed. If the upgrade is to the target version, the status of the first basic information and the second basic information will be compared, and a comparison result of whether the upgrade was successful will be obtained based on a preset comparison threshold.

[0053] like Figure 3 As shown in this embodiment, after the upgrade task is started, each thread will traverse in the order of first the line card (service board) and then the main control board, comparing and matching the detection results one by one and executing the upgrade. At the same time, it will determine whether a network element-level reset (reboot) is required based on the upgrade package configuration.

[0054] In this embodiment, the basic information of all individual boards within the network element includes parameters such as the number of boards, hardware version, network slot, and software version. Taking the number of boards and the slot number of boards as thresholds as an example, if the number of boards within the network element changes or the corresponding slot number of each board changes after the upgrade, it is considered that the network element reset is abnormal, and the network element upgrade is also considered to have failed.

[0055] Optionally, after starting the maintenance task, the task is executed according to the maintenance thread, and the maintenance progress and exception information are recorded. The specific recorded data of the maintenance task includes: Generate a globally unique task identifier (taskId) for the maintenance task, and calculate the total number of all maintenance task items in the maintenance task; The number of completed maintenance items and the number of abnormal maintenance items are initialized to 0, and the error information string "errorInfo" is initialized to be empty. In this embodiment, the information is maintained in the cache using taskId as the key.

[0056] The maintenance tasks are grouped according to network elements and executed accordingly. It is then determined whether each maintenance task has been completed. If a maintenance task is completed, the number of completed maintenance tasks is incremented by one. If an anomaly occurs in a maintenance task item, the number of anomaly maintenance items is incremented by one, and the anomaly information generated based on the anomaly is stored in the anomaly information string errorInfo. Based on the number of completed maintenance items, the number of abnormal maintenance items, and the total number, the current maintenance progress is periodically calculated using a progress calculation method. The formula for the progress calculation method is: (C+F) / N; where C represents the number of completed maintenance items, F represents the number of abnormal maintenance items, and N represents the total number.

[0057] In this embodiment, a polling query is used to query the current maintenance progress value and update the progress bar. The polling query time interval is 10 seconds, and the progress bar is displayed as a percentage.

[0058] Optionally, the scoring rules for inspection tasks include: weight configuration rules, anomaly score configuration rules, and rejection threshold configuration rules; The weighting configuration rules are used to assign weights to special items in the inspection and to calculate the overall quality assessment score of the inspection task based on the weights. The exception item scoring configuration rules are used to set deduction values ​​for abnormal situations that occur during the execution of inspection tasks. The abnormal situations include inspection error results, failure to obtain valid values, and failure to log in. The negation threshold configuration rule is used to determine whether the proportion of the number of abnormal units to the total number of all units corresponding to the inspection task exceeds the preset negation threshold. If it exceeds the threshold, the inspection task score is zero. The unit is a network element or a single disk.

[0059] In this embodiment, the weight configuration rules allow manual adjustment of the weights corresponding to sub-inspection items in the overall quality assessment template. Sub-inspection items not included in the overall quality assessment template are not weighted. The anomaly scoring configuration rules are divided into two types: fixed scores and proportional scores. To improve performance, the scoring rules are loaded into the cache when the service starts, and no expiration time is set. The scoring cache is overwritten each time the service restarts, improving the efficiency of score calculation when multiple network elements / single disks are inspected concurrently.

[0060] Based on and Figure 1 Using the same principle as the method shown, this embodiment of the invention also provides a batch maintenance system for OLT equipment, such as... Figure 4 As shown, it includes: The task creation module is used to retrieve maintenance tasks created by the user. The network element information acquisition module is used to acquire multiple network elements corresponding to the maintenance task, as well as the single-disk version information of the network element; The task generation module is used to construct a maintenance thread for each network element based on the maintenance task and the single-disk version information, and to configure the maximum number of parallel network elements. The task recording module is used to execute the task according to the maintenance thread after the maintenance task is started, and to record the maintenance progress and exception information to obtain the record data of the maintenance task. The task score calculation module is used to calculate the maintenance score by weighting the maintenance tasks according to the recorded data of the maintenance tasks and the preset scoring rules. The result output module is used to encapsulate the maintenance score and the category of the maintenance task to obtain the maintenance result.

[0061] The OLT equipment batch maintenance system of this invention can execute the OLT equipment batch maintenance method provided in this invention. The implementation principle is similar. The actions performed by each module and unit in the OLT equipment batch maintenance system of each embodiment of this invention correspond to the steps in the OLT equipment batch maintenance method of each embodiment of this invention. For detailed functional descriptions of each module of the OLT equipment batch maintenance system, please refer to the descriptions in the corresponding OLT equipment batch maintenance methods shown above, which will not be repeated here.

[0062] The aforementioned OLT equipment batch maintenance system can be a computer program (including program code) running on a computer device, such as an application software; the application software can be used to execute the corresponding steps in the method provided in the embodiments of the present invention.

[0063] The modules described in the embodiments of the present invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.

[0064] Based on the same principles as the methods shown in the embodiments of the present invention, the embodiments of the present invention also provide an electronic device, which may include, but is not limited to: a processor and a memory; the memory for storing computer programs; and the processor for executing the methods shown in any embodiment of the present invention by invoking the computer programs.

[0065] In one alternative embodiment, an electronic device is provided, such as Figure 5 As shown, Figure 5 The illustrated electronic device includes a processor and a memory. The processor and memory are connected, for example, via a bus. Optionally, the electronic device may also include a transceiver, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver is not limited to one unit, and the structure of this electronic device does not constitute a limitation on the embodiments of the present invention.

[0066] The memory stores application code (computer program) that executes the present invention, and its execution is controlled by a processor. The processor executes the application code stored in the memory to implement the content shown in the foregoing method embodiments.

[0067] Among these, electronic devices can also be terminal devices. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0068] This invention provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.

[0069] According to another aspect of the present invention, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various embodiments described above.

[0070] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0071] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.

[0072] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

Claims

1. A method for batch maintenance of OLT equipment, characterized in that, The method includes: Retrieve user-defined maintenance tasks; Obtain multiple network elements corresponding to the maintenance task, as well as the single-disk version information of the network element; Based on the maintenance task, a maintenance thread for each network element is constructed using the single-disk version information, and the maximum number of parallel network elements is configured. After the maintenance task is started, the task is executed according to the maintenance thread, and the maintenance progress and exception information are recorded to obtain the maintenance task record data; Based on the recorded data of the maintenance tasks, the maintenance tasks are weighted and calculated according to the preset scoring rules to obtain the maintenance score; The maintenance score is encapsulated with the category of the maintenance task to obtain the maintenance result.

2. The method for batch maintenance of OLT equipment according to claim 1, characterized in that, When the maintenance task is an inspection task, the specific steps for obtaining a user-defined inspection task are as follows: Create an initial inspection template to support users in selecting one or more inspection items, setting alarm conditions for each inspection item, and setting the maximum number of parallel inspection threads to obtain the content inspection template. The content inspection template is processed to obtain the inspection task.

3. The method for batch maintenance of OLT equipment according to claim 2, characterized in that, When the maintenance task is an upgrade task, obtaining the user-defined upgrade task specifically involves: Receive the target upgrade information input; The corresponding target upgrade package is selected from the FTP resource server according to the target upgrade information, and the upgrade task is obtained based on the target upgrade package. The target upgrade package is used to upgrade the current software version to the target version. The FTP resource server is pre-configured for managing and distributing software upgrade packages.

4. The method for batch maintenance of OLT equipment according to claim 3, characterized in that, Also includes: The target upgrade package is matched and detected with the single disk version information of the network element to be upgraded; wherein, the matching and detection content includes: version number, compilation time and single disk type; Upgrade the software for disks that pass the matching test.

5. A method for batch maintenance of OLT equipment according to claim 3, characterized in that, Also includes: After the upgrade task is completed, determine whether a network element-level reset is required based on the target upgrade package. If not, the maintenance score will be calculated after all upgrade tasks have been completed. If necessary, the basic information of all single disks within the network element can be queried and stored based on the upgrade task ID, network element ID, and single disk ID as a composite key to obtain the first basic information; After resetting, the basic information of all single disks in the network element is re-queried and stored to obtain the second basic information. Based on the second basic information, it is determined whether the software version should be upgraded to the target version. If the target version is not upgraded, the upgrade is considered to have failed. If the upgrade is to the target version, the status of the first basic information and the second basic information will be compared, and a comparison result of whether the upgrade was successful will be obtained based on a preset comparison threshold.

6. The method for batch maintenance of OLT equipment according to claim 1, characterized in that, After the maintenance task is started, the task is executed according to the maintenance thread, and the maintenance progress and exception information are recorded. The specific recorded data of the maintenance task includes: Generate a globally unique task identifier (taskId) for the maintenance task, and calculate the total number of all maintenance task items in the maintenance task; The number of completed maintenance items and the number of abnormal maintenance items are initialized to 0, and the error information string "errorInfo" is initialized to be empty. The maintenance tasks are grouped according to network elements and executed accordingly. It is then determined whether each maintenance task has been completed. If a maintenance task is completed, the number of completed maintenance tasks is incremented by one. If an anomaly occurs in a maintenance task item, the number of anomaly maintenance items is incremented by one, and the anomaly information generated based on the anomaly is stored in the anomaly information string errorInfo. Based on the number of completed maintenance items, the number of abnormal maintenance items, and the total number, the current maintenance progress is periodically calculated using a progress calculation method. The formula for the progress calculation method is: (C+F) / N; where C represents the number of completed maintenance items, F represents the number of abnormal maintenance items, and N represents the total number.

7. A method for batch maintenance of OLT equipment according to claim 2, characterized in that, The scoring rules for inspection tasks include: weight configuration rules, anomaly score configuration rules, and rejection threshold configuration rules; The weighting configuration rules are used to assign weights to special items in the inspection and to calculate the overall quality assessment score of the inspection task based on the weights. The exception item scoring configuration rules are used to set deduction values ​​for abnormal situations that occur during the execution of inspection tasks. The abnormal situations include inspection error results, failure to obtain valid values, and failure to log in. The negation threshold configuration rule is used to determine whether the proportion of the number of abnormal units to the total number of all units corresponding to the inspection task exceeds the preset negation threshold. If it exceeds the threshold, the inspection task score is zero. The unit is a network element or a single disk.

8. A batch maintenance system for OLT equipment, characterized in that, include: The task creation module is used to retrieve maintenance tasks created by the user. The network element information acquisition module is used to acquire multiple network elements corresponding to the maintenance task, as well as the single-disk version information of the network element; The task generation module is used to construct a maintenance thread for each network element based on the maintenance task and the single-disk version information, and to configure the maximum number of parallel network elements. The task recording module is used to execute the maintenance task according to the maintenance thread after the maintenance task is started, and to record the maintenance progress and exception information to obtain the maintenance task recording data. The task score calculation module is used to calculate the maintenance score by weighting the maintenance tasks according to the recorded data of the maintenance tasks and the preset scoring rules. The result output module is used to encapsulate the maintenance score and the category of the maintenance task to obtain the maintenance result.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-7.

10. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1-7.

Images