A method, apparatus and electronic device for managing Kylin operating system software

Abstract

This application belongs to the field of information security technology, specifically relating to a method, apparatus, and electronic device for managing software in the Kylin operating system, aiming to solve the problem of preventing software information in the Kylin operating system from being tampered with. The method includes: acquiring software feature information, including software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of files contained in the software; constructing a metadata feature matrix; constructing a file feature matrix; determining whether the software is the same based on the metadata feature matrix and the file feature matrix; if they are the same, modifying the software identifier, software name, and software package name of the later-installed software to those of the earlier-installed software. The Kylin operating system software management method and apparatus provided in this application can effectively prevent software tampering and solve the problem of incorrect classification after software has been tampered with.

Description

Technical Field

[0001] This invention belongs to the field of information security technology, specifically relating to a method, device, and electronic device for managing Kylin operating system software, as well as a computer-readable storage medium. Background Technology

[0002] In domestically produced Kylin operating systems such as Kylin V10, standard software uses the deb format. The installation and management of related software are usually achieved through apt or dpkg (Debian Packager) managers. Among them, dpkg manager is a lower-level software installation and management tool compared to apt.

[0003] In the existing technology, the aforementioned apt and dpkg managers can realize basic management functions such as installation, upgrade and uninstallation of software on the computer, but they are significantly lacking in the level of refined management of software assets. Specifically, they lack the ability to classify and inventory software assets and generate software asset reports, and they do not have the ability to manage software compliance, thus failing to meet users' needs in terms of software asset control and compliance audit.

[0004] Furthermore, the dpkg manager has the function of unpacking and repackaging existing deb software, which allows for the modification of information contained within the deb software. Currently, traditional software classification methods based on dpkg or apt software managers are limited to the deb software information provided by the software manager. In this case, if the deb software information is modified, traditional software classification methods will fail to correctly categorize the software, thus affecting the accuracy and reliability of software management. Summary of the Invention

[0005] To address the aforementioned technical problems in the prior art, namely how to prevent software information in the Kylin operating system from being tampered with, this application provides a Kylin operating system software management method, apparatus, and electronic device.

[0006] In a first aspect of this application, a software management method for the Kylin operating system is provided, comprising:

[0007] Obtain the software's characteristic information, which includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The characteristic information is represented as a string composed of ASCII printable characters.

[0008] Construct a metadata feature matrix, wherein the elements of the metadata feature matrix are characters, the metadata feature matrix has 4 rows, the software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix, and the number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version;

[0009] Construct a file feature matrix, where each row of the file feature matrix corresponds one-to-one with a file, and each row of the file feature matrix corresponds to a file feature string of the file. The file feature string is a string composed of the file name and file size concatenated together. The row order of the matrix corresponding to the file feature string is equal to the order of the file feature string in the file feature sequence. The file feature sequence is composed of all file feature strings corresponding to all files arranged in ascending order of their corresponding ASCII codes. The number of columns in the file feature matrix is ​​equal to the maximum value among the string lengths of all file feature strings.

[0010] Based on the metadata feature matrix and the file feature matrix, determine whether the first software and the second software are the same;

[0011] If the first software is the same as the second software, the software identifier, software name, and software package name of the second software shall be modified to the software identifier, software name, and software package name of the first software, respectively, and the installation time of the first software shall be earlier than the installation time of the second software.

[0012] Optionally, elements in the metadata feature matrix and the file feature matrix that do not have a corresponding character are set to blank.

[0013] Optionally, the file feature string is composed of the file name, the character "+", and the file size concatenated in sequence.

[0014] Optionally, determining whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix includes:

[0015] Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference.

[0016] If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, the first row of the first file feature matrix is ​​aligned with each row of the second file feature matrix in turn, and the first column of the first file feature matrix is ​​kept aligned with the first column of the second file feature matrix.

[0017] If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix.

[0018] During each alignment, the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix is ​​calculated, and the second element with a non-zero difference is recorded.

[0019] Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix.

[0020] Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix;

[0021] If the feature change value is less than or equal to a preset change threshold, the first software is determined to be the same as the second software; otherwise, the first software is determined to be different from the second software.

[0022] Optionally, the Kylin operating system software management method further includes:

[0023] Based on the software's feature information and the software compliance database, the compliance attributes of the software are determined. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted.

[0024] If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant.

[0025] If the software's compliance attribute indicates that installation is prohibited, then the software is deemed to be in violation of regulations.

[0026] If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation.

[0027] If the software's compliance attribute is that it must be installed and the software's installation status is that it is not installed or has been deleted, then the software is determined to be in violation of regulations.

[0028] If the software's compliance attribute is "must be installed," the software's installation status is "installed," and the software version is outside the version constraint range, then the software is determined to be in violation.

