UE-to-UE Relay Mapping for Native Non-IP Traffic Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for Layer-3 UE-to-UE relay focus solely on handling Internet Protocol (IP) traffic and do not address Non-IP traffic without IP encapsulation.
Innovation Solution
A network device generates a relay identifier and maintains a mapping between source and target UE identifiers for Non-IP communication links, using Layer-2 IDs to forward Non-IP packets without IP encapsulation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Layer-3 UE-to-UE relay is used for Non-IP traffic communication, then communication between UEs outside cell coverage is enabled, but existing solutions only support IP traffic and do not address Non-IP traffic without IP encapsulation
Solution Approach 1:
The patent changes the protocol parameter from IP-based to Non-IP based, allowing the relay mechanism to handle different traffic types. By modifying the protocol stack to operate at Layer 2 instead of Layer 3 for Non-IP traffic, the system achieves versatility in supporting both IP and Non-IP traffic without requiring separate relay mechanisms.
Solution Approach 2:
The patent introduces a Layer 2 relay mechanism that acts as an intermediary for Non-IP traffic between UEs. This intermediary operates at the data link layer, providing forwarding capabilities for Non-IP packets without requiring IP encapsulation, thus resolving the limitation of existing IP-only relay solutions.
2Adaptability or versatility
If IP encapsulation is used for Non-IP traffic, then existing IP-based relay solutions can handle the traffic, but the original Non-IP nature and efficiency are compromised
Solution Approach 1:
The patent extracts the IP encapsulation step from the relay process by implementing a dedicated Layer 2 relay mechanism. This extraction allows Non-IP traffic to be handled natively without being wrapped in IP packets, preserving the original Non-IP characteristics and efficiency while still enabling relay functionality through a separate protocol path.
3Reliability
If multiple SL unicast links are established for different applications, then high reliability communication is achieved, but identifier management and link differentiation become complex
Solution Approach 1:
The patent segments the identifier space by introducing application-specific identifiers that are distinct from generic Layer 2 IDs. This segmentation allows the system to maintain multiple simultaneous unicast links for different applications with clear identifier differentiation, reducing the complexity of identifier management while preserving communication reliability through dedicated links for each application.
Data Source
AI summary
A method for Non-IP traffic communication by UE-to-UE relay is provided. The method is implemented by a network device in a communication network. The method includes receiving a first Direct Communication Request from a source UE. The first Direct Communication Request indicates the establishment of a Non-IP communication link with the source UE and includes a first source UE identifier for the source UE and a first target UE identifier for a target UE. The network device generates a first relay identifier for a relay used in the Non-IP communication link between a source UE and the target UE. The network device maintains a mapping between the first relay identifier, the first source UE identifier, and the first target UE identifier.