OS Connection Capability Mapping for Mobile Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices running different operating systems face challenges in directly mapping application requirements to specific types of mobile data connections, as these requirements are expressed in OS-specific ways, leading to inconsistencies in connection parameters such as DNN, S-NSSAI, and SSC mode.
Innovation Solution
The introduction of a 'Connection Capability' parameter, which is OS-independent, allows for the association of OS-specific application requirements with 3GPP-specific parameters through routing policy rules, enabling UEs to determine the appropriate mobile data connection type by mapping OS-specific requirements to OS-independent capabilities and applying corresponding URSP rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If OS-specific connection capability parameters are used to establish network connections, then application requirements can be directly mapped to connection types, but inconsistencies arise across different operating systems leading to mapping failures
Solution Approach 1:
The patent introduces an intermediary mapping mechanism that translates OS-specific connection capability parameters (Android/iOS specific values) into standardized 3GPP connection parameters. This intermediary layer allows applications to request connections using their native OS parameters while ensuring consistent mapping to standardized network connection types across different operating systems, thereby resolving the inconsistency issue.
Solution Approach 2:
The patent transforms connection capability parameters from OS-specific forms (with different value systems for Android and iOS) into a unified 3GPP standardized form. By changing the parameter representation from platform-dependent to platform-independent, the system achieves consistent connection establishment across different operating systems while maintaining adaptability to various application requirements.
2Manufacturing precision
If routing policy rules are created for each OS-specific connection capability, then precise control over connection types is achieved, but the complexity of managing multiple OS-specific rules increases
Solution Approach 1:
The patent creates a universal routing policy rule structure that handles multiple OS-specific connection capabilities through a single standardized framework. Instead of maintaining separate rule sets for each operating system, the universal rules accept standardized 3GPP parameters that represent various OS-specific capabilities, allowing one rule set to serve multiple OS platforms and reducing management complexity while maintaining precise connection control.
Solution Approach 2:
The standardized 3GPP connection parameters act as an intermediary layer between OS-specific application requirements and routing policy rules. This intermediary representation allows routing rules to operate on a unified parameter set rather than dealing with multiple OS-specific parameter variations, thereby simplifying rule management while preserving precise control over connection type selection.
Data Source
AI summary
Apparatuses, methods, and systems are disclosed for determining what type of network connection to establish from an operating system (“OS”) specific connection capability. One apparatus includes a processor and a transceiver that communicates with a mobile communication network over one or more access networks. The processor receives a first request to establish a network connection. Here, the first request includes a first connection capability, the first connection capability being an OS-specific parameter indicating a preferred connection characteristic. The processor selects a routing policy rule based on the first connection capability and sends (via the transceiver) a second request to the mobile communication network to establish a first type of network connection. Here, the first type of network connection is indicated by the selected routing policy rule.