CN109949026B

CN109949026B - Red packet information generation method and device, terminal and server

Info

Publication number: CN109949026B
Application number: CN201711386212.8A
Authority: CN
Inventors: 刘超
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-12-20
Filing date: 2017-12-20
Publication date: 2023-04-14
Anticipated expiration: 2037-12-20
Also published as: CN109949026A

Abstract

The embodiment of the application provides a method, a device, a terminal and a server for generating red packet information, wherein a red packet generation request indicating that an account number for sending a red packet is sent is received from a client, and a red packet configuration interface is returned to the client; receiving at least one configuration parameter (the configuration parameter comprises an affinity index range and a total amount of the red packet) returned by the client through a red packet configuration interface; determining each red packet receiving account which has an affinity index within the affinity index range with the red packet sending account from each friend account associated with the red packet sending account; and determining the red packet information corresponding to each red packet receiving account (the sum of the red packet amounts indicated by the generated red packet information is not greater than the total red packet amount), so that the purpose of generating the red packet information corresponding to the red packet generation request is achieved, the problem of single red packet information generation mode in the prior art is solved, and the application of the user based on the red packet is facilitated to effectively improve the viscosity between the user and other users.

Description

Red packet information generation method and device, terminal and server

Technical Field

The invention relates to the technical field of computers, in particular to a red packet information generation method, a red packet information generation device, a terminal and a server.

Background

The application of the red envelope in the social network not only facilitates the work and life of users, but also enhances the viscosity and interaction among the users to the great extent, so that the communication among the users is more and more tight.

In the prior art, a red packet sender triggers a red packet sending operation in a chat interface, and sets a red packet sending amount to generate and immediately send a red packet to a user in the chat interface, so that the problem of single red packet information generation mode generally exists, and the stickiness between the user and other users can not be effectively improved based on the application of the red packet.

In view of the above, a method, an apparatus, a terminal and a server for generating red packet information are provided to solve the problem that a single red packet information generation manner is required in the prior art.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, a terminal, and a server for generating red envelope information, so as to avoid a problem in the prior art that a red envelope information generation manner is single, and facilitate a user to effectively improve stickiness with other users based on red envelope application.

In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:

a red packet information generation method comprises the following steps:

receiving a red packet generation request which indicates that an account number sent by a red packet exists and is sent by a client, and returning a red packet configuration interface to the client;

receiving at least one configuration parameter returned by the client through the red packet configuration interface, wherein the configuration parameter comprises an affinity index range and a total amount of the red packet;

determining each red packet receiving account number of which the intimacy index between the each friend account number and the red packet sending account number is within the intimacy index range from each friend account number associated with the red packet sending account number;

and determining the red packet information corresponding to each red packet receiving account, wherein the red packet information indicates the amount of the red packet, and the sum of the generated red packet amounts indicated by the red packet information is not more than the total amount of the red packet.

A red packet information generation method comprises the following steps:

sending a red packet generation request indicating that a red packet sending account exists to a server;

receiving a red packet configuration interface returned by the server;

and returning at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each piece of red packet information corresponding to the account sent out by the red packet based on the intimacy index range and the total amount of the red packet in the at least one configuration parameter, each piece of red packet information indicates a red packet receiving account and a red packet amount, and the sum of the red packet amounts indicated by the generated red packet information is not more than the total amount of the red packet.

A red envelope information generating apparatus comprising:

the system comprises a red packet generation request receiving unit, a red packet configuration interface sending unit and a red packet generation request receiving unit, wherein the red packet generation request receiving unit is used for receiving a red packet generation request which indicates that a red packet sending account exists and is sent by a client side and returning a red packet configuration interface to the client side;

a configuration parameter receiving unit, configured to receive at least one configuration parameter returned by the client through the red envelope configuration interface, where the configuration parameter includes an affinity index range and a total amount of red envelopes;

the device comprises a red packet receiving account number determining unit, a red packet receiving account number determining unit and a red packet receiving account number determining unit, wherein the red packet receiving account number determining unit is used for determining each red packet receiving account number of which the intimacy index between the red packet receiving account number and each friend account number associated with the red packet sending account number is within the intimacy index range;

the red packet information determining unit is used for determining red packet information corresponding to each red packet receiving account, the red packet information indicates the amount of red packets, and the sum of the generated red packet amounts indicated by the red packet information is not greater than the total amount of red packets.

A server, comprising: at least one memory and at least one processor; the memory stores a program, the processor invokes the memory stored program, the program to:

determining each red packet receiving account which has an affinity index within the affinity index range with the red packet sending account from each friend account associated with the red packet sending account;

determining red packet information corresponding to each red packet receiving account respectively, wherein the red packet information indicates the amount of red packets, and the sum of the generated red packet amounts indicated by the red packet information is not more than the total amount of the red packets.

A red envelope information generating apparatus comprising:

the device comprises a red packet generation request sending unit, a red packet generation unit and a red packet generation unit, wherein the red packet generation request sending unit is used for sending a red packet generation request indicating that a red packet sending account exists to a server;

the red packet configuration interface receiving unit is used for receiving the red packet configuration interface returned by the server;

and a configuration parameter returning unit, configured to return at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each piece of red packet information corresponding to the red packet sending account based on the intimacy index range and the total amount of red packets in the at least one configuration parameter, each piece of red packet information indicates a red packet receiving account and a red packet amount, and the total amount of red packets indicated by each piece of red packet information generated is not greater than the total amount of red packets.

A terminal, comprising: at least one memory and at least one processor; the memory stores a program, the processor invokes the program stored by the memory, the program to:

sending a red packet generation request indicating that an account number sent by a red packet exists to a server;

receiving a red packet configuration interface returned by the server;

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 embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a flowchart of a method for generating red envelope information according to an embodiment of the present disclosure;

fig. 2 is an interface schematic diagram of a red envelope configuration interface according to an embodiment of the present disclosure;

fig. 3 is a flowchart of a method for determining red envelope information respectively corresponding to each red envelope receiving account according to the embodiment of the present application;

fig. 4 is a flowchart of another method for determining red envelope information respectively corresponding to each red envelope receiving account according to the embodiment of the present application;

fig. 5 is a flowchart of a method for determining historical behavior data between a red packet receiving account and a red packet sending account, and determining red packet sending time within a red packet sending time period corresponding to the red packet receiving account based on the historical behavior data according to the embodiment of the present application;

fig. 6 is a flowchart of another red envelope information generation method according to the embodiment of the present application;

fig. 7 is a flowchart of another method for generating red envelope information according to the embodiment of the present application;

fig. 8 is a schematic structural diagram of a red packet information generating device according to an embodiment of the present application;

fig. 9 is a block diagram of a hardware structure of a server according to an embodiment of the present disclosure;

fig. 10 is a schematic structural diagram of a red packet information generating apparatus according to an embodiment of the present application;

fig. 11 is a block diagram of a hardware structure of a terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a flowchart of a red envelope information generating method provided in an embodiment of the present application, where the method may be applied to a server (such as a red envelope information generating server or other specially configured service devices), and the server receives a red envelope generating request sent by a client to generate red envelope information corresponding to the red envelope generating request; referring to fig. 1, the method includes:

s101, receiving a red packet generation request which indicates that a red packet sending account is sent and is sent by a client, and returning a red packet configuration interface to the client;

optionally, the server receives a red packet generation request sent by the terminal through the client, where the red packet generation request indicates that there is a red packet sending account, and the red packet sending account may be an account currently logged in the client sending the red packet generation request. For example, a user logs in an account 1 on a client, and sends a red packet generation request to a server through the client, where the red packet generation request indicates that the account 1 is present.

