Resource transfer method, apparatus, system, electronic device, and storage medium

Abstract

The application provides a resource transfer method, device and system, electronic equipment and storage medium, and belongs to the technical field of Internet. The method comprises the following steps: receiving a first resource transfer request sent by an intermediate server, the first resource transfer request being sent by any third-party server associated with the intermediate server, the first resource transfer request carrying a first user identifier registered by the third-party server and resource transfer data; querying a second user identifier associated with the first user identifier according to an association relationship; and transferring resources from a resource account of the second user identifier to a resource account of the intermediate server according to the resource transfer data, the intermediate server being configured to transfer resources from the resource account of the intermediate server to a resource account of the third-party server. The above method provides a cascading interaction mode, that is, even if the third-party server does not establish an association with the application server, the function of proxy resource transfer can be realized through the intermediate server, and the application range of the scheme is wide.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a resource transfer method, apparatus, system, electronic device, and storage medium. Background Technology

[0002] With the development and advancement of internet technology, the ways to pay various living expenses have undergone tremendous changes. For example, electricity, water, and gas bills have changed from being paid offline to being paid through apps.

[0003] Furthermore, users can enable the automatic payment function within the application. Third-party entities associated with the application, such as power companies and water companies, can automatically deduct fees from the user's account without requiring the user to perform the payment action, thus avoiding the negative impact of forgetting to pay and greatly facilitating people's lives.

[0004] However, the above method only applies to third-party objects associated with the application, and not to third-party objects not associated with the application, thus limiting its application scope. Summary of the Invention

[0005] This application provides a resource transfer method, apparatus, system, electronic device, and storage medium, which have a wide range of applications and support the function of transferring resources on behalf of third-party objects not associated with the application. The technical solution is as follows:

[0006] On the one hand, a resource transfer method is provided, the method comprising:

[0007] The system receives a first-generation resource transfer request sent by an intermediate server. The first-generation resource transfer request is sent by any third-party server associated with the intermediate server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data.

[0008] Based on the established association, query the second user identifier associated with the first user identifier. The association includes the association between a third-party user identifier registered on any third-party server and a local user identifier registered on this end. The association indicates that the local user identifier has enabled the proxy resource transfer function for the third-party user identifier.

[0009] Based on the resource transfer data, resources are transferred from the resource account of the second user identifier to the resource account of the intermediate server, and the intermediate server is used to transfer the resources from the resource account of the intermediate server to the resource account of the third-party server.

[0010] In one possible implementation, prior to the activation request for the resource transfer function sent by the receiving terminal, the method further includes:

[0011] Obtain the third-party object identifier of at least one third-party server associated with the intermediate server;

[0012] The terminal sends at least one third-party object identifier to the terminal, which displays the at least one third-party object identifier. In response to a selection operation of any third-party object identifier, the terminal obtains the first user identifier corresponding to the third-party object identifier and sends the activation request.

[0013] In another possible implementation, the association also includes resource transfer conditions for the third-party user identifier, wherein transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data includes:

[0014] In response to the resource transfer data satisfying the resource transfer conditions of the first user identifier, resources are transferred from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data.

[0015] In another possible implementation, after transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes:

[0016] A resource transfer notification message is sent to the intermediate server. The resource transfer notification message includes the first user identifier and the resource transfer data. The resource transfer notification message is used to notify the intermediate server to transfer the resource from the intermediate server's resource account to the third-party server's resource account according to the first user identifier and the resource transfer data.

[0017] In another possible implementation, before transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes:

[0018] Send a first prompt message to the terminal that is logged in with the second user identifier. The first prompt message is used to prompt the terminal to transfer resources on behalf of the first user identifier.

[0019] In another possible implementation, after transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes:

[0020] A second prompt message is sent to the terminal that logged in with the second user identifier. The second prompt message is used to indicate that the resource transfer on behalf of the first user identifier has been completed.

[0021] In another possible implementation, after establishing the association between the first user identifier and the second user identifier, the method further includes:

[0022] A third notification message is sent to the terminal, which indicates that the resource transfer function has been successfully activated.

[0023] In another possible implementation, after establishing the association between the first user identifier, the second user identifier, and the resource transfer conditions, the method further includes:

[0024] A fourth notification message is sent to the intermediate server. The fourth notification message carries the first user identifier and the resource transfer conditions, and is used to indicate that the proxy resource transfer function for the first user identifier has been successfully activated.

[0025] In another possible implementation, the application server includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, wherein the sub-application runs within the parent application;

[0026] The first application server is configured to receive the first generation resource transfer request, query the second user identifier associated with the first user identifier according to the association relationship, and send a second generation resource transfer request to the second application server. The second generation resource transfer request carries the resource transfer data and the second user identifier.

[0027] The second application server is used to receive the second generation resource transfer request and, based on the resource transfer data, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server.

[0028] On the other hand, another resource transfer method is provided, the method comprising:

[0029] Receive a first-generation resource transfer request sent by an associated third-party server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data.

[0030] It has been confirmed that the resource transfer function for the first user identifier has been enabled;

[0031] Send a first generation resource transfer request to the associated application server. The first generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user ID associated with the first user ID to the resource account of the local end.

[0032] In another possible implementation, before receiving the fourth prompt message sent by the application server, the method further includes:

[0033] Receive a third-party object identifier sent by at least one associated third-party server;

[0034] The application server sends at least one received third-party object identifier to the application server, the application server sends the at least one third-party object identifier to the terminal, the terminal displays the at least one third-party object identifier, and in response to a selection operation of any third-party object identifier, obtains the first user identifier corresponding to the third-party object identifier and enables the proxy resource transfer function for the first user identifier.

[0035] On the other hand, a method for activating the resource transfer function is provided, the method comprising:

[0036] The first application interface of the target application is displayed. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered on the third-party server to which the third-party object identifier belongs. The third-party object identifier is associated with an intermediate object identifier, and the intermediate object identifier is associated with the target application.

[0037] In response to the triggering operation of the activation request button, a second application interface is displayed, which includes a resource account of a second user identifier logged into the target application and an activation confirmation button;

[0038] In response to the activation confirmation button, the resource transfer function between the second user identifier and the first user identifier is activated.

[0039] In one possible implementation, before receiving the prompt message when the resource transfer function is not activated, the method further includes:

[0040] The display interface includes at least one third-party object identifier, and the at least one third-party object identifier is associated with the intermediate object identifier;

[0041] In response to the selection of any third-party object identifier, a settings interface is displayed, the settings interface including the selected third-party object identifier and an input field;

[0042] Obtain the first user identifier entered in the input field;

[0043] Store the first user identifier in correspondence with the third-party object identifier.

[0044] In another possible implementation, the target application is a parent application, and child applications run within the parent application; the first application interface is the interface of the child application. The step of activating the resource transfer function from the second user identifier to the first user identifier in response to the triggering operation of the activation confirmation button includes:

[0045] In response to the activation confirmation button, the parent application is invoked, and an activation request for the resource transfer function is sent to the second application server corresponding to the parent application. The activation request carries the second user identifier and the first user identifier. The second application server is used to send the activation request to the first application server corresponding to the child application. The first application server is used to establish the association between the first user identifier and the second user identifier.

[0046] In another possible implementation, the second application interface further includes a condition setting button, and the method further includes:

[0047] In response to the triggering operation of the condition setting button, the input resource transfer conditions are obtained, and the activation request also carries the resource transfer conditions. The first application server is used to establish the association relationship between the first user identifier, the second user identifier and the resource transfer conditions.

[0048] In another possible implementation, the method further includes:

[0049] Receive the prompt message sent by the second application server;

[0050] The notification message is displayed through the notification interface of the parent application; or,

[0051] The notification message is displayed through the notification interface of the sub-application.

[0052] On the other hand, a resource transfer device is provided, the device comprising:

[0053] The resource transfer request receiving module is used to receive a first-generation resource transfer request sent by an intermediate server. The first-generation resource transfer request is sent by any third-party server associated with the intermediate server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data.

[0054] The user identifier query module is used to query the second user identifier associated with the first user identifier based on the established association relationship. The association relationship includes the association relationship between a third-party user identifier registered on any third-party server and a local user identifier registered on this end. The association relationship indicates that the local user identifier has enabled the proxy resource transfer function for the third-party user identifier.

[0055] The resource transfer module is used to transfer resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data. The intermediate server is used to transfer the resources from the resource account of the intermediate server to the resource account of the third-party server.

[0056] In one possible implementation, the device further includes:

[0057] An activation request receiving module is used to receive an activation request for the resource transfer function sent by the terminal. The activation request carries the second user identifier and the first user identifier of the terminal login.

[0058] The association establishment module is used to establish the association between the first user identifier and the second user identifier.

[0059] In another possible implementation, the association establishment module is further configured to establish an association between the first user identifier, the second user identifier, and the resource transfer conditions.

[0060] In another possible implementation, the device further includes:

[0061] The object identifier acquisition module is used to acquire the third-party object identifier of at least one third-party server associated with the intermediate server.

[0062] An object identifier sending module is used to send at least one acquired third-party object identifier to the terminal. The terminal is used to display the at least one third-party object identifier, and in response to a selection operation of any third-party object identifier, obtain the first user identifier corresponding to the third-party object identifier and send the activation request.

[0063] In another possible implementation, the association also includes resource transfer conditions identified by the third-party user.

[0064] The resource transfer module is used to, in response to the resource transfer data satisfying the resource transfer conditions of the first user identifier, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data.

[0065] In another possible implementation, the device further includes:

[0066] The notification message sending module is used to send a resource transfer notification message to the intermediate server. The resource transfer notification message includes the first user identifier and the resource transfer data. The resource transfer notification message is used to notify the intermediate server to transfer the resource from the intermediate server's resource account to the third-party server's resource account according to the first user identifier and the resource transfer data.

[0067] In another possible implementation, the device further includes:

[0068] The first prompt message sending module is used to send a first prompt message to the terminal that is logged in with the second user identifier. The first prompt message is used to prompt the first user identifier to transfer resources on their behalf.

[0069] In another possible implementation, the device further includes:

[0070] The second prompt message sending module is used to send a second prompt message to the terminal that is logged in with the second user identifier. The second prompt message is used to prompt that the resource transfer on behalf of the first user identifier has been completed.

[0071] In another possible implementation, the device further includes:

[0072] The third prompt message sending module is used to send a third prompt message to the terminal, which is used to indicate that the resource transfer function has been successfully activated.

[0073] In another possible implementation, the device further includes:

[0074] The fourth prompt message sending module is used to send a fourth prompt message to the intermediate server. The fourth prompt message carries the first user identifier and the resource transfer conditions, and is used to indicate that the proxy resource transfer function for the first user identifier has been successfully activated.

[0075] On the other hand, another resource transfer device is provided, the device comprising:

[0076] The resource transfer request receiving module is used to receive a first-generation resource transfer request sent by an associated third-party server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data.

[0077] The transfer function activation confirmation module is used to determine that the proxy resource transfer function for the first user identifier has been activated;

[0078] The resource transfer request sending module is used to send the first generation resource transfer request to the associated application server. The first generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user identifier associated with the first user identifier to the resource account of the local end.

[0079] In one possible implementation, the device further includes:

[0080] The notification message receiving module is used to receive a resource transfer notification message sent by the application server, wherein the resource transfer notification message includes the first user identifier and the resource transfer data;

[0081] The resource transfer module is used to transfer the resource from the local resource account to the resource account of the third-party server based on the first user identifier and the resource transfer data.

[0082] In another possible implementation, the device further includes:

[0083] The prompt message receiving module is used to receive a fourth prompt message sent by the application server. The fourth prompt message carries the first user identifier and the resource transfer conditions, and is used to prompt that the proxy resource transfer function for the first user identifier has been successfully activated.

[0084] The user identifier marking module is used to mark the first user identifier as a user identifier that has enabled the resource transfer function;

