Service request redirection method and system, storage medium and program product

Abstract

The invention provides a service request redirection method and system, a storage medium and a program product, which can be applied to the field of financial science and technology. The method comprises the steps that under the condition that a service request is detected, the service request is intercepted, and the service request is information which is initiated by a control end and requests a first old server to execute a service; analyzing the service request, and determining an interface identifier of a first old server side and a version number of a control side; according to the interface identifier and the version number, determining an interface address of the new server, and performing parameter rewriting on the service request, so that the rewritten service request conforms to an interface specification of the new server; and according to the interface address of the new server side, sending the rewritten service request to the new server side, so that the new server side executes the service. According to the method, the problem of poor user experience caused by a hard coding forced upgrading strategy is solved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a method for redirecting service requests, a computer-readable storage medium, and a system for redirecting requests for computer program products and services. Background Technology

[0002] In the current mobile financial application field, with the rapid iteration of technology, bank applications (APPs) need to be frequently updated to adapt to new business needs and technological advancements. Currently, a common strategy is to hard-code mandatory upgrades, forcing users to upgrade their APP versions to match new service interfaces. While this strategy can ensure that all users receive the latest version of the APP in a timely manner to some extent, it often comes at the cost of user experience, especially for users who cannot upgrade immediately or easily due to various reasons (such as limited network access, insufficient mobile storage space, or outdated devices), thus causing user churn. Summary of the Invention

[0003] The main objective of this application is to provide a method for redirecting service requests, a computer-readable storage medium, and a system for redirecting requests for computer program products and services, so as to at least solve the problem of poor user experience caused by hard-coded forced upgrade strategies in the prior art.

[0004] To achieve the above objectives, according to one aspect of this application, a method for redirecting service requests is provided, comprising: upon detecting a service request, intercepting the service request, wherein the service request is a request initiated by a control terminal to request information from a first old server to perform a service; parsing the service request to determine the interface identifier of the first old server and the version number of the control terminal; determining the interface address of a new server based on the interface identifier and the version number and rewriting the parameters of the service request so that the rewritten service request conforms to the interface specification of the new server; and sending the rewritten service request to the new server based on the interface address of the new server, so that the new server performs the service.

[0005] In some embodiments, after determining the interface address of the new server based on the interface identifier and the version number and rewriting the parameters of the service request, before sending the rewritten service request to the new server based on the interface address of the new server, the method further includes: determining whether the data transmission protocol of the new server and the first old server are consistent; if the data transmission protocol of the new server and the first old server are inconsistent, performing protocol conversion on the rewritten service request according to the data transmission protocol of the new server and the first old server, so that the converted service request conforms to the protocol requirements of the new server.

[0006] In some embodiments, determining the interface address of the new server and rewriting the parameters of the service request based on the interface identifier and the version number includes: obtaining a predefined rule set, the predefined rule set including a version range, the correspondence between interface identifier information and routing rules; searching for the routing rule that matches the interface identifier and the version number from the predefined rule set to obtain a target routing rule; determining the interface address and the parameter mapping relationship between the new server and the first old server based on the target routing rule; and rewriting the parameters of the service request based on the parameter mapping relationship.

[0007] In some embodiments, based on the interface identifier and the version number, a target routing rule is obtained by searching a predefined rule set for routing rules that match the interface identifier and the version number. This includes: using a semantic matching strategy to search the predefined rule set for interface identifier information corresponding to a version range that matches the version number as target identifier information; using a keyword matching strategy to search the predefined rule set for routing rules corresponding to the target identifier information that matches the interface identifier as intermediate routing rules; if there is one intermediate routing rule, determining the intermediate routing rule as the target routing rule; if there are multiple intermediate routing rules, determining the precision score corresponding to the version range of the multiple intermediate routing rules based on the version number, wherein the smaller the version range, the higher the corresponding precision score; and determining the intermediate routing rule corresponding to the highest precision score as the target routing rule.

[0008] In some embodiments, after sending the rewritten service request to the new server according to the interface address of the new server so that the new server executes the service, the method further includes: if an error occurs when the new server executes the service, obtaining a predefined degradation rule, the degradation rule including restoring the rewritten service request to meet the interface specification of a second old server, the second old server being the same as or different from the first old server; determining the interface address of the second old server according to the degradation rule, and restoring the parameters of the rewritten service request; sending the restored service request to the second old server according to the interface address of the second old server so that the second old server executes the service.

[0009] In some embodiments, when an error occurs during the execution of the service on the new server, the method further includes: analyzing the error log of the service execution error to obtain an analysis result, wherein the analysis result indicates that at least one item in the server, parameter mapping, and data transmission protocol has an error; and adjusting the predefined rule set according to the analysis result, such that the adjusted rule set is different from the predefined rule set in terms of the item in which the analysis result indicates an error.

[0010] In some embodiments, after the new server completes the service, it sends a response message to the control terminal. After sending the rewritten service request to the new server according to the interface address of the new server, the method further includes: obtaining a redirection error rate, which represents the ratio of the number of service execution errors to the total number of requests to execute the service; obtaining a service response time, which is the duration between the time the service request was sent and the time the response message was sent; and if the redirection error rate is greater than a first threshold and the service response time is greater than a second threshold, and the service request is detected again, the service request is not intercepted, so that the service request is sent to the first old server, and the first old server executes the service.

[0011] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform any of the methods described.

