A profiling and governance system, method, and I / O interconnect chip for UB interconnect protocol

Abstract

This invention discloses a profile governance system, method, and IO interconnect chip for the UB interconnect protocol. The profile governance system is deployed on the IO interconnect chip, which is positioned on the access path from third-party access objects to the UB interconnect domain. The profile governance system includes: a construction module, used to obtain static declarations of third-party access objects to construct capability descriptors and continuously collect operational information of third-party access objects to construct operational profiles; a binding module, connected to the construction module, used to obtain different governance templates based on static declarations and bind capability descriptors, operational profiles, and all governance templates in a binding list; and a governance module, connected to the binding module, used to detect consistency deviations between capability descriptors and operational profiles and perform governance using the corresponding governance templates. This invention improves the working efficiency of third-party access objects by binding capability descriptors and operational profiles and performing governance through governance templates.

Description

Technical Field

[0001] This invention relates to the field of data governance, and in particular to a profiling governance system, method, and I / O interconnect chip for the UB interconnect protocol. Background Technology

[0002] UB (Lingqu) is a system architecture designed for third-party access objects, enabling a large number of third-party access objects to simultaneously access the UB interconnect domain and thus provide diverse access services. As the UB open interconnect system gradually shifts from a closed and controlled internal interconnect to open access for third-party chips, modules, and components, the responsibilities of the IO interconnect chips used to connect third-party access objects and the UB interconnect domain are no longer limited to chain establishment, forwarding, and basic path isolation. Instead, they need to further assume system responsibilities such as object identification and operational governance within the UB unified protocol domain.

[0003] Existing solutions typically fragment information such as the name and attributes of third-party access objects, using it locally in independent operations like driver configuration, permission settings, or resource allocation, without integrating this information. Monitoring only characteristics like connection links, transaction processing, and thermal power consumption during third-party access to the UB interconnect domain makes it difficult to take appropriate governance actions when access anomalies occur, thus affecting the normal use of the target access object and other third-party access objects. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention discloses a profile governance system for the UB Interconnect protocol, applied to a UB Interconnect domain driven by the UB Interconnect protocol. The profile governance system is deployed on an IO Interconnect chip, which is positioned on the access path from a third-party access object to the UB Interconnect domain. The profile governance system includes: a construction module, used to obtain the static declaration of the third-party access object to construct a capability descriptor, and continuously collect the operational information of the third-party access object to construct and update an operational profile; a binding module, connected to the construction module, used to obtain different governance templates based on the static declaration, bind the capability descriptor, the operational profile, and all the governance templates to form corresponding binding relationships and construct a binding list for the third-party access object; and a governance module, connected to the binding module, used to continuously perform consistency checks on the capability descriptors and operational profiles in the binding list, and when a consistency deviation occurs between the capability descriptor and the operational profile, use the corresponding governance template according to the binding relationship for governance.

[0005] Preferably, the static declaration includes static identification information and capability description preset by the third-party access object before access begins; the operational information includes real-time identification information used by the third-party access object when accessing the UB interconnect domain and real-time behavior information generated by the third-party access object when accessing the UB interconnect domain; the construction module includes: a first collection unit, used to collect the static declaration of the third-party access object, and map the static identification information and capability description in the static declaration to declaration fields of the same format respectively; a descriptor construction unit, connected to the first collection unit, used to construct the capability descriptor based on all the declaration fields; a second collection unit, used to continuously collect the operational information of the third-party access object, and construct corresponding sub-profiles based on the real-time identification information and real-time behavior information in the operational information respectively; and a profile update unit, connected to the second collection unit, used to update the operational profile based on the latest sub-profile.

[0006] Preferably, the static declaration further includes the governance template; the governance template includes at least a semantic governance template associated with the static identification information and a capability governance template associated with the capability description; the binding module includes: a template acquisition unit, used to acquire the semantic governance template and the capability governance template; a mapping unit, connected to the template acquisition unit, used to map the capability descriptor, the running profile, the semantic governance template and the capability governance template to index fields of the same type respectively; and a binding unit, connected to the mapping unit, used to establish the binding relationship between the capability descriptor, the running profile, the semantic governance template and the capability governance template according to the index fields, and construct a binding list for storing all the index fields.

