CN112732296B

CN112732296B - Software version updating method and device, storage medium and electronic equipment

Info

Publication number: CN112732296B
Application number: CN202011635663.2A
Authority: CN
Inventors: 李阅苗
Original assignee: Qingdao Haier Technology Co Ltd; Haier Smart Home Co Ltd
Current assignee: Qingdao Haier Technology Co Ltd; Haier Smart Home Co Ltd
Priority date: 2020-12-31
Filing date: 2020-12-31
Publication date: 2023-10-24
Anticipated expiration: 2040-12-31
Also published as: CN112732296A

Abstract

The invention discloses a software version updating method and device, a storage medium and electronic equipment. Wherein the method comprises the following steps: acquiring a first whole machine software baseline corresponding to a first electronic device which is currently controlled and a second whole machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device; combining the first complete machine software base line and the second complete machine software base line to obtain a to-be-tested set system software base line; judging whether the to-be-tested set software base line is matched with a first preset rule or not; and when the to-be-tested set software base line is not matched with the first preset rule, updating the version of the management software corresponding to the to-be-tested set software base line according to the first preset rule. The invention solves the technical problem of lower execution efficiency of the linkage scene of the home appliances caused by the corresponding software upgrading process of the home appliances.

Description

Software version updating method and device, storage medium and electronic equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and apparatus for updating a software version, a storage medium, and an electronic device.

Background

With the development of the internet of things, a plurality of home appliances can work in a linkage way, and two or more home appliances are combined for use, so that a plurality of home appliances in a series of home scenes are completed, and the home appliances are called complete home appliances. Each set of home appliances is required to provide a plurality of linkage scenes for users. However, in the running process of the home appliance, for example, in environments such as an experience shop and an exhibition hall, the situation that the whole version is disordered and the scene execution fails due to the independent upgrading of a single home appliance occurs sometimes, so that the technical problem of lower execution efficiency of the linkage scene of the home appliance in the upgrading process of each software corresponding to the home appliance can occur.

In view of the above problems, no effective solution has been proposed at present.

Disclosure of Invention

The embodiment of the invention provides a software version updating method and device, a storage medium and electronic equipment, which are used for at least solving the technical problem of low execution efficiency of a linkage scene of a complete household appliance product caused by the fact that the complete household appliance product is in the corresponding software updating process.

According to an aspect of an embodiment of the present invention, there is provided a software version updating method, including: acquiring a first complete machine software baseline corresponding to a first electronic device which is currently controlled and a second complete machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, wherein the first complete machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second complete machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software; combining the first whole machine software baseline and the second whole machine software baseline to obtain a to-be-tested set system software baseline; judging whether the to-be-tested set software base line is matched with a first preset rule or not; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device are linked in a normal execution scene; and when the to-be-tested set software baseline is not matched with the first preset rule, updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule.

According to another aspect of the embodiment of the present invention, there is also provided a software version updating apparatus, including: the system comprises an acquisition unit, a control unit and a control unit, wherein the acquisition unit is used for acquiring a first complete machine software baseline corresponding to a first electronic device which is currently controlled and a second complete machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, the first complete machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second complete machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software; the merging unit is used for merging the first complete machine software base line and the second complete machine software base line to obtain a to-be-tested set system software base line; the judging unit is used for judging whether the to-be-tested set software base line is matched with a first preset rule or not; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device are linked in a normal execution scene; and the updating unit is used for updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule when the to-be-tested set software baseline is not matched with the first preset rule.

According to a further aspect of embodiments of the present invention, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the above-described software version updating method when run.

According to yet another aspect of the embodiments of the present invention, there is also provided an electronic device including a memory in which a computer program is stored, and a processor configured to execute the software version updating method described above by the computer program.

