CN116777518A

CN116777518A - Transaction management method, device, storage medium and equipment

Info

Publication number: CN116777518A
Application number: CN202310573547.XA
Authority: CN
Inventors: 郑春益; 刘泽华
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2023-05-18
Filing date: 2023-05-18
Publication date: 2023-09-19

Abstract

The specification discloses a transaction management method, a device, a storage medium and equipment, wherein the method comprises the following steps: firstly, historical budget verification data aiming at resource popularization affairs are obtained, the historical budget verification data comprises continuous unit budget verification data corresponding to unit time periods respectively, each transaction verification request generated in the unit time periods is the sum value of first budget verification data corresponding to each transaction verification request, then, based on a pre-trained threshold prediction model, a budget fusing threshold corresponding to the resource popularization affairs is predicted according to the historical budget verification data, the threshold prediction model is generated based on historical fusing data in a learning mode, the historical fusing data comprises historical unit budget verification data corresponding to each unit time period in preset time periods before and after the resource popularization affairs are fused, and finally, when the budget fusing threshold is larger than or equal to an available budget value corresponding to the resource popularization affairs, the resource popularization affairs are closed.

Description

Transaction management method, device, storage medium and equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a transaction management method, apparatus, storage medium, and device.

Background

An internet commerce platform is needed that provides the ability to personalize marketing campaigns to resident merchants/institutions. The platform assists the merchant/organization to show respective marketing campaigns to users through the product core capability, and the users participate and enjoy rights according to the campaign rules.

However, in the internet high-traffic scenario, there is a problem that the instantaneous consumption of the active budget is increased due to the large visit amount of the user. Especially when the upper limit of the activity budget is close, or the preferential activity is invalid due to insufficient budget, user complaints are easily caused, and negative effects are caused on the platform and the merchant; or the marketing campaign ends prematurely before the budget is consumed due to setting too low a budget threshold, the active budget not being exhausted, affecting the marketing effect.

Therefore, improving the budget utilization of marketing campaigns and fully securing the user experience is a currently urgent issue.

Disclosure of Invention

According to the transaction management method, the device, the storage medium and the equipment, the budget fusing threshold value can be adaptively adjusted according to the historical budget verification data, the budget utilization rate of resource popularization transactions is improved, and the transaction use experience of users is guaranteed. The technical scheme is as follows:

In a first aspect, embodiments of the present disclosure provide a transaction management method, where the method includes:

acquiring historical budget verification data aiming at resource popularization matters, wherein the historical budget verification data comprises continuous unit budget verification data corresponding to unit time periods respectively, the unit budget verification data is the sum value of first budget verification data corresponding to each transaction verification request generated in the unit time periods respectively, and the transaction verification requests are sent by a user side participating in the resource popularization matters;

based on a pre-trained threshold prediction model, predicting a budget fusing threshold corresponding to the resource popularization transaction according to the historical budget verifying data, wherein the threshold prediction model is generated based on historical fusing data in a learning mode, and the historical fusing data comprises the historical budget fusing threshold and historical unit budget verifying data corresponding to each unit duration in preset durations before and after the resource popularization transaction fusing is closed;

and closing the resource promotion transaction when the budget fusing threshold is greater than or equal to an available budget value corresponding to the resource promotion transaction.

In a second aspect, embodiments of the present disclosure provide a transaction management device, the device including:

The historical data acquisition module is used for acquiring historical budget verification data aiming at resource popularization matters, wherein the historical budget verification data comprises unit budget verification data corresponding to continuous unit time periods respectively, the unit budget verification data is the sum value of first budget verification data corresponding to each transaction verification request generated in the unit time periods respectively, and the transaction verification requests are sent by a user terminal participating in the resource popularization matters;

the fusing threshold prediction module is used for predicting a budget fusing threshold corresponding to the resource popularization transaction according to the historical budget verifying data based on a pre-trained threshold prediction model, the threshold prediction model is generated based on historical fusing data, and the historical fusing data comprises historical unit budget verifying data corresponding to each unit duration in preset durations before and after fusing of the resource popularization transaction;

and the transaction fusing judging module is used for closing the resource popularization transaction when the budget fusing threshold value is larger than or equal to the available budget value corresponding to the resource popularization transaction.

In a third aspect, the present description embodiments provide a computer program product storing at least one instruction adapted to be loaded by a processor and to perform the above-described method steps.

In a fourth aspect, the present description provides a storage medium storing a computer program adapted to be loaded by a processor and to perform the above-described method steps.

In a fifth aspect, embodiments of the present disclosure provide an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.

The technical scheme provided by some embodiments of the present specification has the following beneficial effects:

according to the transaction management method provided by the embodiment of the specification, firstly, historical budget verification data aiming at resource popularization transactions are obtained, the historical budget verification data comprises unit budget verification data corresponding to continuous unit time periods respectively, each transaction verification request generated in the unit time periods of the unit budget verification data is the sum value of first budget verification data corresponding to each transaction verification request, then, based on a pre-trained threshold prediction model, a budget fusing threshold corresponding to the resource popularization transactions is predicted according to the historical budget verification data, the threshold prediction model is generated based on historical fusing data in a learning mode, the historical fusing data comprises the historical budget fusing threshold and historical unit budget verification data corresponding to each unit time period in preset time periods before and after the resource popularization transactions are fused, finally, when the budget fusing threshold is larger than or equal to an available budget value corresponding to the resource popularization transactions, the resource popularization transactions are closed, self-adaptive adjustment of the budget fusing threshold is realized, the budget utilization rate of the resource popularization transactions is improved, and further, and the transaction using experience of users is guaranteed.

