Proximity Request Validation Using Application Layer User ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Proximity-based Services (ProSe) communication, users initiating proximity requests do not know the identity of the target user, and the proximity request validation process can be stuck if the target user is unresponsive, leading to inefficiencies and privacy concerns.
Innovation Solution
A method where a network entity provides the application layer user ID (ALUID) of the discoverer to the discoveree, along with a validating response indicator, allowing the user to respond to proximity requests and ensuring the process is not stuck due to unresponsiveness, by transmitting proximity request validation messages based on the validating operation or a timer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the network entity provides the application layer user ID (ALUID) of the discoverer to the discoveree, then user privacy is enhanced by revealing the initiator's identity, but the system complexity increases due to additional message components
Solution Approach 1:
The proximity request validation message is segmented into distinct components: the ALUID field containing the discoverer's identity, the validating response indicator field, and other necessary parameters. This segmentation allows the identity information to be clearly provided without overwhelming the message structure, resolving the contradiction between information completeness and structural simplicity.
Solution Approach 2:
The discoverer's ALUID is extracted as a separate, dedicated field within the proximity request validation message. This extraction ensures that the identity information is prominently provided to the discoveree while maintaining a clean, organized message structure that doesn't become unnecessarily complex.
2Reliability
If the proximity request validation process waits for user response, then privacy protection is maintained by requiring explicit consent, but system efficiency deteriorates due to potential process stalls
Solution Approach 1:
The validation process dynamically adapts its behavior based on the validating response indicator. When the indicator specifies 'proceed without response,' the system automatically continues the validation without waiting for user input, improving efficiency. When the indicator requires explicit consent, the system waits for user response, maintaining privacy protection. This dynamic adjustment resolves the contradiction between reliability and productivity.
Solution Approach 2:
The system changes the parameter of user response requirement based on the validating response indicator value. By modifying this parameter dynamically, the system can switch between requiring explicit user consent and proceeding automatically, thereby balancing privacy protection reliability with validation process efficiency in different scenarios.
3Reliability
If the system requires explicit user validation for proximity requests, then security is improved, but the operation time increases due to waiting for user response
Solution Approach 1:
The validation time requirement dynamically changes based on the validating response indicator. For indicators requiring explicit consent, the system waits for user response, ensuring security. For indicators allowing automatic proceeding, the system reduces validation time by not waiting, thus resolving the contradiction between security and response time.
Solution Approach 2:
The system performs preliminary assessment of the validating response indicator before initiating the user validation wait. By预先 determining whether user response is required based on the indicator, the system avoids unnecessary waiting time while maintaining security requirements, effectively resolving the time-security contradiction.
Data Source
AI summary
The disclosure proposes a proximity request validating method, a UE using the same method, an identity request method, and a network entity using the same method. In one of the exemplary embodiments, a UE may receive a proximity request validation message of a D2D discovery using the transceiver module, wherein the proximity request validation message comprises an application layer user ID of a discoverer and a validating response indicator. The UE may then transmits a proximity request validation response message in response to the proximity request validation message using the transceiver module according to a validating operation in response to receiving the validating operation, and transmits the proximity request validation response message using the transceiver module according to the validating response indicator in response to the validating operation is not received.