A method for producing customized plug-in for PON terminal equipment

Abstract

The present invention discloses a method for producing a customized plug-in for a PON terminal device. The method provides a method for encoding a plug-in, introduces intelligent operation into the upgrade management of the plug-in for the PON terminal device, and provides a method for verifying the plug-in upgrade during the production process. By using the method for producing a customized plug-in for a PON terminal device disclosed by the present invention, plug-in production is performed, which saves manpower and hardware costs in the production version verification stage, introduces intelligent management into the production upgrade of the plug-in, avoids manual errors caused by multiple versions, ensures the correctness of the plug-in, and thus guarantees the quality of the software.

Description

Technical Field

[0001] The present invention relates to the technical field of software plug-ins, and in particular to a method for producing a customized plug-in for PON terminal equipment. Background Art

[0002] With the continuous development of the information age, the internet has penetrated every walk of life, from shopping malls to ordinary households. PON equipment has become an indispensable part of network access. Due to the diverse needs of different regions, industries, and user types, customized plug-ins have been launched across the country to meet these diverse requirements. However, due to the wide variety of plug-ins, different provinces, regions, models, and batches of equipment may require different software versions. This creates management difficulties during version testing and equipment production, increasing labor and time costs.

[0003] If all plug-ins are merged into one version, more flash memory space will be required to support the writing of larger software, resulting in hardware waste and increased costs. It will also be extremely inconvenient when modifications or new plug-ins need to be produced and written in the future. More consideration needs to be given to the flash memory space of the devices in the existing network, and managing the addition and deletion of different plug-ins is also relatively complicated. Summary of the Invention

[0004] In order to solve the above problems of high manpower and time costs, large flash consumption, and complex management of different plug-ins, the present invention proposes a method for producing customized plug-ins for PON terminal equipment.

[0005] A method for producing a customized plug-in for a PON terminal device, comprising:

[0006] Step S1: The staff configures the plug-in and production environment preconditions;

[0007] Step S2: Producing the plug-in using the PON terminal equipment;

[0008] Step S3: The smart device verifies the produced plug-in.

[0009] Furthermore, the preconditions of step S1 also include:

[0010] Custom plugin coding;

[0011] Production environment configuration plug-in code table, plug-in library;

[0012] The production software integrates writing plug-in coding commands and integrates downloading, upgrading and running plug-in functions.

[0013] Furthermore, the customized plug-in coding structure includes: SDK code, plug-in name code, and plug-in version number.

[0014] Furthermore, the plug-in production process in step S2 further includes the following sub-steps:

[0015] Step S21: The production staff uses a scanner to scan the PON terminal device label, and the scanner sends the scanned information to the smart device;

[0016] Step S22: The smart device checks the plug-in coding table based on the plug-in coding information sent by the scanner to determine whether the plug-in coding needs to be written into the version;

[0017] Step S23: If the default code of the device is not found, the plug-in code is not written, and the plug-in upgrade verification is not performed by default;

[0018] Step S24: Find the plug-in code that needs to be written to the device, call the write plug-in code command integrated in the PON software through the telnet function of the PON terminal device, and write the corresponding plug-in code. If the plug-in code is not found, do not write it;

[0019] Furthermore, the plug-in production process in step S2 further includes the following sub-steps:

[0020] Step S25: Error checking: The PON device software checks whether the plug-in code supports the model according to the plug-in code information and performs error checking. If the plug-in code does not support the software, the information is returned to the smart device.

[0021] Step S26: The smart device calls the download plug-in command integrated in the PON software through the telnet service;

[0022] Step S27: After the PON download is completed, the MD5 value of the downloaded plug-in is fed back to the smart device, and the smart device performs MD5 verification on the downloaded plug-in;

[0023] Step S28: For the PON device that passes the md5 verification, the smart device calls the upgrade function integrated in the PON software through telnet to upgrade the plug-in;

[0024] Step S29: If the md5 verification fails, return to step S26 and re-download the verification. The number of verification failures is increased by 1. If the verification fails three times, manual intervention is required.

