Business processing method and device based on uniform interface

Abstract

The invention provides a business processing method and device based on a uniform interface, equipment, a medium and a program product, relates to the technical field of artificial intelligence and information security, and can be applied to the field of financial science and technology or other fields. The method comprises the following steps: receiving a first request sent by a unified interface client; identifying a source-end user and a destination-end system of the first request, wherein the uniform interface is docked with a plurality of back-end systems; converting the first request based on a service processing specification of a destination end system to obtain a second request matched with the destination end system; matching a source end user and a destination end system with the abnormal behavior record table; if the source end user is determined to be the user in the abnormal behavior record table through matching and the source end user adds the abnormal behavior information of the source end user to the second request according to the abnormal behavior record table to obtain a third request; and forwarding the third request to a destination end system.

Description

Technical Field

[0001] This invention relates to the fields of artificial intelligence and information security, and can be used in the fields of financial technology or other fields. More specifically, it relates to a business processing method, apparatus, equipment, medium and program product based on a unified interface. Background Technology

[0002] When businesses provide services, especially if they offer a wide variety of services and many are expanded gradually, insufficient planning during initial system development can lead to different systems providing services through their own clients. This requires users to interface with multiple systems. For example, corporate clients of banks often need to interface with multiple banking systems, and there may be additional business integrations on top of existing systems. Furthermore, while there is often overlap in the users of these multiple systems, their independence prevents the potential benefits of this user overlap from being effectively explored and utilized. Summary of the Invention

[0003] In view of the above problems, the present invention provides a business processing method, apparatus, device, medium and program product based on a unified interface.

[0004] A first aspect of this invention provides a business processing method based on a unified interface, wherein the unified interface is configured on a server. The method includes: receiving a first request sent through a unified interface client; identifying a source user and a destination system of the first request, wherein the unified interface interfaces with multiple backend systems, and the destination system is one of the multiple backend systems; converting the first request based on the business processing specifications of the destination system to obtain a second request adapted to the destination system; matching the source user and the destination system with an abnormal behavior record table, the abnormal behavior record table recording users and their abnormal behavior information who exhibit abnormal behavior during access to the multiple backend systems; if the source user is determined to be a user in the abnormal behavior record table through matching, appending the abnormal behavior information of the source user to the second request according to the abnormal behavior record table to obtain a third request; and forwarding the third request to the destination system.

[0005] According to an embodiment of the present invention, if the source user is determined to be a user in the abnormal behavior record table through matching and the abnormal behavior information of the source user does not originate from the source user's access to the destination system, the abnormal behavior information of the source user is appended to the second request to obtain the third request.

[0006] According to an embodiment of the present invention, the abnormal behavior record table is obtained by: acquiring traffic data of accessing multiple backend systems through the unified interface; using an abnormal behavior detection model to detect user behavior based on the traffic data, wherein the abnormal behavior detection model is a trained machine learning model; and when the abnormal behavior detection model detects that any user's behavior is abnormal, recording the user's information and its abnormal behavior information in the abnormal behavior record table.

[0007] According to an embodiment of the present invention, the user and their abnormal behavior information in the abnormal behavior record table come from feedback from the backend system.

[0008] According to an embodiment of the present invention, the feedback from the backend system to the user and abnormal behavior information in the abnormal behavior record table includes: receiving response data sent by the backend system and forwarded to the unified interface client after conversion; if the response data packet contains abnormal behavior information that meets preset conditions, extracting user information and corresponding abnormal behavior information from the response data and recording it in the abnormal behavior record table.

[0009] According to an embodiment of the present invention, the method further includes: receiving a first response sent by the destination system after processing the third request; converting the first response based on the business processing specifications of the destination system to obtain a second response adapted to the unified interface client format; and sending the second response to the unified interface client of the source user.

[0010] According to an embodiment of the present invention, the method further includes: acquiring traffic data of accessing multiple backend systems through the unified interface; and obtaining traffic distribution information of the multiple backend systems based on the traffic data.

[0011] According to an embodiment of the present invention, the traffic distribution information includes the distribution of traffic over time, and the method further includes: outputting a dynamic allocation strategy for the computing resources of the multiple back-end systems based on the traffic distribution information of the multiple back-end systems.

[0012] In a second aspect, the present invention provides a business processing device based on a unified interface, wherein the unified interface is set on a server, and the device includes a request forwarding module and an auxiliary security control module.

[0013] The request forwarding module is used to: receive a first request sent through a unified interface client; identify the source user and destination system of the first request, wherein the unified interface interfaces with multiple backend systems, and the destination system is one of the multiple backend systems; and convert the first request based on the business processing specifications of the destination system to obtain a second request adapted to the destination system.