[0012] According to another aspect of this application, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of any of the methods described herein.

[0013] According to another aspect of this application, a service request redirection system is provided, comprising: a control terminal for sending service requests; a routing decision engine including: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including methods for performing any one of the methods described; a first old server terminal for receiving and executing the service request when the routing decision engine does not intercept the service request; and a new server terminal for executing the service corresponding to the rewritten service request upon receiving a rewritten service request sent by the routing decision engine.

[0014] By applying the technical solution of this application, when a service request from the control terminal to the first old server to execute a service is detected, the interface identifier of the first old server and the version number of the control terminal can be accurately identified by intercepting the service request and parsing its content. Subsequently, based on this information, the interface address of the service corresponding to the request on the new server is determined, and the parameters of the service request are rewritten to meet the interface specifications of the new server, thus achieving service request adaptation. This means that even if the parameter format, name, or data type changes between the old and new servers, the rewritten service request can still be correctly parsed and executed by the new server. This process eliminates compatibility barriers caused by changes in parameter structure, enabling older client versions to seamlessly connect to newer services and solving the problem of service call failures caused by parameter incompatibility. Finally, according to the interface address of the new server, the rewritten service request is sent to the new server, which then executes the requested service. This method achieves intelligent redirection of service requests, removes the hard-coded restriction of specific server interface addresses by the client, and allows access to the new version of the server interface even if the client has not been updated. This avoids the problem of being unable to access the new service due to an outdated client version. This ensures that different versions of the client can seamlessly integrate with the new service, allowing older clients to enjoy the new service without needing to upgrade. This not only avoids the decline in user experience and user churn caused by forcing users to upgrade their clients, but also significantly shortens the service upgrade cycle, improves service continuity and user experience, and enhances user stickiness. Attached Figure Description

[0015] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0016] Figure 1 A hardware structure block diagram of a mobile terminal for performing a service request redirection method according to an embodiment of this application is shown.

[0017] Figure 2 A flowchart illustrating a service request redirection method according to an embodiment of this application is shown.

[0018] Figure 3 A detailed flowchart of a service request redirection method according to an embodiment of this application is shown.

[0019] Figure 4 A structural block diagram of a service request redirection device provided according to an embodiment of this application is shown.

[0020] The above figures include the following reference numerals:

[0021] 102. Processor; 104. Memory; 106. Transmission device; 108. Input / output device. Detailed Implementation

[0022] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; 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.

[0025] It should be noted that the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and it does not violate public order and good morals. Corresponding operation portals are provided for users to choose to authorize or refuse.

[0026] As described in the background section, the hard-coded forced upgrade strategy in the prior art results in a poor user experience. To solve this technical problem, embodiments of this application provide a service request redirection method, a computer-readable storage medium, and a computer program product and service request redirection system.

[0027] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0028] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal for a service request redirection method according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0029] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the service request redirection method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0030] This embodiment provides a method for redirecting service requests running on a mobile terminal, computer terminal, or similar computing device. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0031] Figure 2 This is a flowchart illustrating a service request redirection method according to an embodiment of this application. Figure 2 As shown, the method includes the following steps:

[0032] Step S201: If a service request is detected, the service request is intercepted. The service request is a request initiated by the control terminal to request the first old server to perform the service.

[0033] Specifically, the aforementioned control terminal, also known as the client, refers to the application or terminal device through which the user directly interacts. Optionally, in the fintech field, these services include, but are not limited to, account management services (such as viewing account balances, transaction history, and personal information updates), payment and transfer services (such as domestic and international transfers, credit card payments, and automatic deductions), credit and investment services (such as credit applications, loan approvals, purchasing and redeeming wealth management products, and stock trading), and customer support services (such as online customer service, frequently asked questions, and complaint handling). Optionally, the mechanism for intercepting the above service requests can be implemented by a load balancer, proxy server, or dedicated middleware, which resides between the control terminal and the first client terminal and is responsible for inspecting all incoming communications.

[0034] Step S202: Parse the above service request to determine the interface identifier of the first old server and the version number of the control terminal.

[0035] Specifically, the aforementioned interface identifier refers to the interface identifier of the first old server accessed by the aforementioned service request view.

[0036] Step S203: Based on the above interface identifier and the above version number, determine the interface address of the new server and rewrite the parameters of the above service request so that the rewritten service request conforms to the interface specification of the above new server.

[0037] Optionally, the above parameter rewriting may include field name conversion (such as from card No to account Number), data type conversion (such as string to date), adding or deleting parameters (for example, a new server may need an additional verification token), etc.

[0038] Step S204: Based on the interface address of the new server, send the rewritten service request to the new server so that the new server can execute the service.

[0039] Specifically, the service request with rewritten parameters is sent to the specified interface address of the new server. After receiving the request, the new server executes the service and returns the result to the control end.

