Cloud Portal Hub for Multi-Service Resource Planning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In a Cloud computing environment with multiple implementations and providers, users face the burden of separately accessing and managing different Cloud systems, leading to complexity and inefficiency.

Innovation Solution

A technology-neutral process integration using a business meta-schema format Cloud Data Interchange (CDI) provides a resource planning layer that abstracts underlying Cloud services, allowing users to access and manage multiple Cloud implementations through a centralized portal, enabling seamless request handling and routing across various Cloud providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users access multiple Cloud systems separately, then each Cloud service can be managed independently, but user complexity and time consumption increase significantly

Engineering Contradiction:
ImproveCloud service management capabilityVSAvoidUser operation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a portal as an intermediary layer between users and multiple Cloud systems. The portal receives user requests, determines the appropriate Cloud implementation based on request content, and routes requests accordingly. This mediator approach allows users to access diverse Cloud services through a single interface without needing to understand or manage each underlying system separately, thus reducing operational complexity while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The portal is designed as a universal access point that can handle requests for multiple different Cloud implementations through a single interface. Instead of requiring separate access points for each Cloud system, the portal provides multi-functional capabilities to manage various Cloud services (infrastructure, platform, software services) uniformly, thereby improving ease of operation without sacrificing adaptability.

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

2Adaptability or versatility

If users access multiple Cloud systems separately, then each service can be managed independently, but time consumption increases

Engineering Contradiction:
ImproveMulti-Cloud service accessVSAvoidService access time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-establishing the portal infrastructure that contains routing logic and Cloud implementation knowledge. When a user submits a request, the portal has already been prepared to interpret the request content, determine the appropriate Cloud implementation, and route it efficiently. This preliminary setup eliminates the need for users to spend time understanding different Cloud systems or manually configuring access to each one.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The portal acts as a time-saving intermediary that automatically performs the complex task of routing requests to appropriate Cloud implementations. Instead of users spending time determining which Cloud system to access, the intermediary portal handles this determination and routing automatically based on request content, significantly reducing service access time while maintaining multi-Cloud capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If a centralized portal is introduced to simplify access, then user operation becomes easier, but system complexity increases

Engineering Contradiction:
ImproveUser access simplicityVSAvoidPortal system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The portal system is segmented into distinct functional components: request reception module, determination module, and routing module. Each component has a specific, well-defined function. The request reception module handles user input, the determination module analyzes request content and identifies appropriate Cloud implementations, and the routing module directs requests to the correct destination. This segmentation reduces overall system complexity by creating modular, manageable components rather than a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

While the portal does increase system complexity, it introduces a standardized intermediary layer that simplifies the interface between users and diverse Cloud systems. The complexity is concentrated in the portal's routing logic, which uses standardized determination criteria based on request content. This centralized complexity management allows the portal to provide simplified user access while the underlying complexity is handled systematically through standardized mediation protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8396989B2Resource planning and data interchange functionality within a cloud computing environment
Publication Date: 2013.03.12 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8396989B2 patent drawing
  • US8396989B2 patent drawing
  • US8396989B2 patent drawing

AI summary

The present invention provides technology neutral process integration (Cloud Resource Planning), and optimization methodology leveraging a business meta-schema format Cloud Data Interchange (CDI) to integrate, enable, and invoke Cloud services. One example is that the present invention provides a management layer at the process level. There can be multiple Cloud implementations/types within a govern enterprise—perhaps utilizing different infrastructure (e.g., hardware of one supplier versus that of another) or different areas of functionality (computing services, storage services, etc). This disclosure provides an abstraction or ‘resource planning’ layer above these core services such that a customer does not have to have knowledge or choose different Cloud types and/or understand or choose each underlying service. As such, it provides a ‘one stop’ portal.