The above is only a preferred mode of issuing an account number by a red envelope provided in the embodiment of the present application, and is not limited herein.

Optionally, after receiving the red envelope generation request, the server responds to the red envelope generation request and returns a red envelope configuration interface to the client. In this embodiment of the present application, preferably, the red envelope configuration interface returned to the client is an operable interface, that is, a user may operate the red envelope configuration interface displayed on the client.

S102, receiving at least one configuration parameter returned by the client through a red packet configuration interface, wherein the configuration parameter comprises an affinity index range and a total amount of the red packet;

optionally, at least one parameter configuration item is set in the red-envelope configuration interface, where the at least one parameter configuration item includes an affinity index range configuration item and a red-envelope total amount configuration item (such as affinity index range configuration item 1 and red-envelope total amount configuration item 2 in an interface schematic diagram of the red-envelope configuration interface shown in fig. 2), and the user fills in the affinity index range at a corresponding position 3 of the affinity index range configuration item in the red-envelope configuration interface and fills in the red-envelope total amount at a corresponding position 4 of the red-envelope total amount configuration item in the red-envelope configuration interface to return at least one configuration parameter to the server (for example, click a "submit" button 5 in the red-envelope configuration interface to return at least one configuration parameter to the server), where the at least one configuration parameter includes an affinity index range and a red-envelope total amount.

The above is only a preferred mode of the red packet configuration interface provided in the embodiment of the present application, and specifically, the inventor may arbitrarily set the content in the red packet configuration interface according to the own requirement, which is not limited herein.

Further, the red packet configuration interface provided in the embodiment of the present application may further include prompt information 6 as shown in fig. 2, and optionally, the red packet configuration interface shown in fig. 2 refers to the red packet information generated by using the red packet information generation method provided in the embodiment of the present application as an intelligent AI red packet, specifically, the content of the prompt information 6 in fig. 2 is "description: when you set the intelligent AI red envelope, the system sends a warm blessing to your friends in the specified date according to your setting.

The above is only a preferred mode of the prompt message provided in the embodiment of the present application, and the inventor can arbitrarily set the specific content of the prompt message according to his own needs, which is not limited herein.

S103, determining each red packet receiving account number of which the intimacy index between each red packet sending account number and each friend account number associated with the red packet sending account number is within the intimacy index range;

optionally, all accounts in the friend address list of the account sent out in the red envelope are determined as the friend accounts associated with the account sent out in the red envelope; or all accounts in the group specified by the red envelope sending account are determined as the friend accounts associated with the red envelope sending account. The group designated by the red envelope sending account number may be any one or more groups in each group to which the red envelope sending account number belongs.

The above is only the preferred way for determining each friend account associated with the red envelope sending account provided in the embodiment of the present application, and specifically, the inventor can arbitrarily set the way for determining each friend account associated with the red envelope sending account according to the needs of the inventor, which is not limited here.

Optionally, after determining each friend account associated with the red packet sending account, it is necessary to select, from the determined friend accounts associated with the red packet sending account, each friend account whose affinity index with the red packet sending account is within an affinity index range (the affinity index range is an affinity index range included in the received returned at least one configuration parameter), and determine each selected friend account as a red packet receiving account.

In the embodiment of the present application, preferably, the intimacy degree index between two accounts indicates intimacy degree between two users owning the two accounts.

In the embodiment of the present application, preferably, the intimacy degree index between two account numbers can be obtained by analyzing historical behavior data between the two account numbers. The historical behavior data between the two accounts comprises: historical interaction behavior data between two accounts [ e.g., space (WeChat friend circle, QQ space, etc.) interaction data between two accounts, chat data between two accounts, etc. ], attributes of any one account to the other account (e.g., nickname of one account to the other, etc.), and the like.

Optionally, a higher affinity index between two accounts indicates a higher affinity between two users owning the two accounts; alternatively, a higher affinity index between two accounts indicates a lower degree of affinity between two users owning the two accounts.

The above is only a preferred way of the relationship between the intimacy degree index and the intimacy degree provided by the embodiment of the present application, and the inventor can arbitrarily set the relationship between the intimacy degree index and the intimacy degree according to his own needs, which is not limited herein.

Further, in order to ensure that the intimacy degree between two account numbers can best represent the current intimacy degree between the two account numbers, the intimacy degree between the two account numbers can be calculated once every preset time interval so as to update the intimacy degree between the two account numbers.

Optionally, when the configuration parameter returned to the server is the affinity index range, the affinity index range may be an affinity index (as shown in fig. 2, the affinity index range returned to the server is the affinity index 8), or may be an affinity index interval (for example, the affinity index range returned to the service may be from the affinity index 5 to the affinity index 9).

In this embodiment of the present application, preferably, the determining the red envelope receiving account from each friend account associated with the red envelope sending account may further include: randomly selecting a preset number of friend account numbers from the friend account numbers associated with the red packet sending account number as red packet receiving account numbers; or selecting a preset number of recently-contacted friend accounts from the friend accounts associated with the account sent out in the red envelope as red envelope receiving accounts; or receiving selection operation of each friend account related to the account sent out in the red envelope, and determining each selected friend account as a red envelope receiving account.

The above is only the preferred way for determining the red envelope receiving account number from each friend account number associated with the red envelope sending account number provided in the embodiment of the present application, and specifically, the inventor may arbitrarily set the way for determining the red envelope receiving account number from each friend account number associated with the red envelope sending account number according to the own requirement, which is not limited herein.

S104, determining the red packet information corresponding to each red packet receiving account, wherein the red packet information indicates the amount of the red packet, and the sum of the amounts of the red packets indicated by the generated red packet information is not more than the total amount of the red packet.

Fig. 3 is a flowchart of a method for determining red envelope information respectively corresponding to each red envelope receiving account according to an embodiment of the present disclosure.

As shown in fig. 3, the method includes:

s301, distributing the money of the red envelope to each red envelope receiving account number respectively based on the intimacy indexes between the red envelope sending account number and each red envelope receiving account number;

optionally, allocating the money amount of the bonus package to each bonus package receiving account respectively based on the intimacy index between the bonus package sending account and each bonus package receiving account respectively, includes: and respectively distributing the money of the red envelope to each red envelope receiving account according to the intimacy index between the red envelope receiving account and the red envelope sending account.

Optionally, if the higher the intimacy index between two accounts is, the higher the intimacy degree between two users owning the two accounts is, the higher the intimacy index between the two accounts is, the higher the allocated red envelope amount of the red envelope receiving account with the higher intimacy index between the two accounts and the red envelope sending account is; if the intimacy index between two accounts is higher, which indicates that the intimacy degree between two users owning the two accounts is lower, the higher intimacy index between the two accounts and the red packet sending account is, the lower the red packet amount allocated to the red packet receiving account is.

Or determining the intimacy index between the red packet receiving account and the red packet sending account, determining the preset red packet amount corresponding to the intimacy index, and distributing the determined red packet amount to the red packet receiving account.

Or, determining an intimacy index between the red packet receiving account and the red packet sending account, determining a preset weight corresponding to the intimacy index, calculating a product result of the determined weight and the total amount of the red packets (the total amount of the red packets included in at least one configuration parameter), and allocating the total amount of the red packets to the red packet receiving account (the amount of the total amount of the red packets is the calculated product result). Optionally, the preset weight corresponding to the intimacy degree index is not greater than 1.

The above is only a preferred way of allocating the money amount of the bonus package to each bonus package receiving account based on the intimacy index between the bonus package sending account and each bonus package receiving account, which is provided in the embodiment of the present application, and specifically, the inventor can arbitrarily set a specific implementation way of allocating the money amount of the bonus package to each bonus package receiving account based on the intimacy index between the bonus package sending account and each bonus package receiving account according to the own requirement, which is not limited herein.

