Microservice Data Caching for Low-Latency 5G Service Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing 5G core network architectures face challenges in optimizing data access and processing times for micro-services, leading to increased resource consumption and operating costs due to the need for frequent interactions with shared persistence layers, which can cause conflicts and complexity.

Innovation Solution

Implementing a local cache (primary cache) within each application device to store data from a second service, allowing for rapid access and synchronization, while maintaining independence and flexibility between services, even in the presence of temporary failures or changes in the persistence layer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If micro-services frequently interact with shared persistence layers to access data, then data consistency is maintained, but processing times increase and resource consumption rises

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements local caches within micro-services that pre-load and store frequently accessed data from the shared persistence layer. This preliminary action allows micro-services to retrieve data locally without repeated interactions with the persistence layer, maintaining data consistency through periodic synchronization while significantly reducing access time and processing delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces local caches as intermediary layers between micro-services and the shared persistence layer. These caches act as mediators that hold copies of data, allowing micro-services to access data quickly while the cache management system maintains consistency with the persistence layer through background synchronization mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If micro-services frequently interact with shared persistence layers to access data, then data availability is ensured, but resource consumption increases

Engineering Contradiction:
Improvedata availabilityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent pre-loads data into local caches before it is needed by micro-services, and maintains these caches with periodically synchronized data from the persistence layer. This preliminary action ensures data availability is maintained while avoiding the continuous resource consumption that would result from frequent persistence layer interactions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Local caches serve as intermediary storage layers that reduce the burden on the shared persistence layer. By handling data access requests locally and only synchronizing with the persistence layer when necessary, the system maintains data availability while significantly reducing overall resource consumption across the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If micro-services share a common persistence layer, then data consistency is maintained, but service independence and flexibility are reduced

Engineering Contradiction:
Improvedata consistencyVSAvoidservice independence
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic persistence layer access model into distributed local caches within each micro-service. Each micro-service maintains its own local cache, which is independently managed and synchronized with the shared persistence layer. This segmentation preserves data consistency through coordinated synchronization while granting each service independence in managing its data access patterns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing each micro-service to have customized cache management strategies, synchronization policies, and data access patterns tailored to its specific requirements. While the shared persistence layer maintains overall data consistency, each service can optimize its local cache behavior independently, enhancing flexibility and adaptability.

Inventive Principle:
Principle #3Local quality

4Measurement precision

If micro-services access shared persistence layer frequently, then up-to-date data is obtained, but network latency increases

Engineering Contradiction:
Improvedata freshnessVSAvoidnetwork latency
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent pre-synchronizes data from the shared persistence layer into local caches before micro-services need to access it. This preliminary action ensures that data is already available locally in an up-to-date state, eliminating the need for frequent network trips to the persistence layer and thereby reducing network latency while maintaining data freshness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Local caches act as intermediary storage that holds synchronized copies of data from the persistence layer. This intermediary layer provides micro-services with immediate access to up-to-date data without requiring direct, frequent communication with the persistence layer, thus maintaining data freshness while significantly reducing network latency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12563125B2Entity for implementing a service in a network, application device, and method for executing an operation of a service
Publication Date: 2026.02.24 ORANGE SA
  • US12563125B2 patent drawing
  • US12563125B2 patent drawing

AI summary

An entity for implementing a service in a network, an application device, and a method for executing an operation of a service are described. An entity is configured to implement a first service implemented by a first application device of a communications network, the entity including a management module configured to acquire, via an application programming interface of a second service implemented in the network, data managed by the second service, said management module being configured to store said acquired data in a primary cache of the entity, an update module configured to update, following a modification of one of said data managed by said second service, the primary cache to reflect said modification using said programming interface, and a processing module, configured to use at least one of said data from the primary cache when executing at least one operation of the first service.