Account Processing Method, Device, Electronic Device, and Computer Readable Medium

Abstract

Embodiments of the present disclosure disclose an account processing method, apparatus, electronic device, and computer-readable medium. A specific implementation of the method includes: in response to receiving a hosting request for a hosted account sent by a hosted account terminal, obtaining hosting information for the hosted account; detecting whether the account status of the hosted sub-account is an idle state, and detecting whether the account status of the hosting account is an unhosted state; in response to detecting that the account status of the hosted sub-account is an idle state and the account status of the hosting account is an unhosted state, sending the hosting information to the hosting account terminal of the hosting account; and in response to receiving feedback information indicating acceptance of hosting sent by the hosting account terminal, performing hosting processing on the hosted sub-account. This implementation prevents nested hosting of accounts and reduces the likelihood of account information leakage.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technologies, and particularly to an account processing method, apparatus, electronic device, and computer-readable medium. Background Art

[0002] With the continuous growth of cloud service users, the secure operation (account trusteeship) of user accounts has also increased accordingly. Currently, for the trusteeship of cloud service users' accounts, the commonly adopted method is to entrust all cloud service users' accounts to a unified account operator for account trusteeship.

[0003] However, the above trusteeship method usually has the following technical problems: when there are a large number of accounts entrusted by the account operator, it is easy to cause nested trusteeship of accounts and leakage of account information. Summary of the Invention

[0004] The content part of the present disclosure is used to briefly introduce concepts, which will be described in detail in the following detailed implementation part. The content part of the present disclosure is not intended to identify the key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] Some embodiments of the present disclosure propose an account processing method, apparatus, electronic device, and computer-readable medium to solve the technical problems mentioned in the above background art part.

[0006] In a first aspect, some embodiments of the present disclosure provide an account processing method, the method including: in response to receiving a trusteeship request for a to-be-trusteeship account sent by a to-be-trusteeship account terminal, obtaining trusteeship information corresponding to the to-be-trusteeship account, where the trusteeship information includes a to-be-trusteeship sub-account and a trusteeship account for trusteeship of the to-be-trusteeship sub-account, and the to-be-trusteeship sub-account is a sub-account of the to-be-trusteeship account established by the to-be-trusteeship account terminal; detecting whether the account status of the to-be-trusteeship sub-account is an idle state, and detecting whether the account status of the trusteeship account is an un-trusteeship state; in response to detecting that the account status of the to-be-trusteeship sub-account is an idle state and the account status of the trusteeship account is an un-trusteeship state, sending the trusteeship information to a trusteeship account terminal of the trusteeship account; in response to receiving feedback information sent by the trusteeship account terminal indicating acceptance of trusteeship, performing trusteeship processing on the to-be-trusteeship sub-account.

[0007] Optionally, before performing the trusteeship processing on the to-be-trusteeship sub-account, the method further includes: generating account association information based on the trusteeship account and the to-be-trusteeship sub-account; storing the account association information in a local database.

[0008] Optionally, the above-mentioned trusteeship processing of the above-mentioned entrusted sub-account includes: in response to detecting operation information indicating the selection of the above-mentioned entrusted sub-account sent by the above-mentioned trusteeship account terminal, determining whether there is account association information corresponding to the above-mentioned trusteeship account and the above-mentioned entrusted sub-account in the local database; in response to determining the existence, generating a temporary token corresponding to the above-mentioned entrusted sub-account, and sending the above-mentioned temporary token to the above-mentioned trusteeship account terminal; in response to detecting operation information indicating the selection of the above-mentioned entrusted sub-account and the above-mentioned temporary token sent by the above-mentioned trusteeship account terminal within a preset time period, performing trusteeship processing on the above-mentioned entrusted sub-account.

[0009] Optionally, the above-mentioned trusteeship processing of the above-mentioned entrusted sub-account includes: in response to receiving a target entrusted sub-account for transferring the trusteeship of the above-mentioned entrusted sub-account sent by the above-mentioned trusteeship account terminal, associating the above-mentioned entrusted sub-account with the above-mentioned target entrusted sub-account; in response to receiving operation information indicating the selection of the above-mentioned target entrusted sub-account sent by the above-mentioned trusteeship account terminal, sending at least one entrusted sub-account corresponding to the above-mentioned target entrusted sub-account to the above-mentioned trusteeship account terminal for display.

[0010] Optionally, the above-mentioned generation of account association information based on the above-mentioned trusteeship account and the above-mentioned entrusted sub-account includes: in response to receiving a first trusteeship instruction sent by the above-mentioned trusteeship account terminal, associating the above-mentioned trusteeship account and the above-mentioned entrusted sub-account to generate account association information.

[0011] Optionally, the above-mentioned generation of account association information based on the above-mentioned trusteeship account and the above-mentioned entrusted sub-account includes: in response to receiving a second trusteeship instruction sent by the above-mentioned trusteeship account terminal, associating the trusteeship sub-account of the above-mentioned trusteeship account and the above-mentioned entrusted sub-account to generate account association information.

[0012] Optionally, before the above-mentioned generation of account association information based on the above-mentioned trusteeship account and the above-mentioned entrusted sub-account, the above-mentioned method further includes: setting the account status of the above-mentioned entrusted sub-account to the trusteeship status.

[0013] Optionally, the above-mentioned method further includes: in response to determining that the account status of the above-mentioned entrusted sub-account is the working status, setting the request status of the above-mentioned entrusted sub-account to the rejected status; in response to the account status of the above-mentioned trusteeship account being the trusteeship status, setting the request status of the above-mentioned entrusted sub-account to the rejected status.

