Domestic operating system version compatibility detection method

Abstract

The invention relates to the technical field of computers, and particularly provides a domestic operating system version compatibility detection method, which comprises the following steps of: acquiring a full-quantity warehouse package of a new operating system and a full-quantity warehouse package of an old operating system, and storing the full-quantity warehouse package and the full-quantity warehouse package in different directories; respectively extracting the software package of the new version and the software package of the old version from the corresponding storage directories, constructing a new version analysis database table based on the software package of the new version, and constructing an old version analysis database table based on the software package of the old version; comparing the new version analysis database table with the old version analysis database table to obtain a compatibility difference database table; and generating a compatibility difference report based on the compatibility difference database table. By means of the technical scheme, the technical problems that in the prior art, operating system version compatibility detection is low in efficiency, prone to errors and incomplete in coverage are solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and specifically provides a method for detecting the compatibility of domestic operating system versions. Background Art

[0002] With the acceleration of my country's independent innovation in information technology, the research and development of domestic operating systems has made significant progress. Considering factors such as security and technological innovation, the operating system version needs to be continuously upgraded to adapt to the ever-changing security needs and technical standards. However, in the process of operating system version iteration, there is often a lack of smooth compatibility processing of old version operating system components, resulting in compatibility issues when the new version of the operating system runs the old version of the application, such as dynamic library mismatch, interface symbol change, command execution exception and configuration file error. After the operating system is upgraded, if the compatibility issues of the above components are not properly handled, it will directly lead to the poor operation or even inability of the old version of the application to run in the new operating system environment. This not only affects the business continuity and work efficiency of users, but also seriously hinders the widespread application of the new version of the operating system and the smooth transition of software.

[0003] Therefore, after the operating system is upgraded, compatibility testing between the old and new versions of the operating system is of great significance for the subsequent compatibility integration of the new version of the operating system. Existing operating system compatibility testing methods mostly rely on manual comparison, testing or limited automated tools, and have the following significant disadvantages:

[0004] (1) Inefficiency: The manual inspection process is time-consuming and difficult to quickly identify the differences in massive software packages and complex features.

[0005] (2) Lack of accuracy: Manual comparison is susceptible to subjective factors and may result in missing subtle but critical compatibility issues.

[0006] (3) Lack of systematicity: Existing tools often detect a single type of feature (such as dynamic libraries) and lack comprehensive analysis of multiple compatibility factors.

[0007] (4) Difficult to apply on a large scale: For the needs of multi-version and large-scale compatibility assessment of domestic operating systems, existing methods are difficult to meet the requirements of efficient and accurate automated detection. Summary of the invention

[0008] In order to overcome the above defects, the present invention is proposed to solve the technical problems in the prior art of low efficiency, easy error and incomplete coverage of operating system version compatibility detection.

[0009] The present invention proposes a method for detecting the compatibility of domestic operating system versions, comprising the steps of:

[0010] Get the full warehouse package of the new operating system and the full warehouse package of the old operating system and store them in different directories;

[0011] Extract the new version software package and the old version software package from the corresponding storage directory respectively, and construct a new version analysis database table based on the new version software package, and construct an old version analysis database table based on the old version software package;

[0012] Compare the new version analysis database table with the old version analysis database table to obtain a compatibility difference database table;

[0013] A compatibility difference report is generated based on the compatibility difference database table.

[0014] Further, the step of obtaining the full warehouse package of the new operating system and the full warehouse package of the old operating system and storing them in different directories includes the following steps:

[0015] Get the full repository package of the new operating system, name it new-os-packages, and store it in the specified directory to get the new operating system package directory new-os-packages;

[0016] Get the full repository package of the old operating system, name it old-os-packages, and store it in another specified directory to get the old operating system package directory old-os-packages.

[0017] further,

[0018] The new version analysis database table includes a new version dynamic library database table with soname as the index, a new version symbol interface database table with symbol interface name as the primary key, a new version command file database table with command file path as the primary key, and a new version configuration file database table with configuration file path as the primary key.

[0019] The old version analysis database table includes an old version dynamic library database table with soname as index, an old version symbolic interface database table with symbolic interface name as primary key, an old version command file database table with command file path as primary key, and an old version configuration file database table with configuration file path as primary key.

