Data processing method and device, computer device and storage medium

Abstract

The application discloses a data processing method and device, computer equipment and a storage medium. The method comprises the following steps: obtaining a service request initiated by a first object of a first application; the service request is used for requesting to execute a target service for a second object; the second application and the first application contain the second object; obtaining a data authorization link according to the service request, and sending the data authorization link to a second device of the second object; the data authorization link indicates that the second object is authorized to the first object; obtaining authorization confirmation information returned by the second device, the authorization confirmation information is generated according to the authorization operation of the second object based on the data authorization link; the authorization confirmation information is used for authorizing the use permission of the target service data of the second object in the second application to the first object according to the authorization confirmation information; the first object is used for executing the target service for the second object according to the use permission of the target service data. By using the application, the safety and efficiency of the first object for executing the target service for the second object can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the continuous development of computer networks, various business forms are emerging one after another, and users are increasingly inclined to conduct various businesses online. Among these, there are situations where one user conducts business for another user.

[0003] In the existing application, if User 1 needs to process a transaction for User 2, User 1 can submit a transaction request. User 2 can obtain a verification code used to authorize the transaction with User 1. User 2 can then send this verification code to User 1, who can then use it to process the transaction for User 2. It is evident that when User 1 processes a transaction for User 2, it involves sending a verification code, and both User 1 and User 2 need to interact with the code. This presents security risks for User 1 when processing transactions for User 2, and the process is cumbersome and inefficient. Summary of the Invention

[0004] This application provides a data processing method, apparatus, computer equipment, and storage medium that can improve the security and efficiency of a first object performing target business for a second object.

[0005] This application provides a data processing method, which is applied to a first server corresponding to a first application, and the method includes:

[0006] Obtain the business request initiated by the first object in the first application; the business request is used to request the execution of the target business for the second object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0007] Obtain a data authorization link according to the business request, and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object;

[0008] Obtain the authorization confirmation information returned by the second device. The authorization confirmation information is generated based on the authorization operation performed by the second object in the first application based on the data authorization link.

[0009] Based on the authorization confirmation information, the first object is granted the right to use the target business data; the target business data belongs to the second object in the second application; the first object in the first application is used to perform the target business for the second object according to the right to use the target business data.

[0010] This application provides a data processing method, which is applied to a first device corresponding to a first object, and the method includes:

[0011] Output the business request interface of the first application;

[0012] Based on the business request operation performed by the first object in the business request interface, a data authorization link is output; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of the target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0013] Send the data authorization link to the second device corresponding to the second object.

[0014] Optionally, sending the data authorization link to the second device corresponding to the second object includes:

[0015] Based on the sending operation for the data authorization link, output the communication list of the first object in the first application; the communication list contains N communication objects of the first object; the N communication objects include the second object; N is a positive integer;

[0016] Based on the selection operation for the second object in the communication list, the data authorization link is sent to the second device.

[0017] Optionally, the above methods also include:

[0018] If the target business is not executed for the second object at the first time point after the output data authorization link, a business execution prompt message for the target business will be output.

[0019] Optionally, the above methods also include:

[0020] If the target service is not executed for the second object at the second time point after the data authorization link is output, a service failure message for the target service will be output.

[0021] Optionally, the second object has remaining data resources in the second application; the target service is to transfer data resources to the second object in the second application when the amount of remaining data resources is less than or equal to a resource threshold; the remaining data resources of the second object in the second application correspond to the object identifier of the second object; the target service is executed based on the object identifier; the above method further includes:

[0022] Obtain the resource transfer amount and object identifier entered by the first object in the business request interface, and execute the business request operation based on the resource transfer amount and object identifier;

[0023] The above methods also include:

[0024] When the remaining data resource quantity is less than or equal to the resource quantity threshold, and the target data resource is transferred from the first object in the data resource pool of the first application to the second object in the second application based on the object identifier, a transfer success prompt message is output in the first application; the target data resource is the data resource indicated by the resource transfer quantity.

[0025] Optionally, the data authorization link contains the object identifier of the second object entered by the first object in the second application; when the data authorization link is triggered in the first application of the second device, and the second object is bound to the object identifier in the first application, the second device is used to output the data authorization page in the first application;

[0026] The data authorization page includes a one-click authorization control. The second device is used to perform the target business for the second object based on the authorization operation triggered by the one-click authorization control.

[0027] This application provides a data processing apparatus, which is applied to a first server corresponding to a first application. The apparatus includes:

[0028] The request acquisition module is used to acquire business requests initiated by a first object in a first application; the business requests are used to request the execution of target business for a second object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0029] The link sending module is used to obtain a data authorization link according to a business request and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object.

[0030] The information acquisition module is used to acquire the authorization confirmation information returned by the second device. The authorization confirmation information is generated based on the second object performing the authorization operation based on the data authorization link in the first application.

[0031] The authorization module is used to authorize the first object to use the target business data according to the authorization confirmation information; the target business data belongs to the business data of the second object in the second application; the first object in the first application is used to execute the target business for the second object according to the use rights of the target business data.

[0032] Optionally, the method by which the link sending module obtains the data authorization link based on the business request includes:

[0033] Create a business event for the target business based on the business request, and add a business not executed status to the business event;

[0034] Generate a data authorization link based on the event identifier of the business event.

[0035] Optionally, the authorization confirmation information may include an event identifier;

[0036] The authorization module grants the first object access to target business data based on the authorization confirmation information in the following ways:

[0037] Extract the event identifier from the authorization confirmation information, and query the business event based on the extracted event identifier;

[0038] Based on the retrieved business events, grant the first object permission to use the target business data.

[0039] Optionally, the second object in the first application and the second object in the second application have the same object identifier; the business event contains the object identifier;

[0040] The authorization module grants the first object access to target business data based on the queried business events in the following ways:

[0041] Extract object identifiers from the retrieved business events;

[0042] Obtain the object identity information of the second object in the first application;

[0043] Generate a data authorization request based on the object identifier and object identity information;

[0044] The data authorization request is sent to the second server corresponding to the second application, so that when the second server successfully authenticates the object identity of the second object based on the object identity information, it authorizes the first object to use the target business data based on the object identifier.

[0045] Optionally, the above-mentioned device is also used for:

[0046] After granting the first object permission to use the target business data, the business inactive status added for the business processing event will be updated to the business executed status.

[0047] Optionally, the business event has a finite time frame; the above apparatus is also used for:

[0048] When the business execution status of a business event is not executed when the deadline is reached, the business not executed status added to the business event will be updated to the business failed execution status, and an execution failure prompt message for the target business will be returned to the first device corresponding to the first object.

[0049] Optionally, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object;

[0050] The target business data is the amount of remaining data resources; the target business is to transfer data resources to a second object in the second application based on the object identifier when the amount of remaining data resources is less than or equal to the resource amount threshold.

[0051] Optionally, the service request may also include resource transfer volume; the above-mentioned device is also used for:

[0052] When the amount of remaining data resources is detected to be less than or equal to the resource amount threshold, the target data resources indicated by the resource transfer amount are obtained from the data resource pool of the first object in the first application.

[0053] Based on the object identifier, the target data resource is transferred to the second object in the second application.

[0054] Optionally, the above-mentioned device is also used for:

[0055] According to the query cycle, a query request for the amount of remaining data resources is sent to the second server corresponding to the second application.

[0056] Obtain the resource quantity indication information returned by the second server based on the query request, and determine the relationship between the remaining data resource quantity and the resource quantity threshold based on the resource quantity indication information; the resource quantity indication information includes the relationship between the remaining data resource quantity and the resource quantity threshold detected by the second server; or

[0057] Obtain the amount of remaining data resources returned by the second server based on the query request, and determine the relationship between the amount of remaining data resources obtained and the resource threshold.

[0058] This application provides a data processing apparatus, which is applied to a first device corresponding to a first object, the apparatus comprising:

[0059] The interface output module is used to output the business request interface of the first application.

[0060] The link output module is used to output a data authorization link based on the business request operation performed by the first object in the business request interface; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of the target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0061] The link sending module is used to send the data authorization link to the second device corresponding to the second object.

[0062] Optionally, the data authorization link is a URL link; the link output module outputs the data authorization link in the manner specified by the business request operation performed by the first object in the business request interface, including:

[0063] Obtain the business request description information for the target business entered by the first object in the business request interface;

[0064] Based on the business request, output text data containing a description of the business request and a URL link.

[0065] Optionally, the data authorization link is an identifier code link; the link output module outputs the data authorization link in the manner specified by the business request operation performed by the first object in the business request interface, including:

[0066] Based on the business request, output image data containing the target business's default text and identifier link.

[0067] Optionally, the method by which the link sending module sends the data authorization link to the second device corresponding to the second object includes:

[0068] Based on the sending operation for the data authorization link, output the communication list of the first object in the first application; the communication list contains N communication objects of the first object; the N communication objects include the second object; N is a positive integer;

