Interface docking management system and interface docking management method

Abstract

The present invention relates to the technical field of interface management, and discloses an interface docking management system and an interface docking management method. The system is applied to an interface user end, and includes: configuring a single interface content, wherein the single interface content includes: an interface template content; upon receiving an interface request sent by a target interface, determining a request mode corresponding to the interface request according to an interface definition, wherein the request modes include: a single interface request mode and a combined interface request mode; determining an interface call mode according to the request mode, and performing an interface call on the target interface based on the interface template content and the interface call mode. Since the interface docking management system in the present invention is applied to the interface user end, and performs an interface call on the target interface based on the interface template content in the configured single interface content and the interface call mode corresponding to the target interface, the technical problem that interface docking generally tends to construct a large and comprehensive interface design at the end, which easily leads to traffic waste and data redundancy, is solved.

Description

Technical Field

[0001] The present invention relates to the technical field of interface management, and in particular to an interface docking management system and an interface docking management method. Background Art

[0002] As business expands, internal systems need to connect to an increasing number of external systems, often through interfaces. The industry has developed a variety of interface management tools, but the functionality currently offered by these platforms is primarily focused on the build side, with limited support for interface users. Interface designers often design them to be comprehensive and extensive to support a wide range of businesses and minimize the need for interface modifications. Users typically only require a subset of field values ​​on an interface. Circulating comprehensive, extensive interfaces internally can lead to wasted traffic and redundant data.

[0003] The above content is only used to assist in understanding the technical solution of the present invention and does not constitute an admission that the above content is prior art. Summary of the Invention

[0004] The main purpose of the present invention is to provide an interface docking management system and an interface docking management method, aiming to solve the technical problem in the prior art that interface docking usually tends to build a large and comprehensive interface design, which easily leads to traffic waste and data redundancy.

[0005] To achieve the above object, the present invention provides an interface docking management system, which is applied to an interface user end. The system includes: an interface configuration module and an interface request module;

[0006] The interface configuration module is used to configure the content of a single interface, wherein the content of the single interface includes: interface template content;

[0007] The interface request module is used to determine the request mode corresponding to the interface request according to the interface definition when receiving the interface request sent by the target interface, and the request mode includes: a single interface request mode and a combined interface request mode;

[0008] The interface request module is further configured to determine an interface calling method corresponding to the target interface according to the request method, and perform an interface call on the target interface based on the interface template content and the interface calling method.

[0009] Optionally, the interface request module is further configured to determine an interface calling method corresponding to the target interface according to the request method;

[0010] The interface request module is further configured to obtain the interface request data carried by the interface request when the interface call mode is a single interface call mode;

[0011] The interface request module is further configured to perform template rendering on the interface request data based on the interface template content to obtain request data to be executed;

[0012] The interface request module is further configured to perform an interface call on the target interface using the request data to be executed.

[0013] Optionally, the interface configuration module is further configured to configure combined interface content based on the single interface content, wherein the combined interface content includes: single interface dependency relationships between a plurality of single interfaces;

[0014] The interface request module is further configured to determine a single interface calling sequence according to the single interface dependency when the interface calling mode is determined to be a combined interface calling mode;

[0015] The interface request module is further configured to perform an interface call on the target interface in the single interface call manner based on the single interface call sequence.

[0016] Optionally, the interface configuration module is further configured to configure an authorization single interface, and when the configuration is completed, configure a combined interface content based on the single interface content, wherein the combined interface content is configured with the user data single interface being dependent on the authorization single interface, and the authorization data filling method of the user data interface;

[0017] The interface request module is further configured to obtain an authorization code through the authorization form interface;

[0018] The interface request module is further configured to perform an interface call on the target interface through the single interface call method based on the authorization code, the authorization data filling method, and the single interface call sequence.

[0019] Optionally, the interface docking management system further includes: an interface view rendering module;

[0020] The interface view rendering module is used to obtain interface view content based on the single interface content;

[0021] The interface view rendering module is further configured to determine and return target demand data based on the interface view content, interface actual data, and the interface request data.

[0022] Optionally, the interface configuration module is further configured to determine request requirement information according to business requirements;

[0023] The interface configuration module is further configured to determine a request identifier, request address information, and interface view content based on the request requirement information;

[0024] The interface configuration module is further configured to determine request parameter variables, and determine a request body based on the request parameter variables and the request requirement information;

[0025] The interface configuration module is further configured to configure the single interface content based on the request identifier, the request address information, the interface view content and the information request body.

[0026] Optionally, the interface view rendering module is further configured to perform field parsing on the interface view content and determine target requirement parameters according to the parsing results;

[0027] The interface view rendering module is further used to determine target requirement data based on the target requirement parameters, interface actual data and the interface request data.

[0028] In addition, to achieve the above-mentioned purpose, the present invention also proposes an interface docking management method based on the above-mentioned interface docking management system, the interface docking management method is applied to the interface user end, and the method includes:

[0029] The interface configuration module configures single interface content, and the single interface content includes: interface template content;

[0030] When the interface request module receives the interface request sent by the target interface, it determines the request mode corresponding to the interface request according to the interface definition, and the request mode includes: a single interface request mode and a combined interface request mode;

[0031] The interface request module determines the interface calling mode corresponding to the target interface according to the request mode, and performs an interface call on the target interface based on the interface template content and the interface calling mode.

[0032] Optionally, the step of the interface request module determining an interface calling method corresponding to the target interface according to the request method, and performing an interface calling on the target interface based on the interface template content and the interface calling method includes:

[0033] The interface request module determines the interface calling mode corresponding to the target interface according to the request mode;

[0034] The interface request module obtains the interface request data carried by the interface request when the interface call mode is a single interface call mode;

[0035] The interface request module performs template rendering on the interface request data based on the interface template content to obtain request data to be executed;

[0036] The interface request module performs an interface call on the target interface through the request data to be executed.

[0037] Optionally, after the step of configuring the single interface content by the interface configuration module, the method further includes:

[0038] The interface configuration module is further configured to configure the combined interface content based on the single interface content, wherein the combined interface content includes: single interface dependency relationships between a plurality of single interfaces;

[0039] After the step of the interface request module determining the interface call mode corresponding to the target interface according to the request mode, the method further includes:

[0040] When the interface calling mode is determined to be a combined interface calling mode, the interface request module determines a single interface calling order according to the single interface dependency relationship;

[0041] The interface request module performs an interface call on the target interface through the single interface call method based on the single interface call sequence.

[0042] The present invention discloses an interface docking management system applied to an interface user end, comprising: an interface configuration module and an interface request module; the interface configuration module is used to configure a single interface content, wherein the single interface content includes: an interface template content; the interface request module is used to determine, upon receiving an interface request sent by a target interface, a request mode corresponding to the interface request according to an interface definition, wherein the request modes include: a single interface request mode and a combined interface request mode; the interface request module is further used to determine an interface call mode according to the request mode, and to perform an interface call on the target interface based on the interface template content and the interface call mode; compared with the prior art in which interfaces designed based on a construction end are usually designed to be large and comprehensive, resulting in large and comprehensive interfaces circulating internally and causing traffic waste and data redundancy, since the interface docking management system of the present invention is applied to an interface user end, upon receiving an interface request sent by a target interface, the interface request module determines, upon receiving an interface request sent by a target interface, a request mode corresponding to the interface request according to the interface definition, and determines an interface call mode according to the request mode, and then performs an interface call on the target interface based on the interface template content and the interface call mode in the configured single interface content, thereby solving the technical problem in the prior art in which interface docking usually tends to be large and comprehensive due to the construction end, which easily leads to traffic waste and data redundancy. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 This is a structural block diagram of the first embodiment of the interface docking management system of the present invention;

[0044] Figure 2 This is a flowchart of executing a single interface request in the first embodiment of the interface docking management system of the present invention;

[0045] Figure 3This is an example diagram of complex combination interface call in the first embodiment of the interface docking management system of the present invention;

[0046] Figure 4 This is a flowchart of executing a combined interface request in the first embodiment of the interface docking management system of the present invention;

[0047] Figure 5 This is an example diagram of combined interface calling in the first embodiment of the interface docking management system of the present invention;

[0048] Figure 6 This is a structural block diagram of a second embodiment of the interface docking management system of the present invention;

[0049] Figure 7 This is a flow chart of a first embodiment of an interface docking management method according to the present invention based on the above-mentioned interface docking management system;

