Contextualized Information Bus for Context-Aware Service Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The evolution of the Internet from a host-centric system to a content-centric system has introduced complexities, such as the need for multiple transmission technologies and protocols that are not seamlessly integrated, limiting the ability of applications to utilize concurrent transmission links effectively, and existing IP-based security mechanisms are complex and not integrated with content-centric networking.
Innovation Solution
The Contextualized Information Bus (CIBUS) is introduced, which leverages Information Centric Network (ICN) architecture to enable context-aware communication by using hierarchical names and contexts for service discovery, routing, caching, and security, providing a flatter networking architecture that integrates with both application and physical layers, allowing for flexible interface selection and seamless integration with various protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple transmission technologies and protocols are integrated to enable context-aware communication, then adaptability and communication flexibility are improved, but device complexity and integration difficulty increase
Solution Approach 1:
The patent segments the networking functionality into distinct layers: a flatter architecture with application layer directly interfacing to physical layer, eliminating intermediate protocol layers. This segmentation allows each layer to handle specific functions independently, reducing integration complexity while maintaining adaptability across multiple transmission technologies
Solution Approach 2:
The patent implements a universal service request primitive that can handle multiple transmission technologies (WiFi, LTE, Bluetooth, etc.) and protocols through a single unified interface. The service request primitive includes context parameters that enable the system to adapt to different transmission media without requiring separate handling mechanisms for each technology
2Measurement precision
If service requests include detailed context information for precise service matching, then service delivery accuracy is improved, but information processing overhead increases
Solution Approach 1:
The patent implements context parameters that are included in service request primitives only when necessary for accurate service matching. The system selectively adds context information (such as location, device type, network conditions) based on the specific service requirements, avoiding unnecessary information overhead while maintaining precision where needed
3Ease of operation
If a flatter networking architecture is implemented to integrate application and physical layers, then ease of operation and flexibility are improved, but compatibility with existing protocols may be compromised
Solution Approach 1:
The patent introduces service request primitives as an intermediary mechanism between the application layer and physical layer. These primitives carry service identification and context information that enable the flatter architecture to communicate effectively with existing protocols and network elements, maintaining compatibility while achieving operational flexibility
Data Source
AI summary
An NE comprising a plurality of physical interfaces configured to communicate to a plurality of remote NEs in an ICN, a receiver coupled to the plurality of physical interfaces and configured to receive a request for a service from a first of the remote NE via the ICN, wherein the service request comprises a requested service name and a requested service context, a memory comprising a service profile comprising a supported service associating with a supported service name and a supported service context, a processor coupled to the memory and the receiver and configured to generate a service response when the requested service name matches the supported service name and the requested service context matches the supported service context, and a transmitter coupled to the processor and the plurality of physical interfaces and configured to transmit the service response to the first NE via the ICN.