[0069] Based on the selection operation for the second object in the communication list, the data authorization link is sent to the second device.

[0070] Optionally, the above-mentioned device is also used for:

[0071] If the target business is not executed for the second object at the first time point after the output data authorization link, a business execution prompt message for the target business will be output.

[0072] Optionally, the above-mentioned device is also used for:

[0073] If the target service is not executed for the second object at the second time point after the data authorization link is output, a service failure message for the target service will be output.

[0074] Optionally, the second object has remaining data resources in the second application; the target service is to transfer data resources to the second object in the second application when the amount of remaining data resources is less than or equal to a resource threshold; the remaining data resources of the second object in the second application correspond to the object identifier of the second object; the target service is executed based on the object identifier; the above apparatus is also used for:

[0075] Obtain the resource transfer amount and object identifier entered by the first object in the business request interface, and execute the business request operation based on the resource transfer amount and object identifier;

[0076] The above-mentioned device is also used for:

[0077] When the remaining data resource quantity is less than or equal to the resource quantity threshold, and the target data resource is transferred from the first object in the data resource pool of the first application to the second object in the second application based on the object identifier, a transfer success prompt message is output in the first application; the target data resource is the data resource indicated by the resource transfer quantity.

[0078] Optionally, the data authorization link contains the object identifier of the second object entered by the first object in the second application; when the data authorization link is triggered in the first application of the second device, and the second object is bound to the object identifier in the first application, the second device is used to output the data authorization page in the first application;

[0079] The data authorization page includes a one-click authorization control. The second device is used to perform the target business for the second object based on the authorization operation triggered by the one-click authorization control.

[0080] This application provides a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, the processor performs the method of this application.

[0081] This application provides a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method described above.

[0082] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative embodiments described above.

[0083] This application allows a first server corresponding to a first application to obtain a business request initiated by a first object in the first application. The business request requests the execution of a target business for a second object. The target business is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the business request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target business data. The target business data belongs to the second object's business data in the second application. The first object in the first application executes the target business for the second object based on the access rights to the target business data. Therefore, the method proposed in this application allows the second object to authorize data for the first object through the authorization operation performed in the first application based on the data authorization link when the first object wants to execute a target business for the second object, thereby accepting the target business executed by the first object and improving the security and efficiency of the target business execution. Attached Figure Description

[0084] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the 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.

[0085] Figure 1 This is a schematic diagram of a network architecture provided in an embodiment of this application;

[0086] Figure 2 This is a schematic diagram illustrating a business transaction scenario provided in this application;

[0087] Figure 3 This is a flowchart illustrating a data processing method provided in this application;

[0088] Figures 4a-4c This is a schematic diagram of an interface for handling the target business provided in this application;

[0089] Figures 5a-5b This is a schematic diagram illustrating a scenario where a data transmission authorization link is provided in this application;

[0090] Figure 6 This is a schematic diagram illustrating a scenario for confirming the processing of a target business, as provided in this application.

[0091] Figure 7This is a flowchart illustrating a data processing method provided in this application;

[0092] Figure 8 This is a schematic diagram of an information prompt scenario provided in this application;

[0093] Figure 9 This is a schematic diagram illustrating an information notification scenario provided in this application;

[0094] Figure 10 This is a schematic diagram illustrating a data sharing scenario provided in this application;

[0095] Figure 11 This is a flowchart illustrating an authorized query process provided in this application;

[0096] Figure 12 This is a flowchart illustrating an authorization confirmation process provided in this application;

[0097] Figure 13 This is a flowchart illustrating a business process provided in this application;

[0098] Figure 14 This is a schematic diagram of the structure of a data processing device provided in this application;

[0099] Figure 15 This is a schematic diagram of the structure of a data processing device provided in this application;

[0100] Figure 16 This is a schematic diagram of the structure of a computer device provided in this application. Detailed Implementation

[0101] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0102] Please see Figure 1 , Figure 1 This is a schematic diagram of a network architecture provided in an embodiment of this application. Figure 1 As shown, the network architecture may include server 100a, server 101a, and a terminal device cluster. The terminal device cluster may include one or more terminal devices; the number of terminal devices is not limited here. Figure 1 As shown, the multiple terminal devices may specifically include terminal device 100b, terminal device 101b, terminal device 102b, ..., terminal device 103b.

[0103] Among them, terminal devices 100b, 101b, 102b, ..., 103b can all be terminal devices that contain the first application, that is, terminal devices with the first application installed. In other words, terminal devices 100b, 101b, 102b, ..., 103b can all be terminal devices of users of the first application. Figure 1 As shown, terminal devices 100b, 101b, 102b, ..., 103b can all connect to server 101a via a network, so that each terminal device can interact with server 101a through the network connection. Server 100a can also connect to server 101a via a network, so that server 100a can interact with server 101a through the network connection.

[0104] like Figure 1 Both server 100a and server 101a shown can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing 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, and big data and artificial intelligence platforms. Terminal devices can be smart terminals such as smartphones, tablets, laptops, desktop computers, and smart TVs. The following description uses the communication between terminal device 100b, terminal device 101b, server 100a, and server 101a as an example to illustrate the specific implementation of this application.

[0105] Please see also Figure 2 , Figure 2 This is a schematic diagram illustrating a business transaction scenario provided in this application. For example... Figure 2 As shown, server 100a can be referred to as the first server, which is the backend server for the first application, and server 101a can be referred to as the second server, which is the backend server for the second application. Terminal device 100b can be referred to as the first device, and the user to which the first device belongs can be referred to as the first object; similarly, terminal device 101b can be referred to as the second device, and the user to which the second device belongs can be referred to as the second object.

[0106] A first object can initiate a service request in a first application on a first device to handle (i.e., execute) a target service for a second object. The second device sends this service request to a first server, which can return a data authorization link to the second device. This data authorization link instructs the second object to authorize data access to the first object to accept the target service handled by the first object. Therefore, the second device can send this data authorization link to the second device corresponding to the second object based on the user operation of the first object. Furthermore, the second object can authorize data access to the first object through this data authorization link in the first application of the second device.

[0107] Specifically, the second object can agree to the first object performing the target service on its behalf via a data authorization link in the second device. The second device can then return authorization confirmation information to the first server. The second application contains the second object's remaining data resources. The second object's data authorization to the first object is equivalent to authorizing the first object to use the remaining data resources in the second application. Therefore, when the first server confirms the second object's agreement to data authorization through this authorization confirmation information, the first server can request data authorization from the second server, that is, request authorization for the second object to use the remaining data resources in the second application. The second server can then authorize the first server to use the second object's remaining data resources. Authorizing the first server to use the second object's remaining data resources is equivalent to authorizing the first object to use the second object's remaining data resources, because subsequently, the first object executes the target service based on the second object's usage rights of the remaining data resources.

[0108] The aforementioned target service could be to transfer data resources from the first object to the second object in the second application when the remaining data resources of the second object in the second application are detected to be less than or equal to a resource threshold. For example... Figure 2 As shown, since the first object in the first server has the right to use the remaining data resources of the second object in the second application, the first server can periodically (e.g., according to a certain period) send a query request to the second server regarding the remaining data resources of the second object. After the second server receives the query request, it can return resource quantity prompt information to the first server. The resource quantity prompt information may include the relationship between the remaining data resources of the second object detected by the second server and the resource quantity threshold.

[0109] Therefore, after receiving the resource quantity prompt, the first server can determine the relationship between the remaining data resources of the second object and the resource quantity threshold. If the first server finds that the remaining data resources of the second object are less than or equal to the resource quantity threshold, then the first server can obtain the target data resources from the first object's data resource pool and transfer them to the second server. The second server can then transfer these target data resources to the second object in the second application, such as transferring them to the second object's application account within the second application. These target data resources can be the data resources specified by the first object as the transfer resource quantity (i.e., the amount of data resources transferred for the second object in a single transaction) when the first object handles the target business for the second object.

[0110] Using the method provided in this application, when the first object handles the target business for the second object in the first application, the second object only needs to authorize the first object's data through the data authorization link in the first application to agree to the first object handling the target business for it. Therefore, the security and convenience of handling the target business are improved, and the efficiency of handling the target business is increased.

[0111] Please see Figure 3 , Figure 3 This is a flowchart illustrating a data processing method provided in this application. The method is applied to a first server corresponding to a first application. For example... Figure 3 As shown, the method may include:

[0112] Step S101: Obtain a business request initiated by a first object in the first application; the business request is used to request the execution of a target business for a second object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0113] Optionally, in this embodiment, the executing entity may be a first server corresponding to a first application, which may be a backend server of the first application; the first application may be any application capable of handling the target business, which is associated with a second application, and the target business may be a business handled by a first object in the first application for a second object. The second application may be any application associated with the target business.

