CN112166410A - System operation method, system, movable platform and storage medium - Google Patents
System operation method, system, movable platform and storage medium Download PDFInfo
- Publication number
- CN112166410A CN112166410A CN201980033902.6A CN201980033902A CN112166410A CN 112166410 A CN112166410 A CN 112166410A CN 201980033902 A CN201980033902 A CN 201980033902A CN 112166410 A CN112166410 A CN 112166410A
- Authority
- CN
- China
- Prior art keywords
- configuration file
- version
- filled
- difference information
- storage area
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- RZVHIXYEVGDQDX-UHFFFAOYSA-N 9,10-anthraquinone Chemical compound C1=CC=C2C(=O)C3=CC=CC=C3C(=O)C2=C1 RZVHIXYEVGDQDX-UHFFFAOYSA-N 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a system operation method, a system, a movable platform and a storage medium, the method obtains and operates a first configuration file containing difference information between the configuration files of previous versions, when a version rollback instruction is received, the difference information between the configuration file of the version and the first configuration file can be searched and obtained from the first configuration file according to the information of the version which is returned to a target, and therefore a second configuration file corresponding to the version is generated and operated according to the difference information and the first configuration file, the automatic rollback of the firmware version is further achieved, manual configuration of firmware parameters is not needed, manual operation is saved, and efficiency is improved.
Description
Technical Field
The embodiment of the application relates to the field of data processing, in particular to a system operation method, a system, a movable platform and a storage medium.
Background
In the related art, when the firmware of the drone or the unmanned system is updated, the configuration file of the system needs to be updated, and some contents may be added, deleted or changed in the updated configuration file, this presents difficulties for the system to degrade to the old version, however, in practical scenarios, the need to revert to the old version is real, especially in unmanned aerial vehicles or unmanned systems, where configuration information such as camera encoding, sensor calibration parameters, etc. are all different from vehicle to vehicle, sometimes these parameters have to be manually configured to degrade to the old version, therefore, the degradation efficiency is low, and the batch execution of the unmanned plane or the unmanned system is not facilitated, so how to realize the version update and ensure the forward and backward compatibility of the configuration file, the important technical problem to be solved is that the firmware version of the unmanned aerial vehicle or the unmanned aerial vehicle system can be automatically switched back to the old version.
Disclosure of Invention
The embodiment of the application provides a system operation method, a system, a movable platform and a storage medium, which are used for enabling a firmware version of the system to automatically fall back to an old version.
A first aspect of an embodiment of the present application provides a system operation method, including: acquiring and operating a first configuration file, wherein the first configuration file comprises difference information between the first configuration file and configuration files of previous versions; receiving a version rollback instruction, wherein the version rollback instruction comprises version information to which a target is rolled back; according to the version information, searching and obtaining difference information between the first configuration file and a second configuration file corresponding to the version from the first configuration file; and generating and operating a second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
A second aspect of an embodiment of the present application provides a control system, including: an instruction receiving component, a memory and one or more processors, the one or more processors operating individually or in concert, the instruction receiving component being in communication with the one or more processors, the memory having stored therein a computer program that, when executed by the processor, is configured to: acquiring and operating a first configuration file, wherein the first configuration file comprises difference information between the first configuration file and configuration files of previous versions; the instruction receiving component is to: receiving a version rollback instruction, wherein the version rollback instruction comprises version information to which a target is rolled back; the processor is further configured to: according to the version information, searching and obtaining difference information between the first configuration file and a second configuration file corresponding to the version from the first configuration file; and generating and operating a second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
A third aspect of embodiments of the present application provides a movable platform, including: the second aspect provides the control system described above.
A fourth aspect of embodiments of the present invention is to provide a computer-readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the method of the first aspect.
By obtaining and operating the first configuration file containing the difference information between the configuration files of the previous versions, when a version rollback instruction is received, the difference information between the configuration file of the version and the first configuration file can be searched and obtained from the first configuration file according to the information of the version to which the target is rolled back, so that the second configuration file corresponding to the version is generated and operated according to the difference information and the first configuration file, the automatic rollback of the firmware version is further realized, the manual configuration of firmware parameters is not needed, the manual operation is saved, the efficiency is improved, particularly on equipment which carries sensor equipment and has different parameters, such as an unmanned aerial vehicle or an unmanned system, and the version rollback can be automatically executed on the basis of the difference information of the configuration files of different versions without additionally reconfiguring individualized parameters for the sensor on each equipment, batch version rollback operations are easy to perform.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a flowchart of a method for operating a system according to an embodiment of the present application;
FIG. 2 is a diagram of an application scenario provided by an embodiment of the present application;
fig. 3 is a schematic diagram of another application scenario provided in an embodiment of the present application;
4 a-4 b are schematic diagrams of a user interaction interface provided by an embodiment of the application;
FIG. 5a is a diagram of exemplary difference information provided by an embodiment of the present application;
FIG. 5b is a schematic diagram of another exemplary difference information provided by an embodiment of the present application;
FIG. 5c is a schematic diagram of yet another exemplary difference information provided by an embodiment of the present application;
fig. 6 is a flowchart of a method for obtaining a first configuration file according to an embodiment of the present application;
fig. 7a is a schematic diagram illustrating a comparison between a third configuration file and a configuration file to be filled in according to an embodiment of the present application;
fig. 7b is a schematic diagram illustrating a comparison between another third configuration file provided in the embodiment of the present application and a configuration file to be filled in;
fig. 7c is a schematic diagram illustrating a comparison between a third configuration file provided in an embodiment of the present application and a configuration file to be filled in;
fig. 8 is a schematic structural diagram of a control system according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It will be understood that when an element is referred to as being "secured to" another element, it can be directly on the other element or intervening elements may also be present. When a component is referred to as being "connected" to another component, it can be directly connected to the other component or intervening components may also be present.
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 herein in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
The embodiment of the application provides a system operation method. Fig. 1 is a flowchart of a system operation method according to an embodiment of the present disclosure. The execution subject of the method may be a control system of a device, such as an unmanned aerial vehicle or a smart driving vehicle, which is equipped with sensors, and parameters of the sensors are different from one vehicle to another, for example, the unmanned aerial vehicle according to the present embodiment may include an unmanned ship or an unmanned aerial vehicle, and accordingly, the control system according to the present embodiment may be a navigation control system of the unmanned ship or a flight control system of the unmanned aerial vehicle, and the smart driving vehicle according to the present embodiment refers to a vehicle, such as an unmanned vehicle or an automobile equipped with an auxiliary driving system, which can execute automatic control or auxiliary control of the vehicle through the sensors mounted on the vehicle itself. As shown in fig. 1, the method in this embodiment may include:
The designation of "first profile" in this embodiment is only used to distinguish this profile from other profiles, and does not have other meanings. For ease of understanding, the first configuration file may be understood as an example of a configuration file of a latest version of firmware, and the configuration file may be obtained by a template programming method (e.g., protobuf), so that the configuration file may be compared with an old version of the configuration file obtained by the method before, replaced, and the like, and at the same time, the configuration file obtained by the method may lack fields and/or include undefined fields.
The "difference information" referred to in this embodiment may be recorded in an undefined field of the first configuration file, and for example, the difference information may include at least one of the following information: the configuration file of the later version is compared with the configuration file of the previous version to delete the field and the field value, add the field and the field data, change the field of the data, and the value before the field is changed and the value after the field is changed.
The process of acquiring and running the first configuration file in the embodiment may be exemplarily understood as a process of firmware upgrade.
For example, fig. 2 is a schematic diagram of an application scenario provided in the embodiment of the present application, where the scenario includes the smart driving vehicle 21 and the server 22. As shown in fig. 2, in an embodiment, data transmission may be performed between the intelligent driving vehicle 21 and the server 22 by using wireless communication, before the upgrade, the server 22 configures difference information between the first configuration file and the configuration files of previous versions, and records the difference information in an undefined field of the first configuration file, during the upgrade, the server 22 sends the first configuration file carrying the difference information to the intelligent driving vehicle 21, and the intelligent driving vehicle 21 overwrites the original configuration file by the received first configuration file.
The first configuration file is adopted to cover the original configuration file, so that the storage space of the control system which is taken as the execution main body in the embodiment can be saved, the space waste is avoided, and because the difference information in the first configuration file is configured by the server, the operation of configuring the difference information by the control system can be saved, the processing resource of the control system is saved, meanwhile, the control system is allowed to return to the old version according to the difference information, and the version returning efficiency is improved.
For example, fig. 3 is a schematic diagram of another application scenario provided in the embodiment of the present application, as shown in fig. 3, in another embodiment mode, the server 22 sends a configuration file of a latest version of firmware to the smart driving vehicle 21, where the configuration file does not include the difference information, and after receiving the configuration file of the latest version of firmware, the smart driving vehicle 21 may compare the latest configuration file with a configuration file of a current version to obtain difference information between the configuration file of the current operating version and the latest configuration file, and obtain difference information between the configuration file of the latest version and the configuration files of the previous versions according to the difference information between the configuration file of the current version and the configuration files of the previous versions included in the configuration file of the current version. The first configuration file is then generated by recording the difference information into an undefined field of the latest version of the configuration file.
The control system serving as the execution main body of the embodiment generates the difference information between the configuration file of the latest version and the configuration files of the previous version, so that the calculation amount of the server side can be reduced, the efficiency of the server side for distributing the new version configuration file is improved, meanwhile, the difference information between the previous configuration file and the latest configuration file can be accurately obtained, automatic rollback can be ensured according to the difference information in a version rollback scene, parameters of devices such as sensors are prevented from being manually configured, and the rollback operation efficiency is improved.
Of course, the above description is only given by using fig. 2 and fig. 3 as an example, and is not intended to limit the application scenario to which the present embodiment is applied and the manner of acquiring the first configuration file. In fact, in some embodiments, the smart driving vehicle 21 in fig. 2 and 3 may also be replaced by an unmanned aerial vehicle or other device equipped with sensor devices, and parameters of the sensor devices are different according to different bodies, and in fact, the server 22 in fig. 2 and 3 may also be replaced by other devices having data processing and transmitting capabilities, such as a ground station.
For example, the user may send a version rollback instruction to the execution subject control system of the present embodiment through a ground station, a mobile phone, or other devices, or, in other embodiments, the control system may receive a rollback instruction input by the user via the user interface by providing a user interface, such as, for example, fig. 4 a-4 b are schematic diagrams of a user interaction interface provided by an embodiment of the present application, as shown in fig. 4a, in some scenarios, the control system may display the version information for the current version Vn and the previous old versions V1 through Vn-1 on a user interactive interface, from which the user selects the version to which the target is to be backed by means such as clicking, pressing or voice command, and the control system obtains the information of the target backspacing version according to the operation instruction or the voice instruction input by the user. Or, as shown in fig. 4b, in other scenarios, the control system may set an input area 421 on the user interaction interface, where the input area 421 may include a first sub-area 4211 for inputting version information of the target fallback and a second sub-area 4212 for inputting a current version, where in some scenarios, the input area 421 may not include the second sub-area 4212, and the user may fill the version of the target fallback in the input area 421 by touching or voice inputting, and generate the fallback instruction by triggering the enter key 422 on the interaction interface manually or by voice.
The rollback instruction referred to in this embodiment includes version information of the target rollback, for example, in some embodiments, the rollback instruction may carry a version number of the target rollback, in other embodiments, the rollback instruction may use the current version number to point to the version number of the target rollback, and the current version number may be, for example, VB-VA, VB represents the current version number, and VA represents the version number of the target rollback.
For example, fig. 5a is a schematic diagram of exemplary difference information provided in an embodiment of the present application, in fig. 5a, a later version VB differs from a previous version VA in that values of the field a and the field B are changed, and when it is determined that the version VA is a target fallback version, values aa and bb of the field a and the field B in the version VA are obtained. For another example, fig. 5b is a schematic diagram of another exemplary difference information provided in the embodiment of the present application, as shown in fig. 5b, a difference between a later version VB and a previous version VA is that a field C is added to the later version, and when it is determined that the version VA is a target fallback version, the configuration file for obtaining the version VA does not include information of the field C. For another example, fig. 5c is a schematic diagram of still another exemplary difference information provided in the embodiment of the present application, in fig. 5c, a difference between the later version VB and the previous version VA is that the field D is deleted in the later version, and then, when it is determined that the version VA is the target fallback version, the value jj of the field D is included in the configuration file of the version VA.
Although the case of individually changing the value, adding the field, and deleting the field is exemplarily illustrated only in fig. 5a, 5b, and 5c, it is not excluded that the two or more differences may exist between the configuration file of the later version and the configuration file of the previous version at the same time, and when the two or more differences are included between the configuration file of the later version and the configuration file of the previous version, the difference information may be obtained by referring to the corresponding difference cases in fig. 5a, 5b, and 5c, respectively, and will not be described herein again.
And 104, generating and operating the second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
For example, when the configuration file of the target fallback-to version is different from the first configuration file in that the first configuration file deletes the field D, according to the difference information, when the fallback-to target fallback-to version, the data of the field D deleted by the first configuration file is added to the first configuration file to form the second configuration file.
Or when the configuration file of the target rollback version is different from the first configuration file in that the field C is added to the first configuration file, deleting the field C from the first configuration file when the target rollback version is in the rollback state, and generating a second configuration file.
Or when the difference between the configuration file of the target fallback to version and the first configuration file is that the first configuration file modifies the value of the field B, acquiring the value of the field B in the target fallback to version according to the difference information, and changing the value of the field B in the first configuration file to the value to generate a second configuration file.
Further, the second configuration file generated in this embodiment may still carry difference information between the first configuration file and the configuration files of the previous versions, or, while the second configuration file is generated, according to a difference between the second configuration file and the first configuration file and a difference between the first configuration file and another previous configuration file, difference information between the second configuration file and the first configuration file and difference information between the second configuration file and the previous configuration file are generated and recorded in an undefined field of the second configuration file, so that the control system can upgrade to a version corresponding to the first configuration file again according to the difference information or further reduce to an older version.
By obtaining and operating the first configuration file containing the difference information between the configuration files of the previous versions, when a version rollback instruction is received, the difference information between the configuration file of the version and the first configuration file can be searched and obtained from the first configuration file according to the information of the version to which the target is rolled back, so that the second configuration file corresponding to the version is generated and operated according to the difference information and the first configuration file, the automatic rollback of the firmware version is further realized, the manual configuration of firmware parameters is not needed, the manual operation is saved, the efficiency is improved, particularly on equipment which carries sensor equipment and has different parameters, such as an unmanned aerial vehicle or an unmanned system, and the version rollback can be automatically executed on the basis of the difference information of the configuration files of different versions without additionally reconfiguring individualized parameters for the sensor on each equipment, batch version rollback operations are easy to perform.
Fig. 6 is a flowchart of a method for acquiring a first configuration file according to an embodiment of the present application, where as shown in fig. 6, the method includes the following steps:
The third configuration file referred to in this embodiment is used to refer to the configuration file of the currently running version, and its name is only for descriptive convenience and convenience of distinction, and has no other meaning.
The configuration file to be filled in this embodiment is obtained by using a template programming method (for example, protobuf), so that the configuration file may implement operations such as comparison and replacement with an old version of the configuration file (for example, a third configuration file) obtained by using the method before, and at the same time, the configuration file obtained by using the method may lack fields and/or include undefined fields.
Taking the scenario shown in fig. 3 as an example, the configuration file of the latest version sent by the server 22 to the intelligent driving vehicle 21 in fig. 3 may be specifically referred to as a to-be-filled configuration file in this embodiment, where the configuration file includes data of fields updated with respect to the currently running third configuration file at this time, for example, fig. 7a is a schematic comparison diagram between a third configuration file provided in this embodiment of the present application and the to-be-filled configuration file, as shown in fig. 7a, if the value of the field B is changed with respect to the third configuration file by the configuration file of the latest version, and the field a and the field C are not changed, then the to-be-filled configuration file includes the updated value aa of the field B, and other fields are empty; for another example, fig. 7b is a schematic diagram illustrating a comparison between another third configuration file and a configuration file to be filled in provided in this embodiment, where when the content dd of the field D is added to the third configuration file in the latest version, the value of the field D is included in the configuration file to be filled in, and other fields are null. For another example, fig. 7C is a schematic diagram illustrating a comparison between a third profile and a to-be-filled profile provided in an embodiment of the present application, where when the content of the field C is deleted from the third profile in the latest version of the profile, the content of the field C is not included in the to-be-filled profile, where the symbol "…" in fig. 7a to 7C represents an omitted numerical value.
Of course, the above cases of fig. 7a to 7c are only illustrative and not exclusive, and actually, the configuration file to be filled in may be in the form of a combination of two or more cases of fig. 7a to 7 c.
For example, to implement the generation and operation of the first configuration file, an implementation of this embodiment may copy the third configuration file from the first storage area to the second storage area before receiving the update data, and store the configuration file to be filled in the first area after receiving the update data, and overwrite the third configuration file in the first area, where the second storage area is used to store the backup file.
In the process of generating the first configuration file, a third configuration file may be obtained by searching in the second storage area, and then the third configuration file is traversed by a traversal method, if a traversed field is included in the configuration file to be filled, and the value of the field in the configuration file to be filled is null, the value of the field in the third configuration file is configured to the configuration file to be filled, if the third configuration file includes some fields that are not included in the configuration file to be filled, information and values of the fields are filled into undefined fields of the configuration file to be filled to obtain first difference information, further, the configuration file to be filled is traversed, if the configuration file to be filled includes fields that are not included in the third configuration file and/or the value of a field of the configuration file to be filled is different from the value of the corresponding field in the third configuration file, and filling the information and the numerical values of the fields into undefined fields of the configuration file to be filled to obtain second difference information, and further obtaining the first configuration file.
After the first configuration file is obtained, the third configuration file in the second area can be deleted, so that the storage space is saved.
Or, in another implementation manner of this embodiment, the received configuration file to be filled may also be stored in the second area. And then obtaining a first configuration file by adopting a method similar to the first mode, covering a third configuration file in the first area by adopting the first configuration file after obtaining the first configuration file, and deleting the first configuration file in the second area.
By comparing the fields contained in the configuration file to be filled with the fields in the currently running third configuration file in the firmware version updating process, filling the empty fields in the configuration file to be filled with the contents of the corresponding fields in the third configuration file, filling the information of the fields of adding, deleting and changing numerical values of the configuration file to be filled with respect to the third configuration file in the undefined fields of the configuration file to be filled, generating difference information, so that when the control system performs version rollback operation, the control system can automatically obtain the configuration file of the old version according to the difference information without manually changing firmware parameters, thereby improving the efficiency, particularly in unmanned aerial vehicles or unmanned aerial vehicle systems, the parameters of sensors of each unmanned aerial vehicle or unmanned aerial vehicle system are different, under the condition, the method according to the embodiment can avoid the situation that the version is degraded, the complex operation of manual reconfiguration sensor parameter has improved efficiency, can carry out version to a large amount of unmanned aerial vehicle or unmanned driving system simultaneously and roll back or upgrade the operation.
Fig. 8 is a schematic structural diagram of a control system provided in an embodiment of the present application, where the control system may be configured to perform the method of any of the embodiments, as shown in fig. 8, where the control system 80 includes: an instruction receiving component 81, a memory 82 and one or more processors 83, the one or more processors 83 being operated separately or in cooperation, the instruction receiving component 81 being in communication connection with the one or more processors 83, the memory 82 having stored therein a computer program for, when executed by the processor: obtaining and operating a first configuration file, wherein the first configuration file comprises difference information between the first configuration file and configuration files of previous versions; the instruction receiving component is to: receiving a version rollback instruction, wherein the version rollback instruction comprises version information to which a target is rolled back; the processor is further configured to: according to the version information, searching and obtaining difference information between the first configuration file and a second configuration file corresponding to the version from the first configuration file; and generating and operating the second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
In one embodiment, the system further comprises: the transceiving component 84, when the processor 83 performs the operation of obtaining and running the first configuration file, includes the following operations:
receiving update data through the transceiving component, wherein the update data comprises a configuration file to be filled, and the configuration file to be filled comprises data of a field updated relative to a currently running third configuration file at this time; configuring data which is not updated in the third configuration file in the current updating to corresponding fields of the configuration file to be filled based on the data of the fields which are updated, and generating a first configuration file; recording the difference of the data corresponding to the updated fields on the first configuration file and the third configuration file and the data of the fields existing in the third configuration file but not existing in the first configuration file into the first configuration file, and generating difference information between the first configuration file and the third configuration file.
In one embodiment, the processor 83 is further configured to, before generating the first configuration file, perform the following operations: copying the third configuration file from a first storage area storing the third configuration file into a second storage area.
In one embodiment, the processor 83 is further configured to, after copying the third configuration file from the first storage area storing the third configuration file to the second storage area, perform the following operations: and covering the third configuration file in the first storage area by using the received configuration file to be filled.
In one embodiment, the processor 83, when performing the operation of generating the first configuration file, is configured to: searching the second storage area to obtain the third configuration file; and traversing each field of the third configuration file, and if the traversed field is included in the configuration file to be filled and the numerical value of the field on the configuration file to be filled is null, configuring the numerical value of the field on the third configuration file to the configuration file to be filled.
In one embodiment, the processor 83, after receiving the update data through the transceiving component, is further configured to: and storing the received configuration file to be filled in a second storage area.
In one embodiment, the processor, after generating the first configuration file, is further configured to:
and overwriting the third configuration file stored in the first storage area by using the generated first configuration file.
In one embodiment, the generated second configuration file includes difference information between the second configuration file and the first configuration file, and difference information between the second configuration file and previous versions of the second configuration file.
The control system provided by this embodiment can be used to execute the method of any of the above embodiments, and the execution mode and the beneficial effect are similar, and are not described herein again.
The embodiment of the application also provides a movable platform, and the movable bottle cap comprises the control system as shown in the embodiment of fig. 8.
Wherein the movement should include a smart driving vehicle or drone. The unmanned aerial vehicle or the intelligent driving vehicle is equipped with a sensor, and parameters of the sensor are different from those of the equipment of the unmanned aerial vehicle or the intelligent driving vehicle, for example, the unmanned aerial vehicle according to the present embodiment may include an unmanned ship or an unmanned aerial vehicle, accordingly, the control system according to the present embodiment may be a navigation control system of the unmanned ship or a flight control system of the unmanned aerial vehicle, and the intelligent driving vehicle according to the present embodiment refers to a vehicle which can perform automatic control or auxiliary control of the vehicle through the sensor mounted on the vehicle itself, such as an unmanned vehicle or an automobile equipped with an auxiliary driving system.
For example, the drone includes: an unmanned ship or an unmanned aerial vehicle.
The execution mode and the beneficial effects of the movable platform provided by the embodiment are similar to those of the control system, and are not described again here.
In addition, the present embodiment also provides a computer-readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the method of any of the above embodiments.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (20)
1. A method of operating a system, comprising:
obtaining and operating a first configuration file, wherein the first configuration file comprises difference information between the first configuration file and configuration files of previous versions;
receiving a version rollback instruction, wherein the version rollback instruction comprises version information to which a target is rolled back;
according to the version information, searching and obtaining difference information between the first configuration file and a second configuration file corresponding to the version from the first configuration file;
and generating and operating the second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
2. The method of claim 1, wherein obtaining and running the first configuration file comprises:
receiving updating data, wherein the updating data comprises a configuration file to be filled in, and the configuration file to be filled in comprises data of a field updated relative to a currently running third configuration file in the updating;
configuring data which is not updated in the third configuration file in the current updating to corresponding fields of the configuration file to be filled based on the data of the fields which are updated, and generating a first configuration file;
recording the difference of the data corresponding to the updated fields on the first configuration file and the third configuration file and the data of the fields existing in the third configuration file but not existing in the first configuration file into the first configuration file, and generating difference information between the first configuration file and the third configuration file.
3. The method of claim 2, wherein prior to generating the first configuration file, the method further comprises:
copying the third configuration file from a first storage area storing the third configuration file into a second storage area.
4. The method of claim 3, wherein after copying the third configuration file from the first storage area storing the third configuration file to the second storage area, the method further comprises:
and covering the third configuration file in the first storage area by using the received configuration file to be filled.
5. The method according to claim 3 or 4, wherein the configuring, based on the data of the field where the update is made, the data, which is not updated in the current update in the third configuration file, on the corresponding field of the configuration file to be filled out, to generate the first configuration file comprises:
searching the second storage area to obtain the third configuration file;
and traversing each field of the third configuration file, and if the traversed field is included in the configuration file to be filled and the numerical value of the field on the configuration file to be filled is null, configuring the numerical value of the field on the third configuration file to the configuration file to be filled.
6. The method of claim 2, wherein after receiving the update data, the method further comprises:
and storing the received configuration file to be filled in a second storage area.
7. The method of claim 6, wherein after generating the first configuration file, the method further comprises:
and overwriting the third configuration file stored in the first storage area by using the generated first configuration file.
8. The method according to any one of claims 1-7, wherein the generated second configuration file comprises difference information between the second configuration file and the first configuration file, and difference information between the second configuration file and previous versions of the second configuration file.
9. A control system, comprising: an instruction receiving component, a memory, and one or more processors, the one or more processors operating alone or in conjunction, the instruction receiving component and the one or more processors being communicatively coupled, the memory having stored therein a computer program, the processor when executing the program being configured to: obtaining and operating a first configuration file, wherein the first configuration file comprises difference information between the first configuration file and configuration files of previous versions;
the instruction receiving component is to: receiving a version rollback instruction, wherein the version rollback instruction comprises version information to which a target is rolled back;
the processor is further configured to: according to the version information, searching and obtaining difference information between the first configuration file and a second configuration file corresponding to the version from the first configuration file; and
and generating and operating the second configuration file corresponding to the version according to the difference information and the first configuration file so as to rollback from the version corresponding to the first configuration file to the version corresponding to the second configuration file.
10. The system of claim 9, further comprising: the transceiver component, when the processor performs the operation of obtaining and running the first configuration file, comprises the following operations:
receiving update data through the transceiving component, wherein the update data comprises a configuration file to be filled, and the configuration file to be filled comprises data of a field updated relative to a currently running third configuration file at this time;
configuring data which is not updated in the third configuration file in the current updating to corresponding fields of the configuration file to be filled based on the data of the fields which are updated, and generating a first configuration file;
recording the difference of the data corresponding to the updated fields on the first configuration file and the third configuration file and the data of the fields existing in the third configuration file but not existing in the first configuration file into the first configuration file, and generating difference information between the first configuration file and the third configuration file.
11. The system of claim 10, wherein the processor, prior to generating the first configuration file, is further configured to:
copying the third configuration file from a first storage area storing the third configuration file into a second storage area.
12. The system of claim 11, wherein the processor, after copying the third configuration file from the first storage area storing the third configuration file to the second storage area, is further configured to:
and covering the third configuration file in the first storage area by using the received configuration file to be filled.
13. The system of claim 11 or 12, wherein the processor, when performing the operation of generating the first configuration file, is configured to:
searching the second storage area to obtain the third configuration file;
and traversing each field of the third configuration file, and if the traversed field is included in the configuration file to be filled and the numerical value of the field on the configuration file to be filled is null, configuring the numerical value of the field on the third configuration file to the configuration file to be filled.
14. The system of claim 10, wherein the processor, after receiving the update data via the transceiver component, is further configured to:
and storing the received configuration file to be filled in a second storage area.
15. The system of claim 14, wherein the processor, after generating the first configuration file, is further configured to:
and overwriting the third configuration file stored in the first storage area by using the generated first configuration file.
16. The system according to any of claims 9-15, wherein the generated second configuration file comprises difference information between the second configuration file and the first configuration file, and difference information between the second configuration file and previous versions of the second configuration file.
17. A movable platform comprising a control system according to any one of claims 9-16.
18. The movable platform of claim 17, comprising: intelligent driving vehicle or unmanned aerial vehicle.
19. The movable platform of claim 18, wherein the drone includes:
an unmanned ship or an unmanned aerial vehicle.
20. A computer-readable storage medium, in which a computer program is stored, which computer program is executable by a processor to implement the method of any one of claims 1-8.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2019/106630 WO2021051341A1 (en) | 2019-09-19 | 2019-09-19 | System operation method, system, mobile platform and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112166410A true CN112166410A (en) | 2021-01-01 |
Family
ID=73859400
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980033902.6A Pending CN112166410A (en) | 2019-09-19 | 2019-09-19 | System operation method, system, movable platform and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112166410A (en) |
| WO (1) | WO2021051341A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114153527A (en) * | 2021-12-02 | 2022-03-08 | 天地伟业技术有限公司 | Configuration file modification method and device of camera and electronic equipment |
| CN116701501A (en) * | 2022-11-21 | 2023-09-05 | 荣耀终端有限公司 | Camera calibration data loading method and device and terminal equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070294684A1 (en) * | 2006-06-15 | 2007-12-20 | Fujitsu Limited | Computer program and apparatus for updating installed software programs |
| CN102255761A (en) * | 2011-08-19 | 2011-11-23 | 迈普通信技术股份有限公司 | File-based configuration rollback system and configuration rollback method |
| CN109542875A (en) * | 2018-11-20 | 2019-03-29 | 中国银行股份有限公司 | A kind of generation method and device of configuration file |
| CN110221860A (en) * | 2019-06-11 | 2019-09-10 | 腾讯科技（深圳）有限公司 | A kind of configuration file processing method, device, terminal and medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101420431B (en) * | 2008-11-28 | 2012-07-04 | 中兴通讯股份有限公司 | FOTA server, terminal and software version processing method and system therefor |
| CN102567053A (en) * | 2011-12-20 | 2012-07-11 | 云海创想信息技术（无锡）有限公司 | Method and device for downgrading software version |
| US20150220322A1 (en) * | 2014-02-06 | 2015-08-06 | Src, Inc. | System and method for reinstalling, upgrading or downgrading an operating system |
| US10289401B1 (en) * | 2016-12-30 | 2019-05-14 | Juniper Networks, Inc | Systems and methods for efficiently downgrading operating systems installed on network devices |
| CN108170448B (en) * | 2017-12-26 | 2020-06-09 | 车智互联（北京）科技有限公司 | System for automatically and efficiently releasing software update version |
-
2019
- 2019-09-19 WO PCT/CN2019/106630 patent/WO2021051341A1/en active Application Filing
- 2019-09-19 CN CN201980033902.6A patent/CN112166410A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070294684A1 (en) * | 2006-06-15 | 2007-12-20 | Fujitsu Limited | Computer program and apparatus for updating installed software programs |
| CN102255761A (en) * | 2011-08-19 | 2011-11-23 | 迈普通信技术股份有限公司 | File-based configuration rollback system and configuration rollback method |
| CN109542875A (en) * | 2018-11-20 | 2019-03-29 | 中国银行股份有限公司 | A kind of generation method and device of configuration file |
| CN110221860A (en) * | 2019-06-11 | 2019-09-10 | 腾讯科技（深圳）有限公司 | A kind of configuration file processing method, device, terminal and medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114153527A (en) * | 2021-12-02 | 2022-03-08 | 天地伟业技术有限公司 | Configuration file modification method and device of camera and electronic equipment |
| CN116701501A (en) * | 2022-11-21 | 2023-09-05 | 荣耀终端有限公司 | Camera calibration data loading method and device and terminal equipment |
| CN116701501B (en) * | 2022-11-21 | 2024-04-12 | 荣耀终端有限公司 | Camera calibration data loading method and device and terminal equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021051341A1 (en) | 2021-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11797479B2 (en) | Integrating object-based data integration tool with a version control system in centralized and decentralized environments | |
| US20210126986A1 (en) | Distributed processing system and method for the provision of location based services | |
| CN110413282B (en) | Redundant resource processing method, device, equipment and storage medium | |
| CN101582860B (en) | Method for replacing user interface skins of different communication equipment | |
| CN112166410A (en) | System operation method, system, movable platform and storage medium | |
| CN110231945A (en) | Method, apparatus, electronic equipment and the computer storage medium of code downloading | |
| CN111569427B (en) | Resource processing method and device, storage medium and electronic device | |
| WO2021238301A1 (en) | Application update method, apparatus and device and medium | |
| KR101705197B1 (en) | Local server apparatus and data relaying method thereof | |
| CN107239303B (en) | Application program update package generation method and device and application program update method and device | |
| CN207611373U (en) | A kind of control system based on master/slave structure | |
| US11507541B2 (en) | Method to model server-client sync conflicts using version trees | |
| CN106375551B (en) | Information interaction method, device and terminal | |
| CN112905306A (en) | Multi-cluster container management method and device, electronic equipment and storage medium | |
| US20160277919A1 (en) | Mobile Terminal Configuration Method and System | |
| CN113760313A (en) | Method, device and equipment for upgrading cloud platform, cloud platform system and storage medium | |
| US8516015B2 (en) | Mechanism for making changes to server file system | |
| US8707307B2 (en) | Creating jobs by replacing execution attributes within job definition when a job activation request is received with execution attributes based on predetermined conditions being satisfied | |
| CN110309018B (en) | Charging equipment system switching method, charging equipment and readable storage medium | |
| CN105608108A (en) | Universal GIS data collaborative collection method and apparatus as well as server | |
| CN112055057B (en) | Method, system and equipment for dynamic expansion of Web system | |
| CN112153156B (en) | Data processing method and device for cloud service | |
| US20220413838A1 (en) | Vehicle data communication device, center device, data communication method, and computer-readable non-transitory tangible storage medium | |
| US20240143411A1 (en) | Method for automatically maintaining an infrastructure as code state of a resource space hosted on a cloud platform | |
| CN114816575A (en) | Component loading method, hosting method, system, electronic device and storage medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240515 Address after: Building 3, Xunmei Science and Technology Plaza, No. 8 Keyuan Road, Science and Technology Park Community, Yuehai Street, Nanshan District, Shenzhen City, Guangdong Province, 518057, 1634 Applicant after: Shenzhen Zhuoyu Technology Co.,Ltd. Country or region after: China Address before: 518057 Shenzhen Nanshan High-tech Zone, Shenzhen, Guangdong Province, 6/F, Shenzhen Industry, Education and Research Building, Hong Kong University of Science and Technology, No. 9 Yuexingdao, South District, Nanshan District, Shenzhen City, Guangdong Province Applicant before: SZ DJI TECHNOLOGY Co.,Ltd. Country or region before: China |