[0014] The auxiliary security control module is used to: match the source user and the destination system with an abnormal behavior record table, which records users and their abnormal behavior information who exhibit abnormal behavior during access to multiple backend systems; if the source user is determined to be a user in the abnormal behavior record table through matching, the abnormal behavior information of the source user is appended to the second request to obtain a third request based on the abnormal behavior record table. The request forwarding module is further used to forward the third request to the destination system. In some embodiments, the auxiliary security control module is specifically used to append the abnormal behavior information of the source user to the second request to obtain a third request if the source user is determined to be a user in the abnormal behavior record table through matching and the abnormal behavior information of the source user does not originate from the source user's access to the destination system. According to an embodiment of the present invention, the device further includes a traffic monitoring module, and the abnormal behavior record table is obtained through traffic monitoring by the traffic monitoring module. The traffic monitoring module is specifically used to access traffic data from multiple backend systems through the unified interface; to perform user behavior detection based on the traffic data using an abnormal behavior detection model, which is a trained machine learning model; and to record the user's information and abnormal behavior information in the abnormal behavior record table when the abnormal behavior detection model detects any abnormal behavior of any user.

[0015] According to an embodiment of the present invention, the traffic monitoring module is further configured to: acquire traffic data of accessing multiple backend systems through the unified interface, and obtain traffic distribution information of the multiple backend systems based on the traffic data.

[0016] According to an embodiment of the present invention, the traffic distribution information includes the distribution of traffic over time, and correspondingly, the traffic monitoring module is further configured to: output a dynamic allocation strategy for the computing resources of the multiple back-end systems based on the traffic distribution information of the multiple back-end systems.

[0017] A third aspect of the present invention provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0018] A fourth aspect of the present invention also provides a computer-readable storage medium having a computer program or instructions stored thereon, wherein the computer program or instructions, when executed by a processor, implement the steps of the above-described method.

[0019] A fifth aspect of the present invention also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps of the above-described method. Attached Figure Description

[0020] The above-described features, other objects, and advantages of the present invention will become clearer from the following description of embodiments of the invention with reference to the accompanying drawings, in which:

[0021] Figure 1 The illustration schematically depicts an application scenario of a business processing method, apparatus, device, medium, and program product based on a unified interface according to embodiments of the present invention.

[0022] Figure 2 The illustration schematically depicts the system architecture of a service processing method, apparatus, device, medium, and program product based on a unified interface according to embodiments of the present invention;

[0023] Figure 3 A flowchart illustrating a service processing method based on a unified interface according to an embodiment of the present invention is shown schematically.

[0024] Figure 4 A flowchart illustrating a service processing method based on a unified interface according to another embodiment of the present invention is shown.

[0025] Figure 5 This illustration schematically shows a flowchart of the process for obtaining an abnormal behavior record table in a business processing method according to another embodiment of the present invention;

[0026] Figure 6 A supplementary flowchart illustrating a business processing method based on a unified interface according to another embodiment of the present invention is shown schematically;

[0027] Figure 7 This illustration schematically shows the interaction flow of an enterprise customer accessing multiple backend systems through a unified interface in one embodiment.

[0028] Figure 8 This illustration schematically shows the interaction flow of an enterprise customer accessing multiple backend systems through a unified interface in another embodiment.

[0029] Figure 9 A block diagram of a service processing apparatus based on a unified interface according to an embodiment of the present invention is illustrated; and

[0030] Figure 10 A block diagram schematically illustrates an electronic device suitable for implementing a service processing method based on a unified interface according to an embodiment of the present invention. Detailed Implementation

[0031] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the invention. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the invention for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concept of the invention.

[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0033] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0034] In the technical solution of this invention, the user information (including but not limited to user personal information, user image information, user device information) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0035] The embodiments of the present invention provide a business processing method, apparatus, device, medium, and program product based on a unified interface. This not only enables request conversion and forwarding by connecting to multiple backend systems through the unified interface, making it easier for users to obtain services from multiple backend systems, but also allows the appending of abnormal behavior information to the forwarding message when a user's behavior of accessing a backend system through the unified interface is determined to be abnormal. This allows the accessed backend system to combine the abnormal behavior information with its own access control policy to control the user's access permissions, thereby improving the efficiency of sharing security risk information and security control among multiple backend systems.

[0036] Figure 1 The illustration shows an application scenario diagram of a business processing method, apparatus, device, medium, and program product based on a unified interface according to embodiments of the present invention.

