An OLT device batch maintenance method, system, device and storage medium

Abstract

The present application relates to the technical field of software maintenance, and especially relates to an OLT device batch maintenance method, system, device and storage medium. The present application aims to solve the technical problems of lacking of exception and interruption processing, single function, unable to undertake complex actual online scene, and high misjudgment and misoperation rate in the prior art. The present application comprises the following steps: obtaining a maintenance task created by a user; obtaining a plurality of network elements corresponding to the maintenance task and single-disk version information of the network elements; constructing a maintenance thread of each network element by using the single-disk version information according to the maintenance task, and configuring a maximum number of parallel network elements; starting the maintenance task, executing the task according to the maintenance thread, recording maintenance progress and exception information, and obtaining record data of the maintenance task; performing weighted calculation on the maintenance task according to a preset scoring rule according to the record data of the maintenance task, and obtaining a maintenance score; and encapsulating the maintenance score and a category of the maintenance task, and obtaining 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 network element and single disk basic information; 3. entering the target directory of each single disk in a command line input mode to execute corresponding query / modification / upload / decompression commands; 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:

[0005] 1. In the query link, a corresponding command script can be written at present to realize the query type configuration inspection of 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 complex actual online scene cannot be handled.

[0006] 2. The OLT device maintenance service is usually accompanied by simultaneous operation of a large number of devices in the same region, and the number of terminals that can be operated by the same worker at the same time is limited, so 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

[0007] 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 that the lack of exception and interruption processing and the single function cannot handle the complex actual online scene, and the misjudgment and misoperation rate is high.

[0008] The technical scheme for solving the above technical problems is as follows: an OLT device batch maintenance method, comprising:

[0009] obtaining a maintenance task created by a user in a self-defined manner;

[0010] obtain a plurality of network elements corresponding to the maintenance task, and single-disk version information of the network elements;

[0011] construct a maintenance thread of each network element according to the maintenance task and the single-disk version information, and configure a maximum number of parallel network elements;

[0012] After starting 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;

[0013] According to the record data of the maintenance task, perform weighted calculation on the maintenance task according to a preset scoring rule, and obtain a maintenance score;

[0014] Encapsulate the maintenance score and the category of the maintenance task, and obtain a maintenance result.

[0015] Further, when the maintenance task is an inspection task, obtaining the user-defined created inspection task specifically comprises:

[0016] 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;

[0017] Process the content inspection template to obtain an inspection task.

[0018] Further, when the maintenance task is an upgrade task, obtaining the user-defined created upgrade task specifically comprises:

[0019] Receive input target upgrade information;

[0020] 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 the current software version to the target version; wherein the FTP resource server is pre-configured and used to manage the software upgrade package.

[0021] Further, the above also includes:

[0022] 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;

[0023] Perform software upgrade on the single disk that passes the matching and detection.

[0024] Further, the above also includes:

[0025] After the upgrade task is completed, it is determined whether a network element level reset is needed according to whether the target upgrade package needs to be acquired;

[0026] If not, the maintenance score is calculated after all upgrade tasks are completed;

[0027] If yes, based on the combination of the upgrade task id, the network element id and the single disk id, the basic information of all single disks in the network element is queried and stored to obtain first basic information;

[0028] After the reset, the basic information of all single disks in the network element is re-queried and stored to obtain second basic information, and it is determined whether the software version is upgraded to the target version based on the second basic information;

[0029] If not, it is determined that the upgrade fails;

[0030] If yes, the first basic information and the second basic information are compared in state, and a comparison result of whether the upgrade is successful is obtained based on a preset comparison threshold.

[0031] Further, after the maintenance task is started, 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:

[0032] 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;

[0033] 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;

[0034] The maintenance task is executed in groups according to the network element, and it is determined whether each maintenance task item is completed:

[0035] If the maintenance task item is completed, the number of completed maintenance items is added by one;

[0036] If the maintenance task item is abnormal, the number of abnormal maintenance items is added by one, and the abnormal information generated according to the abnormality is stored in the abnormal information string errorInfo;

