Non-IP D2D Communication via PDCP Encapsulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication technologies face inefficiencies in device-to-device communication, particularly in scenarios where Internet Protocol (IP) addressing is not feasible, such as in machine-to-machine communication or when data is too small, leading to unnecessary overhead and complexity.
Innovation Solution
The implementation of non-IP device-to-device (D2D) communication using packet data convergence protocol (PDCP)-based encapsulation, which eliminates the need for IP addressing by employing protocols like PC5 and Wireless Access in Vehicular Environments (WAVE), allowing secure data transfer through layer-2 IDs and identity-based cryptography, reducing the complexity and overhead associated with IP-based communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP-based communication is used for device-to-device communication, then communication reliability is improved, but communication overhead and complexity increase
Solution Approach 1:
The patent extracts and removes the IP addressing layer from the communication stack, implementing direct layer-2 communication between devices. This eliminates IP header overhead and simplifies the protocol stack while maintaining communication reliability through direct MAC-address-based forwarding in the data plane.
Solution Approach 2:
The patent segments the control plane and data plane operations, using IP-based routing only for control signaling (plane establishment, tear-down, management) while implementing efficient layer-2 direct forwarding for actual data transmission. This segmentation allows reliable control communication while optimizing data plane efficiency.
2Measurement precision
If IP addressing is used in machine-to-machine communication, then device identification is improved, but implementation cost and overhead increase
Solution Approach 1:
The patent removes IP addressing requirements from machine-to-machine communication scenarios, using only layer-2 MAC addresses for device identification and communication. This extraction eliminates the need for IP address allocation, routing tables, and associated processing, significantly reducing implementation cost and overhead while maintaining precise device identification through MAC addresses.
3Productivity
If small data packets are transmitted using IP protocol, then data transmission capability is improved, but header overhead becomes excessive
Solution Approach 1:
The patent extracts and eliminates IP headers from small data packet transmissions by implementing direct layer-2 encapsulation. This removal of redundant IP header layers significantly reduces overhead for small packets, improving transmission efficiency and reducing bandwidth consumption while maintaining full data transmission capability.
4Reliability
If secure communication is established through IP-based protocols, then security negotiation capability is improved, but communication efficiency decreases
Solution Approach 1:
The patent segments security negotiation from data transmission by establishing secure layer-2 connections once through controlled plane signaling, then maintaining these connections for subsequent data transmissions. This segmentation allows comprehensive security negotiation (authentication, encryption setup) to occur once, after which data can flow efficiently without repeated negotiation overhead.
Data Source
AI summary
Device to device (D2D) communication can be performed with packet data convergence protocol (PDCP) based encapsulation without internet protocol (IP) addressing. The non-IP D2D PDCP-encapsulated communication can further include two forms of secure data transfer. A first non-IP D2D PDCP-encapsulated communication can be a negotiated non-IP D2D PDCP-encapsulated communication. A second non-IP D2D PDCP-encapsulated communication can be a non-negotiated non-IP D2D communication. The non-negotiated non-IP D2D PDCP-encapsulated communication can include a common key management server (KMS) version and a distributed KMS version. The encapsulated communication can be used with various protocols, including a PC5 protocol (such as the PC5 Signaling Protocol) and wireless access in vehicular environments (WAVE) protocols.