[0037] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal 101, a second terminal 102, a third terminal 103, a network 104, and a server (cluster) 105. Network 104 is a medium used to provide a communication link between the first terminal 101, the second terminal 102, the third terminal 103, and the server (cluster) 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0038] Server (cluster) 105 may include servers that provide various services. For example, server (cluster) 105 may be set up in a bank to provide various banking services for a banking system.

[0039] Users can use the first terminal 101, the second terminal 102, and the third terminal 103 to interact with the server (cluster) 105 via the network 104 to receive or send messages, etc. The first terminal 101, the second terminal 102, and the third terminal 103 can be personal user terminals (such as mobile phones and personal computers), or they can be client terminal systems that need to interact with the server (cluster) 105 to obtain corresponding services (such as enterprise systems used by corporate clients of banks).

[0040] Taking the interaction between an enterprise system and a bank system to obtain banking services as an example, the application scenario 100 is further explained as follows.

[0041] To meet their daily operational and financial management needs, corporate clients typically need to connect to multiple bank systems, such as API open platforms, specialized business systems, and bank-enterprise interconnection systems. They also have the need to add new business connections on top of the existing systems.

[0042] In some real-world scenarios, the application programming interfaces (APIs) provided by various banking systems exhibit significant heterogeneity issues, including but not limited to: differences in data interaction formats, security mechanisms, fragmented API access paths, and difficulties in subsequent maintenance.

[0043] Differences in data exchange formats, such as some systems using Extensible Markup Language (XML) and others using JavaScript Object Notation (JSON), require enterprises to develop and maintain parsing and encapsulation logic for multiple formats.

[0044] Differences in security mechanisms refer to the differences in standards and technical solutions adopted by various systems for interface communication security authentication and data encryption. For example, some systems rely on specific asymmetric encryption algorithms, some rely on digital certificates for authentication and data signing, while other systems may use different encryption algorithms or certificate systems, increasing the complexity and cost of enterprise system security adaptation.

[0045] Dispersed interface access paths refer to the fact that the service interfaces of each system are deployed on different network addresses, with different access paths and network configuration requirements. Enterprises need to configure and manage the request address and connection parameters of each destination system separately.

[0046] Post-upgrade maintenance difficulties refer to situations where, after upgrades and iterations, data centers need to be migrated or servers need to be upgraded, requiring enterprises to continuously update their firewall strategies.

[0047] The heterogeneous nature of these interfaces presents numerous technical obstacles for enterprises when integrating with multiple banking systems, including substantial development workload, high adaptation costs, high system coupling, and difficulties in subsequent maintenance. Enterprises are required to customize and develop dedicated integration modules for each system, resulting in a significant waste of resources and severely limiting the flexibility and efficiency of business expansion.

[0048] In light of this, the inventors conceived of using a front-end program to effectively shield the heterogeneity of the underlying banking system interfaces, perform message conversion and encryption / decryption, and forward requests to various back-end systems. Specifically, this front-end program could be as follows: Figure 2 The unified interface 210 and the unified interface client 220 are shown. Figure 2 The illustration schematically depicts a system architecture 200 for a service processing method, apparatus, device, medium, and program product based on a unified interface according to an embodiment of the present invention.

[0049] Combination Figure 1 and Figure 2 The unified interface 210 can be set in the server (cluster) 105, and all the backend systems are connected to the unified interface 210.

[0050] The unified interface client 220 can be set in the first terminal 101, the second terminal 102, or the third terminal 103.

[0051] Users can send requests to the unified interface 210 through the unified interface client 220 in the first terminal 101, the second terminal 102, and the third terminal 103. The unified interface 210 performs access conversion and forwarding to obtain corresponding services from multiple backend systems (such as system 1, system 2, system 3, and system 4).

[0052] As can be seen, the unified interface 210 and the unified interface client 220 can provide a unified interface call method to forward user requests to the corresponding backend systems. Furthermore, the unified interface 210 can also monitor transaction status after forwarding requests to various systems, simplifying enterprise integration processes and reducing integration complexity and maintenance costs. Moreover, the unified interface 210 can share abnormal behavior information of the same user among multiple backend systems to assist in security control. For example, before access forwarding, the unified interface 210 can attach abnormal behavior information of a monitored user to the message to be forwarded, thus informing the backend systems of previous abnormal behaviors of that user for reference in security control. Therefore, the unified interface 210 of this embodiment can at least effectively utilize the shared user behavior information of multiple backend systems to improve the security control efficiency and performance of each backend system in terms of security control.

