A business system and a business execution method

Abstract

The present specification provides a business system and a business execution method. The business system comprises a credit investigation sub-system corresponding to a credit investigation agency and a data source sub-system corresponding to each data source agency, a hub gateway module and a plurality of business application clusters are arranged in the credit investigation sub-system; the business application clusters comprise a common application cluster and an independent application cluster, the independent application cluster is connected to a target sub-system, and the common application cluster is connected to other sub-systems. The hub gateway module is used for: for a business request for a target business sent by a demander of credit investigation data, routing the business request to a business application cluster matched with the target business based on feature information corresponding to the business request; the business application cluster is used for: requesting original data from a data sub-system connected thereto according to the received business request, and generating credit investigation data based on the original data returned by the data sub-system, and sending the credit investigation data to the demander of the credit investigation data.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of computer technology, and more particularly to a business system and a business execution method. Background Technology

[0002] In related technologies, in order to accurately assess users' creditworthiness, financial institutions usually need to rely on credit reporting agencies to obtain multi-dimensional credit-related data. As an intermediary, credit reporting agencies connect with multiple third-party data source institutions from their own business systems to obtain various types of credit data such as users' credit records, repayment behavior, and performance history, and then process and integrate this data before feeding it back to financial institutions.

[0003] However, the existing credit reporting network architecture has significant stability vulnerabilities. Because credit reporting agencies rely on numerous data source institutions downstream, and these institutions vary in system stability and data transmission quality, when any data source institution experiences anomalies such as system failures, network interruptions, or data transmission errors, these anomalies propagate upwards to the corresponding business processing stages of the credit reporting agency, thus affecting the agency's overall operations. This can lead to the credit reporting agency being unable to respond normally to requests from financial institutions, resulting in business unavailability. Summary of the Invention

[0004] In view of the above, one or more embodiments of this specification provide the following technical solutions:

[0005] According to a first aspect of one or more embodiments of this specification, a business system is proposed, the business system comprising: a credit reporting subsystem corresponding to a credit reporting agency and a data source subsystem corresponding to each data source agency, wherein the credit reporting subsystem is provided with a central gateway module and multiple business application clusters;

[0006] The business application cluster includes a regular application cluster and an independent application cluster. The data source subsystem includes a target subsystem that meets preset filtering conditions and other subsystems besides the target subsystem. The independent application cluster is connected to the target subsystem, and the regular application cluster is connected to the other subsystems.

[0007] The central gateway module is used to: for business requests sent by the credit data requester for a target business, and based on the feature information corresponding to the business request, route the business request to a business application cluster that matches the target business;

[0008] Any business application cluster is used to: request raw data from the data source subsystem it interfaces with based on the received business request, generate credit data based on the raw data returned by the data source subsystem, and send the credit data to the party requesting the credit data.

[0009] According to a second aspect of one or more embodiments of the present specification, a business execution method is provided, which is applied to a credit investigation subsystem corresponding to a credit investigation institution, wherein the credit investigation subsystem is provided with a hub gateway module and a plurality of business application clusters, the business application clusters include a common application cluster and an independent application cluster, the independent application cluster is connected to a target subsystem satisfying a preset screening condition in a data source subsystem corresponding to each data source institution, and the common application cluster is connected to other subsystems except the target subsystem, and the method comprises:

[0010] receiving a business request for a target business sent by a demand side of credit investigation data;

[0011] routing, by the hub gateway module, the business request to a business application cluster matched with the target business based on feature information corresponding to the business request;

[0012] requesting, by the business application cluster, original data from a data source subsystem connected thereto according to the received business request, generating credit investigation data based on the original data returned by the data source subsystem, and sending the credit investigation data to the demand side of credit investigation data, so that the demand side of credit investigation data executes the target business according to the received credit investigation data.

[0013] According to a third aspect of one or more embodiments of the present specification, a business execution device is provided, which is applied to a credit investigation subsystem corresponding to a credit investigation institution, wherein the credit investigation subsystem is provided with a hub gateway module and a plurality of business application clusters, the business application clusters include a common application cluster and an independent application cluster, the independent application cluster is connected to a target subsystem satisfying a preset screening condition in a data source subsystem corresponding to each data source institution, and the common application cluster is connected to other subsystems except the target subsystem, and the device comprises:

[0014] a receiving module configured to receive a business request for a target business sent by a demand side of credit investigation data;

[0015] a gateway module configured to route the business request to a business application cluster matched with the target business based on feature information corresponding to the business request;

[0016] a sending module configured to request, by the business application cluster, original data from a data source subsystem connected thereto according to the received business request, generate credit investigation data based on the original data returned by the data source subsystem, and send the credit investigation data to the demand side of credit investigation data, so that the demand side of credit investigation data executes the target business according to the received credit investigation data.

[0017] According to a fourth aspect of one or more embodiments of this specification, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor implements the steps of the method described above by executing the executable instructions.

[0018] According to a fifth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method described above.

[0019] According to a sixth aspect of one or more embodiments of this specification, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the method described above.