[0050] Figure 8 This is a flow chart of a second embodiment of the interface docking management method of the present invention based on the above-mentioned interface docking management system.

[0051] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0052] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0053] The technical solution of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0054] It should be noted that the descriptions of "first", "second", etc. in the embodiments of the present invention are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0055] Reference Figure 1 , Figure 1 This is a structural block diagram of the first embodiment of the interface docking management system of the present invention.

[0056] like Figure 1 As shown, the interface docking management system of this embodiment is applied to the interface user end, and the system includes: an interface configuration module 100 and an interface request module 200.

[0057] The interface configuration module 100 is used to configure single interface content, and the single interface content includes: interface template content.

[0058] It should be noted that the above-mentioned single interface content can be the relevant information of the single interface configured by the interface configuration module 100, that is, the request content of the three-party interface defined by the interface configuration module 100, such as: request unique identifier, request URL (Uniform Resource Locator), Method (request method), Header (request header), request body, cache definition, Mock definition, etc. This embodiment does not limit this.

[0059] It should be understood that the interface template content can be used to render the data of the request currently received by the system into data capable of executing the request. The interface template content in this embodiment can be parameter information requested by the system.

[0060] The interface request module 200 is used to determine the request mode corresponding to the interface request according to the interface definition when receiving the interface request sent by the target interface. The request mode includes: a single interface request mode and a combined interface request mode.

[0061] It is understandable that the target interface may be any interface defined by a third party, such as an interface for querying user information defined by a third party. This embodiment does not limit the specific function of the target interface.

[0062] It should be noted that the above interface request may be a request sent by the target interface for docking with the system.

[0063] It should be understood that since the interfaces in this embodiment include single interfaces and combined interfaces, the request modes corresponding to interface requests may include single interface request modes and combined interface request modes. A single interface request mode is a request mode corresponding to a single interface, while a combined interface request mode is a request mode corresponding to a combined interface. In this embodiment, the request mode corresponding to an interface can be determined based on the interface definition corresponding to each interface.

[0064] The interface request module 200 is further configured to determine an interface calling method corresponding to the target interface according to the request method, and perform an interface call on the target interface based on the interface template content and the interface calling method.

[0065] It is understandable that the above interface calling method can be a method for calling an interface. The interface calling method in this embodiment can include a single interface calling method and a combined interface calling method, wherein the single interface calling method is a method for calling a single interface; the combined interface calling method is a method for calling a combined interface.

[0066] It should be noted that the single interface calling method can be based on the interface template content configured by the interface configuration module 100, combined with the data of the current request, and rendered into data that can execute the request, thereby executing the calling method of the third-party interface. The combined interface calling method can be to first arrange the single interface calling sequence based on the single interface dependency diagram in the single interface content configured by the interface configuration module 100, and then call the single interface calling method with the combined data to realize the combined interface calling. Therefore, in this embodiment, after determining the interface calling method corresponding to the target interface according to the request method, the call to the target interface can be realized based on the interface template content and the interface calling method corresponding to the target interface.

[0067] In a specific implementation, first, the single interface content or the dependency relationship between the single interfaces in the combined interface can be configured. When an interface request sent by the target interface is received, the interface request is determined to be a single interface request mode or a combined interface request mode according to the interface definition. If it is a single interface request mode, the interface call mode corresponding to the target interface is a single interface call mode; if it is a combined interface request mode, the interface call mode corresponding to the target interface is a combined interface call mode. After determining the interface call mode corresponding to the target interface, the target interface can be called through the corresponding interface call mode based on the interface template content configured by the interface configuration module 100. Specifically, if the interface call mode corresponding to the target interface is a single interface call, the interface template content configured by the interface configuration module 100 can be combined with the data of the current request to render it into data that can execute the request, thereby executing the call of the target interface. If the interface call mode corresponding to the target interface is a combined interface call, the single interface call sequence can be arranged according to the single interface dependency graph in the single interface content configured by the interface configuration module 100, and then the combined data is called to call the single interface call mode, thereby executing the call of the target interface.

[0068] Furthermore, in order to implement interface calling of a single interface, the interface request module 200 is further configured to determine an interface calling mode corresponding to the target interface according to the request mode.

