Binary file version confirmation method, device, equipment, medium and program product

Abstract

The binary file version confirmation method, device, equipment, medium and program product provided by the application, comprising: obtaining a target binary file to be processed; obtaining corresponding source code version information, patch number information and compilation environment information according to the target binary file; processing the target binary file according to a preset operation rule to generate a corresponding unique identifier; associating the unique identifier, the source code version information, the patch number information and the compilation environment information to obtain associated data, and writing the associated data into a target database for storage; obtaining user input query identifier information through a preset interactive terminal; matching and calling the version information corresponding to the query identifier information in the target database according to the query identifier information, and outputting the version information to the interactive terminal; the method provided by the application is used to realize the technical effect of improving the version determination accuracy and flexibility.

Description

Technical Field

[0001] This application relates to the field of computer software technology, and in particular to a method, apparatus, device, medium and program product for verifying the version of a binary file. Background Technology

[0002] With increasing software complexity and the widespread adoption of mass production, version control and defect fixing have become core aspects of ensuring product stability. In the development of consumer and industrial electronics, the unreadable nature of binary files makes version information difficult to identify directly. When customers encounter problems after integrating patches containing binary files, it's challenging to quickly pinpoint the source of the problematic binary file. Therefore, achieving accurate version confirmation of binary files has become a challenging and significant issue.

[0003] In existing technologies, the main method for confirming binary file versions is to use a version number-based management approach. This involves assigning a unique version number to each product version and associating all related source code and binary files with that version number. When a customer reports a problem, the corresponding source code version and compilation environment can be located simply by using the version number. Some systems also attempt to indirectly associate binary files with commit records from source code management systems (such as distributed version control systems) to achieve version confirmation.

[0004] However, existing technologies suffer from low accuracy and poor flexibility in confirming binary file versions due to factors such as insufficient flexibility caused by mandatory patch merging, unclear origin due to the lack of independent and unique identifiers for binary files, and difficulty in tracing historical versions due to reliance on manual recording. Summary of the Invention

[0005] The binary file version verification method, apparatus, device, medium, and program products provided in this application are intended to improve the accuracy and flexibility of version determination.

[0006] Firstly, this application provides a method for verifying the version of a binary file, including:

[0007] Obtain the target binary file to be processed, which includes the pre-built binary file used in the release version and the compiled binary file generated during compilation;

[0008] Based on the target binary file, obtain the corresponding source code version information, patch number information, and compilation environment information. Among them, the patch number information corresponds to the relevant identification information in the released patch file.

[0009] The target binary file is processed according to preset operation rules to generate a corresponding unique identifier;

[0010] The unique identifier, source code version information, patch number information, and compilation environment information are associated to obtain associated data, which is then written into the target database for storage.

[0011] The system obtains the user-inputted identifier information through a pre-set interactive terminal. The identifier information is obtained by calculating the target binary file using a pre-set tool.

[0012] Based on the identifier information to be queried, match and retrieve the version information corresponding to the identifier information to be queried from the target database, and output the version information to the interactive terminal.

[0013] In one possible implementation, the target binary file is processed according to preset operation rules to generate a corresponding unique identifier, including:

[0014] For the pre-built binary file, the first full data of the pre-built binary file is obtained through the relevant commands of the pre-built source code management system;

[0015] For compiled binary files, after the compilation process is completed, obtain the second full data of the compiled binary file;

[0016] A preset hash operation method is used to calculate the hash value of the first and second full data sets. The hash value is then used as the unique identifier of the target binary file. The preset hash operation method is a 256-bit secure hash operation.

[0017] In one possible implementation, unique identifiers, source code version information, patch number information, and compilation environment information are associated to obtain associated data, including:

[0018] Using the unique identifier corresponding to the target binary file as the association primary key, and using the source code version information, patch number information, and compilation environment information corresponding to the target binary file as multiple corresponding association fields, a mapping relationship between the association primary key and each association field is established.

[0019] Based on the mapping relationship, unique identifiers, source code version information, patch number information, and compilation environment information are integrated to generate associated data;

[0020] Based on the associated primary key, establish a mapping between the associated primary key and the patch number information;

[0021] Based on the association mapping, locate the patch corresponding to the target binary file;

[0022] Receive patch integration commands sent by users via interactive terminals;

[0023] Update the patch number information and associated data corresponding to the target binary file according to the patch merge instruction.

[0024] In one possible implementation, the associated data is written to the target database for storage, including:

[0025] The target database is divided into multiple sub-warehouses using a database layering approach.

[0026] The unique identifier, source code version information, patch number information, and compilation environment information in the associated data are stored in each sub-warehouse corresponding to the target database.

[0027] In one possible implementation, after writing the associated data to the target database for storage, the method further includes:

[0028] Based on the target database, establish the corresponding query interface;

