AI gateway account management method and system based on DNA mark

Abstract

The invention discloses an AI gateway account management method and system based on a DNA mark, and the method comprises the steps: receiving a creation request of a management account, and obtaining the function attribute information, the data authority information, the account ID of the management account, and the DNA mark information in the creation request; generating an account ID to create a user account, generating DNA mark information of the user account based on the account ID of the management account and the DNA mark information, and configuring function attribute information and data authority information of the user account based on the function attribute information and the data authority information in the creation request; wherein the DNA mark information of the management account is a prefix of the DNA mark information of the user account; and receiving an operation request of the management account, analyzing the target account information in the operation request, and executing the operation request when it is judged that the management account has the operation authority for the target account. The DNA genetic hierarchical relationship between the accounts is recorded through the character string in the specific format, so that accurate management and data analysis can be carried out on the user.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet account management, and in particular to an AI gateway account management method and system based on DNA markers. Background Art

[0002] AI big model technology is experiencing rapid development and application. Large models are increasingly being leveraged in a growing number of application scenarios, significantly improving work efficiency. However, different AI big models currently excel in different functions and fields. Furthermore, using multiple AI big models is costly and requires constant switching. Consequently, some AI big model service providers have begun offering AI gateways to serve end users.

[0003] In internet products, account systems are a core infrastructure. Traditional account systems typically use simple independent identifiers or only record direct hierarchical relationships. As the application of AI big models is rapidly developing, if AI big model service providers provide AI gateway products that need to be rapidly disseminated or perform precise user relationship analysis, the following problems may arise: 1. It is difficult to clearly display the multi-level relationships between accounts; 2. When an intermediate account is deleted, its hierarchical relationships are difficult to maintain; 3. There is a lack of effective mechanisms to track the dissemination path of AI gateway products within the user community; 4. It is impossible to flexibly design reward mechanisms based on user relationship networks, resulting in weak user account management capabilities. Summary of the Invention

[0004] To solve the above problems, the purpose of the present invention is to provide an AI gateway account management method and system based on DNA markers, which records the DNA genetic hierarchical relationship between accounts through a character string in a specific format, thereby achieving clear expression of account relationships, flexible management and rapid product dissemination, thereby enabling accurate management and data analysis of users.

[0005] The technical solution provided by the present invention is: an AI gateway account management method based on DNA markers, comprising the following steps: Receive a creation request for a management account, and obtain function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; Generate an account ID to create a user account, generate DNA marker information for the user account based on the account ID and DNA marker information of the management account, and configure the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request; wherein the DNA marker information of the management account is a prefix of the DNA marker information of the user account; An operation request from the management account is received, target account information in the operation request is parsed, and the operation request is executed when it is determined that the management account has operation authority over the target account.

[0006] Preferably, receiving a creation request for a management account, and obtaining the functional attribute information, data permission information, the account ID of the management account, and DNA marker information in the creation request further includes: Read the account level, role, model mapping, level mapping and gear information of the management account, copy the resources, IP whitelist, model whitelist and model restrictions of the management account through maps.Clone, and copy the allowed level of the management account through append; The target character string value of the management account is obtained to obtain DNA mark information and the account ID of the management account is obtained.

[0007] Preferably, generating an account ID to create a user account, generating DNA marker information of the user account based on the account ID and DNA marker information of the management account, and configuring the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request further includes: Generate the user account's DNA signature information based on the following rules: User account's DNA signature information = Management account's DNA signature information + Management account's account ID + "."; Configure the user account: Inherit the account level and role in the creation request to ensure consistency of the permission hierarchy. Inherit the model mapping, level mapping, and gear information in the creation request to maintain unified business logic. Use maps.Clone to copy the resources, IP whitelist, model whitelist, and model restrictions in the creation request. Use append to copy the allowed level of the management account to avoid sharing the underlying array to achieve independence of sub-account permissions. Decoupling the functional attributes and data permission configuration of the user account from the management account or the superior management account to support independent adjustment of permissions to meet flexible business needs; The VirtualLevel configured for the user account is the same as the Level by default. The VirtualLevel is configured to allow individual adjustment to facilitate cross-level account management.