[0053] It should be noted that the service processing method based on a unified interface provided in the embodiments of the present invention can generally be executed by server (cluster) 105. Correspondingly, the service processing apparatus, device, medium, and program product based on a unified interface provided in the embodiments of the present invention can generally be located in server (cluster) 105. The service processing method based on a unified interface provided in the embodiments of the present invention can also be executed by a server or server cluster that is different from server (cluster) 105 and capable of communicating with the first terminal 101, the second terminal 102, the third terminal 103, and / or server (cluster) 105. Correspondingly, the service processing apparatus, device, medium, and program product based on a unified interface provided in the embodiments of the present invention can also be located in a server or server cluster that is different from server (cluster) 105 and capable of communicating with the first terminal 101, the second terminal 102, the third terminal 103, and / or server (cluster) 105.

[0054] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0055] It should be noted that the business processing methods, devices, equipment, media, and program products based on a unified interface as defined in the embodiments of the present invention can be used in the field of fintech, or in any field other than fintech. The present invention does not limit the application field.

[0056] The following will be based on Figure 1 The scene described and Figure 2 The system architecture, through Figures 3-8 The business processing method based on a unified interface according to embodiments of the present invention will be described in detail.

[0057] Figure 3 A flowchart illustrating a service processing method 300 based on a unified interface according to an embodiment of the present invention is shown.

[0058] like Figure 3 As shown, the business processing method 300 includes operations S301 to S306.

[0059] In operation S301, the first request is received through the unified interface client 220.

[0060] In operation S302, the source user and destination system of the first request are identified, wherein the unified interface 210 connects to multiple backend systems, and the destination system is one of the multiple backend systems.

[0061] In operation S303, the first request is converted based on the service processing specifications of the destination system to obtain a second request adapted to the destination system. These service processing specifications include, but are not limited to, message format and encryption / decryption methods.

[0062] In operation S304, the source user and destination system of the first request are matched with the abnormal behavior record table, which is used to record users and their abnormal behavior information that have abnormal behavior in accessing multiple backend systems.

[0063] The abnormal behavior log table is generated by the unified interface 210 by summarizing and statistically analyzing information related to abnormal user behavior during access to multiple backend systems. This abnormal behavior information may include, but is not limited to: the type of abnormality (such as authentication failure or the presence of a network attack), the specific content of the abnormal behavior, information about the accessed backend system, or the risk level of the abnormal behavior.

[0064] The information in this abnormal behavior log table can come from the unified interface 210's monitoring of traffic data accessing multiple backend systems through this interface. For example, if an abnormal user behavior is detected, the specific details of the abnormal behavior can be recorded (such as the characteristics of the behavior, the type of abnormality, the time, and the backend systems accessed). Alternatively, the information in this abnormal behavior log table can also come from feedback from the backend systems, such as the backend systems reporting information related to abnormal user behavior they have detected, or extracting specific abnormal behavior information from the response data sent from the backend systems to the terminal.

[0065] Next, in operation S305, if the source user is determined to be a user in the abnormal behavior record table through matching, the abnormal behavior information of the source user is appended to the second request according to the abnormal behavior record table to obtain the third request.

[0066] Then, by operating S306, the third request is forwarded to the destination system.

[0067] In some embodiments, operation S305 can be as follows: as long as the user is recorded in the abnormal behavior log table, the abnormal behavior information of the user in the table can be appended to the request to be forwarded. This is particularly applicable when the unified interface actively monitors abnormal user behavior. For example, the unified interface 210 can monitor user behavior by accumulating the overall situation of user access to multiple backend systems. Therefore, when abnormal access behavior of a user is detected, the abnormal behavior information can be notified to each backend system in subsequent accesses. As another example, based on the user's access to each backend system, when the unified interface 210 detects that a user's access to a backend system is abnormal, the unified interface 210 can immediately notify the backend system, and can also inform the user of the abnormality in subsequent accesses to that backend system and other backend systems, so that each system can strengthen the detection and security control of the user's subsequent accesses.

[0068] In other practical situations, operation S305 can also be as follows: if the source user is identified through matching as a user in the abnormal behavior record table, and the abnormal behavior information of the source user does not originate from the source user's access to the destination system, then the abnormal behavior information of the source user is appended to the second request to obtain the third request. Specifically, when the user's abnormal behavior information is limited to access to a specific backend system, this abnormal behavior information can be only disclosed when the user accesses other backend systems, so that other backend systems can refer to it for security control. This situation is particularly applicable when a unified interface obtains detection and analysis results from backend systems.