[0040] In this embodiment, when a service request is detected from the control terminal requesting the first old server to execute a service, this application intercepts the service request and parses its content to accurately identify the interface identifier of the first old server and the version number of the control terminal. Subsequently, based on this information, the interface address of the service corresponding to the request is determined on the new server, and the parameters of the service request are rewritten to meet the interface specifications of the new server, achieving service request adaptation. This means that even if the parameter format, name, or data type changes between the old and new servers, the rewritten service request can still be correctly parsed and executed by the new server. This process eliminates compatibility barriers caused by changes in parameter structure, enabling older client versions to seamlessly connect to newer services and resolving service call failures caused by parameter incompatibility. Finally, based on the interface address of the new server, the rewritten service request is sent to the new server, which then executes the requested service. This method achieves intelligent redirection of service requests, removing the hard-coded restriction of specific server interface addresses by the client. This allows the client to access the new version of the server interface even if it has not been updated, avoiding the problem of being unable to access new services due to an outdated client version. This ensures that different versions of the client can seamlessly integrate with the new service, allowing older clients to enjoy the new service without needing to upgrade. This not only avoids the decline in user experience and user churn caused by forcing users to upgrade their clients, but also significantly shortens the service upgrade cycle, improves service continuity and user experience, and enhances user stickiness.

[0041] Furthermore, this application determines which new server interface a service request should be redirected to by parsing the version number of the control terminal, which simplifies version management and maintenance. It eliminates the need to write separate adaptation logic for each older client version, reducing development and operational costs.

[0042] In practical applications, in order to achieve efficient interception of the above service requests, regular expressions or predefined patterns can be used to match the request path to quickly identify which service requests need to be redirected.

[0043] In one optional embodiment of this application, after determining the interface address of the new server based on the interface identifier and the version number and rewriting the parameters of the service request, before sending the rewritten service request to the new server based on the interface address of the new server, the method further includes: determining whether the data transmission protocol of the new server and the first old server are consistent; if the data transmission protocol of the new server and the first old server are inconsistent, performing protocol conversion on the rewritten service request based on the data transmission protocol of the new server and the first old server, so that the converted service request conforms to the protocol requirements of the new server. In this embodiment, after determining the interface address of the new server based on the interface identifier and version number and rewriting the parameters of the service request, in order to ensure that the service request can be correctly processed by the new server, this application further determines whether the data transmission protocol of the new server and the first old server are consistent. If the two protocols are found to be inconsistent, the rewritten service request is converted according to the respective data transmission protocols of the new and old servers to meet the needs of the new server. This not only solves the compatibility problem caused by protocol differences, but also ensures that the service request can be smoothly transmitted between different versions of the service, improves the overall adaptability and efficiency of service redirection, and further ensures the continuity of transactions and the consistency of user experience.

[0044] Specifically, when the data transmission protocols of the new server and the first old server are inconsistent, for example, the first old server uses XML while the new server uses JSON, this application calls a protocol converter to enable the protocol converter to intervene and convert the rewritten service request according to the respective data transmission protocols of the new and old servers so that it meets the requirements of the new server.

[0045] Based on the above embodiments, sending the rewritten service request to the new server according to the interface address of the new server includes: sending the converted service request to the new server according to the interface address of the new server.

[0046] Furthermore, if the data transmission protocol of the new server and the first old server are consistent, there is no need to perform protocol conversion on the rewritten service request; the rewritten service request can be directly sent to the new server for service execution.

[0047] In other exemplary embodiments, determining the interface address of the new server and rewriting the parameters of the service request based on the interface identifier and the version number includes: obtaining a predefined rule set, which includes a version range, the correspondence between interface identifier information and routing rules; searching the predefined rule set for the routing rule that matches the interface identifier and the version number to obtain the target routing rule; determining the interface address and the parameter mapping relationship between the new server and the first old server based on the target routing rule; and rewriting the parameters of the service request based on the parameter mapping relationship.

[0048] In the above embodiments, a rule set covering the mapping relationships between different version ranges, interface identification information, and routing rules is pre-established. This rule set allows for the intelligent selection of matching routing rules based on the interface identifier and version number in the service request sent by the client. This further ensures that older versions of clients are guided to the new version of the server without the inconvenience of forced upgrades. Users don't need to worry about frequently downloading new versions of the app due to service updates, further enhancing user stickiness and improving user experience. Furthermore, this solution eliminates the need to manually create or update the interface adaptation layer for each older client version and eliminates the need to maintain multiple versions of the service simultaneously, further reducing development and maintenance complexity, resource consumption, and the probability of potential errors.

[0049] Specifically, the predefined rule set mentioned above can be stored in a cloud configuration center or locally, supporting rapid remote updates. The predefined rule set can also include the correspondence between version range, interface identifier information, routing rules, and the interface address of the new version of the server.

[0050] According to some specific implementations of this application, the aforementioned service request is an HTTP request. This request contains information about the action the control terminal wants to perform, such as querying account balance or transferring funds, and also carries some metadata about the control terminal itself. Parsing the aforementioned service request to determine the interface identifier of the first old server and the version number of the control terminal may include: parsing the aforementioned service request to extract the version number carried in the User-Agent field from the HTTP request header data, and parsing the interface identifier carried in the URL path field from the HTTP request body.

[0051] The User-Agent field typically includes the client (controller) type, operating system, browser (if it is a web client), and version number.

[0052] After parsing and obtaining the interface identifier and version number, the method further includes: checking whether the version number is valid; determining whether the interface identifier exists and whether there are corresponding routing rules based on a predefined rule set; and generating an error response and returning it to the control terminal if a problem is detected.

[0053] In some embodiments, based on the interface identifier and the version number, the target routing rule is obtained by searching the predefined rule set for routing rules that match the interface identifier and the version number. This includes traversing the predefined rule set and determining the version range of the version number and the routing rules corresponding to the interface version information that is the same as the interface identifier. These are the target routing rules. By traversing the predefined rule set, routing rules that match the interface identifier and version number can be found quickly and accurately.