Drawings

In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of a transaction management method according to an embodiment of the present disclosure;

FIG. 2 is a schematic flow chart of a transaction management method according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart of a transaction management method according to an embodiment of the present disclosure;

FIG. 4 is an exemplary diagram of historical budget verification data provided in accordance with an embodiment of the present disclosure;

FIG. 5 is an exemplary diagram of historical budget verification data provided in accordance with an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of a transaction management device according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a transaction management device according to an embodiment of the present disclosure;

fig. 8 is a block diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

In the description of the present specification, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present specification, it should be noted that, unless expressly specified and limited otherwise, "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The specific meaning of the terms in this specification will be understood by those of ordinary skill in the art in the light of the specific circumstances. In addition, in the description of the present specification, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The following is a detailed description of embodiments in connection with the examples of the present specification. The implementations described in the following exemplary examples do not represent all implementations consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present description as detailed in the accompanying claims. The flow diagrams depicted in the figures are exemplary only and are not necessarily to be taken in the order shown. For example, some steps are juxtaposed and there is no strict order of logic, so the actual order of execution is variable.

Referring to fig. 1, a flow chart of a transaction management method according to an embodiment of the present disclosure is shown. In the embodiments in the present specification, the transaction management method is applied to a transaction management device or an electronic apparatus configured with the transaction management device. The transaction management method specifically may include the following steps, which will be described in detail with respect to the flowchart shown in fig. 1:

s102, acquiring historical budget verification data aiming at resource popularization matters, wherein the historical budget verification data comprises continuous unit budget verification data corresponding to unit time periods respectively, the unit budget verification data is the sum value of first budget verification data corresponding to each transaction verification request generated in the unit time periods respectively, and the transaction verification requests are sent by a user side participating in the resource popularization matters;

It should be noted that, the resource promotion transaction may be a marketing activity pushed by a merchant, where the resource promotion transaction includes a transaction budget, the resource promotion transaction is displayed on each user side through the internet business platform, and the user participates in the resource promotion transaction and consumes the transaction budget corresponding to the resource promotion transaction through the user side.

In the embodiment of the specification, a user participates in a resource popularization transaction through a user side and generates a transaction verification request, wherein the transaction verification request carries first budget verification data generated by the user participating in the resource popularization transaction, and the first budget verification data is transaction budget consumed by the user participating in the resource popularization transaction.

In this embodiment of the present disclosure, the transaction management device may obtain historical budget verification data corresponding to a resource popularization transaction, where the historical operation verification data includes unit budget verification data corresponding to each continuous unit duration, and the unit budget verification data is a sum value of first budget verification data corresponding to each transaction verification request generated in the unit duration.

In the embodiment of the specification, in the running process of a resource popularization transaction, a transaction management device acquires a transaction verification request sent by a user participating in the resource popularization transaction in real time, calculates first budget verification data corresponding to the transaction verification request according to the transaction verification request, and stores the first budget verification data and a time identifier corresponding to the transaction verification request in an associated mode. The transaction management device obtains stored first budget verification data in a timing mode, performs data summation on each first budget verification data in unit time according to the stored first budget verification data and the corresponding time mark to obtain unit budget verification data corresponding to a plurality of continuous unit time respectively, and takes the plurality of continuous unit budget verification data as historical budget verification data. For example, the unit duration may be 1 second, and if there are transaction verification requests sent by multiple clients in each second, all the first budget verification data generated in one second are accumulated and summed to obtain unit budget verification data corresponding to one second, and the unit budget verification data sequence of each second from the beginning of the resource promotion transaction to the current moment is used as historical budget verification data.

S104, based on a pre-trained threshold prediction model, predicting a budget fusing threshold corresponding to a resource popularization transaction according to historical budget verifying data, wherein the threshold prediction model is generated based on historical fusing data, and the historical fusing data comprises the historical budget fusing threshold and historical unit budget verifying data corresponding to each unit duration in preset durations before and after the resource popularization transaction fusing is closed;

in the embodiment of the present disclosure, after the historical budget verification data is obtained, the historical budget verification data is input into a pre-trained threshold prediction model, and the threshold prediction model may predict a budget fusing threshold corresponding to a resource popularization transaction according to the historical budget verification data. The threshold prediction model is generated based on historical fusing data, and the historical fusing data comprises historical unit budget verification data corresponding to each unit duration in preset durations before and after fusing and closing of the resource popularization transaction.