[0025] Furthermore, the step S25 of error checking the plug-in code includes: checking the code through SDK.

[0026] Furthermore, the production verification step S3 further includes the following sub-steps:

[0027] Step S31: After the other production processes are restored to factory, the smart device reads the plug-in code written on the PON device and compares it with the plug-in code on the server to determine whether it is applicable to the device;

[0028] Step S32: If applicable, proceed to step S33; if not, report the fault and the corresponding error code;

[0029] Step S33: calling the start plug-in command through telnet to check whether the returned activation result is successful;

[0030] Step S34: Successful verification is completed, and the corresponding error code is reported if failure occurs.

[0031] Beneficial effects of the present invention: The present invention proposes a method for producing customized plug-ins for PON terminal equipment, provides a method for plug-in encoding, introduces intelligent operation into the plug-in upgrade management of PON terminal equipment, and provides a method for plug-in upgrade verification during the production process, which has the following effects:

[0032] (1) Each plug-in only needs to be verified on a unified production version, without having to verify numerous production versions each time, saving manpower in the reproduction version verification stage; due to the unified version, the plug-in is downloaded and upgraded to the PON equipment during the production stage, saving flash memory expenses and hardware costs;

[0033] (2) Through plug-in coding, the production and upgrade of plug-ins are brought into intelligent management, saving labor costs and avoiding the mistakes that are easy to cause due to multiple versions;

[0034] (3) It has various verification processes to ensure the correctness of the plug-in and improve the quality of the software. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 This is a flow chart of a method for producing a customized plug-in for a PON terminal device proposed by the present invention; DETAILED DESCRIPTION

[0036] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described with reference to the accompanying drawings.

[0037] The present invention proposes a method for producing a customized plug-in for a PON terminal device, such as Figure 1 As shown, it includes preconditions, production process and production verification process.

[0038] In this embodiment, the preconditions include:

[0039] a. Customized plug-in code, consisting of three parts: supported SDK code, plug-in name code, and plug-in version number;

[0040] b. The production environment has a plug-in code table and plug-in library;

[0041] c. The production software integrates writing plug-in coding commands and integrates downloading, upgrading and running plug-in functions.

[0042] In this embodiment, the plug-in production process includes the following steps:

[0043] a. Production personnel use a scanner to scan the PON terminal device label, and the scanner sends the scanned information to the smart device;

[0044] b. The smart device checks the plug-in coding table based on the plug-in coding information sent by the scanner to determine whether the plug-in coding needs to be written into the version;

[0045] c. If the default code of the device is not found, the plug-in code will not be written and the plug-in upgrade verification will not be performed by default;

[0046] d. Find the plug-in code that needs to be written to the device, call the write plug-in code command integrated in the PON software through the PON terminal device telnet function, and write the corresponding plug-in code (if not found, do not write);

[0047] e. Error check: The PON device software checks whether the plug-in code supports the model according to the plug-in code information (based on SDK code verification), performs error checking, and returns information to the smart device if the plug-in code does not support the software.

[0048] f. The smart device calls the download plug-in command integrated in the PON software through telnet;

[0049] g. After the PON download is completed, the smart device will receive the MD5 value of the downloaded plug-in, and the smart device will perform MD5 verification on the downloaded plug-in;

[0050] h. For PON devices that pass the md5 verification, the smart device uses telnet to call the upgrade function integrated in the PON software to upgrade the plug-in;

[0051] i. If the MD5 verification fails, return to step f and download the verification again. The number of verification failures is increased by 1. If the verification fails three times, manual inspection is required.

[0052] In this embodiment, a production verification process is also included, including the following steps:

[0053] a. After completing other production processes and restoring the factory settings, the smart device reads the plug-in code written on the PON device and compares it with the plug-in code on the server to determine whether it is applicable to the device;

[0054] b. Proceed to step c if applicable. Do not apply the error code corresponding to the fault report.