[0020] further,

[0021] The step of constructing a new version analysis database table based on the new version of the software package includes the following steps:

[0022] Extract the full name of the new version of the dynamic library from the new version of the software package, record soname as the primary key, and build a new version of the dynamic library database table with soname as the index.

[0023] Parse the new version of the dynamic library content, record the name of the symbolic interface, return value, number of parameters and each parameter type, and form a new version of the symbolic interface database table with the symbolic interface name as the primary key.

[0024] Identify the key command files in the new version of the dynamic library, record the corresponding content and related metadata, and build a new version of the command file database table with the command file path as the primary key.

[0025] Identify key configuration files in the new version of the dynamic library, record the corresponding content and related metadata, and build a new version of the configuration file database table with the configuration file path as the primary key;

[0026] The step of constructing an old version analysis database table based on the old version of the software package includes the following steps:

[0027] Extract the full name of the old version of the dynamic library from the old version of the software package, record soname as the primary key, and build the old version of the dynamic library database table with soname as the index.

[0028] Parse the old version of the dynamic library content, record the name of the symbolic interface, return value, number of parameters and each parameter type, and form an old version of the symbolic interface database table with the symbolic interface name as the primary key.

[0029] Identify key command files in the old version of the dynamic library, record the corresponding content and related metadata, and build an old version of the command file database table with the command file path as the primary key.

[0030] Identify key configuration files in the old version of the dynamic library, record the corresponding content and related metadata, and build an old version configuration file database table with the configuration file path as the primary key.

[0031] Further, the comparing the new version analysis database table with the old version analysis database table to obtain a compatibility difference database table includes the steps of:

[0032] In the new version dynamic database table and the old version dynamic database table, index according to soname, check whether there is a dynamic library with the same soname, and build a dynamic library difference table;

[0033] Compare the return value, number of parameters and each parameter type of each group of symbolic interfaces with the same name in the new version symbolic interface database table and the old version symbolic interface database table to see if they are consistent, and construct a symbolic interface difference table;

[0034] Compare the contents of each group of command files with the same path in the new version command file database table with those in the old version command file database table to see if they are consistent, and build a command file difference table;

[0035] Compare the contents of each group of configuration files with the same path in the new version configuration file database table with those in the old version configuration file database table to see if they are consistent, and build a configuration file difference table.

[0036] Further, generating a compatibility difference report based on the compatibility difference database table comprises the steps of:

[0037] Count the number and distribution of incompatibility issues in the dynamic library difference table, symbol interface difference table, command file difference table, and command file difference table;

[0038] Lists detailed information about each incompatibility issue, including different dynamic library sonames, parameter differences between symbolic interfaces with the same name, content differences between command files with the same path, and content differences between configuration files with the same path.

[0039] Analyze the impact of each incompatibility issue on the running of the old version of the application software on the new version of the operating system.

[0040] Working principle and beneficial effects of the present invention:

[0041] In the technical solution of the present invention, the full warehouse packages of the new and old versions of the operating system are first parsed to extract key information such as dynamic libraries, interface symbols, command files, and configuration files in the new and old versions of the operating system, and form corresponding database tables; then, the compatibility differences are identified by comparing and analyzing these database tables; finally, the compatibility difference report is generated by describing the database tables with compatibility differences, providing a basis for the subsequent new operating system compatibility fusion technical solution. The efficient and accurate identification of the compatibility differences between the new and old operating systems is achieved, providing strong technical support for the smooth transition of domestic operating system version upgrades. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The disclosure of the present invention will become more easily understood with reference to the accompanying drawings. It is easy for those skilled in the art to understand that these drawings are only for illustrative purposes and are not intended to limit the scope of protection of the present invention. In addition, similar numbers in the figures are used to represent similar components, among which:

[0043] Figure 1 It is a flow chart of the main steps of a method for detecting the compatibility of domestic operating system versions according to the present invention. DETAILED DESCRIPTION

[0044] Some embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