In the embodiment of the present disclosure, before transaction management is performed, first, fusing data of some historical resource popularization transactions during transaction fusing is obtained, where the fusing data includes a fusing threshold and historical unit budget verification data within a preset time period before and after fusing. For example, when the fusing threshold of the resource popularization transaction a is 2000 and the available budget value of the resource popularization transaction a is smaller than 2000, the resource popularization transaction a is fused and closed, and the historical unit budget verification data in the preset time period is historical unit budget verification data of a period of time before the resource popularization transaction a is fused and historical unit budget verification data of a period of time after the resource popularization transaction a is fused.

It should be noted that, when the available budget of the resource promotion transaction is reduced to be less than the fusing threshold, after the resource promotion transaction is fused and closed, a part of the transaction qualification of the resource promotion transaction is obtained, but a user end which has not sent a transaction verification request is still present, after the resource promotion transaction is fused and closed, transaction verification data sent by the part of the user end is received, and corresponding first budget verification data is calculated and stored. Thus, after the resource promotion transaction is fused off, there will still be historical unit budget accounting data with a reduced trend in data value presentation.

Based on the historical fusing data, the threshold prediction model can be used for learning and training, and the threshold prediction model can be used for predicting the budget fusing threshold for the resource popularization transaction according to the historical budget verifying data generated in the running process of the resource popularization transaction through learning the relation between the historical unit budget verifying data and the fusing threshold in the historical fusing data and the descending trend characteristics of the historical unit budget verifying data after the resource popularization transaction is fused off.

In one embodiment, the threshold prediction model includes a fuse trend function that is learned based on historical fuse data. The threshold prediction model firstly carries out trend analysis on the historical budget verification data, determines a budget constant value corresponding to the historical budget verification data, and then predicts a budget fusing threshold corresponding to the resource popularization transaction according to the budget constant value and the fusing trend function.

In one embodiment, trend analysis is performed on historical budget verification data to determine a budget constant value corresponding to the historical budget verification data, including: determining a data type corresponding to the historical budget verification data according to the quantity distribution condition of transaction verification requests corresponding to the historical budget verification data, taking the unit budget verification data corresponding to a target unit duration in the historical budget verification data as a budget constant value if the data type is fluctuation, taking an average value corresponding to each unit budget verification data in the historical budget verification data as a budget constant value if the data type is stable, and taking the target unit duration as the unit duration closest to the current moment.

In one embodiment, determining the data type corresponding to the historical budget verification data according to the number distribution of transaction verification requests corresponding to the historical budget verification data includes: calculating fluctuation coefficients corresponding to each unit budget verification data in the historical budget verification data, determining that the historical budget verification data is stable if the fluctuation coefficients are smaller than a fluctuation coefficient threshold, and determining that the historical budget verification data is of a fluctuation type if the fluctuation coefficients are larger than or equal to the fluctuation coefficient threshold.

In one embodiment, predicting the budget fuse threshold corresponding to the resource promotion transaction according to the budget constant value and the fuse trend function includes: and calculating predicted budget verification data corresponding to each of the continuous N seconds in the future based on the budget constant value and the fusing trend function, calculating the sum value of the predicted budget verification data corresponding to each of the continuous N seconds, and taking the sum value as a budget fusing threshold.

And S106, closing the resource promotion transaction when the budget fusing threshold is greater than or equal to the available budget value corresponding to the resource promotion transaction.

In the embodiment of the specification, the resource promotion transaction comprises transaction budget, in the running process of the resource promotion transaction, each first budget verification data is verified based on transaction budget to obtain available budget values, the available budget values are updated in real time according to each first budget verification data, and when the available budget values are smaller than or equal to a budget fusing threshold value, the resource promotion transaction is automatically fused and closed.

It can be understood that when the budget fusing threshold is greater than or equal to the available budget value corresponding to the resource promotion transaction, it indicates that the available budget value corresponding to the resource promotion transaction is already at a lower value, and at this time, in order to avoid the transaction side of the resource promotion transaction from exceeding the budget, the resource promotion transaction is closed, so as to avoid more users participating in the resource promotion transaction and causing the transaction side to exceed the budget.

In one embodiment, after the resource promotion transaction is fused and closed, at least one user side which participates in the resource promotion transaction and does not send a transaction verification request when the resource promotion transaction is closed is determined, and the resource promotion transaction in the at least one user side is kept in an open state.

It can be understood that when the budget fusing threshold is greater than or equal to the available budget value corresponding to the resource popularization transaction, after the resource popularization transaction is fused and closed, a part of users participate in the resource popularization transaction or the participation page of the resource popularization transaction is about to participate in the resource popularization transaction, and at this time, in order to ensure that the part of users can normally participate in the resource popularization transaction, the resource popularization transaction at the user side of the part of users is kept in an open state.

It should be noted that, when the available budget value of the resource promotion transaction is smaller than the budget fusing threshold, the fusing closing is performed, and at this time, the available budget value of the resource promotion transaction is not 0, and then the active budget support of the resource promotion transaction can be provided for at least one user side that is participating in the resource promotion transaction but does not send a transaction verification request when the resource promotion transaction is closed based on the remaining available budget value.