[0008] Preferably, receiving the operation request from the management account, parsing the target account information in the operation request, and executing the operation request when it is determined that the management account has the operation authority for the target account further includes: The DNA identification information of the management account is the DNA identification information of the user account + the account ID of the management account + ".", then the management account and the user account are in a direct management relationship, and the management account has operation authority over the user account; If the DNA flag information of the management account is greater than the DNA flag information of the user account + the account ID of the management account + ".", then the management account and the user account are in an indirect management relationship, and the management account has operation authority over the user account; Execute the operation request.

[0009] Preferably, the method further comprises: Receive access requests sent by management accounts or user accounts, parse the user modelMapper value in the access request to route to the corresponding AI big model API interface. If the user modelMapper value in the access request is empty, route to the AI ​​big model API interface based on the multi-dimensional access rules preset in the AI ​​gateway.

[0010] Preferably, the method further comprises: An account deletion request for a target account is received from a management account or a superior management account, and upon verifying that the management account has operation authority over the target account, the account information of the target account is deleted from the database.

[0011] Preferably, the method further comprises: Verify that the management account has operation authority over the target account; Receive a credit limit management request from a management account or a superior management account for a target account, deduct the parent_balance from the management account or superior management account, and correspondingly increase the parent_balance balance of the target account, where the increase in the parent_balance of the target account is less than the original parent_balance of the management account or superior management account, and record audit information of the credit limit management operation; Receive an authorization operation request from a management account or a superior management account for a target account, and modify a corresponding attribute value of the target account based on the authorization operation request.

[0012] Preferably, the method further comprises: Obtain the account ID and DNA mark information of all management accounts or user accounts in the AI ​​gateway; Perform DNA genetic path analysis based on the account ID and DNA marker information of all management accounts or user accounts to obtain the user group transmission path; the DNA marker information of each account = the DNA marker information of its management account + the account ID of its management account + "."; A reward mechanism is configured based on the DNA genetic pathway analysis results.

[0013] Based on the same concept, the present invention also provides an AI gateway account management system based on DNA markers, including: A request receiving module, configured to receive a request to create a management account, and obtain the function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; An account generation module, configured to generate an account ID to create a user account, generate DNA identifier information for the user account based on the account ID and DNA identifier information of the management account, and configure the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request; wherein the DNA identifier information of the management account is a prefix of the DNA identifier information of the user account; The management execution module is configured to receive an operation request from the management account, parse target account information in the operation request, and execute the operation request when it is determined that the management account has operation authority over the target account.

[0014] Based on the same concept, the present invention further provides an electronic device, comprising: a memory for storing a processing program; A processor, wherein when executing the processing program, the processor implements any one of the above-mentioned AI gateway account management methods based on DNA markers.

[0015] Based on the same concept, the present invention also provides a readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, any one of the above-mentioned AI gateway account management methods based on DNA markers is implemented.

[0016] Due to the adoption of the above technical solution, the present invention has the following advantages and positive effects compared with the prior art: The technical solution of this embodiment uses the DNA marker information of the management account as a prefix to the DNA marker information of the user account to record the DNA genetic hierarchical relationship between accounts, achieving clear expression of account relationships, flexible management, and rapid product dissemination, thereby further enabling precise user management and data analysis. The DNA marker information of the management account serves as a prefix to the DNA marker information of the user account, naturally forming a permission inheritance relationship. Furthermore, by independently configuring user account permissions, flexible permission allocation is supported. Before executing an operation request, the management account's jurisdiction is quickly determined by parsing the target account's DNA marker prefix. This embodiment, based on a hierarchical matching mechanism based on DNA marker prefixes, significantly reduces the complexity of permission verification and improves system response efficiency compared to traditional role / attribute tag matching. Combining biometric encoding with permission management, it not only strengthens identity authentication by leveraging the uniqueness of DNA, but also enables structured permission management through marker prefixes. This solves the problems of identity isolation, coarse-grained permissions, and difficult auditing in traditional account systems, making it suitable for AI gateway scenarios with high security requirements (such as medical data sharing and financial model services). BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The specific embodiments of the present invention are further described in detail below with reference to the accompanying drawings, wherein: Figure 1 This is a flow chart of the AI ​​gateway account management method based on DNA markers of the present invention; Figure 2 This is a schematic diagram of the composition of the AI ​​gateway system based on DNA markers of the present invention. DETAILED DESCRIPTION

