Matching information generation method, software package matching relationship determination method, and device

Abstract

The present application provides a matching information generation method, a software package matching relationship determination method, and a device. The matching information generation method comprises: obtaining version information of an interface set of a first software package, and obtaining version information of an interface set of a second software package, wherein the interface set of the first software package has an interaction relationship with the interface set of the second software package; and on the basis of the version information of the interface set of the first software package and the version information of the interface set of the second software package, generating product matching information of the first software package, wherein the product matching information is used for indicating a matching relationship between the interface set of the first software package and the interface set of the second software package. By using this means, the product matching information of the first software package can be automatically generated, reducing the labor cost, and improving the efficiency.

Description

Method for generating matching information, method and device for determining matching relationship of software package

[0001] This application claims priority to the Chinese patent application with application number 202311767027.9 filed with the State Intellectual Property Office of China on December 21, 2023, and priority to the Chinese patent application entitled “Method for generating supporting information, method and device for determining supporting relationship of software package”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of data processing technology, and in particular to a method for generating matching information, a method for determining matching relationships of software packages, and a data processing device. Background Art

[0003] A product may contain multiple software packages, often with different release cadences. New versions of software packages may also add functionality that interacts with other packages. Determining the interoperability between these packages is a complex issue for package version management.

[0004] Currently, the version matching management between different software packages usually adopts the method of manual verification and confirmation based on the entire software package, performing compatibility tests on each software package to determine whether the software packages are compatible with each other, and then outputting the version matching table of the software packages.

[0005] However, manually confirming the matching relationship of software packages has the disadvantages of heavy workload, low efficiency and difficult management. Summary of the Invention

[0006] The present application discloses a method for generating matching information, a method for determining matching relationships of software packages, and a data processing device, which can automatically perform version matching verification of software packages with high efficiency.

[0007] In the first aspect, the present application provides a method for generating supporting information. It is understood that the method for generating supporting information can be executed by a data processing device, which can be an electronic device, or a processor or chip (system) or circuit for an electronic device. The present application does not limit this. The method for generating supporting information includes:

[0008] Obtaining version information of an interface set of a first software package and obtaining version information of an interface set of a second software package, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship. Generating product matching information for the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package, wherein the product matching information indicates the matching relationship between the interface set of the first software package and the interface set of the second software package.

[0009] This application obtains the version information of the interface set of a first software package and the version information of the interface set of a second software package, and then generates product support information for the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package. This method can automatically generate product support information for the first software package, reducing labor costs and improving efficiency.

[0010] A software package's interface is the connection or interaction between software programs, allowing them to exchange information without having to deal with their own internal details. A software package's interface can also serve as a bridge between developers and users, allowing users to access software services and connecting different software programs. A software package's interface set can consist of one or more interfaces.

[0011] The interface set of the first software package interacts with the interface set of the second software package. This means that the interface set of the first software package and the interface set of the second software package must be used together to complete a specific function. For example, the communication interface of a sensor in the interface set of the first software package and the communication interface of a sensor in the interface set of the second software package interact with each other, and their use together can realize the function of transmitting sensor data.

[0012] In one possible implementation, the version information includes a major version number. If the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible. If the major version number of the interface set of the first software package and the major version number of the interface set of the second software package are different, the interface set of the first software package and the interface set of the second software package are not compatible.

[0013] In this implementation, whether the interface sets of the software packages are compatible is confirmed based on whether the major version numbers of the interface sets of the software packages are the same, which can improve the efficiency of confirming the compatible relationship between the interface sets of the software packages.

[0014] It is understandable that the version information includes a major version number. That is, the version information of the interface set of the first software package includes a major version number. The version information of the interface set of the second software package also includes a major version number.

[0015] The software interface may change depending on the application scenario of the software function. This change may include, for example, modification or deletion of an interface. In one possible implementation, the interface set of the first software package includes multiple interfaces, and the major version number of the interface set of the first software package is updated when one or more of the multiple interfaces are modified or deleted.

[0016] In this implementation, the major version number of a software package is updated when an interface is modified or deleted. This design allows for unified and standardized version information for all software packages, facilitating verification of supporting information based on the major version number, thereby improving the efficiency of verifying supporting relationships.

[0017] When a new software function or function point is added, a new software interface will be added. In a possible implementation, the version information of the interface set of the first software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the first software package.

[0018] In this implementation, the minor version number of the software package is updated when a new interface is added. Based on this design, by considering the minor version number, it is possible to better distinguish scenarios where version information has changed.

[0019] In a possible implementation, the version information of the interface set of the second software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the second software package.

[0020] Optionally, if the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible. In this case, the minor version number of the interface set of the first software package and the minor version number of the interface set of the second software package can be the same or different.

[0021] If the major version number of the interface set of the first software package is different from the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are incompatible. In this case, the minor version number of the interface set of the first software package and the minor version number of the interface set of the second software package can be the same or different.

[0022] In a possible implementation, the first software package may be, for example, a mobile data center (MDC) software package, and the second software package may be, for example, an MDC development tool (MDC Development Studio, MDS) software package.

[0023] In one possible implementation, the method for generating the compatibility information can be applied before a software package is released. For example, before a software package is released, the compatibility relationship between the software package and existing (already released) software packages can be determined. This allows users to directly refer to the compatibility information of the software package when using the software package after it is released to know which software packages are compatible with it, thereby improving user convenience.

[0024] In a second aspect, the present application provides a method for determining software package matching relationships. It is understood that the method for determining software package matching relationships can be performed by a data processing device, which can be an electronic device, or a processor or chip (system) or circuit for an electronic device, and the present application does not limit this. The method for determining software package matching relationships includes:

[0025] A first software package and a second software package are obtained, wherein a first interface set of the first software package and a second interface set of the second software package have an interactive relationship. A matching relationship between the first interface set of the first software package and the second interface set of the second product is determined based on version information of the first interface set of the first software package and version information of the second interface set of the second software package. If the first interface set of the first software package and the second interface set of the second product are incompatible, a prompt message is output, the prompt message including information related to the incompatibility.

[0026] This application obtains a first software package and a second software package, and based on the version information of the first interface set of the first software package and the version information of the second interface set of the second software package, determines the compatibility relationship between the first interface set of the first software package and the second interface set of the second product. Furthermore, when the first interface set of the first software package and the second interface set of the second product are incompatible, a prompt message is output. This approach allows users to be given compatibility prompts based on the internal functional characteristics of the software when software is incompatible, allowing users to know which software or software is incompatible, saving time in locating the problem.

[0027] A software package's interface is the connection or interaction between software programs, allowing them to exchange information without having to deal with their own internal details. A software package's interface can also serve as a bridge between developers and users, allowing users to access software services and connecting different software programs. A software package's interface set can consist of one or more interfaces.

[0028] The first interface set of the first software package and the second interface set of the second software package interact with each other. This means that the first interface set of the first software package and the second interface set of the second software package must be used together to achieve a specific function. For example, the communication interface of a sensor in the first interface set of the first software package and the communication interface of a sensor in the second interface set of the second software package interact with each other, and using them together can achieve the function of transmitting sensor data.

[0029] In a possible implementation, the prompt information may be that the first interface set of the first software package and the second interface set of the second product are not compatible.

[0030] In a second possible implementation, the prompt information may be an upgrade message. For example, if the first interface set of the first software package and the second interface set of the second product are incompatible, and the major version number of the first interface set of the first software package is lower than the major version number of the second interface set of the second product, the prompt information may be an upgrade message for the first interface set of the first software package.

[0031] In another possible implementation, the prompt information may include that the first interface set of the first software package is incompatible with the second interface set of the second product, and further includes upgrading the first interface set of the first software package.

[0032] Based on the prompt information, the user can know which software or softwares are not compatible, thereby saving positioning time. The prompt information can be at least one of text information, voice information, etc., and this solution does not limit this.

[0033] In one possible implementation, the version information includes a major version number. If the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are compatible. If the major version number of the first interface set of the first software package and the major version number of the second interface set of the second software package are different, the first interface set of the first software package and the second interface set of the second software package are not compatible.

[0034] In this implementation, whether the interface sets of the software packages are compatible is confirmed based on whether the major version numbers of the interface sets of the software packages are the same, which can improve the efficiency of confirming the compatible relationship between the interface sets of the software packages.

[0035] It is understandable that the version information includes a major version number. That is, the version information of the first interface set of the first software package includes a major version number. The version information of the second interface set of the second software package also includes a major version number.

[0036] The software interface may change depending on the application scenario of the software function. This change may include, for example, modification or deletion of an interface. In one possible implementation, the first interface set of the first software package includes multiple interfaces, and the major version number of the first interface set of the first software package is updated when one or more of the multiple interfaces are modified or deleted.

[0037] In this implementation, the major version number of a software package is updated when an interface is modified or deleted. This design allows for unified and standardized version information for all software packages, facilitating verification of supporting information based on the major version number, thereby improving the efficiency of verifying supporting relationships.

[0038] When a new software function or function point is added, a new software interface will be added. In one possible implementation, the version information of the first interface set of the first software package also includes a minor version number, and the minor version number is updated when a new interface is added to the first interface set of the first software package.

[0039] In this implementation, the minor version number of the software package is updated when a new interface is added. Based on this design, by considering the minor version number, it is possible to better distinguish scenarios where version information has changed.

[0040] In a possible implementation, the version information of the second interface set of the second software package also includes a minor version number, and the minor version number is updated when a new interface is added to the second interface set of the second software package.

[0041] Optionally, if the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are compatible. In this case, the minor version number of the first interface set of the first software package and the minor version number of the second interface set of the second software package may be the same or different.

[0042] If the major version number of the first interface set of the first software package is different from the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are incompatible. In this case, the minor version number of the first interface set of the first software package and the minor version number of the second interface set of the second software package can be the same or different.

[0043] In a possible implementation, the first software package may be, for example, a mobile data center (MDC) software package, and the second software package may be, for example, an MDC development tool (MDC Development Studio, MDS) software package.

[0044] In one possible implementation, the software package matching relationship determination method may be applied before running a software package, for example, after running a first software package and before loading a second software package.

[0045] In a third aspect, the present application provides a data processing device. It is understood that the data processing device may be an electronic device, or a processor, chip (system), or circuit for an electronic device, and the present application does not limit this. The data processing device includes:

[0046] The acquisition module is configured to acquire version information of an interface set of a first software package and version information of an interface set of a second software package, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship.

[0047] A processing module is used to generate product matching information of the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package, wherein the product matching information is used to indicate the matching relationship between the interface set of the first software package and the interface set of the second software package.

