Private Cloud Routing Server Connection Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for Smart Device Clients to access Private Cloud Servers are cumbersome, often requiring complex setups, fixed IP addresses, dynamic DNS services, or public cloud-based routing servers, which compromise privacy and security, and are not user-friendly for consumer environments.

Innovation Solution

A system and method that establishes a private cloud routing server and smart device client relationship using session-based message connections, allowing secure communication without relying on public cloud-based routing servers, enabling access to private networks and services behind firewalls with dynamic IP addresses without additional router setups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a fixed IP address and port forwarding are configured to access PCSS from outside LAN, then the Smart Device Client can locate and access the PCSS, but the setup becomes complex and requires router configuration expertise

Engineering Contradiction:
Improveease of access to PCSSVSAvoidrouter configuration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a public cloud-based routing server as an intermediary between the Smart Device Client and the PCSS. Instead of directly configuring router port forwarding, the routing server mediates the connection by receiving requests from clients outside the LAN and forwarding them to the PCSS through the router's existing firewall rules, thereby simplifying the setup process

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The routing server provides a universal solution that works across different router configurations and network environments. It handles multiple functions including connection establishment, authentication, and data routing through a single service point, eliminating the need for users to configure complex port forwarding rules for each access scenario

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If dynamic DNS service is used to locate PCSS with dynamic IP, then fixed IP requirement is eliminated, but additional service dependency and configuration complexity are introduced

Engineering Contradiction:
Improveadaptability to dynamic IPVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The routing server acts as an intermediary that abstracts away the need for dynamic DNS configuration. It maintains a mapping between client identifiers and the PCSS's dynamic IP address internally, allowing clients to connect using simple identifiers rather than requiring them to set up and manage dynamic DNS services

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements automatic connection establishment where the routing server automatically manages the mapping between clients and the PCSS's dynamic IP address. The server handles IP address changes transparently without requiring user intervention or reconfiguration, making the system adaptable to dynamic IP environments without adding complexity for users

Inventive Principle:
Principle #25Self-service

3Ease of operation

If public cloud-based routing server is used to penetrate firewall, then access to PCSS is enabled, but privacy and security are compromised

Engineering Contradiction:
Improveaccess capabilityVSAvoidsecurity risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The routing server is designed as a trusted intermediary that implements strong authentication mechanisms. It verifies client credentials before establishing connections to the PCSS and uses secure communication protocols to protect data in transit, thereby enabling access while maintaining security through controlled mediation rather than unrestricted public access

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements different security levels for different parts of the architecture. The routing server uses public-key infrastructure and encrypted communication channels for external interactions, while the PCSS itself maintains private network isolation. This layered security approach allows public accessibility at the routing layer while preserving private security at the data layer

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11356417B2Private cloud routing server connection mechanism for use in a private communication architecture
Publication Date: 2022.06.07 KINGSTON DIGITAL INC
  • US11356417B2 patent drawing
  • US11356417B2 patent drawing
  • US11356417B2 patent drawing

AI summary

A private cloud routing server client device (PCRSCD) is disclosed which connects to a private cloud routing server (PCRS) by a connection based on whether the PCRS is in a same Local Area Network (LAN) as the PCRSCD and whether the PCRS is directly connected to the public cloud network.