Interface call control method and device

Abstract

The present invention provides an interface call control method and device, the method comprising: establishing an interface consumption relationship in a software design stage; specifically, an application system of an interface provider registers an interface; an application system of an interface caller registers its own use requirements for the interface; the application system of the interface provider reviews whether the use requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the use requirements of the application system of the interface caller; after the evaluation is passed, a set of interface consumption relationships is established: the service side of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller; thereby realizing the forward shifting of the interface call relationship management between application systems from the runtime control to the development and design stage, and then by having the service side review the call application of the interface consumer and establishing an interface consumption relationship view, the necessity and rationality of the interface call of the consumer can be reviewed, and the service capability can be evaluated.

Description

Technical Field

[0001] The present invention belongs to the technical field of interface calling, and more specifically, particularly relates to an interface calling management and control method and device. Background Art

[0002] Current large-scale application software uses either traditional monolithic architecture or microservice architecture, and the need for mutual calls between different services is becoming more and more frequent. When the service capabilities of the service provider interface are insufficient or abnormal access is found, the access traffic is generally reduced by IP restrictions or service degradation, and there is a lack of prior evaluation and access mechanisms; when the service provider interface content changes, there is also a lack of timely notification mechanisms.

[0003] like Figure 1 As shown in the figure, under the monolithic architecture, there is usually no runtime registration center, and consumers and providers call directly. Figure 2 As shown in the figure, under the microservice architecture, there are a large number of mutual calls between services. Usually, after the service is started, the service will be automatically registered in the registration center. When the consumer needs to call the service, it first finds the required service from the registration center, and then the consumer can directly call the provider's service; under the microservice architecture, the registration center is needed to control the interface call relationship in the running state, and only the services registered in the registration center can be called.

[0004] However, the control of the above call relationships occurs when the system is running, which is an in-process control. It is impossible to plan and allocate service resources in advance, and there is a lack of review of whether the interface call requirements are reasonable. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide an interface call management method and device for reviewing the necessity and rationality of consumer interface calls and evaluating service capabilities.

[0006] The first aspect of the present invention discloses an interface call management method, comprising: establishing an interface consumption relationship in a software design stage; wherein the establishing of the interface consumption relationship comprises:

[0007] The application system registration interface of the interface provider;

[0008] The application system of the interface caller registers its own use requirements for the interface;

[0009] The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller;

[0010] After the evaluation is passed, a set of interface consumption relationships is established: the service party of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller.

[0011] Optionally, after establishing the interface consumption relationship, the method further includes:

[0012] Cancel the interface consumption relationship.

[0013] Optionally, the canceling the interface consumption relationship includes:

[0014] The application system of the interface caller applies to cancel the use demand of the interface;

[0015] The application system of the interface provider reviews the cancellation application of the application system of the interface caller;

[0016] After the review is passed, the consumption relationship between the original interface caller's application system and the interface provider's application system regarding the interface will be revoked.

[0017] Optionally, after establishing the interface consumption relationship, the method further includes:

[0018] Change the interface consumption relationship.

[0019] Optionally, the changing the interface consumption relationship includes:

[0020] The application system of the interface provider modifies the interface and generates a new interface;

[0021] The application system of the interface caller registers its own demand for using the new interface;

[0022] The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller;

[0023] After the evaluation is passed, a set of interface consumption relationships is established: the service provider of the new interface is the application system of the interface provider, and the consumer of the new interface is the application system of the interface caller.

[0024] Optionally, after the interface consumption relationship is changed, the consumption relationship of the interface to the interface by the application system of the interface caller remains unchanged.

[0025] The second aspect of the present invention discloses an interface call control device, comprising: an establishment module, used to establish an interface consumption relationship in the software design stage; wherein the establishment module is used to establish the interface consumption relationship in the software design stage, specifically for:

[0026] The application system registration interface of the interface provider;

[0027] The application system of the interface caller registers its own use requirements for the interface;

[0028] The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller;

[0029] After the evaluation is passed, a set of interface consumption relationships is established: the service party of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller.

[0030] Optionally, the interface calls the control device, further comprising:

[0031] The cancellation module is used to cancel the interface consumption relationship.