[0037] 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.

[0038] Further, the scoring rule of the above-mentioned inspection task includes: a weight configuration rule, an abnormal item score configuration rule, and a negative threshold configuration rule.

[0039] The weight configuration rule is used to configure a weight for an inspection special item, and the overall quality evaluation score of the inspection task is calculated according to the weight.

[0040] The abnormal item score configuration rule is used to set a deduction value for an abnormal situation occurring in the execution of the inspection task, and the abnormal situation includes an inspection error result, an invalid value not being obtained, and an unsuccessful login.

[0041] 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 inspection task exceeds a preset negative threshold, and if so, the score of the inspection task is zero; wherein the unit is a network element or a single disk.

[0042] In a second aspect, the present application also provides an OLT device batch maintenance system, which comprises:

[0043] A task creation module is configured to obtain a maintenance task created by a user.

[0044] A network element information acquisition module is configured to obtain a plurality of network elements corresponding to the maintenance task and single disk version information of the network elements.

[0045] A task generation module is configured to construct a maintenance thread of each network element according to the maintenance task and using the single disk version information, and configure a maximum number of parallel network elements.

[0046] A task record module is configured to execute a task according to the maintenance thread after starting the maintenance task, record maintenance progress and abnormal information, and obtain record data of the maintenance task.

[0047] A task score calculation module is configured to perform a weighted calculation on the maintenance task according to a preset scoring rule according to the record data of the maintenance task, and obtain a maintenance score.

[0048] A result output module is configured to encapsulate the maintenance score and a category of the maintenance task, and obtain a maintenance result.

[0049] In a third aspect, the present application also provides an electronic device, which comprises a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the OLT device batch maintenance method of the present application when executing the computer program.

[0050] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the OLT device batch maintenance method.

[0051] Compared with the prior art, the present application has the following advantages:

[0052] 1. The inspection task of the present application can be set through a graphical interface, making the operation more intuitive and simple. The operation and maintenance personnel can select specific inspection items, set the inspection period, and adjust the inspection parameters according to the needs. Batch selection of network elements and single disks is supported, and the inspection strategy can be flexibly adjusted for different device types to ensure the comprehensiveness and pertinence of the inspection work.

[0053] 2. The automated maintenance process of the present application reduces the need for manual intervention, reduces the possibility of human error, and greatly improves the maintenance efficiency. For the maintenance results, the system can automatically generate detailed reports (in Excel, PDF, and Word formats) for subsequent analysis and archiving, further reducing the workload of the operation and maintenance personnel.

[0054] 3. The present application uses a timed polling method to obtain the maintenance progress, ensuring that the user can understand the maintenance status in real time. For abnormal situations, the system records detailed abnormal information to help quickly locate the problem. In the upgrade task, the system compares the state information of the device before and after the restart to accurately determine whether the upgrade is successful, increasing the reliability of the system.

[0055] 4. The scoring rules of the present application are loaded in the form of configuration files, supporting customization of scoring standards according to different inspection needs.

[0056] Other features and advantages of the present application will be set forth in the following description, and in part will become apparent to those skilled in the art from the description, or can be learned by practice of the present application. The objects and other advantages of the present application can be achieved and obtained by the structures indicated in the specification, claims, and drawings. BRIEF DESCRIPTION OF DRAWINGS

[0057] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0058] Figure 1 Fig. 1 shows a flowchart of an OLT device batch maintenance method according to an embodiment of the present application;

[0059] Figure 2 A flowchart of a patrol task according to an embodiment of the present application is shown;

[0060] Figure 3 A flowchart of an upgrade task according to an embodiment of the present application is shown;

[0061] Figure 4 A structural diagram of an OLT device batch maintenance system according to an embodiment of the present application is shown;

[0062] Figure 5 A structural diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0063] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the following will clearly and completely explain the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0064] Figure 1 A flowchart of an OLT device batch maintenance method according to an embodiment of the present application is shown, as shown in Figure 1 The OLT device batch maintenance method according to an embodiment of the present application includes:

[0065] The OLT device batch maintenance method according to an embodiment of the present application is used in a software system composed of a plurality of microservices, which includes a patrol service, an upgrade service, a user and communication service, and a device information service, and a set of graphical system for user operation. Each service is independently deployed, and partial microservices can be degraded or disabled for different use ranges (such as devices in the region only perform patrol).

[0066] First, patrol item information, an FTP resource server, and OLT device information are configured. The configuration of the patrol item information specifically includes:

[0067] When the present embodiment is first deployed, the following steps are used to complete the delivery of initial patrol item information, operation command set, and scoring rules, and trigger the establishment of a patrol item table:

[0068] The initial patrol item information, operation command set, and scoring rules can be configured through an XML resource file or an Excel format file. These files will be used to trigger the establishment of the patrol item table, ensuring that the system can identify and process all patrol tasks and related parameters.

[0069] In this embodiment, the inspection item information includes inspection item type, result expression, inspection item label, and alarm condition.

[0070] The inspection item type is divided into two levels. The first level type includes network element, single disk, and port. The second level type includes device information, environment state, configuration state, running state, performance state, and resource amount. When the inspection item result is generated, the data will be divided into different tables / sheets according to the first level type. The second level type is used by the user to filter the inspection item in the graphical interface of the system.

[0071] The inspection result expression type includes numerical value, character string, and Boolean value. When the inspection item information is defined, the corresponding result type needs to be specified. For example, temperature and quantity are related to numerical value, and enable and disable state are related to Boolean value. The default value is character type.

[0072] The inspection item label is divided into master control, uplink, and line card. One inspection item can belong to multiple labels. A certain inspection task involves multiple different login methods and operation command sets.

[0073] The alarm condition includes the judgment according to the result expression type. For the numerical value type inspection result (including the numerical value converted from date), the condition format of greater than, less than, equal to, and their combinations is provided. For the Boolean value type inspection result, the condition format of true / false result is provided. The user defines the combination when starting the inspection task in the graphical interface. The alarm condition also includes the alarm state keyword, that is, after triggering the alarm, special marking is performed in the inspection result according to the state value. The alarm state includes normal, abnormal, not acquired, not defined, and default.

[0074] In this embodiment, the operation command is divided into basic operation and inspection operation. The entire execution process includes environment verification, command legality verification, and multiple steps. The following is a detailed process and mechanism description:

[0075] Basic operation: including login, logout, reset, software and hardware information query, fixed directory, and other basic functions.

[0076] Inspection operation: including independent and non-reusable query / modification command, which is specially used for device state checking.

[0077] Single inspection command execution process: 1. Environment verification: ensure that the execution environment meets the requirements. 2. Command legality verification: verify whether the command is legal and effective. 3. Single command execution and return of terminal result: execute the command on the device and obtain the result. 4. Return value analysis: analyze the data returned by the command and extract useful information. 5. Exception handling (if any): handle any abnormal situations that occur during execution. 6. Return to the main path: after completing the above steps, return to the main flow to continue executing subsequent commands or end the current task.

[0078] A command operation set contains multiple single inspection commands, contains a combination of basic operations and inspection operation commands, and encapsulates all step analysis results in the form of key-value pairs;

[0079] The command includes basic commands and custom commands, and the basic commands can be obtained from a basic command set, which contains all default preset information. Generally speaking, each command set contains a certain number of basic commands and custom commands;

[0080] Each custom command needs to be configured with predecessor information: complete execution directory, command starting symbol, and successor information: analysis keyword title, command ending symbol, return value retrieval range, and whether to cache results.

[0081] Among them, the command starting and ending symbols are used to obtain complete return values, and the complete return value is the terminal device command line print return value, which is a single line or multiple line long text. According to the set retrieval range (single line, multiple lines) and keyword title, the target return value output by the terminal can be obtained.

