A rule object-based management method and device in an AI operating system and a readable storage medium

Abstract

The application provides a rule object-based management method and device in an AI operating system and a readable storage medium. The method comprises: performing pre-access consistency verification on a to-be-accessed object to obtain a first verification result; if the first verification result is a verification pass, registering the to-be-accessed object, and determining a target rule object according to object description information; establishing binding association information based on the object description information and the target rule object; obtaining actual running information of the to-be-accessed object, and performing runtime consistency verification on the actual running information based on the binding association information and the target rule object to obtain a second verification result; performing a corresponding control operation according to a control strategy mapping relationship of the second verification result and the target rule object, and generating an execution archive record. The embodiment of the application can ensure that the to-be-accessed object does not run out of the access time admission condition based on the binding association information, and improve the accuracy and traceability of system operation control.

Description

Technical Field

[0001] This application belongs to the field of electronic digital data processing technology, and in particular relates to a management method, device and readable storage medium based on rule objects in an AI operating system. Background Technology

[0002] With the development of artificial intelligence systems, AI operating systems typically need to integrate various types of objects, such as large language models, intelligent agents, vector database adapters, knowledge graph managers, inference engines, tool plugins, task execution components, data processing components, external service interfaces, and policy control components. After being integrated into the system, these objects usually participate in processes such as task scheduling, permission invocation, interface access, data processing, inference execution, and state updates.

[0003] In existing technologies, the aforementioned objects are typically governed using separate mechanisms such as object registration, access control, task scheduling, interface access control, and log auditing. For example, the object registration mechanism is only responsible for object registration, the access control mechanism is only responsible for permission allocation, the task scheduling mechanism is only responsible for execution scheduling, the interface management mechanism is only responsible for interface call control, and the logging system is only responsible for recording some runtime events.

[0004] This decentralized governance approach can easily lead to a disconnect between the actual control logic of the object to be connected at runtime and the access conditions at the time of connection, increasing the operational risk of the AI ​​operating system. Summary of the Invention

[0005] This application provides a rule-based object management method, apparatus, and readable storage medium in an AI operating system, which can solve the problem that the actual control logic of the object to be accessed may be disconnected from the access conditions after access.

[0006] In a first aspect, embodiments of this application provide a rule-based management method in an AI operating system, including: When an object to be accessed is accessed, its object description information is obtained. Perform a pre-access consistency check on the object to be accessed to obtain a first check result; If the first verification result is successful, the object to be accessed is registered, and the target rule object is determined from the rule object set according to the object description information; Based on the object description information and the target rule object, establish binding association information; During the operation of the object to be accessed, the actual operation information of the object to be accessed is obtained, and at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual operation information is compared with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result; Based on the mapping relationship between the second verification result and the control policy of the target rule object, the corresponding control operation is executed, and an execution archive record is generated. The execution archive record is used to record information related to the object to be accessed, the target rule object, and the control operation.

[0007] Secondly, embodiments of this application provide a rule-based management device in an AI operating system, comprising: The acquisition module is used to acquire the object description information of the object to be accessed when the object is accessed. The pre-access verification module is used to perform a pre-access consistency verification on the object to be accessed and obtain a first verification result. The rule object matching module is used to register the object to be accessed if the first verification result is that the verification is passed, and to determine the target rule object from the rule object set according to the object description information. The binding association establishment module is used to establish binding association information based on the object description information and the target rule object; The runtime verification module is used to obtain the actual running information of the object to be accessed during the running process of the object to be accessed, and compare at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual running information with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result; The control operation execution module is used to execute corresponding control operations based on the control strategy mapping relationship between the second verification result and the target rule object; The execution archiving module is used to generate execution archive records, which are used to record information related to the object to be accessed, the target rule object, and the control operation.

[0008] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any one of the first aspects above.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of the first aspects above.

[0010] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to perform the method described in any one of the first aspects above.

[0011] The beneficial effects of the embodiments in this application compared with the prior art are: This application embodiment obtains the object description information of the object to be accessed when the object is accessed; performs a pre-access consistency check on the object to be accessed to obtain a first check result; if the first check result is successful, the object to be accessed is registered, and a target rule object is determined from the rule object set based on the object description information. Then, based on the object description information and the target rule object, binding association information is established; the target rule object is used as a unified rule benchmark to provide a continuous association structure throughout the entire lifecycle for subsequent consistency checks, ensuring the consistency of the control mainline of the object to be accessed throughout the entire lifecycle; during the operation of the object to be accessed, the actual operation information of the object to be accessed is obtained, and the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, and actual... At least one of the following, the actual rule version information and the actual lifecycle status information, is compared with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result. Based on the second verification result and the control strategy mapping relationship of the target rule object, the corresponding control operation is executed, so that when the object to be connected is running, verification is performed based on the binding association information and the target rule object, which improves the inheritance and constraint of the access conditions after access in the verification process, and ensures that the object to be connected does not run independently from the consistency control main line during runtime. In addition, by generating execution archive records, a traceable archive chain of the object to be connected is formed, which ensures the consistency of the rule version and the continuity of control operations of the object to be connected throughout its lifecycle, and ensures that the object to be connected does not run independently from the access conditions at the time of access, thereby improving the accuracy and traceability of the AI ​​operating system's operation control.

[0012] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of the first type of management method based on rule objects in an AI operating system provided in an embodiment of this application; Figure 2 This is a schematic diagram of the second process of a rule-based management method in an AI operating system provided in an embodiment of this application; Figure 3 This is a schematic diagram of the third process of the rule object-based management method in an AI operating system provided in an embodiment of this application; Figure 4 This is a schematic diagram of the fourth process of the rule object-based management method in an AI operating system provided in an embodiment of this application; Figure 5 This is a schematic diagram of the fifth process of a rule-based management method in an AI operating system provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a rule-based management device in an AI operating system provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0015] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0016] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0017] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0018] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0019] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0020] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0021] In some embodiments, the rule-based object management method in the AI ​​operating system of this application is applied to the AI ​​operating system. The AI ​​operating system is a platform for artificial intelligence applications, providing a unified environment for access review, operation control, resource scheduling, and full lifecycle governance for various objects to be accessed, ensuring that the objects to be accessed operate safely, controllably, and traceably under their original access conditions.

[0022] Figure 1 This is a schematic diagram of the first type of management method based on rule objects in an AI operating system provided in an embodiment of this application. For example... Figure 1 The method shown includes steps S11 to S16, which are described in detail below: S11: When an object is to be accessed, obtain the object description information of the object to be accessed.

[0023] In some implementations, when an object to be accessed is accessed, the AI ​​operating system receives the access request from the object to be accessed, and in response to the access request, obtains the object description information of the object to be accessed.

[0024] In the application, when a new external requirement arises to access a new object, the object to be accessed interacts with the AI ​​operating system, generates an access request, and the AI ​​operating system receives the access request and then obtains the object description information of the object to be accessed.

[0025] For example, the objects to be integrated include any one of the following: large language model module, intelligent agent module, vector database adapter, knowledge graph manager, inference engine, tool plugin, task execution component, and external service interface. Memory management of the objects to be integrated is one implementation method for integrating the AI ​​operating system, and is constrained by the target rule object, permission identifier, lifecycle control handle, and rule version information.

[0026] In some implementations, object description information includes object identifier, object type information, interface description information, dependency information, permission declaration information, and integrity verification information.

[0027] Among them, the object identifier is the unique identifier of the object to be accessed, and the integrity verification information indicates whether the files, configurations, images or code digests of the object to be accessed have changed.

[0028] For example, the object description information includes the object identifier object_id, module type information: module_type, interface description information: interface_desc, dependency information: dependency_info, permission declaration information: permission_claim, and integrity verification information: integrity_value.

[0029] {"object_id":"agent_plugin_001","module_type":"tool_plugin","interface_desc":["read_file","write_log"],"dependency_info":["vector_db","tas k_scheduler"],"permission_claim":["read_workspace","write_audit_log"],"integrity_value":"hash_8f21ab","version_info":"1.0.3","runtime_env": "container_runtime"} In some embodiments, the object description information may also include auxiliary fields such as object version information, runtime environment information, and resource requirement information.

[0030] S12: Perform a pre-access consistency check on the object to be accessed and obtain the first check result.

[0031] In the application, the self-attributes declared by the object to be accessed are compared in multiple dimensions to achieve consistency verification before access, and to determine whether the object to be accessed conforms to the target rule object in dimensions such as identity, content, interface, dependency and permission.

[0032] In some implementations, verification is performed on dimensions such as identity identification, content integrity, interface capabilities, dependencies, and permission requirements to conduct consistency checks before integration.

[0033] S13: If the first verification result is successful, the object to be accessed is registered, and the target rule object is determined from the rule object set according to the object description information.

[0034] The rule object is used to constrain the access, registration, operation, permissions, interfaces, dependencies, integrity, and lifecycle state of the object to be accessed. The target rule object is a rule object determined from the set of rule objects whose applicable conditions match the object description information of the object to be accessed.

[0035] In some implementations, the rule object includes a rule object identifier, rule version information, rule type information, applicable object type information, permission constraint information, dependency constraint information, interface constraint information, integrity verification constraint information, lifecycle constraint information, and control policy mapping relationship.

[0036] For example, a rule object includes a rule object identifier: rule_id, rule version information: rule_version, applicable object type: applicable_type, interface constraint: interface_constraint, permission constraint: permission_constraint, dependency constraint: dependency_constraint, integrity constraint: integrity_constraint, lifecycle constraint: lifecycle_constraint, and control policy mapping relationship: control_policy.

[0037] {"rule_id": "rule_tool_plugin_001","rule_version": "v2.1","applicable_type": "tool_plugin","interface_constraint":["read_file","write_log"],"permission_constraint":["read_workspace","write_audit_log"],"dependency_constrain t":["vector_db","task_scheduler"],"integrity_constraint":"hash_required","lifecycle_constraint":["registered","running","frozen","unloading","ter cited"],"control_policy":{"permission_mismatch":"revoke_permission","integrity_mismatch":"freeze_object","dependency_mismatch":"pause_dependenc y_call","interface_mismatch":"block_interface_call","version_incompatible":"trigger_rule_review","lifecycle_abnormal":"trigger_lifecycle_review"}} Using the target rule object corresponding to the object to be connected as a unified rule benchmark, the object to be connected uses the same source rule basis before connection, during runtime, and after execution, forming a closed loop based on a unified rule version, reducing the occurrence of rule version errors throughout the entire lifecycle.

[0038] Step S13: Determine the target rule object from the rule object set based on the object description information, including: S131: Match the information in the object description with the information in each candidate rule object in the rule object set.

[0039] In the application, object description information is read to obtain object identifier, object type information, interface description information, dependency information, permission declaration information, and integrity verification information. Then, each candidate rule object in the rule object set is traversed, and the applicable object type information, permission constraint information, dependency constraint information, interface constraint information, and integrity verification constraint information of the currently traversed candidate rule object are matched with the object type information, permission declaration information, dependency information, interface description information, and integrity verification information in the object description information. Candidate rule objects that meet all matching conditions are determined as target rule objects.

[0040] S132: If the candidate rule object's adaptive object type information matches the object type information of the object description information, the candidate rule object's interface constraint information covers the interface description information of the object description information, the candidate rule object's dependency constraint information covers the dependency relationship information of the object description information, the permission declaration information of the object description information does not exceed the permission constraint information of the candidate rule object, and the integrity verification information of the object description information conforms to the integrity verification constraint information of the candidate rule object, then the target rule object is obtained.

[0041] In some implementations, the interface constraint information of the candidate rule object covers the interface description information of the object description information. This means that the interface constraint information includes each interface identifier in the interface description information, or the ratio between the number of intersections between the interface constraint information and the interface identifiers and the total number of interface identifiers is greater than or equal to a preset interface coverage threshold. The total number of interface identifiers is determined based on the interface description information.

[0042] In application, each interface identifier is obtained from the interface description information. If information corresponding to each interface identifier is found in the interface constraint information, it is determined that the interface constraint information includes each interface identifier in the interface description information. Therefore, it is determined that the interface constraint information of the candidate rule object covers the interface description information of the object description information. Alternatively, the number of intersections is determined based on the information of the corresponding interface identifier found in the interface constraint information, and then the ratio between the number of intersections and the total number of interface identifiers is calculated. If the ratio is greater than or equal to a preset interface coverage threshold, it is determined that the interface constraint information of the candidate rule object covers the interface description information of the object description information.

[0043] The preset interface coverage threshold can be determined based on the security level of the AI ​​operating system or the object type. For example, the calculation formula is: Ratio = Number of intersections / Total number of interface identifiers. The preset interface coverage threshold is 0.8, 0.9, or 1.0.

[0044] The dependency constraint information of the candidate rule object covers the dependency relationship information of the object description information. The dependency constraint information includes the identifier of each dependent object in the dependency relationship information, or the dependency type corresponding to each dependent object identifier in the dependency relationship information belongs to the set of allowed dependency types of the target rule object. The set of allowed dependency types is determined based on the dependency constraint information.

[0045] In application, the identifiers of each dependent object are obtained from the dependency relationship information. If information corresponding to each dependent object identifier is found in the dependency constraint information, it is determined that the dependency constraint information contains each dependent object identifier in the dependency relationship information, and thus it is determined that the dependency constraint information of the candidate rule object covers the dependency relationship information of the object description information. Alternatively, the set of allowed dependency types for the target rule object is determined based on the dependency constraint information of the candidate rule object. If a dependency type corresponding to each dependent object identifier is found in the set of allowed dependency types, it is determined that the dependency type corresponding to each dependent object identifier in the dependency relationship information belongs to the set of allowed dependency types for the target rule object, and thus it is determined that the dependency constraint information of the candidate rule object covers the dependency relationship information of the object description information.

