CN112711722A

CN112711722A - Data processing and assisting method, device and storage medium

Info

Publication number: CN112711722A
Application number: CN201911017269.XA
Authority: CN
Inventors: 张璐; 孟瑶; 张进; 滕怀宏; 何赛; 李岩; 王霞
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-10-24
Filing date: 2019-10-24
Publication date: 2021-04-27

Abstract

The embodiment of the application provides a data processing and assisting method, data processing and assisting equipment and a storage medium. In the embodiment of the application, the first user pulls the user for the application by inviting the second user to the application to generate the specified behavior, the resource sharing mechanism is embedded in the process that the first user requests the second user to generate the specified behavior in the application, the participation enthusiasm of the second user can be increased through the resource sharing mechanism, the participation degree and the participation effect of the second user are improved, and the quick increase of the user reflux amount of the application is facilitated.

Description

Data processing and assisting method, device and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data processing and boosting method, device, and storage medium.

Background

In the prior art, some internet applications provide a pull reward mechanism to seed users. Under the mechanism, the seed user shares the related links of the application with the new user, and if the new user accesses the application through the links shared by the seed user, the application provides coupons and rewards for the seed user, or improves the grade of the seed user, and the like, so as to encourage the seed user.

However, the user backflow effect brought by the existing mode is not ideal, the backflow speed is low, the backflow amount is low, and particularly, the user backflow effect of the existing mode is increasingly poor along with the time, so that a new solution is urgently needed in the face of user backflow.

Disclosure of Invention

Aspects of the present application provide a data processing and boosting method, device and storage medium for rapidly increasing a user reflow amount of an application.

An embodiment of the present application provides a data processing method, including: displaying a page pointed by a first link, wherein the first link is shared by a first user; responding to the operation of a second user on a trigger control on the page, and determining that the second user performs specified behaviors on the first user; acquiring the resource shared by the first user for the second user; wherein the trigger control corresponds to the specified behavior.

An embodiment of the present application further provides a data processing method, including: displaying a sharing page according to a sharing request of a first user; acquiring resource information to be shared by the first user based on the sharing page; generating a first link required by resource sharing based on the resource information, wherein a page pointed by the first link contains a trigger control, and the trigger control corresponds to a specified behavior; and sending the first link to a second user so that the second user performs specified actions on the first user through the trigger control and acquires the resources shared by the first user.

The embodiment of the application further provides a power assisting method, which comprises the following steps: displaying a first link shared by a first user; responding to the click operation of a second user on the first link, and displaying a red packet getting page pointed by the first link; responding to the operation of the second user on the power-assisted control on the red envelope getting page, performing power assistance on the first user, and obtaining the red envelope shared by the first user for the second user.

The embodiment of the application further provides a power assisting method, which comprises the following steps: displaying a red envelope sharing page according to a power-assisted request of a first user; acquiring the red envelope information to be shared by the first user based on the red envelope sharing page; generating a first link required for sharing the red envelope based on the red envelope information, wherein a red envelope getting page pointed by the first link comprises a power-assisted control; and sending the first link to a second user so that the second user can assist the first user through the assistance control and obtain the red envelope shared by the first user.

An embodiment of the present application further provides a computer device, including: a memory, a processor, and a display;

the display is used for displaying a page pointed by a first link, and the first link is shared by a first user; the memory for storing a computer program; the processor, coupled with the memory, to execute the computer program to: responding to the operation of a second user on a trigger control on the page, and determining that the second user performs specified behaviors on the first user; acquiring the resource shared by the first user for the second user; wherein the trigger control corresponds to the specified behavior.

the display is used for displaying a sharing page according to a sharing request of a first user; the memory for storing a computer program; the processor, coupled with the memory, to execute the computer program to: acquiring resource information to be shared by the first user based on the sharing page; generating a first link required by resource sharing based on the resource information, wherein a page pointed by the first link contains a trigger control, and the trigger control corresponds to a specified behavior; and sending the first link to a second user so that the second user performs specified actions on the first user through the trigger control and acquires the resources shared by the first user.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement any one of the data processing methods and the steps in the assisting method provided in the embodiments of the present application.

In the embodiment of the application, the first user pulls the user for the application by inviting the second user to the application to generate the specified behavior, the resource sharing mechanism is embedded in the process that the first user requests the second user to generate the specified behavior in the application, the participation enthusiasm of the second user can be increased through the resource sharing mechanism, the participation degree and the participation effect of the second user are improved, and the quick increase of the user reflux amount of the application is facilitated.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic structural diagram of a network system according to an exemplary embodiment of the present application;

fig. 2 is a schematic diagram illustrating a sharing approval process based on a red packet according to an exemplary embodiment of the present application;

fig. 3a to fig. 3e are schematic state diagrams of a part of interfaces involved in a sharing approval process according to an exemplary embodiment of the present application;

fig. 4 is a schematic view of a procedure of approval based on a bonus packet according to an exemplary embodiment of the present application;

5a-5d are schematic diagrams of states of portions of interfaces involved in a compliment process provided by an exemplary embodiment of the present application;

fig. 6a is a schematic diagram of a background data processing flow corresponding to a red packet according to an exemplary embodiment of the present application;

fig. 6b is a schematic diagram of a background data processing flow corresponding to a red packet in the present application according to an exemplary embodiment;

fig. 7a is a schematic flowchart of a data processing method according to an exemplary embodiment of the present application;

FIG. 7b is a schematic flow chart diagram of another data processing method provided in an exemplary embodiment of the present application;

FIG. 8a is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application;

fig. 8b is a schematic structural diagram of another computer device according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, 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 application.

Aiming at the problem of user backflow in the prior art, in the embodiment of the application, a first user pulls a user for the application by inviting a second user to the application to generate a specified behavior, a resource sharing mechanism is embedded in the process that the first user requests the second user to generate the specified behavior in the application, the participation enthusiasm of the second user can be increased through the resource sharing mechanism, the participation degree and the participation effect of the second user are improved, and the user backflow amount of the application is favorably and rapidly increased.

Fig. 1 is a schematic structural diagram of a network system according to an exemplary embodiment of the present application. As shown in fig. 1, the network system includes: a server device 10a and at least two terminal devices 10 b. The implementation forms of the server device 10a and the terminal device 10b presented in fig. 1 are only exemplary and are not limited thereto.

The server device 10a and each terminal device 10b may be connected wirelessly or by wire. Alternatively, the server device 10a may be communicatively connected to the terminal device 10b through a mobile network, and accordingly, the network format of the mobile network may be any one of 2G (gsm), 2.5G (gprs), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4G + (LTE +), WiMax, 5G, and other network formats that may appear in the future. Alternatively, the server device 10a may also be communicatively connected to each terminal device 10b through bluetooth, WiFi, infrared, or the like.

In the present embodiment, the physical form of the server device 10a is not limited. The server device 10a may be a single server device, a cloud server array, or a Virtual Machine (VM) running in the cloud server array. In addition, the server device may also refer to other computing devices with corresponding service capabilities, for example, a computer, a smart phone, and other terminal devices running a server program.

In this embodiment, the terminal device 10b is a computer device used by a user and having functions of computing, accessing internet, communicating and the like required by the user, and may be a smart phone, a tablet computer, a personal computer, a wearable device and the like, for example. The terminal device 10b typically comprises at least one processing unit and at least one memory. The number of processing units and memories depends on the configuration and type of terminal device 10 b. The Memory may include volatile, such as RAM, non-volatile, such as Read-Only Memory (ROM), flash Memory, etc., or both. The memory typically stores an Operating System (OS), one or more application software programs, and may also store program data and the like. In addition to the processing unit and the memory, the terminal device 10b may also include a network card chip, an IO bus, an audio/video component, and other basic configurations. Optionally, depending on the implementation of the terminal device 10b, the terminal device 10b may also include some peripheral devices, such as a keyboard, a mouse, a stylus, a printer, etc. These peripheral devices are well known in the art and will not be described in detail herein.

In this embodiment, the terminal device 10b has a client program installed and running thereon, and can provide a local service to the user. Accordingly, the server device 10a installs and runs a server program corresponding to the client program, and can perform corresponding processing in response to various requests of the terminal device 10b, and return the processing result to the terminal device 10b, as well as provide resources to the terminal device 10b, store data of the client, and the like. The server program executed on the server device 10a differs depending on the client program executed on the terminal device 10 b.

For example, the server program and the client program respectively installed on the server device 10a and the terminal device 10b may be the server program and the client program of the nailing and other instant messaging applications, respectively. For example, the server program and the client program installed in the server device 10a and the terminal device 10b may be a server program and a client program of a mail application such as outlook and foxmail, respectively. For example, the server program and the client program installed in the server device 10a and the terminal device 10b may be a server program and a client program of a video playback application such as Tencent and Youke, respectively. For example, the server program and the client program installed in the server device 10a and the terminal device 10b may be a server program and a client program of shopping applications such as naobao, tianmao, kyoto, and zhuoduo, respectively.

In either application, increasing user traffic is one of the major issues that applications have been concerned with and focused on solving. In this embodiment, the first application is taken as an example for description, and the first application may be any application. The first application may employ a mechanism or policy that encourages its visiting users to invite (or pull) their users, increasing their user traffic. For convenience of description, in the embodiment of the present application, a user qualified to invite other users for the first application is referred to as a first user, and other users that can be invited by the first user are referred to as second users, which include but are not limited to: new users and attrition users.

Alternatively, the first user may be any user that accessed the first application within a recent period of time, including, but not limited to: an active user of the first application, a seed user, a user who accessed the first application for the first time during a recent period of time, and a user who accessed the first application occasionally during the recent period of time. The time length of the last period of time is not limited in the embodiment, and can be flexibly set according to the application scene and the application requirement. The active user refers to a user who meets a certain requirement set according to the property of the application. The seed user can attract more users by means of self influence, and is the first user who supports the application.

In this embodiment, the first application employs a pull mechanism to encourage the first user to pull the user for his or her purpose. The pull mechanism requires the first user to invite the second user to the first application for a specified action to occur with respect to the first user, thereby achieving the purpose of pulling the user for the first application. In this embodiment, the "designated behavior" is not limited, but is a behavior required or set in the pull mechanism, and can be flexibly set according to an application scenario. For example, the specified behavior may be a praise behavior, a group behavior or a blood adding behavior, or may be a comment behavior, a price cut behavior, a behavior of browsing a specified commodity or a payment substitute behavior, and the like.

For example, taking the designated behavior as an approval behavior as an example, the essence of the first user pulling the second user for the first application is to invite the second user to enter the designated page of the first application as an approval of the first user, and only if the second user approves the approval of the first user on the designated page of the first application, it means that the first user successfully pulls the first application to the second user for the first application.

For another example, taking the designated behavior as a grouping behavior, the essence of the first user pulling the second user for the first application is to invite the second user to enter the designated page of the first application to join the team created by the first user, and only if the second user successfully joins the team created by the first user on the designated page of the first application, it means that the first user successfully pulls the second user for the first application.

For another example, taking the specified behavior as a comment behavior as an example, the fact that the first user pulls the second user for the first application is to invite the second user to enter a specified page of the first application to make a comment for the first user, and only if the second user successfully comments the first user on the specified page of the first application, it means that the first user successfully pulls the second user for the first application.

Furthermore, in the above mentioned pull mechanism, a resource sharing mechanism is embedded in the process that the first user invites the second user to enter the first application and performs a specified action on the second user, so that the participation enthusiasm of the second user can be increased through the resource sharing mechanism, the participation degree and the participation effect of the second user can be improved, and the user reflux amount of the application can be increased rapidly. In the embodiment of the present application, the resource shared by the first user is not limited, and may be any resource that can attract the second user, for example, a network red packet, a coupon, a credit, a flow, a virtual token, a telephone fee, and the like.

In the following embodiments of the present application, a technical solution of the embodiments of the present application will be described from the perspective of a first user inviting a second user and the perspective of a second user accepting the first user invitation. For convenience of description and distinction, a terminal device used by a first user is referred to as a first terminal device, and a terminal device used by a second user is referred to as a second terminal device. The first user is a user authorized to invite other users for the first application, the second user is a target user to be invited, and the number of the second users may be one or multiple.