[0069] For example, when the unified interface 210 learns from a backend system (such as system 1) that a user is behaving abnormally while accessing system 1, according to an embodiment of the present invention, information about this abnormal behavior can be collected through an exception information record table. This abnormal behavior information is then added to the request forwarded to system 2 when the user accesses another system (such as system 2) through the unified interface 210. This informs system 2 of the user's abnormal behavior while accessing system 1, allowing system 2 to use this abnormal behavior information to control user access permissions. In this scenario, the unified interface 210 does not need to attach the abnormal behavior information to the user's access to system 1, as system 1 already possesses this information, thus reducing information redundancy.

[0070] According to an embodiment of the present invention, when forwarding, the unified interface 210 adds some prior information that may be helpful for security control to the request, allowing each backend system to make a judgment based on its own security control policy. This enables security information sharing among multiple backend systems connected to the unified interface 210, thereby improving access security.

[0071] In one embodiment, the information in the abnormal behavior log table can come from feedback from the backend system. For example, when a user accesses any backend system (System 1, System 2, System 3, or System 4) through the unified interface 210, if the backend system determines that a user's behavior is abnormal based on its own security control policy, it will not only handle the issue using its own security processing program but also proactively report the relevant information to the unified interface 210. The unified interface 210 can then record the reported abnormal behavior information in the abnormal behavior log table. As another example, when a user accesses any backend system (System 1, System 2, System 3, or System 4) through the unified interface 210, the unified interface 210 can also be configured to detect whether the response data returned to the user by the backend system contains abnormal behavior information that meets preset conditions (such as a specific anomaly type or a risk level higher than a specific threshold). If so, the abnormal behavior information can be extracted and recorded in the abnormal behavior log table. A related embodiment can be found... Figure 4 Introduction.

[0072] Figure 4 A flowchart illustrating a service processing method 400 based on a unified interface according to another embodiment of the present invention is shown.

[0073] like Figure 4 As shown, in addition to operations S301 to S306, the business processing method 400 may also include operations S407 to S410.

[0074] For instructions on operations SS301 to S306, please refer to the previous text.

[0075] Next, in operation S407, the first response sent by the destination system after processing the third request is received. The first response is the response data to be converted and forwarded to the unified interface client 220.

[0076] In operation S408, the first response is converted based on the business processing specification of the destination system to obtain a second response adapted to the unified interface client 220 format.

[0077] In operation S409, the second response is sent to the unified interface client 220 of the aforementioned source user.

[0078] Furthermore, in operation S410, if the first response contains abnormal behavior information that meets preset conditions, the user and the corresponding abnormal behavior information can be extracted from the first response and recorded in the abnormal behavior record table. For example, it can detect whether the first response contains a field that indicates abnormal user behavior, and if such a field exists, check whether the value of the field belongs to a preset value range (e.g., different values ​​can represent the type or level of abnormal behavior). If so, the abnormal behavior information can be extracted and recorded in the abnormal behavior record table.

[0079] The preset conditions allow the unified interface 210 to extract only some abnormal behavior information, such as information on abnormal behaviors that are necessary for sharing with other backend systems for security assessment (such as information involving network attack behavior, or information involving impersonation behavior, etc.). On the one hand, this reduces the information redundancy in the abnormal behavior table, and on the other hand, it reduces unnecessary information extraction and recording by the unified interface 210, thus saving resources.

[0080] As can be seen, this embodiment of the invention can add an abnormal behavior detection function to the response messages sent to the user, based on the message conversion and forwarding process of the unified interface 210. If abnormal behavior information that meets preset conditions is detected, it is automatically recorded in the abnormal behavior record table, so that the unified interface 210 can share the abnormal information with other systems subsequently accessed by the user. In this way, the unified interface 210 can serve as a unified portal for communication between multiple backend systems and users, while also possessing a secure information sharing function, which helps to improve the security control capabilities of multiple backend systems.

[0081] In other embodiments, the information in the abnormal behavior log table can also be determined by the unified interface 210 after monitoring and tracking traffic data accessing multiple backend systems. Specifically, the unified interface 210 can monitor and analyze the traffic data passing through the unified interface 210 through the traffic monitoring module 213, and detect abnormal behavior information within it. A related embodiment can be referred to. Figure 5 The illustration.

[0082] Figure 5 The flowchart illustrating the process of obtaining the abnormal behavior record table in the business processing method of another embodiment of the present invention is shown.

[0083] like Figure 5 As shown, the process of obtaining the abnormal behavior record table in this embodiment includes operations S501 to S503.

[0084] When operating S501, traffic data for accessing multiple backend systems through unified interface 210 is obtained.

[0085] When operating S502, the abnormal behavior detection model is used to detect user behavior based on the above traffic data. The abnormal behavior detection model is a pre-trained machine learning model.