[0029] Optionally, the Kylin operating system software management method further includes:

[0030] If the software's compliance attributes are "allowed to install" or "required to install" and the software version is outside the scope of the version constraints, then the software version is determined to be in violation.

[0031] Optionally, the Kylin operating system software management method further includes:

[0032] If the software violates the rules, a software violation alert will be displayed; and,

[0033] If the software version is in violation, a software version violation warning will be displayed.

[0034] Optionally, the Kylin operating system software management method further includes:

[0035] The software is classified according to its feature information and a software classification database. The software classification database includes software identifiers and corresponding software classification names, including application software, office software, entertainment software, and security software.

[0036] Optionally, the Kylin operating system software management method further includes:

[0037] A software asset report is generated based on the software's classification and characteristic information.

[0038] In a second aspect of this application, a Kylin operating system software management device is provided, comprising:

[0039] The software feature information acquisition module is used to acquire the feature information of the software. The feature information includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters.

[0040] A metadata feature matrix construction module is used to construct a metadata feature matrix. The elements of the metadata feature matrix are characters. The metadata feature matrix has 4 rows. The software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix. The number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version.

[0041] The file feature matrix construction module is used to construct a file feature matrix. The rows of the file feature matrix correspond one-to-one with the files, and the rows of the file feature matrix correspond to the file feature strings of the files. The file feature strings are strings composed of the file name and file size of the files. The row order of the matrix corresponding to the file feature strings is equal to the order of the file feature strings in the file feature sequence. The file feature sequence is composed of the file feature strings corresponding to all files arranged in ascending order according to their corresponding ASCII codes. The number of columns of the file feature matrix is ​​equal to the maximum value among the string lengths of all the file feature strings.

[0042] The software comparison module is used to determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix;

[0043] The software correction module is used to modify the software identifier, software name, and software package name of the second software to the software identifier, software name, and software package name of the first software, respectively, if the first software is the same as the second software, wherein the installation time of the first software is earlier than the installation time of the second software.

[0044] Optionally, elements in the metadata feature matrix and the file feature matrix that do not have a corresponding character are set to blank.

[0045] Optionally, the software comparison module is specifically used for:

[0046] Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference.

[0047] If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, the first row of the first file feature matrix is ​​aligned with each row of the second file feature matrix in turn, and the first column of the first file feature matrix is ​​kept aligned with the first column of the second file feature matrix.

[0048] If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix.

[0049] During each alignment, the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix is ​​calculated, and the second element with a non-zero difference is recorded.

[0050] Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix.

[0051] Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix;

[0052] If the feature change value is less than or equal to a preset change threshold, the first software is determined to be the same as the second software; otherwise, the first software is determined to be different from the second software.

[0053] Optionally, the Kylin operating system software management device further includes a compliance management module, which is used for:

[0054] Based on the software's feature information and the software compliance database, the compliance attributes of the software are determined. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted.

[0055] If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant.

[0056] If the software's compliance attribute indicates that installation is prohibited, then the software is deemed to be in violation of regulations.

[0057] If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation.

[0058] If the software's compliance attribute is that it must be installed and the software's installation status is that it is not installed or has been deleted, then the software is determined to be in violation of regulations.

[0059] If the software's compliance attribute is "must be installed," the software's installation status is "installed," and the software version is outside the version constraint range, then the software is determined to be in violation.

[0060] Optionally, the compliance management module is also used for:

[0061] If the software's compliance attributes are "allowed to install" or "required to install" and the software version is outside the scope of the version constraints, then the software version is determined to be in violation.

[0062] Optionally, the Kylin operating system software management device further includes an alarm module, which is used for:

[0063] If the software violates the rules, a software violation alert will be displayed; and,

[0064] If the software version is in violation, a software version violation warning will be displayed.

[0065] Optionally, the Kylin operating system software management device further includes a classification module, which is used for:

[0066] The software is classified according to its feature information and a software classification database. The software classification database includes software identifiers and corresponding software classification names, including application software, office software, entertainment software, and security software.

[0067] Optionally, the Kylin operating system software management device further includes a software asset report generation module, used for:

[0068] A software asset report is generated based on the software's classification and characteristic information.

[0069] In a third aspect of this application, an electronic device is provided, comprising:

[0070] At least one processor; and a memory communicatively connected to at least one of the processors; wherein the memory stores instructions executable by the processor to implement the Kylin operating system software management method described above.

[0071] In a fourth aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for execution by the computer to implement the above-described Kylin operating system software management method.

[0072] In a fifth aspect of this application, a computer program product containing instructions is provided, which, when executed by a computer device, causes the computer device to perform the Kylin operating system software management method described above.

