Interface calling method and device

Abstract

The invention discloses an interface calling method and device, and the method comprises the steps: obtaining a calling parameter and retrieval information sent by an interface caller; target interface configuration information matched with the retrieval information is obtained from a preset configuration information base based on the retrieval information, and the preset configuration information base comprises interface configuration information corresponding to at least two preset interfaces; calling a target interface corresponding to the target interface configuration information based on the calling parameter and the target interface configuration information to obtain a calling result; and returning a calling result to the interface caller. According to the method and the device, an interface caller does not need to perceive the calling process of different preset interfaces, so that indiscriminate calling can be carried out, and the interface calling difficulty of the interface caller is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of interface calling, and in particular to an interface calling method and device. Background Art

[0002] In the context of multi-device integration and end-cloud integration, we hope to have a unified solution that can support capability calls between different devices, different platforms, and different application types without distinction. However, in the existing technical solutions, in scenarios across devices (such as mobile phones, tablets, car computers, etc.), systems (such as Android, Windows, Linux, IOS, etc.), and application types (such as APP, mini-programs, quick applications, etc.), interface callers need to make different forms of calls for different devices, different systems, and different application types. Indiscriminate calls cannot be made, which makes interface calls more difficult.

[0003] That is, in the prior art, the interface caller cannot make indiscriminate calls, and interface calls are difficult. Summary of the invention

[0004] The embodiments of the present application provide an interface calling method and device, which enable an interface caller to make indiscriminate calls and reduce the interface calling difficulty for the interface caller.

[0005] In a first aspect, the interface calling method provided by the present application includes:

[0006] Get the call parameters and retrieval information sent by the interface caller;

[0007] Based on the search information, acquiring target interface configuration information matching the search information from a preset configuration information library, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces;

[0008] Calling the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result;

[0009] The calling result is returned to the interface caller.

[0010] In a second aspect, the interface calling device provided by the present application includes:

[0011] The first acquisition module is used to acquire the call parameters and retrieval information sent by the interface caller;

[0012] A second acquisition module, configured to acquire target interface configuration information matching the search information from a preset configuration information library based on the search information, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces;

[0013] A calling module, used for calling the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result;

[0014] The return module is used to return the call result to the interface caller.

[0015] In a third aspect, the electronic device provided in the present application includes a memory and a processor, the memory stores a computer program, and the processor is used to run the computer program in the memory to implement the steps in the interface calling method provided in the present application.

[0016] In a fourth aspect, the computer-readable storage medium provided in the present application stores a plurality of instructions, which are suitable for loading by a processor to implement the steps in the interface calling method provided in the present application.

[0017] In a fifth aspect, the computer program product provided in the present application includes a computer program or instructions, which, when executed by a processor, implement the steps in the interface calling method provided in the present application.

[0018] In this application, compared with the related art, the calling parameters and retrieval information sent by the interface caller are obtained; based on the retrieval information, the target interface configuration information matching the retrieval information is obtained from the preset configuration information library, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces; based on the calling parameters and the target interface configuration information, the target interface corresponding to the target interface configuration information is called to obtain the calling result; and the calling result is returned to the interface caller. This application only needs to obtain the calling parameters and retrieval information provided by the interface caller, select the corresponding interface configuration information for the interface caller according to the retrieval information, and then call the target interface based on the calling parameters and the target interface configuration information and return the calling result to the interface caller. The interface caller does not need to perceive the calling process of different preset interfaces, so that it can make indiscriminate calls, reducing the difficulty of interface calling for the interface caller. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1 It is a scenario diagram of the interface calling system provided in an embodiment of the present application;

[0021] Figure 2 It is a flowchart of an embodiment of the interface calling method provided in the embodiment of the present application;

[0022] Figure 3 It is a schematic diagram of a process of acquiring target interface configuration information matching the search information from a preset configuration information library based on the search information in an embodiment of the interface calling method provided by the embodiment of the present application;

[0023] Figure 4 It is a schematic diagram of the relationship between the preset configuration information library, the configuration information set, the set attribute information and the interface configuration information in one embodiment of the interface calling method provided by the embodiment of the present application;

[0024] Figure 5 It is a flowchart of another embodiment of the interface calling method provided in the embodiment of the present application;

[0025] Figure 6 It is a structural diagram of an embodiment of an interface calling device provided in an embodiment of the present application;

[0026] Figure 7 It is a structural diagram of another embodiment of the interface calling device provided in the embodiment of the present application;

[0027] Figure 8 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] It should be noted that the principles of the present application are illustrated by implementing them in an appropriate computing environment. The following description is based on the illustrated specific embodiments of the present application and should not be considered as limiting other specific embodiments of the present application that are not described in detail herein.

[0029] In the following description of the present application, reference is made to “some embodiments”, which describe a set of all possible embodiments, but it can be understood that “some embodiments” may be the same set or different sets of all possible embodiments and may be combined with each other without conflict.

[0030] In the following description of the present application, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0031] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0032] In order to improve the effect of interface calling, the embodiment of the present application provides an interface calling method, an interface calling device, an electronic device, a computer readable storage medium and a computer program product. The interface calling method can be executed by the interface calling device, or by an electronic device integrated with the interface calling device.

[0033] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0034] Please refer to Figure 1 , this application also provides an interface calling system, such as Figure 1 As shown, the interface calling system includes an electronic device 100, and the interface calling device provided by the present application is integrated in the electronic device 100.