[0007] Preferably, the governance module includes: a detection unit, configured to perform semantic consistency detection between the static identification information and the real-time identification information, and to perform behavioral consistency detection between the capability description and the real-time behavioral information; a consistency determination unit, connected to the detection unit, configured to determine the deviation content and degree of deviation between the capability descriptor and the operational profile based on the first result of the semantic consistency detection and the second result of the behavioral consistency detection; a governance unit, connected to the consistency determination unit, configured to, when the capability descriptor and the operational profile are not completely consistent, invoke the corresponding governance template based on the deviation content, and determine the deviation level based on the degree of deviation; and a dynamic adjustment unit, connected to the governance unit, configured to determine a governance strategy based on the deviation level and the invoked governance template, and output the governance strategy to govern the third-party access object.

[0008] Preferably, the construction module further includes a descriptor update unit connected to the descriptor construction unit, used to reconstruct the capability descriptor for updating when the static declaration of the third-party access object changes.

[0009] This invention discloses a profile governance method for the UB interconnection protocol, applied to the profile governance system. The profile governance method includes: step S1, obtaining the static declaration of the third-party access object to construct a capability descriptor, and continuously collecting the operation information of the third-party access object to construct and update the operation profile; step S2, obtaining different governance templates according to the static declaration, binding the capability descriptor, the updated operation profile, and all the governance templates to form a corresponding binding relationship and constructing a binding list of the third-party access object; step S3, performing consistency detection on the capability descriptor and the operation profile in the binding list to determine whether a consistency deviation occurs: if yes, then using the corresponding governance template according to the binding relationship for governance; if no, then the third-party access object can access normally.

[0010] Preferably, the static declaration includes static identification information and capability description preset by the third-party access object before access begins; step S1 includes: step S11a, collecting the static declaration of the third-party access object and dividing the static declaration into multiple declaration fields respectively used to represent the static identification information and the capability description; step S12a, constructing the capability descriptor based on all the declaration fields; the runtime information includes real-time identification information used by the third-party access object when accessing the UB interconnect domain and real-time behavior information generated by the third-party access object when accessing the UB interconnect domain; step S1 further includes: step S11b, continuously collecting the runtime information of the third-party access object and constructing corresponding sub-profiles based on the real-time identification information and the real-time behavior information in the runtime information; step S12b, updating the runtime profile based on the latest sub-profile.

[0011] Preferably, the governance template includes at least a semantic governance template associated with the static identification information and a capability governance template associated with the capability description; step S2 includes: step S21, obtaining the semantic governance template and the capability governance template; step S22, mapping the capability descriptor, the running profile, the semantic governance template, and the capability governance template to index fields of the same type; step S23, constructing the binding relationship based on all the index fields, and then constructing the binding list.

[0012] Preferably, step S3 includes: step S31, performing semantic consistency detection on the static identification information and the real-time identification information, and performing behavioral consistency detection on the capability description and the real-time behavioral information; step S32, determining whether a consistency deviation has occurred based on the first result of the semantic consistency detection and the second result of the behavioral consistency detection: if yes, proceed to step S33; if no, the third-party access object accesses normally; step S33, obtaining the deviation content and degree of deviation between the capability descriptor and the running profile based on the first result and the second result; step S34, calling the corresponding governance template based on the deviation content, and determining the deviation level based on the deviation degree; step S35, determining a governance strategy based on the deviation level and the called governance template, and outputting the governance strategy to govern the third-party access object.

[0013] This invention discloses an IO interconnect chip for the UB interconnect protocol. The IO interconnect chip is set on the access path of a third-party access object to access the UB interconnect domain, and the profile management system is mounted on the IO interconnect chip.

[0014] The present invention achieves the following beneficial effects: by binding the static capability descriptor of the third-party access object, the continuously updated operational profile during the access process, and the governance template obtained from the static declaration of the third-party access object, the consistency detection of the capability descriptor and the operational profile is used to determine whether the third-party access object has generated any abnormalities during the access process. Then, the governance template is used in a timely manner to govern, which effectively reduces the impact of the third-party access object on the target access object and other third-party access objects, improves the working efficiency of the third-party access object, and ensures the security of the UB interconnection domain. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the portrait management system of the present invention; Figure 2 This is a schematic diagram of the building module of the present invention; Figure 3 This is a schematic diagram of the binding module of the present invention; Figure 4 This is a schematic diagram of the governance module of the present invention; Figure 5 This is a schematic flowchart of the portrait remediation method of the present invention; Figure 6 This is a flowchart illustrating the process of constructing the capability descriptor of the present invention; Figure 7 This is a schematic diagram illustrating the process of building and running the image of the present invention; Figure 8This is a schematic diagram illustrating the process of constructing the binding list according to the present invention; Figure 9 This is a schematic diagram illustrating the process of managing third-party access objects according to the present invention.

[0016] In the attached diagram: 1. Construction module, 11. First acquisition unit, 12. Descriptor construction unit, 13. Second acquisition unit, 14. Profile update unit, 15. Descriptor update unit, 2. Binding module, 21. Template acquisition unit, 22. Mapping unit, 23. Binding unit, 3. Governance module, 31. Detection unit, 32. Consistency determination unit, 33. Governance unit, 34. Dynamic adjustment unit. Detailed Implementation

[0017] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0019] The present invention will be further described below with reference to the accompanying drawings and specific embodiments, but this is not intended to limit the scope of the invention.

[0020] This invention discloses a profile management system for the UB interconnect protocol, applied to a UB interconnect domain driven by the UB interconnect protocol. The profile management system is deployed on an I / O interconnect chip, which is positioned on the access path of third-party access objects to the UB interconnect domain; such as Figure 1 As shown, the profile governance system includes: a construction module 1, used to obtain static declarations of third-party access objects to construct capability descriptors, and continuously collect operational information of third-party access objects to construct and update operational profiles; a binding module 2, connected to the construction module 1, used to obtain different governance templates based on static declarations, bind the capability descriptors, updated operational profiles, and all governance templates to form binding relationships and construct a binding list of third-party access objects; and a governance module 3, connected to the binding module 2, used to continuously perform consistency checks on the capability descriptors and operational profiles in the binding list, and to use the corresponding governance template for governance based on the binding relationship when there is a consistency deviation between the capability descriptors and the operational profiles.

[0021] Specifically, the UB interconnection domain is used to receive transaction access, message interaction, maintenance operations and management access initiated by third-party access objects, and connects the shared resource domain and other service domains to send the above content to the shared resource domain or other service domains that are the target access objects.

[0022] Third-party access objects include, but are not limited to, AI accelerators, network accelerators, switching chips, storage controllers, board-level expansion modules, and other heterogeneous objects accessed through UB-related interfaces. These objects are used to access the IO interconnect chip and, after passing security verification, send request statements to the UB interconnect domain through the IO interconnect chip to access the shared resource domain, thereby performing resource acquisition, resource allocation, and other operations.

[0023] This application only addresses the governance of capability descriptors and operational profiles generated after third-party access objects connect to the IO interconnect chip; it does not discuss the handling of request statements or other related matters.

[0024] On the one hand, the static declaration of a third-party access object shall include at least one or more of the following fields: 1) Identity fields, such as GUID (Globally Unique Identifier), EID (Entity Identifier), Vendor ID, Device ID, etc.; 2) Functional fields, such as entity function and service type; 3) Resource management fields, such as configuration space structure, resource space structure, accessible resource segments, shared resource eligibility, resource pool ownership attributes, etc.; 4) Permission fields, such as the set of allowed transaction types, whether consistent access is allowed, whether atomic access is allowed, whether direct access to shared doorbells / shared queues is allowed, whether specific ordering semantics are allowed, etc.; 5) Governance fields, such as default permission scope, default semantic template, default fault domain template, default SLA template, default recovery template, default lifecycle template, etc.; 6) Version fields, such as Version (version number), Type (entity type of the third-party access object), validity status, etc.

[0025] Module 1 maps each item in the static declaration to the corresponding declaration field, saves all declaration fields, and builds the capability descriptor.

[0026] In one embodiment, the capability descriptor is represented as follows: Descriptor = {D id D func D mgmt D sem D gov D ver}; in, Descriptor is a capability descriptor; D id This is the declaration field for the identity class field; D func This is the declaration field for a functional class field; D mgmt This is the declaration field for resource management class fields; D sem This is the declaration field for permission-type fields; D gov This is a declaration field for governance-related fields; D ver This is the declaration field for version-type fields.

