Service response data table maintenance method, device, equipment, medium and program product

Abstract

The application discloses a kind of service response data table maintenance method, device, equipment, medium and program product.The method comprises: when meeting the update condition of service response data table, obtain the service complaint information in pre-set time interval, and extract abnormal service type in service complaint information;According to service complaint information, trace back user historical service log, and locate the abnormal reason of the abnormal service type according to user historical service log;According to abnormal reason, when all users request the service of the abnormal service type, the proportion value that user perception is abnormal appears;According to proportion value, the response server identification of part or all user identification in service response data table is replaced by the server identification of backup server, and the updated service response data table is obtained.The embodiment of the application, by maintaining service response data table, reduce the inconvenience caused to user due to service interruption or abnormality, improve service quality and user experience.

Description

Technical Field

[0001] This invention relates to the field of distributed technology, applicable to the financial technology field, and particularly to a service response data table maintenance method, apparatus, device, medium, and program product. Background Technology

[0002] In recent years, many commercial banks have actively launched online banking services and successfully connected them with the network systems of numerous platforms such as securities companies, fund companies, and non-financial payment institutions. Online banking offers a wide variety of comprehensive services, and correspondingly, the frequency of its deployment and changes is also quite high.

[0003] Production upgrades refer to the product and service upgrade process initiated by the server-side for commercial banks' information systems. This encompasses various aspects, including content updates and iterations, functional adjustments and changes, defect fixes and improvements, and performance optimizations. However, with numerous program modifications, diverse transaction scenarios, and complex logic, inadequate self-testing and failure to promptly detect problems can lead to production issues. Analyzing and locating these problems and releasing patches consumes significant time.

[0004] Therefore, there is an urgent need for a method to quickly resolve the above problems, restore the normal operation of non-new transactions, and provide a buffer time for problem repair. Summary of the Invention

[0005] Based on this, the present invention provides a service response data table maintenance method, apparatus, equipment, medium and program product to solve the problem of slow repair of program issues caused by production changes, which affects the customer's user experience.

[0006] In a first aspect, embodiments of the present invention provide a service response data table maintenance method, the method comprising:

[0007] When the update conditions of the service response data table are met, obtain service complaint information within a preset time range and extract the abnormal service type from the service complaint information;

[0008] The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application.

[0009] Based on the service complaint information, the user's historical service logs are traced back, and the cause of the abnormality of the abnormal service type is located based on the user's historical service logs;

[0010] Based on the stated cause of the anomaly, the percentage of users experiencing an anomaly is determined when all users request the service of the anomaly type.

[0011] Based on the ratio, the response server identifiers of some or all user identifiers in the service response data table are replaced with the server identifiers of the backup server to obtain an updated service response data table, in which the backup server is configured with a second version of the service application.

[0012] Secondly, embodiments of the present invention provide a service response data table maintenance apparatus, the apparatus comprising:

[0013] The abnormal service type extraction module is used to obtain service complaint information within a preset time range when the update conditions of the service response data table are met, and to extract the abnormal service type from the service complaint information.

[0014] The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application.

[0015] The anomaly cause localization module is used to trace back the user's historical service logs based on service complaint information, and locate the anomaly cause of the anomaly type based on the user's historical service logs;

[0016] The proportion value determination module is used to determine, based on the cause of the anomaly, the proportion of users experiencing an anomaly when all users request the service of the anomaly service type.

[0017] The server identifier replacement module is used to replace the response server identifier of some or all user identifiers in the service response data table with the server identifier of the backup server according to a ratio value, so as to obtain an updated service response data table. The backup server is configured with a second version of the service application.

[0018] Thirdly, embodiments of the present invention provide an electronic device, the electronic device comprising:

[0019] At least one processor; and

[0020] A memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a service response data table maintenance method according to any embodiment of the present invention.

[0022] Fourthly, a computer-readable storage medium is also provided, the computer-readable storage medium storing computer instructions, the computer instructions being used to cause a processor to execute and implement a service response data table maintenance method according to any embodiment of the present invention.

