OData Service Execution Flow with Runtime Authentication Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Open Data (Odata) protocols lack flexibility in modifying parameters during client request handling, limiting system administrators' ability to add authentication steps or modify data execution processes.

Innovation Solution

The implementation of a system that converts data source metadata to an entity data model, generates a service operation execution flow, and allows editing of this flow to include authentication options, enabling flexible modification of service operations such as client authentication before result delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Odata protocol follows standard implementation, then data communication is simple and straightforward, but system administrators cannot add authentication steps or modify execution processes

Engineering Contradiction:
Improveflexibility to modify parametersVSAvoidservice operation execution flow complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the Odata service operation into distinct executable steps within an execution flow. Each step represents a discrete operation that can be individually configured, including authentication steps, data retrieval steps, and result delivery steps. This segmentation allows system administrators to add, remove, or modify specific steps without affecting the entire service operation, thereby achieving flexibility while maintaining manageable complexity through modular design.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If Odata service executes client requests directly, then response time is fast, but system administrators cannot implement authentication or modify data handling processes

Engineering Contradiction:
Improveability to add authentication stepsVSAvoidrequest handling time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by allowing system administrators to pre-configure the service operation execution flow with authentication steps and data handling procedures before client requests are received. The execution flow is defined in advance, specifying the sequence of operations including authentication verification, data retrieval, and result delivery. When a client request arrives, the pre-configured flow is executed, eliminating the need for runtime modifications and minimizing additional processing time while ensuring authentication and data handling requirements are met.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10313421B2Providing Odata service based on service operation execution flow
Publication Date: 2019.06.04 SAP SE
  • US10313421B2 patent drawing
  • US10313421B2 patent drawing
  • US10313421B2 patent drawing

AI summary

A method and system for providing an OData service based on a service operation execution flow is described. Initially a data source metadata is converted to an entity data model. Based on the entity data model, the service operation execution flow is generated that displays a process for executing a service operation. Next, one or more runtime configuration data are received to edit the generated service operation execution flow. The edited service operation execution flow defines a communication between a data source and a client requesting execution of the service operation. Finally, based on the edited service operation execution flow and the entity data model the Odata service is published to process a client request for executing the service operation.