An instruction interaction method and device of a multitask computing platform and an electronic device

Abstract

The application provides a kind of instruction interaction method, device and electronic equipment of multi-task computing platform, method includes: the demand description of interactive task in multi-task computing platform is carried out semantic deconstruction and interactive element extraction, to generate instruction interaction metadata conformation;According to the channel configuration parameter and the interactive time limit requirement element in instruction interaction metadata conformation, create the exclusive control channel between sender and receiver in multi-task platform;According to the process identification and the authority rule in instruction interaction metadata conformation, establish the two-way binding of sender, receiver interactive process and exclusive control channel;In the permission constraint and channel association of two-way binding, sender interactive process encapsulates uplink interactive instruction as instruction feature embedded data block;In the link protection and check rule of two-way binding, receiver interactive process reads instruction feature embedded data block from exclusive control channel, to be encapsulated as feedback data block in response to uplink interactive instruction, at least reduces the interaction failure.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of multi-task cooperation, in particular to a multi-task computing platform instruction interaction method and device and electronic equipment. BACKGROUND

[0002] In the operation scene of the multi-task computing platform, the cooperation between different tasks depends on efficient and reliable instruction interaction. The accurate transmission of instructions, permission control and data integrity protection directly affect the task execution efficiency and cooperation stability of the platform. With the increase in the number of tasks carried by the platform and the complication of interaction logic, higher requirements are put forward for the directionality, timeliness and fault tolerance of instruction interaction, and an instruction interaction scheme that can adapt to the complex task cooperation requirements is urgently needed.

[0003] There is an instruction interaction scheme based on a general shared channel in the prior art, which creates a unified public channel for all interactive tasks to share. The instruction sender directly transmits instruction data to the public channel, and the receiver selects the target instruction from the channel and executes it. This scheme does not need to configure a channel for each group of tasks, simplifying the initial configuration process and having certain applicability in simple task interaction scenarios.

[0004] However, this general shared channel scheme has obvious technical defects: due to the lack of directional constraints of exclusive channels and unified management at the metadata level, the instructions of different tasks are prone to confusion in the channel, and the permission management lacks effective association basis, resulting in poor directionality of instruction transmission; at the same time, the instruction data is not deeply bound with the verification rules, and the data integrity verification lacks a unified standard, making the reliability of instruction interaction low, which is difficult to meet the needs of orderliness and accuracy of instruction interaction in complex multi-task cooperation scenarios. SUMMARY

[0005] To solve the above technical problems, the present application provides a multi-task computing platform instruction interaction method, device and electronic equipment to at least alleviate the above technical problems.

[0006] The technical scheme provided by the embodiments of the present application is as follows:

[0007] The application discloses a method for instruction interaction of a multi-task computing platform, which comprises the following steps: step 1, semantic deconstruction and interaction element extraction are performed on a requirement description of an interactive task in the multi-task computing platform to generate an instruction interaction metadata configuration; step 2, a dedicated control channel between a sender and a receiver in the multi-task platform is created according to a channel configuration parameter and an interaction time limit requirement element in the instruction interaction metadata configuration; step 3, a bidirectional binding of an interactive process of the sender and the receiver to the dedicated control channel is established according to a process identifier and a permission rule in the instruction interaction metadata configuration; step 4, under the permission constraint and the channel association of the bidirectional binding, the sender interactive process encapsulates an uplink interactive instruction into an instruction feature embedded data block based on a format requirement of a created instruction transmission verification structure body; and step 5, under the link guarantee and the verification rule of the bidirectional binding, the receiver interactive process reads the instruction feature embedded data block from the dedicated control channel to generate result data encapsulated as a feedback data block in response to the uplink interactive instruction.

[0008] Optionally, step 2 comprises: step 21, a dedicated control channel identifier for process binding verification is allocated through a channel basic information structure body, a channel type is set as an instruction interaction channel to initialize the dedicated control channel.

[0009] Optionally, step 2 further comprises: step 22, an interactive process binding structure body, an instruction transmission verification structure body and a result feedback adaptation structure body are created, the interactive process binding structure body is used for storing a process-channel association relationship, the instruction transmission verification structure body presets a verification anchor point generation rule, and the result feedback adaptation structure body defines a result data format.

[0010] Optionally, step 2 further comprises: step 23, core parameters including a process identifier, an interaction time limit and a data length are extracted from the instruction interaction metadata configuration and written into corresponding fields of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body respectively, a unidirectional association of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body with the dedicated control channel is established, and the core parameters of the instruction interaction metadata configuration are synchronized to configuration fields of the dedicated control channel to complete creation of the dedicated control channel.

[0011] Optionally, step 23 comprises: step 231, extracting the process identification, interaction time limit, and data length parameter from the instruction interaction metadata schema, and writing them into the interaction process binding structure, instruction transmission verification structure, and result feedback adaptation structure according to the field mapping rule; step 232, establishing the one-way association of the interaction process binding structure, instruction transmission verification structure, and result feedback adaptation structure with the exclusive control channel through the structure association interface, and synchronizing the association relationship to the structure association field of the instruction interaction metadata schema; step 233, verifying the parameter integrity of the interaction process binding structure, instruction transmission verification structure, and result feedback adaptation structure to ensure that the core parameters of the instruction interaction metadata schema are not missed, and completing the creation of the exclusive control channel after the parameter integrity verification is passed.

[0012] Optionally, step 3 comprises: step 31, reading the sender and receiver process identification and permission rule from the instruction interaction metadata schema, and the permission rule defines the interaction permission of the sender only writing and the receiver only reading; step 32, filling the exclusive control channel identification and corresponding process identification into the interaction process binding structure based on the sender and receiver process identification, and setting the read-write permission flag based on the permission rule; step 33, verifying the uniqueness of the association information in the interaction process binding structure by the system layer, updating the running state of the exclusive control channel to occupied after the verification is passed, and synchronizing the channel state field of the instruction interaction metadata schema to complete the bidirectional binding.

[0013] Optionally, step 4 comprises: step 41, calling the verification anchor generation rule in the instruction transmission verification structure by the sender interaction process, generating a unique verification anchor based on the uplink interaction instruction content, and the unique verification anchor is used for data integrity verification by the receiver; step 42, integrating the instruction type, execution parameter, unique verification anchor, and sender process identification according to the format requirement of the instruction transmission verification structure to generate instruction feature embedded data block; step 43, the exclusive control channel feeds back the transmission permission based on the interaction time limit parameter of the instruction interaction metadata schema, so that the sender transmits the instruction feature embedded data block to the exclusive control channel in a non-blocking mode.

[0014] Optionally, step 42 comprises: step 421, extracting the type feature and execution parameter feature of the uplink interaction instruction, and associating them with the sender process identification to obtain the instruction-process association feature set; step 422, calling the verification anchor generation rule of the instruction transmission verification structure, and performing hash calculation on the type feature, execution parameter feature, and process identification in the instruction-process association feature set to generate a unique verification anchor; step 423, encapsulating the instruction-process association feature set and the unique verification anchor in the order of "identification-parameter-feature-anchor" to form the instruction feature embedded data block.

[0015] Optionally, step 5 comprises: step 51, the receiving interactive process listens to the transmission state of the exclusive control channel, verifies the read-only right of the interactive process binding structure, reads the instruction feature embedded data block after the right verification, step 52, calls the verification rule of the instruction transmission verification structure, extracts the unique verification anchor point, instruction type feature and execution parameter feature in the instruction feature embedded data block, verifies the integrity after the fusion of the instruction type feature and the execution parameter feature through the bidirectional verification anchoring mechanism, and records the verification result to the result feedback adaptation structure; step 53, executes the uplink interactive instruction logic after the verification, generates the result data, encapsulates according to the format requirement of the result feedback adaptation structure, adds the feedback verification anchor point and encapsulates as the feedback data block, and reversely transmits to the sender through the exclusive control channel.

[0016] Optionally, step 52 comprises: step 521, extracts the unique verification anchor point, instruction type feature and execution parameter feature from the instruction feature embedded data block; step 522, according to the verification rule of the instruction transmission verification structure, recalculates the hash value after the fusion of the instruction type feature and the execution parameter feature, and compares with the extracted unique verification anchor point; step 523, if the comparison is consistent, it is determined that the data is complete, and the verification result "pass" is written to the result feedback adaptation structure; if the comparison is inconsistent, it is marked as "abnormal", and a retransmission request is triggered to the sender through the exclusive control channel, and the retransmission request carries the abnormal type identification.

[0017] Optionally, it further comprises step 6, the sender interactive process verifies the feedback data block, and updates the interactive state identification of the instruction interactive element data conformation.