[0085] The prompt message sending module is used to send the fourth prompt message to the third-party server, prompting the third-party server to send a resource transfer request on behalf of the server if the resource transfer conditions are met.

[0086] In another possible implementation, the device further includes:

[0087] The object identifier receiving module is used to receive a third-party object identifier sent by at least one associated third-party server;

[0088] An object identifier sending module is used to send at least one received third-party object identifier to the application server. The application server is used to send the at least one third-party object identifier to the terminal. The terminal is used to display the at least one third-party object identifier. In response to a selection operation on any third-party object identifier, the terminal obtains the first user identifier corresponding to the third-party object identifier and enables the proxy resource transfer function for the first user identifier.

[0089] On the other hand, a device for activating a resource transfer function is provided, the device comprising:

[0090] The application interface display module is used to display the first application interface of the target application. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered on the third-party server to which the third-party object identifier belongs. The third-party object identifier is associated with an intermediate object identifier, and the intermediate object identifier is associated with the target application.

[0091] The application interface display module is also used to display a second application interface in response to the triggering operation of the activation request button. The second application interface includes a resource account of the second user identifier logged into the target application and an activation confirmation button.

[0092] The transfer function activation module is used to activate the resource transfer function between the second user identifier and the first user identifier in response to the activation confirmation button.

[0093] In one possible implementation, the device further includes:

[0094] The first prompt information receiving module is used to receive prompt information when the resource transfer function is not enabled. The prompt information is used to indicate that the second user identifier has completed the transfer of resources from the first user identifier to the third-party object identifier.

[0095] The application interface display module is used to display the first application interface according to the prompt information.

[0096] In another possible implementation, the application interface display module is further configured to display an identifier display interface, the identifier display interface including at least one third-party object identifier, and the at least one third-party object identifier being associated with the intermediate object identifier; in response to a selection operation of any third-party object identifier, a settings interface is displayed, the settings interface including the selected third-party object identifier and an input field; the device further includes:

[0097] An identifier storage module is used to obtain the first user identifier entered in the input field and store the first user identifier in correspondence with the third-party object identifier.

[0098] In another possible implementation, the application interface display module is used to display an identifier display interface, the identifier display interface including at least one third-party object identifier, and the at least one third-party object identifier is associated with the intermediate object identifier; in response to a selection operation of any third-party object identifier, the first application interface is displayed, the first application interface including the selected third-party object identifier and an input field; the first user identifier entered in the input field is obtained, and the activation request button is displayed on the first application interface.

[0099] In another possible implementation, the target application is a parent application, and a child application runs in the parent application, with the first application interface being the interface of the child application;

[0100] The transfer function activation module is used to respond to the activation confirmation button, call the parent application, and send an activation request for the resource transfer function to the second application server corresponding to the parent application. The activation request carries the second user identifier and the first user identifier. The second application server is used to send the activation request to the first application server corresponding to the child application. The first application server is used to establish the association between the first user identifier and the second user identifier.

[0101] In another possible implementation, the second application interface further includes a condition setting button, and the device further includes:

[0102] The resource transfer condition acquisition module is used to acquire the input resource transfer conditions in response to the trigger operation of the condition setting button. The activation request also carries the resource transfer conditions. The first application server is used to establish the association relationship between the first user identifier, the second user identifier and the resource transfer conditions.

[0103] In another possible implementation, the device further includes:

[0104] The second prompt information receiving module is used to receive prompt information sent by the second application server;

[0105] The application interface display module is also used to display the prompt information through the notification interface of the parent application; or, through the notification interface of the sub-application.

[0106] On the other hand, a resource transfer system is provided, which includes: a third-party server, an application server, and an intermediate server, wherein the third-party server and the intermediate server are associated, and the application server and the intermediate server are associated.

[0107] The third-party server is used to send a first-generation resource transfer request to the intermediate server. The first-generation resource transfer request carries a first user identifier and resource transfer data registered on the third-party server.

[0108] The intermediate server is configured to receive the first proxy resource transfer request sent by the third-party server, determine that the proxy resource transfer function for the first user identifier has been enabled, and send the first proxy resource transfer request to the application server.

[0109] The application server is configured to receive the first proxy resource transfer request; query the second user identifier associated with the first user identifier according to the established association relationship, the association relationship including the association relationship between a third-party user identifier registered on any third-party server and a user identifier registered on the application server, the association relationship indicating that the user identifier on the application server has enabled the proxy resource transfer function for the third-party user identifier; and transfer resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data.

[0110] The intermediate server is also used to transfer resources from the intermediate server's resource account to the third-party server's resource account.

[0111] In one possible implementation, the application server includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, wherein the sub-application runs within the parent application;

[0112] The first application server is configured to receive the first generation resource transfer request, query the second user identifier associated with the first user identifier according to the association relationship, and send a second generation resource transfer request to the second application server. The second generation resource transfer request carries the resource transfer data and the second user identifier.

[0113] The second application server is used to receive the second generation resource transfer request and, based on the resource transfer data, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server.

[0114] In another possible implementation, the system further includes a terminal;

[0115] The application server is further configured to send a first prompt message to the terminal logged in to the second user identifier before transferring resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data. The first prompt message is used to prompt the terminal to transfer resources on behalf of the first user identifier.

[0116] The terminal is also configured to receive the first prompt information and display the first prompt information;

[0117] The application server is further configured to send a second prompt message to the terminal after transferring resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data. The second prompt message is used to prompt that the resource transfer has been completed on behalf of the first user identifier.

[0118] On the other hand, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction, which is loaded and executed by the processor to perform the operations performed in the resource transfer method or the activation method that substitutes for resource transfer function in any of the above possible implementations.

[0119] In another aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored in the computer-readable storage medium, the instruction being loaded and executed by a processor to implement the operation performed by the electronic device in the resource transfer method or the activation method that substitutes for the resource transfer function in any of the above possible implementations.

[0120] The beneficial effects of the technical solutions provided in this application are:

[0121] In this embodiment, a cascading interaction method is provided. This method allows resource transfer to be performed even if the third-party server is not associated with the application server. The intermediate server receives the resource transfer request from a third-party server that is associated with the intermediate server but not with the application server. The intermediate server then forwards the resource transfer request to the application server. The application server transfers resources from the resource account of the second user ID associated with the first user ID to the intermediate server, and the intermediate server then forwards the resources to the resource account of the third-party server. This expands the application scope of the solution. Attached Figure Description

[0122] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0123] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application;

[0124] Figure 2 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0125] Figure 3 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0126] Figure 4 This is a flowchart of a method for enabling a resource transfer function provided in an embodiment of this application;

[0127] Figure 5This is a flowchart of a method for enabling a resource transfer function provided in an embodiment of this application;

[0128] Figure 6 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0129] Figure 7 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0130] Figure 8 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0131] Figure 9 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0132] Figure 10 This is a schematic diagram of the process for enabling a resource transfer function provided in an embodiment of this application;

[0133] Figure 11 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0134] Figure 12 This is a schematic diagram of an application interface provided in an embodiment of this application;

[0135] Figure 13 This is a schematic diagram of a resource transfer process provided in an embodiment of this application;

[0136] Figure 14 This is a schematic diagram of an information flow and resource flow provided in an embodiment of this application;

[0137] Figure 15 This is a block diagram of a resource transfer device provided in an embodiment of this application;

[0138] Figure 16 This is a block diagram of a resource transfer device provided in an embodiment of this application;

[0139] Figure 17 This is a block diagram of a resource transfer device provided in an embodiment of this application;

[0140] Figure 18 This is a block diagram of a resource transfer device provided in an embodiment of this application;

[0141] Figure 19 This is a block diagram of an activation device for resource transfer functionality provided in an embodiment of this application;

[0142] Figure 20 This is a block diagram of an activation device for resource transfer functionality provided in an embodiment of this application;

[0143] Figure 21 This is a block diagram of a resource transfer system provided in an embodiment of this application;

[0144] Figure 22 This is a block diagram of a resource transfer system provided in an embodiment of this application;

[0145] Figure 23 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0146] Figure 24 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0147] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0148] It is understood that the terms "each," "multiple," and "any," etc., used in this application, mean "multiple" includes two or more, "each" refers to each of the corresponding multiple servers, and "any" refers to any one of the corresponding multiple servers. For example, multiple servers include 10 servers, and "each server" refers to each of these 10 servers, while "any server" refers to any one of the 10 servers.

[0149] First, the terms used in this application will be introduced as follows:

[0150] 1. Third-party objects, third-party object identifiers, and third-party servers:

[0151] A third-party object can be an organization that provides third-party services, such as an electricity company, gas company, water company, or telecom operator. A third-party object has a third-party object identifier to distinguish different third-party objects. For example, the third-party object identifier can be the company name, company number, etc. A third-party server is a server configured for a third-party object to provide services to that third-party object.

[0152] 2. Intermediate object, intermediate object identifier, intermediate server:

[0153] An object that acts as a bridge between a third-party object and the target application is called an intermediary object. An intermediary object has an intermediary object identifier to identify its identity; for example, the intermediary object identifier could be the name of an organization. An intermediary server is a server configured for the intermediary object, used to provide services to it.

[0154] The aforementioned third-party objects and intermediate objects can sign an agreement to establish a relationship, thus establishing a relationship between the third-party server and the intermediate server, and enabling interaction between the third-party server and the intermediate server.

[0155] 3. First User Identifier and Second User Identifier:

[0156] Both the first user identifier and the second user identifier are used to identify a user. The difference lies in that the first user identifier is registered on the third-party object's third-party server, while the second user identifier is registered on the target application's application server. This means a user can be either a user of the target application or a user of the services provided by the third-party object. By establishing a link between the first and second user identifiers, the resource account of the second user identifier can be used to pay the fees for third-party services for the first user identifier.

[0157] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application. See also... Figure 1 The implementation environment includes a terminal 101, an application server 102, an intermediate server 103, and at least one third-party server 104. Figure 1 (Taking three third-party servers 104 as an example). Terminal 101, application server 102, intermediate server 103, and at least one third-party server 104 are connected via a wireless or wired network. Furthermore, a target application provided by application server 102 can be installed on terminal 101, and the user corresponding to terminal 101 can use the target application to perform functions such as data transmission and message interaction.

[0158] Terminal 101 can be a computer, mobile phone, tablet computer or other terminal. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0159] The target application can be any application installed on terminal 101; furthermore, the target application can be a target application in the operating system of terminal 101, or it can be a target application provided by a third party. For example, the target application can be a shopping application, a financial application, or a social application, etc. The application server 102 can be the backend server corresponding to the target application. Accordingly, the application server 102 can be a shopping server, a financial server, a social application server, etc.

[0160] Intermediate server 103 is a server associated with application server 102, and third-party server 104 is a server associated with intermediate server 103. Application server 102, intermediate server 103, and third-party server 104 can all be independent servers or server clusters composed of multiple servers.

[0161] Terminal 101 can utilize the target application to execute the above-mentioned resource transfer function activation method to activate the proxy resource transfer function for third-party user identifiers registered on the third-party server. After the proxy resource transfer function is activated, the third-party server 104 can send a proxy resource transfer request to the intermediate server 103. The intermediate server 103 forwards the proxy resource transfer request to the application server 102. Based on the proxy resource transfer request, the application server 102 transfers resources from the resource account of the user identifier registered on the application server 102 associated with the third-party user identifier to the resource account of the intermediate server 103. The intermediate server 103 then forwards the resources to the resource account of the third-party server 104.

[0162] The target application can also be a parent application, and the parent application runs child applications. Accordingly, the application server 102 can include a first application server corresponding to the child application and a second application server corresponding to the parent application. The first application server can be used to query the user identifier registered in the second application server that is associated with the third-party user identifier. The second application server can be used to transfer resources from the resource account of the user identifier to the resource account of the intermediate server 103.

