BQL Engine Translating Structured Queries to Native Commands

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to modifying data in business systems require extensive coding and generate high network traffic due to fixed granularity and the need for multiple data calls, making it inefficient and cumbersome to manage data integrity and security.

Innovation Solution

A Business Query Language (BQL) engine translates structured queries into native commands for backend business objects, allowing client applications to define queries and updates efficiently, reducing the amount of code and network traffic by using a structured query language and a fast search infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional client proxies are used to modify data in backend applications, then data security and integrity are maintained, but large amounts of code are required and high network traffic is generated

Engineering Contradiction:
Improvedata integrityVSAvoidcode complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service layer with standardized service interfaces that act as an intermediary between the user interface and backend applications. This service layer consolidates data modification logic, reducing the need for extensive client proxy code while maintaining data integrity through centralized service methods that handle multiple data calls efficiently.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service layer provides universal service methods that can handle multiple types of data modifications through a common interface. Instead of requiring separate client proxy implementations for each backend application, the standardized services provide multi-functional capabilities that work across different data sources, reducing overall code complexity.

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

2Reliability

If multiple data calls are made to maintain data integrity during data modification, then data consistency is preserved, but network traffic increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple data modification operations into unified service methods. Instead of making separate data calls for each modification, the service layer combines related operations into single service calls that maintain data consistency while reducing the total number of network transactions required.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The service layer performs preliminary validation and preparation of data modifications before executing them. By pre-processing data and determining the necessary modifications in advance, the system can execute fewer, more efficient network calls that maintain consistency without generating excessive traffic.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If client proxies provide fixed granularity for data modifications, then implementation is simplified, but flexibility in defining modification granularity is lost

Engineering Contradiction:
Improveimplementation simplicityVSAvoidmodification granularity flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The service layer provides dynamic granularity control for data modifications. Service methods can be designed to operate at different levels of granularity depending on the specific requirements, allowing the system to adapt between fine-grained and coarse-grained modifications without requiring separate client proxy implementations for each granularity level.

Inventive Principle:
Principle #15Dynamics

4Ease of operation

If user interfaces directly access backend applications without a service layer, then access is straightforward, but security and data integrity become problematic

Engineering Contradiction:
Improveaccess easeVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The service layer acts as a secure intermediary between user interfaces and backend applications. It provides a standardized interface that maintains ease of access while enforcing security policies and data integrity rules centrally, eliminating the need for complex client proxy security implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7895226B2System and method for translating and executing update requests
Publication Date: 2011.02.22 SAP SE
  • US7895226B2 patent drawing
  • US7895226B2 patent drawing
  • US7895226B2 patent drawing

AI summary

Methods and systems for converting standardized, structured update requests into native business object commands are provided. The structured update requests may be defined in a business object-specific structured query language (BQL). A BQL engine may translate the structured update request into a command formatted for use by the appropriate business object or a programming interface in communication with the business object.