Interface query method and device, equipment and medium
By utilizing entity recognition technology in the interface management platform, the problems of difficult and slow matching of interface fields and data type parsing in API shared services have been solved, enabling efficient API interface querying and usage.
Patent Information
- Application Number
- CN202411018193.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-26
- Publication Date
- 2024-11-08
AI Technical Summary
In large-scale API sharing services, developers struggle to quickly match query interface fields, data type parsing is difficult, data content querying consumes a lot of work, and API changes and migration issues occur frequently.
By storing the mapping relationship between interfaces and parameters through the interface management platform, and using entity recognition technology to determine the entity type of keywords, it is possible to quickly search for API interfaces by using parameter values as keywords.
It reduces the workload for users when searching for and using APIs, improves the efficiency of API interface usage, and ensures the accuracy of data type parsing and rapid API interface matching.
Smart Images

Figure CN118921396A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of big data technology, and in particular to an interface query method, device, equipment and medium. Background Art
[0002] In modern software development, API (application programming interface) plays a key role, enabling different software systems to communicate and interact with each other. With the rapid development of cloud computing, mobile applications and the Internet of Things, the importance of API sharing services has become increasingly prominent. API sharing services can be public API markets or internal API libraries of enterprises, providing developers with rich functions and resources, accelerating the software development and integration process.
[0003] For large-scale API sharing services, it is becoming increasingly challenging to effectively manage and utilize these APIs. In particular, when developers use these APIs, they often need to understand the meaning and type of interface fields in order to correctly use and parse data. However, due to the complexity and diversity of APIs and the lack of standardized interface field naming specifications, developers often face the problem of difficulty in quickly matching interface fields for queries. Summary of the invention
[0004] In view of this, this specification provides the following methods, devices, equipment and media.
[0005] In a first aspect of the present application, an interface query method is provided, which is applied to an interface management platform, wherein the interface management platform stores a mapping relationship between interfaces and parameters; the method comprises:
[0006] Get the keywords used to query the interface;
[0007] Performing entity recognition on the keyword to determine the entity type of the keyword;
[0008] A search is performed in the parameters in the interface management platform, a parameter of an entity type whose entity type is the keyword is determined as a target parameter, an interface corresponding to the target parameter is determined as a target interface, and the target interface is returned.
[0009] In a second aspect of the present application, an interface query device is provided, which is applied to an interface management platform, wherein the interface management platform stores a mapping relationship between interfaces and parameters; the device comprises:
[0010] An acquisition unit, used to acquire keywords for querying the interface;
[0011] An identification unit, used to perform entity identification on the keyword to determine the entity type of the keyword;
[0012] The search unit is used to search in the parameters in the interface management platform, determine the parameter of the entity type whose entity type is the keyword as the target parameter, determine the interface corresponding to the target parameter as the target interface, and return the target interface.
[0013] In a third aspect of the present application, an electronic device is provided, comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are interconnected via the bus;
[0014] The memory stores machine-readable instructions, and the processor executes the above method by calling the machine-readable instructions.
[0015] In a fourth aspect of the present application, a machine-readable storage medium is provided, wherein the machine-readable storage medium stores machine-readable instructions, and when the machine-readable instructions are called and executed by a processor, the above method is implemented.
[0016] The above embodiments of this specification have at least the following beneficial effects:
[0017] The above technical solution associates and saves the API interface with the parameters it contains and the entity type corresponding to the parameters; thus, when it is necessary to search for the API interface, the entity type corresponding to the keyword can be identified by performing entity recognition on the input keyword; and then the parameter corresponding to the entity type can be used as the target parameter, and the API interface containing the target parameter can be used as the target API interface. Therefore, the technical solution realizes the search for the API interface by using a value of a parameter of the target API interface as a keyword, which reduces the workload of users when searching and using the API and improves the efficiency of using the API interface. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 is a flow chart of an interface query method shown in an exemplary embodiment;
[0019] Figure 2 is a schematic diagram of an interface parameter shown in an illustrative embodiment;
[0020] Figure 3 is a schematic diagram of an interface query method shown in an illustrative embodiment;
[0021] Figure 4 is a schematic diagram of an interface parameter management shown in an illustrative embodiment;
[0022] Figure 5 is a schematic diagram of an interface query method shown in an illustrative embodiment;
[0023] Figure 6is a hardware structure diagram of an electronic device where an interface query device is located, shown in an exemplary embodiment;
[0024] Figure 7 It is a block diagram of an interface query device shown in an illustrative embodiment. DETAILED DESCRIPTION
[0025] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0026] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.
[0027] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of this specification, the related technologies of furniture traceability involved in the embodiments of this specification are briefly described below.
[0028] API (Application Programming Interface), also known as application programming interface, is a set of specifications that define how software components interact with each other. API allows different software systems to communicate and exchange data, enabling them to work together. In software development, developers can use API to access specific functions or services without having to understand the underlying implementation details. API is usually provided in the form of functions, methods or protocols, and developers can program according to these interface specifications to achieve specific functions.
[0029] API parameters usually refer to the data or information passed to the API when calling the API. API parameters can be used to specify the details of the operation, the content of the request, or to control the behavior of the API. API parameters usually include input parameters and output parameters, which refer to the parameters passed to the API when calling the API and the results returned to the caller after the API is executed.
[0030] Entity recognition, also known as named entity recognition (NER), is an important task of natural language processing (NLP), which aims to identify and classify entities with specific meanings from text, such as names of people, places, organizations, etc. The main technical backgrounds of entity recognition algorithms include machine learning, natural language processing, semantic technology, and knowledge graphs.
[0031] Elasticsearch, or ES for short, is an open source distributed search and analytics engine built on Apache Lucene. Its main technical background includes distributed architecture, inverted index, distributed search and query, real-time, multiple query types, distributed aggregation and analysis, scalability, and plug-in ecosystem. The distributed architecture enables Elasticsearch to achieve high availability and horizontal scalability, the inverted index accelerates the search process, the real-time can process real-time data streams and logs, multiple query types meet different needs, distributed aggregation and analysis can perform complex statistical analysis on large-scale data sets, and the scalability and plug-in ecosystem enable users to expand and customize as needed. ES is a powerful, flexible, and reliable search and analytics engine that plays an important role in enterprise search, log analysis, e-commerce, and other fields.
[0032] In modern software development, API (application programming interface) plays a key role, enabling different software systems to communicate and interact with each other. With the rapid development of cloud computing, mobile applications and the Internet of Things, the importance of API sharing services has become increasingly prominent. API sharing services can be public API markets or internal API libraries of enterprises, providing developers with rich functions and resources, accelerating the software development and integration process.
[0033] For large-scale API sharing services, it is becoming increasingly challenging to effectively manage and utilize these APIs. In particular, when developers use these APIs, they often need to understand the meaning and type of the interface fields in order to correctly use and parse data. However, due to the complexity and diversity of APIs and the lack of standardized interface field naming specifications, developers often face the following problems:
[0034] 1. It is difficult to quickly match and query interface fields: When users search by keywords, the interface field names and descriptions in the API documentation may not be clear and detailed enough, making it difficult to accurately understand the meaning and purpose of the fields in the matching results. Matching can only be performed based on the basic information or text of the API resource.
[0035] 2. Difficulty in parsing data types: When parsing data returned by the interface, developers need to accurately identify the data type of each field, such as string, integer, date, etc., in order to correctly process and use the data.
[0036] 3. Data content cannot be queried: Developers usually need to import the data calls of the interface into Elasticsearch before supporting data content queries. This process requires a lot of development work and time.
[0037] 4. API changes and migration issues: The interface fields of API shared services may change over time or differ between different API versions. Developers need to be aware of these changes and adapt to the new interface fields in a timely manner.
[0038] In view of this, this specification proposes an interface query method that configures the metadata information of the API interface and combines it with an entity matching algorithm to enable the user to automatically match the interface input and output parameter information of the corresponding entity after entering keywords, so as to more accurately query the required API interface.
[0039] The present application is described below through specific embodiments and in combination with specific application scenarios.
[0040] See also Figure 1 , Figure 1 The present invention is a flowchart of an interface query method shown in an exemplary embodiment.
[0041] The above method is applied to an interface management platform, and the interface management platform stores the mapping relationship between interfaces and parameters; the following steps can be performed:
[0042] Step 102: Obtain keywords for querying the interface.
[0043] API interfaces are usually managed by an interface management platform. API interfaces are registered in the interface management platform and are maintained and managed by the interface management platform.
[0044] Since the number of API interfaces is usually very complex and diverse, when developers need to use a certain API or a certain type of API, they usually need to query it in the interface management platform. When querying the interface, they usually search through a search engine connected to the interface management platform.
[0045] The search engine connected to the interface management platform can be built-in or externally connected to the interface management platform. In this specification, the search engine connected to the interface management platform can generally be regarded as a component of the interface management platform.
[0046] A search engine is a software system specifically used to retrieve information. It allows users to obtain relevant information by entering keywords.
[0047] Traditional API interface management platforms and their connected search engines usually only register the name and brief information of the API interface. When users perform interface queries, the keywords they use must hit the name of the API interface or part of the brief information in order to query the corresponding API interface.
[0048] In the interface management platform of the present application, the mapping relationship between the interface and each corresponding parameter is stored in the interface management platform.
[0049] An API interface usually has a set of parameters, including parameters passed to the API interface when the API is called, and parameters of the result returned to the caller after the API interface is executed, which can usually be called output parameters and input parameters. The number of input and output parameters of an API interface depends on the specific API design and functional requirements. Generally speaking, an API interface can correspond to one or more parameters, and multiple API interfaces can also correspond to the same parameter.
[0050] See also Figure 2 , Figure 2 It is a schematic diagram of an interface parameter shown in an illustrative embodiment.
[0051] Figure 2 An exemplary mapping relationship between a portion of API interfaces and parameters in an interface management platform of an example is shown.
[0052] The interface management platform stores three API interfaces A, B, and C, and five parameters a, b, c, d, and e. API interface A contains three parameters, parameter a, parameter c, and parameter e; API interface B contains one parameter, parameter b; and API interface C contains one parameter, parameter d.
[0053] Step 104: Perform entity recognition on the keyword to determine the entity type of the keyword.
[0054] In this application, users can enter available values of parameters corresponding to the API interface to search for the API interface.
[0055] For example, the function of an API interface is to query the household registration information of a specific person, the input parameter is the name of the household registration person, and the output parameter is the household registration information. However, due to the randomness of API interface naming, the API interface may be named arbitrarily, such as "household registration query interface", "hujichaxun", "Household registration", "HJCX", or "AAA123", etc., and the developer may not know the name of the API interface.
[0056] However, the developer may know that one of the parameters of the API interface may be a name. In this case, the developer may query the implementation of the API interface by entering any name as a keyword, such as "Zhang San" or "Li Qiang".
[0057] After receiving the keywords input by the user, the interface management platform can perform entity recognition on the input keywords and determine the entity category corresponding to the keywords. Among them, this specification does not specifically limit the specific entity recognition algorithm. For example, a rule-based method can be used, such as using pre-written rules to identify entities, such as regular expressions, dictionary matching, etc.; for another example, a statistical-based method can also be used, using machine learning algorithms and statistical models to automatically learn features and patterns. Commonly used algorithms may include hidden Markov models (HMM), maximum entropy models (MaxEnt), conditional random fields (CRF), support vector machines (SVM), neural network models, such as recurrent neural networks (RNN), long short-term memory networks (LSTM), converter models (Transformer), etc.; for another example, a deep learning-based method can be used, such as using a bidirectional LSTM-CRF network structure, or using pre-trained language models such as BERT, GPT, etc.
[0058] The interface management platform recognizes the keyword "Zhang San" input above and can identify that its corresponding entity category is a name entity.
[0059] Step 106: Search the parameters in the interface management platform, determine the parameters of the entity type whose entity type is the keyword as the target parameter, determine the interface corresponding to the target parameter as the target interface, and return the target interface.
[0060] After identifying the entity category corresponding to the input keyword, the interface management platform can use the category entity to search for the parameters corresponding to the API interface managed in the interface management platform. The parameter whose entity type corresponds to the keyword is determined as the target parameter. A mapping relationship is established from keywords to entity types and then to parameters.
[0061] After determining the target parameters, the target interface corresponding to the target parameters can be further determined based on the mapping relationship between the API interface and the parameters saved in the interface management platform, thereby completing the complete search process of determining the entity type through keywords, determining the target parameters from the entity type, and determining the target API interface from the target parameters, thereby realizing the search for API interfaces through keywords of parameter value types.
[0062] See also Figure 3 , Figure 3It is a schematic diagram of an interface query method shown in an illustrative embodiment.
[0063] Still Figure 2 Taking the embodiment in as an example, Figure 3 An exemplary process of searching target parameters by keywords in the interface management platform of this example is shown.
[0064] The interface management platform can save the entity category corresponding to each parameter; the entity category corresponding to parameters a, b, c is entity α; the entity category corresponding to parameters d, e is entity γ.
[0065] According to a value of a parameter of a target API interface input by a user, such as a developer, k is used as a keyword; by performing entity recognition on k, its corresponding entity type is identified as entity γ; and the target parameters corresponding to entity γ are parameters a, b, c;
[0066] And as Figure 2 As shown, the target API interface corresponding to parameters a and c is API interface A, and the target API interface corresponding to parameter b is API interface B.
[0067] Therefore, through keyword k, target API interfaces whose entity types corresponding to the parameters contained therein are the same as the keyword types corresponding to keyword k can be found: API interface A and API interface B.
[0068] In the above embodiment, an API interface is associated and saved with the parameters it contains and the entity types corresponding to the parameters; when it is necessary to search for an API interface, entity recognition is performed on the input keyword to identify the entity type corresponding to the keyword, and the parameters corresponding to the entity type are used as target parameters, and the API interface containing the target parameters are used as the target API interface, thereby achieving the search for the API interface by using a value of a parameter of the target API interface as a keyword, thereby reducing the workload of users when searching and using the API and improving usage efficiency.
[0069] In an exemplary embodiment shown in this specification, determining a parameter of an entity type whose entity type is the keyword as a target parameter may include:
[0070] The entity type of the parameter in the interface management platform is determined, and the parameter whose entity type is the entity type of the keyword is determined as the target parameter.
[0071] This specification also does not specifically limit the method for determining the entity type corresponding to the parameter. For example, when the API interface is registered with the interface management platform, it can be pre-associated and saved in the interface management platform; it can also be saved in the interface management platform after being identified by the interface management platform, or the interface type corresponding to the parameter can be identified and determined in real time during the search.
[0072] In an exemplary embodiment shown in this specification, the interface management platform saves the entity type of the parameter.
[0073] The interface management platform saves the entity type of the parameter, the mapping relationship between the entity type corresponding to the parameter and the parameter, and combines the mapping relationship between the API interface and the parameter to establish a mapping relationship between the entity type and the API interface.
[0074] When the API interface is registered to the interface management platform, in addition to saving the API interface and the parameters contained therein to the interface management platform, the interface management platform can also determine the entity type corresponding to each parameter and save it to the interface management platform.
[0075] In an exemplary embodiment shown in this specification, the entity type corresponding to the parameter is determined by analyzing the metadata of the parameter.
[0076] Parameter metadata generally refers to descriptive information about the parameter, such as the parameter's name, type, range, unit, default value, description, etc.
[0077] Similarly, a variety of methods can be used to determine the correspondence between parameter metadata and entity types. For example, a rule-based method can be used, such as using pre-written rules to identify entities, such as regular expressions, dictionary matching, etc.; another example is a statistical method that uses machine learning algorithms and statistical models to automatically learn features and patterns, such as neural network models; another example is a deep learning-based or pre-trained language model.
[0078] In an illustrative embodiment shown in this specification, for an entity type, a standard metadata of the entity type may also be determined according to the characteristics of the entity type, thereby implementing a standard definition of the entity type.
[0079] When determining the entity type corresponding to the parameter, the metadata of the parameter may be matched with the standard metadata of each entity type, and the entity type whose matching degree exceeds a preset matching threshold may be determined as the entity type corresponding to the parameter.
[0080] See also Figure 4 , Figure 4 It is a schematic diagram of an interface parameter management shown in an illustrative embodiment.
[0081] Still Figure 2 Taking the embodiment in as an example, Figure 4 The process of determining the entity type of a parameter in the interface management platform of this example is shown.
[0082] The interface management platform saves parameters a, b, c, d, and e, and their metadata are [a], [b], [c], [d], and [e], respectively. When the above parameters are registered to the interface management platform, the interface management platform analyzes their metadata, determines the entity type of the parameter based on the parameter metadata, and saves it in the interface management platform.
[0083] In the interface management platform, the metadata [a], [b], [c] corresponding to parameters a, b, c are saved to match entity type a, and the metadata [d], [e] corresponding to parameters d, e are saved to match entity type b.
[0084] See also Figure 5 , Figure 5 It is a schematic diagram of an interface query method shown in an illustrative embodiment.
[0085] The interface management platform stores the mapping relationship between API interfaces and parameters, the metadata corresponding to the parameters, and the entity types corresponding to the metadata.
[0086] When the user enters a keyword, entity recognition can be performed on the keyword, and the recognized entity type can be used as the target entity type. The parameter whose metadata meets the requirements of the target entity type can be determined as the target parameter, and the API interface containing the target parameter can be determined as the target API interface and returned as the search result.
[0087] Still Figure 2 Taking the implementation example in as an example, when API interfaces A, B, and C are registered to the interface management platform, the interface management platform saves the mapping relationship between the API interface and its parameters, and extracts the metadata of each parameter to determine the entity type corresponding to the parameter, and establishes a mapping relationship between entity α and parameters a, b, and c, and a mapping relationship between entity γ and parameters d and e.
[0088] When a user uses keyword k to search for an API interface on the above-mentioned interface management platform, the keyword k can first be subjected to entity recognition to determine that its entity category is entity γ, and based on the mapping relationship between entity type and parameters, the target parameters can be determined to be parameters d and e; further, based on the mapping relationship between parameters and API interfaces, the target API interfaces can be determined to be API interfaces A and C.
[0089] Since the correspondence between API interface and parameters, the correspondence between parameters and metadata, and the correspondence between metadata and entity types are all determined when the API interface is registered in the interface management platform, when the API interface is registered in the interface management platform, the interface management platform can directly save the correspondence between the entity type and the API interface.
[0090] When actually searching, after the user enters a keyword and the keyword is recognized as an entity, the corresponding API interface can be directly determined based on the recognized entity type.
[0091] In an illustrative embodiment shown in the present description, after the target API interface is found, the target API interface can be returned as a search result, and the target parameters can be returned and displayed as additional information of the target API interface to enable the user to better understand the returned search results.
[0092] In addition, the above search method can be combined with the traditional API search method.
[0093] When an API interface is registered to the interface management platform, the description information of the API interface may also be associated with the API interface and saved.
[0094] The description information of the API interface may include the name and introduction of the API interface. The introduction of the API interface introduces the usage and usage scenarios of the API interface.
[0095] When receiving keywords input by the user, in addition to using the above method in combination with entity categories for searching, you can also use the keywords as search terms in parallel to search for the keywords in the description information of the API interface in the interface management platform, and return the search results together with the search results of the above method in combination with entity categories.
[0096] In addition, since the description information of the API interface may include a description of the parameters, the name of the entity type obtained after entity recognition of the keywords entered by the user, such as "name", can also be used as a search term to search for the description information of the API interface in the interface management platform, and the search results can be returned together.
[0097] The above interface management platform can have built-in or external professional search engines, such as Lucene, Solr, RDBMS, OpenTSDB, HBase, etc., to achieve more efficient search.
[0098] In an exemplary embodiment shown in this specification, the ElasticSearch engine can be used as a search engine.
[0099] See also Figure 6 , Figure 6 It is a hardware structure diagram of an electronic device where an interface query device is located, which is shown as an illustrative embodiment. At the hardware level, the device includes a processor 602, an internal bus 604, a network interface 606, a memory 608, and a non-volatile memory 610, and of course may also include hardware required for other services. One or more embodiments of this specification can be implemented based on software, such as the processor 602 reading the corresponding computer program from the non-volatile memory 610 into the memory 608 and then running it. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.
[0100] See also Figure 7 , Figure 7 It is a block diagram of an interface query device shown in an illustrative embodiment.
[0101] The interface query device is applied to an interface management platform, and the interface management platform stores the mapping relationship between interfaces and parameters; the device may include:
[0102] An acquisition unit 710 is used to acquire keywords for querying the interface;
[0103] An identification unit 720, configured to perform entity identification on the keyword to determine the entity type of the keyword;
[0104] The search unit 730 is used to search in the parameters in the interface management platform, determine the parameter of the entity type whose entity type is the keyword as the target parameter, determine the interface corresponding to the target parameter as the target interface, and return the target interface.
[0105] In one embodiment, the interface management platform further stores description information of the interface, wherein the description information includes the name of the interface and a brief introduction of the interface;
[0106] The device further includes: a second search unit 740, which is used to
[0107] The keyword is searched in the description information of the interface stored in the interface management platform, and the interface whose description information contains the keyword is determined as the target interface.
[0108] In one embodiment, determining the parameter whose entity type is the keyword as the target parameter includes:
[0109] Determining the entity type of the parameter in the interface management platform;
[0110] A parameter whose entity type is the entity type of the keyword is determined as a target parameter.
[0111] In one embodiment, the interface management platform stores the entity type of the parameter.
[0112] In one embodiment, the interface management platform stores the entity type of the parameter, including:
[0113] When the interface management platform saves the interface registered to the interface management platform, the metadata corresponding to the parameters contained in the interface are matched with the standard metadata of each entity type, and the entity type with a matching degree exceeding a preset threshold is determined as the entity type of the parameter.
[0114] In one embodiment, returning the target interface includes:
[0115] Returns the target interface and displays the target parameters corresponding to the target interface.
[0116] In one embodiment, the interface management platform includes an Elasticsearch engine.
[0117] The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.
[0118] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can refer to the partial description of the method embodiments. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. Ordinary technicians in this field can understand and implement it without paying creative work.
[0119] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.
[0120] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0121] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0122] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0123] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, furniture or equipment that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, furniture or equipment. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, furniture or equipment that includes the elements.
[0124] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0125] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "one", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0126] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0127] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.
Claims
1. An interface query method, applied to an interface management platform, wherein the interface management platform stores a mapping relationship between interfaces and parameters; characterized in that: Get the keywords used to query the interface; Performing entity recognition on the keyword to determine the entity type of the keyword; A search is performed in the parameters in the interface management platform, a parameter of an entity type whose entity type is the keyword is determined as a target parameter, an interface corresponding to the target parameter is determined as a target interface, and the target interface is returned.
2. The method according to claim 1, characterized in that: The interface management platform also stores the description information of the interface, which includes the name of the interface and a brief introduction of the interface; The method further comprises: The keyword is searched in the description information of the interface stored in the interface management platform, and the interface whose description information contains the keyword is determined as the target interface.
3. The method according to claim 1, characterized in that The step of determining the parameter whose entity type is the keyword as the target parameter includes: Determining the entity type of the parameter in the interface management platform; A parameter whose entity type is the entity type of the keyword is determined as a target parameter.
4. The method according to claim 3, characterized in that The interface management platform stores the entity type of the parameter.
5. The method according to claim 1, characterized in that The interface management platform stores the entity type of the parameter, including: When the interface management platform saves the interface registered to the interface management platform, the metadata corresponding to the parameters contained in the interface are matched with the standard metadata of each entity type, and the entity type with a matching degree exceeding a preset threshold is determined as the entity type of the parameter.
6. The method according to claim 1, characterized in that The returning the target interface comprises: Returns the target interface and displays the target parameters corresponding to the target interface.
7. The method according to claim 1, characterized in that The interface management platform includes an Elasticsearch engine.
8. An interface query device, applied to an interface management platform, wherein the interface management platform stores the mapping relationship between interfaces and parameters; characterized in that: The device comprises: An acquisition unit, used to acquire keywords for querying the interface; An identification unit, used to perform entity identification on the keyword to determine the entity type of the keyword; The search unit is used to search in the parameters in the interface management platform, determine the parameter of the entity type whose entity type is the keyword as the target parameter, determine the interface corresponding to the target parameter as the target interface, and return the target interface.
9. A machine-readable storage medium, characterized in that: The machine-readable storage medium stores machine-readable instructions, and when the machine-readable instructions are called and executed by a processor, the method according to any one of claims 1 to 7 is implemented.
10. A computer device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 7 is implemented.
