Event Bus File Transfer Automation for Edge Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack a mechanism to efficiently link files to event notifications through the publisher-subscriber pattern, leading to a cumbersome multistep process for application developers when transferring files between edge devices hidden behind firewalls.
Innovation Solution
A method for end-to-end event flows that involves storing a file associated with a source event at a source edge device, uploading it to a cloud device, generating cloud and destination events by updating file paths, and transferring these events across devices to facilitate seamless file availability notifications to subscribers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If point-to-point file transfers are repeated multiple times for multiple subscribers, then file delivery to multiple subscribers is achieved, but the process becomes cumbersome and complex for application developers
Solution Approach 1:
The system segments the file transfer process into distinct phases: publication phase (publisher uploads file once), notification phase (event bus distributes file location information to multiple subscribers), and download phase (subscribers retrieve files independently). This segmentation eliminates the need for repeated point-to-point transfers while reducing process complexity.
Solution Approach 2:
The event bus acts as an intermediary between the publisher and multiple subscribers. Instead of direct publisher-subscriber transfers, the event bus receives the published file location and distributes notifications to all subscribers, simplifying the transfer process and reducing developer burden.
2Adaptability or versatility
If files are transferred between edge devices hidden behind firewalls, then file sharing is achieved, but the transfer process becomes difficult and cumbersome
Solution Approach 1:
The event bus system serves as a mediator that operates independently of firewall restrictions. File location information and event notifications are transmitted through the event bus infrastructure, which handles the complexity of firewall-nested edge device communication, making the process easier to operate.
Solution Approach 2:
Instead of transferring actual file data across firewall boundaries, the system transfers a copy of the file location information through the event bus. Subscribers receive notifications containing file location details and independently retrieve files, avoiding complex cross-firewall data transfers.
3Reliability
If a multistep process is used to link files to event notifications, then file events are processed, but the process is cumbersome to application developers
Solution Approach 1:
The system merges file transfer and event notification into a unified publish-subscribe process. When a publisher publishes a file event, the file location is automatically distributed through the event bus to all subscribers, combining what would otherwise be separate file transfer and event notification steps into a single integrated operation.
Solution Approach 2:
The event bus provides universal functionality by handling both file location distribution and event notification delivery through a single mechanism. This multi-functional approach eliminates the need for separate processes, reducing complexity while maintaining reliable file event processing.
Data Source
AI summary
A method for end-to-end event flows includes storing a file associated with a source event at a source storage location in a source edge device, uploading the file to a cloud device, storing the file at a cloud storage location, generating a cloud event by changing a file path referenced in the source event to point to the cloud storage location of the file, and transferring the cloud event to the cloud device. The method includes transferring the cloud event to a destination edge device, downloading the file to the destination edge device, generating a destination event by changing the file path referenced in the cloud event to point to a destination storage location of the file, publishing an availability of the file in the destination edge device to multiple destination subscribers, and transferring the file from the destination storage location to one or more destination subscribers.