Further, the manner of allocating the money of the red envelope to each red envelope receiving account respectively may also be: calculating the total number of the red packet receiving accounts in all the red packet receiving accounts corresponding to the red packet sending account, determining the average red packet amount of each red packet receiving account based on the total amount of the red packets and the total number of the red packet receiving accounts (the average red packet amount is determined by dividing the total amount of the red packets by the total number of the red packet receiving accounts), and respectively determining the red packet amount corresponding to each red packet receiving account as the average red packet amount.

Or, the manner of allocating the money of the red envelope to each red envelope receiving account respectively may also be: and randomly distributing the total amount of the red packets to each red packet receiving account.

In this embodiment, preferably, a total amount of the red envelope allocated to each red envelope receiving account corresponding to the red envelope sending account is not greater than a total amount of the red envelope corresponding to the red envelope sending account (where the total amount of the red envelope is the total amount of the red envelope included in the at least one configuration parameter).

The above is only the preferred way of allocating the money amount of the red envelope to each red envelope receiving account respectively provided in the embodiment of the present application, and specifically, the inventor may arbitrarily set the way of allocating the money amount of the red envelope to each red envelope receiving account according to the own requirement, which is not limited herein.

S302, red packet information indicating a red packet sending account and a red packet amount corresponding to the red packet receiving account is generated according to the red packet amount distributed by the red packet receiving account.

Optionally, for each red packet receiving account, red packet information corresponding to the red packet receiving account is generated based on the red packet amount allocated to the red packet receiving account, and the red packet information corresponding to the red packet receiving account indicates the red packet amount allocated to the red packet receiving account and the red packet sending account corresponding to the red packet receiving account.

Further, as shown in fig. 2, at least one parameter configuration item set in the red envelope configuration interface provided in the embodiment of the present application may further include a red envelope sending time period configuration item 7, and the user fills the red envelope sending time period at a corresponding position 8 of the red envelope sending time period configuration item 7 in the red envelope configuration interface, so that at least one configuration parameter returned to the server includes the red envelope sending time period.

Fig. 4 is a flowchart of another method for determining red envelope information respectively corresponding to each red envelope receiving account according to the embodiment of the present application.

As shown in fig. 4, the method includes:

s401, distributing the money of the red envelope to each red envelope receiving account respectively based on the intimacy index between each red envelope sending account and each red envelope receiving account;

the execution process of step S401 provided in this embodiment is the same as the execution process of step S301 provided in the above embodiment, and for the execution process of step S401, reference is made to the above description of step S301, which is not repeated herein.

S402, determining historical behavior data between a red packet receiving account and a red packet sending account, and determining red packet sending time within a red packet sending time period corresponding to the red packet receiving account based on the historical behavior data;

optionally, in this embodiment of the present application, an execution sequence between step S401 and step S402 is not limited, that is, step S401 may be executed first, and then step S402 may be executed; step S401 may be executed after step S402 is executed; or step S401 and step S402 are performed simultaneously.

In this embodiment, preferably, for each red packet receiving account corresponding to a red packet sending account, determining historical behavior data between the red packet sending account and the red packet receiving account, and determining a red packet sending time corresponding to the red packet receiving account based on the historical behavior data (the determined red packet sending time is within a red packet sending time period included in at least one parameter configuration item).

And S403, generating red packet information indicating a red packet sending account, a red packet amount and red packet sending time corresponding to the red packet receiving account according to the red packet amount distributed by the red packet receiving account and the determined red packet sending time corresponding to the red packet receiving account.

Optionally, for each red packet receiving account corresponding to the red packet sending account, red packet information corresponding to the red packet receiving account is generated according to the red packet amount to which the red packet receiving account is allocated and the red packet sending time corresponding to the red packet receiving account, and the generated red packet information corresponding to the red packet receiving account indicates the red packet amount to which the red packet receiving account is allocated, the red packet sending time corresponding to the red packet receiving account, and the red packet sending account corresponding to the red packet receiving account.

Further, in order to facilitate understanding of the method for generating the red envelope information provided in the embodiment of the present application, a method of "determining historical behavior data between a red envelope receiving account and a red envelope sending account, and determining a red envelope sending time within a red envelope sending time period corresponding to the red envelope receiving account based on the historical behavior data" in the method for generating the red envelope information provided in the embodiment of the present application is described in detail, and please refer to fig. 5 specifically.

As shown in fig. 5, the method includes:

s501, determining historical behavior data between a red packet receiving account and a red packet sending account;

s502, analyzing historical behavior data, and determining at least one special date corresponding to the red envelope receiving account, wherein the at least one special date comprises a commemorative day related to a user with the red envelope receiving account;

s503, judging whether a special date exists in the red packet sending time period; if the special date exists in the red packet sending time period, executing step S504; if no special date exists in the red packet sending time period, executing step S505;

s504, selecting one special date from all special dates existing in the red packet sending time period, and determining the special date as red packet sending time corresponding to the red packet receiving account;

optionally, the manner of selecting one special date from the special dates existing in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account may be: selecting one special date from all special dates existing in a red packet sending time period by a user with a red packet sending account to determine the special date as red packet sending time corresponding to a red packet receiving account; alternatively, it may be: and randomly selecting one special date from all special dates in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account.

The above is only a preferred manner of the process of "selecting one special date from among special dates existing in the red packet transmission time period to determine the red packet transmission time corresponding to the red packet receiving account" provided in the embodiment of the present application, and specifically, the inventor may arbitrarily set a specific execution manner of the process of "selecting one special date from among special dates existing in the red packet transmission time period to determine the red packet transmission time corresponding to the red packet receiving account" according to the needs of the inventor, which is not limited herein.

S505, determining whether a known festival exists in the red packet sending time period; if yes, go to step S506; if not, go to step S507;

further, as shown in fig. 5, in the method for determining historical behavior data between a red packet receiving account and a red packet sending account and determining red packet sending time within a red packet sending time period corresponding to the red packet receiving account based on the historical behavior data according to the embodiment of the present application, if no special date exists within the red packet sending time period, the method further includes: it is determined whether a known holiday exists within the red packet transmission period.

In the embodiment of the present application, it is preferable that the known festival is a legal festival and a holiday (such as labor festival, national festival, mid-autumn festival, etc.), the above are only some known festivals provided in the embodiment of the present application, and specific contents related to the known festivals are not described in detail herein.

S506, selecting one known festival from all known festivals existing in the red packet sending time period to determine the known festival as red packet sending time corresponding to the red packet receiving account;

optionally, selecting one known festival from known festivals existing in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account includes: selecting one known festival from all known festivals existing in a red packet sending time period by a user with a red packet sending account to determine the red packet sending time corresponding to a red packet receiving account; or randomly selecting one known festival from all known festivals existing in the red packet sending time period to be determined as the red packet sending time corresponding to the red packet receiving account.

The above is only a preferred manner of "selecting one known festival from known festivals existing in a red packet transmission time period to determine the red packet transmission time corresponding to the red packet receiving account" provided in the embodiment of the present application, and specifically, the inventor may arbitrarily set an execution manner of "selecting one known festival from known festivals existing in a red packet transmission time period to determine the red packet transmission time corresponding to the red packet receiving account" according to his own needs, which is not limited herein.

S507, determining an estimated contact date between the red packet receiving account and the red packet sending account within a red packet sending time period based on historical behavior data between the red packet receiving account and the red packet sending account;

