Server-Based File Brokerage for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server-based systems lack efficient mechanisms for brokering files and tasks across computing and mobile devices, particularly when devices are not connected to the server, limiting collaborative efforts and access to resources.
Innovation Solution
A server-based system that uses request and notification queues to facilitate file transfers and task execution between devices, allowing requests to be made and tasks to be performed even when devices are not directly connected, through a global communication network, enabling conditional file transfers and notifications regardless of device connectivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If devices must be connected to the server to access files or perform tasks, then server-based control is maintained, but device accessibility and collaborative effort are limited
Solution Approach 1:
The system performs preliminary actions by pre-establishing communication channels and pre-loading necessary data into the server's buffer before actual file transfer or task execution is needed. This allows devices to access files and execute tasks without maintaining continuous connectivity to the server, as the server has already prepared and cached the necessary resources in advance.
Solution Approach 2:
The server acts as an intermediary that decouples direct device-to-device communication requirements from server-mediated operations. By using the server as an intermediate buffer and coordination point, devices can initiate file transfers and task executions without needing direct connectivity to each other, only requiring temporary or asynchronous connection to the server for coordination and notification.
2Speed
If the server waits for device connection before processing requests, then connection stability is ensured, but response time and task execution speed are reduced
Solution Approach 1:
The server performs preliminary processing actions by receiving and buffering requests in advance, preparing file transfer parameters, and pre-establishing communication protocols before the actual data transfer begins. This allows the server to process requests faster once connected, as the preparatory work is already done, reducing overall response time while maintaining connection stability during execution.
Solution Approach 2:
The system maintains continuity of useful action by keeping the server in a ready state with buffered requests and pre-prepared resources, allowing immediate action when devices connect. The server continuously maintains its operational state and buffers incoming requests, so when a device establishes connectivity, the server can immediately begin processing without idle waiting time, thus maintaining both speed and reliability.
3Device complexity
If file transfers require direct device-to-device connection, then transfer speed is maximized, but system complexity and security risks increase
Solution Approach 1:
The server serves as an intermediary that simplifies the file transfer operation by handling all the complexity of connection management, authentication, and data transmission. Instead of requiring direct device-to-device connection which would increase system complexity and security risks, the server mediates these operations, providing a simpler interface for users while managing the underlying complexity and security protocols centrally.
Solution Approach 2:
The system implements self-service by allowing devices to autonomously initiate file transfers and task executions through simple user actions, while the server automatically handles the complex coordination, authentication, and data transmission. The devices don't need to manually establish connections or manage transfer parameters - they simply initiate requests, and the server self-manages the entire process, reducing operational complexity for users.
Data Source
AI summary
A server-based files and tasks brokerage system and method are disclosed. In response to receiving a request from a requesting computing device, the server posts the request to a request queue. The request is for a requested mobile telephonic device to perform a task. The server posts a first notification to a first notification queue, in response to receiving the request. The server pushes the first notification to the requested device upon confirming a connection. Upon detecting a first condition of the task being for the requested device to receive a file, the server transfers the file from a file repository. Upon detecting a second condition of the task being for the requested device to send a file, the server transfers the file to the file repository. In response to confirming task completion, the server posts a second notification to a second notification queue associated with the requesting device.