A method for low-latency encrypted information transmission in the Internet of Things with edge computing collaboration

By dynamically calculating risk enhancement values ​​and employing a two-layer encryption mechanism, combined with smooth resource scheduling and node health screening, the system addresses the comprehensive requirements of low latency, high reliability, and high security in edge computing collaborative IoT systems, achieving stability and security assurance in high-risk environments.

CN123122856APending Publication Date: 2026-11-17XIAN PAVOR TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610945563.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-29
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies in edge computing collaborative IoT systems struggle to simultaneously meet the combined requirements of low latency, high reliability, and high security. In particular, they are prone to creating security-weakened channels in high-concurrency and high-intensity adversarial environments, and also suffer from issues such as dynamic changes in node health status and limited computing resources.

Method used

By acquiring business type identifiers, device trustworthiness scores, and historical abnormal behavior scores, the risk enhancement value is dynamically calculated, a session symmetric key is generated and jointly encrypted with a pre-burned static link root key, and combined with smooth resource scheduling and node health screening, the signature threshold is dynamically calculated to establish a non-degradable security level and a minimum guaranteed resource pool, thereby preventing attacks and optimizing resource allocation.

Benefits of technology

It achieves high encryption strength and resource stability in high-risk environments, prevents attackers from faking congestion to induce degradation, blocks man-in-the-middle attacks, ensures the authenticity and reliability of critical data, avoids system crashes, and guarantees the stability and security of distributed systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123122856A_ABST
    Figure CN123122856A_ABST
Patent Text Reader

Abstract

This invention relates to the field of data security and proposes a low-latency encrypted information transmission method for IoT in edge computing collaboration. The method includes determining the final execution security level by combining service type and risk enhancement value to ensure security is no less than the basic requirements. An inner encapsulation packet is generated using a joint encryption mechanism of session key and static root key to ensure data transmission confidentiality. During network congestion, elastic resource allocation is dynamically adjusted based on anti-surge triggering conditions and smoothing coefficients to achieve differentiated scheduling for lossless protection of high-level services and adaptive compression of low-level services. The receiving end filters the valid set based on node health, dynamically calculates the signature threshold, and generates an aggregate signature; if there are insufficient valid nodes, a maintenance mode is triggered; otherwise, the status is committed. This method effectively solves the challenges of low latency, high reliability, and secure collaboration in high-concurrency transmission in IoT edge scenarios through dynamic security grading, dual encryption, and smooth resource scheduling.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of data security technology, and more specifically, to a method for low-latency encrypted information transmission in the Internet of Things (IoT) with edge computing collaboration. Background Technology

[0002] With the widespread application of IoT systems in smart manufacturing, connected vehicles, energy dispatching, and urban infrastructure, the number of terminal devices is growing exponentially, and massive amounts of data are aggregated, processed, and forwarded through edge nodes. In this type of edge computing collaborative architecture, it is necessary to ensure the security and integrity of data transmission while also meeting the real-time requirements of low latency and high concurrency, resulting in a highly coupled relationship between security mechanisms and scheduling mechanisms.

[0003] In existing technology cases, a fixed security level is usually preset according to the business type, and resource allocation and security policy adjustment are made in combination with the current network load status. When network congestion or increased link pressure is detected, the encryption process is often dynamically compressed, the proportion of redundant verification is reduced, or the number of nodes participating in signing is reduced to improve throughput efficiency in order to ensure real-time performance. This load-aware security adaptive mechanism has a certain engineering rationality in normal environment, but it has obvious hidden dangers in adversarial scenarios.

[0004] Especially in real-world operating environments, network conditions are not absolutely reliable. Attackers can manipulate network conditions by injecting abnormal traffic, creating false congestion, amplifying link latency, or interfering with node communication quality to fabricate the appearance of resource strain or performance degradation. This can induce the system to trigger security policy adjustment mechanisms. When there is no non-degradable constraint between security level and network condition, high-risk situations often present the risk of actively reducing encryption strength or signature thresholds, leading to a decrease in overall security density and creating exploitable attack windows. Such attacks do not require cracking the cryptographic algorithm itself but rather manipulate environmental variables, making them highly covert and difficult to detect in a timely manner.

[0005] On the other hand, during the collaborative process of distributed edge nodes, the health status of nodes has dynamic characteristics. Existing multi-node signature or consistency mechanisms mostly adopt fixed threshold models, which do not fully consider the real-time reliability fluctuations of nodes. When some nodes are incorrectly judged as unavailable due to network interference or abnormal behavior, the signature threshold is automatically lowered when the number of effective nodes decreases, or write failures still occur due to unreasonable threshold configuration when there are enough nodes, which in turn leads to state splitting or consistency risks. In the absence of absolute security lower limit control, erroneous state commits may still occur in extreme scenarios, affecting the stability of the global system.

