A service request distribution method, device, equipment, storage medium and program product
By parsing the resource identifier information and interface category of business requests, determining the customer identifier, and querying the rule configuration table, the problem of business request distribution during data migration was solved, and accurate distribution and processing of business requests were achieved.
Patent Information
- Application Number
- CN202411520408.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-11-28
- Estimated Expiration
- 2044-10-29
AI Technical Summary
During data migration, how can business requests be accurately distributed to the old or new system to ensure normal business processing?
By parsing the pending business requests, resource identification information and interface categories are obtained, target information is determined, and the target system is identified by querying the rule configuration table in the database based on the customer identifier. The business requests are then sent to the target system.
It ensures accurate distribution of business requests and guarantees normal business processing.
Smart Images
Figure CN119652975B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] Embodiments of the present application relate to the technical field of computer, and particularly relate to a method and apparatus for distributing service requests, a device, a storage medium and a program product. BACKGROUND
[0002] With the rapid development of computer technology, the degree of enterprise informatization is higher and higher, and the old system is replaced by the new system with more perfect functions, so that the system function is more and more perfect.
[0003] After the development of the new system, the data in the old system needs to be migrated to the new system, so that the new system can process the corresponding service request. In the data migration process, in order to ensure the normal processing of the business, the service request needs to be distributed to the old system or the new system according to the progress of the data migration, so it is particularly important to accurately distribute the service request to the target system. SUMMARY
[0004] Embodiments of the present application provide a method and apparatus for distributing service requests, a device, a storage medium and a program product, which can accurately distribute the service request to the target system and ensure the normal processing of the business.
[0005] In a first aspect, the present application provides a method for distributing service requests, comprising:
[0006] obtaining a to-be-processed service request; wherein the to-be-processed service request comprises request header information, request body information, session information and request message;
[0007] analyzing the to-be-processed service request to obtain resource identification information and interface category;
[0008] determining target information based on the interface category; wherein the target information is any one of the resource identification information, the request header information, the request body information, the session information and the request message;
[0009] determining a customer identifier according to the target information, and querying a rule configuration table from a database based on the customer identifier;
[0010] determining a target system from the rule configuration table based on the resource identification information, and sending the to-be-processed service request to the target system for processing; wherein the target system is an old system or a new system.
[0011] In a second aspect, the present application further provides a device for distributing service requests, comprising:
[0012] The business request to be processed acquisition module is configured to acquire a business request to be processed; wherein the business request to be processed comprises request header information, request body information, session information and a request message;
[0013] The business request to be processed analysis module is configured to analyze the business request to be processed to obtain resource identification information and an interface category;
[0014] The target information determination module is configured to determine target information based on the interface category; wherein the target information is any one of the resource identification information, the request header information, the request body information, the session information and the request message;
[0015] The customer identification determination module is configured to determine a customer identification according to the target information, and query a rule configuration table from a database based on the customer identification;
[0016] The target system determination module is configured to determine a target system from the rule configuration table based on the resource identification information, and send the business request to be processed to the target system for processing; wherein the target system is an old system or a new system.
[0017] In a third aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the business request distribution method according to any of the embodiments of the present application when executing the program.
[0018] In a fourth aspect, a computer readable storage medium is provided, which stores a computer program, and the program is executable on a processor to implement the business request distribution method according to any of the embodiments of the present application.
[0019] In a fifth aspect, a computer program product is provided, which includes a computer program, and the computer program is executable on a processor to implement the business request distribution method according to any of the embodiments of the present application.
[0020] The embodiment of the application discloses a service request distribution method, device, equipment, storage medium and program product, acquires a to-be-processed service request; wherein the to-be-processed service request comprises request header information, request body information, session information and a request message; the to-be-processed service request is analyzed to obtain resource identification information and an interface category; target information is determined based on the interface category; wherein the target information is any one of the resource identification information, the request header information, the request body information, the session information and the request message; a customer identifier is determined according to the target information, and a rule configuration table is queried from a database based on the customer identifier; a target system is determined from the rule configuration table based on the resource identification information, and the to-be-processed service request is sent to the target system for processing. The service request distribution method provided in the embodiment determines the customer identifier from any one of the resource identification information, the request header information, the request body information, the session information and the request message through the interface category analyzed from the to-be-processed service request, determines the target system based on the customer identifier, associates the service request distribution with the customer identifier, can accurately distribute the service request to the target system, and ensures normal processing of the service. BRIEF DESCRIPTION OF DRAWINGS
[0021] In order to more clearly explain the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the application, and therefore should not be regarded as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.
[0022] Figure 1 A flowchart of a service request distribution method provided by the embodiment of the application;
[0023] Figure 2 A flowchart of a service request distribution method provided by the embodiment of the application;
[0024] Figure 3 A structural schematic diagram of a service request distribution device provided by the embodiment of the application;
[0025] Figure 4 A structural schematic diagram of an electronic device provided by the embodiment of the application. DETAILED DESCRIPTION
[0026] The application will be further described below in combination with the drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the application, and not to limit the application. In addition, it should be noted that, for the convenience of description, only the parts related to the application are shown in the drawings, not all the structures.
[0027] It should be noted that similar labels and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. Meanwhile, in the description of the present application, the terms "first", "second" and the like are only used to distinguish description, and cannot be understood as indicating or implying relative importance. The acquisition, storage, use, processing and the like of data in the technical solution of the present application all comply with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of the present application, some industry existing solutions of software, components, models and the like may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0028] Figure 1 A flow chart of a service request distribution method provided by an embodiment of the present application is provided. The method can be applied to the distribution of service requests. The method can be executed by a service request distribution device. The device can be implemented in the form of software and / or hardware. Alternatively, the device can be implemented by an electronic device, which can be a mobile terminal, a PC terminal or a server, etc. As shown in Figure 1 the method includes the following steps.
[0029] S110, obtaining a to-be-processed service request.
[0030] The to-be-processed service request includes request header information, request body information, session information and request message. The to-be-processed service request can be a hypertext transfer protocol (HTTP) request initiated by a service initiator for processing a certain service to achieve a certain requirement or purpose. In this embodiment, the load balancing sends the to-be-processed service request directly to the web application after receiving the to-be-processed service request. The web application sends the to-be-processed service request to the subsequent service system after processing the to-be-processed service request.
[0031] S120, analyzing the to-be-processed service request to obtain resource identification information and interface category.
[0032] The resource identifier information can be understood as a uniform resource identifier (URI). The interface category can be understood as an interface category of the resource identifier information, which is defined and configured by a starting person of the business system. In this embodiment, the distribution rules of the business requests corresponding to different interface categories are different, and the distribution rule is a rule for determining a customer identifier (ID) and determining a target system based on the customer identifier. In this application scenario, the interface category can include eleven categories, which are a first category, a second category, a third category, a fourth category, a fifth category, a sixth category, a seventh category, an eighth category, a ninth category, a tenth category, and an eleventh category. The interface category can be identified by a keyword, and the value of the keyword can determine the specific interface category. For example, assuming that the keyword is “Tp”, when Tp = 1, the interface category is the first category; when Tp = 2, the interface category is the second category; when Tp = 3, the interface category is the third category; when Tp = 4, the interface category is the fourth category; when Tp = 5, the interface category is the fifth category; when Tp = 6, the interface category is the sixth category; when Tp = 7, the interface category is the seventh category; when Tp = 8, the interface category is the eighth category; when Tp = 9, the interface category is the ninth category; when Tp = 10, the interface category is the tenth category; and when Tp = 11, the interface category is the eleventh category.
[0033] In S130, target information is determined based on the interface category.
[0034] The target information can be any one of the resource identifier information, the request header information, the request body information, the session information, and the request message. The target information can be understood as information that can determine the market identifier.
[0035] Specifically, the manner of determining the target information based on the interface category can be as follows: if the interface category is the first category, the determined target information is the request body information; if the interface category is the second category, the determined target information is the session information; if the interface category is the third category, the determined target information is the resource identifier information; if the interface category is the fourth category, the determined target information is the request body information; if the interface category is the fifth category, the determined target information is the request message; if the interface category is the sixth category or the eighth category, the determined target system is a new system; if the interface category is the ninth category, the determined target system is an old system; if the interface category is the seventh category, the determined target information is the request message; if the interface category is the tenth category, the determined target information is the request message; and if the interface category is the eleventh category, the determined target information is the request header information.
[0036] In S140, a customer identifier is determined based on the target information, and a rule configuration table is queried from a database based on the customer identifier.
[0037] The rule configuration table is configured with a correspondence between the resource identification information and the target system, and one customer identification corresponds to one rule configuration table. The correspondence between the customer identification and the rule configuration table is pre-set, and the correspondence between the resource identification information and the target system is also pre-set. The correspondence between the customer identification and the rule configuration table and the correspondence between the resource identification information and the target system are updated with the migration progress of the business data corresponding to the customer identification from the old system to the new system.
[0038] Optionally, if the interface category is the first category, the determined target information is the request body information, and the manner of determining the customer identification according to the target information can be: extracting data corresponding to a preset key field from the request body information to obtain the customer identification.
[0039] The preset key field can be a field pre-configured for association with the customer identification, for example, can be “Rule_cntnt”. Specifically, when Tp=1, data corresponding to the key field (key) “Rule_cntnt” is extracted from the request body information, so as to obtain the customer identification.
[0040] Optionally, if the interface category is the second category, the determined target information is the session information; and the manner of determining the customer identification according to the target information can be: extracting data corresponding to a preset key field from the session information to obtain a first keyword; querying customer information according to the first keyword and customer login information; and parsing the customer information to obtain the customer identification.
[0041] The manner of querying the customer information according to the first keyword and the customer login information can be: splicing the first keyword and the customer login information, and querying the customer information from the session information again based on the spliced information. Specifically, when Tp=2, data corresponding to the attribute Rule_cntnt, i.e., the first keyword (key1), is obtained from the current session information, the customer information (UserInfoDo) is queried from the session information again with the customer login information (loginUserId)+the first keyword (key1) as the key, and finally the customer information is parsed to obtain the customer identification.
[0042] Optionally, if the interface category is the third category, the determined target information is the resource identification information; and the manner of determining the customer identification according to the target information can be: performing path matching on the resource identification information to obtain the customer identification.
[0043] The process of performing path matching on the resource identification information can be: first determining a storage path corresponding to the resource identification information, and then obtaining the customer identification from the storage path. Specifically, when Tp=3, there is no data of Rule_cntnt in this case, and the customer identification is obtained by performing path matching on the resource identification information.
[0044] Optionally, if the interface category is the fourth category, the determined target information is the request body information; and the manner of determining the customer identifier according to the target information can be: extracting data corresponding to a preset key field from the request body information; and obtaining the customer identifier by intercepting a set number of sub-data at a preset position from the data corresponding to the preset key field.
[0045] The preset position can be front, rear or middle, and the set number can be preset. For example, the first 15 bits of the sub-data are intercepted from the data corresponding to the preset key field as the customer identifier. Specifically, when Tp=4, the key field corresponding to the data is extracted from the request body information, and the first 15 bits are intercepted from the extracted data to obtain the customer identifier.
[0046] Optionally, if the interface category is the fifth category, the determined target information is the request message; and the manner of determining the customer identifier according to the target information can be: decrypting the request message; extracting data corresponding to a preset key field from the decrypted request message; and obtaining the customer identifier by querying the database corresponding to the database ID for data corresponding to the second keyword.
[0047] The data includes the second keyword and the database ID. In this embodiment, the request message is represented in the form of Extensible Markup Language (XML), so the request message needs to be decrypted first. In the request message, the data corresponding to the preset key field is represented in the form of “second keyword + preset separator + database ID”. The preset separator can be “@”. After obtaining the second keyword and the database ID, the data corresponding to the second keyword is queried from the database corresponding to the database ID to obtain the customer identifier. Specifically, when Tp=5, it is an employee channel request, the data corresponding to Rule_cntnt is extracted after the request message is decrypted: second keyword @ database ID; and then the data corresponding to the second keyword is queried from the database corresponding to the database ID to obtain the customer identifier.
[0048] Optionally, if the interface category is the seventh category, the determined target information is the request message; and the manner of determining the customer identifier according to the target information can be: decrypting the request message; and obtaining the customer identifier by extracting data corresponding to a preset key field from the decrypted request message.
[0049] Specifically, when Tp=7, the request message in the xml format is decrypted first, and then the data corresponding to Rule_cntnt is extracted from the decrypted request message to obtain the customer identifier.
[0050] Optionally, if the interface category is the tenth category, the determined target information is a request message; and the manner of determining the customer identifier according to the target information can be: extracting form data from the request message; extracting data corresponding to a preset key field from the form data to obtain the customer identifier.
[0051] Specifically, when Tp=10, it is form submission, and the data corresponding to Rule_cntnt is extracted from the form data in the request message to obtain the customer identifier.
[0052] Optionally, if the interface category is the eleventh category, the determined target information is request header information; and the manner of determining the customer identifier according to the target information can be: obtaining a token ID from the request header information; obtaining customer information from a database according to the token ID; and parsing the customer information to obtain the customer identifier.
[0053] Specifically, when Tp=11, the token ID (tokenId) is obtained from the request header information (header), and the customer information (UserInfoDo) is read from the database (redis) according to the tokenId, and the customer information is parsed to obtain the customer identifier.
[0054] S150, determining a target system from a rule configuration table based on the resource identifier information, and sending the to-be-processed business request to the target system for processing.
[0055] The target system is an old system or a new system.
[0056] Specifically, the manner of determining the target system from the rule configuration table based on the resource identifier information can be: determining a transmission channel of the to-be-processed business request based on the resource identifier information; if the transmission channel is a preset channel, extracting real resource identifier information from the request message; and determining the target system from the rule configuration table based on the real resource identifier information.
[0057] The preset channel can be a 68 interface from P5. If the transmission channel is the preset channel, the request message needs to be decrypted, and then the real resource identifier information is extracted from the decrypted request message, and the target system is determined from the rule configuration table based on the real resource identifier information. If the transmission channel is not the preset channel, the target system is directly determined from the rule configuration table based on the resource identifier information.
[0058] Optionally, before querying the rule configuration table from the database based on the customer identifier, the following steps are further included: determining a switching state of the data corresponding to the customer identifier; and if the switching state is in switching, discarding the to-be-processed business request and generating an error code.
[0059] The switching state is switching, switching completion and non-switching. The switching can be understood as that the data corresponding to the customer identifier is still in the process of migrating from the old system to the new system, that is, part of the data is migrated to the new system and another part of the data is still in the old system. The switching completion can be understood as that the data corresponding to the customer identifier has been completely migrated from the old system to the new system. The non-switching can be understood as that the data corresponding to the customer identifier is still in the old system. If the switching state is switching, the new system and the old system cannot process the business request, so the to-be-processed business request is discarded, and an error code is generated. If the switching state is switching completion or non-switching, the business request is distributed according to the determined target system.
[0060] The technical scheme of the embodiment comprises the following steps: obtaining a to-be-processed business request; wherein the to-be-processed business request comprises request header information, request body information, session information and a request message; analyzing the to-be-processed business request to obtain resource identifier information and an interface category; determining target information based on the interface category; wherein the target information is any one of the resource identifier information, the request header information, the request body information, the session information and the request message; determining a customer identifier according to the target information, and querying a rule configuration table from a database based on the customer identifier; determining a target system from the rule configuration table based on the resource identifier information, and sending the to-be-processed business request to the target system for processing. The business request distribution method provided in the embodiment determines the customer identifier from any one of the resource identifier information, the request header information, the request body information, the session information and the request message through the interface category parsed from the to-be-processed business request, determines the target system based on the customer identifier, associates the distribution of the business request with the customer identifier, and can accurately distribute the business request to the target system, thereby ensuring the normal processing of the business.
[0061] On the basis of the above embodiment, Figure 2 is a flowchart of a business request distribution method provided in the second embodiment of the application, as shown in Figure 2 The method comprises the following steps:
[0062] S201, obtaining a to-be-processed business request.
[0063] S202, analyzing the to-be-processed business request to obtain resource identifier information and an interface category.
[0064] S203, determining target information based on the interface category, and determining a customer identifier according to the target information.
[0065] S204, determining a switching state of data corresponding to the customer identifier.
[0066] S205, if the switching state is switching, discarding the to-be-processed business request and generating an error code.
[0067] S206, if the switching state is switching completion or no switching, querying a rule configuration table from a database based on a customer identifier.
[0068] S207, determining a transmission channel of the to-be-processed service request based on the resource identifier information.
[0069] S208, if the transmission channel is a preset channel, extracting real resource identifier information from the request message; and determining a target system from the rule configuration table based on the real resource identifier information.
[0070] S209, if the transmission channel is not the preset channel, determining the target system from the rule configuration table based on the resource identifier information.
[0071] S210, sending the to-be-processed service request to the target system for processing.
[0072] Figure 3 is a structural schematic diagram of a service request distribution device provided by an embodiment of the present application, as shown in the figure, the device comprises: Figure 3
[0073] a to-be-processed service request obtaining module 310, configured to obtain a to-be-processed service request; wherein the to-be-processed service request comprises request header information, request body information, session information and a request message;
[0074] a to-be-processed service request parsing module 320, configured to parse the to-be-processed service request to obtain resource identifier information and an interface category;
[0075] a target information determining module 330, configured to determine target information based on the interface category; wherein the target information is any one of the resource identifier information, the request header information, the request body information, the session information and the request message;
[0076] a customer identifier determining module 340, configured to determine a customer identifier according to the target information, and query a rule configuration table from a database based on the customer identifier;
[0077] a target system determining module 350, configured to determine a target system from the rule configuration table based on the resource identifier information, and send the to-be-processed service request to the target system for processing; wherein the target system is an old system or a new system.
[0078] Optionally, the target information determining module 330 is further configured to:
[0079] if the interface category is a first category, the determined target information is the request body information;
[0080] Optionally, the customer identifier determining module 340 is further configured to:
[0081] Extract data corresponding to the preset key field from the request body information to obtain the customer identifier.
[0082] Optionally, the target information determination module 330 is further configured to:
[0083] If the interface category is the second category, the determined target information is session information.
[0084] Optionally, the customer identifier determination module 340 is further configured to:
[0085] Extract data corresponding to the preset key field from the session information to obtain a first keyword.
[0086] Query the customer information according to the first keyword and the customer login information.
[0087] Parse the customer information to obtain the customer identifier.
[0088] Optionally, the target information determination module 330 is further configured to:
[0089] Determine the target information based on the interface category, including:
[0090] If the interface category is the third category, the determined target information is resource identifier information.
[0091] Optionally, the customer identifier determination module 340 is further configured to:
[0092] Perform path matching on the resource identifier information to obtain the customer identifier.
[0093] Optionally, the target information determination module 330 is further configured to:
[0094] If the interface category is the fourth category, the determined target information is request body information.
[0095] Optionally, the customer identifier determination module 340 is further configured to:
[0096] Extract data corresponding to the preset key field from the request body information.
[0097] Extract a set number of sub-data in a preset position from the data corresponding to the preset key field to obtain the customer identifier.
[0098] Optionally, the target information determination module 330 is further configured to:
[0099] If the interface category is the fifth category, the determined target information is a request message.
[0100] Optionally, the customer identifier determination module 340 is further configured to:
[0101] Decrypt the request message.
[0102] extracting data corresponding to the preset key field from the decrypted request message; wherein the data includes a second keyword and a database ID;
[0103] querying data corresponding to the second keyword from a database corresponding to the database ID to obtain a customer identifier.
[0104] Optionally, the method further comprises:
[0105] if the interface category is the sixth category or the eighth category, the determined target system is a new system;
[0106] if the interface category is the ninth category, the determined target system is an old system.
[0107] Optionally, the target information determination module 330 is further configured to:
[0108] if the interface category is the seventh category, the determined target information is the request message;
[0109] Optionally, the customer identifier determination module 340 is further configured to:
[0110] decrypting the request message;
[0111] extracting data corresponding to the preset key field from the decrypted request message to obtain the customer identifier.
[0112] Optionally, the target information determination module 330 is further configured to:
[0113] if the interface category is the tenth category, the determined target information is the request message;
[0114] Optionally, the customer identifier determination module 340 is further configured to:
[0115] extracting form data from the request message;
[0116] extracting data corresponding to the preset key field from the form data to obtain the customer identifier.
[0117] Optionally, the target information determination module 330 is further configured to:
[0118] if the interface category is the eleventh category, the determined target information is request header information;
[0119] Optionally, the customer identifier determination module 340 is further configured to:
[0120] obtaining a token ID from the request header information;
[0121] obtaining customer information from a database according to the token ID;
[0122] parsing the customer information to obtain the customer identifier.
[0123] Optionally, the target system determining module 350 is further configured to:
[0124] determine a transmission channel of the to-be-processed service request based on the resource identification information;
[0125] if the transmission channel is a preset channel, extract the real resource identification information from the request message;
[0126] determine the target system from the rule configuration table based on the real resource identification information.
[0127] Optionally, the apparatus further comprises a switching state determining module configured to:
[0128] determine a switching state of the data corresponding to the client identification; wherein the switching state is switching, switching completed, and not switched;
[0129] if the switching state is switching, discard the to-be-processed service request and generate an error code.
[0130] The apparatus can perform the method provided by all the foregoing embodiments of the application, and has the corresponding function modules and beneficial effects of performing the foregoing method. Technical details not described in the embodiment can be referred to the method provided by all the foregoing embodiments of the application.
[0131] Figure 4 A structural diagram of an electronic device 10 that can be used to implement embodiments of the application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit the inventiveness in any way.
[0132] As Figure 4As shown, the electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., connected to the at least one processor 11 in communication. The memory stores computer programs executable by the at least one processor 11, and the processor 11 can perform various appropriate actions and processes according to the computer programs stored in the read-only memory (ROM) 12 or loaded into the random access memory (RAM) 13 from the storage unit 18. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0133] Various components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc., an output unit 17, such as various types of displays, a speaker, etc., a storage unit 18, such as a magnetic disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.
[0134] The processor 11 can be various general and / or special-purpose processing components having processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as the distribution method of service requests.
[0135] In some embodiments, the distribution method of service requests can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the distribution method of service requests described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the distribution method of service requests by any other appropriate means, such as by means of firmware.
[0136] The various embodiments of the systems and techniques described above can be implemented in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
[0137] Computer programs used to implement the processes of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer program
[0138] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store computer programs for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0139] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.
[0140] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), blockchain network, and the Internet.
[0141] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. A server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.
[0142] The embodiments of the present application further provide a computer program product, comprising a computer program which, when executed by a processor, implements the method for distributing a service request as provided in any of the embodiments of the present application.
[0143] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).
[0144] It is to be understood that the above description is merely a preferred embodiment of the application and the applied technical principles. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, modifications and substitutions can be made without departing from the scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims
1. A method for distributing business requests, characterized in that, include: Obtain pending business requests; wherein, the pending business requests include request header information, request body information, session information, and request message; The pending business request is parsed to obtain resource identification information and interface category; The target information is determined based on the interface category; wherein, the target information is any one of the resource identification information, the request header information, the request body information, the session information, and the request message; The customer identifier is determined based on the target information, and the rule configuration table is queried from the database based on the customer identifier; The target system is determined from the rule configuration table based on the resource identification information, and the pending business request is sent to the target system for processing; wherein the target system is an old system or a new system.
2. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the first category, then the determined target information is the request body information; Accordingly, the customer identifier is determined based on the target information, including: Extract the data corresponding to the preset key fields from the request body information to obtain the customer identifier.
3. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the second category, then the determined target information is session information; Accordingly, the customer identifier is determined based on the target information, including: Extract data corresponding to preset key fields from the session information to obtain the first keyword; Query customer information based on the first keyword and customer login information; The customer information is parsed to obtain the customer identifier.
4. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: Determining target information based on the interface category includes: If the interface category is the third category, then the determined target information is resource identification information; Accordingly, the customer identifier is determined based on the target information, including: The resource identification information is used for path matching to obtain the customer identification.
5. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the fourth category, then the determined target information is the request body information; Accordingly, the customer identifier is determined based on the target information, including: Extract data corresponding to preset key fields from the request body information; The customer identifier is obtained by extracting a set number of sub-data at a preset position from the data corresponding to the preset key fields.
6. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the fifth category, then the determined target information is a request message; Accordingly, the customer identifier is determined based on the target information, including: Decrypt the request message; Extract data corresponding to preset key fields from the decrypted request message; wherein, the data includes a second keyword and a database ID; The customer identifier is obtained by querying the data corresponding to the second keyword from the database corresponding to the database ID.
7. The method according to claim 1, characterized in that, Also includes: If the interface category is the sixth or eighth category, then the target system is determined to be a new system; If the interface category is the ninth category, then the target system is the old system.
8. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the seventh category, then the determined target information is a request message; Accordingly, the customer identifier is determined based on the target information, including: Decrypt the request message; Extract the data corresponding to the preset key fields from the decrypted request message to obtain the customer identifier.
9. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the tenth category, then the determined target information is a request message; Accordingly, the customer identifier is determined based on the target information, including: Extract form data from the request message; Extract the data corresponding to the preset key fields from the form data to obtain the customer identifier.
10. The method according to claim 1, characterized in that, Determining target information based on the interface category includes: If the interface category is the eleventh category, then the determined target information is the request header information; Accordingly, the customer identifier is determined based on the target information, including: Obtain the token ID from the request header information; Retrieve customer information from the database based on the token ID; The customer information is parsed to obtain the customer identifier.
11. The method according to claim 1, characterized in that, Determining the target system from the rule configuration table based on the resource identification information includes: The transmission channel for the pending service request is determined based on the resource identification information; If the transmission channel is a preset channel, then extract the real resource identifier information from the request message; The target system is determined from the rule configuration table based on the real resource identification information.
12. The method according to claim 1, characterized in that, Before querying the rule configuration table from the database based on the customer identifier, the process also includes: Determine the switching status of the data corresponding to the customer identifier; wherein the switching status is in progress, switching completed, or not switched. If the switching status is in progress, the pending service request is discarded and an error code is generated.
13. A service request distribution device, characterized in that, include: The pending business request acquisition module is used to acquire pending business requests; wherein, the pending business request includes request header information, request body information, session information and request message; The pending business request parsing module is used to parse the pending business requests to obtain resource identification information and interface categories; The target information determination module is used to determine target information based on the interface category; wherein, the target information is any one of the resource identification information, the request header information, the request body information, the session information, and the request message; The customer identifier determination module is used to determine the customer identifier based on the target information and query the rule configuration table from the database based on the customer identifier; The target system determination module is used to determine the target system from the rule configuration table based on the resource identification information, and send the pending business request to the target system for processing; wherein the target system is an old system or a new system.
14. An electronic device, characterized in that, The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements a method for distributing service requests as described in any one of claims 1-12.
15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the service request distribution method as described in any one of claims 1-12.
16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the service request distribution method as described in any one of claims 1-12.
Citation Information
Patent Citations
Data synchronization method, device and system
CN114900531A
Data processing method and device
CN116233244A