Cross-level information interaction intelligent adaptation method and system

Abstract

The present application relates to the technical field of communication mechanism, specifically to a cross-layer information interaction intelligent adaptation method and system, comprising the following steps: obtaining the end side and interface message comparison field semantics to establish channel index, determining slot landing point according to field constraint identifier to establish field routing list, judging session migration position to establish breakpoint record, selecting switching path according to access authority and missing identifier to establish message pass token, adjusting sending channel to write frame header to generate communication scheme.In the present application, by comparing the message field with the access level to build channel index, the static matching limit is broken through, based on the constraint identifier to determine the landing point to generate the routing list to fill the transmission fault, combined with the token to judge the migration position to build the breakpoint record to maintain the coherence of the flow conversion, dynamically selecting the path to generate the pass token to eliminate the authority hindrance, adjusting the channel to write the target frame header to reshape the cross-layer call sequence, effectively rooting out the synchronous lag disadvantages to establish the self-matching collaborative interaction environment.

Description

Technical Field

[0001] This invention relates to the field of communication mechanism technology, and in particular to a cross-level information interaction intelligent adaptation method and system. Background Technology

[0002] The field of communication mechanism technology mainly involves information transmission, state synchronization, instruction coordination, and interaction constraint management between differentiated software layers, business processes, protocol stacks, service interfaces, and data resources. Its core aspects include the identification agreement between information senders and receivers, the field definition of interactive data, the calling order between layers, the encapsulation rules of message formats, the mapping relationship of interface parameters, the recording method of session state, the judgment basis of permission verification, and the handling process of abnormal interactions. Overall, it is used to support the application layer, service layer, protocol layer, and data layer to complete request submission, result return, state update, and context transmission according to established rules. Traditional cross-level information interaction intelligent adaptation methods and systems refer to technical issues related to inconsistencies in information content, interaction rules, and processing flows between different software levels. Typically, this involves pre-configuring a level identifier table, an interface field mapping table, a message type list, parameter conversion rules, interaction sequence templates, status code mapping relationships, and permission judgment conditions. This process identifies the source of requests from different levels, splits fields, converts formats, completes parameters, matches rules, selects the target level, and writes interaction records. Based on preset business process nodes, interface call conditions, data dictionary entries, and context state records, it completes the adaptation and transmission of cross-level information.

[0003] Traditional cross-level information interaction relies on pre-configured hierarchical identifier tables and interaction sequence templates to handle differentiated software requests. Static matching mechanisms are difficult to cope with frequent context state changes. Over-reliance on fixed parameter conversion rules for format conversion can easily cause context transmission gaps in business processes. Rigid interface parameter mapping and session state recording methods cannot guarantee the dynamic continuity of calls between levels. Fixed permission verification and iteration weaken the flexibility of exception handling, resulting in unavoidable operational lag and failure risks in information transmission and state synchronization between multiple levels. Summary of the Invention

[0004] To achieve the above objectives, the present invention adopts the following technical solution: a cross-level information interaction intelligent adaptation method, comprising the following steps: S1: Based on the edge gateway protocol stack, obtain the end-side request message, target-level interface message, session token identifier, compare field semantics, message direction and access level, and establish an interface channel index; S2: Based on the interface channel index, filter the target field slots of the edge gateway access channel, determine the slot landing point according to the field adaptation constraint identifier, and establish a field slot routing list; S3: Based on the field slot routing list, determine the cross-level session migration location, mark the switching location according to the token adaptation identifier, and establish a session migration breakpoint record; S4: Based on the session migration breakpoint record, determine the message field transfer path within the cross-level call channel, select the transfer path according to access permissions, missing field identifiers, and business process nodes, and establish a message access token; S5: Based on the message access token, adjust the cross-level transmission channel, write the target slot and frame header identifier, and generate a cross-level adaptive communication scheme.

[0005] As a further aspect of the present invention, the interface channel index includes a mapped logical link key value, a bound network card address, and an allocated addressing priority; the field slot routing list includes a set memory offset, a defined data format, and a reserved buffer capacity; the session migration breakpoint record includes a frozen communication timestamp, a saved context snapshot, and a temporarily stored sequence number parameter; the message access token includes an issued encrypted digest, a set lifecycle threshold, and an granted release credential; and the cross-layer adaptive communication scheme includes a planned reassembly strategy, established retransmission rules, and an optimized reshaping mechanism.

[0006] As a further aspect of the present invention, the slot landing point refers to the specific writing position and mapping position of the target field in the edge gateway access channel determined according to the field adaptation constraint.

[0007] As a further aspect of the present invention, the cross-level transmission channel refers to the communication transmission path for transmitting adapted messages between the differentiated interface level, the protocol level, and the service level.

[0008] As a further aspect of the present invention, the specific steps of S1 are as follows: S101: Obtain the client-side request message, target-level interface message, session token identifier and port access identifier, parse the protocol type, header and payload content, and match the corresponding semantic tags according to the field name and field value to form message field semantic tags; S102: Based on the semantic marker of the message field, compare the values ​​of the same-name field between the end-side request message and the target-level interface message, verify the matching relationship between the message direction and the access level, associate the session token identifier and the port access identifier, and generate a direction-level association key. S103: Based on the direction level association key, determine the correspondence between field semantic labels, message direction and access level, merge the port access identifier under the same session token identifier with the target level interface message, and establish an interface channel index.

[0009] As a further aspect of the present invention, the specific steps of S2 are as follows: S201: Based on the interface channel index, retrieve the interface number, port access identifier and field slot number within the edge gateway access channel, merge the field slot numbers according to the channel number, filter the target field slot, and generate a channel slot correspondence table; S202: Based on the channel slot correspondence table, compare the consistency of the field semantics with the target field slot semantics label, determine the required flag value and access permission identifier level, associate the slot number with the permission level, and obtain the slot landing point identifier table. S203: Based on the slot landing point identifier table, map the routing relationship between the target field slot, field semantics, required field flag and access permission flag, merge the slot landing points according to the interface number, and establish a field slot routing list.

[0010] As a further aspect of the present invention, the specific steps of S3 are as follows: S301: Based on the field slot routing list, compare the interface numbers of the regional business server access channel and the cloud management platform access channel, verify the occupancy status of the field slot number in the two types of channels, map the migration position according to the channel number, and generate a channel migration position table. S302: Based on the channel migration location table, compare the token version identifier value and the scope identifier value, determine the version change relationship and scope inheritance relationship under the same session token identifier, associate the migration location and field slot number, and obtain the token scope switching table; S303: Based on the token scope switching table, determine the slot occupancy status for the field occupancy identifier, map the breakpoint relationship between the token version identifier, scope identifier, field occupancy identifier and switching position, and establish a session migration breakpoint record.

[0011] As a further aspect of the present invention, the specific steps of S4 are as follows: S401: Based on the session migration breakpoint record, verify the cross-level message call channel breakpoint number, field slot number and message direction, map path nodes according to the matching relationship between the field transfer-out end and the transfer-in end, and generate a field transfer path table; S402: Based on the field transfer path table, compare the access permission identifier level with the business process node order, determine the missing field identifier's placeholder status in the path node, associate the access permission level, process node, and field slot number to obtain the path selection identifier table. S403: Select an identifier table based on the path, merge path nodes under the same session token identifier for the field transfer path table, map access permission identifier, business process node, missing field identifier and transfer path, and establish a message passage token.

[0012] As a further aspect of the present invention, the specific steps of S5 are as follows: S501: Based on the message access token, parse the session token identifier, transfer path and access permission identifier, compare the cross-level sending channel protocol route and transfer path nodes, adjust the protocol route according to the node order, and generate a protocol route matching table; S502: According to the protocol routing matching table, call the transport layer and message exit identifier, compare the path node layer sequence number with the exit number, associate the protocol route, transport layer and message exit identifier, and obtain the exit layer mapping table; S503: Based on the export level mapping table, and according to the target slot and frame header identifier, verify the correspondence between the slot number and the export number, map the frame header identifier, protocol route and transmission level, and establish a cross-level adaptation communication scheme.

[0013] A cross-level information interaction intelligent adaptation system, comprising: The interface channel index building module is used to implement: S1: Based on the edge gateway protocol stack, obtain the end-side request message, the target layer interface message, the session token identifier, compare the field semantics, message direction and access layer, and build the interface channel index; The field slot routing list creation module is used to implement: S2: Based on the interface channel index, filter the target field slots of the edge gateway access channel, determine the slot landing point according to the field adaptation constraint identifier, and create a field slot routing list; The session migration breakpoint recording module is used to implement: S3: Based on the field slot routing list, determine the cross-level session migration location, mark the switching location according to the token adaptation identifier, and establish a session migration breakpoint record; The message access token generation module is used to implement: S4: Based on the session migration breakpoint record, determine the message field transfer path in the cross-level call channel, select the transfer path according to the access permissions, missing field identifiers and business process nodes, and establish a message access token; The cross-level transmission channel adaptation module is used to implement: S5: Based on the message access token, adjust the cross-level transmission channel, write the target slot and frame header identifier, and generate a cross-level adaptation communication scheme.

[0014] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, a dynamic interface channel index is constructed by comparing the semantics of message fields with the access layer to overcome the inherent rule matching limitations. Based on the field adaptation constraint identifier, the slot landing point is determined and a routing list is generated to accurately fill the information transmission gap. The cross-layer session migration position is determined by combining the token adaptation identifier to construct breakpoint records to maintain the continuity of business flow. According to the access permission and missing field identifier, the transfer path is dynamically selected to generate a pass token to eliminate the permission verification obstacle. The sending channel is adjusted according to the pass token and accurately written to the target slot and frame header identifier to reshape the cross-layer call order. From the underlying architecture dimension, the drawback of state synchronization lag is eliminated and a highly self-matching collaborative interaction environment is established. Attached Figure Description

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

[0016] Figure 1 This is a schematic diagram of the steps of the present invention; Figure 2 This is a detailed schematic diagram of S1 of the present invention; Figure 3 This is a detailed schematic diagram of S2 of the present invention; Figure 4 This is a detailed schematic diagram of S3 of the present invention; Figure 5 This is a detailed schematic diagram of S4 of the present invention; Figure 6 This is a detailed schematic diagram of S5 of the present invention; Figure 7 This is a system module diagram of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0018] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0019] This embodiment provides a cross-level information interaction intelligent adaptation method. In practical applications, for example, during the operation of a communication network where a terminal-side service initiates a service message to a regional service server via an edge gateway and the cloud management platform continues the management session, the terminal-side service generates a request frame carrying service fields. The edge gateway handles protocol parsing, interface addressing, field forwarding, and transmission shaping; the regional service server handles the service session; and the cloud management platform handles the management session. The objects processed by this method are always the protocol messages, session credentials, access port status, and field carrying locations in the aforementioned communication network.

[0020] Please see Figure 1 and Figure 2 The specific steps of S1 are as follows: Based on the edge gateway protocol stack, obtain the end-side request message, target-level interface message, session token identifier, and port access identifier; compare the semantics of the message fields, message direction, and access level; and establish an interface channel index. The edge gateway protocol stack is a protocol processing component deployed on the edge gateway, responsible for frame reception, header identification, payload decomposition, and target interface encapsulation. The end-side request message is a service request frame sent to the edge gateway by the end-side service terminal through the access port. The target-level interface message is the target received frame structure published by the regional service server interface or cloud management platform interface and read by the edge gateway. The session token identifier is a credential marker that enters with the request frame and is used to associate the same service session context. The port access identifier is a marker added by the edge gateway when the message enters, corresponding to the physical and logical access points. The interface channel index is the index record formed in this step; its data object consists of logical link key values, network card address binding information, and addressing priority rules, with input from message parsing results and access point registration information.

[0021] S101: Based on the edge gateway protocol stack, obtain the end-side request message, target-level interface message, session token identifier, and port access identifier. Compare the message field semantics, message direction, and access layer to establish an interface channel index. The edge gateway protocol stack is a protocol processing component deployed on the edge gateway, responsible for frame reception, header identification, payload decomposition, and target interface encapsulation. The end-side request message is a service request frame sent by the end-side service terminal to the edge gateway via the access port. The target-level interface message is the target received frame structure published by the regional service server interface or cloud management platform interface and read by the edge gateway. The session token identifier is a credential marker that enters with the request frame and is used to associate the same service session context. The port access identifier is a marker added by the edge gateway when the message enters, corresponding to the physical and logical access points. The interface channel index is the index record formed in this step. Its data object consists of logical link key values, network card address binding information, and addressing priority rules. Input comes from message parsing results and access point registration information.

[0022] S102: Based on the semantic tags of the message fields, compare the fields corresponding to the semantic tags in the request message from the end side and the target layer interface message. Verify whether the field value category conforms to the target interface's receiving constraints, and verify whether the request sending direction and the target receiving direction are continuous, and whether the access layer to which the port belongs and the layer to which the target interface belongs are connected. The verified fields are bound to the session token identifier and the port access identifier to form a direction layer association key. The direction layer association key is a connection record describing the source interface, receiving interface, session affiliation, and entry point affiliation of the field, carrying the positioning relationship required for subsequent merging. When fields are carried repeatedly, retain the corresponding record that can be received based on the valid write position in the interface structure, add a conflict status to the conflicting fields and write it to the traceability record; fields that are not connected in direction or layer do not enter the channel merging process.

[0023] S103: Based on the direction-level association key, the semantic tags, packet sending direction, access level, port access identifier, and target-level interface packets under the same session affiliation are merged into channel retrieval records. The logical link key carries the retrieval relationship between session affiliation, ingress affiliation, and target interface affiliation. The network interface card (NIC) address comes from the edge gateway ingress registration record and is bound to the actual transmit / receive interface. The addressing priority comes from the routing selection order in the interface configuration and limits the target interface selection relationship when packets are sent out, thereby establishing an interface channel index. When the target interface registration status is invalid, the NIC address is unavailable, or the channel merging relationship conflicts, the index record is appended with a paused addressing status and written to the channel status log. Subsequent field slot positioning only reads index records in the addressable state.

[0024] Please see Figure 1 and Figure 3 The specific steps of S2 are as follows: Based on the interface channel index, filter the target field slots within the edge gateway access channel, determine the slot landing point according to the field semantics, required field flags, and access permission identifiers, and establish a field slot routing list. A field slot is a write location in the target interface message structure used to carry a specific semantic field. The slot number, carrying format, and buffer constraints are provided by the interface configuration storage area. The required field flag is a field reception requirement marker registered with the target interface configuration. The access permission identifier is a field access level marker obtained after session credentials are authenticated. The field slot routing list is the routing record output in this step, carrying the target field slot, field source semantics, write constraints, memory offset description, data format restrictions, and reserved buffer capacity category.

[0025] S201: Based on the interface channel index, read the interface number, port access identifier, and field slot number corresponding to the addressable access channel. Merge slot records belonging to the same target interface structure according to channel number, and read the semantic tags, data format restrictions, and current write status registered for each slot. Slots with semantic relationship to the parsed field and in a write-allowed state are selected as target field slots, forming a channel-slot mapping table. The channel-slot mapping table is an intermediate record connecting channel affiliation, interface affiliation, slot number, and semantic reception range. Its input comes from the interface channel index and slot configuration, and its output goes to slot landing point verification. When the interface number is not registered, the slot configuration is missing, or the slot write status is locked, the corresponding slot is given an unselectable status and the reason for the configuration error is retained.

[0026] S202: Based on the channel slot mapping table, verify the semantic tags of the message fields against the semantic tags of the target field slots item by item. After semantic acceptance is established, read the required flags registered by the target interface and the access permission identifier formed by the session credential authentication record. The required flags limit the field categories that the target message must carry, and the access permission identifier limits the slot categories that the current session can write to and the access levels that can be reached. Establish a landing point relationship between fields that meet the semantic reception constraints and whose permission status allows writing and the slot number to obtain the slot landing point identifier table. The slot landing point identifier table carries the field source, target slot, required status, permission status, and write permission. When there is no acceptable slot for a required field, the field is registered as missing and pending processing; when the permission status does not allow writing, the field is registered as prohibited from writing and the authentication feedback is retained.

[0027] S203: Based on the slot landing point identifier table, merge the routing relationships between target field slots, field semantics, required field flags, and access permission flags according to the interface number and write them into the field slot routing list. The memory offset description points to the write position in the target interface packet carrying area, originates from the interface configuration storage area, and is fixedly bound to the slot number; the data format specifies the encoding and encapsulation categories used when the field enters the target slot; the reserved buffer capacity status indicates whether the slot remains in an acceptance state during packet reassembly. Before writing to the list, verify the field parsing status, slot write status, and permission status. If there are format inconsistencies, slot occupation conflicts, or buffer acceptance status failures, the list retains the fields to be handled and the reasons for the exceptions, and outputs the route records that can continue to be accepted to the session migration location for judgment and processing.

[0028] Please see Figure 1 and Figure 4The specific steps of S3 are as follows: Based on the field slot routing list, determine the session migration position between the regional business server access channel and the cloud management platform access channel. Mark the switching position according to the token version identifier, scope identifier, and field occupancy identifier, and establish a session migration breakpoint record. The token version identifier is a state update marker generated during the hierarchical continuation of session credentials. The scope identifier is the authorization boundary marker for the session credentials to be authorized to reach the business access channel or management access channel. The field occupancy identifier is a slot status record formed by whether the slot has been written, is pending writing, or is in a pending disposal state. The session migration breakpoint record is a data object that fixes the continuation position when the session switches from the regional business server access channel to the cloud management platform access channel. It includes frozen communication timestamp records, saved context snapshots, and temporarily stored sequence number parameters. Its output enters the field transfer path selection processing.

[0029] S301: Based on the field slot routing list, read the interface numbers of the regional business server access channel and the cloud management platform access channel. Verify the source slot status of the field slot number corresponding to the same field semantics in the business access channel and the receiving slot status in the management access channel. Register the acceptance positions of the source slot and receiving slot according to the channel number, generating a channel migration position table. The channel migration position table is an intermediate record carrying the source channel, receiving channel, source slot, receiving slot, and slot status. When the receiving channel interface status is invalid, the field slot has no semantic acceptance relationship, or the source field is in a conflict pending state, the migration position is registered as pending freezing and written to the session state log, and is not entered into the credential scope for acceptance confirmation.

[0030] S302: Based on the channel migration location table, read the token version identifier and scope identifier under the same session ownership, verify the status update relationship of session credentials between the service access channel and the management access channel, and verify whether the authorization boundary covers the receiving channel corresponding to the migration location. The migration location verified by credential status acceptance and authorization boundary is bound to the field slot number to obtain the token scope switching table. The token scope switching table records the binding relationship between session credential status, authorization boundary, receiving slot, and migration location. When the credential status is not accepted, the authorization boundary does not cover the target receiving channel, or the credential authentication record is invalid, the switching table registers a rejection switching status, the source channel retains the session ownership before freezing, and outputs an authorization feedback record.

[0031] S303: Based on the token scope switching table, read the field occupancy identifier to distinguish between fields already carried in the source slot, fields to be carried in the target slot, and fields awaiting handling due to missing or conflicting information. Establish breakpoint relationships between the token version identifier, scope identifier, field occupancy identifier, and switching location, forming a session migration breakpoint record. Communication timestamp records are obtained from edge gateway message reception and forwarding traces, used to mark the communication status at the migration boundary; context snapshots save session ownership, slot routing, authorization status, and field handling status; sequence number parameters are derived from the continuation order description in the protocol header and are temporarily stored with the breakpoint. If the breakpoint write fails, the context snapshot is missing, or the sequence acceptance status is inconsistent with the received message, the switching location remains frozen, and the abnormal status is output to the field transfer path selection processing along with the breakpoint.

[0032] Please see Figure 1 and Figure 5 The specific steps of S4 are as follows: Based on the session migration breakpoint record, determine the packet field transfer path within the cross-level packet call channel, select the transfer path according to the access permission identifier, business process node, and missing field identifier, and establish a packet access token. The business process node is the processing position record of business access, edge transfer, and management access within the same session. The missing field identifier is a status record formed when a required field has no slot to write to or when the field is not accepted during migration continuation. The packet access token is a pass credential object issued by the edge gateway for the verified transfer path, containing the issued encrypted digest, the set lifecycle determination rules, and the granted release credential. The encrypted digest is bound to session ownership, breakpoint status, path status, and permission status. The lifecycle determination rules limit the validity status of the credential in the current session continuation phase. The release credential limits the authorized sending channels and target exits, and its output enters the sending channel for adaptation processing.

[0033] S401: Based on the session migration breakpoint record, read the breakpoint number, field slot number, and message direction. Verify whether the field transfer-out end and field transfer-in end associated with the breakpoint have a confirmed slot acceptance relationship. Register the path nodes according to the order of transfer-out end, edge transfer position, and transfer-in end, and generate a field transfer path table. The field transfer path table is a data object that records the position and direction constraints of the field within the cross-level call channel, carrying the breakpoint attribution, source slot, target slot, path node, and transfer status. When the breakpoint remains in a frozen error state, the message direction conflicts with the breakpoint attribution direction, or the target slot loses write permission, the path node is registered as unrestricted. The original field status and the reason for the exception are jointly stored in the session log, without entering permission and missing field verification.

[0034] S402: Based on the field transfer path table, read the access permission identifier and business process node sequence. Verify whether the field is authorized to pass through the corresponding path node according to the credential authorization boundary, and check whether the field pointed to by the missing field identifier has a controlled write position in the path node. Path nodes with permission status allowing passage and field placeholder status conforming to the target interface's acceptance constraints are bound to the field slot number, resulting in a path selection identifier table. The path selection identifier table carries the path node, authorization status, missing field handling status, target slot, and allowable status. If the missing field has no controlled write position, permission authentication fails, or the node sequence is inconsistent with the breakpoint acceptance status, the path status is registered as prohibited, and the failure status and field source record are written to the trace storage and returned to the session access side.

[0035] S403: Based on the path selection identifier table, merge path nodes in the same session belonging to the allowed state, bind access permission identifiers, business process nodes, missing field identifiers, and transfer paths to the access credential, and establish a message access token. The encrypted digest is issued by the secure encapsulation processing structure based on the session credential status, breakpoint status, selected path, and field write status. The lifecycle determination rule is based on the current session connection stage and path allowance status registration. The allowance credential specifies the authorized sending channel, egress belonging, and target slot write permission. If digest verification fails, the credential status becomes invalid, or the egress belonging does not belong to the selected path, the access credential is given an unsendable status and the reason for rejection is retained. The sending channel adaptation processing only reads access credentials in the allowed state.

[0036] Please see Figure 1 and Figure 6 The specific steps of S5 are as follows: Based on the message access token, adjust the protocol routing, transport layer, and message exit identifier of the cross-level transmission channel, write the target slot and frame header identifier, and generate a cross-level adaptive communication scheme. Protocol routing is the encapsulation path rule recorded by the edge gateway for messages from the access side to the target interface side. The transport layer is the access home status corresponding to the message arriving at the regional business server interface or cloud management platform interface. The message exit identifier is the outgoing interface location marker registered by the transmission driver. The frame header identifier is the header encapsulation marker that identifies the message source, session home, and transmission direction of the target interface. The cross-level adaptive communication scheme is a communication record object used to execute message transmission and transmission status retention. It includes planned reassembly strategies, established retransmission rules, and optimized reshaping mechanisms. After its formation, it inherits the subsequent message transmission status of the same session.

[0037] S501: Based on the message access token, read the session token identifier, transfer path, and access permission identifier. Verify the path node specified by the access credential against the currently registered protocol route of the cross-level sending channel, and adjust the route pointer according to the path node acceptance order to generate a protocol route matching table. The protocol route matching table is a record that associates the access credential with the actual sending route, carrying session affiliation, path node, authorization status, route status, and target interface affiliation. If the path node does not correspond to the sending route, the route registration status is invalid, or the credential permissions do not cover the target interface, the matching record is appended with a prohibited outgoing status, the message to be sent is retained in the controlled temporary storage area, the reason for the route anomaly is written into the communication log, and no outgoing record is output to the egress location processing.

[0038] S502: Based on the protocol routing matching table, read the transport layer and message exit identifier. Verify whether the layer affiliation corresponding to the path node and the interface affiliation corresponding to the exit identifier are compatible. Associate the verified protocol route, transport layer, and message exit identifier to obtain the exit layer mapping table. The exit layer mapping table describes the sending location record of the message from the corresponding outgoing interface to the corresponding access layer, carrying the route affiliation, exit affiliation, layer affiliation, and sending permission status. If the exit registration fails, the target layer and path node are not compatible, or the sending driver does not confirm that the exit is in a sendable state, the mapping record is registered as a suspended sending state, and the interface feedback content returns the protocol routing matching record and is retained in the communication log.

[0039] S503: Based on the exit layer mapping table, read the target slot and frame header identifier, verify whether the slot number corresponds to the target interface structure pointed to by the exit identifier, and write the verified fields into the target slot according to the confirmed data format. Write the frame header identifier into the header of the message to be sent, forming a cross-layer adaptive communication scheme. The reassembly strategy carries the field writing order, target slot ownership, and header encapsulation relationship; the retransmission rule carries the processing relationship of re-entering the sending verification according to the original access credential state when the sending confirmation has not returned; and the shaping mechanism carries the frame structure arrangement and sending order maintenance relationship before the message enters the exit. When the target slot is not writable, the frame header state is inconsistent with the target interface, the sending confirmation is missing, or the access credential is invalid during retransmission, the message to be sent remains in a controlled state and retains the credential state, interface feedback, and sending state. When the sending confirmation is valid, the communication record saves the exit state and session continuation state, and subsequent messages read this record to enter the same continuation relationship.

[0040] Please see Figure 7 A cross-level information interaction intelligent adaptation system, comprising: Interface Channel Index Building Module: Based on the edge gateway protocol stack, this module acquires end-side request messages, target-level interface messages, session token identifiers, compares field semantics, message direction, and access layer, and builds an interface channel index. It is configured with an access message input interface, an interface configuration reading interface, and an index output interface. The input objects are end-side request messages, target-level interface messages, session token identifiers, and port access identifiers. Internally, it stores protocol identification descriptions, field semantic tags, and direction layer association keys. The output object is an interface channel index containing logical link key values, network interface card address binding information, and addressing priority rules. Incompatible states, unregistered access points, and missing session credentials are parsed and written to the logging interface but not placed in the index output interface.

[0041] The field and slot routing list creation module: Based on the interface channel index, it filters the target field and slot of the edge gateway access channel, determines the slot landing point according to the field adaptation constraint identifier, and creates a field and slot routing list. It is configured with an interface for receiving the interface channel index, an interface for reading the slot configuration, and an interface for outputting the routing list. Internally, it stores a channel and slot mapping table and a slot landing point identifier table. Field semantics, mandatory field flags, and access permission identifiers are used as the basis for slot landing points. The output object is a field and slot routing list containing memory offset descriptions, data format restrictions, and reserved buffer capacity categories. Inconsistent format states, prohibited permission states, and missing field states are retained in the routing list output content.

[0042] Session migration breakpoint recording module: Based on the field slot routing list, it determines the cross-level session migration location, marks the switch location according to the token adaptation identifier, and establishes a session migration breakpoint record. It is configured with a field slot routing list receiving interface, a token status receiving interface, and a breakpoint record output interface. Internally, it stores a channel migration location table and a token scope switching table. The slot acceptance status, token version identifier, scope identifier, and field occupancy identifier between the regional business server access channel and the cloud management platform access channel are limited to breakpoint binding content. The output object is a session migration breakpoint record containing communication timestamp freeze records, context snapshots, and temporary sequence number parameters; switch rejection status and incomplete context status are attached to the breakpoint record output interface.

[0043] The message access token generation module, based on session migration breakpoint records, determines the message field transfer path within the cross-level call channel. It selects the transfer path according to access permissions, missing field identifiers, and business process nodes, and then establishes a message access token. It is configured with an interface for receiving session migration breakpoint records, an interface for reading field slot routing lists, and an interface for outputting access credentials. Internally, it stores a field transfer path table and a path selection identifier table. Access permission identifiers, business process nodes, and missing field identifiers are used as the basis for path permission. The output object is a message access token containing an encrypted digest, preset lifecycle rules, and permission credentials. Unpermitted paths, digest verification failure status, and credential expiration status are attached to the access credential output content.

[0044] Cross-level transmission channel adaptation module: Based on message access tokens, it adjusts the cross-level transmission channel, writes the target slot and frame header identifier, and generates a cross-level adapted communication scheme. It is configured with a message access token receiving interface, a transmission channel status reading interface, and a communication record output interface. Internally, it stores a protocol routing matching table and an exit layer mapping table. Protocol routing, transport layer, message exit identifier, target slot, and frame header identifier are limited to the transmission encapsulation content. The output object is a cross-level adapted communication scheme containing reassembly strategies, retransmission rules, and reshaping mechanisms. Exit unavailable status, encapsulation inconsistency status, and no-return-acknowledgement status are attached to the communication record output content and used together with the session continuation status as the reading content for subsequent message processing.

[0045] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of protection of the technical solution.

Claims

1. A cross-level information interaction intelligent adaptation method, characterized in that, Includes the following steps: S1: Based on the edge gateway protocol stack, obtain the end-side request message, target-level interface message, session token identifier, compare field semantics, message direction and access level, and establish an interface channel index; S2: Based on the interface channel index, filter the target field slots of the edge gateway access channel, determine the slot landing point according to the field adaptation constraint identifier, and establish a field slot routing list; S3: Based on the field slot routing list, determine the cross-level session migration location, mark the switching location according to the token adaptation identifier, and establish a session migration breakpoint record; S4: Based on the session migration breakpoint record, determine the message field transfer path within the cross-level call channel, select the transfer path according to access permissions, missing field identifiers, and business process nodes, and establish a message access token; S5: Based on the message access token, adjust the cross-level transmission channel, write the target slot and frame header identifier, and generate a cross-level adaptive communication scheme.

2. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The interface channel index includes the mapped logical link key value, the bound network card address, and the assigned addressing priority. The field slot routing list includes the set memory offset, the limited data format, and the reserved buffer capacity. The session migration breakpoint record includes the frozen communication timestamp, the saved context snapshot, and the temporarily stored sequence number parameter. The message access token includes the issued encrypted digest, the set lifecycle threshold, and the granted release credential. The cross-layer adaptive communication scheme includes the planned reassembly strategy, the formulated retransmission rules, and the optimized reshaping mechanism.

3. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The slot placement point refers to the specific writing and mapping position of the target field in the edge gateway access channel, determined according to the field adaptation constraints.

4. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The cross-level transmission channel refers to the communication transmission path for transmitting adapted messages between the differentiated interface layer, protocol layer, and service layer.

5. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The specific steps of S1 are as follows: S101: Obtain the client-side request message, target-level interface message, session token identifier and port access identifier, parse the protocol type, header and payload content, and match the corresponding semantic tags according to the field name and field value to form message field semantic tags; S102: Based on the semantic marker of the message field, compare the values ​​of the same-name field between the end-side request message and the target-level interface message, verify the matching relationship between the message direction and the access level, associate the session token identifier and the port access identifier, and generate a direction-level association key. S103: Based on the direction level association key, determine the correspondence between field semantic labels, message direction and access level, merge the port access identifier under the same session token identifier with the target level interface message, and establish an interface channel index.

6. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The specific steps of S2 are as follows: S201: Based on the interface channel index, retrieve the interface number, port access identifier and field slot number within the edge gateway access channel, merge the field slot numbers according to the channel number, filter the target field slot, and generate a channel slot correspondence table. S202: Based on the channel slot correspondence table, compare the consistency of the field semantics with the target field slot semantics label, determine the required flag value and access permission identifier level, associate the slot number with the permission level, and obtain the slot landing point identifier table. S203: Based on the slot landing point identifier table, map the routing relationship between the target field slot, field semantics, required field flag and access permission flag, merge the slot landing points according to the interface number, and establish a field slot routing list.

7. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The specific steps for S3 are as follows: S301: Based on the field slot routing list, compare the interface numbers of the regional business server access channel and the cloud management platform access channel, verify the occupancy status of the field slot number in the two types of channels, map the migration position according to the channel number, and generate a channel migration position table. S302: Based on the channel migration location table, compare the token version identifier value and the scope identifier value, determine the version change relationship and scope inheritance relationship under the same session token identifier, associate the migration location and field slot number, and obtain the token scope switching table; S303: Based on the token scope switching table, determine the slot occupancy status for the field occupancy identifier, map the breakpoint relationship between the token version identifier, scope identifier, field occupancy identifier and switching position, and establish a session migration breakpoint record.

8. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The specific steps of S4 are as follows: S401: Based on the session migration breakpoint record, verify the cross-level message call channel breakpoint number, field slot number and message direction, map path nodes according to the matching relationship between the field transfer-out end and the transfer-in end, and generate a field transfer path table; S402: Based on the field transfer path table, compare the access permission identifier level with the business process node order, determine the missing field identifier's placeholder status in the path node, associate the access permission level, process node, and field slot number to obtain the path selection identifier table. S403: Select an identifier table based on the path, merge path nodes under the same session token identifier for the field transfer path table, map access permission identifier, business process node, missing field identifier and transfer path, and establish a message passage token.

9. The intelligent adaptation method for cross-level information interaction according to claim 1, characterized in that, The specific steps of S5 are as follows: S501: Based on the message access token, parse the session token identifier, transfer path and access permission identifier, compare the cross-level sending channel protocol route and transfer path nodes, adjust the protocol route according to the node order, and generate a protocol route matching table; S502: According to the protocol routing matching table, call the transport layer and message exit identifier, compare the path node layer sequence number with the exit number, associate the protocol route, transport layer and message exit identifier, and obtain the exit layer mapping table; S503: Based on the export level mapping table, and according to the target slot and frame header identifier, verify the correspondence between the slot number and the export number, map the frame header identifier, protocol route and transmission level, and establish a cross-level adaptation communication scheme.

10. A cross-level information interaction intelligent adaptation system, characterized in that, The system is used to implement the intelligent adaptation method for cross-level information interaction as described in any one of claims 1-9, comprising: The interface channel index building module is used to implement: S1: Based on the edge gateway protocol stack, obtain the end-side request message, the target layer interface message, the session token identifier, compare the field semantics, message direction and access layer, and build the interface channel index; The field slot routing list creation module is used to implement: S2: Based on the interface channel index, filter the target field slots of the edge gateway access channel, determine the slot landing point according to the field adaptation constraint identifier, and create a field slot routing list; The session migration breakpoint recording module is used to implement: S3: Based on the field slot routing list, determine the cross-level session migration location, mark the switching location according to the token adaptation identifier, and establish a session migration breakpoint record; The message access token generation module is used to implement: S4: Based on the session migration breakpoint record, determine the message field transfer path in the cross-level call channel, select the transfer path according to the access permissions, missing field identifiers and business process nodes, and establish a message access token; The cross-level transmission channel adaptation module is used to implement: S5: Based on the message access token, adjust the cross-level transmission channel, write the target slot and frame header identifier, and generate a cross-level adaptation communication scheme.

Images