[0006] Furthermore, IoT terminal devices have limited computing resources and often use session symmetric keys for data encryption. If only single-layer session encryption is relied upon, the session key is at risk of being intercepted or replayed during edge link transmission if the communication link is subjected to eavesdropping or man-in-the-middle interference. On the other hand, using a high-strength public-key mechanism would increase computational burden, handshake latency, and power consumption, hindering the continuous operation of large-scale low-power devices. Therefore, improving link key protection capabilities under lightweight conditions is a significant challenge facing current technologies.

[0007] In summary, under high concurrency and high-intensity adversarial environments, the above-mentioned problems overlap and can easily lead to a security weakening channel under the guise of performance, making it difficult to simultaneously meet the comprehensive requirements of low latency, high reliability, and high security.

[0008] Therefore, there is an urgent need for a low-latency encrypted information transmission method for IoT in collaboration with edge computing, in order to solve the technical problem that existing technologies cannot simultaneously meet the comprehensive requirements of low latency, high reliability and high security when faced with a weakened security channel. Summary of the Invention

[0009] In view of this, the present invention proposes a low-latency encrypted information transmission method for IoT with edge computing collaboration, which aims to solve the technical problem in the prior art that it is difficult to meet the comprehensive requirements of low latency, high reliability and high security when facing a weakened security channel.

[0010] This invention discloses a method for low-latency encrypted information transmission in the Internet of Things (IoT) with edge computing collaboration, comprising:

[0011] Step S1: Obtain the business type identifier of the data to be processed and map it to obtain the basic security level; collect the data value coefficient, device trust score and historical abnormal behavior score, and calculate the risk enhancement value; based on the basic security level and the risk enhancement value, determine the final execution security level by taking the larger value, wherein the final execution security level is not lower than the basic security level;

[0012] Step S2: Generate a session symmetric key, encrypt the original data using the session symmetric key to obtain ciphertext; use the pre-programmed static link root key to jointly encrypt the ciphertext and the session symmetric key to generate an inner encapsulation packet;

[0013] Step S3: Based on the final execution security level, query the corresponding minimum guaranteed resource quota; if network congestion is detected, determine whether the preset anti-surge triggering condition is met. If the preset anti-surge triggering condition is met, dynamically adjust the elastic resource allocation based on the smoothing coefficient to obtain the total amount of available resources at instant, and queue and send data according to this total amount.

[0014] Step S4: The receiving node group decrypts and verifies the inner encapsulation packet, and filters the effective node set based on the real-time health score of each node; according to the number of effective nodes and combined with the absolute security lower limit constant, the final signature threshold is dynamically calculated; if the number of effective nodes is lower than the absolute security lower limit constant, the system maintenance mode is triggered and writing is rejected; otherwise, when the number of collected signatures reaches the final signature threshold, an aggregate signature is generated and a status commit packet is broadcast.

[0015] Preferably, in step S1, obtaining the service type identifier of the data to be processed and mapping it to the basic security level includes:

[0016] Define data type collection and mapping function The formula is:

[0017] ;

[0018] in, This represents the basic security level, where the value belongs to the set. Integers; This represents the service type identifier for the data packet, and is an enumerated value.

[0019] Preferably, in step S1, the formula for calculating the risk enhancement value is:

[0020] ;

[0021] in, Indicates risk score; This represents the data value coefficient, with a value range of [value range missing]. Floating-point numbers between; This indicates the device's current credibility score, with a value range of [value range missing]. Floating-point numbers between; This represents the normalized score for historical anomalous behavior, with values ​​ranging from... Floating-point numbers between; For the preset weighting coefficients, and .

[0022] Preferably, in step S1, the final execution security level is determined by taking the largest value and calculated using the following formula:

[0023] ;

[0024] in, This indicates the final execution security level, where the value belongs to the set. Integers; This represents the floor function; used for enforcing constraints. This is to prevent attacks that could downgrade the security level.

[0025] Preferably, in step S2, the data ciphertext is jointly encrypted with the session symmetric key to generate an inner encapsulation packet, including:

[0026] Call the hardware-secure random number generator The session symmetric key in bit string form is generated using the following formula. ,include:

[0027] ;

[0028] The encrypted data payload is obtained using the AES encryption algorithm and the following formula. ,include: ;

[0029] in, For the encrypted data payload, This is the original plaintext data;

[0030] Obtain the factory-pre-programmed static link root key The inner encapsulation package is generated using the following formula. ,include:

[0031] ;

