Logical Database Locking for Concurrent LNP Record Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database locking mechanisms for local number portability (LNP) databases are ineffective in preventing corruption or invalidation of records during concurrent operations, particularly when multiple service providers access and update records.

Innovation Solution

A logical locking mechanism that locks records within the LNP database based on item types and values, using a lock manager to manage and control access, ensuring that records are not corrupted or invalidated during read/write operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If typical database locking mechanisms are used in LNP database, then data access control is provided, but records are corrupted or invalidated during concurrent operations

Engineering Contradiction:
Improvedata integrityVSAvoidconcurrent access capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a lock indicator field as an intermediary mechanism between multiple service providers accessing the LNP database. This lock indicator acts as a mediator that coordinates access between concurrent operations, allowing one service provider to lock a record by setting the indicator while other service providers check the indicator before accessing the same record, thereby preventing corruption while maintaining concurrent access capability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical database locking mechanisms with a logical lock indicator field stored within the database record itself. Instead of using external locking systems or primary key-based locks, the solution uses a dedicated field (lock indicator) that can be set and checked through normal database operations, substituting complex mechanical locking systems with a simpler field-based approach

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

2Reliability

If lock indicator field is added to database record, then concurrent access control is improved, but device complexity increases

Engineering Contradiction:
Improveconcurrent operation safetyVSAvoiddatabase structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The lock indicator field serves multiple functions: it acts as both a data integrity marker and a locking mechanism for concurrent access control. By making this field multi-functional, the patent avoids adding separate complex locking structures, thereby improving concurrent operation safety without proportionally increasing database structure complexity

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

Solution Approach 2:

The patent changes the state of an existing database field (the lock indicator) between different values (e.g., locked/unlocked states) to control access. This parameter-based approach allows the system to implement locking functionality by simply changing field values rather than adding complex structural elements, thus improving reliability while minimizing complexity increase

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250252078A1Database locking using logical lock mechanism
Publication Date: 2025.08.07 NEUSTAR INC
  • US20250252078A1 patent drawing
  • US20250252078A1 patent drawing
  • US20250252078A1 patent drawing

AI summary

Systems and methods for locking databases during database operation, such a logical mechanisms for locking a local number portability (LNP) database associated with the Number Portability Administration Center (NPAC), are described. For example, the systems and methods may utilize various logical constructs, such as parameters that identify items or records within a database (e.g., object type and value information). and lock records that include such parameters.