In the embodiment of the invention, a first complete machine software baseline corresponding to a first electronic device which is currently controlled and a second complete machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device are obtained, wherein the first complete machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second complete machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software; combining the first whole machine software baseline and the second whole machine software baseline to obtain a to-be-tested set system software baseline; judging whether the to-be-tested set software base line is matched with a first preset rule or not; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device are linked in a normal execution scene; when the to-be-detected set software baseline is not matched with the first preset rule, the mode of updating the version of the management software corresponding to the to-be-detected set software baseline according to the first preset rule achieves the aim of improving the scene linkage execution efficiency of the set of household appliances in the software upgrading process, thereby realizing the technical effect of improving the scene linkage execution efficiency of the set of household appliances, and further solving the technical problem of low scene linkage execution efficiency of the set of household appliances caused by the fact that each software corresponding to the set of household appliances is upgraded.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIG. 1 is a schematic illustration of an application environment of an alternative software version update method according to an embodiment of the present application;

FIG. 2 is a schematic illustration of an application environment of another alternative software version update method according to an embodiment of the present application;

FIG. 3 is a flow diagram of an alternative software version update method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a software architecture of a home appliance in a set of software version updating methods according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a relationship model between a set version and a scene and complete machine version of an alternative software version updating method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a software baseline of a home electronics suite of an alternative software version update method according to an embodiment of the present application;

FIG. 7 is a schematic flow diagram of a suite software version system of an alternative software version updating method according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an alternative software version updating device according to an embodiment of the present invention;

fig. 9 is a schematic structural view of an alternative electronic device according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

According to an aspect of the embodiment of the present invention, a software version updating method is provided, optionally, as an alternative implementation manner, the software version updating method may be applied, but is not limited to, in the environment shown in fig. 1. The software version updating method described above may be applied, but is not limited to, in a hardware environment as shown in fig. 1. The hardware environment comprises: a terminal device 104, a network 112 and a server 114 which interact with the user in a man-machine manner. Human-machine interaction can be performed between the user 102 and the terminal device 104, and a software version updating application client is operated in the terminal device 104. The terminal device 104 includes a display 110, a processor 108, and a memory 106. The display 110 is configured to present software version information of a third party device to be currently controlled, such as the first electronic device 120 and/or the second electronic device 122; the processor 108 is configured to obtain a first complete machine software baseline corresponding to a first electronic device currently controlled, and a second complete machine software baseline corresponding to a second electronic device having a linkage relationship with the first electronic device.

In addition, the server 114 includes a database 116 and a processing engine 118, and the database 116 is used for storing information of the first preset rule. The processing engine 118 is configured to update the version of the management software corresponding to the to-be-tested set-up software baseline according to the first preset rule when the to-be-tested set-up software baseline does not match the first preset rule.

As another alternative embodiment, the software version updating method of the present application described above may be applied to fig. 2. As shown in fig. 2, a human-machine interaction may be performed between a user 202 and a user device 204. The user device 204 includes a memory 206 and a processor 208. In this embodiment, the ue 204 may, but is not limited to, refer to performing the operations performed by the terminal device 102, and update the version of the management software corresponding to the baseline of the to-be-tested set software according to the first preset rule.

Alternatively, in this embodiment, the first electronic device 104 and the user device 204 may be terminal devices configured with target clients, which may include, but are not limited to, at least one of the following: a mobile phone (e.g., an Android mobile phone, iOS mobile phone, etc.), a notebook computer, a tablet computer, a palm computer, a MID (Mobile Internet Devices, mobile internet device), a PAD, a desktop computer, a smart television, etc. The target client may be a video client, an instant messaging client, a browser client, an educational client, and the like. The first electronic device 120 and the second electronic device 122 may be smart home devices such as a first humidifier, an air conditioner, and a sweeping robot, and the network 112 may include, but is not limited to: a wired network, a wireless network, wherein the wired network comprises: local area networks, metropolitan area networks, and wide area networks, the wireless network comprising: bluetooth, WIFI, and other networks that enable wireless communications. The server 114 may be a single server, a server cluster including a plurality of servers, or a cloud server. The above is merely an example, and is not limited in any way in the present embodiment.

Optionally, as an optional implementation manner, as shown in fig. 3, the software version updating method includes:

s302, acquiring a first whole machine software baseline corresponding to a first electronic device which is currently controlled and a second whole machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, wherein the first whole machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second whole machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software;

s304, combining the first whole machine software baseline and the second whole machine software baseline to obtain a to-be-tested set system software baseline;

s306, judging whether a to-be-tested set software baseline is matched with a first preset rule; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic equipment and the second electronic equipment when the first electronic equipment and the second electronic equipment are linked in a normal execution scene;

