Version rollback method and device of transaction system, storage medium and program product

Abstract

The embodiment of the invention provides a version rollback method and device of a transaction system, a storage medium and a program product, relates to the field of financial science and technology or other related fields, and is applied to computer equipment, the transaction system is deployed on the computer equipment, and system state information and current update card BIN data of the transaction system are obtained; calling two or more groups of historical card BIN data from a card BIN database according to the system state information; according to the current update card BIN data, performing version updating on a transaction system version of the transaction system; if the updated operation state of the transaction system is abnormal, determining target card BIN data from two or more groups of historical card BIN data according to the current updated card BIN data; according to the target card BIN data, the transaction system version of the transaction system is fallback, the transaction system after version fallback is obtained, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of fintech or other related fields, and particularly relates to a method, device, storage medium, and program product for rolling back the version of a trading system. Background Art

[0002] When the trading system provides trading services, it needs to use card BIN (Bank Identification Number) data as the basis for trading services, that is, the trading system only processes trading requests that are verified based on card BIN data, and then completes the trading services. Since there are many types of trading services, the amount of card BIN data is very large. To ensure the processing efficiency of the trading system, the card BIN data is added or deleted according to the actual types of trading services, and then the trading system version of the trading system is updated according to the added or deleted card BIN data, so that the trading system provides corresponding trading services.

[0003] For the addition and deletion operations on the card BIN data, due to the change of data, and then updating the trading system version of the trading system according to the added or deleted card BIN data, it may cause the update of the trading system to fail. In the prior art, when the update of the trading system fails, the trading system version of the trading system is rolled back to the previous trading system version so that the rolled-back trading system provides trading services.

[0004] However, the trading services provided by the trading system rolled back based on the solution of the prior art are determined based on the previous trading system version, and there are significant differences from the actual trading services that need to be provided currently, resulting in a problem of poor user experience. Summary of the Invention

[0005] This application provides a method, device, storage medium, and program product for rolling back the version of a trading system to solve the problem of poor user experience.

[0006] In a first aspect, this application provides a method for rolling back the version of a trading system, which is applied to a computer device on which a trading system is deployed. The method includes: obtaining the system status information of the trading system and the currently updated card BIN data; calling two or more groups of historical card BIN data from the card BIN database according to the system status information; updating the trading system version of the trading system according to the currently updated card BIN data; if the running status of the updated trading system is abnormal, determining target card BIN data from the two or more groups of historical card BIN data according to the currently updated card BIN data; and rolling back the trading system version of the trading system according to the target card BIN data to obtain the trading system after version rollback.

[0007] In a second aspect, the present application provides a version rollback device for a trading system, which is applied to a computer device on which a trading system is deployed. The device includes:

[0008] An acquisition module, configured to acquire the system status information of the trading system and the current updated card BIN data;

[0009] A processing module, configured to call two or more groups of historical card BIN data from a card BIN database according to the system status information; update the trading system version of the trading system according to the current updated card BIN data; if the running status of the updated trading system is abnormal, determine target card BIN data from the two or more groups of historical card BIN data according to the current updated card BIN data;

[0010] A rollback module, configured to roll back the trading system version of the trading system according to the target card BIN data to obtain a trading system after version rollback.

[0011] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0012] The memory stores computer execution instructions;

[0013] The processor executes the computer execution instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect as above.