[0027] On the other hand, the operational information of third-party access objects includes one or more of the following: 1) Link information, such as port static identification information, link static identification information, bandwidth information, etc.; 2) Transaction operation information, such as latency information, timeout information, etc.; 3) Management information, such as configuration space access success rate, resource space access success rate, management message legality, etc.; 4) Resource domain information, such as shared VC (Virtual Channel), shared credit (token) pool, shared queue, shared cache, etc.; 5) Status information, such as normal state, controlled state, isolated state, etc.; 6) Protocol operation information, such as protocol violation, semantic violation, doorbell / queue update anomaly, etc.; 7) Thermal power consumption operation information, such as the temperature, power consumption, hotspot migration, throttling times, and hot recovery times of the firmware device of the third-party access object, etc.

[0028] Module 1 constructs a corresponding sub-portrait for each item in the runtime information, saves each sub-portrait, and constructs the runtime portrait.

[0029] In one embodiment, the representation of the running image is as follows: Portrait = {P link , P txn , P mgmt , P res ,P state , P proto ,P thermal}; in, Portrait is a running portrait; P link Sub-profiles of link information; P txn A sub-profile of transaction execution information; P mgmt Sub-profiles for management information; Pres Sub-profiles of resource domain information; P state A sub-portrait of status information; P proto A sub-portrait of protocol operation information; P thermal A sub-profile of thermal power consumption operation information.

[0030] Module 1 obtains continuously updated runtime information during the access process of third-party access objects, and continuously updates the runtime profile based on the updated runtime information.

[0031] Furthermore, binding module 2 constructs a binding list. In the binding list, the capability descriptors of third-party access objects are bound to the content in the operational profile to establish corresponding binding relationships. As shown in the above embodiment, identity fields are bound to link information, functional and permission fields are bound to transaction operational information, and resource management fields are bound to management information.

[0032] In addition, the binding list also includes resource slots and status slots. Resource slots are used to store resource domain information, and status slots are used to store status information.

[0033] The static declaration includes multiple governance templates, such as basic information templates, permission templates, semantic templates, fault domain templates, SLA (Service Level Agreement) templates, recovery templates, and lifecycle templates. Binding module 2 extracts the governance templates from the static declaration and saves them in the binding list.

[0034] In one embodiment, capability descriptors, operational profiles, and governance templates are mapped to a binding list in the following manner: BindEntry={Descriptor_ID,Portrait_ID,Policy_Profile_ID,FaultDomain_Profile_ID,SLA_Profile_ID,Recovery_Profile_ID,LifeCircle_Profile_ID}; in, BindEntry is a list of bindings; Descriptor_ID is the capability descriptor; Portrait_ID is the running portrait; Policy_Profile_ID is the permission template; FaultDomain_Profile_ID is the fault domain template; SLA_Profile_ID is the SLA template; Recovery_Profile_ID is the recovery template; LifeCircle_Profile_ID is the lifecycle template.

[0035] The basic information template records the device ID (Identifier), address space, and corresponding governance policies of the third-party access object. The permission template records the permission scope of the third-party access object and the corresponding governance policies.

[0036] A fault domain is used to represent the range of devices that can be affected by the third-party access object. The fault domain template records the fault domain status of the third-party access object, including normal fault domains and restricted fault domains. It is used to switch the normal fault domain status in the fault domain template to a restricted fault domain after restricting the permission scope of the third-party access object, and switch back to a normal fault domain after the permission scope is restored.

[0037] SLAs are used to constrain third-party governance objects, including performance metrics such as latency limits and queue limits, and reliability metrics such as packet loss rate and downtime. The SLA template records these metrics, along with the governance strategies for exceeding them.

[0038] The recovery template records a set of recovery rules for third-party access objects. These rules are used to determine the recovery steps to restore the object to the corresponding permission range or fault domain during processes such as restoring the shrunken permission range to the original permission range or switching fault domains.

[0039] The lifecycle template records the lifecycle of a third-party access object, including its registration and connection to the IO interconnect chip, sending a request to the IO interconnect chip to access the UB interconnect domain, acquiring and allocating resources based on the request, and exiting the IO chip connection. The lifecycle template is used to implement pre-defined governance rules based on the corresponding operational steps when consistency discrepancies occur, combined with appropriate governance templates, such as permission templates and semantic templates, for coordinated governance.