[0020] As can be seen from the above embodiments, the technical solution proposed in this specification deploys different business application clusters within the credit reporting subsystem, allowing different clusters to interface with different data source subsystems. This architecture design achieves precise data isolation of business application clusters at the data source level: each business application cluster only interacts with its corresponding data source subsystem, and the data transmission paths and processing logic between clusters are completely independent. Under this architecture, when some data source subsystems experience anomalies, the impact of the anomaly will be strictly limited to the business application clusters that interface with them. Other business application clusters, because they have not established connections with the abnormal data source subsystems, will not have their data interaction and business operations interfered with. This mechanism significantly reduces the impact of anomalies in some data source institutions on the overall business of the credit reporting agency, improves the business stability and risk resistance of the credit reporting agency, and ensures the continuous and reliable output of credit reporting services. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the overall architecture of a business system provided in an exemplary embodiment;

[0022] Figure 2 This is a schematic diagram of the internal structure of a business system provided in an exemplary embodiment;

[0023] Figure 3 This is a schematic diagram of the internal execution logic of a business system provided in an exemplary embodiment;

[0024] Figure 4 This is a flowchart illustrating a business execution method provided in an exemplary embodiment;

[0025] Figure 5 This is a schematic diagram of the structure of a device provided in an exemplary embodiment;

[0026] Figure 6 This is a block diagram of a service execution apparatus provided in an exemplary embodiment. DETAILED DESCRIPTION

[0027] In order for those skilled in the art to better understand the technical solutions in the specification, the technical solutions in the specification will be clearly and completely described below in combination with the drawings in the embodiments of the specification. Obviously, the described embodiments are only some of the embodiments of the specification, not all. Based on the embodiments in the specification, all other embodiments obtained by those of ordinary skill in the art without creative labor should be within the protection scope of the specification.

[0028] In the field of financial services, financial institutions usually need to obtain multi-dimensional credit-related data from credit investigation agencies to accurately assess the credit status of users. Specifically, the information flow path is as follows: the financial institution as the data demander initiates a data query or credit evaluation request to the credit investigation agency; the credit investigation agency as an intermediate node receives the request, connects multiple third-party data source institutions based on its own business system, and obtains various credit data such as credit records, repayment behavior, and performance history of users; after processing and integration, the credit investigation agency feeds back the formed credit report, credit score, and other results to the financial institution, providing decision support for the credit approval, risk control, and other businesses of the financial institution.

[0029] However, when any data source institution is abnormal, the abnormality will be transmitted upward to the corresponding business processing link of the credit investigation agency, causing the credit investigation agency to be unable to normally respond to the request of the financial institution, resulting in unavailable business.

[0030] For example, the server of a data source institution fails, causing it to be unable to return the performance history data of a user within the 5-second response time limit set by the credit investigation agency. At this time, the thread of the credit investigation agency calling the data source is long-term occupied due to continuous waiting for response, and is unable to release resources to process other requests. With the passage of time, a large number of similar threads are accumulated, gradually consuming the thread pool resources of the system, so that the normal query request of the credit investigation agency to other data sources is also hindered due to lack of available threads, eventually causing the overall timeout failure of the batch credit evaluation request initiated by the financial institution, and the credit approval system is in a stagnant state.

[0031] For another example, the network transmission module of a data source institution fails, causing frequent packet loss and retransmission during data interaction. When a credit investigation institution initiates a user credit record query, the data source institution cannot complete data verification and return within the specified time due to network instability. The thread responsible for interfacing with the data source enters a retry loop because it has not received a result within the timeout, further occupying CPU and memory resources of the system. As the number of retries increases, thread occupancy continues to rise, and the core processing module of the credit investigation institution runs slowly due to excessive resource occupation, resulting in not only a failure to respond to new query requests in a timely manner, but also a serious delay in processing tasks received from financial institutions, ultimately causing overall blockage of the financial institution credit approval process.

[0032] Based on this, the present specification provides a business system, which deploys different business application clusters within a credit investigation institution, and interfaces different clusters with different data source institutions. The business application clusters are guaranteed to be accurately isolated in the data source dimension, avoiding the influence of abnormalities of some data source institutions on the overall business.

[0033] Figure 1 FIG. 1 is a schematic diagram of the overall architecture of a business system provided by an example embodiment. As shown in FIG. 1, the business system can include a credit investigation subsystem corresponding to a credit investigation institution, a data source subsystem corresponding to each data source institution, and a demander of credit investigation data. Figure 1

[0034] The demander of credit investigation data can be a financial subsystem corresponding to a financial institution, such as a business processing system constructed by a bank, a securities company, an insurance company, or other financial institutions, for providing financial services such as deposit and withdrawal, money transfer, credit issuance, securities trading, insurance, and claims processing.

[0035] The credit investigation subsystem can be a specialized platform operated by a credit investigation institution, for integrating, verifying, analyzing, and feedback processing of related business requests and multi-channel credit data (such as credit records and default information), and forming standardized credit evaluation results.

[0036] The data source subsystem can be a data platform of a data source institution such as an e-commerce platform, a social network, a communication operator, a government department, or the like, for storing cross-domain data such as user consumption behavior records, social interaction data, communication trajectories and positioning, enterprise business information, credit investigation data, and tax records.

[0037] The credit investigation subsystem can interface with multiple financial subsystems and multiple data source subsystems, thereby receiving business requests from different financial subsystems and obtaining required data from different data source subsystems.

[0038] Further, the present specification also provides a schematic diagram of the internal structure of a business system, as shown in FIG. 2.​Figure 2 as shown.

[0039] Figure 2 Fig. 1 is a schematic diagram of an internal structure of a business system according to an example embodiment.

[0040] The credit investigation subsystem is provided with a hub gateway module and a plurality of business application clusters, which can include common application clusters and independent application clusters, and the independent application clusters and the common clusters respectively process different businesses.

