Virtual Cloud Node Protocol Conversion for On-Premise Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

On-premise computing environments lack scalability and integration with cloud computing environments, limiting their ability to leverage cloud resources while maintaining control and security.

Innovation Solution

A virtual cloud node is introduced within an on-premise computing environment, acting as a proxy and protocol converter between cloud and on-premise systems, enabling seamless communication and data processing using protocols like SOAP and CORBA, and facilitating the extension of on-premise installations to cloud services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If on-premise computing environments use dedicated local servers, then control and security are improved, but scalability and integration with cloud services deteriorate

Engineering Contradiction:
Improvecontrol and securityVSAvoidscalability and cloud integration
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

A virtual cloud node is introduced as an intermediary component within the on-premise environment that bridges local servers and cloud services. This virtual node enables communication and data exchange between the on-premise CORBA-based system and cloud SOAP-based services without requiring fundamental changes to the existing on-premise architecture, thus maintaining control and security while enabling cloud scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Stability of the object's composition

If on-premise systems use CORBA protocol, then existing system operation is maintained, but compatibility with cloud SOAP services deteriorates

Engineering Contradiction:
Improveexisting system operationVSAvoidprotocol compatibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The virtual cloud node performs protocol parameter transformation by converting CORBA protocol parameters to SOAP protocol parameters and vice versa. This allows the on-premise system to continue using CORBA while the virtual node translates communications to SOAP for cloud service compatibility, resolving the protocol incompatibility without changing the core on-premise system operation.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If cloud computing resources are integrated, then scalability is improved, but system complexity deteriorates

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The protocol conversion and cloud integration complexity is extracted from the core on-premise server system and consolidated into a dedicated virtual cloud node. This separation allows the on-premise system to maintain its simple CORBA-based operation while the virtual node handles all complex protocol translation and cloud communication tasks independently.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10771283B2Virtual cloud node
Publication Date: 2020.09.08 SAP SE
  • US10771283B2 patent drawing
  • US10771283B2 patent drawing
  • US10771283B2 patent drawing

AI summary

Data packets are received by a virtual cloud node from a cloud server. The virtual cloud node is one of a plurality of computing nodes forming part of an on-premise computing environment. Each of the computing nodes include at least one computing device and executed a plurality of servers with one of the servers being a central management server. Thereafter, the virtual cloud node converts the data packets from a first protocol compatible with the cloud server to a second protocol. The central management server routes the converted data packets to another one of the computing nodes for processing or consumption. Related apparatus, systems, techniques and articles are also described.