From the perspective of inviting a second user by a first user, the technical scheme of the application is explained as follows:

for the first user, if the second user is expected to be successfully pulled for the first application, the second user needs to be invited to enter the first application and perform a specified action on the second user. Based on this, the first user may send a sharing request to the first terminal device. For example, a first user may enter a resource sharing initiation page provided by a first application, click a resource sharing initiation control on the resource sharing initiation page, and send a sharing request. Or, the first user may also send a sharing request to the first terminal device in a voice manner.

For the first terminal device, the sharing page can be displayed according to the sharing request of the first user. The sharing page is an interactive interface between the first user and the first terminal device, and the first terminal device may obtain resource information to be shared by the first user based on the sharing page, as shown in fig. 1. Furthermore, a first link required for resource sharing can be generated based on the resource information to be shared by the first user. As shown in FIG. 1, the page pointed to by the first link includes a trigger control, which corresponds to a specified behavior. In other words, once the trigger control is triggered, an "operation that takes place a specified action with respect to the first user" is performed. In addition, the page pointed by the first link also has a function of enabling the second user to acquire the resource shared by the first user, which can be called as a resource getting page, so that the trigger control can also trigger the operation of acquiring the resource shared by the first user for the second user. As shown in fig. 1, after obtaining the first link, the first terminal device may send the first link to the second user (actually, send the first link to the second terminal device), so that the second user performs a specified action on the first user through a trigger control on a page pointed by the first link and obtains a resource shared by the first user.

In this embodiment, through a first link of resource sharing, a trigger control is set on a page pointed to by the first link, and the trigger control is bound with "an operation of a specified behavior occurring to a first user" and "an operation of acquiring a resource shared by the first user for a second user" in advance, so that by using a resource sharing mechanism, it is beneficial to attract the second user to enter the page pointed to by the first link, and by means of the psychology that the second user wants to acquire the resource shared by the first user, the second user can be prompted to have the specified behavior occurring to the first user through the trigger control and acquire the resource shared by the first user, and the user reflux amount of the application is beneficial to be rapidly increased.

In the embodiment of the present application, an implementation manner in which the first terminal device obtains the resource information to be shared by the first user based on the sharing page is not limited. The resource information to be shared by the first user may include but is not limited to: the first user shares the information of the type, the total amount, the number and the like of the resources.

In an optional embodiment, the sharing page carries resource information to be shared by the first user by default, for example, the information includes information such as a total amount of resources to be shared by the first user, a number of resources, and the like. Based on this, the first terminal device can directly acquire resource information such as the total amount of resources and the number of resources to be shared by the first user from the sharing page.

In another optional embodiment, the shared page supports input operations. By means of the input function of the sharing page, the first user can input resource information such as the total amount of resources to be shared, the number of the resources and the like on the sharing page according to the resource sharing requirement. Based on this, the first terminal device may respond to an input operation of the first user on the shared page, and acquire the total amount of resources, the number of resources, and the like input by the first user as resource information.

It should be noted that the sharing page in this embodiment may support multiple input modes, for example, a text input mode, a voice input mode, an image input mode, or the like.

In an exemplary embodiment, a voice input control is included on the sharing page, and the first user can click the voice input control to invoke a voice input function and input resource information to be shared. For example, a first user may input a speech signal: "i want to share 10 random red parcels, and the total amount of the red parcels is 100 yuan", wherein the resource information that the first user wants to share is the total amount of the 10 random red parcels and the red parcels is 100 yuan. For another example, the first user may input a speech signal: "i want to share 5 traffic packets, and the total traffic is 200M", where the 5 traffic packets and the total traffic is 200M are resource information that the first user wants to share. For the first terminal device, the voice signal input by the first user on the sharing page can be acquired, and the resource information such as the total amount of the resources and the number of the resources to be shared by the first user can be analyzed from the voice signal.

In another exemplary embodiment, the sharing page includes an information input area, and the first user can click the information input area to invoke an information input function, and input the resource information to be shared in the information input area. As shown in fig. 1, the shared page includes an information input area corresponding to the total amount of resources and an information input area corresponding to the number of resources, and the first user can input the total amount of resources and the number of resources in the two information input areas, respectively. In fig. 1, the total amount of resources is shown as 100, and the number of resources is shown as 10. For the first terminal device, the text information input by the first user on the sharing page may be acquired, so as to acquire resource information such as the total amount of resources and the number of resources to be shared by the first user.

In another exemplary embodiment, the sharing page includes a photographing control, and the first user may click the photographing control to photograph the carrier including the resource information that the first user wants to share, to obtain a picture including the resource information that the first user wants to share, or may click the photographing control to load the picture including the resource information that the first user wants to share from the gallery. The first terminal device can identify the picture provided by the first user, and acquire resource information such as the total amount of resources and the number of resources to be shared by the first user, which are contained in the picture.

Further, in other embodiments of the present application, the resource information to be shared by the first user may include, in addition to the total amount of resources and the number of resources to be shared by the first user, guidance text information. For example, the first user inputs the guide text information on the sharing page in a voice input mode, a text input mode or an image input mode. Optionally, taking the sharing page shown in fig. 1 as an example, the sharing page may further include: indicating an information input area corresponding to the text information. In fig. 1, the indication text information is illustrated by taking "like, lead package" as an example. For the first terminal device, the guidance text information input by the first user on the sharing page may also be obtained.

The text information is guided to reflect the incidence relation between resource sharing and the occurrence of specified behaviors, and the text information belongs to the language and the plan expression used in the resource sharing. For example, the guidance text information may be "help me add power, get a red envelope", "stretch out your fat hand to give me a praise, and you have an opportunity to empty a shopping cart", and the like, and may be flexibly set according to application requirements. The instructional text information may be embodied in the first link and may also be embodied in the page to which the first link points. In other words, the first link and/or the page to which the first link points may include the referring text information. For the second user, by directing the text information, information can be obtained, and the information is a resource which can be shared by the first user after the first user has a specified behavior.

After the resource information to be shared by the first user is obtained, a first link required for resource sharing can be generated based on the resource information. And the generation process of the first link is related to the data processing logic corresponding to the resource sharing. The data processing logic corresponding to the resource sharing is different, and the process of generating the first link is also different. In the embodiment, a method for realizing resource sharing by establishing virtual resource flow is provided. That is, in the resource sharing process, an intermediate account is adopted, the resource that the first user needs to share is actually stored in the intermediate account, and under the condition that the second user obtains the resource that the first user shares but does not initiate a resource transfer request, the resource that the second user obtains and is shared by the first user is not transferred from the intermediate account to the second user, and when the second user initiates a resource transfer request for the obtained resource, the resource that the second user obtains is directly transferred from the intermediate account to a third-party resource account related to resource transfer. Therefore, in the whole resource sharing process, the resource does not actually reach the resource account of the second user.

Based on the resource sharing scheme implemented in the virtual resource flow manner, if the resource information to be shared by the first user includes the total amount of resources and the number of resources, the process of generating the first link includes: transferring corresponding resources from the resource account of the first user to the intermediate account according to the total amount of the resources; dividing the total resource amount into N acquirable resource components according to the number of the resources, wherein N represents the number of the resources and is a positive integer; a first link is generated based on the trigger control and the N available resource components. For example, a trigger control may be added to the first link and associated with the N available resource components, such that when the second user clicks on the trigger control, an operation to retrieve a target resource component for the second user from the N available resource components is triggered.

Further, under the condition that the resource information to be shared by the first user includes the total resource amount, the number of resources and the guidance text information, the process of generating the first link includes: transferring corresponding resources from the resource account of the first user to the intermediate account according to the total amount of the resources; dividing the total resource amount into N acquirable resource components according to the number of the resources, wherein N represents the number of the resources and is a positive integer; a first link is generated based on the trigger control, the N available resource components, and the guide text information. For example, a trigger control and referral text information may be added to a first link and the trigger control associated with N available resource components, such that the referral text information is embodied on the first link and, upon the second user clicking on the trigger control, an operation to retrieve a target resource component for the second user from the N available resource components is triggered.

It should be noted that, in combination with the virtual resource flow manner, the operation of generating the first link according to the resource information to be shared by the first user may be completed on the first terminal device side or may be completed by the server device. In the embodiments of the present application, a description of a case where the server device completes the operation is focused. For the situation completed by the server device, the first terminal device needs to provide resource information to be shared by the first user to the server device, and then the server device generates a first link based on the resource information to be shared by the first user and returns the first link to the first terminal device. The process of the server device generating the first link based on the resource information to be shared by the first user is described in the foregoing description, and details are not described here.

In the optional embodiment of the application, the total amount of resources, the number of resources and the guidance text information are not limited at all, and a user can flexibly set the resources as required according to own sharing requirements. Of course, in order to make resource sharing more reasonable, some resource sharing requirements may be set. For example, a total resource requirement may be set to limit the total resource to a reasonable range, such as not less than a set lower limit, such as 0.1, and not greater than a set upper limit, such as 999. The resource number requirement can also be set to limit the resource number within a reasonable range, for example, the resource number can not be less than a set lower limit value, such as 1, and can not be greater than a set upper limit value, such as 99. Further, a term specification may be set for specifying the guide text information, for example, the occurrence of non-civilized words, sensitive words, etc. is not allowed, the maximum word count limit cannot be exceeded, etc. These requirements can be flexibly set according to application requirements.

Based on the above, in some embodiments of the application, in the process of obtaining the resource information to be shared by the first user based on the sharing page, it may be further determined whether the total amount of the resource input by the first user meets the set total amount of the resource requirement; judging whether the number of the resources input by the first user meets the set requirement of the number of the resources; judging whether the guide text information input by the first user meets the set expression specification; if the judgment results of the judgment operations are yes, acquiring the total amount of the resources, the number of the resources and the guidance text information input by the first user as the resource information. Otherwise, if the judgment result of a certain judgment operation is negative, the prompt information can be displayed on the sharing page to prompt the first user to re-input the resource information corresponding to the judgment operation.

Optionally, after the first user inputs a kind of resource information, it may be determined in time whether the resource information input by the first user meets the corresponding requirement; if the resource information is not satisfied, the first user can be prompted to input the resource information again. Or, after the first user inputs all the resource information, judging whether the resource information meets the corresponding requirements; if yes, acquiring resource information input by the first user; if not, prompting the user which resource information does not meet the requirement, and requiring the user to input again.

In the above optional embodiment of the present application, the qualification of the first user for resource sharing is not limited, which means that the first user can pull the user for the first application through the resource sharing manner indefinitely. In addition, of course, some rules may be set according to the application scenario to reasonably limit the number of times and time of resource sharing performed by the first user.

For example, one or more rounds of sharing activities may be set, each round of sharing activities including at least one activity period. And setting an upper limit value of the number of times of allowing resource sharing in each activity period, and/or setting an upper limit value of the number of times of allowing resource sharing in each round of sharing activity. The upper limit values of the allowed resource sharing times in different activity periods can be the same or different. Similarly, the upper limit values of the number of times of resource sharing allowed for the sharing activities of different rounds may be the same or different. In this scenario, the first user needs to share resources in each activity period during each round of sharing activity, the number of times of sharing resources in the activity period cannot exceed the upper limit of the number of times allowed in the activity period, and/or the number of times of sharing resources in the current round of sharing activity cannot exceed the upper limit of the number of times allowed in the current round of sharing activity, and otherwise, the first user cannot continue to share resources.

Based on the above, after receiving the sharing request of the first user, before obtaining the resource information to be shared by the first user based on the sharing page, at least one of the following determination operations may be further performed:

judging whether the total times of sharing resources in the current round of sharing activities of the first user reaches the upper limit of the times allowed by the current round of sharing activities;

judging whether the number of times of sharing resources by the first user in the current activity period reaches the upper limit of the number of times allowed in the current activity period;

