Automatic Service Extension via Registry Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data access services require significant changes and disruptions when additional fields are added to customer account information, necessitating new services that can be similar or replace existing ones, leading to complexities in software development and client configuration.

Innovation Solution

The system automatically extends data access services by identifying an extension service using additional registry entries without modifying the original service implementation or registry entries, allowing seamless transition and new interfaces without disrupting clients or requiring coding changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If additional fields are added to customer account information, then service functionality is improved, but device complexity increases due to requiring new services and modifications to existing services

Engineering Contradiction:
Improveservice functionalityVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments service functionality into extensible components where additional fields are added as separate extension services rather than modifying the core service. This allows the service to be divided into base functionality and optional extensions, reducing overall system complexity while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal service extension mechanism that can handle multiple types of additional fields through a common registry-based approach. Instead of creating specialized services for each field addition, a single extensible service framework handles diverse functionality requirements.

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

2Adaptability or versatility

If new services are defined to accommodate additional fields, then service adaptability is improved, but ease of operation deteriorates due to requiring client reconfiguration

Engineering Contradiction:
Improveservice adaptabilityVSAvoidclient configuration
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service through automatic service extension detection. The system automatically identifies and applies appropriate service extensions based on registry entries without requiring client intervention or reconfiguration, making the service adapt to new fields autonomously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses preliminary action by pre-registering service extensions in a registry before they are needed. When additional fields are added, the corresponding extension services are already registered and automatically selected, eliminating the need for client reconfiguration at the time of field addition.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If existing services are modified to include new fields, then service functionality is improved, but reliability deteriorates due to potential disruptions to existing clients

Engineering Contradiction:
Improveservice functionalityVSAvoidservice stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies the nested doll principle by placing extension services within the existing service framework. Extension services are nested alongside the base service, with the system automatically selecting and combining them. This nesting allows functionality expansion while preserving the stability of the original service implementation.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a service registry and automatic selection process. This intermediary layer sits between the client requests and the actual service implementations, automatically routing requests to the appropriate base service and extension service combinations, thereby isolating clients from modifications.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If service registry entries are modified to add new services, then service adaptability is improved, but loss of information increases due to potential errors in modifying existing registry entries

Engineering Contradiction:
Improveservice extensibilityVSAvoidregistry integrity
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments registry entries into separate base service definitions and extension service definitions. This segmentation prevents modifications to existing base service registry entries, as extensions are added as distinct, separate entries that reference the base service rather than modifying it directly.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10104200B2Automatic service extensibility
Publication Date: 2018.10.16 SAP SE
  • US10104200B2 patent drawing
  • US10104200B2 patent drawing
  • US10104200B2 patent drawing

AI summary

The disclosure generally describes computer-implemented methods, software, and systems, including a method for automatically extending a service associated with data access. A request is received from a client, the request being for data associated with a first service. The first service is identified by a service identifier included in the request and defining a first behavior associated with the first service and use of the requested data. Using the service identifier, an extension service is identified that is associated with the first service. The identifying occurs automatically based on additional registry entries for the extension service, without modifying original registry entries for the first service, and without modifying a first service implementation associated with the first service. Data responsive to the received request is provided to the client. The data is provided according to a second behavior associated with the extension service.