[0073] The Kylin operating system software management method and apparatus provided in this application utilize software feature information to construct a comparison matrix to determine whether the software has changed. For changed software, historical software information is used to correct the changes, thereby preventing software tampering. This also solves the problem that traditional software classification methods cannot correctly classify software after it has been tampered with. Furthermore, it improves the accuracy of software compliance determination and addresses the lack of software compliance management and software asset reporting in the Kylin operating system. Attached Figure Description

[0074] Figure 1 This is a flowchart illustrating one implementation of the Kylin operating system software management method of this application;

[0075] Figure 2 This is a flowchart illustrating another implementation of the Kylin operating system software management method of this application;

[0076] Figure 3 This is a structural block diagram of one embodiment of the Kylin operating system software management device of this application;

[0077] Figure 4 This is a structural block diagram of another embodiment of the Kylin operating system software management device of this application. Detailed Implementation

[0078] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description, in conjunction with the accompanying drawings and examples, further clarifies this application. It should be understood that the specific examples described herein are merely illustrative and not intended to limit the scope of this application. Furthermore, the technical features involved in the various embodiments of this application described below can be combined with each other as long as they do not conflict with each other.

[0079] The present application will now be described in detail with reference to the accompanying drawings. A first aspect of this application provides a software management method for the Kylin operating system. Figure 1 The diagram illustrates a flowchart of one embodiment of the Kylin operating system software management method of this application. Figure 1 As shown, the Kylin operating system software management method of the first embodiment of this application includes:

[0080] Step S101: Obtain the feature information of the software, which includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters.

[0081] Step S102: Construct a metadata feature matrix. The elements of the metadata feature matrix are characters. The metadata feature matrix has 4 rows. The software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix. The number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version.

[0082] Step S103: Construct a file feature matrix, wherein each row of the file feature matrix corresponds to a file, and each row of the file feature matrix corresponds to a file feature string of the file. The file feature string is a string composed of the file name and file size of the file. The row order of the matrix corresponding to the file feature string is equal to the order of the file feature string in the file feature sequence. The file feature sequence is composed of the file feature strings corresponding to all files arranged in ascending order according to their corresponding ASCII codes. The number of columns in the file feature matrix is ​​equal to the maximum value among the string lengths of all the file feature strings.

[0083] Step S104: Determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix;

[0084] Step S105: If the first software is the same as the second software, modify the software identifier, software name, and software package name of the second software to the software identifier, software name, and software package name of the first software, respectively. The installation time of the first software is earlier than the installation time of the second software.

[0085] The software management method for the Kylin operating system provided in this application is applied to the Kylin operating system, such as Kylin V10, and is suitable for managing deb format files in the Kylin system. The method reuses the data interface of the Kylin system dpkg manager for managing software installation, upgrades, uninstallation, and software information collection, thereby enabling information collection and monitoring of the installation process of deb software on the Kylin operating system. For ease of use, deb software will be referred to as "software" below. The deb format is the standard software format for the Kylin operating system; therefore, deb software encompasses all types of software in the Kylin operating system.

[0086] Specifically, in step S101, the software's characteristic information can be obtained through the data interface of the dpkg manager. This characteristic information includes the software identifier, software name, package name, software version, software installation time, and the filenames and sizes of the files contained within the software, i.e., the filenames and sizes in the file list released by the package. All characteristic information is represented as strings composed of ASCII printable characters; for example, the software name is represented as the string "WPS", the filename as the string "photo", and the file size uses the same unit, such as KB. For example, a file size of 100KB is represented as the string "100KB".

[0087] Specifically, in step S102, the metadata feature matrix is ​​a matrix composed of character elements, with its rows representing the software identifier, software name, software package name, and software version, respectively. Each row represents a string, and the matrix elements are the characters within those strings. For example, the first row of the metadata feature matrix is ​​the software identifier, the second row is the software name, the third row is the software package name, and the fourth row is the software version. The number of columns in the metadata feature matrix is ​​equal to the maximum length among the strings representing the software identifier, software name, software package name, and software version—that is, the longest string among the four rows. Since the lengths of the four strings may not be the same, for strings shorter than the maximum length, some elements in their corresponding matrix rows will lack corresponding characters. These elements can be filled with whitespace or other specific characters.

[0088] Specifically, in step S103, the filename and file size of the software files are concatenated to form a file feature string. For example, if the filename is "photo" and the file size is "100K", a concatenation operator "+" can be added to form the file feature string "photo+100K". Alternatively, no concatenation operator can be added, or other concatenation operators can be used. All file feature strings corresponding to all files are arranged in ascending order according to their corresponding ASCII codes to form a file feature sequence. Then, a file feature matrix is ​​constructed, with the strings in the file feature sequence serving as rows in the file feature matrix, ensuring a one-to-one correspondence between the rows of the file feature matrix and the file feature strings (i.e., a one-to-one correspondence with the files). The row order of the file feature strings in the file feature matrix is ​​equal to their order in the file feature sequence. For example, the file feature string that appears first is in the first row of the file feature matrix, the file feature string that appears second is in the second row, and so on. The number of columns in the file feature matrix is ​​equal to the length of the longest file feature string. Since the length of file feature strings varies, for file feature strings whose length is less than the maximum length value, some elements in the matrix row will be missing corresponding characters. Similarly, these elements can be filled with whitespace characters or other specific characters.