[0040] Furthermore, governance module 3 performs consistency checks between the latest operational profile and the static capability descriptor after a change in the capability descriptor or an update to the operational profile. When a consistency discrepancy occurs, the corresponding governance template is invoked for governance. For example, after an update to the operational profile, if the transaction operation information of a third-party access object indicates that the third-party access object is performing an atomic operation, but the statically declared functional class field specifies that the third-party object is prohibited from performing atomic operations, then governance module 3 determines that a consistency discrepancy has occurred. It invokes the permission template related to the functional class transaction and uses the governance strategy in the permission template for governance, such as rewriting the third-party access object to a controlled state and updating the sub-profile used to store state information during the next operational profile update.

[0041] In a preferred embodiment of the present invention, the static declaration includes static identification information and capability description preset by the third-party access object before access begins; the runtime information includes real-time identification information used by the third-party access object when accessing the UB interconnect domain and real-time behavior information generated by the third-party access object when accessing the UB interconnect domain; such as Figure 2 As shown, the construction module 1 includes: a first acquisition unit 11, used to acquire the static declarations of third-party access objects, and map the static identification information and capability descriptions in the static declarations to declaration fields of the same format; a descriptor construction unit 12, connected to the first acquisition unit 11, used to preprocess each declaration field after mapping, and construct capability descriptors from the preprocessed declaration fields; a second acquisition unit 13, used to continuously acquire the operation information of third-party access objects, and construct corresponding sub-portfolios based on the real-time identification information and real-time behavior information in the operation information; and a portrait update unit 14, connected to the second acquisition unit 13, used to update the operation portrait based on the latest sub-portfolios.

[0042] Specifically, static identification information includes identity fields and version fields, while capability descriptions include function fields, resource management fields, and permission fields. Real-time identification information includes link information, and real-time behavioral information includes transaction execution information and management information.

[0043] On one hand, after a third-party access object successfully connects to the IO interconnect chip, the first acquisition unit 11 reads the static declaration of the third-party access object through the corresponding IO interface, divides it into multiple raw fields according to category, and maps all raw fields to declaration fields, including identity fields, function fields, etc. The raw declaration fields may use different bit widths and different encoding methods. After mapping all raw fields, the descriptor construction unit 12 performs standardization processing on these declaration fields, converts all declaration fields into a unified standard encoding in a preset standardized format, and constructs a capability descriptor based on the unified standard encoding.

[0044] On the other hand, during the access process of the third-party access object, the second collection unit 13 continuously acquires the operation information of the third-party access object at a preset sampling period. The profile update unit 14 constructs a corresponding sub-profile based on the operation information of the third-party access object in each sampling period to update the operation profile.

[0045] In a preferred embodiment of the present invention, the static declaration further includes a governance template; the governance template includes at least a semantic governance template associated with the static identification information and a capability governance template associated with the capability description; such as Figure 3 As shown, the binding module 2 includes: a template acquisition unit 21, used to acquire semantic governance templates and capability governance templates; a mapping unit 22, connected to the template acquisition unit 21, used to map capability descriptors, operation profiles, semantic governance templates and capability governance templates to index fields of the same type respectively; and a binding unit 23, connected to the mapping unit, used to establish binding relationships between capability descriptors, operation profiles, semantic governance templates and capability governance templates based on the index fields, and to construct a binding list for storing all index fields.

[0046] Specifically, semantic governance templates include basic information templates, fault domain templates, etc., while capability governance templates include permission templates, semantic templates, etc.

[0047] The template acquisition unit 21 obtains the governance class fields from the static declaration of the third-party access object and constructs corresponding governance templates based on each governance class field. The governance template includes the governance object (such as permission scope or SLA) extracted from the governance class fields and the governance strategy. For example, the permission template defines that if the third-party access object violates the prescribed operation type, the permission scope of the third-party access object will be narrowed, and the status of the third-party access object will be changed to controlled mode. Request statements issued by the third-party access object in controlled mode will be executed by proxy. The IO interconnect chip manages the third-party access object according to the governance strategy. The operation information of the third-party access object changes accordingly after receiving the management, and the corresponding sub-profile will also be updated. For example, in the sub-profile of the status information of the third-party access object rewritten to controlled mode, the status will be changed from normal mode to controlled mode. At the same time, the IO interconnect chip calls the fault domain template of the third-party access object and switches it to a restricted fault domain.

[0048] Furthermore, mapping unit 22 maps the capability descriptor, operational profile, and all governance templates of the same third-party access object to index fields such as Descriptor_ID and Portrait_ID as shown in the above embodiment. Binding unit 23 constructs corresponding binding relationships based on the content corresponding to the index fields and builds a binding list. The binding list includes all index fields of the third-party access object, and subsequent consistency comparisons and governance are performed based on the index fields.