[0045] Figure 1This is a schematic diagram of the main steps of a method for detecting the compatibility of domestic operating system versions according to the present invention. Figure 1 As shown, in this embodiment, a method for detecting the compatibility of domestic operating system versions mainly includes the following steps S1-S4.

[0046] Step S1: Data preparation.

[0047] Get the full warehouse package of the new operating system, name it new-os-packages, and store it in the specified directory to get the new operating system package directory new-os-packages; get the full warehouse package of the old operating system, name it old-os-packages, and store it in another specified directory to get the old operating system package directory old-os-packages.

[0048] Through step S1, in the face of the diversity of operating systems, a widely compatible full-warehouse package extraction logic is adopted to ensure consistency between different operating system releases. The naming rules for the operating system package directory are simple and clear, which is convenient for automated process identification and subsequent processing, and is also easy for technical personnel to understand and maintain.

[0049] In one implementation, in order to ensure the efficiency and compatibility of data preparation, a highly versatile software package management tool or custom script is used. These tools and scripts have cross-platform capabilities to adapt to different operating system environments. The selection of tools is based on their wide support for operating system package management systems and their automated processing capabilities, so that the full warehouse package of the operating system can be quickly and accurately located and obtained.

[0050] In one implementation, a distributed storage system (such as HDFS) is used to store the full warehouse package of the operating system, and multi-threaded or distributed download tools are used to speed up the download speed. To solve the problem of processing large-scale data sets, high-speed data transmission protocols and storage optimization technologies are used to ensure the fast and secure transfer and storage of a large number of software packages in the full warehouse package, while reducing disk I / O conflicts. Intelligent algorithms are used to optimize storage allocation and resource management to avoid system resource shortages caused by large-scale file operations during the data preparation stage.

[0051] Step S2: Data extraction and database construction.

[0052] S21: extracting a new version of the software package from the new operating system package directory new-os-packages, and executing the following steps S211-S214 on the new version of the software package to construct a new version analysis database table.

[0053] S211: extract the full name of the new version of the dynamic library from the new version of the software package, record the soname as the primary key, and build a new version of the dynamic library database table with the soname as the index.

[0054] In step S211, soname is selected as the primary key because soname is a unique identifier of the dynamic library, which can ensure accurate matching of the dynamic library in the database. The purpose of building an index is to speed up the query speed and improve the processing efficiency.

[0055] S212: Parse the new version of the dynamic library content, record the name of the symbolic interface, the return value, the number of parameters and the type of each parameter, and form a new version of the symbolic interface database table with the symbolic interface name as the primary key.

[0056] Through step S212, detailed records of each symbolic interface, including the return value, number of parameters and type of each parameter, are made in order to accurately identify compatibility issues at the interface level and avoid runtime errors caused by interface changes.

[0057] S213: Identify key command files in the new version dynamic library, record corresponding content and related metadata, and construct a new version command file database table with the command file path as the primary key.

[0058] S214: Identify key configuration files in the new version dynamic library, record corresponding content and related metadata, and construct a new version configuration file database table with the configuration file path as the primary key.

[0059] Through steps S213-S214, for command files and configuration files, their file paths are used as primary keys, combined with metadata records, to quickly locate specific file differences, especially changes in the content of command files and configuration files, which often directly affect application behavior.

[0060] S22: extracting the old version of the software package from the old operating system package directory old-os-packages, and executing the following steps S221-S224 on the old version of the software package to construct an old version analysis database table.

[0061] S221: extract the full name of the old version dynamic library from the old version software package, record the soname as the primary key, and build an old version dynamic library database table with the soname as the index.

[0062] In step S221, soname is selected as the primary key because soname is a unique identifier of the dynamic library, which can ensure accurate matching of the dynamic library in the database. The purpose of building an index is to speed up the query speed and improve the processing efficiency.

[0063] S222: Parse the content of the old version dynamic library, record the name, return value, number of parameters and type of each parameter of the symbolic interface, and form an old version symbolic interface database table with the symbolic interface name as the primary key.

[0064] Through step S222, detailed records of each symbolic interface, including the return value, number of parameters and type of each parameter, are made in order to accurately identify compatibility issues at the interface level and avoid runtime errors caused by interface changes.