[0163] The solution in this application can be applied in various scenarios. For example, in the scenario of paying living expenses, users can activate the resource transfer function for electricity, water, gas, and telephone bills using the above method. After successful activation, third-party entities such as power companies, water companies, gas companies, and telecom operators that are not associated with the target application can directly transfer resources from the user's resource account without the user needing to perform any payment operations.

[0164] Figure 2 This is a flowchart of a resource transfer method provided in an embodiment of this application. See also... Figure 2 This embodiment includes:

[0165] 201. Receive the first generation resource transfer request sent by the intermediate server. The first generation resource transfer request is sent by any third-party server associated with the intermediate server. The first generation resource transfer request carries the first user identifier registered with the third-party server and resource transfer data.

[0166] 202. Query the second user identifier associated with the first user identifier based on the established association relationship. The association relationship includes the association relationship between the third-party user identifier registered on any third-party server and the local user identifier registered on this end. The association relationship indicates that the local user identifier has enabled the function of transferring resources on behalf of the third-party user identifier.

[0167] 203. Based on the resource transfer data, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server. The intermediate server is used to transfer resources from the resource account of the intermediate server to the resource account of the third-party server.

[0168] The above method receives resource transfer requests from third-party servers that are associated with the intermediate server but not with the application server. The intermediate server then forwards the resource transfer requests to the application server. The application server transfers resources from the resource account of a second user associated with the first user ID to the intermediate server, and the intermediate server forwards the resources to the resource account of the third-party server. This provides a cascading interaction method, which can realize the function of resource transfer even if the third-party server is not associated with the application server, thus expanding the application scope of the solution.

[0169] Figure 3 This is a flowchart of a resource transfer method provided in an embodiment of this application. See also... Figure 3 This embodiment includes:

[0170] 301. Receive the first generation resource transfer request sent by the associated third-party server. The first generation resource transfer request carries the first user identifier registered with the third-party server and resource transfer data.

[0171] 302. Confirm that the resource transfer function for the first user identifier has been enabled.

[0172] 303. Send a first-generation resource transfer request to the associated application server. The first-generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user ID associated with the first user ID to the resource account of the local end.

[0173] The above method receives resource transfer requests from third-party servers associated with the intermediate server but not associated with the application server. The intermediate server then forwards these requests to the application server associated with it. This provides a cascading interaction method, allowing resource transfer functionality to be implemented even if the third-party server is not associated with the application server, thus expanding the application scope of the solution. Furthermore, the intermediate server only sends the resource transfer request to the application server after confirming that the user ID corresponding to the request has enabled the resource transfer function. This prevents third-party servers from maliciously deducting fees from users who have not enabled the resource transfer function, improving the security of resource transfer.

[0174] Figure 4 This is a flowchart of a method for enabling a resource transfer function provided in an embodiment of this application.

[0175] See Figure 4 This embodiment includes:

[0176] 401. Display the first application interface of the target application. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered on the third-party server to which the third-party object identifier belongs. The third-party object identifier is associated with an intermediate object identifier, and the intermediate object identifier is associated with the target application.

[0177] 402. In response to the triggering operation of the activation request button, a second application interface is displayed, which includes a resource account identified by the second user of the target application and an activation confirmation button.

[0178] 403. In response to the triggering operation of the activation confirmation button, activate the resource transfer function from the second user ID to the first user ID.

[0179] The above-mentioned method for enabling the resource transfer function is applicable to the first user identifier corresponding to a third-party object that is not associated with the target application. Enabling the resource transfer function expands the application scenarios of the solution and can enable the transfer of water, gas, electricity and other fees, making it convenient for users to pay their living expenses and improving user stickiness.

[0180] Figure 5 This is a flowchart illustrating a method for activating a resource transfer proxy function according to an embodiment of this application. This embodiment describes the interaction process between the terminal, application server, intermediate server, and third-party server during the activation of the resource transfer proxy function. See also... Figure 5 This embodiment includes:

[0181] 500. The third-party server sends the third-party object identifier to the associated intermediate server.

[0182] This application's embodiments involve terminals, application servers, intermediate servers, and third-party servers:

[0183] The application server can be the backend server of a target application installed on the terminal. This target application can be any application, and it must have resource transfer functionality. Accordingly, the application server can be used to provide resource transfer services. For example, if the target application is a social application, the application server can be the backend server of that social application. In this application, the terminal logs into the application server based on its user identifier, and the terminal acts as the resource transferor.

[0184] An intermediate server is a server associated with the application server. It can provide services such as resource storage and transfer. For example, an intermediate server could be a server corresponding to a payment institution such as a bank. In this application, the intermediate server acts as a relay for resources.

[0185] A third-party server is a server associated with an intermediate server. It is the server corresponding to a third-party entity that provides living resources or specific living services. For example, if the third-party entity is a gas company, then the third-party server is the server corresponding to the gas company. In this application, the third-party server is the recipient of the resources.

[0186] The third-party object identifier is the identifier of the third-party object corresponding to the third-party server, used to distinguish different third-party objects. This third-party object identifier can be a name, trademark, number, or other identifier; this application does not impose any restrictions on this.

[0187] The association between an intermediate server and a third-party server refers to a relationship between the intermediate server and the third-party server. The association process involves the third-party server sending information about its corresponding third-party object and verification information to the intermediate server. Once the intermediate server verifies the information about the third-party object, it establishes the association with the third-party server. The association between an intermediate server and an application server refers to a relationship between the intermediate server and the application server. The association process is similar to the one described above. It should be noted that the above association processes are merely illustrative and this application does not impose any limitations on them.

[0188] The application server can be associated with one or more intermediate servers, and each intermediate server can also be associated with one or more third-party servers. When the application server is associated with multiple intermediate servers, and each intermediate server is associated with multiple third-party servers, each third-party server can send its corresponding third-party object identifier to the intermediate server it is associated with. After receiving the multiple third-party object identifiers sent by the multiple third-party servers associated with it, each intermediate server sends the multiple third-party object identifiers to the application server it is associated with. Subsequently, the application server can receive the multiple third-party object identifiers sent by the intermediate servers.

[0189] In one possible implementation, the third-party server also sends at least one first user identifier corresponding to the third-party object identifier to the associated intermediate server, and the intermediate server is also used to send the received at least one first user identifier to the associated application server.

[0190] The first user identifier is an identifier registered by the user on a third-party server to distinguish different users. The first user identifier can be a name, number, etc. In specific application scenarios, the first user identifier can be a water bill account number, water bill account name, gas bill account number, gas account name, mobile phone number, etc. This application does not impose any restrictions on this. Users can pay fees to third-party entities based on this first user identifier.

[0191] The third-party server may send at least one first user identifier corresponding to the third-party object identifier to the intermediate server at the same time as sending the third-party object identifier, or the third-party server may send at least one first user identifier corresponding to the third-party object identifier after sending the third-party object identifier to the intermediate server. This application does not impose any restrictions on this.

[0192] 501. The intermediate server receives a third-party object identifier sent by at least one associated third-party server and sends the received third-party object identifier to the application server.

[0193] The intermediate server may also store the received third-party object identifiers. This storage may be done before, after, or simultaneously with sending the received third-party object identifiers to the application server. This application does not impose any restrictions on this.

[0194] In one possible implementation, the intermediate server also receives at least one first user identifier corresponding to a third-party object identifier sent by at least one associated third-party server, and stores the third-party object identifier and the corresponding first user identifier. Then, when it receives a successful activation message for the proxy resource transfer function from the application server, it can directly mark the stored first user identifier as having activated the proxy resource transfer function.

[0195] 502. The application server obtains the third-party object identifier of at least one third-party server associated with the intermediate server and sends the obtained third-party object identifier to the terminal.

[0196] Before this step, the application server needs to receive at least one third-party object identifier from the intermediate server, store the at least one third-party object identifier, and when it receives a request from the terminal to retrieve the at least one third-party object identifier, it retrieves the stored at least one third-party object identifier and sends the at least one third-party object identifier to the terminal. Alternatively, the application server may also directly send the at least one third-party object identifier to the terminal when it receives the at least one third-party object identifier; this application does not impose any restrictions on this.

[0197] 503. The terminal displays the first application interface of the target application, which includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button.

[0198] The first user identifier is registered on the third-party server to which the third-party object identifier belongs, and is used to represent the user's identity. The third-party object identifier is associated with the intermediate object identifier, and the intermediate object identifier is associated with the target application. The intermediate object identifier refers to the identifier of the intermediate object corresponding to the intermediate server.

[0199] For example, the intermediate object can be an institution with resource management authority, such as a bank, and the third-party object can be a merchant that establishes a relationship with the bank, in which case the merchant can be called a sub-merchant of the bank.

[0200] Associating a third-party object identifier with an intermediate object identifier means that the third-party server corresponding to the third-party object identifier is associated with the intermediate server corresponding to the intermediate object identifier. Associating an intermediate object identifier with a target application means that the intermediate server corresponding to the intermediate object identifier is associated with the application server corresponding to the target application.

[0201] The first application interface can be an interface for the target application to initiate resource transfer, a notification interface for successful resource transfer, an interface for setting the association between the first user identifier and the third-party user identifier, or other interfaces of the target application. This application does not limit this.

[0202] The "Activate Request" button is used to request the activation of the resource transfer proxy function for the first user identifier. This function automatically transfers resources to the second user identifier instead of requiring the user to initiate the transfer on the terminal. Once the resource transfer proxy function for the first user identifier is activated, the terminal can complete the resource transfer for that user identifier without needing to initiate a request.

[0203] Depending on whether the second user identifier has replaced the first user identifier in transferring resources to a third-party object identifier, this step is divided into the following two cases:

[0204] The first scenario involves the second user identifier transferring resources to a third-party object identifier on behalf of the first user identifier. This step is implemented as follows: The terminal receives a notification message when the resource transfer function is not enabled. The notification message indicates that the resource transfer on behalf of the first user identifier has been completed, and the terminal displays the first application interface based on the notification message.

[0205] The second user identifier is the user identifier of the currently logged-in target application. This user identifier can be a user account registered on the application server corresponding to the target application, and can be used by the application server to distinguish different users based on the second user identifier.

[0206] The second notification message received by the terminal is sent to the terminal by the application server, and is used to notify the terminal that the resource transfer based on the first user identifier to the third-party object identifier is complete. This resource transfer is initiated by the terminal itself, even before the first user identifier has enabled the resource transfer proxy function. The notification message may include the third-party object identifier, the first user identifier, the resource account corresponding to the second user identifier, etc. Of course, the notification message may also include the time of the resource transfer, the value of the transferred resources, etc., which are not limited in this application.

[0207] The terminal can generate a first application interface based on the prompt information. The first application interface may include a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. This activation request button is used to request activation of the resource transfer function for the first user identifier upon triggering. The first application interface may also include information such as the current remaining resource value and the current resource payable value corresponding to the first user identifier; this application does not limit this. The third-party object identifier, the first user identifier, the current remaining resource value, and the current resource payable value can be displayed at the top of the first application interface, while the activation request button can be displayed in the middle, at the bottom, or in another location. The activation request button can be highlighted with color, and a prompt message can be displayed on the activation request button, such as "Activate automatic deduction, safe and worry-free," etc. Of course, the prompt message can also be other than that; this application does not limit this.

[0208] It should be noted that before the terminal receives the prompt message when the resource transfer function is not enabled, the method further includes: the terminal displaying an identifier display interface, which includes at least one third-party object identifier, and at least one third-party object identifier is associated with an intermediate object identifier; in response to the selection operation of any third-party object identifier, the terminal displays a settings interface, which includes the selected third-party object identifier and an input field; the terminal obtains the first user identifier entered in the input field; and stores the first user identifier and the third-party object identifier accordingly.

[0209] Before displaying the identifier on the terminal, the terminal must first obtain at least one third-party object identifier. In one possible implementation, the terminal can obtain the at least one third-party object identifier locally, which is received from the application server in advance and stored on the terminal. In another possible implementation, the terminal can obtain the at least one third-party object identifier from the server. This can be achieved by the terminal responding to the request to obtain the third-party object identifier by sending a request to the application server and receiving at least one third-party object identifier from the server.

