Method and device for processing interface between systems
By collecting and optimizing subsystem interface information on the public platform of the system and determining the optimal interface, the problem of development difficulty and large amount caused by the complexity of interface calls between systems is solved, and more efficient interface development is achieved.
Patent Information
- Application Number
- CN202111348885.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-11-15
- Publication Date
- 2024-11-26
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
When inter-system interface calls become complicated, it is difficult to develop interfaces between new systems and multiple existing systems, resulting in an increase in development volume.
By pre-collecting interface information of each subsystem on the system's public platform, determining the optimal interface that meets the target subsystem field call needs in accordance with preset optimization rules, reducing development difficulty and development volume.
It effectively reduces the development difficulty and development volume of new systems, improves the efficiency of inter-system interface calling, and reduces development complexity.
Smart Images

Figure CN114047910B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of distributed technology, and more specifically, to a method and device for processing an interface between systems. Background Art
[0002] Today's systems are becoming increasingly large, and the interface calls between systems are becoming increasingly complex.
[0003] When developing a new system, it is necessary to sort out the interface information of all existing systems that may have data call relationships with the new system. If the new system has data call relationships with multiple existing systems, it is necessary to develop interfaces between the new system and each existing system separately, which is difficult to develop and requires a large amount of development. Summary of the invention
[0004] In view of this, the present invention provides a method and device for processing interfaces between systems, which effectively reduce the difficulty and workload of developing new systems.
[0005] In order to achieve the above-mentioned invention object, the specific technical solution provided by the present invention is as follows:
[0006] A method for processing an interface between systems is applied to a common platform in a system, wherein the system further comprises a plurality of subsystems, each subsystem having an interface with at least one other subsystem, and the method comprises:
[0007] When receiving an interface call request, parsing the interface call request to obtain at least one field required to be called by the target subsystem;
[0008] Read the interface information published by each subsystem in the system from the pre-stored interface information configuration file;
[0009] According to preset optimization rules, the optimal interface that meets the field call requirements of the target subsystem is determined based on the interface information released by each subsystem.
[0010] Optionally, the determining, according to a preset optimization rule and according to the interface information published by each subsystem, an optimal interface that meets the field call requirements of the target subsystem includes:
[0011] Traversing the interface information configuration file to determine all interface combinations that meet the field call requirements of the target subsystem, the interface combination comprising: interface information containing any field that the target subsystem needs to call, and a subsystem identifier that publishes the interface information;
[0012] Counting the number of interfaces hit by each interface combination, the number of subsystems, the number of subsystems that are already connected, and the number of interfaces between subsystems that are already connected;
[0013] The optimization goal is to minimize the number of interfaces and subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems, and determine the optimal interface that meets the field call requirements of the target subsystem.
[0014] Optionally, after determining the optimal interface that meets the target subsystem field call requirement, the method further includes:
[0015] Obtaining the data volume of each field required to be called by the target subsystem;
[0016] Determine whether the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface;
[0017] If the data volume of each field required to be called by the target subsystem is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface required to be developed for the target subsystem;
[0018] If the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
[0019] Optionally, the method further includes:
[0020] Upon receiving an interface query request, verify the identity information of the requester;
[0021] When the identity information of the requester is verified, the interface query request is parsed to obtain query parameters;
[0022] Querying the interface information corresponding to the query parameter in the interface information configuration file;
[0023] The interface information corresponding to the query parameter obtained by the query is fed back to the requester.
[0024] Optionally, the method further includes:
[0025] When receiving the interface error information, parsing the interface error information to obtain the error interface information;
[0026] Sending an error verification request carrying the error reporting interface information to the subsystem that publishes the error reporting interface information;
[0027] If the interface correctness information fed back by the subsystem that published the error interface information is received, no operation is performed on the error interface information;
[0028] If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
[0029] An interface processing device between systems is applied to a common platform in the system, wherein the system further comprises a plurality of subsystems, each subsystem having an interface with at least one other subsystem, and the device comprises:
[0030] An interface call request parsing unit, configured to parse the interface call request upon receiving the interface call request, and obtain at least one field required to be called by the target subsystem;
[0031] A configuration file reading unit, used to read the interface information published by each subsystem in the system from a pre-stored interface information configuration file;
[0032] The optimal interface determination unit is used to determine the optimal interface that meets the field call requirements of the target subsystem according to the interface information released by each subsystem in accordance with the preset optimization rules.
[0033] Optionally, the optimal interface determination unit is specifically configured to:
[0034] Traversing the interface information configuration file to determine all interface combinations that meet the field call requirements of the target subsystem, the interface combination comprising: interface information containing any field that the target subsystem needs to call, and a subsystem identifier that publishes the interface information;
[0035] Counting the number of interfaces hit by each interface combination, the number of subsystems, the number of subsystems that are already connected, and the number of interfaces between subsystems that are already connected;
[0036] The optimization goal is to minimize the number of interfaces and subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems, and determine the optimal interface that meets the field call requirements of the target subsystem.
[0037] Optionally, the device further includes an interface extreme value checking unit, which is specifically used to:
[0038] Obtaining the data volume of each field required to be called by the target subsystem;
[0039] Determine whether the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface;
[0040] If the data volume of each field required to be called by the target subsystem is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface required to be developed for the target subsystem;
[0041] If the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
[0042] Optionally, the device further includes an interface information query unit, specifically configured to:
[0043] Upon receiving an interface query request, verify the identity information of the requester;
[0044] When the identity information of the requester is verified, the interface query request is parsed to obtain query parameters;
[0045] Querying the interface information corresponding to the query parameter in the interface information configuration file;
[0046] The interface information corresponding to the query parameter obtained by the query is fed back to the requester.
[0047] Optionally, the device further includes an interface information modification unit, which is specifically configured to:
[0048] When receiving the interface error information, parsing the interface error information to obtain the error interface information;
[0049] Sending an error verification request carrying the error reporting interface information to the subsystem that publishes the error reporting interface information;
[0050] If the interface correctness information fed back by the subsystem that published the error interface information is received, no operation is performed on the error interface information;
[0051] If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
[0052] Compared with the prior art, the beneficial effects of the present invention are as follows:
[0053] The present invention discloses a method for processing interfaces between systems. A public platform in the system collects interface information published by each subsystem in the system in advance. When an interface call request is received, the public platform determines the optimal interface that meets the field call requirements of the target subsystem according to the interface information published by each subsystem in accordance with preset optimization rules, thereby effectively reducing the difficulty and workload of developing a new system. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] 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 only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0055] Figure 1 A schematic diagram of the system structure disclosed in an embodiment of the present invention;
[0056] Figure 2 A schematic diagram of a flow chart of an interface processing method between systems disclosed in an embodiment of the present invention;
[0057] Figure 3 A schematic diagram of a partial method flow of an interface processing method between systems disclosed in an embodiment of the present invention;
[0058] Figure 4 The present invention is a schematic diagram of the structure of an interface processing device between systems disclosed in an embodiment of the present invention. DETAILED DESCRIPTION
[0059] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only 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.
[0060] After research, the inventor found that: the current system is becoming more and more complex, with a large number of subsystems, and there are multiple interfaces between each subsystem, and the interface calls between systems are becoming more and more complicated. When developing a new subsystem, it is necessary to sort out the interface information of all existing systems that may have data call relationships with the new system. If the new system has a data call relationship with multiple existing systems, it is necessary to develop the interface between the new system and each existing system separately, which is difficult to develop and the resulting development workload is also large.
[0061] In order to solve the above technical problems, the present invention discloses an interface processing method between systems, which is applied to a common platform in a system. The system also includes multiple subsystems, and each subsystem has an interface with at least one other subsystem. Figure 1 Taking the system structure shown in the figure as an example, each subsystem in the system can exchange data with the public platform and publish interface information to the public platform. The subsystems can also exchange data through interfaces. It should be noted that Figure 1 The system structure shown is only an example, and the present invention does not specifically limit the number of subsystems and the data interaction relationship between subsystems.
[0062] The public platform collects the interface information published by each subsystem in the system in advance. When an interface call request is received, the public platform determines the optimal interface that meets the field call requirements of the target subsystem according to the interface information published by each subsystem in accordance with the preset optimization rules, effectively reducing the difficulty and amount of new system development.
[0063] For details, please refer to Figure 2 , a method for processing an interface between systems disclosed in this embodiment includes the following steps:
[0064] S101: When an interface call request is received, the interface call request is parsed to obtain at least one field required to be called by the target subsystem;
[0065] The interface call request can be manually input into the public platform by the developer, or sent to the public platform by the target subsystem.
[0066] The target subsystem can be a subsystem to be developed, or it can be an existing system within the system, but new functions need to be developed.
[0067] At least one field that the target subsystem needs to call is a field that needs to be called to other subsystems in the system to implement the functions of the target subsystem. The field can be in the interface of one subsystem, or in the interfaces of more than one subsystems, or in more than one interface of one subsystem, or in more than one interface of more than one subsystems. No specific limitation is made here.
[0068] Taking the banking system as an example, the payment system within the banking system needs to call the account number and password in the account management system when implementing the account number and password verification function during the payment process.
[0069] S102: Reading interface information published by each subsystem in the system from a pre-stored interface information configuration file;
[0070] Each subsystem in the system publishes its interface information to the public platform, and the public platform organizes the interface information published by each subsystem to form an interface information configuration file.
[0071] Interface information includes: subsystem identifier, interface identifier, field information in the interface, etc.
[0072] S103: According to preset optimization rules, the optimal interface that meets the field call requirements of the target subsystem is determined based on the interface information released by each subsystem.
[0073] The optimization goal of the preset optimization rule is to determine the optimal interface that minimizes the development difficulty and development workload of the target subsystem and meets the field call requirements of the target subsystem based on the interface information released by each subsystem.
[0074] See also Figure 3 This embodiment discloses a method for determining an optimal interface that meets the target subsystem field call requirements, which specifically includes the following steps:
[0075] S201: traverse the interface information configuration file to determine all interface combinations that meet the target subsystem field call requirements;
[0076] Specifically, at least one field required to be called by the target subsystem is matched with the fields in the interface information published by each subsystem in the interface information configuration file to obtain all interface combinations that meet the field call requirements of the target subsystem.
[0077] The interface combination includes: interface information containing any field that the target subsystem needs to call, and the subsystem identifier that publishes the interface information.
[0078] The number of interfaces in the interface combination is one or more.
[0079] S202: Counting the number of interfaces hit by each interface combination, the number of subsystems, the number of subsystems that are already connected, and the number of interfaces between subsystems that are already connected;
[0080] Among them, the number of interfaces hit by the interface combination is the number of all interfaces in the interface combination, the number of subsystems hit by the interface combination is the number of all subsystems in the interface combination, the number of connected subsystems hit by the interface combination is the number of subsystems in the interface combination that are already connected to the target subsystem, which number can be 0, and the number of interfaces between the already connected subsystems hit by the interface combination is the number of interfaces in the interface combination that are already connected to the target subsystem.
[0081] S203: Determine the optimal interface that meets the target subsystem field call requirements by taking the minimum number of interfaces and subsystems hit by the interface combination and the maximum number of connected subsystems and interfaces between connected subsystems as the optimization goal.
[0082] It is understandable that in order to reduce the development difficulty and development workload of the target subsystem, the fewer the number of interfaces and subsystems hit by the interface combination, the better, and the more the number of already connected subsystems hit by the interface combination and the number of interfaces between already connected subsystems, the better.
[0083] On this basis, specifically, the optimization goal can be achieved through an evaluation function. The number of interfaces hit by the interface combination, the number of subsystems, the number of connected subsystems and the number of interfaces between already connected subsystems, and the variance of the number of hit fields in the interface are used as independent variables of the evaluation function. According to the pre-set weights of each independent variable, the evaluation score of each interface combination is calculated. The optimization goal is to minimize the number of interfaces and the number of subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems. According to the evaluation score of each interface combination, the optimal interface that meets the target subsystem field call requirements is determined.
[0084] It should be noted that the purpose of optimizing the target is to reduce the development difficulty and development workload of the target subsystem. A specific example may be: if the fields that the target subsystem needs to call include field 1, field 2, and field 3, the interface between subsystem A and subsystem B in the system includes field 1, the interface between subsystem B and subsystem C includes field 2, and the interface between subsystem C and other subsystems includes field 3, then it is necessary to develop an interface between the target subsystem and subsystem C, and at the same time, make subsystem C request field 2 from subsystem B, and subsystem C request field 1 from subsystem A through subsystem B, and finally make subsystem C obtain field 1, field 2, and field 3 through the interface request with the target subsystem. In this case, for the target subsystem, it is only necessary to develop the interface between the target subsystem and subsystem C, which effectively reduces the development difficulty and development workload of the target subsystem.
[0085] Furthermore, after the public platform determines the optimal interface that meets the target subsystem field call requirements, it will obtain the interface extreme value information, that is, the upper limit of the data volume, according to the format of the optimal interface, and then implement automatic testing of the interface through automatic testing software to improve the effectiveness of system testing.
[0086] Specifically, the data volume of each field that the target subsystem needs to call is obtained, and it is determined whether the data volume of each field that the target subsystem needs to call is greater than the upper limit of the data volume of the corresponding optimal interface. Taking field 1 that the target subsystem needs to call as an example, the interface that includes field 1 in the optimal interface is interface A, and it is necessary to determine whether the data volume of field 1 of the target subsystem at runtime is greater than the upper limit of the data volume of interface A. If the data volume of each field that the target subsystem needs to call is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface that the target subsystem needs to develop. If the data volume of each field that the target subsystem needs to call is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
[0087] The inventors also found through research that many system problems are caused by incorrect interface information during subsystem development, which brings a huge workload to the subsequent system maintenance.
[0088] In order to solve the above technical problems, this embodiment discloses an interface processing method between systems, and the public platform provides an interface query function and an interface error screening function.
[0089] Specifically, the interface query function is implemented as follows:
[0090] When the public platform receives an interface query request, it verifies the identity information of the requester to ensure the security of the interface information of each subsystem in the system.
[0091] When the identity information of the requester is authenticated, the interface query request is parsed to obtain query parameters, which may be a subsystem identifier, an interface identifier, or a subsystem identifier + an interface identifier.
[0092] The interface information corresponding to the query parameter is queried in the interface information configuration file, and the interface information corresponding to the query parameter obtained by the query is fed back to the requester.
[0093] The interface error screening function is implemented as follows:
[0094] When the interface error information is received, the interface error information is parsed to obtain the error interface information.
[0095] An error verification request carrying the error interface information is sent to the subsystem that publishes the error interface information.
[0096] If the subsystem that publishes the error interface information receives the correct interface information, no operation is performed on the error interface information.
[0097] If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
[0098] Based on the method for processing an interface between systems disclosed in the above embodiment, this embodiment correspondingly discloses a device for processing an interface between systems, which is applied to a common platform in the system. The system also includes multiple subsystems, and each subsystem has an interface with at least one other subsystem. Figure 4 , the device comprises:
[0099] The interface call request parsing unit 401 is used to parse the interface call request when receiving the interface call request to obtain at least one field required to be called by the target subsystem;
[0100] The configuration file reading unit 402 is used to read the interface information published by each subsystem in the system from the pre-stored interface information configuration file;
[0101] The optimal interface determination unit 403 is used to determine the optimal interface that meets the field call requirements of the target subsystem according to the interface information released by each subsystem according to the preset optimization rules.
[0102] Optionally, the optimal interface determining unit 403 is specifically configured to:
[0103] Traversing the interface information configuration file to determine all interface combinations that meet the field call requirements of the target subsystem, the interface combination comprising: interface information containing any field that the target subsystem needs to call, and a subsystem identifier that publishes the interface information;
[0104] Counting the number of interfaces hit by each interface combination, the number of subsystems, the number of subsystems that are already connected, and the number of interfaces between subsystems that are already connected;
[0105] The optimization goal is to minimize the number of interfaces and subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems, and determine the optimal interface that meets the field call requirements of the target subsystem.
[0106] Optionally, the device further includes an interface extreme value checking unit, which is specifically used to:
[0107] Obtaining the data volume of each field required to be called by the target subsystem;
[0108] Determine whether the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface;
[0109] If the data volume of each field required to be called by the target subsystem is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface required to be developed for the target subsystem;
[0110] If the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
[0111] Optionally, the device further includes an interface information query unit, specifically configured to:
[0112] Upon receiving an interface query request, verify the identity information of the requester;
[0113] When the identity information of the requester is verified, the interface query request is parsed to obtain query parameters;
[0114] Querying the interface information corresponding to the query parameter in the interface information configuration file;
[0115] The interface information corresponding to the query parameter obtained by the query is fed back to the requester.
[0116] Optionally, the device further includes an interface information modification unit, which is specifically configured to:
[0117] When receiving the interface error information, parsing the interface error information to obtain the error interface information;
[0118] Sending an error verification request carrying the error reporting interface information to the subsystem that publishes the error reporting interface information;
[0119] If the interface correctness information fed back by the subsystem that published the error interface information is received, no operation is performed on the error interface information;
[0120] If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
[0121] The present embodiment discloses an interface processing device between systems. A public platform in the system collects in advance interface information published by each subsystem in the system. When an interface call request is received, the public platform determines the optimal interface that meets the field call requirements of the target subsystem according to the interface information published by each subsystem in accordance with preset optimization rules, thereby effectively reducing the difficulty and workload of developing a new system.
[0122] It should be noted that the method and device for processing an interface between systems provided by the present invention can be applied to the distributed field or the financial field. The above is only an example and does not limit the application field of the method and device for processing an interface between systems provided by the present invention.
[0123] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.
[0124] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including 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, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0125] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0126] The above-mentioned embodiments may be combined arbitrarily. For the above description of the disclosed embodiments, the features recorded in the embodiments in this specification may be replaced or combined with each other, so that professional and technical personnel in this field can implement or use the present application.
[0127] 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. A method for processing an interface between systems, characterized in that: A common platform is applied to a system, the system further comprising a plurality of subsystems, each subsystem having an interface with at least one other subsystem, the method comprising: When receiving an interface call request, parsing the interface call request to obtain at least one field required to be called by the target subsystem; Read the interface information published by each subsystem in the system from the pre-stored interface information configuration file; According to preset optimization rules, the optimal interface that meets the field call requirements of the target subsystem is determined based on the interface information released by each subsystem.
2. The method according to claim 1, characterized in that The step of determining the optimal interface that meets the field call requirements of the target subsystem according to the interface information published by each subsystem according to the preset optimization rules includes: Traversing the interface information configuration file to determine all interface combinations that meet the field call requirements of the target subsystem, the interface combination comprising: interface information containing any field that the target subsystem needs to call, and a subsystem identifier that publishes the interface information; Count the number of interfaces, the number of subsystems, the number of connected subsystems, and the number of interfaces between connected subsystems hit by each interface combination, wherein the number of connected subsystems hit by the interface combination is the number of subsystems in the interface combination that are already connected to the target subsystem, and the number of interfaces between connected subsystems hit by the interface combination is the number of interfaces in the interface combination that are already connected to the target subsystem; The optimization goal is to minimize the number of interfaces and subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems, and determine the optimal interface that meets the field call requirements of the target subsystem.
3. The method according to claim 1, characterized in that After determining the optimal interface that meets the target subsystem field call requirements, the method further includes: Obtaining the data volume of each field required to be called by the target subsystem; Determine whether the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface; If the data volume of each field required to be called by the target subsystem is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface required to be developed for the target subsystem; If the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
4. The method according to claim 1, characterized in that The method further comprises: Upon receiving an interface query request, verify the identity information of the requester; When the identity information of the requester is verified, the interface query request is parsed to obtain query parameters; Querying the interface information corresponding to the query parameter in the interface information configuration file; The interface information corresponding to the query parameter obtained by the query is fed back to the requester.
5. The method according to claim 1, characterized in that The method further comprises: When receiving the interface error information, parsing the interface error information to obtain the error interface information; Sending an error verification request carrying the error reporting interface information to the subsystem that publishes the error reporting interface information; If the interface correctness information fed back by the subsystem that published the error interface information is received, no operation is performed on the error interface information; If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
6. An interface processing device between systems, characterized in that: A common platform applied to a system, the system further comprising a plurality of subsystems, each subsystem having an interface with at least one other subsystem, the device comprising: An interface call request parsing unit, configured to parse the interface call request upon receiving the interface call request, and obtain at least one field required to be called by the target subsystem; A configuration file reading unit, used to read the interface information published by each subsystem in the system from a pre-stored interface information configuration file; The optimal interface determination unit is used to determine the optimal interface that meets the field call requirements of the target subsystem according to the interface information released by each subsystem in accordance with the preset optimization rules.
7. The device according to claim 6, characterized in that The optimal interface determination unit is specifically used to: Traversing the interface information configuration file to determine all interface combinations that meet the field call requirements of the target subsystem, the interface combination comprising: interface information containing any field that the target subsystem needs to call, and a subsystem identifier that publishes the interface information; Count the number of interfaces, the number of subsystems, the number of connected subsystems, and the number of interfaces between connected subsystems hit by each interface combination, wherein the number of connected subsystems hit by the interface combination is the number of subsystems in the interface combination that are already connected to the target subsystem, and the number of interfaces between connected subsystems hit by the interface combination is the number of interfaces in the interface combination that are already connected to the target subsystem; The optimization goal is to minimize the number of interfaces and subsystems hit by the interface combination and maximize the number of connected subsystems and the number of interfaces between already connected subsystems, and determine the optimal interface that meets the field call requirements of the target subsystem.
8. The device according to claim 6, characterized in that The device also includes an interface extreme value checking unit, which is specifically used for: Obtaining the data volume of each field required to be called by the target subsystem; Determine whether the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface; If the data volume of each field required to be called by the target subsystem is not greater than the upper limit of the data volume of the corresponding optimal interface, the optimal interface is determined to be the interface required to be developed for the target subsystem; If the data volume of each field required to be called by the target subsystem is greater than the upper limit of the data volume of the corresponding optimal interface, the fields whose data volume is greater than the upper limit of the data volume of the corresponding optimal interface and the corresponding optimal interface are displayed.
9. The device according to claim 6, characterized in that The device also includes an interface information query unit, which is specifically used to: Upon receiving an interface query request, verify the identity information of the requester; When the identity information of the requester is verified, the interface query request is parsed to obtain query parameters; Querying the interface information corresponding to the query parameter in the interface information configuration file; The interface information corresponding to the query parameter obtained by the query is fed back to the requester.
10. The device according to claim 6, characterized in that The device also includes an interface information modification unit, which is specifically used to: When receiving the interface error information, parsing the interface error information to obtain the error interface information; Sending an error verification request carrying the error reporting interface information to the subsystem that publishes the error reporting interface information; If the interface correctness information fed back by the subsystem that published the error interface information is received, no operation is performed on the error interface information; If the interface modification information fed back by the subsystem that publishes the error reporting interface information is received, the error reporting interface information in the interface information configuration file is modified accordingly according to the interface modification information.
Citation Information
Patent Citations
Processing method and system for interface call request
CN109857484A
Interface calling method and device and related equipment
CN112948723A
Interface call system and method
US20160371129A1
Method and device for simulating interface, computer apparatus, and storage medium
WO2020192141A1