[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the first aspect and / or various possible implementation manners of the first aspect as above.

[0015] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the first aspect and / or various possible implementation manners of the first aspect as above.

[0016] The version rollback method, device, storage medium and program product of the trading system provided by this application are applied to a computer device on which a trading system is deployed. By obtaining the system status information of the trading system and the current updated card BIN data; according to the system status information, calling two or more groups of historical card BIN data from the card BIN database; according to the current updated card BIN data, performing version update on the trading system version of the trading system; if the running status of the updated trading system is abnormal, then according to the current updated card BIN data, determining the target card BIN data from the two or more groups of historical card BIN data; according to the target card BIN data, performing rollback on the trading system version of the trading system to obtain the trading system after version rollback. By pre-calling two or more groups of historical card BIN data from the card BIN database according to the system status information of the trading system before performing the version update of the trading system, the rollback efficiency is improved when version rollback is required; further, if the running status of the updated trading system is abnormal, then by calculating the similarity between the current updated card BIN data and each group of historical card BIN data respectively, determining the historical card BIN data with the highest similarity as the target card BIN data, and performing version rollback on the trading system according to the target card BIN data to obtain the trading system after version rollback, so as to reduce the difference between the trading services provided by the trading system after version rollback and the actual trading services corresponding to the current updated card BIN data, that is, reducing the number of trading services that the trading system cannot provide to users, which also improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application and used together with the specification to explain the principles of this application.

[0018] Figure 1 It is a schematic diagram of a scenario of the version rollback method of the trading system provided by an embodiment of this application;

[0019] Figure 2 It is a flowchart of the version rollback method of the trading system provided by an embodiment of this application;

[0020] Figure 3 It is a flowchart of the version rollback method of the trading system provided by another embodiment of this application;

[0021] Figure 4 It is a schematic structural diagram of the version rollback device of the trading system provided by an embodiment of this application;

[0022] Figure 5 It is a schematic structural diagram of the electronic device provided by this application.

[0023] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and will be described in more detail hereinafter. These drawings and the written description are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Description of Specific Embodiments

[0024] Here, exemplary embodiments will be described in detail, and examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0025] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. Moreover, the processing of relevant data, such as collection, storage, use, processing, transmission, provision, disclosure, and application, complies with the relevant laws, regulations, and standards of the relevant regions, takes necessary confidentiality measures, does not violate public order and good customs, and provides corresponding operation entrances for users to choose to authorize or refuse.

[0026] In addition, the present application involves big data analysis of user information (including but not limited to personal biometric characteristics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and uses artificial intelligence technology for automated decision-making. For technical solutions that make decisions having a significant impact on personal rights and interests based on the results of automated decision-making, corresponding operation entrances are provided for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0027] It should be noted that the version rollback method, device, storage medium, and program product of the trading system provided by the present application can be used in the field of fintech, and can also be used in any field other than the field of fintech. The present application does not limit the application field of the version rollback method, device, storage medium, and program product of the trading system.

[0028] A specific application scenario of the present application is an application scenario where, after the trading system updates the version based on card BIN data, the version needs to be rolled back due to abnormal operating conditions. Figure 1 This is a schematic diagram of a scenario for the version rollback method of the trading system provided by the embodiments of the present application, as Figure 1As shown, the execution subject of the method provided by the embodiment of the present application can be an electronic control unit, an electronic device, or a terminal device. The terminal device includes a computer device. Taking the computer device as the execution subject for illustration, a trading system is deployed on the computer device. Exemplarily, for example, the trading system has a daily update cycle and updates the trading system version according to the currently updated card BIN (Bank Identification Number) data, thereby providing the current trading service corresponding to the currently updated card BIN data to customers. Before updating the trading system version of the trading system, based on the version rollback method of the trading system provided by the embodiment of the present application, the computer device calls historical card BIN data from the card BIN database according to the system status information, and then updates the trading system version. If the running state of the updated trading system is abnormal, the target card BIN data is determined from the historical card BIN data according to the currently updated card BIN data, and then the trading system version of the trading system is rolled back according to the target card BIN data to obtain the trading system after version rollback. For example, the trading system version 2.3 of the trading system is rolled back to the trading system version 1.x, thereby providing trading services to customers.

[0029] In the prior art, when the trading system update fails (the running state of the updated trading system is abnormal), the computer device will roll back the trading system version of the trading system to the previous trading system version so that the trading system after rollback provides trading services. However, the trading services provided by the trading system rolled back based on the solution of the prior art are determined based on the previous trading system version, which is quite different from the actual trading services that need to be provided currently, resulting in a poor user experience.

[0030] The version rollback method, device, storage medium, and program product of the trading system provided by the present application aim to solve the above technical problems in the prior art.

[0031] The following uses specific embodiments to elaborate in detail on the technical solution of the present application and how the technical solution of the present application solves the above technical problems. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0032] Figure 2 It is a flowchart of the version rollback method of the trading system provided by an embodiment of the present application, as Figure 2As shown in the figure, the execution subject of the version rollback method of the trading system provided in this embodiment can be an electronic control unit, an electronic device, or a terminal device. The terminal device includes a computer device. Exemplarily, in this embodiment, the computer device is used as the execution subject of the method in this embodiment for description. The version rollback method of the trading system provided in this embodiment is applied to a computer device on which a trading system is deployed, and includes the following steps:

[0033] Step S101, obtain the system status information of the trading system and the current updated card BIN data.

