System interface dependency management and monitoring method and system based on incidence relation table
By constructing an interface relationship table and performing multi-dimensional queries and intelligent monitoring, the problem of managing and monitoring interface dependencies between complex systems is solved, achieving visualization of system architecture and high efficiency in emergency fault handling.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING ZHONGGUANCUN BANK CO LTD
- Filing Date
- 2025-12-31
- Publication Date
- 2026-04-14
AI Technical Summary
Existing technologies cannot effectively manage, query, and monitor interface dependencies between complex systems, leading to difficulties in fault location, opaque system architecture, and coarse-grained anomaly monitoring, resulting in low analysis efficiency.
By constructing an interface association table, the interface call chain is clearly presented. Multi-dimensional query and intelligent monitoring methods are used to record and compare the actual call relationship with the legitimate call relationship, triggering alarms.
It enables visualization of system architecture, precise and efficient impact analysis, improves emergency response efficiency and system stability, and reduces maintenance costs.
Smart Images
Figure CN121858342A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the fields of information technology and system operation and maintenance, and in particular to a method and system for managing, analyzing and monitoring interface call dependencies between devices in a complex distributed system environment. Background Technology
[0002] China UnionPay Full-Channel Payment Platform is a core payment service provided to financial institutions and merchants. Its interface system is mainly divided into two categories: online transaction interface (real-time interaction) and batch / file interface (back-end processing).
[0003] In modern enterprise IT architectures, especially large financial systems (such as the UnionPay omnichannel system), business functions are typically accomplished through collaboration between the system and numerous third-party systems (such as the core accounting system, the UnionPay system, and the customer settlement system) via interfaces. The internal implementation of a single external interface may call multiple third-party interfaces, forming a complex call chain. This complex dependency relationship presents significant operational and management challenges.
[0004] 1. Difficulty in analyzing the scope of impact: When a third-party system interface fails or changes, it is difficult to quickly and accurately assess which business interfaces of this system will be affected, resulting in low efficiency in fault location and emergency handling.
[0005] 2. Lack of architecture and documentation: The interface dependencies between systems often lack unified and accurate records, or only exist in the design documents, which are out of touch with the actual operation, resulting in an opaque system architecture and high learning costs for newcomers and system maintenance costs.
[0006] 3. Coarse-grained anomaly monitoring: Most existing monitoring devices focus on the availability and performance metrics of individual interfaces (such as response time and success rate), lacking the ability to monitor the logical level of the business call chain. For example, they cannot effectively detect logical anomalies such as "system B was mistakenly called when system A was supposed to be called".
[0007] 4. Low efficiency in troubleshooting: When business failures occur, maintenance personnel need to manually sort out complex system call relationships, which is time-consuming and labor-intensive, and prone to omissions, making it difficult to meet the high requirements of financial business for rapid recovery.
[0008] In existing technologies, common solutions use configuration management databases (CMDBs) or API gateways to record interface information. However, CMDBs typically focus on asset information and struggle to intuitively represent dynamic call dependency chains. API gateways, on the other hand, primarily manage inbound traffic and lack effective management of call relationships between the system's internal systems and backend third-party services. Therefore, there is an urgent need for a technical solution that can accurately characterize, conveniently query, and intelligently monitor based on dependency relationships. Summary of the Invention
[0009] This invention aims to address the problem of effectively managing, querying, and monitoring interface dependencies between complex systems in existing technologies. Specifically, it addresses how to clearly present interface call chains, how to quickly perform fault impact analysis, and how to monitor abnormal interface call logic, thereby improving the intelligence level of system operation and maintenance and the efficiency of fault emergency handling.
[0010] To solve the above-mentioned technical problems, the present invention adopts the following technical solution. The core idea is to make the scattered and implicit inter-system interface dependencies explicit and structured through a core interface association table, and build powerful query analysis capabilities and intelligent monitoring capabilities based on this table.
[0011] This invention provides a method for system interface dependency management and monitoring based on an association table, comprising: constructing an interface association table, constructing a multi-dimensional query, and implementing intelligent monitoring; wherein,
[0012] The method for constructing the interface association table includes the following steps:
[0013] S11 queries all external interfaces of the UnionPay omnichannel system, sorts out the external interfaces that each external interface calls to the third-party system, and stores the call relationship between the external interface and the external interface of the third-party system as a positive dependency relationship in the interface association table;
[0014] The positive dependency relationships stored in the interface association table represent legitimate call relationships;
[0015] The multidimensional query method includes the following steps:
[0016] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0017] S22 extracts the initiating interface and calling interface from the transaction information and records the actual calling relationship;
[0018] When implementing intelligent monitoring, the system determines whether the actual call relationship is a legitimate one based on the API that initiated the call.
[0019] S31 When the calling initiating interface is an external interface of the UnionPay omnichannel system, the actual calling relationship is compared with the positive dependency relationship stored in the interface association table;
[0020] An alarm is triggered when the actual call relationship is not a legitimate call relationship.
[0021] Preferably, the method for constructing the interface association table further includes: S12 querying the external interfaces of the third-party system, sorting out the external interfaces of the UnionPay omnichannel system used by each external interface, and storing the call relationship between the external interface and the external interface of the UnionPay omnichannel system as a reverse dependency relationship in the interface association table;
[0022] The reverse dependency relationships stored in the interface association table are valid call relationships;
[0023] When the interface initiating the call is an external interface of a third-party system, S32 compares the actual call relationship with the reverse dependency relationship stored in the interface association table;
[0024] An alarm is triggered when the actual call relationship is not a legitimate call relationship.
[0025] Preferably, the method for constructing the interface association table further includes: S13 querying the business type of the third-party system, sorting out the external interfaces of the UnionPay omnichannel system that initiate the interface calls of each step of each business type, and storing the call relationship between the initiating interface of each step and the external interface of the UnionPay omnichannel system as a business dependency relationship in the interface association table;
[0026] The business dependency relationships stored in the interface association table represent legitimate call relationships.
[0027] Multidimensional query methods also include:
[0028] S23 extracts the business type, business steps, and call interfaces from the transaction information and records the actual call relationships;
[0029] When implementing intelligent monitoring, the legality of the actual call relationship is determined based on the business type:
[0030] When the initiator of the call is a third-party system, S33 compares the actual call relationship with the business dependency relationship stored in the interface association table. If the actual call relationship is not a valid call relationship, an alarm is triggered.
[0031] Preferably, the method for constructing the interface association table further includes: S14 querying the front-end port that provides the service, sorting out the system name that uses the front-end port, the initiating interface when using the front-end port, and the external interface of the UnionPay omnichannel system that the initiating interface calls, and storing the calling relationship of the front-end port, the system name that uses the front-end port, the initiating interface, and the external interface as the front-end port dependency relationship in the interface association table;
[0032] The interface association table stores the preceding port dependencies as valid call relationships;
[0033] Multidimensional query methods also include:
[0034] S24 extracts the front-end port, the system name using the port, the initiating interface, and the external interface from the transaction information, and records the actual call relationship.
[0035] When implementing intelligent monitoring, the validity of the actual call relationship is determined based on the front-end port:
[0036] S34 compares the actual call relationship with the front-end port dependency relationship stored in the interface association table. If the actual call relationship is not a valid call relationship, an alarm is triggered.
[0037] Front-end port impact analysis: By inputting a network front-end port or address, all upstream and downstream interfaces communicating through that front-end port can be traced, greatly facilitating fault location at the network layer.
[0038] Preferably, the alarm is triggered by pushing the monitored abnormal information to the operation and maintenance terminal via email, SMS, or other means.
[0039] On the other hand, this invention provides a system interface dependency management and monitoring device based on a relational table, comprising: a relational management module, a query analysis module, a monitoring engine module, and an alarm processing module, wherein...
[0040] The relationship management module is used to build and maintain an interface association table that stores legitimate call relationships;
[0041] The legal invocation relationships include: positive dependency relationships and negative dependency relationships;
[0042] The positive dependency relationship refers to the calling relationship between external interfaces and peripheral interfaces of third-party systems;
[0043] The reverse dependency relationship refers to the calling relationship between the external interface and the external interface of the UnionPay omnichannel system;
[0044] The query and analysis module is used to respond to query requests, collect real-time transaction information from the unified logs of the UnionPay omnichannel system, extract the call initiation interface and the call interface from the transaction information, and record the actual call relationship.
[0045] The monitoring engine module is used to compare the actual call relationship in real time with the positive or negative dependency relationship in the interface association table of the call initiating interface; when the actual call relationship is not a legitimate call relationship, an abnormal transaction signal is generated.
[0046] The alarm processing module is used to generate and send alarm information based on abnormal transaction signals.
[0047] Thirdly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the methods described above.
[0048] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the method described in any of the preceding claims.
[0049] Compared with the prior art, the present invention has the following significant advantages:
[0050] 1. Architecture Visualization: It clearly presents complex and implicit interface dependencies in a structured way, making the system architecture clear at a glance and greatly reducing the complexity of understanding and management.
[0051] 2. Accurate and efficient impact analysis: When a third-party system fails, the scope of the affected business of this system can be located in seconds, providing key basis for emergency decision-making and shortening the business recovery time.
[0052] 3. Enhanced monitoring: Moving beyond traditional performance monitoring to include logical relationship monitoring, enabling the discovery of more subtle anomalies and improving system stability and security.
[0053] 4. Low maintenance cost: All functions are implemented based on a single core data table. The structure is simple, easy to understand and maintain, and avoids the high costs associated with introducing complex and heavy components. Attached Figure Description
[0054] To better understand the above and other objects, features, advantages, and functions of the present invention, reference can be made to the embodiments shown in the accompanying drawings. The same reference numerals in the drawings refer to the same parts. Those skilled in the art should understand that the drawings are intended to schematically illustrate preferred embodiments of the invention and do not limit the scope of the invention in any way; the parts in the drawings are not drawn to scale.
[0055] Figure 1 This invention presents a call relationship diagram between an external interface and multiple peripheral interfaces for a system interface dependency management and monitoring method based on an association table.
[0056] Figure 2 This is a relationship diagram between an external interface and multiple external interfaces used by a system interface dependency management and monitoring method based on an association table according to the present invention.
[0057] Figure 3This invention presents a system interface dependency management and monitoring method based on an association table, which includes a call relationship diagram between a business type and the external interface that initiates the interface call for each step of the business type.
[0058] Figure 4 This invention provides a front-end port for a system interface dependency management and monitoring method based on an association table, along with a call relationship diagram of the system name, initiating interface, and external interface using the front-end port.
[0059] Figure 5 This is a block diagram of the module composition of a system interface dependency management and monitoring device based on an association table according to the present invention. Detailed Implementation
[0060] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.
[0061] The term "comprising" and its variations as used herein signify open inclusion, i.e., "including but not limited to". Unless otherwise stated, the term "or" means "and / or". The term "based on" means "at least partially based on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
[0062] In order to at least partially solve one or more of the above-mentioned problems and other potential problems, embodiments of this disclosure propose a system interface dependency management and monitoring method based on association tables.
[0063] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.
[0064] A method for managing and monitoring system interface dependencies based on a relational table includes: constructing an interface relational table, constructing a multidimensional query, and implementing intelligent monitoring.
[0065] The method for constructing the interface association table includes any one or a combination of the following steps:
[0066] S11 queries all external interfaces of the UnionPay omnichannel system, sorts out the external interfaces that each external interface calls to the third-party system, and stores the call relationship between the external interface and the external interface of the third-party system as a positive dependency relationship in the interface association table;
[0067] The positive dependency relationships stored in the interface association table represent legitimate call relationships;
[0068] like Figure 1 The diagram shown illustrates the call relationships between one external interface (1001 payment interface) of the UnionPay omnichannel system and multiple external interfaces. The simplest representation of the forward dependency relationships stored in the interface association table is shown in Table 1.
[0069] Initiate Interface Calling the interface 1001 Payment Interface Core Ledger MbsdCor_1000_2779 1001 Payment Interface Core positing MbsdCor_1300_0001 1001 Payment Interface Core query MbsdCor_1400_2710 1001 Payment Interface UnionPay payment 000401-00-00 1001 Payment Interface UnionPay inquiry 000401-12-00 1001 Payment Interface Customer payment 71 1001 Payment Interface Customer settlement inquiry 05 1001 Payment Interface Heilongjiang UnionPay payment agent (payOther) 1001 Payment Interface Heilongjiang UnionPay query queryOrderStatus 1001 Payment Interface Order result notification pay.b2b.000102
[0070] S12 queries the external interfaces of the third-party system, sorts out the external interfaces of the UnionPay omnichannel system used by each external interface in the external interface table, and stores the call relationship between the external interfaces and the external interfaces of the UnionPay omnichannel system as a reverse dependency relationship in the interface association table.
[0071] The reverse dependency relationships stored in the interface association table are valid call relationships;
[0072] like Figure 2 The diagram shows the call relationship between a third-party system's external interface (Core Current Account Basic Information Query MbsdCor_1400_0038) and its multiple external interfaces. The simplest representation of the reverse dependency relationship stored in the interface association table is shown in Table 2.
[0073] Initiate Interface Calling the interface Core Current Account Basic Information Inquiry MbsdCor_1400_0038 UnionPay Cardless Five Elements (trans.I0101) Core Current Account Basic Information Inquiry MbsdCor_1400_0038 Facial recognition payment activation trans.IFPR00401 Core Current Account Basic Information Inquiry MbsdCor_1400_0038 Face payment update trans.IFPR00402 Core Current Account Basic Information Inquiry MbsdCor_1400_0038 Order received trans.IOrderpayb2b000101 Core Current Account Basic Information Inquiry MbsdCor_1400_0038 UnionPay QuickPass Card Binding / Unbinding Notification trans.IYsfNoticeUnbindCard
[0074] S13 queries the business types of third-party systems, sorts out the external interfaces of the UnionPay omnichannel system that initiate each step of each business type, and stores the calling relationship between the initiation interface of each step and the external interface of the UnionPay omnichannel system as a business dependency relationship in the interface association table.
[0075] The business dependency relationships stored in the interface association table represent legitimate call relationships.
[0076] like Figure 3 The diagram shows the call relationship between a business type (unified payment) of a third-party system and the external interfaces of the UnionPay omnichannel system that initiate the calls to the interfaces of each step of the business type.
[0077] The simplest representation of business dependencies stored in the interface association table is shown in Table 3:
[0078] Business type Business steps External Interface Unified payment 5915 Instant Transfer Inquiry and Printing CupSettleR1 UnionPay R1 Clearing Unified payment 5915 Instant Transfer Inquiry and Printing NoCardAcctCalc Cardless Account Verification and Settlement Unified payment 2903 Direct Debit Agreement Payment Reversal backrev.I0002 UnionPay Asynchronous Notification Unified payment 2904 Callback Payment System Asynchronous Notification backrev.I0002 UnionPay Asynchronous Notification Unified payment 0801 Termination Notice trans.IC0002 Card Issuance and Collection Cancellation
[0079] S14 queries the front-end ports that provide services, sorts out the system names that use the front-end port, the initiating interface when using the front-end port, and the external interfaces of the UnionPay omnichannel system that the initiating interface calls, and stores the front-end port, the system name that uses the front-end port, the initiating interface, and the external interface call relationship as the front-end port dependency relationship in the interface association table.
[0080] The interface association table stores the preceding port dependencies as valid call relationships;
[0081] like Figure 4 The diagram shows the relationship between a front-end port (nginx-8084) that provides the query service and the system name, initiating interface, and external interface that use this front-end port.
[0082] The simplest representation of the front-end port dependency relationship stored in the interface association table is shown in Table 4:
[0083] Front Port Peripheral System Initiate Interface External interface nginx-8084 Cardless CUPNOCARD Five Elements 0101 Authentication trans.I1801 nginx-8084 Cardless CUPNOCARD Transaction Inquiry 3101 Authentication trans.I1801 nginx-8084 Cardless CUPNOCARD Check-out 4001 Sign out trans.INoCardSignOut nginx-8084 Cardless CUPNOCARD 4002 Check-in Sign in via trans.INoCardSignIn nginx-8084 Order payment Order transaction result notification pay.b2b.000102 Single payment via trans.I1001 nginx-8084 Order payment Order transaction result notification pay.b2b.000102 Order authorization interface trans.IOrderpayAuth nginx-8084 Order payment Order transaction result notification pay.b2b.000102 Order result notification trans.IOrderpayInform nginx-8084 UnionPay Four Elements Inquiry - 00-00 Authentication trans.I1801 nginx-8084 UnionPay Account opening verification - 85-02 Authentication trans.I1801 nginx-8084 UnionPay Return inquiry 000000-00-00 Single transaction query request trans.I1301 nginx-8084 UnionPay Return 000000-04-00 Collection and cancellation refund on behalf of trans.IR0001 nginx-8084 UnionPay Single collection 000000-11-03 Single transaction collection trans.IC0003 nginx-8084 UnionPay Bulk collection 000000-21-06 Bulk collection trans.IC0004 nginx-8084 UnionPay Single collection inquiry 000000-22-02 Bulk collection trans.IC0004 nginx-8084 UnionPay Cancel 000000-31-00 Collection and cancellation refund on behalf of trans.IR0001 nginx-8084 UnionPay Contract signed 000000-72-16 Collection and signing agreement trans.IC0001 nginx-8084 UnionPay Existing collection agreement 000000-72-17 Collection and signing agreement trans.IC0001 nginx-8084 UnionPay Contract termination 000000-74-05 Collection and signing agreement trans.IC0001 nginx-8084 UnionPay Receive contract signing SMS on behalf 000000-77-12 Send SMS trans.IC006 nginx-8084 UnionPay Single payment on behalf 000401-00-00 Single payment via trans.I1001 nginx-8084 UnionPay Payment inquiry 000401-12-00 Single payment via trans.I1001 nginx-8084 UnionPay Single collection inquiry 000501-00-00 Single transaction query request trans.I1301
[0084] The method for multidimensional query is as follows: In response to the query request, real-time transaction information is collected from the unified logs of the UnionPay omnichannel system. The actual call relationship is recorded according to the transaction information. The actual call relationship is compared with the legal call relationship stored in the interface association table. If the actual call relationship does not belong to the legal call relationship, an alarm is triggered.
[0085] Depending on the different construction methods of the interface association table mentioned above, the legal call relationships stored in the interface association table can be: forward dependency, reverse dependency, business dependency, front-end port dependency, or at least one or more combinations of these relationships.
[0086] In the API relationship table, the types and number of legitimate call relationships affect the dimensions of queries and the accuracy of monitoring. By adding and approving legitimate call relationships in the API relationship table, monitoring of business transactions can be increased or adjusted.
[0087] Example 1
[0088] As shown in Table 1, valid call relationships only include positive dependencies.
[0089] The multidimensional query method includes the following steps:
[0090] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0091] S22 extracts the initiation interface from the transaction information as the external interface of the UnionPay omnichannel system (1001 payment interface) and the calling interface as (customer settlement payment 71), and records the actual calling relationship (1001 payment interface, customer settlement payment 71).
[0092] Since the initiating interface of S31 is an external interface of the UnionPay omnichannel system, the record corresponding to the external interface (1001 payment interface) is retrieved in the interface association table;
[0093] The actual call relationship (1001 payment on behalf interface, customer settlement payment 71) is compared with the record corresponding to the external interface (1001 payment on behalf interface) retrieved from the interface association table. Since it is the same as the 6th record, it is determined that the current actual call relationship (1001 payment on behalf interface, customer settlement payment 71) is a legitimate call relationship.
[0094] Example 2
[0095] As shown in Table 1, taking the example of valid call relationships including only positive dependencies:
[0096] The multidimensional query method includes the following steps:
[0097] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0098] S22 extracts the initiation interface from the transaction information as the external interface of the third-party system (Core Current Account Basic Information Query MbsdCor_1400_0038), and the calling interface is (Face Payment Activation trans.IFPR00401). It records the actual calling relationship (Core Current Account Basic Information Query MbsdCor_1400_0038, Face Payment Activation trans.IFPR00401).
[0099] Since the S31 originates from a third-party system's external interface, it will not be searched in the interface association table, and therefore, no alarm will be triggered.
[0100] In this example, the interface relationship table only includes positive dependencies. For transaction information where the initiating interface is an external interface of a third-party system, the call relationship will not be queried or monitored. As a result, some transactions are not monitored, leading to a single query dimension and low monitoring accuracy. However, it is still possible to achieve the purpose of monitoring targeted transactions.
[0101] Example 3
[0102] Taking a valid call relationship that includes both forward and reverse dependencies as an example, the corresponding content of the interface association table includes the contents of both Table 1 and Table 2.
[0103] The multidimensional query method includes the following steps:
[0104] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0105] S22 extracts the initiation interface from the transaction information as the external interface of the third-party system (Core Current Account Basic Information Query MbsdCor_1400_0038), and the calling interface is (Face Payment Activation trans.IFPR00401). It records the actual calling relationship (Core Current Account Basic Information Query MbsdCor_1400_0038, Face Payment Activation trans.IFPR00401).
[0106] Since the initiating interface of S31 is an external interface of a third-party system, the record corresponding to the external interface (Core Current Account Basic Information Query MbsdCor_1400_0038) is retrieved in the interface association table;
[0107] The actual call relationship (Core Current Account Basic Information Query MbsdCor_1400_0038, Face Payment Activation trans.IFPR00401) is compared with the record corresponding to the external interface (Core Current Account Basic Information Query MbsdCor_1400_0038) retrieved from the interface association table. If it is the same as the second record, it is determined that the current actual call relationship (Core Current Account Basic Information Query MbsdCor_1400_0038, Face Payment Activation trans.IFPR00401) is a legitimate call relationship.
[0108] In this example, the interface relationship table includes both forward and reverse dependencies. For transaction information where the initiating interface is an external interface of the UnionPay omnichannel system or a third-party system's external interface, the call relationships will be queried and monitored. Compared to Examples 1 and 2, in this example, all transactions are under monitoring, resulting in multi-dimensional queries and improved monitoring accuracy.
[0109] Example 4
[0110] Taking a legitimate call relationship that also includes a business dependency relationship as an example, the corresponding content of the interface association table also includes the content of Table 3.
[0111] The multidimensional query method includes the following steps:
[0112] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0113] S22 extracts business type, business steps, and API calls from transaction information and records the actual call relationships.
[0114] Since the initiator of the call is a third-party system, in the interface association table, retrieve the business steps (801 cancellation notice) and its calling interface (trans.IC0002 card issuance side cancellation) corresponding to the business type (unified payment) and their records.
[0115] The actual call relationship (Unified Payment, 801 cancellation notification, trans.IC0002 card issuance side cancellation) is compared with the business steps and call interface records corresponding to the business type (Unified Payment) retrieved from the interface association table.
[0116] Similar to record 5, it is determined that the current actual call relationship (unified payment, 801 termination notice, trans.IC0002 card issuance side termination) is a legitimate call relationship.
[0117] In this example, the interface relationship table includes business dependencies. For transaction information containing business types, the call relationships are queried and monitored. All transactions are under monitoring, improving monitoring accuracy.
[0118] Example 5
[0119] Taking a valid call relationship that simultaneously includes forward dependency, reverse dependency, and front-end port dependency as an example, the corresponding content of the interface association table includes the contents of Table 1, Table 2, and Table 4.
[0120] The multidimensional query method includes the following steps:
[0121] S21 responds to query requests by collecting real-time transaction information from the system's unified logs;
[0122] The initiation interface extracted from the transaction information by S22 is the external interface of the UnionPay omnichannel system (1001 payment interface), and the calling interface is (UnionPay payment 000401-00-00). The first actual calling relationship is recorded (1001 payment interface, UnionPay payment 000401-00-00).
[0123] S23 also extracted the front-end port (nginx-8084) providing the service, the system name using the front-end port (UnionPay), the initiating interface (single query 000401-00-00), and the external interface (single payment trans.I1001) from the transaction information, and recorded the second actual call relationship (nginx-8084, UnionPay, single query 000401-00-00, single payment trans.I1001).
[0124] Since the initiating interface of S31 is the external interface of the UnionPay omnichannel system (1001 payment interface), the record (multiple records) corresponding to the external interface (1001 payment interface) is retrieved in the interface association table.
[0125] The first actual call relationship (1001 payment interface, UnionPay payment 000401-00-00) is compared with the record corresponding to the external interface (1001 payment interface) retrieved from the interface association table. It is the same as the 4th record in Table 1. Therefore, the current first actual call relationship (1001 payment interface, UnionPay payment 000401-00-00) is determined to be a legitimate call relationship.
[0126] S32 Since the front-end port for this transaction is (nginx-8084), retrieve the records (multiple records) corresponding to the front-end port (nginx-8084) in the interface association table.
[0127] The second actual call relationship (nginx-8084, UnionPay UNIONPAY, single query 000401-00-00, single payment trans.I1001) is compared with the record corresponding to the front-end port (nginx-8084) retrieved from the interface association table. It is the same as the 20th record in Table 4. Therefore, the current second actual call relationship (nginx-8084, UnionPay UNIONPAY, single query 000401-00-00, single payment trans.I1001) is determined to be a valid call relationship.
[0128] In S31 and S21 above, if either the first or second actual call relationship is not a legitimate call relationship, an alarm is triggered.
[0129] In this example, the interface relationship table includes forward dependencies, reverse dependencies, and front-end port dependencies. For any transaction record, dual monitoring is performed, ensuring that not only are all transactions monitored, but monitoring is also conducted from multiple dimensions, thus improving monitoring accuracy.
[0130] Example 6
[0131] like Figure 5 As shown, a system interface dependency management and monitoring device based on a relational table includes: a relational management module 1, a query analysis module 2, a monitoring engine module 3, and an alarm processing module 4.
[0132] Relationship Management Module 1 is used to build and maintain an interface association table that stores legitimate call relationships;
[0133] The legal invocation relationships include: positive dependency relationships and negative dependency relationships;
[0134] The positive dependency relationship refers to the calling relationship between external interfaces and peripheral interfaces of third-party systems;
[0135] The reverse dependency relationship refers to the calling relationship between the external interface and the external interface of the UnionPay omnichannel system;
[0136] Query and analysis module 2 is used to respond to query requests, collect real-time transaction information from the unified logs of the UnionPay omnichannel system, extract the call initiation interface and the call interface from the transaction information, and record the actual call relationship.
[0137] Monitoring engine module 3 is used to compare the actual call relationship in real time according to the positive or negative dependency relationship between the call initiating interface and the interface association table; when the actual call relationship is not a legitimate call relationship, an abnormal transaction signal is generated.
[0138] Alarm processing module 4 is used to generate and send alarm information based on abnormal transaction signals.
[0139] Referring to the above embodiments, forward dependencies, reverse dependencies, business dependencies, and front-end port dependencies can be used individually or in any combination, and will not be listed in detail here.
[0140] In the example above, separate interface association tables are provided based on different dependencies. In actual implementation, interface association tables corresponding to different dependencies can be merged into a single table. For items that do not overlap, preset values or empty values can be set. During querying, different keywords / items can be selected for retrieval based on different dependencies.
[0141] The key to this invention lies in digitizing interface dependency relationships and utilizing an interface association table to construct two core capabilities: multi-dimensional querying and intelligent monitoring. Beneficial effects include, but are not limited to:
[0142] 1. Monitor the legality of specific transactions by maintaining the interface relationship table;
[0143] 2. By establishing multiple dependency query methods and conducting anomaly monitoring based on relationship comparison.
Claims
1. A method for managing and monitoring system interface dependencies based on a relational table, characterized in that, include: Construct an interface relationship table, build multidimensional queries, and implement intelligent monitoring; among these, The method for constructing the interface association table includes the following steps: S11 queries all external interfaces of the UnionPay omnichannel system, sorts out the external interfaces that each external interface calls to the third-party system, and stores the call relationship between the external interface and the external interface of the third-party system as a positive dependency relationship in the interface association table; The positive dependency relationships stored in the interface association table represent legitimate call relationships; The multidimensional query method includes the following steps: S21 responds to query requests by collecting real-time transaction information from the system's unified logs; S22 extracts the initiating interface and calling interface from the transaction information and records the actual calling relationship; When implementing intelligent monitoring, the system determines whether the actual call relationship is a legitimate one based on the API that initiated the call. S31 When the calling initiating interface is an external interface of the UnionPay omnichannel system, the actual calling relationship is compared with the positive dependency relationship stored in the interface association table; An alarm is triggered when the actual call relationship is not a legitimate call relationship.
2. The system interface dependency management and monitoring method based on a relational table as described in claim 1, characterized in that, The method for constructing the interface association table includes the following steps: S12 queries the external interfaces of the third-party system, sorts out the external interfaces of the UnionPay omnichannel system used by each external interface, and stores the call relationship between the external interface and the external interface of the UnionPay omnichannel system as a reverse dependency relationship in the interface association table; The reverse dependency relationships stored in the interface association table are valid call relationships; When the interface initiating the call is an external interface of a third-party system, S32 compares the actual call relationship with the reverse dependency relationship stored in the interface association table; An alarm is triggered when the actual call relationship is not a legitimate call relationship.
3. The system interface dependency management and monitoring method based on a relational table as described in claim 1, characterized in that, Other methods for constructing interface association tables include: S13 queries the business types of third-party systems, sorts out the external interfaces of the UnionPay omnichannel system that initiate each step of each business type, and stores the calling relationship between the initiation interface of each step and the external interface of the UnionPay omnichannel system as a business dependency relationship in the interface association table. The business dependency relationships stored in the interface association table represent legitimate call relationships. Multidimensional query methods also include: S23 extracts the business type, business steps, and call interfaces from the transaction information and records the actual call relationships; When implementing intelligent monitoring, the legality of the actual call relationship is determined based on the business type: When the initiator of the call is a third-party system, S33 compares the actual call relationship with the business dependency relationship stored in the interface association table. If the actual call relationship is not a valid call relationship, an alarm is triggered.
4. The system interface dependency management and monitoring method based on a relational table as described in claim 2, characterized in that, Other methods for constructing interface association tables include: S13 queries the business types of third-party systems, sorts out the external interfaces of the UnionPay omnichannel system that initiate each step of each business type, and stores the calling relationship between the initiation interface of each step and the external interface of the UnionPay omnichannel system as a business dependency relationship in the interface association table. The business dependency relationships stored in the interface association table represent legitimate call relationships. Multidimensional query methods also include: S23 extracts the business type, business steps, and call interfaces from the transaction information and records the actual call relationships; When implementing intelligent monitoring, the legality of the actual call relationship is determined based on the business type: When the initiator of the call is a third-party system, S33 compares the actual call relationship with the business dependency relationship stored in the interface association table. If the actual call relationship is not a valid call relationship, an alarm is triggered.
5. A system interface dependency management and monitoring method based on an association table as described in any one of claims 1 to 4, characterized in that, Other methods for constructing interface association tables include: S14 queries the front-end ports that provide services, sorts out the system names that use the front-end port, the initiating interface when using the front-end port, and the external interfaces of the UnionPay omnichannel system that the initiating interface calls, and stores the front-end port, the system name that uses the front-end port, the initiating interface, and the external interface call relationship as the front-end port dependency relationship in the interface association table. The interface association table stores the preceding port dependencies as valid call relationships; Multidimensional query methods also include: S24 extracts the front-end port, the system name using the port, the initiating interface, and the external interface from the transaction information, and records the actual call relationship. When implementing intelligent monitoring, the validity of the actual call relationship is determined based on the front-end port: S34 compares the actual call relationship with the front-end port dependency relationship stored in the interface association table. If the actual call relationship is not a valid call relationship, an alarm is triggered.
6. A system interface dependency management and monitoring method based on an association table as described in any one of claims 1 to 4, characterized in that, The alarm is generated by pushing abnormal information detected by the system to the operation and maintenance terminal via email, SMS, or other means.
7. A system interface dependency management and monitoring method based on a relational table as described in claim 5, characterized in that, The alarm is generated by pushing abnormal information detected by the system to the operation and maintenance terminal via email, SMS, or other means.
8. A system interface dependency management and monitoring device based on a relational table, employing the method described in any one of claims 1 to 7, characterized in that, It includes: a relationship management module, a query analysis module, a monitoring engine module, and an alarm handling module. The relationship management module is used to build and maintain an interface association table that stores legitimate call relationships; The legal invocation relationships include: positive dependency relationships and negative dependency relationships; The positive dependency relationship refers to the calling relationship between external interfaces and peripheral interfaces of third-party systems; The reverse dependency relationship refers to the calling relationship between the external interface and the external interface of the UnionPay omnichannel system; The query and analysis module is used to respond to query requests, collect real-time transaction information from the unified logs of the UnionPay omnichannel system, extract the call initiation interface and the call interface from the transaction information, and record the actual call relationship. The monitoring engine module is used to compare the actual call relationship in real time with the positive or negative dependency relationship in the interface association table of the call initiating interface; when the actual call relationship is not a legitimate call relationship, an abnormal transaction signal is generated. The alarm processing module is used to generate and send alarm information based on abnormal transaction signals.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1 to 7.