WO2024001543A1 - System update file configuration method and apparatus, system update method and apparatus, and storage medium - Google Patents

Abstract

Provided in the embodiments of the present application are a system update file configuration method and apparatus, a system update method and apparatus, and an electronic device and a storage medium. The system update file configuration method comprises: acquiring a target file and at least one associated file, which is associated with the target file (S1000); acquiring a digital signature of the target file, and establishing a first mapping relationship between the digital signature and the target file (S2000); establishing a second mapping relationship between the target file and each associated file (S3000); acquiring a version difference between an original system version and an updated system version, and generating a system difference description file according to the version difference, the first mapping relationship and the second mapping relationship (S4000); and configuring a system update file according to the system difference description file (S5000).

Description

System update file configuration method, system update method, device and storage medium

Cross-references to related applications

This application is filed based on the Chinese patent application with application number 202210760740.

Technical field

Embodiments of the present application relate to the field of software version production and management, and in particular to a system update file configuration method, system update method, system update file configuration device, electronic equipment and storage media.

Background technique

There are two version release methods in software development: point version release and rolling release. Taking the Linux operating system distribution as an example, Ubuntu uses a point version release method. Generally, a new point version is released every few months, and users specifically upgrade the system based on this new point version; while Arch Linux uses a rolling release method, and users will have Small, frequent updates keep users on the latest release.

Taking the communications field as an example, due to comprehensive considerations of cost and stability, point version distribution is often used for system updates. However, the version management granularity of point version release is large and the support for new features is inflexible. Therefore, how to provide more lightweight, accurate and flexible system update files to achieve the rolling release capability of system versions is an issue that needs to be solved urgently.

Contents of the invention

Embodiments of the present application provide a system update file configuration method, system update method, system update file configuration device, electronic equipment, and storage media.

In a first aspect, embodiments of the present application provide a system update file configuration method, which includes: obtaining a target file and at least one associated file associated with the target file; obtaining a digital signature of the target file, and establishing the relationship between the digital signature and the associated file. a first mapping relationship between the target files; establishing a second mapping relationship between the target files and each of the associated files; obtaining the version difference between the original system version and the updated system version, and based on the version difference . The first mapping relationship and the second mapping relationship generate a system difference description file; and configure a system update file according to the system difference description file.

In a second aspect, embodiments of the present application provide a system update method, which includes: obtaining the system update file according to the system update file configuration method described in the first aspect; and updating the system according to the system update file. .

In a third aspect, embodiments of the present application provide a system update file configuration device, which device includes at least one processor; at least one memory for storing at least one program; when at least one of the programs is configured by at least one of the processors During execution, the system update file configuration method described in the first aspect is implemented.

In a fourth aspect, embodiments of the present application provide an electronic device, which includes at least one processor; at least one memory for storing at least one program; when at least one of the programs is executed by at least one of the processors Implement the system update method described in the second aspect.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the system update file configuration method as described in the first aspect. , or, the system update method as described in the second aspect.

Description of drawings

Figure 1 is a schematic diagram of system update;

Figure 2 is a flow chart of a system update file configuration method provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the version fingerprint tree provided by the embodiment of this application;

Figure 4 is a schematic diagram of the configuration process of the system update file provided by the embodiment of the present application;

Figure 5 is a schematic diagram of the difference analysis between the original system version and the updated system version provided by the embodiment of the present application;

Figure 6 is a schematic diagram of the construction process of the version update package provided by the embodiment of the present application;

Figure 7 is a schematic diagram of system update provided by the embodiment of the present application;

Figure 8 is a schematic structural diagram of a system update file configuration device provided by an embodiment of the present application;

Figure 9 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

It should be noted that although the functional modules are divided in the device schematic diagram and the logical sequence is shown in the flow chart, in some cases, the modules can be divided into different modules in the device or the order in the flow chart can be executed. The steps shown or described. The terms "first", "second", etc. in the description, claims, and above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific sequence or sequence.