optionally, based on historical behavior data between the red packet receiving account and the red packet sending account, a time period in which historical time coincides with the red packet sending time period [ for example, if the red packet sending time period is from 2018, month 1 to 2018, month 15, then respectively determining from 8 month 1 to 8 month 15 of each year in historical time as a time period coinciding with the red packet sending time period (e.g., determining from 2017, month 8, 1 to 8 month 15 as a time period coinciding with the red packet sending time period), and determining an estimated contact date from the determined time period (historical interaction behavior data is generated between the red packet sending account and the red packet receiving account at the estimated contact date; that is, there is interaction behavior between a user owning the red packet sending account and a user owning the red packet receiving account at the estimated contact date).

S508, selecting one estimated contact date from the determined estimated contact dates to determine the estimated contact date as the red packet sending time corresponding to the red packet receiving account.

Optionally, selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account, where the method includes: selecting one estimated contact date from the estimated contact dates by a user with the red packet sending account to determine the estimated contact date as red packet sending time corresponding to the red packet receiving account; or randomly selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account.

The above is merely a preferred manner of selecting one estimated contact date from each determined estimated contact date to determine the red packet sending time corresponding to the red packet receiving account, and specifically, the inventor may arbitrarily set a specific implementation manner of selecting one estimated contact date from each determined estimated contact date to determine the red packet sending time corresponding to the red packet receiving account according to a requirement of the inventor, which is not limited herein.

In this embodiment, preferably, for each red packet receiving account corresponding to a red packet sending account, analyzing historical behavior data between the red packet receiving account and the red packet sending account, and determining at least one special date corresponding to the red packet receiving account [ wherein the at least one special date includes: a memorial day associated with the user who owns the red envelope receiving account (e.g., a birthday, wedding memorial day, etc.) can be obtained from the user who owns the red envelope receiving account; judging whether a special date corresponding to the red packet receiving account exists in the red packet sending time period or not; if the special date corresponding to the red packet receiving account exists in the red packet sending time period, selecting one special date from each special date corresponding to the red packet receiving account existing in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if no special date corresponding to the red packet receiving account exists in the red packet sending time period, determining whether a known festival exists in the red packet sending time period; if the known festival exists in the red packet sending time, selecting one known festival from all known festivals existing in the red packet sending time period to determine the known festival as the red packet sending time corresponding to the red packet receiving account; if the known festival does not exist in the red packet sending time, determining the estimated contact date between the red packet receiving account and the red packet sending account within the red packet sending time period based on historical behavior data between the red packet receiving account and the red packet sending account; and selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account.

Further, in this embodiment of the application, if it is determined that there is no estimated contact date between the red packet receiving account and the red packet sending account within the red packet sending time period based on the historical behavior data between the red packet receiving account and the red packet sending account, a randomly selected one day of two holidays within the red packet sending time period may be determined as the red packet sending time corresponding to the red packet receiving account; if there is no double holiday in the red packet sending time period, one day may be randomly selected from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account/the red packet receiving account is deleted (where the red packet receiving account deletion indicates that the red packet receiving account is no longer used as the red packet receiving account in the embodiment of the present application).

The above is only a preferred implementation manner of the process of determining historical behavior data between the red packet receiving account and the red packet sending account, and determining red packet sending time within the red packet sending time period corresponding to the red packet receiving account based on the historical behavior data, which is provided in this embodiment of the present application, and specifically, the inventor may arbitrarily set an implementation manner of the process according to own requirements, which is not limited herein.

In this embodiment, preferably, after each piece of red packet information corresponding to a red packet generation request is generated, if it is determined that the current amount paid by the client for the red packet generation request is not less than the total amount of the red packet amounts indicated by the pieces of red packet information corresponding to the red packet generation request, each piece of generated red packet information corresponding to the red packet generation request is determined to be an effective red packet information, and correspondingly, the server pushes, to the red packet receiving account indicated by the effective red packet information, the red packet indicating the red packet amount indicated by the effective red packet information at the red packet sending time indicated by the effective red packet information.

Fig. 6 is a flowchart of another red packet information generating method according to an embodiment of the present application.

As shown in fig. 6, the method includes:

s601, receiving a red packet generation request which indicates that a red packet sending account exists and is sent by a client, and returning a red packet configuration interface to the client;

s602, receiving at least one configuration parameter returned by the client through a red packet configuration interface, wherein the configuration parameter comprises an affinity index range and a total amount of the red packet;

s603, determining each red packet receiving account which has the intimacy index within the intimacy index range with the red packet sending account from each friend account associated with the red packet sending account;

s604, determining the red packet information corresponding to each red packet receiving account respectively, wherein the red packet information indicates the amount of the red packet, and the sum of the amounts of the red packets indicated by the generated red packet information is not more than the total amount of the red packet;

optionally, the execution manner of steps S601 to S604 provided in the embodiment of the present application is the same as the execution manner of steps S101 to S104 provided in the embodiment described above, and for the specific execution process of steps S601 to S604, reference is made to the description of steps S101 to S104 in the embodiment described above, which is not repeated herein.

S605, returning each generated red packet information to the client;

optionally, in this embodiment of the application, after the server generates each piece of red packet information corresponding to the red packet generation request sent by the client in step S604, each piece of generated red packet information may be returned to the client, so that the client performs a response operation on each piece of red packet information corresponding to the red packet generation request returned by the server.

In this embodiment of the present application, preferably, the response operation of the client to each piece of red packet information returned by the server includes a modification operation of the client to each piece of red packet information returned by the server and corresponding to the red packet generation request.

Optionally, the operation of modifying each red packet information may include: adding a piece of red packet information in each piece of returned red packet information, wherein the piece of added red packet information indicates a red packet receiving account, and the piece of added red packet information also indicates a red packet amount [ here, the user can autonomously set the red packet amount for the piece of added red packet information through the client ], and the red packet receiving account indicated by the piece of added red packet information is different from the red packet receiving account corresponding to each piece of red packet information returned by the server.

Optionally, the operation of modifying each red packet information may include: and deleting at least one piece of red packet information in each piece of returned red packet information. Namely, at least one piece of red packet information is selected from the returned red packet information, and the selected red packet information is deleted.

Optionally, the operation of modifying each red packet information may include: at least one piece of red packet information is selected from the returned red packet information, and the content indicated by the selected red packet information is modified (for example, the red packet amount indicated by the red packet information is modified).

Optionally, the modification operation on each piece of red packet information may include one or more of an addition operation, a deletion operation, and a modification operation on each piece of returned red packet information.

The above is only the preferred mode of the client for the response operation on each piece of red packet information returned by the client according to the embodiment of the present application, and specifically, the inventor can arbitrarily set the mode of the client for the response operation on each piece of red packet information returned by the client according to the own requirement, which is not limited here.

S606, receiving the response operation of the client to each returned red packet information, generating at least one piece of target red packet information, determining each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of the red packet.

Optionally, the server receives a response operation of the client on each piece of red packet information returned, modifies each piece of red packet information corresponding to the red packet generation request generated by the server in step S604 to generate at least one piece of target red packet information [ where at least one piece of target red packet information is a response operation according to each piece of red packet information returned by the client), modifies each piece of red packet information corresponding to the red packet generation request generated by the server in step S604 to obtain red packet information (where the obtained red packet information also corresponds to the red packet receiving account and indicates that there is a red packet amount), and determines each piece of target red packet information as a new piece of red packet information corresponding to the red packet generation request (that is, it may be considered that each piece of red packet information generated in step S604 is deleted, and determines at least one piece of target red packet information generated in step S606 as the generated red packet information corresponding to the red packet generation request).

Further, after step S606 is completed, in this embodiment of the application, each piece of determined new red packet information corresponding to the red packet generation request may also be returned to the client, so that the client performs response operation on the returned red packet information again, or each piece of new red packet information corresponding to the red packet generation request determined in step S606 is used as the finally generated red packet information corresponding to the red packet generation request, so that the user at the client side can know the information.

Further, as shown in fig. 6, the method for generating red packet information according to the embodiment of the present application may further include:

step S607, determining whether the current amount paid by the client for the red packet generation request is not less than the total amount of the red packet amount indicated by each red packet information corresponding to the red packet generation request; if the current amount is not less than the total amount, go to step S608; if the current amount is less than the total amount, executing step S609;

optionally, step S607 may be executed after step S606, or may be executed before step S606 (if executed before step S606, it is described that the method for generating red envelope information provided in the embodiment of the present application does not execute step S606 any more, and whether to execute steps S605 to S606 in the embodiment of the present application, or whether to execute step S606, which may be set by the inventor according to his own needs).

Optionally, for each piece of red packet information corresponding to the red packet generation request that is finally determined (if step S606 is not executed, each piece of red packet information corresponding to the red packet generation request that is finally determined is each piece of red packet information generated in step S604; if step S606 is executed, each piece of red packet information corresponding to the red packet generation request that is finally determined is each piece of target red packet information determined in step S606); calculating the sum of the money amounts of the red parcels indicated by each piece of red parcel information (summing the money amounts of the red parcels indicated by each piece of red parcel information, wherein the obtained summation result is the sum of the money amounts of the red parcels indicated by each piece of red parcel information, namely the total money amount of the money amounts of the red parcels indicated by each piece of red parcel information); determining whether the current amount paid by the client for the red packet generation request is not less than the calculated total amount; if yes, go to step S608; if not, go to step S609.

Step S608, determining each piece of red packet information as an effective red packet information;

optionally, after the red packet information is determined to be valid red packet information, the red packet information can be pushed to a red packet receiving account by the server in a red packet mode; if the red packet information is not determined to be valid red packet information, the red packet information cannot be pushed to a red packet receiving account number by the server in a red packet mode.

Optionally, the server may push the red packet carrying the red packet amount indicated by the effective red packet information to the red packet receiving account indicated by the effective red packet information at the red packet sending time indicated by the effective red packet information.

And step S609, determining the difference between the current amount and the total amount, and returning payment prompting information for prompting the user at the client side to pay the difference to the client.

Optionally, if the current amount is less than the total amount, determining a difference between the current amount and the total amount, and returning a prompt message to the client, where the prompt message is used to prompt the user at the client side to pay the difference, so as to execute step S608 after the client pays the difference.

Further, in the method for generating red envelope information provided in the embodiment of the present application, in a case that it is determined that the current amount paid by the client for the red envelope generation request is not less than the calculated total amount, a case that the current amount paid by the client for the red envelope generation request is greater than the calculated total amount is included, in this case, a difference between the paid current amount and the calculated total amount may be determined, and the difference may be placed in an amount recycle pool corresponding to the red envelope generation request.

Optionally, after receiving the red packet generation request, the server sets an empty amount recycling pool corresponding to the red packet generation request, where the amount recycling pool is used for recycling the amount. For example, in a case where the current amount paid by the client for the red packet generation request is greater than the calculated total amount, a difference between the current amount paid and the calculated total amount is determined, and the difference is deposited into the amount recycling pool corresponding to the red packet generation request, so as to recycle the difference.

Furthermore, in a red envelope information generation method provided by the embodiment of the application, red envelope prompt information corresponding to effective red envelope information can be further determined, so that at the red envelope sending time indicated by the effective red envelope information, the red envelope corresponding to the effective red envelope information is received and the account number is pushed to send the red envelope, the red envelope carries the red envelope amount indicated by the effective red envelope information and is determined the red envelope prompt information corresponding to the effective red envelope information.

Optionally, for each valid red packet information corresponding to the red packet generation request, the following process may be performed: determining red packet prompt information corresponding to the effective red packet information, determining red packet sending time indicated by the effective red packet information, and further pushing a red packet to a red packet receiving account corresponding to the effective red packet information at the red packet sending time indicated by the effective red packet information, wherein the pushed red packet carries the red packet amount indicated by the effective red packet information and the red packet prompt information corresponding to the effective red packet information.

Optionally, the manner of determining the red packet prompt information corresponding to the red packet information may be: and determining red packet prompt information corresponding to the red packet information based on the red packet sending time indicated by the red packet information. For example, if the red packet sending time indicated by the red packet information is the birthday of the user of the red packet receiving account indicated by the red packet information, it is determined that the red packet prompt information corresponding to the red packet information is related to the birthday (e.g., the generated red packet prompt information corresponding to the red packet information is happy birthday); if the red packet sending time indicated by the red packet information is a known festival, determining that red packet prompt information corresponding to the red packet information is related to the known festival (for example, when the red packet sending time indicated by the red packet information is a national festival, determining that the red packet prompt information corresponding to the red packet information is national festival happy).

Further, in the method for generating the red envelope information provided by the embodiment of the application, the client is also supported to autonomously set the red envelope prompt information corresponding to the red envelope information.

The above is only the determination and setting manner of the red packet prompt message provided in the embodiment of the present application, and the inventor can arbitrarily set the specific determination manner of the red packet prompt message according to the needs of the inventor, which is not limited herein.

Further, in the method for generating the red envelope information provided in the embodiment of the present application, the amount of the red envelope carried by the red envelope which is not received by the red envelope receiving account over the time period of sending the red envelope may be put into the amount recycling pool corresponding to the request for generating the red envelope.

Optionally, for each valid red packet information corresponding to the red packet generation request, a red packet of the red packet amount indicated by the valid red packet information is pushed to the red packet receiving account indicated by the valid red packet information within the red packet generation time period indicated by the red packet generation request; after the red envelope generation time period indicated by the red envelope generation request, all the red envelopes which are successfully pushed and are not picked and which correspond to the red envelope generation request need to be determined, and all the red envelopes which are not successfully pushed and correspond to the red envelope generation request need to be determined; and depositing the determined red packet amount indicated by each red packet into an amount recycling pool corresponding to the red packet generation request so as to return the total amount in the amount recycling pool corresponding to the red packet generation request to the client (the account for paying for the red packet generation request).

Fig. 7 is a flowchart of another method for generating red envelope information according to an embodiment of the present application, where the method is applicable to a terminal, and with reference to fig. 7, the method includes:

s701, sending a red packet generation request indicating that a red packet sending account exists to a server;

optionally, the terminal may send a red packet generation request indicating that there is a red packet to send an account to the server through the client disposed on the terminal.

S702, receiving a red packet configuration interface returned by the server;

optionally, after receiving the red packet generation request, the server returns to the red packet configuration interface, and the terminal receives the red packet configuration interface returned by the server through the client set on the terminal and displays the red packet configuration interface on the terminal.

In the embodiment of the present application, preferably, the structure of the red packet configuration interface is described in the above embodiment, and is not described herein again.

Optionally, the user may configure at least one configuration parameter through a red packet configuration interface displayed on the terminal, and send the configured at least one configuration parameter to the server.

And S703, returning at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each red packet information corresponding to the account sent out by the red packet based on the intimacy index range and the total amount of the red packet in the at least one configuration parameter, wherein each red packet information indicates a red packet receiving account and a red packet amount, and the sum of the red packet amounts indicated by the generated red packet information is not more than the total amount of the red packet.

Optionally, the at least one configuration parameter returned to the server by the terminal based on the red packet configuration interface includes the intimacy index range and the total amount of the red packet; after receiving the at least one configuration parameter, the server may generate each piece of red envelope information corresponding to the red envelope generation request based on the received at least one configuration parameter, where a total sum of red envelope amounts indicated by the generated each piece of red envelope information is not greater than a total red envelope amount.

Optionally, please refer to the description of the above embodiment for the process of generating, by the server, each piece of red packet information corresponding to the red packet generation request according to the received at least one configuration parameter, which is not described herein again.

In this embodiment of the present application, preferably, the at least one configuration parameter further includes a red packet transmission time period. Correspondingly, when the at least one configuration parameter further includes a red packet sending time period, the server indicates red packet sending time according to each piece of red packet information, which is generated by the at least one configuration parameter and corresponds to the red packet generating request, and the red packet sending time indicated by the red packet information may be the red packet sending time, which is located in the red packet sending time period and corresponds to the red packet receiving account indicated by the red packet information.

Optionally, please refer to the description of the above embodiment, and details are not repeated herein, in a manner of determining the red packet sending time corresponding to the red packet receiving account indicated by the red packet information corresponding to the red packet generating request based on the red packet sending time period.

In the following, the red envelope information generating apparatus provided in the embodiment of the present invention is described, and the red envelope information generating apparatus described below may be considered as a program module that is required to be provided by a server to implement the red envelope information generating method provided in the embodiment of the present invention. The contents of the red packet information generating device described below may be referred to in correspondence with the contents of the red packet information generating method described above.

Fig. 8 is a schematic structural diagram of a red packet information generating device according to an embodiment of the present application.

As shown in fig. 8, the apparatus includes:

a red packet generation request receiving unit 81, configured to receive a red packet generation request that indicates that a red packet sending account exists and is sent by a client, and return a red packet configuration interface to the client;

the configuration parameter receiving unit 82 is configured to receive at least one configuration parameter returned by the client through the red packet configuration interface, where the configuration parameter includes an affinity index range and a total amount of the red packet;

a red envelope receiving account number determining unit 83, configured to determine, from the respective friend account numbers associated with the red envelope sending account numbers, each red envelope receiving account number whose affinity index with the red envelope sending account number is within the affinity index range;

a red packet information determining unit 84, configured to determine red packet information corresponding to each red packet receiving account, where the red packet information indicates a red packet amount, and a sum of the red packet amounts indicated by the generated red packet information is not greater than a total red packet amount.

Optionally, the red packet information determining unit includes:

the device comprises a red packet amount determining unit, a red packet amount determining unit and a red packet amount determining unit, wherein the red packet amount determining unit is used for distributing red packet amount to each red packet receiving account based on the intimacy index between a red packet sending account and each red packet receiving account;

and the red packet information determining subunit is used for generating red packet information which indicates that a red packet sending account and a red packet amount are included and corresponds to the red packet receiving account according to the red packet amount allocated to the red packet receiving account.

Optionally, the at least one configuration parameter further includes a red packet sending time period, and the red packet information determining unit provided in an embodiment of the present application further includes a red packet sending time determining unit, configured to determine historical behavior data between a red packet receiving account and a red packet sending account, and determine, based on the historical behavior data, red packet sending time located in the red packet sending time period and corresponding to the red packet receiving account.

Correspondingly, the red packet information determining subunit is specifically configured to: and generating the red packet information which indicates the red packet sending account, the red packet amount and the red packet sending time corresponding to the red packet receiving account according to the red packet amount distributed by the red packet receiving account and the determined red packet sending time corresponding to the red packet receiving account.

In this embodiment of the present application, preferably, the red packet sending time determining unit is specifically configured to: determining historical behavior data between a red packet receiving account and a red packet sending account; analyzing historical behavior data, and determining at least one special date corresponding to the red envelope receiving account, wherein the at least one special date comprises a commemorative day related to a user owning the red envelope receiving account; judging whether a special date exists in the red packet sending time period or not; if the special dates exist in the red packet sending time period, selecting one special date from all the special dates existing in the red packet sending time period to determine the special date as the red packet sending time corresponding to the red packet receiving account; and if no special date exists in the red packet sending time period, selecting one known festival from all known festivals existing in the red packet sending time period to determine the known festival as the red packet sending time corresponding to the red packet receiving account.

Further, the red packet sending time determining unit provided in the embodiment of the present application is further configured to determine, based on historical behavior data between a red packet receiving account and a red packet sending account, an estimated contact date between the red packet receiving account and the red packet sending account within a red packet sending time period when there is no known holiday within the red packet sending time period; and selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account.

Further, the red packet information generating device provided by the embodiment of the present application further includes a response unit, where the response unit is configured to return each generated red packet information to the client; and receiving response operation of the client to each returned red packet information, generating at least one piece of target red packet information, determining each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, and indicating the amount of the red packet by the target red packet information.

Further, the red envelope information generating device provided by the embodiment of the present application further includes a payment unit, where the payment unit is configured to: determining whether the current amount paid by the client for the red packet generation request is not less than the total amount of the red packet amount indicated by each red packet information corresponding to the red packet generation request; if the current amount is not less than the total amount, determining each piece of red packet information as an effective red packet information; and if the current amount is less than the total amount, determining the difference between the current amount and the total amount, and returning payment prompt information for prompting the user at the client side to pay the difference to the client.

Further, the red packet information generating device provided by the embodiment of the present application further includes a recycling unit, and the recycling unit is configured to determine a difference between the current amount and the total amount if the current amount is not less than the total amount, and place the difference into an amount recycling pool corresponding to the red packet generating request.

Further, the red envelope information generating device provided by the embodiment of the present application further includes a red envelope pushing unit, configured to determine red envelope prompt information corresponding to the valid red envelope information; and at the red packet sending time indicated by the effective red packet information, pushing a red packet to a red packet receiving account corresponding to the effective red packet information, wherein the red packet carries the red packet amount indicated by the effective red packet information and the determined red packet prompt information corresponding to the effective red packet information.

Further, the recycling unit in the red packet information generating device provided in the embodiment of the present application is further configured to: and putting the money of the red envelope carried by the red envelope which is not picked up by the receiving account of the red envelope in the money recovery pool corresponding to the request for generating the red envelope after the time period of sending the red envelope is exceeded.

The red packet information generating device shown in fig. 8 provided by the embodiment of the present invention is applicable to a server; optionally, fig. 9 shows a block diagram of a hardware structure of a server, and referring to fig. 9, the hardware structure of the server may include: at least one processor 91, at least one communication interface 92, at least one memory 93 and at least one communication bus 94;

in the embodiment of the present invention, the number of the processor 91, the communication interface 92, the memory 93 and the communication bus 94 is at least one, and the processor 91, the communication interface 92 and the memory 93 complete mutual communication through the communication bus 94;

the processor 91 may be a central processing unit CPU, or an Application Specific Integrated Circuit ASIC (Application Specific Integrated Circuit), or one or more Integrated circuits configured to implement embodiments of the present invention, etc.;

the memory 93 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory) or the like, such as at least one disk memory;

wherein the memory stores a program, the processor may invoke the program stored in the memory, and the program is operable to:

receiving a red packet generation request which indicates that a red packet sending account exists and is sent by a client, and returning a red packet configuration interface to the client;

determining each red packet receiving account number of which the intimacy index between the friend account number and the red packet sending account number is within the intimacy index range from each friend account number associated with the red packet sending account number;

and determining the red packet information corresponding to each red packet receiving account respectively, wherein the red packet information indicates the amount of the red packet, and the sum of the amounts of the red packets indicated by the generated red packet information is not more than the total amount of the red packet.

In the following, the red envelope information generating apparatus provided in the embodiment of the present invention is introduced, and the red envelope information generating apparatus described below may be considered as a program module that is required to be provided by the terminal to implement the red envelope information generating method provided in the embodiment of the present invention. The contents of the red packet information generating device described below may be referred to in correspondence with the contents of the red packet information generating method described above.

Fig. 10 is a schematic structural diagram of a red packet information generating device according to an embodiment of the present application.

As shown in fig. 10, the apparatus includes:

a red packet generation request sending unit 101, configured to send a red packet generation request indicating that there is a red packet sending account to the server;

a red packet configuration interface receiving unit 102, configured to receive a red packet configuration interface returned by the server;

a configuration parameter returning unit 103, configured to return at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each piece of red packet information corresponding to the red packet sending account based on the intimacy index range and the total amount of red packets in the at least one configuration parameter, where each piece of red packet information indicates a red packet receiving account and a red packet amount, and a total amount of red packets indicated by each piece of red packet information generated is not greater than the total amount of red packets.

In this embodiment of the application, preferably, the at least one configuration parameter further includes a red packet sending time period, and the red packet information further indicates red packet sending time within the red packet sending time period, which corresponds to the red packet receiving account indicated by the red packet information.

The red packet information generating device shown in fig. 10 provided by the embodiment of the present invention can be applied to a terminal; optionally, fig. 11 shows a block diagram of a hardware structure of the terminal, and referring to fig. 11, the hardware structure of the terminal may include: at least one processor 111, at least one communication interface 112, at least one memory 113, and at least one communication bus 114;

in the embodiment of the present invention, the number of the processor 111, the communication interface 112, the memory 113, and the communication bus 114 is at least one, and the processor 111, the communication interface 112, and the memory 113 complete mutual communication through the communication bus 114;

the processor 111 may be a central processing unit CPU, or an Application Specific Integrated Circuit ASIC (Application Specific Integrated Circuit), or one or more Integrated circuits configured to implement embodiments of the present invention, etc.;

the memory 113 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory) or the like, such as at least one disk memory;