[0114] The first object can be a user in a first application. The operations performed by the first object, as described below, can be performed through the first application logged into the user account of the first object. Both the first and second applications can include the second object; that is, the second object is a user in both the first and second applications. Operations performed by the second object in the first application can be performed through the first application logged into the user account of the second object, and operations performed on the second object in the second application can be performed on the user account of the second object in the second application.

[0115] The first object can correspond to the first device, which can be the terminal device of the first object. The first device can include a first application logged in with the user account of the first object. The second object can correspond to the second device, which can be the terminal device of the second object. The second device can include a first application logged in with the user account of the second object.

[0116] The first server can obtain a business request initiated by the first object in the first application. This business request can be sent from the first device corresponding to the first object to the first server. Specifically, the first object can select to handle the target business for the second object in the first application of the first device, and the first device can then generate the business request.

[0117] Optionally, the target service could be a low-amount automatic top-up service. For example, the second application could include the data resources of the second object, which can be referred to as the remaining data resources of the second object. Therefore, it can be understood that the target service could be to take a corresponding amount of data resources from the data resource pool of the first object in the first application and transfer them to the second object in the second application when the amount of the remaining data resources of the second object in the second application is less than or equal to a resource threshold, thereby topping up the data resources of the second object in the second application. The data resource pool of the first object in the first application could be the data resource account of the first object in the first application, such as the balance account of the first object in the first application, a linked bank card account, or other application accounts added by the first object.

[0118] In this context, the second object in the first application and the second object in the second application can share the same object identifier. The aforementioned target service can be executed through this object identifier. Therefore, when the first object handles the target service for the second object in the first application, the first object can also enter the object identifier of the second object and the resource transfer amount. This resource transfer amount indicates how much data resource needs to be transferred to the second object in the second application when the remaining data resource amount of the second object in the second application is less than or equal to a resource amount threshold. Therefore, the aforementioned service request can include the object identifier of the second object and the resource transfer amount. Optionally, the object identifier of the second object can be the communication number of the second object.

[0119] Therefore, it can be understood that the above-mentioned business request is a request to perform a target business for the second object, and the execution of the target business is related to the object data of the second object in the second application (e.g., the amount of remaining data resources of the second object in the second application).

[0120] Please see Figures 4a-4c , Figures 4a-4c This is a schematic diagram of an interface for handling a target service provided in this application. The target service can be an automatic recharge service, specifically a low-amount automatic recharge service. For example, the automatic recharge service can involve transferring data resources to a second object in the second application when the remaining data resources of a certain object (such as a second object) in the second application are less than or equal to a resource threshold (which can be arbitrarily set according to the actual application scenario).

[0121] like Figure 4a As shown, the mobile phone recharge terminal interface 100c includes a button 101c for processing the target service "automatic recharge". Therefore, the first object can generate the aforementioned service request by triggering (e.g., clicking) this button 101c, requesting to process the target service for the second object. For example... Figure 4b As shown, the terminal interface 100d in the recharge personal center also includes the target service "Auto-Recharge," as shown in the Auto-Recharge function bar in box 101d. The first object can generate the aforementioned service request by triggering (e.g., clicking) this Auto-Recharge function bar, requesting to process the target service for the second object. For example... Figure 4c As shown, the "Mobile Phone Recharge" mini-program interface 100e includes a "Communication Service Hall" function control 101e. Clicking this function control 101e displays a function bar 102e in the mini-program interface 100e. This function bar 102e contains multiple function controls, specifically including "Recharge Phone Credit," "Recharge Data," "Automatic Recharge," and "Balance Inquiry" function controls. Therefore, the second object can also generate the aforementioned service request by triggering (e.g., clicking) the "Automatic Recharge" function control in the function bar 102e, requesting the processing of the target service for the second object.

[0122] Step S102: Obtain a data authorization link according to the business request, and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object;

[0123] Optionally, the first server can obtain a data authorization link based on the service request. This data authorization link is used to instruct the second object to authorize data to the first object. Therefore, the first server can send this data authorization link to the second device corresponding to the second object.

[0124] In this context, "the first server sends the data authorization link to the second device corresponding to the second object" means that the first server sends the data authorization link to the first application within the second device corresponding to the second object. Specifically, this process can be as follows: the first server can return the data authorization link to the first device corresponding to the first object; the first device, based on the sending operation of the second object, can then send the data authorization link to the second device corresponding to the second object. The second object can be an object in the first object's contact list within the first application; therefore, the first object can select the second object from its contact list to send the data authorization link.

[0125] Optionally, the first server can create a business event for the target business based on the business request. This business event can be understood as a record of business creation, representing a request from the first object to perform the target business for the second object. The business event can contain any data related to the first object performing the target business for the second object, such as the object identifier of the second object. When the first server first creates the business event, it can also add a "business not executed" status to it. This "business not executed" status indicates that the first object has not yet successfully performed the target business for the second object, meaning that the second object has not yet accepted (agreed to) the target business performed by the first object.

[0126] The business events created above also have an event identifier. The first server can generate the data authorization link based on the event identifier, and the data authorization link contains the event identifier.

[0127] Please see Figures 5a-5b , Figures 5a-5b This is a schematic diagram illustrating a scenario where a data transmission authorization link is provided in this application. First, as... Figure 5aAs shown, when the first object handles the target business for the second object, it can enter the object identifier of the second object on the terminal interface 100f. This object identifier can be the communication number "123 4565 4321" in the terminal interface 100f. The target business handled by the first object for the second object can be transferring 100 yuan of data resources to the second object in the second application when the remaining data resources of the second object in the second application are less than 10 yuan. Here, 10 yuan can be the resource threshold mentioned below, and 100 yuan can be the resource transfer amount mentioned below. The first object can click the "Confirm Business Handling" button 101f in the terminal interface 100f, and then the first device can display the terminal interface 102f. The terminal interface 102f includes a prompt pop-up window 103f, which contains a function bar 104f. The first object can trigger (e.g., click) the function bar 104f to generate the above-mentioned business request. Through this business request, the first server is requested to generate a data authorization link and return the data authorization link.

[0128] Furthermore, please see Figure 5b When the first object triggers the function bar 104f in the aforementioned terminal interface 102f, the first device can not only obtain the data authorization link returned by the first server, but the first device can also jump from the terminal interface 102f to the terminal interface 100g. The terminal interface 100g includes the first object's communication list (i.e., address book) in the first application. The communication list can include the first object's "Friend 1", "Friend 2", "Friend 3", "Group 1" and "Group 2" in the first application.

[0129] The second target can be Friend 1. Therefore, the first target can select Friend 1 in terminal interface 100g, which will then redirect to terminal interface 102g. Terminal interface 102g includes a pop-up window 103g, which includes a data authorization link 104g. The first target can click the "Send" button in pop-up window 103g to send the data authorization link 104g to Friend 1, i.e., to Friend 1's corresponding second device. Furthermore, it also supports the first target entering a message in pop-up window 103g. When sending data authorization link 104g to Friend 1, the message entered by the first target in pop-up window 103g will also be sent to Friend 1.

[0130] After the second user clicks the "Send" button in pop-up window 103g, causing the first device to send data authorization link 104g to the first user, the first device can then be displayed on terminal interface 102g and then on terminal interface 105g. Terminal interface 105g includes a pop-up window 106g indicating successful transmission of data authorization link 104g, which includes a "OK" button 107g. The first user can click this button 107g to cancel the display of pop-up window 106g on terminal interface 105g.

[0131] Step S103: Obtain the authorization confirmation information returned by the second device. The authorization confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application.

[0132] Optionally, the aforementioned data authorization link can be a URL link or an identification code link, which can be a QR code link. The data authorization link can also carry the object identifier of the second object. Therefore, after the first server sends the data authorization link to the second device corresponding to the second object, the second device can output the data authorization link in the first application. Then, the second device can output an authorization interface based on the second object's triggered operation (such as a click operation) on the data authorization link. If the second device detects that the first application has the object identifier of the second object bound to it (such as the communication number of the second object), the authorization page can include a one-click authorization control, which can be a button control.

[0133] Therefore, after the second object performs an authorization operation based on the data authorization link in the first application (such as a trigger operation by the second object on the one-click authorization control in the authorization interface, which can be a click operation or a swipe operation, etc.), the second device can generate authorization confirmation information. This authorization confirmation information indicates that the second object confirms that it has authorized the first object to handle the target business for itself. This authorization confirmation information may include the event identifier of the aforementioned business event.

[0134] Step S104: Authorize the first object to use the target business data according to the authorization confirmation information; the target business data belongs to the second object's business data in the second application; the first object in the first application is used to perform the target business for the second object according to the access permission of the target business data.

[0135] Optionally, after obtaining the authorization confirmation information, the first server may authorize the first object to use the target business data. This target business data is the business data of the second object in the second application. For example, the target business data could be the remaining data resources of the second object in the second application. The specific process by which the first server authorizes the second object to use the target business data may be as follows:

[0136] The first server can extract the event identifier from the authorization confirmation information. The first server can query the business event created above based on the event identifier, and then authorize the first object to use the target business data based on the queried business event.

[0137] Please see Figure 6 , Figure 6 This is a schematic diagram illustrating a scenario for confirming the processing of a target business, as provided in this application. For example... Figure 6 As shown, terminal interfaces 100h, 101h, and 102h can all be application interfaces of the first application in the second device. User "Lele" can be the first object, and terminal interface 100h is the chat interface between the first and second objects. The data authorization link sent by the first object to the second object is contained in message 103h. The second device can display this information on terminal interface 101h based on the second object's click on the data authorization link in message 103h. Terminal interface 101h includes a "Agree to activate for me" button 104h. The second device can generate authorization confirmation information based on the second object's click on this button 104h (i.e., the authorization operation performed based on the data authorization link). This authorization confirmation information then allows the first server to successfully process the target service for the second object based on the first object's request (specifically, successfully processing the target service for the second object when obtaining the usage rights to the remaining data resources of the second object from the second server). From the user's perspective, when the second object clicks the control 104h, it will jump to the terminal interface 102h. The terminal interface 102h includes a "Successful Activation" pop-up window 105h. This pop-up window 105h is used to indicate that the second object has successfully accepted the target service handled by the first object, that is, the target service has been successfully handled for the second object.

[0138] Specifically, the first server can extract the object identifier of the second object from the queried business events. The first server can also obtain the object identity information of the second object in the first application. This object identity information may be the relevant user information registered by the second object in the first application, which can represent the object identity of the second object.

[0139] Therefore, the first server can generate a data authorization request based on the object identifier extracted from the business event and the obtained object identity information. This data authorization request is a request to the second application to obtain access to the target business data. The first server can then send this data authorization request to the second server corresponding to the second application, which may be the application's backend server. The second server can obtain the object identifier and object identity information of the second object from the data authorization request. Therefore, the second server can authenticate the object identity of the second object using this object identity information. If authentication is successful, the second server can authorize the first object to use the target business data based on the object identifier.

[0140] It should be noted that the first application and the second application can agree in advance that the second server corresponding to the second application can identify the object identity information of the object in the first application. That is, the second server can authenticate the object by using the object identity information of the object in the first application.

[0141] The remaining data resources of the second object in the second application can be corresponding to the object identifier, which can be the communication number of the second object. Therefore, transferring data resources to the second object in the second application can refer to recharging the communication number of the second object.

[0142] Therefore, the aforementioned remaining data resources can refer to the call charges of the object identifier of the second object, and the target business data can be the call charge balance of the object identifier of the second object. This call charge balance is also the amount of remaining data resources of the second object in the second application. Authorizing the first object to use the target business data based on the object identifier can refer to authorizing the first object to use the call charge balance of the object identifier of the second object.

[0143] Once the first object in the first application is granted permission to use the target business data, it indicates that the first object has successfully processed the target business for the second object, meaning the target business has been successfully executed for the second object. At this point, the "business not executed" status added to the business event can be updated to "business executed," indicating that the second object has accepted the target business processed for it by the first object.

[0144] Furthermore, the aforementioned business events also have an absolute timeframe. This absolute timeframe can be a target time period after the first object initiates the business request. For example, if the target time period is 24 hours, then the absolute timeframe can be 24 hours after the first object initiates the business request. For instance, if the target time period is 1 hour, and the first object initiates the business request at 9:00 AM, then the absolute timeframe could be 1 hour after 9:00 AM, which is 10:00 AM. In fact, disregarding business latency, the moment the first object initiates the business request can be the moment the business event is created.

[0145] Therefore, it is understandable that the aforementioned business events can only be executed before the deadline. After the deadline, the business events become invalid. Thus, when the deadline is reached, the business event's execution status is still "not executed," not "executed." The first server can update the "not executed" status added to the business event to "invalid execution," indicating that the business event can no longer be executed. If the first object still wants to process the target business for the second object, the first object needs to re-initiate the business request.

[0146] Furthermore, after updating the business event's non-executed status to a failed execution status, the first server can also return an execution failure message for the target business to the first device of the first object, thereby indicating to the first object that the target business for the second object has failed.

[0147] After successfully granting the second object access to the target business data in the second application to the first object, it indicates that the target business has been successfully executed for the second object in the first application. Therefore, subsequently, the first object in the first application can check whether the remaining data resources of the second object in the second application are less than the resource threshold by checking the access rights to the target business data. If they are less, data resources can be transferred from the data resource pool of the first object in the first application to the second object in the second application.

[0148] The access rights to the target business data granted to the second object can be either indirect or direct, specifically including:

[0149] The first server can send a query request for the amount of remaining data resources to the second server corresponding to the second application through a query cycle. For example, the query cycle can be 1 minute. Therefore, the first server can send a query request to the second server once every 1 minute. Each query request sent by the first server is used to query the second server for the amount of remaining data resources of the second object at the current time. One query request corresponds to one remaining data resource. The remaining data resources corresponding to one query request are the remaining data resources of the second object in the second application at the time the query request was sent. The remaining data resources corresponding to different query requests can be the same or different.

[0150] Therefore, after receiving the query request sent by the first server, the second server can either return a resource quantity indication message to the first server, or directly return the remaining data resources of the second object in the second application. If the second server returns a resource quantity indication message to the first server based on the query request, it indicates that the authorized access to the target business data for the first object is indirect. This resource quantity indication message does not directly include the remaining data resources of the second object in the second application, but rather includes the relationship between the remaining data resources detected by the second server and a resource quantity threshold. This method keeps the remaining data resources of the second object in the second application confidential to the first server, while allowing the first server to directly obtain the relationship between the remaining data resources and the resource quantity threshold. The resource quantity threshold can be set according to the actual application situation; for example, the resource quantity threshold could be 20 yuan.

[0151] If the second server returns the remaining data resources of the second object in the second application to the first server based on the query request, it indicates that the access permission for the target business data authorized to the first object is direct. In this case, the remaining data resources are directly communicated to the first server. By obtaining the remaining data resources, the first server can compare the amount of the remaining data resources with the resource threshold.

[0152] As can be seen, through the two authorization methods described above (direct authorization and indirect authorization), the first server can obtain the relationship between the remaining data resources and the resource threshold. This relationship can be that the remaining data resources are greater than, less than, or equal to the resource threshold. If the first server detects that the remaining data resources are less than or equal to the resource threshold, the first server can transfer data resources from the data resource pool of the first object in the first application to the second object in the second application.

[0153] The aforementioned business request may also include the resource transfer amount recorded by the first object in the first device. This resource transfer amount indicates the amount of data resources that need to be transferred when transferring data resources to the second object in the second application in a single transaction. Therefore, the aforementioned business event may also include this resource transfer amount. Thus, when the first server detects that the remaining data resources are less than or equal to a resource threshold, the first server can obtain the data resources indicated by the resource transfer amount from the data resource pool of the first object in the first application. The data resources indicated by the resource transfer amount can be referred to as the target data resources, and the data resources indicated by the resource transfer amount can be data resources with a resource transfer amount equal to this amount. Furthermore, the first server can transfer the target data resources obtained from the data resource pool of the first object in the first application to the second object in the second application through the object identifier, that is, perform data resource transfer to the object identifier corresponding to the second object in the second application.

[0154] Using the method provided in this application, when a first object requests to perform a target service for a second object, and when the second object authorizes data to the first object to accept the target service performed by the second object, the first object can directly send a data authorization link to the second object. Then, the second object can directly authorize the first object through the data authorization link in the first application, so that the target service can be performed for the second object through the data resource pool of the first object in the first application.

[0155] This application allows a first server corresponding to a first application to obtain a business request initiated by a first object in the first application. The business request requests the execution of a target business for a second object. The target business is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the business request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target business data. The target business data belongs to the second object's business data in the second application. The first object in the first application executes the target business for the second object based on the access rights to the target business data. Therefore, the method proposed in this application allows the second object to authorize data for the first object through the authorization operation performed in the first application based on the data authorization link when the first object wants to execute a target business for the second object, thereby accepting the target business executed by the first object and improving the security and efficiency of the target business execution.

[0156] Please see Figure 7 , Figure 7This is a flowchart illustrating a data processing method provided in this application. The method is applied to a first device corresponding to a first object. The content in the embodiments of this application can be related to the above. Figure 7 The contents of the corresponding embodiments are combined with each other, but the embodiments of this application belong to the front-end method. Figure 3 The corresponding implementation example belongs to the background method. For example... Figure 7 As shown, the method may include:

[0157] Step S201: Output the business request interface of the first application;

[0158] Optionally, in this embodiment, the executing entity may be a first device corresponding to a first object. The first device can output a business request interface based on the relevant business processing operations of the first object. This business request interface includes the target business that can be processed. The target business is associated with a second application, and the first object can process the target business for the second object in this business request interface. See the following description for details.

[0159] For a detailed description of the first application, the second application, the first object, the second object, and the target business, please refer to the above. Figure 3 The description in the corresponding embodiment.