[0069] The interface request module 200 is further configured to obtain the interface request data carried by the interface request when the interface calling mode is a single interface calling mode.

[0070] It should be noted that the above-mentioned interface request data may be parameter data carried in the interface request, such as a request identifier, parameters required for the request, etc., which is not limited in this embodiment.

[0071] The interface request module 200 is further configured to perform template rendering on the interface request data based on the interface template content to obtain request data to be executed.

[0072] The interface request module 200 is further configured to perform an interface call on the target interface using the request data to be executed.

[0073] In the specific implementation, refer to Figure 2 , Figure 2 This is a flowchart of a single interface request execution in the first embodiment of the interface docking management system of the present invention. Figure 2 As shown, after receiving the interface request sent by the target interface, the interface definition can be read to determine whether the interface request is a single interface request or a combined interface request based on the interface definition. If it is a single interface request, the interface call method corresponding to the target interface can be determined as a single interface call method. At this time, the interface template content configured by the interface configuration module 100 can be combined with the interface request data of the current request carried in the interface request to render the interface request data into data that can execute the request, and then call the actual request. After that, the view can also be rendered and the required data can be returned to the requester.

[0074] Furthermore, in order to implement interface calling of the combined interface, the interface configuration module 100 is further configured to configure the combined interface content based on the single interface content, and the combined interface content includes: single interface dependency relationships between a plurality of single interfaces.

[0075] It should be noted that the aforementioned combined interface content may be information related to the combined interface configured by the interface configuration module 100. Accordingly, the aforementioned single interface dependency relationship refers to the dependency relationship between multiple single interfaces in the combined interface. In actual applications, when configuring the combined interface, the interface configuration module 100 may configure the dependency relationship between multiple single interfaces, as well as information such as parameter transfer relationships, based on the configuration of the single interface, to obtain the combined interface content.

[0076] The interface request module 200 is further configured to determine a single interface calling sequence according to the single interface dependency when the interface calling mode is determined to be a combined interface calling mode.

[0077] It should be understood that the above-mentioned single interface calling order may be the order of calling each single interface in the combined interface.

[0078] The interface request module 200 is further configured to perform an interface call on the target interface in the single interface call manner based on the single interface call sequence.

[0079] It can be understood that since the combined interface is composed of multiple single interfaces, after obtaining the calling order of each single interface in the combined interface, this embodiment can implement the calling of the combined interface according to the single interface calling order and then combine the data to call the single interface calling method.

[0080] It should be understood that referring to Figure 3 , Figure 3 This is an example diagram of a complex combined interface call in the first embodiment of the interface docking management system of the present invention. The combined interface call in this embodiment may have a complex arrangement method, and all interfaces in the interface docking management system proposed in this solution are based on the configuration method, which can simplify the process of docking with three-party interfaces. For the internal system, calling through the request identifier can unify the calling process; at the same time, through the response view, the internal transmission of redundant data is reduced, thereby improving the internal system performance; in addition, it can also effectively prevent corrosion, that is, based on the expansion of the system, for the problem that the third-party data may be missing, various policies, such as default values, can also be formulated to effectively protect the internal security of the system.

[0081] In the specific implementation, refer to Figure 4 , Figure 4 This is a flowchart of the combined interface request execution in the first embodiment of the interface docking management system of the present invention. Figure 4 As shown, after receiving the interface request sent by the target interface, the interface definition can be read to determine whether the interface request is a single interface request or a combined interface request based on the interface definition. If it is a combined interface request, the interface call method corresponding to the target interface can be determined as the combined interface call method. At this time, the single interface call sequence can be arranged according to the single interface dependency relationship in the combined interface content configured by the interface configuration module 100, and then the single interface call method can be called according to the single interface call sequence combination data to implement the combined interface call. After that, the view can be rendered and the required data can be returned to the requester.

[0082] Furthermore, the interface configuration module 100 is also used to configure the authorization single interface, and when the configuration is completed, configure the combined interface content based on the single interface content, wherein the combined interface content is configured with the user data single interface depending on the authorization single interface, and the authorization data filling method of the user data interface.

