Private Cloud Routing Server Architecture for Secure Smart Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for Smart Device Clients to access Private Cloud Servers are cumbersome, require technical expertise, and rely on public cloud-based routing servers, which pose security and business risks, especially in consumer-oriented environments where fixed IP addresses are not available and router setups are complex.
Innovation Solution
A system and method that employs a Private Cloud Routing Server and Private Network Service, allowing Smart Device Clients to access Private Cloud Servers securely without relying on public cloud-based routing servers, using message boxes for session-based authentication and communication, eliminating the need for external router setups and ensuring secure peer-to-peer connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a public cloud-based routing server is used to enable Smart Device Clients to access Private Cloud Servers, then connectivity and service access are improved, but security risks and business vulnerabilities increase due to reliance on external third-party infrastructure
Solution Approach 1:
The patent extracts and removes the public cloud-based routing server from the system architecture. Instead of relying on external third-party routing infrastructure, the system implements direct peer-to-peer communication between Smart Device Clients and Private Cloud Servers, eliminating the security vulnerabilities and business risks associated with public cloud dependency while maintaining connectivity
Solution Approach 2:
The patent introduces a messaging service as an intermediary that enables indirect communication between clients and servers without requiring public cloud routing infrastructure. The messaging service facilitates connection establishment and data transmission through alternative pathways, allowing systems to communicate securely without exposing themselves to public cloud-based security risks
2Ease of operation
If conventional router setup and configuration methods are used to enable external access to Private Cloud Servers, then network connectivity is achieved, but system complexity and difficulty of deployment increase significantly
Solution Approach 1:
The patent implements self-service mechanisms where the messaging service automatically handles connection establishment, routing, and communication protocols between Smart Device Clients and Private Cloud Servers. The system performs self-configuration and self-management without requiring manual router setup, port forwarding configuration, or complex network administration, thereby eliminating deployment complexity while maintaining connectivity
Solution Approach 2:
The messaging service acts as an intermediary that abstracts away complex network configuration requirements. Instead of requiring users to manually configure routers and firewalls, the messaging service handles all networking complexities behind the scenes, providing simple, unified access points for clients to connect to private cloud services
3Ease of operation
If fixed IP addresses and port forwarding are configured to allow external access to Private Cloud Servers, then direct connectivity is improved, but cost and setup complexity increase
Solution Approach 1:
The patent removes the requirement for fixed IP addresses and port forwarding configurations from the system. By eliminating these conventional networking requirements, the system avoids the costs associated with obtaining and maintaining static IP addresses, as well as the complexity of configuring port forwarding rules on network infrastructure
Solution Approach 2:
The messaging service serves as an intermediary that enables connectivity without requiring traditional network configuration mechanisms. It provides alternative routing pathways that work with dynamic IP addresses and do not require port forwarding, thereby reducing deployment costs and simplifying infrastructure requirements while maintaining direct client-server connectivity
Data Source
AI summary
A method and system for use with a public cloud network is disclosed, wherein the public cloud network includes at least one private cloud routing server, at least one private network service and at least one smart device client in communication therewith. The method and system comprise setting up the at least one private cloud routing server, the at least one private network service and the at least one smart device client in a client server relationship. The at least one private cloud routing server includes a message box associated therewith. The first message box is located in the public network. The at least one smart client includes a second message box associated therewith. The second message box is located on the public network. The method includes passing session based message information between the at least one private cloud routing server and the at least one smart device client via the first message box and the second message box in a secure manner. The session based information is authenticated by the private cloud routing server and the at least one smart device client. The smart device client and the private cloud routing server can then communicate with each other after the session based information is authenticated. The at least one private network service is then manageable and accessible by the at least one smart device client from anywhere at anytime without utilizing a public cloud based routing server.