CN113793137A - Mobile banking version release control method and device - Google Patents
Mobile banking version release control method and device Download PDFInfo
- Publication number
- CN113793137A CN113793137A CN202111154650.8A CN202111154650A CN113793137A CN 113793137 A CN113793137 A CN 113793137A CN 202111154650 A CN202111154650 A CN 202111154650A CN 113793137 A CN113793137 A CN 113793137A
- Authority
- CN
- China
- Prior art keywords
- user
- version
- mobile phone
- information
- users
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000004519 manufacturing process Methods 0.000 claims abstract description 27
- 238000004590 computer program Methods 0.000 claims description 17
- 230000011218 segmentation Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 6
- 238000012795 verification Methods 0.000 description 5
- 230000001276 controlling effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000003111 delayed effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/108—Remote banking, e.g. home banking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a mobile phone bank version release control method and a mobile phone bank version release control device, wherein the method comprises the following steps: collecting user information of a mobile phone bank, flow statistic information of user login and transaction information of funds; dividing users into a plurality of batch nodes; starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes: carrying out automatic deployment of the mobile phone bank gray-scale version; acquiring a user production log for deploying a mobile phone bank gray-scale version; when the error log is not captured, carrying out automatic deployment on the mobile phone bank gray scale version by the users of the next batch of nodes; and when the error log is captured, version rollback is carried out, the mobile phone bank gray-scale version is off-shelved, and after the repair is completed, the automatic deployment of the mobile phone bank gray-scale version is carried out from the users of the first batch of nodes. The invention relates to the technical field of Internet of things, and can control the risk influence range of the release of the mobile phone bank grayscale version and improve the user experience.
Description
Technical Field
The invention relates to the technical field of Internet of things, in particular to a mobile phone bank version release control method and device.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
With the rapid development of digital economy, mobile banking as a main customer channel of banks becomes more and more important, and the stability and safety of versions related to the mobile banking also become more and more important, so that the on-line of new functions and the transformation of original old functions become cautious, and serious consequences and social influence can be caused once problems occur. One scheme in the prior art is that the grayscale version of the mobile phone bank is pushed to the full number of users, so that the full number of users verify the grayscale version together, and once a problem occurs, the version release is delayed or the versions need to be reissued, so that the use of the full number of users is influenced, and the extremely poor user experience is caused; another scheme in the prior art is to collect user data by adopting a manual white list in the background and enable the users to help the verification together, the version verification mode needs manual operation and has the possibility of misoperation, and the version is delayed to be released or reissued after the verification is in a problem.
Disclosure of Invention
The embodiment of the invention provides a mobile phone bank version release control method, which is used for ensuring the version quality, controlling the risk influence range of mobile phone bank gray-scale version release, reducing the misoperation of manual operation, being more efficient and safer and improving the user experience, and comprises the following steps:
collecting user information of a mobile phone bank, flow statistic information of user login and transaction information of funds;
dividing the user into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds;
starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
The embodiment of the invention also provides a mobile banking version release control device, which is used for ensuring the version quality, controlling the risk influence range of mobile banking gray-scale version release, reducing the misoperation of manual operation, being more efficient and safer and improving the user experience, and comprises the following steps:
the information collection module is used for collecting user information of the mobile banking, flow statistical information of user login and transaction information of funds;
the user dividing module is used for dividing the users into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds;
the execution module is used for starting from the users of the first batch of nodes and sequentially executing the following steps for the users of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the mobile phone bank version release control method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program for executing the mobile phone bank version release control method.
In the embodiment of the invention, user information of a mobile phone bank, flow statistical information of user login and transaction information of funds are collected; dividing the user into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds; starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes: carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online; acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log; when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again. Compared with the technical scheme in the prior art, the automatic deployment of the grayscale versions can be carried out in batches by dividing the user into a plurality of batches of nodes, the version quality is guaranteed, the risk influence range of the grayscale version release of the mobile phone bank is controlled, the misoperation of manual operation is reduced, the efficiency is higher, the safety is higher, and the user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
fig. 1 is a flowchart of a mobile banking version release control method provided in an embodiment of the present invention;
FIG. 2 is a flowchart of a user dividing the user into a plurality of batch nodes according to an embodiment of the present invention;
fig. 3 is a flowchart of automated deployment of a mobile banking grayscale version provided in an embodiment of the present invention;
fig. 4 is a schematic diagram of a mobile banking version release control apparatus provided in an embodiment of the present invention;
fig. 5 is a schematic diagram of a computer device provided in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
An embodiment of the present invention provides a mobile banking version release control method, fig. 1 is a flowchart of the mobile banking version release control method provided in the embodiment of the present invention, and as shown in fig. 1, the method includes the following steps:
step 101: collecting user information of a mobile phone bank, flow statistic information of user login and transaction information of funds;
step 102: dividing the user into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds;
step 103: starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error log is not captured, carrying out automatic deployment on the mobile phone bank gray scale version by the users of the next batch of nodes; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
As can be seen from the flow shown in fig. 1, the method for controlling release of a mobile banking version in the embodiment of the present invention is different from a technical scheme in the prior art in which a grayscale version of a mobile banking is pushed to a full number of users to be verified together, and is also different from a technical scheme in the prior art in which a manual white list is used to collect user data in a background to help the users to be verified together.
During specific implementation, firstly, user information of a mobile phone bank, flow statistic information of user login and transaction information of funds are collected, and then, according to the collected user information, the flow statistic information of user login and the transaction information of funds, the user is divided into a plurality of batches of node users. In an embodiment, the user information may comprise, for example, a user zone. Fig. 2 is a flowchart of a user dividing the user into a plurality of batch nodes according to an embodiment of the present invention, as shown in fig. 2, in this example, the user is divided into a plurality of batch nodes according to the collected user information, the traffic statistic information of the user login, and the transaction information of the fund, which includes the following steps:
step 201: judging the size of the user influence range according to the user region, the flow statistical information logged by the user and the transaction information of funds;
step 202: and according to the size of the user influence range, dividing the users into the users of a plurality of batches of nodes according to the influence range from small to large.
In the embodiment, a plurality of user regions are divided according to the risk influence range of the user regions on the release of the mobile phone bank gray-scale version from small to large, then the number of users in each batch is determined by combining the flow statistical information logged by the users and the transaction information of funds, a batch of users with the minimum risk influence range of the release of the mobile phone bank gray-scale version is selected as a first batch node, a batch of users with the influence range which is slightly larger than that of the first batch node and is relatively close to that of the first batch node is selected as a second batch node, and the like, and the users are divided into a plurality of batches of users according to the influence range from small to large. The user information may further include a user client number and/or a user mobile phone number.
In one embodiment, the transaction information for the funds may include a transaction amount of the funds. In the embodiment, a rule set for dividing the user is preset according to the transaction amount of funds, the flow statistical information of user login and the user region.
In one embodiment, dividing users into a plurality of batches of users of nodes according to the collected user information, the flow statistic information logged by the users and the transaction information of funds may include: and dividing the users into a plurality of batches of nodes according to the collected user information, the flow statistical information and fund transaction information of user login and a rule set based on the user information and the version information in advance. For example, in this example, the user information, the flow statistic information of the user login, and the transaction information of the fund are respectively given to the risk influence range of the mobile phone bank grayscale version release with an influence coefficient, the influence coefficient and the influence range are positively correlated, the influence coefficient is calculated according to the calculation rule in advance based on the user information and the version information set, and the user is divided into a plurality of batches of users of nodes according to the division rule in advance based on the rule set of the user information mixed version information.
After dividing users into a plurality of batches of nodes, starting from the user of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes: carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online; acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log; when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
Starting from a user of a first batch node, automatically deploying a mobile phone bank gray-scale version; the mobile phone bank grayscale version is a new version of the mobile phone bank to be online. Fig. 3 is a flowchart of automated deployment of a mobile banking grayscale version provided in the embodiment of the present invention, and as shown in fig. 3, in this example, automated deployment of a mobile banking grayscale version is performed, including the following steps:
step 301: writing program codes for automatic deployment of the mobile phone bank gray scale version by using JAVA language according to a rule set based on user information and version information;
step 302: and according to the written program code for automatically deploying the mobile phone bank grayscale version, automatically deploying the mobile phone bank grayscale version.
In the embodiment, according to a rule set of a user who divides the user into a plurality of batch nodes and based on user information and version information, a program code for automatically deploying the mobile phone bank gray-scale version is written by using a JAVA language, so that the user information of the first batch nodes, which needs to be automatically deployed by the mobile phone bank gray-scale version, is automatically acquired, and the mobile phone bank gray-scale version of the user of the first batch nodes is automatically deployed.
After the automatic deployment of the mobile phone bank gray scale version is carried out on the users of the first batch of nodes, a user production log for deploying the mobile phone bank gray scale version is obtained, and an error log is captured in the user production log. In the embodiment, according to the program code for automatically deploying the mobile phone bank grayscale version, the program code for automatically acquiring the user production log is written by using JAVA language, so that the user production log for automatically deploying the mobile phone bank grayscale version is automatically acquired, and an error log is captured in the user production log.
In one embodiment, when capturing the error log, invoking an online running version of a mobile banking machine to perform version rollback, and repairing an off-shelf mobile banking grayscale version may include: and sending the captured error log to an error handler. For example, in this example, according to a programmed program code for automatically acquiring a production log, automatically analyzing whether an error is thrown out from the production log of a user, when the error log is captured, automatically sending the error log to an error handler, then triggering a calling interface, automatically calling an online running version of a mobile phone bank to perform version rollback, and restoring a grayscale version of an off-shelf mobile phone bank to realize quick positioning and quick solution of the problem of the grayscale version of the mobile phone bank; and after the repairing is finished, the automatic deployment of the mobile phone bank gray scale version is carried out from the users of the first batch of nodes again.
In one embodiment, when the error log is not captured, the automatic deployment of the mobile phone bank grayscale version is carried out on the users of the next batch of nodes until the user deployment of all the batches of nodes is completed. In the embodiment, when no error is reported in the automatic deployment and verification process of the mobile phone bank grayscale version, the users of the next batch of nodes are automatically triggered to carry out the automatic deployment of the mobile phone bank grayscale version until the users of the last batch of nodes carry out the automatic deployment of the mobile phone bank grayscale version and the verification is reported without error, and the automatic deployment of the mobile phone bank grayscale version is completed.
The embodiment of the invention also provides a mobile phone bank version release control device, which is described in the following embodiment. The principle of the device for solving the problems is similar to the mobile phone bank version release control method, so the implementation of the device can refer to the implementation of the mobile phone bank version release control method, and repeated parts are not described again.
The embodiment of the invention provides a mobile phone bank version release control device, fig. 4 is a schematic diagram of the mobile phone bank version release control device provided in the embodiment of the invention, and as shown in fig. 4, the device comprises the following modules:
the information collection module 41 is used for collecting user information of the mobile banking, flow statistic information of user login and transaction information of funds;
the user dividing module 42 is used for dividing the user into a plurality of batches of users of nodes according to the collected user information, the flow statistical information of user login and the transaction information of fund;
an executing module 43, configured to, starting from the user of the first batch of nodes, sequentially execute the following steps for the user of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
In one embodiment, the user information includes a user zone; the user dividing module 42 is specifically configured to: judging the size of the user influence range according to the user region, the flow statistical information logged by the user and the transaction information of funds; and according to the size of the user influence range, dividing the users into the users of a plurality of batches of nodes according to the influence range from small to large.
In one embodiment, the user information further includes a user customer number, and/or a user phone number.
In one embodiment, the transaction information for funds includes a transaction amount for the funds.
In one embodiment, the user segmentation module 42 is specifically configured to: and dividing the users into a plurality of batches of nodes according to the collected user information, the flow statistical information and fund transaction information of user login and a rule set based on the user information and the version information in advance.
In one embodiment, when capturing the error log, the execution module 43 is specifically configured to: and sending the captured error log to an error handler.
Fig. 5 is a schematic diagram of a computer device provided in an embodiment of the present invention, and as shown in fig. 5, the computer device 500 includes: a memory 510, a processor 520, and a computer program 530 stored on the memory 510 and executable on the processor 520, when executing the computer program 530, effecting: the mobile phone bank version release control method.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program for executing the method for controlling release of a mobile banking version is stored, and when executed by a processor, the computer program implements: the mobile phone bank version release control method.
In summary, in the embodiment of the present invention, user information of the mobile banking, flow statistics information of user login, and transaction information of funds are collected; dividing the user into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds; starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes: carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online; acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log; when the error log is not captured, carrying out automatic deployment on the mobile phone bank gray scale version by the users of the next batch of nodes; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again. Compared with the technical scheme in the prior art, the automatic deployment of the grayscale versions can be carried out in batches by dividing the user into a plurality of batches of nodes, the version quality is guaranteed, the risk influence range of the grayscale version release of the mobile phone bank is controlled, the misoperation of manual operation is reduced, the efficiency is higher, the safety is higher, and the user experience is improved.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart or block diagram block or blocks.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (14)
1. A mobile banking version release control method is characterized by comprising the following steps:
collecting user information of a mobile phone bank, flow statistic information of user login and transaction information of funds;
dividing the user into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds;
starting from the users of the first batch of nodes, the following steps are sequentially executed for the users of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
2. The mobile banking version release control method of claim 1, wherein the user information includes a user zone;
dividing the user into a plurality of batch nodes according to the collected user information, the flow statistical information of user login and the transaction information of funds, wherein the batch nodes comprise:
judging the size of the user influence range according to the user region, the flow statistical information logged by the user and the transaction information of funds;
and according to the size of the user influence range, dividing the users into the users of a plurality of batches of nodes according to the influence range from small to large.
3. The mobile banking version release control method of claim 2, wherein the user information further includes a user customer number, and/or a user mobile phone number.
4. The mobile banking version release control method as claimed in claim 1, wherein the transaction information of the fund includes a transaction amount of the fund.
5. The method as claimed in claim 1, wherein the step of dividing the users into a plurality of batches of nodes according to the collected user information, the flow statistical information of user login and the transaction information of funds comprises:
and dividing the users into a plurality of batches of nodes according to the collected user information, the flow statistical information and fund transaction information of user login and a rule set based on the user information and the version information in advance.
6. The method for controlling release of a mobile banking version as claimed in claim 1, wherein when capturing an error log, calling an online running version of a mobile banking machine to perform version rollback and an off-shelf mobile banking grayscale version to perform repair comprises:
and sending the captured error log to an error handler.
7. A mobile banking version release control device is characterized by comprising:
the information collection module is used for collecting user information of the mobile banking, flow statistical information of user login and transaction information of funds;
the user dividing module is used for dividing the users into a plurality of batches of node users according to the collected user information, the flow statistical information of user login and the transaction information of funds;
the execution module is used for starting from the users of the first batch of nodes and sequentially executing the following steps for the users of each batch of nodes:
carrying out automatic deployment of the mobile phone bank gray-scale version; the mobile phone bank gray scale version is a new version of the mobile phone bank to be online;
acquiring a user production log for deploying a mobile phone bank gray-scale version, and capturing an error log in the user production log;
when the error logs are not captured, carrying out automatic deployment on the mobile phone bank gray-scale versions by users of next batch of nodes until the deployment of the users of all the batches of nodes is completed; when the error log is captured, calling the online running version of the mobile phone bank to perform version rollback, restoring the off-shelf mobile phone bank gray-scale version, and after restoration is completed, starting automatic deployment of the mobile phone bank gray-scale version from the user of the first batch of nodes again.
8. The mobile banking version release control device of claim 7, wherein the user information includes a user zone;
the user division module is specifically configured to:
judging the size of the user influence range according to the user region, the flow statistical information logged by the user and the transaction information of funds;
and according to the size of the user influence range, dividing the users into the users of a plurality of batches of nodes according to the influence range from small to large.
9. The apparatus for controlling release of mobile banking version as claimed in claim 8, wherein the user information further includes a user customer number, and/or a user mobile phone number.
10. The mobile banking version release control apparatus of claim 7, wherein the transaction information of the funds includes a transaction amount of the funds.
11. The mobile banking version release control device of claim 7, wherein the user segmentation module is specifically configured to:
and dividing the users into a plurality of batches of nodes according to the collected user information, the flow statistical information and fund transaction information of user login and a rule set based on the user information and the version information in advance.
12. The mobile banking version release control device of claim 7, wherein the execution module is further configured to:
and sending the captured error log to an error handler.
13. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the mobile banking version release control method of any one of claims 1 to 6 when executing the computer program.
14. A computer-readable storage medium storing a computer program for executing the mobile banking version release control method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111154650.8A CN113793137A (en) | 2021-09-29 | 2021-09-29 | Mobile banking version release control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111154650.8A CN113793137A (en) | 2021-09-29 | 2021-09-29 | Mobile banking version release control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113793137A true CN113793137A (en) | 2021-12-14 |
Family
ID=79184496
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111154650.8A Pending CN113793137A (en) | 2021-09-29 | 2021-09-29 | Mobile banking version release control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113793137A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111158715A (en) * | 2019-12-19 | 2020-05-15 | 中国平安财产保险股份有限公司 | Gray scale release control method and system |
| CN112130892A (en) * | 2020-09-23 | 2020-12-25 | 平安科技（深圳）有限公司 | Product gray level release method, device, equipment and storage medium |
| CN113138880A (en) * | 2021-04-09 | 2021-07-20 | 浙商银行股份有限公司 | Block chain system gray level release method, device, equipment and storage medium |
| CN113138774A (en) * | 2021-05-11 | 2021-07-20 | 中国工商银行股份有限公司 | Gradation issuing method, gradation issuing apparatus, electronic device, gradation issuing medium, and program product |
| CN113450158A (en) * | 2021-07-09 | 2021-09-28 | 中国银行股份有限公司 | Bank activity information pushing method and device |
-
2021
- 2021-09-29 CN CN202111154650.8A patent/CN113793137A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111158715A (en) * | 2019-12-19 | 2020-05-15 | 中国平安财产保险股份有限公司 | Gray scale release control method and system |
| CN112130892A (en) * | 2020-09-23 | 2020-12-25 | 平安科技（深圳）有限公司 | Product gray level release method, device, equipment and storage medium |
| CN113138880A (en) * | 2021-04-09 | 2021-07-20 | 浙商银行股份有限公司 | Block chain system gray level release method, device, equipment and storage medium |
| CN113138774A (en) * | 2021-05-11 | 2021-07-20 | 中国工商银行股份有限公司 | Gradation issuing method, gradation issuing apparatus, electronic device, gradation issuing medium, and program product |
| CN113450158A (en) * | 2021-07-09 | 2021-09-28 | 中国银行股份有限公司 | Bank activity information pushing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109598604B (en) | Day-to-day cutting judgment method and device | |
| CN106685894B (en) | Risk identification method, device and system | |
| US11586534B2 (en) | Identifying flaky tests | |
| CN110599341A (en) | Transaction calling method and system | |
| CN112732571A (en) | Test data generation method and device | |
| CN112114903A (en) | File loading method and device | |
| CN112148614A (en) | Regression testing method and device | |
| CN110795326A (en) | Code interception detection method, storage medium, electronic device and system | |
| CN112835682B (en) | Data processing method, device, computer equipment and readable storage medium | |
| CN107193619B (en) | Method and device for automatically updating compiled version | |
| CN113793137A (en) | Mobile banking version release control method and device | |
| CN107016613B (en) | Data modification method and device | |
| CN116402325A (en) | Automatic business process processing method and device | |
| CN115757618A (en) | Identity card information synchronization method and device | |
| CN113962789A (en) | Bank account checking method and device | |
| CN114971638A (en) | Transaction authentication method and device based on risk identification | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN113392009A (en) | Exception handling method and device for automatic test | |
| CN112433950A (en) | Method for automatically building test environment, electronic equipment and storage medium | |
| CN110908976A (en) | Accumulation fund data acquisition method and system | |
| CN110716855B (en) | Processor instruction set testing method and device | |
| CN111737036B (en) | Service processing method and device based on robot flow automation | |
| CN113129132A (en) | Credit credit product application method and device based on block chain | |
| CN113436004A (en) | Transaction processing method and device based on core bank system | |
| CN106709803B (en) | Payment service monitoring processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |