Front-End Message Lifetime Management via Back-End Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of awareness between back-end and front-end system components in software systems leads to unfavorable message handling issues, where stateful messages become invalid but are not updated, causing inappropriate messages to be displayed to the user.

Innovation Solution

Implementing a front-end component that manages the lifetime of stateful messages by continually validating their validity before displaying them, using a process that involves querying the back-end service process for relevance and employing a mark and sweep algorithm to remove invalid messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the back-end reports stateful messages to the front-end without awareness of front-end context, then the back-end can efficiently process calls, but the front-end may display invalid messages to the user

Engineering Contradiction:
Improveback-end processing efficiencyVSAvoidmessage validity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The front-end component continuously queries the back-end service process to check whether stateful messages remain valid before displaying them to the user. This feedback mechanism allows the front-end to receive updated information about message validity without interfering with the back-end's efficient processing, thus resolving the contradiction between processing efficiency and message reliability

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The front-end component takes responsibility for validating its own received messages by implementing a validation process that queries the back-end service process. This self-service approach allows the front-end to ensure message validity independently, maintaining back-end efficiency while improving message reliability

Inventive Principle:
Principle #25Self-service

2Device complexity

If the back-end does not track front-end message reception status, then the back-end maintains system simplicity, but invalid messages may be displayed to the user

Engineering Contradiction:
Improvesystem complexityVSAvoidmessage accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system divides the message management responsibility into two segments: the back-end service process focuses on generating and reporting messages, while the front-end component focuses on validating and displaying messages. This segmentation allows the back-end to remain simple while the front-end ensures message accuracy through validation queries

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A message validation process acts as an intermediary between the back-end service process and the front-end display. This intermediary validates messages by querying the back-end service process before display, ensuring message accuracy without requiring the back-end to track front-end state, thus maintaining system simplicity

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the front-end continuously validates message validity, then message accuracy is improved, but additional communication overhead with the back-end is introduced

Engineering Contradiction:
Improvemessage validityVSAvoidvalidation overhead
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The front-end component validates message validity at periodic intervals (specifically, before displaying messages to the user) rather than continuously monitoring. This periodic validation approach ensures message accuracy while minimizing communication overhead with the back-end service process

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS7890959B2System and method for message lifetime management
Publication Date: 2011.02.15 SAP SE
  • US7890959B2 patent drawing
  • US7890959B2 patent drawing
  • US7890959B2 patent drawing

AI summary

A system and method for message lifetime management. According to an embodiment of the invention, a front-end application process identifies during a user interface interaction cycle of the front-end application process at least one stateful message reported to the front-end application process by a back-end service process during a prior user interface interaction cycle of the front-end application process, the at least one stateful message having been stored in a message buffer by the front-end application process, queries the back-end service process to determine whether the at least one stateful message is currently valid, and removes the at least one stateful message from the message buffer if it is determined not to be currently valid.