and S308, updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule when the to-be-tested set software baseline is not matched with the first preset rule.

Optionally, in this embodiment, the method for prompting update of a software version may be applied, but not limited to, in an update process of control software of a plurality of home devices in the internet of things. That is, a plurality of home devices that perform scene linkage can be managed in the software version updating system. The first electronic device and the second electronic device herein may include, but are not limited to: humidifiers, air conditioning, sweeping robots, etc. Here, this is an example, and this is not limiting in this embodiment.

In step S302, during actual application, the software version information of a plurality of management software is included in the whole software baseline of the first electronic device; here, taking a refrigerator as an example, there are multiple control software such as circuit board control software a, temperature control software B in the refrigerator, control software C for a display screen of the refrigerator, etc., where a combination of software versions corresponding to the control software a, B and C respectively forms a complete machine software baseline of the refrigerator, at this time, each control software corresponding to a current complete machine software baseline V1 (which may also be recorded as V1.2.1) of the refrigerator is that the version of the control software a is V1, the version of the control software B is V2, and the version of the control software C is V1.

In step S304, during practical application, the first complete machine software baseline and the second complete machine software baseline are combined to obtain a to-be-tested set system software baseline, that is, the version numbers of the control software corresponding to the current first electronic device and the version numbers of the control software corresponding to the second electronic device are combined to obtain a set of version numbers of the software as the to-be-tested set system software baseline. For example, when the first electronic device is a refrigerator, the version of the corresponding control software a is V1, the version of the control software B is V2, and the version of the control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V2, the version of the control software E is V2, and the version of the control software F is V1; then the test set software baseline may be V1.2.1.2.2.1.

In step S306, during actual application, the first preset rule includes software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device are linked in a normal execution scene, where the first electronic device is taken as a refrigerator, the second electronic device is taken as an air conditioner as an example, when the refrigerator and the air conditioner are linked in the normal execution scene, the version of control software a corresponding to the refrigerator is V1, the version of control software B is V1, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V1, the version of the control software E is V2, and the version of the control software F is V1; or the version of control software A corresponding to the refrigerator is V1, the version of control software B is V2, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V2, the version of the control software E is V1, and the version of the control software F is V2; then the first preset rule may be stored as a normal linkage scenario, and the set-up software baseline may be V1.1.1.1.2.1 or V1.2.1.2.1.2. And when the baseline of the software to be tested is V1.2.1.2.2.1, the baseline of the software to be tested is not matched with the first preset rule.

In step S308, in the actual application, taking the scenario in step S306 as an example, when the to-be-tested set software baseline does not match the first preset rule, the version of the management software corresponding to the to-be-tested set software baseline is correspondingly updated according to the set software baseline V1.1.1.1.2.1 or V1.2.1.2.1.2 stored in the first preset rule. Here, the version of the control software a of the refrigerator may be updated to V1, while the control software D of the air conditioner is updated to V1; or the version of the control software E of the air conditioner may be updated to V1 and the version of the control software F may be updated to V1.

In one embodiment, step S302 is preceded by: determining a plurality of corresponding set software baselines as a set software baselines when the first electronic equipment and the second electronic equipment are linked in a normal execution scene; and storing the set of the software baseline set into a first rule file corresponding to a first preset rule.

In this embodiment, taking the first electronic device as a refrigerator and the second electronic device as an air conditioner as an example, when the refrigerator and the air conditioner are in a scene of normal execution scene linkage, the version of control software a corresponding to the refrigerator is V1, the version of control software B is V1, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V1, the version of the control software E is V2, and the version of the control software F is V1; or the version of control software A corresponding to the refrigerator is V1, the version of control software B is V2, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V2, the version of the control software E is V1, and the version of the control software F is V2; then the baseline V1.1.1.1.2.1 or V1.2.1.2.1.2 of the hitching software under the normal linkage scene is stored in the first preset rule.

In one embodiment, step S308 includes: matching the to-be-detected set software baseline with a set of set software baselines in a first rule file; when the to-be-tested set of software baselines cannot be matched with the set of software baselines, updating the version of management software corresponding to the to-be-tested set of software baselines according to any set of software baselines in the set of software baselines.