[0029] The query interface is associated with each sub-warehouse. The query interface is used to receive the identification information to be queried and to perform subsequent query operations. The query interface can call the unique identifier and corresponding associated data stored in each sub-warehouse.

[0030] In one possible implementation, based on the identifier information to be queried, version information corresponding to the identifier information to be queried is matched and retrieved from the target database, and the version information is output to the interactive terminal, including:

[0031] Input the identifier information to be queried into the query interface of the target database;

[0032] Based on the query interface, retrieve the target unique identifier that matches the query identifier information in each sub-warehouse of the target database;

[0033] Based on the target's unique identifier, determine the corresponding target-related data;

[0034] Based on the target association data, determine the corresponding target source code version information, target patch number information, and target compilation environment information;

[0035] The target source code version information, target patch number information, and target compilation environment information are integrated to generate the version information corresponding to the identifier information to be queried, and the version information value is output to the interactive terminal.

[0036] Secondly, this application provides a binary file version verification device, comprising:

[0037] The first acquisition module is used to acquire the target binary file to be processed, wherein the target binary file includes the pre-built binary file when the release version is released and the compiled binary file generated during compilation;

[0038] The second acquisition module is used to acquire the corresponding source code version information, patch number information and compilation environment information based on the target binary file. The patch number information corresponds to the relevant identification information in the released patch file.

[0039] The generation module is used to process the target binary file according to preset operation rules to generate a corresponding unique identifier;

[0040] The association module is used to associate unique identifiers, source code version information, patch number information, and compilation environment information to obtain association data, and then write the association data into the target database for storage.

[0041] The third acquisition module is used to acquire the user-inputted identifier information through a preset interactive terminal, wherein the identifier information is obtained by calculating the target binary file using a preset tool;

[0042] The processing module is used to match and retrieve the version information corresponding to the query identifier information from the target database, and output the version information to the interactive terminal.

[0043] In one possible implementation, the generation module is further configured to:

[0044] For the pre-built binary file, the first full data of the pre-built binary file is obtained through the relevant commands of the pre-built source code management system;

[0045] For compiled binary files, after the compilation process is completed, obtain the second full data of the compiled binary file;

[0046] A preset hash operation method is used to calculate the hash value of the first and second full data sets. The hash value is then used as the unique identifier of the target binary file. The preset hash operation method is a 256-bit secure hash operation.

[0047] In one possible implementation, the association module is also used for:

[0048] Using the unique identifier corresponding to the target binary file as the association primary key, and using the source code version information, patch number information, and compilation environment information corresponding to the target binary file as multiple corresponding association fields, a mapping relationship between the association primary key and each association field is established.

[0049] Based on the mapping relationship, unique identifiers, source code version information, patch number information, and compilation environment information are integrated to generate associated data;

[0050] Based on the associated primary key, establish a mapping between the associated primary key and the patch number information;

[0051] Based on the association mapping, locate the patch corresponding to the target binary file;

[0052] Receive patch integration commands sent by users via interactive terminals;

[0053] Update the patch number information and associated data corresponding to the target binary file according to the patch merge instruction.

[0054] In one possible implementation, the association module is also used for:

[0055] The target database is divided into multiple sub-warehouses using a database layering approach.

[0056] The unique identifier, source code version information, patch number information, and compilation environment information in the associated data are stored in each sub-warehouse corresponding to the target database.

[0057] In one possible implementation, the association module is also used for:

[0058] Based on the target database, establish the corresponding query interface;

[0059] The query interface is associated with each sub-warehouse. The query interface is used to receive the identification information to be queried and to perform subsequent query operations. The query interface can call the unique identifier and corresponding associated data stored in each sub-warehouse.

[0060] In one possible implementation, the processing module is further configured to:

[0061] Input the identifier information to be queried into the query interface of the target database;

[0062] Based on the query interface, retrieve the target unique identifier that matches the query identifier information in each sub-warehouse of the target database;

[0063] Based on the target's unique identifier, determine the corresponding target-related data;

[0064] Based on the target association data, determine the corresponding target source code version information, target patch number information, and target compilation environment information;

[0065] The target source code version information, target patch number information, and target compilation environment information are integrated to generate the version information corresponding to the identifier information to be queried, and the version information value is output to the interactive terminal.

[0066] Thirdly, this application provides a binary file version verification device, including: a memory and a processor;

[0067] The memory stores instructions that the computer executes;