[0089] Specifically, in step S104, the similarity of two software programs (represented as the first software and the second software) is determined based on the metadata feature matrix and the file feature matrix. The two software programs can be designated software for comparison, or any two software programs compared during a scan of software within the operating system. Specifically, step S104 may include:

[0090] Step S1041: Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference.

[0091] Step S1042: If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, align the first row of the first file feature matrix with each row of the second file feature matrix in turn, and keep the first column of the first file feature matrix aligned with the first column of the second file feature matrix.

[0092] Step S1043: If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix.

[0093] Step S1043: During each alignment, calculate the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix, and record the second element with a non-zero difference.

[0094] Step S1044: Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix.

[0095] Step S1045: Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix;

[0096] Step S1046: If the feature change value is less than or equal to a preset change threshold, determine that the first software and the second software are the same; otherwise, determine that the first software and the second software are different.

[0097] Specifically, in step S104, the metadata feature matrices and file feature matrices of the two software programs are compared. Specifically, comparing the metadata feature matrices of the two software programs can be achieved by subtracting them, and recording the first non-zero element in the resulting matrix where the difference is non-zero. This recording includes recording the value of the first element and its position (row and column). The subtraction can be either subtracting the second metadata matrix from the first metadata matrix, or subtracting the first metadata matrix from the second metadata matrix.

[0098] Specifically, when comparing file feature matrices, since the number of files contained in the two software programs may differ, the sizes of the two file feature matrices may also differ. Therefore, a moving comparison method is adopted. Specifically, the first row of the file feature matrix with fewer rows is aligned sequentially with each row of the file feature matrix with more rows, starting from the first row of the file feature matrix with more rows, while always keeping the first columns of the two file feature matrices aligned. Each time the alignment is performed, the elements in the intersection of the two file feature matrices are subtracted, that is, the ASCII code difference between the elements in the intersection is calculated, and the second element that is not zero after each calculation is recorded. The record includes recording the value of the second element and the position of the second element, that is, the row and column where the second element is located. The subtraction can be the element in the first file feature matrix minus the element in the second file feature matrix, or the element in the second file feature matrix minus the element in the first file feature matrix.

[0099] Specifically, all second elements can be recorded in a set. After obtaining the set of second elements, a new matrix is ​​created. The size of the new matrix is ​​the same as the larger of the first and second document feature matrices. Elements in the new matrix that occupy the same positions as all second elements are set to 0, and elements in other positions are set to 1. It should be noted that the new matrix can also be obtained first, followed by the first elements. This application does not limit the order in which the new matrix and the first elements are obtained.

[0100] Specifically, after obtaining all the first elements and the new matrix, the sum of the number of first elements and the number of elements with a value of 1 in the new matrix is ​​calculated as the feature change value. Then, the feature change value is compared with a preset threshold. If the feature change value is less than or equal to the preset threshold, the first software and the second software are determined to be the same; otherwise, the first software and the second software are determined to be different.

[0101] Specifically, in step S105, if the first software and the second software are the same, the software identifier, software name, and software package name of the software with a later installation time are replaced with the software identifier, software name, and software package name of the software with an earlier installation time. This completes the information correction for the software with a later installation time, thereby preventing the software information from being tampered with. In step S105, the software with an earlier installation time is recorded as the first software. The installation time of the first software is earlier than that of the second software. Here, "first" for the first software and "second" for the second software are only used to distinguish different software and are not a limitation on the software or the order of software installation time. Those skilled in the art can easily understand that the software with an earlier installation time can also be recorded as the second software. For example, in one possible implementation, if the installation time of the first software is earlier than the installation time of the second software, then the feature information such as the software identifier, software name, and software package name of the second software is replaced with the corresponding feature information in the first software; if the installation time of the first software is earlier than the installation time of the second software, then the feature information such as the software identifier, software name, and software package name of the second software is replaced with the corresponding feature information in the first software; if the installation time of the second software is later than the installation time of the first software, then the feature information such as the software identifier, software name, and software package name of the first software is replaced with the corresponding feature information in the second software.

[0102] Figure 2 A flowchart illustrating another embodiment of the video human behavior recognition method of this application is shown, such as... Figure 2 As shown, the video human behavior recognition method of the second embodiment of this application includes:

[0103] Step S201: Obtain the feature information of the software, which includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters.

[0104] Step S202: Construct the metadata feature matrix;

[0105] Step S203: Construct the file feature matrix;

[0106] Step S204: Determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix;

[0107] Step S205: If the first software is the same as the second software, modify the software identifier, software name and software package name of the second software to the software identifier, software name and software package name of the first software, respectively. The installation time of the first software is earlier than the installation time of the second software.

[0108] Step S206: Determine whether the second software is compliant;

[0109] Step S207: If the second software violates the rules, display a software violation alarm; and if the software version of the second software violates the rules, display a software version violation alarm.

[0110] Step S208: Classify the second software;

[0111] Step S209: Generate a software asset report based on the classification and characteristic information of all software.

[0112] Specifically, steps S201-S205 can refer to steps S101-S105.

[0113] Specifically, in step S206, after correcting the second software installed later, it is determined whether the second software is compliant. Software compliance refers to the software management standards established during the software asset management process, including which software is allowed to be installed, prohibited from installation, or required to be installed. Software that is allowed to be installed is defined as compliant; software that is prohibited from installation is defined as non-compliant; software that is required to be installed is defined as compliant if it is actually installed on the computer, and non-compliant if it is not actually installed on the computer. In addition, software compliance can also include software version compliance, that is, restricting the software version range. If the software version of the software already installed on the computer is within the version constraint range, it is defined as compliant; if the software version of the software already installed on the computer is not within the version constraint range, it is defined as non-compliant. Specifically, step S206 may include:

[0114] Step S2061: Determine the compliance attributes of the software based on the software's feature information and the software compliance database. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted.

[0115] Step S2062: If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then determine that the software is compliant.

[0116] Step S2063: If the compliance attribute of the software is prohibited from installation, the software is determined to be in violation of regulations;

[0117] Step S2064: If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation.

[0118] Step S2065: If the software's compliance attribute is "must be installed" and the software's installation status is "not installed" or "deleted", then the software is determined to be in violation.

[0119] Step S2066: If the software's compliance attribute is "must be installed", the software's installation status is "installed", and the software version is outside the version constraint range, then the software is determined to be in violation.

[0120] Step S2067: If the compliance attribute of the software is "allowed to install" or "required to install" and the software version of the software is outside the scope of the version constraint, determine that the software version is in violation.

[0121] Specifically, in step S206, the software compliance database is a pre-established database, which includes the software identifier and corresponding software version, as well as the corresponding software compliance attributes and version constraint scope. The software's characteristic information also includes the software's installation status. The compliance attributes include allowed installation, prohibited installation, and mandatory installation, and the installation status includes installed, not installed, and deleted. Specifically, in step S206, the software compliance database can be searched by the software identifier to obtain the corresponding compliance attributes and version constraint scope. Then, based on the software's installation status, software version, and compliance attributes, it is determined whether the software and version are compliant; non-compliance is considered a violation.

[0122] Specifically, in step S206, software (including the second software) compliance includes: if the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant. Software non-compliance includes: if the software's compliance attribute is "prohibited to install," then the software is determined to be non-compliant; if the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, then the software is determined to be non-compliant; if the software's compliance attribute is "required to install" and the software's installation status is "not installed" or "deleted," then the software is determined to be non-compliant; if the software's compliance attribute is "required to install," the software's installation status is "installed," and the software version is outside the version constraint range, then the software is determined to be non-compliant. Software version non-compliance includes: if the software's compliance attribute is "allowed to install" or "required to install," and the software version is outside the version constraint range, then the software version is determined to be non-compliant. Specifically, in step S107, if there is a software non-compliance or a software version non-compliance, an alarm message can be displayed.

[0123] Specifically, in addition to assessing software compliance, software can also be categorized. In step S108, the software classification database is a pre-established database, which includes software identifiers and corresponding software classification names. Software classifications can be obtained by searching the software classification database based on the software identifier. Further, in step S109, a software asset report can be generated based on the classification and characteristic information of all software. This software asset report is used to summarize and statistically analyze the software assets in the operating system. It can include various software classifications, such as which software is included in application software, etc. The software asset report can also include software compliance statistics, such as which software is compliant and which is non-compliant. Existing software asset reports can be referenced for this purpose, and therefore will not be elaborated further.

[0124] The software's characteristic information may also include software installation time, software deletion time, and installation status. Step S107 further allows for the generation of alarms based on these factors, such as software installation alarms, unauthorized software uninstallation alarms, and alarms for not installing required software. For example, if the software's installation status is "not installed" but it is in the process of installation, an installation alarm is generated; if the software's installation status is "not installed" and its compliance attribute is "required installation," an alarm for not installing required software is generated; if the software's installation status is "deleted" and its compliance attribute is "required installation," an unauthorized uninstallation alarm is generated. Users can configure various alarms based on these settings.