[0018] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments. The advantages and features of the present invention will become more apparent from the following description and claims. It should be noted that the drawings are greatly simplified and not to exact ratios, and are intended solely to facilitate and clearly illustrate the embodiments of the present invention.

[0019] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the various components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0020] First embodiment like Figure 1 As shown, this embodiment provides an AI gateway account management method based on DNA markers, including the following steps: Receive a creation request for a management account, and obtain function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; Generate an account ID to create a user account, generate DNA marker information for the user account based on the account ID and DNA marker information of the management account, and configure the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request; wherein the DNA marker information of the management account is a prefix of the DNA marker information of the user account; An operation request from the management account is received, target account information in the operation request is parsed, and the operation request is executed when it is determined that the management account has operation authority over the target account.

[0021] The technical solution of this embodiment records the DNA genetic hierarchical relationship between accounts by prefixing the DNA marker information of the management account with the DNA marker information of the user account. This enables clear expression of account relationships, flexible management, and rapid product dissemination, thereby further enabling precise user management and data analysis. The management account's DNA marker information, prefixed with the user account's DNA marker information, naturally forms a permission inheritance relationship. Furthermore, by independently configuring user account permissions, flexible permission allocation is supported. For example, the management account can grant basic permissions to user accounts in batches while customizing differentiated permissions for specific user accounts to meet the needs of complex organizational structures. It should be noted that, to facilitate the description of the relationship between parent accounts, child accounts, and ancestor accounts, in this embodiment, the account with account creation permission is referred to as the management account, and the account being created / operated is referred to as the user account. Once a user account is created, further user accounts can be created. At this point, the original user is referred to as the management account, and the original management account is referred to as the superior management account. For example, if account A creates account B, account A becomes the management account, and account B becomes the user account. When account B creates account C, account B becomes the management account, account C becomes the user account, and account A becomes the superior management account. Before executing an operation request, the jurisdiction of the management account is quickly determined by parsing the DNA signature prefix of the target account. This embodiment is based on a hierarchical matching mechanism based on DNA signature prefixes. Compared with traditional role / attribute tag matching, it greatly reduces the complexity of permission verification and improves system response efficiency. Combining biometric encoding with permission management not only utilizes the uniqueness of DNA to strengthen identity authentication, but also implements structured management of permissions through signature prefixes. This solves the problems of identity isolation, coarse-grained permissions, and audit difficulties in traditional account systems. It is suitable for AI gateway scenarios with high security requirements (such as medical data sharing, financial model services, etc.).

[0022] Preferably, receiving a creation request for a management account, and obtaining the functional attribute information, data permission information, the account ID of the management account, and DNA marker information in the creation request further includes: Read the account level, role, model mapping, level mapping and gear information of the management account, copy the resources, IP whitelist, model whitelist and model restrictions of the management account through maps.Clone, and copy the allowed level of the management account through append; The target character string value of the management account is obtained to obtain DNA mark information and the account ID of the management account is obtained.

[0023] The technical solution of this embodiment reads the management account's core configurations, including account level, role, and model mapping, and uses maps.Clone to deep copy resources, IP whitelists, and model whitelists. This allows user accounts to directly inherit the management account's complete permissions system, reducing duplication. Using maps.Clone to deep copy key configurations, such as resources and whitelists, ensures that the user and management account configuration files are independent of each other. Modifying user account configurations does not affect the management account, avoiding the risk of permission coupling. Model restrictions and tier information are copied to clarify the user account's model usage scope and resource quota, preventing resource misuse and abnormal system load. The DNA signature inherits the management account prefix. Combined with model mapping and level mapping information, it forms a hierarchical identity chain, facilitating the tracking of account permission sources and operational responsibilities. By inheriting the management account's model mapping (e.g., the mapping between model ID and permission) and level mapping (e.g., the mapping between role and operation level), user accounts can precisely match the models and operational permissions required by their business, achieving fine-grained control. By copying tier information (e.g., resource usage priority or quota limits), user accounts can dynamically adjust resource allocation strategies based on actual needs, balancing flexibility and resource utilization.

[0024] Preferably, generating an account ID to create a user account, generating DNA marker information of the user account based on the account ID and DNA marker information of the management account, and configuring the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request further includes: Generate the user account's DNA signature information based on the following rules: User account's DNA signature information = Management account's DNA signature information + Management account's account ID + "."; Configure the user account: Inherit the account level and role in the creation request to ensure consistency of the permission hierarchy. Inherit the model mapping, level mapping, and gear information in the creation request to maintain unified business logic. Use maps.Clone to copy the resources, IP whitelist, model whitelist, and model restrictions in the creation request. Use append to copy the allowed level of the management account to avoid sharing the underlying array to achieve independence of sub-account permissions. Decoupling the functional attributes and data permission configuration of the user account from the management account or the superior management account to support independent adjustment of permissions to meet flexible business needs; The VirtualLevel configured for the user account is the same as the Level by default. The VirtualLevel is configured to allow individual adjustment to facilitate cross-level account management.

[0025] A string in a specific format records the DNA genetic hierarchy relationship between accounts In this embodiment, the DNA signature of a user account consists of the management account's DNA signature, the account ID, and a separator (.), forming a tree-like hierarchical structure (e.g., ParentDNA.ParentID.). This structure preserves kinship while ensuring global uniqueness, facilitating permission tracing and accountability. The DNA signature generation rules incorporate the account ID to avoid collision risks caused by random generation. The inheritance mechanism strengthens the trustworthiness of the signature and reduces the possibility of unauthorized account impersonation. By inheriting the management account's account level and roles, the permission hierarchy of a child account remains consistent with that of the parent account, avoiding confusion caused by manual configuration differences. By inheriting model mappings, level mappings, and gear information, user accounts can directly reuse the management account's business rules (such as model permissions and resource quotas), reducing duplication and ensuring consistent business logic. Using maps.Clone to deep copy resources, IP whitelists, and model whitelists ensures that user and management account configuration files do not interfere with each other, avoiding security risks caused by sharing underlying data. By appending permission levels, while retaining the basic permissions of the management account, user accounts can expand to higher permissions, achieving incremental upgrades in permissions. Decouple the functional attributes and data permissions of user accounts from management accounts, support independent adjustments (such as individually modifying the data access scope of user accounts), and adapt to dynamic business needs (such as temporary authorization or permission revocation).

[0026] A key aspect of this implementation is cross-level management: VirtualLevel defaults to the same level, but supports independent adjustment. This allows user accounts to obtain cross-level permissions (such as in emergency operations) without changing their actual level, improving management flexibility. This avoids the rigidity of permissions caused by hierarchical solidification, while also enabling traceability of permission adjustments through VirtualLevel tagging.

[0027] The technical solution of this embodiment has good system maintainability and scalability. The hierarchical design of DNA marks provides a clear attribution path for operation logs (such as ParentDNA.ParentID.ChildID), which facilitates tracing the source of operations and enhances security audit capabilities. It is adaptable to multiple business scenarios, supports diverse needs from strict permission inheritance (such as in the financial field) to flexible and independent adjustment (such as in R&D environments), and has a wide range of business adaptability. Through the hierarchical generation of DNA marks, structured inheritance of configurations, permission decoupling and independent adjustment, and the combination of deep copy and incremental copy, an account management system with trusted identity, precise permissions, and flexible and controllable control is achieved.

[0028] Preferably, receiving the operation request from the management account, parsing the target account information in the operation request, and executing the operation request when it is determined that the management account has the operation authority for the target account further includes: The DNA identification information of the management account is the DNA identification information of the user account + the account ID of the management account + ".", then the management account and the user account are in a direct management relationship, and the management account has operation authority over the user account; If the DNA flag information of the management account is greater than the DNA flag information of the user account + the account ID of the management account + ".", then the management account and the user account are in an indirect management relationship, and the management account has operation authority over the user account; Execute the operation request.

[0029] The technical solution of this embodiment enables precise distinction between direct and indirect management relationships. Direct management: When the management account's DNA flag is identical to the user account's DNA flag + management account ID + ".", it indicates a direct superior-subordinate relationship, and the management account has direct operational authority. Indirect management: When the management account's DNA flag is greater than the user account's DNA flag + management account ID + ".", it indicates that the user account is at a lower level (not directly connected) than the management account, but still falls under its jurisdiction. The management account can exercise authority through an indirect relationship. This clearly delineates authority boundaries and supports multi-level management structures (such as group-branch-department hierarchies). Indirect management relationships, on the other hand, only allow superior accounts to operate subordinate accounts, preventing cross-level lateral authority violations (such as accounts at the same level operating on each other) and improving system security. This embodiment uses string matching (such as prefix matching or length comparison) to quickly determine permissions, eliminating the need for frequent database queries or complex logic invocations, reducing system overhead, and achieving lightweight permission verification. This embodiment also separates VirtualLevel from Level to allow temporary adjustment of account permissions (such as cross-level operations) while preserving the actual hierarchical structure, adapting to emergency scenarios or special business needs. The functional attributes and data permissions of user accounts are decoupled from management accounts, supporting independent adjustments (such as modifying data permissions separately) to meet flexible business policy changes.

[0030] This implementation is scalable and audit-friendly, supporting large-scale organizational structures. The hierarchical design of the DNA identifier is naturally adapted to complex organizational structures (such as multi-level branches and nested teams). New accounts automatically inherit the rules of their parent node, eliminating the need to restructure the permissions system. Changes and operations are traceable and auditable. The hierarchical structure of the DNA identifier (e.g., ParentDNA.ParentID.ChildID) clearly records account ownership, and operation logs can be traced back to specific management nodes, facilitating security audits and accountability.

[0031] In a preferred embodiment, the method further comprises: Receive access requests sent by management accounts or user accounts, parse the user modelMapper value in the access request to route to the corresponding AI big model API interface. If the user modelMapper value in the access request is empty, route to the AI ​​big model API interface based on the multi-dimensional access rules preset in the AI ​​gateway.

[0032] The technical solution of this embodiment provides flexible and precise routing capabilities. By parsing the user modelMapper value, the system can accurately route requests to the target AI large model API interface based on custom identifiers in the request (such as model version, business scenario tags, etc.), supporting differentiated model call requirements (such as different algorithm branches and functional modules) and implementing dynamic model mapping. When the user modelMapper is empty, multi-dimensional access rules (such as load balancing, resource priority, user permission level, etc.) are automatically triggered to avoid request failures due to configuration errors and improve system fault tolerance. Multi-dimensional rules can comprehensively consider factors such as the real-time load of the API interface (such as QPS, response latency) and resource utilization (such as GPU / CPU utilization) to dynamically select the optimal node, prevent single point overload, and ensure service stability. Combined with user account permission levels (such as management account priority) or business priorities (such as paid user privileges), hierarchical resource scheduling is achieved, improving the response efficiency of high-value requests and implementing a hierarchical scheduling strategy.

[0033] In a preferred embodiment, the method further comprises: An account deletion request for a target account is received from a management account or a superior management account, and upon verifying that the management account has operation authority over the target account, the account information of the target account is deleted from the database.