[0041] Further, the data source subsystems can include target subsystems satisfying preset screening conditions and other subsystems except the target subsystems, and the independent application clusters are connected to the target subsystems, and the other subsystems are connected to the common application clusters.

[0042] In actual applications, there are a large number of data source institutions, and the data stored by different data source institutions or the businesses involved are also different, so the target subsystems and the other subsystems can be divided based on different screening conditions. The screening conditions can include one or more of the following: the data stored by the data source subsystems are data required for a specified business (such as personal consumer credit business, enterprise supply chain financing business, etc.), the data stored by the data source subsystems are data provided by a specified data provider (such as a commercial bank, a leading consumer finance company, etc.), the intended transaction amount of the business involved by the data source subsystems is greater than a preset transaction amount, and the intended transaction volume of the business involved by the data source subsystems is greater than a preset transaction volume.

[0043] For example, in the consumer finance scenario, if the screening condition is that the data stored by the data source subsystems are data required for personal consumer credit business, enterprise supply chain financing business, etc., then the data source subsystems storing personal credit card repayment records, consumption installment performance, and supply chain upstream and downstream enterprise accounts receivable data can be divided into target subsystems.

[0044] If the screening condition is that the data stored by the data source subsystems are data provided by a target commercial bank, a leading consumer finance company, etc., then the data source subsystems connected to the target commercial bank, the leading consumer finance company, etc. can be listed as target subsystems, and the remaining data source subsystems connected to local small loan companies and regional financial institutions can be listed as other subsystems.

[0045] If the screening condition is "the proposed transaction amount of the business involved by the data source subsystem is greater than 500,000 per transaction", the data source subsystems storing data related to personal housing mortgage loans (usually more than 1 million per transaction) and large consumption installment (such as more than 500,000 per transaction) can be divided into target subsystems, while the data source subsystems storing small consumption loans (a few thousand per transaction) and daily credit card records (usually less than 10,000 per transaction) are divided into other subsystems.

[0046] If the screening condition is "the proposed transaction volume of the business involved by the data source subsystem is greater than the preset transaction volume (such as 1,000 per day)", the data source subsystems interfacing with mainstream e-commerce platform consumption credit business (daily transaction volume can reach tens of thousands) and large-scale chain supermarket installment business (daily transaction volume exceeds 5,000) can be listed as target subsystems, while the rest of the small brand installment business (less than 200 per day) and individual merchant small credit (about 500 per day) are listed as other subsystems.

[0047] Of course, the above is only an exemplary enumeration of several screening conditions, and other screening conditions can also be included in actual application, which is not limited in the present specification.

[0048] It should be noted that when there are two or more screening conditions, a comprehensive priority score can be calculated based on the two screening conditions, and different screening conditions can be assigned corresponding weights to determine the priority ranking of each data source subsystem. For example, when "involving specified business (weight 60%) " and "proposed transaction amount greater than 500,000 (weight 40%) " are used as screening conditions, if X subsystem meets the specified business and the transaction amount is 60,000, Y subsystem meets the specified business but the transaction amount is 30,000, and Z subsystem does not meet the specified business but the transaction amount is 80,000, the comprehensive score of X can be calculated as 60% x 1 + 40% x (60 / 50) = 1.48, the score of Y is 60% x 1 + 40% x 0 = 0.6, and the score of Z is 60% x 0 + 40% x (80 / 50) = 0.64. Finally, according to the score ranking, X is determined as the core target subsystem, Z is the second, and Y is the ordinary target subsystem, so as to realize differentiated resource allocation and risk control.

[0049] Further, the above target subsystems can include multiple ones, i.e. when multiple subsystems meet the preset screening condition, all subsystems that meet the condition are included in the target subsystem category, and different target subsystems interface with different independent application clusters. For example, in the personal consumption credit business scenario, if the screening condition is "data source subsystems storing personal credit card repayment records and online lending overdue information", then A subsystem which stores both types of data and B subsystem which only stores personal credit card repayment records but is verified to fully meet the business needs can be divided into target subsystems and provide data support for the business together.

[0050] Of course, in addition to the target subsystem and other subsystems, other types of subsystems can also be divided, for example, each subsystem can be classified according to the above screening conditions, and taking the above priority score as an example, the data source subsystem with a score below 0.6 is classified as other subsystems; the data source subsystem with a score of 0.6-0.8 is classified as an alternative subsystem; and the data source subsystem with a score above 0.8 is classified as a target subsystem.

[0051] In this way, the credit investigation system can perform different businesses through the business application cluster connected with different data source subsystems, that is, through the independent application cluster connected with the target subsystem that meets the preset screening conditions, the high-preservation business with higher requirements for data stability is executed, and through the ordinary application cluster connected with other subsystems, the ordinary business with lower requirements for data stability is executed.

[0052] In the process of deploying each business application cluster in the credit investigation subsystem content part, the credit investigation subsystem can first configure and deploy the ordinary application cluster, and when a target subsystem that needs to be connected appears, the configuration data (such as database connection parameters, server resource allocation information, network communication protocol settings, etc.) of the ordinary application cluster can be obtained, and based on the configuration data, the independent application cluster connected with the target subsystem is deployed. Thus, the configuration data between different business application clusters is reused, and resources are saved. This way avoids the need to reconfigure a large number of tedious basic configurations for each newly connected target subsystem, reduces the human input and possible errors in the configuration process, shortens the deployment period, improves the overall deployment efficiency and resource utilization, and also facilitates the subsequent unified management and maintenance of each application cluster.

