Content Centric M2M Routing via URL Component Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M communication systems, such as Zigbee, Z-Wave, and IP-based solutions, face challenges in compatibility with TCP/IP networks, energy efficiency, and resource constraints, leading to complex development, high costs, and limitations in supporting heterogeneous environments and large-scale user requests.
Innovation Solution
A method for routing data in a content-centric network using a database FIB that associates URL components with unique node identifiers, allowing for efficient forwarding of content requests and reducing payload size, while also implementing a PIT to manage data packets and support subscription requests and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If current M2M communication systems (Zigbee, Z-Wave, IP-based solutions) are used, then device compatibility and network functionality are achieved, but development complexity and costs increase, and energy efficiency deteriorates
Solution Approach 1:
The patent segments the M2M system into distinct functional layers: a content generation layer with resource-constrained sensors, a content networking layer with gateway nodes running CCN protocols, and an application layer. This segmentation allows each layer to be optimized independently, reducing overall system complexity while maintaining functionality.
Solution Approach 2:
The patent introduces gateway nodes as intermediaries between resource-constrained sensor nodes and the CCN infrastructure. These gateways handle complex routing, content storage, and protocol translation, allowing simple sensors to benefit from sophisticated network capabilities without bearing the computational burden, thus reducing development complexity for end devices.
2Use of energy by moving object
If traditional M2M protocols are used, then device communication is enabled, but energy consumption increases due to complex protocol stacks
Solution Approach 1:
The patent extracts the complex protocol stack functionality from resource-constrained sensor nodes and relocates it to gateway nodes with sufficient computational resources. Sensors only need to generate and transmit simple content packets, while gateways handle Interest packet routing, content storage, and protocol management, dramatically reducing energy consumption at the sensor level.
Solution Approach 2:
The ContentStore at gateway nodes automatically caches content locally, enabling rapid response to Interest packets without requiring continuous sensor communication. This self-service mechanism reduces the frequency of sensor activations and associated energy consumption while maintaining responsive content delivery.
3Adaptability or versatility
If content requests are routed through traditional IP-based networks, then TCP/IP compatibility is achieved, but payload size and transmission overhead increase
Solution Approach 1:
The patent changes the fundamental addressing parameter from IP-based hierarchical addressing to content-name-based addressing in CCN. Content names encode both location and identity information, allowing more efficient routing decisions and reduced payload requirements. Interest packets contain only content names rather than full TCP/IP headers, reducing overhead.
4Productivity
If sensor resources are allocated to handle large-scale user requests directly, then user interaction capacity increases, but sensor energy depletion accelerates
Solution Approach 1:
The patent introduces a spatial dimension to the system architecture by distributing content storage across multiple gateway nodes in a network. When a sensor generates content, it is propagated to multiple gateways that maintain it in their ContentStores. This distributed storage allows any gateway to serve user requests, effectively increasing system capacity without increasing sensor workload or energy consumption.
Data Source
AI summary
A method for routing data at a first node of a network including a second node. The method includes: providing the first node with a database storing an association between: an URL component identifying content at the first node, and a unique identifier associated to the second node, the unique identifier being specified by the second node; registering content locally stored in the second node by storing in the database an association between an URL component identifying the locally stored content and the unique identifier of the second node; and, upon reception from a requesting entity, by the first node, of a content request having a content identifier, the method includes: checking in the database whether the content identifier includes the URL component, and forwarding the content request to the second node if the content identifier includes the URL component associated with the unique identifier of the second node.