Remote Access via Cloud Notification for AllJoyn Gateway Agents
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions do not provide a mechanism for users to remotely access AllJoyn services when the remote configuration file is deactivated or deleted in the gateway agent.
Innovation Solution
The method involves a cloud server creating and managing a notification resource creation request with a parameter 'remote configuration file' to activate a local remote configuration file in the gateway agent, enabling remote access by forwarding remote access requests from a mobile device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the remote configuration file is deactivated or deleted in the gateway agent, then security and resource management are improved, but remote access capability is lost
Solution Approach 1:
The system performs preliminary actions by creating notification resources and updating configuration files in advance. When a remote configuration file is deactivated or deleted, the system proactively creates a notification resource that triggers the gateway agent to update its local configuration, ensuring remote access capability is restored without manual intervention
Solution Approach 2:
The system implements a feedback mechanism where the cloud server monitors the status of remote configuration files and sends notification resources to the gateway agent when changes occur. This feedback loop ensures that the gateway agent's local configuration remains synchronized with the cloud server, maintaining remote access capability while allowing configuration changes for security management
2Stability of the object's composition
If the gateway agent maintains strict synchronization with the cloud server configuration, then configuration consistency is improved, but system flexibility and user autonomy are reduced
Solution Approach 1:
The system transitions from static configuration synchronization to dynamic updates. The gateway agent periodically checks for notification resources and updates its local configuration based on current cloud server status. This dynamic approach allows the system to maintain consistency when needed while adapting to changes without rigid constraints
Solution Approach 2:
The gateway agent autonomously monitors for notification resources and performs self-updates when configuration changes are detected. This self-service mechanism eliminates the need for manual configuration management while maintaining consistency, allowing the system to adapt automatically to cloud server changes
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
Disclosed are an implementation method, apparatus and system for remote access. The method includes: a mobile device, MD, transmitting a first resource updating request to a cloud server, CS; according to the first resource updating request, the CS creating an attribute "remote configuration file" of a resource, and generating and transmitting a notification resource creation request to a gateway agent, GA, where the notification resource creation request includes a parameter "remote configuration file"; according to the parameter "remote configuration file" of the notification resource creation request, the GA activating a local remote configuration file; the CS receiving a remote access request transmitted by the MD, and according to an attribute "notified attribute" of an updated resource, forwarding the remote access request to the GA; and according to the activated remote configuration file, the GA executing the remote access request. With this application, a mechanism for a user to remotely access the AllJoyn service may be achieved when the remote configuration file is deactivated or deleted in the gateway agent.