Client Interfaces for Package Content Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional package mechanisms in data processing systems lack effective strategies for handling object generation, interfacing, and enhancements, especially when dealing with multiple interfaces, modules, components, and services across development projects, leading to complexity and inflexibility.

Innovation Solution

The implementation of client interfaces that allow access to package content through access objects, enabling services to expose and access content from client packages, while using dependency control lists to manage access permissions and visibility across package hierarchies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional package mechanisms are used to structure software, then packages can hide content and provide basic access control, but the mechanism lacks flexibility for handling object generation, interfacing, and enhancements across multiple interfaces and services

Engineering Contradiction:
Improveflexibility for handling object generation, interfacing, and enhancementsVSAvoidcomplexity of package mechanism
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the package mechanism into multiple hierarchical levels (package level, interface level, object level) with distinct access control lists at each level. This allows fine-grained control over object generation, interfacing, and enhancements without requiring a complete redesign of the package mechanism, thus improving flexibility while managing complexity through structured division.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to the package mechanism by introducing interface-level access control lists that operate alongside package-level controls. This multi-dimensional approach enables independent management of access permissions for different interfaces and services, providing the needed flexibility for object generation and enhancements without linearly increasing overall system complexity.

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

2Ease of operation

If packages expose development objects through interfaces, then access to objects is enabled, but control over access permissions and visibility across package hierarchies is insufficient

Engineering Contradiction:
Improveaccess to package contentVSAvoidcontrol over access permissions
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies local quality by implementing access control lists at specific interface levels rather than uniformly across the entire package. Each interface can have its own access control list defining which development objects are accessible and under what conditions. This localized approach maintains ease of access for authorized users while providing reliable, fine-grained control over permissions and visibility in different parts of the package hierarchy.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces access control lists as intermediary structures between packages and development objects. These intermediate control mechanisms mediate access requests by evaluating permissions defined in the access control lists before granting access to development objects. This intermediary layer enhances control reliability without directly impeding ease of operation for authorized access scenarios.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If nested packages are used to structure software components, then modularity is improved, but visibility and access control across nested hierarchies becomes more difficult to manage

Engineering Contradiction:
Improvemodularity of software structureVSAvoidmanagement of visibility and access control
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent implements nested access control lists that mirror the nested package hierarchy. Each package level maintains its own access control list, and nested packages inherit or override permissions through their respective access control lists. This nested structure preserves modularity by allowing independent management of each package's visibility and access control while systematically managing the complexity through hierarchical inheritance and override mechanisms.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS7669181B2Client interfaces for packages
Publication Date: 2010.02.23 SAP SE
  • US7669181B2 patent drawing
  • US7669181B2 patent drawing
  • US7669181B2 patent drawing

AI summary

A method and system for employing client interfaces for packages. In one embodiment, an access object associated with a service provided by a first package is located, where the service is seeking to access content residing at a second package. A client interface is then created at the second package using the access object. The client interface is used to provide access to the content by exposing the content to the service via the client interface.