In the embodiment of the specification, firstly, historical budget verification data aiming at resource popularization matters are obtained, the historical budget verification data comprises continuous unit time length corresponding unit budget verification data respectively, each transaction verification request generated in the unit time length of the unit budget verification data is the sum value of first budget verification data respectively corresponding to each transaction verification request, then, based on a pre-trained threshold prediction model, a budget fusing threshold corresponding to the resource popularization matters is predicted according to the historical budget verification data, the threshold prediction model is generated based on historical fusing data, the historical fusing data comprises the historical budget fusing threshold and the historical unit budget verification data respectively corresponding to each unit time length in preset time length before and after the resource popularization matters are fused, finally, when the budget fusing threshold is larger than or equal to an available budget value corresponding to the resource popularization matters, the resource popularization matters are closed, the self-adaptive adjustment of the budget fusing threshold is realized, the budget utilization rate of the resource popularization matters is improved, and further, the business use experience of users is ensured.

Referring to fig. 2, for a schematic flow chart of a transaction management method provided in an embodiment of the present disclosure, the transaction management method may include the following steps:

S202, acquiring a transaction verification request for a resource popularization transaction;

In the embodiment of the specification, a user participates in a resource popularization transaction through a user side and generates a transaction verification request, wherein the transaction verification request carries first budget verification data generated by the user participating in the resource popularization transaction, the first budget verification data is a transaction budget consumed by the user participating in the resource popularization transaction, and the user side sends the transaction verification request to a transaction management device.

It should be noted that, in the embodiment of the present disclosure, the transaction management device may be a functional module running on the internet commerce platform, and during the pushing of the resource promotion transaction, the transaction management device may obtain, in real time, a transaction verification request sent by the user side.

S204, calculating first budget verification data corresponding to the transaction verification request based on the transaction verification request;

In the embodiment of the present disclosure, after obtaining a transaction verification request sent by a user side, first budget verification data corresponding to the transaction verification request is calculated.

For example, the resource promotion transaction may be a commodity price reduction promotion, the user purchases a commodity in the price reduction promotion, and then generates a transaction verification request, the transaction verification request includes real payment of the commodity purchased by the user and commodity price information, the difference between the real payment of the commodity and the commodity price is a preferential price, and the preferential price is first budget verification data corresponding to the transaction verification request.

S206, carrying out association storage on the first budget verification data and the time mark corresponding to the transaction verification request;

in the embodiment of the specification, the event identification corresponding to the first budget verification data and the transaction verification request is stored in a storage medium, so that the prediction of the fusing threshold value is performed according to the historical budget verification data.

S208, acquiring historical budget verification data for resource popularization matters;

in the embodiment of the present disclosure, step S208 is referred to in another embodiment of the present disclosure for detailed description of step S102, and will not be described herein.

S210, determining a budget constant value corresponding to the historical budget verification data by carrying out trend analysis on the historical budget verification data;

In the embodiment of the present disclosure, the prediction of the budget fusing threshold is performed according to the historical budget verification data based on the pre-trained threshold prediction model, and the threshold prediction model is generated based on the historical fusing data, where the historical fusing data includes the historical budget fusing threshold and historical unit budget verification data corresponding to each unit duration in preset durations before and after the fusing of the resource popularization transaction. The threshold prediction model obtains a fusing trend function for representing the change condition of budget verification data after fusing through learning the historical fusing data. The budget constant value is a constant value used for predicting a budget fuse threshold in the fuse trend function.

In the embodiment of the present disclosure, the determination of the budget constant value is related to the change situation of the budget verification data in the last period, and according to the historical budget verification data, the trend analysis is performed on the historical budget verification data, so as to determine the budget constant value corresponding to the historical budget verification data.

In one embodiment, a data type corresponding to historical budget verification data is determined according to a quantity distribution condition of transaction verification requests corresponding to the historical budget verification data, if the data type is fluctuation type, unit budget verification data corresponding to a target unit duration in the historical budget verification data is used as a budget constant value, the target unit duration is the unit duration closest to the current moment, and if the data type is stable type, an average value corresponding to each unit budget verification data in the historical budget verification data is used as the budget constant value.

It can be understood that, according to different active times of the user, the number of transaction verification requests is different at different time points, and in the inactive time of the user, the transaction verification requests generated in each second may present a relatively stable number change condition, and no large data fluctuation occurs; during the time that the user is active, a surge or decrease in the number of transaction verification requests may occur over a period of time. In this embodiment of the present disclosure, according to the historical budget verification data, the corresponding fluctuation coefficient may be calculated according to the number of transaction verification requests in each second in a period of time, if the fluctuation coefficient is greater than or equal to a preset fluctuation coefficient threshold, the historical budget verification data is determined to be of a fluctuation type, and if the fluctuation coefficient is less than the preset fluctuation coefficient threshold, the historical budget verification data is determined to be stationary.

Optionally, the historical budget verification data includes corresponding unit budget verification data of each unit time length in history, the data type corresponding to the historical budget verification data is determined according to the change condition of the unit budget verification data in the last period, if the unit budget verification data in the last period is stable and the data fluctuation is small, the historical budget verification data is determined to be stable, and the average value of the unit budget verification data in the last period is taken as a budget constant value; if the data fluctuation of the unit budget verification data in the last period of time is severe, the historical budget verification data is determined to be fluctuation, and the unit budget verification data in the last period of time is taken as a budget constant value.