[0054] In some embodiments, based on the interface identifier and the version number, a target routing rule is obtained by searching the predefined rule set for routing rules that match the interface identifier and the version number. This includes: using a semantic matching strategy to search the predefined rule set for interface identifier information corresponding to a version range that matches the version number as target identifier information; using a keyword matching strategy to search the predefined rule set for routing rules corresponding to the target identifier information that matches the interface identifier as intermediate routing rules; if there is one intermediate routing rule, determining the intermediate routing rule as the target routing rule; if there are multiple intermediate routing rules, determining the precision score corresponding to the version range of the multiple intermediate routing rules based on the version number, wherein the smaller the version range, the higher the corresponding precision score; and determining the intermediate routing rule corresponding to the highest precision score as the target routing rule.

[0055] In the above embodiments, a semantic matching strategy is employed, which intelligently compares the client's version number with the version range in a predefined rule set to find the most matching version interval. This strategy goes beyond simple numerical comparison, recognizing version numbers such as "v4.1" and corresponding them to the rule range "4.0≤ver<5.0," ensuring that even small changes in the version number can find a suitable routing rule. Matching interface identifiers with keywords ensures the accuracy and efficiency of interface identification. If only one intermediate routing rule is found from the predefined rule set, this rule will be directly identified as the target routing rule and immediately applied to the service request's routing decision and parameter rewriting. This immediate application reduces time latency in the decision-making process and improves service response speed. When multiple intermediate routing rules exist, by calculating the version range of each rule, it can be determined which rule most accurately describes the client version, thus making the optimal routing decision. This intelligent selection avoids routing errors caused by rule ambiguity, improving service stability and user experience. Through the precise matching and selection of routing rules, the old version of the client was able to successfully connect to the new server, avoiding problems such as transaction failures and missing functions caused by version incompatibility, thereby improving the overall service quality and user satisfaction.

[0056] According to some other embodiments of this application, after sending the rewritten service request to the new server based on the interface address of the new server so that the new server can execute the service, the method further includes: in the event of an error in the execution of the service by the new server, obtaining a predefined degradation rule, the degradation rule including restoring the rewritten service request to meet the interface specification of the second old server, the second old server being the same as or different from the first old server; determining the interface address of the second old server according to the degradation rule, and restoring the parameters of the rewritten service request; and sending the restored service request to the second old server based on the interface address of the second old server so that the second old server can execute the service. This design enables a rapid fallback to the old version of the server when an anomaly occurs on the new server, ensuring service continuity and transaction reliability, and further improving the stability and security of service redirection.

[0057] The downgrade rules in this application allow for flexible selection of rollback paths during the switching between old and new services. Whether rolling back to the previous version or an earlier stable version, intelligent decisions can be made based on the current service status and version compatibility, further enhancing the robustness and adaptability of the system.

[0058] It should be noted that the aforementioned first old server, second old server, and new server refer to the physical or virtual servers where the service is deployed and running. These servers are responsible for receiving requests from the control terminal, processing the business logic within the requests, and returning the results or responses to the control terminal. Specifically, the first old server and second old server are those released earlier than the new server. Both the first and second old servers are the default servers accessed by lower-version control terminals (i.e., lower-version clients), while the new server is the default server accessed by higher-version control terminals (i.e., higher-version clients). Typically, the second old server is released later than the first old server.

[0059] In the fintech field, the server side may consist of multiple servers to form a highly available service cluster. These servers run various backend applications for banking services, such as database servers storing customer data, application servers processing transaction logic, and load balancers managing request distribution.

[0060] Optionally, if an error occurs when the new server executes the service, the method further includes: analyzing the error logs of the service execution error to obtain analysis results, whereby the analysis results indicate that at least one item in the server, parameter mapping, and data transmission protocol has an error; and based on the analysis results, performing rule rollback adjustments on the predefined rule set so that the adjusted rule set differs from the predefined rule set in the items where the analysis results indicate errors. If an error occurs when the new server executes the service, this solution first identifies the problem by analyzing the error logs, whether it's an internal logic error on the server, inaccurate parameter mapping, or incompatibility with the data transmission protocol. This automatic diagnostic capability reduces troubleshooting time, avoids blind adjustments when the source of the problem is unclear, and improves repair efficiency. Once the error log analysis clarifies the source of the error, this application can automatically adjust the predefined rule set, rolling back to a previously stable state or using backup rules. This means that when a problem occurs on the new server, requests from older client versions can be redirected to a more stable server interface, ensuring service continuity and preventing users from being affected by service interruptions. In addition, this application can automatically switch to more reliable routing rules and service paths with almost no noticeable effect on the user. This greatly reduces the failures and anomalies encountered by users during service upgrades and improves the user experience.

[0061] In some other embodiments, after the new server completes the service, it sends a response message to the control terminal. After sending the rewritten service request to the new server according to the interface address of the new server, the method further includes: obtaining a redirection error rate, which represents the ratio of the number of service execution errors to the total number of requests to execute the service; obtaining a service response time, which is the duration between the time the service request is sent and the time the response message is sent; and if the redirection error rate is greater than a first threshold and the service response time is greater than a second threshold, and the service request is detected again, the service request is not intercepted, so that the service request is sent to the first old server, and the first old server executes the service.