[0035] Among them, the electronic device 100 can be any device equipped with a processor and has processing capabilities, such as mobile electronic devices with processors such as smart phones, tablet computers, PDAs, laptops, smart speakers, or fixed electronic devices with processors such as desktop computers, televisions, servers, industrial equipment, etc.

[0036] In addition, if Figure 1 As shown, the interface calling system may further include a memory 200 for storing original data, intermediate data and result data.

[0037] In the embodiment of the present application, the memory 200 can be a cloud storage. Cloud storage is a new concept extended and developed from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as the storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of different types of storage devices (storage devices are also called storage nodes) in the network through application software or application interfaces to work together and provide external data storage and business access functions.

[0038] At present, the storage method of the storage system is: create a logical volume, and when creating a logical volume, allocate physical storage space for each logical volume. The physical storage space may be composed of disks of a storage device or several storage devices. The client stores data on a logical volume, that is, stores the data on the file system. The file system divides the data into many parts, each of which is an object. The object contains not only data but also additional information such as data identification (ID, ID entity). The file system writes each object into the physical storage space of the logical volume, and the file system records the storage location information of each object, so that when the client requests to access the data, the file system can allow the client to access the data according to the storage location information of each object.

[0039] The process of the storage system allocating physical storage space to a logical volume is as follows: based on the estimated capacity of the objects stored in the logical volume (this estimate often has a large margin relative to the actual capacity of the objects to be stored) and the grouping of independent redundant disk arrays (RAID, Redundant Array of Independent Disks), the physical storage space is pre-divided into stripes. A logical volume can be understood as a stripe, thereby allocating physical storage space to the logical volume.

[0040] It should be noted that Figure 1 The scenario diagram of the interface calling system shown is merely an example. The interface calling system and scenario described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the interface calling system and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is equally applicable to similar technical problems.

[0041] It should be noted that the serial numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0042] Please refer to Figure 2 , Figure 2 is a flow chart of an embodiment of the interface calling method provided in the embodiment of the present application, such as Figure 2 As shown, the process of the interface calling method provided by this application is as follows:

[0043] 201. Obtain the call parameters and retrieval information sent by the interface caller.

[0044] In the embodiment of the present application, the interface caller can be a cloud microservice, an application (Application, APP) of various systems, a quick application of various systems, a mini-program of various systems, etc., which is set according to the specific situation and is not limited in this application.

[0045] Generally speaking, programming language communication at the method level uses a network interface format, exposing only parameters and results for others to call. Interfaces are generally divided into interface providers and interface callers. Interface providers can specify the type of received parameters and the return form, while interface callers can only access them in full accordance with the parameters specified by the interface provider. In the embodiments of the present application, each preset interface is provided by each interface provider.

[0046] The calling parameters are provided by the interface caller and used as the input parameters of the preset interface. The preset interface returns the output parameters corresponding to the input parameters. For example, the calling parameters are used to call the interface of a navigation application. The calling parameters may include the primary key, variable type, destination, and departure point. The primary key is represented by key, the variable type is represented by type, the destination is represented by description, and the departure point is represented by name. For example, the calling parameters are in the following format:

[0047]

[0048]

[0049] The meaning of the above fields is an optional form of protocol agreement. In other protocols, other characters, graphics and other elements may be used to express the same meaning as the examples provided in the embodiments of the present application. For example, expressing the various fields or character information of the present application in other expressions such as German and French is also within the scope of protection of the present application.

[0050] The retrieval information includes at least one interface attribute and / or at least one set attribute, and a set contains at least one interface. The interface attribute is used to retrieve the interface, and the set attribute is used to retrieve the set. The at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface retrieval keyword information, and an interface description information.

[0051] In a specific embodiment, the retrieval information includes at least one interface attribute, and the at least one interface attribute includes an interface identifier, an interface primary key, an interface name, interface retrieval keyword information, and interface description information.

[0052] The interface identifier may be an interface ID (Identity document), where ID is an abbreviation of various proprietary terms such as identity card identification number, account number, unique code, exclusive number, industrial design, country abbreviation, legal term, universal account, decoder, software company, etc.

[0053] In a specific embodiment, the interface identifier is 1000, the interface primary key is com.oplus.service.std.xxx, the interface name is "Start Navigation", the interface search keyword information includes: "Navigation", "Path Finding", etc., and the interface description information is: calling this service will start the navigation function. Of course, in other embodiments, the search information may also include other attributes such as interface version information, which is not limited in this application.

[0054] 202. Acquire target interface configuration information matching the search information from a preset configuration information library based on the search information.

[0055] The preset configuration information library includes interface configuration information corresponding to at least two preset interfaces. The interface configuration information corresponding to at least two preset interfaces can be pre-configured and stored. Different preset interfaces can implement different functions.

[0056] Among them, each different preset interface is an interface exposed by each interface provider, and each interface provider can be a cloud microservice, applications of various systems, Software as a Service (SAAS), quick applications of various systems, applets of various systems, and the like.

[0057] Among them, the interface configuration information includes at least one interface attribute. The at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface search keyword information, and an interface description information. The interface identifier, the interface primary key, the interface name, the interface search keyword information, and the interface description information are mainly used to search for interfaces. When an interface caller needs to call an interface, the interface can be found in a variety of ways. For example, by searching for the interface identifier, the interface primary key, the interface name, the interface search keyword information, and the interface description information in the information. If the interface caller only knows some vague information, for example, the interface caller can only provide interface search keyword information or interface description information, it can also be searched by indexing keywords or performing semantic analysis based on the interface description information.

