M2M Encryption Bypass for URLLC Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M communication systems face challenges in maintaining low latency and high security simultaneously, especially in URLLC applications, as traditional security measures like encryption increase latency and impact reliability.
Innovation Solution
Establishing a hardware-based trust relationship between machine controllers and devices through key pairs and certificates of authority, allowing for encryption-bypassed communication in mission-critical data sessions while maintaining encryption for non-critical data, utilizing ultra-reliable low latency communications (URLLC) network slices for bypassed channels and enhanced mobile broadband (eMBB) or massive IoT (MIoT) slices for encrypted channels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If encryption is used to secure M2M communication, then security and confidentiality are improved, but network latency increases and reliability deteriorates
Solution Approach 1:
The patent segments communication data into two categories: mission-critical data and non-mission-critical data. Mission-critical data is transmitted through an encryption-bypassed low-latency channel, while non-mission-critical data uses encrypted channels. This segmentation allows the system to achieve low latency for critical communications without compromising overall security, as the most time-sensitive data does not require encryption processing.
Solution Approach 2:
The patent applies different security measures to different data streams based on their specific requirements. Mission-critical control data receives minimal security processing (authentication only) to maintain ultra-low latency, while non-critical data receives full encryption. This local differentiation of security quality allows the system to optimize latency where it matters most while maintaining adequate security elsewhere.
2Loss of information
If encryption is applied to all data sessions, then confidentiality is maintained, but communication speed and latency performance deteriorate
Solution Approach 1:
The patent divides data traffic into mission-critical and non-mission-critical segments. Only non-mission-critical data undergoes encryption processing, while mission-critical data is transmitted in plaintext after authentication. This segmentation preserves confidentiality for less time-sensitive data while maintaining high speed for critical control commands.
Solution Approach 2:
Instead of applying full encryption to all data, the patent applies encryption partially only to non-mission-critical data. This partial action approach maintains adequate confidentiality protection while avoiding the performance penalty of encrypting every byte of traffic, especially time-sensitive control data.
3Reliability
If traditional security measures are implemented, then authentication and confidentiality are ensured, but latency increases impacting URLLC performance
Solution Approach 1:
The patent performs authentication and trust relationship establishment as preliminary actions during device boot-up or connection initialization. Once authenticated, the devices can communicate through the encryption-bypassed low-latency channel without repeated security processing. This preliminary action approach ensures security is established upfront while enabling ultra-low latency communication thereafter.
Solution Approach 2:
The patent extracts the encryption step from the mission-critical communication path while retaining authentication. By removing only the encryption/decryption operations from the critical data flow (while keeping authentication intact), the system achieves ultra-low latency for control commands while maintaining basic security through trusted device pairing.
Data Source
AI summary
The disclosed technology provides systems and methods for accelerating communication for low latency, high reliability, and secure machine control systems through encryption bypass. Machine controllers, e.g., drone, robot, or autonomous-vehicle controllers, establish a hardware-based trust relationship with the controlled machines allowing for the communication of unencrypted low-latency control and data messages, for example, via ultra-reliable low latency (URLLC) cellular network slices. The machines can relay non-mission-critical communications via encrypted communication using different network slices. The machines can also use distributed ledgers to store and access events and records used to create and/or maintain the trust relationship, and archive data for subsequent use.