[0023] Fifthly, a computer program product is also provided, the computer program product including a computer program, which, when executed by a processor, implements a service response data table maintenance method as described in any embodiment of the present invention.

[0024] The technical solution of this invention proposes a method for determining whether to redirect all user requests to a backup server based on the proportion of user-perceived anomalies. By redirecting some or all user requests to the backup server, the anomaly issues introduced by the new version of the service application can be effectively resolved. This efficient switching mechanism helps ensure service continuity, reduces inconvenience to users caused by service interruptions or anomalies, and improves service quality and user experience.

[0025] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a flowchart of a service response data table maintenance method according to Embodiment 1 of the present invention;

[0028] Figure 2 This is a flowchart of another service response data table maintenance method provided in Embodiment 2 of the present invention;

[0029] Figure 3 This is a schematic diagram of a service response data table maintenance device according to Embodiment 3 of the present invention;

[0030] Figure 4 This is a schematic diagram of the structure of an electronic device for a service response data table maintenance method according to Embodiment 4 of the present invention. Detailed Implementation

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

[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention 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 so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a 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.

[0033] Example 1

[0034] Figure 1 This is a flowchart illustrating a service response data table maintenance method according to Embodiment 1 of the present invention. This embodiment is applicable to situations where user access results are abnormal due to product deployment changes. The method can be executed by a service response data table maintenance device, which can be implemented in hardware and / or software and can be configured in an operation and maintenance management system. Figure 1 As shown, the method includes:

[0035] S110. When the update conditions of the service response data table are met, obtain the service complaint information within the preset time interval, and extract the abnormal service type from the service complaint information.

[0036] The service response data table stores the mapping relationship between user identifiers and server identifiers of the response server, and the response server is configured with the first version of the service application.

[0037] Optionally, the update conditions for the service response data table may include:

[0038] After the second version of the service application used for testing is put into production and used as the first version of the service application, and after a preset production and use period, it is determined that the update conditions of the service response data table are met.

[0039] During actual customer use of online banking, the online banking version is updated due to production changes. The second version of the service application refers to the old version before the iteration, and the first version of the service application refers to the new version after the iteration. When the first version of the service application has been in production for a period of time and reaches the preset maintenance time, it is said to meet the update conditions of the service response data table. Using the production and usage time as the trigger condition for the update condition can, on the one hand, accumulate a certain amount of complaint information, which is convenient for subsequent anomaly analysis and maintenance, and on the other hand, automate the data table maintenance without manual intervention.

[0040] The service response data table contains user identifiers and corresponding server identifiers. Updating the service response data table involves selectively updating and replacing the server identifiers based on the user identifiers to adapt to some changes caused by the update deployment.

[0041] S120. Based on the service complaint information, trace back the user's historical service logs, and locate the cause of the abnormality of the abnormal service type based on the user's historical service logs.

[0042] When a user encounters an anomaly in the query results while using the current first version of the service application, they will initiate a complaint report. Upon receiving the complaint report, the backend extracts historical service log data corresponding to the user's complaint information using the time and user ID. By analyzing this historical service data, the cause of the anomaly under the corresponding anomaly service type is determined. In this embodiment of the invention, the cause of the anomaly could be due to a version update leading to the anomaly.

[0043] S130. Based on the cause of the anomaly, determine the proportion of users experiencing an anomaly when all users request the service of the anomaly type.

[0044] In a specific example, if the abnormal service type is the incomplete display of fixed deposit records, then among all users with fixed deposit business at the bank, those who are aware of the incomplete display of fixed deposit records will be counted. For ease of understanding, if the reason for the incomplete display of fixed deposit records is that the user has made too few deposits, then regardless of product iterations, the number of fixed deposit records displayed for such users will remain unchanged, and these users will be considered as those who are unaware of the abnormality. Conversely, for another group of users who have made more deposits, and whose number of fixed deposit records displayed after product iteration is significantly less than the number displayed before product iteration, these users will be considered as those who have perceived the abnormality.

[0045] S140. Based on the ratio value, replace the response server identifier of some or all user identifiers in the service response data table with the server identifier of the backup server to obtain the updated service response data table, wherein the backup server is configured with the second version of the service application.

[0046] The ratio refers to the proportion of users experiencing perceived anomalies out of all users requesting the abnormal service. Different server replacement strategies are implemented based on the ratio. Specifically, the backup server stores the second version of the service application before the iteration. Before the server replacement strategy is implemented, the service response data table only contains the response server, that is, the server storing the first version of the service application after the iteration. The updated service response data table has different numbers of response servers and backup servers depending on the server replacement strategy.

[0047] Furthermore, after replacing the response server identifiers of some or all user identifiers in the service response data table with the server identifiers of the backup server according to the ratio value, to obtain the updated service response data table, it may also include:

[0048] In response to a target user's target service request, extract the target user identifier from the target service request;

[0049] Determine the server identifier of the target server corresponding to the target user identifier in the service response data table;

[0050] When the server identifier of the target server is the response server, the target login data corresponding to the target user identifier is obtained from the response server, and the first service result of the first version of the service application corresponding to the target service request is called in the response server using the target login data.

[0051] When the server identifier of the target server is a backup server, the target login data corresponding to the target user identifier is searched in the distributed session cache system, and the second service result of the second version of the service application corresponding to the target service request is called in the backup server using the target login data.

[0052] The response server stores a table relating user identifiers to login data, which is cached in a distributed session caching system.

[0053] After completing the update of the service response data table, if a service request corresponding to the updated service response data table is received again from a user, the target server corresponding to the target user is searched in the updated service response data table according to the target user's ID.

[0054] Expanding on this, if the target server is a response server, it means that the target server corresponding to the target user has not changed in this round of updates. Based on the above example, it can be inferred that the target user is a user who has not perceived the anomaly. In this case, the pre-stored target login data corresponding to the target user ID can be directly obtained from the response server, and the specific business data requested by the target user can be obtained based on the target login data. Conversely, if the target server is a backup server, it means that the target server corresponding to the target user has changed in this round of iterations. Based on the above example, it can be inferred that the target user is a user who has perceived the anomaly. In this case, it is necessary to use the backup server to provide the target user with a second version of the service application to avoid the aforementioned perceived anomaly.

[0055] It's important to note that the backup server, acting as a temporary server, does not store all user login data. Therefore, when retrieving data, it needs to obtain the target user's login data through a distributed session cache system. This target login data is then used to retrieve the specific business data requested by the target user. Specifically, the target login data is pre-cached in the distributed session cache system by the response server. Distributing user login data reduces access latency caused by excessive client data, alleviates the pressure on the response server through traffic distribution, and ensures system operation even if the response server fails, as the backup server can retrieve data from the distributed session cache system.

[0056] This invention proposes a method for determining whether to redirect all user requests to a backup server based on the proportion of user-perceived anomalies. By redirecting some or all user requests to the backup server, the anomaly issues introduced by the new version of the service application can be effectively resolved. This efficient switching mechanism helps ensure service continuity, reduces inconvenience to users caused by service interruptions or anomalies, and improves service quality and user experience.

[0057] Example 2

[0058] Figure 2 This is a flowchart of another service response data table maintenance method provided in Embodiment 2 of the present invention. This embodiment is a refinement based on the above embodiment, and correspondingly, as shown below. Figure 2 As shown, the method specifically includes:

[0059] S210. When the update conditions of the service response data table are met, obtain the service complaint information within the preset time interval, and extract the abnormal service type from the service complaint information.

[0060] S220. Based on the service complaint information, trace back the user's historical service logs, extract historical service request parameters and historical service results from the user's historical service logs, and obtain the comparison service results of the first version of the service application for the historical service request parameters.

[0061] By analyzing a user's historical service logs, we can obtain the request parameters and results of historical services. Different request parameters correspond to different business requests, and the historical service results, combined with the above example, can represent the number of fixed deposit records displayed. Since the first version of the service application is an iterated new version of the product, the result obtained by responding to the request parameters of historical services using the first version of the service application is called the comparison service result. Again, using the above example, the comparison service result can also represent the number of fixed deposit records displayed.

[0062] S230. Based on the historical service results and the data differences between the comparison service results, locate the cause of the abnormality of the abnormal service type.

[0063] Comparing historical service results with comparison service results, specifically comparing the number of fixed deposit records displayed, indicates a discrepancy. If a difference exists, it suggests a data display discrepancy resulting from product version iteration. Determining the cause of the anomaly through data comparison is a prerequisite for subsequent data table maintenance. Only after confirming that the anomaly is indeed due to product iteration can such anomalies be resolved by deploying a backup server.

[0064] S240. Simulate each user requesting the abnormal service type in the first version of the service application and the second version of the service application respectively, and obtain the first service result and the second service result fed back by the first version of the service application and the second version of the service application for each user respectively.

[0065] S250. Count the number of users whose abnormality matches the first service result and the second service result, and calculate the ratio of the number of users to the total number of all users as the proportion of users experiencing abnormality.

[0066] At this point, for all users with fixed-term deposit accounts at the bank, their service requests in the two versions of the service application are simulated, and the corresponding service results are recorded. That is, if the first service result is consistent with the second service result, it indicates that the product update did not cause any significant anomalies, and the user is classified as not meeting the criteria for anomaly. If the first service result is inconsistent with the second service result, it indicates that the product update caused significant anomalies, and the user is classified as meeting the criteria for anomalies. This process categorizes customers based on the same type of abnormal service, thus identifying those who genuinely need to access the backup server, aiming to solve practical problems with fewer resources and improving maintenance efficiency.

[0067] S260. If the ratio value is greater than the preset threshold value, then the response server identifier of all user identifiers in the service response data table is replaced with the server identifier of the backup server to obtain the updated service response data table.

[0068] The threshold value is a preset proportion threshold. When the proportion value is greater than the threshold value, it means that there are too many users with user perception abnormalities. Therefore, the abnormality is considered to be widespread. If each user is maintained individually, the efficiency is low. Therefore, all response server identifiers in the service response data table are replaced with backup server identifiers. That is, all user requests are responded to using the second version of the service application. At this time, the updated service response data table only contains the backup data table.

[0069] S270. If the ratio value is less than or equal to a preset threshold value, the response server of the user identifier that matches the abnormal reason in the service response data table is replaced with the service identifier of the backup server to obtain an updated service response data table.

[0070] Conversely, when the ratio does not exceed the threshold, it indicates that the number of users experiencing abnormal user perception is still within a controllable range. In this case, the response server corresponding to the user experiencing abnormal user perception can be replaced with a backup server. The updated service response data table will then include both the response server and the backup server. Regardless of whether the ratio is high or low, it ensures that subsequent access for any user is normal, effectively resolving anomalies caused by the deployment of new version service applications, achieving targeted maintenance, and optimizing the user experience.

[0071] The technical solution of this invention refines the overall solution, focusing on the updating of the service response data table and the determination of the ratio value. Specifically, different server replacement strategies are implemented based on the ratio value, and the ratio value calculation requires comparing the results of the new version of the service with the historical service results to determine the number of users experiencing anomalies. When the ratio value is high, all user requests are diverted to the backup server to ensure that as many users as possible receive normal service; when the ratio value is low, only the requests of affected users are diverted to the backup server to balance resource usage and service stability. Whether diverting user requests to the response server or the backup server, efficient switching is achieved, enabling timely response and handling of abnormal service types after production changes.

[0072] Example 3

[0073] Figure 3 This is a schematic diagram of a service response data table maintenance device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes:

[0074] The abnormal service type extraction module 310 is used to obtain service complaint information within a preset time interval when the update conditions of the service response data table are met, and to extract the abnormal service type from the service complaint information.

[0075] The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application.

[0076] The anomaly cause location module 320 is used to trace back the user's historical service logs based on the service complaint information, and locate the anomaly cause of the anomaly type based on the user's historical service logs.

[0077] The proportion value determination module 330 is used to determine, based on the cause of the anomaly, the proportion of user-perceived anomalies when all users request the service of the abnormal service type.

[0078] The server identifier replacement module 340 is used to replace the response server identifier of some or all user identifiers in the service response data table with the server identifier of the backup server according to a ratio value, so as to obtain an updated service response data table, wherein the backup server is configured with a second version of the service application.

[0079] This invention proposes a method for determining whether to redirect all user requests to a backup server based on the proportion of user-perceived anomalies. By redirecting some or all user requests to the backup server, the anomaly issues introduced by the new version of the service application can be effectively resolved. This efficient switching mechanism helps ensure service continuity, reduces inconvenience to users caused by service interruptions or anomalies, and improves service quality and user experience.

[0080] Optionally, based on the above embodiments, the abnormal service type extraction module 310 is further configured to determine that the update conditions of the service response data table are met after the second version of the service application used for testing has been put into production and used as the first version of the service application and after a preset production and use period has elapsed.

[0081] Optionally, based on the above embodiments, the anomaly cause location module 320 may include:

[0082] The service result comparison unit is used to extract historical service request parameters and historical service results from the user's historical service log, and obtain the comparison service results of the first version of the service application for the historical service request parameters.

[0083] The anomaly cause localization unit is used to locate the anomaly cause of the anomaly type based on historical service results and data differences between the service results.

[0084] Optionally, based on the above embodiments, the ratio value determination module 330 may include:

[0085] The service result acquisition unit is used to simulate each user requesting the abnormal service type in the first version of the service application and the second version of the service application respectively, and to acquire the first service result and the second service result fed back by the first version of the service application and the second version of the service application for each user respectively.

[0086] The ratio calculation unit is used to count the number of users whose abnormality matches the first service result and the second service result, and to calculate the ratio of the number of users divided by the total number of all users as the ratio of the user-perceived abnormality.

[0087] Optionally, based on the above embodiments, the server identifier replacement module 340 may include:

[0088] The first replacement unit is used to replace the response server identifier of all user identifiers in the service response data table with the server identifier of the backup server if the ratio value is greater than a preset threshold value.

[0089] The second replacement unit is used to replace the response server of the user identifier that matches the abnormal reason in the service response data table with the service identifier of the backup server if the ratio value is less than or equal to a preset threshold value.

[0090] Optionally, based on the above embodiments, it further includes: a service request response unit, used to, after replacing the response server identifier of some or all user identifiers in the service response data table with the server identifier of the backup server according to a ratio value to obtain an updated service response data table, extract the target user identifier in the target service request in response to the target user's target service request.

[0091] Determine the server identifier of the target server corresponding to the target user identifier in the service response data table;

[0092] When the server identifier of the target server is the response server, the target login data corresponding to the target user identifier is obtained from the response server, and the first service result of the first version of the service application corresponding to the target service request is called in the response server using the target login data.

[0093] When the server identifier of the target server is a backup server, the target login data corresponding to the target user identifier is searched in the distributed session cache system, and the second service result of the second version of the service application corresponding to the target service request is called in the backup server using the target login data.

[0094] The response server stores a table relating user identifiers to login data, which is cached in a distributed session caching system.

[0095] The service response data table maintenance device provided in this embodiment of the invention can execute the service response data table maintenance method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0096] 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.