[0086] When operating S503, if the abnormal behavior detection model detects that any user's behavior is abnormal, the user's information and abnormal behavior information are recorded in the abnormal behavior record table.

[0087] As can be seen, the embodiments of the present invention can actively monitor and analyze the forwarded traffic data through the unified interface 210, extract and collect abnormal behavior information, and then share the collected abnormal behavior information among various backend systems to provide prior information for the permission policy control of each backend system.

[0088] According to other embodiments of the present invention, the traffic monitoring module 213 can also record the request volume, response time, and business processing results of each interface in real time. Based on the business processing results and the overall number of interactions, a comprehensive monitoring of business traffic can be achieved. A related embodiment can be referred to. Figure 6 .

[0089] Figure 6 A supplementary flowchart of a business processing method based on a unified interface according to another embodiment of the present invention is illustrated.

[0090] like Figure 6 As shown, the business processing method according to this embodiment may further include operations S601 to S603.

[0091] When operating S601, traffic data for accessing multiple backend systems through unified interface 210 is obtained.

[0092] In operation S602, based on the above traffic data, traffic distribution information of multiple backend systems is obtained.

[0093] In this way, the unified interface 210 can monitor traffic data accessing the backend system and obtain traffic distribution information, so as to understand or grasp the operating status of each system in a timely manner, help operation and maintenance and system optimization, and enable each system to effectively handle high traffic requests to provide a good user experience.

[0094] In one embodiment, the traffic distribution information includes the traffic distribution over time. Accordingly, in operation S603, a dynamic allocation strategy for the computing resources of multiple backend systems can be output based on the traffic distribution information of multiple backend systems. This dynamic allocation strategy can, for example, be the computing resources required by each backend system during different time periods of the day.

[0095] In one embodiment, the dynamic allocation strategy can be provided to the operations and maintenance personnel, who can then dynamically scale and configure each backend system according to the strategy.

[0096] In another embodiment, if a scheduling system that automatically scales up and down cluster computing resources is provided, the traffic distribution information of multiple backend systems or the dynamic allocation strategy of the computing resources of the multiple backend systems can be provided to the scheduling system, so that the scheduling system can dynamically allocate the cluster computing resources of each backend system.

[0097] As can be seen from the embodiments of the present invention, users do not need to pay attention to the message format conversion and network connectivity of each backend system when obtaining services, which reduces the complexity of system integration.

[0098] Next, let's combine... Figure 2 Taking an enterprise customer's existing request message format as XML and the message format of the destination system to be accessed as JSON as an example, through... Figure 7 and Figure 8 An example of the interaction process based on the unified interface 210 is provided.

[0099] The unified interface client 220 is set up in the enterprise system and may include a plug-in configuration module 221 and a security management module 222.

[0100] Plugin configuration module 221: Used to configure interface plugins for various backend systems for customer use; also used to achieve bidirectional format compatibility between the enterprise system and multiple heterogeneous backend systems. The enterprise system can continue to use the original message format for requests, and plugin configuration module 221 can call the preset format mapping rule library to complete the message format conversion according to the format of the backend system corresponding to the interface, such as converting XML format to JSON format; after verifying the signature of the returned content from the backend system, it completes the format conversion of the returned content according to the message format of the enterprise system and returns it to the enterprise system.

[0101] The security management module 222 is compatible with different encryption standards, enabling unified key management and encryption / decryption operations. It interacts with the enterprise system's configuration information to encrypt and sign request content, and decrypt and verify returned content. It obtains the corresponding key information based on the encryption algorithm required by the destination system. If the destination system requires private key information, the security management module obtains the enterprise's private key file and encrypts the request message.

[0102] The unified interface 210 is set on the bank server, such as server (cluster) 105, and may include a request forwarding module 211, an auxiliary security control module 212, and a traffic monitoring module 213.

[0103] The request forwarding module 211 is used to configure the backend system address according to the request type, and to route the request to the corresponding backend system address based on the request type. The unified interface 210 enables network connectivity between the backend systems; the enterprise system does not need to be enabled separately.

[0104] The auxiliary security control module 212, upon receiving an access request, matches the user information and destination system in the access request with a pre-collected abnormal behavior record table. If the matching determines that the user has exhibited abnormal behavior when accessing other systems, the module appends this abnormal behavior information to the access request to be forwarded, thereby notifying the destination system that the user's behavior is abnormal when accessing other systems, thus achieving the sharing of abnormal user behavior information.