and if the judgment result of the at least one judgment operation is negative, the first user is proved to have the resource sharing qualification and can continue to share the resource, and the first user is allowed to execute the input operation on the sharing page. If the judgment result of any judgment operation is yes, the first user does not have the resource sharing qualification any more and cannot share the resource continuously, and the purpose of forbidding the first user to continue sharing the resource can be achieved by forbidding the first user to execute the input operation on the sharing page.

After the first user shares the first link, the first user can also initiate a sharing request again to enter a sharing page. In this scenario, there may be a remaining resource that the first user has previously shared, and in order to facilitate the first user to know the status and related information of the resource that has been previously shared, the first user is allowed to not only re-input new resource information on the sharing page, but also display information of the resource that the first user has previously shared for the first user to view. Further optionally, the sharing page may also display, by default, resource information that the first user has shared the resource last time. For the first terminal device, a sharing page may be displayed according to the sharing request initiated again by the first user, and information of the resource shared by the first user is displayed on the sharing page. Information herein includes, but is not limited to: the time of each shared resource, the total amount of each shared resource, the number of each shared resources, the acquisition state of each shared resource and the like of the first user. The acquisition status here indicates whether the resource has been completely acquired or remains.

Further, when the first user sends the sharing request again, the resources that the first user has previously shared may remain. In view of this, in order to facilitate the first user to continue resource sharing, a sharing control may be further displayed on the sharing page. The first user can click the sharing control to continue to share the remaining resources. The first terminal device can respond to the triggering operation of the first user on the sharing control on the sharing page, and continue to send the first link to the third user, and the third user can be any user who does not acquire the resource shared by the first user. The third user may include a new user different from the second user, or may include the second user who has not acquired the resource shared by the first user.

In this case, the first link is not limited to the manner of transmitting the first link to the second user or the third user. For example, the first terminal device may directly share the first link with friend users in the nailing and other instant messaging applications, or may directly share the first link with friend users in the microblog and other social applications. Or the first link can be copied and then shared to the friend users in other applications in a pasting mode.

From the perspective of receiving the invitation of the first user from the second user, the technical scheme of the application is explained as follows:

for a second user, the first link shared by the first user can be received, and the page pointed by the first link can be accessed by triggering the first link. Wherein the triggering of the first link includes, but is not limited to: click, long press, hover, touch, double click, etc. Referring to fig. 1, the second terminal device may display a page to which the first link points, and include a trigger control on the page, the trigger control corresponding to the specified behavior. Or, the trigger control binds the operation of the specified behavior of the first user, and once the trigger control is triggered, the operation of the specified behavior of the first user is executed.

For the second user, the triggering control may be triggered, or the triggering control may be selected not to be triggered. In this embodiment, the first link is a connection for resource sharing, and the page pointed by the first link may be regarded as a resource pickup page, which may attract the second user to perform a triggering operation on the trigger control to a certain extent. If the second user performs the triggering operation on the triggering control, the second terminal device may respond to the operation of the second user on the triggering control, determine that the second user performs the specified behavior on the first user, and acquire the resource shared by the first user for the second user.

In the above embodiment, no limitation is made on the pickup eligibility of the second user, that is, the second user may take a specified action on the first user and pickup the resource shared by the first user by default. Of course, some limiting conditions may be set according to different application requirements. These limiting conditions are exemplified below:

in some embodiments, the conditions under which the second user takes a specified action with respect to the first user may be set. Based on the above, after the page pointed by the first link is displayed, whether the second user meets the condition that the first user has the specified behavior or not can be judged; if yes, displaying a trigger control on the page; and otherwise, displaying the first prompt message on the page to prompt the second user that the second user does not meet the condition of the specified action on the first user. Whether or not the second user satisfies the conditions for the first user to take place in the specified behavior, the page may also contain other information, such as guide text information, or some other control, etc. For example, where the second user does not satisfy the conditions for the first user to take a specified action, the page may also have a guidance control thereon that may guide the second user to the first user's home page, the first user's store, an activity page of the application, or a details page of a particular good in the application, and so forth. In these embodiments, the display of the trigger control is associated with whether the second user satisfies a condition for the first user to occur a specified behavior; if the condition is met, displaying a trigger control, so that the second user operates the trigger control to perform specified behavior on the first user; in the event of non-satisfaction, the trigger control is not displayed, such that the second user cannot specify a line for the first user.

In this embodiment, the display mode of the trigger control or the first prompt information on the page is not limited. For example, the trigger control or the first prompt message may be displayed directly on the page. For another example, a first floating window may be displayed on the page, and the first floating window includes a trigger control or first prompt information. The first floating window may be any shape, which is not limited thereto.

The condition of the second user for the first user to generate the specified behavior can be flexibly set according to the application requirement. For example, following the aforementioned embodiment of defining the qualification of the first user for resource sharing, one or more rounds of sharing activities are set, and each round of sharing activities includes at least one activity period. The method comprises the steps that a first user is allowed to perform appointed behaviors to a second user, wherein the upper limit value of times of allowing the second user to perform the appointed behaviors to different first users is set in each activity period, and/or only one appointed behavior of the same second user to the same first user is allowed to occur in each activity period, and/or the second user does not have the appointed behaviors after each round of sharing activities is finished.

Based on the above, the determining whether the second user meets the condition for the first user to perform the specified action includes at least one of the following determining operations:

judging whether the times of the second user for different first users to generate the specified behaviors in the current activity period reach the upper limit or not;

judging whether the current round of sharing activities participated by the first user is finished;

judging whether the second user has already performed the specified behavior on the first user within the current activity period;

if the judgment result of any judgment operation is yes, determining that the second user does not meet the condition of the first user for generating the specified behavior; and if the judgment result of the at least one judgment operation is negative, determining that the second user meets the condition of the first user for generating the specified behavior.

In an optional embodiment, if the second user operates the trigger control on the page, the second terminal device may cooperate with the server device to determine that the second user performs the specified behavior on the first user, where the process includes: the second terminal equipment responds to the operation of a second user on the trigger control on the page, sends an information processing request to the server, requests the server equipment to perform processing operation related to the specified behavior for the first user, and returns a processing success message to the second terminal equipment after the processing is successful; and for the second terminal equipment, if the processing success message returned by the server is received, determining that the second user has the appointed behavior on the first user.

According to different designated behaviors, the server device performs processing operations related to the designated behaviors for the first user differently. For example, if the specified behavior is an approval behavior, the server device may receive an approval processing request sent by the second terminal device, increase the approval number of the first user according to the processing request, synchronize the updated approval number of the first user to the first terminal device, and return a processing success message to the second terminal device after the synchronization operation is completed. It should be noted that the processing procedure is only an exemplary process, and is not limited thereto.

In the above embodiment, the condition "acquiring the resource shared by the first user for the second user" is not limited. Of course, reasonable or appropriate resource acquisition conditions may be set according to application requirements. For example, the resource shared by the first user has a validity period, where the validity period refers to a validity period for which the resource is acquired, and may be, for example, 24 hours, 3 days, and the like, and if the validity period ends, the resource shared by the first user cannot be acquired for the second user. For another example, whether the resource shared by the first user remains, if not, the resource shared by the first user cannot be acquired for the second user. Under the condition of setting the resource acquisition condition, before acquiring the resource shared by the first user for the second user, whether the resource shared by the first user is in an acquirable state or not can be judged; and if the resource shared by the first user is in the acquirable state, acquiring the resource shared by the first user for the second user.

Optionally, the determining whether the resource shared by the first user is in the acquirable state includes at least one of the following determination operations:

judging whether the resource shared by the first user is expired;

judging whether the resources shared by the first user are not left;

if the judgment result of any judgment operation is yes, determining that the resource shared by the first user is in an unavailable state; and if the judgment result of the at least one judgment operation is negative, determining that the resource shared by the first user is still in an acquirable state.

Taking the validity period of the resource shared by the first user as 24 hours as an example, judging whether the resource shared by the first user is expired, namely judging whether the time length of sharing the resource shared by the first user exceeds 24 hours; if the time exceeds 24 hours, determining that the resources shared by the first user are expired; otherwise, determining that the resource shared by the first user is not expired.

Optionally, if the resource shared by the first user expires, the expired resource may be returned to the resource account of the first user, or the expired resource may be considered as being invalidated or frozen.

The number of resources shared by the first user may be one or more. If the number of the resources shared by the first user is one, which means that the resources shared by the first user can be acquired by one user, judging whether the resources shared by the first user are not left, namely judging whether the users acquire the resources shared by the first user; if yes, determining that the resources shared by the first user are not left; otherwise, determining that the resources shared by the first user are left. If the number of the resources shared by the first user is multiple, which means that the resources shared by the first user can be acquired by multiple users, whether the resources shared by the first user are not left is judged, that is, whether each resource shared by the first user is acquired by a user is judged; if yes, determining that the resources shared by the first user are not left; otherwise, determining that the resources shared by the first user are left.

Further, under the condition that the resource shared by the first user is still in the non-acquirable state, second prompt information can be displayed on the page, so that on one hand, the second user is prompted to be incapable of acquiring the resource shared by the first user, and on the other hand, whether the second user continues to perform the specified action on the first user is prompted. Under the condition that the resource shared by the first user is in the non-acquirable state, if the second user determines that the specified behavior continues to occur on the first user, the trigger control on the page can be operated, the second terminal device can respond to the operation of the trigger control by the second user, and determine that the specified behavior occurs on the first user by the second user, but the resource shared by the first user cannot be acquired for the second user.

Further, under the condition that the resource shared by the first user is still in the acquirable state, third prompt information can be displayed on the page pointed by the first link to prompt that the resource shared by the first user can be acquired for the second user.

Detailed implementation process of resource acquisition:

the process of obtaining the resource shared by the first user for the second user is related to the data processing logic corresponding to the resource sharing. The data processing logics corresponding to the resource sharing are different, and the process of acquiring the resource shared by the first user for the second user is also different. Continuing with the resource sharing scheme implemented based on the virtual resource flow manner provided in the foregoing embodiment, an embodiment of the present application provides an implementation manner for obtaining a resource shared by a first user for a second user, as described below.

In the optional embodiment, the second terminal device sends a resource acquisition request to the server device, so that the server device determines whether the second user can acquire resources from resources shared by the first user and returns a target resource component acquired by the second user when the second user can acquire the resources; and receiving the target resource component, returned by the server device, acquired by the second user, and displaying the target resource component on the page so that the second user can know the acquired resource amount.

For the server device, the resource acquisition request sent by the second terminal device can be received; judging whether N available resource components remain according to the resource acquisition request; if yes, determining a target resource component acquired by the second user from the remaining resource components, and returning the target resource component to the second terminal equipment; and recording resource acquisition flow information, wherein the resource acquisition flow information comprises information of the target resource component acquired by the second user. The information that the second user acquires the target resource component includes, but is not limited to: identification of the second user, target resource components, acquisition time, etc.

Alternatively, the server device may record a generation order of the N available resource components, and assign the available target resource components to the second user according to the generation order. In addition, the server device may allocate the available target resource component to the second user according to a random allocation manner.

In the resource obtaining process, only the target resource component is allocated to the second user, and the resource corresponding to the target resource component still exists in the intermediate account and is not transferred from the intermediate account to the resource account of the second user, so that a virtual resource flow direction is formed.

And (3) data processing after the resources are acquired:

and after the resources shared by the first user are acquired for the second user, the processing process of the acquired resources by the second user is also involved. And the processing process of the acquired resource by the second user can be different according to different application requirements. For example, in some application scenarios, the second user is allowed to cash out the acquired resource, i.e. the second user may transfer the acquired resource from the intermediate account into its own resource account. For another example, in some application scenarios, the second user is not allowed to bring up the acquired resource, but is allowed to perform a transfer process on the acquired resource, that is, the second user may transfer the acquired resource from the intermediate account to the third-party resource account. And the third-party resource account is different from the resource account of the first user, the resource account of the second user and the intermediate account.