[0048] In this application, a data processing device includes an acquisition module and a processing module. The acquisition module is used to acquire version information of an interface set of a first software package and version information of an interface set of a second software package, and the processing module is used to generate product matching information of the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package.

[0049] In one possible implementation, the version information includes a major version number. If the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible. If the major version number of the interface set of the first software package and the major version number of the interface set of the second software package are different, the interface set of the first software package and the interface set of the second software package are not compatible.

[0050] In a possible implementation, the interface set of the first software package includes multiple interfaces, and the major version number of the interface set of the first software package is updated when one or more interfaces among the multiple interfaces are modified or deleted.

[0051] In a possible implementation, the version information of the interface set of the first software package further includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the first software package.

[0052] In a fourth aspect, the present application provides a data processing device. It is understood that the data processing device may be an electronic device, or a processor, chip (system), or circuit for an electronic device, and the present application does not limit this. The data processing device includes:

[0053] The acquisition module is configured to acquire a first software package and a second software package, wherein a first interface set of the first software package and a second interface set of the second software package have an interactive relationship.

[0054] The processing module is configured to determine a matching relationship between the first interface set of the first software package and the second interface set of the second product according to the version information of the first interface set of the first software package and the version information of the second interface set of the second software package.

[0055] The processing module is further configured to output a prompt message when the first interface set of the first software package and the second interface set of the second product are incompatible, wherein the prompt message includes information related to the incompatibility.

[0056] In this application, a data processing device includes an acquisition module and a processing module. The acquisition module is used to acquire a first software package and a second software package, and the processing module is used to determine the matching relationship between the first interface set of the first software package and the second interface set of the second product based on the version information of the first interface set of the first software package and the version information of the second interface set of the second software package. The processing module is also used to output a prompt message when the first interface set of the first software package and the second interface set of the second product are not compatible.

[0057] In one possible implementation, the version information includes a major version number. If the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are compatible. If the major version number of the first interface set of the first software package and the major version number of the second interface set of the second software package are different, the first interface set of the first software package and the second interface set of the second software package are not compatible.

[0058] In a possible implementation, the first interface set of the first software package includes multiple interfaces, and the major version number of the first interface set of the first software package is updated when one or more interfaces among the multiple interfaces are modified or deleted.

[0059] In a possible implementation, the version information of the first interface set of the first software package further includes a minor version number, and the minor version number is updated when a new interface is added to the first interface set of the first software package.

[0060] In a fifth aspect, the present application provides a computing device, comprising a processor coupled to a memory, wherein the processor is configured to call computer program instructions stored in the memory to execute the method described in any possible implementation of the first aspect or the second aspect.

[0061] In a sixth aspect, the present application provides a chip, which is used to implement the method described in any possible implementation of the first aspect or the second aspect.

[0062] In the seventh aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on at least one processor, the method described in any aspect of the first to second aspects or any possible implementation method can be implemented.

[0063] In an eighth aspect, the present application provides a computer program product, comprising computer instructions that, when executed on at least one processor, can implement the method described in any of the first and second aspects or any possible implementation thereof. The computer program product can be a software installation package, which can be downloaded and executed on a computing device when the method is to be used.

[0064] The beneficial effects of the technical solutions provided in the third to eighth aspects of this application can refer to the beneficial effects of the technical solutions in the first to second aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] The following is an introduction to the drawings used in the embodiments of this application.

[0066] FIG1a is a schematic diagram of a data processing system provided in an embodiment of the present application;

[0067] FIG1b is a schematic diagram of a scenario provided by an embodiment of the present application;

[0068] FIG2 is a flow chart of a method for generating supporting information provided in an embodiment of the present application;

[0069] FIG3 is a schematic diagram of supporting information provided in an embodiment of the present application;

[0070] FIG4 is a flow chart of a method for determining a software package matching relationship according to an embodiment of the present application;

[0071] FIG5 is a schematic structural diagram of a data processing device provided in an embodiment of the present application;

[0072] FIG6 is a schematic structural diagram of another data processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] In order to make the purpose, technical solutions and advantages of this application clearer, the embodiments of this application will be described below in conjunction with the drawings in the embodiments of this application.

[0074] The terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0075] The “embodiment” mentioned herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be understood explicitly and implicitly by those skilled in the art that in the various embodiments of the present application, unless otherwise specified and there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.

[0076] It should be understood that in the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0077] For ease of understanding, the following examples provide some explanations of concepts related to the embodiments of the present application for reference.

[0078] 1. Software package interface set

[0079] A software package's interface is the connection or interaction between software programs, allowing them to exchange information without having to deal with their own internal details. A software package's interface can also serve as a bridge between developers and users, allowing users to access software services and connecting different software programs.

[0080] A package's interface set can contain one or more interfaces.

[0081] 2. Product Support

[0082] If the interaction between two products can be used normally, it means that the two products are compatible.

[0083] The above exemplary description of the concepts can be applied in the following embodiments.

[0084] The data processing system of the embodiment of the present application will be described in detail below with reference to the accompanying drawings. Referring to FIG1 a , FIG1 a is a schematic diagram of a data processing system applicable to the embodiment of the present application, the system including a server 101 and a terminal 102 .

[0085] The server 101 is a device with centralized computing capabilities. Exemplarily, the server 101 can be implemented by a server, a virtual machine, a cloud, or a robot.

[0086] When the server 101 includes a server, the server type includes but is not limited to a general-purpose computer, a dedicated server computer, a blade server, etc. This application does not impose a strict limit on the number of servers included in the server 101, and the number can be one or multiple (such as a server cluster, etc.).

[0087] A virtual machine is a computing module that simulates complete hardware system functions through software and runs in a completely isolated environment. Of course, in addition to virtual machines, the server 101 can also be implemented through other computing instances, such as containers.

[0088] The cloud is a software platform that uses application virtualization technology to enable one or more software or applications to be developed and run in an independent virtualized environment. Optionally, when the server 101 is implemented via the cloud, the cloud can be deployed on a public cloud, a private cloud, or a hybrid cloud.

[0089] The terminal 102 may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.

[0090] In one possible implementation, the server 101 obtains version information of the interface set of the first software package to be released, and obtains version information of the interface set of the second software package of the terminal 102, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship. The server 101 generates product matching information for the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package. The product matching information is used to indicate the matching relationship between the interface set of the first software package and the interface set of the second software package. In this way, the product matching information of the first software package can be automatically generated, reducing labor costs and improving efficiency. Based on this design, when using the first software package, the user can know the software package that matches the first software package based on the product matching information, thereby improving user convenience.

[0091] In one possible implementation, as shown in FIG1b , the terminal 102 may be a vehicle. That is, the software package may be a software package for installation or use in a vehicle, such as a Mobile Data Center (MDC) software package. A vehicle is a device with communication and computing capabilities that can provide mobile travel services to users.

[0092] The above describes the architecture of the embodiment of the present application. The following describes the method of the embodiment of the present application in detail.

[0093] Referring to Figure 2, it is a flow chart of a method for generating supporting information provided by an embodiment of the present application. The method for generating supporting information as shown in Figure 2 may include steps 201-202. It should be understood that this application is described in the order of 201-202 for the convenience of description, and is not intended to limit execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, number of executions, etc. of the above one or more steps. The following description is based on the example of the execution subject of steps 201-202 of the method for generating supporting information being a server, and this application is also applicable to other execution subjects. Steps 201-202 are specifically as follows:

[0094] 201. Obtain version information of an interface set of a first software package, and obtain version information of an interface set of a second software package, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship.

[0095] For example, the first software package may be a platform software package, and the second software package may be a tool software package, but this solution does not impose any limitation on this.

[0096] The interface set of the first software package may include one interface or multiple interfaces. The multiple interfaces in the software package's interface set may be used to implement a single function or multiple functions. For example, the interface set of the first software package includes interface A, interface B, and interface C. Interface A, interface B, and interface C are all used to implement the same function. Alternatively, interface A and interface B are used to implement a first function, and interface C is used to implement a second function, where the first and second functions are different.

[0097] For the interface set of the second software package, please refer to the introduction of the interface set of the first software package, which will not be repeated here.

[0098] The interface set of the first software package interacts with the interface set of the second software package. This means that the interface set of the first software package and the interface set of the second software package must be used together to complete a specific function. For example, the communication interface of a sensor in the interface set of the first software package and the communication interface of a sensor in the interface set of the second software package interact with each other, and their use together can realize the function of transmitting sensor data.

[0099] The version information of the interface set may be, for example, a version number, etc. The version number may be one or more digits and / or letters, and this solution does not impose any restrictions on this.

[0100] The server may obtain the version information of the interface set of the first software package from the first software package, and obtain the version information of the interface set of the second software package from the second software package.

[0101] In one possible implementation, the version information of the interface set of a first software package is stored in the version information table of the first software package's interface set, and the version information of the interface set of a second software package is stored in the version information table of the second software package's interface set. For example, if the interface set of the first software package includes interface A, interface B, and interface C, the version information table of the interface set of the first software package will include the version information of interface A, interface B, and interface C. For details about the version information table of the interface set of the second software package, please refer to the description of the version information table of the interface set of the first software package and will not be repeated here.

[0102] By reading the version information table of the interface set of the first software package and the version information table of the interface set of the second software package, the version information of the interface set of the first software package and the version information of the interface set of the second software package can be obtained.

[0103] 202. Generate product matching information of the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package, where the product matching information is used to indicate a matching relationship between the interface set of the first software package and the interface set of the second software package.

[0104] In one possible implementation, the version information includes a major version number. For example, the version information of the interface set of the first software package includes a major version number, and the version information of the interface set of the second software package also includes a major version number. Exemplarily, the major version number can be 1, 2, 3, etc. It can also be other numbers and / or letters, and this solution does not limit this.

[0105] In a possible implementation, by comparing the major version number of the interface set of the first software package with the major version number of the interface set of the second software package, it can be determined whether the interface set of the first software package and the interface set of the second software package are compatible.

[0106] If the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible.

[0107] If the major version number of the interface set of the first software package is different from the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are not compatible.

[0108] In this example, whether the interface sets of the software packages are compatible is confirmed based on whether the major version numbers of the interface sets of the software packages are the same. This can improve the efficiency of confirming the compatible relationship between the interface sets of the software packages.

[0109] The software interface may change depending on the application scenario of the software function. This change may include, for example, modification or deletion of an interface. In one possible implementation, the interface set of the first software package includes multiple interfaces, and the major version number of the interface set of the first software package is updated when one or more of the multiple interfaces are modified or deleted.