[0062] In the above implementation, by continuously monitoring the redirection error rate and service response time, abnormal states during server-side service execution can be identified and quantified in real time. If any indicator exceeds a preset threshold, it indicates that the new server may have encountered problems, such as technical failures, performance bottlenecks, or configuration errors. In this case, the redirection strategy will be automatically bypassed, and the request will no longer be redirected to the new server. Instead, the service request will be sent directly to the first old server, ensuring that transactions and other important services can be completed smoothly. This avoids service interruptions caused by problems with the new server and maintains the continuity and stability of the overall service.

[0063] According to some other embodiments of this application, sending the rewritten service request to the new server based on the new server's interface address includes: sending the rewritten service request to the new server via an encrypted channel based on the new server's interface address, thereby ensuring the secure transmission of the service request.

[0064] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the service request redirection method of this application will be described in detail below with reference to specific embodiments.

[0065] This embodiment relates to a specific method for redirecting service requests, such as... Figure 3 As shown, this method runs on the routing decision engine and includes the following steps:

[0066] Step S1: The cloud configuration center predefines a version routing rule set. This rule set includes the old version's interface identifier, the new version's target address, and parameter mapping relationships. The configuration center uses a semantic version-based field-level automatic mapping algorithm to map parameters between the old and new versions (i.e.,...). Figure 3 (Version-service mapping rules in the code), parameter mapping relationships support default value injection, field name conversion, and data type casting;

[0067] Step S2: The routing decision engine intercepts and reads the request message data initiated by the client through the routing interceptor, and extracts the interface identifier and version number in the request. The routing decision engine supports semantic version matching. By parsing the HTTP request header data in the request message, the version information in the User-Agent field is obtained, for example, AppVer = 4.1.

[0068] Step S3: The routing decision engine queries the predefined version routing rule set in the configuration center and selects the corresponding routing rule according to the version number. For example, based on the version number AppVer=4.1, it determines 4.0≤ver<5.0→ / v3-router / , thereby dynamically rewriting the request address and parameter structure in the request message data.

[0069] Step S4: The routing decision engine uses a protocol converter to convert between old and new versions of the protocol, resolving the compatibility issues of parameters / formats between the old and new versions. Specifically, the protocol converter supports cross-protocol conversion and field-level intelligent mapping, and the field rewriting engine converts the request body fields according to the JSON Schema, converting the old version of the XML request into the new version of the JSON protocol, thus resolving the format compatibility issues.

[0070] Step S5: The routing decision engine ensures the stability and security of the routing decision process through the traffic monitor. Specifically, the traffic monitor is based on a transaction-level circuit breaker decision model (based on error rate + transaction latency) to ensure the stability and security of the routing redirection process. It has real-time circuit breaker capability. When a request fails, it automatically switches to the old version interface for retry and reports the error log to the configuration center to trigger rule rollback. The circuit breaker controller sets a dual caching strategy (local cache + persistent degradation package) to deal with network unavailability scenarios and ensure the user experience after the user opens the APP.

[0071] Step S6: The routing decision engine sends the rewritten request to the new target address through the service proxy using an HTTPS encrypted channel. After the new version service cluster receives the request, it completes the business processing and outputs a transaction response message compatible with the client version to the client.

[0072] Through the above steps, dynamic routing decisions were achieved, ultimately ensuring that users could actually enjoy the product recommendation service of v5.1 when using the v4.1 APP without pop-ups or upgrades.

[0073] The above-described solution in this application employs a declarative routing management architecture that separates configuration from code, dynamically obtaining routing rules through a configuration center. It designs a process of request semantic parsing → rule matching → target address rewriting, using a routing decision engine to parse configurations and redirect requests. A circuit breaker controller based on version number and error rate rolls back old interfaces according to rules, and traffic monitoring ensures normal service execution. This achieves seamless integration of older app versions with new services, eliminating the need for users to update their app versions and avoiding update notifications, thus improving user experience. For users with older phone models who cannot be forced to update, older versions can use new server-side features, further improving service availability. This application ensures a significantly shortened upgrade cycle, with configuration updates taking effect within seconds, and backend service upgrades no longer relying on client version updates.

[0074] This application also provides a service request redirection device. It should be noted that the service request redirection device of this application can be used to execute the service request redirection method provided in this application. This device is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0075] The following describes the service request redirection device provided in the embodiments of this application.

[0076] Figure 4 This is a structural block diagram of a service request redirection device according to an embodiment of this application. Figure 4 As shown, the device includes:

[0077] The interception module 10 is used to intercept the service request when a service request is detected. The service request is a request initiated by the control terminal to provide information on the first old server to perform the service.

[0078] The parsing module 20 is used to parse the above service request and determine the interface identifier of the first old server and the version number of the control terminal.

[0079] The determination module 30 is used to determine the interface address of the new server based on the interface identifier and the version number mentioned above, and to rewrite the parameters of the service request so that the rewritten service request conforms to the interface specification of the new server.

[0080] The sending module 40 is used to send the rewritten service request to the new server according to the interface address of the new server, so that the new server can execute the service.

[0081] The aforementioned service request redirection device includes a processor and a memory. The interception module, parsing module, determination module, and sending module are all stored as program units in the memory, and the processor executes these program units to implement their respective functions. All of the aforementioned modules reside in the same processor; alternatively, the modules may be located in different processors in any combination.

