Dynamic Endpoint Generation for Business Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems require manual generation of endpoints for business objects, which is time-consuming, prone to errors, and becomes stale if not updated, making it difficult for remote client devices to access and consume dynamic business objects efficiently.

Innovation Solution

The method involves automatically generating and publishing endpoint information, such as contracts, when a business object is created or requested, allowing client devices to access and consume business objects without manual intervention, using dynamic endpoint generation and brokerage technologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual endpoint generation is used, then endpoint information can be precisely controlled, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improveendpoint information accuracyVSAvoidendpoint generation time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system automatically generates endpoint information by extracting metadata from business object definitions without requiring manual intervention. The endpoint generator autonomously creates contracts, addresses, and binding information based on the business object's properties and methods, eliminating the need for manual endpoint creation while maintaining accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical processes of endpoint creation with automated computational processes. Instead of manually constructing endpoint definitions, the system uses algorithms to automatically extract business object metadata and generate corresponding endpoint information, significantly reducing time and effort.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Device complexity

If manual endpoint generation is used, then complex endpoint configurations can be precisely controlled, but the complexity and difficulty of the process increases

Engineering Contradiction:
Improveendpoint configuration capabilityVSAvoidendpoint creation ease
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The endpoint generator performs self-service by automatically analyzing business object definitions and generating appropriate endpoint configurations. The system autonomously determines contract details, binding information, and address formats without requiring user intervention, making the process simple while maintaining comprehensive configuration capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent segments the endpoint generation process into distinct automated steps: extracting business object metadata, generating contracts, creating bindings, and forming addresses. This segmentation allows complex endpoint configuration to be achieved through multiple simple automated operations rather than a single complex manual process.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If static endpoint definitions are used, then endpoint information can be thoroughly documented, but the information becomes stale when business objects change

Engineering Contradiction:
Improveendpoint information freshnessVSAvoidendpoint update automation
Core Design Contradiction:
Loss of informationVSExtent of automation

Solution Approach 1:

The system transitions from static endpoint definitions to dynamic endpoint generation. Endpoints are automatically regenerated whenever business object definitions change, ensuring that endpoint information always reflects the current state of business objects. This dynamic approach eliminates staleness while maintaining thorough documentation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements feedback mechanisms where changes to business object definitions automatically trigger regeneration of endpoint information. The system continuously monitors business object updates and feeds this information back to the endpoint generator, which then produces updated endpoint definitions, ensuring information freshness without manual intervention.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If dynamic business objects are created, then flexibility and adaptability are improved, but the ability to access and consume them by remote clients becomes more difficult

Engineering Contradiction:
Improvebusiness object flexibilityVSAvoidclient access ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces endpoint information as an intermediary layer between dynamic business objects and remote clients. This intermediary automatically translates the internal structure of dynamic business objects into standardizable endpoint definitions that clients can easily consume, bridging the gap between flexibility and client accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces manual endpoint configuration with automated generation that translates dynamic business object definitions into client-friendly endpoint information. This automated translation mechanism maintains business object flexibility while presenting a standardized, easy-to-consume interface to remote clients.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9729394B2Methods and apparatus for allowing user configuration of dynamic endpoint generators and dynamic remote object discovery and brokerage
Publication Date: 2017.08.08 NINTEX USA INC
  • US9729394B2 patent drawing
  • US9729394B2 patent drawing
  • US9729394B2 patent drawing

AI summary

A method for allowing user configuration of an endpoint for consuming a business object includes: loading a definition of the business object, the definition having properties and methods; mapping the definition to endpoint-supported protocols; and allowing user configuration of the endpoint based upon at least one of: (i) services configuration, (ii) protocol configuration, or (iii) managed configuration.