[0110] For example, the interface set of a first software package includes interface D. The major version number of interface D is 1. Based on different application scenarios of the software function, interface D is modified. When the first software package releases a new interface E, the major version number of interface E is updated to 2, for example. Interface D and interface E are interfaces with the same function.

[0111] For example, when interface D of the first software package is deleted, interface D no longer exists. When the first software package releases interface E, the major version number of interface E is updated to, for example, 2. Interface D and interface E have the same functionality. For another example, when the second software package releases interface F, the major version number of interface F is also updated to, for example, 2. Interface F of the second software package interacts with interface E of the first software package.

[0112] When a new software function or function point is added, a new software interface will be added. In a possible implementation, the version information of the interface set of the first software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the first software package.

[0113] That is, the version information of the interface set of the first software package includes not only the major version number but also the minor version number. For example, the interface set of the first software package includes interface G. Here, interface G has a major version number of 1 and a minor version number of 0. When interface H is added to the interface set of the first software package, interface H has a major version number of 1 and a minor version number of 1. Of course, the minor version number can also be 2, etc., and this solution does not impose any restrictions on this.

[0114] The above example is introduced using the example of changes or additions to the software interface of the first software package. For the second software package, please refer to the above description. For example, the version information of the interface set of the second software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the second software package, etc., which will not be repeated here.

[0115] Optionally, if the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible. In this case, the minor version number of the interface set of the first software package and the minor version number of the interface set of the second software package can be the same or different.

[0116] If the major version number of the interface set of the first software package is different from the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are incompatible. In this case, the minor version number of the interface set of the first software package and the minor version number of the interface set of the second software package can be the same or different.

[0117] In a possible implementation, the first software package may be, for example, a mobile data center (MDC) software package, and the second software package may be, for example, an MDS software package.

[0118] The version information of the interface set of the MDC software package can be exemplified as follows:

[0119] The version information of the MDC-MDC application visualization debugging tool (MDC Application Visualizer, MVIZ) interface is 2.0; that is, the major version number of the MDC-MVIZ interface is 2, and the minor version number is 0.

[0120] The version information of the MDC-MDC detection / calibration / diagnostic tool (MCD) interface is 2.0; that is, the major version number of the MDC-MCD interface is 2, and the minor version number is 0.

[0121] The version information of the MDC-MDS interface is 2.0; that is, the major version number of the MDC-MDS interface is 2, and the minor version number is 0.

[0122] The version information of the interface set of the MDS software package can be exemplified as follows:

[0123] The version information of the interface software development kit (SDK)-MDS is 1.0; that is, the major version number of the interface SDK-MDS is 1, and the minor version number is 0.

[0124] The version information of the MDC-MDS interface is 1.0; that is, the major version number of the MDC-MDS interface is 1 and the minor version number is 0.

[0125] The product matching information of the first software package (MDC software package) may be, for example, a product matching table as shown in Table 1:

[0126] Table 1

[0127] The interface set in the MDC software package has a major version number of 2, while the interface set in the MDS software package has a major version number of 1. The major version numbers of the two are different, so the interface set in the MDC software package and the interface set in the MDS software package are not compatible.

[0128] For another example, the first software package may be an MDC SDK software package, and the second software package may be an MDS software package.

[0129] The version information of the interface set of the MDC SDK software package can be exemplified as follows:

[0130] The version information of the interface SDK-MDS is 1.0; that is, the major version number of the interface SDK-MDS is 1 and the minor version number is 0.

[0131] The product supporting information of the first software package (MDC SDK software package) may be, for example, the product supporting table shown in Table 2:

[0132] Table 2

[0133] Among them, since the major version number of the interface set in the above-mentioned MDC SDK software package is 1, the major version number of the interface set of the MDS software package is 1, and the major version numbers of the two are the same, the interface set of the MDC software package and the interface set of the MDS software package are compatible.

[0134] This solution uses a first software package and a second software package as examples. It is understood that the first software package can be a single software package or multiple software packages. The second software package can be a single software package or multiple software packages. It is understood that this example can also be applied to confirming the matching relationship between multiple software packages, and this solution does not limit this.

[0135] As shown in FIG3 , the first software package may be, for example, an MDS software package, the second software package may be, for example, an MDC SDK software package, and the third software package may be, for example, an MDC software package.

[0136] The product matching information of the first software package (MDS software package) may be, for example, the product matching table shown in Table 3:

[0137] Table 3

[0138] The above product supporting information is only introduced by taking the product supporting table as an example. The product supporting information can also be in other forms, such as text, graphics, etc., which is not limited in this solution. Among them, the product supporting information of the first software package can be stored in the software package.

[0139] This example only describes the generation of product supporting information for the first software package. For the generation of product supporting information for the second software package, please refer to the description of step 202 , which will not be repeated here.

[0140] In one possible implementation, the method for generating the compatibility information can be applied before a software package is released. For example, before a software package is released, the compatibility relationship between the software package and existing (already released) software packages can be determined. This allows users to directly refer to the compatibility information of the software package when using the software package after it is released to know which software packages are compatible with it, thereby improving user convenience.

[0141] In this embodiment of the present application, the version information of the interface set of a first software package and the version information of the interface set of a second software package are obtained, and product support information for the first software package is generated based on the version information of the interface set of the first software package and the version information of the interface set of the second software package. This method can automatically generate product support information for the first software package, reducing labor costs and improving efficiency.