[0034] Exemplarily, according to the need to provide actual trading services, the trading system can update the trading system version with a daily update cycle, or can use a week, a month, or a non-fixed time interval as the update cycle to update the trading system version; furthermore, obtain the system status information of the trading system and the current updated card BIN data to provide data support for the subsequent steps of updating and rolling back the trading system version.

[0035] Step S102, according to the system status information, call two or more groups of historical card BIN data from the card BIN database.

[0036] Exemplarily, the system status information includes system time information. Furthermore, according to the system time information, call two or more groups of historical card BIN data from the card BIN database. In a possible implementation manner, determine the call rule for calling historical card BIN data according to the date interval in which the current date corresponding to the system time information is located, and then based on the call rule, call two or more groups of historical card BIN data from the card BIN database; for example, the current date corresponding to the system time information is March 5, 2024, and this current date is the first ten days of March; then the call rule Rule_1 for calling historical card BIN data is to call the card BIN data in the first ten days of the previous month of March, that is, call the card BIN data in the first ten days of February 2024, and the number of calls is two or more groups. Then the computer device calls two or more groups of historical card BIN data from the card BIN database according to the call rule Rule_1; or, the call rule Rule_2 for calling historical card BIN data is to call the card BIN data in the first ten days of the same month of the previous year of this year, that is, call the card BIN data in the first ten days of March 2023, and the number of calls is two or more groups. Then the computer device calls two or more groups of historical card BIN data from the card BIN database according to the call rule Rule_2.

[0037] Step S103, according to the current updated card BIN data, update the trading system version of the trading system.

[0038] Exemplarily, after obtaining the current updated card BIN data, the computer device updates the transaction system version of the transaction system deployed in the computer device according to the current updated card BIN data.

[0039] Step S104, if the running state of the updated transaction system is abnormal, determine the target card BIN data from two or more groups of historical card BIN data according to the current updated card BIN data.

[0040] Exemplarily, after updating the transaction system version of the transaction system deployed in the computer device, detect the running state of the updated transaction system. If the running state of the updated transaction system is normal, there is no need to roll back the version; if the running state of the updated transaction system is abnormal, compare the current updated card BIN data with two or more groups of historical card BIN data respectively, and then determine the target card BIN data from two or more groups of historical card BIN data. Specifically, for example, for each group of historical card BIN data, calculate the similarity between the current updated card BIN data and this group of historical card BIN data, and then determine the historical card BIN data with the closest similarity as the target card BIN data; demonstratively, convert the current updated card BIN data and the historical card BIN data into vectors, and then calculate the cosine value of the angle between the vector corresponding to the current updated card BIN data and the vectors corresponding to each historical card BIN data. Further, among the calculated cosine values of the angles, determine the historical card BIN data corresponding to the cosine value of the angle closest to 1 as the target card BIN data.

[0041] In another possible implementation manner, the specific implementation steps of step S104 include:

[0042] Step S1041, for each group of historical card BIN data, perform a set difference operation on the data set corresponding to the current updated card BIN data and the data set corresponding to this group of historical card BIN data to obtain a data difference set.

[0043] Exemplarily, for each group of historical card BIN data, subtract the data set corresponding to this group of historical card BIN data from the data set corresponding to the current updated card BIN data to obtain a data difference set, that is, use the data set corresponding to the current updated card BIN data minus the data set corresponding to this group of historical card BIN data to obtain the corresponding data difference set, where the data elements in the data difference set are all data elements that belong to the data set corresponding to the current updated card BIN data but do not belong to the data set corresponding to this group of historical card BIN data; specifically, for example, the data set corresponding to the current updated card BIN data is "a, b, c, d, e, f", and the data set corresponding to this group of historical card BIN data is "b, c, d, f, g, h", then the data difference set is "a, e".

[0044] Step S1042: Determine a target data difference set from the data difference sets corresponding to two or more groups of historical card BIN data according to the number of data elements in the data difference set corresponding to each group of historical card BIN data.

[0045] Step S1043: Determine the historical card BIN data corresponding to the target data difference set as the target card BIN data.

