WTRU Registration Updates for Congestion-Aware Unavailability Periods
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems lack effective support for unavailability periods during non-3GPP access, leading to inefficiencies and potential congestion issues when wireless transmit/receive units (WTRUs) experience unavailability events.
Innovation Solution
Implementing a device that sends registration requests with unavailability duration information, receives registration accept messages indicating availability status, determines unavailability events, and sends registration update requests when available, while managing congestion through duration adjustments and rejection messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the WTRU sends frequent registration update requests to inform the network of availability, then the network can maintain accurate device status information, but network congestion increases
Solution Approach 1:
The WTRU proactively informs the network about upcoming unavailability periods before they occur by including unavailability duration information in the initial registration request. This preliminary notification allows the network to prepare and avoid unnecessary communication attempts during the unavailability period, reducing subsequent signaling traffic and congestion.
Solution Approach 2:
Instead of continuous or frequent updates, the system uses periodic registration updates only when the unavailability period ends. The WTRU sends a registration update request at specific intervals (when available), rather than continuously reporting status, which reduces overall signaling traffic while maintaining necessary network awareness.
2Productivity
If the network sends rejection messages with back-off durations to control congestion, then network congestion is reduced, but the WTRU availability responsiveness deteriorates
Solution Approach 1:
The WTRU provides preliminary information about unavailability duration in the initial registration request, allowing the network to anticipate when the WTRU will be unavailable and when it will become available again. This eliminates the need for the network to send rejection messages with back-off durations, as the WTRU proactively manages its own availability timing.
Solution Approach 2:
The system implements a feedback mechanism where the network responds to the unavailability duration information provided by the WTRU. The network can acknowledge the unavailability period and adjust its behavior accordingly, creating a coordinated system that reduces congestion while maintaining responsiveness to actual availability changes.
3Reliability
If the WTRU remains registered during unavailability periods, then the network can quickly reconnect when available, but unnecessary signaling traffic increases causing congestion
Solution Approach 1:
The WTRU performs periodic registration updates only at specific intervals (when becoming available), rather than maintaining continuous registration signaling. This periodic approach reduces unnecessary signaling traffic during unavailability periods while ensuring the network is informed when the WTRU is ready to reconnect.
Solution Approach 2:
The WTRU informs the network in advance about the duration of unavailability periods, allowing the network to maintain the registration state without requiring continuous confirmation signaling. This preliminary notification reduces the need for frequent keep-alive or status verification messages during the unavailability period.
Data Source
AI summary
A device (e.g., a WTRU, network device, such as a device comprising an access and mobility function (AMF)) may perform one or more of the following actions. The device may send a registration request via non-access stratus signaling. The registration request may include a first duration. The device may receive a registration accept message. The registration accept message may indicate whether the device is to inform the network entity when the WTRU is available. The device may determine that an unavailability event has ended. The WTRU may determine whether to inform the network entity that the WTRU is available. The device may send a registration update request, for example, based on a determination that the unavailability event has ended and a determination that the WTRU is to inform the network entity when the WTRU is available. The registration update request may indicate that the WTRU is available.