In the description of the embodiments of this application, unless otherwise explicitly limited, words such as setting, installation, and connection should be understood in a broad sense. Those skilled in the art can reasonably determine the meaning of the above words in the embodiments of this application based on the specific content of the technical solution. specific meaning. In the embodiments of this application, words such as "further", "exemplarily" or "optionally" are used as examples, illustrations or illustrations, and should not be interpreted as being more preferable or better than other embodiments or designs. Advantages. The use of the words "further," "exemplarily," or "optionally" is intended to present the relevant concepts in a specific manner.

Point version release and rolling release are two version release methods in software development. Many Linux distributions, such as Debian, Ubuntu, Linux Mint, Fedora, etc., follow the point version release model. These systems will release a major XYZ version every few months/years. The point version consists of the Linux kernel, desktop environment and Made up of new versions of other software. When a new major version of a point release distribution is released, users need to specifically upgrade their systems. In the rolling release method, software updates are rolled out continuously rather than in batches. This way the software is always updated. Rolling releases follow the same model, providing the latest Linux kernel and software versions as they are released. Arch Linux is the most typical example of a rolling distribution. When users use a rolling distribution, they will get small and frequent updates.

Taking the communications field as an example, due to comprehensive considerations of cost and stability, point version distribution is often used for system updates. However, the version management granularity of point version release is large and the support for new features is inflexible. Sometimes in order to support a new feature It has to upgrade a large version, which is not friendly enough for developers and users.

Based on this, embodiments of the present application provide a system update file configuration method, system update method, system update file configuration device, electronic device and storage medium, by obtaining the digital signature of the target file, and establishing a relationship between the digital signature and the target file. The first mapping relationship, and the establishment of a second mapping relationship between the target file and its associated associated files, so that the first mapping relationship and the second mapping relationship form a fingerprint model of the system version, and updates to the system version can be obtained Make an accurately described system difference description file, so that system update files can be configured according to the system difference description file, making system update files more lightweight, accurate and flexible, realizing the rolling release capability of system versions, and optimizing the user experience. , improving the work efficiency of product managers and system maintenance personnel.

Figure 1 is a schematic diagram of the system update. As shown in the figure, the system in the electronic device 100 on the left side of the figure is the original system version, and the system update file 200 is used to perform the system update. The system in the updated electronic device 100 is the updated system version, completing the system update and upgrade process. .

Figure 2 is a flow chart of a system update file configuration method provided by an embodiment of the present application. As shown in the figure, the system update file configuration method at least includes steps S1000, S2000, S3000, S4000, and S5000.

Step S1000: Obtain the target file and at least one associated file associated with the target file. The target file is a file involved in the system update.

It should be noted that the target file can be any file in the system version. The associated files of the target file refer to the files that will be linked to each other if the target file is modified or the files that will be linked to the target file due to modifications thereof, that is, the files to which the target file has a dependency relationship.

In one embodiment, the target files are all files in the system version.

In another embodiment, the target files are files in the system version that are related to system updates.

Step S2000: Obtain the digital signature of the target file, and establish a first mapping relationship between the digital signature and the target file.

It should be noted that the digital signature of the target file can be set in advance or calculated during the system update file configuration. Related Technology Center: After the same target file (such as a library file) is compiled repeatedly, it is mainly affected by the system time. The binary files compiled twice are different, which will also cause the same target file to have different signatures after being compiled multiple times. However, the digital signature processing in the embodiment of this application ensures that the signature of the same target file remains the same after it is compiled multiple times.

It should also be noted that there are various calculation methods for digital signatures, such as RSA encryption algorithm, national secret algorithm, etc., and any signature algorithm can be implemented in the embodiments of this application. However, for the sake of independent and controllable security, the embodiment of this application uses the national secret algorithm to generate digital signatures. The national cryptographic algorithm refers to the national commercial cryptographic algorithm. It is a cryptographic algorithm standard and its application specification recognized and published by the State Cryptographic Administration. Some of the cryptographic algorithms have become international standards. For example, SM series passwords, SM stands for commercial secrets, that is, commercial passwords, which refer to encryption technology used for business and not involving state secrets. SM3 is an algorithm improved on the basis of SHA-256 and is mainly used for digital signature and verification, and random number generation.