[0068] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0069] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0070] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0071] This application provides a method, apparatus, device, medium, and program product for version confirmation of binary files. By acquiring the target binary file, including both pre-built and compiled files, it lays the foundation for comprehensive version confirmation; by acquiring source code version, patch number, and compilation environment information, it provides richer evidence for version confirmation. A unique identifier is generated according to preset rules to accurately distinguish different files. This information is associated and written to a database for centralized management. The user-inputted identifier information is obtained through an interactive terminal, and then version information is retrieved from the database and output. The entire process reduces version confirmation errors through the comprehensive utilization of multiple information sources and standardized operations. It can flexibly respond to binary file version query needs from different sources and under different circumstances, thereby achieving the technical effect of improving the accuracy and flexibility of version confirmation. Attached Figure Description

[0072] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0073] Figure 1 This application provides a schematic diagram of an application data processing system architecture.

[0074] Figure 2 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 1 ;

[0075] Figure 3 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 2 ;

[0076] Figure 4 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 3 ;

[0077] Figure 4Flowchart of the binary file version verification method provided in the embodiments of this application Figure 6 ;

[0078] Figure 7 A schematic diagram of the binary file version verification device provided in the embodiments of this application;

[0079] Figure 1 A schematic diagram of the structure of the binary file version verification device provided in this application embodiment.

[0080] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0081] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0082] Due to factors such as insufficient flexibility caused by mandatory patch merging, lack of independent and unique identifiers for binary files leading to ambiguity of origin, and difficulty in tracing historical versions due to reliance on manual recording, existing technologies suffer from low accuracy and poor flexibility in confirming binary file versions.

[0083] To address the aforementioned issues, this application provides a method, apparatus, device, medium, and program product for verifying the version of binary files. By acquiring the target binary file, including both pre-built and compiled files, a foundation is laid for comprehensive version verification. Obtaining source code version, patch number, and compilation environment information provides richer evidence for version verification. Generating unique identifiers according to preset rules accurately distinguishes different files. Linking this information and writing it to a database facilitates centralized management. The process involves acquiring the user-inputted identifier information via an interactive terminal, then retrieving version information from the database and outputting it. Through the comprehensive utilization of various information and standardized operations, the entire process reduces errors in version verification. Simultaneously, it can flexibly respond to binary file version query needs from different sources and under different circumstances, thereby achieving the technical effect of improving the accuracy and flexibility of version verification.

[0084] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0085] Figure 1 This is a schematic diagram of an application data processing system architecture provided in an embodiment of this application. The application data processing system is a computer device. Figure 1 As shown, the above architecture includes at least one of a data acquisition device 101, a processing device 102, and a display device 103.

[0086] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the architecture of the application data processing system. In other feasible embodiments of this application, the above architecture may include more or fewer components than illustrated, or combine some components, or split some components, or arrange different components, which can be determined according to the actual application scenario and is not limited here. Figure 2 The components shown can be implemented in hardware, software, or a combination of both.

[0087] In the specific implementation process, the data acquisition device 101 may include an input / output interface or a communication interface, and the data acquisition device 101 can be connected to the processing device through the input / output interface or the communication interface.

[0088] The processing device 102 first acquires the target binary file, including both pre-built and compiled files, and then extracts its source code version, patch number, and compilation environment information. Next, it generates a unique identifier according to preset rules, associates the identifier with the aforementioned information, and stores it in a database. Finally, it obtains the user-inputted identifier information via an interactive terminal, matches it against the database to retrieve the corresponding version information, and outputs it, thereby achieving accurate and flexible version confirmation.

[0089] The display device 103 can also be a touch screen or the screen of a terminal device, used to receive user commands while displaying the above-mentioned content, so as to realize interaction with the user.

[0090] It should be understood that the aforementioned processing device can be implemented by a processor reading instructions from memory and executing those instructions, or it can be implemented by a chip circuit.

[0091] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0092] Figure 1 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 2 ,like Figure 3 As shown, this embodiment provides a method for confirming the version of a binary file, including:

[0093] S201. Obtain the target binary file to be processed.

[0094] In this embodiment, the target binary file includes the pre-built binary file used in the release version and the compiled binary file generated during compilation.

[0095] Obtain the target binary files that need to be processed. These target binary files include two types: one is the pre-built binary files used during the product release phase, and the other is the compiled binary files generated after the engineering compilation process. Both types of files are the core objects for subsequent processing such as identifier generation.

[0096] S202. Based on the target binary file, obtain the corresponding source code version information, patch number information, and compilation environment information.

[0097] In this embodiment, the patch number information corresponds to the relevant identification information in the released patch file.

[0098] Based on the acquired target binary file, collect the corresponding related information, including source code version information, patch number information, and compilation environment information. The patch number information is the specific content that matches the relevant identification information in the externally released patch file.

[0099] S203. Process the target binary file according to the preset operation rules to generate the corresponding unique identifier.

[0100] In one possible implementation, the target binary file is processed according to preset operation rules to generate a corresponding unique identifier, including:

[0101] For a pre-built binary file, the first full data of the pre-built binary file is obtained through relevant commands of the pre-defined source code management system; for a compiled binary file, the second full data of the compiled binary file is obtained after the compilation process is completed; a pre-defined hash operation method is used to calculate the first full data and the second full data to obtain the corresponding hash value, and the hash value is used as the unique identifier corresponding to the target binary file.

[0102] In this embodiment, the preset hash operation method is a 256-bit secure hash operation.

[0103] The target binary file is processed according to pre-defined operation rules to generate a unique identifier. First, the first full data is obtained from the pre-defined binary file through relevant commands of the Source Code Management (SCM) system. After the compilation process is completed, the second full data is obtained. Then, the two types of data are processed by a 256-bit secure hash operation to obtain a hash value. This hash value is the unique identifier of the target binary file.

[0104] S204. Associate the unique identifier, source code version information, patch number information, and compilation environment information to obtain associated data, and write the associated data into the target database for storage.

[0105] The generated unique identifier is associated with source code version information, patch number information, and compilation environment information to form associated data. This associated data is then entered into the specified target database to complete the storage operation, thereby achieving the binding and retention of various types of information with the unique identifier.

[0106] S205. Obtain the query identifier information input by the user through a preset interactive terminal.

[0107] In this embodiment, the identifier information to be queried is obtained by calculating the target binary file using a preset tool.

[0108] The system receives user-inputted identifier information via a pre-set interactive terminal. This identifier information is not manually generated, but rather obtained by the user through calculations on the target binary file using pre-set tools. It serves as the core basis for subsequent queries.

[0109] S206. Based on the identifier information to be queried, match and retrieve the version information corresponding to the identifier information to be queried in the target database, and output the version information to the interactive terminal.

[0110] The obtained identifier information is used as the retrieval basis. Information matching is performed in the target database, and the version information corresponding to the identifier information is retrieved from the database. After the matching and retrieval are completed, this version information is output to the corresponding interactive terminal for relevant personnel to view and use.

[0111] This application provides a method for version confirmation of binary files. By acquiring both pre-built and compiled files from the target binary file, a comprehensive foundation for version confirmation is laid. Obtaining source code version, patch number, and compilation environment information provides richer evidence for version confirmation. A unique identifier is generated according to preset rules to accurately distinguish different files. This information is associated with and written to a database for centralized management. The method obtains the user-input query identifier information through an interactive terminal, then retrieves version information from the database and outputs it. The entire process reduces version confirmation errors through the comprehensive utilization of multiple information sources and standardized operations. It can flexibly respond to binary file version query needs from different sources and under different circumstances, thereby achieving the technical effect of improving the accuracy and flexibility of version confirmation.

[0112] Figure 2 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 3 ,like Figure 4 As shown, this embodiment, based on the above embodiments, provides a detailed explanation of the specific process for obtaining associated data, including:

[0113] S301. Using the unique identifier corresponding to the target binary file as the associated primary key, and using the source code version information, patch number information, and compilation environment information corresponding to the target binary file as multiple associated fields, establish a mapping relationship between the associated primary key and each associated field.

[0114] Set the unique identifier of the target binary file as the associated primary key, and set the source code version information, patch number information, and compilation environment information corresponding to the file as multiple associated fields. Establish a one-to-one mapping relationship between the associated primary key and each associated field. This mapping relationship will be established based on various information collected when releasing the version and making the patch, covering all relevant information of both pre-built and compiled target binary files, ensuring that the correspondence between the primary key and the fields is accurate and without deviation.

[0115] Specifically, after calculating the unique identifiers of the pre-built binary files and the compiled binary files for the release version, the source code version information and compilation environment information of that version are extracted simultaneously. When creating a patch, the corresponding patch number information is extracted. The unique identifier is used as the core primary key, and independent field mappings are established for the three types of information to record the corresponding association between each type of information and the primary key.

[0116] S302. Based on the mapping relationship, integrate the unique identifier, source code version information, patch number information, and compilation environment information to generate associated data.

[0117] Based on the established primary key and mapping relationship of each associated field, the unique identifier of the target binary file, source code version information, patch number information, and compilation environment information are systematically integrated. The integration process retains the original attributes and precise correspondence of each type of information, and finally generates complete association data, which fully carries the identifier of the target binary file and various associated information.

[0118] Specifically, according to the established mapping relationship, the unique identifier of the same target binary file is packaged and integrated with the corresponding source code version, patch number, and compilation environment information to unify the data format, so that the integrated associated data can be directly identified and stored by the target database, while ensuring that the association relationship of each piece of information in the data can be quickly retrieved.

[0119] S303. Based on the associated primary key, establish an association mapping between the associated primary key and the patch number information.

[0120] Based on the primary key, a dedicated mapping is established for the primary key and patch number information. This mapping is a special refinement on the basis of the original overall mapping, focusing on the correspondence between the unique identifier of the target binary file and the patch number information, making the association between the two more direct and facilitating subsequent special queries and location of patches.

