Resource management system, method and device, storage medium and electronic equipment
By creating sub-accounts and generating management pages on each intelligent agent platform, the problem of inconvenient resource management between intelligent agent platforms is solved, and unified resource management convenience is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-01
- Publication Date
- 2026-04-03
AI Technical Summary
Deploying agents on different agent platforms makes it difficult to manage revenue-generating resources, which inconveniences developers in managing resources.
By introducing a payment server, the revenue-generating resources of intelligent agents on different intelligent agent platforms can be managed in a unified manner. This is achieved by creating sub-accounts for each platform and generating management pages, thus enabling unified storage and management of resources.
It improves the ease of management for developers of intelligent agent resources across multiple platforms, allowing them to manage resources on all platforms uniformly through a single management page.
Smart Images

Figure CN121787776A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of computer technology, and in particular to a resource management system, method, apparatus, storage medium and electronic device. Background Technology
[0002] With the development of artificial intelligence (AI) technology, intelligent agents driven by large models (especially large language models (LLMs)) have emerged. These agents can understand the semantics of natural language input by users through the large models they use, and then provide services to users based on the semantics understood by the large models and the predefined business processes within the agent.
[0003] To facilitate the development of intelligent agents, many intelligent agent platforms have emerged on the market. In addition to providing developers with various large models needed to develop intelligent agents, these platforms also allow developers to directly deploy their developed intelligent agents on the platform, which in turn makes the deployed intelligent agents available to users.
[0004] However, since different agent platforms target different user groups, in order to make the developed agents usable by as many users as possible, developers often deploy their agents on multiple different agent platforms. This makes it difficult to manage the revenue resources brought to the developers by agents deployed on different agent platforms. Summary of the Invention
[0005] This specification provides a resource management method, apparatus, storage medium, and electronic device to partially solve the problems existing in the prior art.
[0006] The embodiments in this specification adopt the following technical solutions: This specification provides a resource management method in which a first user deploys a target intelligent agent on at least one intelligent agent platform. The method includes: For each intelligent agent platform, when a resource account creation request corresponding to the target intelligent agent deployed on the intelligent agent platform is received from the first user, a sub-account corresponding to the intelligent agent platform is created for the first user. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. When a management request is received from the first user, a management page is generated containing the sub-accounts created for the first user corresponding to each intelligent agent platform; The management page is provided to the first user.
[0007] This specification provides a resource management system, which includes a payment server, a user terminal for a first user, and multiple intelligent agent platforms; the first user deploys a target intelligent agent on each intelligent agent platform; wherein: The user terminal, for each intelligent agent platform, logs into the intelligent agent platform using the first user's platform account according to the operation of the first user, and sends a resource account creation request to the intelligent agent platform corresponding to the target intelligent agent deployed on the intelligent agent platform; The intelligent agent platform is used to receive the resource account creation request sent by the user terminal and forward the resource account creation request to the payment server; The payment server receives the resource account creation request and creates a sub-account for the first user corresponding to the intelligent agent platform. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The user terminal is also used to send a management request to the payment server, receive and display the management page returned by the payment server; The payment server is also configured to, upon receiving the management request, generate a management page containing a sub-account created for the first user corresponding to each intelligent agent platform, and return the management page to the user terminal.
[0008] This specification provides a resource management device in which a first user deploys a target intelligent agent on at least one intelligent agent platform. The device includes: The sub-account creation module is used to create a sub-account for each intelligent agent platform when it receives a resource account creation request sent by the first user corresponding to the target intelligent agent deployed on the intelligent agent platform. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The management module is used to generate a management page containing sub-accounts created for the first user corresponding to each intelligent agent platform when a management request is received from the first user. The sending module is used to provide the management page to the first user.
[0009] This specification provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described resource management method.
[0010] This specification provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the resource management method described above when executing the program.
[0011] This specification provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described resource management method.
[0012] The above-described at least one technical solution used in the embodiments of this specification can achieve the following beneficial effects: This specification discloses a resource management method. For each intelligent agent platform, upon receiving a resource account creation request from a first user corresponding to a target intelligent agent deployed on that platform, the method creates a sub-account for the first user corresponding to that intelligent agent platform. This sub-account receives and stores resources provided by the second user to the first user when the target intelligent agent deployed on that platform provides services to a second user. Upon receiving a management request from the first user, the method generates and provides a management page containing the sub-accounts created for the first user corresponding to each intelligent agent platform. Through this method, the first user, as a developer, can directly manage the resources provided by target intelligent agents deployed on all intelligent agent platforms through a single management page, greatly improving the convenience of resource management for the first user. Attached Figure Description
[0013] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this specification, illustrate exemplary embodiments and are used to explain this specification, but do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a schematic diagram of the resource management system structure provided in the embodiments of this specification; Figure 2 This is a schematic diagram of the resource management method provided in the embodiments of this specification; Figure 3 A schematic diagram of a resource management device provided in the embodiments of this specification; Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this specification. Detailed Implementation
[0014] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.
[0015] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.
[0016] Figure 1 This is a schematic diagram of the resource management system structure provided in the embodiments of this specification. The system includes: a payment server, a user terminal of the first user, and multiple intelligent agent platforms.
[0017] The first user mentioned in the embodiments of this specification refers to the developer of the intelligent agent. The first user can deploy the target intelligent agent they have developed on multiple intelligent agent platforms. Specifically, for each intelligent agent platform, the first user can log in to the intelligent agent platform through their user terminal using the platform account they use to log in to that intelligent agent platform, and can develop, deploy and manage the target intelligent agent on the intelligent agent platform after logging in.
[0018] The intelligent agent platform can provide the first user with an environment to develop the target intelligent agent, including the large model required. It can also open up the target intelligent agent deployed by the first user to the user group connected to the intelligent agent platform (such as all users with login accounts on the intelligent agent platform), so that users in the user group can use the target intelligent agent through the intelligent agent platform.
[0019] Since different agent platforms connect to different user groups, in order to enable more users to use the target agent, the first user often deploys the same target agent on multiple different agent platforms. However, this makes it difficult to manage the revenue resources brought by the target agent deployed on different agent platforms for the first user. Therefore, this specification introduces a payment server, which is located in the background and is used to manage the revenue resources brought by the target agent deployed on different agent platforms for the first user in a unified manner.
[0020] The user terminal of the first user can be any type of terminal, such as a personal computer, mobile phone, or tablet computer. The user can log in to the intelligent platform through the platform account corresponding to an intelligent agent platform, or install a payment client corresponding to the payment server and log in to the payment server using the first user's main account through the payment client.
[0021] Therefore, based on the aforementioned payment server, user terminal of the first user, and multiple intelligent agent platforms, the embodiments of this specification provide, as follows: Figure 2 The resource management method shown.
[0022] Figure 2 This is a schematic flowchart of a resource management method provided in an embodiment of this specification, which specifically includes the following steps: S200: For each intelligent agent platform, the user terminal, based on the operation of the first user, logs into the intelligent agent platform using the first user's platform account and sends a resource account creation request to the intelligent agent platform corresponding to the target intelligent agent deployed on the intelligent agent platform.
[0023] In the embodiments of this specification, for any intelligent agent platform, the user terminal can respond to the operation of the first user on the user terminal and log in to the intelligent agent platform using the first user's platform account.
[0024] After logging into the intelligent agent platform, the platform can determine whether the first user has already created a corresponding sub-account for the target intelligent agent deployed on the platform on the payment server. If the sub-account has not yet been created, the platform can display recommendation information to the first user. This recommendation information recommends creating a sub-account for the platform on the payment server. The recommendation information includes a control for confirming the creation of the sub-account. The first user can trigger this control to send a resource account creation request to the platform corresponding to the target intelligent agent deployed on the platform. This resource account creation request carries the first user's platform account and is used to create a sub-account for the platform on the payment server.
[0025] Of course, if the intelligent agent platform determines that the first user has not yet created the sub-account, it can also generate an access address carrying the platform account based on the first user's platform account, and activate the payment client installed on the user's terminal that corresponds to the payment server. This allows the payment client launched on the user's terminal to directly jump to the page at the access address, so that the user can send a resource account creation request corresponding to the target intelligent agent deployed on the intelligent agent platform directly to the payment server through this page. The resource account creation request carries the platform account contained in the access address, without needing to forward the resource account creation request from the intelligent agent platform to the payment server through step S201. Step S202 can be executed directly.
[0026] The intelligent agent platform can determine whether it stores the correspondence between the first user's platform account, the first user's main account on the payment server, and the sub-account created by the first user on the intelligent agent platform. If the correspondence is not stored, it can be determined that the first user has not yet created the sub-account.
[0027] S201: The intelligent agent platform receives the resource account creation request sent by the user terminal and forwards the resource account creation request to the payment server.
[0028] When the intelligent agent platform receives a resource account creation request from a user terminal, it can forward the resource account creation request to the payment server.
[0029] S202: The payment server receives the resource account creation request and creates a sub-account for the first user corresponding to the intelligent agent platform.
[0030] Since the resource account creation request always carries the first user's platform account, regardless of whether it is forwarded by the intelligent agent platform, the payment server, upon receiving the request, can generate a token bound to the platform account (hereinafter referred to as the first token) and return it to the intelligent agent platform. The intelligent agent platform then generates a page address for creating a sub-account based on the first token and the platform account, and sends this page address to the user terminal, allowing the user terminal to display the page address to the first user.
[0031] The intelligent agent platform can either directly send the generated page address to the user terminal, allowing the first user to directly access that page, or encode the generated page address into a graphic code before sending it to the user terminal, where the user terminal can display the graphic code. The graphic code can include QR codes, barcodes, etc. When the user terminal displays the graphic code, the first user can scan the graphic code using a payment client installed on the user terminal to trigger access to the page address carried in the graphic code.
[0032] When the first user accesses the page address, the user terminal generates a sub-account creation request carrying the token and platform account contained in the page address, and then sends the sub-account creation request to the payment server. It should be noted that at this time, the token extracted by the user terminal from the page address and carried in the sub-account creation request cannot yet determine whether it is the aforementioned first token.
[0033] After receiving the sub-account creation request, the payment server first searches for the first token it generated and is bound to the platform account in the request. Then, it verifies the sub-account creation request by comparing the first token with the token in the request. Specifically, it compares the first token it generated and is bound to the platform account with the token in the request. If they match, the verification passes; otherwise, it fails.
[0034] After verifying the received sub-account creation request, the payment server first determines the primary account logged into by the first user on the payment server. Then, based on the platform account carried in the sub-account creation request, it creates a sub-account corresponding to the primary account of the first user. This sub-account is used to receive and store resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The second user mentioned in this specification is the user using the target intelligent agent.
[0035] After the payment server creates a sub-account corresponding to the platform account, it can, on the one hand, return a notification message to the user terminal that the sub-account has been successfully created through the intelligent agent platform, or directly return a notification message to the user terminal that the sub-account has been successfully created. On the other hand, it can return the account identifier of the sub-account, the account identifier of the first user's main account, and the platform account to the intelligent agent platform, so that the intelligent agent platform can record the correspondence between the account identifier of the sub-account, the account identifier of the first user's main account, and the platform account. This is used so that the intelligent agent platform can subsequently know that the first user has created a sub-account corresponding to the intelligent agent platform based on the correspondence.
[0036] Subsequently, when the second user uses the target intelligent agent developed by the first user, they can provide resources to the first user through rewards, or by the number of uses or the duration of use. The specific form in which the second user provides resources to the first user depends on the target intelligent agent developed by the first user, and this specification does not impose any restrictions on this. Regardless of the form in which the target intelligent agent obtains profitable resources, the intelligent agent platform can provide the second user with the account identifier of the aforementioned sub-account recorded by the intelligent agent platform itself, enabling the second user to transfer the resources they wish to provide to the first user to that sub-account.
[0037] Figure 2 Steps S200-S202 shown represent the process by which the payment server creates a sub-account corresponding to a smart agent platform. The first user can access this sub-account through... Figure 2The steps S200~S202 shown are to create a corresponding sub-account for each intelligent agent platform where the target intelligent agent is deployed.
[0038] S203: The user terminal sends a management request to the payment server.
[0039] After the first user creates at least one sub-account on the payment server, they can log in to the payment server using the first user's main account through the payment client installed on the user's terminal, and send management requests to the payment server through the main account. In other words, at this time, the user terminal can directly manage all the created sub-accounts through the payment server, bypassing the intelligent agent platform.
[0040] S204: When the payment server receives the management request, it generates a management page containing the sub-accounts created for the first user corresponding to each smart agent platform, and returns the management page to the user terminal.
[0041] S205: The user terminal receives and displays the management page returned by the payment server.
[0042] When the payment server receives the management request, it can query all sub-accounts under the first user's main account, generate a management page containing all the queried sub-accounts, and then return the management page to the user terminal for the user terminal to display.
[0043] The management page includes at least one of the following: the current total resource amount information and resource income and expenditure details for each sub-account. The current total resource amount information for a sub-account describes the total amount of resources currently stored in that sub-account. The resource income and expenditure details describe the amount and time of each instance of resource income and expenditure for that sub-account. These income and expenditure details can be displayed in chronological order or according to a user-defined rule.
[0044] The management page may also include management controls for each sub-account. These controls may include controls for transferring resources within the sub-account, controls for logging out of the sub-account, etc. The user terminal can manage the corresponding sub-account based on the first user's actions on the management controls.
[0045] When generating the aforementioned management page, the payment server can first query all sub-accounts under the primary account of the first user, then query the current total resource amount and resource income and expenditure details of each sub-account. The account identifier, current total resource amount, and resource income and expenditure details corresponding to each sub-account are used as the data to be rendered. Finally, based on the pre-configured page template and the data to be rendered, the management page is rendered. The page templates used to display the data to be rendered for different sub-accounts on this management page can be the same or different; this specification does not impose any restrictions on this.
[0046] When a first user triggers a control on the management page that transfers resources from a sub-account (hereinafter referred to as the target sub-account) to that sub-account, the user terminal can send a resource transfer request to the payment server. Upon receiving the resource transfer request, the payment server first sends an identity verification request to the user terminal to verify the first user's identity. After successful verification, the payment server transfers the amount of resources to be transferred from the target sub-account to the first user's main account, based on the amount of resources to be transferred in the resource transfer request. The first user's main account can not only log in to the payment server, but the resources stored in the main account can also be used for payments on behalf of the first user. Therefore, after transferring the amount of resources from the target sub-account to the first user's main account, the first user can subsequently use the resources originating from the target sub-account for payments.
[0047] When the payment server verifies the identity of the first user through the user terminal, it can perform biometric verification, such as facial recognition or fingerprint verification, on the user terminal. Specifically, after the payment server sends a verification request to the user terminal, the user terminal can collect the first user's biometric information and perform verification locally based on the collected biometric information, then return the verification result to the payment server. Alternatively, the user terminal can also return the collected biometric information to the payment server, which will then verify the first user's identity based on the biometric information collected by the user terminal, obtaining the verification result.
[0048] The above describes a resource management system and method provided by embodiments of this specification. Based on the same idea, this specification also provides corresponding devices, storage media, and electronic devices.
[0049] Figure 3 This is a schematic diagram of a resource management device provided in an embodiment of this specification. A first user deploys a target intelligent agent on at least one intelligent agent platform. The device includes: The sub-account creation module 300 is used to create a sub-account for each intelligent agent platform when it receives a resource account creation request sent by the first user corresponding to the target intelligent agent deployed on the intelligent agent platform. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The management module 301 is used to generate a management page containing sub-accounts created for the first user corresponding to each intelligent agent platform when it receives a management request sent by the first user. The sending module 302 is used to provide the management page to the first user.
[0050] Optionally, the sub-account creation module 300 is specifically used to receive a resource account creation request sent by the intelligent agent platform after the first user logs in to the intelligent agent platform using the platform account; The sub-account creation module 300 is specifically used to determine the first user's main account; and under the main account, create a sub-account corresponding to the platform account.
[0051] Optionally, the sub-account creation module 300 is specifically configured to: generate a first token and return it to the intelligent agent platform, so that the intelligent agent platform generates a page address for creating a sub-account based on the first token and the platform account and displays it to the first user; receive a sub-account creation request sent by the first user through the page address; and after the sub-account creation request is verified successfully based on the first token and the second token carried in the sub-account creation request, create a sub-account corresponding to the platform account under the main account based on the platform account carried in the sub-account creation request.
[0052] Optionally, for each intelligent agent platform, the management page includes information on the current total resource amount and / or resource income and expenditure details contained in the sub-account created for the first user corresponding to that intelligent agent platform.
[0053] Optionally, the management module 301 is further configured to receive a resource transfer request for a target sub-account sent by the first user through the management page; verify the identity of the first user; and after the identity verification is passed, transfer the amount of resources in the target sub-account to the first user's main account according to the amount of resources to be transferred carried in the resource transfer request.
[0054] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can be used to perform the resource management method provided above.
[0055] This specification also provides a computer program product comprising a computer program that, when executed by a processor, implements the resource management method described above.
[0056] based on Figure 1 The resource management method shown in this specification, in addition to the embodiments provided, also provides Figure 4 The diagram shows the structure of the electronic device. Figure 4 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile storage, and may also include other hardware required for business operations. The processor reads the corresponding computer program from the non-volatile storage into memory and then runs it to implement the resource management method described above.
[0057] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.
Claims
1. A resource management method, wherein a first user deploys a target intelligent agent on at least one intelligent agent platform, the method comprising: For each intelligent agent platform, when a resource account creation request corresponding to the target intelligent agent deployed on the intelligent agent platform is received from the first user, a sub-account corresponding to the intelligent agent platform is created for the first user. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. When a management request is received from the first user, a management page is generated containing the sub-accounts created for the first user corresponding to each intelligent agent platform; The management page is provided to the first user.
2. The method as described in claim 1, wherein receiving a resource account creation request sent by the first user corresponding to the target intelligent agent deployed on the intelligent agent platform, specifically includes: After the first user logs into the intelligent agent platform using their platform account, they receive a resource account creation request sent through the intelligent agent platform. Creating a sub-account for the first user corresponding to the intelligent agent platform, specifically including: Determine the primary account of the first user; Under the main account, create a sub-account corresponding to the platform account.
3. The method as described in claim 2, wherein creating a sub-account corresponding to the platform account under the main account specifically includes: Generate a first token and return it to the intelligent agent platform, so that the intelligent agent platform can generate a page address for creating a sub-account based on the first token and the platform account and display it to the first user; Receive the sub-account creation request sent by the first user through the page address; Once the sub-account creation request is verified using the first token and the second token carried in the sub-account creation request, a sub-account corresponding to the platform account is created under the main account based on the platform account carried in the sub-account creation request.
4. The method as described in claim 1, wherein for each intelligent agent platform, the management page includes information on the current total resource amount and / or resource income and expenditure details contained in the sub-account created for the first user corresponding to the intelligent agent platform.
5. The method of claim 2, further comprising: Receive the resource transfer request for the target sub-account sent by the first user through the management page; The first user is verified, and after verification, the amount of resources to be transferred from the target sub-account to the first user's main account is transferred according to the amount of resources to be transferred carried in the resource transfer request.
6. A resource management system, the system comprising a payment server, a user terminal of a first user, and multiple intelligent agent platforms; the first user deploys a target intelligent agent on each intelligent agent platform; wherein: The user terminal, for each intelligent agent platform, logs into the intelligent agent platform using the first user's platform account according to the operation of the first user, and sends a resource account creation request to the intelligent agent platform corresponding to the target intelligent agent deployed on the intelligent agent platform; The intelligent agent platform is used to receive the resource account creation request sent by the user terminal and forward the resource account creation request to the payment server; The payment server receives the resource account creation request and creates a sub-account for the first user corresponding to the intelligent agent platform. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The user terminal is also used to send a management request to the payment server, receive and display the management page returned by the payment server; The payment server is also configured to, upon receiving the management request, generate a management page containing a sub-account created for the first user corresponding to each intelligent agent platform, and return the management page to the user terminal.
7. The system as described in claim 6, wherein the payment server is specifically configured to, upon receiving the resource account creation request, generate a token and return it to the intelligent agent platform; Specifically, the intelligent agent platform is used to generate a page address for creating a sub-account based on the platform account and the token returned by the payment server, and send the page address to the user terminal; The user terminal is specifically used to display the page address, and when the first user triggers the page address, generate a sub-account creation request based on the token carried in the page address and the platform account, and send the sub-account creation request to the payment server. The payment server verifies the sub-account creation request based on the first token generated by the payment server itself and the token carried in the sub-account creation request. After the verification is successful, the server creates a sub-account corresponding to the platform account under the first user's main account based on the platform account carried in the sub-account creation request.
8. The system as described in claim 7, wherein the user terminal is further configured to send a resource transfer request for the target sub-account to the payment server based on the operation of the first user on the management page; The payment server is also used to verify the identity of the first user through the user terminal, and after the identity verification is passed, to transfer the amount of resources in the target sub-account to the first user's main account according to the amount of resources to be transferred carried in the resource transfer request.
9. A resource management device, wherein a first user deploys a target intelligent agent on at least one intelligent agent platform, the device comprising: The sub-account creation module is used to create a sub-account for each intelligent agent platform when it receives a resource account creation request sent by the first user corresponding to the target intelligent agent deployed on the intelligent agent platform. The sub-account is used to receive and store the resources provided by the second user to the first user when the target intelligent agent deployed on the intelligent agent platform provides services to the second user. The management module is used to generate a management page containing sub-accounts created for the first user corresponding to each intelligent agent platform when it receives a management request sent by the first user. The sending module is used to provide the management page to the first user.
10. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of claims 1-5.
11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method described in any one of claims 1-5.
12. A computer program product comprising a computer program that, when executed by a processor, implements the method described in any one of claims 1-5.
Citation Information
Patent Citations
Method and device for displaying settlement information of information resources, equipment and storage medium
CN115131140A
Account cross-platform management method and device
CN115526613A
Account management method and device, equipment and storage medium
CN116308377A
Task execution method and device, computer equipment and storage medium
CN120803643A
Method and system for facilitating collaboration across multiple platforms
US20160294813A1