CN116737208A - Software maintenance upgrade management method and device and electronic equipment - Google Patents
Software maintenance upgrade management method and device and electronic equipment Download PDFInfo
- Publication number
- CN116737208A CN116737208A CN202311030320.7A CN202311030320A CN116737208A CN 116737208 A CN116737208 A CN 116737208A CN 202311030320 A CN202311030320 A CN 202311030320A CN 116737208 A CN116737208 A CN 116737208A
- Authority
- CN
- China
- Prior art keywords
- software
- coupling
- tie
- product
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims description 33
- 230000008878 coupling Effects 0.000 claims abstract description 271
- 238000010168 coupling process Methods 0.000 claims abstract description 249
- 238000005859 coupling reaction Methods 0.000 claims abstract description 249
- 238000000034 method Methods 0.000 claims abstract description 39
- 210000003041 ligament Anatomy 0.000 claims description 51
- 238000003860 storage Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 claims description 8
- 238000001514 detection method Methods 0.000 claims description 5
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000008859 change Effects 0.000 abstract description 11
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000005516 engineering process Methods 0.000 abstract description 4
- 239000000047 product Substances 0.000 description 141
- 238000004146 energy storage Methods 0.000 description 26
- 230000006870 function Effects 0.000 description 22
- 238000010586 diagram Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 8
- 230000003993 interaction Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 4
- 230000008439 repair process Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000033228 biological regulation Effects 0.000 description 2
- 239000003086 colorant Substances 0.000 description 2
- 238000011217 control strategy Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000004397 blinking Effects 0.000 description 1
- 210000004556 brain Anatomy 0.000 description 1
- 239000006227 byproduct Substances 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000005286 illumination Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000010248 power generation Methods 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 0.000 description 1
- 238000003756 stirring Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000008719 thickening Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present application relates to the field of software upgrading technologies of databases, and in particular, to a method and an apparatus for software maintenance, upgrading and management, and an electronic device. Before maintaining and upgrading the user product, the method searches the upgrading relation and the coupling relation between the software according to the upgrading tie and the coupling tie, selects the couplable software for upgrading, and controls the corresponding change of the product version when the software version is changed. Therefore, the upgrade products and upgrade software corresponding to the user demands can be conveniently searched in the database, a proper upgrade scheme is provided for the user at any time, the product use experience of the user is greatly improved, meanwhile, the product maintenance cost of a manufacturer is reduced, and the after-sales service efficiency is improved.
Description
Technical Field
The application relates to the technical field of software development of databases, in particular to a method and a device for software maintenance, upgrading and management and electronic equipment.
Background
The iterative upgrade of software is the stage that each software must pass since release. Whether it be a function change, performance optimization, BUG fix, or other requirement that a software change be made, will cause the software to perform an upgraded version of the action.
For manufacturers, with the update iteration of the technology, some software will be updated accordingly, and the same type of product (or system) will be updated accordingly. Once the product is sold, however, its product type and the software therein is already in a set, and typically for some relatively expensive products, such as household energy storage power supplies, the user wishes to be able to functionally upgrade the purchased product, either by specifying a function or by upgrading the entire product (such as a yearly upgrade service). Based on this, there is an urgent need for software/product upgrades to already sold products, particularly some of the most original versions; in addition, some function (realized by some software) is damaged for other reasons, and it is also necessary to upgrade and repair the function.
Disclosure of Invention
The embodiment of the application mainly solves the technical problem that the current manufacturer hardly meets the product upgrading requirement of the user.
In order to solve the technical problems, one technical scheme adopted by the embodiment of the application is as follows: the software maintenance upgrade management method comprises the following steps: establishing a related tie database of product software, wherein the related tie database comprises related ties with two dimensions, one is aimed at coupling ties among different software which are coupled with each other in each product, and the other is aimed at upgrading ties among different products, which are identical in software but different in version; detecting whether specific software in a specific product is updated currently; if not, upgrading the coupling tie according to the specific product; if yes, upgrading the coupling tie according to the specific software.
Optionally, the establishing the association tie database of the product software includes: acquiring at least one product and software corresponding to the product, wherein the product comprises product information consisting of a product type and a product version, and the software comprises software information consisting of a software type and a software version; establishing a software node according to the software information, and associating the software node according to the product information to obtain a coupling tie corresponding to each product; according to the software information, associating the software nodes of the same software type and different software versions to obtain upgrading bands corresponding to each software; the coupling ligament and the upgrade ligament together form a database of a mesh data structure.
Optionally, the upgrading the coupling tie according to the specific product includes: determining a coupling ligament to be upgraded as a first coupling ligament; searching the same type of coupling tie of the first coupling tie in the associated tie database; selecting a coupling tie of a higher order than the first coupling tie of the same type as a target coupling tie; and upgrading the first coupling tie according to the target coupling tie.
Optionally, the method further comprises: highlighting the same type of coupling ligament or the target coupling ligament; and/or displaying the same type of coupling ligament or the target coupling ligament and hiding non-target coupling ligaments and non-same type of coupling ligaments.
Optionally, the selecting, as the target coupling tie, a coupling tie of a higher order than the first coupling tie in the coupling ties of the same type includes: among the same type of coupling ties, a lowest-order coupling tie of a higher order than the first coupling tie is selected as the target coupling tie.
Optionally, the selecting, as the target coupling tie, a coupling tie of a higher order than the first coupling tie in the coupling ties of the same type includes: among the coupling ties of the same type, the coupling tie of the highest order is selected as the target coupling tie.
Optionally, the upgrading the coupling tie according to the specific software includes: determining a coupling tie to be upgraded as a first coupling tie, determining software to be upgraded as first version target software, and determining other software except the first version target software in the first coupling tie as first coupling software; searching the same type of coupling tie of the first coupling tie in the associated tie database; selecting a target software of a higher order than the first version target software in the same type of coupling bands, and taking the coupling bands of the higher order than the first coupling band as target coupling bands; and upgrading the first coupling tie according to the target coupling tie.
Optionally, if there is no higher-order coupling tie in the same type of coupling tie than the first coupling tie, the method further includes: initiating a development upgrade request, the development upgrade comprising: searching whether heterogeneous coupling ties exist in the associated tie database, wherein the heterogeneous coupling ties comprise higher-order target software than the first version target software; if higher-order target software exists, determining the highest-order target software in the higher-order target software as second-version target software, and determining a coupling tie where the second-version target software is located as the second coupling tie, wherein other software in the second coupling tie except the second-version target software is second coupling software; upgrading the first version of target software and the second version of target software to obtain new version of target software, wherein the new version of target software can simultaneously couple the first coupling software and the second coupling software; a new coupling ligament is formed and the upgrade ligament is updated.
Optionally, if there is no heterogeneous coupling tie containing higher-order target software than the first version of target software, the method further comprises: upgrading the new version of the first version of target software to obtain the new version of target software, wherein the new version of target software can simultaneously couple the first coupling software and the second coupling software; a new coupling ligament is formed and the upgrade ligament is updated.
In order to solve the technical problems, another technical scheme adopted by the embodiment of the application is as follows: there is provided a software maintenance upgrade management apparatus including: the database module is used for establishing a related tie database of product software, and the related tie database comprises related ties with two dimensions, namely a coupling tie between different software which are coupled with each other in each product, and an upgrading tie between the same software and different versions for different products; the upgrade detection module is used for detecting whether specific software in specific products is upgraded currently; the first upgrading module is used for upgrading the coupling tie according to the specific product when upgrading the specific product; and the second upgrading module is used for upgrading the coupling tie according to the specific software when upgrading the specific software in the specific product.
In order to solve the above technical problems, another technical solution adopted by the embodiment of the present application is: there is provided an electronic device including: at least one processor; a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software maintenance upgrade management method described above.
In order to solve the above technical problems, another technical solution adopted by the embodiment of the present application is: there is provided a non-transitory computer-readable storage medium storing computer-executable instructions for causing a computer to perform the software maintenance upgrade management method described above.
Different from the situation of related technology, the embodiment of the application provides a software maintenance and upgrading method, a device and electronic equipment. Before maintaining and upgrading the user product, the method searches the upgrading relation and the coupling relation between the software according to the upgrading tie and the coupling tie, selects the couplable software for upgrading, and controls the corresponding change of the product version when the software version is changed. Therefore, the upgrade products and upgrade software corresponding to the user demands can be conveniently searched in the database, a proper upgrade scheme is provided for the user at any time, the product use experience of the user is greatly improved, meanwhile, the product maintenance cost of a manufacturer is reduced, and the after-sales service efficiency is improved.
Drawings
One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to scale, unless expressly stated otherwise.
FIG. 1 is a schematic flow chart of a software maintenance upgrade management method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a method for creating an association tie database according to an embodiment of the present application;
FIG. 3 is a frame structure diagram of an energy storage power supply according to an embodiment of the present application;
FIGS. 4 a-4 e are diagrams illustrating two product software upgrades and associated tie database creation processes according to embodiments of the present application;
FIG. 5 is a schematic diagram of a method for upgrading a coupling ligament according to a particular product according to an embodiment of the present application;
FIG. 6 is an example of the corresponding associated tie database of FIG. 5;
FIG. 7 is a schematic diagram of a method for upgrading a coupling ligament according to specific software according to an embodiment of the present application;
FIG. 8 is an example of the corresponding associated tie database of FIG. 7;
FIG. 9 is a schematic diagram of a method for developing upgrades provided by an embodiment of the present application;
FIGS. 10a and 10b are examples of the corresponding associated tie database of FIG. 9 before and after an upgrade;
FIG. 11 is a schematic diagram of another method for developing upgrades provided by an embodiment of the present application;
FIG. 12 is a schematic diagram of a software maintenance upgrade management apparatus according to an embodiment of the present application;
fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application. It should be noted that, if not in conflict, the features of the embodiments of the present application may be combined with each other, which are all within the protection scope of the present application. In addition, while the division of functional blocks is performed in a device diagram and the logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in a device diagram or the sequence in a flowchart.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items.
Referring to fig. 1, an embodiment of the present application provides a software maintenance upgrade management method, by creating and maintaining a mesh data structure of software, before upgrading software or a product, according to an upgrade tie and a coupling tie, searching an upgrade relationship and a coupling relationship between software, and then selecting couplable software for upgrading, and at the same time, controlling a change corresponding to a product version when the software version is changed, the method includes:
s11, establishing a related tie database of product software, wherein the related tie database comprises related ties with two dimensions, namely a coupling tie between different software which are coupled with each other in each product, and an upgrading tie between the same software and different versions for different products.
Specifically, referring to fig. 2, the creating the association tie database of the product software includes:
s111, acquiring at least one product and software corresponding to the product. The product includes product information consisting of a product type and a product version, and the software includes software information consisting of a software type and a software version.
To make the structure of the database clear, the product and software can be divided into two hierarchical levels, such as: assume that (A.V1) is taken as a product code, wherein A represents a product model, and V1 represents a product version; let (a.01) be the software code, where a represents the software type and 01 represents the software version. In other embodiments, the product and software may be divided into multiple onion-like levels (3 or more), such as: assume that (A.100.V1) is taken as a product code, wherein A represents a product category, 100 represents a product model, and V1 represents a product version; let (a.1002.01) be the software code, where a represents the software category, 1002 represents the software model, and 01 represents the software version. Regardless of the hierarchy, the minimum hierarchy of software represents the minimum unit of software promotion. Such as: only the software versions in the plurality of software are different, and the software belongs to the same type of software with different versions; assuming that the software model or software type of the two pieces of software are different, the two pieces of software belong to different pieces of software. Whatever the hierarchy, the minimum hierarchy is different, it is a different product.
S112, establishing a software node according to the software information, and associating the software node according to the product information so as to obtain a coupling tie corresponding to each product.
Each software is defined as a node, and each node has an own unique SN unique identifier, wherein the SN unique identifier is an identifier mode with a version number, is not repeated, and can uniquely mark one software. Taking ARM (1001.01) as an example, ARM is a software category, 1001 is a software model, and 01 is a software version.
Each product contains a plurality of pieces of mutually coupled software, and the mutually coupled pieces of mutually coupled software are connected in a relation to form the product. A coupling tie is actually a product.
Taking a household energy storage power supply as an example, the household energy storage power supply can be classified into: miniature (portable/outdoor) energy storage power supplies, household energy storage power supplies and commercial energy storage power supplies. Each energy storage power supply has different capacity, power and functions, but has similar structure/module, and as shown in fig. 3, the energy storage power supply mainly comprises an energy storage battery, an inversion unit (PCS), a main control unit, a communication unit and a man-machine interaction unit; the main control unit is respectively connected with the energy storage battery, the inversion unit, the communication unit and the man-machine interaction unit, and the inversion unit is connected with the energy storage battery; each part/unit has a separate chip for executing the associated software control algorithm and for implementing the respective function.
The energy storage battery includes a battery pack and a Battery Management System (BMS); the battery pack is responsible for energy storage; the battery management system is commonly called a battery manager and is responsible for the functions of battery detection, evaluation, protection, equalization, communication and the like, and the main algorithms include an SOC/SOH/SOP algorithm, an electric quantity equalization algorithm, an overvoltage and undervoltage protection algorithm and the like.
An inversion unit (PCS) controls the charging and discharging processes of the energy storage battery, realizes electric energy conversion and circuit control, converts alternating current of a power grid into direct current on one hand, prepares for charging the energy storage battery, and has a rectification function; on the other hand, the direct current generated by the photovoltaic power generation or energy storage battery is converted into alternating current, and the alternating current has an inversion function, and related functions are realized by a DSP chip, such as control and algorithm related to grid-connected feed, inversion output control strategy, algorithm and the like.
The main control unit adopts an ARM chip, and comprises an Energy Management System (EMS), wherein the EMS is a brain of a decision center of the whole energy storage power supply, is responsible for data acquisition and analysis, network monitoring and optimal scheduling, gives out a scheduling strategy of multi-scale coordinated control, automatically maintains the stable voltage frequency of the micro-grid, and realizes the effective utilization of renewable energy sources and the safe and economical energy storage power supply through reasonable energy management. The core control strategy comprises a frequency regulation strategy, a voltage regulation strategy, a peak clipping and valley filling strategy, a power grid stirring stabilization strategy, a target load real-time tracking strategy, a planned energy storage processing strategy and the like.
The communication unit adopts an IOT chip to realize the functions related to external communication of the energy storage power supply, such as control, data state display and OTA (over the air technology) upgrading of equipment through Bluetooth, wifi, 4G and the like.
The man-machine interaction unit comprises a man-machine interaction interface and an HMI chip, wherein the man-machine interaction interface is usually a touch display screen, and a user controls state information of equipment operation and controls the equipment and the like through the man-machine interaction unit.
Taking an associated tie database formed by a product as an example, as shown in fig. 4a, for example, the software included in the first version a_v1 of the energy storage power supply a includes ARM1001.01, DSP2001.01, BMS3001.01, HMI4001.01, IOT5001.01, that is, the coupling tie corresponding to the product version a_v1.
S113, associating software nodes of the same software type and different software versions according to the software information so as to obtain upgrading bands corresponding to each piece of software.
And acquiring all software versions corresponding to the software nodes, and associating all software versions to obtain upgrading links corresponding to the software nodes. The upgrade tie is a connection of different versions of the same type of software, i.e., upgrade paths of the same type of software.
Assuming that the ARM engineer initiates an upgrade, and upgrades ARM at the time of product upgrade, the engineer retrieves A_V1 in the mesh data structure, and the engineer determines that A_V1 is upgraded to A_V2, then the upgraded associated ligament database is shown in FIG. 4b, and the second version A_V2 of product A contains software including ARM1001.02, DSP2001.01, BMS3001.01, HMI4001.01 and IOT5001.01, namely the coupling ligament corresponding to the product version A_V2, wherein an upgrade ligament is formed between ARM1001.01 and ARM 1001.02.
The upgrade scenario from fig. 4a to fig. 4b is typically an upgrade initiated for a certain software occurrence due to a BUG repair, a function change, a function addition, etc. Taking an energy storage power supply as an example, one practical application scenario is as follows: after the developed A_V1 product is connected with a solar photovoltaic panel, whether a line of the solar photovoltaic panel is in an on state or not needs to be confirmed through a human-computer interaction interface (touch display screen), and the A_V1 product needs a user to be close to the touch display screen of equipment and shield sunlight to see the display state on the screen clearly under strong outdoor sunlight, so that a development engineer needs to update the version of the product after receiving market feedback, ARM software is updated to ARM1001.02 version, and meanwhile, the product is updated to A_V2 from A_V1, and the following steps are realized: and (3) utilizing the illumination LED lamp on the product A to flash twice after the charging circuit is connected.
Based on the above example, assuming that the BMS initiates the upgrade simultaneously with the DSP engineers, the engineers retrieve A_V1, A_V2 in the mesh data structure, both engineers determine to upgrade A_V2 to A_V3, the upgraded associated ligament database is shown in FIG. 4c, the third version A_V3 of product A contains software ARM1001.02, DSP2001.02, BMS3001.02, HMI4001.01, IOT5001.01, i.e., the coupling ligament corresponding to the product version A_V3. An upgrade tie is also formed between DSP2001.01 and DSP2001.02, and between BMS3001.01 and BMS 3001.02.
Similarly, the upgrade scenario from fig. 4b to fig. 4c generally initiates an upgrade for multiple software simultaneous BUG repair, function change, function addition, and the like. Taking an energy storage power supply as an example, one practical application scenario is as follows: after the developed A_V2 product is connected with the grid, the user power grid is suddenly short-circuited after the market feeds back the product, and the problem that the SOC transient jump of the BMS is recovered is caused by probability, so that two software of the DSP2001.01 and the BMS3001.01 are required to be upgraded to the versions of the DSP2001.02 and the BMS3001.02, and meanwhile, the product is upgraded from the A_V2 to the A_V3.
S114, associating the coupling tie with the upgrading tie to form a database of a mesh data structure.
On the basis of the above example, assuming that there is a new project requirement at this time, a new product is required to be made based on the product a, named as the product B, a new ARM (1002.01) and a new HMI (4002.01) need to be created, and after the product B is created by using the DSP, BMS and IOT of the original product a, a new association tie database is shown in fig. 4d, software corresponding to the first version b_v1 of the product B includes HMI4002.01, ARM1002.01, DSP2001.02, BMS3001.02 and IOT5001.01, that is, coupling ties corresponding to the version b_v1 of the product.
The upgrade scenario from fig. 4c to fig. 4d is generally another requirement situation of an existing product to meet the market, and a product corresponding to the market requirement is derived from the product. Taking an energy storage power supply as an example, compared with a product A, the product B is modified by an ARM hardware peripheral circuit on the product B, a new algorithm is introduced, and a set of brand new UI (User Interface) is used on an HMI screen of the product B; the DSP, BMS, IOT of product B is consistent with the software used by product a, but ARM and HMI are new software developed independently.
Based on the above example, assuming that the IOT engineer upgrades the IOT, the engineer retrieves products a_v1, a_v2, a_v3 and b_v1 in the mesh data structure, the engineer decides to upgrade a_v3 and b_v1, and the upgraded association tie database is shown in fig. 4e, software corresponding to the second version b_v2 of the product B includes HMI4002.01, ARM1002.01, DSP2001.02, BMS3001.02 and IOT5001.02, that is, coupling ties corresponding to the product version b_v2; the software corresponding to the fourth version a_v4 of the product a includes ARM1001.02, DSP2001.02, BMS3001.02, HMI4001.01, IOT5001.02, i.e., a coupling tie corresponding to the product version a_v4, wherein an upgrade tie is also formed between IOT5001.01 and IOT 5001.02.
In the upgrading from fig. 4d to fig. 4e, taking the energy storage power supply as an example, the communication between the IOT and the server of the old product adopts an unencrypted mode, and is easy to attack by hackers to be controlled remotely, so maintenance and upgrading are required for IOT software, the communication mode is changed into secure encrypted communication, IOT5001.01 is upgraded to IOT5001.02, and products a and B are also upgraded to versions a_v4 and b_v2 in a following way.
It should be noted that the association tie database includes association ties of two dimensions, namely a coupling tie and an upgrade tie, one of which is a product for the coupling ties between different software that are coupled to each other in each product; and the second is to upgrade the tie between different versions of the same software, upgrade the tie to different products.
When each software type in the plurality of coupling bands is the same and only the version of the software is different, the plurality of coupling bands are of the same type (same type of product), e.g., products a_v1 and a_v2 in fig. 4b belong to the same type of product; when one of the software types is different in the plurality of coupling bands, the plurality of coupling bands are of different types (different types of products), for example, products a_v1 and b_v1 in fig. 4d belong to different types of products.
The database as above may be stored in a remote server or a local server for access, download and update.
S12, detecting whether maintenance and upgrading are carried out on specific software in specific products currently. Whether to upgrade a particular piece of software in a particular product, i.e., whether to upgrade a particular piece of software for a particular coupling tie in the associated tie database.
It will be appreciated that for a product purchased by a user, it is assumed that the user wishes to be able to functionally upgrade the purchased product, which may be a function specified, or may be an upgrade of the entire product; while a certain function is typically implemented by a certain software, in this embodiment the product is associated with a coupling tie in the database of associated ties, the software is associated with a certain software of the coupling tie in the database of associated ties.
If not, executing step S13, and upgrading the coupling tie according to the specific product. Specifically, referring to fig. 5, the upgrading the coupling ligament according to the specific product includes:
s131, determining the coupling tie to be upgraded as a first coupling tie. In this case, the software may be directly used as an access point, and the coupling link to be upgraded is a product that the user wants to upgrade, and it can be understood that the software to be upgraded may be one or multiple.
S132, searching the same type of coupling tie of the first coupling tie in the associated tie database. When each software type in a certain coupling tie is the same as the first coupling tie and only the version of the software is different, the coupling tie is the same type as the first coupling tie.
S133, selecting a coupling ligament of a higher order than the first coupling ligament in the coupling ligaments of the same type as a target coupling ligament.
Wherein, because there may be multiple coupling bands and multiple upgrading bands in the database, in order to facilitate the engineer to confirm the target band, after searching the coupling bands of the same type or the target coupling band, the method may further include:
a. highlighting the same type of coupling ligament or the target coupling ligament. For example in different colours, blinking, bolding etc.
And/or the number of the groups of groups,
b. displaying the same type of coupling ligament or the target coupling ligament, and hiding the non-target coupling ligament and the non-same type of coupling ligament.
S134, upgrading the first coupling tie according to the target coupling tie.
Assuming that a user applies to a manufacturer to upgrade a function of a product, please refer to fig. 6, taking maintenance upgrade of a coupling ligament a.v1 (product a.v1) as an example, a.v1 is first determined to be a first coupling ligament. The same type of coupling tie as the first coupling tie is looked up in the database, as shown in the figure, and includes a.v2, a.v3 and a.v4. As can be seen from fig. 6, a.v2, a.v3 and a.v4 each satisfy this condition, so that one of the coupling bands may be selected as the target coupling band, for example, a.v3, and then the customer's product may be upgraded according to a.v3, for example, an update package of a.v3 may be sent to the customer's product, so that the customer may upgrade a.v1 to a.v3 via the update package.
In some embodiments, the target coupling tie may be selected by: among the same type of coupling ties, a lowest-order coupling tie of a higher order than the first coupling tie is selected as the target coupling tie. For the type of product to be updated, this approach can be updated with minimal software to meet customer needs. In some scenarios, for example, when different software contained in a product cannot be upgraded in parallel, or when a version of the software is upgraded, it takes a long time, the selection manner can update the least software as possible under the condition of meeting the needs of clients, so as to reduce the update consumption of users.
Taking fig. 6 as an example, the selection of the a.v2 as the target coupling link according to the above selection manner, when the user updates the a.v1 to the a.v2 through the update package (or other update manners), the update amount of the internal system of the product only updates the software a.1001.01 to a.1001.02, and the coupling settings of the a.1001.02 and other related software can be directly obtained through the database, which is convenient and fast.
In some embodiments, the target coupling tie may also be selected by: among the coupling ties of the same type, the coupling tie of the highest order is selected as the target coupling tie. Taking fig. 6 as an example, according to the above selection manner, the a.v4 is selected as the target coupling link, and when the user updates the a.v1 to the a.v4 by using the update package (or other update manners), the product internal system upgrades the latest version of each software in the database.
If yes, step S14 is executed to upgrade the coupling tie according to the specific software. Specifically, as shown in fig. 7, the upgrading the coupling link according to the specific software includes:
s141, determining a coupling tie to be upgraded as a first coupling tie, determining software to be upgraded as first version target software, and determining other software except the first version target software in the first coupling tie as first coupling software.
S142, searching the same type of coupling tie of the first coupling tie in the associated tie database. Wherein each software type of the same type of coupling tie and the first coupling tie is the same and only the version of the software is different.
S143, selecting a target software of a higher order than the target software of the first version in the coupling bands of the same type, and taking the coupling bands of the higher order than the first coupling bands as target coupling bands.
In order to facilitate the engineer to confirm the first version of the target software, after the first version of the target software is found, the first version of the target software can be highlighted, for example, the first version of the target software is highlighted in different colors, flickering, thickening and the like; or hiding the original association tie database, and directly displaying the first version of target software and the related coupling ties.
S144, upgrading the first coupling tie according to the target coupling tie.
Referring to fig. 8, assume that in a scenario, a customer specifies that an upgrade with a function of a certain aspect is required, and the function is implemented by software d.4001.01, as shown in fig. 8, upgrade d.4001.01 in a coupling ligament a.v1 in the drawing, determine a.v1 as a first coupling ligament, and determine d.4001.01 as target software of a first version.
Searching the same type of coupling tie of the first coupling tie A.V1 in the association tie database, wherein the coupling tie comprises A.V2, A.V3, A.V4, A.V5 and A.V6, selecting the coupling tie of the same type to comprise higher-order target software d.4001.02 than the first version target software d.4001.01, taking the coupling tie of the higher-order than the first coupling tie A.V1 as the target coupling tie, selecting A.V5 or A.V6 as the target coupling tie in the figure, and upgrading the first coupling tie A.V1 according to the target coupling tie A.V5 or A.V6. For example, the user is provided with an update package for a.v5 or a.v6 so that the user can upgrade the product a.v1 to a.v5 or a.v6 through the update package.
In some embodiments, if none of the same type of coupling ties has a higher order coupling tie than the first coupling tie, the method further comprises: initiate a development upgrade request. Referring to fig. 9, the development upgrade includes:
S145, searching whether the heterogeneous coupling tie contains higher-order target software than the first version target software in the associated tie database.
If there is higher-order target software, step S1452 is executed to determine the highest-order target software in the higher-order target software as a second version target software, and determine the coupling tie where the second version target software is located as the second coupling tie, where the other software in the second coupling tie except the second version target software is the second coupling software.
And S146, upgrading the first version of target software and the second version of target software to obtain new version of target software, wherein the new version of target software can simultaneously couple the first coupling software and the second coupling software.
S147, forming a new coupling tie and updating the upgrade tie.
Referring to fig. 10a and 10b, it is assumed that the software m.3001.02 in the coupling tie j.v2 of fig. 10a is updated for maintenance. For product J.V2, it is the highest order of the same type of coupling ties, thus initiating a development upgrade request.
The software to be upgraded in the first coupling tie J.V2 is determined to be the first version target software (m.3001.02), and other software (j.1001.01) except the target software (m.3001.02) in the first coupling tie J.V2 and (k.2001.01) are determined to be the first coupling software.
Searching a database for whether a heterogeneous coupling tie contains higher-order target software than the first version. As shown in fig. 10a, the heterogeneous coupling bands k.v1 and k.v2 are found in the database to include higher order target software (m.3001.03) and (m.3001.04) than the first version of target software, so that the highest version of target software (m.3001.04) is selected as the second version of target software, and the heterogeneous coupling band k.v2 where the highest version of target software is located is selected as the second coupling band, where (k.2001.01) and (n.4001.01) are the second coupling software.
The first version of the target software (m.3001.02) and the second version of the target software (m.3001.04) are updated in new versions, so that the new version of the target software can simultaneously couple the first coupling software (j.1001.01, k.2001.01) and the second coupling software (k.2001.01, n.4001.01) to form new coupling ties J.V3 and K.V3, and then the upgrading ties (m.3001.01) → (m.3001.02) → (m.3001.03) → (m.3001.04) → (m.3001.05), and the updated database is shown in fig. 10 b. And upgrading the first coupling tie J.V2 according to the software m.3001.05 in the new coupling tie J.V3, and providing a new version of the software m.3001.05 for a user.
In some embodiments, as shown in fig. 11, if there is no higher-order target software, step S1453 is directly performed to upgrade the first version of target software to obtain a new version of target software, where the new version of target software can simultaneously couple the first coupling software and the second coupling software. Based on the obtained new version of the target software, continuing to execute step S147, forming a new coupling tie and updating the upgrading tie; and provides the user with a relevant update package of the new version of the target software.
According to the software maintenance upgrading management method provided by the embodiment of the application, the mesh data structure of the software is established and maintained, before upgrading of the software or a product, according to the upgrading tie and the coupling tie, the upgrading relation and the coupling relation between the software are searched, the couplable software is selected for upgrading, and meanwhile, the corresponding change of the product version is controlled during the change of the software version. Therefore, the upgrade of the software version can be easily maintained, the maintenance cost of engineers on the software version management is greatly reduced, and the efficiency of the software version management is improved. In addition, based on the established association tie database, the existing software can easily search the compatibility relation in the product, stability guarantee is provided for production and assembly of the product and after-sales maintenance of the product, the risk that the product cannot be normally used or even damaged when the internal software of the product is incompatible is avoided, and meanwhile traceability of version iteration and software version iteration is improved.
According to the software maintenance upgrading method provided by the embodiment of the application, the mesh data structure of the software is established and maintained, before maintenance and upgrading are carried out on a user product, according to the upgrading tie and the coupling tie, the upgrading relation and the coupling relation between the software are searched first, then the couplable software is selected for upgrading, and meanwhile, the corresponding change of the product version is controlled during the change of the software version. Therefore, the upgrade products and upgrade software corresponding to the user demands can be conveniently searched in the database, a proper upgrade scheme is provided for the user at any time, the product use experience of the user is greatly improved, meanwhile, the product maintenance cost of a manufacturer is reduced, and the after-sales service efficiency is improved.
An embodiment of the present application provides a software maintenance upgrade management apparatus, as shown in fig. 12, the software maintenance upgrade management apparatus 200 includes: a database module 21, an upgrade detection module 22, a first upgrade module 23, and a second upgrade module 24.
In particular, the database module 21 may build an associated tie database of product software, the associated tie database including coupling ties. The upgrade detection module 22 may detect whether a particular software upgrade is currently performed on a particular product. The first upgrade module 23 may upgrade the coupling tie according to a specific product when the specific product is upgraded. The second upgrade module 24 may upgrade the coupling strap according to particular software in a particular product when the particular software is upgraded.
It should be noted that, the software maintenance upgrade management device may execute the software maintenance upgrade management method provided by the embodiment of the present application, and has the corresponding functional module and beneficial effects of the execution method. Technical details not described in detail in the embodiment of the software maintenance upgrade management apparatus may be referred to the software maintenance upgrade management apparatus provided in the embodiment of the present application.
Referring to fig. 13, fig. 13 is a schematic structural diagram of an electronic device 300 according to an embodiment of the present application, where the electronic device 300 may be used to execute the software maintenance upgrade management method described above. The electronic device 300 includes:
at least one processor 31, and a memory 32 communicatively coupled to the at least one processor 31, one processor 31 being illustrated in fig. 13.
The processor 31 and the memory 32 may be connected by a bus or otherwise, which is illustrated in fig. 13 as a bus connection.
The memory 32 is used as a non-volatile computer readable storage medium for storing non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions/modules corresponding to the software maintenance upgrade management method in the embodiment of the present application. The processor 31 executes various functional applications of the server and data processing by running nonvolatile software programs, instructions and modules stored in the memory 32, i.e., implements the above-described method embodiment software maintenance upgrade management method.
The memory 32 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created according to the use of the firmware system, and the like. In addition, memory 32 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 32 may optionally include memory located remotely from processor 31, which may be connected to the firmware system via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The one or more modules are stored in the memory 32 and when executed by the one or more processors 31 perform the software maintenance upgrade management method of any of the method embodiments described above, e.g., perform the method steps described above and implement the functions of the modules in fig. 12.
The product can execute the software maintenance upgrade management method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. Technical details which are not described in detail in the present embodiment can be referred to the software maintenance upgrade management method provided in the embodiment of the present application.
From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus a general purpose hardware platform, or may be implemented by hardware. Those skilled in the art will appreciate that all or part of the processes implementing the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and where the program may include processes implementing the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; the technical features of the above embodiments or in the different embodiments may also be combined within the idea of the application, the steps may be implemented in any order, and there are many other variations of the different aspects of the application as described above, which are not provided in detail for the sake of brevity; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.
Claims (12)
1. A software maintenance upgrade management method, comprising:
establishing a related tie database of product software, wherein the related tie database comprises related ties with two dimensions, one is aimed at coupling ties among different software which are coupled with each other in each product, and the other is aimed at upgrading ties among different products, which are identical in software but different in version;
detecting whether specific software in a specific product is updated currently;
if not, upgrading the coupling tie according to the specific product;
if yes, upgrading the coupling tie according to the specific software.
2. The method of claim 1, wherein the creating an associated tie database of product software comprises:
acquiring at least one product and software corresponding to the product, wherein the product comprises product information consisting of a product type and a product version, and the software comprises software information consisting of a software type and a software version;
establishing a software node according to the software information, and associating the software node according to the product information to obtain a coupling tie corresponding to each product;
According to the software information, associating the software nodes of the same software type and different software versions to obtain upgrading bands corresponding to each software;
the coupling ligament and the upgrade ligament together form a database of a mesh data structure.
3. The method of claim 1 or 2, wherein the upgrading the coupling ligament according to the particular product comprises:
determining a coupling ligament to be upgraded as a first coupling ligament;
searching the same type of coupling tie of the first coupling tie in the associated tie database;
selecting a coupling tie of a higher order than the first coupling tie of the same type as a target coupling tie;
and upgrading the first coupling tie according to the target coupling tie.
4. A method according to claim 3, characterized in that the method further comprises:
highlighting the same type of coupling ligament or the target coupling ligament; and/or the number of the groups of groups,
displaying the same type of coupling ligament or the target coupling ligament, and hiding the non-target coupling ligament and the non-same type of coupling ligament.
5. A method according to claim 3, wherein said selecting as a target coupling tie a higher order coupling tie of said same type of coupling tie than said first coupling tie comprises:
Among the same type of coupling ties, a lowest-order coupling tie of a higher order than the first coupling tie is selected as the target coupling tie.
6. A method according to claim 3, wherein said selecting as a target coupling tie a higher order coupling tie of said same type of coupling tie than said first coupling tie comprises:
among the coupling ties of the same type, the coupling tie of the highest order is selected as the target coupling tie.
7. The method of any of claims 1-2, wherein the upgrading the coupling tie according to the particular software comprises:
determining a coupling tie to be upgraded as a first coupling tie, determining software to be upgraded as first version target software, and determining other software except the first version target software in the first coupling tie as first coupling software;
searching the same type of coupling tie of the first coupling tie in the associated tie database;
selecting a target software of a higher order than the first version target software in the same type of coupling bands, and taking the coupling bands of the higher order than the first coupling band as target coupling bands;
And upgrading the first coupling tie according to the target coupling tie.
8. The method of claim 7, wherein if none of the same type of coupling ties has a higher order coupling tie than the first coupling tie, the method further comprises: initiating a development upgrade request, the development upgrade comprising:
searching whether heterogeneous coupling ties exist in the associated tie database, wherein the heterogeneous coupling ties comprise higher-order target software than the first version target software;
if higher-order target software exists, determining the highest-order target software in the higher-order target software as second-version target software, and determining a coupling tie where the second-version target software is located as the second coupling tie, wherein other software in the second coupling tie except the second-version target software is second coupling software;
upgrading the first version of target software and the second version of target software to obtain new version of target software, wherein the new version of target software can simultaneously couple the first coupling software and the second coupling software;
a new coupling ligament is formed and the upgrade ligament is updated.
9. The method of claim 8, wherein if higher-order target software is not present, the method further comprises:
upgrading the new version of the first version of target software to obtain the new version of target software, wherein the new version of target software can simultaneously couple the first coupling software and the second coupling software;
a new coupling ligament is formed and the upgrade ligament is updated.
10. A software maintenance upgrade management apparatus, comprising:
the database module is used for establishing a related tie database of product software, and the related tie database comprises related ties with two dimensions, namely a coupling tie between different software which are coupled with each other in each product, and an upgrading tie between the same software and different versions for different products;
the upgrade detection module is used for detecting whether specific software in specific products is upgraded currently;
the first upgrading module is used for upgrading the coupling tie according to the specific product when upgrading the specific product;
and the second upgrading module is used for upgrading the coupling tie according to the specific software when upgrading the specific software in the specific product.
11. An electronic device, comprising:
at least one processor;
a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software maintenance upgrade management method of any one of claims 1 to 9.
12. A non-transitory computer-readable storage medium storing computer-executable instructions for causing a computer to perform the software maintenance upgrade management method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311030320.7A CN116737208B (en) | 2023-08-16 | 2023-08-16 | Software maintenance upgrade management method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311030320.7A CN116737208B (en) | 2023-08-16 | 2023-08-16 | Software maintenance upgrade management method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116737208A true CN116737208A (en) | 2023-09-12 |
| CN116737208B CN116737208B (en) | 2023-10-24 |
Family
ID=87917283
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311030320.7A Active CN116737208B (en) | 2023-08-16 | 2023-08-16 | Software maintenance upgrade management method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116737208B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106610839A (en) * | 2015-10-21 | 2017-05-03 | 阿里巴巴集团控股有限公司 | Method for releasing upgrading package and lightweight upgrading method, device and system |
| US20190171437A1 (en) * | 2017-12-04 | 2019-06-06 | nPhase, Inc. | Server and system for versioning for software in the context of multi-tenancy |
| CN111698558A (en) * | 2020-06-01 | 2020-09-22 | 深圳Tcl数字技术有限公司 | Television software upgrading method, television terminal and computer readable storage medium |
| CN112559373A (en) * | 2020-12-24 | 2021-03-26 | 郑州信大捷安信息技术股份有限公司 | Software compatibility management method and system |
| CN116088893A (en) * | 2022-12-08 | 2023-05-09 | 北京知道创宇信息技术股份有限公司 | Upgrade package generation method, device, electronic equipment and computer readable storage medium |
-
2023
- 2023-08-16 CN CN202311030320.7A patent/CN116737208B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106610839A (en) * | 2015-10-21 | 2017-05-03 | 阿里巴巴集团控股有限公司 | Method for releasing upgrading package and lightweight upgrading method, device and system |
| US20190171437A1 (en) * | 2017-12-04 | 2019-06-06 | nPhase, Inc. | Server and system for versioning for software in the context of multi-tenancy |
| CN111698558A (en) * | 2020-06-01 | 2020-09-22 | 深圳Tcl数字技术有限公司 | Television software upgrading method, television terminal and computer readable storage medium |
| CN112559373A (en) * | 2020-12-24 | 2021-03-26 | 郑州信大捷安信息技术股份有限公司 | Software compatibility management method and system |
| CN116088893A (en) * | 2022-12-08 | 2023-05-09 | 北京知道创宇信息技术股份有限公司 | Upgrade package generation method, device, electronic equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 苏雪等: "服务可用性***的软件在线升级设计", 华东理工大学学报, vol. 31, no. 04 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116737208B (en) | 2023-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103281373B (en) | Home gateway intelligent update device and upgrade method | |
| JP5933689B2 (en) | Method and apparatus for supplying electrical energy | |
| CN108288855B (en) | Dynamic strategy simulation and optimization method based on micro-grid | |
| CN113347225B (en) | OTA (over the air) upgrading method and server for terminal equipment of Internet of things | |
| CN103874113A (en) | Wireless network maintenance method, device and system | |
| CN105159718B (en) | Firmware upgrade method and device | |
| CN104753130A (en) | Mobile equipment charging device and software mounting method thereof | |
| CN101916194A (en) | Method for deploying node procedure of wireless sensing network | |
| CN106849263A (en) | A kind of power supply unit, electric power system, method of supplying power to | |
| CN109217464A (en) | Efficiency control terminal subsystem intelligent management and device | |
| Umemori et al. | Design for upgradable products considering future uncertainty | |
| CN103605814A (en) | Information processing method and information processing system in substation transformation process | |
| CN114115822B (en) | Cloud edge combination-based intelligent wearable operating system generation method and system | |
| CN116737208B (en) | Software maintenance upgrade management method and device and electronic equipment | |
| CN116755747B (en) | Software development and upgrade management method and device and electronic equipment | |
| CN111061741A (en) | Power test data management method, system, terminal and storage medium | |
| CN206602386U (en) | A kind of power supply unit, electric power system | |
| CN112989171A (en) | Data query method, device, equipment and medium | |
| JP5847650B2 (en) | Energy management system, server device, energy management method and program | |
| CN111476487A (en) | Self-adaptive energy management method and device based on block chain and equipment | |
| CN103686668A (en) | Data updating method, system and device | |
| CN110768305A (en) | Method, device and equipment for coordinating standby resources and storage medium | |
| Yan et al. | A multi-agent based autonomous decentralized framework for power system restoration | |
| CN114153525B (en) | AI model servitization sharing method and system for power grid regulation and control service | |
| CN112835647B (en) | Application software configuration method, configuration device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CB03 | Change of inventor or designer information |
Inventor after: Yin Xiangzhu Inventor after: Ma Hui Inventor after: Lai Chongfeng Inventor after: Qiu Jianwen Inventor after: Yang Jiajun Inventor before: Yin Xiangzhu Inventor before: Ma Hui Inventor before: Lai Chongfeng Inventor before: Qiu Jianwen Inventor before: Yang Jiajun |
|
| CB03 | Change of inventor or designer information |