Private Cloud Routing Server Secure Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 compromise privacy and security, and pose business risks due to single-point failures and lack of user control.

Innovation Solution

A system and method that sets up a Private Cloud Routing Server and Smart Device Client in a client-server relationship, using session-based messaging authenticated by the Private Cloud Routing Server, allowing secure communication without relying on public cloud-based routing servers, thus eliminating the need for external router setups and reducing complexity.

Engineering Contradictions & Design Principles

VSEngineering 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 privacy and security are compromised

Engineering Contradiction:
Improveservice accessVSAvoidprivacy compromise
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the routing function from public cloud servers and implements it within the private cloud network itself. Each private cloud server acts as its own routing server, eliminating the need to rely on external public infrastructure. This extraction removes the privacy compromise while maintaining service accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces encrypted tunneling as an intermediary mechanism between Smart Device Clients and Private Cloud Servers. Data passes through encrypted channels that prevent public cloud servers from intercepting or monitoring content, thus maintaining privacy while enabling connectivity through public networks.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a public cloud-based routing server is used to enable Smart Device Clients to access Private Cloud Servers, then service accessibility is improved, but business risk increases due to single-point failures and lack of user control

Engineering Contradiction:
Improveservice accessibilityVSAvoidbusiness risk
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the routing function from centralized public cloud servers and distributes it across multiple private cloud servers. Each private cloud server independently provides routing services to its own clients, eliminating single-point failures. If one server fails, others continue to operate autonomously, maintaining service reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables private cloud servers to autonomously manage their own routing operations without requiring external public cloud infrastructure. Each server independently handles connection establishment, authentication, and data forwarding, giving users full control and eliminating dependency on external service providers.

Inventive Principle:
Principle #25Self-service

3Object-affected harmful factors

If conventional methods are used to access Private Cloud Servers behind firewalls, then secure communication is achieved, but setup complexity and technical expertise requirements increase

Engineering Contradiction:
Improvefirewall securityVSAvoidsetup complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent merges the routing server functionality directly into the private cloud server infrastructure. Instead of requiring separate router configurations and firewall rule setups, the routing server integrates with the existing private cloud architecture, automatically handling connections while maintaining firewall security. This eliminates complex setup procedures while preserving security.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9935930B2Private and secure communication architecture without utilizing a public cloud based routing server
Publication Date: 2018.04.03 KINGSTON DIGITAL INC
  • US9935930B2 patent drawing
  • US9935930B2 patent drawing
  • US9935930B2 patent drawing

AI summary

A method for use with a public cloud network is disclosed. The method includes setting up a private cloud routing server and a smart device client in a client server relationship. The private cloud routing server includes a first message box. The smart client includes a second message box. The first and second message boxes are located on the public cloud network. The method also includes passing an authenticated session based message between the first and the second message boxes in a secure manner. The smart device client and the private cloud routing server can communicate with each other after authentication to provide security. The method also includes setting up another smart device client in a client server relationship with the private cloud routing server. The two smart device clients can privately and securely communicate with each other through the public cloud network.