[0053] Further, each business application cluster in the credit investigation subsystem is provided with a plurality of business applications, and the same business applications are provided in different business application clusters. In addition, the same business applications in different business application clusters share the same local database, and different business applications in the same business application cluster correspond to different local databases. The local database is used to store operation and maintenance data (such as application start / stop time, resource occupancy, error logs, version update records, performance monitoring indicators, etc.) of the corresponding business applications and interaction data (such as user operation records, interface call logs, data transmission records, business request parameters and return results, task execution status, etc.) generated during the execution of the business process. This database design not only realizes the unified management and reuse of core data through the shared database of the same business application, but also guarantees the isolation and security of each application data through the independent database of different business applications. At the same time, the classified storage of operation and maintenance data and interaction data can provide accurate data support for fault troubleshooting, performance optimization, version iteration, and other maintenance work of the business applications.

[0054] Specifically, the business applications set in the business application cluster can include: a branch gateway module, a request processing module and a data processing module; each business application cluster is connected with a corresponding data source subsystem through a respective branch gateway module.

[0055] The request processing module is configured to process the service request routed by the hub gateway module and send the processed service request to the branch gateway module.

[0056] For example, the integrity and validity of the user information carried in the service request can be verified, the query authority of the financial subsystem can be checked for compliance; the service request can be encrypted and desensitized to shield the plaintext transmission of user sensitive information and only retain the necessary identity verification field; the user authorization record can be associated to check whether the user has signed the credit information query authorization document to ensure that the query behavior obtains the explicit consent of the user; a unique query serial number can be generated for tracking the processing status of the request throughout the process, including data calling, result returning, log retention, etc.; abnormal query behavior can be intercepted, such as multiple queries of the same user information in a short period of time, high-frequency queries on non-working days, etc., triggering a risk warning mechanism and suspending processing.

[0057] The branch gateway module is configured to forward the processed service request to the data source subsystem connected therewith, and receive the raw data returned by the data source subsystem and send the raw data to the data processing module.

[0058] The data processing module is configured to process the raw data to obtain the credit data.

[0059] For example, the duplicate information in the raw data can be processed to remove redundant data; the fields with inconsistent formats can be standardized to ensure consistent data formats; missing key information can be reasonably completed or marked; obviously abnormal data (such as income values exceeding a reasonable range, logically inconsistent loan records) can be checked and corrected; at the same time, the data can be classified and integrated according to the credit business requirements, such as classifying the credit records, repayment conditions and overdue information of the customer according to specific dimensions, to finally form credit data that meets the credit standards and analysis requirements.

[0060] Further, the present specification also provides an internal execution logic diagram of a business system in the process of actually executing a business, as shown in Figure 3 .

[0061] Figure 3 is an internal execution logic diagram of a business system provided by an exemplary embodiment, comprising the following steps:

[0062] S300: The data demander sends a service request for a target service.

[0063] In the present specification, the target service can include: deposit / withdrawal service, transfer service, credit card application service, loan approval service, account information modification service, financial product purchase service, etc. The service processing request can carry user information such as user bank card ID, identity ID, name, mobile phone number, etc. These information are the key basis for identifying user identity and ensuring service attribution; in addition, it can also carry other information such as service type identification (such as withdrawal, deposit, transfer, etc.), query content identification (such as data table primary key, data number, key field, etc.), transaction amount, operation time, device number, etc. The present specification does not make specific limitation on this.

[0064] The timing of sending the service request by the data demander can be various, for example, when the user initiates a transfer operation on the bank APP, the bank as the data demander will send a service request to the credit investigation system in time, carrying the user's bank card ID, transfer amount, operation time, etc. Information to verify the user's account status and transfer authority; after the user submits the credit card application form, the card issuing institution will send a query request containing user identity ID, income proof number, etc. Information within 24 hours to verify its credit record through the credit investigation system; when the loan approval enters the final audit link, the financial institution will trigger the service request to call the user's repayment record data in the past 6 months. At this time, the request will carry key information such as loan application number and proposed loan amount; and for the financial product purchase service, some institutions will send a service request after the user completes the risk assessment test to confirm whether the user has bad credit records and ensure the compliance of the financial transaction.

[0065] S302: The hub gateway module of the credit investigation subsystem routes the service request to the service application cluster matched with the target service based on the feature information corresponding to the service request.

[0066] After receiving the service request, the hub gateway module of the credit investigation subsystem can route the service request to the service application cluster matched with the target service based on the feature information corresponding to the service request.

[0067] Among them, the feature information corresponding to the service request corresponds to the screening conditions of the target application cluster and the data source subsystem connected thereto. These feature information can include: service type identification, user-associated data provider information, transaction amount, transaction volume, data query urgency, etc.

[0068] For example, when the characteristic information of the service request is that the service type identifier is "credit card application service", the hub network management will route the request to the application cluster of the target subsystem which interfaces with the storage of credit card application required credit data according to the characteristic; if the characteristic information shows that the user's main transaction data comes from a designated large commercial bank, the request will be routed to the application cluster which interfaces with the data source subsystem of the commercial bank; when the transaction amount characteristic is more than 100 million per transaction, the hub network management will route it to the target application cluster which processes high-amount transaction services, and the data source subsystem which interfaces with the cluster meets the screening condition of "proposed transaction amount greater than preset transaction amount"; when the transaction volume characteristic is more than 20 financial product purchases per day, the request will be routed to the application cluster which adapts to high-frequency transactions, and the data source subsystem which interfaces with the cluster meets the screening requirement of "proposed transaction volume greater than preset transaction volume".