[0105] The traffic monitoring module 213 records the request volume, response time, and number of transactions for each interface in real time. Based on the number of transactions, transaction results, and overall transaction volume data, it enables panoramic monitoring of business traffic and accurately tracks transaction fluctuation trends and anomalies. In some embodiments, the traffic monitoring module 213 also accurately records the number of requests and response time for each interface, helping to understand the system's operating status, ensuring the system can effectively handle high-traffic requests, and providing a good user experience. The traffic monitoring module 213 can be customized to configure key business information fields for each interface, such as transaction amount, to track transaction fluctuations and anomalies. After enterprise customers' systems are uniformly connected to this device, the bank can grasp the overall transaction situation of the enterprise, gain more timely insight into the enterprise's operating status, and use it for proactive marketing and risk control management.

[0106] The process of an enterprise system accessing a bank's backend system (i.e., the destination system) is as follows: Figure 7 As shown, the process can include: First, the enterprise system submits business messages using a unified interface client 220 developed with the unified interface development kit. The unified interface client 220 determines the message format and encryption method corresponding to the destination system, converts the message to obtain the message format corresponding to the destination system, and completes encryption. Then, the request is sent to the unified interface 210 developed on the server side using the unified interface development kit. Next, the unified interface 210 can record the request traffic of the interface, convert the format according to the request type, and forward it to the destination system.

[0107] The process by which the destination system returns the processing result (i.e., response data) to the enterprise system is as follows: Figure 8 As shown, the process may include: First, the destination system returns the result to the unified interface 210, allowing the unified interface 210 to update the status of the original request traffic. Then, the unified interface 210 converts the returned result into a new format and returns it to the enterprise system. Next, the enterprise system uses the unified interface client 220 to complete signature verification and decryption, and completes the interface format conversion to obtain the transaction result.

[0108] This invention enables multi-source interactive processing based on a unified interface. For example, banks can provide enterprises with a unified access service, significantly reducing the technical barriers and operational costs for connecting enterprises, decreasing integration and maintenance costs, reducing the amount of adaptation code, and greatly improving customer deployment time. Banks can also analyze traffic interaction and dynamically allocate computing resources for each service to improve service capabilities. Furthermore, banks can share abnormal access behavior of the same user across different systems, assisting each system in more efficient security control.

[0109] Based on the service processing methods based on unified interfaces described in the above embodiments, this invention also provides a service processing apparatus based on a unified interface. The following will be combined with... Figure 9 The business processing device is described in detail.

[0110] Figure 9 A block diagram of a service processing apparatus 500 based on a unified interface according to an embodiment of the present invention is shown schematically.

[0111] like Figure 9 As shown, the service processing device 500 includes a request forwarding module 211 and an auxiliary security control module 212. The service processing device 500 can be configured on a unified interface 210.

[0112] The request forwarding module 211 is used to: receive a first request sent through the unified interface client 220; identify the source user and destination system of the first request, wherein the unified interface 210 interfaces with multiple backend systems, and the destination system is one of the multiple backend systems; and convert the first request based on the business processing specifications of the destination system to obtain a second request adapted to the destination system. In one embodiment, the request forwarding module 211 can perform the operations S301 to S03 described above.

[0113] The auxiliary security control module 212 is used to: match the source user and destination system of the first request with an abnormal behavior record table, which records users and their abnormal behavior information who exhibit abnormal behavior during access to any backend system; if the source user is determined to be a user in the abnormal behavior record table through matching, the abnormal behavior information of the source user is appended to the second request according to the abnormal behavior record table to obtain the third request. In one embodiment, the auxiliary security control module 212 can perform the operations S304 and S305 described above.

[0114] The request forwarding module 211 is also used to forward the third request to the destination system. In one embodiment, the request forwarding module 211 can also perform the operation S306 described above.

[0115] According to other embodiments of the present invention, the service processing apparatus 500 may further include the traffic monitoring module 213 described above. The traffic monitoring module 213 may execute the operations S501 to S503 described above, or operations S601 to S603.

[0116] The business processing unit 500 can execute reference Figures 3-7 The business processing methods described above are detailed in the previous text and will not be repeated here.

[0117] According to embodiments of the present invention, any plurality of modules among the request forwarding module 211, the auxiliary security control module 212, and the traffic monitoring module 213 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of the present invention, at least one of the request forwarding module 211, the auxiliary security control module 212, and the traffic monitoring module 213 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the request forwarding module 211, the auxiliary security control module 212, and the traffic monitoring module 213 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0118] Figure 10 A block diagram schematically illustrates an electronic device suitable for implementing a service processing method based on a unified interface according to an embodiment of the present invention.