[0142] The above example is introduced by taking the method for generating supporting information as an example. The embodiment of the present application also provides a method for determining the supporting relationship of a software package. Referring to Figure 4, it is a flow chart of a method for determining the supporting relationship of a software package provided by the embodiment of the present application. Optionally, the method can be applied to the aforementioned data processing system, such as the data processing system shown in Figure 1a or Figure 1b. The method for determining the supporting relationship of a software package as shown in Figure 4 may include steps 401-403. It should be understood that this application is described in the order of 401-403 for the convenience of description, and is not intended to be limited to execution in the above order. The embodiment of the present application does not limit the order of execution, execution time, number of executions, etc. of the above one or more steps. The following description is based on the example of the execution subject of steps 401-403 of the method for determining the supporting relationship of a software package as a server, and this application is also applicable to other execution subjects. Steps 401-403 are as follows:

[0143] 401. Obtain a first software package and a second software package, wherein a first interface set of the first software package and a second interface set of the second software package have an interactive relationship.

[0144] It is understood that the first software package may include one or more interface sets. Each interface set may include one or more interfaces. Different interfaces in an interface set may be used to implement the same functionality or different functionality. Regarding the second software package, it may also include one or more interface sets, etc. For details, please refer to the introduction of the first software package and will not be repeated here.

[0145] The first interface set of the first software package may include one or more interfaces, and the second interface set of the second software package may include one or more interfaces.

[0146] 402. Determine a matching relationship between the first interface set of the first software package and the second interface set of the second product based on the version information of the first interface set of the first software package and the version information of the second interface set of the second software package.

[0147] The version information of the interface set may be, for example, a version number, etc. The version number may be one or more digits and / or letters, and this solution does not impose any restrictions on this.

[0148] In one possible implementation, the version information includes a major version number. For example, the version information for the first interface set of a first software package includes a major version number, and the version information for the second interface set of a second software package also includes a major version number. Exemplarily, the major version number can be 1, 2, 3, etc. It can also be other numbers and / or letters, and this solution does not limit this.

[0149] In one possible implementation, by comparing the major version number of the first interface set of the first software package with the major version number of the second interface set of the second software package, it can be determined whether the first interface set of the first software package and the second interface set of the second software package are compatible.

[0150] If the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are compatible.

[0151] If the major version number of the first interface set of the first software package is different from the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are not compatible.

[0152] In this example, whether the interface sets of the software packages are compatible is confirmed based on whether the major version numbers of the interface sets of the software packages are the same. This can improve the efficiency of confirming the compatible relationship between the interface sets of the software packages.

[0153] The software interface may change depending on the application scenario of the software function. This change may include, for example, modification or deletion of an interface. In one possible implementation, the first interface set of the first software package includes multiple interfaces, and the major version number of the first interface set of the first software package is updated when one or more of the multiple interfaces are modified or deleted.

[0154] For example, the first interface set of a first software package includes interface K1. The major version number of interface K1 is 1. Based on different application scenarios of the software function, interface K1 is modified. When the first software package releases a new interface W1, the major version number of interface W1 is updated to 2, for example. Interface K1 and interface W1 are interfaces with the same function.

[0155] For example, when interface K1 of the first software package is deleted, interface K1 no longer exists. When the first software package releases interface W1, the major version number of interface W1 is updated to, for example, 2. Interfaces K1 and W1 have the same functionality. For another example, when the second software package releases interface K2, the major version number of interface K2 is also updated to, for example, 2. Interface K2 of the second software package interacts with interface W1 of the first software package.

[0156] When a new software function or function point is added, a new software interface will be added. In one possible implementation, the version information of the first interface set of the first software package also includes a minor version number, and the minor version number is updated when a new interface is added to the first interface set of the first software package.

[0157] That is, the version information of the first interface set of the first software package includes not only the major version number but also the minor version number. For example, the first interface set of the first software package includes interface M1. Interface M1 has a major version number of 1 and a minor version number of 0. When interface N1 is added to the first interface set of the first software package, interface N1 has a major version number of 1 and a minor version number of 1. Of course, the minor version number can also be 2, etc., and this solution does not impose any restrictions on this.

[0158] The above example is introduced using the example of changes or additions to the software interface of the first software package. For the second software package, please refer to the above description. For example, the version information of the interface set of the second software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the second software package, etc., which will not be repeated here.

[0159] Optionally, if the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are considered compatible. In this case, the minor version number of the first interface set of the first software package and the minor version number of the second interface set of the second software package may be the same or different.

[0160] If the major version number of the first interface set of the first software package is different from the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are incompatible. In this case, the minor version number of the first interface set of the first software package and the minor version number of the second interface set of the second software package can be the same or different.

[0161] 403. When the first interface set of the first software package and the second interface set of the second product are incompatible, output a prompt message, where the prompt message includes information related to the incompatibility.

[0162] In a possible implementation, the prompt information may be that the first interface set of the first software package and the second interface set of the second product are not compatible.

[0163] In a second possible implementation, the prompt information may be an upgrade message. For example, if the first interface set of the first software package and the second interface set of the second product are incompatible, and the major version number of the first interface set of the first software package is lower than the major version number of the second interface set of the second product, the prompt information may be an upgrade message for the first interface set of the first software package.

