A semantic recognition and adjudication system and method for UB interconnection protocol and IO interconnection chip

Abstract

The application discloses a semantic recognition and arbitration system and method for a UB interconnection protocol and an IO interconnection chip. A request processing system is arranged on an IO interconnection chip, and the IO interconnection chip is arranged on an access path of a third-party access object to a UB interconnection domain. The request processing system comprises a legality judgment module configured to judge the legality of a request statement sent by the third-party access object and to reject an illegitimate request statement; a capability matching module configured to identify semantic characteristic information of the request statement, to match the semantic characteristic information with a capability profile of the third-party access object, and to output a matching result; and an arbitration module configured to obtain an execution mode for executing the request statement according to the matching result and to process the request statement of the third-party access object according to the execution mode. The application removes illegitimate statements, thereby improving the security of the UB interconnection domain. The corresponding execution mode is obtained by arbitrating the request statement, thereby improving the processing efficiency of the UB interconnection domain.

Description

Technical Field

[0001] This invention relates to the field of data governance, and more particularly to a semantic recognition and adjudication system, method, and I / O interconnect chip for the UB interconnect protocol. Background Technology

[0002] Third-party objects send request statements to the UB (Lingqu) interconnect domain by accessing the IO interconnect chip. The IO interconnect chip is responsible for transmitting the request statements to the UB interconnect domain.

[0003] As the UB open interconnect system gradually opens up access permissions to third-party objects, the IO interconnect chip no longer only undertakes data transmission functions, but also needs to analyze and process the request statements sent by third-party access objects. After the third-party object has completed physical access, the IO interconnect chip needs to determine whether the identity and permissions of the third-party access object are legitimate. The IO interconnect chip also needs to determine whether the request statements issued by the third-party access object are compatible with the processing capabilities of the third-party access object. Summary of the Invention

[0004] To address the aforementioned problems faced by I / O interconnect chips, this invention proposes a semantic recognition and adjudication system for the UB interconnect protocol, applied to the UB interconnect domain. The semantic recognition and adjudication system is deployed on an I / O interconnect chip, which is positioned on the access path of a third-party access object accessing the UB interconnect domain. The semantic recognition and adjudication system includes: a legality judgment module, used to judge the legality of request statements sent by the third-party access object and reject invalid request statements; a capability matching module, connected to the legality judgment module, used to identify the semantic feature information of the legal request statement, match the semantic feature information with the capability profile of the third-party access object, and output the matching result; and an adjudication module, connected to the capability matching module, used to adjudicate the execution method for executing the request statement based on the matching result, and process the request statement of the third-party access object according to the execution method.

[0005] Preferably, the legality judgment module includes: an access object judgment unit, used to obtain the real-time access status and permission scope of the third-party access object, and judge whether the third-party access object has been securely accessed and whether the permission scope of the third-party access object is valid based on the real-time access status; an access object processing unit, connected to the access object judgment unit, used to refuse to process the corresponding request statement when the third-party access object is in an insecure access state, the permission scope of the third-party access object is invalid, or the permission scope of the third-party access object does not match the capability scope of the UB interconnection domain; a request statement judgment unit, used to judge whether the request statement matches the service type of the UB interconnection domain and whether the format of the request statement is valid; and a request statement processing unit, connected to the request statement judgment unit, used to refuse to process the corresponding request statement when the request statement does not match the service type of the UB interconnection domain and the format of the request statement is invalid.

[0006] Preferably, the capability matching module includes: a vector construction unit, which constructs a corresponding semantic feature vector based on the semantic feature information; the semantic feature information includes semantic category information, semantic attribute information, semantic constraint information, subject permission information, and context information.

[0007] A capability profile building unit is used to build a capability profile for the third-party access object that securely accesses the IO interconnect chip; the capability profile includes allowed transaction types, allowed processing scope, and request subject status; a matching unit is connected to the vector building unit and the capability profile building unit respectively, and is used to match the semantic feature vector with the capability profile and output the matching result.

[0008] Preferably, the capability profile includes a basic capability profile and a dynamic capability profile; the capability profile construction unit includes: a first construction subunit, used to collect the allowed transaction types and allowed processing ranges of the third-party access object to construct the corresponding basic capability profile; and a second construction subunit, used to continuously update the request subject status of the third-party access object when the third-party access object sends the request statement, so as to dynamically construct the dynamic capability profile.

[0009] Preferably, the adjudication module is pre-configured with adjudication rules for classifying and adjudicating based on different matching conditions; the adjudication module includes a pass-through execution unit, a semantic change unit, a proxy execution unit, and a delayed execution unit; the adjudication module further includes: a resource information acquisition unit, used to acquire real-time resource information of the UB interconnection domain; and an adjudication unit, respectively connected to the resource information acquisition unit, the pass-through execution unit, the semantic change unit, the proxy execution unit, and the delayed execution unit, used to, based on the adjudication rules,: adjudicate the request statement that matches the capability profile as the pass-through execution, and trigger the pass-through execution unit to pass-through the request statement to the UB interconnection domain; adjudicate the request statement that does not match the capability profile as the semantic change, and trigger the semantic change unit to perform semantic change on the request statement before transmitting it to the UB interconnection domain; adjudicate the request statement that is adjudicated as the semantic change and the request statement used to operate shared resources as proxy execution, and trigger the proxy execution unit to execute the request statement on behalf of the third-party access object; and when the real-time resource information cannot satisfy the request statement, adjudicate the request statement as delayed execution, and trigger the delayed execution unit to delay the execution of the request statement.