[0119] like Figure 10 As shown, an electronic device 900 according to an embodiment of the present invention includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0120] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 executes various operations of the method flow according to embodiments of the present invention by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also execute various operations of the method flow according to embodiments of the present invention by executing programs stored in said one or more memories.

[0121] According to an embodiment of the present invention, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output (I / O) interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0122] This invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of the invention.

[0123] According to embodiments of the present invention, a computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of the present invention, a computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0124] Embodiments of the present invention also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of the present invention.

[0125] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this invention. According to embodiments of the invention, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0126] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0127] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this embodiment of the invention. According to embodiments of the invention, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0128] According to embodiments of the present invention, program code for executing the computer programs provided in the embodiments of the present invention can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0129] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0130] Those skilled in the art will understand that the features described in the various embodiments of the present invention can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in the present invention. In particular, the features described in the various embodiments of the present invention can be combined and / or combined in various ways without departing from the spirit and teachings of the present invention. All such combinations and / or combinations fall within the scope of the present invention.

Claims

1. A business processing method based on a unified interface, wherein the unified interface is set on the server side, wherein, The method includes: Receive the first request sent by the client through the unified interface; Identify the source user and destination system of the first request, wherein the unified interface interfaces with multiple backend systems, and the destination system is one of the multiple backend systems; Based on the business processing specifications of the destination system, the first request is transformed to obtain a second request adapted to the destination system; The source user and the destination system are matched with an abnormal behavior record table, which is used to record users and their abnormal behavior information who have abnormal behavior in accessing multiple backend systems. If the source user is determined to be a user in the abnormal behavior record table through matching, the abnormal behavior information of the source user is appended to the second request according to the abnormal behavior record table to obtain the third request. The third request is forwarded to the destination system.

2. The method according to claim 1, wherein, If the source user is determined to be a user in the abnormal behavior record table through matching, and the abnormal behavior information of the source user does not originate from the source user's access to the destination system, the abnormal behavior information of the source user is appended to the second request to obtain the third request.

3. The method according to claim 1, wherein, The abnormal behavior record table was obtained in the following way: Obtain traffic data for accessing multiple backend systems through the unified interface; User behavior is detected based on the traffic data using an abnormal behavior detection model, which is a trained machine learning model. When the abnormal behavior detection model detects that any user's behavior is abnormal, it records the user's information and abnormal behavior information in the abnormal behavior record table.

4. The method according to claim 1, wherein, The user and their abnormal behavior information in the abnormal behavior record table comes from feedback from the backend system.

5. The method according to claim 4, wherein, The user and their abnormal behavior information in the abnormal behavior record table comes from feedback from the backend system, including: Receive response data sent by the backend system in the format to be converted and then forwarded to the unified interface client; If the response data packet contains abnormal behavior information that meets preset conditions, user information and corresponding abnormal behavior information are extracted from the response data and recorded in the abnormal behavior record table.

6. The method according to claim 1 or 5, wherein, The method further includes: Receive the first response sent by the destination system after processing the third request, wherein the first response is response data to be converted and forwarded to the unified interface client; Based on the business processing specifications of the destination system, the first response is converted to obtain a second response that is adapted to the unified interface client format; The second response is sent to the unified interface client of the source user.

7. The method according to claim 1, wherein, The method further includes: Obtain traffic data for accessing multiple backend systems through the unified interface; Based on the traffic data, traffic distribution information of multiple backend systems is obtained.

8. The method according to claim 7, wherein, The traffic distribution information includes the distribution of traffic over time, and the method further includes: Based on the traffic distribution information of the multiple backend systems, a dynamic allocation strategy for the computing resources of the multiple backend systems is output.

9. A service processing device based on a unified interface, wherein the unified interface is located on a server side, wherein, The device includes a request forwarding module and an auxiliary security control module, wherein: The request forwarding module is used for: Receive the first request sent by the client through the unified interface; Identify the source user and destination system of the first request, wherein the unified interface interfaces with multiple backend systems, and the destination system is one of the multiple backend systems; Based on the business processing specifications of the destination system, the first request is transformed to obtain a second request adapted to the destination system; The auxiliary safety control module is used for: The source user and the destination system are matched with an abnormal behavior record table, which is used to record users and their abnormal behavior information who have abnormal behavior in accessing multiple backend systems. If the source user is determined to be a user in the abnormal behavior record table through matching, the abnormal behavior information of the source user is appended to the second request according to the abnormal behavior record table to obtain the third request. The request forwarding module is further configured to forward the third request to the destination system.

10. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program or instructions stored thereon, wherein, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program or instructions, wherein, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 8.

Images