[0014] Optionally, the above-mentioned method further includes: in response to receiving feedback information indicating the rejection of the trusteeship sent by the above-mentioned trusteeship account terminal, setting the request status of the above-mentioned entrusted sub-account to the rejected status, and generating information indicating the rejection of the trusteeship request and sending it to the above-mentioned entrusted account terminal.

[0015] In a second aspect, some embodiments of the present disclosure provide an account processing apparatus, the apparatus comprising: an obtaining unit configured to obtain, in response to receiving a hosting request for a hosted account sent by a hosted account terminal, hosting information corresponding to the hosted account, wherein the hosting information includes a hosted sub-account and a hosting account for hosting the hosted sub-account, and the hosted sub-account is a sub-account of the hosted account established by the hosted account terminal; a detecting unit configured to detect whether the account status of the hosted sub-account is an idle state and whether the account status of the hosting account is an unhosted state; a sending unit configured to send the hosting information to a hosting account terminal of the hosting account in response to detecting that the account status of the hosted sub-account is an idle state and the account status of the hosting account is an unhosted state; and a hosting unit configured to perform a hosting process on the hosted sub-account in response to receiving feedback information sent by the hosting account terminal indicating acceptance of hosting.

[0016] Optionally, before the hosting unit, the apparatus further comprises: a generating unit configured to generate account association information based on the hosting account and the hosted sub-account; and a storing unit configured to store the account association information in a local database.

[0017] Optionally, the hosting unit is further configured to: determine whether there is account association information corresponding to the hosting account and the hosted sub-account in the local database in response to detecting operation information sent by the hosting account terminal indicating selection of the hosted sub-account; generate a temporary token corresponding to the hosted sub-account and send the temporary token to the hosting account terminal in response to determining that there is such information; and perform a hosting process on the hosted sub-account in response to detecting operation information sent by the hosting account terminal indicating selection of the hosted sub-account and the temporary token within a preset time period.

[0018] Optionally, the hosting unit is further configured to: perform an association process between the hosted sub-account and a target hosted sub-account in response to receiving the target hosted sub-account for transferring and hosting the hosted sub-account sent by the hosting account terminal; and send at least one hosted sub-account corresponding to the target hosted sub-account to the hosting account terminal for display in response to receiving operation information sent by the hosting account terminal indicating selection of the target hosted sub-account.

[0019] Optionally, the generating unit is further configured to: perform an association process between the hosting account and the hosted sub-account to generate account association information in response to receiving a first hosting instruction sent by the hosting account terminal.

[0020] Optionally, the generating unit is further configured to: in response to receiving the second hosting instruction sent by the above-mentioned hosted account terminal, associate the hosted sub-account of the above-mentioned hosted account with the above-mentioned sub-account to be hosted, so as to generate account association information.

[0021] Optionally, before the generating unit, the device further includes: a setting unit configured to set the account status of the above-mentioned sub-account to be hosted to the hosted status.

[0022] Optionally, the device further includes: a first rejection setting unit configured to, in response to determining that the account status of the above-mentioned sub-account to be hosted is the working status, set the request status of the above-mentioned sub-account to be hosted to the rejected status; a second rejection setting unit configured to, in response to the account status of the above-mentioned hosted account being the hosted status, set the request status of the above-mentioned sub-account to be hosted to the rejected status.

[0023] Optionally, the device further includes: a rejection setting unit configured to, in response to receiving the feedback information indicating rejection of hosting sent by the above-mentioned hosted account terminal, set the request status of the above-mentioned sub-account to be hosted to the rejected status, and generate information indicating a request for rejection of hosting and send it to the above-mentioned sub-account terminal to be hosted.

[0024] In a third aspect, some embodiments of the present disclosure provide an electronic device, including: one or more processors; a storage device having stored thereon one or more programs, which when executed by the one or more processors cause the one or more processors to implement the method described in any implementation manner of the first aspect above.

[0025] In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having stored thereon a computer program, wherein the program, when executed by a processor, implements the method described in any implementation manner of the first aspect above.

[0026] The above-mentioned various embodiments of the present disclosure have the following beneficial effects: Through the account processing method of some embodiments of the present disclosure, nested custody of accounts is prevented, and the possibility of account information leakage is reduced. Specifically, the reasons for the nested custody of accounts and the easy leakage of account information are as follows: When there are a large number of accounts entrusted by the account operator, it is easy to cause nested custody of accounts and easy leakage of account information. Based on this, in the account processing method of some embodiments of the present disclosure, first, in response to receiving a custody request for a corresponding entrusted account sent by an entrusted account terminal, obtain custody information corresponding to the above-mentioned entrusted account. Among them, the above-mentioned custody information includes the entrusted sub-account and the custody account used to custody the above-mentioned entrusted sub-account. The above-mentioned entrusted sub-account is a sub-account of the above-mentioned entrusted account established by the above-mentioned entrusted account terminal. Thus, it is convenient to subsequently detect whether the entrusted sub-account has custody of other accounts and whether the custody account is custody by other accounts. Next, detect whether the account status of the above-mentioned entrusted sub-account is the idle state, and detect whether the account status of the above-mentioned custody account is the un-custody state. Thus, it can be detected whether the entrusted sub-account has custody of other accounts (whether it is in the idle state), and whether the custody account is custody by other accounts (whether it is in the un-custody state). Thus, nested custody of accounts is prevented. Then, in response to detecting that the account status of the above-mentioned entrusted sub-account is the idle state and the account status of the above-mentioned custody account is the un-custody state, send the above-mentioned custody information to the custody account terminal of the above-mentioned custody account. Thus, when it is detected that neither the entrusted sub-account nor the custody account is nested in custody, the above-mentioned custody information can be sent to the custody account terminal of the above-mentioned custody account, so that the custody account terminal can process the custody information. Finally, in response to receiving the feedback information indicating acceptance of custody sent by the above-mentioned custody account terminal, perform custody processing on the above-mentioned entrusted sub-account. Here, because the statuses of both the entrusted sub-account and the custody account are detected, nested custody of accounts is prevented. Also because nested custody of accounts is prevented, the possibility of account information leakage is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the elements and elements are not necessarily drawn to scale.

[0028] Figure 1 is a schematic diagram of an application scenario of the account processing method of some embodiments of the present disclosure;

[0029] Figure 2 is a flowchart according to some embodiments of the account processing method of the present disclosure;

[0030] Figure 3 is a flowchart of some other embodiments of the account processing method according to the present disclosure;

[0031] Figure 4 is a flowchart of still some other embodiments of the account processing method according to the present disclosure;

[0032] Figure 5 is a schematic structural diagram of some embodiments of the account processing apparatus according to the present disclosure;

[0033] Figure 6 is a schematic structural diagram of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed implementation manners

[0034] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0035] In addition, it should be noted that for the sake of convenience of description, only parts related to the relevant invention are shown in the drawings. Without conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other.

[0036] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependent relationships.

[0037] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive. Those skilled in the art should understand that unless clearly specified otherwise in the context, it should be understood as "one or more".

[0038] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0039] The present disclosure will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0040] Figure 1 is a schematic diagram of an application scenario of the account processing method according to some embodiments of the present disclosure.

[0041] In Figure 1In the application scenario, first, the computing device 101 can respond to the received hosting request for the hosted account sent by the hosted account terminal, and obtain the hosting information 102 corresponding to the above-mentioned hosted account. Among them, the above-mentioned hosting information 102 includes the hosted sub-account 1021 and the hosting account 1022 used to host the above-mentioned hosted sub-account 1021. The above-mentioned hosted sub-account 1021 is a sub-account of the above-mentioned hosted account established by the above-mentioned hosted account terminal. Then, the computing device 101 can detect whether the account status of the above-mentioned hosted sub-account 1021 is an idle state, and detect whether the account status of the above-mentioned hosting account 1022 is an unhosted state. Then, the computing device 101 can respond to detecting that the account status of the above-mentioned hosted sub-account 1021 is an idle state, and the account status of the above-mentioned hosting account 1022 is an unhosted state, and send the above-mentioned hosting information 102 to the hosting account terminal 103 of the above-mentioned hosting account 1022. Finally, the computing device 101 can respond to receiving the feedback information 104 sent by the above-mentioned hosting account terminal 103 indicating acceptance of hosting, and perform hosting processing on the above-mentioned hosted sub-account 1021.

[0042] It should be noted that the above-mentioned computing device 101 can be hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster composed of multiple servers or terminal devices, or can be implemented as a single server or a single terminal device. When the computing device is embodied as software, it can be installed in the above-mentioned listed hardware devices. It can be implemented as, for example, multiple software or software modules used to provide distributed services, or can be implemented as a single software or software module. No specific limitation is made here.

[0043] It should be understood that Figure 1 the number of computing devices in

[0044] Continuing to refer to Figure 2 , a flow 200 of some embodiments of the account processing method according to the present disclosure is shown. The account processing method includes the following steps:

[0045] Step 201, in response to receiving a hosting request for a hosted account sent by a hosted account terminal, obtain hosting information corresponding to the above-mentioned hosted account.

[0046] In some embodiments, the execution subject of the account processing method (such as Figure 1The computing device 101 shown can, in response to receiving a hosting request for a hosted account sent by a hosted account terminal, obtain the hosting information for the hosted account sent by the hosted account terminal through a wired connection or a wireless connection. Among them, the hosting information includes a hosted sub-account and a hosting account for hosting the hosted sub-account. The hosted sub-account is a sub-account of the hosted account established by the hosted account terminal. Here, the hosted account terminal can be a terminal that logs in to the hosted account. The hosting request can be a request instruction for hosting the hosted sub-account of the hosted account sent by the hosted account terminal. The hosting information can refer to the account information for hosting the hosted sub-account of the hosted account sent by the hosted account terminal. The hosting account can be an account selected by the hosted account terminal for hosting the hosted sub-account.

[0047] In an actual application scenario, a user can log in to a hosted account (e.g., 135XXXX2312) on the hosted account terminal. After completing the login of the hosted account, the hosted account terminal can create a hosted sub-account (e.g., 135XXXX9840) of the hosted account (e.g., 135XXXX2312). Then, the hosted account terminal can open the front-end page corresponding to the execution entity, browse and select a hosting account (e.g., 156XXXX3812) for hosting the hosted sub-account on the opened front-end page. Finally, the hosted account terminal can perform a merge process on the hosted sub-account and the hosting account to obtain the hosting information. For example, the user can log in to the hosted account in the front-end APP corresponding to the execution entity on the mobile phone. After completing the login of the hosted account, the user can browse and select a hosting account for hosting the hosted sub-account in the front-end APP.

[0048] In the actual interaction process between the hosted account terminal and the execution entity, first, the hosted account terminal can first send a hosting request for the hosted account to the execution entity. Next, after receiving the hosting request for the hosted account sent by the hosted account terminal, the execution entity obtains the hosting information for the hosted account sent by the hosted account terminal.

[0049] Step 202, detect whether the account status of the hosted sub-account is an idle status, and detect whether the account status of the hosting account is an unhosted status.

[0050] In some embodiments, the above-mentioned execution entity may detect whether the account status of the above-mentioned sub-account to be entrusted is an idle status, and detect whether the account status of the above-mentioned entrusted account is an unentrusted status. Here, the idle status may indicate that the above-mentioned sub-account to be entrusted does not entrust other accounts. Here, the unentrusted status may indicate that the above-mentioned entrusted account is not entrusted by other accounts.

[0051] Thus, the situation of nested entrustment can be prevented. For example, the sub-account to be entrusted "A" entrusts the account "B" (that is, the account "B" is managed by the sub-account to be entrusted "A"). At this time, if the sub-account to be entrusted "A" is further entrusted to the entrusted account "C" (that is, the sub-account to be entrusted "A" is managed by the entrusted account "C"), it belongs to nested entrustment, which is likely to cause the leakage of account information.

[0052] Step 203, in response to detecting that the account status of the above-mentioned sub-account to be entrusted is an idle status, and the account status of the above-mentioned entrusted account is an unentrusted status, send the above-mentioned entrusted information to the entrusted account terminal of the above-mentioned entrusted account.

[0053] In some embodiments, the above-mentioned execution entity may, in response to detecting that the account status of the above-mentioned sub-account to be entrusted is an idle status, and the account status of the above-mentioned entrusted account is an unentrusted status, send the above-mentioned entrusted information to the entrusted account terminal of the above-mentioned entrusted account. In practice, the above-mentioned execution entity may send the above-mentioned entrusted information to the entrusted account terminal of the above-mentioned entrusted account by means of a wired connection or a wireless connection.

[0054] Step 204, in response to receiving the feedback information indicating acceptance of entrustment sent by the above-mentioned entrusted account terminal, perform entrustment processing on the above-mentioned sub-account to be entrusted.

[0055] In some embodiments, the above-mentioned execution entity may, in response to receiving the feedback information indicating acceptance of entrustment sent by the above-mentioned entrusted account terminal, perform entrustment processing on the above-mentioned sub-account to be entrusted. Here, the feedback information indicating acceptance of entrustment may refer to the entrusted account terminal accepting the entrustment of the above-mentioned sub-account to be entrusted. Here, the entrustment processing may refer to the above-mentioned execution entity performing a suspension process on the account. In practice, the above-mentioned execution entity may, in response to receiving the feedback information indicating acceptance of entrustment sent by the above-mentioned entrusted account terminal, perform an account suspension on the above-mentioned sub-account to be entrusted. In an actual application scenario, when the sub-account to be entrusted is an account of the supplier type on a shopping platform, in response to receiving the feedback information indicating acceptance of entrustment sent by the above-mentioned entrusted account terminal, the above-mentioned execution entity may log in to the sub-account to be entrusted, and when receiving the operation information acting on the sub-account to be entrusted sent by the above-mentioned entrusted account terminal (for example, processing the order information received by the sub-account to be entrusted), the above-mentioned execution entity may process the received order information through the sub-account to be entrusted.

[0056] Optionally, in response to determining that the account status of the above-mentioned managed sub-account is the working status, set the request status of the above-mentioned managed sub-account to the rejected status.

[0057] In some embodiments, the above-mentioned execution entity may, in response to determining that the account status of the above-mentioned managed sub-account is the working status, set the request status of the above-mentioned managed sub-account to the rejected status. Here, the working status may indicate that the above-mentioned managed sub-account manages other accounts. Here, the request status may refer to the status of the current request to manage the above-mentioned managed sub-account. Here, the rejected status may indicate that the request to manage the above-mentioned managed sub-account is rejected.

[0058] Optionally, in response to the account status of the above-mentioned managing account being the managed status, set the request status of the above-mentioned managed sub-account to the rejected status.

[0059] In some embodiments, the above-mentioned execution entity may, in response to the account status of the above-mentioned managing account being the managed status, set the request status of the above-mentioned managed sub-account to the rejected status. Here, the managed status may indicate that the above-mentioned managing account is managed by other accounts. Thus, the situation of nested management can be prevented.

[0060] The above embodiments of the present disclosure have the following beneficial effects: Through the account processing method of some embodiments of the present disclosure, nested custody of accounts is prevented, and the possibility of account information leakage is reduced. Specifically, the reasons for the nested custody of accounts and the easy leakage of account information are as follows: When there are many accounts entrusted by the account operator, it is easy to cause the nested custody of accounts and the easy leakage of account information. Based on this, the account processing method of some embodiments of the present disclosure first, in response to receiving a custody request for a corresponding entrusted account sent by an entrusted account terminal, obtains custody information corresponding to the above-mentioned entrusted account. Among them, the above-mentioned custody information includes an entrusted sub-account and a custody account for custody of the above-mentioned entrusted sub-account. The above-mentioned entrusted sub-account is a sub-account of the above-mentioned entrusted account established by the above-mentioned entrusted account terminal. Thus, it is convenient to subsequently detect whether the entrusted sub-account has entrusted other accounts and whether the custody account has been entrusted by other accounts. Then, it is detected whether the account status of the above-mentioned entrusted sub-account is an idle state, and whether the account status of the above-mentioned custody account is an un-custody state. Thus, it can be detected whether the entrusted sub-account has entrusted other accounts (whether it is in an idle state), and whether the custody account has been entrusted by other accounts (whether it is in an un-custody state). Thereby, nested custody of accounts is prevented. Then, in response to detecting that the account status of the above-mentioned entrusted sub-account is an idle state and the account status of the above-mentioned custody account is an un-custody state, the above-mentioned custody information is sent to the custody account terminal of the above-mentioned custody account. Thus, when it is detected that neither the entrusted sub-account nor the custody account is nested in custody, the above-mentioned custody information can be sent to the custody account terminal of the above-mentioned custody account, so that the custody account terminal can process the custody information. Finally, in response to receiving the feedback information indicating acceptance of custody sent by the above-mentioned custody account terminal, custody processing is performed on the above-mentioned entrusted sub-account. Here, because the statuses of both the entrusted sub-account and the custody account are detected, nested custody of accounts is prevented. Also because nested custody of accounts is prevented, the possibility of account information leakage is reduced.

[0061] Further referring to Figure 3 , some other embodiments of the account processing method according to the present disclosure are shown. The account processing method includes the following steps:

[0062] Step 301, in response to receiving a custody request for a corresponding entrusted account sent by an entrusted account terminal, obtain custody information corresponding to the above-mentioned entrusted account.

[0063] Step 302, detect whether the account status of the above-mentioned entrusted sub-account is an idle state, and whether the account status of the above-mentioned custody account is an un-custody state.

[0064] Step 303: In response to detecting that the account status of the above-mentioned entrusted sub-account is the idle status and the account status of the above-mentioned trustee account is the un-trustee status, send the above-mentioned trusteeship information to the trustee account terminal of the above-mentioned trustee account.

[0065] In some embodiments, for the specific implementation of steps 301-303 and the resulting technical effects, reference may be made to Figure 2 steps 201-203 in the corresponding embodiments, which will not be elaborated here.

[0066] Step 304: In response to receiving the feedback information indicating acceptance of trusteeship sent by the above-mentioned trustee account terminal, generate account association information based on the above-mentioned trustee account and the above-mentioned entrusted sub-account.

[0067] In some embodiments, in response to receiving the feedback information indicating acceptance of trusteeship sent by the above-mentioned trustee account terminal, based on the above-mentioned trustee account and the above-mentioned entrusted sub-account, the execution subject of the account processing method (e.g., Figure 1 the computing device 101 shown) may generate account association information through the following steps:

[0068] First step: In response to receiving the first trusteeship instruction sent by the above-mentioned trustee account terminal, perform an association process on the above-mentioned trustee account and the above-mentioned entrusted sub-account to generate account association information. Here, the first trusteeship instruction may be an instruction specifying that the above-mentioned trustee account trustees the above-mentioned entrusted sub-account. Here, the association process may refer to a concatenation process. In practice, the above-mentioned execution subject may perform a concatenation process on the above-mentioned trustee account and the above-mentioned entrusted sub-account to generate account association information. For example, the above-mentioned execution subject may perform a concatenation process on the above-mentioned trustee account [135XXXX2312] and the above-mentioned entrusted sub-account [135XXXX9840] to generate the account association information [135XXXX2312]-[135XXXX9840].

[0069] Second step: In response to receiving the second trusteeship instruction sent by the above-mentioned trustee account terminal, perform an association process on the trustee sub-account of the above-mentioned trustee account and the above-mentioned entrusted sub-account to generate account association information. Here, the second trusteeship instruction may be an instruction specifying that the above-mentioned trustee sub-account trustees the above-mentioned entrusted sub-account. Here, the trustee sub-account of the above-mentioned trustee account may refer to the sub-account of the above-mentioned trustee account created by the above-mentioned trustee account terminal for trusteeship of the above-mentioned entrusted sub-account. Here, the association process may refer to a concatenation process.

[0070] Optionally, before generating the account association information based on the above-mentioned trustee account and the above-mentioned entrusted sub-account, the method further includes: setting the account status of the above-mentioned entrusted sub-account to the trusteeship status.

[0071] In some embodiments, the above-mentioned execution entity may set the account status of the above-mentioned entrusted sub-account to the entrusted status. Here, the entrusted status may indicate that the above-mentioned entrusted sub-account is successfully entrusted.

[0072] Step 305, store the above-mentioned account association information in the local database.

[0073] In some embodiments, the above-mentioned execution entity may store the above-mentioned account association information in the local database.

[0074] Step 306, in response to detecting the operation information indicating the selection of the above-mentioned entrusted sub-account sent by the above-mentioned entrusted account terminal, determine whether there is account association information corresponding to the above-mentioned entrusted account and the above-mentioned entrusted sub-account in the local database.

[0075] In some embodiments, the above-mentioned execution entity may, in response to detecting the operation information indicating the selection of the above-mentioned entrusted sub-account sent by the above-mentioned entrusted account terminal, determine whether there is account association information corresponding to the above-mentioned entrusted account and the above-mentioned entrusted sub-account in the local database. Here, the operation information indicating the selection of the above-mentioned entrusted sub-account may refer to the operation information for entrusting the above-mentioned entrusted sub-account (for example, the user clicks the control for entrusting the above-mentioned entrusted sub-account on the above-mentioned entrusted account terminal). In practice, the above-mentioned execution entity may determine whether the local database stores the account association information including the above-mentioned entrusted account and the above-mentioned entrusted sub-account.

[0076] Step 307, in response to determining the existence, generate a temporary token corresponding to the above-mentioned entrusted sub-account, and send the above-mentioned temporary token to the above-mentioned entrusted account terminal.

[0077] In some embodiments, in response to determining the existence, the above-mentioned execution entity may generate a temporary token corresponding to the above-mentioned entrusted sub-account, and send the above-mentioned temporary token to the above-mentioned entrusted account terminal. Here, the temporary token may refer to a temporary security token. For example, the temporary token may refer to a Security Token. Here, the temporary token may refer to the password for logging in to the above-mentioned entrusted sub-account within a preset duration, and the permission to operate the above-mentioned entrusted sub-account is set.

[0078] Step 308, in response to detecting the operation information indicating the selection of the above-mentioned entrusted sub-account and the above-mentioned temporary token sent by the above-mentioned entrusted account terminal within a preset duration, perform the entrusting process on the above-mentioned entrusted sub-account.

[0079] In some embodiments, the above-mentioned execution entity may, in response to detecting, within a preset time period, operation information sent by the above-mentioned entrusted account terminal indicating the selection of the above-mentioned entrusted sub-account and the above-mentioned temporary token, perform an entrustment process on the above-mentioned entrusted sub-account. Here, detecting the operation information sent by the above-mentioned entrusted account terminal indicating the selection of the above-mentioned entrusted sub-account and the above-mentioned temporary token may refer to the login information of the above-mentioned entrusted account terminal logging in to the above-mentioned entrusted sub-account through the above-mentioned temporary token.

[0080] In practice, the above-mentioned execution entity may perform an entrustment process on the above-mentioned entrusted sub-account through the following steps:

[0081] First step, in response to receiving the target entrusted sub-account sent by the above-mentioned entrusted account terminal for entrusting the above-mentioned entrusted sub-account, associate the above-mentioned entrusted sub-account with the above-mentioned target entrusted sub-account. Here, transfer of entrustment may refer to taking over. That is, the above-mentioned entrusted sub-account may be transferred under the above-mentioned target entrusted sub-account for entrustment. Here, the target entrusted sub-account may refer to the account selected by the above-mentioned entrusted account terminal for taking over multiple entrusted sub-accounts. Here, the association process may refer to splicing process.

[0082] Second step, in response to receiving the operation information sent by the above-mentioned entrusted account terminal indicating the selection of the above-mentioned target entrusted sub-account, send at least one entrusted sub-account corresponding to the target entrusted sub-account to the above-mentioned entrusted account terminal for display. Here, the operation information indicating the selection of the above-mentioned target entrusted sub-account may refer to the login information of logging in to the above-mentioned target entrusted sub-account. In practice, after receiving the operation information sent by the above-mentioned entrusted account terminal indicating the selection of the above-mentioned target entrusted sub-account, the above-mentioned execution entity may send all at least one entrusted sub-account taken over by the target entrusted sub-account to the above-mentioned entrusted account terminal for display.

[0083] From Figure 3 it can be seen that compared with Figure 2 the description of some corresponding embodiments, Figure 3 in some corresponding embodiments, the process 300 can establish an association relationship between the entrusted account and the entrusted sub-account, facilitating subsequent entrustment processing of the entrusted sub-account. In addition, through the generated temporary token, it is not only convenient for the entrusted account terminal to perform a login operation on the above-mentioned entrusted sub-account, but also sets the permission for the entrusted account terminal to operate the above-mentioned entrusted sub-account, preventing the loss or tampering of key information in the entrusted sub-account.

[0084] Further referring to Figure 4 , some other embodiments of the account processing method according to the present disclosure are shown. The account processing method includes the following steps:

[0085] Step 401: In response to receiving a hosting request for a hosted account sent by the terminal of the hosted account, obtain the hosting information corresponding to the above-mentioned hosted account.

[0086] Step 402: Detect whether the account status of the above-mentioned hosted sub-account is the idle state, and detect whether the account status of the above-mentioned hosting account is the unhosted state.

[0087] Step 403: In response to detecting that the account status of the above-mentioned hosted sub-account is the idle state and the account status of the above-mentioned hosting account is the unhosted state, send the above-mentioned hosting information to the terminal of the hosting account of the above-mentioned hosting account.

[0088] Step 404: In response to receiving the feedback information indicating acceptance of hosting sent by the terminal of the above-mentioned hosting account, perform hosting processing on the above-mentioned hosted sub-account.

[0089] In some embodiments, the specific implementation of steps 401-404 and the technical effects brought can refer to Figure 2 Steps 201-204 in the corresponding embodiments, which will not be elaborated here.

[0090] Step 405: In response to receiving the feedback information indicating rejection of hosting sent by the terminal of the above-mentioned hosting account, set the request status of the above-mentioned hosted sub-account to the rejected state, and generate information indicating a rejected hosting request and send it to the terminal of the above-mentioned hosted account.

[0091] In some embodiments, the above-mentioned execution subject can, in response to receiving the feedback information indicating rejection of hosting sent by the terminal of the above-mentioned hosting account, set the request status of the above-mentioned hosted sub-account to the rejected state, and generate information indicating a rejected hosting request and send it to the terminal of the above-mentioned hosted account. Here, the feedback information indicating rejection of hosting can refer to the terminal of the hosting account rejecting to host the above-mentioned hosted sub-account. Here, the rejected state can represent rejecting to host the above-mentioned hosted sub-account.

[0092] From Figure 4 it can be seen that compared with Figure 2 the description of the corresponding some embodiments, Figure 4 the process 400 in the corresponding some embodiments can timely feedback the request status of the current hosted sub-account to the terminal of the hosting account, so that when the request status of the hosted sub-account is the rejected state subsequently, the terminal of the hosted account can re-specify the hosting account.

[0093] Further referring to Figure 5 , as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides some embodiments of an account processing device, and these device embodiments are related to Figure 2corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0094] As Figure 5 shown, the account processing device 500 of some embodiments includes: an acquisition unit 501, a detection unit 502, a sending unit 503, and a trusteeship unit 504. Among them, the acquisition unit 501 is configured to, in response to receiving a trusteeship request for a corresponding entrusted account sent by an entrusted account terminal, acquire trusteeship information corresponding to the above-mentioned entrusted account, where the above-mentioned trusteeship information includes an entrusted sub-account and a trusteeship account for trusteeship of the above-mentioned entrusted sub-account, and the above-mentioned entrusted sub-account is a sub-account of the above-mentioned entrusted account established by the above-mentioned entrusted account terminal; the detection unit 502 is configured to detect whether the account status of the above-mentioned entrusted sub-account is an idle state, and detect whether the account status of the above-mentioned trusteeship account is an un-trusteeship state; the sending unit 503 is configured to, in response to detecting that the account status of the above-mentioned entrusted sub-account is an idle state and the account status of the above-mentioned trusteeship account is an un-trusteeship state, send the above-mentioned trusteeship information to the trusteeship account terminal of the above-mentioned trusteeship account; the trusteeship unit 504 is configured to, in response to receiving feedback information indicating acceptance of trusteeship sent by the above-mentioned trusteeship account terminal, perform trusteeship processing on the above-mentioned entrusted sub-account.