[0125] Making corrections to the software before determining compliance and / or classification can make the compliance assessment and classification more accurate. It should be noted that in this embodiment, the compliance assessment and classification of the second software with a later installation date is used to illustrate the processing of new software; the compliance assessment and classification of the first software with an earlier installation date have already been performed. Those skilled in the art will readily understand that the aforementioned compliance assessment and classification can be applied to all software.

[0126] It should be noted that the software compliance judgment and classification can be performed by only one of them, or both. This implementation method provides an example of performing both.

[0127] This application provides a software management method for the Kylin operating system. By acquiring the characteristic information of the software and constructing a comparison matrix, it can determine whether the software has changed. For the software that has changed, it can be corrected based on historical software information, thereby preventing software tampering. This not only solves the problem that traditional software classification methods cannot accurately classify software after the software information has been tampered with, but also improves the accuracy of software compliance judgment. At the same time, it makes up for the deficiencies of the Kylin operating system in software compliance management functions and software asset report generation.

[0128] A second aspect of this application provides a Kylin operating system software management device. Figure 3 This application shows a structural block diagram of one embodiment of the Kylin operating system software management device, as follows: Figure 3 As shown, the Kylin operating system software management device of the third embodiment of this application includes:

[0129] The software feature information acquisition module 301 is used to acquire the feature information of the software. The feature information includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters.

[0130] Metadata feature matrix construction module 302 is used to construct a metadata feature matrix. The elements of the metadata feature matrix are characters. The metadata feature matrix has 4 rows. The software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix. The number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version.

[0131] The file feature matrix construction module 303 is used to construct a file feature matrix. The rows of the file feature matrix correspond one-to-one with the files, and the rows of the file feature matrix correspond to the file feature strings of the files. The file feature strings are strings composed of the file name and file size of the files. The row order of the matrix corresponding to the file feature strings is equal to the order of the file feature strings in the file feature sequence. The file feature sequence is composed of the file feature strings corresponding to all files arranged in ascending order according to their corresponding ASCII codes. The number of columns of the file feature matrix is ​​equal to the maximum value among the string lengths of all the file feature strings.

[0132] Software comparison module 304 is used to determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix;

[0133] The software correction module 305 is used to modify the software identifier, software name, and software package name of the second software to the software identifier, software name, and software package name of the first software, respectively, if the first software is the same as the second software, wherein the installation time of the first software is earlier than the installation time of the second software.

[0134] In the metadata feature matrix and the file feature matrix, elements without corresponding characters can be set to blank. The file feature string can be composed of the file name, the character "+", and the file size concatenated sequentially.

[0135] Specifically, the software comparison module can be used for:

[0136] Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference.

[0137] If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, the first row of the first file feature matrix is ​​aligned with each row of the second file feature matrix in turn, and the first column of the first file feature matrix is ​​kept aligned with the first column of the second file feature matrix.

[0138] If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix.

[0139] During each alignment, the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix is ​​calculated, and the second element with a non-zero difference is recorded.

[0140] Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix.

[0141] Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix;

[0142] If the feature change value is less than or equal to a preset change threshold, the first software is determined to be the same as the second software; otherwise, the first software is determined to be different from the second software.

[0143] Figure 4 This application shows a structural block diagram of another embodiment of the Kylin operating system software management device, such as... Figure 4 As shown, the Kylin operating system software management device of the fourth embodiment of this application includes:

[0144] The software feature information acquisition module 401 is used to acquire the feature information of the software. The feature information includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters.

[0145] Metadata feature matrix construction module 402 is used to construct the metadata feature matrix;

[0146] File feature matrix construction module 403, used to construct file feature matrix;

[0147] Software comparison module 404 is used to determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix;

[0148] The software correction module 405 is used to modify the software identifier, software name and software package name of the second software to the software identifier, software name and software package name of the first software respectively if the first software is the same as the second software, wherein the installation time of the first software is earlier than the installation time of the second software.

[0149] The compliance management module 406 is used to determine the compliance of the second software based on the software's feature information and the software compliance database.

[0150] The alarm module 407 is used to display a software violation alarm if the software violates the rules; and to display a software version violation alarm if the software version violates the rules.

[0151] The classification module 408 classifies the software according to its feature information and a software classification database. The software classification database includes software identifiers and corresponding software classification names. The software classification names include application software, office software, entertainment software, and security software.

[0152] The software asset report generation module 409 is used to generate a software asset report based on the classification of the software and the characteristic information of the software.

[0153] Specifically, the compliance management module is used for:

[0154] Based on the software's feature information and the software compliance database, the compliance attributes of the software are determined. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted.

