Low-Complexity Wireless Device Authentication via Edge Enabler Clients
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in supporting diverse device complexities and capabilities, particularly in authentication between user equipment (UE) and edge computing servers, with wearable devices and low-cost, low-complexity devices experiencing limited communication capabilities.
Innovation Solution
A method involving a user equipment (UE) performs bootstrapping procedures with edge servers to generate authentication codes for registration, utilizing a bootstrapping server function (BSF) to verify these codes and establish secure communication with edge enabler clients (EECs) and servers, enabling authentication and discovery of additional edge servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional authentication methods are used in wireless communication systems, then security can be maintained for standard devices, but wearable and low-complexity devices experience limited communication capabilities and cannot establish secure connections with edge servers
Solution Approach 1:
The authentication process is segmented into multiple components: bootstrapping phase (establishing initial security context), application phase (generating service-specific authentication codes), and discovery phase (finding edge servers). This segmentation allows different device types to participate in authentication at appropriate complexity levels while maintaining overall security through the structured multi-phase approach
Solution Approach 2:
The Edge Enabler Client (EEC) acts as an intermediary between the wireless device and edge servers, managing authentication codes and facilitating secure communication. The EEC receives authentication codes from the bootstrapping server and uses them to establish secure connections with edge servers, enabling devices with limited capabilities to authenticate securely through this intermediary component
2Reliability
If comprehensive authentication protocols are implemented to support all device types, then security is maintained, but device complexity and processing requirements increase
Solution Approach 1:
Security context and cryptographic materials are established in advance during the bootstrapping phase, before actual application authentication is needed. The bootstrapping server pre-generates authentication codes and distributes them to the EEC, so that during application phase, devices with limited capabilities only need to use pre-computed values rather than performing complex cryptographic operations in real-time
Solution Approach 2:
The system supports multiple authentication code formats and types (e.g., different key derivation parameters, various authentication code structures) that can be selected based on device capabilities. Low-complexity devices can use simplified authentication parameters while more capable devices can utilize more secure but computationally intensive parameters, allowing the system to adapt the authentication complexity to match device capabilities
3Device complexity
If simplified authentication procedures are used to reduce device complexity, then wearable and low-complexity devices can connect, but security verification and authentication reliability are compromised
Solution Approach 1:
The system moves part of the authentication complexity from the device dimension to the network dimension. Instead of requiring complex cryptographic processing at the device, the authentication verification is performed by the bootstrapping server and EEC in the network, which have sufficient processing capabilities. This dimensional shift allows simple devices to participate in secure authentication without burdening them with complex verification operations
Data Source
AI summary
This disclosure relates to techniques for performing wireless communications including authentication between user equipment and edge computing servers. One or more edge enabler client(s) operating at a user equipment may authenticate with one or more edge computing server(s). The authentication may use generic bootstrapping architecture, among various possibilities.