CN114035979A - Transaction request processing method and device - Google Patents

Transaction request processing method and device Download PDF

Info

Publication number
CN114035979A
CN114035979A CN202111313326.6A CN202111313326A CN114035979A CN 114035979 A CN114035979 A CN 114035979A CN 202111313326 A CN202111313326 A CN 202111313326A CN 114035979 A CN114035979 A CN 114035979A
Authority
CN
China
Prior art keywords
service
unit
client
micro
global
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
Application number
CN202111313326.6A
Other languages
Chinese (zh)
Inventor
郑凯帆
尹小敏
邓亚丽
谢炜琪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202111313326.6A priority Critical patent/CN114035979A/en
Publication of CN114035979A publication Critical patent/CN114035979A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a transaction request processing method and device, which can be applied to the field of distribution. Receiving a transaction request sent by a target client through external gateway micro-services in a global routing unit of a client information component, wherein the client information component is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services; and calling the microservices in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request. In the scheme, the client information component is divided into a plurality of units, and micro services capable of providing corresponding services are arranged in each divided unit. When the client information component is developed and maintained, each unit and the micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.

Description

Transaction request processing method and device
Technical Field
The invention relates to the technical field of data processing, in particular to a method and a device for processing a transaction request.
Background
The bank core system stores massive customer data, and when receiving a transaction request of a peripheral system or other service request parties, the transaction request is processed by utilizing a customer information component of the bank core system. However, currently, the bank core system usually deploys the customer information components on the host individually, and when the customer information components are developed or maintained, the customer information components need to be started from the whole of the customer information components, which may cause higher development cost and maintenance cost.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for processing a transaction request, so as to solve the problems of higher development cost and higher maintenance cost in the existing manner of deploying a customer information component.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
the first aspect of the embodiment of the invention discloses a method for processing a transaction request, which comprises the following steps:
receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of a client information component, wherein the client information component is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services;
and calling the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request.
Preferably, if the transaction type of the transaction request is an account opening transaction;
the invoking the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request includes:
when the transaction request is positioned to the account opening arrangement microservice in the global business unit through the external gateway microservice, calling the comprehensive microservice in the global business unit, and checking an account opening information column in a request message of the transaction request;
when the account opening information column passes the verification, calling the comprehensive micro-service to determine whether the request message carries a client number corresponding to the target client;
if the request message carries the client number, executing the following steps;
if the request message does not carry the client number, calling a micro-service of a number sender in the global routing unit to generate the client number, and executing the following steps;
the following steps include:
calling global routing microservice in the global routing unit, and registering routing information of the target client, wherein the routing information indicates the mapping relation between the client number and a target subunit number, and the target subunit number is an identifier corresponding to any service subunit in the fragment service unit;
writing the specified information of the target client carried by the request message into the aggregated microservice in the global service unit;
and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
Preferably, if the transaction type of the transaction request is other transactions except the opening transaction;
the invoking the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request includes:
acquiring a client number corresponding to the target client carried in a request message of the transaction request;
calling global routing microservice in the global routing unit, and inquiring a target subunit number corresponding to the client number from a preset routing table, wherein the routing table comprises mapping relations between the client numbers and the subunit numbers, and the subunit number is an identifier corresponding to the service subunit in the fragment service unit;
and calling the micro-service in the service subunit corresponding to the target subunit number, and processing the transaction request.
Preferably, if the transaction type of the transaction request is a maintenance transaction;
the calling of the micro-service in the service subunit corresponding to the target subunit number and the processing of the transaction request comprise:
determining whether to modify the aggregation library or not according to the request message;
if the aggregation base is modified, calling an internal gateway microservice of the global routing unit to forward the transaction request to the global service unit;
the aggregation micro-service of the global business unit is called to modify the aggregation library according to the request message, the main body engineering micro-service in the business subunit corresponding to the target subunit number is called, and the client information of the target client is modified according to the request message;
if not, calling the main body engineering micro-service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
Preferably, the customer information component further divides a technical management unit, and the technical management unit comprises micro-services for providing public services and management services.
A second aspect of the embodiments of the present invention discloses a transaction request processing apparatus, including:
the system comprises a receiving module, a processing module and a sending module, wherein the receiving module is used for receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of a client information assembly, the client information assembly is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services;
and the calling module is used for calling the microservices in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request.
Preferably, if the transaction type of the transaction request is an account opening transaction; the calling module comprises:
the first calling sub-module is used for calling the comprehensive micro-service in the global service unit when the transaction request is positioned to the account opening arrangement micro-service in the global service unit through the external gateway micro-service, and checking an account opening information field in a request message of the transaction request;
the second calling sub-module is used for calling the comprehensive micro-service to determine whether the request message carries the client number corresponding to the target client or not when the account opening information column passes the verification; if the request message carries the client number, executing the following steps; if the request message does not carry the client number, calling a micro-service of a number sender in the global routing unit to generate the client number, and executing the following steps;
the following steps include:
calling global routing microservice in the global routing unit, and registering routing information of the target client, wherein the routing information indicates the mapping relation between the client number and a target subunit number, and the target subunit number is an identifier corresponding to any service subunit in the fragment service unit;
writing the specified information of the target client carried by the request message into the aggregated microservice in the global service unit;
and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
Preferably, if the transaction type of the transaction request is other transactions except the opening transaction; the calling module comprises:
the acquisition submodule is used for acquiring the client number corresponding to the target client carried in the request message of the transaction request;
a third calling sub-module, configured to call a global routing micro-service in the global routing unit, and query, from a preset routing table, a target sub-unit number corresponding to the client number, where the routing table includes a mapping relationship between each client number and each sub-unit number, and the sub-unit number is an identifier corresponding to the service sub-unit in the fragment service unit;
and the fourth calling sub-module is used for calling the micro-service in the service sub-unit corresponding to the target sub-unit number and processing the transaction request.
Preferably, if the transaction type of the transaction request is a maintenance transaction; the fourth calling sub-module is specifically configured to: determining whether to modify the aggregation library or not according to the request message; if the aggregation base is modified, calling an internal gateway microservice of the global routing unit to forward the transaction request to the global service unit; the aggregation micro-service of the global business unit is called to modify the aggregation library according to the request message, the main body engineering micro-service in the business subunit corresponding to the target subunit number is called, and the client information of the target client is modified according to the request message; if not, calling the main body engineering micro-service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
Preferably, the customer information component further divides a technical management unit, and the technical management unit comprises micro-services for providing public services and management services.
Based on the method and the device for processing the transaction request provided by the embodiment of the invention, the method comprises the following steps: receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of a client information component, wherein the client information component is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services; and calling the microservices in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request. In the scheme, a distributed architecture is adopted for the client information component, the client information component is divided into a plurality of units, and micro-services capable of providing corresponding services are arranged in each divided unit. When the client information component is developed and maintained, each unit and the micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a transaction request processing method according to an embodiment of the present invention;
FIG. 2 is a block diagram of a client information component according to an embodiment of the present invention;
FIG. 3 is a flow diagram of processing a transaction request for an account opening transaction according to an embodiment of the invention;
FIG. 4 is a flow diagram of processing a transaction request for a transaction type of a maintenance transaction provided by an embodiment of the invention;
fig. 5 is a block diagram of a transaction request processing apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
It should be noted that the transaction request processing method and apparatus provided by the present invention can be used in the distributed field. The above description is only an example, and does not limit the application field of the transaction request processing method and apparatus provided by the present invention.
As can be seen from the background art, currently, the customer information component is usually deployed on the host individually, and when the customer information component is developed or maintained, the customer information component needs to be started from the whole customer information component, which may cause higher development cost and maintenance cost.
Therefore, the embodiment of the invention provides a method and a device for processing a transaction request, which adopt a distributed architecture for a client information component, divide the client information component into a plurality of units, and set micro-services capable of providing corresponding services in each divided unit. When developing and maintaining customer information components, individual units and microservices can be individually adjusted to reduce development and maintenance costs.
Referring to fig. 1, a flow chart of a processing method of a transaction request according to an embodiment of the present invention is shown, the processing method includes the following steps:
step S101: and receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of the client information component.
It should be noted that the customer information component is at least divided into a plurality of units, such as a global routing unit, a global service unit, a fragment service unit, and the like, each unit can be regarded as a Data Center Node (DCN), each unit is a self-contained set capable of completing all key service operations, and the self-contained set includes micro services for realizing the key service operations and data allocated to the unit.
The global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service subunits, and each service subunit comprises a plurality of micro-services. That is, the global routing unit and the global service unit are not shareable (i.e. not divided into sub-units), and the sharded service unit can be sharded (i.e. a plurality of service sub-units are divided into the sharded service unit).
It should be noted that, the client information component is divided into units in advance, for example, the client information component is divided into at least a global routing unit, a global service unit and a fragment service unit; after the client information component is subjected to unit division, determining a unique service code of each micro-service; according to the services provided by each unit (such as a global routing unit, a global service unit, a fragmentation service unit and the like), configuring correct service codes under the unit (namely defining which micro services are contained in the unit); and pre-configures a mapping rule of client numbers and subunit numbers (service subunit identifications) for specifying which client numbers are mapped with which service subunits, for example: the mapping rule is configured that the client number with the tail number of 000-499 is mapped to the service subunit 1, and the client number with the tail number of 500-999 is mapped to the service subunit 2. The global routing unit is used for providing gateway service and other services for the client information component, and after the unit division of the client information component is completed, unit information of each unit needs to be configured in the gateway service.
It should be further noted that the global routing unit may provide services such as a gateway service (specifically provided by an external gateway micro service and an internal gateway micro service), a global routing service (specifically provided by a global routing micro service), a number sending service (specifically provided by a number sender micro service), a parameter service, and the like for the client information component; wherein, the global routing service at least comprises: a function of registering routing information (registering a mapping relationship between a client number and a subunit number), and a function of inquiring the subunit number according to the client number. The peripheral system can access the customer information component through the external gateway microservice, and the internal gateway microservice can be called by different units in the customer information component.
Preferably, the client information component is further divided into a technical management unit, and the technical management unit comprises micro-services for providing public services and management services; namely, the client information component at least divides a global routing unit, a global service unit, a fragment service unit and a technical management unit.
The above details describe the unit division of the client information component, and in order to more conveniently understand the specific content of the client information component, the example is illustrated by the schematic architecture diagram of the client information component shown in fig. 2, and the unit division of the client information component shown in fig. 2 is only for example.
As shown in fig. 2. The client information component at least divides a global routing unit (G unit in figure 2), a global service unit (N unit in figure 2) and a fragment service unit (B unit in figure 2); the G unit comprises an external gateway microservice, an internal gateway microservice, a global routing microservice, a sender microservice (also called a global sequence number generator microservice), a parameter microservice and the like; the N unit comprises comprehensive micro-services, aggregation micro-services, account opening and arranging micro-services, public parameter micro-services and the like; the B unit is divided into a plurality of business subunits, such as B01 and B02, and each business subunit at least comprises a maintenance scheduling microservice and a main body engineering microservice.
As can be seen from the above, the mapping rule is used to specify which client numbers are mapped with which service sub-units, so that the service sub-units can be divided by the fragment service unit according to the mapping rule, that is, which service sub-units correspond to which client numbers, that is, the service sub-units are divided by the fragment service unit according to the client numbers.
In the process of implementing step S101 specifically, a transaction request sent by a target client (for example, a public client) through a peripheral system is received through an external gateway microservice in a global routing unit of a client information component, where the format of the transaction request is a message format, that is, the peripheral system sends the transaction request in a manner of reporting a request message.
Step S102: and calling the microservices in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request.
For transaction requests of different transaction types, the invoked units and micro-services are also different, and in the process of the step S102, micro-services in the global routing unit, the global service unit and/or the fragment service unit are invoked to process the transaction requests according to the transaction types of the transaction requests.
In some embodiments, if the transaction type of the transaction request is an account opening transaction, that is, the transaction request is used for opening an account, at this time, the microservices in the global routing unit, the global service unit, and the fragment service unit need to be invoked to process the transaction request.
In some embodiments, if the transaction type of the transaction request is other than the opening transaction, a client number corresponding to a target client carried in a request message of the transaction request is obtained; calling global routing microservice in a global routing unit, and inquiring a target subunit number corresponding to a client number from a preset routing table, wherein the routing table comprises mapping relations between the client numbers and the subunit numbers, and the subunit number is an identifier corresponding to a service subunit in a fragment service unit; and calling the micro-service in the service subunit corresponding to the target subunit number, and processing the transaction request. That is, the routing table maintains the mapping relationship between each client number and each subunit number, and the global routing micro-service can query the subunit number corresponding to the client number of the target client (i.e. the target subunit number) from the routing table, determine which service subunit needs to be accessed according to the target subunit number, and access the micro-service in the service subunit corresponding to the target subunit number through the API.
In the embodiment of the invention, a distributed architecture is adopted for the client information component, the client information component is divided into a plurality of units, and micro-services capable of providing corresponding services are arranged in each divided unit. When the client information component is developed and maintained, each unit and the micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
In the above embodiment of the present invention, referring to fig. 3, the content of processing the transaction request whose transaction type is an account opening transaction in step S102 in fig. 1 shows a flowchart of processing the transaction request whose transaction type is an account opening transaction according to an embodiment of the present invention, which includes the following steps:
step S301: and when the transaction request is positioned to the account opening arrangement microservice in the global service unit through the external gateway microservice, calling the comprehensive microservice in the global service unit, and checking an account opening information column in a request message of the transaction request.
In the process of implementing step S301 specifically, when the transaction type of the transaction request is an account opening transaction (the transaction request at this time is an account opening request), when the transaction request is positioned to an account opening arrangement microservice in the global service unit through an external gateway microservice, the comprehensive microservice in the global service unit is invoked to check an account opening information field in a request message of the transaction request, that is, the account opening information field is checked to determine whether the account opening request conforms to an account opening service rule.
It should be noted that before the comprehensive micro-service in the global service unit is invoked to verify the account opening information field, the aggregate micro-service in the global service unit needs to be invoked to perform client uniqueness identification on the target client (the client uniqueness identification can be performed by querying the aggregate library), and only after the target client passes the client uniqueness identification, the comprehensive micro-service in the global service unit is invoked to verify the account opening information field.
In some embodiments, if the target client fails the client unique identification, or if the account opening information field fails to verify, the account opening process is terminated (i.e., the account opening request is not processed).
Step S302: and when the account opening information column passes the verification, calling the comprehensive micro-service to determine whether the request message carries the client number corresponding to the target client. If the request message carries the client number, executing the step S304 and the subsequent steps; if the request message does not carry the client number, step S303 and the following steps are executed.
It should be noted that the client number field in the request message is used for filling in the client number, and in the process of the specific implementation step S302, when the account opening information field passes the verification, the comprehensive micro-service is invoked to determine whether the client number field in the request message is empty; if the client number field is not empty, determining that the request message carries the client number, and executing the step S304 and the subsequent steps; if the client number field is empty, it is determined that the request message does not carry the client number, and step S303 and subsequent steps are performed.
Step S303: and calling the micro-service of the number sender in the global routing unit to generate a client number, and executing the step S304 and the subsequent steps.
In the process of implementing step S303 specifically, if the request message of the transaction request does not carry the client number, the client number needs to be generated for the target client, specifically, the client number corresponding to the target client may be generated by calling the number issuer microserver in the global routing unit, and step S304 and subsequent steps are executed.
Step S304: and calling the global routing microservice in the global routing unit, and registering the routing information of the target client.
It should be noted that the routing information indicates a mapping relationship between the client number and the target sub-unit number, and the target sub-unit number is an identifier corresponding to any service sub-unit in the fragment service unit.
In the process of implementing step S304 specifically, after a client number (a client number carried in the request packet, or a new client number generated by the micro service of the number sender) is obtained, the global routing micro service in the global routing unit is called, so that the global routing micro service registers the routing information of the target client according to the client number, specifically, the global routing micro service can register the routing information of the target client according to the client number and the mapping rule mentioned in step S101, the registered routing information indicates the mapping relationship between the client number and the target sub-unit number (that is, which service sub-unit the client number corresponds to), and the target sub-unit number is an identifier corresponding to any service sub-unit (specifically determined according to the mapping rule and the client number) in the fragment service unit.
That is, after the client number is obtained, the global routing micro-service in the global routing unit is called, so that the global routing micro-service registers the target sub-unit number corresponding to the target client according to the client number, and the service sub-unit corresponding to the client number can be determined through the target sub-unit number.
Step S305: and writing the specified information of the target client carried by the request message into the aggregated micro-service in the global service unit.
In the process of implementing step S305 specifically, the specified information of the target client carried in the request packet is written into the aggregated microservice in the global service unit, where the specified information includes but is not limited to: client certificate number and certificate type.
Step S306: and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
In the process of implementing step S306 specifically, after writing the specified information of the target client carried in the request packet into the aggregated micro-service in the global service unit, the request packet is forwarded to the main-body engineering micro-service in the service subunit corresponding to the target subunit number, and the main-body engineering micro-service is invoked to create the complete information of the target client, where the complete information includes but is not limited to: detailed information such as customer financial information, customer contact information, and customer market information.
It should be noted that, information can be transferred between the global service unit and the fragment service unit through transaction forwarding of service orchestration.
After the main body engineering microservice in the business subunit corresponding to the target subunit number is called to create the complete information of the target customer, the account opening request is successfully processed (namely, the account is successfully opened).
In the embodiment of the invention, if the transaction type of the transaction request is an account opening transaction, micro-services in the global routing unit, the global service unit and the fragment service unit are called to process the transaction request. When the client information component is developed and maintained subsequently, each unit and micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
In the above embodiment of the present invention, the content of the transaction request for processing the transaction type of the transaction other than the account-opening transaction in step S102 in fig. 1 is shown, and if the transaction type of the transaction request is the maintenance transaction, referring to fig. 4, a flowchart for processing the transaction request for processing the transaction type of the maintenance transaction provided in the embodiment of the present invention is shown, and includes the following steps:
step S401: and determining whether to modify the aggregation library or not according to the request message. If the aggregation base is modified, executing step S402 to step S404; if not, executing step S404;
it should be noted that, when the transaction type of the transaction request is the maintenance transaction, the transaction request is used to modify the customer information of the target customer, and at this time, the request message of the transaction request includes a customer number (that is, the transaction type of the transaction request is the known customer number when the maintenance transaction is performed).
In the process of implementing step S401 specifically, when the transaction type of the transaction request is a maintenance transaction, the transaction request is directly routed to the service sub-unit corresponding to the client number in the fragment service unit. At this time, it is determined whether to modify the aggregation base according to the request message, that is, whether to modify the aggregation base is involved in modifying the client information.
If the aggregation base is modified, executing the step S402 to the step S404, modifying the aggregation base firstly and then modifying the customer information; if the aggregation base is not modified, step S404 is executed to directly modify the client information.
Step S402: and calling the internal gateway micro-service of the global routing unit to forward the transaction request to the global service unit.
In the process of implementing step S402 specifically, if the aggregation base is modified, the internal gateway microservice of the global routing unit is invoked to forward the transaction request to the global service unit.
Step S403: and calling the aggregation micro-service of the global service unit to modify the aggregation library according to the request message.
In the process of implementing step S403 specifically, the aggregation microservice of the global business unit is called to modify the data in the aggregation library according to the request message, such as modifying the client name information and the client certificate information of the target client in the aggregation library.
Step S404: and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
In the process of implementing step S404, after the aggregation base is modified (in the case of modifying the aggregation base), or in the case of not modifying the aggregation base, the main-body engineering microservice in the service subunit corresponding to the target subunit number is called, and the customer information of the target customer is modified according to the request message, thereby completing the processing of the transaction request whose transaction type is the maintenance transaction.
Corresponding to the method for processing a transaction request provided by the embodiment of the present invention, referring to fig. 5, an embodiment of the present invention further provides a block diagram of a processing apparatus for a transaction request, where the processing apparatus includes: a receiving module 501 and a calling module 502;
the receiving module 501 is configured to receive a transaction request sent in a message format by a target client through an external gateway micro-service in a global routing unit of a client information component, where the client information component is divided into at least a global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit include multiple micro-services, the fragment service unit is divided into multiple service sub-units, and each service sub-unit includes multiple micro-services.
In some embodiments, the customer information component further divides a technology management unit, and the technology management unit comprises micro-services for providing public class services and management class services.
The invoking module 502 is configured to invoke micro services in the global routing unit, the global service unit, and/or the fragment service unit according to the transaction type of the transaction request, so as to process the transaction request.
In the embodiment of the invention, a distributed architecture is adopted for the client information component, the client information component is divided into a plurality of units, and micro-services capable of providing corresponding services are arranged in each divided unit. When the client information component is developed and maintained, each unit and the micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
Preferably, in conjunction with the content shown in fig. 5, if the transaction type of the transaction request is an account opening transaction; the calling module 502 includes a first calling sub-module and a second calling sub-module, and the execution principle of each sub-module is as follows:
the first calling sub-module is used for calling the comprehensive micro-service in the global service unit when the transaction request is positioned to the account opening arrangement micro-service in the global service unit through the external gateway micro-service, and checking an account opening information column in a request message of the transaction request;
the second calling sub-module is used for calling the comprehensive micro-service to determine whether the request message carries the client number corresponding to the target client or not when the account opening information column passes the verification; if the request message carries the client number, executing the following steps; if the request message does not carry the client number, calling the number sender micro-service in the global routing unit to generate the client number, and executing the following steps;
the method comprises the following steps:
calling global routing microservice in a global routing unit, registering routing information of a target client, wherein the routing information indicates the mapping relation between a client number and a target subunit number, and the target subunit number is an identifier corresponding to any service subunit in a fragment service unit;
writing the specified information of the target client carried by the request message into the aggregated microservice in the global service unit;
and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
In the embodiment of the invention, if the transaction type of the transaction request is an account opening transaction, micro-services in the global routing unit, the global service unit and the fragment service unit are called to process the transaction request. When the client information component is developed and maintained subsequently, each unit and micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
Preferably, in conjunction with the content shown in fig. 5, if the transaction type of the transaction request is an account opening transaction; the calling module 502 includes an obtaining sub-module, a third calling sub-module, and a fourth calling sub-module, and the execution principle of each sub-module is as follows:
and the acquisition submodule is used for acquiring the client number corresponding to the target client carried in the request message of the transaction request.
And the third calling sub-module is used for calling the global routing micro-service in the global routing unit, inquiring a target sub-unit number corresponding to the client number from a preset routing table, wherein the routing table comprises the mapping relation between each client number and each sub-unit number, and the sub-unit number is an identifier corresponding to a service sub-unit in the fragment service unit.
And the fourth calling sub-module is used for calling the micro-service in the service sub-unit corresponding to the target sub-unit number and processing the transaction request.
In a particular implementation, the transaction type of the transaction request is a maintenance transaction; the fourth calling submodule is specifically configured to: determining whether to modify the aggregation library or not according to the request message; if the aggregation base is modified, calling an inner gateway micro service of the global routing unit to forward the transaction request to the global service unit; the aggregation micro-service of the global business unit is called to modify the aggregation library according to the request message, the main body engineering micro-service in the business subunit corresponding to the target subunit number is called, and the client information of the target client is modified according to the request message; if not, calling the main body engineering micro service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
In summary, embodiments of the present invention provide a method and an apparatus for processing a transaction request, where a distributed architecture is adopted for a client information component, the client information component is divided into a plurality of units, and a micro service capable of providing a corresponding service is set in each of the divided units. When the client information component is developed and maintained, each unit and the micro-service can be independently adjusted, and the development cost and the maintenance cost are reduced.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed 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 modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this 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 implementation. 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 invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A method of processing a transaction request, the method comprising:
receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of a client information component, wherein the client information component is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services;
and calling the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request.
2. The method of claim 1, wherein if the transaction type of the transaction request is an account opening transaction;
the invoking the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request includes:
when the transaction request is positioned to the account opening arrangement microservice in the global business unit through the external gateway microservice, calling the comprehensive microservice in the global business unit, and checking an account opening information column in a request message of the transaction request;
when the account opening information column passes the verification, calling the comprehensive micro-service to determine whether the request message carries a client number corresponding to the target client;
if the request message carries the client number, executing the following steps;
if the request message does not carry the client number, calling a micro-service of a number sender in the global routing unit to generate the client number, and executing the following steps;
the following steps include:
calling global routing microservice in the global routing unit, and registering routing information of the target client, wherein the routing information indicates the mapping relation between the client number and a target subunit number, and the target subunit number is an identifier corresponding to any service subunit in the fragment service unit;
writing the specified information of the target client carried by the request message into the aggregated microservice in the global service unit;
and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
3. The method of claim 1, wherein if the transaction type of the transaction request is other than an account opening transaction;
the invoking the micro-service in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request includes:
acquiring a client number corresponding to the target client carried in a request message of the transaction request;
calling global routing microservice in the global routing unit, and inquiring a target subunit number corresponding to the client number from a preset routing table, wherein the routing table comprises mapping relations between the client numbers and the subunit numbers, and the subunit number is an identifier corresponding to the service subunit in the fragment service unit;
and calling the micro-service in the service subunit corresponding to the target subunit number, and processing the transaction request.
4. The method of claim 3, wherein if the transaction type of the transaction request is a maintenance transaction;
the calling of the micro-service in the service subunit corresponding to the target subunit number and the processing of the transaction request comprise:
determining whether to modify the aggregation library or not according to the request message;
if the aggregation base is modified, calling an internal gateway microservice of the global routing unit to forward the transaction request to the global service unit;
the aggregation micro-service of the global business unit is called to modify the aggregation library according to the request message, the main body engineering micro-service in the business subunit corresponding to the target subunit number is called, and the client information of the target client is modified according to the request message;
if not, calling the main body engineering micro-service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
5. The method of claim 1, wherein the customer information component further defines a technical management unit, and wherein the technical management unit comprises micro-services for providing common class services and management class services.
6. An apparatus for processing a transaction request, the apparatus comprising:
the system comprises a receiving module, a processing module and a sending module, wherein the receiving module is used for receiving a transaction request sent by a target client in a message format through an external gateway micro-service in a global routing unit of a client information assembly, the client information assembly is at least divided into the global routing unit, a global service unit and a fragment service unit, the global routing unit and the global service unit comprise a plurality of micro-services, the fragment service unit is divided into a plurality of service sub-units, and each service sub-unit comprises a plurality of micro-services;
and the calling module is used for calling the microservices in the global routing unit, the global service unit and/or the fragment service unit according to the transaction type of the transaction request to process the transaction request.
7. The apparatus of claim 6, wherein if the transaction type of the transaction request is an account opening transaction; the calling module comprises:
the first calling sub-module is used for calling the comprehensive micro-service in the global service unit when the transaction request is positioned to the account opening arrangement micro-service in the global service unit through the external gateway micro-service, and checking an account opening information field in a request message of the transaction request;
the second calling sub-module is used for calling the comprehensive micro-service to determine whether the request message carries the client number corresponding to the target client or not when the account opening information column passes the verification; if the request message carries the client number, executing the following steps; if the request message does not carry the client number, calling a micro-service of a number sender in the global routing unit to generate the client number, and executing the following steps;
the following steps include:
calling global routing microservice in the global routing unit, and registering routing information of the target client, wherein the routing information indicates the mapping relation between the client number and a target subunit number, and the target subunit number is an identifier corresponding to any service subunit in the fragment service unit;
writing the specified information of the target client carried by the request message into the aggregated microservice in the global service unit;
and calling the main body engineering micro-service in the business subunit corresponding to the target subunit number to create the complete information of the target customer.
8. The apparatus of claim 6, wherein if the transaction type of the transaction request is other than an account opening transaction; the calling module comprises:
the acquisition submodule is used for acquiring the client number corresponding to the target client carried in the request message of the transaction request;
a third calling sub-module, configured to call a global routing micro-service in the global routing unit, and query, from a preset routing table, a target sub-unit number corresponding to the client number, where the routing table includes a mapping relationship between each client number and each sub-unit number, and the sub-unit number is an identifier corresponding to the service sub-unit in the fragment service unit;
and the fourth calling sub-module is used for calling the micro-service in the service sub-unit corresponding to the target sub-unit number and processing the transaction request.
9. The apparatus of claim 8, wherein if the transaction type of the transaction request is a maintenance transaction; the fourth calling sub-module is specifically configured to: determining whether to modify the aggregation library or not according to the request message; if the aggregation base is modified, calling an internal gateway microservice of the global routing unit to forward the transaction request to the global service unit; the aggregation micro-service of the global business unit is called to modify the aggregation library according to the request message, the main body engineering micro-service in the business subunit corresponding to the target subunit number is called, and the client information of the target client is modified according to the request message; if not, calling the main body engineering micro-service in the business subunit corresponding to the target subunit number, and modifying the client information of the target client according to the request message.
10. The apparatus of claim 6, wherein the client information component further partitions a technology management unit, and wherein the technology management unit comprises a micro-service for providing a common class service and a management class service.
CN202111313326.6A 2021-11-08 2021-11-08 Transaction request processing method and device Pending CN114035979A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111313326.6A CN114035979A (en) 2021-11-08 2021-11-08 Transaction request processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111313326.6A CN114035979A (en) 2021-11-08 2021-11-08 Transaction request processing method and device

Publications (1)

Publication Number Publication Date
CN114035979A true CN114035979A (en) 2022-02-11

Family

ID=80143283

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111313326.6A Pending CN114035979A (en) 2021-11-08 2021-11-08 Transaction request processing method and device

Country Status (1)

Country Link
CN (1) CN114035979A (en)

Similar Documents

Publication Publication Date Title
CN111163129B (en) Resource processing method and device based on cross-link network
CN108510389B (en) Intelligent contract calling method and device based on block chain and readable storage medium
CN110443704B (en) Method and device for sending resources in cross-link mode
CN110430162B (en) Method and device for sending authenticable message in cross-link mode
RU2436148C2 (en) Adaptive gateway for switching transactions and data on untrusted networks using context-based rules
CN107315786A (en) Business datum storage method and device
CN110430235B (en) Method, apparatus, storage medium and computing device for cross-chain transmission of authenticatable messages
CN110602056B (en) Service parameter transmission method and device
JP7084427B2 (en) Network entities and methods for identifier assignment and / or identifier mapping for network services
CN112188493A (en) Authentication method, system and related equipment
CN110532025A (en) Data processing method, device, equipment and storage medium based on micro services framework
WO2021234464A2 (en) Systems and methods for device detection and registration
CN110633175A (en) Multi-computer-room data processing method based on micro-service, electronic equipment and storage medium
US20060069783A1 (en) Program, method and device for managing information shared among components, recording medium and communication apparatus
CN115934202A (en) Data management method, system, data service gateway and storage medium
CN112801797A (en) Method and apparatus for processing ticket data using a down-link trusted device
CN113312675A (en) Attribute checking method and device, electronic equipment and storage medium
US20230259930A1 (en) Cross-chain transaction processing method and apparatus, electronic device, and storage medium
CN112989422A (en) Block chain system assembling method and device, electronic equipment and storage medium
US10846156B2 (en) Methods, devices and computer program products for managing software function
CN112835700A (en) Data processing method, device, equipment and storage medium based on intelligent contract
CN114035979A (en) Transaction request processing method and device
US20070233690A1 (en) Web Service Contract Selection
CN112001800A (en) Method and device for processing service in block chain system
CN111932326A (en) Data processing method based on block chain network and related equipment

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