Method for parallel gray shunting of new and old applications in a financial scenario and computer device
By leveraging the self-built canary processing capabilities of gateways in financial scenarios, fine-grained traffic separation between new and old applications is achieved, solving the problem of business transmission needs that existing technologies cannot effectively address, and providing higher business assurance and smoother traffic switching.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- PING AN BANK CO LTD
- Filing Date
- 2023-04-07
- Publication Date
- 2026-05-19
AI Technical Summary
In financial scenarios, existing technologies struggle to achieve fine-grained traffic separation between old and new applications, especially when all transmitted business messages are encrypted. This makes it difficult to effectively address the traffic separation needs of business transmission.
By acquiring patented technology, it can be found that existing technologies cannot effectively solve the technical problems of transmission services, nor can they effectively meet the needs of transmission services.
It enables fine-grained traffic splitting between old and new applications in financial scenarios, providing higher business security without changing the customer's interface contract. Traffic is split through the gateway, enabling a smooth switch between old and new application traffic.
Smart Images
Figure CN116418874B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of financial technology, and in particular to a method for parallel gray-scale separation of new and old applications in financial scenarios, a system and computer equipment for parallel gray-scale separation of new and old applications in financial scenarios. Background Technology
[0002] A canary release, also known as a phased rollout, refers to a release method that allows for a smooth transition between the old and new versions. It's most commonly encountered during system refactoring, where the old system needs to remain unchanged, but user traffic needs to be gradually and seamlessly distributed to the new application system. Ideally, this process should be uninterrupted and imperceptible to users. Common server-side canary releases are categorized into compatibility-based and incompatibility-based canary releases.
[0003] The compatibility change canary rollout is as follows: Physical canary rollout: Traffic splitting rules are configured on the server load balancer (SLB). Traffic can be split according to rules such as request address and request header parameters (e.g., city, channel), distributing a portion of the traffic to the new application. Once all the old traffic has been distributed to the new application, the old application can be taken offline.
[0004] The incompatible change grayscale refers to changes that alter the current interface contract or functionality, such as changes to the interface's request fields, response fields, or URL, resulting in incompatibility with previous services. A common practice is to introduce interface version numbers, allowing both old and new versions to coexist, such as / v1 / api and / v2 / api. The requesting party uses version / v2 / api, and after a period of stability (which could be one day or several months, depending on system stability requirements), version / v1 / api can be removed.
[0005] However, the services provided by banks to their partners need to ensure stability and service compatibility. Option 2, which addresses incompatibility, requires notifying all partners to upgrade, resulting in a large workload and significant risk. Option 1, a physical gray-scale approach, addresses the shortcomings of Option 2; however, it may not be suitable for many banking scenarios, such as when all incoming business messages are encrypted. In such cases, Option 1 cannot perform fine-grained traffic splitting, as it can only split traffic based on limited dimensions, failing to meet the requirements. Summary of the Invention
[0006] In view of this, it is necessary to provide a more convenient and intelligent method for parallel gray-scale separation of new and old applications in financial scenarios, as well as a system and computer equipment for parallel gray-scale separation of new and old applications in financial scenarios.
[0007] Firstly, embodiments of this application provide a method for parallel gray-scale distribution of new and old applications in a financial scenario. The method includes the following steps:
[0008] Obtain grayscale traffic requests, wherein the grayscale traffic requests contain financial feature tags;
[0009] Determine whether the grayscale traffic request switch is turned on, whereby the grayscale traffic request switch determines whether to accept grayscale traffic requests.
[0010] When the grayscale traffic request switch is turned on, it is determined whether each grayscale traffic request is encrypted;
[0011] When the grayscale traffic request is encrypted, the grayscale traffic request is decrypted to obtain the decrypted grayscale traffic request;
[0012] The decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests are colored to obtain each grayscale traffic request with a specific label;
[0013] Match each grayscale traffic request with its specific tag and the corresponding preset grayscale rules;
[0014] Once a match is successful, each grayscale traffic request will be split and forwarded to obtain the corresponding grayscale data.
[0015] When a match fails, each grayscale traffic request is forwarded to the production environment to obtain the corresponding production data.
[0016] Secondly, embodiments of this application provide a system for parallel gray-scale distribution of new and old applications in a financial scenario. Specifically, the system for parallel gray-scale distribution of new and old applications in a financial scenario includes:
[0017] Management backend;
[0018] Gateway, including:
[0019] The interception module is used to intercept all gray-scale traffic requests to access the service;
[0020] The access module is used to access the management backend to determine whether the gray-scale traffic request switch has been turned on, and the gray-scale traffic request switch is for whether to accept gray-scale traffic requests.
[0021] The detection module is used to detect whether the intercepted grayscale traffic requests are encrypted when the grayscale traffic request switch is turned on.
[0022] The decryption module is used to decrypt the gray-scale traffic request to obtain the decrypted gray-scale traffic request when the gray-scale traffic request is encrypted.
[0023] The coloring module is used to color the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific label.
[0024] The matching module is used to match each grayscale traffic request with a specific tag based on a preset grayscale rule.
[0025] The first forwarding module is used to forward each grayscale traffic request to obtain the corresponding grayscale data according to the preset grayscale rules after a successful match.
[0026] The second forwarding module is used to forward each grayscale traffic request to the production environment to obtain the corresponding production data when the matching fails.
[0027] Thirdly, embodiments of this application provide a computer device, the computer device comprising: a computer-readable storage medium for storing program instructions, a processor, and a bus for executing the program instructions to implement the above-described method for parallel gray-scale separation of new and old applications in a financial scenario.
[0028] The aforementioned method, system, and computer equipment for parallel gray-scale traffic splitting of new and old applications in financial scenarios, by building gray-scale processing capabilities on the gateway, can switch traffic between new and old applications according to actual business needs. It can also distribute request traffic in a fine-grained manner based on corresponding feature tags to provide more guarantees during service switching, without changing the interface contract with customers. Traffic splitting is achieved through the gateway, thereby realizing the switching of traffic between new and old applications. Attached Figure Description
[0029] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.
[0030] Figure 1 The flowchart illustrates a method for parallel grayscale splitting of new and old applications in a financial scenario, as provided in this application embodiment.
[0031] Figure 2 This is the first sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the embodiments of this application.
[0032] Figure 3 This is the second sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the embodiments of this application.
[0033] Figure 4 The flowchart illustrates a method for parallel grayscale splitting of new and old applications in a financial scenario, as provided in the second embodiment of this application.
[0034] Figure 5 This is the first sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the second embodiment of this application.
[0035] Figure 6 This is a second sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the second embodiment of this application.
[0036] Figure 7 This is the third sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the second embodiment of this application.
[0037] Figure 8 The fourth sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the second embodiment of this application.
[0038] Figure 9 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application.
[0039] Figure 10 This is a schematic diagram of a system for parallel grayscale separation of new and old applications in a financial scenario, provided as a second embodiment of this application.
[0040] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0041] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.
[0042] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar planned objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data are interchangeable where appropriate; in other words, the described embodiments are implemented according to a sequence other than that illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, may also include other content; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0043] It should be noted that the use of terms such as "first" and "second" in this application is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.
[0044] Please refer to the following: Figure 1 and Figure 10 , Figure 1 The flowchart illustrates a method for parallel grayscale splitting of new and old applications in a financial scenario, as provided in this application embodiment. Figure 10 This is a schematic diagram of a system for parallel gray-scale traffic splitting of new and old applications in a financial scenario, provided in an embodiment of this application. The system 1000 for parallel gray-scale traffic splitting of new and old applications in a financial scenario specifically includes: a management backend 100 and a gateway 200. The gateway 200 specifically includes: an interception module 201, an access module 202, a detection module 203, a decryption module 204, a coloring module 205, a matching module 206, a first forwarding module 207, and a second forwarding module 208. The interception module 201 is used to intercept all gray-scale traffic requests accessing the service. The access module 202 is used to access the management backend 100 to determine whether the gray-scale traffic request switch is enabled, whereby the gray-scale traffic request switch determines whether to accept gray-scale traffic requests. The detection module 203 is used to detect whether the intercepted gray-scale traffic requests are encrypted when the gray-scale traffic request switch is enabled. The decryption module 204 is used to decrypt the gray-scale traffic requests when they are encrypted, obtaining the decrypted gray-scale traffic requests. The coloring module 205 is used to color the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific tag. The matching module 206 is used to match each grayscale traffic request with the specific tag according to a preset grayscale rule. The first forwarding module 207 is used to forward each grayscale traffic request to obtain the corresponding grayscale data according to the preset grayscale rule when the match is successful. The second forwarding module 208 is used to forward each grayscale traffic request to the production environment to obtain the corresponding production data when the match fails. Specifically, the method for parallel grayscale traffic splitting of new and old applications in a financial scenario includes the following steps S102-S116.
[0045] Step S102: Obtain a grayscale traffic request, which includes a financial feature tag. Understandably, the user adds corresponding grayscale processing capabilities to the gateway 200, i.e., sets corresponding traffic distribution tags on the gateway 200. These traffic distribution tags can be used to identify financial feature tags, traffic distribution rules, and classification addresses. The traffic distribution address is a service address pre-set on the gateway 200 to access certain data when an external user wants to obtain grayscale data. When an external user wants to obtain grayscale data, it will send a corresponding grayscale traffic request to the gateway 200. The gateway 200 confirms the purpose of the grayscale traffic request based on the traffic distribution tag in the request header or request content.
[0046] Step S104: Determine whether the grayscale traffic request switch is enabled. The grayscale traffic request switch determines whether grayscale traffic requests are accepted. Understandably, when the gateway 200 receives the grayscale request traffic, it will pre-set whether the corresponding service enables grayscale traffic requests to confirm whether certain users can access grayscale data.
[0047] Step S106: When the grayscale traffic request switch is turned on, determine whether each grayscale traffic request is encrypted. Understandably, when the gateway 200 determines that the service accessed by the grayscale traffic request has the grayscale traffic request switch enabled, it begins processing the intercepted grayscale traffic requests. The gateway 200 first confirms whether the request content of the grayscale traffic request is encrypted.
[0048] Step S108: When the grayscale traffic request is encrypted, the grayscale traffic request is decrypted to obtain the decrypted grayscale traffic request. Understandably, when the grayscale traffic request is encrypted, the gateway 200 needs to decrypt it first to obtain the content of the grayscale traffic request. The gateway 200 will load the corresponding key according to the service corresponding to the grayscale traffic request, and decrypt the grayscale traffic request according to the obtained key to obtain the decrypted grayscale traffic request.
[0049] Step S110 involves coloring the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific tag. Understandably, if the grayscale traffic data obtained by the gateway 200 is unencrypted or the encrypted grayscale traffic data has been successfully decrypted, the content in the grayscale traffic data is identified, and coloring is performed according to preset rules in the grayscale traffic data to obtain each grayscale traffic request with a specific tag.
[0050] Step S112: Match each grayscale traffic request with a specific tag and the corresponding preset grayscale rule. Understandably, the gateway 200 matches each grayscale traffic request with the corresponding grayscale rule for the service accessed by the grayscale traffic request, based on the specific tag on that request.
[0051] Step S114: After a successful match, each grayscale traffic request is split and forwarded to obtain the corresponding grayscale data. Understandably, according to step S112, after a grayscale traffic request is successfully matched, the gateway 200 will obtain the address of the service to be accessed by the grayscale traffic request and forward the grayscale traffic request according to the address, thereby enabling the grayscale traffic request to obtain the corresponding grayscale data.
[0052] Step S116: When a match fails, each grayscale traffic request is forwarded to the production environment to obtain the corresponding production data. Understandably, according to step S112, when a grayscale traffic request fails to match, the gateway 200 will provide the address of the production environment of the service requested by the grayscale traffic request and forward the grayscale traffic request from the grayscale environment to the production environment of the corresponding service to obtain the corresponding production data.
[0053] In the above embodiments, by building a canary processing capability on the gateway 200, the traffic can be switched between old and new applications according to the actual business. It can also distribute request traffic in a fine-grained manner according to the corresponding feature tags to provide more protection when switching services, without changing the interface contract with the customer. The traffic is split through the gateway 200 to achieve the switching of traffic between old and new applications.
[0054] Please refer to the following: Figure 2 This is the first sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the embodiments of this application. Step S108 specifically includes the following steps S202-S208.
[0055] Step S202: Determine whether the grayscale traffic request requires identity verification. Understandably, after obtaining the grayscale traffic request, the gateway 200 first determines whether the grayscale traffic request requires identity authentication.
[0056] Step S204: When identity verification is required, the grayscale traffic request is authenticated to obtain the verification result. Understandably, if the gateway 200 finds that the content of the grayscale traffic request cannot be obtained, it determines that the grayscale traffic request requires identity verification before its content can be obtained. Therefore, the gateway 200 first performs mutual authentication with the external server corresponding to the grayscale traffic request.
[0057] Step S206: When the verification result is successful, obtain the key corresponding to the APPID in the grayscale traffic request. Understandably, after the gateway 200 and the external server successfully verify each other, the gateway 200 obtains the key corresponding to the APPID of the grayscale traffic request based on the content of the grayscale traffic request.
[0058] Step S208: Decrypt the decrypted grayscale traffic request using the key to obtain the decrypted grayscale traffic request. Understandably, the gateway 200 decrypts the grayscale traffic request using the obtained key to obtain the decrypted grayscale traffic request.
[0059] Please refer to the following: Figure 3 This is the second sub-flowchart of the method for parallel gray-scale splitting of new and old applications in a financial scenario provided in the embodiments of this application. The method for parallel gray-scale splitting of new and old applications in a financial scenario further includes the following steps S302-S304.
[0060] Step S302: Detect whether the grayscale traffic request carries a specific traffic marker, where the specific traffic marker is obtained after splitting the grayscale traffic request. Understandably, if the grayscale traffic request carries a specific traffic marker, it means that the grayscale traffic request has already been split and does not need to be processed again to avoid entering an infinite loop.
[0061] Step S304: When the grayscale traffic request carries a specific traffic marker, the corresponding data is obtained directly based on the content of the grayscale traffic request. It can be understood that when the gateway 200 receives a grayscale traffic request with a specific traffic marker, the gateway 200 does not process it, but directly forwards it according to the content of the grayscale traffic request to ensure that the grayscale traffic request obtains the corresponding data.
[0062] Please refer to the following: Figure 4 This is a flowchart of a method for parallel grayscale splitting of new and old applications in a financial scenario, provided in the second embodiment of this application. The method for parallel grayscale splitting of new and old applications in a financial scenario further includes the following steps S402-S416.
[0063] In step S402, gateway 200 intercepts all gray-scale traffic requests to access the service. Understandably, all external requests must first pass through gateway 200 to access the corresponding data. When an external request arrives, gateway 200 intercepts the request for verification.
[0064] In step S404, the gateway 200 accesses the management backend 100 to determine whether the gray-scale traffic request switch has been enabled. The gray-scale traffic request switch determines whether gray-scale traffic requests are accepted. Understandably, the user controls whether each corresponding service accepts gray-scale traffic requests in the management backend 100. When a service can accept gray-scale traffic requests, the user will enable or disable gray-scale access for that service in the management backend 100.
[0065] Step S406: When the grayscale traffic request switch is turned on, the gateway 200 will detect whether the intercepted grayscale traffic requests are encrypted. Understandably, when the management backend 100 sends a message informing the gateway 200 that the grayscale traffic request switch has been turned on, the gateway 200 will begin to determine whether the corresponding intercepted grayscale traffic requests are encrypted.
[0066] In step S408, when the grayscale traffic request is encrypted, the gateway 200 decrypts the grayscale traffic request to obtain the decrypted grayscale traffic request. Understandably, when the grayscale traffic request is encrypted, the gateway 200 needs to decrypt it first to obtain the content of the grayscale traffic request. The gateway 200 will load the corresponding key according to the service corresponding to the grayscale traffic request, and decrypt the grayscale traffic request according to the obtained key to obtain the decrypted grayscale traffic request.
[0067] In step S410, the gateway 200 colors the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific tag. Understandably, if the grayscale traffic data obtained by the gateway 200 is unencrypted or the encrypted grayscale traffic data has been successfully decrypted, the gateway 200 identifies the content in the grayscale traffic data and colors it according to preset rules in the grayscale traffic data to obtain each grayscale traffic request with a specific tag.
[0068] In step S412, the gateway 200 matches each grayscale traffic request with a specific tag according to a preset grayscale rule. It can be understood that the gateway 200 matches each grayscale traffic request with the corresponding grayscale rule for the service accessed by the grayscale traffic request, based on the specific tag on that request.
[0069] In step S414, after a successful match, the gateway 200 forwards each grayscale traffic request according to a preset grayscale rule to obtain the corresponding grayscale data. Understandably, according to step S412, after a successful match, the gateway 200 obtains the address of the service to be accessed by the grayscale traffic request and forwards the grayscale traffic request according to the address, thereby enabling the grayscale traffic request to obtain the corresponding grayscale data.
[0070] In step S416, when a match fails, the gateway 200 forwards each grayscale traffic request to the production environment to obtain the corresponding production data. Understandably, according to step S412, when a grayscale traffic request fails to match, the gateway 200 obtains the address of the production environment for the service requested by the grayscale traffic request and forwards the grayscale traffic request from the grayscale environment to the production environment of the corresponding service to obtain the corresponding production data.
[0071] Please refer to the following: Figure 5 This is the first sub-flowchart of the method for parallel grayscale splitting of new and old applications in a financial scenario provided in the second embodiment of this application. Step S402 specifically includes the following steps S502-S504.
[0072] In step S502, the management backend 100 responds to the user's operation, configuring the corresponding traffic splitting label, traffic splitting rules, traffic splitting address, and whether decryption processing is required. The traffic splitting label is a financial feature label, the traffic splitting rules are rules for hitting grayscale requests and rules for traffic splitting control, and the traffic splitting address is the receiving address for receiving the grayscale traffic request after hitting the grayscale rules. It can be understood that the user configures the management backend 100 according to the gateway 200 corresponding to each service, based on their needs. The user is now making pre-sets in the management backend 100, that is, the user sets the corresponding obtainable traffic splitting label, traffic splitting rules, and service address for each service in the management backend 100, as well as whether to enable the decryption function. Specifically, the traffic splitting label is based on tags such as the business support user openId, user bank customer number, merchant Id, application Id, URL, user account Id, and user device Id. In this embodiment, the traffic splitting rules are per-transaction traffic splitting and percentage-based traffic splitting, and a traffic splitting threshold is set for each rule for control. The term "per-transaction splitting" means that if there are 10 per-transaction splitting requests, only 10 grayscale traffic requests will be accepted.
[0073] In step S504, the management backend 100 pushes the successfully configured content to the gateway 200 for saving and application. Understandably, after the user successfully configures the settings on the management backend 100, the management backend 100 automatically pushes the configured content to the corresponding gateway 200, and the gateway 200 automatically saves and applies the configuration information upon receiving it.
[0074] Please refer to the following: Figure 6 This is the second sub-flowchart of the method for parallel gray-scale splitting of new and old applications in a financial scenario provided in the second embodiment of this application. The method for parallel gray-scale splitting of new and old applications in a financial scenario further includes the following steps S602-S608.
[0075] In step S602, the gateway 200 determines whether the intercepted grayscale traffic request is an encrypted request and carries the financial feature tag. Understandably, when the external grayscale request accesses the corresponding service, the gateway 200 corresponding to the service intercepts the grayscale traffic request, identifies the financial feature tag in the grayscale traffic request header, and determines whether the content of the grayscale traffic request is encrypted.
[0076] In step S604, when the grayscale traffic request is an encrypted request and carries the financial feature tag, the gateway 200 first decrypts the grayscale traffic request to obtain the decrypted grayscale traffic. Understandably, when the gateway 200 identifies from the header of the grayscale traffic request that the grayscale traffic request carries a financial tag and the request content is encrypted, the gateway 200 first decrypts it to obtain the decrypted grayscale traffic and the content of the grayscale traffic request. The financial feature tag in the grayscale traffic request header corresponds to the application ID, but the financial feature tag in the grayscale traffic request content corresponds to the routing tag stored in the gateway 200.
[0077] In step S606, the gateway 200 colors the grayscale traffic request according to the financial feature tag on the grayscale traffic request. Understandably, the gateway 200 identifies the financial attributes in the grayscale traffic request content and colors it according to the identified financial attributes and the traffic splitting rules in the grayscale traffic request.
[0078] In step S608, when the grayscale traffic request is not an encrypted request but carries the financial feature tag, the gateway 200 directly colors the grayscale traffic request based on the financial feature tag. It can be understood that when the grayscale traffic request is not encrypted, the gateway 200 directly identifies the financial feature tag in the grayscale traffic request content to color the traffic.
[0079] Please refer to the following: Figure 7 This is the third sub-flowchart of the method for parallel gray-scale splitting of new and old applications in a financial scenario provided in the second embodiment of this application. The method for parallel gray-scale splitting of new and old applications in a financial scenario further includes the following steps S702-S704.
[0080] In step S702, the gateway 200 obtains the routing address corresponding to each successfully matched grayscale traffic request. The gateway 200 stores the access connection address of the corresponding service. When a match is successful, the gateway 200 will automatically retrieve the corresponding connection address, i.e., the routing address, according to the successfully matched service.
[0081] In step S704, the gateway 200 forwards the grayscale traffic request according to the routing address. Understandably, the gateway 200 forwards the successfully matched grayscale traffic request according to the retrieved address so that the grayscale traffic request can reach the service.
[0082] Please refer to the following: Figure 8 This is the fourth sub-flowchart of the method for parallel gray-scale splitting of new and old applications in a financial scenario provided in the second embodiment of this application. The method for parallel gray-scale splitting of new and old applications in a financial scenario further includes the following steps S802-S804.
[0083] In step S802, the gateway 200 intercepts the grayscale traffic request to detect whether the grayscale traffic request contains a specific traffic marker. The specific traffic marker is obtained after the grayscale traffic request has undergone traffic splitting. It can be understood that if the grayscale traffic request has a specific traffic marker, it means that the grayscale traffic request has already been split and does not need to be further processed, thus avoiding an infinite loop.
[0084] In step S804, when the gateway 200 detects that the grayscale traffic request has a specific traffic marker, the gateway 200 directly forwards the request to obtain the corresponding data based on the address in the grayscale traffic request. It can be understood that when the gateway 200 receives a grayscale traffic request with a specific traffic marker, the gateway 200 does not process it, but directly forwards the request according to its content to ensure that the grayscale traffic request obtains the corresponding data.
[0085] Please refer to the following: Figure 9This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. The computer device 10 includes a computer-readable storage medium 11, a processor 12, and a bus 13. The computer-readable storage medium 11 includes at least one type of readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the computer-readable storage medium 11 can be an internal storage unit of the computer device 10, such as the hard disk of the computer device 10. In other embodiments, the computer-readable storage medium 11 can also be an external storage device of the computer device 10, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 10. Furthermore, the computer-readable storage medium 11 can include both internal storage units and external storage devices of the computer device 10. The computer-readable storage medium 11 can be used not only to store application software and various types of data installed on the computer device 10, but also to temporarily store data that has been output or will be output.
[0086] Bus 13 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0087] Furthermore, the computer device 10 may also include a display component 14. The display component 14 may be a light-emitting diode (LED) display, a liquid crystal display, a touch-sensitive liquid crystal display, or an organic light-emitting diode (OLED) touchscreen, etc. The display component 14 may also be appropriately referred to as a display device or display unit, used to display information processed in the computer device 10 and to display a visual user interface.
[0088] Furthermore, the computer device 10 may also include a communication component 15. The communication component 15 may optionally include a wired communication component and / or a wireless communication component, such as a Wi-Fi communication component, a Bluetooth communication component, etc., which are typically used to establish a communication connection between the computer device 10 and other intelligent control devices.
[0089] In some embodiments, processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, used to run program code stored in computer-readable storage medium 11 or process data. Specifically, processor 12 executes a processing program to control computer device 10 to implement a method for parallel grayscale separation of new and old applications in a financial scenario.
[0090] Understandably, Figure 9 Only a computer device 10 with components 11-15 and a method for parallel grayscale splitting of new and old applications in a financial scenario is shown. Those skilled in the art will understand that... Figure 9 The structure shown does not constitute a limitation on the computer device 10 and may include fewer or more components than shown, or combine certain components, or have different component arrangements.
[0091] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
[0092] The above-listed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.
Claims
1. A method for parallel gray-scale separation of new and old applications in a financial scenario, characterized in that, The method for parallel gray-scale separation of new and old applications in financial scenarios includes: Obtain grayscale traffic requests, wherein the grayscale traffic requests contain financial feature tags, and the gateway is equipped with corresponding grayscale processing capabilities, wherein the financial feature tags are multi-dimensional identifiers based on financial business attributes; Determine whether the grayscale traffic request switch is turned on, whereby the grayscale traffic request switch determines whether to accept grayscale traffic requests. When the grayscale traffic request switch is turned on, it is determined whether each grayscale traffic request is encrypted; When the grayscale traffic request is encrypted, the grayscale traffic request is decrypted to obtain the decrypted grayscale traffic request; The decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests are colored to obtain each grayscale traffic request with a specific label; Match each grayscale traffic request with its specific tag and the corresponding preset grayscale rules; Once a match is successful, each grayscale traffic request will be split and forwarded to obtain the corresponding grayscale data. When a match fails, each grayscale traffic request is forwarded to the production environment to obtain the corresponding production data.
2. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 1, characterized in that, When the grayscale traffic request is encrypted, the process of decrypting the grayscale traffic request to obtain the decrypted grayscale traffic request specifically includes: Determine whether the grayscale traffic request requires identity verification; When identity verification is required, the grayscale traffic request is authenticated to obtain the verification result; When the verification result is successful, the key corresponding to the APPID in the gray-scale traffic request is obtained; The decrypted grayscale traffic request is decrypted using the key to obtain the decrypted grayscale traffic request.
3. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 1, characterized in that, The method further includes: Detect whether the grayscale traffic request has a specific traffic tag, the specific traffic tag being obtained after splitting the grayscale traffic request; When the grayscale traffic request carries a specific traffic tag, the corresponding data is obtained directly based on the content of the grayscale traffic request.
4. A method for parallel gray-scale separation of new and old applications in a financial scenario, characterized in that, The method for parallel gray-scale separation of new and old applications in financial scenarios also includes: The gateway intercepts all gray-scale traffic requests to access the service. The gateway accesses the management backend to determine whether the gray-scale traffic request switch has been turned on, and the gray-scale traffic request switch is for whether to accept gray-scale traffic requests; When the grayscale traffic request switch is turned on, the gateway will detect whether the intercepted grayscale traffic requests are encrypted; When the grayscale traffic request is encrypted, the gateway decrypts the grayscale traffic request to obtain the decrypted grayscale traffic request; The gateway colors the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific label. The gateway matches each grayscale traffic request with a specific tag according to a preset grayscale rule; Once a match is successful, the gateway forwards each grayscale traffic request according to the preset grayscale rules to obtain the corresponding grayscale data. When a match fails, the gateway forwards each grayscale traffic request to the production environment to obtain the corresponding production data.
5. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 4, characterized in that, Before the gateway intercepts all gray-scale traffic requests to access the service, it specifically includes: The management backend responds to user operations, configuring corresponding traffic splitting labels, traffic splitting rules, traffic splitting addresses, and whether decryption processing is required. The traffic splitting labels are financial feature labels, the traffic splitting rules are rules for hitting grayscale requests and rules for traffic splitting control, and the traffic splitting address is the receiving address for receiving the grayscale traffic request after hitting the grayscale rules. The management backend will push the successfully configured content to the gateway for saving and application.
6. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 5, characterized in that, The method further includes: The gateway determines whether the intercepted grayscale traffic request is a ciphertext request and carries the financial feature tag; When the grayscale traffic request is an encrypted request and carries the financial feature tag, the gateway first decrypts the grayscale traffic request to obtain the decrypted grayscale traffic. The gateway performs traffic coloring on the grayscale traffic request based on the financial feature tag on the grayscale traffic request; When the grayscale traffic request is not a ciphertext request but carries the financial feature tag, the gateway directly performs traffic coloring on the grayscale traffic request based on the financial feature tag.
7. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 5, characterized in that, The method further includes: The gateway obtains the routing address corresponding to each grayscale traffic request after a successful match; The gateway forwards the grayscale traffic requests according to the routing address.
8. The method for parallel gray-scale separation of new and old applications in a financial scenario as described in claim 4, characterized in that, The method further includes: The gateway intercepts the grayscale traffic request to detect whether the grayscale traffic request contains a specific traffic marker, which is obtained after the grayscale traffic request is split into multiple traffic streams. When the gateway detects that the grayscale traffic request has a specific traffic tag, the gateway directly forwards the request to obtain the corresponding data based on the address in the grayscale traffic request.
9. A system for parallel gray-scale separation of new and old applications in a financial scenario, characterized in that, The system for parallel gray-scale separation of new and old applications in a financial scenario specifically includes: Management backend; Gateway, including: The interception module is used to intercept all gray-scale traffic requests to access the service; The access module is used to access the management backend to determine whether the gray-scale traffic request switch has been turned on, and the gray-scale traffic request switch is for whether to accept gray-scale traffic requests. The detection module is used to detect whether the intercepted grayscale traffic requests are encrypted when the grayscale traffic request switch is turned on. The decryption module is used to decrypt the gray-scale traffic request to obtain the decrypted gray-scale traffic request when the gray-scale traffic request is encrypted. The coloring module is used to color the decrypted grayscale traffic requests and / or unencrypted grayscale traffic requests to obtain each grayscale traffic request with a specific label. The matching module is used to match each grayscale traffic request with a specific tag based on a preset grayscale rule. The first forwarding module is used to forward each grayscale traffic request to obtain the corresponding grayscale data according to the preset grayscale rules after a successful match. The second forwarding module is used to forward each grayscale traffic request to the production environment to obtain the corresponding production data when the matching fails.
10. A computer device, characterized in that, The computer equipment specifically includes: A computer-readable storage medium for storing program instructions; and The method for processing and executing the program instructions to implement the parallel grayscale splitting of new and old applications in a financial scenario as described in any one of claims 1 to 8 is described in this article.