[0046] The permission declaration information of the object description information does not exceed the permission constraint information of the candidate rule object. The permission constraint information includes each permission identifier in the permission declaration information, or the permission level of the permission declaration information is less than or equal to the highest permission level of the target rule object. The highest permission level is determined based on the permission constraint information.

[0047] In the application, each permission identifier is obtained from the permission declaration information. If information corresponding to each permission identifier is found in the permission constraint information, it is determined that the permission constraint information contains each permission identifier in the permission declaration information, and thus it is determined that the permission declaration information of the object description information does not exceed the permission constraint information of the candidate rule object. Alternatively, the highest permission is determined based on the permission constraint information, and the permission level is determined based on the permission declaration information. The permission level is compared with the highest permission. If the permission level of the permission declaration information is less than or equal to the highest permission level of the target rule object, it is determined that the permission declaration information of the object description information does not exceed the permission constraint information of the candidate rule object.

[0048] The integrity verification information of the object description information conforms to the integrity verification constraint information of the candidate object, which satisfies the integrity verification constraint.

[0049] In the application, integrity verification information is matched with integrity verification constraint information. If the integrity verification information meets the integrity verification constraint, then the integrity verification information of the object description information is determined to conform to the integrity verification constraint information of the candidate rule object.

[0050] S14: Establish binding association information based on object description information and target rule object.

[0051] The binding association information is used to associate the data structures of the object to be accessed, the object description information, and the target rule object. This binding association information serves as an intermediate constraint between the pre-access admission conditions and runtime consistency verification. By binding association information, the runtime verification error caused by the object to be accessed running independently without adhering to the admission conditions can be reduced, thus lowering the runtime error release rate.

[0052] For example, the binding association information includes binding association identifier: binding_id, object identifier to be connected: object_id, target rule object identifier; rule_id, rule version information; rule_version, permission constraint: permission_constraint, interface constraint: interface_constraint, dependency constraint: dependency_constraint, integrity verification value: integrity_value, lifecycle state: lifecycle_state, and binding time: bind_time.

[0053] {"binding_id":"binding_20260424_001","object_id":"agent_plugin_001","rule_id":"rule_tool_plugin_001","rule_version":"v2.1","permission_constraint":["read_workspace","write_audit_log"],"interfac e_constraint":["read_file","write_log"],"dependency_constraint":["vector_db","task_scheduler"],"integrity_value":"hash_8f21ab","lifecycle_state":"registered","bind_time":"2026-04-24T10:30:00Z"} In some implementations, a binding association identifier, lifecycle state, and binding time are generated when establishing binding association information. Then, the binding association identifier, lifecycle state, and binding time are associated and bound with the object identifier, integrity verification information of the object to be connected, and the rule object identifier, rule version information, permission constraint information, dependency constraint information, and interface constraint information of the target rule object to obtain the binding association information.

[0054] Correspondingly, the binding association information includes the binding association identifier, lifecycle status, binding time, object identifier of the object to be connected, integrity verification information, and rule object identifier of the target rule object, rule version information, permission constraint information, dependency constraint information, and interface constraint information. The binding association identifier, lifecycle status, and binding time are generated when the binding association information is established.

[0055] S15: During the operation of the object to be accessed, obtain the actual operation information of the object to be accessed, and compare at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual operation information with the binding association information and the corresponding constraint information in the target rule object to obtain the second verification result.

[0056] In the application, during the operation of the object to be connected, the AI ​​operating system acquires the actual operating information of the object in real time. The actual operating information includes at least one of the following: actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status information.

[0057] Using the target rule object as the constraint benchmark and the binding association information can serve as an intermediate constraint basis between the pre-access admission conditions and the runtime consistency verification. By comparing the actual running information with the binding association information and the target rule object in multiple dimensions such as permissions, interfaces, dependency calls, summaries, version information, and lifecycle status, it is possible to determine whether the object to be accessed runs independently without the access admission conditions.

[0058] In some implementations, when a new external requirement arises, an operation request is generated. The corresponding object to be integrated responds to the input operation request and generates actual operation information. This operation request can be an execution command, a configuration change request, a data retrieval request, etc.

[0059] S16: Based on the mapping relationship between the second verification result and the control strategy of the target rule object, execute the corresponding control operation and generate an execution archive record.

[0060] The control strategy mapping relationship can be set according to the actual application requirements.

[0061] In application, the control operation corresponding to the second verification result is found in the control strategy mapping relationship of the target rule object, and the different operating conditions are handled in a precise and differentiated manner to meet the operating requirements of the AI ​​operating system.

[0062] The execution archive is used to record information related to the object to be connected, the target rule object, and control operations. During the operation of the object to be connected, the information related to the object to be connected is associated to generate a traceable control and archiving closed loop for the object to be connected, providing a foundation for subsequent auditing, fault location, and rule version consistency verification.

[0063] This application embodiment obtains the object description information of the object to be accessed when the object is accessed; performs a pre-access consistency check on the object to be accessed to obtain a first check result; if the first check result is successful, the object to be accessed is registered, and a target rule object is determined from the rule object set based on the object description information. Then, based on the object description information and the target rule object, binding association information is established; the target rule object is used as a unified rule benchmark to provide a continuous association structure throughout the entire lifecycle for subsequent consistency checks, ensuring the consistency of the control mainline of the object to be accessed throughout the entire lifecycle; during the operation of the object to be accessed, the actual operation information of the object to be accessed is obtained, and the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, and actual... At least one of the following, the actual rule version information and the actual lifecycle status information, is compared with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result. Based on the second verification result and the control strategy mapping relationship of the target rule object, the corresponding control operation is executed, so that when the object to be connected is running, verification is performed based on the binding association information and the target rule object, which improves the inheritance and constraint of the access conditions after access in the verification process, and ensures that the object to be connected does not run independently from the consistency control main line during runtime. In addition, by generating execution archive records, a traceable archive chain of the object to be connected is formed, which ensures the consistency of the rule version and the continuity of control operations of the object to be connected throughout its lifecycle, and ensures that the object to be connected does not run independently from the access conditions at the time of access, thereby improving the accuracy and traceability of the AI ​​operating system's operation control.

[0064] In some embodiments, Figure 2 This is a schematic diagram of a second process for a rule-based object management method in an AI operating system provided in an embodiment of this application. For example... Figure 2 As shown, step S12: Perform a pre-access consistency check on the object to be accessed to obtain the first check result, including: S121: Perform uniqueness verification on the object identifier of the object to be accessed.