[0160] Step S202: Based on the business request operation performed by the first object in the business request interface, output a data authorization link; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of the target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0161] Optionally, the first device can output a data authorization link based on the business request operation performed by the first object in the business request interface. This business request operation can be a request operation performed by the first object on the second object, used to request the execution of a target business for the second object. Specifically, this business request operation can be an operation whereby the first object requests the processing of a target business for the second object. Through this business request operation, the first device can generate the aforementioned... Figure 3 In the corresponding embodiment, the first device can send the service request to the first server corresponding to the first application to request the first server to generate a data authorization link based on the service request. The specific process of the first server generating the data authorization link can be found above. Figure 3 The description in the corresponding embodiment.

[0162] Furthermore, the first server can send the generated data authorization link to the first device. This data authorization link can be a URL link, or it can be an identification code link, such as a QR code link. Additionally, the first object can enter a business request description for the target business on the business request interface. This description can be information the first object wants to inform the second object when processing the target business, such as "Let me provide you with uninterrupted, automatic top-ups!" Therefore, if the data authorization link is a URL link, the first device can output the data authorization link by outputting text data containing both the business request description and the URL link.

[0163] Alternatively, the target service may also have a default message, such as "I will protect your phone bill". If the data authorization link is an identification code link, the first device can output the data authorization link by outputting image data containing the identification code link and the default message.

[0164] Step S203: Send the data authorization link to the second device corresponding to the second object.

[0165] Optionally, the second device is used to request the first server to perform the target service for the second object based on the authorization operation performed by the second object in the first application; the authorization operation is performed based on a data authorization link.

[0166] Optionally, the first device can send the data authorization link to the second device corresponding to the second object based on the sending operation of the first object for the data authorization link. Specifically, the first device can output the communication list of the first object in the first application based on the sending operation of the first object for the data authorization link. This communication list can be the first object's friend list in the first application, and can include N communication objects of the first object in the first application. These N communication objects can be N friend users of the first object in the first application, where N is a positive integer, and the specific value of N is determined according to the actual application scenario and is not restricted. The second object is included among these N communication objects.

[0167] Therefore, the first device can send a data authorization link to the second device based on the first object's selection operation for the second object in the communication list. The second device can then authorize the first object to use the target business data in the second application through the authorization operation performed by the second object on the data authorization link. This indicates that the first object has successfully processed the target business for the second object, meaning the target business has been executed on the second object.

[0168] Furthermore, disregarding the latency of business requests, the moment the data authorization link is output can be the moment when the first object executes the business request operation and generates the business request on the business request interface. Therefore, at the first time point after the data authorization link is output, if the target business has not yet been executed on the second object, the first device can output a business execution prompt message for the target business. This prompt message is used to remind the first object to inform the second object to accept the target business to be executed for the second object. It can be understood that the time corresponding to the aforementioned first time point is earlier than the absolute time of the aforementioned business event; the time corresponding to the first time point can be any time before that absolute time. The time corresponding to this first time point can be set according to the actual application scenario.

[0169] Furthermore, if the target service has not been executed for the second object by the second time point after the data authorization link is established, the first device will output a service failure message for the target service. This second time point can be the aforementioned deadline. This service execution failure message can be the aforementioned message indicating that the execution of the target service for the second object has failed. This message serves to inform the first object that the target service request for the second object has failed. If the first object insists on performing the target service for the second object, it can re-execute the service request operation for the second object.

[0170] The second object has remaining data resources in the second application. These remaining data resources correspond to the object identifier of the second object. The target business can be executed based on this object identifier. When the amount of the remaining data resources is less than or equal to the resource amount threshold, the target business can use the data resource pool of the first object in the first application to transfer data resources to the second object in the second application.

[0171] The first device can also obtain the resource transfer amount entered by the first object in the business request interface and the object identifier of the second object. The resource transfer amount is the amount of data resources that need to be transferred to the second object in a single transaction. Therefore, the first device can perform the above-mentioned business request operation based on the resource transfer amount and the object identifier, and the business request generated by performing the business request operation can include the resource transfer amount and the object identifier.

[0172] After successfully executing the target service for the second object, if the remaining data resources of the second object in the second application are less than or equal to the resource threshold, and the first server transfers the target data resources to the second object in the second application based on the object identifier of the second object, the first device can output a transfer success message in the first application. This transfer success message indicates that the first object has successfully transferred data resources to the second object in the second application. The target data resource is the data resource indicated by the resource transfer amount, and the resource amount of the target data resource is the resource transfer amount.

[0173] The aforementioned data authorization link may contain the object identifier of the second object entered by the first object in the second application. When the data authorization link is triggered by the second object in the first application of the second device, and the second device detects that the second object is bound to an object identifier in the first application, the second device can output a data authorization page in the first application. This data authorization page may contain a one-click authorization control. The second device can perform the target business for the second object based on the authorization operation triggered by the second object based on the one-click authorization control (such as a click operation on the one-click authorization control). Specifically, the second device performing the target business for the second object indirectly requests the first server to execute it.

[0174] The data authorization link can be triggered in the following ways: If the data authorization link is a URL link, it can be triggered by clicking the URL link, such as clicking the URL link in the text data above. Alternatively, if the data authorization link is an identifier code link, it can be triggered by recognizing the identifier code link to identify the triggering method of the URL link above, such as long-pressing to recognize the identifier code link in the image data above to trigger the data authorization link.

[0175] Please see Figure 8 , Figure 8This is a schematic diagram of an information prompt scenario provided in this application. The terminal interface 100j can be a "mobile phone recharge" mini-program interface. The terminal interface 100j includes a service execution prompt message 101j sent by the first server to the first device when the target service for the second object is not executed at the time corresponding to the first time node. The service execution prompt message 101j includes the prompt messages "Expiration reminder", "The automatic recharge service you signed for 123***4321 has not yet been verified by the person. Please remind him to complete the verification!", "Expiration item: Number verification must be completed within 24 hours", "Expiration time: 2021-07-08 12:40:14", and "Note: Click here to reactivate automatic recharge. Thank you for using the automatic recharge service!". This service execution prompt message is used to prompt the first object to remind the second object to authorize the data, that is, to remind the second object to accept the target service signed for them.

[0176] Please see Figure 9 , Figure 9 This is a schematic diagram of an information reminder scenario provided in this application. The terminal interface 100k can also be a "mobile phone recharge" mini-program interface. The terminal interface 100k includes a service failure prompt message 101k sent by the first server to the first device when the target service for the second object is not executed at the second time node. The service failure prompt message 101k includes the prompt messages "Expiration reminder notification", "Sorry, the automatic recharge service you activated for 123***4321 failed to complete number verification within 24 hours.", "Your automatic recharge activation failed, the link is valid until 2021-07-08 12:40:14", and "Click here to reactivate automatic recharge. Automatic recharge saves time and is easy!". This service failure prompt message 101k is used to notify the first object that the target service it activated for the second object has failed.

[0177] Using the method provided in this application, the second object can authorize the data of the first object with one click in the first application to accept the target business handled by the first object, thereby improving the security and ease of operation of handling the target business and improving the efficiency of handling the target business.

[0178] This application allows a first server corresponding to a first application to obtain a business request initiated by a first object in the first application. The business request requests the execution of a target business for a second object. The target business is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the business request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target business data. The target business data belongs to the second object's business data in the second application. The first object in the first application executes the target business for the second object based on the access rights to the target business data. Therefore, the method proposed in this application allows the second object to authorize data for the first object through the authorization operation performed in the first application based on the data authorization link when the first object wants to execute a target business for the second object, thereby accepting the target business executed by the first object and improving the security and efficiency of the target business execution.

[0179] Please see Figure 10 , Figure 10 This is a schematic diagram illustrating a data sharing scenario provided in this application. For example... Figure 10 As shown, the user here can refer to the first object mentioned above, the first application can be a mini-program, the target business mentioned above can be a business belonging to a mini-program (such as the mini-program for "mobile phone recharge" mentioned above), the mini-program front-end here refers to the mini-program in the first application of the first device, and the back-end can refer to the first server mentioned above.

[0180] Therefore, the first user can click "Activate" to request the second user to process (i.e., activate) the target service. The first user can then choose to "Send to Friend for Verification." At this point, the first device can request the backend to process the target service for the second user through the mini-program frontend. The backend can generate a sharing record for this transaction, which can refer to the aforementioned service event. After successfully generating the sharing record, the backend can return sharing parameters (i.e., a data authorization link) to the first device's mini-program frontend. These sharing parameters can include the sharing identifier returned through the interface (such as the aforementioned event identifier) ​​and the relevant activation parameters for activating the target service.

[0181] When the first recipient selects "Send to Friend Verification," the first device can also bring up the first recipient's friend list in the first application and select the second recipient from the friend list to send the data authorization link (i.e., sharing parameters). If the sending is successful, a "Sent Successfully, Pending Confirmation" pop-up window will be displayed on the mini-program front end; if the sending fails, a "Sent Failed" pop-up window will be displayed on the mini-program front end, guiding the first recipient to resend.