[0049] In a preferred embodiment of the present invention, such as Figure 4 As shown, the governance module 3 includes: a detection unit 31, used to perform semantic consistency detection between static identification information and real-time identification information, and to perform behavioral consistency detection between capability description and real-time behavioral information; a consistency determination unit 32, connected to the detection unit 31, used to determine the deviation content and degree of deviation between the capability descriptor and the operational profile based on the first result of semantic consistency detection and the second result of behavioral consistency detection; a governance unit 33, connected to the consistency determination unit 32, used to call the corresponding governance template based on the deviation content when the capability descriptor and the operational profile are not completely consistent, and to determine the deviation level based on the degree of deviation; and a dynamic adjustment unit 34, connected to the governance unit 33, used to determine the governance strategy based on the deviation level and the called governance template, and output the governance strategy to govern third-party access objects.

[0050] Specifically, the detection unit 31 performs semantic consistency detection on static identification information and real-time identification information. For example, it detects the identity and version fields in the static identification information with the link information in the real-time identification information, extracts the running entity in the link information and compares it with the identity field, and extracts the version number in the link information and compares it with the version field. Based on whether there is a deviation, the content of the deviation, and the degree of deviation, a first result is generated. It also performs behavioral consistency detection on capability description and real-time behavioral information. For example, it extracts the transaction content (such as atomic operations) in the transaction operation information and compares it with the permission field. Based on whether there is a deviation, the content of the deviation, and the degree of deviation, a second result is generated.

[0051] The consistency determination unit 32 acquires the first result and the second result. If the first result and the second result show a deviation, the degree of deviation is determined based on the number of deviation items, the frequency of deviation occurrence, and the degree of deviation (partial deviation or complete deviation) in the deviation content, and is then quantified. If they are completely consistent, the degree of deviation is 1.

[0052] Furthermore, the governance unit 33 calls the corresponding governance template based on the fields and sub-profiles being compared in the deviation content, and determines the deviation level based on the numerical value of the deviation degree.

[0053] In one embodiment, the deviation levels include consistency, minor deviation, major deviation, and unauthorized access. A deviation level of 1 corresponds to consistency, a deviation level in the range [0.8, 1) corresponds to minor deviation, a deviation level in the range [0.6, 0.8) corresponds to major deviation, and a deviation level below 0.6 corresponds to unauthorized access.

[0054] Furthermore, the dynamic adjustment unit 34 dynamically adjusts the governance strategy of the invoked governance template according to the degree of deviation corresponding to the deviation level. The lower the degree of deviation, the stronger the governance. For example, if a third-party access object is judged to have a minor deviation, only the governance strategy on the governance template is used for governance. However, if the third-party access object is judged to have a severe deviation, the governance strategy needs to be further strengthened. For example, if the original governance strategy was to narrow the scope of permissions to restrict access to some functional classes, the strengthened strategy would be to restrict access to all functional classes, retaining only basic access. If a third-party access object is judged to have exceeded its authority, access is prohibited, and manual review is required to lift the prohibition.

[0055] In a preferred embodiment of the present invention, similarly as Figure 2 As shown, the construction module 1 also includes a descriptor update unit 15 and a connection descriptor construction unit 12, which are used to rebuild the capability descriptor for updating when the static declaration of the third-party access object changes.

[0056] Specifically, when a third-party access object experiences events such as firmware version updates or manual rewriting of static declarations (e.g., rewriting address fields, allowed access limits, etc.), the descriptor update unit 15 freezes the original capability descriptor, re-acquires the static declaration to construct a new capability descriptor, and binds it during the next update of the running profile.

[0057] This invention discloses a profile governance method for the UB interconnection protocol, applied to a profile governance system; such as Figure 5 As shown, the profile governance method includes: Step S1, obtaining the static declaration of the third-party access object to construct the capability descriptor, and continuously collecting the operation information of the third-party access object to construct and update the operation profile; Step S2, obtaining different governance templates according to the static declaration, binding the capability descriptor, the updated operation profile and all governance templates to form corresponding binding relationships and constructing a binding list of third-party access objects; Step S3, performing consistency checks on the capability descriptors and operation profiles in the binding list to determine whether there is a consistency deviation: if yes, then using the corresponding governance template for governance according to the binding relationship; if no, then the third-party access object can access normally.