[0032] Optionally, the interface call control device, when the revocation module is used to revoke the interface consumption relationship, is specifically used to:

[0033] The application system of the interface caller applies to cancel the use demand of the interface;

[0034] The application system of the interface provider reviews the cancellation application of the application system of the interface caller;

[0035] After the review is passed, the consumption relationship between the original interface caller's application system and the interface provider's application system regarding the interface will be revoked.

[0036] Optionally, the interface calls the control device, further comprising:

[0037] Change module, used to change the interface consumption relationship.

[0038] It can be seen from the above technical scheme that an interface call management method provided by the present invention includes: establishing an interface consumption relationship in the software design stage; specifically, the application system of the interface provider registers the interface; the application system of the interface caller registers its own usage requirements for the interface; the application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller; after the evaluation is passed, a set of interface consumption relationships is established: the service party of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller; thereby realizing the forward shifting of the interface call relationship management between application systems from runtime management to the development and design stage, and then by having the service party review the call application of the interface consumer and establish an interface consumption relationship view, it is possible to review the necessity and rationality of the consumer's interface call and evaluate the service capability. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 It is a schematic diagram of a monolithic architecture provided by the prior art;

[0041] Figure 2 It is a schematic diagram of the microservice architecture provided by the existing technology;

[0042] Figure 3 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0043] Figure 4 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0044] Figure 5 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0045] Figure 6 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0046] Figure 7 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0047] Figure 8 This is a flow chart of an interface call management method provided by an embodiment of the present invention;

[0048] Fig. 9 It is a schematic diagram of an interface call control device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments 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 part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising 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, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0051] It should be noted that some professional terms are explained here:

[0052] Monolithic architecture: All functional modules are coupled in a single application and run as a process, which is easy to develop and deploy.

[0053] Microservice architecture: advocates dividing a single application into a group of small services, each of which runs in its own independent process. Services collaborate with each other using lightweight communication mechanisms, which are usually RESTful APIs based on the HTTP protocol. Each service is built around a specific business and can be independently deployed to a production environment.

[0054] Registration Center: A service module under the microservice architecture, used to register service providers and consumers when the system is running.

[0055] It is worth noting that using the registration center to control the interface call relationship generally requires the software system to be transformed into a microservice. If the monolithic architecture is maintained, each interface provider is usually required to control access rights. In addition, the services registered by the registration center are open to all consumers. If you want to limit the authority of a consumer to call the service provider's interface, the registration center generally restricts the IP address or adds a special gateway module to manage user access rights, or the service provider reduces or interrupts the service to the consumer through service downgrade, fuse, etc. when an exception occurs.

[0056] The control of the above call relationships occurs when the system is running, which is an in-process control. It is impossible to plan and allocate service resources in advance, and there is a lack of review on whether the interface call requirements are reasonable.

[0057] Based on this, an embodiment of the present invention provides an interface call management method for solving the problem that the management of call relationships in the prior art occurs when the system is running, which is an in-process management and control, and service resources cannot be planned and allocated in advance, and there is a lack of review of whether the interface call requirements are reasonable.

[0058] See also Figure 3 , this interface calls the control method, including:

[0059] S101. Establish interface consumption relationship during the software design phase.

[0060] That is to say, during the software design phase, an interface consumption relationship view is established, such as the interface consumer and service provider, so that the interface call can be realized.

[0061] Specifically, Figure 4 As shown, the establishment of the interface consumption relationship involved in step S101 includes:

[0062] S201. The application system of the interface provider registers the interface.

[0063] Specifically, the application system of the interface provider registers the name, function, attribute and other information of the interface. Of course, it is not limited to the operations described above, which will not be described one by one here, and all are within the protection scope of this application.

[0064] S202: The application system of the interface caller registers its own demand for using the interface.

[0065] Specifically, the application system of the interface caller registers its own needs, such as what type of interface is needed to achieve what function, etc., which will not be repeated here one by one and are all within the scope of protection of this application.

[0066] S203: The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller.

[0067] Specifically, the application system audit of the interface provider audits the rationality of the interface caller's application system calling the interface. If it is reasonable, the service capability is judged.