[0065] In some implementations, the AI ​​operating system maintains a global object identifier registry. It searches this registry for the corresponding object identifier. If at least one corresponding identifier is found, the system determines that the object identifier for the object to be integrated is already in use, and the uniqueness check fails. If no corresponding identifier is found, the system determines that the object identifier for the object to be integrated is not already in use, and the uniqueness check passes.

[0066] S122: Perform digest consistency verification on the integrity verification information of the object to be accessed.

[0067] In some implementations, a new digest is generated based on the information in the object description. This new digest is then compared to the integrity verification information. If the new digest and integrity verification information are different, the integrity verification fails. If they are the same, the integrity verification passes.

[0068] S123: Perform interface constraint validation on the interface description information of the object to be accessed.

[0069] In some implementations, the interface description information of the object to be accessed is checked for compliance. If the AI ​​operating system cannot recognize the interface description information, the interface constraint verification is deemed to have failed. If the AI ​​operating system can recognize the interface description information, the interface constraint verification is deemed to have passed.

[0070] S124: Perform dependency availability verification on the dependencies of the objects to be accessed.

[0071] In some implementations, dependency information is compared with system resources. If the system resources do not meet the requirements of the dependency, the dependent object is determined to be unavailable, and the dependency availability check fails. If the system resources meet the requirements of the dependency, the dependent object is determined to be available, and the dependency availability check passes.

[0072] S125: Perform permission boundary verification on the permission declaration information of the object to be accessed.

[0073] In some implementations, permission boundary checks are performed on the permission declaration information of the object to be accessed, based on the system's preset permission boundaries. If the permissions required by the object to be accessed are not within the allowed range, the second permission check result is determined to be a failure. If the permissions required by the object to be accessed are within the allowed range, the second permission check result is determined to be a success.

[0074] S126: When the uniqueness check, digest consistency check, interface constraint check, dependency availability check, and permission boundary check all pass, generate the first check result that the representation check has passed.

[0075] In application, when each verification passes, it means that the object to be connected meets the pre-access admission conditions of the AI ​​operating system, and the first verification result indicating that the verification has passed is output.

[0076] The first verification result includes verification passed, verification failed, manual review required, and waiting for supplementary information.

[0077] For example, the first verification result includes: pass, reject, review, pending additional information.

[0078] In some embodiments, the actual runtime information includes at least one of the following: actual interface call information, actual permission usage information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status.

[0079] For example, the actual runtime information includes actual interface call information: actual_interface_call, actual permission usage information: actual_permission_use, actual dependency call information: actual_dependency_call, actual integrity summary information: actual_integrity_value, actual rule version information: actual_rule_version, and actual lifecycle state: actual_lifecycle_state.

[0080] Figure 3 This is a schematic diagram of the third process of a rule-based object management method in an AI operating system provided in an embodiment of this application. For example... Figure 3 As shown, step S15: Compare at least one of the following from the actual runtime information: actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status information, with the corresponding constraint information in the binding association information and the target rule object, including: S151: Determine whether the interface call is inconsistent based on the interface constraint information of the actual interface call information and the binding association information.

[0081] In the application, interface constraint information is obtained from the binding association information, and the actual interface call information is compared with the interface constraint information. If the interface constraint information recorded in the binding association information covers the interface description information in the object description information, the interface call is considered consistent. If the interface constraint information recorded in the binding association information does not cover the interface description information in the object description information, the interface call is considered inconsistent.

[0082] For example, the actual interface call information is "send_external_request", and the interface constraint information is ["read_file", "write_log"]. Comparing the actual interface call information with the interface constraint information, it is determined that ["read_file", "write_log"] does not cover "send_external_request". Correspondingly, a second verification result is generated: interface_mismatch (interface call inconsistency).

[0083] S152: Determine whether the permissions are inconsistent based on the actual permission usage information and the permission constraint information of the bound association information.

[0084] In the application, permission constraint information is obtained from the binding association information, and the actual permission usage information is compared with the permission constraint information. If the usage permissions of the object to be accessed do not exceed the permission constraint information recorded in the binding association information, the permissions are determined to be consistent. If the usage permissions of the object to be accessed exceed the permission constraint information recorded in the binding association information, the permissions are determined to be inconsistent.

[0085] For example, the actual permission usage information is ["read_workspace", "write_audit_log", "delete_workspace"]. The permission constraint information is ["read_workspace", "write_audit_log"]. The actual permission usage information is compared with the permission constraint information, and it is determined that `delete_workspace` exceeds the permission constraint information. Correspondingly, a second verification result is generated: `permission_mismatch` (permission mismatch).

[0086] S153: Determine whether the dependency relationship is inconsistent based on the dependency constraint information of the actual dependency call information and the binding association information.

[0087] In the application, dependency constraint information is obtained from the binding association information, and the actual dependency call information is compared with the dependency constraint information. If the dependency constraint information recorded in the binding association information covers the actual dependency call information, the dependency relationship is determined to be consistent. If the dependency constraint information recorded in the binding association information does not cover the actual dependency call information, the dependency relationship is determined to be inconsistent.

[0088] For example, the actual dependency call information is "external_storage_service", and the dependency constraint information is ["vector_db", "task_scheduler"]. Comparing the actual dependency call information with the dependency constraint information determines that ["vector_db", "task_scheduler"] does not cover "external_storage_service", generating a second verification result: dependency_mismatch (inconsistent dependency relationship).

[0089] S154: Determine whether the integrity is inconsistent based on the integrity verification information of the actual integrity summary information and the binding association information.

[0090] In the application, integrity verification information is obtained from the binding association information, and the actual integrity summary information is compared with the integrity verification information. If the actual integrity summary information is the same as the integrity verification information recorded in the binding association information, the integrity is determined to be consistent. If the actual integrity summary information is different from the integrity verification information recorded in the binding association information, the integrity is determined to be inconsistent.

[0091] For example, the actual integrity digest information is "hash_3c91de", and the integrity verification information is "hash_8f21ab". The actual integrity digest information is compared with the integrity verification information. It is determined that "hash_3c91de" and "hash_8f21ab" are different. Correspondingly, a second verification result is generated: integrity_mismatch (integrity inconsistency).

[0092] S155: Determine whether the versions are incompatible based on the actual rule version information and the rule version information of the binding association information.

[0093] In the application, rule version information is obtained from the binding association information, and the actual rule version information is compared with the rule version information. If the actual rule version information is within the version range recorded in the binding association information, the version is determined to be compatible. If the actual rule version information is not within the version range recorded in the binding association information, the version is determined to be incompatible.

[0094] For example, the actual rule version information is "v3.0", and the rule version information is within the version compatibility range "[v2.0, v2.5]". Comparing the actual rule version information with the rule version information, "v3.0" is not within the version range defined by "[v2.0, v2.5]". Correspondingly, a second verification result is generated: version_incompatible (version incompatible).

[0095] S156: Determine whether the lifecycle is abnormal based on the actual lifecycle status and the lifecycle status of the bound associated information.

[0096] In the application, the lifecycle status is obtained from the binding association information, and the actual lifecycle status is compared with the lifecycle status recorded in the binding association information. If the actual lifecycle status matches the lifecycle status recorded in the binding association information, the lifecycle is determined to be normal. If the actual lifecycle status does not match the lifecycle status recorded in the binding association information, the lifecycle is determined to be abnormal.

[0097] Correspondingly, the second verification results include inconsistent interface calls, inconsistent permissions, inconsistent integrity, inconsistent dependencies, inconsistent integrity, version incompatibility, and abnormal lifecycle.

[0098] For example, the second verification result includes consistent: consistent, permission mismatch: permission_mismatch, integrity mismatch: integrity_mismatch, dependency mismatch: dependency_mismatch, interface call mismatch: interface_mismatch, version incompatibility: version_incompatible, and lifecycle abnormality: lifecycle_abnormal.

[0099] This application embodiment compares at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status information in the actual operation information with the corresponding constraint information in the binding association information and the target rule object. This can identify permission drift, interface out-of-bounds call, dependency offset, integrity change, rule version mismatch, and lifecycle anomaly after the object to be accessed is accessed. This prevents the access condition from running when the object to be accessed leaves the access, and improves the accuracy and traceability of the AI ​​operating system's operation control.

[0100] In some embodiments, Figure 4 This is a schematic diagram of the fourth process of a rule-based object management method in an AI operating system provided in an embodiment of this application. For example... Figure 4 As shown, step S16: Based on the mapping relationship between the second verification result and the control strategy of the target rule object, execute the corresponding control operation, including: S161: If the second verification result indicates consistency, then maintain the scheduling permission status of the object to be accessed.

[0101] In application, when the second verification result demonstrates consistency, it indicates that the actual operating information of the object to be accessed matches the various constraint benchmarks in the binding association information, and its operating status is normal. At this point, no intervention is required in the operating status of the object to be accessed. Based on the control policy mapping relationship, the corresponding control operation for the consistent verification result is executed: maintaining the scheduling permission status of the object to be accessed.

[0102] By maintaining the scheduling permission status of the object to be connected, the continued operation of the object to be connected is allowed.

[0103] S162: If the second verification result is that the permissions are inconsistent, then the permission token of the object to be accessed is revoked, the access control list of the object to be accessed is updated, or the permission identifier of the object to be accessed is turned off, so as to revoke the permissions of the object to be accessed.

[0104] In application, if the second verification result indicates a permission mismatch, it means that the permissions actually used by the object to be connected during operation exceed the permission constraints recorded in the binding association information, resulting in permission drift. In this case, the permissions of the object to be connected need to be revoked. Based on the control policy mapping relationship, the corresponding control operations for the mismatched permissions are executed: revoking the permission token of the object to be connected, updating the access control list of the object to be connected, or disabling the permission identifier of the object to be connected.

[0105] Specifically, revoking the access token of the object to be accessed invalidates the access token of the object based on a token mechanism. Updating the access control list of the object to be accessed removes or restricts the permission entries of the object to be accessed from the permission list. Disabling the permission identifier of the object to be accessed disables the specific permission identifier of the object to be accessed.

[0106] S163: If the second verification result is an inconsistency in integrity, then the process of the object to be accessed is paused, the container instance of the object to be accessed is stopped, the object identifier of the object to be accessed is disabled, or the lifecycle state of the object to be accessed is updated to an abnormal frozen state, so as to freeze the object to be accessed.

[0107] In application, when the second verification result is incomplete, it indicates a discrepancy between the actual content summary of the object to be accessed during operation and the integrity verification value recorded in the binding association information, suggesting content tampering or corruption. In this case, the object to be accessed needs to be frozen. Based on the control policy mapping relationship, the corresponding control operation for incomplete integrity is executed: suspending the process of the object to be accessed, stopping the container instance of the object to be accessed, disabling the object identifier of the object to be accessed, or updating the lifecycle state of the object to be accessed to an abnormal frozen state.

[0108] Specifically, pausing the process of the object to be connected preserves the process context but suspends execution. Stopping the container instance of the object to be connected terminates the container's operation but preserves the container's file system snapshot. Disabling the object's identifier marks the object as unavailable, blocking requests related to the object. Updating the lifecycle state of the object to be connected to an abnormally frozen state modifies the lifecycle state to an abnormally frozen state.

[0109] S164: If the second verification result is that the interface call is inconsistent, then the interface gateway corresponding to the object to be accessed is intercepted, and a token verification failure response or an interface call whitelist rejection response is returned to the object to be accessed, so as to block the interface call of the object to be accessed.

[0110] In application, if the second verification result indicates an interface call inconsistency, it means that the interface actually called by the object to be connected during operation exceeds the interface constraint range recorded in the binding association information, resulting in an out-of-bounds interface call. In this case, it is necessary to block the interface call of the object to be connected. Based on the control policy mapping relationship, the corresponding control operation to block the interface call of the object to be connected is executed: intercepting the interface gateway corresponding to the object to be connected, returning a token verification failure response or an interface call whitelist rejection response to the object to be connected.

[0111] Specifically, intercepting the interface gateway corresponding to the access target involves matching the interface identifier of the access target in the interface gateway traffic filter and directly discarding or redirecting the access target's request. Returning a token verification failure response to the access target indicates that a token verification failure has been detected when interface permissions do not match. Rejecting access based on the interface call whitelist denial response denies access to the access target based on the interface call whitelist.

[0112] S165: If the second verification result is that the version is incompatible, then the operation of the object to be connected will be blocked and the rule version verification will be performed.

[0113] In application, if the second verification result indicates version incompatibility, it means that the version of the rule object actually associated with the object to be connected is inconsistent with the rule version information recorded in the binding association information, resulting in rule version mismatch. In this case, it is necessary to block the operation of the object to be connected and perform a rule version review. Based on the control policy mapping relationship, the corresponding processing version control operation is executed: blocking the operation of the object to be connected and performing a rule version review.

[0114] Among them, rule version review involves notifying the relevant personnel to conduct manual review, or reviewing the rule version information and object description information of the bound and associated information.

[0115] S166: If the second verification result is an abnormal lifecycle, then uninstall the object to be accessed, terminate the object to be accessed, or execute a manual review prompt.

[0116] In application, when the second verification result is a lifecycle anomaly, it indicates that the actual lifecycle state of the object to be connected is inconsistent with the lifecycle state recorded in the binding association information, resulting in a lifecycle state deviation. In this case, the abnormal lifecycle state needs to be handled. Based on the control policy mapping relationship, the corresponding control operation for the lifecycle state is executed: unloading the object to be connected, terminating the object to be connected, or prompting for manual review.

[0117] Terminating the object to be accessed involves cleaning up the instance of the object to be accessed, releasing resources, and revoking permissions.

[0118] Understandably, after passing the pre-access consistency verification, binding association information is established based on object description information and target rule objects. This improves the inheritance and constraint of the verification process on the post-access admission conditions. Consequently, during the runtime consistency verification process, it can identify permission drift, out-of-bounds interface calls, dependency offsets, integrity changes, rule version mismatches, and lifecycle anomalies. This can solve the problem of the lack of binding and interoperability between the general access control scheme and the policy audit mechanism, which leads to the operation deviating from the post-access admission conditions.

[0119] S16: Generate execution archive records, including: S167: Based on the object identifier of the currently archived object to be accessed, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type and operation time of the control operation, generate the current archive summary value.

[0120] In the application, the current object identifier of the object to be accessed, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type and operation time summary value of the control operation, and the current archive summary value are calculated.

[0121] S168: Associate the object identifier of the object to be accessed, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type, operation time, and current archive summary value of the control operation with the record identifier and record summary value of the previous archive record of the object to be accessed, and generate an execution archive record.

[0122] Among them, the preceding archive records are the archive records before the object to be accessed.

[0123] The execution archive record includes the archive identifier, the object identifier and lifecycle status of the object to be accessed, the rule object identifier and rule version information of the target rule object, the first verification result, the second verification result, the operation type, operation time, execution subject, current archive summary value, and the record identifier and record summary value of the previous archive record.

[0124] For example, the execution archive record includes the following archive identifiers: archive_id (identifier of the object to be accessed); object_id (identifier of the target rule object); rule_id (rule version information); rule_version (first verification result); first_check_result (second verification result); second_check_result (control operation type); control_action (operation time); operation_time (executor); executor (lifecycle state); lifecycle_state (identifier of the previous archive record); previous_archive_id (summary value of the previous archive record); and previous_archive_hash.

[0125] {"archive_id":"archive_20260424_001","object_id":"agent_plugin_001","rule_id":"rule_tool_plugin_001","rule_version":"v2.1","first_check_result":"pass","second_check_result":"permission_mismatch","control_actio n":"revoke_permission","operation_time":"2026-04-24T11:12:00Z","executor":"rule_object_manager","lifecycl e_state":"running","previous_archive_id":"archive_20260424_000","previous_archive_hash":"hash_prev_9a81"} The execution archive records can be stored in the master control node, central rule management node, or local rule node of the AI ​​operating system.

[0126] By associating the object identifier of the object to be connected, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type, operation time, and current archive summary value of the control operation with the record identifier and record summary value of the preceding archive record of the object to be connected, an execution archive record is generated to form a traceable archive chain for the object to be connected. Through the traceable archive chain, it is possible to promptly detect if archive records have been partially deleted, inserted, or tampered with, and to verify the consistency of rule versions and the continuity of control operations for the object to be connected during the connection, registration, operation, exception handling, and termination processes.

[0127] In some embodiments, Figure 5 This is a schematic diagram of the fifth process of a rule-based object management method in an AI operating system provided in an embodiment of this application. For example... Figure 5 As shown, before step S14: establishing binding association information based on object description information and target rule object, the following steps are also included: S21: Establish a lifecycle management handle for the object to be connected, and associate the lifecycle management handle with the binding association information.

[0128] The lifecycle management handle includes lifecycle states, allowed state transition sets, resource reference indexes, and permission revocation indexes.

[0129] For example, the lifecycle management handle includes the lifecycle state: lifecycle_state, the allowed transition set: allowed_transition_set, the resource reference index: resource_reference_index, and the permission reclaim index: permission_reclaim_index.

[0130] In the application, the lifecycle state, allowed state transition set, resource reference index, and permission revocation index of the object to be integrated are set, and a lifecycle management handle is generated. The lifecycle management handle is then associated with the binding association information to link the lifecycle state with the binding association information.

[0131] In some embodiments, the object description information is analyzed, the allowed state transition set information is determined based on the object type information, the resource reference index is determined based on the interface description information and dependency information, and the permission declaration information is determined based on the permission revocation index.

[0132] For example, lifecycle states include pending access, verified, registered, running, frozen due to an error, uninstalling, and terminated.

[0133] The corresponding allowed state transition set information includes: when the pre-access consistency check passes, the state changes from pending access to verified status; when registration is completed, the state changes from verified status to registered status; when scheduled to run, the state changes from registered status to running status; when runtime consistency check passes, the state changes from running status to abnormally frozen status; when an unload instruction is received, the state changes from running status to unloading status; when resource release and permission revocation are completed, the state changes from unloading status to terminated status; when the review fails, the state changes from abnormally frozen status to unloading status; and when the review passes, the state changes from abnormally frozen status to running status.

[0134] In some implementations, when the object to be integrated is in an unloaded state or its lifecycle state has ended, the computing resources, storage resources, or network connection resources occupied by the object to be integrated are released based on the resource reference information in the lifecycle management handle. The permission tokens, access credentials, or API call permissions corresponding to the object to be integrated are revoked based on the permission revocation index. After resource release and permission revocation, the lifecycle state is updated.

[0135] S22: Record the lifecycle status of the object to be connected through the lifecycle management handle.

[0136] This application embodiment establishes a lifecycle management handle for the object to be accessed and associates the lifecycle management handle with the binding association information. This enables the lifecycle management handle to record the status of the object to be accessed throughout its entire lifecycle, providing a unified lifecycle management object for the object to be accessed. This reduces the occurrence of state residue, permission residue, and incomplete resource release, ensuring that the actual situation of the object to be accessed is consistent with the status recorded throughout its entire lifecycle.

[0137] Exemplary simulation tests can be used to understand that during runtime consistency verification, it is possible to identify permission drift, out-of-bounds API calls, dependency offsets, integrity changes, rule version mismatches, and lifecycle anomalies.

[0138] The exemplary simulation test provides two sets of systems. One set employs a general access control and policy auditing mechanism to verify the policy when an object is to be accessed and to periodically perform policy auditing during operation. The other set uses the pre-access consistency verification, rule objects, binding association information, runtime consistency verification, control policy mapping relationships, lifecycle management handles, and execution archive records described in the embodiments of this application for object management.

[0139] The objects to be integrated include at least one of the following: a large language model module, an intelligent agent module, a tool plugin, a vector database adapter, and an inference engine component. After these objects are integrated into the AI ​​operating system, a binding association is established between them and the target rule object. This binding association information characterizes the admission baseline corresponding to the object upon successful integration. Runtime consistency verification compares the actual runtime information with the binding association information and the constraint information in the target rule object during the object's operation to identify permission drift, out-of-bounds interface calls, dependency offsets, integrity changes, rule version mismatches, and lifecycle anomalies.