wherein the memory stores a program, the processor may invoke the program stored in the memory, the program to:

receiving a red packet configuration interface returned by the server;

The embodiment of the application provides a method, a device, a terminal and a server for generating red packet information, wherein a red packet generation request indicating that a red packet sending account exists and sent by a client is received, and a red packet configuration interface is returned to the client; receiving at least one configuration parameter (the configuration parameter comprises an affinity index range and a total amount of the red packet) returned by the client through a red packet configuration interface; determining each red packet receiving account which has an affinity index within the affinity index range with the red packet sending account from each friend account associated with the red packet sending account; and determining the red packet information corresponding to each red packet receiving account (the sum of the red packet amounts indicated by the generated red packet information is not greater than the total red packet amount), so that the purpose of generating the red packet information corresponding to the red packet generation request is achieved, the problem of single red packet information generation mode in the prior art is solved, and the application of the user based on the red packet is facilitated to effectively improve the viscosity between the user and other users.

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed in the embodiment corresponds to the method disclosed in the embodiment, so that the description is simple, and the relevant points can be referred to the description of the method part.

Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A red packet information generating method is characterized by comprising the following steps:

receiving at least one configuration parameter returned by the client through the red packet configuration interface, wherein the configuration parameter comprises an affinity index range, a red packet sending time period and a total amount of the red packets, and the affinity index range is an affinity index or an affinity index interval;