[0210] It should be noted that if the terminal obtains at least one third-party object identifier from the application server, the terminal can store the obtained identifier locally. Then, before displaying the identifier display interface, the terminal can directly obtain at least one third-party object identifier from its local storage. That is, steps 501 and 502 only need to be executed once. After the terminal stores at least one third-party object identifier, the activation method for the resource transfer function can begin from step 503.

[0211] Another point to note is that the settings interface can also include a resource transfer request button. Upon triggering this button, the terminal can display a resource transfer interface. This interface may include a third-party object identifier, a first user identifier, resource accounts corresponding to the second user identifier, and input fields for resource values. The terminal can then retrieve the resource value from the input field and send a resource transfer request to the application server based on the first user identifier, the resource accounts corresponding to the second user identifier, and the resource value. Using this method, after setting the first user identifier corresponding to the third-party object identifier, the user can directly initiate a resource transfer, resulting in high efficiency.

[0212] The second scenario involves the second user identifier not having replaced the first user identifier in transferring resources to a third-party object identifier, and the terminal not storing the first user identifier corresponding to the third user identifier. This step is implemented as follows: the terminal displays an identifier display interface, which includes at least one third-party object identifier, and at least one third-party object identifier is associated with an intermediate object identifier; in response to a selection operation on any third-party object identifier, the terminal displays a first application interface, which includes the selected third-party object identifier and an input field; the terminal obtains the first user identifier entered in the input field and displays an activation request button on the first application interface.

[0213] Before this step, the terminal needs to obtain the identifier of at least one third-party object. The method for the terminal to obtain the identifier of at least one third-party object has been introduced in the first method of displaying the first application interface, and will not be repeated here.

[0214] The above method is applicable when the user has not yet set a first user identifier corresponding to the third user identifier in the target application. By directly displaying the user identifier input field and the activation button for the proxy resource transfer function in the first application interface, the user can directly activate the proxy resource function after entering the first user identifier, which is highly efficient.

[0215] 504. In response to the triggering operation of the activation request button, the terminal displays a second application interface, which includes a resource account identified by the second user of the target application and an activation confirmation button.

[0216] The second application interface can be the activation interface for the resource transfer function of the target application or other interfaces, and this application does not impose any restrictions on it.

[0217] A resource account is an account used to store virtual resources, including a user's bank card account or a payment account authorized by the target application, such as the target application's cash balance. The same secondary user identifier can correspond to multiple resource accounts of different types, or multiple resource accounts of the same type. For example, a user can bind multiple bank cards to their secondary user identifier through the target application's payment function, authorizing the application server to transfer resources from the target application's cash balance or from the bound bank card accounts.

[0218] Users can trigger the activation request button in the first application interface to activate the proxy resource transfer function for the first user identifier in the first application interface. In response to the activation request button, the terminal displays a second application interface. The second application interface displays key information for activating the proxy resource transfer function for the first user identifier. After verifying the information in the second application interface, the user can click the activation confirmation button to activate the proxy resource transfer function for the first user identifier. For example, the key information for the proxy resource transfer function may include the first user identifier, the corresponding third-party object identifier, the second user identifier, the resource account of the second user identifier, and the resource transfer conditions, etc.

[0219] The second application interface is also used to modify key information for enabling the resource transfer function for the first user identifier. For example, the second application interface also includes a condition setting button, and the terminal responds to the triggering operation of the condition setting button to obtain the input resource transfer conditions.

[0220] Resource transfer conditions are the conditions that must be met for a resource transfer to be performed on behalf of the first user identifier. These conditions include the timing of the resource transfer, the method of resource transfer, and the value of the transferred resources. The timing of the transfer can be a time condition, such as initiating a resource transfer every Monday or on the 10th of each month. It can also be a resource value condition, such as initiating a resource transfer when the first user identifier's resource account on the third-party server has a remaining resource value of 10 yuan. The method of resource transfer can be based on the priority of the resource account corresponding to the second user identifier. For example, resources can be transferred first from the bank card account corresponding to the second user identifier; if the remaining resource value in that bank card account is insufficient, then resources can be transferred from the payment account of the target application corresponding to the second user identifier. The value of the transferred resources is the amount transferred each time the resource transfer is performed, for example, transferring 20 yuan from the second user identifier's resource account each time. By displaying a condition setting button on the second application interface, users can freely set the conditions for the resource transfer, improving the flexibility of the resource transfer function.

[0221] In one possible implementation, the terminal responds to the triggering operation of the condition setting button by acquiring the input resource transfer condition in the following way: Upon triggering the condition setting button, the terminal displays a pop-up window on the second application interface. The pop-up window includes at least one condition selection button and a corresponding transfer condition. The terminal acquires the transfer condition corresponding to the triggered condition selection button and uses the acquired at least one transfer condition as the resource transfer condition. The transfer condition includes the timing of initiating the resource transfer on behalf of the first user identifier, the method of resource transfer, and the value of the resource to be transferred.

[0222] refer to Figure 6 , Figure 6 This is a schematic diagram of the first application interface. The top of the interface displays the first user identifier (payer name and payer number), as well as a third-party object identifier (payer unit). The center of the interface displays a button to request the activation of the resource transfer function, accompanied by the messages "Activate automatic deduction, safe and worry-free" and "Activate Now." This button, when triggered, requests the activation of the resource transfer function for the first user identifier. The interface also includes a resource value input field and a resource transfer request button. This button displays the message "Pay Now," and when triggered, it requests a resource transfer based on the resource value entered in the input field.

[0223] refer to Figure 7 , Figure 7 This is a schematic diagram of the notification interface for successful resource transfer. The interface displays the message "Payment Successful" at the top and a button to activate the resource transfer function in the middle. The activation request button displays the messages "Automatic Deduction" and "Activate Now".

[0224] refer to Figure 8 , Figure 8 This is a schematic diagram of the second application interface, which is displayed by the terminal in response to the activation request button in the first application interface or the resource transfer success notification interface. The second application interface includes a first user identifier (payment number), a second user identifier (paying user), a third-party object identifier (paying unit), and the resource account (deduction method) corresponding to the second user identifier. It also includes an explanation of the resource transfer function (service content). A confirmation button for activating the resource transfer function is displayed at the bottom of the second application interface, displaying the message "Activate Automatic Deduction." This confirmation button, when triggered, activates the resource transfer function for the first user identifier.

[0225] 505. In response to the activation confirmation button, the terminal sends an activation request to the application server. The activation request carries the second user identifier and the first user identifier.

[0226] In one possible implementation, the activation request also carries resource transfer conditions.

[0227] In one possible implementation, the target application is the parent application, and child applications run within the parent application. The first application interface is the interface of the child applications. Accordingly, this step is implemented as follows: In response to the triggering operation of the activation confirmation button, the terminal calls the parent application and sends an activation request for the resource transfer function to the second application server corresponding to the parent application. The activation request carries the second user identifier and the first user identifier.

[0228] The parent application is the application that runs directly on the operating system. The terminal runs an operating system, and the parent application runs within that operating system. The operating system is a computer program that manages and controls the terminal's hardware and software resources; it is the most basic system software that runs directly on the terminal's bare metal, and applications require the support of the operating system to run. The parent application can be a social media application, email application, or game application, etc. The child application is an application that can run within the environment provided by the parent application. A child application can be a utility payment application, a shopping application, or a game application, etc. For example, a child application can be a mini-program, such as a utility payment mini-program.

[0229] 506. The application server receives a request from the terminal to activate the resource transfer function. The activation request carries the second user identifier and the first user identifier of the terminal login.

[0230] After receiving an activation request carrying a second user identifier and a first user identifier, the application server establishes an association between the first user identifier and the second user identifier and stores this association in the application server. Subsequently, when the application server receives a resource transfer request carrying a first user identifier, it can query the stored association to find the second user identifier associated with the first user identifier, and then perform the resource transfer based on the second user identifier.

[0231] In one possible implementation, the activation request also carries resource transfer conditions based on a first user identifier. Correspondingly, an association is established between the first user identifier and a second user identifier, including establishing an association between the first user identifier, the second user identifier, and the resource transfer conditions. Subsequently, when the application server receives a resource transfer request carrying the first user identifier, it can determine whether the resource transfer request meets the associated resource transfer conditions. If the resource transfer conditions are met, the resource transfer is performed based on the second user identifier.

[0232] It should be noted that when the application server includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, step 506 is implemented as follows: the second application server receives a request from the terminal to enable the resource transfer function, and the enabling request carries the second user identifier and the first user identifier of the terminal login.

[0233] After receiving the activation request for the resource transfer function, the second application server sends the activation request to the first application server corresponding to the sub-application. Then, the first application server receives the activation request, establishes an association between the first user identifier and the second user identifier, and stores the association. Of course, the activation request may also include resource transfer conditions. Accordingly, the first application server establishes an association between the first user identifier and the second user identifier, including: the first application server establishes an association between the first user identifier, the second user identifier, and the resource transfer conditions.

[0234] 507. The application server sends a third notification message to the terminal, which is used to indicate that the resource transfer function has been successfully activated.

[0235] The third prompt information may include the first user identifier, the resource account corresponding to the second user identifier, and the resource transfer conditions of the first user identifier, etc., and this application does not impose any restrictions on this.

[0236] After establishing the association between the first user identifier and the second user identifier, the application server can send a third notification message to the terminal to indicate that the resource transfer function on behalf of the first user identifier by the second user identifier has been successfully activated.

[0237] 508. The terminal receives the third prompt information sent by the application server and displays the third prompt information through the notification interface of the target application.

[0238] The notification interface can be an aggregated interface for notification messages from the target application, used to display notification messages sent to the second user identifier. Displaying a third prompt through the target application's notification interface provides feedback to the user's activation process, resulting in a good interactive experience.

[0239] In one possible implementation, the target application is the parent application, and a child application runs within the parent application. Accordingly, the third prompt information can be displayed through the notification interface of the target application in the following ways: the terminal displays the third prompt information through the notification interface of the parent application; or, the third prompt information is displayed through the notification interface of the child application.

[0240] The notification interface of the parent application can be a public message aggregation interface of the parent application. Correspondingly, the terminal displays prompt information through the notification interface of the parent application in the following ways: the terminal displays a public identifier in the parent application; in response to a trigger operation on the public identifier, the public message aggregation interface is displayed, which includes the third prompt information. The public identifier can be a public account, service account, etc., that manages notification messages sent to the second user identifier. Alternatively, the terminal receives the third prompt information, displays a link to the public message aggregation interface in the parent application, and in response to detecting a trigger operation on the link, displays the public message aggregation interface, which includes the third prompt information.

[0241] For example, after a user follows the official account, the parent application can display a notification message through that official account. The official account can also have template messages. Each time a notification message is displayed, it is added to the template message to form a message that meets the format requirements of the official account and is then displayed in the public message aggregation interface.

[0242] The notification interface of a sub-application can be a service notification interface for the sub-application. Accordingly, the terminal displays the third prompt information through the sub-application's notification interface as follows: the terminal receives the third prompt information, displays a link to the sub-application's service notification interface in the parent application, and displays the service notification interface (including the third prompt information) in response to a trigger operation on the service notification interface. Alternatively, the notification interface of a sub-application can be its message interface. Accordingly, the terminal displays the third prompt information through the sub-application's notification interface as follows: the terminal displays the parent application's interface, which includes a jump button for the sub-application. In response to a trigger operation on the jump button, the terminal displays the sub-application's main interface, which includes a jump button for the message interface. In response to a trigger operation on the jump button, the terminal displays the sub-application's message interface, which includes the third prompt information.

[0243] For example, the third prompt message is a mini-program service notification. When a user interacts with a mini-program, the mini-program pushes a third prompt message to the user through a service notification.

[0244] refer to Figure 9 , Figure 9 This is a schematic diagram of the notification interface of the target application, which includes a message indicating "Activation successful".

[0245] 509. The application server sends a fourth notification message to the intermediate server. The fourth notification message carries the first user identifier and is used to indicate that the resource transfer function for the first user identifier has been successfully activated.

[0246] Optionally, the fourth prompt message may also carry the resource transfer conditions of the first user identifier.

[0247] It should be noted that steps 507 and 509 do not have an execution order requirement. That is, the application server can send notification messages to both the terminal and the intermediate server simultaneously, or it can send the third prompt message to the terminal first and then send the fourth prompt message to the intermediate server, or vice versa. Similarly, steps 508 and 510 also do not have an execution order requirement.

[0248] 510. The intermediate server receives the fourth prompt message sent by the application server and sends the fourth prompt message to the third-party server.

[0249] After receiving the fourth prompt message from the application server, the intermediate server marks the first user identifier as a user identifier for which the resource transfer function has been activated, and sends the fourth prompt message to the third-party server to prompt the third-party server to send a resource transfer request for the first user identifier. In one possible implementation, the fourth prompt message also carries resource transfer conditions; in this case, the intermediate server sends the fourth prompt message to the third-party server to prompt the third-party server to send a resource transfer request if the resource transfer conditions are met.

[0250] The intermediate server pre-stores at least one first user identifier, which can be sent to the intermediate server by a third-party server. After receiving the fourth prompt information, the intermediate server marks the first user identifier as a user identifier that has activated the resource transfer function. Then, when the intermediate server receives a resource transfer request from a third-party server, it can determine whether the first user identifier carried in the resource transfer request has activated the resource transfer function. After confirming that the first user identifier has activated the resource transfer function, the intermediate server sends the resource transfer request to the application server. This can prevent the third-party server from maliciously deducting fees from first users who have not activated the resource transfer function, thereby improving the security of resource transfer.

[0251] After receiving the fourth prompt message, the third-party server can mark the first user identifier carried in the fourth prompt message as having enabled the resource transfer function, and store the resource transfer conditions carried in the fourth prompt message. If the resource transfer conditions are met, the third-party server can send a resource transfer request for the first user identifier to the intermediate server.

[0252] refer to Figure 10 , Figure 10This diagram illustrates the activation process of the resource transfer function. The terminal logs into the parent application using a second user identifier and enters the authorization page of the sub-application. The first application server corresponding to the sub-application requests the resource transfer function and the first user identifier from the terminal. The terminal authorizes the resource transfer function from the second application server. The second application server sends a successful activation message to the first application server, and the first application server sends a successful activation message to the terminal. The first application server synchronizes subscription messages with an intermediate server, and the second application server synchronizes subscription messages with a third-party server. Specifically, subscription message synchronization refers to synchronizing the first user identifier that successfully activated the resource transfer function and the corresponding resource transfer conditions.

[0253] The above-mentioned method for enabling the resource transfer function is applicable to the first user identifier corresponding to a third-party object that is not associated with the target application. Enabling the resource transfer function expands the application scenarios of the solution and can enable the transfer of water, gas, electricity and other fees, making it convenient for users to pay their living expenses and improving user stickiness.

[0254] Figure 11 This is a flowchart illustrating a resource transfer method provided in an embodiment of this application. This embodiment describes the interaction process between a third-party server, an intermediate server, an application server, and a terminal during the resource transfer process. Furthermore, this resource transfer process is executed after the resource transfer function has been enabled for the first user identifier. See also... Figure 11 This embodiment includes:

[0255] 1101. The first generation of resource transfer requests sent by the third-party server to the associated intermediate server carries the first user identifier registered with the third-party server and resource transfer data.

[0256] Among them, resources refer to items that can be owned through the network, including at least one of virtual resources and physical resources. Virtual resources include at least one of account values, virtual avatar products, virtual recharge cards, and virtual currency. Physical resources can be items with a physical form that can be owned by users, such as electricity, gas, water, and communication resources used in daily life.

[0257] Resource transfer data is data related to resource transfer behavior. Resource transfer data may include the third-party object identifier corresponding to the third-party server that initiates the resource transfer, the first user identifier registered on the third-party server, the current remaining resource value of the resource account of the first user identifier, the time of the remaining resource value, and the resource value to be transferred, etc.

[0258] Optionally, the third-party server stores the identifier of the first user who has enabled the resource transfer function and the resource transfer conditions corresponding to the first user identifier. The third-party server can send a resource transfer request to the associated intermediate server when the resource transfer conditions are met.

[0259] 1102. The intermediate server receives the first proxy resource transfer request sent by the associated third-party server and determines that the proxy resource transfer function for the first user identifier has been enabled.

[0260] Optionally, the intermediate server queries the database for the first user identifier. If the first user identifier is a user identifier marked as having enabled the resource transfer function, then it is determined that the resource transfer function for the first user identifier has been enabled. This method is simple and efficient.

[0261] In addition, the intermediate server queries the database for the first user identifier. If the first user identifier is not marked as having enabled the resource transfer function, then it is determined that the resource transfer function for the first user identifier has not been enabled.

[0262] 1103. The intermediate server sends the first generation resource transfer request to the associated application server.

[0263] The intermediate server will only send the first resource transfer request to the application server if it determines that the resource transfer function for the first user identifier is enabled. If the intermediate server determines that the resource transfer function for the first user identifier is not enabled, it will not send the first resource transfer request to the application server. This can prevent third-party servers from maliciously deducting fees from first user identifiers that have not enabled the resource transfer function, thereby improving the security of resource transfer.

[0264] 1104. The application server receives the first generation resource transfer request sent by the intermediate server.

[0265] In one possible implementation, the application server includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, with the sub-application running within the parent application. Accordingly, this step is implemented as follows: the first application server receives a first-generation resource transfer request sent by an intermediate server.

[0266] 1105. The application server queries the second user identifier associated with the first user identifier based on the established association relationship.

[0267] The association relationship includes the association between a third-party user identifier registered on any third-party server and a user identifier registered on the application server. The association relationship indicates that the user identifier registered on the application server has enabled the proxy resource transfer function for the third-party user identifier.

[0268] When the application server includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, this step is implemented as follows: the first application server queries the second user identifier associated with the first user identifier based on the established association relationship.

[0269] Furthermore, after the first application server finds the second user identifier associated with the first user identifier, it sends a second-generation resource transfer request to the second application server. This second-generation resource transfer request carries the second user identifier and resource transfer data.

[0270] 1106. The application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data.

[0271] In one possible implementation, the association also includes resource transfer conditions of a third-party user identifier. Accordingly, the application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data as follows: In response to the resource transfer data satisfying the resource transfer conditions of the first user identifier, the application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data.

[0272] Furthermore, prior to this step, the application server needs to query the resource transfer conditions associated with the first user identifier based on the established relationship. By transferring resources from the resource account of the second user identifier to the resource account of the intermediate server when the resource transfer data meets the resource transfer conditions of the first user identifier, since the resource transfer conditions are set by the user, this proxy resource transfer can meet the user's wishes and improve the security of resource transfer.

[0273] In one possible implementation, before the application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, it must first send a first prompt message to the terminal logged in with the second user identifier. The first prompt message is used to prompt the first user identifier to perform the resource transfer on their behalf.

[0274] The first notification message may include the first user identifier and resource transfer data, and may also include other information; this application does not impose any restrictions on this. Sending this first notification message to the terminal allows users to easily understand the resource dynamics of their resource account, thereby increasing user engagement.

[0275] In one possible implementation, this step is performed as follows: the second application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data.

[0276] Furthermore, before the second application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, it must first receive a second-generation resource transfer request sent by the first application server. This second-generation resource transfer request is sent by the first application server to the second application server after determining that the resource transfer data meets the resource transfer conditions of the first user identifier. That is, before sending the second-generation resource transfer request to the second application server, the first application server not only queries the second user identifier associated with the first user identifier based on the association relationship, but also queries the resource transfer conditions associated with the first user identifier. Then, in response to the resource transfer data meeting the resource transfer conditions of the first user identifier, the first application server sends the second-generation resource transfer request to the second application server.

[0277] 1107. The application server sends a second prompt message to the terminal that logged in with the second user ID. The second prompt message is used to indicate that the resource transfer has been completed on behalf of the first user ID.

[0278] After the application server transfers resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, it sends a second prompt message to the terminal logged in with the second user identifier to indicate that the resource transfer on behalf of the first user identifier has been completed. This allows users to understand the resource status of their resource accounts and can improve user stickiness.

[0279] 1108. The terminal receives the second prompt message sent by the application server and displays the second prompt message through the notification interface of the target application.

[0280] The implementation method of this step is the same as that of step 508, and will not be repeated here.

[0281] refer to Figure 12 , Figure 12 This is a schematic diagram of the notification interface for successful resource transfer. The notification interface includes the value of the transferred resources, the time of the resource transfer, the first user identifier (user number), the resource account (payment method) corresponding to the second user identifier, and an explanation of the resource transfer function (deduction rules), etc.

[0282] 1109. The application server sends a resource transfer notification message to the intermediate server. The resource transfer notification message includes the first user identifier and resource transfer data.

[0283] The resource transfer notification message may also include the resource transfer method, the order number of the resource transfer, etc., and this application does not impose any restrictions on this. The resource transfer notification message is used to notify the intermediate server that the application server has transferred the resources to the intermediate server's resource account.

[0284] It should be noted that there is no requirement for the execution order of steps 1107 and 1109, nor is there a requirement for the execution order of steps 1108 and 1110.

[0285] 1110. The intermediate server receives the resource transfer notification message sent by the application server, and transfers resources from its local resource account to the resource account of the third-party server based on the first user identifier and resource transfer data.

[0286] The intermediate server stores a mapping relationship between third-party object identifiers and first user identifiers. After receiving the resource transfer notification message, the intermediate server queries the third-party object identifier corresponding to the first user identifier based on the stored mapping relationship, and then transfers the resources from the intermediate server's resource account to the resource account of the third-party server of the third-party object identifier.

[0287] The intermediate server can respond to a resource transfer notification message sent by the application server and directly transfer resources from its resource account to the resource account of the third-party server based on the first user identifier and resource transfer data. Alternatively, it can transfer resources from its own resource account to the third-party server's resource account based on preset time conditions, provided those conditions are met. These preset time conditions can be Mondays, the 1st of each month, etc., and this application does not impose any restrictions on this. By transferring resources from its own resource account to the third-party server's resource account according to preset time conditions, the intermediate server can uniformly clear the resource transfer data of multiple first user identifiers corresponding to the third-party server and then uniformly transfer the cleared resources from its own resource account to the third-party server's resource account, thereby reducing the number of resource transfers, improving resource transfer efficiency, and saving service resources.

[0288] 1111. A third-party server receives resources transferred from the resource account of an intermediate server to the resource account of the third-party server.

[0289] It should be noted that, in this application, a monitoring server may also be included between the intermediate server and the application server. The monitoring server records the resources transferred between the intermediate server and the application server. Accordingly, the intermediate server sends a first-generation resource transfer request to the monitoring server, which then forwards the first-generation resource transfer request to the application server. Furthermore, the application server must first transfer its resources to the resource account of the monitoring server, which then forwards the resources to the resource account of the intermediate server. For example, the monitoring server could be a server corresponding to a specific regulatory agency.

[0290] Another point to note is that, in this application, the first application server corresponding to the sub-application is also used to receive the first generation resource transfer request sent by the intermediate server, and to send the first generation resource transfer request to the supervisory server in place of the intermediate server.

