CN117114872A - Method, device and system for interaction of core routes of existing management - Google Patents
Method, device and system for interaction of core routes of existing management Download PDFInfo
- Publication number
- CN117114872A CN117114872A CN202311040512.6A CN202311040512A CN117114872A CN 117114872 A CN117114872 A CN 117114872A CN 202311040512 A CN202311040512 A CN 202311040512A CN 117114872 A CN117114872 A CN 117114872A
- Authority
- CN
- China
- Prior art keywords
- transaction message
- core
- account
- management platform
- cash management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000003993 interaction Effects 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims abstract description 39
- 238000000605 extraction Methods 0.000 claims description 25
- 230000004048 modification Effects 0.000 claims description 11
- 238000012986 modification Methods 0.000 claims description 11
- 238000013507 mapping Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 230000002452 interceptive effect Effects 0.000 claims 1
- 230000006870 function Effects 0.000 abstract description 11
- 238000005516 engineering process Methods 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 14
- 230000015654 memory Effects 0.000 description 10
- 238000004891 communication Methods 0.000 description 8
- 238000012546 transfer Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000007599 discharging Methods 0.000 description 2
- HRANPRDGABOKNQ-ORGXEYTDSA-N (1r,3r,3as,3br,7ar,8as,8bs,8cs,10as)-1-acetyl-5-chloro-3-hydroxy-8b,10a-dimethyl-7-oxo-1,2,3,3a,3b,7,7a,8,8a,8b,8c,9,10,10a-tetradecahydrocyclopenta[a]cyclopropa[g]phenanthren-1-yl acetate Chemical group C1=C(Cl)C2=CC(=O)[C@@H]3C[C@@H]3[C@]2(C)[C@@H]2[C@@H]1[C@@H]1[C@H](O)C[C@@](C(C)=O)(OC(=O)C)[C@@]1(C)CC2 HRANPRDGABOKNQ-ORGXEYTDSA-N 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- HUBANNPOLNYSAD-UHFFFAOYSA-N clopyralid Chemical compound OC(=O)C1=NC(Cl)=CC=C1Cl HUBANNPOLNYSAD-UHFFFAOYSA-N 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 229910052709 silver Inorganic materials 0.000 description 1
- 239000004332 silver Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present application relates to the field of financial science and technology, and provides a method, a device and a system for interaction of an existing management core route, wherein the method is applied to a core gateway, and the core gateway is arranged in a core system and comprises the following steps: receiving a transaction message; determining service scene and account information according to the transaction message; inquiring a current management account subscription table to determine a current management subscription condition of the account information; and determining a routing program associated with the service scene, and routing the transaction message by the routing program according to the current management subscription condition so as to route the transaction message to a cash management platform or a core system. By routing the transaction message to the cash management platform or the core system for processing according to the routing program associated with the service scene in the transaction message and the current management signing condition of the account information in the transaction message, and processing the transaction message instead of directly processing the transaction message by the core system, the functions of the cash management platform can be played and the processing pressure of the core system can be reduced under the condition that the existing cash management platform and the core system are not greatly influenced.
Description
Technical Field
The present disclosure relates to the field of financial science and technology, and in particular, to a method, an apparatus and a system for interaction of core routes of current management.
Background
In the prior art, there is a scenario where a main account manages a plurality of sub-accounts, for example, a bank card is opened with a demand deposit account and a fixed-time deposit account, at this time, an entity bank card has no funds, and the funds are stored in the sub-accounts, and this scenario is called as main entity sub-deficiency. In this scenario, the primary account is managed by the core system and the sub-account is managed by the cash management platform. The core system is responsible for the work such as account coming, account going, account taking and settlement of the main account, and is also responsible for the processing such as account coming checking, account going processing, sub-account advanced collection, dialing down, account taking and settlement of the sub-account. The cash management platform is responsible for maintaining signed cash management sub-accounts, for example, for transfer transactions, judging whether a long limit exists, whether the transfer is allowed, whether the amount in the account is enough, and the like, and after the check is successful, carrying out accounting operation, wherein the cash management user has an entity account in the core system to be used as a signed main account.
When the peripheral system initiates related business to the sub-account, the transaction message is sent to the core system, and after the core system finishes the sub-account billing, the cash management platform is notified to bill. When the peripheral system carries out related business about the cash management sub-account, the cash management platform firstly carries out accounting business on the core system after the core system, and in the process, the cash management platform is finally known as a system which is used for carrying out operation on the cash management sub-account business, so that the processing functions of account checking, account discharging, sub-account cash collection, dialing down, accounting, settlement and the like of the cash management platform are basically not embodied, so that the cash management platform cannot fulfill the functional responsibility of the core system, and the burden of the core system is increased. Meanwhile, if the sub-account is checked in at the core, but the sub-account cannot be checked in at the cash management platform, the checking in of the sub-account in the core system needs to be re-transferred out, so that the transaction burden is increased.
Disclosure of Invention
The method and the device are used for solving the problems that the functions of a cash management platform cannot be exerted in the existing main account and sub-account transaction mode, and meanwhile the core system and the transaction burden are increased.
In order to solve the above technical problems, the present application provides an existing core route interaction method applied to a core gateway, where the core gateway is disposed in a core system, and the method includes:
receiving a transaction message;
determining service scene and account information according to the transaction message;
inquiring a current management account subscription table to determine a current management subscription condition of the account information;
and determining a routing program associated with the service scene, and routing the transaction message by the routing program according to the current management subscription condition so as to route the transaction message to a cash management platform or a core system.
Further, determining the service scenario and the account information according to the transaction message includes:
identifying forwarding interface information and service scenes according to the request interface information in the transaction message;
determining an extraction rule according to the forwarding interface information;
according to the extraction rules, account information is extracted from the transaction message.
Further, identifying forwarding interface information and service scenarios according to the request interface information in the transaction message includes: inquiring the current pipeline configuration information table according to the request url in the transaction message to obtain forwarding service url and a service scene; the existing pipeline is configured with mapping relations of request url, forwarding service url and service scene by a configuration information table;
the determining the extraction rule according to the forwarding interface information includes: extracting a service information table according to the inquired forwarding service url inquiry to obtain an extraction rule; the extraction service information table is configured with a mapping relation between forwarding service url and an extraction rule.
Further, the method further comprises the following steps:
and receiving an existing pipeline configuration information modification instruction sent by a user through a client of the core gateway, wherein the client is provided with a configuration interface, and the user completes modification of the existing pipeline configuration information by triggering a control in the configuration interface.
Further, the method further comprises the following steps:
receiving an existing pipeline configuration information modification instruction sent by a user through a core gateway client, wherein the client is provided with a configuration interface, and the user finishes the input of the existing pipeline configuration information modification instruction by triggering a control in the configuration interface;
and modifying the current pipeline configuration information table according to the current pipeline configuration information modification instruction.
Further, the method further comprises the following steps:
judging whether a forwarding sign is provided in the transaction message, wherein the forwarding sign is set by a cash management platform and is used for identifying whether the transaction message passes through the cash management platform or not;
if the forwarding sign is provided, the transaction message is routed to the core system, otherwise, the transaction message is routed to the cash management platform.
Further, when the service scenario is a query service, the processing procedure of the routing program of the query service includes: if the account information is the current management signing sub-account, the transaction message is routed to the cash management platform, and if the account information is the current management signing main account, the transaction message is routed to the core system;
when the service scene is a financial service, the processing procedure of the routing program of the financial service comprises the following steps: if one of the current management subscription accounts exists in the account information, the transaction message is routed to the cash management platform, otherwise, the transaction message is routed to the core system.
Further, after determining that the subscription account is the presence management subscription account, the method further comprises:
inquiring a transaction message to be processed by the cash management platform and detecting whether the cash management platform is being upgraded;
and if the number of the transaction messages to be processed in the cash management platform is larger than a preset value or the cash management platform is in an upgrading state, routing the transaction messages to a core system for processing.
A second aspect of the present disclosure provides a managed core route interaction device applied to a core gateway, where the core gateway is disposed in a core system, and includes:
the receiving unit is used for receiving the transaction message;
the information extraction unit is used for determining service scenes and account information according to the transaction message;
the identification unit is used for inquiring the current management account subscription table to determine the current management subscription condition of the account information;
and the response unit is used for determining a routing program associated with the service scene, and the routing program routes the transaction message according to the current management subscription condition so as to route the transaction message to the cash management platform or the core system.
A third aspect herein provides a managed core routing interaction system comprising: cash management platform, core gateway and core system;
the cash management platform communicates with a core system through an ESB, and the core gateway is disposed in the core system and is configured to perform the method according to any of the foregoing embodiments.
A fourth aspect herein provides a computer storage medium having stored thereon a computer program which, when executed by a processor of a computer device, implements a method as described in any of the preceding embodiments.
According to the method, the device and the system for the transaction management core route interaction, the core network is arranged at the core system side, after the transaction message is received, the core system determines the service scene and the account information according to the transaction message, the transaction account subscription table is queried to determine the transaction subscription condition of the account information, the routing program associated with the service scene is determined, the routing program routes the transaction message according to the transaction subscription condition so as to route the transaction message to the cash management platform or the core system, the transaction message can be routed to the cash management platform or the core system for processing according to the routing program associated with the service scene in the transaction message and the transaction subscription condition of the account information in the transaction message, and the transaction message is processed by the core system instead of being directly processed by the core system, so that the function of the cash management platform can be exerted under the condition that the existing cash management platform and the core system are not greatly influenced, and the processing pressure of the core system can be reduced.
The foregoing and other objects, features and advantages will be apparent from the following more particular description of preferred embodiments, as illustrated in the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments herein or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments herein and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1A illustrates a block diagram of a managed core routing interaction system of embodiments herein;
FIG. 1B illustrates a block diagram of a managed core routing interaction system of embodiments herein;
FIG. 2 shows a schematic diagram of a database design in a core route according to an embodiment herein;
FIG. 3 illustrates a flow chart of a method of managed core route interaction for a core gateway of embodiments herein;
FIG. 4 illustrates a configuration interface schematic of a core gateway client of embodiments herein;
fig. 5 illustrates another flow chart of a managed core route interaction method of a core gateway of embodiments herein;
FIG. 6 illustrates a flowchart for implementing subscription synchronization during advanced management days for embodiments herein;
FIG. 7 illustrates a flow chart of a counter cross-line transfer of embodiments herein;
FIG. 8 illustrates a flow chart of a cash management channel transfer of embodiments herein;
FIG. 9 illustrates a flow chart of a Unionpay billing service of embodiments herein;
FIG. 10 illustrates a flow diagram of query traffic processing of embodiments herein;
FIG. 11 illustrates a block diagram of a managed core routing interaction device of an embodiment herein;
FIG. 12 illustrates a block diagram of a computer device, which is described herein as an embodiment.
Description of the drawings:
101. a cash management platform;
102. a core gateway;
103. a core system;
1101. a receiving unit;
1102. an information extraction unit;
1103. an identification unit;
1104. a response unit;
1202. a computer device;
1204. a processor;
1206. a memory;
1208. a driving mechanism;
1210. an input/output module;
1212. an input device;
1214. an output device;
1216. a presentation device;
1218. a graphical user interface;
1220. a network interface;
1222. a communication link;
1224. a communication bus.
Detailed Description
The following description of the embodiments of the present disclosure will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the disclosure. All other embodiments, based on the embodiments herein, which a person of ordinary skill in the art would obtain without undue burden, are within the scope of protection herein.
It should be noted that the terms "first," "second," and the like in the description and claims herein and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or device.
The present specification provides method operational steps as described in the examples or flowcharts, but may include more or fewer operational steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When a system or apparatus product in practice is executed, it may be executed sequentially or in parallel according to the method shown in the embodiments or the drawings.
It should be noted that the present management core route interaction method and device can be used in the scenes of main accounts and sub-accounts in the financial field.
The information related to the present application (including but not limited to account information and the like) is information authorized by the user or sufficiently authorized by each party.
In an embodiment of the present disclosure, a core routing interaction system for a present management is provided, which is used for solving the problem that the existing main account and sub account transaction methods cannot perform the function of a cash management platform, and increase the core system and transaction burden. Specifically, as shown in fig. 1A and fig. 1B, the managed core routing interaction system includes: cash management platform 101, core gateway 102, and core system 103.
The cash management platform 101 communicates with the core system 103 through the ESB, and the core gateway 102 is provided in the core system 103 for: receiving a transaction message; determining service scene and account information according to the transaction message; inquiring a current management account subscription table to determine a current management subscription condition of the account information; and determining a routing program associated with the service scene, and routing the transaction message by the routing program according to the current management subscription condition so as to route the transaction message to a cash management platform or a core system.
The cash management platform 101 and the core system 103 are existing systems. The cash management platform is responsible for maintaining signed cash management sub-accounts, and a cash management user opens an entity account at a core system to be used as a signed main account, and the cash management is responsible for account checking, account discharging processing, sub-account cash collecting, dialing, counting, checking and other processing of the sub-accounts. The core system is responsible for the work of account coming, account going, account taking, and the like of the main account.
The transaction message is sent by counter equipment, a banking system, a cash management channel, payment equipment and the like. The transaction message contains account information, request interface information (which can be represented by url), service scenario requirement information, and the like, and specifically, the service scenario includes: query class scenarios and financial class scenarios. For query class scenarios, the transaction message also includes query information. The financial class scenario also includes transaction amount, collection account, etc.
The present management account subscription table includes a main account and a sub account of the present management subscription, and is stored in a database of the core gateway, as shown in fig. 2.
The current management subscription condition of the account information comprises: whether the account in the account information is a signed-up account for current management or a sub-account.
The routing program is associated with the service scene and is a preset program. Specifically, determining a routing program associated with a service scenario, the routing program routing a transaction message according to an existing management subscription condition to route the transaction message to a cash management platform or a core system includes:
when the service scene is a query service, the processing procedure of the routing program of the query service comprises the following steps: if the account information is the current management signing sub-account, the transaction message is routed to the cash management platform, and if the account information is the current management signing main account, the transaction message is routed to the core system;
when the service scene is a financial service, the processing procedure of the routing program of the financial service comprises the following steps: if one of the current management subscription accounts exists in the account information, the transaction message is routed to the cash management platform, otherwise, the transaction message is routed to the core system.
According to the embodiment, the transaction message can be routed to the cash management platform or the core system for processing according to the routing program associated with the service scene in the transaction message and the current management signing condition of the account information in the transaction message, and the non-transaction message is directly processed by the core system, so that the function of the cash management platform can be played and the processing pressure of the core system can be reduced under the condition that the existing cash management platform and the core system are not greatly influenced.
In one embodiment herein, as shown in fig. 3, the process of the core gateway executing the managed core route interaction method includes:
step 301, a transaction message is received.
The transaction message is sent by a counter system, an existing management channel and the like.
Step 302, determining service scene and account information according to the transaction message.
The method specifically comprises the following steps: identifying forwarding interface information and service scenes according to the request interface information in the transaction message; determining an extraction rule according to the forwarding interface information; according to the extraction rules, account information is extracted from the transaction message.
As shown in fig. 2, the database of the core gateway stores a current pipe configuration information table and an extracted service information table in addition to the current pipe account subscription table. The present pipeline is configured with mapping relationships of request url, forwarding service url and business scenario (i.e. rule processing class in fig. 2) by the configuration information table. The extraction service information table is configured with a mapping relationship between the forwarding service url and the extraction rule (i.e., the variable range process and the extraction specification in fig. 2).
According to the request interface information in the transaction message, the identification of the forwarding interface information and the service scene comprises the following steps: inquiring the current pipeline configuration information table according to the request url in the transaction message to obtain forwarding service url and a service scene.
According to the forwarding interface information, determining the extraction rule includes: and extracting the service information table according to the inquired forwarding service url inquiry to obtain an extraction rule.
The extraction rules are agreed with extracted fields, such as query class forwarding service url, which include query account information, and such as financial class forwarding service url, which include payment account information, transaction amount, currency, and collection account information. In specific implementation, the extraction field depends on the service scenario, which is not specifically limited herein.
Step 303, query the present management account subscription table to determine the present management subscription condition of the account information.
Step 304, determining a routing program associated with the service scenario, and routing the transaction message by the routing program according to the current management subscription condition so as to route the transaction message to a cash management platform or a core system.
In an embodiment herein, in order to avoid that the transaction message is continuously sent to the cash management platform under the condition that the present pipe channel sends the transaction message, so as to generate a dead loop, the present pipe core route interaction method includes, in addition to the steps 301 to 304, the following steps:
judging whether the transaction message has a forwarding sign, wherein the forwarding sign is set by a cash management platform and is used for identifying whether the transaction message passes through the cash management platform or not, and when the transaction message is implemented, the cash management platform generates a forwarding sign for the transaction message processed by the cash management platform; if the forwarding sign is provided, the transaction message is routed to the core system, otherwise, the transaction message is routed to the cash management platform.
In an embodiment herein, as shown in fig. 4, the contents of the existing pipe configuration table may be modified through the core gateway client configuration interface shown in fig. 4, and specifically, for the core gateway, the following processing is performed:
receiving an existing pipeline configuration information modification instruction sent by a user through a core gateway client, wherein the client is provided with a configuration interface, and the user finishes the input of the existing pipeline configuration information modification instruction by triggering a control in the configuration interface;
and modifying the current pipeline configuration information table according to the current pipeline configuration information modification instruction.
In one embodiment, as shown in fig. 5, the determining that the tube subscription account occurs further includes:
step 501, query a cash management platform for a transaction message to be processed and detect whether the cash management platform is being upgraded.
Step 502, if the number of transaction messages to be processed in the cash management platform is greater than a predetermined value, which indicates that there is a large processing pressure on the cash management platform, or the cash management platform is in an upgrade state, which indicates that the cash management platform is currently unavailable, the transaction messages are routed to the core system for processing.
The embodiment can relieve the pressure of the cash management platform and improve the processing efficiency of the transaction message on the basis of identifying the processing condition and the upgrading condition of the cash management platform.
In an embodiment of the present application, when the subscription relationship of the cash management sub-account changes, the core system is notified of the change of the subscription relationship in real time, and the cash management ensures successful control of synchronization, if the core system returns that the synchronization result is failure or error, the synchronization subscription fails. After the core system subscription information is synchronized, the changed subscription information is stored in the current management account subscription table. The subscription synchronization process is shown in fig. 6.
The embodiment can ensure high reliability of service and avoid inconsistent subscription information.
In order to more clearly illustrate the technical solutions herein, the following detailed description will take several specific scenarios as examples.
Scene one: counter-side trans-line transfer of finance classes.
As shown in fig. 7, the now pipe core interaction process includes:
(1) The counter system sends a transaction message of cross-bank transfer to the payment system, and the payment system sends the transaction message to the core gateway.
(2) The core gateway receives the transaction message, identifies the transaction scene (the scene is a financial class) and account information, judges whether the account signs up for cash management, if so, forwards the transaction message to a cash management platform for processing (sub-account fund freezing), and if not, forwards the transaction message to a core system for processing.
(3) And after processing, the cash management platform returns the transaction message with the forwarding mark to the core gateway.
(4) After the core gateway recognizes that the transaction message has a forwarding mark, the transaction message is sent to the core system.
(5) The core system sends the deduction success information to the core gateway according to the transaction report Wen Koukuan (the deduction of the main account) after the deduction is completed.
(6) The core network sends the successful deduction information of the main account to the cash management system.
(7) The cash management system deducts the frozen funds, and returns the successful deduction information of the sub-account to the core gateway.
(8) The core network returns the sub-account deduction success information to the payment system, and the payment system feeds back the payment result to the counter system.
Scene II: financial class cash management channel transfers.
As shown in fig. 8, the now pipe core interaction process includes:
(1) And the enterprise network bank sends a transaction message of the cross-bank transfer to the cash management platform.
(2) And after processing the transaction message, the cash management platform returns the transaction message with the forwarding mark to the core gateway through the payment and intermediate service system.
(3) After the core gateway recognizes that the transaction message has a forwarding mark, the transaction message is sent to the core system.
(4) The core system sends the deduction success information to the core gateway according to the transaction report Wen Koukuan (the deduction of the main account) after the deduction is completed.
(5) The core network returns the successful deduction information of the main account to the cash management system through the payment and intermediate service system.
(6) The cash management system returns the processing result to the enterprise network bank and sends a dynamic account notification to the core system.
Scene III: and (5) a financial group account-in-silver business.
As shown in fig. 9, the pipe core interaction process includes:
the core gateway receives the account-entering transaction message sent by the payment and intermediate business system, identifies transaction scene (the scene is financial class) and account information, judges whether the account signs up for cash management, if yes, forwards the transaction message to the cash management platform, and if true, invokes the core system account-entering processing.
The payment and intermediate business system is similar to the Unionpay and is a transaction initiating system.
Scene four: query class traffic.
As shown in fig. 10, the now pipe core interaction process includes:
(1) The core gateway receives the inquiry transaction message sent by the counter system, identifies transaction scenes (the scenes are inquiry types) and account information, and judges whether the account types and the signed cash management are adopted.
(2) If the account is a sub account and the contract is signed, the account is sent to a cash management platform for processing, the cash management platform returns a query result to a core gateway, and the core gateway sends the query result to a counter system.
(3) If the account is the main account and the contract is signed, the result is sent to the core system, the core system returns the query result to the core gateway, and the core gateway sends the query result to the counter system.
Based on the same inventive concept, there is also provided herein a managed core route interaction device, as described in the following embodiments. Because the principle of solving the problem of the present management core route interaction device is similar to that of the present management core route interaction method, the implementation of the present management core route interaction device can refer to the present management core route interaction method, and the repetition is not repeated.
Specifically, as shown in fig. 11, the present managed core route interaction device is applied to a core gateway, and includes:
a receiving unit 1101, configured to receive a transaction message;
an information extraction unit 1102, configured to determine a service scenario and account information according to the transaction message;
an identifying unit 1103, configured to query a current management account subscription table to determine a current management subscription condition of the account information;
the response unit 1104 is configured to determine a routing procedure associated with the service scenario, where the routing procedure routes the transaction message according to the current subscription condition, so as to route the transaction message to the cash management platform or the core system.
According to the embodiment, the transaction message can be routed to the cash management platform or the core system for processing according to the routing program associated with the service scene in the transaction message and the current management signing condition of the account information in the transaction message, and the non-transaction message is directly processed by the core system, so that the function of the cash management platform can be played and the processing pressure of the core system can be reduced under the condition that the existing cash management platform and the core system are not greatly influenced.
The present management core route interaction method, device and system provided by the present management core route interaction method, device and system have the following advantages: interaction between a cash management platform and a core system is realized through ESB, a core gateway is configured in the core system, scene recognition and filtration codes, account recognition rules in each service scene and current pipe account subscription recognition are configured in the core gateway, transaction messages are routed according to routing programs associated with the service scenes and current pipe subscription recognition results, the problem that the prior art business cannot reach the current pipe and is processed is solved, reliability of a business process is greatly enhanced, risks of an original system are fully considered in a design process, an original interface is kept unchanged as far as possible, and therefore the peripheral system can conveniently be connected with the original system, and operation stability of the original system is kept.
In an embodiment herein, a computer device is also provided, as shown in fig. 12, the computer device 1202 may include one or more processors 1204, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. Computer device 1202 may also include any memory 1206 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 1206 may include any one or more of the following combinations: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may store information using any technique. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 1202. In one case, when the processor 1204 executes associated instructions stored in any memory or combination of memories, the computer device 1202 can perform any of the operations of the associated instructions. The computer device 1202 also includes one or more drive mechanisms 1208 for interacting with any memory, such as a hard disk drive mechanism, optical disk drive mechanism, and the like.
The computer device 1202 may also include an input/output module 1210 (I/O) for receiving various inputs (via an input device 1212) and for providing various outputs (via an output device 1214). One particular output mechanism may include a presentation device 1216 and an associated Graphical User Interface (GUI) 1218. In other embodiments, input/output module 1210 (I/O), input device 1212, and output device 1214 may not be included as only one computer device in a network. Computer device 1202 may also include one or more network interfaces 1220 for exchanging data with other devices via one or more communication links 1222. One or more communication buses 1224 couple the above-described components together.
The communication link 1222 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the internet), a point-to-point connection, etc., or any combination thereof. The communication link 1222 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
Embodiments herein also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
Embodiments herein also provide a computer readable instruction, wherein the program therein causes a processor to perform the method of any of the preceding embodiments when the processor executes the instruction.
It should be understood that, in the various embodiments herein, the sequence number of each process described above does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments herein.
It should also be understood that in embodiments herein, the term "and/or" is merely one relationship that describes an associated object, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the elements may be selected according to actual needs to achieve the objectives of the embodiments herein.
In addition, each functional unit in the embodiments herein may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions herein are essentially or portions contributing to the prior art, or all or portions of the technical solutions may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments herein. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Specific examples are set forth herein to illustrate the principles and embodiments herein and are merely illustrative of the methods herein and their core ideas; also, as will be apparent to those of ordinary skill in the art in light of the teachings herein, many variations are possible in the specific embodiments and in the scope of use, and nothing in this specification should be construed as a limitation on the application.
Claims (10)
1. The core route interaction method of the present management is characterized by being applied to a core gateway, wherein the core gateway is arranged in a core system and comprises the following steps:
receiving a transaction message;
determining service scene and account information according to the transaction message;
inquiring a current management account subscription table to determine a current management subscription condition of the account information;
and determining a routing program associated with the service scene, and routing the transaction message by the routing program according to the current management subscription condition so as to route the transaction message to a cash management platform or a core system.
2. The method of claim 1, wherein determining business scenarios and account information from the transaction message comprises:
identifying forwarding interface information and service scenes according to the request interface information in the transaction message;
determining an extraction rule according to the forwarding interface information;
according to the extraction rules, account information is extracted from the transaction message.
3. The method of claim 2, wherein identifying forwarding interface information and traffic scenarios based on request interface information in a transaction message comprises: inquiring the current pipeline configuration information table according to the request url in the transaction message to obtain forwarding service url and a service scene; the existing pipeline is configured with mapping relations of request url, forwarding service url and service scene by a configuration information table;
the determining the extraction rule according to the forwarding interface information includes: extracting a service information table according to the inquired forwarding service url inquiry to obtain an extraction rule; the extraction service information table is configured with a mapping relation between forwarding service url and an extraction rule.
4. A method as recited in claim 3, further comprising:
receiving an existing pipeline configuration information modification instruction sent by a user through a core gateway client, wherein the core gateway client is provided with a configuration interface, and the user finishes the input of the existing pipeline configuration information modification instruction by triggering a control in the configuration interface;
and modifying the current pipeline configuration information table according to the current pipeline configuration information modification instruction.
5. The method as recited in claim 1, further comprising:
judging whether a forwarding sign is provided in the transaction message, wherein the forwarding sign is set by a cash management platform and is used for identifying whether the transaction message passes through the cash management platform or not;
if the forwarding sign is provided, the transaction message is routed to the core system, otherwise, the transaction message is routed to the cash management platform.
6. The method of claim 3, wherein when the traffic scenario is a query class traffic, the processing of the routing program of the query class traffic comprises: if the account information is the current management signing sub-account, the transaction message is routed to the cash management platform, and if the account information is the current management signing main account, the transaction message is routed to the core system;
when the service scene is a financial service, the processing procedure of the routing program of the financial service comprises the following steps: if one of the current management subscription accounts exists in the account information, the transaction message is routed to the cash management platform, otherwise, the transaction message is routed to the core system.
7. The method of claim 1, wherein determining to present the contracted account further comprises:
inquiring a transaction message to be processed by the cash management platform and detecting whether the cash management platform is being upgraded;
and if the number of the transaction messages to be processed in the cash management platform is larger than a preset value or the cash management platform is in an upgrading state, routing the transaction messages to a core system for processing.
8. The utility model provides a core route interaction device of present management, its characterized in that is applied to core gateway, wherein, core gateway sets up in core system, includes:
the receiving unit is used for receiving the transaction message;
the information extraction unit is used for determining service scenes and account information according to the transaction message;
the identification unit is used for inquiring the current management account subscription table to determine the current management subscription condition of the account information;
and the response unit is used for determining a routing program associated with the service scene, and the routing program routes the transaction message according to the current management subscription condition so as to route the transaction message to the cash management platform or the core system.
9. An on-the-fly core routing interactive system, comprising: cash management platform, core gateway and core system;
the cash management platform communicates with a core system through an ESB, the core gateway being provided to the core system for performing the method of any one of claims 1 to 7.
10. A computer storage medium having stored thereon a computer program, which when executed by a processor of a computer device implements the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311040512.6A CN117114872A (en) | 2023-08-17 | 2023-08-17 | Method, device and system for interaction of core routes of existing management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311040512.6A CN117114872A (en) | 2023-08-17 | 2023-08-17 | Method, device and system for interaction of core routes of existing management |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117114872A true CN117114872A (en) | 2023-11-24 |
Family
ID=88799433
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311040512.6A Pending CN117114872A (en) | 2023-08-17 | 2023-08-17 | Method, device and system for interaction of core routes of existing management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117114872A (en) |
-
2023
- 2023-08-17 CN CN202311040512.6A patent/CN117114872A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7004382B2 (en) | Payment validation network | |
| US8131619B1 (en) | Service fee-based payment processing | |
| CA2711936A1 (en) | System and method for data completion including push identifier | |
| CN105205717A (en) | Bank system transaction information management method, system and general account transfer system | |
| CN112053232B (en) | Self-service equipment business accounting consistency processing method and device | |
| JP2938437B2 (en) | How to handle transaction data | |
| CN106709798A (en) | Interbank liquidation method and system | |
| WO2021164555A1 (en) | Transfer processing system, data processing method, card binding method, initiating terminal for sending transaction data, method for sending transaction data, server, and storage medium | |
| CN109377206A (en) | Pay limit system, method, apparatus and storage medium | |
| CN112819473A (en) | Order processing method, server, equipment and medium based on digital dictionary | |
| CN110297824B (en) | Data recording method, device, equipment and storage medium based on resource transfer | |
| CN116777543A (en) | Aggregate payment method and system supporting support and verification integration | |
| CN116823238A (en) | Data transmission method, device, equipment and storage medium in cross-border set-up money transfer | |
| CN114546872B (en) | Certificate management testing method and device, computer equipment and storage medium | |
| CN117114872A (en) | Method, device and system for interaction of core routes of existing management | |
| CN115375451A (en) | Transaction message processing method and device, storage medium and electronic equipment | |
| US10991045B2 (en) | Blockchain-based settlement method, apparatus, and electronic device | |
| CN113159789A (en) | Cross-bank transfer and remittance method and device | |
| CN112446787A (en) | Resource transfer method, device, equipment and storage medium | |
| US20200193402A1 (en) | User interface enforcing device constraints during physical and electronic reconciliation | |
| CN111915421B (en) | Exchange processing method and system for internal transaction of banking system | |
| CN110717747B (en) | Settlement method, settlement device, settlement terminal and computer storage medium | |
| US8423439B1 (en) | Service fee-based payment processing | |
| TWI831114B (en) | Integrity verifying method, system and computer device of separated cross-platform trade and accounting, computer-readable medium | |
| KR20180001980A (en) | Method and apparatus for processing finance data using common virtual account service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |