CORE Protocol Intra-Inter Session Network Coding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless mesh networks face limitations in scalability due to constraints on wireless spectrum, requiring techniques and protocols that enhance throughput and spectral efficiency, while existing methods often address reliability and opportunistic flow combination separately rather than in a cooperative manner.
Innovation Solution
The CORE protocol employs random linear network coding (RLNC) for intra-session coding and allows nodes to set up inter-session coding regions where flows intersect, leveraging RLNC to compensate for losses and failures, thereby increasing throughput beyond traditional methods.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional separate methods are used to address reliability and opportunistic flow combination, then individual problems can be solved, but overall throughput and spectral efficiency are limited
Solution Approach 1:
The patent combines intra-session network coding (for reliability) and inter-session network coding (for throughput enhancement) into a unified protocol called CORE. This merging allows the system to simultaneously achieve both reliability guarantees and throughput improvements by coordinating coding operations across multiple sessions while maintaining individual session integrity.
Solution Approach 2:
The CORE protocol serves multiple functions simultaneously: it provides reliability through intra-session coding, enhances throughput through inter-session coding, and maintains compatibility with existing routing protocols. This multi-functionality resolves the contradiction by making a single system capable of addressing both reliability and throughput requirements.
2Productivity
If network coding is implemented to enhance throughput, then spectral efficiency improves, but system complexity increases
Solution Approach 1:
The patent segments the network coding functionality into distinct intra-session and inter-session components that operate independently but coordinate through the CORE protocol. This segmentation reduces complexity by allowing each component to be implemented and managed separately while still achieving overall spectral efficiency improvements.
Solution Approach 2:
The CORE protocol performs preliminary actions by pre-establishing coding regions and coordinating coding opportunities before data transmission occurs. This preliminary setup simplifies the actual coding operations during transmission, reducing real-time computational complexity while maintaining high spectral efficiency.
3Ease of operation
If routes are set up beforehand to be agnostic to other sessions, then routing simplicity is maintained, but opportunistic coding opportunities may be missed
Solution Approach 1:
The CORE protocol implements feedback mechanisms where nodes report coding opportunities and route information to the CORE coordinator. This feedback allows the system to maintain simple predetermined routes while still discovering and exploiting coding opportunities dynamically, resolving the contradiction between routing simplicity and coding opportunity exploitation.
Solution Approach 2:
The CORE protocol acts as an intermediary layer between simple predetermined routing and opportunistic coding. It receives route information from simple routing protocols, identifies coding opportunities, and coordinates coding operations without requiring complex routing decisions, thus maintaining routing simplicity while enabling coding opportunities.
Data Source
Figure 1
Figure 2
Figure 3(a)~3(b)
AI summary
A wireless network protocol (CORE) and related methods, systems, and circuits are disclosed that are capable of enhancing network performance. The protocol uses random linear network coding (RLNC) for intra-session coding in the network, while allowing nodes in the network to set up inter-session coding regions where flows intersect. Within the inter-session coding regions, combinations of coded packets associated with different unicast sessions are permitted. However, packets associated with multiple different unicast sessions are not allowed to be transmitted outside of the coding regions.