WO2024077780A1 - 交易账户的数据管理方法、装置、电子设备及存储介质 - Google Patents

交易账户的数据管理方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2024077780A1
WO2024077780A1 PCT/CN2022/141648 CN2022141648W WO2024077780A1 WO 2024077780 A1 WO2024077780 A1 WO 2024077780A1 CN 2022141648 W CN2022141648 W CN 2022141648W WO 2024077780 A1 WO2024077780 A1 WO 2024077780A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
information
authorization
target
institution
Prior art date
Application number
PCT/CN2022/141648
Other languages
English (en)
French (fr)
Inventor
黄嘉豪
王峰
周沁薇
韩翔辉
Original Assignee
深圳市富途网络科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市富途网络科技有限公司 filed Critical 深圳市富途网络科技有限公司
Publication of WO2024077780A1 publication Critical patent/WO2024077780A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/06—Asset management; Financial planning or analysis

Definitions

  • the present application belongs to the field of computer technology, and in particular, relates to a data management method, device, electronic device and storage medium for a transaction account.
  • Institutional clients such as large asset clients, trusts, family offices, and asset management companies in the market all have the desire to manage their assets through account authorization when using brokerage trading software.
  • relevant personnel need to deliberately use more complex query operations to distinguish the authorization status of the accounts available for selection, resulting in low account data management efficiency, which in turn leads to low transaction efficiency.
  • the embodiment of the present application provides an implementation scheme different from the related art to solve the technical problem in the related art that when an institution conducts a transaction, the relevant personnel of the institution need to deliberately use more complex query operations to distinguish the authorization status of the accounts for selection, which causes the transaction process to consume a lot of time and the account data management efficiency is low.
  • the present application provides a transaction account data management method, applied to a terminal device, comprising:
  • the first server When receiving the first account data fed back by the first server in response to the account data acquisition request, caching the first account data, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a corresponding account list is generated according to the first account data, wherein the account list includes a plurality of account identifiers corresponding to the plurality of account information, and the account identifiers are used to indicate categories of the corresponding account information;
  • the account list is displayed.
  • the present application provides a data processing method, applied to a first server, comprising:
  • the account data acquisition request is sent by the terminal device to the first server when the terminal device detects that a user starts a target application in the terminal device, and the account data acquisition request includes the institutional account information of an institution that has logged into the target application;
  • the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • the first account data is fed back to the terminal device, so that when the terminal device obtains a control instruction for controlling the display of the account list triggered by the user through the target page in the target application, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information.
  • the present application provides a data management device for a transaction account, applied to a terminal device, comprising:
  • a first sending module configured to send an account data acquisition request to a first server when detecting that a user starts a target application in a terminal device, wherein the account data acquisition request includes the institution account information of an institution that has logged into the target application;
  • a first cache module configured to cache the first account data when receiving the first account data fed back by the first server in response to the account data acquisition request, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a first generating module configured to generate a corresponding account list according to the first account data when a control instruction for controlling the display of the account list is obtained, the account list including a plurality of account identifiers corresponding to the plurality of account information, the account identifiers being used to indicate categories of the corresponding account information;
  • the first display module is used to display the account list.
  • the present application provides a data processing device, applied to a first server, comprising:
  • a first receiving module configured to receive an account data acquisition request sent by a terminal device, wherein the account data acquisition request is sent by the terminal device to the first server when the terminal device detects that a user starts a target application in the terminal device, and the account data acquisition request includes the institutional account information of an institution that has logged into the target application;
  • a determination module configured to determine corresponding first account data according to the institution account information in the account data acquisition request and a preset correspondence relationship, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a feedback module feeds back the first account data to the terminal device, so that when the terminal device obtains a control instruction for controlling the display of the account list triggered by the user through the target page in the target application, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information.
  • the present application provides an electronic device, including:
  • a memory configured to store executable instructions of the processor
  • the processor is configured to execute any method in the first aspect or any possible implementation of the first aspect, or any method in the second aspect or any possible implementation of the second aspect by executing the executable instructions.
  • an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the computer program implements any method in the first aspect or any possible implementation scheme of the first aspect, or the second aspect or any method in any possible implementation scheme of the second aspect.
  • an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements any method described in the first aspect or any possible implementation of the first aspect, or any method described in the second aspect or any possible implementation of the second aspect.
  • the solution provided by the present application can send an account data acquisition request to the first server when detecting that the user starts the target application in the terminal device, and the account data acquisition request includes the institutional account information of the institution that has logged into the target application; when receiving the first account data fed back by the first server in response to the account data acquisition request, cache the first account data, and the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution; when obtaining the control instruction for controlling the display of the account list triggered by the user through the target page in the target application, generate a corresponding account list according to the first account data, and the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information; display the account list.
  • the account list includes multiple account identifiers corresponding to the multiple account information used to indicate the category of the corresponding account information, when conducting transactions, the relevant personnel of the institution can distinguish the authorization status of the accounts available for selection through the account list, without the need for more complicated query operations, saving time, and effectively improving the efficiency of account data management and transaction efficiency.
  • FIG1 is a schematic diagram of the structure of a system provided by an exemplary embodiment of the present application.
  • FIG2 is a flow chart of a method for managing transaction account data provided by an exemplary embodiment of the present application
  • FIG3 is a schematic diagram of an institutional account structure provided by an exemplary embodiment of the present application.
  • FIG4 is a schematic diagram of a first data cache process provided by an exemplary embodiment of the present application.
  • FIG5 is a schematic diagram of an ordering page provided by an exemplary embodiment of the present application.
  • FIG6 is a schematic diagram of a flow chart of an account list display provided by an exemplary embodiment of the present application.
  • FIG7 is a schematic diagram of a transaction verification process provided by an exemplary embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of another system provided by an exemplary embodiment of the present application.
  • FIG9 is a schematic diagram of an account system architecture provided by an exemplary embodiment of the present application.
  • FIG10 is a flow chart of a data processing method provided by an exemplary embodiment of the present application.
  • FIG11 is a schematic diagram of the structure of a data management device for a transaction account provided by an exemplary embodiment of the present application.
  • FIG12 is a schematic diagram of the structure of a data processing device provided by an exemplary embodiment of the present application.
  • FIG. 13 is a schematic block diagram of an electronic device provided by an exemplary embodiment of the present application.
  • Institutions in the stock market refer to institutional investors with strong funds, rich experience and professional teams other than individual investors. Institutions include bank financial management, securities companies, investment trust companies, social security funds, public funds, insurance funds, etc. These institutional investors generally have dedicated institutional seats in the securities market because of the large amount of funds they trade.
  • Chain of responsibility pattern also known as the chain of responsibility pattern, in order to avoid coupling the request sender with multiple request handlers, all request handlers are connected into a chain by having the previous object remember the reference of its next object; when a request occurs, the request can be passed along this chain until an object handles it.
  • a securities dealer is a company that engages in securities trading, or a securities company.
  • Institutional clients such as brokerage firms, large asset clients, trusts, family offices, asset management companies, etc. in the market all have the demand to manage assets through account authorization when using brokerage trading software, that is, to authorize their own accounts to one or more other institutions or users for asset management, so that other institutions or users can obtain the right to use the authorized account.
  • brokerage trading software that is, to authorize their own accounts to one or more other institutions or users for asset management, so that other institutions or users can obtain the right to use the authorized account.
  • the relevant personnel need to deliberately distinguish the authorization status of the account for selection through a more complex query operation, wherein the authorization status includes any of the following: authorization to other users, authorization by other users, more time is consumed in the transaction process, and the account data management efficiency is low.
  • the present application provides a data management method for a trading account, which is used to solve the technical problem that the relevant personnel of the institution need to deliberately distinguish the authorization status of the account for selection through a more complex query operation in the related art, and the transaction process consumes more time, resulting in low efficiency of account data management.
  • Fig. 1 is a schematic diagram of a system structure provided by an exemplary embodiment of the present application.
  • the system may include a terminal device 10 and a first server 20, etc.
  • the terminal device 10 and the first server 20 are connected via a network, such as a wired or wireless network connection.
  • the terminal device 10 is used for:
  • the first server When receiving the first account data fed back by the first server in response to the account data acquisition request, caching the first account data, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a corresponding account list is generated according to the first account data, wherein the account list includes a plurality of account identifiers corresponding to the plurality of account information, and the account identifiers are used to indicate categories of the corresponding account information;
  • the account list is displayed.
  • the first server 20 is used for:
  • the account data acquisition request is sent to the first server when the terminal device 10 detects that a user starts a target application in the terminal device 10, and the account data acquisition request includes the institutional account information of the institution that has logged into the target application;
  • the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • the first account data is fed back to the terminal device 10, so that when the terminal device 10 obtains a control instruction for controlling the display of the account list triggered by the user through the target page in the target application, the terminal device 10 generates a corresponding account list according to the first account data and displays the account list, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information.
  • the terminal device 10 may be a mobile phone, a tablet computer, etc.
  • the terminal device 10 may be used to display a graphical user interface.
  • the terminal device is used to interact with the user through a graphical user interface, such as downloading and installing a corresponding client and running it through the terminal device, such as calling a corresponding application and running it, such as presenting a corresponding graphical user interface by logging into a website, etc.
  • the first server 20 may be a single server, a server cluster consisting of multiple servers, or a cloud platform control center, which is not limited in the present embodiment of the application.
  • FIG2 is a flow chart of a method for managing transaction account data provided by an exemplary embodiment of the present application.
  • the method is applicable to the aforementioned terminal device 10. As shown in FIG2 , the method at least includes the following steps S201-S204:
  • an account data acquisition request is sent to a first server, where the account data acquisition request includes the institutional account information of the institution that has logged into the target application.
  • the user starts the target application by clicking an icon of the target application on the terminal device.
  • the user is an administrator for managing institutional accounts in an institution (such as a securities firm). Institutions often manage more investment categories. In order to facilitate sub-warehouse management, multiple accounts will be opened (for example: investment managers use different accounts to execute different investment portfolio strategies).
  • the administrator has management authority and trading authority over all accounts under the institutional account. Among them, trading authority refers to the use of funds in the account for investment business such as fund purchase, and management authority refers to the management of the structure of the institutional account.
  • Figure 3 is a schematic diagram of an institutional account structure provided by an exemplary embodiment of the present application. As shown in Figure 3, the structure is divided into an Internet account layer and an institutional account layer.
  • the Internet account layer includes an administrator and multiple users, and the users are traders or back-end staff added by the administrator.
  • the institutional account layer includes multiple accounts: account 1, account 2, account 3 and account 4. Among them, account 1 corresponds to user A, account 2 and account 3 correspond to user B, and account 4 corresponds to user C. For any account, the administrator and the user corresponding to the account have management authority and trading authority over the account.
  • the institutional account also includes a main account, which can be used only for depositing money.
  • the aforementioned administrator can also manage the main account.
  • Step 1 Obtain the position information of the master account, which includes investment categories, amount information corresponding to each investment category, investment target information, and trader information under the jurisdiction of the master account.
  • the holding information of the master account may include the investment categories held in the master account, such as funds and stocks.
  • the investment targets may include the names and logos of the stocks.
  • the trader information may include the account information responsible for maintaining the resources held by the master account. In addition, it may also include the trading region corresponding to the trading target.
  • Step 2 Based on the position information, determine the number of associated accounts corresponding to the master account, and generate associated accounts according to the number of accounts.
  • the number of associated accounts corresponding to the master account Acc_v is determined as follows:
  • ⁇ represents the account factor
  • i represents the identifier corresponding to the investment category
  • i and k are natural numbers greater than 1.
  • Step 3 Based on the account data and the position information, update the position information in the master account and the associated account respectively.
  • the above-mentioned institutional account information may include at least one of the following: the name of the institution, an identifier that uniquely identifies the institution (such as a unified social credit code), and a device identification number of a device logged in by the institutional account.
  • the account data request is used to obtain account data under the current institution account.
  • the first account data is cached, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution.
  • the account information may include an account identifier, basic information of the account owner (eg, account number identifier), the amount in the account, and historical transaction data of the account.
  • Account 1, Account 2 and Account 3 are opened by the institution account through the multi-account function, and have a subordinate relationship with the institution account, that is, Account 1, Account 2 and Account 3 are the first account information included in the first account data of the institution;
  • Account 4 can be entrusted to the institution by the second target object (such as the institution's customer), and has a dependent relationship with the institution account, that is, Account 4 is the third account information included in the first account data of the institution.
  • the aforementioned relationship between the institutional account and the multiple accounts included in the aforementioned institutional account layer may also refer to the relationship between the master account and the multiple accounts.
  • the aforementioned administrator may be the actual owner of the master account and may also be a trustee.
  • FIG4 is a schematic diagram of the cache process of the first account data provided by an exemplary embodiment of the present application.
  • the terminal device may include a transaction module and an account data warehouse.
  • the terminal device calls the first account data acquisition interface in the account data warehouse through the transaction module, generates a network protocol request according to the account data warehouse, and sends a network protocol request to the first server, that is, an account data acquisition request.
  • the first server determines the corresponding first account data according to the institutional account information in the account data acquisition request and the preset correspondence relationship, and feeds back the first account data corresponding to the institutional account information to the account data warehouse.
  • the account data warehouse receives and caches the first account data.
  • the preset correspondence relationship may include: an affiliation relationship, a subordinate relationship, and a delegation relationship.
  • the affiliation relationship is used to indicate the second correspondence relationship
  • the delegation relationship is used to indicate the first correspondence relationship.
  • a corresponding account list is generated according to the first account data, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifiers are used to indicate the category of the corresponding account information; optionally, the account identifiers correspond to the account information one-to-one, and the multiple account identifiers include: an account identifier corresponding to the first account information, an account identifier corresponding to the second account information, and an account identifier corresponding to the third account information.
  • the target page is an order page.
  • FIG5 is a schematic diagram of an order page provided by an exemplary embodiment of the present application.
  • the user can select a target account and a purchase amount through the order page.
  • the top of the order page is provided with a return button, a page name “Order”, and a rule viewing button with the words “Buy Rules” displayed.
  • the order page also includes a payment account column, a product name column, and a purchase amount column.
  • the payment account column displays the words “Payment Account” and the target account selected by the user
  • the product name column displays the words “Product Name”, as well as the name of the project currently being traded, such as “XX Fund”, and the basic information of the project, such as “7-day annualized +2.5524%”
  • the purchase amount column displays the words “Purchase Amount” and the transaction currency, such as “USD”, which means US dollars.
  • the purchase amount column also includes an amount input box. When the user does not enter the amount in the amount input box, the amount input box displays an amount input prompt message, such as “0.01 USD”, which is used to remind the user to enter an amount greater than 0.01.
  • the user can trigger the control instruction of controlling the display of the account list by clicking the above payment account column area, and the account list can be displayed in the account selection pop-up window, and the account selection pop-up window can be displayed in the lower area of the order page.
  • the upper area of the account selection pop-up window is provided with a close button and an account selection pop-up window title with the words "Select Payment Account”, and the target application name is displayed below the close button, and the area below the target application name is the account list.
  • Figure 6 is a flow chart of displaying an account list provided by an exemplary embodiment of the present application.
  • the terminal device executes the page display callback function, displays the account selection pop-up window, and enables the page controller to obtain the first account data from the account data warehouse, generate the corresponding account list according to the first account data, and display the account list in the above-mentioned account selection pop-up window through the order page.
  • the account information also includes an account icon, account suffix information, and balance prompt information of each account.
  • account suffix information For example, in the account list in FIG5, "Comprehensive Account (0679)” and “Comprehensive Account (2013)” are account suffix information, “Own Account” (indicating the first account information) and “Delegated Account (indicating the second account information)” are account identifiers, and the balance prompt information of the corresponding account is displayed below the account suffix information: "Cash Available USD 35.00", "Cash Available USD 1,372.61".
  • the account list may also include a selection mark, which is displayed on the right side of the account mark corresponding to the target account selected by the user.
  • the target page may also be an organization information page for displaying detailed information of the organization.
  • the organization information page may display a view button with the words "account list", and the user may trigger a control instruction for controlling the display of the account list by clicking the view button.
  • an account data acquisition request is sent to the first server, and the account data acquisition request includes the institutional account information of the institution that has logged into the target application; when the first account data fed back by the first server in response to the account data acquisition request is received, the first account data is cached, and the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution; when a control instruction for controlling the display of an account list is obtained, which is triggered by the user through the target page in the target application, a corresponding account list is generated according to the first account data, and the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the account information to which it corresponds, and the account list is displayed.
  • the relevant personnel of the institution can distinguish the authorization status of the accounts to be selected through the account list, without the need for more complicated query operations, saving time, and effectively improving the efficiency of account data management.
  • the method further includes steps S301-S304:
  • S302 When receiving the second account data fed back by the first server in response to the account data acquisition request, cache the second account data, where the second account data is the refreshed first account data.
  • a refresh button may be displayed on the target page, and the account data refresh request is used to obtain the latest account data under the current account of the institution.
  • a refresh button may also be provided in the account list, so that the user can refresh the account list when viewing the account list to obtain the latest account data (second account data).
  • the multiple account information included in the account list can be sorted according to a preset priority. The higher the priority, the higher the ranking. The highest priority is the preferred account data. The preferred account data is displayed first in the current brokerage firm and business scenario.
  • the account list also includes fake account data.
  • a fake account is an account that has not been opened by the current institutional account.
  • the fake account is displayed in the account list, which can guide users to open more accounts to increase the account opening rate.
  • the method further includes steps S401-S402:
  • transaction verification is performed to obtain a verification result, including steps S4011-S4012:
  • S4011 Determine whether the user has selected a target account for the current transaction. If so, determine whether the target account is the account corresponding to the first account data. If so, determine whether the target amount entered by the user is greater than a preset minimum amount. If so, determine whether the target amount is less than or equal to the balance in the target account. If so, determine that the verification result is successful.
  • the verification result is determined to be verification failure.
  • FIG7 is a schematic diagram of the transaction verification process provided by an exemplary embodiment of the present application.
  • the transaction verification responsibility chain may include a first node, a second node, a third node, and a fourth node, which respectively perform the following four transaction steps of transaction verification:
  • Step 1 Target account verification, i.e., determining whether the user has selected the target account.
  • Target account verification i.e., determining whether the user has selected the target account.
  • the right area of the payment account column in FIG. 5 above will display the account number information of the target account.
  • the right area of the payment account column is blank. If the user has not selected the target user, the verification result is determined to be a verification failure. If the user has selected the target account, the second node is entered to execute step 2.
  • Step 2 Target account authority verification, i.e., determining whether the target account is the account corresponding to the first account data. In other words, determining whether the target account selected by the user is an account for which the user has management authority and transaction authority. If the target account is not the account corresponding to the first account data, the verification result is determined to be a verification failure. If the target account is the account corresponding to the first account data, the process proceeds to the third node and executes step 3.
  • Step 3 Verify the input amount, i.e., determine whether the target amount input by the user is not less than the preset minimum amount.
  • the preset minimum amount is the minimum amount allowed for the transaction, for example, the preset minimum amount can be 0.01. If the target amount input by the user is less than the preset minimum amount, the verification result is determined to be a verification failure. If the target amount input by the user is not less than the preset minimum amount, enter the fourth node and execute step 4.
  • Step 4 Target account balance verification, i.e., determining whether the target amount is less than or equal to the balance in the target account. If the target amount is greater than the balance in the target account, the verification result is determined to be a verification failure. If the target amount is less than or equal to the balance in the target account, the verification result is determined to be a verification success.
  • the verification result is returned level by level, that is, the fourth node returns the verification result to the third node, the third node returns the verification result to the second node, and the second node returns the verification result to the first node.
  • the above verification process uses the responsibility chain mode, which can improve code reusability and maintainability.
  • the second server is a server for executing fund transactions.
  • the terminal device can receive the order generation prompt information sent by the second server, and display the transaction password input page to prompt the user to enter the transaction password.
  • the password verification is performed.
  • the transaction is completed, and an account information update request is sent to the first server.
  • the account information update request is used to instruct the first server to update the corresponding data under the target account and the balance of the target account.
  • prompt information corresponding to the node that determines the verification result is displayed according to the node that determines the verification result.
  • the node that determines the verification result is the first node.
  • the first node may correspond to prompt information such as "Please select a payment account”.
  • the method further includes steps S501-S503:
  • S501 Send a first authorization request to the first server, wherein the first authorization request includes the institutional account information, the account information of the first target object, and the first account information to be authorized for applying for authorization to the first target object, and the first authorization request is used to instruct the first server to send a first authorization application to the first device corresponding to the account information of the first target object, and obtain first authorization reply information fed back by the first device for the first authorization application, and generate corresponding first authorization prompt information according to the first authorization reply information.
  • the first authorization request includes the institutional account information, the account information of the first target object, and the first account information to be authorized for applying for authorization to the first target object
  • the first authorization request is used to instruct the first server to send a first authorization application to the first device corresponding to the account information of the first target object, and obtain first authorization reply information fed back by the first device for the first authorization application, and generate corresponding first authorization prompt information according to the first authorization reply information.
  • S502 Receive the first authorization prompt information fed back by the first server, where the first authorization prompt information includes first prompt information for indicating that the authorization is passed, or second prompt information for indicating that the authorization is not passed.
  • FIG8 is a schematic diagram of the structure of another system provided by an exemplary embodiment of the present application, which system may include a terminal device 10, a first server 20, a first device 30, and a second device 40, etc.
  • the terminal device 10, the first device 30, and the second device 40 are respectively connected to the first server 20 through a network, such as a wired or wireless network connection, etc.
  • the terminal device 10, the first device 30, and the second device 40 may be a mobile phone, a laptop computer, and other devices.
  • information interaction between the terminal device 10 , the first device 30 , the second device 40 and other devices may be implemented through the first server 20 .
  • the first server determines the first device corresponding to the first target object according to the account information of the first target object in the first authorization request, determines the first authorization application according to the first authorization request, and sends the first authorization application to the first device, wherein the first authorization request is used by an organization to request that the first account information to be authorized be authorized to other organizations or individuals (first target object), wherein the first account information to be authorized is included in the above-mentioned first account information, the first target object may be a user using the first device, and the first authorization request and the first authorization application may contain the same content.
  • the first server may determine the corresponding first account data according to the institution account information in the account data acquisition request and a preset corresponding relationship.
  • the first server After receiving the first authorization request sent by the terminal device, the first server sends the first authorization application to the first device corresponding to the account information of the first target object according to the first authorization request; after receiving the first authorization application, if the first device detects a reply instruction to the first authorization request triggered by the user, it generates a corresponding first authorization reply information, the first device sends the first authorization reply information to the first server, generates a corresponding first authorization prompt information according to the first authorization reply information, and the first server sends the first authorization prompt information to the terminal device.
  • the first server If the first authorization reply information indicates that the first target object agrees to the first authorization application, the first server generates first prompt information indicating that the first target object agrees to the first authorization application and sends it to the terminal device.
  • first authorization reply information indicates that the first target object does not agree to the first authorization application, it means that the first target object has rejected the agency's entrustment for the first account information to be authorized.
  • the first server can generate a second prompt information indicating that the first target object does not agree to the first authorization application and send it to the terminal device.
  • the first server determines the first account information to be authorized as the second account information, and establishes a first correspondence between the second account information of the institution account and the account information of the first target object, and adds the first correspondence to the preset correspondence.
  • the first correspondence indicates that the institution entrusts its own account information to the first target object, so that the first target object has the management authority and transaction authority over the second account information.
  • the method further includes steps S601-S603:
  • S603 Send the second authorization reply information to the first server, so that the first server generates corresponding second authorization prompt information according to the second authorization reply information, and feeds back the second authorization prompt information to the second device.
  • the second authorization request and the second authorization application may contain the same content.
  • the user may choose to agree or disagree with respect to the account information of the second target object and the second account information to be authorized included in the second authorization request, so that the second device generates second authorization reply information.
  • the second authorization reply information indicates that the institution agrees to the second authorization application
  • the second account information to be authorized is determined to be the third account information
  • the first server can generate a third prompt information for indicating that the institution agrees to the second authorization application, and create a second correspondence between the institution account information and the third account information, and add the second correspondence to the preset correspondence.
  • the second correspondence indicates that the second target object entrusts its own account information to the institution, so that the institution has the management authority and transaction authority over the third account information.
  • the first server can generate a fourth prompt information indicating that the organization does not agree to the second authorization application and send it to the second device.
  • FIG 9 is a structural diagram of the account system architecture provided by an exemplary embodiment of the present application. As shown in Figure 9, the account system architecture is configured with a view application programming interface, a business application programming interface, a basic application programming interface, a data center and a basic module.
  • the second server may further include a risk control server.
  • the institutional account does not issue the asset card on the fund homepage.
  • the account owner is not verified in this application, which cancels the limitation in the related technology that only the account owner is supported to conduct fund transactions, thereby improving data processing efficiency.
  • the view application programming interface includes a payment account column interface and an account selection pop-up window interface, which are respectively used to display the payment account column account selection pop-up window on the order page of the target application.
  • the business application programming interface provides a scenario-based business application programming interface, and provides interface encapsulation for business scenarios, including a preferred account interface, an account-related protocol data interface, and a fake account interface, wherein the account-related protocol data interface is used to obtain the real account list data from the first server.
  • the basic application programming interface includes a creation application programming interface, a general transaction account application programming interface, a transaction account application programming interface, a fund account application programming interface, and a query application programming interface, etc.
  • the basic application programming interface is used to provide encapsulation based on the data center interface, as well as interface encapsulation for different brokerage institutions.
  • the data center provides an interface for obtaining account data (first account data, second account data) externally, and internally implements retrying when acquisition fails and regularly refreshing the request network protocol to ensure the timeliness of account data updates, and solves the scenario of data pulling failure during network jitter, thereby improving the reliability of the interface;
  • the basic modules include a storage module (for providing a storage interface), a database module (for providing a database read and write interface), a network module (for providing a network protocol request interface) and a data structure model.
  • the storage module is used to solve the performance problem of the interface, and the database module is used to adapt to the scenario where data needs to be obtained normally when the network has not returned after the target application is restarted.
  • authorized account-related fields are added to the data structure model, and application programming interfaces and implementations for obtaining authorized accounts are added to the basic application programming interface and business application programming interface, and authorized accounts are added to the view application programming interface, so that authorized accounts (second account information and/or third account information) can be selected and used when conducting transactions such as purchasing funds.
  • FIG. 10 is a flow chart of a data processing method provided by an exemplary embodiment of the present application. The method is applicable to the aforementioned first server 20. As shown in FIG. 10 , the method at least includes the following steps S701-S703:
  • S701 receiving an account data acquisition request sent by a terminal device, wherein the account data acquisition request is sent to the first server when the terminal device detects that a user starts a target application in the terminal device, and the account data acquisition request includes the institutional account information of an institution that has logged into the target application;
  • the institution account information in the account data acquisition request determining corresponding first account data according to the institution account information in the account data acquisition request and a preset correspondence relationship, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • the terminal device Feedback the first account data to the terminal device, so that when the terminal device obtains a control instruction for controlling the display of the account list triggered by the user through the target page in the target application, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information.
  • the data processing method further includes steps S801-S805:
  • S802 Send a first authorization application to a first device corresponding to the account information of a first target object according to the first authorization request;
  • S803 Receive first authorization reply information fed back by the first device in response to the first authorization application
  • the first authorization reply information indicates that the first target object agrees to the first authorization application
  • create a first correspondence between the institution account information and the first account information to be authorized add the first correspondence to the preset correspondence, and generate first prompt information for indicating that the first target object agrees to the first authorization application; and send the first prompt information to the terminal device;
  • first authorization reply information indicates that the first target object does not agree to the first authorization application
  • second prompt information for indicating that the first target object does not agree to the first authorization application
  • FIG11 is a schematic diagram of the structure of a data management device for a transaction account provided by an exemplary embodiment of the present application, the device being applied to a terminal device, comprising:
  • a first sending module configured to send an account data acquisition request to a first server when detecting that a user starts a target application in a terminal device, wherein the account data acquisition request includes the institution account information of an institution that has logged into the target application;
  • a first cache module configured to cache the first account data when receiving the first account data fed back by the first server in response to the account data acquisition request, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a first generating module configured to generate a corresponding account list according to the first account data when a control instruction for controlling the display of the account list is obtained, the account list including a plurality of account identifiers corresponding to the plurality of account information, the account identifiers being used to indicate categories of the corresponding account information;
  • the first display module is used to display the account list.
  • the data management device of the transaction account further includes:
  • a second sending module configured to send an account data refresh request to the first server when a click operation of the user on the refresh button displayed on the target page is obtained;
  • a second cache module configured to cache, when receiving second account data fed back by the first server in response to the account data acquisition request, the second account data being the refreshed first account data;
  • a second generating module configured to generate a corresponding refreshed account list according to the second account data
  • the second display module is used to display the refreshed account list.
  • the data management device for the transaction account further includes:
  • a verification module configured to perform transaction verification and obtain a verification result after detecting that the user has triggered an order button displayed on an order page of the target application
  • the third sending module is used to send a transaction request to the second server when the verification result indicates that the verification is successful, so that the second server generates corresponding order information according to the transaction request.
  • the verification module when used to perform transaction verification and obtain a verification result, it is specifically used to:
  • the verification result is determined to be verification failure.
  • the data management device for the transaction account further includes:
  • a fourth sending module configured to send a first authorization request to the first server, wherein the first authorization request includes the institution account information, the account information of the first target object, and first account information to be authorized for applying for authorization to the first target object, the first authorization request is used to instruct the first server to send a first authorization application to a first device corresponding to the account information of the first target object, obtain first authorization reply information fed back by the first device for the first authorization application, and generate corresponding first authorization prompt information according to the first authorization reply information;
  • a second receiving module used to receive the first authorization prompt information fed back by the first server, where the first authorization prompt information includes first prompt information used to indicate that the authorization is passed, or second prompt information used to indicate that the authorization is not passed;
  • the third display module is used to display the first authorization prompt information.
  • the data management device for the transaction account further includes:
  • a third receiving module is used to receive a second authorization application sent by the first server, where the second authorization application is sent by the first server when receiving a second authorization request sent by a second device corresponding to the second target object, where the second authorization request includes the account information of the institution, the account information of the second target object, and the second account information to be authorized for applying for authorization to the institution;
  • a third generating module is used to generate corresponding second authorization reply information when detecting a reply instruction triggered by the user for the second authorization request;
  • the fifth sending module is used to send the second authorization reply information to the first server, so that the first server generates corresponding second authorization prompt information according to the second authorization reply information, and feeds back the second authorization prompt information to the second device.
  • FIG. 12 is a schematic diagram of the structure of a data processing device provided by an exemplary embodiment of the present application, the device is applied to a first server, and includes:
  • a first receiving module configured to receive an account data acquisition request sent by a terminal device, wherein the account data acquisition request is sent by the terminal device to the first server when the terminal device detects that a user starts a target application in the terminal device, and the account data acquisition request includes the institutional account information of an institution that has logged into the target application;
  • a determination module configured to determine corresponding first account data according to the institution account information in the account data acquisition request and a preset correspondence relationship, wherein the first account data includes multiple account information of at least two categories: the first account information of the institution itself, the second account information authorized by the institution to the first target object, and the third account information authorized by the second target object to the institution;
  • a feedback module feeds back the first account data to the terminal device, so that when the terminal device obtains a control instruction for controlling the display of the account list triggered by the user through the target page in the target application, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list includes multiple account identifiers corresponding to the multiple account information, and the account identifier is used to indicate the category of the corresponding account information.
  • the data processing device further includes:
  • a fourth receiving module configured to receive a first authorization request sent by the terminal device, wherein the first authorization request includes the account information of the institution, the account information of the first target object, and first account information to be authorized for applying for authorization to the first target object;
  • a sixth sending module configured to send a first authorization application to a first device corresponding to the account information of the first target object according to the first authorization request;
  • a fifth receiving module configured to receive first authorization reply information fed back by the first device in response to the first authorization application
  • a creation module configured to, if the first authorization reply information indicates that the first target object agrees to the first authorization application, create a first correspondence between the institution account information and the first account information to be authorized; add the first correspondence to the preset correspondence, and generate first prompt information indicating that the first target object agrees to the first authorization application; and send the first prompt information to the terminal device;
  • the seventh sending module is used to generate second prompt information for indicating that the first target object does not agree to the first authorization application if the first authorization reply information indicates that the first target object does not agree to the first authorization application; and send the second prompt information to the terminal device.
  • the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, no further description is given here.
  • the device may perform the above method embodiment, and the above and other operations and/or functions of each module in the device are the corresponding processes in each method in the above method embodiment, respectively, and no further description is given here for the sake of brevity.
  • the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules.
  • the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and/or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.
  • FIG13 is a schematic block diagram of an electronic device provided in an embodiment of the present application, and the electronic device may include:
  • the memory 1301 and the processor 1302, the memory 1301 is used to store the computer program and transmit the program code to the processor 1302.
  • the processor 1302 can call and run the computer program from the memory 1301 to implement the method in the embodiment of the present application.
  • the processor 1302 may be configured to execute the above method embodiments according to instructions in the computer program.
  • the processor 1302 may include but is not limited to:
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the memory 1301 includes but is not limited to:
  • Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory.
  • the volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link DRAM
  • Direct Rambus RAM Direct Rambus RAM, DR RAM
  • the computer program may be divided into one or more modules, which are stored in the memory 1301 and executed by the processor 1302 to complete the method provided by the present application.
  • the one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.
  • the electronic device may further include:
  • the transceiver 1303 may be connected to the processor 1302 or the memory 1301 .
  • the processor 1302 may control the transceiver 1303 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.
  • the transceiver 1303 may include a transmitter and a receiver.
  • the transceiver 1303 may further include an antenna, and the number of antennas may be one or more.
  • bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.
  • the present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, enables the computer to perform the method of the above method embodiment.
  • the present application embodiment also provides a computer program product containing instructions, which, when executed by a computer, enables the computer to perform the method of the above method embodiment.
  • relevant data such as account information is involved.
  • user permission, consent or authorization is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, a computer, a first server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, first server or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a first server, a data center, etc. that includes one or more available media integrated.
  • the available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a tape
  • an optical medium e.g., a digital video disc (digital video disc, DVD)
  • a semiconductor medium e.g., a solid state drive (solid state disk, SSD)
  • modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the module is only a logical function division.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
  • each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Operations Research (AREA)
  • Finance (AREA)
  • Game Theory and Decision Science (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Technology Law (AREA)
  • Educational Administration (AREA)
  • Data Mining & Analysis (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

公开了一种交易账户的数据管理方法、装置、电子设备及存储介质，应用于终端设备，方法包括：当检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，账户数据获取请求包括已登录目标应用程序的机构的机构账号信息；当接收到第一服务器针对账户数据获取请求反馈的第一账户数据时，对第一账户数据进行缓存；当获取到用户通过目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据第一账户数据生成对应的账户列表，账户列表中包括多个账户信息对应的多个账户标识；展示账户列表。

Description

交易账户的数据管理方法、装置、电子设备及存储介质
相关申请的交叉引用
本申请要求于2022年10月12日提交的，申请名称为“交易账户的数据管理方法、装置、电子设备及存储介质”的、中国专利申请号为“CN202211248985.0”的优先权，该中国专利申请的全部内容通过引用结合在本申请中。
技术领域
本申请属于计算机技术领域，尤其涉及一种交易账户的数据管理方法、装置、电子设备及存储介质。
背景技术
市场上的大资产客户、信托、家族办公室、资产管理公司等机构客户在使用券商交易软件时，均有通过账户授权的方式进行资产管理的诉求。然而，相关技术中，机构在进行交易时，相关人员需特意通过较复杂的查询操作区分供选择的账户的授权情况，账户数据管理效率较低，进而导致交易效率较低的问题。
技术解决方案
本申请实施例提供一种与相关技术不同的实现方案，以解决相关技术中，机构在进行交易时，机构相关人员需特意通过较复杂的查询操作区分供选择的账户的授权情况，导致的交易过程消耗时间较多，账户数据管理效率较低的技术问题。
第一方面，本申请提供一种交易账户的数据管理方法，应用于终端设备，包括：
当检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
展示所述账户列表。
第二方面，本申请提供一种数据处理方法，应用于第一服务器，包括：
接收终端设备发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向所述第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
第三方面，本申请提供一种交易账户的数据管理装置，应用于终端设备，包括：
第一发送模块，用于当检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
第一缓存模块，用于当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
第一生成模块，用于当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
第一展示模块，用于展示所述账户列表。
第四方面，本申请提供一种数据处理装置，应用于第一服务器，包括：
第一接收模块，用于接收终端设备发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
确定模块，用于根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
反馈模块，将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
第五方面，本申请提供一种电子设备，包括：
处理器；以及
存储器，用于存储所述处理器的可执行指令；
其中，所述处理器配置为经由执行所述可执行指令来执行第一方面或第一方面各可能的实施方式中的任一方法，或者，第二方面或第二方面各可能的实施方式中的任一方法。
第六方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现第一方面或第一方面各可能的实施方式中的任一方法，或者，第二方面或第二方面各可能的实施方式中的任一方法。
第七方面，本申请实施例提供一种计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现第一方面或第一方面各可能的实施方式中任一所述的方法，或者，第二方面或第二方面各可能的实施方式中的任一方法。
本申请提供的方案，可通过在检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，账户数据获取请求包括已登录目标应用程序的机构的机构账号信息；当接收到第一服务器针对账户数据获取请求反馈的第一账户数据时，对第一账户数据进行缓存，第一账户数据中包括下述至少两个类别的多个账户信息：机构自身的第一账户信息、机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给机构的第三账户信息；当获取到用户通过目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据第一账户数据生成对应的账户列表，账户列表中包括多个账户信息对应的多个账户标识，账户标识用于指示其对应的账户信息的类别；展 示账户列表。由于账户列表中包括用于指示其对应的账户信息的类别的多个账户信息对应的多个账户标识，在进行交易时，机构相关人员可以通过账户列表区分供选择的账户的授权情况，无需较复杂的查询操作，节省了时间，有效提高账户数据管理效率和交易效率。
附图说明
为了更清楚地说明本申请实施例或相关技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1为本申请一示例性实施例提供的一种系统的结构示意图；
图2为本申请一示例性实施例提供的一种交易账户的数据管理方法的流程示意图；
图3为本申请一示例性实施例提供的一种机构账号结构示意图；
图4为本申请一示例性实施例提供的第一数据缓存流程示意图；
图5为本申请一示例性实施例提供的下单页面的示意图；
图6为本申请一示例性实施例提供的账户列表展示的流程示意图；
图7为本申请一示例性实施例提供的交易校验的流程示意图；
图8为本申请一示例性实施例提供的另一种系统的结构示意图；
图9为本申请一示例性实施例提供的一种账户体系架构示意图；
图10为本申请一示例性实施例提供的一种数据处理方法的流程示意图；
图11为本申请一示例性实施例提供的一种交易账户的数据管理装置的结构示意图；
图12为本申请一示例性实施例提供的一种数据处理装置的结构示意图；
图13是本申请一示例性实施例提供的一种电子设备的示意性框图。
具体实施方式
下面详细描述本申请的实施例，所述实施例的示例在附图中示出。下面通过参考附图描述的实施例是示例性的，旨在用于解释本申请，而不能理解为对本申请的限制。
本申请实施例的说明书、权利要求书及附图中的术语“第一”和“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请实施例的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
首先，下面对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
股市中的机构是指除了个人投资者以外的拥有雄厚资金、丰富经验和专业团队的机构投资者。机构包括银行理财、证券公司，投资信托公司，社保基金、公募基金、保险资金等。这些机构投资者由于交易的资金量很大，一般都在证券市场拥有专用机构席位。
职责链模式：又名责任链模式，为了避免请求发送者与多个请求处理者耦合在一起，将所有请求的处理者通过前一对象记住其下一个对象的引用而连成一条链；当有请求发生时，可将请求沿着这条链传递，直到有对象处理它为止。
券商，即经营证券交易的公司，或称证券公司。
市场上的券商、大资产客户、信托、家族办公室、资产管理公司等机构客户在使用券商交易软件时，均有通过账户授权的方式进行资产管理的诉求，即将自己的账户授权给一个或者多个其他机构或者用户的进行资产管理，以使其他机构或用户获得授权账户的使用权限。然而，相关技术中，机构在进行交易时，相关人员需特意通过较复杂的查 询操作区分供选择的账户的授权情况，其中，授权情况包括以下任一种：授权给其他用户、被其他用户授权，交易过程中消耗时间较多，账户数据管理效率较低。因此，本申请提供了一种交易账户的数据管理方法，用于解决相关技术中，机构相关人员需特意通过较复杂的查询操作区分供选择的账户的授权情况，交易过程消耗时间较多，导致的账户数据管理效率较低的技术问题。
下面以具体的实施例对本申请的技术方案以及本申请的技术方案如何解决上述技术问题进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。下面将结合附图，对本申请的实施例进行描述。
图1为本申请一示例性实施例提供的一种系统的结构示意图。该系统可以包括终端设备10和第一服务器20等；终端设备10和第一服务器20之间通过网络连接，比如，通过有线或无线网络连接等。
终端设备10，用于：
当检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
展示所述账户列表。
第一服务器20，用于：
接收终端设备10发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备10检测到用户启动所述终端设备10中的目标应用程序时，向所述第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
将所述第一账户数据反馈至所述终端设备10，使所述终端设备10在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
其中，终端设备10可以为能手机、平板电脑等。终端设备10，可以用于显示图形用户界面。其中，该终端设备用于通过图形用户界面与用户进行交互，例如通过终端设备下载安装相应的客户端并运行，例如通过调用相应的应用程序并运行，例如通过登录网站呈现相应的图像用户界面等。第一服务器20可以是一台服务器，也可以是由多台服务器组成的服务器集群，还可以是云平台控制中心，本申请实施例对此不做限定。
本系统实施例中具体的执行原理及交互过程可参见如下各方法实施例的描述。
图2为本申请一示例性实施例提供的一种交易账户的数据管理方法的流程示意图，该方法适用于前述终端设备10，如图2所示，该方法至少包括以下步骤S201-S204：
S201、当检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息。
可选地，用户通过点击终端设备上目标应用程序的图标启动该目标应用程序。
可选地，用户为机构(如券商机构)中用于管理机构账号的管理员，机构往往会管理比较多的投资品类，为了便于分仓管理，会开设多个账户(例如：投资经理使用不同账户去执行不同的投资组合策略)，管理员具有对机构账号下所有账户的管理权限与交易权限。其中，交易权限指的是使用账户内的资金进行基金购买等投资业务，管理权限指的是对机构账号的结构进行管理，图3为本申请一示例性实施例提供的一种机构账号结构示意图，如图3所示，该结构分为互联网账号层和机构账户层，互联网账号层包括管理员与多个使用者，使用者为管理员添加的交易员或者后台职员。机构账户层包括多个账户：账户1、账户2、账户3和账户4。其中，账户1对应使用者A，账户2和账户3对应使用者B，账户4对应使用者C，针对任一个账户，管理员和该账户对应的使用者均具有对该账户的管理权限及交易权限。
可选地，参见图3所示，机构账号下还包括主账户，主账户可仅用于存钱。前述管理员还可对主账户进行管理。
进一步的，在本申请一实施例中，在主账户设立之后，还包括如下步骤：
步骤一：获取主账户的持仓信息，所述持仓信息包括投资品类、各投资品类对应的数额信息、投资标的信息以及主账户所管辖的交易员信息。
本实施例中主账户的持仓信息可以包括主账户中所持有的投资品类，例如基金、股票，投资标的可以包括各个股票名称、标识等信息，交易员信息可以包括负责维护该主账户所持有资源的账户信息。除此之外还可以包括交易标的对应的交易地区等信息。
步骤二：基于所述持仓信息，确定主账户对应的关联账户的账户数目，并依据所述账户数目生成关联账户。
基于投资品类对应的数量Inv_k、各投资品类对应的数额信息Amo_i、投资标的的数量Obe_j、主账户所管辖的交易员数量Tra_m进行归一化处理，确定主账户对应的关联账户的账户数目Acc_v为：
Figure PCTCN2022141648-appb-000001
其中，ε表示账户因子，i表示投资品类对应的标识，i和k为大于1的自然数。上述计算过程中，将投资品类对应的数量和投资标的对应的数量进行正余弦计算，将计算得到的参数结合各投资品类对应的数额信息共同作为确定账户数目的参数，提高了账户账户数目确定的客观性。
步骤三：基于所述账户数据和所述持仓信息，分别更新所述主账户和所述关联账户中的持仓信息。
通过将主账户中所持有的资源转移至对应的关联账户中，使得交易人员可以直接针对相关的交易标的，在对应的关联账户中操作交易事项，这种方式提高了交易账户的管理效率和交易效率。
可选地，上述机构账号信息可以包括以下至少之一：机构的名称、唯一标识该机构的标识(如统一社会信用代码)，以及机构账号所登录设备的设备标识号。
可选地，账户数据请求用于获取当前机构账号下的账户数据。
S202、当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息。
账户信息可以包括账户标识、该账户所属者的基本信息(如，账号标识)、该账户中的金额以及该账户的历史交易数据等。
参见图3，账户1、账户2和账户3为机构账号通过多账户功能开设的，与机构账号之间为从属关系，即账户1、账户2和账户3为该机构的第一账户数据中包括的第一账 户信息；账户4可以为第二目标对象(如机构的客户)委托给该机构的，与机构账号之间为挂靠关系，即账户4为该机构的第一账户数据中包括的第三账户信息。
可选地，机构账号与前述机构账户层包括的多个账户的前述关系还可指主账户与该多个账户的关系。
可选地，前述管理员可以为主账户的实际拥有人，还可以受托人。
图4为本申请一示例性实施例提供的第一账户数据的缓存流程示意图，如图4所示，终端设备中可以包括交易模块和账户数据仓库，目标应用程序被启动后，终端设备通过交易模块调用账户数据仓库中第一账户数据获取接口，根据账户数据仓库生成网络协议请求，并向第一服务器发送网络协议请求，即账户数据获取请求，第一服务器在接收到网络协议请求后，根据账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，并将机构账号信息对应的第一账户数据反馈给账户数据仓库，账户数据仓库接收并缓存第一账户数据。其中，预设对应关系可以包括：挂靠关系、从属关系，以及委托关系。其中，挂靠关系用于指示第二对应关系，以及委托关系用于指示第一对应关系。
S203、当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；可选地，账户标识与账户信息一一对应，所述多个账户标识包括：所述第一账户信息对应的账户标识、所述第二账户信息对应的账户标识，以及所述第三账户信息对应的账户标识。
S204、展示所述账户列表。
可选地，目标页面为下单页面，图5为本申请一示例性实施例提供的下单页面的示意图，用户在进行购买基金等业务时，可以通过下单页面选择目标账户和买入金额。
具体地，如图5所示，下单页面的顶部设置有返回按钮、页面名称“下单”以及显示有“买入规则”字样的规则查看按钮。此外，下单页面还包括付款账户栏、产品名称栏以及买入金额栏。其中，付款账户栏中显示有“付款账户”字样以及用户所选择的目标账户；产品名称栏显示有“产品名称”字样，以及当前交易的项目名称，如“XX基金”，以及该项目的基本信息，如“7日年化+2.5524％”；买入金额栏显示有“买入金额”字样，以及交易币种，如“USD”，表示美元，买入金额栏中还包括金额输入框，在用户未在金额输入框中输入金额时，该金额输入框中显示有金额输入提示信息，如“0.01美元起”，用于提醒用户输入大于0.01的金额。
用户可以通过点击上述付款账户栏区域触发控制展示账户列表的控制指令，账户列表可以显示于账户选择弹窗中，账户选择弹窗可以显示于下单页面的下方区域。如图5所示，账户选择弹窗中的上方区域设置有关闭按钮以及显示有“选择支付账户”字样的账户选择弹窗标题，在关闭按钮下方显示有目标应用程序名称，目标应用程序名称下方区域为账户列表。
图6为本申请一示例性实施例提供的展示账户列表的流程示意图，如图6所示，当用户点击上述付款账户栏区域，触发控制展示账户列表的控制指令时，终端设备执行页面展示回调函数，展示账户选择弹窗，使页面控制器从账户数据仓库中获取第一账户数据，根据第一账户数据生成对应的账户列表，并通过下单页面将账户列表展示在上述账户选择弹窗中。
可选地，除了账户标识以外，账户信息中还包括账户图标、账户尾号信息，以及各账户的余额提示信息。例如，图5中账户列表中“综合账户(0679)”与“综合账户(2013)”为账户尾号信息，“自身账户”(指示第一账户信息)和“委托出的账户(指示第二账户信息)”为账户标识，账户尾号信息下方分别显示有相应账户的余额提示信息：“现金可用35.00美元”、“现金可用1,372.61美元”。账户列表中还可以包括选中标识， 显示于用户选中的目标账户对应的账户标识右侧。
在另一些可选的实施例中，目标页面还可以为用于展示机构的详细信息的机构信息页面，机构信息页面可以显示有“账户列表”字样的查看按钮，用户可以通过点击查看按钮触发控制展示账户列表的控制指令。
本申请实施例中，通过当检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，账户数据获取请求包括已登录目标应用程序的机构的机构账号信息；当接收到第一服务器针对账户数据获取请求反馈的第一账户数据时，对第一账户数据进行缓存，第一账户数据中包括下述至少两个类别的多个账户信息：机构自身的第一账户信息、机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给机构的第三账户信息；当获取到用户通过目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据第一账户数据生成对应的账户列表，账户列表中包括多个账户信息对应的多个账户标识，账户标识用于指示其对应的账户信息的类别，展示账户列表。由于账户列表中包括用于指示其对应的账户信息的类别的多个账户信息对应的多个账户标识，机构相关人员可以通过账户列表区分供选择的账户的授权情况，无需较复杂的查询操作，节省了时间，有效提高账户数据管理效率。
在本申请中的一些可选的实施例中，所述方法还包括步骤S301-S304：
S301、当获取到所述用户对展示于所述目标页面的刷新按钮的点击操作时，向所述第一服务器发送账户数据刷新请求。
S302、当接收到所述第一服务器针对所述账户数据获取请求反馈的第二账户数据时，对所述第二账户数据进行缓存，所述第二账户数据为刷新后的第一账户数据。
S303、根据所述第二账户数据生成对应的刷新后账户列表。
S304、展示所述刷新后账户列表。
具体地，目标页面中可以显示有刷新按钮，账户数据刷新请求用于获取当前该机构账号下最新的账户数据。
在另一些实施例中，刷新按钮还可以设置于账户列表中，便于用户在查看账户列表时进行刷新，以获取最新的账户数据(第二账户数据)。
可选地，账户列表中包括的多个账户信息可以按照预设优先级排序，优先级越高，排序越靠前，优先级最高的为优选账户数据，优选账户数据在当前券商及业务场景下，优先展示。
可选地，账户列表还包括假账户数据，假账户为当前机构账号未进行开通的账户，假账户显示于账户列表中，可以引导用户开通更多账户，以提高账户的开通率。
在本申请中的一些可选的实施例中，所述方法还包括步骤S401-S402：
S401、在检测到所述用户对展示于目标应用程序的下单页面中的下单按钮的触发操作后，进行交易校验，得到校验结果。
在本申请中的一些可选的实施例中，在S401中，进行交易校验，得到校验结果，包括步骤S4011-S4012：
S4011、确定所述用户是否选择出用于当前交易的目标账户，若是，则确定所述目标账户是否为所述第一账户数据对应的账户，若是，则确定所述用户输入的目标金额是否大于预设最小金额，若是，则确定所述目标金额是否小于或者等于所述目标账户中的余额，若是，则确定校验结果为校验成功。
S4012若所述用户未选择所述目标账户，或所述目标账户不为所述第一账户数据对应的账户，或确定所述用户输入的目标金额不大于预设最小金额，或所述目标金额大于所述目标账户中的余额，则确定校验结果为校验失败。
具体地，通过职责链模式进行交易校验，得到校验结果。图7为本申请一示例性实施例提供的交易校验的流程示意图，如图7所示，具体地，交易校验职责链可以包括第一节点、第二节点、第三节点和第四节点，分别执行以下交易校验的4个交易步骤：
步骤1：目标账户校验，即确定用户是否选择出目标账户。当用户选择出目标账户时，上述图5中的付款账户栏中的右侧区域会显示有目标账户的账户尾号信息，当用户未选择出目标账户时，该付款账户栏中的右侧区域为空白。若用户未选择目标用户，则确定校验结果为校验失败，若用户已选择出目标账户时，进入第二节点，执行步骤2。
步骤2：目标账户权限校验，即确定所述目标账户是否为所述第一账户数据对应的账户。也就是说，确定用户选择的目标账户是否为该用户具有管理权限与交易权限的账户。若目标账户不为第一账户数据对应的账户，则确定校验结果为校验失败，若目标账户为第一账户数据对应的账户，进入第三节点，执行步骤3。
步骤3：输入金额校验，即确定所述用户输入的目标金额是否不小于预设最小金额。预设最小金额为允许交易的最小金额，例如，预设最小金额可以为0.01。若用户输入的目标金额小于预设最小金额，则确定校验结果为校验失败，若用户输入的目标金额不小于预设最小金额，则进入第四节点，执行步骤4。
步骤4：目标账户余额校验，即确定所述目标金额是否小于或者等于所述目标账户中的余额，若目标金额大于目标账户中的余额，则确定校验结果为校验失败，若目标金额小于或者等于目标账户中的余额，则确定校验结果为校验成功。
若校验结果为校验成功，则将校验结果逐级返回，即由第四节点将校验结果返回给第三节点，第三节点将校验结果返回给第二节点，第二节点将校验结果返回给第一节点。上述校验过程使用职责链模式，可以提高代码可复用性，以及可维护性。
S402、在所述校验结果指示校验成功时，向所述第二服务器发送交易请求，以使所述第二服务器根据所述交易请求生成对应的订单信息。其中，第二服务器为执行基金交易的服务器。
可选地，第二服务器在生成对应的订单信息后，终端设备可以接收到第二服务器发送的订单生成提示信息，并显示交易密码输入页面，提示用户输入交易密码。在用户输入密码之后，进行密码验证，密码验证通过后，交易完成，并向第一服务器发送账户信息更新请求，账户信息更新请求用于指示第一服务器对目标账户下的相应的数据以及目标账户的余额进行更新。
可选地，当所述校验结果指示校验失败时，根据确定出校验结果的节点，显示确定出校验结果的节点对应的提示信息。例如，当确定用户未选择目标账户时，确定出校验结果的节点为第一节点，此时，第一节点可以对应如“请选择付款账户”字样的提示信息。
在本申请中的一些可选的实施例中，所述方法还包括步骤S501-S503：
S501、向所述第一服务器发送第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息，所述第一授权请求用于指示所述第一服务器向所述第一目标对象的账号信息对应的第一设备发送第一授权申请，并获取所述第一设备针对所述第一授权申请反馈的第一授权答复信息，以及根据所述第一授权答复信息生成对应的第一授权提示信息。
S502、接收所述第一服务器反馈的所述第一授权提示信息，所述第一授权提示信息包括用于指示授权通过的第一提示信息，或用于指示授权未通过的第二提示信息。
S503、展示所述第一授权提示信息。
图8为本申请一示例性实施例提供的另一种系统的结构示意图，该系统可以包括终端设备10、第一服务器20、第一设备30和第二设备40等；终端设备10、第一设备30、第二设备40分别与第一服务器20之间通过网络连接，比如，通过有线或无线网络连接等。终端设备10、第一设备30、第二设备40可以为手机、笔记本电脑等设备。
可选地，终端设备10、第一设备30、第二设备40等设备之间的信息交互可以通过第一服务器20实现。
具体地，第一服务器根据所述第一授权请求中第一目标对象的账号信息确定所述第一目 标对象对应的第一设备，以及根据第一授权请求确定第一授权申请，并将第一授权申请发送至第一设备，其中，第一授权请求用于机构请求将第一待授权账户信息授权给其他机构或个人(第一目标对象)，其中，第一待授权账户信息包含于上述第一账户信息，第一目标对象可以为使用第一设备的用户，第一授权请求与第一授权申请所包含的内容可以相同。
可选地，第一服务器在接收终端设备发送的账户数据获取请求后，可根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据。
第一服务器在接收所述终端设备发送的第一授权请求后，根据所述第一授权请求向第一目标对象的账号信息对应的第一设备发送第一授权申请；第一设备在接收到第一授权申请以后，若检测到用户触发的针对所述第一授权请求的答复指令时，生成对应的第一授权答复信息，第一设备将第一授权答复信息发送给第一服务器，根据所述第一授权答复信息生成对应的第一授权提示信息，第一服务器将第一授权提示信息发送至终端设备。
若上述第一授权答复信息指示第一目标对象同意所述第一授权申请，第一服务器则生成用于指示第一目标对象同意第一授权申请的第一提示信息并将其发送给终端设备。
若上述第一授权答复信息指示第一目标对象不同意所述第一授权申请，则表示第一目标对象拒绝了所述机构针对第一待授权账户信息的委托，则第一服务器可以生成用于指示第一目标对象不同意第一授权申请的第二提示信息，并发送至终端设备。
若上述第一授权答复信息指示第一目标对象同意所述第一授权申请，第一服务器则将上述第一待授权账户信息确定为第二账户信息，以及在所述机构账号的第二账户信息与所述第一目标对象的账号信息之间建立第一对应关系，并将所述第一对应关系添加至前述预设对应关系中。所述第一对应关系表示所述机构将所述自身的账户信息委托给所述第一目标对象，使得该第一目标对象具有对第二账户信息的管理权限及交易权限。
在本申请中的一些可选的实施例中，所述方法还包括步骤S601-S603：
S601、接收所述第一服务器发送的第二授权申请，所述第二授权申请为所述第一服务器在接收所述第二目标对象对应的第二设备发送的第二授权请求时发送的，所述第二授权申请中包括所述机构账号信息、所述第二目标对象的账号信息、以及申请授权给所述机构的第二待授权账户信息。
S602、当检测到所述用户触发的针对所述第二授权请求的答复指令时，生成对应的第二授权答复信息。
S603、将所述第二授权答复信息发送至所述第一服务器，使所述第一服务器根据所述第二授权答复信息生成对应的第二授权提示信息，并将所述第二授权提示信息反馈至所述第二设备。
可选地，第二授权请求与第二授权申请所包含的内容可以相同。第二设备在接收到第二授权请求时，用户可以针对第二授权请求中包括的第二目标对象的账号信息、以及第二待授权账户信息，选择同意或是不同意，以使第二设备生成第二授权答复信息。
若第二授权答复信息指示所述机构同意第二授权申请，则确定所述第二待授权账户信息为第三账号信息，第一服务器可以生成用于指示所述机构同意第二授权申请的第三提示信息，以及将创建机构账号信息与第三账号信息的第二对应关系，并将所述第二对应关系添加至预设对应关系中。所述第二对应关系表示所述第二目标对象将自身的账户信息委托给所述机构，使得该机构具有对第三账户信息的管理权限及交易权限。
若第二授权答复信息指示所述机构不同意第二授权申请，则表示机构拒绝了所述第二目标对象针对第二待授权账户信息的委托，第一服务器可以生成用于指示机构不同意第二授权申请的第四提示信息，并发送至第二设备。
通过上述方案，可以组成机构的账户体系架构，图9为本申请一示例性实施例提供的账户体系架构的结构示意图。如图9所示，账户体系架构配置有视图应用程序编程接口、业务应用程序编程接口、基础应用程序编程接口、数据中心和基础模块。
可选地，第二服务器还可以进一步包括风控服务器。
可选地，机构账号不下发基金首页的资产卡片，在创建订单前，本申请中不对账户所属者进行校验，取消了相关技术中仅支持账户所属者进行基金交易的限制，提高了数据处理效率。
具体地，视图应用程序编程接口包括付款账户栏接口和账户选择弹窗接口，分别用于在目标应用程序的下单页面上显示付款账户栏账户选择弹窗。业务应用程序编程接口提供场景化的业务应用程序编程接口，以及提供业务场景使用的接口封装，包括优选账户接口，账户相关协议数据接口和假账户接口，其中，账户相关协议数据接口用于从第一服务器得到的真实账户列表数据。基础应用程序编程接口包括创建应用程序编程接口、普通交易账户应用程序编程接口、交易账户应用程序编程接口、基金账户应用程序编程接口和查询应用程序编程接口等，基础应用程序编程接口用于提供基于数据中心接口的封装，以及不同券商机构等接口封装。数据中心对外提供账户数据(第一账户数据、第二账户数据)获取的接口，内部实现通过获取失败重试，定时刷新请求网络协议保证账户数据更新的及时性，以及解决网络抖动时数据拉取失败的场景，提高接口的可靠性；基础模块包括存储模块(用于提供存储接口)、数据库模块(用于提供数据库读写接口)、网络模块(用于提供网络协议请求接口)和数据结构模型，通过存储模块解决接口的性能问题，通过数据库模块适配目标应用程序重启后网络未返回时需要正常获取数据的场景。
在本技术方中，在数据结构模型中增加了授权账户相关字段，并且在基础应用程序编程接口、业务应用程序编程接口中增加获取授权账户的应用程序编程接口和实现，以及在视图应用程序编程接口中增加了授权的账户，使得在进行购买基金等交易业务时可以选择和使用授权账户(第二账户信息和/或第三账户信息)。
图10为本申请一示例性实施例提供的一种数据处理方法的流程示意图，该方法适用于前述第一服务器20，如图10所示，该方法至少包括以下步骤S701-S703：
S701、接收终端设备发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
S702、根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
S703、将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
在本申请中的一些可选的实施例中，所述数据处理方法还包括步骤S801-S805：
S801、接收所述终端设备发送的第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息；
S802、根据所述第一授权请求向第一目标对象的账号信息对应的第一设备发送第一授权申请；
S803、接收所述第一设备针对所述第一授权申请反馈的第一授权答复信息；
S804、若所述第一授权答复信息指示所述第一目标对象同意所述第一授权申请，则创建所述机构账号信息与所述第一待授权账户信息的第一对应关系；将所述第一对应关系添加至所述预设对应关系，并生成用于指示所述第一目标对象同意所述第一授权申请 的第一提示信息；将所述第一提示信息发送至所述终端设备；
S805、若所述第一授权答复信息指示所述第一目标对象不同意所述第一授权申请，则生成用于指示所述第一目标对象不同意所述第一授权申请的第二提示信息；将所述第二提示信息发送至所述终端设备。
本数据处理方法的具体实施方式可参见前述内容，此处不再赘述。
图11为本申请一示例性实施例提供的一种交易账户的数据管理装置的结构示意图，该装置应用于终端设备，包括：
第一发送模块，用于当检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
第一缓存模块，用于当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
第一生成模块，用于当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
第一展示模块，用于展示所述账户列表。
在本申请中的一些可选的实施例中，该交易账户的数据管理装置还包括：
第二发送模块，用于当获取到所述用户对展示于所述目标页面的刷新按钮的点击操作时，向所述第一服务器发送账户数据刷新请求；
第二缓存模块，用于当接收到所述第一服务器针对所述账户数据获取请求反馈的第二账户数据时，对所述第二账户数据进行缓存，所述第二账户数据为刷新后的第一账户数据；
第二生成模块，用于根据所述第二账户数据生成对应的刷新后账户列表；
第二展示模块，用于展示所述刷新后账户列表。
在本申请中的一些可选的实施例中，所述交易账户的数据管理装置还包括：
校验模块，用于在检测到所述用户对展示于目标应用程序的下单页面中的下单按钮的触发操作后，进行交易校验，得到校验结果；
第三发送模块，用于在所述校验结果指示校验成功时，向第二服务器发送交易请求，以使所述第二服务器根据所述交易请求生成对应的订单信息。
在本申请中的一些可选的实施例中，所述校验模块在用于进行交易校验，得到校验结果时，具体用于：
确定所述用户是否选择出用于当前交易的目标账户，若是，则确定所述目标账户是否为所述第一账户数据对应的账户，若是，则确定所述用户输入的目标金额是否大于预设最小金额，若是，则确定所述目标金额是否小于或者等于所述目标账户中的余额，若是，则确定校验结果为校验成功；
若所述用户未选择所述目标账户，或所述目标账户不为所述第一账户数据对应的账户，或确定所述用户输入的目标金额不大于所述预设最小金额，或所述目标金额大于所述目标账户中的余额，则确定校验结果为校验失败。
在本申请中的一些可选的实施例中，所述交易账户的数据管理装置还包括：
第四发送模块，用于向所述第一服务器发送第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息，所述第一授权请求用于指示所述第一服务器向所述第一目标对象的账号信息对应的第一设备发送第一授权申请，并获取所述第一设备针对所述第一 授权申请反馈的第一授权答复信息，以及根据所述第一授权答复信息生成对应的第一授权提示信息；
第二接收模块，用于接收所述第一服务器反馈的所述第一授权提示信息，所述第一授权提示信息包括用于指示授权通过的第一提示信息，或用于指示授权未通过的第二提示信息；
第三展示模块，用于展示所述第一授权提示信息。
在本申请中的一些可选的实施例中，所述交易账户的数据管理装置还包括：
第三接收模块，用于接收所述第一服务器发送的第二授权申请，所述第二授权申请为所述第一服务器在接收所述第二目标对象对应的第二设备发送的第二授权请求时发送的，所述第二授权请求中包括所述机构账号信息、所述第二目标对象的账号信息、以及申请授权给所述机构的第二待授权账户信息；
第三生成模块，用于当检测到所述用户触发的针对所述第二授权请求的答复指令时，生成对应的第二授权答复信息；
第五发送模块，用于将所述第二授权答复信息发送至所述第一服务器，使所述第一服务器根据所述第二授权答复信息生成对应的第二授权提示信息，并将所述第二授权提示信息反馈至所述第二设备。
图12为本申请一示例性实施例提供的一种数据处理装置的结构示意图，该装置应用于第一服务器，包括：
第一接收模块，用于接收终端设备发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
确定模块，用于根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
反馈模块，将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
在本申请中的一些可选的实施例中，所述数据处理装置还包括：
第四接收模块，用于接收所述终端设备发送的第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息；
第六发送模块，用于根据所述第一授权请求向第一目标对象的账号信息对应的第一设备发送第一授权申请；
第五接收模块，用于接收所述第一设备针对所述第一授权申请反馈的第一授权答复信息；
创建模块，用于若所述第一授权答复信息指示所述第一目标对象同意所述第一授权申请，则创建所述机构账号信息与所述第一待授权账户信息的第一对应关系；将所述第一对应关系添加至所述预设对应关系，并生成用于指示所述第一目标对象同意所述第一授权申请的第一提示信息；将所述第一提示信息发送至所述终端设备；
第七发送模块，用于若所述第一授权答复信息指示所述第一目标对象不同意所述第一授权申请，则生成用于指示所述第一目标对象不同意所述第一授权申请的第二提示信息；将所述第二提示信息发送至所述终端设备。
应理解的是，装置实施例与方法实施例可以相互对应，类似的描述可以参照方法实施例。为避免重复，此处不再赘述。具体地，该装置可以执行上述方法实施例，并且该装置中的各个模块的前述和其它操作和/或功能分别为了上述方法实施例中的各个方法中的相应流程，为了简洁，在此不再赘述。
上文中结合附图从功能模块的角度描述了本申请实施例的装置。应理解，该功能模块可以通过硬件形式实现，也可以通过软件形式的指令实现，还可以通过硬件和软件模块组合实现。具体地，本申请实施例中的方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路和/或软件形式的指令完成，结合本申请实施例公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。可选地，软件模块可以位于随机存储器，闪存、只读存储器、可编程只读存储器、电可擦写可编程存储器、寄存器等本领域的成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法实施例中的步骤。
图13是本申请实施例提供的电子设备的示意性框图，该电子设备可包括：
存储器1301和处理器1302，该存储器1301用于存储计算机程序，并将该程序代码传输给该处理器1302。换言之，该处理器1302可以从存储器1301中调用并运行计算机程序，以实现本申请实施例中的方法。
例如，该处理器1302可用于根据该计算机程序中的指令执行上述方法实施例。
在本申请的一些实施例中，该处理器1302可以包括但不限于：
通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等等。
在本申请的一些实施例中，该存储器1301包括但不限于：
易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
在本申请的一些实施例中，该计算机程序可以被分割成一个或多个模块，该一个或者多个模块被存储在该存储器1301中，并由该处理器1302执行，以完成本申请提供的方法。该一个或多个模块可以是能够完成特定功能的一系列计算机程序指令段，该指令段用于描述该计算机程序在该电子设备中的执行过程。
如图13所示，该电子设备还可包括：
收发器1303，该收发器1303可连接至该处理器1302或存储器1301。
其中，处理器1302可以控制该收发器1303与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。收发器1303可以包括发射机和接收机。收发器1303还可以进一步包括天线，天线的数量可以为一个或多个。
应当理解，该电子设备中的各个组件通过总线系统相连，其中，总线系统除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
本申请还提供了一种计算机可读存储介质，其上存储有计算机程序，该计算机程序 被计算机执行时使得该计算机能够执行上述方法实施例的方法。或者说，本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得计算机执行上述方法实施例的方法。
可以理解的是，在本申请的具体实施方式中，涉及到账户信息等相关的数据，当本申请以上实施例运用到具体产品或技术中时，需要获得用户许可、同意或者授权，且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准。
当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例该的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、第一服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、第一服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的第一服务器、数据中心等数据存储设备。该可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。例如，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。
以上仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (12)

  1. 一种交易账户的数据管理方法，应用于终端设备，包括：
    当检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
    当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
    当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
    展示所述账户列表。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    当获取到所述用户对展示于所述目标页面的刷新按钮的点击操作时，向所述第一服务器发送账户数据刷新请求；
    当接收到所述第一服务器针对所述账户数据获取请求反馈的第二账户数据时，对所述第二账户数据进行缓存，所述第二账户数据为刷新后的第一账户数据；
    根据所述第二账户数据生成对应的刷新后账户列表；
    展示所述刷新后账户列表。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    在检测到所述用户对展示于目标应用程序的下单页面中的下单按钮的触发操作后，进行交易校验，得到校验结果；
    在所述校验结果指示校验成功时，向第二服务器发送交易请求，以使所述第二服务器根据所述交易请求生成对应的订单信息。
  4. 根据权利要求3所述的方法，其中，所述进行交易校验，得到校验结果，包括：
    确定所述用户是否选择出用于当前交易的目标账户，若是，则确定所述目标账户是否为所述第一账户数据对应的账户，若是，则确定所述用户输入的目标金额是否大于预设最小金额，若是，则确定所述目标金额是否小于或者等于所述目标账户中的余额，若是，则确定校验结果为校验成功；
    若所述用户未选择所述目标账户，或所述目标账户不为所述第一账户数据对应的账户，或确定所述用户输入的目标金额不大于所述预设最小金额，或所述目标金额大于所述目标账户中的余额，则确定校验结果为校验失败。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    向所述第一服务器发送第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息，所述第一授权请求用于指示所述第一服务器向所述第一目标对象的账号信息对应的第一设备发送第一授权申请，并获取所述第一设备针对所述第一授权申请反馈的第一授权答复信息，以及根据所述第一授权答复信息生成对应的第一授权提示信息；
    接收所述第一服务器反馈的所述第一授权提示信息，所述第一授权提示信息包括用于指示授权通过的第一提示信息，或用于指示授权未通过的第二提示信息；
    展示所述第一授权提示信息。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    接收所述第一服务器发送的第二授权申请，所述第二授权申请为所述第一服务器在接收所述第二目标对象对应的第二设备发送的第二授权请求时发送的，所述第二授权请求中包括所述机构账号信息、所述第二目标对象的账号信息、以及申请授权给所述机构的第二待授权账户信息；
    当检测到所述用户触发的针对所述第二授权申请的答复指令时，生成对应的第二授权答复信息；
    将所述第二授权答复信息发送至所述第一服务器，使所述第一服务器根据所述第二授权答复信息生成对应的第二授权提示信息，并将所述第二授权提示信息反馈至所述第二设备。
  7. 一种数据处理方法，应用于第一服务器，包括：
    接收终端设备发送的账户数据获取请求，其中，所述账户数据获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向所述第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
    根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
    将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    接收所述终端设备发送的第一授权请求，所述第一授权请求中包括所述机构账号信息、所述第一目标对象的账号信息、以及申请授权给所述第一目标对象的第一待授权账户信息；
    根据所述第一授权请求向第一目标对象的账号信息对应的第一设备发送第一授权申请；
    接收所述第一设备针对所述第一授权申请反馈的第一授权答复信息；
    若所述第一授权答复信息指示所述第一目标对象同意所述第一授权申请，则创建所述机构账号信息与所述第一待授权账户信息的第一对应关系；将所述第一对应关系添加至所述预设对应关系，并生成用于指示所述第一目标对象同意所述第一授权申请的第一提示信息；将所述第一提示信息发送至所述终端设备；
    若所述第一授权答复信息指示所述第一目标对象不同意所述第一授权申请，则生成用于指示所述第一目标对象不同意所述第一授权申请的第二提示信息；将所述第二提示信息发送至所述终端设备。
  9. 一种交易账户的数据管理装置，应用于终端设备，包括：
    第一发送模块，用于当检测到用户启动终端设备中的目标应用程序时，向第一服务器发送账户数据获取请求，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
    第一缓存模块，用于当接收到所述第一服务器针对所述账户数据获取请求反馈的第一账户数据时，对所述第一账户数据进行缓存，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
    第一生成模块，用于当获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别；
    第一展示模块，用于展示所述账户列表。
  10. 一种数据处理装置，应用于第一服务器，包括：
    第一接收模块，用于接收终端设备发送的账户数据获取请求，其中，所述账户数据 获取请求为所述终端设备检测到用户启动所述终端设备中的目标应用程序时，向第一服务器发送的，所述账户数据获取请求包括已登录所述目标应用程序的机构的机构账号信息；
    确定模块，用于根据所述账户数据获取请求中的机构账号信息与预设对应关系确定对应的第一账户数据，所述第一账户数据中包括下述至少两个类别的多个账户信息：所述机构自身的第一账户信息、所述机构授权给第一目标对象的第二账户信息，以及第二目标对象授权给所述机构的第三账户信息；
    反馈模块，将所述第一账户数据反馈至所述终端设备，使所述终端设备在获取到所述用户通过所述目标应用程序中的目标页面触发的用于控制展示账户列表的控制指令时，根据所述第一账户数据生成对应的账户列表，并展示所述账户列表，所述账户列表中包括所述多个账户信息对应的多个账户标识，所述账户标识用于指示其对应的账户信息的类别。
  11. 一种电子设备，包括：
    处理器；以及
    存储器，用于存储所述处理器的可执行指令；
    其中，所述处理器配置为经由执行所述可执行指令来执行权利要求1-8任一项所述的方法。
  12. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-8任一项所述的方法。
PCT/CN2022/141648 2022-10-12 2022-12-23 交易账户的数据管理方法、装置、电子设备及存储介质 WO2024077780A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211248985.0 2022-10-12
CN202211248985.0A CN115439253A (zh) 2022-10-12 2022-10-12 交易账户的数据管理方法、装置、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024077780A1 true WO2024077780A1 (zh) 2024-04-18

Family

ID=84251056

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/141648 WO2024077780A1 (zh) 2022-10-12 2022-12-23 交易账户的数据管理方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN115439253A (zh)
WO (1) WO2024077780A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115439253A (zh) * 2022-10-12 2022-12-06 深圳市富途网络科技有限公司 交易账户的数据管理方法、装置、电子设备及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101872464A (zh) * 2009-04-27 2010-10-27 美国银行公司 金融机构实现的账户管理系统
US20130054456A1 (en) * 2011-08-30 2013-02-28 Bank Of America Corporation System for allocating and managing contributions to account categories
CN111681105A (zh) * 2020-06-08 2020-09-18 中国银行股份有限公司 账户管理方法及装置
CN111833066A (zh) * 2020-07-01 2020-10-27 中国建设银行股份有限公司 一种账户授权的方法、装置及系统
CN112532653A (zh) * 2020-12-22 2021-03-19 深圳市富途网络科技有限公司 一种管理第三方账号的方法及装置
CN113888326A (zh) * 2021-09-08 2022-01-04 深圳市富途网络科技有限公司 数据处理方法、装置、设备及计算机可读存储介质
CN115439253A (zh) * 2022-10-12 2022-12-06 深圳市富途网络科技有限公司 交易账户的数据管理方法、装置、电子设备及存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101872464A (zh) * 2009-04-27 2010-10-27 美国银行公司 金融机构实现的账户管理系统
US20130054456A1 (en) * 2011-08-30 2013-02-28 Bank Of America Corporation System for allocating and managing contributions to account categories
CN111681105A (zh) * 2020-06-08 2020-09-18 中国银行股份有限公司 账户管理方法及装置
CN111833066A (zh) * 2020-07-01 2020-10-27 中国建设银行股份有限公司 一种账户授权的方法、装置及系统
CN112532653A (zh) * 2020-12-22 2021-03-19 深圳市富途网络科技有限公司 一种管理第三方账号的方法及装置
CN113888326A (zh) * 2021-09-08 2022-01-04 深圳市富途网络科技有限公司 数据处理方法、装置、设备及计算机可读存储介质
CN115439253A (zh) * 2022-10-12 2022-12-06 深圳市富途网络科技有限公司 交易账户的数据管理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN115439253A (zh) 2022-12-06

Similar Documents

Publication Publication Date Title
US8818888B1 (en) Application clusters
US20180322485A1 (en) Ledger management systems and methods
US11790363B2 (en) Cryptocurrency storage distribution
GB2461781A (en) Method and a system for performing an automated teller machine (ATM) transaction
US20150379485A1 (en) Systems and methods for identifying and remedying account error events in networked computer systems
US20210173677A1 (en) Graphical User Interface and Operator Console Management System for Distributed Terminal Network
US20200007647A1 (en) Real-time Event Orchestrator
US20220171505A1 (en) Graphical User Interface and Operator Console Management System for Distributed Terminal Network
US20210389854A1 (en) Biometric Authentication, Decentralized Learning Framework, and Adaptive Security Protocols in Distributed Terminal Network
US20220159056A1 (en) Graphical User Interface and Operator Console Management System for Distributed Terminal Network
US20210312026A1 (en) Graphical User Interface and Operator Console Management System for Distributed Terminal Network
US20210173673A1 (en) Distributed Terminals Network Management, Systems, Interfaces and Workflows
WO2024077780A1 (zh) 交易账户的数据管理方法、装置、电子设备及存储介质
KR102590475B1 (ko) 증권형 토큰 정보 관리 서비스 방법 및 sto 플랫폼
JP2007047999A (ja) 証券決済残高管理システム及び証券決済残高管理プログラム
US20220263886A1 (en) Graphical User Interface and Operator Console Management System for Distributed Terminal Network
US20180189874A1 (en) Systems and methods for bond pricing
US20180189873A1 (en) Systems and Methods for Bond Pricing
US11610260B1 (en) System, method and program product to transfer, allocate and track ownership interests in aggregated accounts
KR20220066786A (ko) 실물자산 투자방법
US20190244292A1 (en) Exotic currency settlement systems and methods
CN115345722B (zh) 资金管理系统、方法、电子设备和存储介质
US20240185234A1 (en) Hierarchical digital issuance tokens and claim tokens
US20230010355A1 (en) Real estate fund transfer facilitation system
CN115545929B (zh) 资金管理方法、装置、电子设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22961958

Country of ref document: EP

Kind code of ref document: A1