Message Gates for Secure Distributed Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed computing technologies, such as Jini, are not scalable enough for small footprint devices due to resource constraints and require Java support, TCP/IP connectivity, and code-centric programming models, making them unsuitable for heterogeneous environments and small embedded devices.
Innovation Solution
The implementation of message gates in a distributed computing environment using XML for secure and reliable message passing, allowing clients and services to communicate without relying on Java or TCP/IP, and enabling message verification and authentication, facilitating communication between diverse devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Java support and TCP/IP connectivity are required for distributed computing, then communication reliability is improved, but device compatibility and scalability to small footprint devices deteriorate
Solution Approach 1:
The patent changes the fundamental parameters of the communication model by replacing Java-based RMI with XML-based message passing. This allows the system to maintain communication reliability while adapting to devices with varying capabilities, including small footprint devices that cannot run Java virtual machines. The message gate architecture enables parameter adjustment based on device capabilities.
Solution Approach 2:
The patent segments the communication system into independent message gates that can operate autonomously. Each message gate handles authentication, message formatting, and transmission independently, allowing the system to function without requiring full Java or TCP/IP stacks on all devices. This segmentation enables deployment on resource-constrained devices while maintaining overall system reliability.
2Adaptability or versatility
If code-centric programming models are used, then service capabilities are improved, but complexity of implementation and configuration increases
Solution Approach 1:
The patent introduces message gates as intermediary components that mediate between service capabilities and communication. Instead of direct code-centric interactions, services communicate through standardized XML messages routed by message gates. This intermediary layer simplifies implementation by providing a uniform interface while maintaining rich service capabilities.
Solution Approach 2:
The patent replaces the mechanical code-centric programming model with a data-centric XML message model. Services are described through XML schemas rather than code interfaces, and message gates automatically handle message formatting and validation. This substitution reduces implementation complexity while preserving service capabilities.
3Reliability
If message authentication and verification are implemented, then security is improved, but processing overhead and message complexity increase
Solution Approach 1:
The patent implements preliminary authentication where message gates establish security credentials before message exchange. The authentication service pre-validates message gates and establishes trust relationships in advance. This preliminary action ensures security while keeping individual messages simple, as the authentication overhead occurs during gate establishment rather than with each message.
Data Source
AI summary
Embodiments of a system and method using message authentication with message gates are described. A message gate is the message endpoint for a client or service in a distributed computing environment. A message gate may provide a secure endpoint that sends and receives type-safe messages. Gates may perform the sending and receiving of messages between clients and services using a protocol specified in a service advertisement. In one embodiment, the messages are eXtensible Markup Language (XML) messages. For a client, a message gate represents the authority to use some or all of a service's capabilities. Each capability may be expressed in terms of a message that may be sent to the service. Creation of a message gate may involve an authentication service that may authenticate the client and/or service and that generates an authentication credential. A message gate may perform verification of messages against a message schema to ensure that the messages are allowed. Message gates may embed the authentication credential in outgoing messages so that the receiving message gate may authenticate the message. Messages may also include information to allow the receiving gate to verify that the message has not been compromised prior to receipt.