The interpretation of the resource transfer process may vary in different application scenarios. For example, in some scenarios, where the second user-initiated resource transfer activity is a purchase activity, the acquired resource may be transferred from the intermediate account to a resource account of the seller or merchant. For another example, in some scenarios, the second user-initiated resource transfer action is referred to as a gift action, and the acquired resource may be transferred from the intermediate account to the resource account of the gift-giver.

Based on the analysis, after the target resource component is displayed, the second terminal device may further detect whether the second user initiates a resource transfer behavior in the first application, and may determine a third-party resource account related to the resource transfer behavior in a case that it is detected that the second user initiates the resource transfer behavior in the first application; and then, sending a resource transfer request to a server to request the server to transfer the resource corresponding to the target resource component from the intermediate account to a third-party resource account.

Correspondingly, the server-side device may further receive a resource transfer request sent by the second terminal device, where the resource transfer request includes a third-party resource account related to the resource transfer behavior; and acquiring the running information according to the recorded resources, and transferring the resources corresponding to the target resource components from the intermediate account to the third-party resource account.

It should be noted that, all resources corresponding to the target resource component may be transferred from the intermediate account to the third-party resource account in the primary resource transfer behavior. Or, under the action of multiple resource transfers, all the resources corresponding to the target resource component are transferred from the intermediate account to the corresponding third-party resource account for multiple times, and part of the resources are transferred from the intermediate account to the corresponding third-party resource account each time. The accounts of the third party resources involved in different resource transfer activities may be the same or different.

Further, in the embodiment of the application, an expiration date may also be set for the resource shared by the first user acquired by the second user. The term "validity period" herein refers to a validity period during which the resource acquired by the second user is transferred (or used), for example, 48 hours, 7 days, one month, one year, or the like. The second user needs to perform the transfer process on the resource within the validity period. Based on this, before the server device receives the resource transfer request of the second terminal device, it can also determine whether the validity period of the resource corresponding to the target resource component is over; if so, the resource corresponding to the target resource component may be returned to the resource account of the first user from the intermediate account. If not, waiting for the second user to perform the transfer processing on the resource.

Further, after transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account, the server device further needs to record resource transfer flow information, where the resource transfer flow information includes information about transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account. The relevant information here includes but is not limited to: third party resource accounts, the amount of resources transferred, the number of resource transfers, and the transfer time for each resource transfer, among others.

Scenario implementation example:

in order to facilitate understanding of the technical solution of the present application, a certain shopping application is taken as an example in the following scenario embodiment.

In the shopping-like application, to stimulate the first user to pull the user for the application, an interactive (PK) activity is initiated. In the interactive activity, the participating users need to share the praise page with other users to pull the praise pages for the other users, and the different participating users compete for the praise amount (referred to as the PK praise amount), and a party winning the competition or the PK can obtain a certain reward. For example, the party that wins the PK may raise the user level, the higher the offer enjoyed by shopping. As another example, a party that wins a PK may obtain a full discount coupon, a flyer coupon, or a discount coupon during a given event. Wherein the amount of approval of each participating user may represent the amount of users that the participating user pulls for the application.

Alternatively, in the above-described interactive activities, the PK approval amount may be agreed between the participating users in units of users. Or, in the above-mentioned interactive activity, the users participating in the interactive activity may be grouped together, and in units of queues, the PK points out among different groups, and the PK participates in at least two groups, each group including at least one user. This is not limited as to how the users are grouped together. At least two teams participating in a PK, each team containing the same number of users. And each user in each team needs to share the praise page to pull the praise of other users for the user, and the sum of the praise amount of all users in the team is used as the praise amount of the team. For all users participating in the interactive activity, the way that the users pull other users to like the users through the sharing like page is the same or similar, so in this scenario embodiment, the example that the first user pulls the second user to like the users still is taken as an example for explanation. The first user is any user participating in the interactive activity.

In order to facilitate the first user to quickly and efficiently pull more users to like the first user, the shopping application provides a bonus package and like mechanism for the users, namely, a bonus package mechanism is embedded in the process of sharing like the first user. Fig. 2 and 3a to 3e describe a process in which a first user shares praise with a second user through a red packet. Fig. 4 and fig. 5a to 5d describe the process in which the second user agrees to the first user in the process of getting a red envelope.

Referring to fig. 2, the sharing approval process based on the red packet:

step 21: the first user enters an active page on which a red packet emitting control is displayed. The red envelope control is not limited to the implementation form of the red envelope control, and may be, for example, a button, a shortcut key pointing to the red envelope charging page, or a floating window pointing to the red envelope charging page.

Step 22: judging whether the triggering operation of the red packet sending control is monitored; if yes, the first user selects the red packet, and the step 23 is entered; if not, the first user does not generate the red packet, and the sharing approval operation based on the red packet can be finished, or the existing sharing approval process is entered. Triggering operations on the red packet control include, but are not limited to: click, double click, hover, touch, long press, etc.

Step 23: the red envelope top-up page is displayed and step 24 is entered. As shown in fig. 3a, which is a schematic diagram of a red-envelope recharge page, in fig. 3a, the red-envelope recharge page includes a total amount input area, a number input area and a text input area. The text entry field is used for the first user to enter instructional text information, such as "baituoxi-kuai to me praise, send you a red pack".

Optionally, some first qualification criteria may be set for making some reasonable constraints on the behavior of the first user towards the red envelope during the interactive activity. The first qualification defining conditions include, but are not limited to: the total times of red packet generation of the same user during the interactive activity cannot exceed the upper limit value of the permitted times during the activity, such as 999 times; in the case where the interactive activity lasts for a plurality of days, the total number of times of red packet generation by the same user per day cannot exceed the upper limit of the number of times allowed per day, such as 99 times; the total amount of the red packages of the same user during the activity cannot exceed the upper limit value of the amount allowed during the activity, such as 1000 dollars.

Based on the above, in step 24, it is determined whether the first user is qualified to send the red packet according to a first qualification defining condition set in advance; if yes, go to step 26; if not, go to step 25.

Step 25: and displaying reason information of the first user unqualified red packet on the red packet recharging page, and finishing the operation of praise based on the red packet. Taking the total number of red packages during the interactive activity of the first user as the upper limit 999 of the number of red packages allowed during the activity, as shown in FIG. 3b, the "ditch enough! You have accumulated up to an upper limit of 999 times to red packages.

Step 26: and responding to the input operation on the red packet recharging page, acquiring the total amount and the number of the red packets input by the first user, and entering the step 27. Based on the red packet charging page shown in fig. 3a, a schematic diagram of the red packet charging page after the total amount and the number of red packets are input is shown in fig. 3 c. In fig. 3c, the total amount of the red packets is 21.83 yuan, and the number of the red packets is 34 for exemplary illustration.

Optionally, some red packet limiting conditions may be set for limiting the sent red packet, so as to ensure that the sent red packet is more reasonable. Red envelope constraints include, but are not limited to: limiting the total amount of the red packet to be not less than the set minimum amount, such as 0.1 yuan; limiting the number of the red-emitting packages to be not less than a set minimum number, such as 1; and so on. Based on this, in step 26, it can also be determined whether the total amount input by the first user is less than the set minimum amount, and whether the number of red packets input by the first user is less than the set minimum number; if not, the total amount and the number of the red packages input by the first user can be obtained; otherwise, the first user may be prompted to re-enter.

Step 27: and responding to the triggering operation of the first user on the recharging control on the red packet recharging page, sending a recharging request to the server to cooperate with the server to carry out recharging operation, and entering step 28.

Wherein, first terminal equipment cooperates with the server to carry out the operation of adding money, include: the server returns a payment page to the first terminal device, wherein the payment page comprises information such as related information of interactive activities, a payment account, payment amount (total amount of the red packet), payment time and the like; after the first user inputs the payment password to confirm payment, the server side transfers funds corresponding to the total amount of the red packages to the intermediate account from the resource account bound by the first user, generates a first link of the red packages according to the total amount of the red packages and the number of the red packages, and returns the first link to the first terminal device. The flow of the server generating the first link can be seen in the embodiment shown in fig. 6 a.

Step 28: and receiving a first link returned by the server after the recharging is successful, and sharing the first link to the second user by means of a sharing function supported by the shopping application. The first link may be a pan password, but is not limited thereto. In fig. 3d, the first link is illustrated by taking a pan pass code in a red packet form as an example, and guidance text information of "approval of red packet by first user XXX" is displayed on the pan pass code in the red packet form, and the guidance text information is merely an example. In addition, it is shown in fig. 3d that: the sharing modes of the ocean panning circle, the friend circle, the payment treasure, the nail and the like.

It is noted that the praise red envelope shared by the first user may be a random red envelope or a regular red envelope. The random red envelope means that the money amounts of the red envelopes received by different receiving users may be different and are randomly distributed. The conventional red envelope means that the money amounts of the red envelopes received by different receiving users are the same and are fixed. In this embodiment, the type of praise red packet is not limited.

Step 29: the first user again enters the active page with the red packet-emitting control displayed thereon.

Step 30: judging whether the triggering operation of the red packet sending control is monitored; if yes, go to step 31; if not, the sharing approval operation based on the red packet is finished.

Step 31: displaying a red envelope recharging page, wherein the red envelope recharging page comprises a red envelope list area, and information of each red envelope shared by the first user is displayed in the red envelope list area, and the information comprises but is not limited to: the time of sharing the red envelope each time, the total amount of each shared red envelope, whether each shared red envelope is taken up, the total number of each shared red envelope, and the corresponding sharing control under the condition that the red envelope is not taken up. Fig. 3e is a schematic diagram of a red packet top-up page including a red packet list area.

Step 32: and responding to the triggering operation of the sharing control in the red packet list area, and sharing the red packets which are not completely received again.

Optionally, as shown in fig. 3e, the red envelope list area includes at least one sub-area, and each sub-area displays one red envelope information shared by the first user. The first user can click the sub-area corresponding to the corresponding red packet and enter the detail drawing page corresponding to the red packet. For the first terminal equipment, responding to the clicking operation of a first user on a certain sub-area, and displaying a red packet pickup detail page corresponding to the sub-area.

See fig. 4 for a complimentary packet based approval process:

step 41: displaying a first link, the first link being shared by the first user.

Step 42: and responding to the triggering operation of the second user on the first link, and displaying an active page corresponding to the first link.

Optionally, some second qualification conditions can be set in the interactive activity to reasonably limit the behavior of the second user to get the red envelope. The second qualification requirements include, but are not limited to: no approval is allowed after the interactive activity is finished; in the case that the interactive activity lasts for a plurality of days, the total number of times of praise per day by the same user cannot exceed the upper limit value of the number of times allowed per day, such as 10 times; during the interactive activity, for the same praised user, each praised user can only praise for the praised user once every day; and so on.

Based on the above, in step 43, it is determined whether the second user qualifies for approval of the bonus round; if yes, go to step 45; if not, go to step 44.

Step 44: and displaying a red packet page on the active page in a floating window mode, and displaying prompt information on the red packet page to prompt that the second user does not have the qualification of participating in praise of the red packet. The page state diagram in this case is shown in fig. 5 a. In fig. 5a, the second user is shown with the praise times of the day already running out, and the other cases are similar.

Further, on the page shown in fig. 5a, other interface elements may also be displayed, such as a control in the form of "go to my interactive home page", and the second user may enter the interactive home page of the first user by clicking on the control. The content and form of the interactive main page are not limited in the embodiments of the present application, and may be, for example, a page having interest or entertainment, such as a virtual farm page capable of raising a virtual animal.

Step 45: judging whether the red envelope shared by the first user is in a retrievable state; if yes, go to step 46; if not, go to step 47.

Optionally, it may be determined whether the red packet is expired; and if the red packet is overdue, determining that the red packet is in an unavailable state. Or judging whether the red envelope is completely received, namely whether a balance exists; if the red envelope is not picked up, the red envelope is determined to be in a non-picking state. Of course, the two operations described above may be used in combination.

