Shared Data Layer for Mobile Network Location Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy mobile network architectures face high signaling loads and complexity due to messaging-based designs, limiting fine-grained location reporting to a limited number of users and impacting multiple network entities, which is undesirable for 5G network optimization.
Innovation Solution
A data-centric architecture with a Shared Data Layer (SDL) is introduced, allowing data sharing across network entities and enabling optimized signaling flows, reducing network complexity and signaling load by storing subscriber, session, and mobility data in the data plane, and using simplified stateless Virtualized Network Functions (VNFs) to manage user location changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If messaging-based architecture is used for location reporting, then network entities can communicate location information, but signaling load and network complexity increase significantly
Solution Approach 1:
The patent extracts the location information from traditional messaging-based signaling flows and places it into data plane traffic. Specifically, location information is embedded in GTP-U headers or payload data traffic, separating the location reporting function from the control plane signaling, thereby reducing signaling load while maintaining reporting capability
Solution Approach 2:
The patent introduces a database as an intermediary component that stores and manages location information. The database receives location updates from network entities and provides location data to application entities, eliminating the need for direct messaging between multiple network entities and reducing overall signaling complexity
2Measurement precision
If fine-grained location reporting is implemented for all users, then location accuracy improves, but signaling load becomes unsustainable
Solution Approach 1:
The patent creates a centralized copy of location information in the database, which can be accessed by multiple application entities without requiring additional signaling for each access. This single source of truth eliminates redundant location reporting messages while maintaining fine-grained location tracking for all users
Solution Approach 2:
The database serves multiple functions simultaneously: it stores location information, manages subscriptions from multiple application entities, provides location data to numerous consumers, and handles updates from various network entities. This multi-functional approach supports fine-grained reporting for all users through a single infrastructure
3Adaptability or versatility
If location change reporting is activated for multiple entities, then comprehensive location tracking is achieved, but the number of impacted network entities increases
Solution Approach 1:
The patent extracts the location data management function from multiple network entities and centralizes it in the database. Application entities subscribe to location changes at the database level rather than interacting with multiple network entities, reducing the number of impacted entities while maintaining comprehensive tracking coverage
Solution Approach 2:
The database acts as an intermediary that consolidates location tracking requests from multiple application entities. Instead of each entity independently interacting with various network nodes, they all interface with the single database, which manages the complexity of comprehensive location tracking
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of the invention include a database, referred to as Shared Data Layer SDL, of a mobile network, said database configured to: - support data sharing between mobile network entities, said data including data related to user location change reporting, said mobile network entities including at least one entity, such as RAN entity or CN entity such as CCF, referred to as serving entity, and at least one entity needing User location Information, referred to as application entity, such as Policy controller referred to as PCRF or API exposure Function referred to as SCEF.