[0140] The differences between the control system and the system described in this application embodiment can be evaluated using the following indicators. The control system performs admission verification only when the object to be accessed is connected, and does not perform runtime consistency verification based on binding association information during operation. The system described in this application embodiment establishes binding association information after the object to be accessed is connected, and performs runtime consistency verification on the actual operation information based on the binding association information and the target rule object during operation, executes control operations based on the verification results, and generates execution archive records. By comparing the following indicators, the ability of the method described in this application embodiment to identify and handle permission drift, out-of-bounds interface calls, dependency offsets, integrity changes, rule version mismatches, and lifecycle anomalies can be determined, thereby ensuring that the object to be accessed does not run independently without the post-access admission conditions: The metrics include: permission drift detection rate, interface out-of-bounds call blocking rate, dependency offset detection rate, integrity anomaly detection rate, rule version mismatch detection rate, lifecycle anomaly handling success rate, average anomaly response time, and execution archive integrity rate.

[0141] The following metrics are used to determine the success rate of each event: Permission drift detection rate (PERFERENCE) is the ratio of the number of detected PERFERENCE samples to the total number of PERFERENCE samples; Interface out-of-bounds call blocking rate (IEEC) is the ratio of the number of blocked IEEC samples to the total number of IEEC samples; Dependency offset detection rate (DIOC) is the ratio of the number of detected dependency offset samples to the total number of dependency offset samples; Integrity anomaly detection rate (IEEC) is the ratio of the number of detected integrity anomaly samples to the total number of integrity anomaly samples; Rule version mismatch detection rate (RRM) is the ratio of the number of detected rule version mismatch samples to the total number of rule version mismatch samples; Lifecycle anomaly handling success rate (WASCH) is the ratio of the number of correctly handled lifecycle anomaly samples to the total number of lifecycle anomaly samples; Average anomaly response time is the average time from an anomaly occurrence to the execution of a control operation; and Execution archive completeness rate (EEAC) is the ratio of the number of execution archive records with complete object identifiers for the target object, target rule object identifiers, rule version information, first verification result, second verification result, control operation type, and operation time to the total number of execution archive records.

[0142] It should be understood that the sequence number of some steps in the above embodiments does not necessarily indicate the order of execution; provided that the functional logic relationship between the verification, registration, binding association information establishment, runtime consistency verification and control operation execution of the object to be accessed is not violated, each step can be adjusted according to the actual system deployment method.

[0143] It should also be understood that the collection, storage and use of data in the above embodiments are carried out in compliance with laws and regulations and user authorization requirements, and their use or implementation does not involve harming the public interest.

[0144] Corresponding to the method described in the above embodiments, Figure 6 A schematic diagram of the structure of a rule-based object management device in an AI operating system provided in an embodiment of this application is shown. For ease of explanation, Figure 6 Only the parts relevant to the embodiments of this application are shown.

[0145] In some embodiments, Figure 6 This is a schematic diagram of the structure of a rule-based object management device in an AI operating system provided in an embodiment of this application. For example... Figure 6 As shown, the management device includes: The acquisition module 10 is used to acquire the object description information of the object to be accessed when the object is accessed. The pre-access verification module 11 is used to perform pre-access consistency verification on the object to be accessed and obtain the first verification result. The rule object matching module 12 is used to register the object to be accessed if the first verification result is that the verification is passed, and to determine the target rule object from the rule object set according to the object description information. The binding association establishment module 14 is used to establish binding association information based on object description information and target rule object, where the target rule object is the rule object applied to the object to be connected; The runtime verification module 14 is used to obtain the actual running information of the object to be connected during the running process of the object to be connected, and compare at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual running information with the binding association information and the corresponding constraint information in the target rule object to obtain the second verification result; The control operation execution module 15 is used to execute the corresponding control operation according to the control strategy mapping relationship between the second verification result and the target rule object; The execution archive module 16 is used to generate execution archive records, which are used to record information related to the object to be accessed, the target rule object, and the control operation.

[0146] In some embodiments, the specific implementation of the object to be accessed, including but not limited to its internal storage structure, index structure, scheduling mechanism, permission isolation mechanism and audit tracing mechanism, can be implemented by the subordinate implementation method followed by the object to be accessed itself, and its internal implementation does not constitute a limitation on the scope of protection of this application.

[0147] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device 2 of this embodiment includes: at least one processor 20 ( Figure 7(Only one is shown in the diagram), memory 21, and computer program 22 stored in said memory 21 and executable on said at least one processor 20, wherein said processor 20 executes said computer program 22 to implement the steps in any of the above method embodiments.

[0148] The electronic device 2 may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will understand that... Figure 7 This is merely an example of electronic device 2 and does not constitute a limitation on electronic device 2. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0149] The processor 20 can be a Central Processing Unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0150] In some embodiments, the memory 21 may be an internal storage unit of the electronic device 2, such as a hard disk or memory of the electronic device 2. In other embodiments, the memory 21 may be an external storage device of the electronic device 2, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device 2. Furthermore, the memory 21 may include both internal and external storage units of the electronic device 2. The memory 21 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 21 can also be used to temporarily store data that has been output or will be output.

[0151] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0152] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0153] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the above-described method embodiments.

[0154] This application provides a computer program product that, when run on an electronic device, enables the electronic device to implement the steps described in the various method embodiments above.

[0155] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some cases, the computer-readable medium cannot be an electrical carrier signal or a telecommunication signal.

[0156] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0157] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0158] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0159] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0160] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A rule-based object management method in an AI operating system, characterized in that, include: When an object to be accessed is accessed, its object description information is obtained. Perform a pre-access consistency check on the object to be accessed to obtain a first check result; If the first verification result is successful, the object to be accessed is registered, and the target rule object is determined from the rule object set according to the object description information; Based on the object description information and the target rule object, establish binding association information; During the operation of the object to be accessed, the actual operation information of the object to be accessed is obtained, and at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual operation information is compared with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result; Based on the mapping relationship between the second verification result and the control policy of the target rule object, the corresponding control operation is executed, and an execution archive record is generated. The execution archive record is used to record information related to the object to be accessed, the target rule object, and the control operation.

2. The method of claim 1, wherein: The object description information includes object identifier, object type information, interface description information, dependency information, permission declaration information, and integrity verification information; the rule object includes rule object identifier, rule version information, rule type information, applicable object type information, permission constraint information, dependency constraint information, interface constraint information, integrity verification constraint information, lifecycle constraint information, and control policy mapping relationship; Determining the target rule object from the rule object set based on the object description information includes: Match each piece of information in the object description information with each piece of information in each candidate rule object in the rule object set; If the candidate rule object's adaptive object type information matches the object type information of the object description information, the candidate rule object's interface constraint information covers the interface description information of the object description information, the candidate rule object's dependency constraint information covers the dependency relationship information of the object description information, the object description information's permission declaration information does not exceed the candidate rule object's permission constraint information, and the object description information's integrity verification information conforms to the candidate rule object's integrity verification constraint information, then the target rule object is obtained.