Step 46: displaying the red-packed page in a floating window manner on the active page, displaying the praise control on the red-packed page, and entering step 48. The page state diagram in this case is shown in fig. 5 b. Optionally, some guiding text information may also be displayed on the red envelope page, such as "catch up to like the red envelope bar" shown in fig. 5 b.

Step 47: displaying a red packet page on the active page in a floating window manner, displaying a praise control on the red packet page, displaying prompt information of whether the unavailable red packet continues to be praise or not, and entering step 48. The page state diagram in this case is shown in fig. 5 c. In FIG. 5c, the red pack is expired, and the prompting message shown in FIG. 5c is "cry out for expired red pack and the next time it is too early". For example, the red envelope pickup validity period may be 24 hours, 3 days, etc.

And 48: judging whether the trigger operation of the praise control is monitored; if yes, indicating that the second user approves the first user, and getting the red packet, and entering step 49; if not, finishing the compliment operation based on the red packet.

Step 49: and sending an approval request to the server to complete approval operation on the first user in cooperation with the server. Further, if step 48 is skipped from step 46, the method further includes step 50.

Step 50: and sending a pickup request to the server to complete the red packet pickup operation in cooperation with the server. A schematic diagram of a page in which the second user successfully agrees to the first user and successfully receives the red envelope is shown in fig. 5 d.

Here, fig. 3a to 3e and fig. 5a to 5d are schematic page state diagrams, and interface elements related to the technical solution of the present application are mainly embodied in these drawings, and those skilled in the art can understand that, depending on different application scenarios, the pages shown in these drawings may include some other interface elements, such as pictures, texts, small videos, and the like, which is not limited herein.

In the process of sending the red packet, the server needs to cooperate with the first terminal device to complete a background data processing flow corresponding to the red packet. Similarly, in the process of red packet getting, the server needs to cooperate with the second terminal device to complete the background data processing flow corresponding to the red packet getting. In the embodiment of the present application, the implementation form of the device at the server is not limited, and the device may be one server, a server array, or one service system. The server of this embodiment includes: for example, the first service node responsible for the interactive activity and the second service node responsible for the payment management are shown in fig. 6a, and the background data processing flow corresponding to the red packet is shown in fig. 6 b.

Referring to fig. 6a, the background data processing flow corresponding to the red packet includes:

61a, the first service node receives a recharging request sent by the first terminal device, wherein the recharging request includes information such as total amount of the red packet and the number of the red packet.

62a, the first service node sends a red packet sending instruction to the second service node according to the recharging request, wherein the red packet sending instruction comprises information such as the total amount of the red packets, the number of the red packets and the like.

63a, the second service node creates a payment order and creates a payment link according to the red packet-sending instruction.

64a, the second service node forwards the payment order and the payment link to the first terminal device via the first service node.

65a, the first service node receives the red packet payment request sent by the first terminal device.

66a, the first service node forwards the red envelope payment request to the second service node.

67a, the second service node transfers funds corresponding to the total amount of the red envelope from the resource account of the first user to the intermediate account according to the red envelope payment request.

68a, the second service node divides the total amount of the red packets into M amounts of the red packets, wherein M is the number of the red packets, and records the M amounts of the red packets and the generation sequence for the second user to receive. The M red packet amounts may be the same or different. For example, the second service node may adopt a certain random algorithm to split the total amount of the red packet into M random red packet amounts, but is not limited to this.

69a, the second service node generates a first link required to share the red envelope, the first link pointing to the active page and being associated with the M red envelope amounts.

70a, the second service node returns the first link to the first terminal device through the first service node, so that the first terminal device shares the first link with the second user.

Referring to fig. 6b, the background data processing procedure corresponding to the red packet includes:

61b, the second terminal equipment sends a pickup request to the first service node to request to pickup the red packet.

62b, the first service node forwards the pick-up request to the second service node.

63b, the second service node judges whether M red packet amounts remain according to the getting request; and under the condition that M red packet amounts generated before are remained, distributing one red packet amount to a second user according to the red packet amount generation time, and recording a red packet getting running water. In this process, no actual capital outlay is generated.

And when the second user receives one red packet, the second service node records a red packet receiving running water for the second user. If the second user receives a plurality of red packets, a plurality of red packets can receive running water.

And 64b, the second service node returns the money of the red envelope taken by the second user to the second terminal equipment through the first service node, so that the money of the red envelope is displayed to the second user by the second terminal equipment.

The second user may use the red envelope after getting it. In this embodiment, special provisions are made for sharing the bonus package in favor, which is not available for consumption only during the designated activity.

65b, the second terminal device sends a shopping payment request to the first service node, wherein the shopping payment request carries information such as the resource account of the merchant and the amount to be paid.

66b, the first service node forwards the purchase payment request to the second service node.

67b, the second service node checks the red packet getting assembly line of the second user, and determines the usable red packet amount according to the red packet amount and the amount to be paid in all the red packet getting assembly lines.

For example, if the sum of the red packet amounts in all the red packet fetching flowing water is less than the amount to be paid, all the red packet amounts in all the red packet fetching flowing water can be used as the usable red packet amounts; and conversely, selecting a part of the red envelope to take the red envelope amount in the flowing water (the sum of the red envelope amounts is larger than or equal to the amount to be paid) as the usable red envelope amount.

In this embodiment, the red packet amount received by the second user may be used for multiple times, and each time, a part of the red packet amount is used until the red packet amount is used up or the valid period of the red packet use is over. Optionally, each of the collected red envelope amounts has a usage period of validity, which may be one month, three months, or one year from the date of collection, a specified or particular activity period, or the like.

68b, the second service node transfers the amount of the available red envelope from the intermediate account to the merchant's resource account and records the red envelope usage stream. The red packet using running water can be one or more, and can be determined according to the amount of using several red packets.

Optionally, if the amount to be paid is greater than the sum of all the red-envelope amounts, the second service node further transfers a part of funds from the resource account of the second user to the resource account of the merchant.

69b, the second service node returns the payment result to the second terminal equipment through the first service node.

It should be noted that the above flow is only an exemplary one and is not limited thereto.

The technical scheme of the embodiment of the application mainly relates to the following two processes: the process of resource sharing by the first user, and the process of acquiring the resource shared by the first user by the second user are not limited to these two processes. For example, the technical solution of the present application may also relate to a resource transfer process after the second user acquires the resource. Two main processes and other processes related to the technical solution of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 7a is a schematic flowchart of a data processing method according to an exemplary embodiment of the present application. The embodiment describes a resource sharing process mainly from the perspective of the first user. As shown in fig. 7a, the method comprises:

71a, displaying a sharing page according to a sharing request of a first user;

72a, acquiring resource information to be shared by the first user based on the sharing page;

73a, generating a first link required by resource sharing based on resource information, wherein a page pointed by the first link contains a trigger control, and the trigger control corresponds to a specified behavior;

and 74a, sending the first link to a second user, so that the second user performs specified actions on the first user through a trigger control and acquires the resources shared by the first user.

In this embodiment, the sharing page is an interactive interface between the first user and the first terminal device, and the first terminal device may obtain resource information to be shared by the first user based on the sharing page. The resource information to be shared by the first user includes but is not limited to: the first user shares information such as the total amount of resources and the number of the resources.

In an optional embodiment, the sharing page carries resource information to be shared by the first user by default. Based thereon, one embodiment of step 72a includes: and directly acquiring resource information to be shared by the first user carried by default on the sharing page, such as the total amount of resources, the number of resources and the like.

In another alternative implementation, the shared page supports input operations. Based thereon, another embodiment of step 72a includes: responding to the input operation of the first user on the sharing page, and acquiring the total amount of the resources and the number of the resources input by the first user as resource information.

Based on the above, one embodiment of the step 73a, namely, generating the first link required for resource sharing based on the resource information, includes: transferring corresponding resources from the resource account of the first user to the intermediate account according to the total amount of the resources; dividing the total resource amount into N acquirable resource components according to the number of the resources, wherein N represents the number of the resources and is a positive integer; a first link is generated based on the trigger control and the N available resource components.

Wherein the N acquirable resource components may be the same. For example, the total amount of resources may be divided by the number of resources N to obtain N identical resource components. Of course, the N resource components may be different, where "different" may be that the N resource components are completely different, or that there are some differences in the N resource components. For example, N resource components may be randomly generated according to the total amount of resources and the number N of resources.

In this embodiment, the page pointed to by the first link includes a trigger control, and the trigger control corresponds to the specified behavior. In other words, once the trigger control is triggered, an "operation that takes place a specified action with respect to the first user" is performed. In addition, the page pointed by the first link also has a function of enabling the second user to acquire the resource shared by the first user, which can be called as a resource getting page, so that the trigger control can also trigger the operation of acquiring the resource shared by the first user for the second user.

In this embodiment, the "designated behavior" is not limited, but is a behavior required or set in the pull mechanism, and can be flexibly set according to an application scenario. For example, the specified behavior may be a praise behavior, a group behavior or a blood adding behavior, or may be a comment behavior, a price cut behavior, a behavior of browsing a specified commodity or a payment substitute behavior, and the like.

Further, the resource information to be shared by the first user may include guide text information in addition to the total amount of resources and the number of resources to be shared by the first user. The text information is guided to embody the incidence relation between resource sharing and the occurrence of the specified behaviors. Based on this, in other embodiments of the present application, the obtaining resource information to be shared by the first user based on the sharing page further includes: and acquiring the guide text information input by the first user as resource information. Accordingly, the generating a first link according to the trigger control and the N available resource components includes: a first link is generated based on the trigger control, the N available resource components, and the guide text information. In this embodiment, the page to which the first link points includes, in addition to the trigger control, directed text information. In addition, the first link may also contain guide text information.

In some optional embodiments, in order to make resource sharing more reasonable, some resource sharing requirements may be set. For example, a total resource requirement may be set to limit the total resource to a reasonable range, such as not less than a set lower limit, such as 0.1, and not greater than a set upper limit, such as 999. The resource number requirement can also be set to limit the resource number within a reasonable range, for example, the resource number can not be less than a set lower limit value, such as 1, and can not be greater than a set upper limit value, such as 99. Further, a term specification may be set for specifying the guide text information, for example, the occurrence of non-civilized words, sensitive words, etc. is not allowed, the maximum word count limit cannot be exceeded, etc. These requirements can be flexibly set according to application requirements.

Based on the above, in step 72a, that is, in the process of acquiring the resource information to be shared by the first user based on the sharing page, the following determination operations may also be performed:

judging whether the total amount of the resources input by the first user meets the set total amount of the resources requirement or not;

judging whether the number of the resources input by the first user meets the set requirement of the number of the resources;

judging whether the guide text information input by the first user accords with the set wording specification;

if the judgment results of the judgment operations are yes, acquiring the total amount of the resources, the number of the resources and the guidance text information input by the first user as the resource information.

In some optional embodiments, some rules may also be set according to the application scenario to reasonably limit the number of times, time, and the like of resource sharing performed by the first user. Based on this, before the step 72a, that is, before acquiring the resource information to be shared by the first user based on the sharing page, the method of this embodiment may further include: judging whether the total times of sharing resources in the current round of sharing activities of the first user reaches the upper limit of the times allowed by the current round of sharing activities, wherein each round of sharing activities comprises at least one activity time interval; judging whether the number of times of sharing resources by the first user in the current activity period reaches the upper limit of the number of times allowed in the current activity period; and if the judgment result of the at least one judgment operation is negative, allowing the first user to execute the input operation on the sharing page.

In some optional embodiments, after the first user shares the first link, the sharing request may be initiated again. At this point, resources that the first user has previously shared may remain. In view of this, after sending the first link to the second user, step 74a, the method further comprises: displaying a sharing page according to the sharing request initiated by the first user again, wherein the sharing page displays the information of the resources shared by the first user and a sharing control; and responding to the triggering operation of the first user on the sharing control, and continuously sending the first link to a third user, wherein the third user is any user who does not acquire the resource shared by the first user. The third user may include a new user different from the second user, or may include the second user who has not acquired the resource shared by the first user. When the first user sends the sharing request again, if the resources shared by the first user before are left, the sharing control can be displayed on the sharing page. Therefore, the first user can click the sharing control to continue to share the remaining resources.