[0046] Exemplarily, after obtaining the data difference sets corresponding to each group of historical card BIN data, count the number of data elements in the data difference set corresponding to each group of historical card BIN data, and then determine the target data difference set from the data difference sets corresponding to two or more groups of historical card BIN data according to the number of data elements in the data difference set corresponding to each group of historical card BIN data. Among them, the target data difference set is the data difference set with the least number of data elements. The reason is that the fewer the number of data elements, the more data elements in the data set corresponding to a group of historical card BIN data include the data elements in the data set corresponding to the current updated card BIN data, and at the same time, the data elements that cause the abnormal operation state of the updated trading system do not exist in the data set corresponding to the historical card BIN data. Furthermore, according to the determined target data difference set, the historical card BIN data corresponding to the target data difference set can be determined as the target card BIN data.

[0047] Furthermore, the specific implementation manner of step S1043 includes:

[0048] Step S10431: Determine whether the target data difference set corresponds to two or more groups of historical card BIN data.

[0049] Step S10432: If the target data difference set corresponds to two or more groups of historical card BIN data, determine the historical card BIN data with the most number of data elements from the two or more groups of historical card BIN data; determine the historical card BIN data with the most number of data elements as the target card BIN data.

[0050] Step S10433: If the target data difference set corresponds to one group of historical card BIN data, determine the one group of historical card BIN data as the target card BIN data.

[0051] Exemplarily, after obtaining the target data difference set, it is determined whether the target data difference set corresponds to two or more sets of historical card BIN data; if the target data difference set corresponds to two or more sets of historical card BIN data, then from the two or more sets of historical card BIN data, the historical card BIN data with the largest number of data elements is determined; the historical card BIN data with the largest number of data elements is determined as the target card BIN data; specifically, for example, the target data difference set corresponds to three sets of historical card BIN data, the number of data elements in the first set of historical card BIN data is num_1, the number of data elements in the second set of historical card BIN data is num_2, and the number of data elements in the third set of historical card BIN data is num_3. Among num_1, num_2, and num_3, num_2 is the maximum value, which indicates that while the first set of historical card BIN data, the second set of historical card BIN data, and the third set of historical card BIN data all contain the data elements in the data set corresponding to the same currently updated card BIN data, among these three sets of historical card BIN data, the second set of historical card BIN data corresponding to num_2 also contains the largest number of other data elements. Therefore, the second set of historical card BIN data is determined as the target card BIN data. Correspondingly, if the target data difference set only corresponds to one set of historical card BIN data, then this set of historical card BIN data is determined as the target card BIN data.

[0052] In the steps of this embodiment, by means of data set calculation, the data difference between the currently updated card BIN data and each set of historical card BIN data is accurately determined, and then the historical card BIN data with the smallest data difference is determined as the target card BIN data. Further, when rolling back the transaction system version of the transaction system in the subsequent steps, the transaction service provided by the rolled-back transaction system has a small difference (or no difference) from the actual transaction service corresponding to the currently updated card BIN data, thereby solving the problem of poor user experience. Among them, the smallest data difference means that the number of data elements in the target data difference set is the least; further, based on the historical card BIN data, the transaction system version can be rolled back and run, while the currently updated card BIN data will cause the running state of the transaction system to be abnormal. Therefore, the data that causes the running state of the transaction system to be abnormal exists in the target data difference set. Furthermore, based on the target data difference set determined in step S1042, it can provide data support for analyzing the reason for the abnormal running state of the transaction system in the subsequent steps, that is, according to the target data difference set, the abnormal reason of the transaction system is determined.

[0053] Step S105, roll back the transaction system version of the transaction system according to the target card BIN data to obtain the transaction system after the version rollback.

[0054] Exemplarily, after obtaining the target card BIN data, the computer device rolls back the transaction system version of the transaction system according to the target card BIN data, and then obtains the transaction system after the version rollback, so as to provide transaction services to users.

[0055] The method provided in this embodiment is applied to a computer device on which a transaction system is deployed. By obtaining the system status information of the transaction system and the current updated card BIN data; according to the system status information, calling two or more groups of historical card BIN data from the card BIN database; according to the current updated card BIN data, performing version update on the transaction system version of the transaction system; if the running status of the updated transaction system is abnormal, then determining the target card BIN data from two or more groups of historical card BIN data according to the current updated card BIN data; and rolling back the transaction system version of the transaction system according to the target card BIN data to obtain the transaction system after the version rollback. By pre-calling two or more groups of historical card BIN data from the card BIN database according to the system status information of the transaction system before performing the transaction system version update, the rollback efficiency is improved when version rollback is required; further, if the running status of the updated transaction system is abnormal, then by calculating the similarity between the current updated card BIN data and each group of historical card BIN data respectively, determining the historical card BIN data with the highest similarity as the target card BIN data, and performing version rollback on the transaction system according to the target card BIN data to obtain the transaction system after the version rollback, so as to reduce the difference between the transaction services provided by the transaction system after the version rollback and the actual transaction services corresponding to the current updated card BIN data, that is, reducing the number of services that the transaction system cannot provide transaction services to users, which also improves the user experience.