[0069] S304: The service application cluster of the credit investigation subsystem requests original data from the data source subsystem which interfaces with it according to the received service request;

[0070] S306: The service application cluster generates credit investigation data based on the original data returned by the data source subsystem.

[0071] For any service application cluster, after receiving a service request, the service application cluster can request original data from the data source subsystem which interfaces with it according to the received service request.

[0072] In this process, the request processing module in the service application cluster can first process the service request and send the processed service request to the branch gateway module in the service application cluster, and then the branch gateway forwards the processed service request to the data source subsystem which interfaces with it.

[0073] After receiving the service request, the data source subsystem can determine the original data required for executing the target service (such as the user's credit repayment records in the past 5 years, credit card overdraft frequency, asset mortgage information, loan overdue days, etc.) according to the user identity ID, service type identifier, query content identifier and other information carried in the service request, and then return the original data to the credit investigation subsystem through the branch gateway module.

[0074] The branch gateway module can first send the original data to the data processing module in the service application cluster, and then the data processing module processes the original data. For example, for credit approval services, the data processing module will eliminate duplicate repayment records, verify the authenticity of asset mortgage information, and convert overdue days into credit deduction indicators, finally generating credit investigation data including user credit score, risk level, and historical default details, providing standardized reference for the decision of financial institutions.

[0075] S308: The business application cluster sends credit data to the central gateway;

[0076] S310: The central gateway sends credit data to the party requesting the credit data.

[0077] After obtaining the credit data, the business application cluster can send the credit data to the central gateway, and then send the credit data to the credit data requester through the central gateway.

[0078] Once credit data is received, those who need it can use it to execute their target business. For example, after receiving credit data related to a user's credit card application, a bank will approve the application and set a reasonable credit limit based on the data if the user has a high credit score and no history of default. Microfinance companies will determine whether to issue a loan, as well as the loan interest rate and term, based on the user's repayment ability and risk level assessed in the credit data. Wealth management platforms will refer to credit data to determine the user's risk tolerance and recommend suitable wealth management products, ensuring that business operations meet business requirements while effectively controlling risks.

[0079] Furthermore, in practical applications, it is often necessary to maintain business systems to ensure stable operation, improve business processing efficiency, and promptly fix potential vulnerabilities. During this process, the credit reporting subsystem can receive maintenance requests for target applications within a specified application cluster, and based on the maintenance requests, determine the local database corresponding to the target application as the target database. Then, it can read the maintenance data and interaction data of the target application within the specified application cluster from the target database, and perform maintenance on the target application within the specified application cluster based on the read maintenance data and interaction data.

[0080] by Figure 2 Taking application module b1 as an example, when maintenance is required for this application module, the maintenance request carries the cluster identifier "Cluster 1" and the corresponding module identifier "Module a1". Upon receiving this request, the credit scoring subsystem quickly locates the local database bound to "Module a1" within "Cluster 1". Subsequently, it reads maintenance data from this target database, such as the operating logs of module a1 for the past 30 days, the frequency of error codes, and peak resource usage. Simultaneously, it extracts interaction data, including interface call records between module a1 and the data source subsystem, data transmission latency, and collaborative operation records with other modules within the cluster. Based on this data, maintenance personnel can analyze whether module a1 has memory leaks, interface response timeouts, or collaborative logic vulnerabilities with other modules. They can then perform targeted code optimization, interface parameter adjustments, or collaborative process refactoring to complete the maintenance work for the target application.

[0081] In the present specification, the demand side receiving credit data can be a financial subsystem corresponding to a financial institution, and the service request can include a query request for historical positioning information of a user.

[0082] In the process of performing the service, the financial subsystem can obtain a service processing request for a target service sent by the user through a service device, determine geographical location information corresponding to the location of the service device, and send the query request to the credit subsystem. Then, the credit subsystem routes the query request to a service application cluster connected thereto, to query the historical positioning information of the user read by the target application through the service application cluster, and returns the historical positioning information to the financial subsystem (the target application is provided by a data source subsystem corresponding to the service application cluster).

[0083] Then, the financial subsystem can determine whether the target service has a risk according to the geographical location information and the historical positioning information.

[0084] For example, the financial subsystem can determine the difference between the geographical location information and the historical positioning information, and determine whether the difference is greater than a preset distance difference. If yes, it indicates that the user's current operation service location deviates too much from the past frequently used location, and there is a risk of account theft or non-personal operation. Therefore, the financial subsystem can trigger a risk warning mechanism, such as requiring the user to perform secondary identity verification (such as face recognition, SMS verification code verification, etc.), or temporarily freezing the processing flow of the service. If not, it indicates that the user's current operation location is consistent with the historical behavior habit, and the risk of the target service is low. The financial subsystem can continue to process the service according to the normal process.

[0085] Based on the above service system, the present specification also provides a service execution method applied to a credit subsystem, as shown in Figure 4

[0086] Figure 4 A service execution method provided for an exemplary embodiment includes the following steps:

[0087] S400: receiving a service request for a target service sent by a demand side receiving credit data;

[0088] S402: routing the service request to a service application cluster matched with the target service through the hub gateway module based on feature information corresponding to the service request;

[0089] ​S404: Through this business application cluster, raw data is requested from the data source subsystem it is connected to based on the received business request, and credit data is generated based on the raw data returned by the data source subsystem. The credit data is then sent to the credit data requester so that the credit data requester can execute the target business based on the received credit data.

[0090] The credit reporting subsystem includes a central gateway module and multiple business application clusters. The business application clusters include ordinary application clusters and independent application clusters. The independent application clusters are connected to the target subsystems that meet the preset screening conditions in the data source subsystems corresponding to each data source institution. The ordinary application clusters are connected to other subsystems other than the target subsystems.

[0091] As can be seen from the above embodiments, this specification adds new business links by deploying a business application cluster, and uses the same set of code for independent deployment while sharing a database, which not only ensures code reusability but also allows for flexible expansion. By adding routing rules based on traffic type to the gateway application, a traffic loop is achieved, effectively avoiding traffic interference between different clusters. When a data source institution experiences an anomaly, only the ordinary cluster is affected, while the high-security cluster can still provide services to the relevant institutions normally, greatly improving the system's disaster recovery capabilities. Furthermore, under normal circumstances, the high-security cluster strictly controls access, significantly reducing the number of dependent downstream data source institutions from hundreds to just a few, significantly lowering the probability of downstream institution anomalies and effectively improving the stability of the high-security cluster.

[0092] Figure 5 This is a schematic structural diagram of a device provided in an exemplary embodiment. For example... Figure 5 As shown, device 500 mainly consists of a communication interface 502, a user interface 504, a processor 506, and a data storage 508. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 510. The communication interface 502 enables device 500 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 502 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 502 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 502 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 502 may also include multiple physical communication interfaces, such as Wi-Fi interfaces, Bluetooth interfaces, and wide-area wireless interfaces.

[0093] User interface 504 includes receiving user input and providing output to the user. Therefore, user interface 504 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 504 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 504 may include software, circuitry, or other forms of logic capable of transmitting and receiving data from external user input / output devices. Additionally or alternatively, device 500 may support remote access from other devices via communication interface 502 or another physical interface (not shown). User interface 504 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 504 may also be configured as a display device for rendering or displaying text fragments.

[0094] Processor 506 may contain one or more general-purpose processors and / or special-purpose processors.

[0095] Data storage 508 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 506. Data storage 508 may include removable and non-removable components.

[0096] Processor 506 is capable of executing program instructions 518 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 508 to perform the various functions described herein. Data storage 508 may contain a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 500, enable device 500 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 518 by processor 506 may result in processor 506 using data 512.

[0097] For example, program instructions 518 may include an operating system 522 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 500 and one or more applications 520 (e.g., a browser, social application, or game application). Similarly, data 512 may include operating system data 516 and application data 514. Operating system data 516 is primarily accessible to the operating system 522, while application data 514 is primarily accessible to one or more applications 520. Application data 514 may reside in a file system visible or hidden from the user of device 500.

[0098] The application programs 520 can communicate with the operating system 522 through one or more application programming interfaces (APIs). These APIs can facilitate the application programs 520 reading and / or writing to the application data 514, communicating or receiving information via the communication interface 502, receiving or displaying information on the user interface 504, and so on.

[0099] In some terminology, the application programs 520 can be referred to simply as "apps." In addition, the application programs 520 can be downloaded to the device 500 through one or more online application stores or application markets. However, the application programs can also be installed on the device 500 through other means, such as through a web browser or a physical interface on the device 500 (e.g., a USB port).

[0100] Referring to Figure 6 , the business execution apparatus can be applied to a device as shown in Figure 5 , to implement the technical solutions of the present specification. Wherein, the business execution apparatus can include:

[0101] The receiving module 600 is configured to receive a business request for a target business sent by a demand side of credit investigation data;

[0102] The gateway module 602 is configured to route the business request to a business application cluster matched with the target business based on feature information corresponding to the business request;

[0103] The sending module 604 is configured to request original data from a data source subsystem interfaced therewith according to the received business request through the business application cluster, generate credit investigation data based on the original data returned by the data source subsystem, and send the credit investigation data to the demand side of credit investigation data, so that the demand side of credit investigation data executes the target business according to the received credit investigation data.

[0104] Optionally, a plurality of business applications are arranged in each business application cluster, and the business applications arranged in different business application clusters are the same;

[0105] The same business applications in different business application clusters share a same local database, and different business applications in a same business application cluster correspond to different local databases, and the local database is configured to store operation and maintenance data of the corresponding business application and interaction data generated in the execution of the business process.

[0106] Optionally, the apparatus further comprises an operation and maintenance module 606 configured to receive an operation and maintenance request for a target application in a designated application cluster, and determine a local database corresponding to the target application as a target database according to the operation and maintenance request; read operation and maintenance data and interaction data of the target application in the designated application cluster from the target database, and perform operation and maintenance on the target application in the designated application cluster according to the read operation and maintenance data and interaction data.

[0107] Optionally, the apparatus further comprises a deployment module 608 configured to configure and deploy the common application cluster; if a target subsystem that needs to be interfaced appears, obtain configuration data of the common application cluster, and deploy an independent application cluster that interfaces with the target subsystem based on the configuration data.

[0108] Optionally, for each business application cluster, the business applications in the business application cluster comprise a branch gateway module, a request processing module and a data processing module; each business application cluster interfaces with a corresponding data source subsystem through the branch gateway module thereof;

[0109] The sending module 604 is specifically configured to process the service request routed by the hub gateway module through the request processing module, and send the processed service request to the branch gateway module;

[0110] The branch gateway module forwards the processed service request to the data source subsystem that interfaces therewith, and receives raw data returned by the data source subsystem and sends the raw data to the data processing module;

[0111] The data processing module processes the raw data to obtain the credit investigation data.

[0112] Optionally, the preset screening condition comprises:

[0113] The stored data is at least one of data required by a designated business, data provided by a designated data provider, a proposed transaction amount of the involved business being greater than a preset transaction amount, and a proposed transaction volume of the involved business being greater than a preset transaction volume.

[0114] For ease of description, the above apparatus is described in various modules or units in terms of function. Of course, when implementing one or more of the present specification, the functions of each module or unit can be implemented in the same or more software and / or hardware, or the modules implementing the same function can be combined into a plurality of sub-modules or sub-units, etc. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0115] Based on the same concept as the above method, the present specification also provides an electronic device, comprising: a processor; a memory for storing processor executable instructions; wherein the processor implements the steps of the method according to any one of the above embodiments by running the executable instructions.