[0010] Preferably, the semantic change includes semantic rewriting and semantic downgrading; the request statement that is determined to be subject to the semantic change includes at least one of a first access content and a second access content; the first access content does not match the allowed transaction type in the capability profile; the second access content matches the allowed transaction type, and the second access content exceeds the allowed processing range in the capability profile; the semantic change unit includes: a semantic rewriting subunit, used to rewrite the first access content to match the allowed transaction type when the request statement includes the first access content, so that the first access content matches the capability profile; and a semantic downgrading subunit, connected to the semantic rewriting subunit, used to determine after the semantic rewriting subunit has finished executing: whether the request statement contains the second access content, and downgrading the second access content to within the allowed processing range when the request statement includes the second access content, and downgrading the rewritten but out-of-the-allowed-processing first access content to within the allowed processing range, so that both the second access content and the first access content match the capability profile.

[0011] Preferably, the delayed execution unit is provided with a delayed queue, which temporarily stores the request statements that have been decided to be delayed; when the real-time resource information satisfies the request statement, the delayed execution unit executes the corresponding request statement in the delayed queue.

[0012] Preferably, the system further includes a violation statistics module, connected to the legality judgment module and the adjudication module, for performing violation statistics on the request statements based on the historical behavior of the third-party access object; the violation statistics module includes: a violation type determination unit, for determining the violation type of the request statement based on the judgment result of the legality judgment module, and for determining the violation type of the request statement based on the adjudication result of the adjudication module; a violation counting unit, connected to the violation type determination unit, for counting the violation of the request statements that generated the violation according to the violation type; and a violation management unit, connected to the violation counting unit, for updating the capability profile according to the violation type and the violation count, and adjusting the permission scope of the third-party access object according to the updated capability profile.

[0013] This invention proposes a semantic recognition and adjudication method for the UB interconnection protocol, applied to the semantic recognition and adjudication system. The semantic recognition and adjudication method includes: step S1, determining whether the request statement sent by the third-party access object is legal; if yes, proceed to step S2; if no, refuse to process the illegal request statement; step S2, matching the legally determined request statement based on the capability profile of the third-party access object, and outputting the matching result; step S3, adjudicating the execution method for executing the request statement based on the matching result; step S4, processing the request statement of the third-party access object according to the execution method.

[0014] This invention provides 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 the semantic recognition and adjudication system.

[0015] The following beneficial effects can be obtained by using the present invention: 1. Upon receiving a request statement, the validity of the request statement is first determined by the validity judgment module, and invalid request statements are rejected to prevent invalid statements from entering the UB interconnection domain and improve the security of the UB interconnection domain.

[0016] 2. By matching request statements with the capability profiles of third-party access objects and adjudicating request statements based on the matching results, it is possible to effectively execute request statements based on the processing permissions of third-party objects, thereby improving the processing efficiency of the UB interconnection domain. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the semantic recognition and adjudication system of the present invention; Figure 2 This is a schematic diagram of the legality judgment module in this invention; Figure 3 This is a schematic diagram of the capability matching module in this invention; Figure 4 This is a schematic diagram of the capability profiling unit in this invention; Figure 5 This is a schematic diagram of the adjudication module in this invention; Figure 6 This is a schematic diagram of the semantic modification unit in this invention; Figure 7 This is a schematic diagram of the violation statistics module in this invention; Figure 8 This is a flowchart illustrating the semantic recognition and adjudication method of the present invention.

[0018] In the attached image: 1. Legality Judgment Module; 11. Access Object Judgment Unit; 12. Access Object Processing Unit; 13. Request Statement Judgment Unit; 14. Request Statement Processing Unit; 2. Capability Matching Module; 21. Vector Construction Unit; 22. Capability Profile Construction Unit; 221. First Construction Subunit; 222. Second Construction Subunit; 23. Matching Unit; 3. Adjudication Module; 31. Resource Information Acquisition Unit; 32. Adjudication Unit; 33. Transparent Execution Unit; 34. Semantic Modification Unit; 341. Semantic Rewriting Subunit; 342. Semantic Degradation Subunit; 35. Proxy Execution Unit; 36. Delayed Execution Unit; 4. Violation Statistics Module; 41. Violation Type Determination Unit; 42. Violation Counting Unit; 43. Violation Governance Unit. Detailed Implementation

[0019] 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.

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

[0021] 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.

[0022] This invention provides a semantic recognition and adjudication system for the UB interconnect protocol, applied to the UB interconnect domain. The semantic recognition and adjudication system is deployed on an I / O interconnect chip, which is positioned on the access path of third-party access objects accessing the UB interconnect domain; such as Figure 1As shown, the semantic recognition and adjudication system includes: a legality judgment module 1, used to judge the legality of request statements sent by third-party access objects and refuse to process illegal request statements; a capability matching module 2, connected to the legality judgment module 1, used to identify the semantic feature information of legal request statements, match the semantic feature information with the capability profile of third-party access objects, and output the matching result; and an adjudication module 3, connected to the capability matching module 2, used to adjudicate the execution method for executing request statements based on the matching result, and process the request statements of third-party access objects according to the execution method.

[0023] Specifically, UB (Unified Bus) is a unified interconnection protocol for AI and high-performance computing. It enables IO access by connecting third-party access objects to the UB interconnection domain in a unified manner using the UB interconnection protocol.

[0024] The UB Interconnect domain is a high-performance local computing node built on the UB Interconnect protocol. Third-party access objects only need to be compatible with the UB Interconnect protocol to send request statements to the UB Interconnect domain, which then processes the request statement.

[0025] Specifically, third-party access targets are storage devices or terminal devices such as third-party chips, third-party modules, and third-party components.

[0026] The IO interconnect chip is located on the connection path between the third-party access object and the UB interconnect domain. It is used for interface conversion and data transmission between the third-party access object and the UB interconnect domain, and establishes a high-speed data channel to achieve low-latency, high-bandwidth data interaction.

[0027] The request statement sent by the third-party access object is a read / write request for the unified address space, and the content includes the operation type, the target address, and the data content to be operated.

[0028] Furthermore, the legality judgment module 1 performs a legality judgment on each request statement and removes invalid request statements to prevent invalid request statements from directly entering the UB interconnection domain and thus affecting the security of the UB interconnection domain.

[0029] Furthermore, the capability matching module 2 matches the legitimate request statement with the capability profile of the third-party access object that issued the statement, in order to form the basis for subsequent adjudication.

[0030] Furthermore, the adjudication module 3 issues corresponding adjudications to the request statements based on different matching results, and executes the request statements by adopting appropriate execution methods, so that the UB interconnection domain can efficiently execute a large number of request statements sent by different third-party objects while satisfying security requirements.

[0031] In a preferred embodiment of the present invention, such as Figure 2 As shown, the legality judgment module 1 includes: an access object judgment unit 11, used to obtain the real-time access status and permission scope of a third-party access object, and to judge whether the third-party access object has been securely accessed and whether the permission scope of the third-party access object is valid based on the real-time access status; an access object processing unit 12, connected to the access object judgment unit 11, used to refuse to process the corresponding request statement when any of the following situations occur: the third-party access object is in an insecure access state, the permission scope of the third-party access object is invalid, or the permission scope of the third-party access object does not match the capability scope of the UB interconnection domain; a request statement judgment unit 13, used to judge whether the request statement matches the service type of the UB interconnection domain and whether the format of the request statement is valid; and a request statement processing unit 14, connected to the request statement judgment unit 13, used to refuse to process the corresponding request statement when any of the following situations occur: the request statement does not match the service type of the UB interconnection domain and the format of the request statement is invalid.

[0032] Specifically, the access object judgment unit 11 is used to determine whether the third-party access object has passed the secure access process, whether the third-party access object has a legitimate identity, basic credentials and available permissions in the current UB interconnection domain, whether the third-party access object is in a controlled state, and whether the third-party access object has had its permissions invalidated, been downgraded or prohibited from entering the specific shared resource domain.

[0033] Specifically, the third-party access object completes access verification by performing a fixed security process such as pre-configuration of certificates, key exchange, and identity authentication with the UB interconnection domain. Only after completing the fixed security process can trusted access be considered complete. The access object judgment unit 11 determines whether the third-party access object has passed the secure access process by comparing the authentication record during access.

[0034] The access object judgment unit 11 checks the unique identity ID, session credentials, and permission scope registered by the third-party access object in the UB interconnection domain to confirm that the identity of the third-party access object is not forged, the credentials are valid, and it has the corresponding access permissions, and there is no unauthorized access.

[0035] When a third-party access object is not accessing for the first time, the access object judgment unit 11 determines whether the third-party access object's permission scope has been invalidated, downgraded, or prohibited from entering a specific shared resource domain by querying the capability profile.

[0036] Based on the above judgment, for any request statement that meets any of the following criteria: failed to pass the secure access process, identity forged, session expired, under control, or with restricted permissions, the access object processing unit 12 refuses to execute the request statement and removes it.

[0037] Furthermore, the request statement judgment unit 13 is used to determine whether the request statement belongs to the request type that the request object (i.e., the target UB interconnection domain) can handle, and whether the format of the request statement is complete, whether the fields are identifiable, whether the length is valid, and whether the necessary identifiers exist.

[0038] Specifically, the request statement judgment unit 13 makes a judgment by comparing the access type in the request statement with the type that the target UB interconnect domain is allowed to process, and judges the format, fields and necessary identifiers of the request statement according to the syntax rules that the IO interconnect chip can recognize.