[0056] Figure 3 For the flowchart of the version rollback method of the transaction system provided in another embodiment of the present application, as Figure 3 shown, based on the version rollback method of the transaction system provided in the embodiment shown in Figure 2 the embodiment shown, the step S102 is further refined. Then the version rollback method of the transaction system provided in this embodiment includes the following steps:

[0057] Step S201, obtain the system status information of the transaction system and the current updated card BIN data.

[0058] Step S202, determine the system maintenance information and historical transaction records of the transaction system according to the system status information.

[0059] Step S203, generate estimated transaction information according to the historical transaction records.

[0060] Step S204: Call two or more groups of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information.

[0061] Exemplarily, when the administrator of the trading system does not maintain the trading system, the probability of the trading system having an abnormal running state after being updated is relatively small. When the administrator of the trading system maintains the trading system, the probability of the trading system having an abnormal running state after being updated is relatively large. Therefore, according to the system status information of the trading system, determine the system maintenance information of the trading system, that is, determine whether the administrator of the trading system has maintained the trading system; further, according to the system status information, determine the historical transaction records of the trading system, and then generate estimated transaction information according to the transaction services corresponding to the historical transaction records to estimate the transaction services provided to the user; furthermore, according to the system maintenance information and the estimated transaction information, that is, call two or more groups of historical card BIN data from the card BIN database.

[0062] In the steps of this embodiment, by analyzing the system status information of the trading system, determine whether the trading system has undergone system maintenance and determine the historical transaction services provided by the trading system, so as to estimate the transaction services that are expected to be provided to the user according to the historical transaction services, and then adaptively call two or more groups of historical card BIN data from the card BIN database, improving the matching degree between the two or more groups of historical card BIN data called from the card BIN database and the currently updated card BIN data. When rolling back the trading system version of the trading system in subsequent steps, the transaction services provided by the rolled-back trading system have a small difference (or no difference) from the actual transaction services to be provided corresponding to the currently updated card BIN data, thereby solving the problem of poor user experience.

[0063] Furthermore, in a possible implementation manner, the specific implementation steps of step S204 include:

[0064] Step S2041: Determine the system maintenance level according to the system maintenance information; where the system maintenance level includes a primary maintenance level and a secondary maintenance level, and the maintenance scope corresponding to the secondary maintenance level is larger than the maintenance scope corresponding to the primary maintenance level.

[0065] Step S2042: If the system maintenance level is the primary maintenance level, call two groups of historical card BIN data from the card BIN database according to the primary maintenance level and the estimated transaction information.

[0066] Step S2043: If the system maintenance level is the secondary maintenance level, call multiple groups of historical card BIN data from the card BIN database according to the secondary maintenance level and the estimated transaction information.

[0067] Exemplarily, based on the system maintenance information, determine the maintenance scope of the administrator of the trading system for maintaining the trading system, and then determine the system maintenance level. Among them, the system maintenance level includes the first-level maintenance level and the second-level maintenance level. The maintenance scope corresponding to the second-level maintenance level is larger than the maintenance scope corresponding to the first-level maintenance level. That is, the larger the system maintenance scope, the higher the corresponding system maintenance level, and the greater the possibility of anomalies occurring after the trading system is updated. Furthermore, judge the system maintenance level. If the system maintenance level is the first-level maintenance level, call two sets of historical card BIN data from the card BIN database according to the first-level maintenance level and the estimated transaction information; if the system maintenance level is the second-level maintenance level, call multiple sets of historical card BIN data from the card BIN database according to the second-level maintenance level and the estimated transaction information.

[0068] In the steps of this embodiment, by analyzing the maintenance scope of the trading system maintenance, the corresponding system maintenance level is determined, and then according to the system maintenance level and the estimated transaction information, the historical card BIN data with the corresponding quantity and corresponding data content is determined, which improves the accuracy and efficiency of calling the historical card BIN data.

[0069] Furthermore, in another possible implementation manner, the specific implementation steps of step S204 include:

[0070] Step S204A, determine the system maintenance category according to the system maintenance information; among them, the system maintenance category includes the first maintenance category, the second maintenance category, and the third maintenance category. The first maintenance category is used to indicate the maintenance of the target data area of the trading system, and the target data area is the data area updated based on the currently updated card BIN data; the second maintenance category is used to indicate the maintenance of the data area associated with the target data area in the trading system; the third maintenance category is used to indicate the maintenance of the data area not related to the target data area in the trading system.

[0071] Step S204B, if the system maintenance category is the first maintenance category, call multiple sets of historical card BIN data from the card BIN database according to the first maintenance category and the estimated transaction information.

[0072] Step S204C, if the system maintenance category is the second maintenance category, call two sets or more of historical card BIN data from the card BIN database according to the second maintenance category and the estimated transaction information.

[0073] Step S204D, if the system maintenance category is the third maintenance category, call two sets of historical card BIN data from the card BIN database according to the third maintenance category and the estimated transaction information.

[0074] Exemplarily, based on the system maintenance information, determine the maintenance content of the transaction system maintained by the administrator of the transaction system, and then determine the system maintenance category; wherein, the system maintenance category includes the first maintenance category, the second maintenance category, and the third maintenance category. The first maintenance category is used to indicate the maintenance of the target data area of the transaction system, and the target data area is the data area updated based on the current updated card BIN data; the second maintenance category is used to indicate the maintenance of the data area associated with the target data area in the transaction system; the third maintenance category is used to indicate the maintenance of the data area not related to the target data area in the transaction system; further, whether it is related to the target data area determines the likelihood of an exception occurring after the transaction system is updated, that is, the more related, the greater the likelihood of an exception occurring.

[0075] Furthermore, judge the system maintenance category. If the system maintenance category is the first maintenance category, then call multiple groups of historical card BIN data from the card BIN database according to the first maintenance category and the estimated transaction information; if the system maintenance category is the second maintenance category, then call two or more groups of historical card BIN data from the card BIN database according to the second maintenance category and the estimated transaction information; if the system maintenance category is the third maintenance category, then call two groups of historical card BIN data from the card BIN database according to the third maintenance category and the estimated transaction information.

[0076] In the steps of this embodiment, by analyzing the maintenance content of the transaction system maintenance, the corresponding system maintenance category is determined, and then according to the system maintenance category and the estimated transaction information, the historical card BIN data with the corresponding quantity and the corresponding data content is determined, improving the accuracy and efficiency of the call of the historical card BIN data.

[0077] Step S205, update the version of the transaction system of the transaction system according to the current updated card BIN data.

[0078] Step S206, if the running state of the updated transaction system is abnormal, then determine the target card BIN data from two or more groups of historical card BIN data according to the current updated card BIN data.

[0079] Step S207, roll back the version of the transaction system of the transaction system according to the target card BIN data to obtain the transaction system after the version rollback.

[0080] In this embodiment, the implementation manners of step S201, step S205 - step S207 are the same as those of Figure 2 step S101, step S103 - step S105 in the embodiment shown in this application, and will not be elaborated here one by one.

[0081] Figure 4The structural schematic diagram of the version rollback device of the trading system provided by an embodiment of the present application is as follows Figure 4 As shown in Figure 4 , the version rollback device 3 of the trading system provided in this embodiment is applied to a computer device on which a trading system is deployed, and includes

[0082] An acquisition module 31, configured to acquire the system status information of the trading system and the current updated card BIN data

[0083] A processing module 32, configured to call two or more groups of historical card BIN data from the card BIN database according to the system status information; update the trading system version of the trading system according to the current updated card BIN data; if the running status of the updated trading system is abnormal, determine the target card BIN data from two or more groups of historical card BIN data according to the current updated card BIN data

[0084] A rollback module 33, configured to roll back the trading system version of the trading system according to the target card BIN data to obtain the trading system after version rollback

[0085] In a possible implementation manner, when the processing module 32 calls two or more groups of historical card BIN data from the card BIN database according to the system status information, it is specifically configured to: determine the system maintenance information and historical transaction records of the trading system according to the system status information; generate estimated transaction information according to the historical transaction records; call two or more groups of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information

[0086] In a possible implementation manner, when the processing module 32 calls two or more groups of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information, it is specifically configured to: determine the system maintenance level according to the system maintenance information; where the system maintenance level includes a primary maintenance level and a secondary maintenance level, and the maintenance scope corresponding to the secondary maintenance level is larger than the maintenance scope corresponding to the primary maintenance level; if the system maintenance level is the primary maintenance level, call two groups of historical card BIN data from the card BIN database according to the primary maintenance level and the estimated transaction information; if the system maintenance level is the secondary maintenance level, call multiple groups of historical card BIN data from the card BIN database according to the secondary maintenance level and the estimated transaction information