In one embodiment, the digital signature of the target file is generally in the form of a unique code. The unique code is recorded in the data structure, and a record is added to mark the mapping relationship between the unique code and the source file, that is, a digital signature is established. The first mapping relationship between the target file and the target file. Based on this mapping relationship, a fingerprint node corresponding to the target file is formed, and multiple fingerprint nodes are aggregated to form a fingerprint tree, which can also be called a fingerprint model.

It can be understood that fingerprint nodes, fingerprint trees or fingerprint models are only one form of expression, and other forms of expression, such as linked lists, graphs, and databases, can achieve the purpose of the embodiments of the present application, which is to construct a system version of holographic projection.

Step S3000: Establish a second mapping relationship between the target file and each associated file.

It should be noted that when the target file has associated files that are dependent on it, in order to show their interdependence, a dependency record will be added to the fingerprint node corresponding to the target file, pointing to the fingerprint node of B. Since the target file often has multiple associated files, so there are multiple such pointing relationships, that is, a second mapping relationship is formed. The first mapping relationship and the second mapping relationship together constitute a fingerprint tree or fingerprint model corresponding to the system version. This fingerprint tree or fingerprint model can accurately and effectively describe the association of each file in the system version, so that when the version is upgraded, Files modified by editing and their associated files are described in a targeted manner. In the embodiment of the present application, the fingerprint tree or fingerprint model is recorded in the form of a system description file.

Figure 3 is a schematic diagram of a version fingerprint tree provided by an embodiment of the present application, which can more intuitively display the structure of a system version fingerprint tree. As shown in the figure, after compiling a version file and completing a target compilation, the corresponding fingerprint node hashA is generated. The node stores the unique signature information of the target file. At the same time, the node stores the mapping relationship between itself and the target file, that is, A.exe and the fingerprint. The mapping relationship between nodes hashA is the first mapping relationship. As can be seen in the figure, the files that A.exe depends on are libB, libC and D.config. These files are associated files. The associated files will also generate fingerprint nodes correspondingly, which are hashB, hashC and hashD respectively, and originally A. The relationship between the exe file and libB, libC and D.config will also be reflected in the fingerprint nodes formed by it. These fingerprint nodes and the relationships between them constitute a fingerprint tree.

Step S4000: Obtain the version difference between the original system version and the updated system version, and generate a system difference description file based on the version difference, the first mapping relationship and the second mapping relationship.

It should be noted that, in order to achieve more flexible rolling updates, the system update file configuration method in the embodiment of the present application only analyzes and describes the differences between the original system version and the updated system version.

In one embodiment, by obtaining the original system version and the updated system version, an original system description file corresponding to the original system version is generated according to the original system version, the first mapping relationship and the second mapping relationship, and based on the updated system version, the first mapping relationship The mapping relationship and the second mapping relationship generate an update system description file corresponding to the updated system version. Finally, a system difference description file is obtained based on the original system description file and the updated system description file.

In another embodiment, a commit record for version update is obtained, and the version difference is obtained based on the commit record. Compared with the previous embodiment, this embodiment obtains version differences directly based on the submission record, requiring less workload for comparison and analysis of the old and new versions.

It should be noted that the system difference description file describes the difference between the fingerprint trees of the two system versions. The difference in the fingerprint trees can reflect information such as changed source files, changed version files, version file sizes, and the impact of effective configurations. The system difference description file also records the fingerprint tree corresponding to the original system version and the fingerprint tree corresponding to the updated system version. Among them, the fingerprint tree corresponding to the original system version can help the user determine whether the system meets the update conditions when the user performs a system update.

Step S5000: Configure the system update file according to the system difference description file.

It should be noted that system update files usually exist in the form of rolling update packages or rolling upgrade packages, which are convenient for users to download and run.

Figure 4 is a schematic diagram of the configuration process of the system update file provided by the embodiment of the present application, illustrating the configuration steps of the system update file. As shown in the figure, it includes at least steps S5100, S5200 and S5300.

Step S5100: Obtain the system upgrade file according to the system difference description file.

Step S5200: Obtain the system update operation file according to the system upgrade file.

It should be noted that the system update operation file generates upgrade operation steps based on the predefined global upgrade configuration. These upgrade operation steps are recorded in the system update operation file and are used to guide users to update the system according to the upgrade operation steps. .

