Wireless Reachability Management via RMF for Privacy-Preserving Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in managing reachability across devices with different access technologies while preserving user privacy and efficiently establishing connections between them.
Innovation Solution
The Reachability Management Function (RMF) architecture allows for the association of devices with unique user identifiers, alternative communication methods, and privacy-preserving connections, using temporary secure reachability tokens (TSR) to facilitate communication between wireless transmit/receive units (WTRUs) with different access technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional direct identifier sharing is used to establish connections between devices, then connection establishment is simple and direct, but user privacy is compromised and security is reduced
Solution Approach 1:
The patent introduces a Reachability Management Function (RMF) as an intermediary entity that mediates between calling and called devices. The RMF receives reachability requests, validates them against operator policies, and provides authorized access information without exposing direct device identifiers. This intermediary mechanism enhances security and privacy while managing the complexity of cross-technology reachability centrally.
Solution Approach 2:
The patent segments the reachability management process into distinct functional components: device identification, policy validation, authorization checking, and connection facilitation. By dividing the complex reachability management into modular segments handled by the RMF, the system achieves better security control without overwhelming individual devices with complexity.
2Adaptability or versatility
If multiple access technologies are supported for reachability, then connectivity versatility is improved, but device and network complexity increases
Solution Approach 1:
The RMF is designed as a universal function that handles reachability requests across multiple access technologies (3GPP and non-3GPP networks). Instead of implementing separate management mechanisms for each technology, the single RMF provides multi-functional support, reducing overall system complexity while maintaining broad compatibility.
Solution Approach 2:
The RMF acts as a technology-agnostic intermediary that abstracts the complexities of different access technologies from individual devices. Calling and called devices interact with the RMF through standardized interfaces, allowing the RMF to handle technology-specific complexities centrally while presenting a unified interface to users.
3Ease of operation
If device identifiers are shared openly to enable communication, then connection establishment is simplified, but user privacy is compromised
Solution Approach 1:
The RMF serves as a privacy-preserving intermediary that enables connection establishment without direct identifier exposure. The called device registers its reachability preferences with the RMF, and the calling device submits requests to the RMF. The RMF validates requests and provides authorized access information, allowing connections to be established while keeping device identifiers confidential and preventing unauthorized access.
Data Source
AI summary
A first wireless transmit/receive unit (WTRU) may send a call request to an AMF. The call request may indicate a known identifier to reach a second WTRU. The first WTRU may receive a call response that indicates a call rejection and/or that the second WTRU has configured alternate reachability methods. The first WTRU may send a reachability request to a reachability management function (RMF). The reachability request may include a known identifier, an identifier of the first WTRU, and/or information about one or more capabilities of the first WTRU. The first WTRU may receive a reachability response from the RMF that indicates the second WTRU can connect with the first WTRU. The reachability response may include information to connect with the first WTRU. The first WTRU may send a call request to an AS. The first WTRU may receive a call response that indicates a call is established.