[0087] In a possible implementation manner, when the processing module 32 calls two or more groups of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information, it is specifically used for: determining the system maintenance category according to the system maintenance information; wherein, the system maintenance category includes a first maintenance category, a second maintenance category, and a third maintenance category, the first maintenance category is used to indicate the maintenance of the target data area of the transaction system, and the target data area is the data area for data update based on the currently updated card BIN data; the second maintenance category is used to indicate the maintenance of the data area associated with the target data area in the transaction system; the third maintenance category is used to indicate the maintenance of the data area not related to the target data area in the transaction system; if the system maintenance category is the first maintenance category, then call multiple groups of historical card BIN data from the card BIN database according to the first maintenance category and the estimated transaction information; if the system maintenance category is the second maintenance category, then call two or more groups of historical card BIN data from the card BIN database according to the second maintenance category and the estimated transaction information; if the system maintenance category is the third maintenance category, then call two groups of historical card BIN data from the card BIN database according to the third maintenance category and the estimated transaction information.

[0088] In a possible implementation manner, when the processing module 32 determines the target card BIN data from two or more groups of historical card BIN data according to the currently updated card BIN data, it is specifically used for: for each group of historical card BIN data, perform a set difference operation on the data set corresponding to the currently updated card BIN data and the data set corresponding to this group of historical card BIN data to obtain a data difference set; determine the target data difference set from the data difference sets corresponding to the two or more groups of historical card BIN data according to the number of data elements in the data difference set corresponding to each group of historical card BIN data; and determine the historical card BIN data corresponding to the target data difference set as the target card BIN data.

[0089] In a possible implementation manner, when the processing module 32 determines the historical card BIN data corresponding to the target data difference set as the target card BIN data, it is specifically used for: determining whether the target data difference set corresponds to two or more groups of historical card BIN data; if the target data difference set corresponds to two or more groups of historical card BIN data, then determine the historical card BIN data with the largest number of data elements from the two or more groups of historical card BIN data; and determine the historical card BIN data with the largest number of data elements as the target card BIN data; if the target data difference set corresponds to one group of historical card BIN data, then determine the one group of historical card BIN data as the target card BIN data.

[0090] Among them, the acquisition module 31, the processing module 32, and the fallback module 33 are connected in sequence. The version fallback device 3 of the transaction system provided in this embodiment can execute as Figures 2 - 3The technical solutions of any of the method embodiments shown above have similar implementation principles and technical effects, which will not be elaborated here.

[0091] Figure 5 FIG. is a schematic structural diagram of an electronic device provided by the present application. As Figure 5 shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. Among them, the processor 501, the memory 502, and the communication component 503 are connected through a bus 504.

[0092] In a specific implementation process, at least one processor 501 executes computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above-mentioned method.

[0093] For the specific implementation process of the processor 501, reference can be made to the above method embodiment, and its implementation principle and technical effects are similar, which will not be elaborated here in this embodiment.

[0094] In the above embodiment, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0095] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0096] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0097] The present application also provides a computer program product, including a computer program which, when executed by a processor, implements the above-mentioned method.

[0098] The present application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-mentioned method.

[0099] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0100] It should be further noted that although the steps in the flowchart are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order restriction, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0101] It should be understood that the above device embodiments are illustrative, and the devices of the present application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0102] In addition, unless otherwise specified, in each embodiment of the present application, each functional unit / module can be integrated in one unit / module, or each unit / module can exist physically alone, or two or more units / modules can be integrated together. The above integrated unit / module can be implemented in the form of hardware or in the form of a software program module.

[0103] When the integrated unit / module is implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory (RRAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), an enhanced dynamic random access memory (EDRAM), a high-bandwidth memory (HBM), a hybrid memory cube (HMC), etc.

[0104] When the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of this application. And the aforementioned memory includes: USB flash drives, read-only memories (ROMs), random access memories (RAMs), external hard drives, magnetic disks, or optical discs, etc., all kinds of media that can store program codes.

[0105] In the above embodiments, the descriptions of each embodiment have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, 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, it should be considered as the scope recorded in this specification.