[0164] In another possible implementation, the prompt information may include that the first interface set of the first software package is incompatible with the second interface set of the second product, and further includes upgrading the first interface set of the first software package.

[0165] The above are just a few examples of prompt information, and this solution does not limit them.

[0166] For example, the server may output the above-mentioned prompt information to the terminal. The prompt information may be at least one of text information, voice information, etc., and this solution does not impose any limitation on this.

[0167] Based on the prompt information, the user can know which software or software are incompatible, thereby saving positioning time.

[0168] In a possible implementation, when the first interface set of the first software package and the second interface set of the second product are matched, the first software package and the second software package are run.

[0169] In one possible implementation, the software package matching relationship determination method may be applied before running a software package, for example, after running a first software package and before loading a second software package.

[0170] In an embodiment of the present application, by obtaining a first software package and a second software package, and based on the version information of the first interface set of the first software package and the version information of the second interface set of the second software package, determining the compatibility relationship between the first interface set of the first software package and the second interface set of the second product; then, when the first interface set of the first software package and the second interface set of the second product are incompatible, a prompt message is output. Using this method, when software is incompatible, a compatibility prompt can be given to the user based on the internal functional characteristics of the software, allowing the user to know which software or software is incompatible, saving locating time.

[0171] It should be noted that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0172] The above describes in detail the method of the embodiment of the present application, and the following provides the device of the embodiment of the present application. It will be understood that in the various device embodiments of the present application, the division of multiple units or modules is only a logical division based on function, and is not intended to limit the specific structure of the device. In a specific implementation, some functional modules may be subdivided into more small functional modules, and some functional modules may be combined into one functional module, but no matter whether these functional modules are subdivided or combined, the general process performed by the device is the same. For example, some devices include a receiving unit and a sending unit. In some designs, the sending unit and the receiving unit can also be integrated into a communication unit, which can implement the functions implemented by the receiving unit and the sending unit. Typically, each unit corresponds to its own program code (or program instructions), and when the program code corresponding to each of these units runs on the processor, the unit is controlled by the processing unit to execute the corresponding process to implement the corresponding function.

[0173] The embodiments of the present application also provide an apparatus for implementing any of the above methods, for example, providing a data processing apparatus including modules (or means) for implementing each step performed by the server in any of the above methods.

[0174] For example, referring to FIG5 , which is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application, the data processing device is used to implement the aforementioned method for generating supporting information, such as the method for generating supporting information shown in FIG2 .

[0175] As shown in FIG5 , the apparatus may include an acquisition module 501 and a processing module 502 , specifically as follows:

[0176] The acquisition module 501 is configured to acquire version information of an interface set of a first software package and version information of an interface set of a second software package, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship.

[0177] The processing module 502 is used to generate product matching information of the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package, wherein the product matching information is used to indicate the matching relationship between the interface set of the first software package and the interface set of the second software package.

[0178] In this application, a data processing device includes an acquisition module and a processing module. The acquisition module is used to acquire version information of an interface set of a first software package and version information of an interface set of a second software package, and the processing module is used to generate product matching information of the first software package based on the version information of the interface set of the first software package and the version information of the interface set of the second software package.

[0179] In one possible implementation, the version information includes a major version number. If the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are compatible. If the major version number of the interface set of the first software package and the major version number of the interface set of the second software package are different, the interface set of the first software package and the interface set of the second software package are not compatible.

[0180] In a possible implementation, the interface set of the first software package includes multiple interfaces, and the major version number of the interface set of the first software package is updated when one or more interfaces among the multiple interfaces are modified or deleted.

[0181] In a possible implementation, the version information of the interface set of the first software package further includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the first software package.

[0182] The introduction of the above modules can be found in the description of the above embodiments and will not be repeated here.

[0183] Alternatively, as shown in FIG5 , the data processing apparatus may be used to implement the aforementioned software package matching relationship determination method, such as the software package matching relationship determination method shown in FIG4 .

[0184] As shown in FIG5 , the apparatus may include an acquisition module 501 and a processing module 502 , specifically as follows:

[0185] The acquisition module 501 is configured to acquire a first software package and a second software package, wherein a first interface set of the first software package and a second interface set of the second software package have an interactive relationship.

[0186] The processing module 502 is configured to determine a matching relationship between the first interface set of the first software package and the second interface set of the second product according to the version information of the first interface set of the first software package and the version information of the second interface set of the second software package.

[0187] The processing module 502 is further configured to output a prompt message when the first interface set of the first software package and the second interface set of the second product are incompatible, wherein the prompt message includes information related to the incompatibility.

[0188] In this application, a data processing device includes an acquisition module and a processing module. The acquisition module is used to acquire a first software package and a second software package, and the processing module is used to determine the matching relationship between the first interface set of the first software package and the second interface set of the second product based on the version information of the first interface set of the first software package and the version information of the second interface set of the second software package. The processing module is also used to output a prompt message when the first interface set of the first software package and the second interface set of the second product are not compatible.

[0189] In one possible implementation, the version information includes a major version number. If the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are compatible. If the major version number of the first interface set of the first software package and the major version number of the second interface set of the second software package are different, the first interface set of the first software package and the second interface set of the second software package are not compatible.

[0190] In a possible implementation, the first interface set of the first software package includes multiple interfaces, and the major version number of the first interface set of the first software package is updated when one or more interfaces among the multiple interfaces are modified or deleted.