[0058] In a specific embodiment, the interface configuration information of the preset interface is obtained, and each interface attribute in the interface configuration information of the preset interface is compared with each interface attribute in the retrieval information. If the interface configuration information of the preset interface includes each interface attribute in the retrieval information, the interface configuration information of the preset interface is determined to be the target interface configuration information that matches the retrieval information.

[0059] Furthermore, if the interface configuration information of each interface configuration information in the preset configuration information library does not contain the interface configuration information containing each interface attribute in the search information, the interface description information in the interface configuration information of the preset interface is obtained, and the interface description information in the interface configuration information is input into the pre-trained preset neural network model to obtain the prediction identifier of the interface configuration information predicted by the preset neural network model. The prediction identifier based on the interface configuration information is matched with the interface identifier in the search information, and the interface configuration information with the same prediction identifier as the interface identifier in the search information is determined as the target interface configuration information.

[0060] Among them, the preset neural network model can be a Transformer model, a BERT (Bidirectional Encoder Representations from Transformers) model, etc. The preset neural network model can be pre-trained using a preset training set, and the preset training set includes multiple interface configuration information and corresponding annotated interface identifiers. For example, the preset training set includes interface configuration information A and interface configuration information B, and the preset training set includes the annotated interface identifier corresponding to interface configuration information A as 2001, and the annotated interface identifier corresponding to interface configuration information B as 2002, which can be pre-annotated manually.

[0061] 203. Call the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result.

[0062] In a specific embodiment, the calling parameters are used as input parameters of the target interface corresponding to the target interface configuration information, and the output parameters of the target interface based on the input parameters are obtained, and the output parameters of the target interface based on the input parameters are determined as the calling result.

[0063] Compared with the prior art, the present application only needs to obtain the calling parameters and retrieval information provided by the interface caller, select the corresponding interface configuration information for the interface caller based on the retrieval information, and then call the target interface based on the calling parameters and the target interface configuration information and return the calling result to the interface caller. The interface caller does not need to perceive the calling process of different preset interfaces, so that indiscriminate calls can be made, reducing the difficulty of interface calling for the interface caller.

[0064] In another specific embodiment, the interface configuration information includes a calling protocol of a preset interface. The target interface configuration information includes a target calling protocol of the target interface, and the target calling protocol of the target interface is provided by the interface provider of the target interface. For example, if the target calling protocol of the target interface is ANDROID_MESSENGER, then the Android Messenger method will be used for calling; when the target calling protocol of the target interface is the Hypertext Transfer Protocol (HTTP), then the HTTP Restful API method will be used. HTTP is a simple request-response protocol that usually runs on top of the Transmission Control Protocol (TCP). It specifies what kind of messages the client may send to the server and what kind of responses it may get.

[0065] Correspondingly, based on the calling parameters and the target interface configuration information, the target interface corresponding to the target interface configuration information is called to obtain a calling result, including:

[0066] (1) Encapsulate the call parameters based on the target call protocol to obtain the encapsulated call parameters.

[0067] Specifically, if the target calling protocol is ANDROID_MESSENGER, the IBinder of the interface provider is obtained through bindService(), and the calling parameters are encapsulated in the Messenger. When the target calling protocol is HTTP, the calling parameters are encapsulated in the HTTP body.

[0068] (2) The encapsulated call parameters are passed into the target interface as input parameters to obtain the call result returned by the target interface.

[0069] When calling an interface, this application uses the calling protocol defined by the interface provider to encapsulate the calling parameters and then complete the call. The interface caller does not need to perceive the difference in the interface protocol to complete the call. The interface can be called indiscriminately, reducing the difficulty of calling for the interface caller.

[0070] In another specific embodiment, the target interface configuration information includes the interface provider type of the target interface. An interface provider may have multiple deployment methods. For example, some interface providers are pre-installed on the device and may be resident and alive, such as some system services and Software as a Service (SAAS) of Android. Some interface providers are pre-installed, but not resident, and require a framework to pull up, such as the AIUnit (Artificial Intelligence Unit) service. The AIUnit service provides capability building in four major directions: visual algorithms, video algorithms, audio algorithms, and perception algorithms. It can provide artificial intelligence algorithm interfaces to application developers, allowing application developers to efficiently write AI (Artificial Intelligence) applications for running on mobile devices. Some interface providers need to be dynamically loaded and run. For example, the interface provider is a UPK (ubiquitous package), and the deployment method of the interface provider is determined to be APK (Android application package) dynamic loading.

[0071] Correspondingly, based on the calling parameters and the target interface configuration information, the target interface corresponding to the target interface configuration information is called to obtain a calling result, including:

[0072] (1) Determine the deployment mode of the interface provider based on the interface provider type of the target interface.

[0073] Specifically, if the interface provider is SAAS, since SAAS is always kept alive, go directly to the next step. If the interface provider is UPK, determine that the deployment mode of the interface provider is APK dynamic loading. If the interface provider is AiUnit, the deployment mode of the interface provider is active loading and running.

[0074] (2) Deploy the interface provider based on the interface provider's deployment method.

[0075] Specifically, if the interface provider is SAAS, since SAAS is always kept alive, proceed directly to the next step. If the interface provider is UPK, determine that the deployment mode of the interface provider is APK dynamic loading, then dynamically load, install and run the interface provider. If the interface provider is AiUnit, actively trigger the corresponding AI module to load, install and run.

[0076] (3) Call the target interface based on the calling parameters and obtain the calling result.

[0077] This application determines the deployment method according to the interface provider type and deploys the interface provider. It can support various types of interface provider types. The interface caller does not need to be aware of the interface provider type to complete the call, which can reduce the difficulty of the interface caller.

[0078] Since the present application selects a matching target interface for the interface caller and chooses an appropriate method to deploy or run the provider according to the interface provider type of the target interface, the interface caller does not need to worry about the deployment method and status of the interface provider. It can support various types of interface provider types. The interface caller does not need to perceive the interface provider type and can call the interface indiscriminately, which can reduce the difficulty of calling for the interface caller.

[0079] In another specific embodiment, the target interface configuration information includes a target parameter verification condition corresponding to the target interface. The target interface corresponding to the target interface configuration information is called based on the calling parameters and the target interface configuration information to obtain a calling result, including: checking whether the calling parameters meet the target parameter verification standard; when the calling parameters meet the target parameter verification condition, the target interface corresponding to the target interface configuration information is called based on the calling parameters and the target interface configuration information to obtain a calling result. Among them, the target parameter verification condition includes a parameter name verification condition, a parameter type verification condition, and a parameter value constraint range. For example, the parameter name verification condition is: the parameter name needs to include the departure parameter and the destination parameter; the parameter type verification condition is: the parameter type is a string; the parameter value constraint range is: the parameter value of each parameter is within the constraint range. The target parameter verification condition can be set according to the specific situation, and this application does not limit this. Verify the parameters according to the target parameter verification condition to avoid parameter errors.

[0080] 204. Return the call result to the interface caller.

[0081] Furthermore, since the interface caller may just want to call a standard function but does not care about the specific implementation of the function, in order to enable the interface caller to complete the call by only providing the information of a standard function, refer to Figure 3 , Figure 3 The present invention is a flowchart of obtaining target interface configuration information matching the search information from a preset configuration information library based on the search information in an embodiment of the interface call method provided by the embodiment of the present application. In a specific embodiment, the target interface corresponding to the target interface configuration information is called based on the call parameters and the target interface configuration information to obtain the call result, including:

[0082] S301: Match the search information with the set attribute information of each configuration information set and each interface configuration information respectively to obtain a matching result matching the search information.

[0083] The preset configuration information base includes at least one configuration information set and set attribute information of each configuration information set, and the configuration information set includes at least one interface configuration information. Different preset interfaces corresponding to different interface configuration information in the same configuration information set can realize the same standard capability, and different preset interfaces corresponding to different interface configuration information in the same configuration information set have different implementation methods on the basis of realizing the same standard capability.

[0084] like Figure 4 As shown, the preset configuration information library includes two configuration information sets, namely, configuration information set C and configuration information set D. Among them, the collection attribute information of configuration information set C is C0, and configuration information set C includes 2 interface configuration information, namely, interface configuration information C1 and interface configuration information C2. Among them, the collection attribute information of configuration information set D is D0, and configuration information set D includes 2 interface configuration information, namely, interface configuration information D1 and interface configuration information D2. Among them, the collection attribute information C0 and the interface configuration information C1 can be converted to each other according to the parameter conversion relationship between the collection attribute information C0 and the interface configuration information C1; the collection attribute information C0 and the interface configuration information C1 can be converted to each other according to the parameter conversion relationship between the collection attribute information C0 and the interface configuration information C1.

[0085] The preset interface corresponding to the interface configuration information C1 is the interface provided by the navigation application C1, and the preset interface corresponding to the interface configuration information C2 is the interface provided by the navigation application C2. For example, both the navigation application C1 and the navigation application C2 can implement the standard function of the navigation function, but the implementation methods of the navigation application C1 and the navigation application C2 are different. The above only takes the example that the preset configuration information library includes two configuration information sets, and the configuration information set includes 2 interface configuration information. In other embodiments, the preset configuration information library includes a larger number of configuration information sets, and the configuration information set includes a larger number of interface configuration information. This application does not limit this.

[0086] The matching result may be set attribute information, interface configuration information, or empty. If the matching result is empty, it means that the configuration information set cannot be obtained from it, and the call failure is returned.

[0087] The retrieval information includes at least one interface attribute and / or at least one collection attribute, the collection attribute information includes at least one collection attribute, and the interface configuration information includes at least one interface attribute. The at least one collection attribute includes at least one of a collection identifier, a collection primary key, a collection name, collection retrieval keyword information, and collection description information. The at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface retrieval keyword information, and an interface description information.

[0088] In a specific implementation, each set of attribute information and each interface configuration information is respectively determined as information to be matched, and each attribute in the information to be matched is compared with each interface attribute in the search information. If the information to be matched contains each interface attribute in the search information, the information to be matched is determined as the matching result of the search information.

[0089] S302: When the matching result is set attribute information, determine the interface configuration information that meets the preset configuration condition in the configuration information set corresponding to the matching result as the target interface configuration information that matches the search information.

[0090] In an embodiment of the present application, when the matching result is set attribute information, it indicates that the interface caller does not have a specific desired interface, and an interface configuration information can be selected from the configuration information set corresponding to the matching result as the target interface configuration information that matches the search information.

[0091] In a specific embodiment, a piece of interface configuration information randomly selected from the configuration information set is determined as the interface configuration information that meets the preset configuration condition.

