Device software version number self-adaption method

The self-adaptive software version method through a private format summary file and customized configuration structure addresses high maintenance costs and error probabilities by adapting software versions based on OEM and province codes, reducing the need for multiple versions.

CN119088433APending Publication Date: 2024-12-06ITIBIA TECH (SUZHOU) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411048735.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-01
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

OEM manufacturers face high maintenance costs and increased error probabilities due to the need for multiple software versions to meet diverse customer requirements.

Method used

A method for self-adapting device software version numbers by creating a private format summary file and using a customized configuration structure to modify province or OEM codes, allowing the software version to adapt without preparing additional versions.

Benefits of technology

Reduces the number of software versions needed, lowers maintenance costs, and enhances adaptability to meet various customer requirements, minimizing errors and additional software preparation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088433A_ABST
    Figure CN119088433A_ABST
Patent Text Reader

Abstract

The invention relates to an equipment software version number self-adaption method. The method comprises the following steps: creating a version number summary file according to a private format; starting the equipment to read the current version number of the equipment; if the version number is not 0 or 1, the current version number is directly used, and software version number automatic generation logic is not triggered; and if the version number is 0 or 1, triggering software version number automatic generation logic. By adding a private software version number summary file and specific software version number processing logic, the number of maintained software versions is reduced, and the software version number can be self-adaptive; based on a self-defined configuration structure, the software version number can be self-adapted only by modifying a province code or an OEM manufacturer code, and different software versions do not need to be additionally prepared.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to a method for self-adapting device software version number. Background Art

[0002] At present, OEM manufacturers in various regions have their own software version number customization requirements, resulting in more and more software versions being required, high maintenance costs, and the probability of errors increases with the number of versions.

[0003] Therefore, it is necessary to develop a method for adaptively adjusting the device software version number so that one software version can simultaneously meet the software version number requirements of various customers. Summary of the invention

[0004] The purpose of the present invention is to overcome the deficiencies in the prior art and provide a method for self-adaptation of device software version numbers.

[0005] The purpose of the present invention is achieved through the following technical solutions:

[0006] A method for self-adapting a device software version number, characterized by comprising the following steps:

[0007] 1) Create a version number summary file in a private format;

[0008] 2) The device starts and reads the current version number of the device;

[0009] If the version number is not 0 or 1, the current version number is used directly without triggering the automatic generation logic of the software version number;

[0010] If the version number is 0 or 1, the software version number automatic generation logic is triggered.

[0011] Furthermore, in the above-mentioned method for self-adaptation of device software version number, in said step 1), the summary format of the software version number is as follows:

[0012] Section:OEM{oemid}[_B{bindflag}]

[0013] Key:Version{Fwver}_{Eth}_{Voip}

[0014] Oemid refers to the OEM manufacturer code;

[0015] bindflag refers to the province code;

[0016] Fwver refers to 0 or 1;

[0017] Eth refers to the number of LAN ports;

[0018] Voip refers to the number of voice ports.

[0019] Furthermore, in the above-mentioned method for self-adapting the device software version number, in said step 2), the device starts to read the current version number of the device;

[0020] There is a compilation configuration file when the version is compiled. Modify the version information in the configuration file as needed. If not changed, the default is 0 or 1;

[0021] After the version is burned, the device starts and parses the version information of this configuration file to obtain the software version number of the current device.

[0022] Furthermore, in the above-mentioned method for self-adapting the device software version number, in step 2), if the version number is not 0 or 1, the current version number is directly used without triggering the automatic generation logic of the software version number;

[0023] The obtained software version number is compared with 0 and 1. If they are not equal, it means that a special version number is customized and the subsequent software version number automatic generation logic is not triggered.

[0024] Furthermore, in the above-mentioned method for self-adaptation of device software version number, in step 2), if the version number is 0 or 1, the software version number automatic generation logic is triggered;

[0025] Get the province code and OEM manufacturer code of the current device, and get the number of LAN ports and voice ports of the current device;

[0026] Search for version records in the created software version number summary file by province code and OEM code;

[0027] Continue to search for the version number in the search results by version number, number of device LAN ports, and number of device voice ports.

[0028] Compared with the prior art, the present invention has significant advantages and beneficial effects, which are specifically embodied in the following aspects:

[0029] ① The present invention reduces the number of software versions to be maintained by adding a private software version number summary file and a specific software version number processing logic, and the software version number can be adaptive; based on a custom configuration structure, the software version number can be adaptive only by modifying the province code or OEM manufacturer code, and there is no need to prepare different software versions additionally;

[0030] ② When the device needs to be used in many provinces and OEM manufacturers and has special requirements for the software version number, the device has strong adaptability and does not require additional software versions, reducing software version maintenance. At the same time, when a region needs a temporary special customized version number, a version with a special version number can also be temporarily generated, which has strong adaptability;

[0031] ③ You only need to modify the province code or OEM manufacturer code to make the software version number adaptive. There is no need to prepare different software versions, which reduces maintenance costs and the chance of errors.

[0032] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or be understood by practicing the specific embodiments of the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0034] Figure 1 : Schematic diagram of the process of the present invention;

[0035] Figure 2 : Example version number summary file format description;

[0036] Figure 3 : Compile configuration file description of the embodiment;

[0037] Figure 4 : Implementation code flow chart. DETAILED DESCRIPTION

[0038] The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents the selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present invention.

[0039] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, directional terms and order terms are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0040] like Figure 1 As shown, a method for device software version number self-adaptation reduces the number of software versions to be maintained by adding a private software version number summary file and a specific software version number processing logic, and the software version number can be self-adaptive, including the following steps:

[0041] 1) Create a version number summary file in a private format;

[0042] The software version number summary format is as follows:

[0043] Section:OEM{oemid}[_B{bindflag}]