[0032] in, Shared only between end-side devices and edge nodes for protection Confidentiality during local area network transmission, in addition, Instead of being dynamically distributed over the network, it adopts an offline pre-configuration mechanism, transmitting data via a secure channel before the IoT edge node leaves the factory. Write to the secure chip or trusted execution environment's storage area of ​​the node.

[0033] Preferably, in step S3, the total resource capacity is defined by the following formula. ,include:

[0034] ;

[0035] in, To ensure real-time resource pooling; To enhance the elasticity of the resource pool;

[0036] For the final execution security level The index value of the obtained security level , its in Instantaneous available resources at any given moment It is obtained by calculation using the following formula:

[0037] ;

[0038] in, Indicates level The minimum guaranteed quota, from It is allocated in the middle, cannot be preempted, and satisfies the following conditions: ≥ ≥ ;

[0039] Indicates level exist The amount of elastic resources allocated at any given time, from The system is allocated according to security level, and in resource contention scenarios, higher-level security is guaranteed based on security level. Not to be reduced;

[0040] Calculate the theoretical elastic resource demand at time t under each security level. It is obtained by calculation using the following formula:

[0041] ;

[0042] The formula logic is that when relying solely on the minimum guaranteed quota Unable to be at the target time Internal clearing backlog The difference is the required elastic resources.

[0043] Preferably, in step S3, the judgment logic for the anti-vibration trigger condition is determined through a resource reallocation trigger condition function. Implementation, including:

[0044] ;

[0045] in, Indicates the backlog depth of higher-level queues; Indicates the duration of high load; This indicates the high-demand hold-up time threshold, used to identify backlog situations at the third security level; This represents the resource utilization threshold for low-level queues. This indicates the reserved buffer threshold. It is a low-level reserved buffer used for smooth elastic scheduling, preventing resources from being frequently preempted by high-level resources, thereby suppressing jitter and short-term fluctuations, and used to judge the situation of idle waste in the first safety level;

[0046] When network congestion is detected and triggered At that time, perform smooth preemption of resources, making available resources available momentarily available. Updated to ,include:

[0047] ;

[0048] in, ; This is the smoothing coefficient corresponding to security level i, used to suppress severe fluctuations in resource allocation; Let be the amount of elastic resources at time t; For target elastic resource increment;

[0049] Furthermore, the target elastic resource increment The following set of differential constraints must be satisfied. :

[0050]

[0051] in, A larger value indicates a more stable resource allocation. This is a dynamic compression coefficient, determined by the total resource water level; the more scarce the resources, the lower the compression coefficient. The smaller; This is the medium-level adjustment coefficient, falling between the high and low levels.

[0052] Preferably, in step S4, the set of valid nodes The selection criteria are:

[0053]

[0054] in, Indicates the first One edge node; Represents a node Health score; This indicates the health threshold.

[0055] Number of valid nodes Defined as a set The cardinality, i.e. .

[0056] Preferably, the final signature threshold The calculation formula is:

[0057] ;

[0058] in, This represents the floor function; The lower safety limit constant; the circuit breaker logic is... Force switch to maintenance mode Reject any new write requests;

[0059] Based on the above And health score, for the device Select a fixed verification node group ,include:

[0060] ;

[0061] In the time window The internal members remain unchanged.

[0062] Preferably, in step S4, the status submission packet The structure is defined as follows:

[0063]

[0064] in, Indicates the current logical clock epoch generated based on Lamport Clock; Hash The hash value representing the global state machine; Indicates by at least The aggregate signature generated by each node.

[0065] This invention, by locking in the security baseline, building encryption depth, ensuring resource resilience, and safeguarding the consensus gate, has the core advantage of robustness and immutability in adversarial environments.

[0066] Step S1 establishes a non-degradable security baseline, using a maximum-value operation to force the final security level to be no lower than the base level, effectively defending against attackers' attempts to induce downgrade attacks by faking congestion and deceiving the system into reducing encryption strength. Simultaneously, based on historical anomaly scores, devices with past anomaly records are subject to high-level monitoring to prevent latent spoofing attacks, ensuring that critical smart grid commands maintain the highest encryption strength under all operating conditions. Step S2 employs a two-layer encapsulation of session keys and root keys; pre-programmed static root keys protect dynamic session keys, building a defense-in-depth defense. Even if the session key is cracked or replayed, attackers cannot forge legitimate data packets due to the lack of the root key, effectively blocking man-in-the-middle attacks and illegal injections, ensuring the authenticity of emergency signals in open environments such as vehicle networks. Step S3 establishes a minimum guaranteed resource pool to resist resource-exhaustion-type DDoS attacks, ensuring no packet loss of high-priority data. A smoothing coefficient is introduced to filter traffic fluctuations, preventing attackers from triggering frequent system reconfigurations through periodic small peaks, thus preventing resource jitter and crashes and ensuring the real-time performance of industrial internet control signals. Step S4 filters the effective set based on node health and sets an absolute security lower limit. When there are insufficient healthy nodes, maintenance mode is triggered directly to refuse writes, rather than forcing consensus. This effectively defends against Byzantine faults and node spoofing attacks, preventing distributed energy storage and other systems from generating erroneous global states when nodes are damaged. Attached Figure Description