[0082] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters can at least address the poor user experience caused by hard-coded forced upgrade strategies in existing technologies.

[0083] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0084] This invention provides a computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to execute the service request redirection method.

[0085] Specifically, the methods for redirecting service requests include:

[0086] Step S201: If a service request is detected, the service request is intercepted. The service request is a request initiated by the control terminal to request the first old server to perform the service.

[0087] Specifically, the aforementioned control terminal, also known as the client, refers to the application or terminal device through which the user directly interacts. Optionally, in the fintech field, these services include, but are not limited to, account management services (such as viewing account balances, transaction history, and personal information updates), payment and transfer services (such as domestic and international transfers, credit card payments, and automatic deductions), credit and investment services (such as credit applications, loan approvals, purchasing and redeeming wealth management products, and stock trading), and customer support services (such as online customer service, frequently asked questions, and complaint handling). Optionally, the mechanism for intercepting the above service requests can be implemented by a load balancer, proxy server, or dedicated middleware, which resides between the control terminal and the first client terminal and is responsible for inspecting all incoming communications.

[0088] Step S202: Parse the above service request to determine the interface identifier of the first old server and the version number of the control terminal.

[0089] Specifically, the aforementioned interface identifier refers to the interface identifier of the first old server accessed by the aforementioned service request view.

[0090] Step S203: Based on the above interface identifier and the above version number, determine the interface address of the new server and rewrite the parameters of the above service request so that the rewritten service request conforms to the interface specification of the above new server.

[0091] Optionally, the above parameter rewriting may include field name conversion (such as from card No to account Number), data type conversion (such as string to date), adding or deleting parameters (for example, a new server may need an additional verification token), etc.

[0092] Step S204: Based on the interface address of the new server, send the rewritten service request to the new server so that the new server can execute the service.

[0093] Specifically, the service request with rewritten parameters is sent to the specified interface address of the new server. After receiving the request, the new server executes the service and returns the result to the control end.

[0094] In some embodiments, after determining the interface address of the new server based on the interface identifier and the version number and rewriting the parameters of the service request, before sending the rewritten service request to the new server based on the interface address of the new server, the method further includes: determining whether the data transmission protocol of the new server and the first old server are consistent; if the data transmission protocol of the new server and the first old server are inconsistent, performing protocol conversion on the rewritten service request based on the data transmission protocol of the new server and the first old server, so that the converted service request conforms to the protocol requirements of the new server.

[0095] In some embodiments, determining the interface address of the new server and rewriting the parameters of the service request based on the interface identifier and the version number includes: obtaining a predefined rule set, the predefined rule set including version range, the correspondence between interface identifier information and routing rules; searching the predefined rule set for the routing rule that matches the interface identifier and the version number to obtain the target routing rule; determining the interface address and the parameter mapping relationship between the new server and the first old server based on the target routing rule; and rewriting the parameters of the service request based on the parameter mapping relationship.

[0096] In some embodiments, based on the interface identifier and the version number, a target routing rule is obtained by searching the predefined rule set for routing rules that match the interface identifier and the version number. This includes: using a semantic matching strategy to search the predefined rule set for interface identifier information corresponding to a version range that matches the version number as target identifier information; using a keyword matching strategy to search the predefined rule set for routing rules corresponding to the target identifier information that matches the interface identifier as intermediate routing rules; if there is one intermediate routing rule, determining the intermediate routing rule as the target routing rule; if there are multiple intermediate routing rules, determining the precision score corresponding to the version range of the multiple intermediate routing rules based on the version number, wherein the smaller the version range, the higher the corresponding precision score; and determining the intermediate routing rule corresponding to the highest precision score as the target routing rule.

[0097] In some embodiments, after sending the rewritten service request to the new server according to the interface address of the new server so that the new server can execute the service, the method further includes: if an error occurs when the new server executes the service, obtaining a predefined degradation rule, the degradation rule including restoring the rewritten service request to meet the interface specification of the second old server, the second old server being the same as or different from the first old server; determining the interface address of the second old server according to the degradation rule, and restoring the parameters of the rewritten service request; and sending the restored service request to the second old server according to the interface address of the second old server so that the second old server can execute the service.

[0098] In some embodiments, if an error occurs when the new server executes the service, the method further includes: analyzing the error log of the service execution error to obtain analysis results, wherein the analysis results indicate that at least one item in the server, parameter mapping, and data transmission protocol has an error; and adjusting the predefined rule set according to the analysis results, so that the adjusted rule set is different from the predefined rule set in terms of the items in which the analysis results indicate an error.

[0099] In some embodiments, after the new server completes the service, it sends a response message to the control terminal. After sending the rewritten service request to the new server according to the interface address of the new server, the method further includes: obtaining a redirection error rate, which represents the ratio of the number of service execution errors to the total number of requests to execute the service; obtaining a service response time, which is the duration between the time when the service request is sent and the time when the response message is sent; and if the redirection error rate is greater than a first threshold and the service response time is greater than a second threshold, and the service request is detected again, the service request is not intercepted, so that the service request is sent to the first old server, and the first old server executes the service.

[0100] This invention provides a device including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it at least implements the steps of the above-described service request redirection method.

[0101] The devices mentioned in this article can be servers, PCs, tablets, mobile phones, etc.

[0102] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having at least the following method steps:

[0103] Step S201: If a service request is detected, the service request is intercepted. The service request is a request initiated by the control terminal to request the first old server to perform the service.

[0104] Step S202: Parse the above service request to determine the interface identifier of the first old server and the version number of the control terminal.

[0105] Step S203: Based on the above interface identifier and the above version number, determine the interface address of the new server and rewrite the parameters of the above service request so that the rewritten service request conforms to the interface specification of the above new server.

[0106] Step S204: Based on the interface address of the new server, send the rewritten service request to the new server so that the new server can execute the service.

[0107] In some embodiments, after determining the interface address of the new server based on the interface identifier and the version number and rewriting the parameters of the service request, before sending the rewritten service request to the new server based on the interface address of the new server, the method further includes: determining whether the data transmission protocol of the new server and the first old server are consistent; if the data transmission protocol of the new server and the first old server are inconsistent, performing protocol conversion on the rewritten service request based on the data transmission protocol of the new server and the first old server, so that the converted service request conforms to the protocol requirements of the new server.

[0108] In some embodiments, determining the interface address of the new server and rewriting the parameters of the service request based on the interface identifier and the version number includes: obtaining a predefined rule set, the predefined rule set including version range, the correspondence between interface identifier information and routing rules; searching the predefined rule set for the routing rule that matches the interface identifier and the version number to obtain the target routing rule; determining the interface address and the parameter mapping relationship between the new server and the first old server based on the target routing rule; and rewriting the parameters of the service request based on the parameter mapping relationship.

[0109] In some embodiments, based on the interface identifier and the version number, a target routing rule is obtained by searching the predefined rule set for routing rules that match the interface identifier and the version number. This includes: using a semantic matching strategy to search the predefined rule set for interface identifier information corresponding to a version range that matches the version number as target identifier information; using a keyword matching strategy to search the predefined rule set for routing rules corresponding to the target identifier information that matches the interface identifier as intermediate routing rules; if there is one intermediate routing rule, determining the intermediate routing rule as the target routing rule; if there are multiple intermediate routing rules, determining the precision score corresponding to the version range of the multiple intermediate routing rules based on the version number, wherein the smaller the version range, the higher the corresponding precision score; and determining the intermediate routing rule corresponding to the highest precision score as the target routing rule.

[0110] In some embodiments, after sending the rewritten service request to the new server according to the interface address of the new server so that the new server can execute the service, the method further includes: if an error occurs when the new server executes the service, obtaining a predefined degradation rule, the degradation rule including restoring the rewritten service request to meet the interface specification of the second old server, the second old server being the same as or different from the first old server; determining the interface address of the second old server according to the degradation rule, and restoring the parameters of the rewritten service request; and sending the restored service request to the second old server according to the interface address of the second old server so that the second old server can execute the service.

[0111] In some embodiments, if an error occurs when the new server executes the service, the method further includes: analyzing the error log of the service execution error to obtain analysis results, wherein the analysis results indicate that at least one item in the server, parameter mapping, and data transmission protocol has an error; and adjusting the predefined rule set according to the analysis results, so that the adjusted rule set is different from the predefined rule set in terms of the items in which the analysis results indicate an error.

[0112] In some embodiments, after the new server completes the service, it sends a response message to the control terminal. After sending the rewritten service request to the new server according to the interface address of the new server, the method further includes: obtaining a redirection error rate, which represents the ratio of the number of service execution errors to the total number of requests to execute the service; obtaining a service response time, which is the duration between the time when the service request is sent and the time when the response message is sent; and if the redirection error rate is greater than a first threshold and the service response time is greater than a second threshold, and the service request is detected again, the service request is not intercepted, so that the service request is sent to the first old server, and the first old server executes the service.

[0113] This application also provides a service request redirection system, including:

[0114] The control terminal is used to send service requests;

[0115] A routing decision engine includes: one or more processors, memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include methods for performing any of the above-described methods;

[0116] The first old server is used to receive and execute the above service requests when the above routing decision engine does not intercept the above service requests;

[0117] The new server is used to execute the service corresponding to the rewritten service request when it receives the rewritten service request sent by the routing decision engine.

[0118] Through the above embodiments, when the routing decision engine detects a service request from the control terminal requesting the first old server to execute a service, it intercepts the service request and parses its content to accurately identify the interface identifier of the first old server and the version number of the control terminal. Subsequently, based on this information, it determines the interface address of the service corresponding to the request on the new server and rewrites the parameters of the service request to meet the interface specifications of the new server, achieving service request adaptation. This means that even if the parameter format, name, or data type changes between the old and new servers, the rewritten service request can still be correctly parsed and executed by the new server. This process eliminates compatibility barriers caused by changes in parameter structure, enabling older client versions to seamlessly connect to newer services and resolving service call failures caused by parameter incompatibility. Finally, based on the interface address of the new server, the rewritten service request is sent to the new server, which then executes the requested service. This method achieves intelligent redirection of service requests, removing the hard-coded restriction of specific server interface addresses by the client. This allows the client to access the new version of the server interface even if it has not been updated, avoiding the problem of being unable to access new services due to an outdated client version. This ensures that different versions of the client can seamlessly integrate with the new service, allowing older clients to enjoy the new service without needing to upgrade. This not only avoids the decline in user experience and user churn caused by forcing users to upgrade their clients, but also significantly shortens the service upgrade cycle, improves service continuity and user experience, and enhances user stickiness.