[0116] Based on the same concept as the above method, the present specification also provides a computer readable storage medium, which stores computer instructions, and the instructions are executed by a processor to implement the steps of the method according to any one of the above embodiments.

[0117] Based on the same concept as the above method, the present specification also provides a computer program product, which comprises computer program / instructions, and the computer program / instructions are executed by a processor to implement the steps of the method according to any one of the above embodiments.

[0118] Those skilled in the art can understand that:

[0119] In the present specification, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, product or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or further includes elements inherent to such a process, method, product or device. Without more limitations, it does not exclude the presence of other same or equivalent elements in the process, method, product or device including the elements.

[0120] In the present specification, "one", "a" and "the" do not refer to the singular, but also include the plural.

[0121] In the present specification, the first, second, etc. ordinal numbers do not necessarily indicate the order, and many times are used for the convenience of distinguishing the objects. For example, the first server and the second server usually refer to two servers. In order to distinguish the two servers, they are expressed as the first server and the second server. Of course, sometimes the two servers can also be the same server.

[0122] In this specification, unless specifically stated otherwise, "receiving, sending of data" is not necessarily direct receiving and sending, and can be indirect receiving and sending. For example, A receiving data sent by B can be understood as A directly receiving data sent by B, or can be understood as A indirectly receiving data sent by B through other subjects such as C. Similarly, B sending data to A can be understood as B directly sending data to A, or can be understood as B indirectly sending data to A through other subjects such as C. Here, C can be one subject, or two or more subjects.