In this embodiment, taking the first electronic device as a refrigerator and the second electronic device as an air conditioner as an example, when the baseline of the to-be-tested set software is V1.2.1.2.2.1, the set software baseline V1.1.1.1.2.1 or V1.2.1.2.1.2 stored in the first preset rule corresponds to updating the version of the management software corresponding to the to-be-tested set software baseline. Here, the version of the control software a of the refrigerator may be updated to V1, while the control software D of the air conditioner is updated to V1; or the version of the control software E of the air conditioner may be updated to V1 and the version of the control software F may be updated to V1.

In an embodiment, step S308 further includes: determining a target set software baseline from the first rule file; and upgrading management software corresponding to at least one of the first electronic equipment and the second electronic equipment through an Over-the-Air (OTA) Over-the-Air system according to the target set system software baseline. The target hitching software baseline can be determined according to a scene corresponding to the hitching software baseline in the first preset rule file. And selecting a target set software baseline suitable for the current scene from the first preset rule file, and upgrading management software corresponding to at least one of the first electronic equipment and the second electronic equipment.

In an embodiment, step S308 further includes: under the condition that a first electronic device and a second electronic device corresponding to a to-be-tested set software baseline are detected, and a linkage scene is added, prompting to increment a minor version number in a version number corresponding to the to-be-tested set software baseline; matching a target set system software baseline from the first rule file according to the incremented minor version number; and updating the version of the management software corresponding to the to-be-tested set system software baseline according to the target set system software baseline.

In the embodiment of the invention, the following steps are included: 1) The set base line version number is composed of three bits of X, Y and Z.

2) The major version number zero (0. Y. Z) set is in the initial stage of development, and everything can be changed at any time. Such a version should not be considered as a stable version, but can only be used in joint debugging, acceptance environments.

3) Version number 1.0.0 is used for acceptance, formally release version, only formally release version is available for experience shop deployment. After this version, all of the scene, the single product model, and any changes to the software product in the suite must change the version.

4) The master version number X (x.y.z|x > 0) must be incremented when any of the scene, singleton, software in the suite changes, resulting in incompatibility with the original baseline version.

5) The minor version number Y (x.y.z|x > 0) must be incremented when the scene and the singleton in the set are changed, but are compatible with the original base line version.

6) Revision number Z (x.y.z|x > 0) must be changed when the version of software installed in the in-train single-product network device changes.

In an embodiment, step S308 further includes: under the condition that the change of the number of the electronic devices corresponding to the to-be-tested set software base line is detected, prompting to increment a minor version number in the version numbers corresponding to the to-be-tested set software base line; matching a target set system software baseline from the first rule file according to the incremented minor version number; and updating the version of the management software corresponding to the to-be-tested set system software baseline according to the target set system software baseline.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention.

Based on the above embodiments, in an application embodiment, the software version updating method of the embodiment of the present invention includes the following steps as shown in fig. 4: the household appliances are combined by two or more household appliances, and a plurality of household appliances which are used for completing a plurality of family scenes are called complete household appliances.

1. The complete product consists of a plurality of single-product network device models. For example, the household appliance sleeve is composed of a plurality of household appliance products with the same type.

2. Each set of kits is intended to provide a user with a number of linked scenarios.

3. Multiple software products may be installed on a single product network device, and dependencies may exist between the software products.

4. There may also be a dependency between the software products on the single-product network and the cloud service.

5. The set of stock products contains a plurality of individual items, each stock realizing a specific linkage scenario.

6. All the concepts can be upgraded, such as terminal software upgrade, cloud service upgrade and complete set system upgrade.

In the home appliance set 1.0, there are an air conditioner A1, a refrigerator B1, and a water heater C1, which can perform scene linkage. In the sleeve system of the household appliances 2.0, the washing machine D1 and 4 household appliances are added to perform scene linkage at the same time.

As shown in fig. 5, the network device software is a software set formed by a plurality of component software running on the network device, including, but not limited to, computer board firmware, communication module firmware/software, screen end operating system software and application software of the screen device, voice module operating system software and application software of the voice network device, and the like. Certain dependency relationship exists between the software, and functions and interactions of the network device are jointly realized.