Further, in some optional embodiments, the method of this embodiment further includes: receiving a resource acquisition request of a second user; judging whether the N obtainable resource components remain; if yes, determining a target resource component acquired by the second user from the remaining resource components, and returning the target resource component to the second user; and recording resource acquisition flow information, wherein the resource acquisition flow information comprises information of the target resource component acquired by the second user. The information that the second user acquires the target resource component includes, but is not limited to: identification of the second user, target resource components, acquisition time, etc.

In some optional embodiments, the method of this embodiment further includes: receiving a resource transfer request of a second user, wherein the resource transfer request comprises a third-party resource account related to the resource transfer behavior; and acquiring the running information according to the resources, and transferring the resources corresponding to the target resource components from the intermediate account to the third-party resource account.

Further optionally, before receiving the resource transfer request of the second user, the method of this embodiment further includes: judging whether the validity period of the resource corresponding to the target resource component is finished or not; and if so, returning the resources corresponding to the target resource components to the resource account of the first user from the intermediate account.

Further optionally, after transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account, the method of this embodiment further includes: and recording resource transfer flow information, wherein the resource transfer flow information comprises relevant information of transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account.

It should be noted that, the operation related to the resource obtaining request and the operation related to the resource transferring request may be completed by the first terminal device, or may be executed by the server device, which is not limited thereto.

In this embodiment, the first user pulls the user for the application by inviting the second user to the application to generate the designated behavior, and a resource sharing mechanism is embedded in the process that the first user requests the second user to generate the designated behavior in the application, so that the participation enthusiasm of the second user can be increased through the resource sharing mechanism, the participation degree and the participation effect of the second user are improved, and the quick increase of the user reflux amount of the application is facilitated.

Fig. 7b is a schematic flowchart of another data processing method according to an exemplary embodiment of the present application. The present embodiment describes the resource acquisition process mainly from the perspective of the second user. As shown in fig. 7b, the method comprises:

71b, displaying a page pointed by the first link, wherein the first link is shared by the first user;

72b, responding to the operation of the second user on the trigger control on the page, and determining that the second user performs the specified action on the first user;

73b, acquiring the resource shared by the first user for the second user; wherein the trigger control corresponds to the specified behavior.

In this embodiment, the "specified behavior" is not limited, and the specified behavior includes, but is not limited to, at least one of the following: power-assisted behavior, browsing behavior, payment-for-help behavior, and comment behavior. Similarly, the implementation form of the "first link" is not limited in this embodiment, and the first link is, for example, a pan password, a one-dimensional code, a two-dimensional code, or a URL link.

Accordingly, the page pointed to by the first link may be different according to the application scenario. For example, the following steps are carried out: the page may be a PK page in a PK activity, or a cut price page in a cut price activity, or a detail page of a commodity in a group purchase activity, or a resource pickup page in a resource pickup activity, and so on.

In some optional embodiments, before step 72b, that is, before responding to the operation of the trigger control on the page by the second user, the method of this embodiment further includes: judging whether the second user meets the condition that the first user generates the specified behavior; if yes, displaying a trigger control on the page; and otherwise, displaying the first prompt message on the page to prompt the second user that the second user does not meet the condition of the specified action on the first user.

Optionally, the determining whether the second user satisfies the condition for the first user to perform the specified action includes: performing at least one of the following determination operations: judging whether the frequency of the second user to generate the specified behavior for the first user in the current activity period reaches the upper limit; judging whether the current round of sharing activities participated by the first user is finished or not, wherein each round of sharing activities comprises at least one activity time interval; judging whether the second user has already performed the specified behavior on the first user within the current activity period; if the judgment result of any judgment operation is yes, determining that the second user does not meet the condition of the first user for generating the specified behavior; and if the judgment result of the at least one judgment operation is negative, determining that the second user meets the condition of the first user for generating the specified behavior.

In an alternative embodiment, step 72b, determining that the second user has performed the specified action with respect to the first user in response to the second user operating the trigger control on the page, includes: responding to the operation of a second user on the trigger control on the page, and sending an information processing request to the server to request the server equipment to perform processing operation related to the specified behavior for the first user; for the server-side equipment, processing operation related to the specified behavior can be carried out on the first user according to the information processing request, and a processing success message is returned to the second terminal equipment after the processing is successful; and for the second terminal equipment, if the processing success message returned by the server is received, determining that the second user has the appointed behavior on the first user.

In some alternative embodiments, reasonable or appropriate resource acquisition conditions may be set according to application requirements. Under the condition of setting the resource acquisition condition, before acquiring the resource shared by the first user for the second user, whether the resource shared by the first user is in an acquirable state or not can be judged; and if the resource shared by the first user is in the acquirable state, acquiring the resource shared by the first user for the second user.

Optionally, the determining whether the resource shared by the first user is in the acquirable state includes at least one of the following determination operations: judging whether the resource shared by the first user is expired; judging whether all the resources shared by the first user are picked up; if the judgment result of any judgment operation is yes, determining that the resource shared by the first user is in an unavailable state; and if the judgment result of the at least one judgment operation is negative, determining that the resource shared by the first user is still in an acquirable state.

In some optional embodiments, the step 73b of acquiring the resource shared by the first user for the second user includes: the second terminal equipment sends a resource acquisition request to the server equipment, so that the server equipment determines whether the second user can acquire resources from the resources shared by the first user or not and returns a target resource component acquired by the second user under the condition that the second user can acquire the resources; and receiving the target resource component, returned by the server device, acquired by the second user, and displaying the target resource component on the page so that the second user can know the acquired resource amount.

Further optionally, the method of this embodiment further includes: and displaying a viewing control on the page, responding to the triggering operation of the second user on the viewing control, and displaying the resource sharing details of the first user. In this alternative embodiment, the display of the target resource component and the view control on the page is not limited. Wherein, on the page, an optional way of displaying the target resource component and the view control includes: displaying a second floating window on the page, the second floating window comprising a target resource component and a view control,

in an alternative embodiment, the resources shared by the first user are stored in an intermediate account. The second user is only allocated with the target resource component, and the resource corresponding to the target resource component still exists in the intermediate account and is not transferred from the intermediate account to the resource account of the second user, so that a virtual resource flow direction is formed.

After the method of this embodiment displays the target resource component, the method further includes: detecting whether a second user initiates a resource transfer behavior in a first application; if the second user is detected to initiate the resource transfer behavior in the first application, determining a third-party resource account related to the resource transfer behavior, wherein the first application is an application to which a page pointed by the first link belongs; and sending a resource transfer request to the server to request the server to transfer the resource corresponding to the target resource component from the intermediate account to the third-party resource account. The interpretation of the resource transfer process may vary in different application scenarios. For example, in some scenarios, where the second user-initiated resource transfer activity is a purchase activity, the acquired resource may be transferred from the intermediate account to a resource account of the seller or merchant. For another example, in some scenarios, the second user-initiated resource transfer action is referred to as a gift action, and the acquired resource may be transferred from the intermediate account to the resource account of the gift-giver.

In this embodiment, the first user pulls the user for the application by inviting the second user to the application to generate the designated behavior, and a resource sharing mechanism is embedded in the process that the first user requests the second user to generate the designated behavior in the application, so that the enthusiasm of the second user to participate is increased through the resource sharing mechanism, the participation degree and the participation effect of the second user are improved, and the quick increase of the user reflux amount of the application is facilitated.

The data processing method can be applied to various scenes, and information such as specified behaviors and resources can be specified in different application scenes. The technical solution of the present application is described below by taking a power-assisted scenario as an example.

When a first user needs assistance from other users, an assistance request can be sent. In the boosting process, a red envelope sharing mechanism can be embedded. For the first terminal equipment, displaying a red envelope sharing page according to the power-assisted request of the first user; acquiring red envelope information to be shared by a first user based on a red envelope sharing page; red packet information includes, but is not limited to: the total sum of the red packets and the total number of the red packets. And then, generating a first link required for sharing the red envelope based on the red envelope information, wherein the red envelope getting page pointed by the first link comprises a power-assisted control. And then, the first link is sent to a second user, so that the second user can assist the first user through the assistance control and obtain the red envelope shared by the first user.

For the second user, the terminal device (i.e., the second terminal device) of the second user may receive the first link shared by the first user and display the first link shared by the first user. The first link shared by the first user can be sent to the second terminal device by the first terminal device. After the second user sees the first link shared by the first user, the first link may be clicked. The second terminal device can respond to the clicking operation of the second user on the first link, display a red envelope getting page pointed by the first link, and display a power-assisted control on the red envelope getting page. The second user can initiate the action of assisting the first user by operating the assistance control. And the second terminal equipment responds to the operation of the second user on the power-assisted control, performs power assistance on the first user and obtains the red envelope shared by the first user for the second user.

For the detailed implementation process and the related description of the boosting method, reference may be made to the foregoing embodiments, and details are not repeated herein.

In the above embodiment of the application, the second user may click the first link shared by the first user, enter the page pointed by the first link, and approve and receive the bonus package shared by the first user for the first user through an approve control on the page. It should be noted that the manner in which the second user agrees with the first user is not limited to this. For example, in some application scenarios, the first user may share the first link into a social platform or application with interactive functionality, such as a microblog, a circle of friends or the like. In these application scenarios, it is possible to,

the second user can also like the first user directly in a social platform or application with an interaction function, such as a microblog, a comment or a friend circle. For the first application to which the first link belongs, the first application can communicate with social platforms or applications with an interaction function, such as a microblog, a known circle or a friend circle, and the like, so as to acquire the amount of approval of the second user to the first user in the social platforms or applications. The total amount of the praise obtained by the first user comprises the praise amount of the second user to the first user in the social platforms or the applications with the interaction function, and also comprises the praise amount of the second user to the first user on the corresponding page of the first application.

In addition, in the above embodiments of the present application, a detailed description is given to a technical solution of "resource sharing and a certain operation" provided in the embodiments of the present application, by taking a first user as a first application to pull a second user, and taking an "exemplary solution of combining praise and red packet" as an example. However, the technical solution provided in the embodiment of the present application is not limited to an application scenario of pulling a user for an application. For example, in the case where the first application is a shopping-type application provided by an e-commerce, the merchant may also attract more interested users to the store, or attract more users to comment on himself or his merchandise, or promote his merchandise, by "an exemplary scheme of a combination of approval and a red-envelope" or the like, thereby increasing the merchandise exposure rate.

An exemplary scenario focusing on store + Rebate pack or coupon:

for example, merchant a may combine a red-emitting pack or coupon with the operation of the store of interest in order to attract more users to focus on their store. The method comprises the steps that a merchant A firstly determines information of a red packet or a coupon to be issued, then a first link is generated according to the information of the red packet or the coupon to be issued, the first link points to a shop home page of the merchant A, and the first link comprises a focus control; and then the first link is shared in the friend circle, the microblog and/or the known account number of the user, or the first link can be shared in friends of the user, old users of shops and the like. A user seeing the first link can enter a shop front page of a merchant A if the first link is triggered, a floating window of a red-collar packet or a coupon can pop up on the shop front page of the merchant A, and a focus control is contained on the floating window; if the user clicks the attention control, the user can pay attention to the shop of the merchant A and receive the red packet or the coupon issued by the merchant A.

Optionally, a control for the red packages or coupons is displayed on a shop page of the merchant a, the merchant a may trigger the control for the red packages or coupons to call out a page of the red packages or coupons, fill information such as the number of the red packages or coupons to be issued on the page, and then click a confirmation control on the page to submit a request for the red packages or coupons to the server. After receiving the request, the server side can generate a first link for the merchant A according to the information of the red packet or the coupon, wherein the first link points to a shop home page of the merchant A, and the first link comprises a focus control. For the details of the distribution of the red pack or the coupon and the picking up of the red pack or the coupon, the same or similar embodiments can be referred to, and the details are not repeated herein.

Exemplary scenario for posting a comment + Rebate pack or coupon:

for another example, the merchant a may use a red pack or a coupon in combination with the evaluation operation in order to increase the number of user evaluations of the product. The method comprises the steps that a merchant A firstly determines information of a red packet or a coupon to be issued, then a first link is generated according to the information of the red packet or the coupon to be issued, the first link points to a commodity evaluation page of the merchant A, and the first link comprises an evaluation control; and then the first link is shared in the friend circle, the microblog and/or the known account number of the user, or the first link can be shared in friends of the user, old users of shops and the like. Seeing the user of the first link, if triggering the first link, entering a commodity evaluation page of a merchant A, popping up a floating window of a red-collar packet or a coupon on the commodity evaluation page, and containing an evaluation control on the floating window; if the user clicks the evaluation control, a commodity selection list can be popped up, the user can select the commodity to be evaluated, after the user selects the commodity to be evaluated, the user can enter an evaluation detail page of the commodity, and after the user fills in the evaluation on the evaluation detail page and submits the evaluation, the red packet or the coupon issued by the merchant A can be received.

Of course, the merchant a may also pull the user evaluation number for a specific item B, for example, the item B may be a newly placed item, or an item with a relatively low sales volume, or an item with less interest. For the information, the merchant A firstly determines the information of the red packet or the coupon to be issued, and then generates a first link according to the information of the red packet or the coupon to be issued, wherein the first link points to an evaluation detail page of the commodity B, and the first link comprises an evaluation control; and then the first link is shared in the friend circle, the microblog and/or the known account number of the user, or the first link can be shared in friends of the user, old users of shops and the like. A user seeing the first link can enter an evaluation detail page of the commodity B if the first link is triggered, a floating window of a red-collar packet or a coupon can pop up on the evaluation detail page, and an evaluation control is contained on the floating window; if the user clicks the evaluation control, an input box can be popped up, and after the user fills in the evaluation and submits the evaluation, the red packet or the coupon issued by the merchant A can be received.

Optionally, the evaluation control may also bind preset evaluation content in advance, and after the user clicks the evaluation control, the evaluation may be completed directly, and the red packet or the coupon issued by the merchant a is picked up. Further optionally, preset evaluation content may also be displayed in a floating window for a user to view and determine whether to perform evaluation.

Exemplary scenario for browsing merchandise + red pack or coupon:

for example, the merchant a may increase the exposure rate of the product C in order to advertise the product C, and may use a method of combining a red package or a coupon with a browsing operation. The merchant A firstly determines information of the red packet or the coupon to be issued, and then generates a first link according to the information of the red packet or the coupon to be issued, wherein the first link points to a detail page of the commodity C, and the first link comprises a browsing control; and then the first link is shared in the friend circle, the microblog and/or the known account number of the user, or the first link can be shared in friends of the user, old users of shops and the like. A user seeing the first link can enter a detail page of the commodity C if the first link is triggered, a floating window of a red-collar packet or a coupon can pop up on the detail page of the commodity C, and a browsing control is contained on the floating window; if the user clicks the browse control, the details of the commodity C can be browsed, and the red packet or the coupon issued by the merchant A can be picked up.

In the above exemplary embodiment, the red packet or the coupon is given as an example for description, but besides the red packet and the coupon, the resource that can be issued by the merchant may also be some other resource information, for example, some user right of the user in the store, or network traffic, or a membership card or a telephone fee of some video playing APPs, and the like, and the resource information can be flexibly set according to the type of the resource supported by the application and the type of the resource that can be provided by the merchant.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 71a to 71d may be device a; for another example, the execution subject of

steps

71a and 72a may be device a, and the execution subject of steps 73a and 74a may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 71a, 72a, etc., are merely used for distinguishing various operations, and the sequence numbers themselves do not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Fig. 8a is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application. The computer apparatus as shown in fig. 8a comprises: memory 81a, processor 82a and display 83 a.

And a display 83a for displaying a page pointed to by the first link, the first link being shared by the first user.

The memory 81a is used for storing a computer program and may be configured to store other various data to support operations on the computer device. Examples of such data include instructions for any application or method operating on the computer device, contact data, phonebook data, messages, pictures, videos, and the like.

A processor 82a, coupled to the memory 81a, for executing the computer program in the memory 81a for: responding to the operation of a second user on a trigger control on the page, and determining that the second user has an appointed behavior on the first user; acquiring the resource shared by the first user for the second user; wherein the trigger control corresponds to the specified behavior.

In an alternative embodiment, the processor 82a is further configured to: before responding to the triggering operation of a second user on a first control on a page, judging whether the second user meets the condition that the first user has a specified behavior; if yes, displaying a trigger control on the page through the display 83 a; if not, the first prompt message is displayed on the page through the display 83a to prompt the second user that the condition for the first user to perform the specified action is not satisfied.

Optionally, one way for the display 83a to display the trigger control or the first prompt message on the page includes: and displaying a first floating window on the page, wherein the first floating window comprises a trigger control or first prompt information.

Further optionally, the processor 82a, when determining whether the second user meets the condition for the first user to perform the specified behavior, is specifically configured to perform at least one of the following determination operations:

judging whether the frequency of the second user to generate the specified behavior for the first user in the current activity period reaches the upper limit;

judging whether the current round of sharing activities participated by the first user is finished or not, wherein each round of sharing activities comprises at least one activity time interval;

if the judgment result of any judgment operation is yes, determining that the second user does not meet the condition of the first user for generating the specified behavior;

and if the judgment result of the at least one judgment operation is negative, determining that the second user meets the condition of the first user for generating the specified behavior.

In an optional embodiment, when determining that the second user has the specified behavior with respect to the first user, the processor 82a is specifically configured to: responding to the triggering operation of the second user on the triggering control, and sending an information processing request to the server side to request the server side to perform processing operation related to the specified behavior for the first user; and under the condition that a processing success message returned by the server is received, determining that the second user has a specified behavior on the first user.

In an alternative embodiment, the processor 82a is further configured to: before acquiring the resource shared by the first user for the second user, judging whether the resource shared by the first user is still in an acquirable state; and if the resource shared by the first user is still in the acquirable state, acquiring the resource shared by the first user for the second user.

Further, the processor 82a is further configured to: under the condition that the resource shared by the first user is in the unavailable state, displaying second prompt information on the page to prompt whether the second user continues to perform specified behaviors on the first user; and under the condition that the resources shared by the first user are in the unavailable state, responding to the operation of the second user on the trigger control, and determining that the second user has the specified behavior on the first user.

Further, when determining whether the resource shared by the first user is still in the acquirable state, the processor 82a is specifically configured to perform at least one of the following determination operations:

judging whether the resource shared by the first user is expired;

judging whether all the resources shared by the first user are picked up;

if the judgment result of any judgment operation is yes, determining that the resource shared by the first user is in an unavailable state;

and if the judgment result of the at least one judgment operation is negative, determining that the resource shared by the first user is still in an acquirable state.

In an alternative embodiment, as shown in fig. 8a, the computer device of this embodiment further includes: a communication component 84 a. Based on this, when the processor 82a acquires the resource shared by the first user for the second user, it is specifically configured to: sending a resource acquisition request to the server through the communication component 84a, so that the server determines whether the second user can acquire resources from the resources shared by the first user and returns a target resource component acquired by the second user under the condition that the second user can acquire the resources; and receiving the target resource component acquired by the second user and returned by the server through the communication component 84a, and displaying the target resource component on the page.

Further, the processor 82a is further configured to: displaying a view control on the page pointed to by the first link via the display 83 a; and in response to the triggering operation of the viewing control by the second user, displaying the resource sharing details of the first user via the display 83 a.

When the display 83a displays the target resource component and the view control, it is specifically configured to: and displaying a second floating window on the page, wherein the second floating window comprises the target resource component and the viewing control.

In an alternative embodiment, the resources shared by the first user are stored in an intermediate account. The second user acquires the target resource component, and the resource corresponding to the target resource component is still stored in the intermediate account and is not transferred to the resource account of the second user. Based thereon, the processor 82a is further configured to: detecting whether a second user initiates a resource transfer behavior in a first application; if the second user is detected to initiate the resource transfer behavior in the first application, determining a third-party resource account related to the resource transfer behavior, wherein the first application is an application to which the page belongs; and sending a resource transfer request to the server through the communication component 84a to request the server to transfer the resource corresponding to the target resource component from the intermediate account to the third-party resource account.

In an alternative embodiment, the specified behavior comprises at least one of: power-assisted behavior, browsing behavior, payment-for-help behavior, and comment behavior.

In an optional embodiment, the page pointed to by the first link is a PK page in a PK activity, or a cut price page in a cut price activity, or a product detail page in a group purchase activity, or a resource pickup page in a resource pickup activity.

In an alternative embodiment, the first link may be a password-panning, one-dimensional code, two-dimensional code, or URL link.

Further, as shown in fig. 8a, the computer apparatus further includes: power components 85a, audio components 86a, and the like. Only some of the components are schematically shown in fig. 8a, and it is not meant that the computer device comprises only the components shown in fig. 8 a. The computer device of the embodiment can be implemented as a desktop computer, a notebook computer, a smart phone, an IOT device, or other terminal devices. Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps in the method embodiment shown in fig. 7b when executed.

Fig. 8b is a schematic structural diagram of another computer device according to an exemplary embodiment of the present application. The computer apparatus of fig. 8b comprises: memory 81b, processor 82b, display 83b and communication component 84 b.

The display 83b is configured to display a sharing page according to the sharing request of the first user.

The memory 81b is used for storing a computer program and may be configured to store other various data to support operations on the computer device. Examples of such data include instructions for any application or method operating on the computer device, contact data, phonebook data, messages, pictures, videos, and the like.

A processor 82b, coupled to the memory 81b, for executing the computer program in the memory 81b for: acquiring resource information to be shared by the first user based on the sharing page;

generating a first link required by resource sharing based on the resource information, wherein a page pointed by the first link contains a trigger control, and the trigger control corresponds to a specified behavior;

and sending the first link to a second user through a communication component 84b, so that the second user performs a specified action on the first user through the trigger control and acquires the resource shared by the first user.

In an optional embodiment, when acquiring the resource information to be shared by the first user, the processor 82b is specifically configured to: responding to the input operation of a first user on the sharing page, and acquiring the total amount of resources and the number of resources input by the first user as the resource information.

Further, when the processor 82b generates the first link required for resource sharing, it is specifically configured to: transferring corresponding resources from the resource account of the first user to an intermediate account according to the total amount of the resources; dividing the total resource amount into N acquirable resource components according to the number of the resources, wherein N represents the number of the resources and is a positive integer; generating the first link based on the trigger control and the N acquirable resource components.

In an optional embodiment, when obtaining the resource information to be shared by the first user, the processor 82b is further configured to: and acquiring the guidance text information input by the first user as the resource information, wherein the guidance text information embodies the incidence relation between resource sharing and appointed behavior. Based on this, the processor 82b, when generating the first link, is specifically configured to: generating the first link according to the trigger control, the N acquirable resource components and the guide text information, wherein the page pointed to by the first link also comprises the guide text information.

In an optional embodiment, the processor 82b is further configured to, in the process of obtaining resource information to be shared by the first user based on the sharing page, perform the following determination operation:

judging whether the guide text information input by the first user meets the set expression specification;

if the judgment result of the judgment operation is yes, acquiring the total amount of the resources, the number of the resources and the guidance text information input by the first user as the resource information.

In an alternative embodiment, the processor 82b is further configured to: before acquiring the resource information to be shared by the first user, executing at least one of the following judgment operations:

judging whether the total times of sharing resources in the current round of sharing activities of the first user reaches the upper limit of the times allowed by the current round of sharing activities, wherein each round of sharing activities comprises at least one activity time interval;

judging whether the number of times of the first user sharing the resources in the current activity period reaches the upper limit of the number of times allowed in the current activity period;

and if the judgment result of the at least one judgment operation is negative, allowing the first user to execute input operation on the sharing page.