S212, predicting a budget fusing threshold corresponding to a resource popularization transaction based on a budget constant value and a fusing trend function, wherein the fusing trend function is a trend function learned based on historical fusing data;

in the embodiment of the present specification, predicted budget verification data corresponding to each of N seconds in the future is calculated based on the budget constant value and the fusing trend function, and a sum of the predicted budget verification data corresponding to each of N seconds in the future is calculated, and the sum is used as the budget fusing threshold.

S214, closing the resource promotion transaction when the budget fusing threshold is greater than or equal to an available budget value corresponding to the resource promotion transaction;

in the embodiment of the present disclosure, step S214 is referred to as a detailed description of step S106 in another embodiment of the present disclosure, and will not be described herein.

S216, determining at least one user side which participates in the resource promotion transaction but does not send a transaction verification request when the resource promotion transaction is closed;

s218, keeping the resource promotion transaction in at least one user terminal in an open state.

In the embodiment of the specification, a transaction verification request for a resource popularization transaction is acquired, first budget verification data corresponding to the transaction verification request is calculated based on the transaction verification request, the first budget verification data and a time identifier corresponding to the transaction verification request are stored in a correlated mode, historical budget verification data for the resource popularization transaction is acquired, a trend analysis is carried out on the historical budget verification data, a budget constant value corresponding to the historical budget verification data is determined, a budget fusing threshold corresponding to the resource popularization transaction is predicted based on the budget constant value and a fusing trend function, the fusing trend function is a trend function learned based on the historical fusing data, when the budget fusing threshold is larger than or equal to an available budget value corresponding to the resource popularization transaction, the resource popularization transaction is closed, self-adaptive adjustment of the budget fusing threshold is achieved, the budget utilization rate of the resource popularization transaction is improved, further, the transaction using experience of a user is guaranteed, and at least one user end which is participating in the resource popularization transaction but does not send the transaction verification request is determined when the resource popularization transaction is closed, the resource popularization transaction is kept in an open state, the resource popularization transaction is guaranteed to be in a popularization transaction, and after the resource popularization transaction is closed, the user experience is not influenced by the user is improved.

Referring to fig. 3, for a schematic flow chart of a transaction management method provided in an embodiment of the present disclosure, the transaction management method may include the following steps:

s302, acquiring historical budget verification data aiming at resource popularization matters, wherein the historical budget verification data comprises continuous unit budget verification data corresponding to unit time periods respectively, the unit budget verification data is the sum value of first budget verification data corresponding to each transaction verification request generated in the unit time periods respectively, and the transaction verification requests are sent by a user side participating in the resource popularization matters;

in the embodiment of the present disclosure, the step S302 is referred to in another embodiment of the present disclosure for detailed description of the step S102, which is not repeated here.

S304, determining the data type corresponding to the historical budget verification data according to the quantity distribution condition of the transaction verification requests corresponding to the historical budget verification data;

in this embodiment of the present disclosure, the transaction management device acquires, in real time, a transaction verification request sent by each user side, and stores first budget verification data corresponding to the transaction verification request and a corresponding event identifier. The historical budget verification data is transaction verification request data acquired in the last period of time, and the data type corresponding to the historical budget verification data is determined according to the quantity fluctuation condition of the transaction verification requests in the period of time.

It can be understood that, according to different active times of the user, the number of transaction verification requests is different at different time points, and in the inactive time of the user, the transaction verification requests generated in each second may present a relatively stable number change condition, and no large data fluctuation occurs; during the time that the user is active, a surge or decrease in the number of transaction verification requests may occur over a period of time.

In this embodiment of the present disclosure, according to the historical budget verification data, the corresponding fluctuation coefficient may be calculated according to the number of transaction verification requests in each second in a period of time, if the fluctuation coefficient is greater than or equal to a preset fluctuation coefficient threshold, the historical budget verification data is determined to be of a fluctuation type, and if the fluctuation coefficient is less than the preset fluctuation coefficient threshold, the historical budget verification data is determined to be stationary.

The fluctuation coefficient is an index for reflecting the time-unbalanced condition of the data. The calculation method is as follows: the ratio of the maximum unit budget verification data to the corresponding average value of each unit budget verification data in the historical budget verification data.

S306, if the data type is fluctuation type, taking unit budget verification data corresponding to a target unit time length in the historical budget verification data as a budget constant value, wherein the target unit time length is the unit time length closest to the current time;

in the embodiment of the present disclosure, if it is determined that the data type of the historical budget verification data is a fluctuation type, which indicates that the data fluctuation of the historical budget verification data is large, the unit budget verification data corresponding to the last unit duration in the historical budget verification data is used as the budget constant value. For example, when the current time is 14 minutes and 45 seconds, the unit budget verification data corresponding to 14 minutes and 44 seconds in the historical budget verification data is taken as the budget constant value.