[0083] It should be noted that the authorization form interface described above may be an interface that requires authorization verification upon invocation. In practical applications, the interface side of this embodiment may also incorporate a permissions system. In this case, the interface configuration module 100 may first configure the authorization form interface and then add the definition of the combined interface. Specifically, in the configuration of the combined interface, the user data form interface may be configured to be dependent on the authorization form interface, and the method for populating the authorization data for the user data interface may be defined.

[0084] The interface request module 200 is further configured to obtain an authorization code through the authorization form interface.

[0085] It should be understood that if the interface party introduces an authorization system, the interface request module 200 needs to obtain an authorization code first and then call the user data interface.

[0086] The interface request module 200 is further configured to perform an interface call on the target interface through the single interface call method based on the authorization code, the authorization data filling method, and the single interface call sequence.

[0087] It can be understood that all configuration fields in the interface configuration module 100 are a kind of template engine, which can be filled with content through the corresponding data filling method. Therefore, in this embodiment, the interface configuration module 100 can pre-configure the authorization data filling method, so that the content can be filled through the authorization data filling method when the interface call is made subsequently.

[0088] In the specific implementation, refer to Figure 5 , Figure 5 This is an example diagram of combined interface call in the first embodiment of the interface docking management system of the present invention. Figure 5 As shown, if a permission system is introduced in the interface call, when calling the combined interface, the interface request module 200 can first obtain the authorization code, and then call the user data single interface based on the authorization code, authorization data filling method and single interface calling order, and through the single interface calling method.

[0089] Furthermore, the interface configuration module 100 is further configured to determine request requirement information according to business requirements.

[0090] It should be noted that the above business requirement may be a time business requirement, and accordingly, the above request requirement information may be the required requesting party data information. In actual applications, if the actual business requirement requires obtaining information such as a user's name and age, the corresponding request requirement information may be the user's name and age.

[0091] The interface configuration module 100 is further configured to determine a request identifier, request address information, and interface view content based on the request requirement information.

[0092] It should be understood that the above request identifier may be an identifier corresponding to an interface request, for example, GetUserNameAndAge. This embodiment does not limit the specific form of the request identifier.

[0093] It is understandable that the above-mentioned request address information may be the address of the interface request on the Internet, and this embodiment does not limit the method for obtaining the request address information.

[0094] The interface configuration module 100 is further configured to determine request parameter variables, and determine a request body based on the request parameter variables and the request requirement information.

[0095] It should be noted that the above request parameter variables can be variables that identify the information that the request needs to obtain, such as: uid, showDetail, etc., among which the request parameter variable uid can be used to identify the user, and the variable showDetail can be used to distinguish whether to return more detailed information.

[0096] The interface configuration module 100 is further configured to configure the single interface content based on the request identifier, the request address information, the interface view content and the information request body.

[0097] In a specific implementation, if the target interface is a third-party predefined interface for querying user information, the interface uses the request parameter variable uid to identify the user and uses the variable showDetail to determine whether to return more detailed information, the information includes:

[0098] curl 'http: / / www.example.com / user'--data-raw'{"uid":123456,"showDetail":false}'

[0099] {"name":"Zhang San",

[0100] "age": "40",

[0101] "city": "Changsha",

[0102] "hobbit": "singing and dancing",

[0103] "motto": "Only those who work hard can win"}

[0104] If the call is based on actual business needs, only the name and age of the requester are needed. Then when using API management, the interface configuration content can be:

[0105] Request ID: GetUserNameAndAge;

[0106] Request url: http: / / www.example.com / user;

[0107] Request body: {"uid": ${uid}, "showDetail": false};