determining all account numbers in the friend address list of the red packet sending account number as friend account numbers related to the red packet sending account number; or determining all accounts in a group designated by the red packet sending account as friend accounts associated with the red packet sending account, wherein the group designated by the red packet sending account comprises any one or more groups in each group to which the red packet sending account belongs;

determining each bonus receiving account number, of which the intimacy index between the two account numbers is within the intimacy index range, from each friend account number associated with the bonus issuing account number, wherein the intimacy index between the two account numbers is determined according to space interaction data between the two account numbers or the attribute of any one of the two account numbers for marking the other account number;

determining historical behavior data between the red packet receiving account and the red packet sending account, and determining red packet sending time within the red packet sending time period corresponding to the red packet receiving account based on the historical behavior data, specifically comprising: if no special date or known festival exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date on which historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account;

determining red packet information corresponding to each red packet receiving account, wherein the red packet information indicates red packet amount and red packet sending time, and the sum of the generated red packet amount indicated by each red packet information is not more than the total red packet amount;

returning each generated red packet information to the client, receiving response operation of the client to each returned red packet information, and generating at least one piece of target red packet information; the response operation comprises: adding red packet information into each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and determining each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of the red packet.

2. The method of claim 1, wherein the determining the red packet information respectively corresponding to each red packet receiving account comprises:

distributing the money of the red parcels to each red parcel receiving account respectively based on the intimacy index between the red parcel sending account and each red parcel receiving account;

and according to the red packet amount distributed by the red packet receiving account, red packet information indicating the red packet sending account and the red packet amount corresponding to the red packet receiving account is generated.

3. The method according to claim 2, wherein the generating of the red packet information indicating that the red packet sending account and the red packet amount correspond to the red packet receiving account according to the red packet amount allocated to the red packet receiving account comprises:

and generating the red packet information which indicates that the red packet sending account, the red packet amount and the red packet sending time correspond to the red packet receiving account according to the red packet amount distributed by the red packet receiving account and the determined red packet sending time corresponding to the red packet receiving account.

4. The method of claim 3, wherein the determining historical behavior data between the red packet receiving account and the red packet sending account, and determining a red packet sending time within the red packet sending time period corresponding to the red packet receiving account based on the historical behavior data comprises:

determining historical behavior data between the red packet receiving account and the red packet sending account;

analyzing the historical behavior data, and determining at least one special date corresponding to the red envelope receiving account, wherein the at least one special date comprises a commemorative day related to the user owning the red envelope receiving account;

judging whether the special date exists in the red packet sending time period or not;

if the special dates exist in the red packet sending time period, selecting one special date from all the special dates existing in the red packet sending time period to determine the special date as the red packet sending time corresponding to the red packet receiving account;

and if the special date does not exist in the red packet sending time period, selecting one known festival from all known festivals existing in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account.

5. The method of claim 1, further comprising:

determining whether the current amount paid by the client for the red packet generation request is not less than the total amount of the red packet amounts indicated by each piece of red packet information corresponding to the red packet generation request;

if the current amount is not less than the total amount, determining each piece of red packet information as an effective red packet information;

and if the current amount is less than the total amount, determining the difference between the current amount and the total amount, and returning payment prompt information for prompting the user at the client side to pay the difference to the client side.

6. The method of claim 5, wherein if the current amount is not less than the total amount, the method further comprises:

and determining the difference between the current amount and the total amount, and putting the difference into an amount recycling pool corresponding to the red packet generation request.

7. The method of claim 6, further comprising:

determining red packet prompt information corresponding to the effective red packet information;

and at the red packet sending time indicated by the effective red packet information, pushing a red packet to a red packet receiving account corresponding to the effective red packet information, wherein the red packet carries the red packet amount indicated by the effective red packet information and the determined red packet prompt information corresponding to the effective red packet information.

8. A red packet information generation method is characterized by comprising the following steps:

receiving a red packet configuration interface returned by the server;

returning at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each piece of red packet information corresponding to the red packet sending account based on an intimacy index range, a red packet sending time period and a total red packet amount in the at least one configuration parameter, wherein the intimacy index range is an intimacy index or intimacy index interval, each piece of red packet information indicates a red packet receiving account and a red packet amount and a red packet sending time corresponding to the red packet receiving account and located in the red packet sending time period, and the sum of the red packet amounts indicated by the generated each piece of red packet information is not greater than the total red packet amount;