[0291] refer to Figure 13 , Figure 13 This is a schematic diagram illustrating the resource transfer process. A third-party server sends a first resource transfer request to an intermediate server. If the intermediate server determines that the first user identifier carried in the first resource transfer request has enabled the resource transfer function, it sends the first resource transfer request to a monitoring server. The monitoring server then sends the first resource transfer request to a first application server. The first application server queries the resource transfer conditions corresponding to the first user identifier. If it determines that the resource transfer data carried in the first resource transfer request meets the conditions, it sends a second resource transfer request to a second application server. The second resource transfer request carries a second user identifier associated with the first user identifier and the resource transfer data. Based on this resource transfer data, the second application server transfers resources from the resource account corresponding to the second user identifier to the resource account of the monitoring server. The monitoring server forwards the resources to the resource account of the intermediate server, and the intermediate server forwards the resources to the resource account of the third-party service. Finally, after transferring resources from the resource account corresponding to the second user identifier to the monitoring server, the second application server sends a resource transfer success message to the terminal.

[0292] refer to Figure 14 , Figure 14 This diagram illustrates the information and resource flow during the resource transfer process. The resource transfer request is sent by a third-party server, passes through an intermediate server, a monitoring server, and a first application server before reaching the second application server. Resources are transferred from the resource account of the second user to the resource account of the monitoring server, from the resource account of the monitoring server to the resource account of the intermediate server, and then from the resource account of the intermediate server to the resource account of the third-party server.

[0293] The above method receives resource transfer requests from third-party servers that are associated with the intermediate server but not with the application server. The intermediate server then forwards the resource transfer requests to the application server. The application server transfers resources from the resource account of a second user associated with the first user ID to the intermediate server, and the intermediate server forwards the resources to the resource account of the third-party server. This provides a cascading interaction method, which can realize the function of resource transfer even if the third-party server is not associated with the application server, thus expanding the application scope of the solution.

[0294] Furthermore, the intermediate server only sends the resource transfer request to the application server after confirming that the user ID corresponding to the resource transfer request has enabled the resource transfer function. This can prevent third-party servers from maliciously deducting fees from users who have not enabled the resource transfer function, thereby improving the security of resource transfer.

[0295] Furthermore, the application server transfers resources from the resource account identified by the second user to the intermediate server only when the resource transfer request meets the resource transfer conditions. Since the resource transfer conditions are set by the user, the resource transfer can meet the user's wishes and ensure the security of the resource transfer.

[0296] Figure 15 This is a block diagram of a resource transfer device provided in an embodiment of this application. See also... Figure 15 This embodiment includes:

[0297] The resource transfer request receiving module 1501 is used to receive a first-generation resource transfer request sent by an intermediate server. The first-generation resource transfer request is sent by any third-party server associated with the intermediate server and carries the first user identifier registered with the third-party server and resource transfer data.

[0298] User ID query module 1502 is used to query the second user ID associated with the first user ID based on the established association relationship. The association relationship includes the association relationship between the third-party user ID registered on any third-party server and the local user ID registered on this end. The association relationship indicates that the local user ID has enabled the function of transferring resources on behalf of the third-party user ID.

[0299] The resource transfer module 1503 is used to transfer resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data. The intermediate server is used to transfer resources from the resource account of the intermediate server to the resource account of the third-party server.

[0300] In one possible implementation, see Figure 16 The device also includes:

[0301] The activation request receiving module 1504 is used to receive the activation request for the resource transfer function sent by the terminal. The activation request carries the second user identifier and the first user identifier of the terminal login.

[0302] The association establishment module 1505 is used to establish the association between the first user identifier and the second user identifier.

[0303] In another possible implementation, the association establishment module 1505 is also used to establish the association between the first user identifier, the second user identifier, and the resource transfer conditions.

[0304] In another possible implementation, see Figure 16 The device also includes:

[0305] The object identifier acquisition module 1506 is used to acquire the third-party object identifier of at least one third-party server associated with the intermediate server.

[0306] The object identifier sending module 1507 is used to send at least one third-party object identifier to the terminal. The terminal is used to display at least one third-party object identifier. In response to the selection operation of any third-party object identifier, the terminal obtains the first user identifier corresponding to the third-party object identifier and sends an activation request.

[0307] In another possible implementation, the association also includes resource transfer conditions of a third-party user identifier. Resource transfer module 1503 is used to transfer resources from the resource account of a second user identifier to the resource account of an intermediate server in response to the resource transfer data satisfying the resource transfer conditions of the first user identifier.

[0308] In another possible implementation, see Figure 16 The device also includes:

[0309] The notification message sending module 1508 is used to send a resource transfer notification message to the intermediate server. The resource transfer notification message includes a first user identifier and resource transfer data. The resource transfer notification message is used to notify the intermediate server to transfer resources from the intermediate server's resource account to the third-party server's resource account according to the first user identifier and resource transfer data.

[0310] In another possible implementation, see Figure 16 The device also includes:

[0311] The first prompt message sending module 1509 is used to send a first prompt message to the terminal that has logged in with the second user identifier. The first prompt message is used to prompt the first user identifier to transfer resources on their behalf.

[0312] In another possible implementation, see Figure 16 The device also includes:

[0313] The second prompt message sending module 1510 is used to send a second prompt message to the terminal that has logged in with the second user identifier. The second prompt message is used to prompt that the resource transfer has been completed on behalf of the first user identifier.

[0314] In another possible implementation, see Figure 16 The device also includes:

[0315] The third prompt message sending module 1511 is used to send a third prompt message to the terminal, which is used to indicate that the resource transfer function has been successfully activated.

[0316] In another possible implementation, see Figure 16 The device also includes:

[0317] The fourth prompt message sending module 1512 is used to send a fourth prompt message to the intermediate server. The fourth prompt message carries the first user identifier and resource transfer conditions, and is used to indicate that the proxy resource transfer function for the first user identifier has been successfully activated.

[0318] This application provides a cascading interaction method by receiving resource transfer requests from third-party servers associated with the intermediate server but not associated with the application server. The intermediate server forwards the resource transfer requests to the application server, and the application server transfers resources from the resource account of a second user associated with a first user ID to the intermediate server. The intermediate server then forwards the resources to the resource account of the third-party server. This allows the resource transfer function to be implemented through the intermediate server even if the third-party server is not associated with the application server, thus expanding the application scope of the solution.

[0319] Figure 17 This is a block diagram of a resource transfer device provided in an embodiment of this application. See also... Figure 17 This embodiment includes:

[0320] The resource transfer request receiving module 1701 is used to receive a first-generation resource transfer request sent by an associated third-party server. The first-generation resource transfer request carries the first user identifier registered with the third-party server and resource transfer data.

[0321] The transfer function activation confirmation module 1702 is used to determine that the proxy resource transfer function for the first user identifier has been activated.

[0322] The resource transfer request sending module 1703 is used to send a first-generation resource transfer request to the associated application server. The first-generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user ID associated with the first user ID to the resource account of the local end.

[0323] In one possible implementation, see Figure 18 The device also includes:

[0324] The notification message receiving module 1704 is used to receive resource transfer notification messages sent by the application server. The resource transfer notification message includes a first user identifier and resource transfer data.

[0325] The resource transfer module 1705 is used to transfer resources from the local resource account to the resource account of a third-party server based on the first user identifier and resource transfer data.

[0326] In another possible implementation, see Figure 18 The device also includes:

[0327] The prompt message receiving module 1706 is used to receive the fourth prompt message sent by the application server. The fourth prompt message carries the first user identifier and resource transfer conditions, and is used to prompt that the proxy resource transfer function for the first user identifier has been successfully activated.

[0328] User identifier marking module 1707 is used to mark the first user identifier as a user identifier that has enabled the resource transfer function;

[0329] The prompt message sending module 1708 is used to send a fourth prompt message to the third-party server, prompting the third-party server to send a resource transfer request on behalf of the server if the resource transfer conditions are met.

[0330] In another possible implementation, see Figure 18 The device also includes:

[0331] The object identifier receiving module 1709 is used to receive a third-party object identifier sent by at least one associated third-party server;

[0332] The object identifier sending module 1710 is used to send at least one received third-party object identifier to the application server. The application server is used to send at least one third-party object identifier to the terminal. The terminal is used to display at least one third-party object identifier. In response to the selection operation of any third-party object identifier, the module obtains the first user identifier corresponding to the third-party object identifier and enables the proxy resource transfer function for the first user identifier.

[0333] This application provides a cascading interaction method by receiving resource transfer requests from third-party servers associated with an intermediate server but not associated with the application server. The intermediate server then forwards these requests to the application server associated with it. This allows resource transfer functionality to be implemented even if the third-party server is not associated with the application server, expanding the application scope of the solution. Furthermore, the intermediate server only sends the resource transfer request to the application server after confirming that the user ID corresponding to the request has enabled resource transfer functionality. This prevents third-party servers from maliciously deducting fees from users who have not enabled resource transfer functionality, improving the security of resource transfer.

[0334] Figure 19 This is a block diagram of an activation device for resource transfer functionality provided in an embodiment of this application. See also... Figure 19 This embodiment includes:

[0335] The application interface display module 1901 is used to display the first application interface of the target application. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered in the third-party server to which the third-party object identifier belongs. The third-party object identifier is associated with an intermediate object identifier, and the intermediate object identifier is associated with the target application.

[0336] The application interface display module 1901 is also used to display a second application interface in response to the triggering operation of the activation request button. The second application interface includes a resource account with a second user identifier for logging into the target application and an activation confirmation button.

[0337] The transfer function activation module 1902 is used to activate the resource transfer function from the second user ID to the first user ID in response to the activation confirmation button.

[0338] In one possible implementation, see Figure 20 The device also includes:

[0339] The first prompt information receiving module 1903 is used to receive prompt information when the resource transfer function is not enabled. The prompt information is used to indicate that the second user identifier has completed the transfer of resources from the first user identifier to the third-party object identifier.

[0340] The application interface display module 1901 is used to display the first application interface according to the prompt information.

[0341] In another possible implementation, the application interface display module 1901 is further configured to display an identifier display interface, which includes at least one third-party object identifier, and the at least one third-party object identifier is associated with an intermediate object identifier; in response to a selection operation on any third-party object identifier, a settings interface is displayed, which includes the selected third-party object identifier and an input field; see also Figure 20 The device also includes:

[0342] The identifier storage module 1904 is used to obtain the first user identifier entered in the input field and store the first user identifier in correspondence with the third-party object identifier.

[0343] In another possible implementation, the application interface display module 1901 is used to display an identifier display interface, which includes at least one third-party object identifier and the at least one third-party object identifier is associated with an intermediate object identifier; in response to a selection operation on any third-party object identifier, a first application interface is displayed, which includes the selected third-party object identifier and an input field; a first user identifier entered in the input field is obtained, and an activation request button is displayed on the first application interface.

[0344] In another possible implementation, the target application is the parent application, and child applications run within the parent application. The interface of the first application is the interface of the child application.

[0345] The transfer function activation module 1902 is used to respond to the trigger operation of the activation confirmation button, call the parent application, and send an activation request for the resource transfer function to the second application server corresponding to the parent application. The activation request carries the second user identifier and the first user identifier. The second application server is used to send the activation request to the first application server corresponding to the child application. The first application server is used to establish the association relationship between the first user identifier and the second user identifier.

[0346] In another possible implementation, the second application interface also includes a condition setting button, see [link to relevant documentation]. Figure 20 The device also includes:

[0347] The resource transfer condition acquisition module 1905 is used to acquire the input resource transfer conditions in response to the trigger operation of the condition setting button. The activation request also carries the resource transfer conditions. The first application server is used to establish the association relationship between the first user identifier, the second user identifier and the resource transfer conditions.

[0348] In another possible implementation, see Figure 20 The device also includes:

[0349] The second prompt information receiving module 1906 is used to receive prompt information sent by the second application server;

[0350] The application interface display module 1901 is also used to display prompt information through the notification interface of the parent application; or, through the notification interface of the child application.

[0351] The aforementioned device for activating the resource transfer function is applicable to first user identifiers corresponding to third-party objects not associated with the target application, thereby expanding the application scenarios of the solution. It can enable resource transfer functions for water, gas, and electricity bills, facilitating users' payment of living expenses and thus increasing user stickiness.