[0018] Optionally, step 6 comprises: step 61, the sender interactive process listens to the feedback state of the exclusive control channel, reads the feedback data block, and calls the instruction transmission verification structure to verify the feedback verification anchor point; step 62, if the verification is passed, the result data is extracted from the feedback data block, and the interactive state identification of the instruction interactive element data conformation is updated to "complete"; if the verification fails, it is marked as "feedback abnormal", and the instruction transmission is reinitiated according to the retry rule in the instruction interactive element data conformation; step 63, the final state of the instruction interactive element data conformation is synchronized to the interactive log of the multi-task computing platform.

[0019] Optionally, step 62 comprises: step 621, if the feedback verification anchor point verification is passed, the execution state and the result parameter are extracted from the feedback data block, and the interactive state identification of the instruction interactive element data conformation is updated to "complete"; step 622, if the verification fails, it is marked as "feedback abnormal" in the instruction interactive element data conformation, and the abnormal type is recorded as anchor point mismatch and / or data loss; step 623, based on the abnormal type, the instruction encapsulation and transmission process of step 4 is re-executed according to the retry rule in the instruction interactive element data conformation, and the retry number is written to the retry count field of the instruction interactive element data conformation.

[0020] A command interaction device for a multi-task computing platform includes: an interaction element extraction module, used to perform semantic deconstruction and interaction element extraction on the requirement description of the interaction task in the multi-task computing platform to generate a command interaction metadata configuration; a dedicated channel creation module, used to create a dedicated control channel between the sender and receiver in the multi-task platform according to the channel configuration parameters and interaction timeliness requirements in the command interaction metadata configuration; and a process channel binding module, used to establish a two-way binding between the sender and receiver interaction processes and the dedicated control channel according to the process identifier and permission rules in the command interaction metadata configuration.

[0021] The instruction encapsulation and transmission module is used to encapsulate uplink interaction instructions into instruction feature-embedded data blocks based on the format requirements of the created instruction transmission verification structure, under the two-way bound permission constraints and channel association. The instruction response and feedback module is used to read instruction feature-embedded data blocks from the dedicated control channel, generate result data after responding to uplink interaction instructions, and encapsulate them into feedback data blocks, under the two-way bound link protection and verification rules. The status update module is used to verify the feedback data blocks and update the interaction status identifier of the instruction interaction metadata construct.

[0022] An electronic device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the instruction interaction method of the multitasking computing platform described above.

[0023] The technical scheme provided in the application has the following technical benefits: the technical scheme of the application integrates core elements of interactive tasks through instruction interaction metadata conformation, thereby providing a unified basis for subsequent channel creation, process binding and other steps, and effectively solving the problem of scattered interactive elements and lack of unified control in the traditional scheme. The instruction interaction metadata conformation covers key information such as channel configuration parameters, interaction timeliness requirements, process identifiers, and permission rules, so that the execution of each step has clear parameter support, improving the orderliness of instruction interaction, and greatly reducing the probability of instruction confusion compared to the case of lack of unified element control in the traditional general channel scheme. The creation of the exclusive control channel provides an independent transmission link for each group of interactive tasks, avoiding the problem of multiple task instructions competing for transmission resources in the traditional general channel. In combination with the associated configuration of the interactive process binding structure and the instruction transmission verification structure, the channel is deeply bound with core parameters, so that the channel has directional transmission and verification support capability, and compared to the characteristics of lack of exclusive adaptation in the traditional scheme, the directionality of instruction transmission is higher, and the interaction efficiency is better. The two-way binding mechanism is based on the process identifier and the permission rule in the instruction interaction metadata conformation, and clearly defines the permission boundary of the sender and the receiver, avoiding channel association conflicts through system layer uniqueness verification. This binding method makes the association of the process and the channel more stable and the permission control more accurate, solves the defects of chaotic permission management and lack of clear association basis in the traditional scheme, reduces the risk of instruction misdelivery and unauthorized access, and improves the security of instruction interaction. The encapsulation of the instruction feature embedded data block is based on the format requirements of the instruction transmission verification structure, and integrates the instruction features and the unique verification anchor, so that the data block has self-verification capability. The receiver verifies the data integrity through the two-way verification anchoring mechanism, and compared to the case of lack of unified verification standard in the traditional scheme, the reliability of data transmission is higher, and the interaction failure caused by data damage or tampering is effectively reduced. At the same time, the feedback data block is encapsulated and verified according to the same format, forming a complete interaction, further guaranteeing the integrity of instruction interaction. BRIEF DESCRIPTION OF DRAWINGS

[0024] Figure 1 A flowchart of an instruction interaction method of a multi-task computing platform is provided for an embodiment of the application.

[0025] Figure 2 A structural diagram of an instruction interaction device of a multi-task computing platform is provided for an embodiment of the application.

[0026] Figure 3 A structural diagram of an electronic device is provided for an embodiment of the application. DETAILED DESCRIPTION

[0027] As Figure 1As shown, it is a kind of instruction interaction method of multi-task computing platform in the embodiment of the application, comprising the following steps: step 1, the semantic deconstruction and interactive element extraction are carried out on the demand description of the interactive task in the multi-task computing platform, so as to generate the instruction interaction metadata conformation; step 2, according to the channel configuration parameter and the interactive time limit requirement element in the instruction interaction metadata conformation, the exclusive control channel between the sender and the receiver in the multi-task platform is created; step 3, according to the process identification and the permission rule in the instruction interaction metadata conformation, the bidirectional binding of the sender, the receiver interactive process and the exclusive control channel is established; step 4, under the permission constraint and the channel association of the bidirectional binding, the sender interactive process encapsulates the uplink interactive instruction as the instruction characteristic embedded data block based on the format requirement of the created instruction transmission verification structure body; step 5, under the link protection and the verification rule of the bidirectional binding, the receiver interactive process reads the instruction characteristic embedded data block from the exclusive control channel, so as to generate the result data encapsulated as the feedback data block after responding to the uplink interactive instruction.

[0028] Optionally, step 2 comprises: step 21, the exclusive control channel identification used for process binding verification is allocated through the channel basic information structure body, the channel type is set as the instruction interaction channel to initialize the exclusive control channel.

[0029] Optionally, step 2 further comprises: step 22, the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body are created, the interactive process binding structure body is used for storing the process-channel association relationship, the instruction transmission verification structure body presets the verification anchor point generation rule, and the result feedback adaptation structure body defines the result data format.

[0030] Optionally, step 2 further comprises: step 23, the core parameters including the process identification, the interactive time limit and the data length are extracted from the instruction interaction metadata conformation, are respectively written into the corresponding fields of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body, the one-way association of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body with the exclusive control channel is established, and the core parameters of the instruction interaction metadata conformation are synchronized to the configuration field of the exclusive control channel to complete the creation of the exclusive control channel.

[0031] In the embodiment of the application, step 2 is implemented to realize the directionalization and the checkable initialization of the exclusive control channel through the cooperative configuration of the channel basic information structure body and the multi-type function structure body. Different from the simple creation of the traditional general channel, the application realizes the directionalization and the checkable initialization of the exclusive control channel through the parameter injection and the structure body association design driven by the instruction interaction metadata conformation, so as to lay the foundation for the precise adaptation of the subsequent bidirectional binding and the instruction interaction, realize the deep binding mode of “channel-structure body-parameter”, and solve the problems of the single function and the poor adaptability of the traditional channel.

[0032] Preferably, the specific implementation process of step 21 is as follows: the system layer calls the channel resource allocation interface to query the idle channel resource pool of the multi-task computing platform, filters the adapted physical transmission link based on the channel configuration parameters (such as channel bandwidth demand, transmission priority) in the instruction interaction meta-data conformation, and allocates a dedicated control channel identifier (channel_id) for the link through the field mapping logic of the channel base information structure (channel_base_t). The channel_id is composed of the platform unique resource identifier prefix (such as 0x02 representing control type channel) and the link serial number (such as 001-999), and its physical meaning is the unique identifier for distinguishing the dedicated channels of different interaction tasks, which is from the control channel identifier pool pre-allocated by the platform resource management module; at the same time, the channel type field in channel_base_t is set to "instruction interaction channel", which clearly defines the function positioning of the channel as carrying the transmission of uplink interaction instructions and feedback data, and the initial running state field is set to "idle", indicating that the channel is currently not occupied. The initialization result forms the basic channel instance, providing a physical transmission carrier for subsequent structure association and process binding.

[0033] Preferably, in the specific technical implementation of step 22, the system layer creates three types of function-differentiated structure instances according to the full-process requirements of instruction interaction. Among them, the interaction process binding structure (lwp_bind_t) contains the associated channel identifier field (bind_channel_id), the process identifier field (lwp_id), and the read-write permission flag field (rw_flag), and their physical meanings are the unique identifier of the bound dedicated control channel, the unique identifier of the associated interaction process, and the operation permission identifier of the process to the channel, respectively. The design purpose of this structure is to store the directional association relationship between the process and the channel, avoiding multiple processes competing for the same channel; the instruction transmission verification structure (data_check_t) contains the built-in verification anchor generation rule field (anchor_rule), which is a hash calculation logic based on instruction features, specifically a composite hash algorithm combining instruction type, execution parameter and process identifier. Its physical meaning is to define the generation method of the verification anchor, ensuring the uniqueness of the verification anchor of different instruction data blocks; the result feedback adaptation structure (result_adapt_t) contains the result data format field (data_format), the feedback verification anchor field (feedback_anchor), and the execution status field (exec_status), whose physical meanings are the packaging specification of feedback data, the integrity verification identifier of feedback data, and the result status of instruction execution, respectively. The design purpose of this structure is to unify the format standard of feedback data, providing a basis for the sender to verify the feedback data. The creation of the three types of structure instances provides structured support for the permission control, integrity verification, and result adaptation of instruction interaction.

[0034] Preferably, in a scenario, when step 23 is specifically implemented, first, three core parameters of process identification (lwp_sender, lwp_receiver, representing the unique identification of the sender and receiver interactive processes, respectively, from the identification assigned by the process management module of the multi-task computing platform), interaction time limit (timeout, physically meaning the maximum allowed time consumption of instruction transmission, such as 50 ms, from the time limit requirement in the interactive task demand description), and data length (data_len, physically meaning the maximum preset length of instruction data block, such as 1024 bytes, from the storage resource configuration of the platform for instruction data) are extracted from the instruction interaction metadata schema, lwp_sender and lwp_receiver are written into the process identification field of lwp_bind_t according to the field mapping rule, and timeout and data_len are written into the corresponding configuration fields of data_check_t and result_adapt_t; then the associated structure registration function of channel_base_t is called through the structure association interface, the instance pointers of lwp_bind_t, data_check_t, and result_adapt_t are written into the associated structure list field of channel_base_t, respectively, to establish a one-way association between the three types of structures and the dedicated control channel, and the association result is synchronized to the structure association field of the instruction interaction metadata schema, forming an association mapping of "channel-structure", which physically means to explicitly define the function support structure corresponding to the dedicated control channel; finally, the system layer calls the parameter integrity verification interface, traverses the core fields of the three types of structures, checks whether there are empty fields that have not been assigned values, ensures that there is no omission of core parameters of the instruction interaction metadata schema, and after the verification passes, the configuration field of channel_base_t is updated to contain the complete configuration information of the three types of structure parameters. The complete configuration result enables the basic channel instance to have the integrated ability of permission control, verification generation, and result adaptation, and completes the creation of the dedicated control channel.

[0035] Optionally, step 23 includes: step 231, extracting process identification, interaction time limit, and data length parameters from the instruction interaction metadata schema, and writing them into the interactive process binding structure, the instruction transmission verification structure, and the result feedback adaptation structure according to the field mapping rule, respectively; step 232, establishing a one-way association between the interactive process binding structure, the instruction transmission verification structure, and the result feedback adaptation structure and the dedicated control channel through the structure association interface, and synchronizing the association relationship to the structure association field of the instruction interaction metadata schema; step 233, verifying the parameter integrity of the interactive process binding structure, the instruction transmission verification structure, and the result feedback adaptation structure, so that there is no omission of core parameters of the instruction interaction metadata schema, and the creation of the dedicated control channel is completed after the parameter integrity verification passes.

[0036] The implementation of the above step 23 realizes the parameter transmission and association mode of constructing the "instruction interaction metadata conformation-function structure- exclusive control channel", which is different from the simple assignment and loose association of parameters and structures in the traditional scheme. Through the designed multi-dimensional field mapping rule, structured association mechanism and layered integrity verification logic, the application realizes accurate allocation of parameters, stable binding of structures and channels, and no-missing verification of parameters, ensures that the configuration of the exclusive control channel has directionality, traceability and integrity, and provides accurate parameter support and structural guarantee for subsequent process binding and instruction interaction.

[0037] Preferably, the specific implementation process of step 231 is as follows. First, three types of core parameters are extracted from the instruction interaction metadata conformation, wherein the process identifier includes the sender process identifier (lwp_snd) and the receiver process identifier (lwp_rcv), and the physical meaning is the unique process identification code allocated by the multi-task computing platform for the interactive task, and the source is the process identifier pool pre-allocated by the platform process management module; the interaction time limit (t_limit) has the physical meaning of the maximum allowed time from sending to receiving feedback of the instruction, and the source is the time limit constraint in the interaction task demand description; the data length (d_len) has the physical meaning of the maximum preset storage length of the instruction data block, and the source is the instruction data storage threshold (such as 1024 bytes) configured by the platform based on storage resources. Then, the multi-dimensional field mapping table designed by the application is called, which pre-defines a one-to-one correspondence between the core parameters and the fields of the three types of structures, wherein the process identifier (lwp_snd, lwp_rcv) is written into the "process identifier list" field of the interactive process binding structure (lwp_bind_t), the interaction time limit (t_limit) is written into the "time limit constraint" field of the instruction transmission verification structure (data_check_t) and the "feedback timeout threshold" field of the result feedback adaptation structure (result_adapt_t), and the data length (d_len) is written into the "maximum length of data block" field of the three types of structures. Through the mapping table, accurate allocation of parameters is realized, and the interactive process binding structure, the instruction transmission verification structure, and the result feedback adaptation structure after parameter filling are generated.

[0038] Preferably, in the specific technical implementation of step 232, first, the struct_assoc_register interface designed in the present application is called, which has built-in channel-structure association verification logic, and the input parameters are the channel identifier (channel_id) of the exclusive control channel, the instance pointers of the three types of structures (lwp_bind_ptr, data_check_ptr, result_adapt_ptr), and the association type identifier (assoc_type="one-way"). When the interface is executed, first, the channel basic information structure (channel_base_t) of the exclusive control channel is queried through channel_id, and in the "association structure index table" field of channel_base_t, the instance pointers of the three types of structures and the corresponding structure type identifiers (such as "lwp_bind", "data_check", and "result_adapt") are written, respectively, to establish a one-way association between the three types of structures and the exclusive control channel, and to ensure that the channel can call the functions of the structures in a directional manner. Subsequently, the core information of the association relationship (including channel_id, structure type identifier, and instance pointer hash value) is written into the "structure association field" of the instruction interaction metadata conformation, and a traceable record of the association relationship is formed, and the physical meaning of the record is the association mapping certificate of the instruction interaction metadata conformation with the channel and the structure, which provides a traceable basis for parameter query and state synchronization in the subsequent steps.

[0039] Preferably, in a scenario, step 233 is specifically implemented, first, the layered parameter integrity verification mechanism designed in this application is executed, which is divided into two levels of field level verification and association level verification. The field level verification is for the interactive process binding structure, the instruction transmission verification structure, and the result feedback adaptation structure, respectively traversing the core fields (such as the process identifier and channel identifier fields of lwp_bind_t, the time constraint and verification rule fields of data_check_t), checking whether the fields have been assigned and meet the parameter format requirements (such as the process identifier being an 8-bit hexadecimal number and the interactive time being a non-negative integer); the association level verification compares the core parameter list of the instruction interaction metadata configuration with the parameters written in the three types of structures, checks whether there is a core parameter missing writing or writing value inconsistency (such as the interactive time in the metadata configuration being 50ms, and the time constraint in data_check_t being 40ms, which is determined as inconsistent). After the layered verification, the parameter integrity verification report is generated, the physical meaning of the report is the validity voucher of the parameter configuration of the three types of structures, which is written into the "configuration verification field" of the channel base information structure (channel_base_t) of the dedicated control channel, the creation of the dedicated control channel is completed, and it is ensured that the configuration parameters of the dedicated control channel are comprehensive, consistent and effective, providing a reliable basic configuration for subsequent process binding and instruction transmission.

[0040] Optionally, step 3 includes: step 31, reading the sender and receiver process identifiers and permission rules from the instruction interaction metadata configuration, the permission rules defining the interaction permissions of the sender only writing and the receiver only reading; step 32, filling the interactive process binding structure with the dedicated control channel identifier and the corresponding process identifier based on the sender and receiver process identifiers, and setting the read-write permission markers based on the permission rules; step 33, the system layer checks the uniqueness of the associated information in the interactive process binding structure, and updates the running state of the dedicated control channel to occupied after the verification is passed, and synchronizes to the channel state field of the instruction interaction metadata configuration, to complete the bidirectional binding.

[0041] In the embodiment of the application, the bidirectional binding mode of "metadata configuration driven- permission differentiation configuration- uniqueness verification locking" is constructed through step 3, which is different from the simple association of processes and channels in the traditional scheme. Through the precise parameter support provided by the instruction interaction metadata configuration, the application realizes the differentiated binding of the sender and the receiver, and then performs a unique verification through the system layer to ensure the directionality and exclusivity of the binding relationship, so that the dedicated control channel is only open to the target interactive process with corresponding permissions, laying a solid foundation for the directional transmission and permission control of subsequent instructions, and realizing the threefold protection of parameter traceability, permission refinement and association uniqueness in the binding process.

[0042] Preferably, the specific implementation process of step 31 is as follows: the parameter reading interface of the instruction interaction metadata configuration is called, the sender process identifier (lwp_snd_id) and the receiver process identifier (lwp_rcv_id) are extracted from the "process configuration field" of the instruction interaction metadata configuration, and the physical meaning of the two is the unique identification code allocated by the multi-task computing platform to the instruction sender and receiver interaction process, which comes from the identification resource pool (such as the code format is 8-bit hexadecimal number, for example: lwp_snd_id=0x1A3B5C7D, lwp_rcv_id=0x2D4F6H8J) pre-allocated by the platform process management module based on task scheduling requirements. At the same time, the permission rule is read from the "permission rule field" of the instruction interaction metadata configuration, which is a two-way permission constraint pre-set based on the interaction task requirement, which clearly stipulates that the sender process only has "write-only permission" (i.e. only can write instruction data to the exclusive control channel, cannot read any data in the channel), and the receiver process only has "read-only permission" (i.e. only can read instruction data and feedback data from the exclusive control channel, cannot write any data to the channel), and the source of the permission rule is the data flow constraint in the interaction task requirement description, which avoids illegal reading or tampering of instruction data and ensures the security of instruction interaction.

[0043] Preferably, in the specific technical implementation of step 32, based on the sender process identifier (lwp_snd_id) and the receiver process identifier (lwp_rcv_id) extracted in step 31, the field assignment interface of the interaction process binding structure (lwp_bind_t) is called, and the exclusive control channel identifier (channel_id) is written into the "associated channel identifier" field corresponding to lwp_snd_id and lwp_rcv_id in lwp_bind_t, and lwp_snd_id and lwp_rcv_id are filled into the corresponding "process identifier" field, forming a one-to-one correspondence of "process identifier-channel identifier". Based on the permission rule read in step 31, set the read-write permission flag (rw_flag) in lwp_bind_t, which uses binary encoding form, where "01" represents write-only permission, corresponding to writing into the rw_flag field corresponding to the sender process; "10" represents read-only permission, corresponding to writing into the rw_flag field corresponding to the receiver process, and the physical meaning of the binary code is permission identification, which will be used for permission verification in subsequent instruction transmission, to ensure that the sender and receiver can only perform operations within the permission range, avoiding unauthorized behavior.

[0044] Preferably, in a scenario, step 33 is specifically implemented, the system layer calls the combined uniqueness verification algorithm designed in this application, the core logic of the algorithm is to extract the combination information of "associated channel identifier (channel_id) + process identifier (lwp_snd_id / lwp_rcv_id)" in the interactive process binding structure (lwp_bind_t), perform hash calculation on the combination information to obtain a combined hash value, query the channel-process binding hash table of the multi-task computing platform (the hash table stores all established "channel_id+lwp_id" combination hash values), if the same combination hash value is not queried, it is determined that the associated information is unique, avoiding channel conflicts caused by binding multiple channels to the same process or binding repeated processes to the same channel; if the same combination hash value is queried, a binding conflict alarm is triggered and the current binding process is terminated. After verification, the state update interface of the exclusive control channel is called, the "running state" field in the channel base information structure (channel_base_t) is updated to "occupied", and the physical meaning of this state is that the exclusive control channel has been bound by the target interactive process and can receive instruction transmission requests. At the same time, the "occupied" state is written into the "channel state field" of the instruction interaction meta-data conformation, forming a traceability record of the binding state, which will be used for channel state query in subsequent instruction transmission, ensuring that only channels in the "occupied" state and with valid binding relationship can perform instruction interaction, completing the bidirectional binding of the sending and receiving interactive processes and the exclusive control channel.

[0045] Optionally, step 4 includes: step 41, the sending interactive process calls the verification anchor generation rule in the instruction transmission verification structure, generates a unique verification anchor based on the uplink interactive instruction content, and the unique verification anchor is used for data integrity verification of the receiving side; step 42, according to the format requirement of the instruction transmission verification structure, integrate instruction type, execution parameter, unique verification anchor, and sending process identifier to generate instruction feature embedded data block; step 43, the exclusive control channel feeds back transmission permission based on the interaction time limit parameter of the instruction interaction meta-data conformation, so that the sending side transmits the instruction feature embedded data block to the exclusive control channel in a non-blocking mode.

[0046] In the embodiments of the present application, the implementation of steps 41 and 43 constructs the collaborative mode of "check anchor point uniqueness generation-time linkage non-blocking transmission", which is different from the single generation of check code and the fixation of transmission mode in the traditional scheme. The present application generates a unique check anchor point through the designed multi-field weighted hash rule, ensures the traceability and integrity of the instruction data block, and binds the interaction time depth of the transmission permission and the instruction interaction metadata conformation. The non-blocking transmission mode is adopted to adapt to the concurrent demand of the multi-task computing platform, which avoids the interaction failure caused by transmission timeout and does not affect the normal execution of other tasks, and realizes the fine generation logic of the check anchor point and the time adaptive characteristics of the transmission mode.

[0047] Preferably, the specific implementation process of step 41 is as follows. The sender interaction process calls the preset multi-field weighted hash rule in the instruction transmission check structure body (data_check_t). The rule is designed to adapt to the instruction interaction scene, and the core logic is to assign differential weights according to the influence degree of instruction fields on interaction integrity. First, the core content of the uplink interaction instruction is decomposed, and three types of core fields are extracted, i.e. instruction type (cmd_type, the physical meaning is the functional classification identifier of the instruction, such as starting task, adjusting parameter, etc., the source is the header field of the uplink interaction instruction), execution parameter (exec_param, the physical meaning is the specific configuration data required for instruction execution, the source is the parameter segment of the uplink interaction instruction), and sender process identifier (lwp_snd_id, the physical meaning is the unique identification code of the sender interaction process, the source is the instruction interaction metadata conformation). The weights are assigned according to the rule: the weight proportion of instruction type is 40% (because the instruction type directly determines the execution logic and has the highest influence on interaction effectiveness), the weight proportion of execution parameter is 35% (the accuracy of parameter affects the execution result), and the weight proportion of sender process identifier is 25% (to ensure the binding association of anchor point and sender). The three types of fields are weighted and hashed to generate a 64-bit binary format unique check anchor point (anchor_code, example: 1011001101001011...). The physical meaning of the unique check anchor point is the exclusive integrity identifier of the current instruction data block, which is guaranteed by "field weight differentiation + hash algorithm irreversibility" and will serve as the core basis for verifying whether the data of the receiver has been tampered with or damaged.

[0048] Preferably, in a scenario, when step 43 is implemented, the sender interaction process initiates a transmission request to the exclusive control channel based on the instruction feature-embedded data block generated in step 42, which contains the length information (d_len) of the instruction feature-embedded data block, the unique verification anchor point (anchor_code), and the sender process identifier (lwp_snd_id). After the exclusive control channel receives the request, it reads the interaction time limit parameter (t_limit, the physical meaning is the maximum allowed time for instruction transmission, which comes from the interaction task requirement description, for example: t_limit=50ms) in the instruction interaction metadata conformation, calculates the time difference between the initiation time of the current transmission request and the start time of the interaction task, and if the time difference does not exceed t_limit, it is determined that the transmission is within the valid time limit; at the same time, through the bidirectional association of the channel base information structure (channel_base_t) and the data transmission control structure (data_transfer_t), the real-time occupancy state of the exclusive buffer is queried, and if the buffer occupancy rate is lower than the preset threshold (such as 70%), the transmission permission is fed back. After the sender interaction process receives the permission, it performs the transmission operation in a non-blocking mode, i.e. the transmission process does not block other task logic of the sender interaction process, and the transmission progress is fed back in real time through a polling mechanism, and the instruction feature-embedded data block is written into the exclusive buffer in segments; during the transmission process, the transmission progress marker of the data transmission control structure is updated to "transmitting" and the state is synchronized to the "transmission state field" of the instruction interaction metadata conformation, ensuring that the transmission state is traceable; if a timeout (time difference exceeds t_limit) or a sudden increase in buffer occupancy is detected during the transmission process, the transmission is immediately paused and marked as "transmission interruption", and the transmission is resumed after the channel feedbacks the re-permission, which ensures the transmission timeliness and avoids occupying too many platform resources.

[0049] Optionally, step 42 includes: step 421, extracting the type feature, execution parameter feature, and process identifier of the uplink interaction instruction to obtain the instruction-process association feature set; step 422, calling the verification anchor point generation rule of the instruction transmission verification structure to perform hash calculation on the type feature, execution parameter feature, and process identifier in the instruction-process association feature set to generate a unique verification anchor point; step 423, encapsulating the instruction-process association feature set and the unique verification anchor point in the order of "identifier-parameter-feature-anchor" to form the instruction feature-embedded data block.

[0050] In the present application, step 42 is to construct the instruction data block generation mode of "feature fine extraction-correlation uniqueness fusion-structured sequential packaging", which is different from the simple splicing and single verification of instruction data in the traditional scheme. Through the hierarchical extraction of instruction features, the deep correlation of process identification, and the structured packaging of fixed order, the instruction feature embedded data block has traceability, checkability, and analyzability, realizes the pertinence of feature extraction, the exclusivity of correlation fusion, and the normativity of packaging structure, and provides a clear data basis for the subsequent receiving party's permission verification and integrity check.

[0051] Preferably, the specific implementation process of step 421 is as follows: first, the uplink interactive instruction is field parsed to extract two types of core features: instruction type feature (cmd_type_feat) and execution parameter feature (exec_param_feat). The physical meaning of the instruction type feature is the quantitative identification of the instruction function classification, which is derived from the function code in the header of the uplink interactive instruction (such as function code 0x01 for starting a task and 0x02 for adjusting parameters), and the function code is converted into a fixed-length vector (such as a 16-dimensional vector) through the feature quantization mapping table designed by the present application; the physical meaning of the execution parameter feature is the structured representation of the execution parameter, which is derived from the parameter segment of the uplink interactive instruction, and after standardized processing according to the data type (integer, floating point) of the parameter, a parameter feature matrix (param_feat_mat) is generated, the rows of the matrix represent parameter items (such as temperature threshold, running time), and the columns represent the quantized values of the parameters (such as temperature threshold 25℃ quantized as 0x19). Then, the sender process identification (lwp_snd_id, the physical meaning of which is the unique identification code of the sender process, which is derived from the instruction interaction meta-data conformation) is called to establish the association of the three types of data through the feature association matrix (feat_assoc_mat) designed by the present application, the rows of the matrix correspond to the instruction type feature and the execution parameter feature, the columns correspond to the sender process identification, and the intersection is the association weight (such as the association weight of the instruction type feature and the process identification 0.6, the association weight of the execution parameter feature and the process identification 0.4). Based on the weight, the feature fusion is performed to obtain the instruction-process association feature set (lwp_cmd_assoc_feat), and the physical meaning of the feature set is the instruction core feature set bound to the sender identity.

[0052] Preferably, in the specific implementation of step 422, the call instruction transmits the preset multi-dimensional weighted hash rule in the data_check_t structure, which is designed for the instruction interaction scene, and the core purpose is to combine the instruction characteristics and the sender identity to ensure the exclusivity of the unique verification anchor. Taking the instruction-process association feature set (lwp_cmd_assoc_feat) obtained in step 421 as the processing object, first, the instruction type feature vector, the execution parameter feature matrix, and the sender process identification in the feature set are serialized respectively, and converted into a continuous binary data stream; then the hash weight is allocated according to the preset weight allocation rule, wherein the instruction type feature accounts for 35%, the execution parameter feature accounts for 40%, and the sender process identification accounts for 25%, and the weight allocation is based on the influence degree of various data on the uniqueness of the instruction; the serialized binary data stream is weighted and spliced according to the weight to obtain the fused data stream (fused_data_stream); finally, the designed hash calculation logic is executed on the fused data stream to generate a binary unique verification anchor (anchor_code) with a fixed length (such as 64 bits), and the physical meaning of the unique verification anchor is the exclusive integrity verification identification of the current instruction-process association combination, which is guaranteed by the "exclusivity of feature association + irreversibility of hash algorithm".

[0053] Preferably, in a scene, in the specific implementation of step 423, the instruction-process association feature set (lwp_cmd_assoc_feat) obtained in step 421 and the unique verification anchor (anchor_code) obtained in step 422 are taken as the processing object, and structured packaging is performed in the fixed order of "identification-parameter-feature-anchor". First, the sender process identification (lwp_snd_id) is written in the data block header as the identity trace field of the data block; then the structured data of the execution parameter feature matrix (such as the quantized value sequence arranged in the order of parameter items) is written as the core configuration data of instruction execution; then the instruction type feature vector and the feature association weight information in the instruction-process association feature set are written as the basis for instruction function identification; finally, the unique verification anchor (anchor_code) is written in the tail of the data block as the core field of data integrity verification. In the packaging process, in order to ensure the consistency of the receiver analysis, field separation identifiers (such as 0xAA) are added between the fields, and a length identifier (data_len) is added at the start of the data block to record the total number of data block bytes (such as 512 bytes), and finally an instruction feature fused data block (cmd_feat_fused_block) is formed, which has the physical meaning of a structured instruction data carrier with identity trace, function identification, and integrity verification three attributes, and can directly adapt to the transmission format requirements of the exclusive control channel.

[0054] Optionally, step 5 comprises: step 51, the receiving party interactive process listens to the transmission state of the exclusive control channel, verifies the read-only authority of itself through the interactive process binding structure, reads the instruction feature embedded data block after the authority verification is passed; step 52, the verification rule of the instruction transmission verification structure is called, the unique verification anchor point in the instruction feature embedded data block is extracted together with the instruction type feature and the execution parameter feature, the integrity is verified through the bidirectional verification anchoring mechanism after the instruction type feature and the execution parameter feature are fused, and the verification result is recorded to the result feedback adaptation structure; step 53, after the verification is passed, the uplink interactive instruction logic is executed, the result data is generated, is packaged according to the format requirement of the result feedback adaptation structure, the feedback verification anchor point is added and is packaged into a feedback data block, and is reversely transmitted to the sender through the exclusive control channel.

[0055] In the application, steps 51 and 53 construct the receiving party interactive mode of "transmission state accurate listening-authorization double verification-instruction directional execution-feedback structured packaging", which is different from the mode of passive reading, single authorization verification and simple feedback packaging in the traditional scheme. The application realizes the legality of the receiving party operation, the pertinence of the instruction execution and the checkability of the feedback data through the cooperative verification of the channel state and the process authority and the associated generation of the instruction execution and the feedback anchor point, realizes the double nature of the authorization verification, the structured feedback packaging and the association of the anchor point generation, and provides end support for the integrity and reliability of the instruction interaction.

[0056] Preferably, the specific implementation process of step 51 is as follows: the receiver interactive process starts the transmission state polling mechanism, calls the channel state query interface at a preset period (such as 10 ms), reads the "transmission progress marker" field in the channel base information structure (channel_base_t) of the exclusive control channel, the physical meaning of the field is the transmission state identification (such as "not transmitted", "transmitting", "transmission completed") of the instruction feature embedded data block, and the source is the state data updated synchronously in the transmission process of the sender. When it is detected that the "transmission progress marker" is "transmission completed", the authority verification process is triggered: first, the receiver process identifier (lwp_rcv_id, the physical meaning is the unique identification code of the receiver interactive process, and the source is the instruction interaction meta data conformation) and the corresponding read-write permission marker (rw_flag) of the interactive process binding structure (lwp_bind_t) are extracted, and it is verified whether the rw_flag is "read only" (binary code "10"); then through the one-way association of lwp_bind_t and channel_base_t, it is checked whether the lwp_rcv_id is in the "associated process list" of the exclusive control channel, realizing the double check of "permission marker + process identity", avoiding illegal process reading data. After the authority verification is passed, based on the buffer address (buf_addr, the physical meaning is the starting storage address of the exclusive buffer, and the source is the platform storage resource allocation result) and the data length (d_len, the physical meaning is the total byte number of the instruction feature embedded data block, and the source is the synchronous parameter before the transmission of the sender) configured in the data transmission control structure (data_transfer_t), the complete data is read from the exclusive buffer in byte order, the instruction feature embedded data block (cmd_feat_fused_block) is obtained, and the consistency of the read data and the transmission data of the sender is ensured.

[0057] Preferably, in a scenario, when step 53 is specifically implemented, the receiving interactive process extracts the instruction type feature (cmd_type_feat) and the execution parameter feature (exec_param_feat) from the instruction feature fusion data block (cmd_feat_fused_block) triggered by the integrity verification result of step 52 (“pass”), matches the corresponding instruction execution logic based on the instruction type feature (such as calling the parameter configuration interface for the instruction type “parameter adjustment”, and calling the task scheduling interface for the instruction type “task start”), and executes the corresponding operation based on the specific configuration data in the execution parameter feature (such as adjustment threshold, task priority), to generate result data (result_data). The result data includes execution status (exec_status, physical meaning as success / failure identifier of instruction execution, such as 0x00 for “success” and 0x01 for “failure”), result parameter (result_param, physical meaning as actual output data after execution, such as adjusted parameter value, process ID after task start), and receiving process identifier (lwp_rcv_id), which is the real-time output after instruction execution. Then, the result feedback adaptation structure body (result_adapt_t) is structured and packaged according to the format requirements: first, write lwp_rcv_id as feedback identity identifier, then write exec_status and result_param as core result data; then, call the verification anchor generation rule of the instruction transmission verification structure body (data_check_t) to perform weighted hash calculation on result_data and lwp_rcv_id to generate feedback verification anchor (feedback_anchor, physical meaning as integrity identifier of feedback data block, its generation rule is consistent with the unique verification anchor, ensuring the uniformity of the verification logic), and write the feedback verification anchor into the corresponding field of the result feedback adaptation structure body. After packaging, the feedback data block (feedback_data_block) is formed, based on the bidirectional transmission capability of the exclusive control channel, a reverse transmission request is initiated to the sender, the “transmission progress marker” of the data transmission control structure body is updated to “feedbacking” during the transmission process, and after the transmission is completed, it is updated to “feedback completed” and the state is synchronized to the “transmission state field” of the instruction interaction meta data conformation, providing a basis for the sender to listen to the feedback state.

[0058] Optionally, step 52 comprises: step 521, extracting the unique check anchor and the instruction type feature, execution parameter feature from the instruction feature embedded data block; step 522, according to the check rule of the instruction transmission check structure, recalculating the hash value after fusing the instruction type feature and the execution parameter feature, and comparing it with the extracted unique check anchor; step 523, if the comparison is consistent, it is determined that the data is complete, and the verification result "pass" is written into the result feedback adaptation structure; if the comparison is inconsistent, it is marked as "abnormal", and a retransmission request is triggered to the sender through a dedicated control channel, and the retransmission request carries the abnormal type identifier.

[0059] In this application, through step 52, the "double feature precise extraction-weighted fusion hash-exception type directional classification" bidirectional check anchor mode is constructed, which is different from the mode of single feature check, simple hash comparison and general exception feedback in the traditional scheme. Through hierarchical extraction of instruction core features, differential weight fusion and precise definition of exception types, the application realizes the rigor of data integrity verification and the pertinence of exception feedback, realizes the comprehensiveness of feature extraction, the adaptability of hash calculation and the refinement of exception handling, provides core check support for the reliability of instruction interaction, and ensures that the receiver only processes complete and effective instruction data.

[0060] Preferably, the specific implementation process of step 521 is as follows: taking the instruction feature embedded data block (cmd_feat_fused_block) read by step 51 as the processing object, calling the feature hierarchical extraction interface designed by the application, and parsing each field according to the data block packaging order (identifier-parameter-feature-anchor). First, the unique check anchor (anchor_code, the physical meaning is the instruction data integrity identifier generated by the sender, the source is the hash value calculated by the sender based on the instruction content and process identifier, the format is 64-bit binary) is extracted from the tail of the data block; then the instruction type feature (cmd_type_feat, the physical meaning is the quantitative representation of instruction function, the source is the 16-dimensional feature vector packaged by the sender) is extracted from the feature segment of the data block; finally, the execution parameter feature (exec_param_feat, the physical meaning is the structured data of instruction execution parameter, the source is the parameter feature matrix packaged by the sender, the matrix row represents the parameter item and the column represents the quantitative value). The extracted unique check anchor, instruction type feature and execution parameter feature are combined in the order of "anchor-type feature-parameter feature" to form a feature extraction set (extracted_feat_set), and the physical meaning of the set is a core data carrier for integrity verification, ensuring the comprehensiveness of the check basis.

[0061] Preferably, in the specific technical implementation of step 522, the call instruction transmits the preset weighted fusion hash rule in the data_check_t structure body, which is designed for the adaptive instruction interaction scene, and the core purpose is to highlight the influence of key features on the verification result through differentiated weights, avoiding the problem of low verification fault tolerance caused by single feature hashing. Taking the extracted_feat_set obtained in step 521 as the processing object, first, the instruction type feature vector and the execution parameter feature matrix are respectively serialized to convert them into continuous binary data streams; then, the hash weights are allocated according to the preset weight allocation rule, wherein the instruction type feature accounts for 35% (because the instruction type determines the execution logic and has a higher impact on data integrity), and the execution parameter feature accounts for 40% (the parameter accuracy directly affects the execution result), and the weight allocation is based on the influence degree of the features on the effectiveness of the instruction interaction; the serialized two types of feature data streams are weighted and spliced according to the weights to obtain the fused_feat_stream; finally, the designed hash calculation logic is executed on the fused_feat_stream to generate the compare_anchor consistent with the unique verification anchor format, and the compare_anchor is compared with the unique verification anchor (anchor_code) in the extracted_feat_set bit by bit to obtain the match_result, which is "consistent" or "inconsistent", and the physical meaning is the integrity verification conclusion of the current instruction data block.

[0062] Preferably, in a scenario, when step 523 is implemented, the match_result obtained in step 522 is taken as the processing object, if the match_result is consistent, it is determined that the instruction feature embedding data block is complete, the field write interface of the result_adapt_t structure is called, and the verification result "pass" is written into the "verification state" field of the structure, providing verification basis for subsequent result packaging. If the match_result is inconsistent, the verification result is marked as "abnormal", and the abnormal type is accurately classified based on the log information of the feature extraction and comparison process: when the difference between the compare_anchor and the anchor_code exceeds the preset proportion (such as 5%), it is determined that the anchor point is not matched (the physical meaning is that the instruction data transmission process is tampered or the hash calculation is deviated); when there is a field missing (such as the number of rows of the execution parameter feature matrix is less than the preset number) when extracting features in step 521, it is determined that the data is missing (the physical meaning is that the instruction data block transmission is not complete). The abnormal type is written into the "abnormal type" field of the result_adapt_t structure, the abnormal feedback interface of the exclusive control channel is called, the retransmission request carrying the abnormal type identifier (such as 0x01 represents anchor point mismatch, 0x02 represents data missing) is generated, and the retransmission request is sent to the sender interactive process through the bidirectional transmission capability of the exclusive control channel, so that the sender can retransmit the complete instruction data.

[0063] Optionally, it further comprises step 6, the sender interactive process checks the feedback data block, and updates the interaction state identifier of the instruction interaction element data conformation.

[0064] Optionally, step 6 comprises: step 61, the sender interactive process listens to the feedback state of the exclusive control channel, reads the feedback data block, and calls the instruction transmission verification structure to verify the feedback verification anchor point; step 62, if the verification is passed, the result data is extracted from the feedback data block, and the interaction state identifier of the instruction interaction element data conformation is updated to "completed"; if the verification fails, it is marked as "feedback abnormal", and the instruction transmission is reinitiated according to the retry rule in the instruction interaction element data conformation; step 63, the final state of the instruction interaction element data conformation is synchronized to the interaction log of the multi-task computing platform.

[0065] In the present application, the implementation of steps 61 and 63 realizes the construction of "accurate perception of feedback state-verification of anchor point bidirectional verification-structured tracing of interaction state", which is different from the mode of passive feedback monitoring, single verification logic and scattered log recording in traditional solutions. Through the cooperative monitoring of the polling mechanism and the state field, the homologous verification of the feedback verification anchor point and the full-dimensional log encapsulation of the interaction state, the present application realizes the timeliness of feedback reception, the reliability of verification results and the traceability of the interaction process, realizes the end protection of the integrity of the instruction interaction, and provides reference historical data support for subsequent similar task interaction.

[0066] Preferably, the specific implementation process of step 61 is as follows: the sender interaction process starts the feedback state polling mechanism, calls the channel feedback query interface according to the preset period (such as 15 ms), reads the "transmission progress marker" field in the channel base information structure (channel_base_t) of the exclusive control channel, the physical meaning of the field is the transmission state identifier (such as "unfeedback", "feedbacking" and "feedback completed") of the feedback data block, and the source is the state data updated synchronously in the receiving feedback transmission process. When it is detected that the "transmission progress marker" is "feedback completed", based on the buffer address (buf_addr, the physical meaning is the starting storage address of the exclusive buffer, and the source is the platform storage resource allocation result) and the feedback data length (feedback_len, the physical meaning is the total byte number of the feedback data block, and the source is the synchronized parameter before the receiving feedback transmission) configured in the data transmission control structure (data_transfer_t), the complete data is read in byte order from the exclusive buffer to obtain the feedback data block (feedback_data_block). Then, the preset verification anchor generation rule (homologous to the rule of generating a unique verification anchor by the sender and generating a feedback verification anchor by the receiver) in the instruction transmission verification structure (data_check_t) is called to extract the feedback verification anchor (feedback_anchor, the physical meaning is the integrity identifier of the feedback data block, and the source is the hash value calculated by the receiver based on the result data and the receiver process identifier) from the feedback data block; At the same time, the core data (execution state, result parameter, receiver process identifier) in the feedback data block is executed according to the same weight allocation rule to generate a verification anchor (verify_anchor), and the feedback verification anchor and the verification anchor are compared bit by bit in binary to obtain a feedback verification result (feedback_check_result), which is "pass" or "fail", and the physical meaning is the integrity verification conclusion of the feedback data block.

[0067] Preferably, in the specific technical implementation of step 63, the instruction interaction metadata configuration updated in step 62 is taken as the processing object, the core state information is extracted, including interaction state identification (such as "complete", "feedback exception"), exception type (such as "anchor point mismatch", "data missing", only in the case of exception), retry count (retry_cnt, physical meaning is the number of times of retransmission of the instruction, source is the value accumulated according to the retry rule in step 62, example: 0-3 times), interaction time limit actual consumption (t_actual, physical meaning is the total time consumption from the start of instruction transmission to the end of feedback verification, source is the system timestamp difference calculation, example: 35ms), sender process identification (lwp_snd_id), receiver process identification (lwp_rcv_id), and exclusive control channel identification (channel_id). The structured log generation interface designed in the present application is called to encapsulate the above-mentioned core state information into a standardized interaction log entry (log_entry) according to the fixed field order of "channel identification-process identification-interaction state-time limit consumption-exception information-retry count". The physical meaning of the log entry is the full-dimensional state record of a single instruction interaction, the fields are distinguished by a separator (such as 0xBB) to ensure the consistency of log analysis. Through the log writing interface of the multi-task computing platform, the standardized interaction log entry is synchronized to the interaction log module of the platform, which stores all interaction log entries of the same exclusive control channel in the form of log files (such as channel_0x02001.log), updates the log writing state marker to "archived" during the synchronization process, and synchronizes the marker to the "log state field" of the instruction interaction metadata configuration, ensuring the full-process traceability of the interaction state and providing data support for subsequent interaction problem troubleshooting and interaction efficiency optimization.

[0068] Optionally, step 62 includes: step 621, if the feedback verification anchor point verification is passed, the execution state and result parameter are extracted from the feedback data block, the interaction state identification of the instruction interaction metadata configuration is updated to "complete"; step 622, if the verification fails, the feedback exception is marked in the instruction interaction metadata configuration, and the exception type is recorded as anchor point mismatch and / or data missing; step 623, based on the exception type, the instruction packaging and transmission process of step 4 is re-executed according to the retry rule in the instruction interaction metadata configuration, and the retry count is written into the retry count field of the instruction interaction metadata configuration.

[0069] In the present application, based on step 62, the interactive state of "check result directional driving-exception type accurate image-retry rule dynamic adaptation" is constructed, which is different from the mode of state update singularization, exception definition fuzzification and retry logic fixation in the traditional scheme. Through the structured mapping of check results and interactive states, the scenario-based classification of exception types, and the deep binding of retry rules and exception types, the present application realizes the accuracy of interactive state update, the pertinence of exception handling and the rationality of retry execution, realizes the full field coverage of state update, the quantitative basis of exception classification and the differentiated adaptation of retry logic, provides the core driving for fault tolerance of instruction interaction, and ensures efficient repair under abnormal scenarios and orderly ending under normal scenarios.

[0070] Preferably, the specific implementation process of step 621 is as follows. Taking the feedback check result ("pass") obtained in step 61 as the processing object, a feedback data parsing interface is called to extract two types of core result data from the feedback data block (feedback_data_block): execution status (exec_status, physical meaning: final state identifier of the receiving party executing the instruction, source: output after receiving party execution, format: binary encoding, such as 0x00 representing "success" and 0x01 representing "failure") and result parameter (result_param, physical meaning: actual output data after instruction execution, source: operation result of receiving party execution logic, such as actual value after parameter adjustment, process ID after task start, etc.). The extracted execution status and result parameter are stored in association in the "result data field" of the instruction interaction metadata conformation, and at the same time, a metadata update interface is called to update the "interactive state identifier" field of the instruction interaction metadata conformation to "complete". The physical meaning of this identifier is that the whole process from initiation to feedback check pass of a single instruction interaction is completed, and the "interaction completion timestamp" field is updated synchronously (source: current system time, format: millisecond level timestamp, example: 1698765432100ms), forming a complete interaction success state record and providing structured data support for subsequent log synchronization.

[0071] Preferably, in the specific technical implementation of step 622, the feedback verification result ("failure") obtained in step 61 is taken as the processing object, the exception marking interface is called, and "feedback exception" is marked in the "interaction state identification" field of the instruction interaction metadata configuration, indicating that the current interaction does not reach the expectation. Based on the verification log generated in the verification process of step 61 (including the comparison details of the feedback verification anchor and the verification anchor, and the field analysis log of the feedback data block), the type of exception is accurately defined: when the comparison log shows that the binary bit difference between the feedback verification anchor (feedback_anchor) and the verification anchor (verify_anchor) accounts for more than a preset threshold (such as 3%), it is determined that there is an "anchor point mismatch" exception, and the physical meaning of this exception is that the feedback data block is tampered with or the hash calculation is deviated in the transmission process, and the source is the homologous verification logic of the verification anchor; when the analysis log shows that the core field (such as the execution state and the result parameter) in the feedback data block is missing or the length is less than the preset standard (such as the result parameter field length is less than 8 bytes), it is determined that there is a "data missing" exception, and the physical meaning of this exception is that the feedback data block transmission is incomplete, and the source is the structured analysis result of the feedback data. The determined type of exception is written into the "exception type field" of the instruction interaction metadata configuration, and if there are two types of exceptions coexisting, the principle of "anchor point mismatch priority" is followed to record the composite exception identification (such as 0x03 represents "anchor point mismatch + data missing"), and the accuracy of the exception image is ensured.

[0072] Preferably, in a scenario, step 623 is specifically implemented to process the retry rule in the instruction interaction metadata complex recorded in step 622, which is designed for different abnormal scenarios, and the core logic is to assign different retry strategies based on the repair difficulty of the abnormal type, which is derived from the preset "retry configuration field" in the instruction interaction metadata complex (including the upper limit of the number of retries corresponding to different abnormal types, the retry interval). First, read the "retry count field" (retry_cnt, physical meaning: the number of retries currently executed, initial value 0) in the instruction interaction metadata complex. If the number of retries does not reach the upper limit of the corresponding abnormal type (for example, the upper limit of "anchor point mismatch" is 3 times, and the upper limit of "data missing" is 2 times. Example: current retry_cnt=1<3), determine the retry interval based on the abnormal type (for example, the anchor point mismatch corresponds to an interval of 20ms, and the data missing corresponds to an interval of 15ms), and wait for the interval time to trigger the retry process. The retry process specifically re-executes the instruction encapsulation and transmission process in step 4: the sender interaction process re-calls the verification anchor point generation rule of the instruction transmission verification structure, generates a unique verification anchor point based on the original uplink interaction instruction content, integrates the new instruction feature embedded data block according to the format requirement, and re-transmits it through the exclusive control channel in a non-blocking mode. After transmission is completed, the retry count field (retry_cnt) is incremented by 1 and written into the instruction interaction metadata complex. If the number of retries reaches the upper limit and is still unsuccessful, the "interaction status identifier" field is marked as "interaction failure", and the retry process is terminated, ensuring the rationality of the retry execution and the controllability of the resource occupation.

[0073] As shown in Figure 2 , it is an instruction interaction device of a multi-task computing platform according to an embodiment of the present application, comprising: an interaction element extraction module, configured to perform semantic deconstruction and interaction element extraction on the demand description of the interaction task in the multi-task computing platform to generate an instruction interaction metadata complex; an exclusive channel creation module, configured to create an exclusive control channel between the sender and the receiver in the multi-task platform according to the channel configuration parameters and the interaction time limit requirement elements in the instruction interaction metadata complex; a process channel binding module, configured to establish a bidirectional binding between the sender, the receiver interaction process and the exclusive control channel according to the process identifier and the permission rule in the instruction interaction metadata complex; an instruction encapsulation and transmission module, configured to encapsulate the uplink interaction instruction into an instruction feature embedded data block based on the format requirement of the created instruction transmission verification structure under the permission constraint and channel association of the bidirectional binding; an instruction response feedback module, configured to read the instruction feature embedded data block from the exclusive control channel under the link protection and verification rule of the bidirectional binding, generate result data and encapsulate it into a feedback data block after responding to the uplink interaction instruction; and a state updating module, configured to verify the feedback data block and update the interaction state identifier of the instruction interaction metadata complex.

[0074] As Figure 3 shown in Fig. 1, an electronic device according to an embodiment of the present application includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the instruction interaction method of the multi-task computing platform when executing the computer program.

[0075] The above Figure 2 and Figure 3 are exemplary explanations, and the description of the above Figure 1 can be referred to, and will not be repeated here.

Claims

1. A method for instruction interaction of a multitasking computing platform, characterized in that, Comprise: Step 1, the semantic deconstruction and interactive element extraction of the demand description of the interactive task in the multi-task computing platform are carried out to generate the instruction interaction metadata conformation; Step 2, according to the channel configuration parameter and the interaction time limit requirement element in the instruction interaction metadata conformation, the exclusive control channel between the sender and the receiver in the multi-task platform is created; Step 3, according to the process identification and the permission rule in the instruction interaction metadata conformation, the bidirectional binding of the sender, the receiver interactive process and the exclusive control channel is established; Step 4, under the permission constraint and the channel association of the bidirectional binding, the sender interactive process encapsulates the uplink interactive instruction into the instruction characteristic embedded data block based on the format requirement of the created instruction transmission verification structure body; Step 5, under the link protection and the verification rule of the bidirectional binding, the receiver interactive process reads the instruction characteristic embedded data block from the exclusive control channel to generate the result data encapsulated as the feedback data block in response to the uplink interactive instruction.

2. The method of instruction interaction of a multi-task computing platform according to claim 1, wherein, Step 2 comprises: step 21, the exclusive control channel identification used for process binding verification is allocated through the channel basic information structure body, the channel type is set as the instruction interaction channel to initialize the exclusive control channel.

3. The method of instruction interaction of a multi-task computing platform according to claim 2, wherein, Step 2 further comprises: step 22, the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body are created, the interactive process binding structure body is used for storing the process-channel association relationship, the instruction transmission verification structure body presets the verification anchor point generation rule, and the result feedback adaptation structure body defines the result data format.

4. The method of instruction interaction of a multi-task computing platform according to claim 2, wherein, Step 2 further comprises: step 23, the core parameters including the process identification, the interaction time limit and the data length are extracted from the instruction interaction metadata conformation and written into the corresponding fields of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body respectively, the one-way association of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body with the exclusive control channel is established, and the core parameters of the instruction interaction metadata conformation are synchronized to the configuration field of the exclusive control channel to complete the creation of the exclusive control channel.

5. The method of instruction interaction of a multi-task computing platform according to claim 4, wherein, Step 23 comprises: step 231, the process identification, the interaction time limit and the data length parameters are extracted from the instruction interaction metadata conformation and written into the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body respectively according to the field mapping rule; step 232, the one-way association of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body with the exclusive control channel is established through the structure body association interface, the association relationship is synchronized to the structure body association field of the instruction interaction metadata conformation; and step 233, the parameter integrity of the interactive process binding structure body, the instruction transmission verification structure body and the result feedback adaptation structure body is verified to make the core parameters of the instruction interaction metadata conformation not missed, and the creation of the exclusive control channel is completed after the parameter integrity verification passes.

6. The method of instruction interaction of a multi-task computing platform of claim 1, wherein, Step 3 comprises: step 31, reading the sender, receiver process identifier and permission rule from the instruction interaction metadata configuration, the permission rule defining the interaction permission of the sender only write and the receiver only read; step 32, filling the exclusive control channel identifier and the corresponding process identifier in the interaction process binding structure based on the sender and receiver process identifier, and setting the read-write permission mark based on the permission rule; step 33, the system layer checks the uniqueness of the associated information in the interaction process binding structure, and updates the running state of the exclusive control channel to occupied after the check is passed, and synchronizes to the channel state field of the instruction interaction metadata configuration, so as to complete the bidirectional binding.

7. The method of instruction interaction of a multi-task computing platform of claim 1, wherein, Step 4 comprises: step 41, the sender interaction process calls the check anchor generation rule in the instruction transmission check structure, generates a unique check anchor based on the uplink interaction instruction content, and the unique check anchor is used for data integrity verification of the receiver; step 42, integrating the instruction type, execution parameter, unique check anchor and sender process identifier according to the format requirement of the instruction transmission check structure to generate instruction feature embedded data block; step 43, the exclusive control channel feeds back transmission permission based on the interaction time limit parameter of the instruction interaction metadata configuration, so that the sender transmits the instruction feature embedded data block to the exclusive control channel in a non-blocking mode.

8. The method of instruction interaction of a multi-task computing platform according to claim 7, wherein, Step 42 comprises: step 421, extracting the type feature and execution parameter feature of the uplink interaction instruction, and associating the sender process identifier to obtain the instruction-process association feature set; step 422, calling the check anchor generation rule of the instruction transmission check structure, and performing hash calculation on the type feature, execution parameter feature and process identifier in the instruction-process association feature set to generate a unique check anchor; step 423, encapsulating the instruction-process association feature set and the unique check anchor in the order of "identifier-parameter-feature-anchor" to form the instruction feature embedded data block.

9. The method of instruction interaction of a multi-task computing platform of claim 1, wherein, Step 5 comprises: step 51, the receiver interaction process listens to the transmission state of the exclusive control channel, verifies the read-only permission of itself through the interaction process binding structure, and reads the instruction feature embedded data block after the permission verification is passed; step 52, calling the check rule of the instruction transmission check structure, extracting the unique check anchor, instruction type feature and execution parameter feature in the instruction feature embedded data block, verifying the integrity through the bidirectional check anchoring mechanism after fusing the instruction type feature and execution parameter feature, and recording the verification result to the result feedback adaptation structure; step 53, executing the uplink interaction instruction logic after the verification is passed, generating result data, encapsulating according to the format requirement of the result feedback adaptation structure, adding a feedback check anchor and encapsulating as a feedback data block, and transmitting to the sender through the exclusive control channel in reverse.

10. The method of instruction interaction of a multi-task computing platform according to claim 9, wherein, Step 52 includes: step 521, extracting unique check anchor and instruction type features, execution parameter features from instruction feature embedded data block; step 522, according to the check rule of instruction transmission check structure, recalculating the hash value after fusing instruction type features and execution parameter features, and comparing it with the extracted unique check anchor; step 523, if the comparison is consistent, it is determined that the data is complete, and the verification result "pass" is written into the result feedback adaptation structure; if the comparison is inconsistent, it is marked as "abnormal", and a retransmission request is triggered to the sender through the exclusive control channel, and the retransmission request carries the abnormal type identifier.

11. The method of claim 1-10, wherein, It also includes step 6, the sender interaction process checks the feedback data block, and updates the interaction state identifier of the instruction interaction element data conformation.

12. The method of instruction interaction of a multi-task computing platform according to claim 11, wherein, Step 6 includes: step 61, the sender interaction process listens to the feedback state of the exclusive control channel, reads the feedback data block, and calls the instruction transmission check structure to verify the feedback check anchor; step 62, if the verification is passed, the result data is extracted from the feedback data block, and the interaction state identifier of the instruction interaction element data conformation is updated to "complete"; if the verification fails, it is marked as "feedback exception", and the instruction transmission is reinitiated according to the retry rule in the instruction interaction element data conformation; step 63, the final state of the instruction interaction element data conformation is synchronized to the interaction log of the multi-task computing platform.

13. The method of instruction interaction of a multi-task computing platform according to claim 12, wherein, Step 62 includes: step 621, if the feedback check anchor verification is passed, the execution state and result parameter are extracted from the feedback data block, and the interaction state identifier of the instruction interaction element data conformation is updated to "complete"; step 622, if the verification fails, mark "feedback exception" in the instruction interaction element data conformation, and record the exception type as anchor mismatch and / or data missing; step 623, based on the exception type, re-execute the instruction packaging and transmission process of step 4 according to the retry rule in the instruction interaction element data conformation, and the retry count is written into the retry count field of the instruction interaction element data conformation.

14. An instruction interaction apparatus for a multitasking computing platform, characterized by: It includes: An interaction element extraction module for semantic deconstruction and interaction element extraction of the demand description of the interaction task in the multi-task computing platform to generate an instruction interaction element data conformation; A dedicated channel creation module for creating a dedicated control channel between the sender and the receiver in the multi-task platform according to the channel configuration parameters and interaction time limit elements in the instruction interaction element data conformation; A process channel binding module for establishing a bidirectional binding between the sender and receiver interaction processes and the dedicated control channel according to the process identifier and permission rules in the instruction interaction element data conformation; An instruction packaging and transmission module for packaging the uplink interaction instruction as an instruction feature embedded data block based on the format requirements of the created instruction transmission check structure under the permission constraints and channel association of the bidirectional binding; An instruction response feedback module for reading the instruction feature embedded data block from the dedicated control channel under the link protection and check rule of bidirectional binding, generating result data and packaging it as a feedback data block after responding to the uplink interaction instruction.

15. An electronic device, comprising: A computer program product comprising a processor, a memory, and a computer program stored on the memory and loadable on the processor, the processor implementing the method of instruction interaction of the multitasking computing platform of any of claims 1-13 when executing the computer program.

Images