[0044] Key:Version{Fwver}_{Eth}_{Voip}

[0045] Oemid refers to the OEM manufacturer code;

[0046] bindflag refers to the province code;

[0047] Fwver refers to 0 or 1;

[0048] Eth refers to the number of LAN ports;

[0049] Voip refers to the number of voice ports.

[0050] 2) The device starts and reads the current version number of the device;

[0051] There is a compilation configuration file when the version is compiled. Modify the version information in the configuration file as needed. If not changed, the default is 0 or 1;

[0052] After the version is burned, the device starts and parses the version information of this configuration file to obtain the software version number of the current device;

[0053] If the version number is not 0 or 1, the current version number is used directly without triggering the automatic generation logic of the software version number;

[0054] Compare the obtained software version number with 0 and 1. If they are not equal, it means that a special version number is customized and the subsequent software version number automatic generation logic is not triggered.

[0055] If the version number is 0 or 1, the software version number automatic generation logic is triggered;

[0056] Get the province code and OEM manufacturer code of the current device, and get the number of LAN ports and voice ports of the current device;

[0057] Search for version records in the created software version number summary file by province code and OEM code;

[0058] Continue to search for the version number in the search results by version number, number of device LAN ports, and number of device voice ports.

[0059] Example:

[0060] Create a version number summary file in a proprietary format;

[0061] The device starts and reads the current version number of the device;

[0062] If the version number is not 0 or 1, the current version number is used directly without triggering the automatic generation logic of the software version number;

[0063] If the version number is 0 or 1, the software version number automatic generation logic is triggered;

[0064] The version number summary file format is as follows Figure 2 As shown, in the current embodiment, the default version numbers of OEM manufacturer 0 are defined as V1.0.0 and V1.0.1, the default version numbers of OEM manufacturer 1 are defined as v2.0.0 and v2.0.1, and the version numbers of the devices with 8 LAN ports and 8 voice ports of OEM manufacturer 1 are defined as v2.0.0_JS2312 and v2.0.1_JS2312;

[0065] Modify the compilation configuration file as required, such as Figure 3 Therefore, in the current embodiment, the automatic generation of the version number is triggered and the configuration file is compiled as follows: Figure 3 An example of automatic generation of version number requirements;

[0066] After the device burns the compiled version, it starts and parses the version information of the configuration file, thereby obtaining the current device software version number as 0;

[0067] Compare the obtained software version number with 0 and 1. The current version number is 0, which conforms to the automatic generation logic of the version number. According to the code logic, Figure 4 As shown, trigger the logic of automatic version number generation;

[0068] Get the province code and OEM manufacturer code of the current device, and get the number of LAN ports and voice ports of the current device. The province code is 1, the OEM manufacturer code is 1, the number of LAN ports of the device is 8, and the number of voice ports is 8;

[0069] Search the version record in the software version number summary file according to the province code and OEM code, that is, search for the record of OEM1_B1 according to the province code 1 and OEM code 1. The version number summary file has this record. According to the code logic, Figure 4 Therefore, the next search action is triggered;

[0070] The current version number is 0, the number of LAN ports is 8, and the number of voice ports is 8. Continue to match and search in the search record according to Version0_8_8. Finally, a record is found with the version number v2.0.0_JS2312. The device then uses this version number as the final version number.

[0071] In summary, the present invention is based on a customized configuration structure, which enables the software version number to adapt itself only by modifying the province code or OEM manufacturer code, without the need to prepare different software versions additionally.

[0072] When the device needs to be used in many provinces and OEM manufacturers and has special requirements for the software version number, the device has strong adaptability and does not require additional software versions, reducing software version maintenance. At the same time, when a region requires a temporary special customized version number, a version with a special version number can also be temporarily generated, which has strong adaptability.

[0073] You only need to modify the province code or OEM manufacturer code to make the software version number adaptive. There is no need to prepare different software versions, which reduces maintenance costs and the chance of errors.

[0074] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention. It should be noted that similar numbers and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0075] The above is only a specific implementation of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

[0076] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for self-adapting device software version number, characterized by: The following steps are involved: 1) Create a version number summary file in a private format; 2) The device starts and reads the current version number of the device; If the version number is not 0 or 1, the current version number is used directly without triggering the automatic generation logic of the software version number; If the version number is 0 or 1, the software version number automatic generation logic is triggered.

2. A method for self-adapting device software version number according to claim 1, characterized in that: In step 1), the software version number summary format is as follows: Section:OEM{oemid}[_B{bindflag}] Key:Version{Fwver}_{Eth}_{Voip} Oemid refers to the OEM manufacturer code; bindflag refers to the province code; Fwver refers to 0 or 1; Eth refers to the number of LAN ports; Voip refers to the number of voice ports.

3. The method for self-adapting device software version number according to claim 1, characterized in that: In step 2), the device starts to read the current version number of the device; There is a compilation configuration file when the version is compiled. Modify the version information in the configuration file as needed. If not changed, the default is 0 or 1; After the version is burned, the device starts and parses the version information of this configuration file to obtain the software version number of the current device.

4. The method for self-adapting device software version number according to claim 1, characterized in that: Step 2), if the version number is not 0 or 1, the current version number is used directly without triggering the automatic generation logic of the software version number; The obtained software version number is compared with 0 and 1. If they are not equal, it means that a special version number is customized and the subsequent software version number automatic generation logic is not triggered.

5. The method for self-adapting device software version number according to claim 1, characterized in that: Step 2), if the version number is 0 or 1, the software version number automatic generation logic is triggered; Get the province code and OEM manufacturer code of the current device, and get the number of LAN ports and voice ports of the current device; Search for version records in the created software version number summary file by province code and OEM code; Continue to search for the version number in the search results by version number, number of device LAN ports, and number of device voice ports.