[0092] In another specific embodiment, the interface configuration information with the highest historical call count in the configuration information set is determined as the interface configuration information that meets the preset configuration condition. When the interface caller calls each preset interface, the call count of each preset interface by the interface caller is recorded to obtain the historical call count.

[0093] Further, in the case where the matching result is interface configuration information, the matching result is determined as target interface configuration information matching the search information.

[0094] Since this application only requires the interface caller to provide collection attribute information, it can retrieve the configuration information set corresponding to the collection attribute information, and then use an interface configuration information of the configuration information set to call the interface and return it to the interface caller, it can reduce the interface callers and reduce the difficulty of calling the interface.

[0095] See also Figure 5 , Figure 5 : is a flow chart of another embodiment of the interface calling method provided in the embodiment of the present application. In the embodiment of the present application, the interface calling method may include:

[0096] 401. Get the call parameters and retrieval information sent by the interface caller.

[0097] The calling parameters are provided by the interface caller and used as the input parameters of the preset interface. The preset interface returns the output parameters corresponding to the input parameters. For example, the calling parameters are used to call the interface of a navigation application. The calling parameters may include the primary key, variable type, destination, and departure point. The primary key is represented by key, the variable type is represented by type, the destination is represented by description, and the departure point is represented by name. For example, the calling parameters are in the following format:

[0098]

[0099] The meaning of the above fields is an optional form of protocol agreement. In other protocols, other characters, graphics and other elements may be used to express the same meaning as the examples provided in the embodiments of the present application. For example, expressing the various fields or character information of the present application in other expressions such as German and French is also within the scope of protection of the present application.

[0100] The retrieval information includes at least one interface attribute or at least one collection attribute. The interface attribute is used to retrieve the interface, and the collection attribute is used to retrieve the collection. A collection corresponds to at least one interface. At least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface retrieval keyword information, and an interface description information. At least one collection attribute includes at least one of a collection identifier, a collection primary key, a collection name, a collection retrieval keyword information, and a collection description information.

[0101] In a specific embodiment, the interface identifier is 1000, the interface primary key is com.oplus.service.std.xxx, the interface name is "Start Navigation", the interface search keyword information includes: "Navigation", "Path Finding", etc., and the interface description information is: calling this service will start the navigation function. Of course, in other embodiments, the search information may also include other attributes such as interface version information, which is not limited in this application.

[0102] 402. Match the search information with the set attribute information of each configuration information set and each interface configuration information respectively to obtain a matching result matching the search information.

[0103] The preset configuration information base includes at least one configuration information set and set attribute information of each configuration information set, and the configuration information set includes at least one interface configuration information. Different preset interfaces corresponding to different interface configuration information in the same configuration information set can realize the same standard capability, and different preset interfaces corresponding to different interface configuration information in the same configuration information set have different implementation methods on the basis of realizing the same standard capability.

[0104] For example, the preset configuration information includes two configuration information sets, namely, configuration information set C and configuration information set D, wherein configuration information set C includes two interface configuration information, namely, interface configuration information C1 and interface configuration information C2, the preset interface corresponding to interface configuration information C1 is the interface provided by navigation application C1, and the preset interface corresponding to interface configuration information C2 is the interface provided by navigation application C2. Among them, navigation application C1 and navigation application C2 can both implement the standard function of navigation function, but the implementation methods of navigation application C1 and navigation application C2 are different.

[0105] The configuration information set includes at least one set attribute, and the at least one set attribute includes at least one of a set identifier, a set primary key, a set name, set search keyword information, and a set description information. For example, the set identifier is represented by "id", the set primary key is represented by "key", the set name is represented by "name", and the set description information is represented by "description". Furthermore, the configuration information set also includes set input parameters and set output parameters, wherein the set input parameters are represented by "inputParams" and the set output parameters are represented by "outputParams".

[0106] Specifically, the set attribute information of the configuration information set is in the following format:

[0107]

[0108]

[0109] The meaning of the above fields is an optional form of protocol agreement. In other protocols, other characters, graphics and other elements may be used to express the same meaning as the examples provided in the embodiments of the present application. For example, expressing the various fields or character information of the present application in other expressions such as German and French is also within the scope of protection of the present application.

[0110] The configuration information set includes at least one interface attribute, and the at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, interface search keyword information, and an interface description information. For example, the interface identifier is represented by "id", the interface primary key is represented by "key", the interface name is represented by "name", and the interface description information is represented by "description".

[0111] Furthermore, the configuration information interface also includes interface input parameters, interface output parameters, parameter verification standards, parameter conversion relationships, interface provider types, and calling protocols, where interface input parameters are represented by "inputParams", interface output parameters are represented by "outputParams", parameter conversion relationships are represented by "paramConvertRules", interface provider types are represented by "providerType", and calling protocols are represented by "apiType".

[0112] Specifically, the set attribute information of the configuration information set is in the following format:

[0113]

[0114]

[0115]

[0116] The meaning of the above fields is an optional form of protocol agreement. In other protocols, other characters, graphics and other elements may be used to express the same meaning as the examples provided in the embodiments of the present application. For example, expressing the various fields or character information of the present application in other expressions such as German and French is also within the scope of protection of the present application.

[0117] The matching result may be collection attribute information, interface configuration information, or empty. If the matching result is empty, it means that the configuration information cannot be obtained from it, and the call fails.