In an alternative embodiment, the processor 82b is further configured to: after the first link is sent to the second user, the sharing page is displayed through a display 83b according to a sharing request initiated by the first user again, and the sharing page displays information of resources shared by the first user and a sharing control; in response to the triggering operation of the sharing control by the first user, the communication component 84b continues to send the first link to a third user, where the third user is any user who has not acquired the resource shared by the first user.

In an alternative embodiment, the processor 82b is further configured to: the communication component 84b receives a resource acquisition request of the second user; determining whether the N acquirable resource components remain; if yes, determining a target resource component acquired by the second user from the remaining resource components, and returning the target resource component to the second user; and recording resource acquisition flow information, wherein the resource acquisition flow information comprises information of the target resource component acquired by the second user.

In an alternative embodiment, the processor 82b is further configured to: the communication component 84b receives a resource transfer request of the second user, the resource transfer request including a third party resource account to which the resource transfer action relates; and acquiring running information according to the resources, and transferring the resources corresponding to the target resource components from the intermediate account to the third-party resource account.

Optionally, the processor 82b is further configured to: before receiving the resource transfer request of the second user, judging whether the validity period of the resource corresponding to the target resource component is finished; and if so, returning the resources corresponding to the target resource components from the intermediate account to the resource account of the first user.

Further, the processor 82b is further configured to: after transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account, recording resource transfer flow information, wherein the resource transfer flow information includes information related to the transfer of the resource corresponding to the target resource component from the intermediate account to the third-party resource account.

Further, as shown in fig. 8b, the computer apparatus further includes: power supply components 85b, audio components 86b, and the like. Only some of the components are schematically shown in fig. 8b, and it is not meant that the computer device comprises only the components shown in fig. 8 b. The computer device of this embodiment may be implemented as a terminal device such as a desktop computer, a notebook computer, a smart phone, or an IOT device, or may be a server device such as a conventional server, a cloud server, or a server array. Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps in the method embodiment shown in fig. 7a when executed.

In addition to the computer device, an embodiment of the present application further provides a server device, where the server device includes: a memory, a processor, and a communications component; the memory is used for storing a computer program; a processor is coupled to the memory for executing the computer program in the memory for:

receiving a resource sharing request sent by a first terminal device through a communication component, wherein the request carries resource information to be shared by a first user, and the resource information comprises: the total amount of resources and the number of resources;

transferring corresponding resources from the resource account of the first user to the intermediate account according to the total amount of the resources;

dividing the total resource amount into N acquirable resource components according to the number of the resources, wherein N represents the number of the resources and is a positive integer;

a first link is generated based on the trigger control and the N available resource components.

Optionally, the processor is further configured to: receiving a resource acquisition request of a second user through a communication component; judging whether the N obtainable resource components remain; if yes, determining a target resource component acquired by the second user from the remaining resource components, and returning the target resource component to the second user; and recording resource acquisition flow information, wherein the resource acquisition flow information comprises information of the target resource component acquired by the second user.

Further, the processor is further configured to: receiving a resource transfer request of a second user through the communication component, wherein the resource transfer request comprises a third party resource account related to the resource transfer behavior; and acquiring the running information according to the resources, and transferring the resources corresponding to the target resource components from the intermediate account to the third-party resource account.

Further, the processor is further configured to: before receiving a resource transfer request of a second user, judging whether the validity period of the resource corresponding to the target resource component is finished; and if so, returning the resources corresponding to the target resource components to the resource account of the first user from the intermediate account.

Further, the processor is further configured to: after the resources corresponding to the target resource components are transferred from the intermediate account to the third-party resource account, resource transfer flow information is recorded, wherein the resource transfer flow information comprises relevant information of the resources corresponding to the target resource components transferred from the intermediate account to the third-party resource account.

The memories of fig. 8a and 8b may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The communication components of fig. 8a and 8b described above are configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may further include a Near Field Communication (NFC) module, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and the like.

The displays in fig. 8a and 8b described above include screens, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply components of fig. 8a and 8b described above provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio components of fig. 8a and 8b described above may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data processing method, comprising:

displaying a page pointed by a first link, wherein the first link is shared by a first user;

responding to the operation of a second user on a trigger control on the page, and determining that the second user performs specified behaviors on the first user; and

acquiring the resource shared by the first user for the second user; wherein the trigger control corresponds to the specified behavior.

2. The method of claim 1, prior to responding to a triggering operation of a first control on the page by a second user, further comprising:

judging whether the second user meets the condition that the first user has the specified behavior;

and if so, displaying the trigger control on the page.

3. The method of claim 2, further comprising:

and if not, displaying first prompt information on the page to prompt the second user that the second user does not meet the condition of the specified behavior of the first user.

4. The method of claim 3, wherein displaying the trigger control or the first prompt on the page comprises:

and displaying a first floating window on the page, wherein the first floating window comprises the trigger control or first prompt information.

5. The method of claim 2, wherein determining whether the second user satisfies a condition for a specified behavior to occur for the first user comprises: performing at least one of the following determination operations:

judging whether the frequency of the second user to generate the specified behavior for the first user in the current activity period reaches an upper limit;

judging whether the second user has already performed specified behaviors on the first user in the current activity period;

and if the judgment result of the at least one judgment operation is negative, determining that the second user meets the condition that the first user has the appointed behavior.

6. The method of claim 1, wherein determining that the second user has performed the specified action with respect to the first user in response to the second user operating the on-page trigger control comprises:

responding to the triggering operation of a second user on the triggering control, and sending an information processing request to a server to request the server to perform processing operation related to the specified behavior for the first user; and

and if a processing success message returned by the server is received, determining that the second user performs specified behaviors on the first user.

7. The method of claim 1, further comprising, prior to obtaining the resource shared by the first user for the second user:

judging whether the resource shared by the first user is still in an acquirable state;

and if the resource shared by the first user is still in an acquirable state, acquiring the resource shared by the first user for the second user.

8. The method of claim 7, wherein determining whether the resource shared by the first user is still available comprises: performing at least one of the following determination operations:

judging whether the resources shared by the first user are expired;

judging whether the resources shared by the first user are not left;

9. The method of claim 7, further comprising:

if the resource shared by the first user is in the unavailable state, displaying second prompt information on the page to prompt the second user whether to continue to perform specified actions on the first user; and

and under the condition that the resources shared by the first user are in the unavailable state, responding to the operation of the second user on the trigger control, and determining that the second user has the appointed behavior on the first user.

10. The method according to any one of claims 1-9, wherein obtaining the resource shared by the first user for the second user comprises:

sending a resource acquisition request to a server, so that the server determines whether the second user can acquire resources from the resources shared by the first user and returns a target resource component acquired by the second user under the condition that the second user can acquire the resources;

and receiving a target resource component which is returned by the server and acquired by the second user, and displaying the target resource component on the page.

11. The method of claim 10, further comprising:

displaying a viewing control on the page; and

and responding to the triggering operation of the second user on the viewing control, and displaying the resource sharing details of the first user.

12. The method of claim 11, wherein displaying the target resource component and the view control on the page comprises:

and displaying a second floating window on the page, wherein the second floating window comprises the target resource component and the viewing control.

13. The method of claim 10, wherein the resources shared by the first user are stored in an intermediate account; after displaying the target resource component, further comprising:

if the second user is detected to initiate the resource transfer behavior in the first application, determining a third-party resource account related to the resource transfer behavior, wherein the first application is an application to which the page belongs;

and sending a resource transfer request to the server to request the server to transfer the resource corresponding to the target resource component from the intermediate account to the third-party resource account.

14. The method of any of claims 1-9, wherein the specified behavior comprises at least one of: power-assisted behavior, browsing behavior, payment-for-help behavior, and comment behavior.

15. The method of claim 14, wherein the page is a PK page in a PK campaign, or a cut price page in a cut price campaign, or a merchandise detail page in a group purchase campaign, or a resource pickup page in a resource pickup campaign.

16. The method of any of claims 1-9, wherein the first link is a pan password, two-dimensional code, or URL link.

17. A data processing method, comprising:

displaying a sharing page according to a sharing request of a first user;

acquiring resource information to be shared by the first user based on the sharing page;

and sending the first link to a second user so that the second user performs specified actions on the first user through the trigger control and acquires the resources shared by the first user.

18. The method according to claim 17, wherein obtaining resource information to be shared by the first user based on the sharing page includes:

responding to the input operation of a first user on the sharing page, and acquiring the total amount of resources and the number of resources input by the first user as the resource information.

19. The method of claim 18, wherein generating the first link required for resource sharing based on the resource information comprises:

transferring corresponding resources from the resource account of the first user to an intermediate account according to the total amount of the resources;

generating the first link based on the trigger control and the N acquirable resource components.

20. The method of claim 19, wherein obtaining resource information to be shared by the first user based on the sharing page further comprises: acquiring guidance text information input by the first user as the resource information, wherein the guidance text information embodies an incidence relation between resource sharing and occurrence of specified behaviors;

said generating said first link from said trigger control and said N acquirable resource components comprises: generating the first link according to the trigger control, the N acquirable resource components and the guide text information, wherein the page pointed to by the first link also comprises the guide text information.

21. The method according to claim 20, wherein in the process of obtaining resource information to be shared by the first user based on the sharing page, the method further includes the following determining operation:

22. The method according to claim 21, further comprising, before obtaining resource information to be shared by the first user based on the sharing page:

23. The method of any of claims 17-22, further comprising, after transmitting the first link to a second user:

displaying the sharing page according to the sharing request initiated by the first user again, wherein the sharing page displays the information of the resources shared by the first user and a sharing control;

and responding to the triggering operation of the first user on the sharing control, and continuously sending the first link to a third user, wherein the third user is any user who does not acquire the resource shared by the first user.

24. The method of any one of claims 19-22, further comprising:

receiving a resource acquisition request of the second user;

determining whether the N acquirable resource components remain;

if yes, determining a target resource component acquired by the second user from the remaining resource components, and returning the target resource component to the second user; and

recording resource acquisition flow information, wherein the resource acquisition flow information comprises information of the target resource component acquired by the second user.

25. The method of claim 24, further comprising:

receiving a resource transfer request of the second user, wherein the resource transfer request comprises a third-party resource account related to a resource transfer behavior;

and acquiring running information according to the resources, and transferring the resources corresponding to the target resource components from the intermediate account to the third-party resource account.

26. The method of claim 25, further comprising, prior to receiving the resource transfer request of the second user:

judging whether the validity period of the resource corresponding to the target resource component is finished or not;

and if so, returning the resources corresponding to the target resource components from the intermediate account to the resource account of the first user.

27. The method of claim 25, further comprising, after transferring the resource corresponding to the target resource component from the intermediate account to the third party resource account:

recording resource transfer flow information, wherein the resource transfer flow information comprises relevant information of transferring the resource corresponding to the target resource component from the intermediate account to the third-party resource account.

28. A method of assisting a force, comprising:

displaying a first link shared by a first user;

responding to the click operation of a second user on the first link, and displaying a red packet getting page pointed by the first link;

responding to the operation of the second user on the power-assisted control on the red envelope getting page, performing power assistance on the first user, and obtaining the red envelope shared by the first user for the second user.

29. A method of assisting a force, comprising:

displaying a red envelope sharing page according to a power-assisted request of a first user;

acquiring the red envelope information to be shared by the first user based on the red envelope sharing page;

generating a first link required for sharing the red envelope based on the red envelope information, wherein a red envelope getting page pointed by the first link comprises a power-assisted control;

and sending the first link to a second user so that the second user can assist the first user through the assistance control and obtain the red envelope shared by the first user.

30. A computer device, comprising: a memory, a processor, and a display;

the display is used for displaying a page pointed by a first link, and the first link is shared by a first user;

the memory for storing a computer program;

the processor, coupled with the memory, to execute the computer program to:

31. A computer device, comprising: a memory, a processor, and a display;

the display is used for displaying a sharing page according to a sharing request of a first user;

the memory for storing a computer program;

the processor, coupled with the memory, to execute the computer program to:

32. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 29.