The network device software is identified and managed by adopting the version number after passing the compatibility test of the whole machine, and a base line of the network device whole machine software is formed. With iterations of the web browser software functions and interactions, each web browser model may correspond to multiple complete machine software baselines.

The linkage scene software is a network device software set formed by a plurality of network device software which are interconnected, and certain dependency relationship exists among the network device software, so that a certain linkage scene is realized together.

And the linkage scene software is verified through linkage scene test, and is identified and managed by adopting the version number, so that a linkage scene software baseline is formed. With iterative changes in the type/model of the network device, each linkage scene may correspond to a plurality of linkage scene software baselines.

As shown in fig. 6, in fig. 6; 1. and the linkage scene software base line is used for defining which network device products participate in the linkage scene and the whole machine software base line version of the linkage scene supported by each network device.

2. And the linkage scene software baseline version is expressed by a version number and is used for representing a certain linkage scene software baseline subjected to quality authentication.

3. Linkage scene software baseline version compatibility: compatibility relationships among linkage scene definitions, net ware product models, net ware software are described. Consider that the linked scene software baseline version is not downward compatible with the original baseline version when either:

a) When the single-product software version of the network appliance in the linkage scene software baseline is changed, the changed linkage scene cannot be executed correctly on the original product model set;

b) When the network device model in the linkage scene software baseline is increased, reduced or changed, a new product model set is formed, so that the linkage scene after the change cannot be correctly executed on the new product model set.

Wherein, the set of baseline version rules are as follows:

a sleeve base line: and a snapshot of a certain set of systems, all planned models, all planned scenes supported to run normally, the recorded models, scenes and all relevant software and hardware versions at the moment.

Baseline version number: a number describing the package base line, the base line version reflecting the current status of the package.

Baseline version changes: reflects the changing and upgrading transition paths of scenes in the set system, the model of the single product, the software on the single product and the like.

Baseline version compatibility: the description reflects the compatibility relationship between the scene and model in the suite.

The set of baseline version numbers were as follows:

1) The set base line version number is composed of three bits of X, Y and Z.

The set of baseline version change rules are as follows:

1) When a more advanced version of software occurs, either upgrading or downgrading, installed in any single-product network device within the suite, Z must be incremented.

After the change, when any one of the current scenes cannot be executed correctly on the set of the original model, the increment X must be caused.

2) When any scene in the set is changed or a new scene is added, Y must be incremented.

3) When the number of single product models is reduced or the number of single product models is increased in the set to form a new model set, Y must be increased.

After the change, any one of the current scenes must be incremented by X when it is not possible to perform correctly on the new model set.

4) Cases where an incremental X must result after a change in 1), 2), 3) is defined as a set of baseline version incompatibilities. And the case that no incremental X is caused, is defined as the forward compatibility of the lineage baseline version.

5) The change of the base line version number caused by any change can be issued only through test acceptance.

Based on the above embodiments, in an application embodiment, the software version updating method of the embodiment of the present invention includes the following steps, as shown in fig. 7:

s702, the software testing department completes the hitching test, records the hitching software baseline, and sends the hitching software baseline to the cloud.

S704, acquiring a scene software version from the cloud by an experience store.

S706, the experience store determines whether the scene software version accords with the set system software version baseline.

And S708, updating the software version corresponding to the electronic equipment through the OTA software package when the scene software version and the set system software version base line are not matched.

S710, the electronic equipment completes the baseline updating of the scene software version.

In the embodiment of the invention, a first wireless network created by searching a first electronic device in a client operated by a second electronic device is adopted; receiving first wireless network information corresponding to the first wireless network under the condition that the first wireless network is searched; connecting the first wireless network by utilizing the first wireless network information; transmitting second wireless network information corresponding to a second wireless network created by the second electronic device to the first electronic device under the condition that the second electronic device is connected with the first wireless network, so that the first electronic device is connected with the second wireless network; under the condition that the first electronic equipment is determined to be connected with the second wireless network, the first electronic software version is updated to a management platform mode corresponding to the client through the second wireless network, the purpose that intelligent equipment is bound through a network of third-party WIFI equipment is achieved, network binding of the intelligent equipment can be achieved only through a mobile terminal, the technical effect of controlling control efficiency is improved, and the technical problem that execution efficiency of a linkage scene of the complete household appliance is low due to the fact that software corresponding to the complete household appliance is updated in the process is solved.