[0121] Specifically, based on the overall mapping relationship, the corresponding data of the associated primary key and patch number information are extracted separately to establish an independent special association mapping table. This table records all patch number information corresponding to each unique identifier. After a new patch is created and the corresponding binary file identifier is calculated, the new patch number information will be added to this mapping table in a timely manner.

[0122] S304. Locate the patch corresponding to the target binary file based on the association mapping.

[0123] Relying on the established association primary key and exclusive association mapping of patch number information, the system searches through the association primary key corresponding to the target binary file, accurately finds and locates all patches corresponding to the file in the mapping relationship. The location process relies on the direct association of the exclusive mapping to quickly match the corresponding patch information without any extra search steps.

[0124] Optionally, when it is necessary to locate a patch, enter the associated primary key of the target binary file, and perform a precise search through a special association mapping table. The system will automatically match and display all patch number information corresponding to the primary key. Based on the patch number information, the corresponding patch file can be located directly, including patches that come with the release version and patches added later.

[0125] S305, Receive patch integration command sent by user through interactive terminal.

[0126] The system receives patch merging commands from users via a pre-configured interactive terminal. These commands are user requests to merge patches into the target binary file. The interactive terminal receives all information from the commands, including the relevant identifiers of the patches to be merged and the corresponding primary keys associated with the target binary file, ensuring that no command information is lost.

[0127] Optionally, the user enters a patch merge command in the interactive terminal, which includes the primary key associated with the target binary file and the patch number to be merged. The interactive terminal will verify the format of the command information. After confirming that the information is complete and conforms to the operation specifications, the terminal will receive the command and transmit it to the background processing system, waiting for the subsequent patch merge operation to be executed.

[0128] S306. Update the patch number information and associated data corresponding to the target binary file according to the patch merge instruction.

[0129] Based on the received patch merge instruction, the patch number information corresponding to the target binary file is updated, and the new merged patch number is added to the original information. At the same time, based on the updated patch number information, the overall associated data corresponding to the file is updated synchronously. The updated associated data will retain the original information, and only the patch-related content will be corrected and supplemented.

[0130] Optionally, the system finds the associated primary key of the corresponding target binary file based on the information in the patch merge instruction, adds the newly merged patch number to the patch number information, and then re-integrates the unique identifier and various associated information according to the updated patch number information to generate new associated data. At the same time, the old associated data is archived and the new associated data is synchronously written to the target database.

[0131] The binary file version confirmation method provided in this application provides a mapping relationship established with a unique identifier as the core, which makes the correspondence between the target binary file and various related information more accurate. The integrated and generated related data can completely retain all relevant information of the file. The dedicated patch number mapping makes patch location more direct and efficient. Receiving compliant patch merging instructions can ensure the accuracy of operation instructions. Updating information and related data according to instructions can keep the relevant data of the target binary file up-to-date. This achieves accurate management of binary file related information, rapid patch location, and real-time data updates, improving the overall efficiency and data accuracy of binary version confirmation.

[0132] Figure 3 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 4 ,like Figure 5 As shown, this embodiment, based on the above embodiment, provides supplementary explanations of the specific process of writing the associated data into the target database for storage and subsequent processes, including:

[0133] S401. The target database is divided into multiple sub-warehouses using a database layering approach.

[0134] To address the issue of the massive number of binary files, a database layering approach is adopted. The target database used to store related data is systematically divided. After splitting the database according to reasonable layering rules, multiple independent yet collaborative database partitions are obtained, laying the foundation for subsequent partitioned storage of related data and adapting to the storage needs of massive binary file related data.

[0135] Specifically, hierarchical partitioning rules are formulated based on the type of associated data and the business attributes of binary files. The database is layered according to the encoding range of unique identifiers and the version segment of source code version information. The target database is split into multiple sub-warehouses, each corresponding to a fixed range of associated data, to ensure the orderliness and regularity of sub-warehouse storage.

[0136] S402. Store the unique identifier, source code version information, patch number information, and compilation environment information from the associated data into each sub-warehouse corresponding to the target database.

[0137] The integrated associated data is broken down, and the unique identifiers, source code version information, patch number information, and compilation environment information are stored in the corresponding sub-warehouses of the target database according to the sub-warehouse division rules of the target database. Each type of information is stored independently in the corresponding sub-warehouse and retains its association with the unique identifier, thus realizing the sub-warehouse management of massive associated data.

[0138] Specifically, according to the corresponding rules of the partitioning, the same unique identifier and the matching source code version information, patch number information, and compilation environment information are stored in the designated partitions respectively. An index is built for the unique identifier in each partition to ensure that the information in each partition can be accurately associated through the unique identifier. Data format adaptation is completed synchronously during storage.