[0034] In this embodiment, only management accounts or superior management accounts are allowed to initiate deletion requests for target accounts. Operational permissions are verified through DNA tag matching or hierarchical relationships to prevent unauthorized operations (such as illegal deletion of peer or subordinate accounts). Account deletion involves data purging, requiring strict permission management. By verifying the hierarchical relationship between the management account's DNA prefix and the target account's tag (such as a parent account deleting a child account), the legitimacy of the operation is ensured, reducing the risk of accidental or malicious deletion. A key difference between this embodiment and the existing technology is that even if an intermediate-level management account is physically deleted, its user account (sub-account) can still exist in the AI ​​gateway system and operate as a zero-level account. This is because the DNA tag information of the management account (parent account) of the account remains the prefix of the DNA tag information of the user account (sub-account) of the account, and the management account (parent account) still has operational permissions over its user account (sub-account). In other words, deleting any account in the system will not affect the normal operation of its superior and subordinate accounts.

[0035] In a preferred embodiment, the method further comprises: Verify that the management account has operation authority over the target account; Receive a credit limit management request from a management account or a superior management account for a target account, deduct the parent_balance from the management account or superior management account, and correspondingly increase the parent_balance balance of the target account, where the increase in the parent_balance of the target account is less than the original parent_balance of the management account or superior management account, and record audit information of the credit limit management operation; Receive an authorization operation request from a management account or a superior management account for a target account, and modify a corresponding attribute value of the target account based on the authorization operation request.

[0036] The technical solution of this embodiment realizes the transfer of quota from the management account to the target account through the deduction and increment mechanism of parent_balance, and the increment of the target account is strictly less than the original value of the management account (such as avoiding resource abuse caused by full transfer), ensuring the controllability of resource allocation. The superior management account can allocate resources across levels and support dynamic quota management under a multi-level organizational structure (such as the group allocating budgets to subsidiaries, or the superior management account’s budget for user accounts). Limiting the increase in the parent_balance of the target account prevents the expansion of target account permissions or resource abuse caused by excessive quota tilt, thereby reducing security risks. Permission verification based on DNA marks ensures that only legitimate management accounts can operate the target account, avoiding unauthorized operations. The management account can achieve flexible configuration of permissions by modifying the attribute values ​​of the target account (such as roles, data permissions, function switches, etc.), adapt to changes in business needs (such as temporary authorization or permission recovery), and realize dynamic permission adjustment.

[0037] In a preferred embodiment, the method further comprises: Obtain the account ID and DNA mark information of all management accounts or user accounts in the AI ​​gateway; Perform DNA genetic path analysis based on the account ID and DNA marker information of all management accounts or user accounts to obtain the user group transmission path; the DNA marker information of each account = the DNA marker information of its management account + the account ID of its management account + "."; A reward mechanism is configured based on the DNA genetic pathway analysis results.

[0038] In the technical solution of this embodiment, each account's DNA signature consists of the management account's DNA signature, the account ID, and a separator (.) (e.g., ParentDNA.ParentID.), forming a unique hierarchical path identifier. By analyzing the DNA signature, the hierarchical relationships and transmission chain of accounts can be clearly restored, enabling accurate tracing of the user group's transmission path, making hierarchical relationships transparent and thus accurately tracing user transmission paths. Based on the contribution of each level of the transmission path (e.g., number of new users attracted, resource consumption, active time, etc.), differentiated reward rules (e.g., tiered commissions, tiered rebates) are configured. For example, a management account can receive a 10% commission on the spending of its direct subordinates and a 5% commission on the spending of its indirect subordinates, incentivizing deep user fission. Based on the transmission path analysis results (e.g., the distribution of high-contribution management accounts and user fission efficiency), reward rules can be optimized (e.g., increasing the reward ratio for popular paths) and resource allocation can be adjusted (e.g., providing additional incentives to high-value management accounts) to improve user growth efficiency. This allows for targeted optimization of user growth strategies. Furthermore, the reward mechanism can be dynamically adjusted based on the DNA path and other dimensions (such as user level and consumption behavior). For example, subordinate users of high-level management accounts can receive higher reward coefficients, or reward rules can be temporarily adjusted for specific business scenarios (such as promotions). This embodiment supports complex organizational structures. The hierarchical design of the DNA mark is naturally adapted to complex models such as multi-level distribution and agency (such as headquarters, regions, branches, and individuals), and can be expanded to large-scale organizational structures without modifying the underlying logic.

