Messenger System for Backend Service Access via Natural Language

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backend systems lack convenient user navigation to source data, requiring users to know specific backend services and navigation paths to access operational data, and users must often navigate through web interfaces or backend application logins with URL knowledge.

Innovation Solution

A messenger-based system and method that receives and parses messages using natural language processing to identify and invoke backend services, allowing users to access services without needing to know the service URL or backend system navigation paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users access backend services through traditional web interfaces or backend application logins, then services can be accessed, but users must know service URLs and navigation paths which increases operation complexity

Engineering Contradiction:
Improveease of accessing backend serviceVSAvoidcomplexity of accessing backend service
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a chatbot as an intermediary between users and backend services. The chatbot receives natural language messages from users, parses them to identify service requirements, and automatically invokes the appropriate backend services. This mediator eliminates the need for users to directly interact with complex web interfaces, URLs, or navigation paths, thereby improving ease of operation while reducing operational complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the traditional mechanical interaction model (clicking through web interfaces, navigating menus, entering URLs) with a natural language processing system. Users simply type or speak their service requirements in natural language, and the system automatically translates this into service invocation commands. This substitution of mechanical navigation with linguistic processing dramatically simplifies the user experience.

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

2Loss of information

If users navigate to source data in backend systems, then operational data can be accessed, but users need to identify proper backend services and know navigation paths which increases time consumption

Engineering Contradiction:
Improveconnection to operational dataVSAvoidtime to access source data
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-establishing connections between report data and source operational data in the backend. When a user views a report, the system has already prepared the navigation path and service invocation parameters. The chatbot can immediately invoke the source service without requiring users to manually search for or navigate to the correct backend service, thereby reducing time loss while maintaining information connection.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by analyzing user interactions with reports and automatically providing contextual information about source data locations. When users query about operational data sources, the system responds with precise service identification and invocation instructions based on the report context, reducing the time needed to access source data while maintaining the connection between report and operational data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8260839B2Messenger based system and method to access a service from a backend system
Publication Date: 2012.09.04 SAP SE
  • US8260839B2 patent drawing
  • US8260839B2 patent drawing
  • US8260839B2 patent drawing

AI summary

What is described is a system and method for accessing a backend service. The method includes receiving a message at a client; parsing the message into parts of the message using a natural language processor; interpreting the parts of the message; identifying a service and a backend system based on the interpreted parts of the message; and invoking the service from the backend system.