[0118] In a specific implementation, each set of attribute information and each interface configuration information is respectively determined as information to be matched, and each attribute in the information to be matched is compared with each interface attribute in the search information. If the information to be matched contains all the same attributes in the search information, the information to be matched is determined as the matching result of the search information.

[0119] Furthermore, if the interface configuration information containing the attributes in the search information does not exist in the various set attribute information and the various interface configuration information of the preset configuration information library, the set description information in each set attribute information and the interface description information in each interface configuration information are respectively determined as the information to be predicted, and the information to be predicted is input into the pre-trained preset neural network model to obtain the prediction identifier of the information to be predicted predicted by the preset neural network model. The prediction identifier of the information to be predicted is matched with the interface identifier or set identifier in the search information, and the information to be predicted with the same prediction identifier as the interface identifier or set identifier in the search information is determined as the matching result.

[0120] 403. When the matching result is set attribute information, the interface configuration information that meets the preset configuration condition in the configuration information set corresponding to the matching result is determined as the target interface configuration information that matches the search information.

[0121] In the embodiment of the present application, when the matching result is set attribute information, it means that there are multiple interface configuration information to choose from in the configuration information set corresponding to the set attribute information, and the interface caller does not have a specific interface he wants, and what is found is a "standard capability". Then it is necessary to use the "standard capability" to search for the corresponding interface again from the preset configuration information library. If there are multiple interfaces, it is necessary to select a suitable interface through a strategy.

[0122] In a specific embodiment, a piece of interface configuration information randomly selected from the configuration information set is determined as the interface configuration information that meets the preset configuration condition.

[0123] In another specific embodiment, the interface configuration information with the highest historical call count in the configuration information set is determined as the interface configuration information that meets the preset configuration condition. When the interface caller calls each preset interface, the call count of each preset interface by the interface caller is recorded to obtain the historical call count.

[0124] 404. When the matching result is interface configuration information, determine the matching result as target interface configuration information matching the search information.

[0125] 405. If the matching result is empty, the call fails.

[0126] 406. Verify whether the calling parameters meet the target parameter verification standard.

[0127] Among them, the target parameter verification conditions include parameter name verification conditions, parameter type verification conditions, and parameter value constraint range. For example, the parameter name verification condition is: the parameter name needs to contain the departure parameter and the destination parameter; the parameter type verification condition is: the parameter type is a string; the parameter value constraint range is: the parameter value of each parameter is within the constraint range. The target parameter verification conditions can be set according to the specific situation, and this application does not limit this.

[0128] It should be noted that, when the matching result is interface configuration information or when the matching result is set attribute information, 406 is executed. Since parameter conversion does not need to be executed when the matching result is interface configuration information, subsequent 407 and 412 may not be executed when the matching result is interface configuration information.

[0129] 407. Perform parameter conversion on the calling parameter based on the target parameter conversion relationship to obtain the calling parameter after parameter conversion.

[0130] The target parameter conversion relationship is preset. When the verification call parameter meets the target parameter verification standard, the call parameter is converted based on the target parameter conversion relationship to obtain the converted call parameter.

[0131] In a specific embodiment, one-to-one mapping is performed according to the same parameter name.

[0132] In another specific embodiment, the relationship between the parameter name in the set attribute information and the parameter name in the interface configuration information is specified, and a one-to-one mapping is performed. For example, if the parameter name in the set attribute information is "to" and the corresponding parameter name in the interface configuration information is "destination", then the "to" in the call parameter is converted to "destination" to obtain the call parameter after the parameter conversion.

[0133] For example, the format of the target parameter conversion relation is as follows,

[0134] {

[0135] "paramName":"to",

[0136] "standardParamName":"destination"

[0137] }

[0138] In another specific embodiment, complex parameter conversion relationships are customized through scripts, and the script field needs to be configured. Script is a script string, and its grammar rules can adopt mature scripting languages, such as Python or custom grammar. For example, if the parameter name in the collection attribute information is "xxx", and the parameter name in the corresponding interface configuration information is "xxx+1", then the "xxx" in the call parameter is converted to "xxx+1" to obtain the call parameter after parameter conversion.

[0139] For example, the format of the target parameter conversion relation is as follows,

[0140] {

[0141] "script":"$xxx+1"

[0142] }

[0143] 408. Determine a deployment mode of the interface provider based on the interface provider type of the target interface.

[0144] Specifically, if the interface provider is SAAS, since SAAS is always kept alive, you do not need to do anything and go directly to the next step. If the interface provider is UPK, determine that the deployment mode of the interface provider is APK dynamic loading. If the interface provider is AiUnit, the deployment mode of the interface provider is active loading and running.

[0145] 409. Deploy the interface provider based on the deployment method of the interface provider.

[0146] Specifically, if the interface provider is SAAS, since SAAS is always kept alive, nothing needs to be done, and you can proceed directly to the next step. If the interface provider is UPK, determine that the deployment mode of the interface provider is APK dynamic loading, then dynamically load, install and run the interface provider. If the interface provider is AiUnit, actively trigger the corresponding AI module to load, install and run.

[0147] 410. Encapsulate the calling parameters based on the target calling protocol to obtain the encapsulated calling parameters.

[0148] Specifically, if the target calling protocol is ANDROID_MESSENGER, the IBinder of the interface provider is obtained through bindService(), and the calling parameters are encapsulated in the Messenger. When the target calling protocol is HTTP, the calling parameters are encapsulated in the HTTP body.

[0149] 411. Pass the encapsulated call parameters as input parameters to the target interface, and obtain the output parameters returned by the target interface.