[0082] For those data with low change frequency but frequent query (such as single disk software / hardware version number), a caching strategy is adopted, and the cache expiration time is manually set. If the same or other inspection process is used in the subsequent same or other inspection process, the cache data is queried first; if the cache does not exist, the command is executed in the device to obtain the data, and the cache is updated.

[0083] For the update of the inspection item content, the following process is followed:

[0084] The newly added resource file is named in the format of "version number + date", which helps to clearly understand the content and time point of each update. The relevant information of each inspection item version update (such as version number, update date, specific content, etc.) will be recorded in the database, so as to facilitate management and tracking. When the service starts, the system will check whether there is a new version of the resource file that has not been loaded. If a new version is found, the system will automatically perform incremental update and loading to ensure that all the latest inspection item information can be timely into effect.

[0085] The command configuration module in the embodiment provides a graphical command set generator, so that users can easily configure the required operation command set online:

[0086] Users can add or delete commands by dragging, making the operation more intuitive and simple. The commands are divided into two parts: basic commands and custom commands.

[0087] Basic commands: can be selected by pulling down from a preset basic command set. Each basic command contains default preset information and is suitable for most routine inspection tasks.

[0088] Customized command: allows users to create and adjust commands based on specific needs to meet more specific or complex inspection requirements.

[0089] The configuration OLT device information specifically includes:

[0090] Users log in by scanning the code through the unified authentication platform, ensuring the legitimacy of the users and access control to system resources. After successful login, users need to calibrate the basic data for this service, including:

[0091] Device basic data source: network element information of OLT devices, which can be imported through templates or obtained online from network management.

[0092] Network management server IP, network management database IP: used to specify the server and database addresses for managing network devices.

[0093] North IP: indicates the interface address used for communication with other systems in the network management system.

[0094] Network management system type: identifies the type of network management system used to correctly parse and process related data.

[0095] Login method: defines how to log in to the target device, including username / password, key, and other authentication information.

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

[0097] Upgrade package download method: FTP server.

[0098] Among them, the network management system is a closed intranet resource server that supports file or parameter download, and some intranet devices can communicate through the gateway to achieve online calibration. The related functions of the network management system for external network devices are disabled to ensure network security.

[0099] In this embodiment, after obtaining the data source, a single disk detection of the network element needs to be performed immediately, and the related device information will be synchronized to the database. The device information data can be set to expire, and when selecting the network element before starting the inspection / upgrade task, if the queried device information has expired, a single disk detection will be performed immediately and the related data will be updated.

[0100] After completing the above configuration, an OLT device batch maintenance method of the present application is executed, including:

[0101] Obtain the maintenance task created by the user;

[0102] Obtain a plurality of network elements corresponding to the maintenance task, and single disk version information of the network elements;

[0103] According to the maintenance task, a maintenance thread of each network element is constructed by using the single-disk version information, and a maximum number of parallel network elements is configured;

[0104] After starting the maintenance task, the task is executed according to the maintenance thread, and maintenance progress and exception information are recorded to obtain record data of the maintenance task;

[0105] According to the record data of the maintenance task, a maintenance score is obtained by performing weighted calculation on the maintenance task according to a preset scoring rule;

[0106] The maintenance score and the category of the maintenance task are encapsulated to obtain a maintenance result.

[0107] Optionally, when the maintenance task is an inspection task, the user-defined created inspection task is specifically:

[0108] An initialization inspection template is created, which is used to support user-defined selection of one or more inspection items, setting of an alarm condition of each inspection item, and setting of a number of maximum parallel inspection threads to obtain a content inspection template;

[0109] The content inspection template is processed to obtain an inspection task.

[0110] As shown in Figure 2 In this embodiment, the generated content inspection template supports batch import and export transplantation. In the initialization inspection template interface, an inspection task can be initiated. First, a device (network element) to be inspected is selected, and data is obtained from a network element information table. Then, immediate execution or setting of a task execution time (reservation mode) can be selected. The reservation inspection task can be generated once a task at a specific time and minute, or batch generation is supported by manually filling in a CRON expression.

