Distributed Database Flexblocks for Cloud Native Mobile Core Scalability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing mobile network cloud native architectures face scalability limitations due to the need for large tables to map identifiers related to the same User Equipment (UE) across load balancers, leading to messaging overhead and synchronization challenges.

Innovation Solution

Implementing a distributed database management system that uses flexblocks to group domain objects and allocate identifiers within contiguous ranges, allowing load balancers to route requests efficiently without maintaining detailed mappings, and utilizing worker instances to manage and perform functions on these flexblocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If load balancers use large tables to map identifiers related to the same UE, then routing efficiency is improved, but system scalability deteriorates due to messaging overhead and synchronization challenges

Engineering Contradiction:

Improverouting efficiencyVSAvoidsystem scalability

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent divides the UE identifier mapping into segments by introducing a distributed database where individual worker instances maintain mappings for specific identifier ranges (flexblocks) rather than requiring a single large centralized table. This segmentation allows the system to scale by distributing the mapping burden across multiple instances.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent transitions from a two-dimensional approach (load balancer maintaining complete identifier-to-worker mappings) to a three-dimensional approach by introducing a hierarchical structure with flexblocks as an intermediate layer. This adds a dimension of abstraction that separates the routing decision from the complete mapping, enabling scalability.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Measurement precision

If load balancers maintain detailed mappings of all identifiers, then routing precision is improved, but device complexity increases due to table size and synchronization requirements

Engineering Contradiction:

Improverouting precisionVSAvoidtable management complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts the detailed identifier mapping functionality from the load balancer and places it in the distributed database managed by worker instances. The load balancer only needs to know which flexblock an identifier belongs to, not the complete mapping details, thereby reducing its complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces flexblocks as an intermediary layer between the load balancer and the complete identifier mappings. Flexblocks act as mediators that provide sufficient routing information without requiring the load balancer to maintain detailed mappings, thus reducing complexity while preserving routing precision.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If worker instances have exclusive access to flexblocks, then data consistency is improved, but system throughput may be reduced due to locking mechanisms

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the complete identifier space into smaller flexblocks that can be independently locked and managed by different worker instances. This segmentation allows concurrent access to different flexblocks, maintaining throughput while ensuring consistency within each locked flexblock.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies partial locking by locking only the specific flexblock being modified rather than the entire identifier space. This partial action allows other worker instances to simultaneously process different flexblocks, maintaining overall system throughput while ensuring data consistency for the locked portion.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11831562B2Distributed database-driven resource management and locking in a cloud native mobile core network node architecture

Publication Date: 2023.11.28 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Systems and methods for efficient database management of non-transitory readable media, including a memory configured to store information associated with service instance requests across a plurality of distributed network resources and a processor configured to receive a service instance request, determine the first native domain object associated with the service instance request, allocate the plurality of network resources to a plurality of distributed worker instances dependent upon a first native domain object, assign the first service instance request to a first worker instance that includes a microservice instance that define service instance blocks to execute the request, and a service instance block manager configured to manage the first service instance request in conjunction with subsequent service instance requests associated with the plurality of worker instances, track running and completed requests, and allocate resources for similar requests across the distributed network nodes.