[0067] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0068] Figure 1 A flowchart of an IoT low-latency encrypted information transmission method for edge computing collaboration provided in an embodiment of the present invention;

[0069] Figure 2 This is a schematic diagram illustrating the security level classification of the edge computing collaborative IoT low-latency encrypted information transmission method provided in an embodiment of the present invention.

[0070] Figure 3 This is a technical architecture diagram of the edge computing collaborative IoT low-latency encrypted information transmission method provided in an embodiment of the present invention. Detailed Implementation

[0071] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the disclosure to those skilled in the art. It should be noted that, unless otherwise specified, embodiments and features in the embodiments of the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0072] See Figure 1 As shown, this embodiment discloses a method for low-latency encrypted information transmission in the Internet of Things (IoT) with edge computing collaboration, including:

[0073] Step S1: Obtain the business type identifier of the data to be processed and map it to obtain the basic security level; collect the data value coefficient, device trust score and historical abnormal behavior score, and calculate the risk enhancement value; based on the basic security level and the risk enhancement value, determine the final execution security level by taking the larger value, wherein the final execution security level is not lower than the basic security level;

[0074] Step S2: Generate a session symmetric key, use the session symmetric key to encrypt the original data to obtain the data ciphertext; use the pre-programmed static link root key to jointly encrypt the data ciphertext and the session symmetric key to generate the inner encapsulation packet;

[0075] Step S3: Based on the final execution security level, query the corresponding minimum guaranteed resource quota; if network congestion is detected, determine whether the preset anti-surge triggering conditions are met. If the preset anti-surge triggering conditions are met, dynamically adjust the elastic resource allocation based on the smoothing coefficient to obtain the total amount of available resources at instant, and queue and send data according to this total amount.

[0076] Step S4: The receiving node group decrypts and verifies the inner encapsulation packet, and filters the set of valid nodes based on the real-time health score of each node; based on the number of valid nodes and the absolute security lower limit constant, the final signature threshold is dynamically calculated; if the number of valid nodes is lower than the absolute security lower limit constant, the system maintenance mode is triggered and writing is rejected; otherwise, when the number of collected signatures reaches the final signature threshold, an aggregate signature is generated and a status commit packet is broadcast.

[0077] Understandably, by dynamically calculating risks based on data value and historical device behavior, and using a maximum-rate operation to forcibly lock in a security minimum, this mechanism effectively defends against induced degradation attacks where attackers fabricate network congestion to trick the system into lowering encryption strength. It also utilizes the memory of historical scores to prevent long-term, spoofing attacks. Combined with a two-layer encapsulation technology using session keys and root keys, the solution achieves dynamic key isolation and integrity protection, effectively blocking man-in-the-middle attacks, key replay, and side-channel analysis, ensuring that critical instructions such as those from the smart grid maintain the highest encryption strength and authenticity under any operating condition. Furthermore, at the resource scheduling and transmission assurance level, a smooth resource scheduling strategy to prevent oscillations is implemented, creating an emergency lane for high-security services. In the face of DDoS attacks aimed at exhausting system resources, a minimum guaranteed resource pool ensures that critical data has dedicated bandwidth, preventing it from being overwhelmed by massive amounts of junk traffic. Simultaneously, the introduction of a smoothing coefficient and anti-oscillation trigger conditions filters out interference created by attackers through periodic small traffic peaks, preventing system crashes due to frequent reconfigurations.

[0078] In step S1 of the embodiments of this application, the service type identifier of the data to be processed is obtained, and the basic security level is mapped to it, including:

[0079] Define data type collection and mapping function The formula is:

[0080] ;

[0081] in, This represents the basic security level, where the value belongs to the set. Integers; This represents the service type identifier for the data packet, and is an enumerated value.

[0082] Specifically, It's included in the data packet and is used to identify the type of data. For example, control commands, video streams, log data, or ordinary sensor readings. It is a preset rule table, indicating that each type of data corresponds to a basic security level.

[0083] In step S1 of the embodiments of this application, the formula for calculating the risk enhancement value is as follows:

[0084] ;