Referring to fig. 4, an exemplary schematic diagram of historical budget verification data is provided in an embodiment of the present application. As shown in fig. 4, the historical budget verification data includes unit budget verification data corresponding to 10 consecutive seconds, and if it is determined that the data type of the historical budget verification data is a fluctuation type according to each unit budget verification data, the unit budget verification data corresponding to the last second is taken as a budget constant value. The budget constant value corresponding to the historical budget verification data shown in fig. 4 is the unit budget verification data corresponding to the 10 th second, and the budget constant value is 1688.

S308, if the data type is stable, taking an average value corresponding to each unit budget verification data in the historical budget verification data as a budget constant value;

in the embodiment of the present disclosure, if it is determined that the data type of the historical budget verification data is stationary, it indicates that the data fluctuation of the historical budget verification data is small, and an average value corresponding to each unit budget verification data in the historical budget verification data is taken as a budget constant value. For example, when the current time is 14 minutes 45 seconds, the historical budget verification data includes unit budget verification data of 14 minutes 44 seconds to 14 minutes 44 seconds, and the average value of the unit budget verification data in the historical budget verification data is taken as a budget constant value.

Referring to fig. 5, an exemplary schematic diagram of historical budget verification data is provided in an embodiment of the present application. As shown in fig. 5, the historical budget verification data includes unit budget verification data corresponding to 10 seconds in succession, and when it is determined that the data type of the historical budget verification data is stationary based on each unit budget verification data, the average value of each unit budget verification data is used as the budget constant value. As shown in fig. 4, in the historical budget verification data, the unit budget verification data corresponding to 1 st second is 525, the unit budget verification data corresponding to 2 nd second is 521, the unit budget verification data corresponding to 3 rd second is 503, the unit budget verification data corresponding to 4 th second is 515, the unit budget verification data corresponding to 5 th second is 533, the unit budget verification data corresponding to 6 th second is 527, the unit budget verification data corresponding to 7 th second is 501, the unit budget verification data corresponding to 8 th second is 531, the unit budget verification data corresponding to 9 th second is 529, and the unit budget verification data corresponding to 10 th second is 522, and the budget constant value is the average value of the unit budget verification data corresponding to 10 th second, and the budget constant value= (525+521+503+515+533+527+501+531+529+522)/10=520.7.

The corresponding budget constant value is the unit budget verification data corresponding to the 10 th second, and the budget constant value is 1688.

S310, calculating predicted budget verification data corresponding to each of the continuous N seconds in the future based on the budget constant value and the fusing trend function;

in the embodiment of the specification, the threshold prediction model includes a fusing trend function, wherein the fusing trend function is a trend function learned based on historical fusing data and can be used for representing the change trend of budget verification data with time after fusing off of resource popularization transactions.

In one embodiment, the fusing trend function may be:

f(x)＝a-ke ^x ；

wherein f (x) is predicted budget verification data, x is time, a is a budget constant value, k is a trend control variable, and the trend control variable is learned based on historical fusing data.

In one embodiment, the fusing trend function may be:

f(x)＝a-kx；

S312, calculating sum values of the predicted budget verification data corresponding to the continuous N seconds respectively, and taking the sum values as budget fusing threshold values;

in the embodiment of the present specification, after determining the budget constant value according to the historical budget verification data, the sum of the predicted budget verification data corresponding to each of N seconds in the future is calculated based on the fusing trend function, and the sum is taken as the budget fusing threshold.

For example, the fuse trend function is f (x) =a-kx, when x is 1, the predicted budget verification data of one second in the future is calculated, and when x is 2, the predicted budget verification data of two seconds in the future is calculated.

Alternatively, the sum of the predicted budget verification data for five consecutive seconds in the future is taken as the budget constant value.

In the embodiment of the present disclosure, the value of N may be set reasonably according to different types of resource promotion transactions and the trend of the change of the fusing trend function, which is not particularly limited in the embodiment of the present disclosure.

S314, closing the resource promotion transaction when the budget fusing threshold is greater than or equal to the available budget value corresponding to the resource promotion transaction;

in the embodiment of the present disclosure, step S314 is referred to the detailed description of step S106 in another embodiment of the present disclosure, and will not be repeated here.

S316, determining at least one user side which participates in the resource promotion transaction but does not send a transaction verification request when the resource promotion transaction is closed;

and S318, maintaining the resource promotion transaction in at least one user terminal to be in an open state.

In the embodiment of the specification, firstly, historical budget verification data for resource popularization matters are obtained, then, the data type corresponding to the historical budget verification data is determined according to the quantity distribution condition of transaction verification requests corresponding to the historical budget verification data, if the data type is fluctuation, the unit budget verification data corresponding to the target unit duration in the historical budget verification data is used as a budget constant value, the target unit duration is the unit duration closest to the current moment, if the data type is stable, the average value corresponding to each unit budget verification data in the historical budget verification data is used as a budget constant value, finally, the sum value of the predicted budget verification data corresponding to each future continuous N seconds is calculated based on the budget constant value and a fusing trend function, the sum value is used as a budget fusing threshold, when the budget fusing threshold is larger than or equal to an available budget value corresponding to the resource popularization matters, the resource popularization matters are closed, the self-adaptive adjustment of the budget fusing threshold is realized, the budget utilization rate of the resource popularization matters is improved, the user experience is further ensured, and at least one user terminal is not influenced when the resource popularization matters are closed, but the user terminal is not influenced by the resource popularization is not in the transaction, and the transaction popularization request is not closed, and the user terminal is not influenced by the resource popularization is guaranteed.