[0068] If the application system usage requirements of the interface caller are reasonable, and the service capability of the interface meets the usage requirements, the evaluation is passed. Of course, the specific process of step S203 can also be other ways, which will not be repeated here, and are all within the protection scope of this application.

[0069] S204: After the evaluation is passed, a set of interface consumption relationships is established.

[0070] Among them, the service provider of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller.

[0071] That is to say, after the consumption relationship is established, the interface can be consumed by the consumer, and the interface consumed by the consumer is provided by the service provider.

[0072] That is, the service provider's data model is provided in the form of an interface, and a consumption relationship mechanism is established with the consumer.

[0073] Specifically, application system A, the interface provider, registers interface a1, and application system A is the service provider of interface a1. Application system B, the interface caller, registers its system's use requirements for interface a1. The interface service provider reviews whether the consumer's use requirements are reasonable, and evaluates whether the interface's service capabilities can meet the consumer's use requirements. After the evaluation is passed, a set of interface consumption relationships is established: application system B consumes interface a1 of application system A, the service provider is application system A, and the consumer is application system B.

[0074] In this embodiment, in the software design phase, the service provider reviews the call application of the interface consumer and establishes an interface consumption relationship view, that is, the service provider can review the rationality of the interface caller's requirements and the service provider can evaluate the usage requirements of the interface caller in advance, which is helpful for coordinating and planning service capabilities, reviewing the necessity and rationality of the consumer's interface call, and evaluating service capabilities. At the same time, it is applicable to different system architectures, both for monolithic architecture systems and microservice architecture systems.

