Guest Transaction Queue for Secure Cross-Cloud Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems between devices and remote resources across different cloud computing services face challenges in asynchronous communication and security, particularly when devices are not registered or authenticated, leading to potential bandwidth overload and exposure of sensitive information.
Innovation Solution
The implementation of a guest transaction queue system that allows devices and resources to communicate asynchronously by creating a shared queue accessible by both parties, with optional authority management and encryption, and the use of a 'site secret' to obscure URLs, enabling secure and anonymous communication without requiring simultaneous activity or pre-authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If permission based access control is implemented for queue communication, then security is improved, but device complexity and authentication overhead increase
Solution Approach 1:
The patent introduces a cloud server as an intermediary that hosts the transaction queue and manages authentication centrally. The server validates messages using cryptographic keys and maintains a registry of authorized devices, eliminating the need for distributed authentication logic across all devices. This centralizes security management and reduces the authentication burden on individual devices while maintaining strong security controls.
2Reliability
If pre-authentication and registration are required for queue access, then security is improved, but communication flexibility and ease of operation deteriorate
Solution Approach 1:
The system performs preliminary authentication by pre-configuring cryptographic key pairs and device identifiers in a registry during device provisioning. This preliminary setup enables rapid subsequent communications without repeated full authentication cycles. The pre-established trust relationships allow devices to join and communicate more flexibly while maintaining security through the pre-configured credentials.
3Speed
If synchronous communication is used between devices, then real-time interaction is improved, but system availability and reliability worsen due to simultaneous activity requirements
Solution Approach 1:
The system implements periodic polling where devices periodically check for new messages in the transaction queue rather than maintaining continuous synchronous connections. The cloud server periodically pushes notifications when messages are available. This periodic approach maintains real-time responsiveness while allowing devices to operate independently without requiring simultaneous activity, thereby improving system availability and reliability.
4Adaptability or versatility
If multiple cloud computing services are used for communication, then system versatility is improved, but integration complexity and device complexity increase
Solution Approach 1:
The patent creates a universal transaction queue interface hosted on the cloud server that can be accessed by devices from different cloud computing services through a standardized protocol. The server acts as a multi-functional intermediary that translates and routes messages between different service ecosystems. This universal interface enables cross-service communication without requiring complex integration logic in each device, as the server handles the adaptation and protocol translation centrally.
Data Source
AI summary
Methods of communication between a remote resource and a data processing device, the system include storing in a transaction queue a message posted from the remote resource; sending a request to create a guest transaction queue, the guest transaction queue being accessible by both the data processing device and the remote resource; creating the guest transaction queue; reading, by the data processing device, the message from the remote resource; responding, from the data processing device to the remote resource by posting a message to the guest transaction queue; reading, by the remote resource, the message from the data processing device.