[0065] S223: Identify key command files in the old version dynamic library, record the corresponding content and related metadata, and construct an old version command file database table with the command file path as the primary key.

[0066] S224: Identify key configuration files in the old version dynamic library, record corresponding content and related metadata, and construct an old version configuration file database table with the configuration file path as the primary key.

[0067] Through steps S223-S224, for command files and configuration files, the file path is used as the primary key, combined with the metadata records, to quickly locate the specific file differences, especially the changes in the content of command files and configuration files, which often directly affect application behavior.

[0068] In this embodiment, metadata represents the initial content data that can be used as a benchmark. Metadata can be regarded as a part of the file content. Usually, the key content that may affect compatibility is called metadata. In this way, when comparing differences, it is possible to identify whether the new system file has compatibility differences by comparing metadata. Metadata is used as benchmark data for comparison, and compatibility differences can be located through analysis.

[0069] In one implementation, the parsing of dynamic libraries and configuration files uses high-performance parsers and algorithms to ensure that high efficiency can be maintained when processing large-volume or complex-structure files, thereby improving parsing efficiency. When constructing the analysis database table, data deduplication and consistency verification mechanisms are used to avoid interference introduced by redundant data and ensure the accuracy of the analysis results.

[0070] Step S3: Compatibility comparison and difference table generation.

[0071] Through the following steps S31-S34, the new version analysis database table is compared with the old version analysis database table to obtain a compatibility difference database table.

[0072] S31: indexing the new version dynamic database table and the old version dynamic database table according to soname, checking dynamic libraries with different sonames, and building a dynamic library difference table;

[0073] S32: Compare the return value, number of parameters and each parameter type of each group of symbolic interfaces with the same name in the new version symbolic interface database table and the old version symbolic interface database table to see whether they are consistent, and construct a symbolic interface difference table;

[0074] S33: Compare the contents of each group of command files with the same path in the new version command file database table and the old version command file database table to see if they are consistent, and construct a command file difference table;

[0075] S34: Compare the contents of each group of configuration files with the same path in the new version configuration file database table and the old version configuration file database table to see if they are consistent, and construct a configuration file difference table.

[0076] The dynamic library difference table, symbol interface difference table, command file difference table and configuration file difference table generated based on the above comparison results constitute a compatibility difference database table, which records each incompatible feature and its difference details in detail.

[0077] In one implementation, SQL queries or customized comparison algorithms are used to compare sonames, symbolic interfaces, command files, and configuration files one by one. The difference analysis not only considers the existence of the difference, but also the changes at the attribute level, such as changes in interface return values, changes in parameter types, etc., to ensure the comprehensiveness of difference identification.

[0078] Step S4: Report output.

[0079] Through the following steps S41-S43, a compatibility difference report is generated based on the compatibility difference database table.

[0080] S41: Count the number and distribution of incompatible issues in the dynamic library difference table, the symbol interface difference table, the command file difference table, and the command file difference table.

[0081] S42: Lists detailed information of each incompatibility issue, including different dynamic library sonames, parameter differences between symbolic interfaces with the same name, content differences between command files with the same path, and content differences between configuration files with the same path.

[0082] S43: Analyze the impact of each incompatibility issue on the old version of application software when it runs on the new version of the operating system.

[0083] In this embodiment, the compatibility difference report includes an overview of compatibility issues, a specific difference description, and a technical impact assessment. The report has a clear structure, which is convenient for quick browsing and in-depth analysis. The compatibility problem overview section counts the number and distribution of various incompatibility issues, helping decision makers to grasp the general situation of the problem; the specific difference description lists the details of each incompatible feature, such as the specific changes in dynamic libraries and interfaces; the technical impact assessment deeply analyzes the impact of these differences on the operation of the old version of the application in the new environment, providing direction for subsequent repairs.

[0084] Furthermore, based on the generated compatibility difference report, a compatibility fusion technical solution can be developed. First, the key incompatible features identified in the report are classified and sorted into a list of problems. Then, for each type of problem, a corresponding solution is designed or recommended, such as providing a compatible version of the dynamic library, modifying or refactoring the interface to restore compatibility, adjusting the command script to comply with the new version specification, updating or converting the configuration file format, etc. Finally, a comprehensive compatibility fusion strategy is formed to guide subsequent operating system upgrades and ensure a smooth transition between the old and new versions.