[0108] Response view: {"name": ${result.name}", "age": ${result.age}}; ...

[0109] That is, the single interface content is configured based on the request identifier, request address information, request interface view, and information request body. At the same time, this embodiment can define uid, name, and age placeholders. In internal system requests, the request can carry the required request identifier (GetUserNameAndAge) and the required parameter uid. At this time, the interface request module 200 can render according to the parameters of the system request and call the actual request. After the three-party interface returns, it is assembled into a streamlined result according to the configured response view name and returns the required requester data.

[0110] This embodiment discloses an interface docking management system applied to an interface user end, comprising: an interface configuration module and an interface request module; the interface configuration module is used to configure a single interface content, wherein the single interface content includes: an interface template content; the interface request module is used to, upon receiving an interface request sent by a target interface, determine a request mode corresponding to the interface request according to an interface definition, wherein the request modes include: a single interface request mode and a combined interface request mode; the interface request module is further used to determine an interface call mode according to the request mode, and perform an interface call on the target interface based on the interface template content and the interface call mode; compared with the prior art, in which interfaces designed based on a construction end are usually designed to be large and comprehensive, resulting in large and comprehensive interfaces circulating internally and causing traffic waste and data redundancy, since the interface docking management system of the present invention is applied to an interface user end, the interface request module, upon receiving an interface request sent by a target interface, determines a request mode corresponding to the interface request according to the interface definition, and determines an interface call mode according to the request mode, and then performs an interface call on the target interface based on the interface template content and the interface call mode in the configured single interface content, thereby solving the technical problem in the prior art that interface docking usually tends to be designed on the construction end, resulting in large and comprehensive interfaces, which easily leads to traffic waste and data redundancy.

[0111] refer to Figure 6 , Figure 6 This is a structural block diagram of the second embodiment of the interface docking management system of the present invention. Based on the first embodiment of the interface docking management system mentioned above, the second embodiment of the interface docking management system of the present invention is proposed.

[0112] like Figure 6 As shown, the interface docking management system further includes: an interface view rendering module 300.

[0113] The interface view rendering module 300 is configured to obtain interface view content based on the single interface content.

[0114] It should be noted that the above interface view content can be the response data returned by the interface request. In actual applications, for an interface that queries user information, if it is necessary to obtain information on the two fields of user name and user age, the corresponding interface view content can be {"name": ${result.name}", "age": ${result.age}}. Among them, the interface view content can correspond to multiple, such as Figure 1 Only the user name is required; Figure 2 Only user age is required.

[0115] The interface view rendering module 300 is further configured to determine and return target demand data based on the interface view content, interface actual data, and the interface request data.

[0116] It should be understood that the aforementioned interface actual data may be the data corresponding to the interface. Accordingly, the aforementioned target demand data may be the data required by the requesting party. In practical applications, for an interface that queries user information, the interface actual data may include user name, user age, user city, user hobbies, etc. If, in actual business needs, only the requesting party's name and age are required, then the user name and age are the corresponding target demand data.

[0117] Furthermore, the interface view rendering module 300 is further configured to perform field parsing on the interface view content and determine target requirement parameters according to the parsing results.

[0118] It should be noted that the target requirement parameters described above may be parameters corresponding to information required by the business. For example, if the information required by the business is the user's name, the corresponding requirement parameter may be "name"; if the information required by the business is the user's age, the corresponding requirement parameter may be "age". In practical applications, since all information in the interface configuration module 100 is configured in the form of fields, this embodiment can perform field parsing on the interface view content to determine the parameters corresponding to the information required by the business based on the parsing results.

[0119] The interface view rendering module 300 is further configured to determine target requirement data based on the target requirement parameters, the actual interface data, and the interface request data.

[0120] In a specific implementation, the interface configuration module 100 will also configure the interface view content when performing interface configuration, so that the interface view rendering module 300 can obtain the interface view content based on the single interface content configured by the interface configuration module 100, and perform field parsing on the interface view content to determine the target requirement parameters based on the parsing results. Finally, the target requirement data can be obtained based on the target requirement parameters, the actual interface data and the interface request data, so that the target requirement data required by the requester can be returned.

[0121] This embodiment obtains the interface view content based on the single interface content through the interface view rendering module, and performs field analysis on the interface view content to determine the target requirement parameters, and then determines the target requirement data based on the target requirement parameters, the actual interface data and the interface request data, so as to accurately return the data required by the requester and improve data acquisition efficiency.

[0122] Based on the above-mentioned embodiments of the interface docking management system, a first embodiment of an interface docking management method based on the interface docking management system of the present invention is proposed.

[0123] refer to Figure 7 , Figure 7 1 is a flow chart of a first embodiment of an interface docking management method according to the present invention based on the above-mentioned interface docking management system.

[0124] In this embodiment, the interface docking management method based on the interface docking management system is applied to the interface user end, including the following steps:

[0125] Step S10: the interface configuration module configures single interface content, and the single interface content includes: interface template content.

[0126] It should be noted that the execution entity of the method of this embodiment can be an interface docking management device on the interface user end that can manage interface docking, or another interface docking management system that can achieve the same or similar functions and includes the interface docking management device. Here, the interface docking management system (hereinafter referred to as the system) is used to specifically illustrate the interface docking management method provided in this embodiment and the following embodiments.

[0127] Step S20: When the interface request module receives the interface request sent by the target interface, it determines the request mode corresponding to the interface request according to the interface definition. The request mode includes: a single interface request mode and a combined interface request mode.

[0128] Step S30: The interface request module determines the interface calling method corresponding to the target interface according to the request method, and performs an interface call on the target interface based on the interface template content and the interface calling method.

[0129] Furthermore, after step S30, the method also includes: the interface view rendering module, which is used to obtain the interface view content based on the single interface content; the interface view rendering module, which is also used to perform field parsing on the interface view content and determine the target requirement parameters based on the parsing results; the interface view rendering module, which is also used to determine and return the target requirement data based on the target requirement parameters, the actual interface data and the interface request data.

[0130] This embodiment discloses an interface docking management method applied to an interface user end, wherein an interface configuration module is used to configure a single interface content, wherein the single interface content includes: an interface template content; an interface request module is used to determine, upon receiving an interface request sent by a target interface, a request mode corresponding to the interface request according to an interface definition, wherein the request modes include: a single interface request mode and a combined interface request mode; the interface request module is further used to determine an interface call mode according to the request mode, and to perform an interface call on the target interface based on the interface template content and the interface call mode; compared with the prior art in which interfaces designed based on a construction end are usually designed to be large and comprehensive, resulting in large and comprehensive interfaces circulating internally and causing traffic waste and data redundancy, since the interface docking management method of the present invention is applied to an interface user end, the interface request module, upon receiving an interface request sent by a target interface, determines, upon receiving an interface request sent by a target interface, a request mode corresponding to the interface request according to the interface definition, and determines an interface call mode according to the request mode, and then performs an interface call on the target interface based on the interface template content and the interface call mode in the configured single interface content, thereby solving the technical problem in the prior art in which interface docking usually tends to be designed on the construction end, resulting in large and comprehensive interfaces, which easily leads to traffic waste and data redundancy. At the same time, this embodiment obtains the interface view content based on the single interface content through the interface view rendering module, and performs field analysis on the interface view content to determine the target requirement parameters, and then determines the target requirement data based on the target requirement parameters, the actual interface data and the interface request data, so as to accurately return the data required by the requester and improve data acquisition efficiency.

[0131] refer to Figure 8 , Figure 8 The flowchart of the second embodiment of the interface docking management method based on the above interface docking management system of the present invention is as follows. Based on the above first embodiment, the second embodiment of the interface docking management method based on the above interface docking management system of the present invention is proposed.

[0132] Based on the above first embodiment, in this embodiment, step S30 includes:

[0133] Step S301: The interface request module determines the interface calling method corresponding to the target interface according to the request method.

[0134] Step S302: When the interface calling mode is a single interface calling mode, the interface request module obtains the interface request data carried by the interface request.

[0135] Step S303: The interface request module performs template rendering on the interface request data based on the interface template content to obtain request data to be executed.

[0136] Step S304: the interface request module performs an interface call on the target interface through the request data to be executed.

[0137] Furthermore, after step S10, the method also includes: the interface configuration module is also used to configure the combined interface content based on the single interface content, and the combined interface content includes: single interface dependency relationships between several single interfaces; accordingly, after step S301, the method also includes: the interface request module determines the single interface calling order according to the single interface dependency relationship when the interface calling method is determined to be a combined interface calling method; the interface request module performs an interface call on the target interface through the single interface calling method based on the single interface calling order.

[0138] In this embodiment, when the interface calling mode corresponding to the target interface is a single interface calling mode, the interface request module obtains the interface request data carried by the interface request, performs template rendering on the interface request data based on the interface template content, obtains the request data to be executed, and performs an interface call on the target interface through the request data to be executed. At the same time, when the interface calling mode corresponding to the target interface is a combined interface calling mode, the single interface calling sequence is determined according to the single interface dependency relationship, and based on the single interface calling sequence, the interface call is performed on the target interface through the single interface calling mode. Since this embodiment unifies the caller's docking mode, it can reduce redundant data transmission and provide effective anti-corrosion for the internal system.

[0139] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0140] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0141] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0142] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. An interface docking management system, characterized in that: The interface docking management system is applied to the interface user end, and the system includes: an interface configuration module and an interface request module; The interface configuration module is used to configure the content of a single interface, wherein the content of the single interface includes: interface template content; The interface request module is used to determine the request mode corresponding to the interface request according to the interface definition when receiving the interface request sent by the target interface, and the request mode includes: a single interface request mode and a combined interface request mode; The interface request module is further configured to determine an interface call mode corresponding to the target interface according to the request mode, and perform an interface call on the target interface based on the interface template content and the interface call mode; The interface request module is further configured to determine an interface calling method corresponding to the target interface according to the request method; The interface request module is further configured to obtain the interface request data carried by the interface request when the interface call mode is a single interface call mode; The interface request module is further configured to perform template rendering on the interface request data based on the interface template content to obtain request data to be executed; The interface request module is further configured to perform an interface call on the target interface using the request data to be executed; The interface configuration module is further configured to configure the combined interface content based on the single interface content, wherein the combined interface content includes: single interface dependency relationships between a plurality of single interfaces; The interface request module is further configured to determine a single interface calling sequence according to the single interface dependency when the interface calling mode is determined to be a combined interface calling mode; The interface request module is further configured to perform an interface call on the target interface in the single interface call manner based on the single interface call sequence.