[0182] Please see Figure 11 , Figure 11 This is a flowchart illustrating an authorized query process provided in this application. Here, "user" refers to the first object, "first application" can be a mini-program, the mini-program's front-end can be on the first device, and the back-end can be the first server.

[0183] The first user can access a page on a first device. This page can be used to check whether the second user has accepted the target service requested by the first user. Upon accessing this page, the mini-program frontend can call a query interface, passing in the sharing identifier contained in the data authorization link. This sharing identifier can be the aforementioned event identifier. Then, by transmitting this sharing identifier to the backend, the backend can query the activation status of the sharing identifier. The activation status of the sharing identifier represents the processing status of the business event, which is the processing status of the target service requested by the first user for the second user. If the processing fails (e.g., the business event is added with a "business expired execution" status), the reason for the failure is returned (e.g., failure due to timeout and lack of confirmation). If the processing succeeds (e.g., the business event is added with a "business executed" status), detailed activation information is displayed. If the processing is not completed (e.g., the business event is added with a "business not executed" status), the page is displayed as "pending activation," guiding the user to share.

[0184] Please see Figure 12 , Figure 12 This is a flowchart illustrating an authorization confirmation process provided in this application. For example... Figure 12 As shown, the user here can refer to the second object, the front end of the mini program can be the front end of the first application on the second device, and the back end can be the first server.

[0185] The second object can access a page where it receives the data authorization link sent by the first object. The second object can call a query interface through the mini-program frontend, passing in the sharing identifier (such as the event identifier mentioned above) contained in the data authorization link to query the backend for the activation status of the sharing identifier. This activation status represents the processing status of the business event, i.e., the processing status of the target business requested by the first object for the second object. If processing fails (e.g., the business event has an added "business expired execution" status), the reason for the failure is returned (e.g., failure due to timeout and lack of confirmation). If processing succeeds (e.g., the business event has an added "business executed" status), detailed activation information is displayed. If processing is not completed (e.g., the business event has an added "business not executed" status), the system displays "pending activation," guiding the user to share.

[0186] Furthermore, when the second object obtains the data authorization link, it can click to activate (e.g., perform an authorization operation) through the link. The mini-program frontend can then identify whether the second object's identifier is bound to the current application (which could be the mini-program itself or the application to which it belongs). If it is, low-amount automatic top-up (the target service) can be activated directly, and the relevant interface can be called upon verification. If the mini-program frontend detects that the second object's identifier is not bound to the current application, data authorization for the first object can be achieved by sending a verification code to the second object. Upon successful verification, the relevant interface can also be called to activate the target service.

[0187] Please see Figure 13 , Figure 13 This is a flowchart illustrating a business process provided in this application. For example... Figure 13 As shown, the sharer can be the first object, and the authorizer can be the second object. For the sharer, the front end can be the first application on the first device, and for the authorizer, the front end can be the second application on the second device. The access layer, logic layer, and data layer can be different business layers belonging to the first server. This process includes:

[0188] S1, query the functions that the sharer can activate for the mobile phone: The first device can query the access layer for the functions that can be activated, such as the functions of the target service.

[0189] S2, Sharer Login Verification: The access layer can verify the login of the sharer, that is, verify the identity of the sharer.

[0190] S3, Query available functions: The access layer can query the logic layer for available functions.

[0191] S4, Query the number's activated function information: The logic layer can query the data layer for information on the functions that the first object has activated.

[0192] S5, Return: Returns the query results to the logic layer.

[0193] S6, Determine the available functions: The logic layer determines the available functions based on the returned results. For example, it can be all available functions except for those already enabled by the first object.

[0194] S7, Return: Returns the judgment result to the access layer.

[0195] S8, Returns Enabled Functions: The access layer returns a judgment on whether a function can be enabled to the front end.

[0196] S9, Generate a sharing record: This sharing record can be a business request, that is, a record of a request to handle the target business for a second object.

[0197] S10, Sharer Login Verification: The access layer can verify the login of the sharer, that is, verify the identity of the sharer.

[0198] S11, Information on records to be activated: The access layer can return information on records to be activated to the logic layer.

[0199] S12, Activation Qualification Verification: The logic layer verifies whether the first object is qualified to activate the target service for the second object.

[0200] S13, Save activation information: If it is determined that the user is eligible, the logic layer can send the activation information to the data layer for saving.

[0201] S14, Return: The data layer returns a data authorization link to the logic layer.

[0202] S15, Return: The logic layer returns a data authorization link to the access layer.

[0203] S16, Return the generation result: The access layer returns a data authorization link to the first device, and then the first device can send the data authorization link to the second device.

[0204] S17, Confirm Authorization: The second device can confirm authorization through this data authorization link.

[0205] S18, Authorized Person Login Verification: The access layer can verify the login of authorized persons, that is, verify the identity of the sharer.

[0206] S19, Activate Function: When the verification is successful, you can request the logic layer to activate the function, that is, to process the target business.

[0207] S20, Query sharing record information: The logic layer can query sharing record information through event identifiers, which can be the aforementioned business events.

[0208] S21, Return: The data layer can return query results to the logic layer, such as whether the query result was found.

[0209] S22, Failure Validation: Verify whether the business event queried has become invalid.

[0210] S23, Functionality Verification: If the function is not invalid, the target service can be activated, and the activation of the service can be verified.

[0211] S24, Update sharing record to authorized: After the first object successfully activates the target service for the second object, the sharing record can be updated to authorized, for example, by adding the service execution status to the service event.

[0212] S25, Return: Returns activation success information (i.e., returns authorization result).

[0213] S26, Return: Returns activation success information (i.e., returns authorization result).

[0214] S27, Return authorization result: Returns activation success information (i.e., returns authorization result).

[0215] This application allows a first server corresponding to a first application to obtain a business request initiated by a first object in the first application. The business request requests the execution of a target business for a second object. The target business is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the business request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target business data. The target business data belongs to the second object's business data in the second application. The first object in the first application executes the target business for the second object based on the access rights to the target business data. Therefore, the method proposed in this application allows the second object to authorize data for the first object through the authorization operation performed in the first application based on the data authorization link when the first object wants to execute a target business for the second object, thereby accepting the target business executed by the first object and improving the security and efficiency of the target business execution.

[0216] Please see Figure 14 , Figure 14 This is a schematic diagram of a data processing apparatus provided in this application. The data processing apparatus can be a computer program (including program code) running on a computer device; for example, the data processing apparatus is application software. This data processing apparatus can be used to execute corresponding steps in the methods provided in the embodiments of this application. The apparatus can be applied to a first server corresponding to a first application. For example... Figure 14 As shown, the data processing device 1 may include: a request acquisition module 11, a link sending module 12, an information acquisition module 13, and an authorization module 14;

[0217] The request acquisition module 11 is used to acquire a business request initiated by a first object in the first application; the business request is used to request the execution of a target business for a second object; the target business is associated with the second application, and both the second application and the first application contain the second object.

[0218] Link sending module 12 is used to obtain a data authorization link according to a business request and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object;

[0219] Information acquisition module 13 is used to acquire authorization confirmation information returned by the second device. The authorization confirmation information is generated based on the second object performing an authorization operation based on the data authorization link in the first application.

[0220] The authorization module 14 is used to authorize the first object to use the target business data according to the authorization confirmation information; the target business data belongs to the business data of the second object in the second application; the first object in the first application is used to perform the target business for the second object according to the use permission of the target business data.

[0221] Optionally, the method by which the link sending module 12 obtains the data authorization link based on the business request includes:

[0222] Create a business event for the target business based on the business request, and add a business not executed status to the business event;

[0223] Generate a data authorization link based on the event identifier of the business event.

[0224] Optionally, the authorization confirmation information may include an event identifier;

[0225] The authorization module 14 authorizes the first object to use the target business data based on the authorization confirmation information in the following ways:

[0226] Extract the event identifier from the authorization confirmation information, and query the business event based on the extracted event identifier;

[0227] Based on the retrieved business events, grant the first object permission to use the target business data.

[0228] Optionally, the second object in the first application and the second object in the second application have the same object identifier; the business event contains the object identifier;

[0229] The authorization module 14 grants the first object access to target business data based on the queried business events in the following ways:

[0230] Extract object identifiers from the retrieved business events;

[0231] Obtain the object identity information of the second object in the first application;

[0232] Generate a data authorization request based on the object identifier and object identity information;

[0233] The data authorization request is sent to the second server corresponding to the second application, so that when the second server successfully authenticates the object identity of the second object based on the object identity information, it authorizes the first object to use the target business data based on the object identifier.

[0234] Optionally, the above-mentioned device 1 is also used for:

[0235] After granting the first object permission to use the target business data, the business inactive status added for the business processing event will be updated to the business executed status.