[0075] In practical applications, such as Figure 5 (exist Figure 3 As shown in the example of FIG. 1 , after step S101, establishing the interface consumption relationship, it also includes:

[0076] S102. Cancel the interface consumption relationship.

[0077] That is to say, the existing interface consumption relationship is revoked. The existing interface consumption relationship can be obtained by step S101, establishing the interface consumption relationship, or by the following step S103, changing the interface consumption relationship. They will not be described one by one here, and they are all within the protection scope of this application.

[0078] After the interface consumption relationship is revoked, the interface consumption relationship does not exist; that is, the corresponding provider and consumer are not associated based on the interface, and the consumer cannot consume the interface. The provider does not provide the interface to the consumer. In other words, revoking the interface consumption relationship means that the interface consumer revokes the use relationship of the service provider interface.

[0079] Specifically, Figure 6 (exist Figure 5 As shown in the example above, the specific process of canceling the interface consumption relationship is as follows:

[0080] S301. The application system of the interface caller applies to cancel the demand for using the interface.

[0081] Specifically, when the application system of the interface caller does not need to consume the interface, it applies to cancel the demand for use of the interface, such as issuing a cancellation request, etc., which is not specifically limited here and can be determined based on actual circumstances, and is all within the scope of protection of this application.

[0082] S302: The application system of the interface provider reviews the cancellation application of the application system of the interface caller.

[0083] Specifically, after receiving the cancellation request, the application system of the interface provider reviews the cancellation application of the application system of the interface caller, and approves the cancellation application when it meets the preset conditions. The preset conditions are not specifically limited here and can be determined according to the actual situation, all of which are within the scope of protection of this application.

[0084] S303: After the review is passed, the original consumption relationship between the application system of the interface caller and the application system of the interface provider regarding the interface is cancelled.

[0085] After the interface consumption relationship is revoked, the interface consumption relationship does not exist; that is, the corresponding provider and consumer are not associated based on the interface, and the consumer cannot consume the interface. The provider does not provide the interface to the consumer.

[0086] For example, application system B, the interface caller, applies to cancel the use demand for interface a1 of application system A. Application system A, the interface service provider, reviews the cancellation application of the consumer. After the review is passed, the original consumption relationship between application system B and application system A interface a1 is cancelled.

[0087] In practical applications, such as Figure 7 (exist Figure 5 As shown in the example of FIG. 1 , after step S101, establishing the interface consumption relationship, it also includes:

[0088] S103. Change the interface consumption relationship.

[0089] That is to say, the existing interface consumption relationship is changed. The existing interface consumption relationship can be obtained by establishing the interface consumption relationship in step S101, or by changing the interface consumption relationship in this step; after the consumption relationship obtained in step S101 is changed, it is changed again. This will not be described one by one here, and all are within the scope of protection of this application. The specific source of changing the interface consumption relationship is not specifically limited here, and it can be determined according to the actual situation, which is within the scope of protection of this application.

[0090] After changing the interface consumption relationship, the original interface consumption relationship may not exist or continue to exist; for example, after changing the interface consumption relationship, the consumption relationship of the interface by the application system of the interface caller remains unchanged. Whether the original interface consumption relationship exists is not specifically limited here, and it depends on the actual situation, and it is within the protection scope of this application.

[0091] Specifically, Figure 8 As shown in the figure, the specific process of changing the interface consumption relationship is:

[0092] S401. The application system of the interface provider modifies the interface and generates a new interface.

[0093] Specifically, the application system of the interface provider modifies the name, function, attribute and other information of the corresponding interface to generate a new interface. Of course, it is not limited to the operations described above, which will not be described here one by one, and are all within the protection scope of this application.

[0094] S402: The application system of the interface caller registers its own demand for using the new interface.

[0095] Specifically, the application system of the interface caller registers its own needs, such as what type of interface is needed to achieve what function, etc., which will not be repeated here one by one and are all within the scope of protection of this application.

[0096] S403: The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller.

[0097] Specifically, the application system audit of the interface provider audits the rationality of the interface caller's application system calling the interface. If it is reasonable, the service capability is judged.

[0098] If the application system usage requirements of the interface caller are reasonable, and the service capability of the interface meets the usage requirements, the evaluation is passed. Of course, the specific process of step S403 can also be other ways, which will not be repeated here, and are all within the protection scope of this application.

[0099] S404. After the evaluation is passed, a set of interface consumption relationships is established: the service provider of the new interface is the application system of the interface provider, and the consumer of the new interface is the application system of the interface caller.

[0100] Among them, the service provider of the new interface is the application system of the interface provider, and the consumer of the new interface is the application system of the interface caller.

[0101] That is, after the consumption relationship is established, the new interface can be consumed by the consumer, and the new interface consumed by the consumer is provided by the service provider.

[0102] It should be noted that interface changes and notifications involve application systems of both the interface service provider and the consumer. When the service provider interface changes, the change is transmitted and notified to the consumer; that is, the service provider's data model is provided in the form of an interface, and a consumer relationship and change notification mechanism are established with the consumer.

[0103] Specifically, application system A, the interface provider, modifies interface a1 and generates a new interface a2, and application system A is the service provider of interface a2. Application system B, the interface caller, registers the use requirements of this system for interface a2. The service provider reviews whether the consumer's demand for using interface a2 is reasonable, and evaluates whether the service capabilities of the interface can meet the consumer's usage requirements. After the evaluation is passed, a set of interface consumption relationships is established: application system B consumes interface a2 of application system A, the service provider is application system A, and the consumer is application system B. The original consumer B's consumption relationship with interface a1 remains unchanged. If B no longer needs to use interface a1, B can revoke the use of interface a1.

[0104] In this embodiment, when the service provider interface is changed, the consumer can be notified of the modification synchronously according to the registered interface call relationship view.

[0105] Another embodiment of the present invention provides an interface call control device, see Fig. 9 , including: establishing module 10, used to establish interface consumption relationship in the software design stage; wherein:

[0106] The module 10 is established to establish the interface consumption relationship during the software design phase, specifically for:

[0107] The application system registration interface of the interface provider.

[0108] The application system of the interface caller registers its own requirements for using the interface.

[0109] The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller;

[0110] After the evaluation is passed, a set of interface consumption relationships is established: the service side of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller.

[0111] The specific working process and principle of the establishment module 10 are described in detail in Figure 3 and Figure 4The embodiments shown will not be described in detail here, and all are within the protection scope of this application.

[0112] In actual application, the interface calls the control device and also includes:

[0113] The cancellation module 30 is used to cancel the interface consumption relationship.

[0114] The cancellation module 30 is used to cancel the interface consumption relationship, specifically for:

[0115] The application system of the interface caller applies to cancel the demand for using the interface.

[0116] The application system of the interface provider shall review the cancellation application of the application system of the interface caller.

[0117] After the review is passed, the original consumption relationship between the interface caller's application system and the interface provider's application system regarding the interface will be revoked.

[0118] The specific working process and principle of the revocation module 30 are described in detail in Figure 5 and Figure 6 The embodiments shown will not be described in detail here, and all are within the protection scope of this application.

[0119] In actual applications, the interface calls the control device, which also includes:

[0120] The changing module 20 is used to change the interface consumption relationship.

[0121] For details on the specific working process and principle of the change module 20, see Figure 7 and Figure 8 The embodiments shown will not be described in detail here, and all are within the protection scope of this application.

[0122] In this embodiment, during the development and design phase, the interface call relationship is registered and reviewed, and the service capabilities of the service provider are planned in advance based on the needs of the consumer. In addition, when the service provider changes the interface, the consumer is notified in time to synchronize the transformation according to the interface call relationship view that has passed the review.

[0123] The features recorded in the various embodiments in this specification can be replaced or combined with each other, and the same and similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system 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 can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0124] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0125] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An interface call management method, characterized in that: include: During the software design phase, establish interface consumption relationships; Changing the interface consumption relationship; wherein establishing the interface consumption relationship includes: The application system registration interface of the interface provider; The application system of the interface caller registers its own use requirements for the interface; The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller; After the evaluation is passed, a set of interface consumption relationships is established: the service side of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller; The changing interface consumption relationship includes: The application system of the interface provider modifies the interface and generates a new interface; The application system of the interface caller registers its own demand for using the new interface; The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller; After the evaluation is passed, a set of interface consumption relationships is established: the service provider of the new interface is the application system of the interface provider, and the consumer of the new interface is the application system of the interface caller; After the interface consumption relationship is changed, the consumption relationship of the interface to the application system of the interface caller remains unchanged.

2. The interface call management method according to claim 1, characterized in that: After establishing the interface consumption relationship, the method further includes: Cancel the interface consumption relationship.

3. The interface call management method according to claim 2, characterized in that: The cancelling of the interface consumption relationship includes: The application system of the interface caller applies to cancel the use demand of the interface; The application system of the interface provider reviews the cancellation application of the application system of the interface caller; After the review is passed, the consumption relationship between the original interface caller's application system and the interface provider's application system regarding the interface will be revoked.

4. An interface call control device, characterized in that: include: Create modules and change modules; The establishment module is used to establish an interface consumption relationship during the software design phase; wherein the establishment module is used to establish an interface consumption relationship during the software design phase, specifically for: The application system registration interface of the interface provider; The application system of the interface caller registers its own use requirements for the interface; The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller; After the evaluation is passed, a set of interface consumption relationships is established: the service side of the interface is the application system of the interface provider, and the consumer of the interface is the application system of the interface caller; The change module is used to change the interface consumption relationship; wherein the change module is used to change the interface consumption relationship, specifically to: The application system of the interface provider modifies the interface and generates a new interface; The application system of the interface caller registers its own demand for using the new interface; The application system of the interface provider reviews whether the usage requirements of the application system of the interface caller are reasonable, and evaluates whether the service capabilities of the interface can meet the usage requirements of the application system of the interface caller; After the evaluation is passed, a set of interface consumption relationships is established: the service provider of the new interface is the application system of the interface provider, and the consumer of the new interface is the application system of the interface caller; After the interface consumption relationship is changed, the consumption relationship of the interface to the application system of the interface caller remains unchanged.

5. The interface call control device according to claim 4, characterized in that: The interface call control device also includes: The cancellation module is used to cancel the interface consumption relationship.

6. The interface call control device according to claim 5, characterized in that: The interface call control device, the cancellation module is used to cancel the interface consumption relationship, specifically for: The application system of the interface caller applies to cancel the use demand of the interface; The application system of the interface provider reviews the cancellation application of the application system of the interface caller; After the review is passed, the consumption relationship between the original interface caller's application system and the interface provider's application system regarding the interface will be revoked.

Images