[0095] Optionally, before the trusteeship unit 504, the device 500 further includes: a generation unit configured to generate account association information based on the above-mentioned trusteeship account and the above-mentioned entrusted sub-account; a storage unit configured to store the above-mentioned account association information in a local database.

[0096] Optionally, the trusteeship unit 504 is further configured to: in response to detecting operation information indicating selection of the above-mentioned entrusted sub-account sent by the above-mentioned trusteeship account terminal, determine whether there is account association information corresponding to the above-mentioned trusteeship account and the above-mentioned entrusted sub-account in the local database; in response to determining that there is, generate a temporary token corresponding to the above-mentioned entrusted sub-account, and send the above-mentioned temporary token to the above-mentioned trusteeship account terminal; in response to detecting operation information indicating selection of the above-mentioned entrusted sub-account and the above-mentioned temporary token sent by the above-mentioned trusteeship account terminal within a preset duration, perform trusteeship processing on the above-mentioned entrusted sub-account.

[0097] Optionally, the trusteeship unit 504 is further configured to: in response to receiving a target entrusted sub-account for transferring and entrusting the above-mentioned entrusted sub-account sent by the above-mentioned trusteeship account terminal, perform an association process on the above-mentioned entrusted sub-account and the above-mentioned target entrusted sub-account; in response to receiving operation information indicating selection of the above-mentioned target entrusted sub-account sent by the above-mentioned trusteeship account terminal, send at least one entrusted sub-account corresponding to the above-mentioned target entrusted sub-account to the above-mentioned trusteeship account terminal for display.

[0098] Optionally, the generating unit is further configured to: in response to receiving the first hosting instruction sent by the above-mentioned hosted account terminal, associate the above-mentioned hosted account with the above-mentioned sub-account to be hosted, so as to generate account association information.

[0099] Optionally, the generating unit is further configured to: in response to receiving the second hosting instruction sent by the above-mentioned hosted account terminal, associate the hosted sub-account of the above-mentioned hosted account with the above-mentioned sub-account to be hosted, so as to generate account association information.

[0100] Optionally, before the generating unit, the apparatus 500 further includes: a setting unit configured to set the account status of the above-mentioned sub-account to be hosted to a hosted status.

[0101] Optionally, the apparatus 500 further includes: a first rejection setting unit configured to, in response to determining that the account status of the above-mentioned sub-account to be hosted is a working status, set the request status of the above-mentioned sub-account to be hosted to a rejected status; a second rejection setting unit configured to, in response to the account status of the above-mentioned hosted account being a hosted status, set the request status of the above-mentioned sub-account to be hosted to a rejected status.

[0102] Optionally, the apparatus 500 further includes: a rejection setting unit configured to, in response to receiving the feedback information indicating rejection of hosting sent by the above-mentioned hosted account terminal, set the request status of the above-mentioned sub-account to be hosted to a rejected status, and generate information indicating a request for rejection of hosting and send it to the above-mentioned hosted account terminal.