[0085] In this embodiment, through detailed report output and the formulation of subsequent technical integration solutions, compatibility issues in the process of upgrading domestic operating system versions are ensured to be efficiently and accurately identified and resolved, greatly improving the continuity of user business, the upgrade efficiency of the operating system and the stability of the software ecosystem.

[0086] It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art can understand that in order to achieve the effects of the present invention, different steps do not have to be performed in such an order. They can be performed simultaneously (in parallel) or in other orders. These changes are within the scope of protection of the present invention.

[0087] Based on the above steps S1-S4, firstly, by parsing the full warehouse packages of the new and old versions of the operating system, key information such as dynamic libraries, interface symbols, command files and configuration files in the new and old versions of the operating system are extracted, and the corresponding database tables are formed; then, by comparing and analyzing these database tables, compatibility differences are identified; finally, the database tables with compatibility differences are described to generate a compatibility difference report, which provides a basis for the subsequent new operating system compatibility fusion technical solution. This achieves efficient and accurate identification of the compatibility differences between the new and old operating systems, and provides strong technical support for the smooth transition of domestic operating system version upgrades.

[0088] The present invention also has the following technical effects:

[0089] 1. Significantly improve detection efficiency: Replace manual comparison with automated processes, significantly shorten compatibility detection time, and adapt to large-scale and frequent version iteration requirements.

[0090] 2. Improve detection accuracy: avoid human omissions, ensure comprehensive and accurate identification of various compatibility issues, and improve detection quality.

[0091] 3. Provide systematic solutions: One-stop solution for comprehensive analysis of multiple compatibility factors, providing all-round compatibility assessment for operating system upgrades.

[0092] 4. Promote smooth transition: Provide scientific basis for compatibility fusion technology solutions, help seamless connection between new and old versions of operating systems, reduce migration costs, and ensure user experience.

[0093] Here are some terms involved in this invention

[0094] 1. "Full warehouse package" refers specifically to all software packages that depend on and adapt to a specific operating system version. This means that the package contains all necessary software components, dynamic libraries, and other dependencies to ensure that the operating system can run normally. A full warehouse package can be regarded as a collection of all required software, usually created for easy management and deployment.

[0095] 2. A software package is the basic unit of software distribution. It contains one or more files that are combined to implement specific functions. In the present invention, a software package is the basic unit that constitutes a full warehouse package. Each software package must be adapted to a specific operating system version and be available in the full warehouse package. A software package usually consists of the following parts:

[0096] Executable files

[0097] Configuration File

[0098] ·document

[0099] Library files (static or dynamic)

[0100] 3. A dynamic library is a shared library that is loaded into memory when a program is running. It contains a set of precompiled functions and procedures that can be shared between multiple programs. The advantage of a dynamic library is that it can reduce memory usage and improve resource utilization. In the present invention, the dynamic library is part of the software package, which provides the necessary runtime support for the software package.

[0101] 4. The relationship between the three

[0102] The full repository package contains all software packages, which are adapted and verified to ensure that they can run correctly on specific operating system versions.

[0103] A software package is the basic unit that constitutes a full warehouse package. Each software package may contain one or more dynamic libraries.

[0104] As part of a software package, the dynamic library provides the functional support required by the software package when it is running.

[0105] In summary, in the present invention:

[0106] The full warehouse package provides a collection of all required software that has been adapted and verified to ensure the integrity and stability of the operating system.

[0107] Packages are self-contained units of software that are designed to run on a specific operating system version and usually include the necessary dynamic libraries.

[0108] The dynamic library is part of the software package and provides the functional support required by the software package when it is running, enabling the software package to work with other software packages.

[0109] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle 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 fall within the protection scope of the present invention.

Claims