[0039] If the access type is completely inconsistent with the type allowed to be processed by the UB interconnection domain, or if the request statement does not meet any of the syntax rules, the request statement processing unit 14 will refuse to execute the request statement and discard it.

[0040] In a preferred embodiment of the present invention, such as Figure 3 As shown, the capability matching module 2 includes: a vector construction unit 21, used to extract semantic feature information of the request statement and construct a corresponding semantic feature vector based on the semantic feature information; the semantic feature information includes semantic category information, semantic attribute information, semantic constraint information, subject permission information, and context information; a capability profile construction unit 22, used to construct a capability profile for third-party access objects that securely access the IO interconnect chip; the capability profile includes allowed transaction types, allowed processing scope, and request subject status; and a matching unit 23, which connects the vector construction unit 21 and the capability profile construction unit 22 respectively, used to match the semantic feature vector with the capability profile and output the matching result.

[0041] Specifically, the vector construction unit 21 groups the extracted semantic feature information into a set of semantic feature vectors. The semantic description features can consist of several semantic fields and parameter fields. The construction length of the semantic fields is based on the number of extracted semantic feature information and can adopt a fixed-length or variable-length structure. For the parameter fields, each semantic feature information can be assigned a value, including binary labels, enumerated values, level values, identifier values, and range values.

[0042] Specifically, semantic feature information includes semantic category information, such as at least one of shared resource, atomic, consistency, and interruption categories. It also includes semantic attribute information, such as the target UB interconnect domain and target resource. Furthermore, it includes semantic constraint information, such as whether atomic completion is required, whether degradation is allowed, whether proxying is allowed, whether latency is allowed, and latency policies. It also includes subject permission information, such as the unique identity ID, session credentials, and permission scope of the third-party access object. Finally, it includes context information, such as the current controlled status and violation statistics of the third-party access object.

[0043] Furthermore, the capability profile building unit 22 constructs a capability profile for third-party access objects to represent their ability to handle transactions. This profile includes the types of transactions allowed, such as requests for shared resources, atomic transactions, consistent transactions, and interruptible transactions. It also includes the allowed processing scope, such as whether atomic completion, degradation, proxying, and delays are allowed, unique identity ID, session credentials, and permission scope. Additionally, it includes the request subject's status, such as the current controlled status, violation statistics, and historical execution results.

[0044] The historical execution results are used for users or other third-party access objects to query.

[0045] Furthermore, the matching unit 23 matches each semantic feature information in the semantic feature vector with the corresponding content in the capability profile one by one, such as matching semantic category information with allowed transactions. Semantic feature information that matches completely is marked as allowed, semantic feature information that matches partially (e.g., the request statement requires the execution of operations A and B, but the capability profile only records that operations A can be allowed) is marked as restricted, and semantic feature information that does not match completely is marked as prohibited.

[0046] In a preferred embodiment of the present invention, the capability profile includes a basic capability profile and a dynamic capability profile; such as Figure 4 As shown, the capability profile construction unit 22 includes: a first construction subunit 221, used to collect the allowed transaction types and allowed processing ranges of third-party access objects to construct the corresponding basic capability profile; and a second construction subunit 222, used to continuously update the request subject status of the third-party access object when the third-party access object sends a request statement, so as to dynamically construct a dynamic capability profile.

[0047] Specifically, the allowed transaction types include shared resource transactions, atomic transactions, consistent transactions, and interruptible transactions.

[0048] Specifically, the shared resource class indicates whether access to the shared doorbell, shared queue, shared descriptor table, and shared resource pool is allowed; the atomic class indicates whether direct atomic operations are allowed; the consistency class indicates whether entry into the consistency domain is allowed; and the interrupt class indicates whether direct injection of interrupts or events is allowed.

[0049] The first construction subunit 221 constructs a basic capability profile of the third-party access object based on the above content.

[0050] Similarly, the request subject status includes the current controlled status of the third-party access object, violation statistics, and historical execution results.

[0051] Specifically, the controlled status includes whether it is in normal service status, restricted service status, pre-isolation status, isolation status, or recovery observation status; violation statistics include violation type and violation count; and historical execution results include the number of times execution was performed for different execution methods.

[0052] The second construction subunit 222 constructs a dynamic capability profile of the third-party access object based on the above content, and updates the dynamic capability profile based on violation statistics and execution results.

[0053] In a preferred embodiment of the present invention, the adjudication module 3 is pre-configured with adjudication rules for classifying and adjudicating based on different matching conditions; such as... Figure 5 As shown, the adjudication module 3 includes: a resource information acquisition unit 31, used to acquire real-time resource information of the UB interconnection domain; an adjudication unit 32; the adjudication module 3 also includes a pass-through execution unit 33, a semantic change unit 34, a proxy execution unit 35, and a delayed execution unit 36; the adjudication unit 32 is connected to the resource information acquisition unit 31, the pass-through execution unit 33, the semantic change unit 34, the proxy execution unit 35, and the delayed execution unit 36 ​​respectively, and is used to: adjudicate request statements that match the capability profile as pass-through execution, and trigger the pass-through execution unit 33 to pass-through the request statement to the UB interconnection domain; adjudicate request statements that do not match the capability profile as semantic change, and trigger the semantic change unit 34 to perform semantic change on the request statement before transmitting it to the UB interconnection domain; adjudicate request statements that are semantically changed and request statements used to operate shared resources as proxy execution, and trigger the proxy execution unit 35 to proxy the execution of the request statement on behalf of a third-party access object; and when real-time resource information cannot satisfy the request statement, adjudicate the request statement as delayed execution, and trigger the delayed execution unit 36 ​​to delay the execution of the request statement.