[0352] It should be noted that the resource transfer device provided in the above embodiments is only illustrated by the division of the above functional modules when performing resource transfer, and the device for activating the resource transfer function provided in the above embodiments is only illustrated by the division of the above functional modules when activating the resource transfer function. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the electronic device can be divided into different functional modules to complete all or part of the functions described above. In addition, the resource transfer device and the resource transfer method embodiments provided in the above embodiments belong to the same concept, and the device for activating the resource transfer function and the method embodiments provided in the above embodiments belong to the same concept. The specific implementation process is detailed in the method embodiments and will not be repeated here.

[0353] Figure 21 This is a block diagram of a resource transfer system provided in an embodiment of this application. See also... Figure 21 The system includes: a third-party server 2100, an application server 2101, and an intermediate server 2102. The third-party server 2100 and the intermediate server 2102 are associated, and the application server 2101 and the intermediate server 2102 are associated.

[0354] The third-party server 2100 is used to send a first-generation resource transfer request to the intermediate server 2102. The first-generation resource transfer request carries the first user identifier registered on the third-party server 2100 and resource transfer data.

[0355] Intermediate server 2102 is used to receive the first proxy resource transfer request sent by third-party server 2100, determine that the proxy resource transfer function for the first user identifier has been enabled, and send the first proxy resource transfer request to application server 2101.

[0356] Application server 2101 is used to receive a first proxy resource transfer request; query a second user identifier associated with a first user identifier based on the established association relationship, the association relationship includes the association relationship between a third-party user identifier registered on any third-party server 2100 and a user identifier registered on application server 2101, the association relationship indicates that the user identifier on application server 2101 has enabled the proxy resource transfer function for the third-party user identifier; and transfer resources from the resource account of the second user identifier to the resource account of intermediate server 2102 based on the resource transfer data.

[0357] Intermediate server 2102 is also used to transfer resources from the resource account of intermediate server 2102 to the resource account of third-party server 2100.

[0358] In one possible implementation, see Figure 22 Application server 2101 includes a first application server 21011 corresponding to the sub-application and a second application server 21012 corresponding to the parent application, with the sub-application running within the parent application;

[0359] The first application server 21011 is used to receive the first generation resource transfer request, query the second user identifier associated with the first user identifier according to the association relationship, and send the second generation resource transfer request to the second application server 21012. The second generation resource transfer request carries resource transfer data and the second user identifier.

[0360] The second application server 21012 is used to receive the second generation resource transfer request and, based on the resource transfer data, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server 2102.

[0361] In another possible implementation, see Figure 22 The system also includes terminal 2103;

[0362] Application server 2101 is also used to send a first prompt message to terminal 2103 logged in with second user ID before transferring resources from the resource account of the second user ID to the resource account of intermediate server 2102 according to resource transfer data. The first prompt message is used to prompt the first user ID to transfer resources on behalf of the first user ID.

[0363] Terminal 2103 is also used to receive and display the first prompt information;

[0364] Application server 2101 is also used to send a second prompt message to terminal 2103 after transferring resources from the resource account of the second user identifier to the resource account of intermediate server 2102 according to the resource transfer data. The second prompt message is used to prompt that the resource transfer has been completed on behalf of the first user identifier.

[0365] The resource transfer system in this application receives resource transfer requests from third-party servers associated with the intermediate server but not associated with the application server. The intermediate server forwards these requests to the application server, which then transfers resources from the resource account of a second user associated with a first user ID to the intermediate server. The intermediate server then forwards these resources to the resource account of the third-party server. This provides a cascading interaction method, enabling resource transfer even if the third-party server is not associated with the application server, thus expanding the application scope of the solution. Furthermore, the intermediate server only sends the resource transfer request to the application server if it has confirmed that the user ID corresponding to the request has enabled the resource transfer function. This prevents third-party servers from maliciously deducting fees from users who have not enabled the resource transfer function, improving the security of resource transfer.

[0366] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0367] Figure 23 A structural block diagram of a terminal 2300 provided in an exemplary embodiment of this application is shown. The terminal 2300 may be a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 2300 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0368] Typically, terminal 2300 includes a processor 2301 and a memory 2302.

[0369] Processor 2301 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 2301 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 2301 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 2301 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 2301 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0370] The memory 2302 may include one or more computer-readable storage media, which may be non-transitory. The memory 2302 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 2302 is used to store at least one instruction, which is executed by the processor 2301 to implement the resource transfer method and the activation method for the substitute resource transfer function provided in the method embodiments of this application.

[0371] In some embodiments, the terminal 2300 may also optionally include a peripheral device interface 2303 and at least one peripheral device. The processor 2301, memory 2302, and peripheral device interface 2303 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 2303 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 2304, a touch display screen 2305, a camera assembly 2306, an audio circuit 2307, a positioning assembly 2308, and a power supply 2309.

[0372] Peripheral device interface 2303 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 2301 and memory 2302. In some embodiments, processor 2301, memory 2302 and peripheral device interface 2303 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 2301, memory 2302 and peripheral device interface 2303 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0373] The radio frequency (RF) circuit 2304 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 2304 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 2304 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 2304 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 2304 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 2304 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0374] Display screen 2305 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 2305 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 2301 for processing. In this case, display screen 2305 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 2305, which serves as the front panel of terminal 2300; in other embodiments, there may be at least two display screens 2305, respectively disposed on different surfaces of terminal 2300 or in a folded design; in still other embodiments, display screen 2305 may be a flexible display screen, disposed on a curved or folded surface of terminal 2300. Furthermore, display screen 2305 may also be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 2305 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0375] The camera assembly 2306 is used to acquire images or videos. Optionally, the camera assembly 2306 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 2306 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0376] The audio circuit 2307 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 2301 for processing, or input to the radio frequency circuit 2304 to achieve voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different part of the terminal 2300. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 2301 or the radio frequency circuit 2304 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 2307 may also include a headphone jack.

[0377] The positioning component 2308 is used to locate the current geographical location of the terminal 2300 in order to enable navigation or LBS (Location Based Service). The positioning component 2308 can be a positioning component based on the US GPS (Global Positioning System), China's BeiDou system, Russia's Granas system, or the European Union's Galileo system.

[0378] Power supply 2309 is used to power the various components in terminal 2300. Power supply 2309 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 2309 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery can also be used to support fast charging technology.

[0379] In some embodiments, the terminal 2300 further includes one or more sensors 2310. The one or more sensors 2310 include, but are not limited to: an accelerometer 2311, a gyroscope 2312, a pressure sensor 2313, a fingerprint sensor 2314, an optical sensor 2315, and a proximity sensor 2316.

[0380] Accelerometer 2311 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal 2300. For example, accelerometer 2311 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 2301 can control touchscreen 2305 to display the user interface in landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 2311. Accelerometer 2311 can also be used for games or for acquiring user motion data.

[0381] The gyroscope sensor 2312 can detect the orientation and rotation angle of the terminal 2300. The gyroscope sensor 2312 can work in conjunction with the accelerometer sensor 2311 to collect the user's 3D movements on the terminal 2300. Based on the data collected by the gyroscope sensor 2312, the processor 2301 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0382] The pressure sensor 2313 can be disposed on the side bezel of the terminal 2300 and / or on the lower layer of the touch display screen 2305. When the pressure sensor 2313 is disposed on the side bezel of the terminal 2300, it can detect the user's grip signal on the terminal 2300, and the processor 2301 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 2313. When the pressure sensor 2313 is disposed on the lower layer of the touch display screen 2305, the processor 2301 can control the operable controls on the UI interface based on the user's pressure operation on the touch display screen 2305. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0383] The fingerprint sensor 2314 is used to collect a user's fingerprint. The processor 2301 identifies the user based on the fingerprint collected by the fingerprint sensor 2314, or vice versa. When the user's identity is identified as trusted, the processor 2301 authorizes the user to perform relevant sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 2314 can be located on the front, back, or side of the terminal 2300. When the terminal 2300 has physical buttons or a manufacturer's logo, the fingerprint sensor 2314 can be integrated with the physical buttons or manufacturer's logo.

[0384] The optical sensor 2315 is used to collect ambient light intensity. In one embodiment, the processor 2301 can control the display brightness of the touch screen 2305 based on the ambient light intensity collected by the optical sensor 2315. Specifically, when the ambient light intensity is high, the display brightness of the touch screen 2305 is increased; when the ambient light intensity is low, the display brightness of the touch screen 2305 is decreased. In another embodiment, the processor 2301 can also dynamically adjust the shooting parameters of the camera assembly 2306 based on the ambient light intensity collected by the optical sensor 2315.

[0385] The proximity sensor 2316, also known as a distance sensor, is typically located on the front panel of the terminal 2300. The proximity sensor 2316 is used to detect the distance between the user and the front of the terminal 2300. In one embodiment, when the proximity sensor 2316 detects that the distance between the user and the front of the terminal 2300 is gradually decreasing, the processor 2301 controls the touchscreen display 2305 to switch from a screen-on state to a screen-off state; when the proximity sensor 2316 detects that the distance between the user and the front of the terminal 2300 is gradually increasing, the processor 2301 controls the touchscreen display 2305 to switch from a screen-off state to a screen-on state.

[0386] Those skilled in the art will understand that Figure 23 The structure shown does not constitute a limitation on terminal 2300 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0387] Figure 24 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 2400 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 2401 and one or more memories 2402. The memories 2402 store at least one instruction, which is loaded and executed by the processors 2401 to implement the resource transfer method and the activation method for the substitute resource transfer function provided in the above-described method embodiments. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input / output. The server may also include other components for implementing device functions, which will not be elaborated here.

[0388] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one instruction, which is loaded and executed by the processor to perform the operations performed in the resource transfer method or the activation method for the substitute resource transfer function in the above embodiments.

[0389] This application also provides a computer-readable storage medium storing at least one instruction, which is loaded and executed by a processor to implement the operations performed in the resource transfer method or the activation method for the substitute resource transfer function in the above embodiments.

[0390] This application also provides a computer program that stores at least one instruction, which is loaded and executed by a processor to implement the operations performed in the resource transfer method or the activation method for the substitute resource transfer function in the above embodiments.

[0391] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0392] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A resource transfer method, characterized in that, The method includes: The system receives a first-generation resource transfer request sent by an intermediate server. The first-generation resource transfer request is sent by any third-party server associated with the intermediate server. The first-generation resource transfer request carries a first user identifier and resource transfer data. The first user identifier is a third-party user identifier registered with the third-party server. Based on the established association, query the second user identifier associated with the first user identifier, where the second user identifier is a local user identifier registered on this end; the association includes the association between a third-party user identifier registered on any third-party server and a local user identifier registered on this end, the association indicating that the local user identifier has enabled the resource transfer function on behalf of the third-party user identifier, the resource transfer function referring to the automatic transfer of resources by the local user identifier on behalf of the third-party user identifier; Based on the resource transfer data, resources are transferred from the resource account of the second user identifier to the resource account of the intermediate server, and the intermediate server is used to transfer the resources from the resource account of the intermediate server to the resource account of the third-party server.

2. The method according to claim 1, characterized in that, Before querying the second user identifier associated with the first user identifier based on the established association, the method further includes: The receiving terminal sends a request to activate the resource transfer function, the activation request carrying the second user identifier and the first user identifier logged in by the terminal; Establish the association between the first user identifier and the second user identifier.

3. The method according to claim 2, characterized in that, The activation request also carries resource transfer conditions for the first user identifier, and the establishment of the association between the first user identifier and the second user identifier includes: Establish the association between the first user identifier, the second user identifier, and the resource transfer conditions.

4. The method according to claim 3, characterized in that, After establishing the association between the first user identifier, the second user identifier, and the resource transfer conditions, the method further includes: A fourth notification message is sent to the intermediate server. The fourth notification message carries the first user identifier and the resource transfer conditions, and is used to indicate that the proxy resource transfer function for the first user identifier has been successfully activated.