[0097] In addition, users are provided with corresponding operation entry points to choose whether to agree to or reject the automated decision results; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0098] Example 4

[0099] Figure 4 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0100] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0101] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0102] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a service response data table maintenance method.

[0103] That is: when the update conditions of the service response data table are met, obtain the service complaint information within the preset time range, and extract the abnormal service type from the service complaint information;

[0104] The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application.

[0105] Based on the service complaint information, the user's historical service logs are traced back, and the cause of the abnormality of the abnormal service type is located based on the user's historical service logs;

[0106] Based on the stated cause of the anomaly, the percentage of users experiencing an anomaly is determined when all users request the service of the anomaly type.

[0107] Based on the ratio, the response server identifiers of some or all user identifiers in the service response data table are replaced with the server identifiers of the backup server to obtain an updated service response data table, in which the backup server is configured with a second version of the service application.

[0108] In some embodiments, a service response data table maintenance method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the service response data table maintenance method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a service response data table maintenance method by any other suitable means (e.g., by means of firmware).

[0109] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0110] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0111] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0112] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0113] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0114] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0115] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0116] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for maintaining a service response data table, characterized in that, include: When the update conditions of the service response data table are met, obtain service complaint information within a preset time range and extract the abnormal service type from the service complaint information; The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application. Based on the service complaint information, the user's historical service logs are traced back, and the cause of the abnormality of the abnormal service type is located based on the user's historical service logs; Based on the stated cause of the anomaly, the percentage of users experiencing an anomaly is determined when all users request the service of the anomaly type. Based on the ratio, the response server identifiers of some or all user identifiers in the service response data table are replaced with the server identifiers of the backup server to obtain the updated service response data table. The backup server is configured with a second version of the service application.