[0055] c. Use telnet to call the start plug-in command and check whether the returned activation result is successful;

[0056] d. If successful, verification is complete; if failed, a corresponding error code will be reported.

[0057] The present invention proposes a method for producing customized plug-ins for PON terminal equipment, provides a method for plug-in encoding, introduces intelligent operation into the plug-in upgrade management of PON terminal equipment, and provides a method for plug-in upgrade verification during the production process, which has the following effects:

[0058] (1) Each plug-in only needs to be verified on a unified production version, without having to verify numerous production versions each time, saving manpower in the reproduction version verification stage; due to the unified version, the plug-in is downloaded and upgraded to the PON equipment during the production stage, saving flash memory expenses and hardware costs;

[0059] (2) Through plug-in coding, the production and upgrade of plug-ins are brought into intelligent management, saving labor costs and avoiding the mistakes that are easy to cause due to multiple versions;

[0060] (3) It has various verification processes to ensure the correctness of the plug-in and improve the quality of the software.

[0061] The basic principles, main features, and advantages of the present invention are shown and described above. Those skilled in the art should understand that the present invention is not limited to the foregoing embodiments. The foregoing embodiments and descriptions are merely illustrative of the principles of the present invention. Various changes and modifications may be made to the present invention without departing from the spirit and scope of the present invention. Such changes and modifications are intended to fall within the scope of the present invention. The scope of protection claimed in the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for producing a customized plug-in for a PON terminal device, characterized in that: include: Step S1: The staff configures the plug-in and production environment prerequisites, including: Customized plug-in code, the customized plug-in code structure includes: SDK code, plug-in name code, plug-in version number; Production environment configuration plug-in code table, plug-in library; The production software integrates writing plug-in coding commands and integrates downloading, upgrading and running plug-in functions; Step S2: Producing the plug-in using the PON terminal equipment, including the following sub-steps: Step S21: The production staff uses a scanner to scan the PON terminal device label, and the scanner sends the scanned information to the smart device; Step S22: The smart device checks the plug-in coding table based on the plug-in coding information sent by the scanner to determine whether the plug-in coding needs to be written into the version; Step S23: If the default code of the PON terminal device is not found, the plug-in code is not written, and the plug-in upgrade verification is not performed by default; Step S24: Find the plug-in code that needs to be written to the PON terminal device, call the write plug-in code command integrated in the PON software through the telnet function of the PON terminal device, and write the corresponding plug-in code. If the plug-in code is not found, do not write it; Step S25: Error checking: the PON device software checks the plug-in code according to the plug-in code information to determine whether it supports the plug-in and performs error checking. If the plug-in does not support the software, the software returns information to the smart device. Step S26: The smart device calls the download plug-in function integrated in the PON software through the telnet service; Step S27: After the download is completed, the PON terminal device feeds back the MD5 value of the downloaded plug-in to the smart device, and the smart device performs MD5 verification on the downloaded plug-in; Step S28: For the PON device that passes the md5 verification, the smart device calls the upgrade function integrated in the PON software through telnet to upgrade the plug-in; Step S29: If the MD5 verification fails, return to step S26 and re-download the verification. The number of verification failures is increased by 1. If the verification fails three times, manual intervention is required. Step S3: The smart device verifies the produced plug-in.

2. A method for producing a customized plug-in for a PON terminal device according to claim 1, characterized in that: The error checking plug-in code in step S25 includes: checking the code through SDK.

3. A method for producing a customized plug-in for a PON terminal device according to claim 1, characterized in that: The verification in step S3 further includes the following sub-steps: Step S31: After the production process is completed and the factory is restored, the smart device reads the plug-in code written on the PON device and compares it with the plug-in code on the server to determine whether it is applicable to the device; Step S32: If applicable, proceed to step S33; if not, report the fault and the corresponding error code; Step S33: calling the start plug-in command through telnet to check whether the returned activation result is successful; Step S34: If the verification is successful, the corresponding error code will be reported if the verification fails.

Images