5. The method according to claim 2, characterized in that, Before the receiving terminal sends the request to activate the resource transfer function, the method further includes: Obtain the third-party object identifier of at least one third-party server associated with the intermediate server; The terminal sends at least one third-party object identifier to the terminal, which displays the at least one third-party object identifier. In response to a selection operation of any third-party object identifier, the terminal obtains the first user identifier corresponding to the third-party object identifier and sends the activation request.

6. The method according to claim 2, characterized in that, After establishing the association between the first user identifier and the second user identifier, the method further includes: A third notification message is sent to the terminal, which indicates that the resource transfer function has been successfully activated.

7. The method according to claim 1, characterized in that, The association also includes resource transfer conditions for the third-party user identifier. The step of transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data includes: In response to the resource transfer data satisfying the resource transfer conditions of the first user identifier, resources are transferred from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data.

8. The method according to claim 1, characterized in that, After transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes: A resource transfer notification message is sent to the intermediate server. The resource transfer notification message includes the first user identifier and the resource transfer data. The resource transfer notification message is used to notify the intermediate server to transfer the resource from the intermediate server's resource account to the third-party server's resource account according to the first user identifier and the resource transfer data.

9. The method according to claim 1, characterized in that, Before transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes: Send a first prompt message to the terminal that is logged in with the second user identifier. The first prompt message is used to prompt the terminal to transfer resources on behalf of the first user identifier.

10. The method according to claim 1, characterized in that, After transferring resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data, the method further includes: A second prompt message is sent to the terminal that logged in with the second user identifier. The second prompt message is used to indicate that the resource transfer on behalf of the first user identifier has been completed.

11. The method according to any one of claims 1-10, characterized in that, The method is executed by an application server, which includes a first application server corresponding to the sub-application and a second application server corresponding to the parent application, wherein the sub-application runs within the parent application. The first application server is configured to receive the first generation resource transfer request, query the second user identifier associated with the first user identifier according to the association relationship, and send a second generation resource transfer request to the second application server. The second generation resource transfer request carries the resource transfer data and the second user identifier. The second application server is used to receive the second generation resource transfer request and, based on the resource transfer data, transfer resources from the resource account of the second user identifier to the resource account of the intermediate server.

12. A resource transfer method, characterized in that, The method includes: Receive a first-generation resource transfer request sent by an associated third-party server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data. It is confirmed that the resource transfer function for the first user identifier has been enabled; the resource transfer function refers to the automatic transfer of resources by the second user identifier instead of the first user identifier; Send a first generation resource transfer request to the associated application server. The first generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user identifier associated with the first user identifier to the resource account of the local end. The application server is used to establish the association between the first user identifier and the second user identifier, wherein the first user identifier is a third-party user identifier registered with the third-party server, and the second user identifier is a user identifier registered with the application server. Before receiving the first-generation resource transfer request sent by the associated third-party server, the method further includes: The application server sends a fourth notification message, which carries the first user identifier and is used to indicate that the resource transfer function for the first user identifier has been successfully activated. The first user identifier is marked as a user identifier who has activated the resource transfer function.

13. The method according to claim 12, characterized in that, After sending the first generation resource transfer request to the associated application server, the method further includes: Receive a resource transfer notification message sent by the application server, the resource transfer notification message including the first user identifier and the resource transfer data; Based on the first user identifier and the resource transfer data, the resource is transferred from the local resource account to the resource account of the third-party server.

14. The method according to claim 12, characterized in that, Before receiving the first-generation resource transfer request sent by the associated third-party server, the method further includes: The fourth prompt message is sent to the third-party server to prompt the third-party server to send a resource transfer request on behalf of the server if the resource transfer conditions are met.

15. The method according to claim 12, characterized in that, Before receiving the fourth prompt message sent by the application server, the method further includes: Receive a third-party object identifier sent by at least one associated third-party server; The application server sends at least one received third-party object identifier to the application server, the application server sends the at least one third-party object identifier to the terminal, the terminal displays the at least one third-party object identifier, and in response to a selection operation of any third-party object identifier, obtains the first user identifier corresponding to the third-party object identifier and enables the proxy resource transfer function for the first user identifier.

16. A method for activating a resource transfer function, characterized in that, The method includes: The first application interface of the target application is displayed. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered on the third-party server to which the third-party object identifier belongs. In response to the triggering operation of the activation request button, a second application interface is displayed, which includes a resource account of a second user identifier logged into the target application and an activation confirmation button; In response to the activation confirmation button being triggered, an activation request carrying the first user identifier and the second user identifier is sent to the application server; The application server is used to establish an association between the first user identifier and the second user identifier, and send a fourth prompt message to the intermediate server and the third-party server; the association indicates that the second user identifier has enabled the resource transfer function for the first user identifier; the fourth prompt message is used to indicate that the resource transfer function for the first user identifier has been successfully enabled. The intermediate server is used to mark the first identifier as a user identifier that has enabled the resource transfer function after receiving the fourth prompt information. The resource transfer function refers to automatically transferring resources using the second user identifier instead of the first user identifier.

17. The method according to claim 16, characterized in that, The first application interface for displaying the target application includes: If the resource transfer function is not enabled, a prompt message is received, which is used to indicate that the second user identifier has completed the transfer of resources from the first user identifier to the third-party object identifier; The first application interface is displayed according to the prompt information.

18. The method according to claim 17, characterized in that, Before receiving the prompt message when the resource transfer function is not activated, the method further includes: The display interface for identifying objects includes at least one third-party object identifier. In response to the selection of any third-party object identifier, a settings interface is displayed, the settings interface including the selected third-party object identifier and an input field; Obtain the first user identifier entered in the input field; Store the first user identifier in correspondence with the third-party object identifier.

19. The method according to claim 16, characterized in that, The first application interface for displaying the target application includes: The display interface for identifying objects includes at least one third-party object identifier. In response to a selection operation of any third-party object identifier, the first application interface is displayed, the first application interface including the selected third-party object identifier and an input field; Obtain the first user identifier entered in the input field and display the activation request button on the first application interface.

20. The method according to claim 16, characterized in that, The target application is the parent application, and the parent application runs child applications. The first application interface is the interface of the child application. The step of sending an activation request carrying the first user identifier and the second user identifier to the application server in response to the activation confirmation button includes: In response to the activation confirmation button, the parent application is invoked, and an activation request for the resource transfer function is sent to the second application server corresponding to the parent application. The activation request carries the second user identifier and the first user identifier. The second application server is used to send the activation request to the first application server corresponding to the child application. The first application server is used to establish the association between the first user identifier and the second user identifier.

21. The method according to claim 16, characterized in that, The second application interface also includes a condition setting button, and the method further includes: In response to the triggering operation of the condition setting button, the input resource transfer conditions are obtained, and the activation request also carries the resource transfer conditions. The first application server is used to establish the association relationship between the first user identifier, the second user identifier and the resource transfer conditions.

22. The method according to claim 20, characterized in that, The method further includes: Receive the prompt message sent by the second application server; The notification message is displayed through the notification interface of the parent application; or, The notification message is displayed through the notification interface of the sub-application.

23. A resource transfer device, characterized in that, The device includes: The resource transfer request receiving module is used to receive a first-generation resource transfer request sent by an intermediate server. The first-generation resource transfer request is sent by any third-party server associated with the intermediate server. The first-generation resource transfer request carries a first user identifier and resource transfer data. The first user identifier is a third-party user identifier registered with the third-party server. The user identifier query module is used to query a second user identifier associated with the first user identifier based on the established association relationship. The second user identifier is a local user identifier registered on this end. The association relationship includes the association relationship between a third-party user identifier registered on any third-party server and a local user identifier registered on this end. The association relationship indicates that the local user identifier has enabled the resource transfer function on behalf of the third-party user identifier. The resource transfer function means that the local user identifier automatically transfers resources on behalf of the third-party user identifier. The resource transfer module is used to transfer resources from the resource account of the second user identifier to the resource account of the intermediate server according to the resource transfer data. The intermediate server is used to transfer the resources from the resource account of the intermediate server to the resource account of the third-party server.

24. A resource transfer device, characterized in that, The device includes: The resource transfer request receiving module is used to receive a first-generation resource transfer request sent by an associated third-party server. The first-generation resource transfer request carries a first user identifier registered on the third-party server and resource transfer data. The transfer function activation determination module is used to determine that the resource transfer function on behalf of the first user identifier has been activated; the resource transfer function on behalf of the first user identifier refers to automatically transferring resources by the second user identifier in place of the first user identifier; The resource transfer request sending module is used to send the first generation resource transfer request to the associated application server. The first generation resource transfer request is used to request the application server to transfer resources from the resource account of the second user identifier associated with the first user identifier to the resource account of the local end. The application server is used to establish the association between the first user identifier and the second user identifier, wherein the first user identifier is a third-party user identifier registered with the third-party server, and the second user identifier is a user identifier registered with the application server. The device further includes: The prompt message receiving module is used to receive a fourth prompt message sent by the application server. The fourth prompt message carries the first user identifier and is used to indicate that the proxy resource transfer function for the first user identifier has been successfully activated. The user identifier marking module is used to mark the first user identifier as a user identifier that has enabled the resource transfer function.

25. A device for activating a resource transfer function, characterized in that, The device includes: The application interface display module is used to display the first application interface of the target application. The first application interface includes a third-party object identifier, a first user identifier corresponding to the third-party object identifier, and an activation request button. The first user identifier is registered on the third-party server to which the third-party object identifier belongs. The application interface display module is also used to display a second application interface in response to the triggering operation of the activation request button. The second application interface includes a resource account of the second user identifier logged into the target application and an activation confirmation button. The transfer function activation module is used to send an activation request carrying the first user identifier and the second user identifier to the application server in response to the triggering operation of the activation confirmation button. The application server is used to establish an association between the first user identifier and the second user identifier, and send a fourth prompt message to the intermediate server and the third-party server; the association indicates that the second user identifier has enabled the resource transfer function for the first user identifier; the fourth prompt message is used to indicate that the resource transfer function for the first user identifier has been successfully enabled. The intermediate server is used to mark the first identifier as a user identifier that has enabled the resource transfer function after receiving the fourth prompt information. The resource transfer function refers to automatically transferring resources using the second user identifier instead of the first user identifier.

26. A resource transfer system, characterized in that, The resource transfer system includes: a third-party server, an application server, and an intermediate server, wherein the third-party server and the intermediate server are associated, and the application server and the intermediate server are associated. The third-party server is used to send a first-generation resource transfer request to the intermediate server. The first-generation resource transfer request carries a first user identifier and resource transfer data. The first user identifier is a third-party user identifier registered on the third-party server. The intermediate server is configured to receive the first proxy resource transfer request sent by the third-party server, determine that the proxy resource transfer function for the first user identifier has been enabled, and send the first proxy resource transfer request to the application server. The application server is configured to receive the first proxy resource transfer request; query the second user identifier associated with the first user identifier based on the established association relationship, wherein the second user identifier is a user identifier registered on the application server; the association relationship includes the association relationship between a third-party user identifier registered on any third-party server and a user identifier registered on the application server, the association relationship indicating that the user identifier on the application server has enabled the proxy resource transfer function for the third-party user identifier; the proxy resource transfer function refers to automatically transferring resources on behalf of the third-party user identifier by the local user identifier; and transfer resources from the resource account of the second user identifier to the resource account of the intermediate server based on the resource transfer data. The intermediate server is also used to transfer resources from the intermediate server's resource account to the third-party server's resource account.

27. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one instruction, which is loaded and executed by the processor to perform the operation performed by the resource transfer method as described in any one of claims 1 to 15 or the activation method for the substitute resource transfer function as described in any one of claims 16 to 22.

28. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is loaded and executed by a processor to perform the operation of the resource transfer method as described in any one of claims 1 to 15 or the activation method for the substitute resource transfer function as described in any one of claims 16 to 22.

Images