[0085] in, Indicates risk score; This represents the data value coefficient, with a value range of [value range missing]. Floating-point numbers between; This indicates the device's current credibility score, with a value range of [value range missing]. Floating-point numbers between; This represents the normalized score for historical anomalous behavior, with values ​​ranging from... Floating-point numbers between; For the preset weighting coefficients, and .

[0086] Specifically, Risk scores are used to assess the level of danger in the current environment and on equipment, allowing for dynamic adjustments to security strategies; seemingly normal equipment may suddenly be compromised by hackers; through calculation... It can sense the trustworthiness of the device. The decline or The system considers historical blemishes; the weighting coefficients allow administrators to flexibly configure the emphasis according to the actual scenario. By introducing configurable weighting coefficients α, β, and γ, the risk assessment model can be flexibly adapted. These three coefficients correspond to data value, current device trustworthiness, and historical abnormal behavior, respectively. For example, in financial payment scenarios, fund security is the primary consideration, so the data value weight α should be increased. In this case, regardless of the device status, high-value data such as transaction keys will be forcibly elevated to the highest security level to ensure the security of the data itself. In industrial control systems, the stable operation of physical equipment is crucial, so the current device trustworthiness weight β should be increased, and the historical behavior weight γ should be appropriately increased. This configuration can smoothly handle occasional environmental interference, and combined with the device's historical reputation, avoid production line shutdowns due to misjudgment. In IoT smart home scenarios, the number of devices is large and computing resources are limited, so the historical behavior weight γ should be increased. Even ordinary data such as temperature and humidity, which have low value, will be identified and isolated if devices have been abnormal for a long time, thus effectively preventing botnet attacks. By flexibly configuring these three weights, the system can achieve optimal security protection in different scenarios.

[0087] See Figure 2 As shown, in step S1 of the embodiment of this application, the final execution security level is determined by taking the largest value and calculated using the following formula:

[0088] ;

[0089] in, This indicates the final execution security level, where the value belongs to the set. Integers; This represents the floor function; used for enforcing constraints. This is to prevent attacks that could downgrade the security level.

[0090] Understandably, by employing the maximum value logic, this formula ensures that the security level can only be increased, not decreased; this is to defend against induced downgrade attacks—no matter how attackers fabricate network congestion, as long as the risk value remains unchanged... As long as it exists, the security level will not drop.

[0091] In step S2 of the embodiments of this application, the data ciphertext is jointly encrypted with the session symmetric key to generate an inner encapsulation packet, including:

[0092] Call the hardware-secure random number generator The session symmetric key in bit string form is generated using the following formula. ,include:

[0093] ;

[0094] The encrypted data payload is obtained using the AES encryption algorithm and the following formula. ,include: ;

[0095] in, For the encrypted data payload, This is the original plaintext data;

[0096] Obtain the factory-pre-programmed static link root key The inner encapsulation package is generated using the following formula. ,include:

[0097] ;

[0098] in, Shared only between end-side devices and edge nodes for protection Confidentiality during local area network transmission, in addition, Instead of being dynamically distributed over the network, it adopts an offline pre-configuration mechanism, transmitting data via a secure channel before the IoT edge node leaves the factory. Write to the secure chip or trusted execution environment's storage area of ​​the node.

[0099] Specifically, in this embodiment, an annual review is conducted to adjust the application of this packaging package, and the review timeline is adjusted accordingly. If the value exceeds a preset threshold, the dual-layer encapsulation mechanism of this embodiment must be used. Furthermore, annual evaluation is required. If the changes show If the trend is upward, then the rotation frequency of the session symmetric key should be adjusted.

[0100] See Figure 3 As shown, in step S3 of the embodiment of this application, the total resource capacity is defined by the following formula. ,include:

[0101] ;

[0102] in, To ensure real-time resource pooling; To enhance the elasticity of the resource pool;

[0103] For the final execution security level The index value of the obtained security level , its in Instantaneous available resources at any given moment It is obtained by calculation using the following formula:

[0104] ;

[0105] in, Indicates level The minimum guaranteed quota, from It is allocated in the middle, cannot be preempted, and satisfies the following conditions: ≥ ≥ ;

[0106] Indicates level exist The amount of elastic resources allocated at any given time, from The system is allocated according to security level, and in resource contention scenarios, higher-level security is guaranteed based on security level. Not to be reduced;

[0107] Calculate the theoretical elastic resource demand at time t under each security level. It is obtained by calculation using the following formula:

[0108] ;

[0109] The formula logic is that when relying solely on the minimum guaranteed quota Unable to be at the target time Internal clearing backlog The difference is the required elastic resources.