[0106] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include well-known common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0107] It should be understood that the present application is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A version rollback method for a trading system, characterized in that: Applied to a computer device, wherein a transaction system is deployed on the computer device, the method comprises: Obtaining system status information of the transaction system and current update card BIN data; Retrieving two or more sets of historical card BIN data from a card BIN database according to the system status information; According to the current update card BIN data, the transaction system version of the transaction system is updated; If the operating state of the updated transaction system is abnormal, the target card BIN data is determined from the two or more groups of historical card BIN data according to the current updated card BIN data; According to the target card BIN data, the transaction system version of the transaction system is rolled back to obtain a transaction system after the version rollback.

2. The method according to claim 1, characterized in that The calling two or more sets of historical card BIN data from a card BIN database according to the system status information includes: Determining system maintenance information and historical transaction records of the transaction system according to the system status information; Generate estimated transaction information based on historical transaction records; The two or more groups of historical card BIN data are called from the card BIN database according to the system maintenance information and the estimated transaction information.

3. The method according to claim 2, characterized in that The calling the two or more sets of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information includes: Determine the system maintenance level according to the system maintenance information; wherein the system maintenance level includes a first-level maintenance level and a second-level maintenance level, and the maintenance scope corresponding to the second-level maintenance level is greater than the maintenance scope corresponding to the first-level maintenance level; If the system maintenance level is the first-level maintenance level, calling the two sets of historical card BIN data from the card BIN database according to the first-level maintenance level and the estimated transaction information; If the system maintenance level is the second-level maintenance level, the multiple groups of historical card BIN data are called from the card BIN database according to the second-level maintenance level and the estimated transaction information.

4. The method according to claim 2, characterized in that: The calling the two or more sets of historical card BIN data from the card BIN database according to the system maintenance information and the estimated transaction information includes: Determine a system maintenance category according to the system maintenance information; wherein the system maintenance category includes a first maintenance category, a second maintenance category and a third maintenance category, wherein the first maintenance category is used to indicate maintenance of a target data area of ​​the transaction system, wherein the target data area is a data area for data update based on the current update card BIN data; the second maintenance category is used to indicate maintenance of a data area in the transaction system associated with the target data area; and the third maintenance category is used to indicate maintenance of a data area in the transaction system that is not associated with the target data area; If the system maintenance category is the first maintenance category, calling the multiple sets of historical card BIN data from the card BIN database according to the first maintenance category and the estimated transaction information; If the system maintenance category is the second maintenance category, calling the two or more sets of historical card BIN data from the card BIN database according to the second maintenance category and the estimated transaction information; If the system maintenance category is the third maintenance category, the two groups of historical card BIN data are called from the card BIN database according to the third maintenance category and the estimated transaction information.

5. The method according to claim 1, characterized in that The step of determining the target card BIN data from the two or more groups of historical card BIN data according to the current update card BIN data comprises: For each set of historical card BIN data, performing a set difference operation on the data set corresponding to the current updated card BIN data and the data set corresponding to the set of historical card BIN data to obtain a data difference set; Determine a target data difference set from the data difference sets corresponding to the two or more sets of historical card BIN data according to the number of data elements in the data difference set corresponding to each set of historical card BIN data; The historical card BIN data corresponding to the target data difference set is determined as the target card BIN data.

6. The method according to claim 5, characterized in that The step of determining the historical card BIN data corresponding to the target data difference set as the target card BIN data includes: Determine whether the target data difference set corresponds to two or more sets of historical card BIN data; If the target data difference set corresponds to two or more groups of historical card BIN data, determine the historical card BIN data with the largest number of data elements from the two or more groups of historical card BIN data; determine the historical card BIN data with the largest number of data elements as the target card BIN data; If the target data difference set corresponds to a set of historical card BIN data, the set of historical card BIN data is determined as the target card BIN data.

7. A version rollback device for a trading system, characterized in that: Applied to a computer device, wherein a transaction system is deployed on the computer device, the device comprises: An acquisition module, used to acquire system status information of the transaction system and current update card BIN data; A processing module, configured to call two or more groups of historical card BIN data from a card BIN database according to the system status information; update the transaction system version of the transaction system according to the current updated card BIN data; if the operation status of the updated transaction system is abnormal, determine the target card BIN data from the two or more groups of historical card BIN data according to the current updated card BIN data; The rollback module is used to roll back the transaction system version of the transaction system according to the target card BIN data to obtain the transaction system after the version rollback.

8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images