[0155] If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant.

[0156] If the software's compliance attribute indicates that installation is prohibited, then the software is deemed to be in violation of regulations.

[0157] If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation.

[0158] If the software's compliance attribute is that it must be installed and the software's installation status is that it is not installed or has been deleted, then the software is determined to be in violation of regulations.

[0159] If the software's compliance attribute is "must be installed," the software's installation status is "installed," and the software version is outside the version constraint range, then the software is determined to be in violation.

[0160] Specifically, in one possible implementation, the compliance management module is further used for:

[0161] If the software's compliance attributes are "allowed to install" or "required to install" and the software version is outside the scope of the version constraints, then the software version is determined to be in violation.

[0162] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process and related descriptions of the system described above can be referred to the corresponding processes in the foregoing method embodiments, and therefore will not be repeated here.

[0163] This application provides a software management device for the Kylin operating system. It establishes a comparison matrix based on the software's characteristic information to determine whether the software has changed. For software that has changed, it corrects the information based on historical software information, thereby achieving the prevention and control of software tampering. This solves the problem that traditional software classification methods are difficult to classify accurately after software information has been tampered with. At the same time, it improves the accuracy of software compliance determination and provides a better foundation for the software compliance management function and software asset report generation function on the Kylin operating system.

[0164] It should be noted that the Kylin operating system software management device provided in the above embodiments is only an example of the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the modules or steps in the embodiments of this application can be further decomposed or combined. For example, the modules in the above embodiments can be merged into one module, or further divided into multiple sub-modules to complete all or part of the functions described above. The names of the modules and steps involved in the embodiments of this application are only for distinguishing the various modules or steps and are not considered as an improper limitation of this application.

[0165] In a third aspect of this application, an electronic device is also provided, the electronic device comprising: at least one processor; and a memory communicatively connected to at least one of the processors; wherein the memory stores instructions executable by the processor, the instructions being executed by the processor to implement the above-described video human behavior recognition method.

[0166] In a fourth aspect of this application, a computer-readable storage medium is also provided, the computer-readable storage medium storing computer instructions for execution by the computer to implement the above-described video human behavior recognition method.

[0167] In a fourth aspect of this application, a computer program product comprising instructions is also provided, which, when executed by a computer device, causes the computer device to perform the video human behavior recognition method described above.

[0168] Those skilled in the art will recognize that the modules and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. The programs corresponding to the software modules and method steps can be placed in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. To clearly illustrate the interchangeability of electronic hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in electronic hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0169] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0170] The terms “first”, “second”, etc., are used to distinguish similar objects, not to describe or indicate a specific order or sequence.

[0171] The term "comprising" or any other similar term is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus / device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent in such process, method, article, or apparatus / device.

[0172] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A software management method for the Kylin operating system, characterized in that, include: Obtain the software's characteristic information, which includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The characteristic information is represented as a string composed of ASCII printable characters. Construct a metadata feature matrix, wherein the elements of the metadata feature matrix are characters, the metadata feature matrix has 4 rows, the software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix, and the number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version; Construct a file feature matrix, where each row of the file feature matrix corresponds one-to-one with a file, and each row of the file feature matrix corresponds to a file feature string of the file. The file feature string is a string composed of the file name and file size concatenated together. The row order of the matrix corresponding to the file feature string is equal to the order of the file feature string in the file feature sequence. The file feature sequence is composed of all file feature strings corresponding to all files arranged in ascending order of their corresponding ASCII codes. The number of columns in the file feature matrix is ​​equal to the maximum value among the string lengths of all file feature strings. Based on the metadata feature matrix and the file feature matrix, determine whether the first software and the second software are the same; If the first software is the same as the second software, the software identifier, software name and software package name of the second software shall be modified to the software identifier, software name and software package name of the first software, respectively, and the installation time of the first software shall be earlier than the installation time of the second software. Based on the software's feature information and the software compliance database, the compliance attributes of the software are determined. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted. If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant. If the software's compliance attribute indicates that installation is prohibited, then the software is deemed to be in violation of regulations. If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation. If the software's compliance attribute is that it must be installed and the software's installation status is that it is not installed or has been deleted, then the software is determined to be in violation of regulations. If the software's compliance attribute is "must be installed", the software's installation status is "installed", and the software version is outside the version constraint range, then the software is determined to be in violation. The step of determining whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix includes: Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference. If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, the first row of the first file feature matrix is ​​aligned with each row of the second file feature matrix in turn, and the first column of the first file feature matrix is ​​kept aligned with the first column of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix. During each alignment, the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix is ​​calculated, and the second element with a non-zero difference is recorded. Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix. Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix; If the feature change value is less than or equal to a preset change threshold, the first software is determined to be the same as the second software; otherwise, the first software is determined to be different from the second software.