[0111] Optionally, when the maintenance task is an upgrade task, the user-defined created upgrade task is specifically:

[0112] Target upgrade information input is received;

[0113] According to the target upgrade information, a corresponding target upgrade package is selected from an FTP resource server, and the upgrade task is obtained based on the target upgrade package, wherein the target upgrade package is used to upgrade the current software version to a target version; wherein the FTP resource server is pre-configured and used to manage a software upgrade package.

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

[0115] Optionally, it further includes:

[0116] The target upgrade package is matched with single-disk version information of the network element to be upgraded, wherein the matching detection content includes version number, compiling time and single-disk type.

[0117] The single disk that passes the matching detection is upgraded.

[0118] Optionally, the method further comprises:

[0119] After the upgrade task is completed, it is determined whether a network element level reset is needed according to the target upgrade package;

[0120] If not, the maintenance score is calculated after all upgrade tasks are completed;

[0121] If yes, the basic information of all single disks in the network element is queried and stored based on the combination of the upgrade task id, the network element id and the single disk id, to obtain first basic information;

[0122] After the reset, the basic information of all single disks in the network element is re-queried and stored to obtain second basic information, and it is determined whether the software version is upgraded to the target version based on the second basic information;

[0123] If not, it is determined that the upgrade fails;

[0124] If yes, the first basic information and the second basic information are compared, and a comparison result of whether the upgrade is successful is obtained based on a preset comparison threshold.

[0125] As shown in Figure 3 In this embodiment, after the upgrade task is started, each thread will be traversed in the order of line card (service disk) and master disk, and the matching detection result is compared and upgraded one by one. At the same time, it is determined whether a network element level reset (restart) is needed according to the upgrade package configuration.

[0126] In this embodiment, the basic information of all single disks in the network element includes single disk quantity, hardware version, in-network slot, software version and other parameters. Taking the single disk quantity and single disk slot number as threshold values as an example, if the single disk quantity in the network element changes or the corresponding slot numbers of the single disks change after the upgrade, it is considered that the network element reset is abnormal, and the network element upgrade fails.

[0127] Optionally, after the maintenance task is started, the maintenance thread executes the task, and records the maintenance progress and abnormal information to obtain record data of the maintenance task, which specifically includes:

[0128] 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;

[0129] Initialize the number of completed maintenance items and the number of abnormal maintenance items to 0, and initialize the error information string errorInfo to be empty;

[0130] In this embodiment, the information is maintained in the cache with taskId as the key.

[0131] The maintenance tasks are grouped according to network elements, and it is determined whether each maintenance task item is completed:

[0132] If the maintenance task item is completed, the number of completed maintenance items is incremented by 1;

[0133] If the maintenance task item is abnormal, the number of abnormal maintenance items is incremented by 1, and the abnormal information generated according to the abnormality is stored in the error information string errorInfo;

[0134] Based on the number of completed maintenance items, the number of abnormal maintenance items, and the total number, the current maintenance progress is calculated periodically 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.

[0135] In this embodiment, the current maintenance progress value is queried and the progress bar is updated by polling query, the polling query interval is 10s, and the progress bar is displayed in percentage form.

[0136] Optionally, the scoring rule of the inspection task includes: a weight configuration rule, an abnormal item score configuration rule, and a negative threshold configuration rule;

[0137] The weight configuration rule is used to configure a weight for a special inspection item, and the overall quality evaluation score of the inspection task is calculated according to the weight;

[0138] The abnormal item score configuration rule is used to set a deduction value for abnormal situations occurring in the execution of the inspection task, and the abnormal situations include inspection error results, no valid value obtained, and unsuccessful login;

[0139] 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 inspection task exceeds a preset negative threshold, if yes, the score of the inspection task is zero; wherein the unit is a network element or a single disk.