[0150] 412. Perform parameter conversion on the output parameter returned by the target interface based on the target parameter conversion relationship to obtain a call result.

[0151] Before the call, the call parameters are converted based on the target parameter conversion relationship to obtain the converted call parameters. Therefore, it is necessary to convert the output parameters returned by the target interface so that the parameters returned to the interface caller are consistent with the type of the call parameters sent by the interface caller, so that the interface caller does not need to perceive the difference in the calling process and implements indiscriminate calling.

[0152] 413. Return the call result to the interface caller.

[0153] In order to better implement the interface calling method provided in the embodiment of the present application, the embodiment of the present application also provides an interface calling device based on the above interface calling method. The meanings of the terms are the same as those in the above interface calling method. For specific implementation details, please refer to the description in the above method embodiment.

[0154] Please refer to Figure 6 , Figure 6 A schematic diagram of the structure of an embodiment of an interface calling device provided in an embodiment of the present application, wherein the interface calling device may include a first acquisition module 601, a second acquisition module 602, a calling module 603 and a return module 604, wherein:

[0155] The first acquisition module 601 is used to acquire the call parameters and search information sent by the interface caller;

[0156] A second acquisition module 602 is used to acquire target interface configuration information matching the search information from a preset configuration information library based on the search information, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces;

[0157] A calling module 603, configured to call a target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information, and obtain a calling result;

[0158] The return module 604 is used to return the call result to the interface caller.

[0159] The specific implementation of each of the above modules can be found in the previous embodiments and will not be described in detail here.

[0160] Please refer to Figure 7 , Figure 7 A schematic diagram of the structure of another embodiment of the interface calling device provided in the embodiment of the present application, the interface calling device may include a first acquisition module 701, a second acquisition module 702, a calling module 703 and a return module 704, wherein:

[0161] The first acquisition module 701 is used to acquire the call parameters and search information sent by the interface caller;

[0162] A second acquisition module 702, configured to acquire target interface configuration information matching the search information from a preset configuration information library based on the search information, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces;

[0163] A calling module 703, configured to call a target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information, and obtain a calling result;

[0164] The return module 704 is used to return the call result to the interface caller.

[0165] In an optional implementation, the preset configuration information library includes at least one configuration information set and set attribute information of each configuration information set, the configuration information set includes at least one interface configuration information, the second acquisition module 702 includes a search module 7021 and a determination module 7022,

[0166] The search module 7021 is used to match the search information with the set attribute information of each configuration information set and each interface configuration information, and obtain a matching result that matches the search information, and the matching result is the set attribute information or the interface configuration information;

[0167] The determination module 7022 is used to determine the interface configuration information that meets the preset configuration condition in the configuration information set corresponding to the matching result as the target interface configuration information that matches the search information when the matching result is set attribute information.

[0168] In an optional implementation, the retrieval information includes at least one interface attribute and / or at least one collection attribute, the collection attribute information includes at least one collection attribute, and the interface configuration information includes at least one interface attribute.

[0169] In an optional implementation, at least one collection attribute includes at least one of a collection identifier, a collection primary key, a collection name, collection retrieval keyword information, and collection description information; at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface retrieval keyword information, and an interface description information.

[0170] In an optional implementation, the target interface configuration information includes a target parameter conversion relationship corresponding to the target interface, and the calling module 703 includes a parameter conversion module 7032, and the parameter conversion module 7032 is used to:

[0171] When the matching result is set attribute information, the calling parameters are converted based on the target parameter conversion relationship to obtain the converted calling parameters;

[0172] The target interface corresponding to the target interface configuration information is called based on the calling parameters after parameter conversion to obtain a calling result.

[0173] In an optional implementation, the target interface configuration information includes a target parameter verification condition corresponding to the target interface, and the calling module 703 includes a parameter verification module 7031, and the parameter verification module 7031 is used to:

[0174] Verify whether the calling parameters meet the target parameter verification standards;

[0175] When the calling parameters meet the target parameter verification condition, the target interface corresponding to the target interface configuration information is called based on the calling parameters and the target interface configuration information to obtain a calling result.

[0176] In an optional implementation, the target interface configuration information includes a target calling protocol of the target interface, and the calling module 703 includes a calling protocol adaptation module 7034, and the calling protocol adaptation module 7034 is used to:

[0177] Encapsulate the calling parameters based on the target calling protocol to obtain the encapsulated calling parameters;

[0178] The encapsulated call parameters are passed into the target interface as input parameters to obtain the call result returned by the target interface.

[0179] In an optional implementation, the target interface configuration information includes the interface provider type of the target interface, and the calling module 703 includes a provider deployment module 7033, and the provider deployment module 7033 is used to:

[0180] Determine the deployment mode of the interface provider based on the interface provider type of the target interface;

[0181] Deploy the interface provider based on the interface provider's deployment method;

[0182] Call the target interface based on the calling parameters and get the calling result.

[0183] The specific implementation of each of the above modules can be found in the previous embodiments and will not be described in detail here.

[0184] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein the processor is used to execute the steps in the interface calling method provided in this embodiment by calling a computer program stored in the memory.

[0185] Please refer to Figure 8 , Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0186] The electronic device may include components such as a processor 101 with one or more processing cores, a memory 102 with one or more computer-readable storage media, a power supply 103, and an input unit 104. Those skilled in the art will appreciate that the electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0187] The processor 101 is the control center of the electronic device, which uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 102, and calling data stored in the memory 102. Optionally, the processor 101 may include one or more processing cores; optionally, the processor 101 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 101.