[0123] In this specification, unless specifically stated otherwise, the association relationship generated between structures can be a direct association relationship or an indirect association relationship. For example, when describing "A is connected with B", unless it is specifically stated that A is directly connected with B, it should be understood that A can be directly connected with B, or A can be indirectly connected with B; for another example, when describing "A is on B", unless it is specifically stated that A is directly above B (AB is adjacent and A is above B), it should be understood that A can be directly above B, or A can be indirectly above B (there are other elements between AB, and A is above B). By analogy.

[0124] This specification uses specific words to describe the embodiments of the specification. As "one embodiment", "an embodiment", and / or "some embodiments" means a certain feature, structure or characteristic related to at least one embodiment of the specification. Therefore, it should be emphasized and noted that the "an embodiment" or "one embodiment" or "one alternative embodiment" mentioned in different places in this specification does not necessarily refer to the same embodiment. In addition, the skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples without contradiction.

[0125] Although one or more embodiments of the specification provide method steps as described in the embodiments or flowcharts, it can be understood that the order of steps listed in the embodiments or flowcharts is only one of the many execution orders, and does not represent the only execution order. Therefore, when the claims involve method steps, the changes and adjustments of the order of the steps or the parallelism between the steps are also within the scope of protection of the claims.

Claims

1. A business system, the business system comprising: The credit reporting agency has a corresponding credit reporting subsystem and each data source agency has its own corresponding data source subsystem. The credit reporting subsystem is equipped with a central gateway module and multiple business application clusters. The business application cluster includes a regular application cluster and an independent application cluster. The data source subsystem includes a target subsystem that meets preset filtering conditions and other subsystems besides the target subsystem. The independent application cluster is connected to the target subsystem, and the regular application cluster is connected to the other subsystems. Each business application cluster has multiple business applications, and the business applications set in different business application clusters are the same. The central gateway module is used to: for a business request sent by the credit data requester for a target business, based on the feature information corresponding to the business request, route the business request to the business application cluster connected to the data source subsystem that matches the target business; wherein, the feature information corresponds to the filtering conditions of the data source subsystem connected to the business application cluster. Any business application cluster is used to: request raw data from the data source subsystem it interfaces with based on the received business request, generate credit data based on the raw data returned by the data source subsystem, and send the credit data to the party requesting the credit data.

2. In the business system as described in claim 1, the same business applications in different business application clusters share the same local database, and different business applications in the same business application cluster correspond to different local databases. The local database is used to store the operation and maintenance data of the corresponding business application and the interaction data generated during the execution of the business.