According to another aspect of the embodiment of the present invention, there is also provided a software version updating apparatus for implementing the above-mentioned software version updating method. As shown in fig. 8, the apparatus includes:

an obtaining unit 802, configured to obtain a first complete machine software baseline corresponding to a first electronic device that is currently controlled, and a second complete machine software baseline corresponding to a second electronic device that has a linkage relationship with the first electronic device, where the first complete machine software baseline includes software version information of a plurality of management software of the first electronic device, and the second complete machine software baseline includes software version information of a plurality of management software of the second electronic device, and each software version information is used to indicate a version number of the management software;

a merging unit 804, configured to merge the first complete machine software baseline and the second complete machine software baseline to obtain a to-be-tested set software baseline;

a judging unit 806, configured to judge whether the to-be-tested set software baseline matches with a first preset rule; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device normally execute scene linkage;

And the updating unit 808 is configured to update, when the to-be-tested set software baseline does not match the first preset rule, a version of management software corresponding to the to-be-tested set software baseline according to the first preset rule.

In the embodiment of the invention, a whole machine software baseline of the first electronic equipment contains software version information of a plurality of management software; here, taking a refrigerator as an example, there are multiple control software such as circuit board control software a, temperature control software B in the refrigerator, control software C for a display screen of the refrigerator, etc., where a combination of software versions corresponding to the control software a, B and C respectively forms a complete machine software baseline of the refrigerator, at this time, each control software corresponding to a current complete machine software baseline V1 (which may also be recorded as V1.2.1) of the refrigerator is that the version of the control software a is V1, the version of the control software B is V2, and the version of the control software C is V1.

In the embodiment of the invention, the first whole machine software baseline and the second whole machine software baseline are combined to obtain the to-be-tested set system software baseline, namely, the version numbers of the control software corresponding to the current first electronic equipment and the version numbers of the control software corresponding to the second electronic equipment are combined to obtain a set of version numbers of the software as the to-be-tested set system software baseline. For example, when the first electronic device is a refrigerator, the version of the corresponding control software a is V1, the version of the control software B is V2, and the version of the control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V2, the version of the control software E is V2, and the version of the control software F is V1; then the test set software baseline may be V1.2.1.2.2.1.

In the embodiment of the invention, the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic equipment and the second electronic equipment when the first electronic equipment and the second electronic equipment are linked in a normal execution scene, wherein the first electronic equipment is taken as a refrigerator, the second electronic equipment is taken as an air conditioner as an example, when the refrigerator and the air conditioner are linked in the normal execution scene, the version of control software A corresponding to the refrigerator is V1, the version of control software B is V1, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V1, the version of the control software E is V2, and the version of the control software F is V1; or the version of control software A corresponding to the refrigerator is V1, the version of control software B is V2, and the version of control software C is V1; when the second electronic equipment is an air conditioner, the corresponding version of the control software D is V2, the version of the control software E is V1, and the version of the control software F is V2; then the first preset rule may be stored as a normal linkage scenario, and the set-up software baseline may be V1.1.1.1.2.1 or V1.2.1.2.1.2. And when the baseline of the software to be tested is V1.2.1.2.2.1, the baseline of the software to be tested is not matched with the first preset rule.

In the embodiment of the present invention, taking the scenario in step S306 as an example, when the to-be-tested set software baseline does not match the first preset rule, the version of the management software corresponding to the to-be-tested set software baseline is correspondingly updated according to the set software baseline V1.1.1.1.2.1 or V1.2.1.2.1.2 stored in the first preset rule. Here, the version of the control software a of the refrigerator may be updated to V1, while the control software D of the air conditioner is updated to V1; or the version of the control software E of the air conditioner may be updated to V1 and the version of the control software F may be updated to V1.

According to still another aspect of the embodiment of the present invention, there is further provided an electronic device for implementing the software version updating method, where the electronic device may be the first electronic device or the management platform shown in fig. 1. As shown in fig. 9, the first electronic device comprises a memory 902 and a processor 904, the memory 902 having stored therein a computer program, the processor 904 being arranged to perform the steps of any of the method embodiments described above by means of the computer program.