[0054] Specifically, the adjudication rules can be pre-set in the adjudication module 3, or they can be uploaded by the user from an external source.

[0055] Furthermore, the resource information acquisition unit 31 acquires the types of resources that the UB interconnection domain can provide and the real-time resource allocation status.

[0056] Furthermore, the adjudication unit 32 adjudicates the request statement based on the unique identity ID of the third-party access object and the corresponding adjudication rules.

[0057] When a request statement satisfies the permission scope of a third-party object and the UB interconnect domain's permission scope for that third-party object, the request statement is deemed to be pass-through execution. The pass-through execution unit 33 then passes the request statement through to the UB interconnect domain, which can directly execute the request statement deemed to be pass-through execution.

[0058] The request statement can include multiple access contents, each with different semantic category information and semantic attribute information. Only when all access contents match the capability profile will the adjudication unit 32 adjudicate the request statement as pass-through execution.

[0059] If the request statement does not meet the permission scope of the third-party object, does not meet the permission scope of the UB Interconnect Domain for the third-party object, or does not match the resource type provided by the UB Interconnect Domain, and if any one or more of the access content in the request statement does not match the capability profile, the adjudication unit 32 adjudicates the request statement as a semantic change. The semantic change unit 34 then performs the semantic change on it.

[0060] When a request statement undergoes semantic modification, or when it needs to access shared resources, such as a shared doorbell, shared counter, or shared status bit, to perform an atomic operation, if the semantic constraint information in the semantic feature vector of the request statement indicates that proxy execution is permitted, the proxy execution unit 35 selects the corresponding proxy item for proxy execution based on the semantic category and semantic attribute information in the semantic feature vector. The proxy item transforms the request statement into a local task, retains the semantically modified request statement, and sends it to the UB interconnect domain. The proxy item can be a local atomic proxy unit, a doorbell proxy unit, a shared resource state machine, a whitelist configuration proxy unit, or a microcontroller. Proxy execution of the request statement through the proxy item ensures the security of the UB interconnect domain.

[0061] When the real-time resource allocation cannot meet the resources required by the request statement, the decision unit 32 will decide the request statement to be executed in a delayed manner, and the delayed execution unit 36 ​​will then execute it in a delayed manner.

[0062] When the request statement includes semantic constraint information, the adjudication unit 32 should also make a decision based on the semantic constraint information. For example, if the semantic change should be made but the semantic constraint information stipulates that downgrading or proxying is not possible, the request statement should be rejected and the reason for rejection should be returned to the third-party access object.

[0063] In a preferred embodiment of the present invention, semantic change includes semantic rewriting and semantic downgrading; the request statement adjudicated as a semantic change includes at least one of a first access content and a second access content; the first access content does not match the allowed transaction type in the capability profile; the second access content matches the allowed transaction type, and the second access content exceeds the allowed processing range in the capability profile; such as Figure 6As shown, the semantic change unit includes: a semantic rewriting subunit 341, used to rewrite the first access content to match the allowed transaction type when the request statement includes the first access content, so that the first access content matches the capability profile; and a semantic downgrading subunit 342, connected to the semantic rewriting subunit 341, used to determine after the semantic rewriting subunit 341 has finished executing: whether the request statement includes the second access content, and downgrading the second access content to within the allowed processing range when the request statement includes the second access content, and downgrading the rewritten but out-of-the-allowed processing first access content to within the allowed processing range, so that both the second access content and the first access content match the capability profile.

[0064] Specifically, the semantic rewriting subunit 341 rewrites the semantic feature information marked as prohibited as the first access content. For example, it rewrites atomic operations that are not recorded in the allowed transaction types to satisfy the allowed transaction types recorded in the capability profile.

[0065] Furthermore, the semantic degradation subunit 342 performs semantic degradation on the semantic feature information marked as restricted as the second access content. For example, the semantic category information of the request statement records that consistent access is allowed, while the allowed transaction types of the capability profile only record that non-consistent access is allowed. Therefore, the semantic degradation subunit 342 downgrades the consistent access to non-consistent access.

[0066] The request statement includes at least one or more first access items, and may include one or more second access items, or a combination of the above. Semantic rewriting subunit 341 performs semantic rewriting on each first access item in the request statement, and semantic degradation subunit 342 performs semantic degradation on each second access item in the request statement. When the request statement includes both first access items and access items matching the capability profile, the adjudication unit 32 still adjudicates it as a semantic change, but the access items matching the capability profile will not undergo semantic change.

[0067] After all the first access content is rewritten and the second access content is downgraded, all the modified access content and the unmodified access content (if any) are integrated into a modified request statement, which is then executed by the proxy execution unit 35.

[0068] In a preferred embodiment of the present invention, a delay queue is provided in the delayed execution unit 36, and the delay queue temporarily stores request statements that have been determined to be delayed for execution; when the real-time resource information satisfies the request statement, the delayed execution unit 36 ​​executes the corresponding request statement in the delay queue.

[0069] Specifically, when the real-time resource allocation of the target UB interconnection domain cannot satisfy the request statement, the delayed execution unit 36 ​​temporarily stores the request statement, which includes the allowed delay information in the semantic constraint information, in the delay queue, and marks it according to the delay policy, semantic attribute information and subject permission information in the semantic constraint information.

[0070] The delay strategy includes priority, maximum waiting time, whether merging is allowed, and merging scheme.

[0071] Furthermore, when a new request statement is added to the delay queue, the delay execution unit 36 ​​determines whether it conflicts with other request statements in the delay queue based on semantic attribute information and subject permission information, and handles the conflict according to the delay strategy, such as merging, discarding low-priority request statements, or sending them to the proxy execution unit 35 for proxy execution (e.g., the semantic constraint information indicates that proxy execution is allowed).

[0072] The delayed execution unit 36 ​​continuously acquires the resource allocation status of the UB interconnect domain, and when the resource allocation status satisfies the corresponding request statement, removes the request statement from the delayed queue and sends it to the corresponding UB interconnect domain.

[0073] In a preferred embodiment of the present invention, such as Figure 7 As shown, it also includes a violation statistics module 4, which is connected to the legality judgment module 1 and the adjudication module 3 respectively. It is used to perform violation statistics on the violation behavior of request statements based on the historical behavior of third-party access objects. The violation statistics module 4 includes: a violation type determination unit 41, which is used to determine the violation type of the request statement based on the judgment result of the legality judgment module 1 and the adjudication result of the adjudication module 3; a violation counting unit 42, connected to the violation type determination unit 41, which is used to count the violation of request statements that generate violations according to the violation type; and a violation governance unit 43, connected to the violation counting unit 42, which is used to update the capability profile according to the violation type and the violation count, and adjust the permission scope of the third-party access object according to the updated capability profile.

[0074] Specifically, the types of violations include illegal third-party processing objects, illegal request statements, request statements that do not match the capability profile, and request statements that are sent repeatedly at high frequency.

[0075] Furthermore, the violation counting unit 42 counts violations for the aforementioned violation request statements according to the violation type, obtains the historical violation count corresponding to the type of the third-party access object that sent the request statement, and adds one to the historical violation count to update the violation count.

[0076] Furthermore, the violation management unit 43 returns the violation count and violation type as violation statistics to the dynamic capability profile and updates it. The dynamic profile is updated based on the comparison between the violation count and the violation threshold for the corresponding violation type. For third-party access objects whose violation count exceeds the violation threshold, their controlled status is changed, making them controlled objects, and the allowed transaction types and allowed processing scope are reduced accordingly, thereby lowering the permission scope of the violating third-party access object.

[0077] Specifically, after a third-party access object commits its first violation, the violation counting unit 42 counts the violation and narrows its permission scope once the violation count exceeds the violation threshold. At this time, the context information of the request statements issued by the third-party access object includes information that it has become a controlled subject, and records the corresponding violation type and violation count. If the third-party access object continues to send violation-counted request statements while in a controlled subject state, the violation governance unit marks it as an isolated subject. In this case, manual intervention is required to re-establish secure access and restore its legitimate identity and permission scope in the UB interconnection domain. The violation statistics module 4 continuously monitors the third-party access object after manual processing. If the third-party access object does not send any violation-counted request statements within a preset monitoring time, it is restored to a controlled subject. The violation statistics module 4 also monitors third-party access objects in the controlled subject state until they return to normal working status. Once a third-party access object sends a violation-counted request statement during the monitoring period, the monitoring time is reset and monitoring continues.

[0078] Third-party access objects in a controlled or isolated state can still pass the legitimacy judgment module 1, but the adjudication module 3 will not issue a pass-through execution adjudication result for the request statement it sends. Instead, it needs to perform semantic modification and proxy execution to ensure the security of the UB interconnection domain.

[0079] This invention proposes a semantic recognition and adjudication method for the UB interconnection protocol, which is applied to the aforementioned semantic recognition and adjudication system; such as Figure 8 As shown, the semantic recognition and adjudication method includes: Step S1, determining whether the request statement sent by the third-party access object is legal; if yes, proceed to step S2; if no, refuse to process the illegal request statement; Step S2, matching the legally determined request statement based on the capability profile of the third-party access object, and outputting the matching result; Step S3, adjudicating the execution method for executing the request statement based on the matching result; Step S4, processing the request statement of the third-party access object according to the execution method.

[0080] Specifically, the system receives request statements from third-party access objects and performs legality checks on both the third-party access object and its request statement. The legality of the third-party access object is determined by verifying whether it has completed the secure access process, possesses a valid identity within the current UB interconnection domain, and that the identity is valid. Pre-configured request statement processing rules are used to determine the completeness of the request statement's format, the recognizability of its fields, the validity of its length, and the presence of necessary identifiers. Request statements that violate at least one of these criteria are deemed illegitimate. After obtaining the judgment results, legitimate statements from legitimate third-party access objects are matched against their capabilities, while requests from illegitimate third-party access objects and illegitimate request statements are rejected.

[0081] Furthermore, semantic feature information is extracted from the request statement, including semantic category information, semantic attribute information, semantic constraint information, subject permission information, and context information. A semantic feature vector is constructed based on this semantic feature information. A basic capability profile and a dynamic capability profile are built for legitimate third-party access objects. The basic capability profile includes the allowed transaction types and allowed processing scope, while the dynamic capability profile includes the request subject status. The semantic feature vector is matched against the corresponding capability profile of the third-party access object, and the matching results are output, including complete matches and incomplete matches.

[0082] Furthermore, for request statements that match the capability profile, they are adjudicated as pass-through execution and the request statement is pass-through to the UB interconnect domain.

[0083] For request statements that do not match the capability profile, examine the first access content that does not match the capability profile at all and check if there is a second access content that partially matches the capability profile. For the first access content, perform semantic rewriting, modifying it to conform to the allowed transaction types and processing range of the third-party access object. For example, if the original access content is to perform atomic read / write, atomic swap, and atomic add-and-drop in out-of-order order, but the third-party access object's allowed processing range is only sequential, after semantic rewriting, it becomes sequential execution of atomic read / write, atomic swap, and atomic add-and-drop. For the second access content, perform semantic degradation, downgrading it to conform to the allowed transaction types and processing range of the third-party access object. For example, if the original access content is to perform consistent access, after semantic degradation, it becomes inconsistent access.

[0084] Furthermore, the semantically modified request statement is not sent directly to the UB interconnect domain. Instead, an access task consistent with the rewritten request statement is generated in the local proxy item (atomic proxy unit, doorbell proxy unit, shared resource state machine, whitelist configuration proxy unit or microcontroller, etc.), and the UB interconnect domain is accessed by proxy according to the access task.

[0085] Before sending a request statement or access task to the UB interconnect domain, it needs to be compared with the real-time resource allocation information. If the resource allocation in the UB interconnect domain cannot temporarily satisfy the request statement or access task, it is placed in a delay queue. When the resource allocation is sufficient, the request statement or access task is retrieved and sent to the UB interconnect domain. Whenever a request statement or access task enters the delay queue, it needs to be compared with other request statements or access tasks in the delay queue based on their semantic feature vectors. The delay strategy stored in the semantic feature vectors is used to determine whether to merge them and to determine the delay priority. The order of these request statements or access tasks in the delay queue is determined based on the delay priority.

[0086] Furthermore, when a third-party access object or request statement is deemed illegal, or when a request statement undergoes semantic rewriting, a violation count is performed based on the violation type (legality violation or semantic degradation or semantic change) and the historical violation count stored in the context information. This violation type and corresponding violation count are then returned to the dynamic capability profile of the corresponding third-party access object and updated. Third-party objects with violation counts exceeding the violation threshold are changed to controlled objects, and the allowed transaction types and allowed processing scope are correspondingly reduced, thereby lowering the permission scope of the violating third-party access object. The permission scope of the third-party access object is restored after subsequent manual recovery or when no violation counts are generated within the monitoring period.

[0087] This invention provides an I / O interconnect chip for the UB interconnect protocol. The I / O interconnect chip is set on the access path of a third-party access object to access the UB interconnect domain, and the I / O interconnect chip is equipped with the aforementioned semantic recognition and adjudication system.

[0088] 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 semantic recognition and adjudication system for the UB interconnection protocol, applied in the UB interconnection domain, characterized in that, The semantic recognition and adjudication system is deployed on the IO interconnect chip, which is set on the access path of third-party access objects to access the UB interconnect domain; The semantic recognition and adjudication system includes: a legality judgment module, used to judge the legality of the request statement sent by the third-party access object and refuse to process the illegal request statement; a capability matching module, connected to the legality judgment module, used to identify the semantic feature information of the legal request statement, match the semantic feature information with the capability profile of the third-party access object, and output the matching result; and an adjudication module, connected to the capability matching module, used to adjudicate the execution method for executing the request statement based on the matching result, and process the request statement of the third-party access object according to the execution method.

2. The semantic recognition and adjudication system according to claim 1, characterized in that, The legality judgment module includes: an access object judgment unit, used to obtain the real-time access status and permission scope of the third-party access object, and determine whether the third-party access object has been securely accessed and whether the permission scope of the third-party access object is valid based on the real-time access status; an access object processing unit, connected to the access object judgment unit, used to refuse to process the corresponding request statement when the third-party access object is in an insecure access state, the permission scope of the third-party access object is invalid, or the permission scope of the third-party access object does not match the capability scope of the UB interconnection domain; a request statement judgment unit, used to determine whether the request statement matches the service type of the UB interconnection domain and whether the format of the request statement is valid; and a request statement processing unit, connected to the request statement judgment unit, used to refuse to process the corresponding request statement when the request statement does not match the service type of the UB interconnection domain and the format of the request statement is invalid.

3. The semantic recognition and adjudication system according to claim 1, characterized in that, The capability matching module includes: a vector construction unit, used to construct a corresponding semantic feature vector based on the semantic feature information; the semantic feature information includes semantic category information, semantic attribute information, semantic constraint information, subject permission information, and context information; a capability profile construction unit, used to construct the capability profile for the third-party access object that securely accesses the IO interconnect chip; the capability profile includes allowed transaction types, allowed processing scope, and request subject status; and a matching unit, connected to the vector construction unit and the capability profile construction unit, used to match the semantic feature vector with the capability profile and output the matching result.

4. The semantic recognition and adjudication system according to claim 3, characterized in that, The capability profile includes a basic capability profile and a dynamic capability profile; The capability profile building unit includes: a first building subunit, used to collect the allowed transaction types and allowed processing ranges of the third-party access object to build the corresponding basic capability profile; and a second building subunit, used to continuously update the request subject status of the third-party access object when the third-party access object sends the request statement, so as to dynamically build the dynamic capability profile.

5. The semantic recognition and adjudication system according to claim 1, characterized in that, The adjudication module is pre-configured with adjudication rules for classifying and adjudicating based on different matching conditions. The adjudication module includes a pass-through execution unit, a semantic change unit, a proxy execution unit, and a delayed execution unit. The adjudication module also includes: a resource information acquisition unit for acquiring real-time resource information of the UB interconnect domain; and an adjudication unit connected to the resource information acquisition unit, pass-through execution unit, semantic change unit, proxy execution unit, and delayed execution unit, respectively, for the following purposes based on the adjudication rules: adjudicating request statements matching the capability profile as pass-through execution, and triggering the pass-through execution unit to pass-through the request statement to the UB interconnect domain; adjudicating request statements not matching the capability profile as semantic change, and triggering the semantic change unit to perform semantic change on the request statement before transmitting it to the UB interconnect domain; adjudicating request statements adjudicated as semantic change and request statements used to operate shared resources as proxy execution, and triggering the proxy execution unit to execute the request statement on behalf of the third-party access object; and when the real-time resource information cannot satisfy the request statement, adjudicating the request statement as delayed execution, and triggering the delayed execution unit to delay the execution of the request statement.

6. The semantic recognition and adjudication system according to claim 5, characterized in that, The semantic change includes semantic rewriting and semantic downgrading; the request statement that is adjudicated as the semantic change includes at least one of a first access content and a second access content; the first access content does not match the allowed transaction type in the capability profile; The second access content matches the permitted transaction type, and the second access content exceeds the permitted processing range in the capability profile; The semantic modification unit includes a semantic rewriting subunit, used to rewrite the first access content to match the allowed transaction type when the request statement includes the first access content, so that the first access content matches the capability profile; A semantic downgrade subunit, connected to the semantic rewrite subunit, is used to determine, after the semantic rewrite subunit has finished executing: whether the second access content exists in the request statement, and if the request statement includes the second access content, downgrade the second access content to within the allowed processing range, and downgrade the first access content that has been rewritten but exceeds the allowed processing range to within the allowed processing range, so that both the second access content and the first access content match the capability profile.

7. The semantic recognition and adjudication system according to claim 5, characterized in that, The delayed execution unit is equipped with a delayed queue, which temporarily stores the request statements that have been decided to be delayed; when the real-time resource information satisfies the request statement, the delayed execution unit executes the corresponding request statement in the delayed queue.

8. The semantic recognition and adjudication system according to claim 1, characterized in that, It also includes a violation statistics module, which is connected to the legality judgment module and the adjudication module respectively, and is used to perform violation statistics on the violation behavior of the request statement based on the historical behavior of the third-party access object; The violation statistics module includes: a violation type determination unit, used to determine the violation type of the request statement based on the judgment result of the legality judgment module, and to determine the violation type of the request statement based on the adjudication result of the adjudication module; a violation counting unit, connected to the violation type determination unit, used to count the violations of the request statements that generate the violation behavior according to the violation type; and a violation management unit, connected to the violation counting unit, used to update the capability profile based on the violation type and the violation count, and to adjust the permission scope of the third-party access object based on the updated capability profile.

9. A semantic recognition and adjudication method for the UB interconnection protocol, characterized in that, Applied to the semantic recognition and adjudication system as described in any one of claims 1-8; The semantic recognition and adjudication method includes: Step S1, determining whether the request statement sent by the third-party access object is legal; if yes, proceeding to Step S2; if no, rejecting the processing of the illegal request statement; Step S2, matching the legally determined request statement based on the capability profile of the third-party access object, and outputting the matching result; Step S3, adjudicating the execution method for executing the request statement according to the matching result; Step S4, processing the request statement of the third-party access object according to the execution method.

10. An I / O interconnect chip for UB interconnect protocols, characterized in that, The IO interconnect chip is located 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 semantic recognition and adjudication system as described in any one of claims 1-8.

Images