3. The method of claim 1, wherein, The step of performing a pre-access consistency check on the object to be accessed to obtain a first check result includes: Perform a uniqueness check on the object identifier of the object to be accessed; Perform a digest consistency check on the integrity verification information of the object to be accessed; Perform interface constraint verification on the interface description information of the object to be accessed; Perform dependency availability verification on the dependencies of the objects to be connected; Perform permission boundary verification on the permission declaration information of the object to be accessed; When the uniqueness check, digest consistency check, interface constraint check, dependency availability check, and permission boundary check all pass, the first check result that the representation check has passed is generated.

4. The method of claim 2, wherein, The interface constraint information of the candidate rule object covers the interface description information of the object description information if the interface constraint information includes each interface identifier in the interface description information, or if the ratio between the number of intersections between the interface constraint information and the interface identifiers and the total number of interface identifiers is greater than or equal to a preset interface coverage threshold, wherein the total number of interface identifiers is determined based on the interface description information.

5. The method of claim 2, wherein, The dependency constraint information of the candidate rule object covers the dependency relationship information of the object description information. The dependency constraint information includes the identifier of each dependent object in the dependency relationship information, or the dependency type corresponding to each dependent object identifier in the dependency information belongs to the set of allowed dependency types of the target rule object, and the set of allowed dependency types is determined based on the dependency constraint information.

6. The method of claim 2, wherein, The permission declaration information of the object description information does not exceed the permission constraint information of the candidate rule object, which means that the permission constraint information includes each permission identifier in the permission declaration information, or the permission level of the permission declaration information is less than or equal to the highest permission level of the target rule object, and the highest permission level is determined based on the permission constraint information.

7. The method of claim 1, wherein, The actual operation information includes at least one of the following: actual interface call information, actual permission usage information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status; the binding association information includes binding association identifier, lifecycle status, binding time, object identifier of the object to be accessed, integrity verification information, and rule object identifier, rule version information, permission constraint information, dependency constraint information, and interface constraint information of the target rule object. The binding association identifier, lifecycle status, and binding time are generated when the object to be accessed is registered. The step of comparing at least one of the following in the actual operation information—actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information, and actual lifecycle status information—with the binding association information and the corresponding constraint information in the target rule object includes: Based on the actual interface call information and the interface constraint information of the binding association information, determine whether the interface calls are inconsistent; Based on the actual permission usage information and the permission constraint information of the binding association information, determine whether the permissions are inconsistent; Based on the actual dependency call information and the dependency constraint information of the binding association information, determine whether the dependency relationship is inconsistent; Based on the integrity verification information of the actual integrity summary information and the binding association information, it is determined whether the integrity is inconsistent; Based on the actual rule version information and the rule version information of the binding association information, determine whether the versions are incompatible; Based on the actual lifecycle state and the lifecycle state of the bound association information, determine whether the lifecycle is abnormal.

8. The method of claim 7, wherein, The second verification result includes inconsistent interface calls, inconsistent permissions, inconsistent integrity, inconsistent dependencies, inconsistent integrity, version incompatibility, and abnormal lifecycle.

9. The method of claim 8, wherein, The step of executing the corresponding control operation based on the control policy mapping relationship between the second verification result and the target rule object includes: If the second verification result indicates consistency, then the scheduling permission status of the object to be accessed is maintained. If the second verification result is that the permissions are inconsistent, then the permission token of the object to be accessed is revoked, the access control list of the object to be accessed is updated, or the permission identifier of the object to be accessed is turned off, so as to revoke the permissions of the object to be accessed. If the second verification result is an inconsistency in integrity, then the process of the object to be accessed is paused, the container instance of the object to be accessed is stopped, the object identifier of the object to be accessed is disabled, or the lifecycle state of the object to be accessed is updated to an abnormal frozen state, so as to freeze the object to be accessed. If the second verification result is that the interface call is inconsistent, then the interface gateway corresponding to the object to be accessed is intercepted, and a token verification failure response or an interface call whitelist rejection response is returned to the object to be accessed, so as to block the interface call of the object to be accessed. If the second verification result is that the version is incompatible, then the operation of the object to be accessed will be blocked and the rule version verification will be performed; If the second verification result is an abnormal lifecycle, then the object to be accessed is uninstalled, the object to be accessed is terminated, or a manual review prompt is executed.

10. The method of claim 1, wherein, The generation of execution archive records includes: Based on the object identifier of the object to be accessed, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type and operation time of the control operation, a current archive summary value is generated. The execution archive record is generated by associating the object identifier of the object to be accessed, the object identifier of the target rule object, the rule version information, the first verification result, the second verification result, the operation type and operation time of the control operation, the current archive summary value, and the record identifier and record summary value of the previous archive record of the object to be accessed.

11. The method of claim 10, wherein, The execution archive record includes an archive identifier, the object identifier and lifecycle status of the object to be accessed, the rule object identifier and rule version information of the target rule object, the first verification result, the second verification result, the operation type, operation time, execution subject of the control operation, the current archive summary value, and the record identifier and record summary value of the preceding archive record.

12. The method of claim 1, wherein, Before establishing the binding association information based on the object description information and the target rule object, the process also includes: Establish a lifecycle management handle for the object to be accessed, and associate the lifecycle management handle with the binding association information. The lifecycle management handle includes lifecycle status, allowed state migration set, resource reference index, and permission revocation index. The lifecycle management handle records the lifecycle status of the object to be connected.

13. An apparatus for managing a rule object in an AI operating system, the apparatus comprising: a rule object management module configured to manage a rule object; and a rule object storage configured to store the rule object. include: The acquisition module is used to acquire the object description information of the object to be accessed when the object is accessed. The pre-access verification module is used to perform a pre-access consistency verification on the object to be accessed and obtain a first verification result. The rule object matching module is used to register the object to be accessed if the first verification result is that the verification is passed, and to determine the target rule object from the rule object set according to the object description information. The binding association establishment module is used to establish binding association information based on the object description information and the target rule object; The runtime verification module is used to obtain the actual running information of the object to be accessed during the running process of the object to be accessed, and compare at least one of the actual permission usage information, actual interface call information, actual dependency call information, actual integrity summary information, actual rule version information and actual life cycle status information in the actual running information with the binding association information and the corresponding constraint information in the target rule object to obtain a second verification result; The control operation execution module is used to execute corresponding control operations based on the control strategy mapping relationship between the second verification result and the target rule object; The execution archiving module is used to generate execution archive records, which are used to record information related to the object to be accessed, the target rule object, and the control operation.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 12.

15. A computer-readable storage medium, the computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 12.

Images