[0119] In some alternative solutions, the service request redirection system also includes a second old server, which may be the same as or different from the first old server. When an error occurs while the new server is executing the service, the routing decision engine obtains predefined degradation rules. These rules include restoring the rewritten service request to meet the interface specifications of the second old server (which may be the same as or different from the first old server); determining the interface address of the second old server based on these degradation rules; restoring the parameters of the rewritten service request; and sending the restored service request to the second old server based on its interface address, so that the second old server can execute the service.

[0120] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0121] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0122] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0123] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0124] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0125] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0126] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0127] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0128] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0129] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0130] As can be seen from the above description, the embodiments of this application achieve the following technical effects:

[0131] The service request redirection method in this application, upon detecting a service request from the control end requesting the execution of a service from the first old server, intercepts and parses the service request to accurately identify the interface identifier of the first old server and the version number of the control end. Subsequently, based on this information, it determines the interface address of the service corresponding to the request on the new server and rewrites the parameters of the service request to meet the interface specifications of the new server, achieving service request adaptation. This means that even if the parameter format, name, or data type changes between the old and new servers, the rewritten service request can still be correctly parsed and executed by the new server. This process eliminates compatibility barriers caused by changes in parameter structure, enabling older client versions to seamlessly integrate with newer services and resolving service call failures due to parameter incompatibility. Finally, based on the interface address of the new server, the rewritten service request is sent to the new server, which then executes the requested service. This method achieves intelligent redirection of service requests, removing the hard-coded restriction of specific server interface addresses by the client. This allows even clients that have not updated to access the new version of the server interface, avoiding the problem of being unable to access new services due to outdated client versions. This ensures that different versions of the client can seamlessly integrate with the new service, allowing older clients to enjoy the new service without needing to upgrade. This not only avoids the decline in user experience and user churn caused by forcing users to upgrade their clients, but also significantly shortens the service upgrade cycle, improves service continuity and user experience, and enhances user stickiness.

[0132] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method of redirecting a service request, characterized by, The method comprises the following steps: In the case of detecting a service request, intercepting the service request, which is a request initiated by a control end to request a first old service end to perform a service; Analyzing the service request to determine the interface identifier of the first old service end and the version number of the control end; According to the interface identifier and the version number, determine the interface address of the new service end and rewrite the parameters of the service request, so that the rewritten service request conforms to the interface specification of the new service end; According to the interface address of the new service end, the rewritten service request is sent to the new service end, so that the new service end performs the service.

2. The method of claim 1, wherein, After determining the interface address of the new service end and rewriting the parameters of the service request according to the interface identifier and the version number, before sending the rewritten service request to the new service end according to the interface address of the new service end, the method further comprises: Determine whether the data transmission protocol of the new service end is consistent with that of the first old service end; In the case where the data transmission protocol of the new service end is inconsistent with that of the first old service end, protocol conversion is performed on the rewritten service request according to the data transmission protocol of the new service end and the first old service end, so that the converted service request conforms to the protocol requirements of the new service end.

3. The method of claim 1, wherein, According to the interface identifier and the version number, determine the interface address of the new service end and rewrite the parameters of the service request, comprising: Obtain a predefined rule set, which includes the correspondence between version range, interface identification information and routing rule; According to the interface identifier and the version number, find the routing rule matching the interface identifier and the version number from the predefined rule set to obtain the target routing rule; According to the target routing rule, determine the interface address and the parameter mapping relationship between the new service end and the first old service end; According to the parameter mapping relationship, re-parameterize the service request.

4. The method of claim 3, wherein, According to the interface identifier and the version number, find the routing rule matching the interface identifier and the version number from the predefined rule set to obtain the target routing rule, comprising: Using semantic matching strategy, find the interface identification information corresponding to the version range matching the version number from the predefined rule set as target identification information; Using keyword matching strategy, find the routing rule corresponding to the target identification information matching the interface identifier from the predefined rule set as intermediate routing rule; In the case where there is one intermediate routing rule, determine that the intermediate routing rule is the target routing rule; In the case where there are multiple intermediate routing rules, according to the version number, determine the accuracy score corresponding to the version range corresponding to multiple intermediate routing rules, the smaller the range of the version range, the higher the accuracy score corresponding to it; Determine that the intermediate routing rule corresponding to the highest accuracy score is the target routing rule.

5. The method of claim 3, wherein, In the case that the new service end executes the service with an error, the method further comprises: In the case that the new service end executes the service with an error, the method further comprises: In the case that the new service end executes the service with an error, the method further comprises: In the case that the new service end executes the service with an error, the method further comprises:

6. The method of claim 3, wherein, In the case that the new service end executes the service with an error, the method further comprises: In the case that the new service end executes the service with an error, the method further comprises: In the case that the new service end executes the service with an error, the method further comprises:

7. The method of claim 1, wherein, The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running.

9. A computer program product comprising computer programs / instructions, characterized in that, The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7.

10. A system for redirection of service requests, characterized by The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The computer readable storage medium comprises a stored program, wherein the program controls the device where the computer readable storage medium is located to execute the method of any one of claims 1 to 7 when the program is running. The computer program / instruction is executed by the processor to realize the steps of the method of any one of claims 1 to 7. The new service end is configured to execute the service corresponding to the rewritten service request when receiving the rewritten service request sent by the routing decision engine.

Images