Cloud Infrastructure Layouts for Policy Enforcement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current system architectures for cloud-platform infrastructure layouts lack a systematic way to extend standardized models for global optimization policies and hierarchical policy enforcement during workflow generation, leading to unanticipated interactions and challenges in generating feasible workflows across diverse cloud environments.

Innovation Solution

A context-aware infrastructure layout architecture that maps northbound services to southbound service fulfillment models, using a core layout and extensions to facilitate policy enforcement, workflow generation, and management of infrastructure layouts, enabling accelerated configuration and deployment of southbound services while ensuring policy compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standardized models are used for cloud-platform infrastructure layouts, then system compatibility and ease of operation are improved, but adaptability to diverse cloud environments and policy enforcement capabilities deteriorate

Engineering Contradiction:
Improveease of workflow generationVSAvoidadaptability to diverse cloud environments
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The infrastructure layout is segmented into a standardized core model and environment-specific extensions. The core model contains universal components and relationships that ensure compatibility, while extensions allow customization for diverse cloud environments. This segmentation enables the system to maintain ease of operation through standardization while achieving adaptability through modular extensions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adds a dimensional layer by introducing extension mechanisms that operate alongside the standardized core model. This allows the infrastructure layout to exist in multiple dimensions - the base standardized dimension for compatibility and an extension dimension for adaptability - resolving the contradiction between ease of operation and versatility.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If standardized models are used for cloud-platform infrastructure layouts, then ease of workflow generation is improved, but policy enforcement capabilities deteriorate

Engineering Contradiction:
Improveease of workflow generationVSAvoidpolicy enforcement capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Policy enforcement is segmented into core policy requirements defined in the standardized model and environment-specific policy extensions. This allows systematic policy enforcement while maintaining ease of workflow generation through the standardized core, with additional reliability through targeted policy extensions for specific environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Policy requirements are preliminarily defined in the core infrastructure layout model before workflow generation occurs. This preliminary action ensures that policy enforcement capabilities are established upfront, allowing workflows to be generated easily while automatically complying with policies, thus resolving the contradiction between ease of operation and reliability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If environment-specific extensions are added to standardized models, then adaptability to diverse cloud environments is improved, but device complexity and difficulty of management increase

Engineering Contradiction:
Improveadaptability to diverse cloud environmentsVSAvoidcomplexity of infrastructure layout
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The infrastructure layout is segmented into a manageable core model and separate extension components. This segmentation allows the system to achieve adaptability through extensions while keeping the core model simple and manageable, reducing overall device complexity through organized modularity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Extensions are nested within the core infrastructure layout model, allowing the standardized core to contain and organize environment-specific extensions. This nesting structure manages complexity by providing a hierarchical organization where the simple core encapsulates the complexity of multiple environment-specific extensions, making the overall system more manageable.

Inventive Principle:
Principle #7Nested doll (Nesting)

4Adaptability or versatility

If environment-specific extensions are added to standardized models, then adaptability to diverse cloud environments is improved, but unanticipated interactions and challenges in generating feasible workflows increase

Engineering Contradiction:
Improveadaptability to diverse cloud environmentsVSAvoidcomplexity of workflow generation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Workflow generation is segmented into core workflow patterns defined in the standardized model and environment-specific workflow extensions. This segmentation reduces unanticipated interactions by clearly separating universal workflow logic from environment-specific adaptations, making workflow generation more predictable and manageable across diverse cloud environments.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10355941B2Sensor data handling for cloud-platform infrastructure layouts
Publication Date: 2019.07.16 ACCENTURE GLOBAL SERVICES LTD
  • US10355941B2 patent drawing
  • US10355941B2 patent drawing
  • US10355941B2 patent drawing

AI summary

A system maintains, generates, and manages infrastructure layouts. The infrastructure layouts include structural relationships for the handling of received sensor data. The infrastructure layouts may be traversed to determine datastore options for the sensor data and contextual information that may be used to enrich the received sensor data.