Alternatively, in this embodiment, the first electronic device may be located in at least one network device of a plurality of network devices of the computer network.

Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:

s1, acquiring a first whole machine software baseline corresponding to a first electronic device which is currently controlled and a second whole machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, wherein the first whole machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second whole machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software;

S2, combining the first whole machine software baseline and the second whole machine software baseline to obtain a to-be-tested set system software baseline;

s3, judging whether a to-be-tested set software baseline is matched with a first preset rule; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic equipment and the second electronic equipment when the first electronic equipment and the second electronic equipment are linked in a normal execution scene;

and S4, updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule when the to-be-tested set software baseline is not matched with the first preset rule.

Alternatively, it will be understood by those skilled in the art that the structure shown in fig. 9 is only schematic, and the electronic device or the first electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a mobile internet device (Mobile Internet Devices, MID), a PAD, etc. Fig. 9 is not limited to the structure of the electronic device and the electronic apparatus described above. For example, the electronics may also include more or fewer components (e.g., network interfaces, etc.) than shown in fig. 9, or have a different configuration than shown in fig. 9.

The memory 902 may be used to store software programs and modules, such as program instructions/modules corresponding to the software version updating method and apparatus in the embodiments of the present invention, and the processor 904 executes the software programs and modules stored in the memory 902, thereby performing various functional applications and data processing, that is, implementing the software version updating method described above. The memory 902 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 902 may further include memory remotely located relative to the processor 904, which may be connected to the terminal 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 memory 902 may be, but not limited to, for storing information such as a virtual first preset rule file. As an example, as shown in fig. 9, the memory 902 may include, but is not limited to, the acquiring unit 802, the merging unit 804, the judging unit 806, and the updating unit 808 in the software version updating device. In addition, other module units in the software version updating device may be included but are not limited to the above, and are not described in detail in this example.

Optionally, the transmission device 906 is used to receive or transmit data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission means 906 includes a network adapter (Network Interface Controller, NIC) that can connect to other network devices and routers via a network cable to communicate with the internet or a local area network. In one example, the transmission device 906 is a Radio Frequency (RF) module for communicating wirelessly with the internet.

In addition, the first electronic device further includes: a display 908 for displaying configuration information of the first electronic device; and a connection bus 910 for connecting the respective module parts in the above-described electronic device.

In other embodiments, the terminal device or the server may be a node in a distributed system, where the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the plurality of nodes through a network communication. Among them, the nodes may form a Peer-To-Peer (P2P) network, and any type of computing device, such as a server, a terminal, etc., may become a node in the blockchain system by joining the Peer-To-Peer network.

According to a further aspect of embodiments of the present invention, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

Alternatively, in the present embodiment, the above-described computer-readable storage medium may be configured to store a computer program for executing the steps of:

Alternatively, in this embodiment, it will be understood by those skilled in the art that all or part of the steps in the methods of the above embodiments may be performed by a program for instructing a terminal device to execute the steps, where the program may be stored in a computer readable storage medium, and the storage medium may include: flash disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic or optical disk, and the like.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

The integrated units in the above embodiments may be stored in the above-described computer-readable storage medium if implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present invention may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing one or more computer devices (which may be personal computers, servers or network devices, etc.) to perform all or part of the steps of the method of the various embodiments of the present invention.

In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.

In several embodiments provided by the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and are merely a logical functional division, and there may be other manners of dividing the apparatus in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.

Claims

1. A method for updating a software version, comprising:

acquiring a first complete machine software baseline corresponding to a first electronic device which is currently controlled and a second complete machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, wherein the first complete machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second complete machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating a version number of the management software;

Combining the first complete machine software baseline and the second complete machine software baseline to obtain a to-be-tested set system software baseline;

judging whether the to-be-tested set software base line is matched with a first preset rule or not; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device normally execute scene linkage;

updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule when the to-be-tested set software baseline is not matched with the first preset rule, wherein updating the version of the management software corresponding to the to-be-tested set software baseline according to the first preset rule when the to-be-tested set software baseline is not matched with the first preset rule comprises: matching the to-be-tested set of software baselines with a set of software baselines stored in a first rule file corresponding to the first preset rule; when the set of software baselines to be tested cannot be matched with the set of software baselines, updating the version of management software corresponding to the set of software baselines to be tested according to any set of software baselines in the set of software baselines, wherein the set of software baselines is composed of a plurality of corresponding set of software baselines when the first electronic equipment and the second electronic equipment are linked in a normal execution scene.

2. The method of claim 1, wherein the obtaining a first complete machine software baseline corresponding to the first electronic device currently controlled comprises:

determining the corresponding plurality of hitching software baselines as the hitching software baseline set when the first electronic equipment and the second electronic equipment are linked in a normal execution scene;

and storing the set of software baselines into the first rule file.

3. The method according to claim 2, wherein updating the version of the management software corresponding to the to-be-tested set-up software baseline according to the first rule when the to-be-tested set-up software baseline does not match the first preset rule comprises:

determining a target set software baseline from the first rule file;

and upgrading management software corresponding to at least one of the first electronic equipment and the second electronic equipment through an over-the-air system OTA according to the target set system software baseline.

4. The method according to claim 2, wherein updating the version of the management software corresponding to the to-be-tested set-up software baseline according to the first rule when the to-be-tested set-up software baseline does not match the first preset rule comprises:

When the first electronic equipment and the second electronic equipment corresponding to the to-be-tested set software base line are detected, under the condition that a linkage scene is added to the first electronic equipment and the second electronic equipment, the secondary version number in the version number corresponding to the to-be-tested set software base line is prompted to be increased;

matching a target set software baseline from the first rule file according to the incremented minor version number;

and updating the version of the management software corresponding to the to-be-tested set system software baseline according to the target set system software baseline.

5. The method according to claim 2, wherein updating the version of the management software corresponding to the to-be-tested set-up software baseline according to the first preset rule when the to-be-tested set-up software baseline does not match the first preset rule, comprises:

under the condition that the change of the number of the electronic devices corresponding to the to-be-tested set software base line is detected, prompting to increment a minor version number in the version numbers corresponding to the to-be-tested set software base line;

6. A software version updating device, comprising:

the system comprises an acquisition unit, a control unit and a control unit, wherein the acquisition unit is used for acquiring a first whole machine software baseline corresponding to a first electronic device which is currently controlled and a second whole machine software baseline corresponding to a second electronic device which has a linkage relation with the first electronic device, the first whole machine software baseline comprises software version information of a plurality of management software of the first electronic device, the second whole machine software baseline comprises software version information of a plurality of management software of the second electronic device, and each software version information is used for indicating the version number of the management software;

the merging unit is used for merging the first complete machine software base line and the second complete machine software base line to obtain a to-be-tested set system software base line;

the judging unit is used for judging whether the to-be-tested set software base line is matched with a first preset rule or not; the first preset rule comprises software version numbers of a plurality of management software corresponding to the first electronic device and the second electronic device when the first electronic device and the second electronic device normally execute scene linkage;

the updating unit is configured to update, when the to-be-detected set software baseline does not match the first preset rule, a version of management software corresponding to the to-be-detected set software baseline according to the first preset rule, where when the to-be-detected set software baseline does not match the first preset rule, updating, according to the first preset rule, the version of management software corresponding to the to-be-detected set software baseline includes: matching the to-be-tested set of software baselines with a set of software baselines stored in a first rule file corresponding to the first preset rule; when the set of software baselines to be tested cannot be matched with the set of software baselines, updating the version of management software corresponding to the set of software baselines to be tested according to any set of software baselines in the set of software baselines, wherein the set of software baselines is composed of a plurality of corresponding set of software baselines when the first electronic equipment and the second electronic equipment are linked in a normal execution scene.

7. The apparatus according to claim 6, comprising: the apparatus further comprises:

the determining unit is used for determining a plurality of corresponding set software baselines as a set software baselines set when the first electronic equipment and the second electronic equipment are linked in a normal execution scene;

and the storage unit is used for storing the set of the software baseline set into a first rule file corresponding to the first preset rule.

8. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program when run performs the method of any one of claims 1 to 5.

9. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of claims 1 to 5 by means of the computer program.