Referring to fig. 6, a schematic structural diagram of a transaction management device according to an embodiment of the present disclosure is provided. As shown in fig. 6, the transaction management device 1 may be implemented as all or a part of an electronic apparatus by software, hardware, or a combination of both. According to some embodiments, the transaction management device 1 includes a historical data acquisition module 11, a fusing threshold prediction module 12, and a transaction fusing determination module 13, and specifically includes:

a historical data obtaining module 11, configured to obtain historical budget verification data for a resource popularization transaction, where the historical budget verification data includes unit budget verification data corresponding to continuous unit time periods respectively, the unit budget verification data is a sum value of first budget verification data corresponding to each transaction verification request generated in the unit time periods respectively, and the transaction verification request is sent by a user terminal participating in the resource popularization transaction;

the fusing threshold prediction module 12 is configured to predict, based on a pre-trained threshold prediction model, a budget fusing threshold corresponding to the resource promotion transaction according to the historical budget verifying data, where the threshold prediction model is generated based on historical fusing data, and the historical fusing data includes historical unit budget verifying data corresponding to each unit duration in preset durations before and after fusing of the resource promotion transaction;

And the transaction fusing judging module 13 is configured to close the resource promotion transaction when the budget fusing threshold is greater than or equal to an available budget value corresponding to the resource promotion transaction.

Optionally, please refer to fig. 7, which is a schematic structural diagram of a transaction management device according to an embodiment of the present disclosure. As shown in fig. 7, the transaction management device further includes a verification request receiving module 14, configured to:

acquiring a transaction verification request aiming at the resource popularization transaction;

calculating first budget verification data corresponding to the transaction verification request based on the transaction verification request;

and carrying out association storage on the first budget verification data and the time identifier corresponding to the transaction verification request.

Optionally, the threshold prediction model includes a fusing trend function, and the fusing threshold prediction module 12 is specifically configured to:

determining a budget constant value corresponding to the historical budget verification data by carrying out trend analysis on the historical budget verification data;

and predicting a budget fusing threshold corresponding to the resource popularization transaction based on the budget constant value and a fusing trend function, wherein the fusing trend function is a trend function learned based on the historical fusing data.

Optionally, when the fusing threshold prediction module 12 performs the trend analysis on the historical budget verification data to determine a budget constant value corresponding to the historical budget verification data, the fusing threshold prediction module is specifically configured to:

determining a data type corresponding to the historical budget verification data according to the quantity distribution condition of transaction verification requests corresponding to the historical budget verification data;

if the data type is fluctuation type, taking unit budget verification data corresponding to a target unit duration in the historical budget verification data as the budget constant value, wherein the target unit duration is the unit duration closest to the current time;

and if the data type is stable, taking an average value corresponding to each unit budget verification data in the historical budget verification data as the budget constant value.

Optionally, when the fusing threshold prediction module 12 determines the data type corresponding to the historical budget verification data according to the number distribution situation of the transaction verification requests corresponding to the historical budget verification data, the fusing threshold prediction module is specifically configured to:

calculating a fluctuation coefficient corresponding to each unit budget verification data in the historical budget verification data;

If the fluctuation coefficient is smaller than a fluctuation coefficient threshold value, determining that the historical budget verification data is stable;

and if the fluctuation coefficient is greater than or equal to the fluctuation coefficient threshold value, determining that the historical budget verification data is of a fluctuation type.

Optionally, when executing the predicting, by the fusing threshold prediction module 12, the budget fusing threshold corresponding to the resource promotion transaction based on the budget constant value and the fusing trend function, the fusing threshold prediction module is specifically configured to:

calculating predicted budget verification data corresponding to each of the continuous N seconds in the future based on the budget constant value and the fusing trend function;

and calculating the sum value of the predicted budget verification data corresponding to the continuous N seconds respectively, and taking the sum value as the budget fusing threshold.

Optionally, the fusing threshold prediction module 12 is specifically configured to, when executing the calculation of predicted budget verification data corresponding to each of N seconds in the future based on the budget constant value and the fusing trend function:

f(x)＝a-kx；

the f (x) is predicted budget verification data, the x is time, the a is a budget constant value, the k is a trend control variable, and the trend control variable is learned based on historical fusing data.

f(x)＝a-ke ^x ；

Optionally, referring to fig. 7, the transaction management device further includes a transaction start-up holding module 15, configured to:

determining at least one user side which participates in the resource promotion transaction but does not send a transaction verification request when the resource promotion transaction is closed;

and keeping the resource promotion transaction in the at least one user terminal in an open state.

It should be noted that, in the transaction management apparatus provided in the foregoing embodiment, when executing the transaction management method, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the transaction management device and the transaction management method embodiment provided in the foregoing embodiments belong to the same concept, which embody the detailed implementation process in the method embodiment, and are not described herein again.

The foregoing embodiment numbers of the present specification are merely for description, and do not represent advantages or disadvantages of the embodiments.