[0110] Understandably, different security levels have different minimum guarantee quotas. Even when resources are scarce, high-level services can ensure sufficient backup resources to operate without being affected by sudden traffic surges in low-level tasks. When traffic surges, the system automatically calculates and allocates resources from the elastic enhancement resource pool to cope with sudden DDoS attacks or business peaks. The elastic resource pool may be idle during use, but this is not wasteful; rather, it represents a strategic reserve for the encryption security system. It ensures that during DDoS attacks or high loads, there is still sufficient computing power to maintain high-strength encryption and key negotiation, guaranteeing the availability and low latency of high-security-level services. This reservation is essentially a necessary cost paid for service continuity and attack resistance.

[0111] In step S3 of the embodiments of this application, the judgment logic for the anti-vibration trigger condition is determined through the resource reallocation trigger condition function. Implementation, including:

[0112] ;

[0113] in, Indicates the backlog depth of higher-level queues; Indicates the duration of high load; This indicates the high-demand hold-up time threshold, used to identify backlog situations at the third security level; This represents the resource utilization threshold for low-level queues. This indicates the reserved buffer threshold. It is a low-level reserved buffer used for smooth elastic scheduling, preventing resources from being frequently preempted by high-level resources, thereby suppressing jitter and short-term fluctuations, and used to judge the situation of idle waste in the first safety level;

[0114] When network congestion is detected and triggered At that time, perform smooth preemption of resources, making available resources available momentarily available. Updated to ,include:

[0115] ;

[0116] in, ; This is the smoothing coefficient corresponding to security level i, used to suppress severe fluctuations in resource allocation; Let be the amount of elastic resources at time t; For target elastic resource increment;

[0117] Furthermore, the target elastic resource increment The following set of differential constraints must be satisfied. :

[0118]

[0119] in, A larger value indicates a more stable resource allocation. This is a dynamic compression coefficient, determined by the total resource water level; the more scarce the resources, the lower the compression coefficient. The smaller; This is the medium-level adjustment coefficient, falling between the high and low levels.

[0120] Specifically, in this embodiment, a dual-condition approach is used to determine whether there is true congestion. Resource adjustments are only triggered when high-level tasks are backlogged for a long period of time, or when low-level resources are very idle, to prevent misjudgments due to instantaneous fluctuations. A smoothing coefficient is used to gradually adjust resource allocation to avoid sudden changes in resource volume and ensure stable operation. In addition, hard constraints are set, such as prioritizing high-level services and dynamically adjusting target resource volume, to ensure orderly and safe resource allocation.

[0121] It is understood that this embodiment combines dynamic resource scheduling with security level assurance to solve the problems of rigid resource allocation, delayed response, and insufficient security isolation in the prior art; through anti-vibration triggering, smooth updates, differentiated constraints, and dynamic compression, it maximizes resource utilization while ensuring the stability of high-level services.

[0122] In the embodiments of this application, in step S4, the set of valid nodes... The selection criteria are:

[0123]

[0124] in, Indicates the first One edge node; Represents a node Health score; This indicates the health threshold.

[0125] Number of valid nodes Defined as a set The cardinality, i.e. .

[0126] Specifically, Represents a node The health score is the health status indicator of the k-th node itself. It is calculated by the system based on real-time data such as the node's resource utilization, response latency, and error rate. It reflects the current operating quality of the node and is an existing technology, which will not be elaborated on in this embodiment. This represents the health threshold, a preset threshold value used to distinguish between healthy and unhealthy nodes.

[0127] In the embodiments of this application, the final signature threshold The calculation formula is:

[0128] ;

[0129] in, This represents the floor function; The lower safety limit constant; the circuit breaker logic is... Force switch to maintenance mode Reject any new write requests;

[0130] based on And health score, for the device Select a fixed verification node group ,include:

[0131] ;

[0132] In the time window The internal members remain unchanged.

[0133] In the embodiments of this application, in step S4, the status submission packet The structure is defined as follows:

[0134]

[0135] in, Indicates the current logical clock epoch generated based on Lamport Clock; Hash The hash value representing the global state machine; Indicates by at least The aggregate signature generated by each node.

[0136] Understandably, by dynamically calculating signature thresholds to select healthy nodes to form a stable verification group, and utilizing the Lamport logical clock to ensure state consistency, a state commit packet containing the aggregate signature is ultimately generated, ensuring the security and stability of signatures in the distributed system. Among these, the maintenance mode... This is a common system protection mechanism in the industry and belongs to existing technology, so this embodiment will not elaborate further.

[0137] In summary, the technical embodiments of this example have the following technical effects:

[0138] At the security strategy level, this implementation achieves a non-downgradeable security level constraint. Traditional systems often passively reduce encryption strength to improve transmission efficiency due to network congestion or excessive load. This is easily exploited by attackers who can induce system downgrades by faking congestion, thereby enabling eavesdropping or tampering. This implementation innovatively introduces a risk enhancement mechanism that comprehensively assesses data value, device trustworthiness, and historical anomaly behavior, mandating that the final security level must not be lower than the basic business level. This means that regardless of how the external network environment deteriorates, high-risk services such as critical control commands always maintain the highest encryption strength. Simultaneously, the system possesses a memory-based risk perception capability. Even if an attacker-controlled device temporarily behaves normally, as long as it has a history of anomalies, the system will automatically upgrade its security verification level, effectively defending against latent attacks and attacks disguised as normal operations, thus locking in the bottom line of security.

[0139] At the resource scheduling level, this embodiment provides anti-oscillation resource smoothing capabilities. Faced with distributed denial-of-service attacks aimed at exhausting system resources, traditional one-size-fits-all scheduling methods often lead to the interruption of critical services due to bandwidth being saturated with junk traffic. This embodiment establishes a minimum guaranteed resource pool and an elastic resource pool, creating a dedicated emergency lane for high-security-level services. When network congestion is detected, the system prioritizes compressing the elastic resources of low-priority services, ensuring that critical alarms and control signaling have dedicated bandwidth and achieving zero packet loss transmission. Furthermore, to address resource jitter attacks where attackers trigger frequent system reconfiguration through periodic small traffic spikes, leading to system crashes, this embodiment introduces a smoothing coefficient and anti-oscillation trigger conditions to filter out instantaneous fluctuations and respond only to persistent congestion, greatly improving the system's operational stability under high-pressure loads.

[0140] At the collaborative verification level, the implementation establishes a trust system combining dynamic thresholds and a circuit breaker mechanism. Regarding node forgery, instead of relying on a fixed number of signatures, it filters the valid node set based on real-time health and dynamically calculates the signature threshold. More importantly, the implementation sets an absolute security lower limit; once the number of online healthy nodes falls below this threshold, the system will directly trigger maintenance mode and refuse to write, preferring to shut down rather than force consensus when security cannot be guaranteed. This mechanism effectively prevents attackers from forging the global state after controlling some nodes, avoiding the spread of erroneous data and ensuring the consistency of the distributed ledger or state machine.

[0141] Finally, in terms of encryption architecture, the two-layer encryption encapsulation provides a defense-in-depth effect. By encrypting data with session keys and encapsulating session keys with static root keys, dynamic key isolation is achieved. Even if a single session key is cracked, attackers, lacking the pre-programmed root key, are still unable to forge legitimate data packets or decrypt other sessions, effectively blocking man-in-the-middle attacks, key replay, and side-channel analysis.

[0142] In summary, this embodiment can ensure protection in real-world scenarios such as smart grids, vehicle-to-everything (V2X) networks, and industrial control, even under extreme conditions such as high-intensity network attacks, node damage, or malicious manipulation.

[0143] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0144] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0145] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0146] These computer program instructions can also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0147] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for low-latency encrypted information transmission in the Internet of Things (IoT) with edge computing collaboration, characterized in that, include: Step S1: Obtain the business type identifier of the data to be processed and map it to the basic security level; Collect data value coefficients, equipment credibility scores, and historical abnormal behavior scores to calculate risk enhancement values; Based on the basic security level and the risk enhancement value, the final execution security level is determined by taking the larger value, wherein the final execution security level is not lower than the basic security level; Step S2: Generate a session symmetric key, encrypt the original data using the session symmetric key to obtain ciphertext; use the pre-programmed static link root key to jointly encrypt the ciphertext and the session symmetric key to generate an inner encapsulation packet; Step S3: Based on the final execution security level, query the corresponding minimum guaranteed resource quota; If network congestion is detected, it is determined whether the preset anti-surge triggering conditions are met. If the preset anti-surge triggering conditions are met, the elastic resource allocation is dynamically adjusted based on the smoothing coefficient to obtain the total amount of available resources at the moment, and the data is queued and sent according to this total amount. Step S4: The receiving node group decrypts and verifies the inner encapsulation packet, and filters the effective node set based on the real-time health score of each node; according to the number of effective nodes, combined with the absolute security lower limit constant, the final signature threshold is dynamically calculated. If the number of valid nodes is lower than the absolute security lower limit constant, the system maintenance mode is triggered and writes are rejected; Otherwise, when the number of collected signatures reaches the final signature threshold, an aggregate signature is generated and a status commit packet is broadcast.

2. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 1, characterized in that, In step S1, the service type identifier of the data to be processed is obtained, and the basic security level is mapped to it, including: Define data type collection and mapping function The formula is: ; in, This represents the basic security level, where the value belongs to the set. Integers; This represents the service type identifier for the data packet, and is an enumerated value.

3. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 2, characterized in that, In step S1, the formula for calculating the risk enhancement value is: ; in, Indicates risk score; This represents the data value coefficient, with a value range of [value range missing]. Floating-point numbers between; This indicates the device's current credibility score, with a value range of [value range missing]. Floating-point numbers between; This represents the normalized score for historical anomalous behavior, with values ​​ranging from... Floating-point numbers between; For the preset weighting coefficients, and .

4. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 3, characterized in that, In step S1, the final execution security level is determined by taking the largest value and calculated using the following formula: ; in, This indicates the final execution security level, where the value belongs to the set. Integers; This represents the floor function; used for enforcing constraints. This is to prevent attacks that could downgrade the security level.

5. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 4, characterized in that, In step S2, the data ciphertext is jointly encrypted with the session symmetric key to generate an inner encapsulation packet, including: Call the hardware-secure random number generator The session symmetric key in bit string form is generated using the following formula. ,include: ; The encrypted data payload is obtained using the AES encryption algorithm and the following formula. ,include: ; in, For the encrypted data payload, This is the original plaintext data; Obtain the factory-pre-programmed static link root key The inner encapsulation package is generated using the following formula. ,include: ; in, Shared only between end-side devices and edge nodes, used for protection Confidentiality during local area network transmission, in addition, Instead of being dynamically distributed over the network, it adopts an offline pre-configuration mechanism, transmitting data via a secure channel before the IoT edge node leaves the factory. Write to the secure chip or trusted execution environment's storage area of ​​the node.

6. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 5, characterized in that, In step S3, the total resource capacity is defined by the following formula. ,include: ; in, To ensure real-time resource pooling; To enhance the elasticity of the resource pool; For the final execution security level The index value of the obtained security level , its in Instantaneous available resources at any given moment It is obtained by calculation using the following formula: ; in, Indicates level The minimum guaranteed quota, from The allocation is made in the middle and cannot be seized. ≤ ,also ≥ ≥ ; Indicates level exist The amount of elastic resources allocated at any given time, from The system is allocated according to security level, and in resource contention scenarios, higher-level security is guaranteed based on security level. Not to be reduced; Calculate the theoretical elastic resource demand at time t under each security level. It is obtained by calculation using the following formula: ; The formula logic is that when relying solely on the minimum guaranteed quota Unable to be at the target time Internal clearing backlog The difference is the required elastic resources.

7. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 6, characterized in that, In step S3, the judgment logic for the anti-vibration trigger condition is determined through the resource reallocation trigger condition function. Implementation, including: ; in, Indicates the backlog depth of the higher-level queue; Indicates the duration of high load; This indicates the high-demand hold-up time threshold, used to identify backlog situations at the third security level; This represents the resource utilization threshold for low-level queues. This indicates the reserved buffer threshold. It is a low-level reserved buffer used for smooth elastic scheduling, preventing resources from being frequently preempted by high-level resources, thereby suppressing jitter and short-term fluctuations, and used to judge the situation of idle waste in the first safety level; When network congestion is detected and triggered At that time, perform smooth preemption of resources, making available resources available momentarily available. Updated to ,include: ; in, ; This is the smoothing coefficient corresponding to security level i, used to suppress severe fluctuations in resource allocation; Let be the amount of elastic resources at time t; For target elastic resource increment; Furthermore, the target elastic resource increment The following set of differential constraints must be satisfied. : in, A larger value indicates a more stable resource allocation. This is a dynamic compression coefficient, determined by the total resource water level; the more scarce the resources, the lower the compression coefficient. The smaller; This is the medium-level adjustment coefficient, falling between the high and low levels.

8. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 7, characterized in that, In step S4, the set of valid nodes The selection criteria are: in, Indicates the first One edge node; Represents a node Health score; This indicates the health threshold. Number of valid nodes Defined as a set The cardinality, i.e. .

9. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 8, characterized in that, The final signature threshold The calculation formula is: ; in, This represents the floor function; The lower safety limit constant; the circuit breaker logic is... Force switch to maintenance mode Reject any new write requests; Based on the above And health score, for the device Select a fixed verification node group ,include: ; In the time window The internal members remain unchanged.

10. The edge computing collaborative IoT low-latency encrypted information transmission method according to claim 9, characterized in that, In step S4, the status submission packet The structure is defined as follows: in, Indicates the current logical clock epoch generated based on Lamport Clock; Hash The hash value representing the global state machine; Indicates by at least The aggregate signature generated by each node.