3. The business system as described in claim 2, wherein the credit reporting subsystem is further configured to: Receive an operation and maintenance request for a target application in a specified application cluster, and determine the local database corresponding to the target application as the target database based on the operation and maintenance request; The system reads the operation and maintenance data and interaction data of the target application in the specified application cluster from the target database, and performs operation and maintenance on the target application in the specified application cluster based on the read operation and maintenance data and interaction data.

4. The business system as described in claim 1, wherein the credit reporting subsystem is specifically used for: Configure and deploy the general application cluster; If a target subsystem needs to be interfaced with, the configuration data of the ordinary application cluster is obtained, and an independent application cluster that interfaces with the target subsystem is deployed based on the configuration data.

5. The business system as described in claim 1, wherein for each business application cluster, the business applications configured in the business application cluster include: Branch gateway module, request processing module, and data processing module; Each business application cluster connects to its corresponding data source subsystem through its own branch gateway module; The request processing module is used to: process the service requests routed by the central gateway module, and send the processed service requests to the branch gateway module; The branch gateway module is used to: forward the processed business request to the data source subsystem it interfaces with, and receive the raw data returned by the data source subsystem and send the raw data to the data processing module; The data processing module is used to process the raw data to obtain the credit data.

6. The business system as described in claim 1, wherein the preset filtering conditions include: The stored data must be data required for the specified business, data provided by the specified data provider, the proposed transaction amount of the business involved must be greater than the preset transaction amount, or the proposed transaction volume of the business involved must be greater than the preset transaction volume.

7. The business system as described in claim 1, wherein the requesting party for receiving credit data includes: The financial subsystem corresponding to the financial institution includes the following business requests: query requests for the user's historical location information; The financial subsystem is used to obtain the business processing request for the target business sent by the user through the business device, determine the geographical location information corresponding to the location of the business device, and send the query request to the credit reporting subsystem. The credit reporting subsystem is used to: route the query request to the corresponding business application cluster, so as to query the user's historical location information read by the target application through the business application cluster, and return the historical location information to the financial subsystem; wherein, the target application is provided by the data source subsystem corresponding to the business application cluster; The financial subsystem is used to determine whether the target business is at risk based on the geographical location information and the historical location information.

8. A business execution method, wherein the method is applied to a credit reporting subsystem corresponding to a credit reporting agency, wherein, The credit reporting subsystem includes a central gateway module and multiple business application clusters. The business application clusters include ordinary application clusters and independent application clusters. The independent application clusters connect to target subsystems within the data source subsystems corresponding to each data source institution that meet preset filtering conditions. The ordinary application clusters connect to other subsystems besides the target subsystems. The method includes: Business requests sent by the demand side that receive credit data, targeting specific business needs; The central gateway module routes the service request to the business application cluster connected to the data source subsystem that matches the target service based on the feature information corresponding to the service request. Each business application cluster contains multiple business applications, and the business applications in different business application clusters are the same. The feature information corresponds to the filtering conditions of the data source subsystem connected to the business application cluster. Through this business application cluster, raw data is requested from the data source subsystem it is connected to based on the received business request, and credit data is generated based on the raw data returned by the data source subsystem. The credit data is then sent to the credit data requester so that the credit data requester can execute the target business based on the received credit data.

9. The method as described in claim 8, wherein each business application cluster is configured with multiple business applications, and the business applications configured in different business application clusters are the same. The same business applications in different business application clusters share the same local database, while different business applications in the same business application cluster correspond to different local databases. The local database is used to store the operation and maintenance data of the corresponding business application and the interaction data generated during the execution of business.

10. The method of claim 9, further comprising: Receive an operation and maintenance request for a target application in a specified application cluster, and determine the local database corresponding to the target application as the target database based on the operation and maintenance request; The system reads the operation and maintenance data and interaction data of the target application in the specified application cluster from the target database, and performs operation and maintenance on the target application in the specified application cluster based on the read operation and maintenance data and interaction data.

11. The method of claim 8, wherein before receiving the service request for the target service sent by the demander of the credit data, the method further comprises: Configure and deploy the general application cluster; If a target subsystem needs to be interfaced with, the configuration data of the ordinary application cluster is obtained, and an independent application cluster that interfaces with the target subsystem is deployed based on the configuration data.

12. The method as described in claim 8, wherein for each business application cluster, the business applications configured in the business application cluster include: Branch gateway module, request processing module, and data processing module; Each business application cluster connects to its corresponding data source subsystem through its own branch gateway module; Before forwarding business requests from the application cluster to the data source subsystem it interfaces with, the method further includes: The request processing module processes the service requests routed by the central gateway module and sends the processed service requests to the branch gateway module. This business application cluster requests raw data from the data source subsystem it interfaces with based on received business requests, specifically including: The branch gateway module forwards the processed business request to the data source subsystem it interfaces with, and receives the raw data returned by the data source subsystem and sends the raw data to the data processing module. Credit data is generated based on the raw data returned by this data source subsystem, specifically including: The data processing module processes the raw data to obtain the credit data.

13. The method of claim 8, wherein the preset filtering conditions include: The stored data must be data required for the specified business, data provided by the specified data provider, the proposed transaction amount of the business involved must be greater than the preset transaction amount, or the proposed transaction volume of the business involved must be greater than the preset transaction volume.

14. An electronic device comprising: processor; A memory for storing processor-executable instructions; wherein the processor implements the steps of the method as described in any one of claims 8-13 by executing the executable instructions.

15. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 8-13.

16. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 8-13.

Images