2. The method as described in claim 1, characterized in that, Also includes: If the software's compliance attributes are "allowed to install" or "required to install" and the software version is outside the scope of the version constraints, then the software version is determined to be in violation.

3. The method as described in claim 1, characterized in that, Also includes: The software is classified according to its feature information and a software classification database. The software classification database includes software identifiers and corresponding software classification names. The software classification names include application software, office software, entertainment software, and security software. A software asset report is generated based on the software's classification and characteristic information.

4. A software management device for the Kylin operating system, characterized in that, include: The software feature information acquisition module is used to acquire the feature information of the software. The feature information includes the software identifier, software name, software package name, software version, software installation time, and the file names and file sizes of the files contained in the software. The feature information is represented as a string composed of ASCII printable characters. A metadata feature matrix construction module is used to construct a metadata feature matrix. The elements of the metadata feature matrix are characters. The metadata feature matrix has 4 rows. The software identifier, the software name, the software package name, and the software version are each a row in the metadata feature matrix. The number of columns in the metadata feature matrix is ​​equal to the maximum value among the string lengths of the software identifier, the software name, the software package name, and the software version. The file feature matrix construction module is used to construct a file feature matrix. The rows of the file feature matrix correspond one-to-one with the files, and the rows of the file feature matrix correspond to the file feature strings of the files. The file feature strings are strings composed of the file name and file size of the files. The row order of the matrix corresponding to the file feature strings is equal to the order of the file feature strings in the file feature sequence. The file feature sequence is composed of the file feature strings corresponding to all files arranged in ascending order according to their corresponding ASCII codes. The number of columns of the file feature matrix is ​​equal to the maximum value among the string lengths of all the file feature strings. The software comparison module is used to determine whether the first software and the second software are the same based on the metadata feature matrix and the file feature matrix; The software correction module is used to modify the software identifier, software name, and software package name of the second software to the software identifier, software name, and software package name of the first software, respectively, if the first software is the same as the second software, and the installation time of the first software is earlier than the installation time of the second software. The compliance management module is used for: Based on the software's feature information and the software compliance database, the compliance attributes of the software are determined. The software compliance database includes the software identifier, software version, and corresponding version constraint scope and compliance attributes. The compliance attributes include allowed installation, prohibited installation, and mandatory installation. The software's feature information also includes the installation status, which includes installed, not installed, and deleted. If the software's compliance attribute is "allowed to install" and the software version is within the version constraint range, or if the software's compliance attribute is "required to install," the software version is within the version constraint range, and the software's installation status is "installed," then the software is determined to be compliant. If the software's compliance attribute indicates that installation is prohibited, then the software is deemed to be in violation of regulations. If the software's compliance attribute is "allowed to install" and the software version is outside the version constraint range, the software is determined to be in violation. If the software's compliance attribute is that it must be installed and the software's installation status is that it is not installed or has been deleted, then the software is determined to be in violation of regulations. If the software's compliance attribute is "must be installed", the software's installation status is "installed", and the software version is outside the version constraint range, then the software is determined to be in violation. Specifically, the software comparison module is used for: Subtract the first metadata feature matrix of the first software from the second metadata feature matrix of the second software, and record the first element with a non-zero difference. If the number of rows in the first file feature matrix of the first software is less than or equal to the number of rows in the second file feature matrix of the second software, the first row of the first file feature matrix is ​​aligned with each row of the second file feature matrix in turn, and the first column of the first file feature matrix is ​​kept aligned with the first column of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, align the first row of the second file feature matrix with each row of the first file feature matrix in turn, and keep the first column of the second file feature matrix aligned with the first column of the first file feature matrix. During each alignment, the ASCII code difference between the elements of the first file feature matrix and the corresponding elements of the second file feature matrix in the intersection region of the first file feature matrix and the second file feature matrix is ​​calculated, and the second element with a non-zero difference is recorded. Create a new matrix, set the elements in the new matrix that are in the same position as all the second elements to 0, and set the elements in the other positions of the new matrix to 1. If the number of rows in the first file feature matrix is ​​less than or equal to the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the second file feature matrix. If the number of rows in the first file feature matrix is ​​greater than the number of rows in the second file feature matrix, the size of the new matrix is ​​the same as that of the first file feature matrix. Calculate the feature change value, which is equal to the sum of the number of the first element and the number of elements with a value of 1 in the new matrix; If the feature change value is less than or equal to a preset change threshold, the first software is determined to be the same as the second software; otherwise, the first software is determined to be different from the second software.

5. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to at least one of the processors; wherein, The memory stores instructions that can be executed by the processor to implement the Kylin operating system software management method as described in any one of claims 1-3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are executed by the computer to implement the Kylin operating system software management method as described in any one of claims 1-3.

Images