[0191] In a possible implementation, the version information of the first interface set of the first software package further includes a minor version number, and the minor version number is updated when a new interface is added to the first interface set of the first software package.

[0192] The introduction of the above modules can be found in the description of the above embodiments and will not be repeated here.

[0193] It should be understood that the division of the modules in the above-mentioned devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or they may be physically separated. In addition, the modules in the data processing device may be implemented in the form of a processor calling software; for example, the data processing device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or the functions of the modules of the device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the modules in the device can be implemented in the form of hardware circuits, and the functions of some or all units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All modules of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0194] 6 is a schematic diagram of the hardware structure of another data processing device provided in an embodiment of the present application. The data processing device 600 shown in FIG6 (the device 600 may be a computer device) includes a memory 601, a processor 602, a communication interface 603, and a bus 604. The memory 601, the processor 602, and the communication interface 603 are connected to each other via the bus 604.

[0195] The memory 601 may be a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0196] The memory 601 can store programs. When the program stored in the memory 601 is executed by the processor 602, the processor 602 and the communication interface 603 are used to execute the various steps of the method for generating supporting information or the various steps of the method for determining the supporting relationship of the software package in the embodiment of the present application.

[0197] The processor 602 is a circuit with signal processing capabilities. In one implementation, the processor 602 can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor 602 can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor 602 is a hardware circuit implemented by an ASIC or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration file and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc. The processor 602 is used to execute relevant programs to implement the functions required to be performed by the units in the data processing device of the embodiment of the present application, or to execute the method for generating supporting information or the method for determining the supporting relationship of the software package of the embodiment of the method of the present application.

[0198] It can be seen that each module in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0199] In addition, the modules in the above device can be fully or partially integrated together, or can be implemented independently. In one implementation, these modules are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the modules of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0200] The communication interface 603 uses a transceiver device such as, but not limited to, a transceiver to implement communication between the apparatus 600 and other devices or a communication network. For example, data can be obtained through the communication interface 603 .

[0201] The bus 604 may include a path for transmitting information between various components of the device 600 (eg, the memory 601 , the processor 602 , and the communication interface 603 ).

[0202] It should be noted that although the device 600 shown in FIG6 only shows a memory, a processor, and a communication interface, in a specific implementation, those skilled in the art will understand that the device 600 also includes other components necessary for normal operation. Furthermore, those skilled in the art will understand that, depending on specific needs, the device 600 may also include hardware components that implement other additional functions. Furthermore, those skilled in the art will understand that the device 600 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily include all of the components shown in FIG6.

[0203] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or processor executes one or more steps in any of the above methods.

[0204] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute one or more steps in any of the above methods.

[0205] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. The mutual coupling, direct coupling, or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, and can be electrical, mechanical or other forms.

[0206] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0207] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for generating matching information, characterized in that: include: Acquire version information of an interface set of a first software package, and acquire version information of an interface set of a second software package, wherein the interface set of the first software package and the interface set of the second software package have an interactive relationship; Product matching information of the first software package is generated according to the version information of the interface set of the first software package and the version information of the interface set of the second software package, wherein the product matching information is used to indicate a matching relationship between the interface set of the first software package and the interface set of the second software package.

2. The method according to claim 1, characterized in that The version information includes a major version number; If the major version number of the interface set of the first software package is the same as the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are matched; If the major version number of the interface set of the first software package is different from the major version number of the interface set of the second software package, the interface set of the first software package and the interface set of the second software package are not compatible.

3. The method according to claim 2, characterized in that The interface set of the first software package includes a plurality of interfaces, and the major version number of the interface set of the first software package is updated when one or more interfaces among the plurality of interfaces are modified or deleted.

4. The method according to claim 3, characterized in that: The version information of the interface set of the first software package also includes a minor version number, and the minor version number is updated when a new interface is added to the interface set of the first software package.

5. A method for determining a software package matching relationship, characterized in that: include: Acquire a first software package and a second software package, wherein a first interface set of the first software package and a second interface set of the second software package have an interactive relationship; Determine, according to the version information of the first interface set of the first software package and the version information of the second interface set of the second software package, a matching relationship between the first interface set of the first software package and the second interface set of the second product; When the first interface set of the first software package and the second interface set of the second product are incompatible, a prompt message is output, wherein the prompt message includes information related to the incompatibility.

6. The method according to claim 5, characterized in that The version information includes a major version number; If the major version number of the first interface set of the first software package is the same as the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are matched; If the major version number of the first interface set of the first software package is different from the major version number of the second interface set of the second software package, the first interface set of the first software package and the second interface set of the second software package are not compatible.

7. The method according to claim 6, characterized in that The first interface set of the first software package includes a plurality of interfaces, and the major version number of the first interface set of the first software package is updated when one or more interfaces among the plurality of interfaces are modified or deleted.

8. The method according to claim 7, characterized in that The version information of the first interface set of the first software package further includes a minor version number, and the minor version number is updated when a new interface is added to the first interface set of the first software package.

9. A computing device, characterized in that include: A processor, the processor is coupled to a memory, and the processor is used to call computer program instructions stored in the memory to execute the method according to any one of claims 1 to 4, or the method according to any one of claims 5 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the method according to any one of claims 1 to 4 or the method according to any one of claims 5 to 8.

Images