Declarative Policy Manager for N:N Resource Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing resource mapping technologies, such as those in Java EE servers, often require 1:1 mappings between resource references and resources, limiting flexibility and efficiency, especially in environments where multiple criteria-based resource access is needed, like multi-tenancy scenarios, and require custom logic or separate versions of applications for different resource access levels.

Innovation Solution

Implementing a declarative policy-based mechanism for N:N resource mapping, allowing server administrators to define rules for context-dependent resource allocation across different scopes, enabling applications to connect to multiple resources without modifications, using a policy manager to dynamically select appropriate resources based on user context.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If 1:1 resource mapping is used, then resource allocation is simple and straightforward, but flexibility and efficiency are limited especially in multi-tenancy scenarios

Engineering Contradiction:
Improveresource allocation flexibilityVSAvoidmapping complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a policy manager as an intermediary component between applications and resources. This policy manager handles the complex N:N mapping logic declaratively, allowing applications to access multiple resources through a single reference element without applications needing to understand the complexity. The policy manager mediates between the simple application interface and the complex resource mapping requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the resource mapping functionality into separate policy definitions that can be independently configured. Instead of hardcoding mappings in applications, the mapping logic is divided into reusable policy elements that can be applied across multiple applications and resource references, reducing overall system complexity while enabling flexible N:N mappings.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If custom logic is implemented for different resource access levels, then specific resource access requirements are met, but application modification is required and scalability is reduced

Engineering Contradiction:
Improvecontext-dependent resource accessVSAvoidapplication deployment ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The policy manager enables self-service resource allocation by automatically selecting appropriate resources based on context information and defined policies. Applications do not need to contain custom logic for resource selection; instead, the policy manager autonomously determines resource assignments based on user context, application requirements, and pre-configured policies, maintaining application simplicity while enabling context-dependent access.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the parameter of resource mapping from fixed 1:1 relationships to dynamic N:N relationships governed by policies. By parameterizing resource access through policy rules that consider context information (such as user role, application type, resource availability), the system achieves context-dependent resource access without modifying application code, thereby maintaining ease of deployment while increasing adaptability.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If N:N resource mapping is implemented, then resource utilization is improved and flexibility is enhanced, but system complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidmapping management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The policy manager serves as an intermediary that manages the complexity of N:N resource mappings. It provides a declarative interface for defining policies and automatically handles the complex logic of matching resource references with appropriate resources based on context. This intermediary approach enables efficient resource utilization through flexible N:N mappings while shielding applications from the underlying complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The policy manager is designed as a universal component that handles multiple functions: it manages N:N mappings, evaluates context information, selects appropriate resources, and applies policies across different applications and resources. This multi-functional approach consolidates complexity into a single reusable component, improving resource utilization efficiency without proportionally increasing overall system complexity.

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

Data Source

PatentUS8874752B2Provision of other than 1:1 resource mapping
Publication Date: 2014.10.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8874752B2 patent drawing
  • US8874752B2 patent drawing
  • US8874752B2 patent drawing

AI summary

A method for providing other than a 1:1 resource mapping may include receiving an indication of a selected resource reference element, receiving an indication of at least one resource to be associated with the resource reference element, and generating, via processing circuitry, a registry including a declarative policy defining an association of the selected resource reference element and the at least one resource in which the registry defines an other than 1:1 mapping between resource reference elements and resources.