[0058] In a preferred embodiment of the present invention, the static declaration includes static identification information and capability description preset by the third-party access object before access begins; such as Figure 6As shown, step S1 includes: step S11a, collecting the static declaration of the third-party access object, and dividing the static declaration into multiple declaration fields used to represent static identification information and capability description respectively; step S12a, constructing a capability descriptor based on all declaration fields; the runtime information includes the real-time identification information used by the third-party access object when accessing the UB interconnection domain and the real-time behavior information generated by the third-party access object when accessing the UB interconnection domain; such as Figure 7 As shown, step S1 further includes: step S11b, continuously collecting the operation information of the third-party access object, and constructing corresponding sub-profiles based on the real-time identification information and real-time behavior information in the operation information; step S12b, updating the operation profile based on the latest sub-profile.

[0059] In a preferred embodiment of the present invention, the governance template includes at least a semantic governance template associated with static identification information and a capability governance template associated with capability description; such as Figure 8 As shown, step S2 includes: step S21, obtaining the semantic governance template and the capability governance template; step S22, mapping the capability descriptor, the running profile, the semantic governance template and the capability governance template to index fields of the same type respectively; step S23, constructing binding relationships based on all index fields, and then constructing a binding list.

[0060] In a preferred embodiment of the present invention, such as Figure 9 As shown, step S3 includes: Step S31, performing semantic consistency detection between static identification information and real-time identification information, and performing behavioral consistency detection between capability description and real-time behavioral information; Step S32, determining whether a consistency deviation has occurred based on the first result of semantic consistency detection and the second result of behavioral consistency detection: if yes, proceed to step S33; if no, the third-party access object can access normally; Step S33, obtaining the deviation content and degree of deviation between capability descriptor and running profile based on the first and second results; Step S34, calling the corresponding governance template based on the deviation content, and determining the deviation level based on the degree of deviation; Step S35, determining the governance strategy based on the deviation level and the called governance template, and outputting the governance strategy to govern the third-party access object.

[0061] This invention discloses an IO interconnect chip for the UB interconnect protocol. The IO interconnect chip is set on the access path of a third-party access object to access the UB interconnect domain, and the IO interconnect chip is equipped with a profile management system.

[0062] The above description is merely a preferred embodiment of the present invention and does not limit the implementation and protection scope of the present invention. Those skilled in the art should realize that any equivalent substitutions and obvious changes made based on the description and illustrations of the present invention should be included within the protection scope of the present invention.

Claims

1. A profile governance system oriented towards the UB interconnect protocol, applied to a UB interconnect domain driven by the UB interconnect protocol, characterized in that, The profile governance system is deployed on an IO interconnect chip, which is located on the access path from a third-party access object to the UB interconnect domain. The profile governance system includes: a construction module, used to obtain the static declaration of the third-party access object to construct a capability descriptor, and continuously collect the operational information of the third-party access object to construct and update an operational profile; a binding module, connected to the construction module, used to obtain different governance templates based on the static declaration, bind the capability descriptor, the operational profile, and all the governance templates to form corresponding binding relationships and construct a binding list for the third-party access object; and a governance module, connected to the binding module, used to continuously perform consistency checks on the capability descriptor and the operational profile in the binding list, and when a consistency deviation occurs between the capability descriptor and the operational profile, use the corresponding governance template according to the binding relationship for governance.

2. The portrait management system according to claim 1, characterized in that, The static declaration includes static identification information and capability description preset by the third-party access object before access begins; the runtime information includes real-time identification information of the third-party access object when accessing the UB interconnect domain and real-time behavior information generated by the third-party access object when accessing the UB interconnect domain. The construction module includes: a first acquisition unit, used to acquire the static declaration of the third-party access object, and map the static identification information and the capability description in the static declaration to declaration fields of the same format; a descriptor construction unit, connected to the first acquisition unit, used to construct the capability descriptor based on all the declaration fields; a second acquisition unit, used to continuously acquire the operation information of the third-party access object, and construct corresponding sub-profiles based on the real-time identification information and the real-time behavior information in the operation information; and a profile update unit, connected to the second acquisition unit, used to update the operation profile based on the latest sub-profile.