2. The method according to claim 1, characterized in that, The update conditions for the service response data table must be met, including: After the second version of the service application used for testing is put into production and used as the first version of the service application, and after a preset production and use period, it is determined that the update conditions of the service response data table are met.

3. The method according to claim 1, characterized in that, The cause of the abnormal service type can be located based on the user's historical service logs, including: Extract historical service request parameters and historical service results from the user's historical service logs, and obtain the comparison service results of the first version of the service application for the historical service request parameters; Based on the data differences between historical service results and comparison service results, the cause of the abnormal service type is located.

4. The method according to claim 1, characterized in that, Based on the stated cause of the anomaly, the percentage of users experiencing a perceived anomaly when all users request services of the aforementioned abnormal service type includes: Simulate each user requesting the abnormal service type in the first version of the service application and the second version of the service application respectively, and obtain the first service result and the second service result returned by the first version of the service application and the second version of the service application for each user respectively; The number of users whose abnormality matches the first service result and the second service result is counted, and the ratio of the number of users to the total number of all users is calculated as the proportion of users experiencing abnormality.

5. The method according to claim 1, characterized in that, Based on the ratio, replace some or all of the user identifiers in the service response data table with the server identifiers of the backup server, including: If the ratio value is greater than the preset threshold value, then the response server identifier of all user identifiers in the service response data table will be replaced with the server identifier of the backup server. If the ratio is less than or equal to a preset threshold, the response server in the service response data table that matches the user identifier of the anomaly reason will be replaced with the service identifier of the backup server.