1. A method for detecting the compatibility of domestic operating system versions, characterized in that: Includes steps: Get the full warehouse package of the new operating system and the full warehouse package of the old operating system and store them in different directories; Extract the new version software package and the old version software package from the corresponding storage directory respectively, and construct a new version analysis database table based on the new version software package, and construct an old version analysis database table based on the old version software package; Compare the new version analysis database table with the old version analysis database table to obtain a compatibility difference database table; A compatibility difference report is generated based on the compatibility difference database table.

2. According to claim 1, a method for detecting the compatibility of domestic operating system versions is characterized in that: The method of obtaining the full warehouse package of the new operating system and the full warehouse package of the old operating system and storing them in different directories includes the following steps: Get the full repository package of the new operating system, name it new-os-packages, and store it in the specified directory to get the new operating system package directory new-os-packages; Get the full repository package of the old operating system, name it old-os-packages, and store it in another specified directory to get the old operating system package directory old-os-packages.

3. A method for detecting the compatibility of domestic operating system versions according to claim 1, characterized in that: The new version analysis database table includes a new version dynamic library database table with soname as the index, a new version symbol interface database table with symbol interface name as the primary key, a new version command file database table with command file path as the primary key, and a new version configuration file database table with configuration file path as the primary key. The old version analysis database table includes an old version dynamic library database table with soname as index, an old version symbolic interface database table with symbolic interface name as primary key, an old version command file database table with command file path as primary key, and an old version configuration file database table with configuration file path as primary key.

4. A method for detecting the compatibility of domestic operating system versions according to claim 3, characterized in that: The step of constructing a new version analysis database table based on the new version of the software package includes the following steps: Extract the full name of the new version of the dynamic library from the new version of the software package, record soname as the primary key, and build a new version of the dynamic library database table with soname as the index. Parse the new version of the dynamic library content, record the name of the symbolic interface, return value, number of parameters and each parameter type, and form a new version of the symbolic interface database table with the symbolic interface name as the primary key. Identify the key command files in the new version of the dynamic library, record the corresponding content and related metadata, and build a new version of the command file database table with the command file path as the primary key. Identify key configuration files in the new version of the dynamic library, record the corresponding content and related metadata, and build a new version of the configuration file database table with the configuration file path as the primary key; The step of constructing an old version analysis database table based on the old version of the software package includes the following steps: Extract the full name of the old version of the dynamic library from the old version of the software package, record soname as the primary key, and build the old version of the dynamic library database table with soname as the index. Parse the old version of the dynamic library content, record the name of the symbolic interface, return value, number of parameters and each parameter type, and form an old version of the symbolic interface database table with the symbolic interface name as the primary key. Identify key command files in the old version of the dynamic library, record the corresponding content and related metadata, and build an old version of the command file database table with the command file path as the primary key. Identify key configuration files in the old version of the dynamic library, record the corresponding content and related metadata, and build an old version configuration file database table with the configuration file path as the primary key.

5. A method for detecting the compatibility of domestic operating system versions according to claim 3, characterized in that: The step of comparing the new version analysis database table with the old version analysis database table to obtain a compatibility difference database table includes the following steps: In the new version dynamic database table and the old version dynamic database table, index according to soname, check whether there is a dynamic library with the same soname, and build a dynamic library difference table; Compare the return value, number of parameters and each parameter type of each group of symbolic interfaces with the same name in the new version symbolic interface database table and the old version symbolic interface database table to see if they are consistent, and construct a symbolic interface difference table; Compare the contents of each group of command files with the same path in the new version command file database table with those in the old version command file database table to see if they are consistent, and build a command file difference table; Compare the contents of each group of configuration files with the same path in the new version configuration file database table with those in the old version configuration file database table to see if they are consistent, and build a configuration file difference table.

6. A method for detecting the compatibility of domestic operating system versions according to claim 1, characterized in that: The generating of the compatibility difference report based on the compatibility difference database table comprises the steps of: Count the number and distribution of incompatibility issues in the dynamic library difference table, symbol interface difference table, command file difference table, and command file difference table; Lists detailed information about each incompatibility issue, including different dynamic library sonames, parameter differences between symbolic interfaces with the same name, content differences between command files with the same path, and content differences between configuration files with the same path. Analyze the impact of each incompatibility issue on the running of the old version of the application software on the new version of the operating system.

Images