[0236] Optionally, the business event has a finite time frame; the above-mentioned device 1 is also used for:

[0237] When the business execution status of a business event is not executed when the deadline is reached, the business not executed status added to the business event will be updated to the business failed execution status, and an execution failure prompt message for the target business will be returned to the first device corresponding to the first object.

[0238] Optionally, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object;

[0239] The target business data is the amount of remaining data resources; the target business is to transfer data resources to a second object in the second application based on the object identifier when the amount of remaining data resources is less than or equal to the resource amount threshold.

[0240] Optionally, the service request may also include resource transfer volume; the aforementioned device 1 is further used for:

[0241] When the amount of remaining data resources is detected to be less than or equal to the resource amount threshold, the target data resources indicated by the resource transfer amount are obtained from the data resource pool of the first object in the first application.

[0242] Based on the object identifier, the target data resource is transferred to the second object in the second application.

[0243] Optionally, the above-mentioned device 1 is also used for:

[0244] According to the query cycle, a query request for the amount of remaining data resources is sent to the second server corresponding to the second application.

[0245] Obtain the resource quantity indication information returned by the second server based on the query request, and determine the relationship between the remaining data resource quantity and the resource quantity threshold based on the resource quantity indication information; the resource quantity indication information includes the relationship between the remaining data resource quantity and the resource quantity threshold detected by the second server; or

[0246] Obtain the amount of remaining data resources returned by the second server based on the query request, and determine the relationship between the amount of remaining data resources obtained and the resource threshold.

[0247] According to one embodiment of this application, Figure 3The steps involved in the data processing method shown can be derived from... Figure 14 The data processing apparatus 1 shown is executed by each module. For example, Figure 3 Step S101 shown can be performed by Figure 14 The request is executed by module 11 in the middle. Figure 3 Step S102 shown can be performed by Figure 14 The link sending module 12 in the middle is used to execute; Figure 3 Step S103 shown can be performed by Figure 14 The information acquisition module 13 in the middle is used to execute, Figure 3 Step S104 shown can be derived from Figure 14 The authorization module 14 in the middle is used to execute.

[0248] This application allows a first server corresponding to a first application to obtain a service request initiated by a first object in the first application. The service request requests the execution of a target service for a second object. The target service is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the service request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target service data. The target service data belongs to the second object's service data in the second application. The first object in the first application executes the target service for the second object based on the access rights to the target service data. Therefore, when the first object wants to execute a target service for the second object, the device proposed in this application allows the second object to authorize data for the first object through the authorization operation performed based on the data authorization link in the first application, thereby accepting the target service executed by the first object and improving the security and efficiency of the target service execution.

[0249] According to one embodiment of this application, Figure 14 The modules in the data processing device 1 shown can be individually or entirely combined into one or more units, or some of the units can be further divided into multiple functionally smaller sub-units to achieve the same operation without affecting the technical effects of the embodiments of this application. The above modules are based on logical function division. In practical applications, the function of one module can also be implemented by multiple units, or the function of multiple modules can be implemented by one unit. In other embodiments of this application, the data processing device 1 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0250] According to one embodiment of this application, a general-purpose computer device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), can perform operations such as... Figure 3 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 14 The data processing apparatus 1 shown herein, and the data processing method for implementing the embodiments of this application, are described. The computer program described above may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0251] Please see Figure 15 , Figure 15 This is a schematic diagram of the structure of a data processing apparatus provided in this application. The data processing apparatus can be a computer program (including program code) running on a computer device; for example, the data processing apparatus is application software. The data processing apparatus can be used to execute corresponding steps in the methods provided in the embodiments of this application. This apparatus can be applied to a first device corresponding to a first object. For example... Figure 15 As shown, the data processing device 1 may include: an interface output module 21, a link output module 22, and a link sending module 23;

[0252] Interface output module 21 is used to output the business request interface of the first application;

[0253] The link output module 22 is used to output a data authorization link based on the business request operation performed by the first object in the business request interface; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of the target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0254] The link sending module 23 is used to send the data authorization link to the second device corresponding to the second object.

[0255] Optionally, the data authorization link is a URL link; the link output module 23 outputs the data authorization link according to the business request operation performed by the first object in the business request interface, including:

[0256] Obtain the business request description information for the target business entered by the first object in the business request interface;

[0257] Based on the business request, output text data containing a description of the business request and a URL link.

[0258] Optionally, the data authorization link is an identifier code link; the link output module 22 outputs the data authorization link according to the business request operation performed by the first object in the business request interface, including:

[0259] Based on the business request, output image data containing the target business's default text and identifier link.

[0260] Optionally, the method by which the link sending module 23 sends the data authorization link to the second device corresponding to the second object includes:

[0261] Based on the sending operation for the data authorization link, output the communication list of the first object in the first application; the communication list contains N communication objects of the first object; the N communication objects include the second object; N is a positive integer;

[0262] Based on the selection operation for the second object in the communication list, the data authorization link is sent to the second device.

[0263] Optionally, the above-mentioned device 2 is also used for:

[0264] If the target business is not executed for the second object at the first time point after the output data authorization link, a business execution prompt message for the target business will be output.

[0265] Optionally, the above-mentioned device 2 is also used for:

[0266] If the target service is not executed for the second object at the second time point after the data authorization link is output, a service failure message for the target service will be output.

[0267] Optionally, the second object has remaining data resources in the second application; the target service is to transfer data resources to the second object in the second application when the amount of remaining data resources is less than or equal to a resource threshold; the remaining data resources of the second object in the second application correspond to the object identifier of the second object; the target service is executed based on the object identifier; the above-mentioned device 2 is further used for:

[0268] Obtain the resource transfer amount and object identifier entered by the first object in the business request interface, and execute the business request operation based on the resource transfer amount and object identifier;

[0269] The aforementioned device 2 is also used for:

[0270] When the remaining data resource quantity is less than or equal to the resource quantity threshold, and the target data resource is transferred from the first object in the data resource pool of the first application to the second object in the second application based on the object identifier, a transfer success prompt message is output in the first application; the target data resource is the data resource indicated by the resource transfer quantity.

[0271] Optionally, the data authorization link contains the object identifier of the second object entered by the first object in the second application; when the data authorization link is triggered in the first application of the second device, and the second object is bound to the object identifier in the first application, the second device is used to output the data authorization page in the first application;

[0272] The data authorization page includes a one-click authorization control. The second device is used to perform the target business for the second object based on the authorization operation triggered by the one-click authorization control.

[0273] According to one embodiment of this application, Figure 7 The steps involved in the data processing method shown can be derived from... Figure 15 The data processing device 2 shown is executed by each module. For example, Figure 7 Step S201 shown can be performed by Figure 15 The interface output module 21 in the middle is used to execute, Figure 7 Step S202 shown can be performed by Figure 15 The link output module 22 in the middle is used to execute; Figure 7 Step S203 shown can be performed by Figure 15 The link sending module 13 in the middle is used to execute this.

[0274] This application allows a first server corresponding to a first application to obtain a service request initiated by a first object in the first application. The service request requests the execution of a target service for a second object. The target service is associated with a second application, and both the second and first applications contain a second object. A data authorization link is obtained based on the service request and sent to a second device corresponding to the second object. The data authorization link instructs the second object to authorize data from the first object. Authorization confirmation information returned by the second device is obtained; this confirmation information is generated after the second object performs an authorization operation based on the data authorization link in the first application. Based on the authorization confirmation information, the first object is authorized to use the target service data. The target service data belongs to the second object's service data in the second application. The first object in the first application executes the target service for the second object based on the access rights to the target service data. Therefore, when the first object wants to execute a target service for the second object, the device proposed in this application allows the second object to authorize data for the first object through the authorization operation performed based on the data authorization link in the first application, thereby accepting the target service executed by the first object and improving the security and efficiency of the target service execution.

[0275] According to one embodiment of this application, Figure 15The modules in the data processing device 2 shown can be individually or entirely combined into one or more units, or some of these units can be further divided into multiple functionally smaller sub-units to achieve the same operation without affecting the technical effects of the embodiments of this application. The above modules are based on logical functional division. In practical applications, the function of one module can be implemented by multiple units, or the function of multiple modules can be implemented by one unit. In other embodiments of this application, the data processing device 2 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0276] According to one embodiment of this application, a general-purpose computer device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), can perform operations such as... Figure 3 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 15 The data processing apparatus 2 shown herein, and the data processing method for implementing the embodiments of this application, are described. The computer program described above can be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0277] Please see Figure 16 , Figure 16 This is a schematic diagram of the structure of a computer device provided in this application. Figure 16 As shown, the computer device 1000 may include a processor 1001, a network interface 1004, and a memory 1005. Furthermore, the computer device 1000 may also include a user interface 1003 and at least one communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. Figure 16 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0278] exist Figure 16 In the computer device 1000 shown, the network interface 1004 provides network communication functionality; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0279] Obtain the business request initiated by the first object in the first application; the business request is used to request the execution of the target business for the second object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0280] Obtain a data authorization link according to the business request, and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object;