[0139] S403. Based on the target database, establish the corresponding query interface.

[0140] Based on the target database that has completed the partitioning and data storage, a matching query interface is built. This query interface is the channel for external data interaction with the target database. The interface’s functions and design are fully adapted to the partitioning structure and data storage rules of the target database, and can support subsequent identification information query operations.

[0141] Optionally, based on the partitioned architecture and data retrieval requirements of the target database, a dedicated query interface is established. This query interface is configured with basic functions for data retrieval, retrieval, and feedback. A fixed format is set for the interface to receive query identifier information, ensuring that the interface can accurately identify various compliant query requests and transmit them to the target database.

[0142] S404. Associate the query interface with each sub-warehouse.

[0143] In this embodiment, the query interface is used to receive the identification information to be queried and to perform subsequent query operations. The query interface can call the unique identifier and corresponding associated data stored in each sub-warehouse.

[0144] The completed query interface establishes a direct association with each sub-warehouse of the target database. The core function of this query interface is to receive the identifier information to be queried from the outside and execute subsequent query-related operations. At the same time, this query interface has the ability to call across sub-warehouses and can directly retrieve the unique identifier and all its corresponding associated data stored in each sub-warehouse.

[0145] Specifically, the query interface is configured with sub-warehouse call permissions, a communication link is established between the query interface and all sub-warehouses, and the sub-warehouse retrieval rules of the query interface are set. When the query interface receives the identifier information to be queried, it can automatically match the corresponding sub-warehouse according to the rules and call the unique identifier and associated data in the warehouse, ensuring that the query interface can complete the retrieval and retrieval of all data across sub-warehouses.

[0146] The binary file version confirmation method provided in this application effectively solves the storage pressure of massive binary file associated data by dividing the target database into hierarchical and warehouse-based partitions. This makes data storage more orderly, and the associated data is stored in warehouses according to rules, ensuring the systematic nature of data management and improving data storage efficiency. By establishing a suitable query interface and associating it with each warehouse, the data query channel is opened up, and the interface is given the ability to call data across warehouses. This greatly improves the matching of the identifier information to be queried and the speed of data retrieval, ensuring the accuracy and speed of data query during the binary version confirmation process.

[0147] Figure 4 Flowchart of the binary file version verification method provided in the embodiments of this application Figure 5 ,like Figure 6 As shown, this embodiment, based on the above embodiments, provides a detailed explanation of the process for matching, retrieving, and outputting version information, including:

[0148] S501. Input the identification information to be queried into the query interface of the target database, and according to the query interface, retrieve the target unique identifier in each sub-compartment of the target database that is consistent with the identification information to be queried.

[0149] The user-provided identifier information is entered into the corresponding query interface of the target database. Based on the relationship between the query interface and each sub-warehouse, a full search is performed in each sub-warehouse of the target database according to the preset search rules. Finally, the target unique identifier that is completely consistent with the identifier information to be queried is selected, and the accurate matching and retrieval of the identifier information is completed.

[0150] Specifically, after the identifier information to be queried is entered in the format required by the query interface, the interface automatically triggers a cross-warehouse retrieval instruction. Based on the encoding rules of the unique identifier, the corresponding warehouse is searched first, and then the remaining warehouses are searched. During the retrieval process, the consistency of information is compared in real time to accurately locate and extract all matching target unique identifiers.

[0151] S502. Determine the corresponding target-related data based on the target's unique identifier.

[0152] Using the retrieved target unique identifier as the core retrieval basis, and leveraging the index relationships established for the unique identifier in the target database sub-warehouses, a precise search is performed within the corresponding sub-warehouses to ultimately determine all target-related data bound to the target unique identifier, ensuring a precise correspondence between the retrieved data and the target unique identifier.

[0153] S503. Based on the target association data, determine the corresponding target source code version information, target patch number information, and target compilation environment information.

[0154] From the identified target-related data, information is split and extracted according to the data storage classification rules to obtain target source code version information, target patch number information, and target compilation environment information corresponding to the target's unique identifier. The extraction process retains the original attributes and correspondences of each type of information.

[0155] Specifically, according to the integration format of the associated data, the target associated data is structurally split, and the source code version, patch number, and compilation environment related information are extracted in sequence. The extracted information is then format-validated and validity-verified, and the verified information is marked as target source code version information, target patch number information, and target compilation environment information, respectively.

[0156] S504. Integrate the target source code version information, target patch number information, and target compilation environment information to generate the version information corresponding to the identifier information to be queried, and output the version information value to the interactive terminal.

[0157] The extracted and verified target source code version information, target patch number information, and target compilation environment information are systematically integrated according to a preset display format to generate version information that corresponds one-to-one with the identifier information to be queried. Then, the integrated version information is pushed to the corresponding interactive terminal to complete the output display of the information.