the determination mode of the red packet receiving account is as follows: determining all account numbers in the friend address list of the red packet sending account number as friend account numbers related to the red packet sending account number; or determining all accounts in a group designated by the red packet sending account as friend accounts associated with the red packet sending account, wherein the group designated by the red packet sending account comprises any one or more groups in each group to which the red packet sending account belongs; determining each bonus receiving account number, of which the intimacy index between the two account numbers is within the intimacy index range, from each friend account number associated with the bonus issuing account number, wherein the intimacy index between the two account numbers is determined according to space interaction data between the two account numbers or the attribute of any one of the two account numbers for marking the other account number;

the red packet sending time is determined in the following mode: determining historical behavior data between the red packet receiving account and the red packet sending account, and if no special date or known festival exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on the historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date when historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account;

receiving each red packet message generated and returned by the server, acquiring response operation to each returned red packet message, and returning the response operation to the server to enable the server to generate at least one piece of target red packet message; the response operation comprises: adding red packet information into each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and the server determines each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of the red packet.

9. A red envelope information generating apparatus, comprising:

the configuration parameter receiving unit is used for receiving at least one configuration parameter returned by the client through the red packet configuration interface, wherein the configuration parameter comprises an affinity index range, a red packet sending time period and a total amount of the red packet, and the affinity index range is an affinity index or an affinity index interval;

the system comprises a red packet receiving account number determining unit, a red packet receiving account number determining unit and a red packet sending account number determining unit, wherein the red packet receiving account number determining unit is used for determining all account numbers in a friend address list of the red packet sending account number as friend account numbers related to the red packet sending account number; or determining all account numbers in a group specified by the red envelope sending account number as friend account numbers associated with the red envelope sending account number, wherein the group specified by the red envelope sending account number comprises any one or more groups in each group to which the red envelope sending account number belongs; determining each bonus receiving account number, of which the intimacy index between the two account numbers is within the intimacy index range, from each friend account number associated with the bonus issuing account number, wherein the intimacy index between the two account numbers is determined according to space interaction data between the two account numbers or the attribute of any one of the two account numbers for marking the other account number;

the red packet information determining unit is configured to determine historical behavior data between the red packet receiving account and the red packet sending account, and determine, based on the historical behavior data, red packet sending time within the red packet sending time period corresponding to the red packet receiving account, and specifically includes: if no special date or known festival exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date on which historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account; determining red packet information corresponding to each red packet receiving account respectively, wherein the red packet information indicates red packet amount and red packet sending time, and the sum of the generated red packet amounts indicated by the red packet information is not more than the total red packet amount

The response unit is used for returning the generated red packet information to the client, receiving response operation of the client on the returned red packet information and generating at least one piece of target red packet information; the response operation comprises: adding red packet information to each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and determining each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates that the amount of the red packet exists.

10. A server, comprising: at least one memory and at least one processor; the memory stores a program, the processor invokes the program stored by the memory, the program to:

receiving at least one configuration parameter returned by the client through the red packet configuration interface, wherein the configuration parameter comprises an affinity index range, a red packet sending time period and a total amount of the red packet, and the affinity index range is an affinity index or an affinity index interval;

determining all account numbers in the friend address list of the red packet sending account number as friend account numbers associated with the red packet sending account number; or determining all account numbers in a group specified by the red envelope sending account number as friend account numbers associated with the red envelope sending account number, wherein the group specified by the red envelope sending account number comprises any one or more groups in each group to which the red envelope sending account number belongs;

determining each red packet receiving account number of which the intimacy index between the two account numbers is within the intimacy index range from each friend account number associated with the red packet sending account number, wherein the intimacy index between the two account numbers is determined according to space interaction data between the two account numbers or the attribute of any one of the two account numbers for marking the other account number;

determining historical behavior data between the red packet receiving account and the red packet sending account, and determining red packet sending time which is corresponding to the red packet receiving account and is located in the red packet sending time period based on the historical behavior data, wherein the method specifically comprises the following steps: if no special date or known festival exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date on which historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account;

returning each generated red packet information to the client, receiving response operation of the client to each returned red packet information, and generating at least one piece of target red packet information; the response operation comprises: adding red packet information to each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and determining each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of the red packet.

11. A red envelope information generating apparatus, comprising:

a configuration parameter returning unit, configured to return at least one configuration parameter to the server based on the red packet configuration interface, so that the server generates each piece of red packet information corresponding to the red packet sending account based on an intimacy index range, a red packet sending time period, and a total red packet amount in the at least one configuration parameter, where the intimacy index range is an intimacy index or an intimacy index interval, each piece of red packet information indicates a red packet receiving account, a red packet amount, and a red packet sending time within the red packet sending time period corresponding to the red packet receiving account, and a sum of the red packet amounts indicated by the generated each piece of red packet information is not greater than the total red packet amount;

the red packet sending time is determined in the following mode: determining historical behavior data between the red packet receiving account and the red packet sending account, and if no special date or known festival exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on the historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date when historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the estimated contact date as the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account;

receiving each red packet message generated and returned by the server, acquiring response operation to each returned red packet message, and returning the response operation to the server to enable the server to generate at least one piece of target red packet message; the response operation comprises: adding red packet information to each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and the server determines each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of the red packet.

12. A terminal, comprising: at least one memory and at least one processor; the memory stores a program, the processor invokes the memory stored program, the program to:

receiving a red packet configuration interface returned by the server;

the determination mode of the red packet receiving account is as follows: determining all account numbers in the friend address list of the red packet sending account number as friend account numbers associated with the red packet sending account number; or determining all account numbers in a group specified by the red envelope sending account number as friend account numbers associated with the red envelope sending account number, wherein the group specified by the red envelope sending account number comprises any one or more groups in each group to which the red envelope sending account number belongs; determining each red packet receiving account number of which the intimacy index between the two account numbers is within the intimacy index range from each friend account number associated with the red packet sending account number, wherein the intimacy index between the two account numbers is determined according to space interaction data between the two account numbers or the attribute of any one of the two account numbers for marking the other account number;

the red packet sending time is determined in the following mode: determining historical behavior data between the red packet receiving account and the red packet sending account, and if no special date or known holiday exists in the red packet sending time period, determining an estimated contact date between the red packet receiving account and the red packet sending account in the red packet sending time period based on the historical behavior data between the red packet receiving account and the red packet sending account, wherein the estimated contact date is a date when historical interaction behavior exists between the red packet receiving account and the red packet sending account; selecting one estimated contact date from the determined estimated contact dates to determine the estimated contact date as the red packet sending time corresponding to the red packet receiving account; (ii) a If the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date does not exist, randomly selecting one day from double holidays in the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account; if the special date and the known festival do not exist in the red packet sending time period, and the estimated contact date and the double holiday do not exist, randomly selecting one day from the red packet sending time period to determine the red packet sending time corresponding to the red packet receiving account, or deleting the red packet receiving account;

receiving each red packet information generated and returned by the server, acquiring response operation to each returned red packet information, and returning the response operation to the server to enable the server to generate at least one piece of target red packet information; the response operation comprises: adding red packet information into each returned red packet information, deleting the red packet information, and modifying the content indicated by the red packet information; and the server determines each piece of generated target red packet information as new red packet information corresponding to the red packet generation request, wherein the target red packet information indicates the amount of red packets.

13. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used for executing the red packet information generating method according to any one of claims 1 to 7 or executing the red packet information generating method according to claim 8.