6. The method according to any one of claims 1-5, characterized in that, After replacing the response server identifiers of some or all user identifiers in the service response data table with the server identifiers of the backup server according to the ratio value, to obtain the updated service response data table, it also includes: In response to a target user's target service request, extract the target user identifier from the target service request; Determine the server identifier of the target server corresponding to the target user identifier in the service response data table; When the server identifier of the target server is the response server, the target login data corresponding to the target user identifier is obtained from the response server, and the first service result of the first version of the service application corresponding to the target service request is called in the response server using the target login data. When the server identifier of the target server is a backup server, the target login data corresponding to the target user identifier is searched in the distributed session cache system, and the second service result of the second version of the service application corresponding to the target service request is called in the backup server using the target login data. The response server stores a table relating user identifiers to login data, which is cached in a distributed session caching system.

7. A service response data table maintenance device, characterized in that, include: The abnormal service type extraction module is used to obtain service complaint information within a preset time range when the update conditions of the service response data table are met, and to extract the abnormal service type from the service complaint information. The service response data table stores the mapping relationship between user identifiers and server identifiers of response servers, and the response server is configured with the first version of the service application. The anomaly cause localization module is used to trace back the user's historical service logs based on service complaint information, and locate the anomaly cause of the anomaly type based on the user's historical service logs; The proportion value determination module is used to determine, based on the cause of the anomaly, the proportion of users experiencing an anomaly when all users request the service of the anomaly service type. The server identifier replacement module is used to replace the response server identifier of some or all user identifiers in the service response data table with the server identifier of the backup server according to a ratio value, so as to obtain an updated service response data table. The backup server is configured with a second version of the service application.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a service response data table maintenance method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute a service response data table maintenance method according to any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements a service response data table maintenance method according to any one of claims 1-6.

Images