Step S5300: Configure the system update file according to the system difference description file, system upgrade file and system update operation file.

FIG. 5 is a schematic diagram of difference analysis between the original system version and the updated system version provided by the embodiment of the present application. As shown in the figure, in the code warehouse 510, the submission record of the code warehouse is specified. The version building module 520 builds the system version before and after the submission according to the submission record, obtains the original system version and the updated system version, and combines the original system version and The updated system version is sent to the version analysis module, and the version analysis module 530 generates a version analysis report 540 as required, such as changed source files, changed version files, version file sizes, effects of effective configuration, etc.

Figure 6 is a schematic diagram of the construction process of the version update package provided by the embodiment of the present application. As shown in the figure, the original system version 610, the updated system version 620 and the update policy 630 are submitted. The package building module 640 compares the fingerprint differences of the two versions and generates a fingerprint upgrade tree, that is, corresponding to the system difference description file. The fingerprint upgrade tree includes two The difference description of each version also includes the fingerprint trees of the old and new versions. The package building module obtains the version upgrade file based on the fingerprint upgrade tree. The package building module generates the upgrade operation steps for this upgrade package based on the predefined global upgrade configuration. The package building module makes the fingerprint upgrade tree, version upgrade file, and upgrade configuration into a system. The update package 650 and the system update package 650 can implement rolling updates of the system.

Embodiments of the present application also provide a system update method. The method includes: obtaining a system update file according to the system update file configuration method of the first aspect, and updating the system according to the system update file.

In one embodiment, updating the system according to the system update file includes the following specific process: obtaining the first mapping relationship and the second mapping relationship corresponding to the current system, that is, the fingerprint tree of the current system; and then obtaining the system update file. The first mapping relationship and the second mapping relationship corresponding to the original system version are the fingerprint tree of the original version system, and the two are compared to obtain the comparison result. The purpose of the comparison is to determine whether the current system meets the system update conditions. . If the comparison result is that the update requirements are met, the current system will be updated; if the comparison result is that the update requirements are not met, the current system will not be updated. When performing system updates, the system update module in the current system deploys the fingerprint tree and version files in the system update package, restarts or reloads the relevant processes according to the operating steps in the upgrade configuration to complete the upgrade, and finally checks the upgrade results. Success If it fails, it will be solidified and if it fails, it will roll back.

Figure 7 is a schematic diagram of system update provided by the embodiment of the present application. As shown in the figure, in the system 700 to be updated, there are many programs 710 running, and these program files have corresponding nodes. These nodes and their relationships constitute a fingerprint tree 720. The shaded programs and nodes in the figure correspond to each other.

Figure 8 is a schematic structural diagram of a system update file configuration device provided by an embodiment of the present application. As shown in Figure 8, an embodiment of the present application also provides a precoding configuration device 800, including: at least one processor 820; at least one memory 810, used to store at least one program; when at least one program is processed by at least one When the processor is executed, the above system update file configuration method is implemented.

Figure 9 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As shown in Figure 9, an embodiment of the present application also provides a precoding configuration device 900, including: at least one processor 920; at least one memory 910, used to store One less program; the above system update method is implemented when at least one program is executed by at least one of the processors.

An embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions. The computer-executable instructions are used to execute the system update file configuration method provided in the embodiment of the present application, or, as implemented in the present application. The system update method provided in the example.

An embodiment of the present application also provides a computer program product, which includes a computer program or computer instructions. The computer program or computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium. Programs or computer instructions, the processor executes the computer program or computer instructions, causing the computer device to execute the system update file configuration method provided in any embodiment of the present application, or the system update method provided in the embodiment of the present application.

The system update file configuration method provided by the embodiment of the present application obtains the digital signature of the target file, establishes a first mapping relationship between the digital signature and the target file, and establishes a second mapping relationship between the target file and its associated associated files. The mapping relationship enables the first mapping relationship and the second mapping relationship to form a fingerprint model of the system version, which can obtain a system difference description file that accurately describes the update of the system version, so that the system update file can be based on the system difference description file. The configuration makes the system update files more lightweight, accurate and flexible, realizes the rolling release capability of system versions, optimizes the user experience, and improves the work efficiency of product managers and system maintenance personnel.

