Dynamic Virtual Repository for Network Service Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network systems face high latency and infrastructure requirements due to the need for real-time access and comparison of information across numerous individual repositories for each subscriber and service, leading to increased traffic and hardware augmentation.
Innovation Solution
The system dynamically instantiates a virtual machine/repository for each user/service, synchronizing it with consolidated databases in the backend, allowing for on-demand access and reduction of infrastructure needs by creating a unified, virtualized environment with dynamic security and schema adaptation capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If individual repositories are maintained for each subscriber and service, then data access accuracy is improved, but latency increases and infrastructure requirements grow
Solution Approach 1:
The patent consolidates multiple individual service repositories into a single unified repository that serves all services and subscribers. This merging eliminates the need to query multiple separate repositories, thereby reducing latency while maintaining data access accuracy through a centralized data structure that all services can access simultaneously.
Solution Approach 2:
The unified repository is designed to serve multiple services and subscribers simultaneously with a single data structure. Instead of having dedicated repositories for each service, the universal repository provides data access to all services (call completion, browsing, texting, third-party services) through a common interface, reducing infrastructure complexity and access latency.
2Device complexity
If individual repositories are maintained for each subscriber and service, then data organization is improved, but network backhaul infrastructure requirements increase
Solution Approach 1:
The patent merges multiple service-specific repositories and their associated network infrastructure into a single unified repository. This consolidation reduces the quantity of network backhaul infrastructure required by eliminating redundant data paths and reducing the number of network hops needed to access data across different services.
Solution Approach 2:
The patent transitions from a distributed horizontal architecture (multiple separate repositories across the network) to a centralized vertical architecture (single unified repository). This dimensional change reorganizes data access from multiple scattered access points to a single centralized point, reducing network infrastructure requirements while maintaining data organization through structured access layers.
3Adaptability or versatility
If platform access is expanded to accommodate all service inquiries, then service capability is improved, but infrastructure build-up is required
Solution Approach 1:
The unified repository provides a universal data access platform that accommodates all service inquiries (call completion, browsing, texting, third-party services) through a single infrastructure. This multi-functional approach maintains high service capability and adaptability while avoiding the need for separate infrastructure builds for each service.
Solution Approach 2:
The patent implements a dynamic unified repository that can adapt to different service requirements without requiring infrastructure changes. The repository dynamically adjusts data retrieval and presentation based on service type and subscriber needs, providing high service capability through software-based adaptability rather than hardware expansion.
Data Source
AI summary
A virtual machine/function of repository is used to collect information for use in providing a particular service to a particular user in a network. The virtual machine/function of repository is dynamically instantiating in a front end of the network upon receiving a request to provision the particular service for the particular user. The collected information pertains only to providing the particular service to the particular user. The virtual machine/function of repository is synchronized with one or more consolidated databases in a back end of the network. The virtual machine/function of repository is deleted upon discontinuation of the particular service for the particular user.