[0039] Second embodiment See also Figure 2 Based on the same concept, the present invention also provides an AI gateway account management system based on DNA markers, including: A request receiving module, configured to receive a request to create a management account, and obtain the function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; An account generation module, configured to generate an account ID to create a user account, generate DNA identifier information for the user account based on the account ID and DNA identifier information of the management account, and configure the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request; wherein the DNA identifier information of the management account is a prefix of the DNA identifier information of the user account; The management execution module is configured to receive an operation request from the management account, parse target account information in the operation request, and execute the operation request when it is determined that the management account has operation authority over the target account.

[0040] The technical solution of this embodiment uses the DNA marker information of the management account as a prefix to the DNA marker information of the user account to record the DNA genetic hierarchical relationship between accounts, achieving clear expression of account relationships, flexible management, and rapid product dissemination, thereby further enabling precise user management and data analysis. The DNA marker information of the management account serves as a prefix to the DNA marker information of the user account, naturally forming a permission inheritance relationship. Furthermore, by independently configuring user account permissions, flexible permission allocation is supported. Before executing an operation request, the management account's jurisdiction is quickly determined by parsing the target account's DNA marker prefix. This embodiment, based on a hierarchical matching mechanism based on DNA marker prefixes, significantly reduces the complexity of permission verification and improves system response efficiency compared to traditional role / attribute tag matching. Combining biometric encoding with permission management, it not only strengthens identity authentication by leveraging the uniqueness of DNA, but also enables structured permission management through marker prefixes. This solves the problems of identity isolation, coarse-grained permissions, and difficult auditing in traditional account systems, making it suitable for AI gateway scenarios with high security requirements (such as medical data sharing and financial model services).

[0041] Based on the same concept, the present invention also provides an electronic device, comprising: a memory, the memory being used to store a processing program; and a processor, the processor implementing any one of the above-mentioned AI gateway account management methods based on DNA markers when executing the processing program.

[0042] Based on the same concept, the present invention also provides a readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, any one of the above-mentioned AI gateway account management methods based on DNA markers is implemented.

[0043] If the AI ​​gateway account management method based on DNA markers is implemented in the form of program instructions and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of software. The computer software is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program code.

[0044] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the identification content specifically executed by the above-described system and device can refer to the corresponding process in the aforementioned method embodiment.

[0045] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they still fall within the scope of protection of the present invention.

Claims

1. An AI gateway account management method based on DNA signature, characterized in that: The following steps are involved: Receive a creation request for a management account, and obtain function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; Generate an account ID to create a user account, generate DNA marker information of the user account based on the account ID and DNA marker information of the management account, and configure the functional attribute information and data permission information of the user account based on the functional attribute information and data permission information in the creation request; The DNA mark information of the management account is the prefix of the DNA mark information of the user account; An operation request from the management account is received, target account information in the operation request is parsed, and the operation request is executed when it is determined that the management account has operation authority over the target account.

2. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: Receiving a creation request for a management account, and obtaining the function attribute information, data permission information, the account ID of the management account, and DNA marker information in the creation request further includes: Read the account level, role, model mapping, level mapping and gear information of the management account, copy the resources, IP whitelist, model whitelist and model restrictions of the management account through maps.Clone, and copy the allowed level of the management account through append; The target character string value of the management account is obtained to obtain DNA mark information and the account ID of the management account is obtained.

3. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: Generating an account ID to create a user account, generating DNA identifier information of the user account based on the account ID and DNA identifier information of the management account, and configuring the function attribute information and data permission information of the user account based on the function attribute information and data permission information in the creation request further includes: Generate the DNA signature information of the user account based on the following rules: DNA signature information of the user account = DNA signature information of the management account + account ID of the management account + ".."; Configure the user account: Inherit the account level and role in the creation request to ensure consistency of the permission hierarchy. Inherit the model mapping, level mapping, and gear information in the creation request to maintain unified business logic. Use maps.Clone to copy the resources, IP whitelist, model whitelist, and model restrictions in the creation request. Use append to copy the allowed level of the management account to avoid sharing the underlying array to achieve independence of sub-account permissions. Decoupling the functional attributes and data permission configuration of the user account from the management account or the superior management account to support independent adjustment of permissions to meet flexible business needs; The VirtualLevel configured for the user account is the same as the Level by default. The VirtualLevel is configured to allow individual adjustment to facilitate cross-level account management.

4. The AI ​​gateway account management method based on DNA markers according to claim 3 is characterized in that: Receiving an operation request from the management account, parsing target account information in the operation request, and executing the operation request when it is determined that the management account has operation authority over the target account further includes: The DNA marker information of the management account is the DNA marker information of the user account + the account ID of the management account + ".", then the management account and the user account are in a direct management relationship, and the management account has operation authority over the user account; If the DNA flag information of the management account is greater than the DNA flag information of the user account + the account ID of the management account + ".", then the management account and the user account are in an indirect management relationship, and the management account has operation authority over the user account; Execute the operation request.

5. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: The method further comprises: Receive access requests sent by management accounts or user accounts, parse the user modelMapper value in the access request to route to the corresponding AI big model API interface. If the user modelMapper value in the access request is empty, route to the AI ​​big model API interface based on the multi-dimensional access rules preset in the AI ​​gateway.

6. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: The method further comprises: An account deletion request for a target account is received from a management account or a superior management account, and upon verifying that the management account has operation authority over the target account, the account information of the target account is deleted from the database.

7. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: The method further comprises: Verify that the management account has operation authority over the target account; Receive a credit limit management request from a management account or a superior management account for a target account, deduct the parent_balance from the management account or superior management account, and correspondingly increase the parent_balance balance of the target account, where the increase in the parent_balance of the target account is less than the original parent_balance of the management account or superior management account, and record audit information of the credit limit management operation; Receive an authorization operation request from a management account or a superior management account for a target account, and modify a corresponding attribute value of the target account based on the authorization operation request.

8. The AI ​​gateway account management method based on DNA markers according to claim 1 is characterized in that: The method further comprises: Obtain the account ID and DNA mark information of all management accounts or user accounts in the AI ​​gateway; Perform DNA genetic path analysis based on the account ID and DNA marker information of all management accounts or user accounts to obtain the user group transmission path; the DNA marker information of each account = the DNA marker information of its management account + the account ID of its management account + ".."; A reward mechanism is configured based on the DNA genetic pathway analysis results.

9. An AI gateway account management system based on DNA signature, characterized in that: include: A request receiving module, configured to receive a request to create a management account, and obtain the function attribute information, data permission information, account ID of the management account, and DNA flag information in the creation request; An account generation module, configured to generate an account ID to create a user account, generate DNA identifier information of the user account based on the account ID and DNA identifier information of the management account, and configure the function attribute information and data permission information of the user account based on the function attribute information and data permission information in the creation request; The DNA mark information of the management account is the prefix of the DNA mark information of the user account; The management execution module is configured to receive an operation request from the management account, parse target account information in the operation request, and execute the operation request when it is determined that the management account has operation authority over the target account.

10. An electronic device, characterized in that: include: a memory for storing a processing program; A processor, wherein when executing the processing program, the processor implements the AI ​​gateway account management method based on DNA markers as described in any one of claims 1 to 8.

Images