Those of ordinary skill in the art can understand that all or some steps in the methods, systems, and functional modules/modules in the devices disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof.

In hardware implementations, the division between functional modules/modules mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. Components execute cooperatively. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is known to those of ordinary skill in the art, the term computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, tapes, disk storage or other magnetic storage devices, or may Any other medium used to store the desired information and that can be accessed by a computer. Additionally, it is known to those of ordinary skill in the art that communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

The terms "component", "module", "system", etc. used in this specification are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process, processor, object, executable file, thread of execution, program or computer running on a processor. Through the illustrations, both applications running on the computing device and the computing device may be components. One or more components can reside in a process or thread of execution, and the component can be localized on one computer or distributed between 2 or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon. A component may, for example, be based on data having one or more data packets (e.g., data from two components interacting with another component, such as a local system, a distributed system, or a network, e.g., via Signals (Internet for interacting with other systems) Signals are communicated through local or remote processes.

Some embodiments of the present application have been described above with reference to the accompanying drawings, but the scope of rights of the present application is not thereby limited. Any modifications, equivalent substitutions and improvements made by those skilled in the art without departing from the scope and essence of this application shall be within the scope of rights of this application.

Claims (11)

A system update file configuration method includes: Obtain a target file and at least one associated file associated with the target file, where the target file is a file involved in the system update; Obtain the digital signature of the target file, and establish a first mapping relationship between the digital signature and the target file; Establish a second mapping relationship between the target file and each of the associated files; Obtain the version difference between the original system version and the updated system version, and generate a system difference description file based on the version difference, the first mapping relationship and the second mapping relationship; Configure the system update file according to the system difference description file. The system update file configuration method according to claim 1, wherein said obtaining the digital signature of the target file includes: According to the national secret signature algorithm, the digital signature of the target file is obtained. The system update file configuration method according to claim 1 or 2, wherein said obtaining the digital signature of the target file includes: Obtain at least one source file corresponding to the target file; The digital signature of the target file is generated based on all of the source files. The system update file configuration method according to claim 1, wherein said obtaining the version difference between the original system version and the updated system version, and based on the version difference, the first mapping relationship and the second mapping Relationship, generate system difference description file, including: Obtain the original system version, and generate an original system description file corresponding to the original system version according to the original system version, the first mapping relationship, and the second mapping relationship; Obtain an update system version, and generate an update system description file corresponding to the update system version according to the update system version, the first mapping relationship, and the second mapping relationship; According to the original system description file and the updated system description file, a system difference description file is obtained. The system update file configuration method according to claim 1, wherein said obtaining the version difference between the original system version and the updated system version includes: Get the commit record used for version update; According to the submission record, the version difference is obtained. The system update file configuration method according to claim 1, wherein said configuring the system update file according to the system difference description file includes: Obtain a system upgrade file according to the system difference description file; Obtain the system update operation file according to the system upgrade file; The system update file is configured according to the system difference description file, the system upgrade file and the system update operation file. A system update method includes: According to the system update file configuration method according to any one of claims 1 to 6, the system update file is obtained; The system is updated according to the system update file. The system update method according to claim 7, wherein updating the system according to the system update file includes: Obtain the first mapping relationship and the second mapping relationship corresponding to the current system; Obtain the first mapping relationship and the second mapping relationship corresponding to the original system version in the system update file; Compare the first mapping relationship and the second mapping relationship corresponding to the current system with the first mapping relationship and the second mapping relationship corresponding to the original system version to obtain a comparison result; If the comparison result meets the update requirements, the current system is updated. A system update file configuration device, including: at least one processor; At least one memory for storing at least one program; The system update file configuration method according to any one of claims 1 to 6 is implemented when at least one of the programs is executed by at least one of the processors. An electronic device including: at least one processor; At least one memory for storing at least one program; The system update method according to any one of claims 7 or 8 is implemented when at least one of the programs is executed by at least one of the processors. A computer-readable storage medium that stores a processor-executable program. When the processor-executable program is executed by the processor, the system update file configuration method as described in any one of claims 1 to 6 is implemented. , or, the system update method according to any one of claims 7 or 8.