Shadow Consolidated Network Repository for Subscriber Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network architectures face difficulties in managing and accessing subscriber information across core-network-related and service-related databases, with restrictive policies and complex access management, making it cumbersome for third-party service providers to access and update subscriber data efficiently.
Innovation Solution
A shadow consolidated network repository (S-CNR) is introduced, which mirrors subscriber information from the main consolidated network repository (M-CNR) and provides a standardized format for third-party application service providers, allowing secure access while maintaining the integrity of core-network-related databases, with open APIs and caching functions to manage and synchronize data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If third party service providers are given direct access to core-network-related databases, then access efficiency is improved, but security and reliability of the core network deteriorate
Solution Approach 1:
The patent creates a copy of the consolidated network repository (CNR) called the service-related repository (S-R). This copy contains mirrored subscriber information and is specifically designed for third-party service providers. The S-R allows efficient data access while the original CNR maintains security controls, resolving the contradiction between access efficiency and security.
Solution Approach 2:
The service-related repository acts as an intermediary between third-party service providers and the core-network-related databases. It provides a buffered layer that mirrors data from the CNR, enabling third parties to access information without direct connection to the core network, thus maintaining security while improving access efficiency.
2Adaptability or versatility
If separate data schemas are used for each service-related database, then adaptability to different service providers is improved, but device complexity and management difficulty increase
Solution Approach 1:
The service-related repository uses a universal standardized data schema that can serve multiple third-party service providers simultaneously. This single schema handles diverse service provider needs, eliminating the complexity of maintaining separate schemas for each provider while preserving adaptability through configuration rather than structural variation.
Solution Approach 2:
The patent merges all service-related databases into a single service-related repository that shares common data schemas. This consolidation reduces management complexity by unifying the data structure across all service providers while maintaining the ability to serve diverse service types through standardized interfaces.
3Stability of the object's composition
If the CNR and independent data repositories are separately provisioned and maintained, then operational independence is improved, but ease of manufacture and maintenance deteriorate
Solution Approach 1:
The service-related repository is provisioned as a copy of the consolidated network repository, automatically inheriting its structure and configuration. This copying mechanism simplifies provisioning and maintenance while preserving operational independence, as the S-R can be deployed independently without requiring separate complex setup procedures.
Data Source
AI summary
A service-related repository provides access to subscriber information to third party application service providers without providing the third party application service providers with access to a main network repository. The service-related repository stores subscriber information in a standardized format and in a format tailored for each third party application service provider. The subscriber information stored within the service-related repository mirrors network subscriber information stored within the main network repository. The main network repository is distinct from a secondary repository that includes the service-related repository. The secondary repository also includes a subscriber-related repository for storing the subscriber information in a standardized format.