[0158] Specifically, the classification logic of target source code version information, target patch number information, and target compilation environment information is integrated into standardized display content. After generating complete version information, the version information is pushed to the user's interactive terminal in real time through the communication link between the query interface and the interactive terminal, and displayed in a clear and structured form for easy viewing by the user.

[0159] The binary file version confirmation method provided in this application can quickly and accurately match the corresponding target unique identifier by inputting the identifier information to be queried into the query interface and searching across sub-warehouses. It can also determine the target associated data by relying on the index, thereby improving the efficiency and accuracy of data retrieval. It can extract various types of target information from the associated data, ensuring the completeness and effectiveness of information extraction. It can integrate various types of target information to generate version information and output it to the interactive terminal, thereby providing users with clear and complete version-related data. It realizes the rapid matching, accurate retrieval and intuitive output of binary file version information, and greatly improves the efficiency of version location during problem investigation.

[0160] Figure 6 This is a schematic diagram of the binary file version verification device provided in an embodiment of this application. The device in this embodiment can be in the form of software and / or hardware. For example... Figure 7As shown, the binary file version verification device 600 provided in this application embodiment includes: a first acquisition module 601, a second acquisition module 602, a generation module 603, an association module 604, a third acquisition module 605, and a processing module 606.

[0161] The first acquisition module 601 is used to acquire the target binary file to be processed, wherein the target binary file includes the pre-built binary file when the release version is released and the compiled binary file generated during compilation;

[0162] The second acquisition module 602 is used to acquire the corresponding source code version information, patch number information and compilation environment information based on the target binary file, wherein the patch number information corresponds to the relevant identification information in the released patch file;

[0163] The generation module 603 is used to process the target binary file according to preset operation rules to generate a corresponding unique identifier;

[0164] The association module 604 is used to associate the unique identifier, source code version information, patch number information and compilation environment information to obtain association data, and write the association data into the target database for storage;

[0165] The third acquisition module 605 is used to acquire the query identifier information input by the user through a preset interactive terminal, wherein the query identifier information is obtained by calculating the target binary file through a preset tool;

[0166] The processing module 606 is used to match and retrieve the version information corresponding to the identifier information to be queried in the target database, and output the version information to the interactive terminal.

[0167] In one possible implementation, the generation module 603 is further configured to:

[0168] For the pre-built binary file, the first full data of the pre-built binary file is obtained through the relevant commands of the pre-built source code management system;

[0169] For compiled binary files, after the compilation process is completed, obtain the second full data of the compiled binary file;

[0170] A preset hash operation method is used to calculate the hash value of the first and second full data sets. The hash value is then used as the unique identifier of the target binary file. The preset hash operation method is a 256-bit secure hash operation.

[0171] In one possible implementation, the association module 604 is further configured to:

[0172] Using the unique identifier corresponding to the target binary file as the association primary key, and using the source code version information, patch number information, and compilation environment information corresponding to the target binary file as multiple corresponding association fields, a mapping relationship between the association primary key and each association field is established.

[0173] Based on the mapping relationship, unique identifiers, source code version information, patch number information, and compilation environment information are integrated to generate associated data;

[0174] Based on the associated primary key, establish a mapping between the associated primary key and the patch number information;

[0175] Based on the association mapping, locate the patch corresponding to the target binary file;

[0176] Receive patch integration commands sent by users via interactive terminals;

[0177] Update the patch number information and associated data corresponding to the target binary file according to the patch merge instruction.

[0178] In one possible implementation, the association module 604 is further configured to:

[0179] The target database is divided into multiple sub-warehouses using a database layering approach.

[0180] The unique identifier, source code version information, patch number information, and compilation environment information in the associated data are stored in each sub-warehouse corresponding to the target database.

[0181] In one possible implementation, the association module 604 is further configured to:

[0182] Based on the target database, establish the corresponding query interface;

[0183] The query interface is associated with each sub-warehouse. The query interface is used to receive the identification information to be queried and to perform subsequent query operations. The query interface can call the unique identifier and corresponding associated data stored in each sub-warehouse.

[0184] In one possible implementation, the processing module 606 is further configured to:

[0185] Input the identifier information to be queried into the query interface of the target database;

[0186] Based on the query interface, retrieve the target unique identifier that matches the query identifier information in each sub-warehouse of the target database;

[0187] Based on the target's unique identifier, determine the corresponding target-related data;

[0188] Based on the target association data, determine the corresponding target source code version information, target patch number information, and target compilation environment information;

[0189] The target source code version information, target patch number information, and target compilation environment information are integrated to generate the version information corresponding to the identifier information to be queried, and the version information value is output to the interactive terminal.