The embodiment of the present disclosure further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded by a processor and executed by the processor to perform the transaction management method according to the embodiment shown in fig. 1 to 5, and the specific execution process may refer to the specific description of the embodiment shown in fig. 1 to 5, which is not repeated herein.

The present disclosure further provides a computer program product, where at least one instruction is stored, where the at least one instruction is loaded by the processor and executed by the processor to perform the transaction management method according to the embodiment shown in fig. 1 to 5, and the specific execution process may refer to the specific description of the embodiment shown in fig. 1 to 5, which is not repeated herein.

Referring to fig. 8, a block diagram of an electronic device according to an embodiment of the present disclosure is provided. The electronic device in this specification may include one or more of the following: processor 110, memory 120, input device 130, output device 140, and bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected by a bus 150.

Processor 110 may include one or more processing cores. The processor 110 connects various parts within the overall terminal using various interfaces and lines, performs various functions of the terminal 100 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and invoking data stored in the memory 120. Alternatively, the processor 110 may be implemented in at least one hardware form of digital signal processing (digital signal processing, DSP), field-programmable gate array (field-programmable gate array, FPGA), programmable logic array (programmable logic Array, PLA). The processor 110 may integrate one or a combination of several of a central processor (central processing unit, CPU), an image processor (graphics processing unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 110 and may be implemented solely by a single communication chip.

The memory 120 may include a random access memory (random Access Memory, RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 120 may be used to store instructions, programs, code, sets of codes, or sets of instructions.

The input device 130 is configured to receive input instructions or data, and the input device 130 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 140 is used to output instructions or data, and the output device 140 includes, but is not limited to, a display device, a speaker, and the like. In the embodiment of the present disclosure, the input device 130 may be a temperature sensor for acquiring an operation temperature of the terminal. The output device 140 may be a speaker for outputting audio signals.

In addition, those skilled in the art will appreciate that the configuration of the terminal illustrated in the above-described figures does not constitute a limitation of the terminal, and the terminal may include more or less components than illustrated, or may combine certain components, or may have a different arrangement of components. For example, the terminal further includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (wireless fidelity, WIFI) module, a power supply, a bluetooth module, and the like, which are not described herein again.

In the embodiment of the present specification, the execution subject of each step may be the terminal described above. Optionally, the execution subject of each step is an operating system of the terminal. The operating system may be an android system, an IOS system, or other operating systems, which embodiments of the present specification are not limited to.

In the electronic device of fig. 8, the processor 110 may be configured to invoke a transaction management program stored in the memory 120 and execute to implement the transaction management methods as described in various method embodiments of the present description.

It will be clear to a person skilled in the art that the solution according to the present description can be implemented by means of software and/or hardware. "Unit" and "module" in this specification refer to software and/or hardware capable of performing a specific function, either alone or in combination with other components, such as Field programmable gate arrays (Field-Programmable Gate Array, FPGAs), integrated circuits (Integrated Circuit, ICs), etc.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present description is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present description. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the specification.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in this specification, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, such as the division of the units, merely a logical function division, and there may be additional manners of dividing the actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some service interface, device or unit indirect coupling or communication connection, electrical or otherwise.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

Those of ordinary skill in the art will appreciate that all or a portion of the steps in the various methods of the above embodiments may be performed by hardware associated with a program that is stored in a computer readable memory, which may include: flash disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic or optical disk, and the like.

The foregoing is merely exemplary embodiments of the present specification and is not intended to limit the scope of the present specification. It is intended that all equivalent variations and modifications as taught herein fall within the scope of the present disclosure. Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.

Claims

1. A transaction management method, the method comprising:

2. The method of claim 1, prior to the obtaining historical budget verification data for the resource promotion transaction, further comprising:

3. The method of claim 1, the threshold prediction model comprising a fusing trend function, the predicting a budget fusing threshold corresponding to the resource promotion transaction from the historical budget verification data comprising:

4. A method according to claim 3, wherein determining the budget constant value corresponding to the historical budget verification data by trend analysis of the historical budget verification data comprises:

5. The method according to claim 4, wherein the determining the data type corresponding to the historical budget verification data according to the number distribution situation of the transaction verification requests corresponding to the historical budget verification data comprises:

6. A method according to claim 3, said predicting a budget fuse threshold corresponding to said resource promotion transaction based on said budget constant value and a fuse trend function, comprising:

7. The method of claim 6, the calculating predicted budget verification data for each of N seconds in the future based on the budget constant value and a fuse trend function, comprising:

f(x)＝-kx；

8. The method of claim 6, the calculating predicted budget verification data for each of N seconds in the future based on the budget constant value and a fuse trend function, comprising:

f(x)＝-ke ^x ；

9. The method of claim 1, when the budget fusing threshold is greater than or equal to an available budget value corresponding to the resource promotion transaction, further comprising, after closing the resource promotion transaction:

10. A transaction management device, comprising:

11. A storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method according to any of claims 1 to 9.

12. An electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the steps of the method according to any one of claims 1-9.

13. A computer program product having stored thereon at least one instruction, which when executed by a processor, implements the steps of the method of any of claims 1 to 9.