Private Cloud Routing Server for Secure External Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for Smart Device Clients to access private cloud storage servers or services within a home or office environment are cumbersome, often requiring fixed IP addresses, complex router setups, or reliance on public cloud-based routing servers, which compromise privacy and security.

Innovation Solution

A system and method that employs a private cloud routing server and a private cloud call-back server to establish a secure session-based message mechanism, allowing Smart Device Clients to access private cloud services without needing a public cloud-based routing server, thereby bypassing the need for complex router setups and ensuring privacy and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a fixed IP address and port opening are configured on the router to access the private cloud storage server from outside the LAN, then the smart device client can locate and access the server, but the system complexity and security risks increase due to firewall penetration requirements

Engineering Contradiction:
ImproveAccess capabilityVSAvoidRouter configuration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based routing server as an intermediary between the smart device client and the private cloud storage server. Instead of directly penetrating the router firewall, the client communicates through the cloud routing server which maintains a mapping between the client's dynamic IP address and the server's fixed IP address. This mediator eliminates the need for complex router configurations while enabling external access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a public cloud-based routing server is used to enable external access to private cloud services, then connectivity is improved, but privacy and security are compromised

Engineering Contradiction:
ImproveExternal access capabilityVSAvoidPrivacy and security risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements a private cloud routing server that is owned and controlled by the user rather than relying on public cloud services. The user's own server acts as the routing intermediary, maintaining the mapping between dynamic client IP addresses and the fixed storage server IP address. This self-service approach eliminates dependency on external public services while preserving privacy and security, as all routing information remains within the user's private infrastructure.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If dynamic DNS service and port mapping are configured to access the server without a fixed IP address, then accessibility is improved, but the setup complexity and time required increase

Engineering Contradiction:
ImproveAccess flexibilityVSAvoidConfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements automatic IP address detection and registration mechanisms where the private cloud routing server proactively monitors and updates the mapping between the user's dynamic IP address and the cloud routing server's address. This preliminary action eliminates the need for manual configuration of dynamic DNS services, as the system automatically adapts to IP changes without requiring user intervention or time-consuming setup procedures.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11683292B2Private cloud routing server connection mechanism for use in a private communication architecture
Publication Date: 2023.06.20 KINGSTON DIGITAL INC
  • US11683292B2 patent drawing
  • US11683292B2 patent drawing
  • US11683292B2 patent drawing

AI summary

A method for use with a public cloud network is disclosed. The method includes setting up at least one private cloud routing server (PCRS) and at least one smart device client on the side of the PCRS in a client server relationship. It also includes setting up at least another smart device client on the side of the PCCBS in a client server relationship with the at least one private cloud call-back server (PCCBS). The private cloud call-back server acts as a middleman to relay communication between the smart device client on the side of the PCCBS and the private cloud routing server. The PCCBS will call back the private cloud routing server on demand based on the smart device client request. The at least one private cloud call-back server includes a first message box associated therewith.