Email-Based Database Record Update via SOA Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems do not efficiently allow users to update records stored in a database server using email, limiting convenience and accessibility for users who need to modify data from remote locations or outside the corporate network.

Innovation Solution

A system that retrieves records from a database server, sends them via email to users for modification, and propagates the changes back to the database server using a Service-Oriented Architecture (SOA) server, which interfaces with email and workflow blocks to facilitate user interaction and update propagation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional database update methods are used, then data security and control are maintained, but user accessibility and convenience are limited

Engineering Contradiction:
Improveuser accessibilityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an email server as an intermediary between users and the database server. Users send update requests via email to the database server, which processes these requests through a structured protocol. This intermediary mechanism allows users to access and update database records remotely without direct network connection to the corporate system, thereby improving accessibility while maintaining security through controlled processing of email-based requests.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If email-based update system is implemented, then user convenience and remote accessibility are improved, but system complexity increases

Engineering Contradiction:
Improveuser convenienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The database server is enhanced with multi-functionality to handle both traditional database operations and email-based update requests. The system can process standard database queries while also receiving, parsing, and executing update requests via email. This universal capability allows the same system to serve multiple purposes without requiring separate infrastructure, thereby managing complexity while providing convenient email-based access.

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

Solution Approach 2:

The update process is segmented into distinct components: email reception module, request parsing module, validation module, and execution module. Each component handles a specific aspect of the email-based update process, making the overall system more manageable and maintainable. This segmentation allows the complex email processing functionality to be integrated into the database server in a structured, modular way.

Inventive Principle:
Principle #1Segmentation

3Productivity

If multiple records are updated individually, then data accuracy is maintained, but time efficiency decreases

Engineering Contradiction:
Improveupdate efficiencyVSAvoiddata accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent enables multiple database records to be updated within a single email message. The email can contain multiple update requests targeting different records, which are processed together in one transaction. This combining approach significantly improves productivity by reducing the number of separate update operations required, while the transactional nature of the processing ensures data accuracy through atomic commit or rollback mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements a feedback mechanism where users receive confirmation emails after their update requests are processed. The confirmation includes details of the records that were successfully updated and any that failed. This feedback loop allows users to verify data accuracy and make corrections if needed, maintaining precision while enabling efficient bulk updates through the initial single email submission.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10536404B2Use of email to update records stored in a database server
Publication Date: 2020.01.14 ORACLE INT CORP
  • US10536404B2 patent drawing
  • US10536404B2 patent drawing
  • US10536404B2 patent drawing

AI summary

According to an aspect multiple records are stored in a database server. A set of records are retrieved by querying the database server. A first file is formed to contain the retrieved set of records. The first file is sent by email to a user, and a second file, with at least one of the set of records modified, is received from the user by email. The received modifications contained in the second file are propagated to the database server, upon receipt of the second file. Users may accordingly be able to effect modifications to multiple records in a single email exchange. According to another aspect, the updates are effected by using a SOA server storing a process definition to interface (send and receive emails) with the user and propagate the changes. The SOA server may contain a workflow block to interact with users based on email exchange.