[0190] The binary file version verification device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0191] Figure 7 A schematic diagram of the structure of a binary file version verification device provided in an embodiment of this application. ​ As shown, the binary file version verification device 700 provided in this embodiment includes at least one processor 701 and a memory 702. Optionally, the device 700 further includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus.

[0192] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to perform the above-described method.

[0193] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0194] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0195] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0196] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0197] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0198] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0199] This application also provides a chip including at least one processor, which is used to execute program instructions to perform the above-described method.

[0200] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0201] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0202] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0203] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0204] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0205] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0206] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0207] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for verifying the version of a binary file, characterized in that, include: Obtain the target binary file to be processed, wherein the target binary file includes the pre-built binary file used in the release version and the compiled binary file generated during compilation; Based on the target binary file, obtain the corresponding source code version information, patch number information, and compilation environment information, wherein the patch number information corresponds to the relevant identification information in the released patch file; The target binary file is processed according to preset operation rules to generate a corresponding unique identifier; The unique identifier, the source code version information, the patch number information, and the compilation environment information are associated to obtain associated data, and the associated data is written into the target database for storage. The system obtains the user-inputted identifier information through a preset interactive terminal, wherein the identifier information is obtained by calculating the target binary file using a preset tool. Based on the identifier information to be queried, the version information corresponding to the identifier information to be queried is matched and retrieved in the target database, and the version information is output to the interactive terminal.

2. The method according to claim 1, characterized in that, The step of processing the target binary file according to preset operation rules to generate a corresponding unique identifier includes: For the preset binary file, the first full data of the preset binary file is obtained through relevant commands of the preset source code management system; For the compiled binary file, after the compilation process is completed, the second full data of the compiled binary file is obtained; A preset hash operation method is used to calculate the corresponding hash value of the first full data and the second full data, and the hash value is used as the unique identifier corresponding to the target binary file. The preset hash operation method is a 256-bit secure hash operation.

3. The method according to claim 2, characterized in that, The step of associating the unique identifier, the source code version information, the patch number information, and the compilation environment information to obtain associated data includes: Using the unique identifier corresponding to the target binary file as the association primary key, and using the source code version information, patch number information, and compilation environment information corresponding to the target binary file as multiple corresponding association fields, a mapping relationship between the association primary key and each of the association fields is established; Based on the mapping relationship, the unique identifier, the source code version information, the patch number information, and the compilation environment information are integrated to generate the associated data; Based on the associated primary key, establish an association mapping between the associated primary key and the patch number information; Based on the association mapping, locate the patch corresponding to the target binary file; Receive patch integration instructions sent by the user through the interactive terminal; Update the patch number information and associated data corresponding to the target binary file according to the patch merge instruction.

4. The method according to any one of claims 1-3, characterized in that, The step of writing the associated data into the target database for storage includes: The target database is divided into multiple sub-warehouses using a database layering approach. The unique identifier, source code version information, patch number information, and compilation environment information in the associated data are stored in each of the sub-warehouses corresponding to the target database.

5. The method according to claim 4, characterized in that, After writing the associated data into the target database for storage, the method further includes: Based on the target database, establish a corresponding query interface; The query interface is associated with each of the sub-warehouses. The query interface is used to receive the identifier information to be queried and perform subsequent query operations. The query interface can call the unique identifier and the corresponding associated data stored in each of the sub-warehouses.

6. The method according to claim 5, characterized in that, The step of matching and retrieving version information corresponding to the query identifier information from the target database, and outputting the version information to the interactive terminal, includes: The identifier information to be queried is input into the query interface of the target database; According to the query interface, retrieve the target unique identifier that matches the query identifier information in each of the sub-warehouses in the target database; Based on the target's unique identifier, determine the corresponding target-related data; Based on the target association data, determine the corresponding target source code version information, target patch number information, and target compilation environment information; The target source code version information, the target patch number information, and the target compilation environment information are integrated to generate the version information corresponding to the query identifier information, and the version information is output to the interactive terminal.

7. A binary file version verification device, characterized in that, include: The first acquisition module is used to acquire the target binary file to be processed, wherein the target binary file includes the preset binary file when the release version is released and the compiled binary file generated during compilation; The second acquisition module is used to acquire the corresponding source code version information, patch number information and compilation environment information based on the target binary file, wherein the patch number information corresponds to the relevant identification information in the released patch file; The generation module is used to process the target binary file according to preset operation rules to generate a corresponding unique identifier; The association module is used to associate the unique identifier, the source code version information, the patch number information, and the compilation environment information to obtain association data, and write the association data into the target database for storage; The third acquisition module is used to acquire the query identifier information input by the user through a preset interactive terminal, wherein the query identifier information is obtained by calculating the target binary file through a preset tool; The processing module is used to match and retrieve version information corresponding to the query identifier information in the target database according to the query identifier information, and output the version information to the interactive terminal.

8. A binary file version verification device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images