[0281] Obtain the authorization confirmation information returned by the second device. The authorization confirmation information is generated based on the authorization operation performed by the second object in the first application based on the data authorization link.

[0282] Based on the authorization confirmation information, the first object is granted the right to use the target business data; the target business data belongs to the second object in the second application; the first object in the first application is used to perform the target business for the second object according to the right to use the target business data.

[0283] Optionally, the processor 1001 can also be used to call the device control application stored in the memory 1005 to achieve:

[0284] Output the business request interface of the first application;

[0285] Based on the business request operation performed by the first object in the business request interface, a data authorization link is output; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of the target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with the second application, and both the second application and the first application contain the second object;

[0286] Send the data authorization link to the second device corresponding to the second object.

[0287] It should be understood that the computer device 1000 described in the embodiments of this application can execute the foregoing text. Figure 3 and Figure 7 The data processing method described in the corresponding embodiments can also be executed as described above. Figure 14 The corresponding embodiment refers to the data processing device 1 described above and the foregoing text. Figure 15The description of the data processing apparatus 1 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0288] Furthermore, it should be noted that this application also provides a computer-readable storage medium storing a computer program executed by the aforementioned data processing apparatus 1 and data processing apparatus 2. The computer program includes program instructions, which, when executed by a processor, enable the execution of the aforementioned... Figure 3 and Figure 7 The description of the data processing method in the corresponding embodiments is already provided and will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer storage medium involved in this application, please refer to the description of the method embodiments of this application.

[0289] As an example, the above program instructions can be deployed and executed on a single computer device, or deployed and executed on multiple computer devices located in one location, or executed on multiple computer devices distributed across multiple locations and interconnected via a communication network. Multiple computer devices distributed across multiple locations and interconnected via a communication network can form a blockchain network.

[0290] The aforementioned computer-readable storage medium can be an internal storage unit of the data processing apparatus or computer device provided in any of the foregoing embodiments, such as a hard disk or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0291] This application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned... Figure 3 and Figure 7The data processing method described in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments related to this application, please refer to the description of the method embodiments of this application.

[0292] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0293] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0294] The methods and related apparatuses provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.

[0295] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, The method is applied to a first server corresponding to a first application, and the method includes: A business request initiated by a first object in a first application is obtained; the business request is used to request the execution of a target business for a second object; the target business is associated with a second application, both the second application and the first application contain the second object, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object, and the target business is to transfer data resources to the second object in the second application based on the object identifier when the amount of the remaining data resources is less than or equal to a resource amount threshold; The data authorization link is obtained according to the service request, and the data authorization link is sent to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object. Obtain the authorization confirmation information returned by the second device, which is generated based on the second object performing an authorization operation in the first application based on the data authorization link; The authorization confirmation information grants the first object permission to use the target business data; the target business data belongs to the second object's business data in the second application, and the target business data is the resource amount of the remaining data resources; the first object in the first application is used to execute the target business for the second object according to the access permission of the target business data.

2. The method according to claim 1, characterized in that, The step of obtaining the data authorization link according to the business request includes: Create a business event for the target business based on the business request, and add a business not executed status to the business event; The data authorization link is generated based on the event identifier of the business event.

3. The method according to claim 2, characterized in that, The authorization confirmation information includes the event identifier; The step of granting the first object access to the target business data based on the authorization confirmation information includes: Extract the event identifier from the authorization confirmation information, and query the business event based on the extracted event identifier; Based on the retrieved business event, authorize the first object to use the target business data.

4. The method according to claim 3, characterized in that, The business event includes the object identifier; The step of authorizing the first object to use the target business data based on the queried business event includes: Extract the object identifier from the retrieved business events; Obtain the object identity information of the second object in the first application; A data authorization request is generated based on the object identifier and the object identity information; The data authorization request is sent to the second server corresponding to the second application, so that when the second server successfully authenticates the object identity of the second object based on the object identity information, it authorizes the first object to use the target business data based on the object identifier.

5. The method according to claim 2, characterized in that, The method further includes: After authorizing the first object to use the target business data, the business not executed status added for the business processing event will be updated to the business executed status.

6. The method according to claim 5, characterized in that, The business event has an absolute time limit; the method further includes: When the service execution status of the service event is the service non-execution status when the absolute time is reached, the service non-execution status added to the service event will be updated to the service failure execution status, and an execution failure prompt message for the target service will be returned to the first device corresponding to the first object.

7. The method according to claim 1, characterized in that, The service request also includes resource transfer volume; the method also includes: When the amount of remaining data resources is detected to be less than or equal to the resource amount threshold, the target data resources indicated by the resource transfer amount are obtained from the data resource pool of the first object in the first application. The target data resource is transferred to the second object in the second application based on the object identifier.

8. The method according to claim 7, characterized in that, The method further includes: According to the query cycle, a query request for the amount of remaining data resources is sent to the second server corresponding to the second application. Obtain the resource quantity prompt information returned by the second server based on the query request, and determine the relationship between the remaining data resource quantity and the resource quantity threshold based on the resource quantity prompt information; the resource quantity prompt information includes the relationship between the remaining data resource quantity and the resource quantity threshold detected by the second server; or Obtain the amount of remaining data resources returned by the second server according to the query request, and determine the relationship between the obtained amount of remaining data resources and the resource amount threshold.

9. A data processing method, characterized in that, The method is applied to a first device corresponding to a first object, and the method includes: Output the business request interface of the first application; Based on the business request operation performed by the first object in the business request interface, a data authorization link is output; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of a target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with a second application, both the second application and the first application contain the second object, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object, and the target business is to transfer data resources to the second object in the second application based on the object identifier when the amount of the remaining data resources is less than or equal to a resource amount threshold; The data authorization link is sent to the second device corresponding to the second object; the second object, in the first application of the second device, authorizes the first object to use the target business data through the data authorization link, the target business data being the business data of the second object in the second application, and the target business data being the resource amount of the remaining data resources; the first object in the first application is used to execute the target business for the second object according to the use permission of the target business data.

10. The method according to claim 9, characterized in that, The data authorization link is a URL link; the step of outputting the data authorization link based on the business request operation performed by the first object in the business request interface includes: Obtain the business request description information for the target business entered by the first object in the business request interface; Based on the business request operation, output text data containing the business request description information and the URL link.

11. The method according to claim 9, characterized in that, The data authorization link is an identifier code link; the step of outputting the data authorization link based on the business request operation performed by the first object in the business request interface includes: Based on the business request operation, output image data containing the default business text of the target business and the identification code link.

12. A data processing apparatus, characterized in that, The device is applied to a first server corresponding to a first application, and the device includes: A request acquisition module is used to acquire a business request initiated by a first object in a first application; the business request is used to request the execution of a target business for a second object; the target business is associated with a second application, both the second application and the first application contain the second object, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object, and the target business is to transfer data resources to the second object in the second application based on the object identifier when the amount of the remaining data resources is less than or equal to a resource amount threshold; A link sending module is used to obtain a data authorization link according to the service request and send the data authorization link to the second device corresponding to the second object; the data authorization link is used to instruct the second object to authorize data to the first object. The information acquisition module is used to acquire the authorization confirmation information returned by the second device, which is generated based on the second object performing an authorization operation based on the data authorization link in the first application; An authorization module is used to authorize the first object to use target business data according to the authorization confirmation information; the target business data belongs to the second object's business data in the second application, and the target business data is the resource amount of the remaining data resources; the first object in the first application is used to execute the target business for the second object according to the use permission of the target business data.

13. A data processing apparatus, characterized in that, The data processing device is applied to a first device corresponding to a first object, and the device includes: The interface output module is used to output the business request interface of the first application. The link output module is used to output a data authorization link based on the business request operation performed by the first object in the business request interface; the business request operation is a request operation performed by the first object on the second object; the business request operation is used to request the execution of a target business for the second object; the data authorization link is used to instruct the second object to authorize data to the first object; the target business is associated with a second application, both the second application and the first application contain the second object, the second object in the first application and the second object in the second application have the same object identifier; the second application has remaining data resources corresponding to the object identifier of the second object, and the target business is to transfer data resources to the second object in the second application based on the object identifier when the amount of the remaining data resources is less than or equal to a resource amount threshold; A link sending module is used to send the data authorization link to the second device corresponding to the second object; the second object, in a first application of the second device, authorizes the first object to use the target business data through the data authorization link, the target business data being the business data of the second object in the second application, and the target business data being the resource amount of the remaining data resources; the first object in the first application is used to execute the target business for the second object according to the use permission of the target business data.

14. A computer device, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1-11.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and executed as described in any one of claims 1-11.

16. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, wherein a processor of a computer device reads from and executes the computer instructions, causing the computer device to perform the method as described in any one of claims 1-11.

Images