Wireless Database Management via Automated Rule Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing and updating wireless communication databases is complex and time-consuming due to the large volume of data and the risk of unintended system disruptions from changes, making it difficult for technicians to locate and modify data fields without affecting other parts of the system.

Innovation Solution

Implementing a system of rules within the database management system that automatically determines whether proposed changes will violate these rules, allowing for scheduled or immediate implementation while providing notifications and overriding options for troubleshooting purposes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a technician manually locates and updates data fields in the database, then the database can be modified, but the process is time-consuming and prone to human error

Engineering Contradiction:

Improvedatabase update efficiencyVSAvoidtime to locate and modify data fields

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs self-validation by automatically checking proposed changes against stored rules before implementation. The database management system autonomously determines whether changes violate integrity constraints, eliminating the need for manual verification by technicians and reducing both time and error rates.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Rules are pre-established and stored in the database before any modifications occur. These rules define acceptable changes in advance, allowing the system to quickly validate proposed modifications against predetermined criteria rather than requiring technicians to manually assess each change's impact.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If a technician modifies database fields, then system operation can be updated, but unintended negative impacts on other system portions may occur

Engineering Contradiction:

Improveability to modify databaseVSAvoidsystem operation stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system prevents harmful changes by checking proposed modifications against stored rules before they are implemented. If a proposed change would violate database integrity or cause unintended side effects, the system blocks the change in advance, thereby protecting system reliability while still allowing legitimate modifications.

Inventive Principle:

Principle #9Preliminary anti-action

Solution Approach 2:

The system provides feedback to technicians about whether proposed changes comply with established rules. This feedback mechanism allows technicians to understand the impact of their proposed modifications and adjust them accordingly, maintaining both adaptability and reliability.

Inventive Principle:

Principle #23Feedback

3Device complexity

If the database structure is maintained with multiple forms and pages, then data organization is achieved, but technicians face difficulty locating specific data fields

Engineering Contradiction:

Improvedatabase structure organizationVSAvoiddifficulty to locate data fields

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary interface between the technician and the complex database structure. This interface allows technicians to specify changes without needing to navigate the underlying forms, pages, and field hierarchy. The system handles the translation from high-level change requests to specific database modifications, reducing operational difficulty while maintaining structured organization.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If automated rule checking is implemented, then change validation is improved, but system complexity increases

Engineering Contradiction:

Improvechange validation accuracyVSAvoiddatabase management system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of rule validation into a separate, dedicated component within the database management system. Rather than embedding validation logic throughout the entire system, rules are stored as discrete entities that can be independently managed and applied. This modular approach improves validation reliability while containing the complexity increase to specific subsystems.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7680492B2Wireless communication database management

Publication Date: 2010.03.16 NOKIA OF AMERICA CORP

AI summary

A technique for updating and maintaining a wireless communication database (40) includes several features. One feature is a search capability that facilitates, for example, an individual locating appropriate portions of the database to be updated in a desired manner. A platinum data image portion includes a relational database regarding various rules governing the contents of the wireless communication database. If a proposed change will violate any of these rules, an error message is provided. If a proposed change is acceptable, it will be implemented on an automated basis. A disclosed example includes the capability of scheduling proposed changes into the future, indicating a proposed change for one particular data field and instructing an automated update of all similar or related data fields in a particular manner.