[0103] It can be understood that the various units described in the apparatus 500 correspond to the respective steps in the method described with reference to Figure 2 Therefore, the operations, features, and beneficial effects described above for the method also apply to the apparatus 500 and the units included therein, and will not be repeated here.

[0104] Next, with reference to Figure 6 , which shows a schematic structural diagram of an electronic device (such as Figure 1 the computing device 101 in Figure 6 600) suitable for implementing some embodiments of the present disclosure. The electronic devices in some embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), etc., and fixed terminals such as digital TVs, desktop computers, etc.

[0105] As shown in Figure 6As shown, the electronic device 600 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0106] Generally, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or wiredly to exchange data. Although Figure 6 the electronic device 600 with various devices is shown, it should be understood that it is not required to implement or have all the shown devices. Instead, more or fewer devices may be implemented or had. Figure 6 Each block shown in the figure may represent one device or, as needed, multiple devices.

[0107] In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program codes for performing the methods shown in the flowcharts. In such some embodiments, the computer program may be downloaded and installed from a network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the methods of some embodiments of the present disclosure are executed.

[0108] It should be noted that the computer-readable media described in some embodiments of the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0109] In some embodiments, the client and the server can communicate using any currently known or future-developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed network.

[0110] The above computer-readable medium may be included in the above electronic device; or it may exist independently and not be assembled into the electronic device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by the electronic device, the electronic device is caused to: in response to receiving a hosting request for a hosted account corresponding to the hosted account terminal, obtain hosting information corresponding to the hosted account, where the hosting information includes a hosted sub-account and a hosting account for hosting the hosted sub-account, and the hosted sub-account is a sub-account of the hosted account established by the hosted account terminal; detect whether the account status of the hosted sub-account is an idle status and whether the account status of the hosting account is an unhosted status; in response to detecting that the account status of the hosted sub-account is an idle status and the account status of the hosting account is an unhosted status, send the hosting information to the hosting account terminal of the hosting account; and in response to receiving feedback information indicating acceptance of hosting sent by the hosting account terminal, perform hosting processing on the hosted sub-account.