[0140] In the embodiment, the weight configuration rule can manually adjust the weight corresponding to the sub-inspection item in the overall quality evaluation template, and the sub-inspection item of the non-overall quality evaluation template does not calculate the weight value. The type of the abnormal item score configuration rule is divided into fixed score and equal proportion score. In order to improve performance, the scoring rule is loaded into the cache when the service starts, and no expiration time is set. Each time the service is restarted and started, the scoring cache will be overwritten to improve the scoring calculation efficiency when multiple network elements / single disks are concurrently inspected.

[0141] Based on the same principle as the method shown in Figure 1 The embodiment of the application also provides an OLT device batch maintenance system, which, as shown in Figure 4 The embodiment of the application also provides an OLT device batch maintenance system, which, as shown in

[0142] A task creation module is configured to obtain a maintenance task created by a user;

[0143] A network element information acquisition module is configured to obtain a plurality of network elements corresponding to the maintenance task and single-disk version information of the network elements;

[0144] A task generation module is configured to 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;

[0145] A task record module is configured to execute a task according to the maintenance thread after starting the maintenance task, record maintenance progress and abnormal information, and obtain record data of the maintenance task;

[0146] A task score calculation module is configured to perform weighted calculation on the maintenance task according to a preset scoring rule according to the record data of the maintenance task, and obtain a maintenance score;

[0147] A result output module is configured to encapsulate the maintenance score and a category of the maintenance task, and obtain a maintenance result.

[0148] The OLT device batch maintenance system of the embodiment of the application can execute the OLT device batch maintenance method provided by the embodiment of the application, and the implementation principles are similar. The actions performed by each module and unit in the OLT device batch maintenance system in each embodiment of the application correspond to the steps in the OLT device batch maintenance method in each embodiment of the application. For the detailed function description of each module of the OLT device batch maintenance system, refer to the description of the corresponding OLT device batch maintenance method in the foregoing, which will not be repeated here.

[0149] The OLT device batch maintenance system can be a computer program (including program code) running in a computer device, for example, the OLT device batch maintenance system is an application software; the application software can be used to execute corresponding steps in the method provided by the embodiments of the present application.

[0150] The modules described in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0151] Based on the same principle as the method shown in the embodiments of the present application, the embodiments of the present application also provide an electronic device, which can include but is not limited to: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the method shown in any of the embodiments of the present application by calling the computer program.

[0152] In an optional embodiment, an electronic device is provided, as shown in Figure 5 As shown in Figure 5 The electronic device shown includes a processor and a memory. The processor and the memory are connected, such as through a bus. Optionally, the electronic device can also include a transceiver, which can be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception, etc. It should be noted that in actual application, the transceiver is not limited to one, and the structure of the electronic device does not constitute a limitation on the embodiments of the present application.

[0153] The memory is used to store the application program code (computer program) for executing the scheme of the present application, and the processor is used to control the execution. The processor is used to execute the application program code stored in the memory to realize the content shown in the foregoing method embodiments.

[0154] The electronic device can also be a terminal device, Figure 5 The electronic device shown is only an example and should not limit the function and use range of the embodiments of the present application.

[0155] The embodiments of the present application provide a computer readable storage medium, which stores a computer program, when the computer program runs on a computer, the computer can execute the corresponding content in the foregoing method embodiments.

[0156] According to another aspect of the present application, there is also provided a computer program product or computer program 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 the processor executes the computer instructions to cause the computer device to perform the methods provided in the various embodiments.

[0157] It should be understood that the flowchart and the block diagram in the drawings illustrate the possible implementation of the methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or the block diagram can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the flowchart or the block diagram can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagram and / or flowchart, and combinations thereof, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or combinations of hardware and software.

[0158] The above computer readable storage medium stores one or more programs, which when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0159] The above description merely illustrates the preferred embodiments of the present application and the principles of the technology applied. It is understood that the disclosed scope of the present application is not limited to the specific combinations of technical features described above, but also covers other technical solutions formed by any combinations of the above technical features or equivalent features thereof without departing from the above disclosed concept. For example, the above technical features can be replaced with other technical features disclosed in the present application (but not limited to) having similar functions to form technical solutions.

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 these 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 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.

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