2. The interface docking management system according to claim 1, wherein: The interface configuration module is further configured to configure the authorization single interface and, upon completion of the configuration, configure the combined interface content based on the single interface content, wherein the combined interface content is configured with the user data single interface being dependent on the authorization single interface and the authorization data filling method of the user data single interface; The interface request module is further configured to obtain an authorization code through the authorization form interface; The interface request module is further configured to perform an interface call on the target interface through the single interface call method based on the authorization code, the authorization data filling method, and the single interface call sequence.

3. The interface docking management system according to claim 1, wherein: The interface docking management system further includes: an interface view rendering module; The interface view rendering module is used to obtain interface view content based on the single interface content; The interface view rendering module is further configured to determine and return target demand data based on the interface view content, interface actual data, and the interface request data.

4. The interface docking management system according to claim 1, wherein: The interface configuration module is further used to determine request requirement information according to business requirements; The interface configuration module is further configured to determine a request identifier, request address information, and interface view content based on the request requirement information; The interface configuration module is further configured to determine request parameter variables, and determine a request body based on the request parameter variables and the request requirement information; The interface configuration module is further configured to configure the single interface content based on the request identifier, the request address information, the interface view content and the information request body.

5. The interface docking management system according to claim 3, wherein: The interface view rendering module is further used to perform field parsing on the interface view content and determine target requirement parameters based on the parsing results; The interface view rendering module is further used to determine target requirement data based on the target requirement parameters, interface actual data and the interface request data.

6. An interface docking management method based on the interface docking management system according to any one of claims 1 to 5, characterized in that: The interface docking management method is applied to the interface user end, and the method includes: The interface configuration module configures single interface content, and the single interface content includes: interface template content; When the interface request module receives the interface request sent by the target interface, it determines the request mode corresponding to the interface request according to the interface definition, and the request mode includes: a single interface request mode and a combined interface request mode; The interface request module determines the interface calling mode corresponding to the target interface according to the request mode; The interface request module obtains the interface request data carried by the interface request when the interface call mode is a single interface call mode; The interface request module performs template rendering on the interface request data based on the interface template content to obtain request data to be executed; The interface request module performs an interface call on the target interface through the request data to be executed; After the step of configuring the single interface content by the interface configuration module, the method further includes: The interface configuration module is further configured to configure the combined interface content based on the single interface content, wherein the combined interface content includes: single interface dependency relationships between a plurality of single interfaces; After the step of the interface request module determining the interface call mode corresponding to the target interface according to the request mode, the method further includes: When the interface calling mode is determined to be a combined interface calling mode, the interface request module determines a single interface calling order according to the single interface dependency relationship; The interface request module performs an interface call on the target interface through the single interface call method based on the single interface call sequence.

Images