3. The portrait management system according to claim 2, characterized in that, The static declaration also includes the governance template; the governance template includes at least a semantic governance template associated with the static identification information and a capability governance template associated with the capability description; The binding module includes: a template acquisition unit for acquiring the semantic governance template and the capability governance template; a mapping unit connected to the template acquisition unit for mapping the capability descriptor, the running profile, the semantic governance template, and the capability governance template to index fields of the same type; and a binding unit connected to the mapping unit for establishing the binding relationship between the capability descriptor, the running profile, the semantic governance template, and the capability governance template based on the index fields, and constructing a binding list for storing all the index fields.

4. The portrait management system according to claim 2, characterized in that, The governance module includes: a detection unit, used to perform semantic consistency detection between the static identification information and the real-time identification information, and to perform behavioral consistency detection between the capability description and the real-time behavioral information; a consistency determination unit, connected to the detection unit, used to determine the deviation content and degree of deviation between the capability descriptor and the operational profile based on the first result of the semantic consistency detection and the second result of the behavioral consistency detection; a governance unit, connected to the consistency determination unit, used to call the corresponding governance template based on the deviation content when the capability descriptor and the operational profile are not completely consistent, and to determine the deviation level based on the degree of deviation; and a dynamic adjustment unit, connected to the governance unit, used to determine a governance strategy based on the deviation level and the called governance template, and output the governance strategy to govern the third-party access object.

5. The portrait management system according to claim 2, characterized in that, The construction module further includes a descriptor update unit, connected to the descriptor construction unit, used to reconstruct the capability descriptor for updating when the static declaration of the third-party access object changes.

6. A profiling and governance method for the UB interconnection protocol, characterized in that, Applied to the portrait management system as described in any one of claims 1-5; The profile management method includes: step S1, obtaining the static declaration of the third-party access object to construct a capability descriptor, and continuously collecting the operation information of the third-party access object to construct and update the operation profile; Step S2: Obtain different governance templates based on the static declaration, bind the capability descriptor, the updated running profile, and all the governance templates to form corresponding binding relationships and construct the binding list of the third-party access object; Step S3: Perform consistency checks on the capability descriptor and running profile in the binding list to determine whether a consistency deviation occurs: if yes, then use the corresponding governance template for governance based on the binding relationship; if no, then the third-party access object can access normally.

7. The portrait retouching method according to claim 6, characterized in that, The static declaration includes static identification information and capability description preset by the third-party access object before access begins; step S1 includes: step S11a, collecting the static declaration of the third-party access object and dividing the static declaration into multiple declaration fields respectively used to represent the static identification information and the capability description; step S12a, constructing the capability descriptor based on all the declaration fields; the runtime information includes real-time identification information used by the third-party access object when accessing the UB interconnect domain and real-time behavior information generated by the third-party access object when accessing the UB interconnect domain; step S1 further includes: step S11b, continuously collecting the runtime information of the third-party access object and constructing corresponding sub-profiles based on the real-time identification information and the real-time behavior information in the runtime information; step S12b, updating the runtime profile based on the latest sub-profile.

8. The portrait retouching method according to claim 7, characterized in that, The governance template includes at least a semantic governance template associated with the static identification information and a capability governance template associated with the capability description; Step S2 includes: Step S21, obtaining the semantic governance template and the capability governance template; Step S22, mapping the capability descriptor, the running profile, the semantic governance template, and the capability governance template to index fields of the same type; Step S23, constructing the binding relationship based on all the index fields, and then constructing the binding list.

9. The portrait retouching method according to claim 7, characterized in that, Step S3 includes: Step S31, performing semantic consistency detection on the static identification information and the real-time identification information, and performing behavioral consistency detection on the capability description and the real-time behavioral information; Step S32, determining whether a consistency deviation has occurred based on the first result of the semantic consistency detection and the second result of the behavioral consistency detection: if yes, proceed to step S33; if no, the third-party access object can access normally; Step S33, obtaining the deviation content and degree of deviation between the capability descriptor and the running profile based on the first result and the second result; Step S34, calling the corresponding governance template based on the deviation content, and determining the deviation level based on the deviation degree; Step S35, determining a governance strategy based on the deviation level and the called governance template, and outputting the governance strategy to govern the third-party access object.

10. An I / O interconnect chip for UB interconnect protocols, characterized in that, The IO interconnect chip is located on the access path of the third-party access object to access the UB interconnect domain, and the IO interconnect chip is equipped with the portrait management system as described in any one of claims 1-5.

Images