[0111] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++; and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0113] The units described in some embodiments of the present disclosure can be implemented in software or in hardware. The described units can also be provided in a processor. For example, it can be described as: a processor includes an acquisition unit, a detection unit, a sending unit, and a hosting unit. Among them, the names of these units do not constitute a limitation on the unit itself in some cases. For example, the detection unit can also be described as "the unit for determining whether the account status of the above-mentioned hosted sub-account is an idle state and determining whether the account status of the above-mentioned hosting account is an un-hosted state".

[0114] The functions described above can be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on Chip (SOCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0115] The above description is only some preferred embodiments of the present disclosure and an explanation of the technical principles applied. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, technical solutions formed by mutually replacing the above features with technical features having similar functions (but not limited to) disclosed in the embodiments of the present disclosure.

Claims

1. An account processing method, including: Upon receiving a hosting request for a hosted account sent by a hosted account terminal, obtaining hosting information corresponding to the hosted account, where the hosting information includes a hosted sub-account and a hosting account for hosting the hosted sub-account, and the hosted sub-account is a sub-account of the hosted account established by the hosted account terminal; Detecting whether the account status of the hosted sub-account is an idle status, and detecting whether the account status of the hosting account is an unhosted status; Upon detecting that the account status of the hosted sub-account is an idle status and the account status of the hosting account is an unhosted status, sending the hosting information to the hosting account terminal of the hosting account; Upon receiving feedback information sent by the hosting account terminal indicating acceptance of hosting, performing hosting processing on the hosted sub-account.

2. The method according to claim 1, wherein, before performing the hosting processing on the hosted sub-account, the method further includes: generating account association information based on the hosting account and the hosted sub-account; storing the account association information in a local database.

3. The method according to claim 2, wherein, the performing hosting processing on the hosted sub-account includes: Upon detecting operation information sent by the hosting account terminal indicating selection of the hosted sub-account, determining whether there is account association information corresponding to the hosting account and the hosted sub-account in the local database; Upon determining the existence, generating a temporary token corresponding to the hosted sub-account, and sending the temporary token to the hosting account terminal; Upon detecting operation information sent by the hosting account terminal indicating selection of the hosted sub-account and the temporary token within a preset time period, performing hosting processing on the hosted sub-account.

4. The method according to claim 3, wherein, the performing hosting processing on the hosted sub-account includes: Upon receiving a target hosted sub-account sent by the hosting account terminal for transferring hosting of the hosted sub-account, performing an association process between the hosted sub-account and the target hosted sub-account; Upon receiving operation information sent by the hosting account terminal indicating selection of the target hosted sub-account, sending at least one hosted sub-account corresponding to the target hosted sub-account to the hosting account terminal for display.

5. The method according to claim 2, wherein, the generating account association information based on the hosting account and the hosted sub-account includes: Upon receiving a first hosting instruction sent by the hosting account terminal, performing an association process between the hosting account and the hosted sub-account to generate account association information.

6. The method according to claim 2, wherein, the generating account association information based on the hosting account and the hosted sub-account includes: In response to receiving the second trusteeship instruction sent by the trusteeship account terminal, associate the trusteeship sub-account of the trusteeship account with the sub-account to be entrusted to generate account association information.

7. The method according to claim 2, wherein, before generating the account association information based on the trusteeship account and the sub-account to be entrusted, the method further includes: Set the account status of the sub-account to be entrusted to the trusteeship status.

8. The method according to claim 1, wherein, the method further includes: In response to determining that the account status of the sub-account to be entrusted is the working status, set the request status of the sub-account to be entrusted to the rejected status; In response to the account status of the trusteeship account being the trusteeship status, set the request status of the sub-account to be entrusted to the rejected status.

9. The method according to claim 1, wherein, the method further includes: In response to receiving the feedback information indicating the rejection of trusteeship sent by the trusteeship account terminal, set the request status of the sub-account to be entrusted to the rejected status, and generate information indicating the rejection of the trusteeship request and send it to the terminal of the sub-account to be entrusted.

10. An account processing device, including: An acquisition unit configured to, in response to receiving a trusteeship request for a corresponding sub-account to be entrusted sent by a trusteeship account terminal, acquire trusteeship information for the corresponding sub-account to be entrusted, where the trusteeship information includes a sub-account to be entrusted and a trusteeship account for trusteeship of the sub-account to be entrusted, and the sub-account to be entrusted is a sub-account of the sub-account to be entrusted established by the trusteeship account terminal; A detection unit configured to detect whether the account status of the sub-account to be entrusted is the idle status, and detect whether the account status of the trusteeship account is the un-trusteeship status; A sending unit configured to, in response to detecting that the account status of the sub-account to be entrusted is the idle status and the account status of the trusteeship account is the un-trusteeship status, send the trusteeship information to the trusteeship account terminal of the trusteeship account; A trusteeship unit configured to, in response to receiving the feedback information indicating acceptance of trusteeship sent by the trusteeship account terminal, perform trusteeship processing on the sub-account to be entrusted.

11. An electronic device, including: One or more processors; A storage device having stored thereon one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-9.

12. A computer-readable medium having stored thereon a computer program, wherein, when the program is executed by a processor, it implements the method according to any one of claims 1-9.

Images