[0188] The memory 102 can be used to store software programs and modules. The processor 101 executes various functional applications and data processing by running the software programs and modules stored in the memory 102. The memory 102 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 102 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 102 may also include a memory controller to provide the processor 101 with access to the memory 102.

[0189] The electronic device also includes a power supply 103 for supplying power to each component. Optionally, the power supply 103 can be logically connected to the processor 101 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 103 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0190] The electronic device may further include an input unit 104, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0191] Although not shown, the electronic device may also include a display unit, an image acquisition component, etc., which will not be described in detail here. Specifically in this embodiment, the processor 101 in the electronic device will load the executable code corresponding to one or more computer programs into the memory 102 according to the following instructions, and the processor 101 will execute the steps in the interface calling method provided in this application, such as:

[0192] Get the call parameters and retrieval information sent by the interface caller;

[0193] Based on the search information, acquiring target interface configuration information matching the search information from a preset configuration information library, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces;

[0194] Call the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result;

[0195] Return the call result to the interface caller.

[0196] It should be noted that the electronic device provided in the embodiment of the present application and the interface calling method in the above embodiment belong to the same concept, and its specific implementation process is detailed in the above related embodiments and will not be repeated here.

[0197] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program stored therein is executed on a processor of an electronic device provided in an embodiment of the present application, the processor of the electronic device executes the steps in the interface calling method provided in the present application. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0198] The present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes various optional implementations of the above-mentioned interface calling method.

[0199] The above is a detailed introduction to an interface calling method and device provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

[0200] It should be noted that when the above embodiments of the present application are applied to specific products or technologies, the relevant data of the user is involved, and the user's permission or consent is required, and the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

Claims

1. An interface calling method, characterized in that: include: Get the call parameters and retrieval information sent by the interface caller; Based on the search information, acquiring target interface configuration information matching the search information from a preset configuration information library, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces; Calling the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result; The calling result is returned to the interface caller.

2. The interface calling method according to claim 1, characterized in that: The preset configuration information base includes at least one configuration information set and set attribute information of each of the configuration information sets, the configuration information set includes at least one of the interface configuration information, and acquiring the target interface configuration information matching the search information from the preset configuration information base based on the search information includes: Matching the search information with the set attribute information of each of the configuration information sets and each of the interface configuration information respectively, to obtain a matching result matching the search information, the matching result being the set attribute information or the interface configuration information; In the case that the matching result is the set attribute information, the interface configuration information that meets the preset configuration condition in the configuration information set corresponding to the matching result is determined as the target interface configuration information that matches the search information.

3. The interface calling method according to claim 2, characterized in that: The retrieval information includes at least one interface attribute and / or at least one set attribute, the set attribute information includes at least one set attribute, and the interface configuration information includes at least one interface attribute.

4. The interface calling method according to claim 3, characterized in that: The at least one collection attribute includes at least one of a collection identifier, a collection primary key, a collection name, collection search keyword information, and collection description information; the at least one interface attribute includes at least one of an interface identifier, an interface primary key, an interface name, an interface search keyword information, and an interface description information.

5. The interface calling method according to claim 2, characterized in that: The target interface configuration information includes a target parameter conversion relationship corresponding to the target interface, and the calling of the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result includes: In the case where the matching result is the set attribute information, performing parameter conversion on the call parameter based on the target parameter conversion relationship to obtain the call parameter after parameter conversion; The target interface corresponding to the target interface configuration information is called based on the calling parameters after parameter conversion to obtain a calling result.

6. The interface calling method according to claim 1, characterized in that: The target interface configuration information includes a target parameter verification condition corresponding to the target interface, and the calling of the target interface corresponding to the target interface configuration information based on the calling parameter and the target interface configuration information to obtain a calling result includes: Verifying whether the calling parameters meet the target parameter verification standard; In the case where the calling parameters meet the target parameter verification condition, the target interface corresponding to the target interface configuration information is called based on the calling parameters and the target interface configuration information to obtain a calling result.

7. The interface calling method according to claim 1, characterized in that: The target interface configuration information includes a target calling protocol of the target interface, and calling the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result includes: Encapsulate the calling parameters based on the target calling protocol to obtain the encapsulated calling parameters; The encapsulated calling parameters are passed into the target interface as input parameters to obtain the calling result returned by the target interface.

8. The interface calling method according to claim 1, characterized in that: The target interface configuration information includes an interface provider type of the target interface, and the calling of the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information to obtain a calling result includes: Determining a deployment mode of the interface provider based on the interface provider type of the target interface; Deploy the interface provider based on the deployment mode of the interface provider; The target interface is called based on the calling parameters to obtain a calling result.

9. An interface calling device, characterized in that: include: The first acquisition module is used to acquire the call parameters and retrieval information sent by the interface caller; A second acquisition module, configured to acquire target interface configuration information matching the search information from a preset configuration information library based on the search information, wherein the preset configuration information library includes interface configuration information corresponding to at least two preset interfaces; A calling module, used for calling the target interface corresponding to the target interface configuration information based on the calling parameters and the target interface configuration information, to obtain a calling result; The return module is used to return the call result to the interface caller.

10. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and the processor is used to run the computer program in the memory to execute the steps in the interface calling method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the interface calling method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps in the interface calling method described in any one of claims 1 to 8 are implemented.

Images