Auxiliary Back-Off Procedure for Wireless Service Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless network technologies, such as 3GPP LTE, do not effectively manage battery and network resource depletion in bad network conditions, as they lack defined back-off procedures for undefined service request reject codes and situations where requests are ignored by the network, leading to repeated service requests and resource wastage.
Innovation Solution
Implementing an auxiliary back-off procedure that allows devices to selectively enable or disable a back-off mechanism based on network conditions, using a maximum service request attempt counter and timer to control service request transmissions, and allowing the procedure to be used for undefined reject causes and situations where requests are ignored.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If devices continuously send service requests to the network without back-off procedures, then network service availability is improved, but battery consumption and network resource depletion worsen in bad network conditions
Solution Approach 1:
The patent implements dynamic back-off procedures that adjust service request transmission timing based on network conditions. When network conditions are poor, the device dynamically increases the back-off period before sending retry requests. This dynamic adjustment prevents continuous transmission that would deplete battery, while still maintaining service availability by retrying when conditions improve.
Solution Approach 2:
The patent changes the time parameter between service requests based on network conditions. By modifying the back-off timer duration according to whether network conditions are good or bad, the system optimizes the balance between maintaining service availability and conserving battery energy during unfavorable network states.
2Reliability
If devices continuously send service requests to the network without back-off procedures, then network service availability is improved, but network resource depletion worsens in bad network conditions
Solution Approach 1:
The patent implements dynamic back-off procedures that adjust service request transmission timing based on network conditions. When network conditions are poor, the device dynamically increases the back-off period before sending retry requests. This dynamic adjustment prevents continuous transmission that would deplete battery, while still maintaining service availability by retrying when conditions improve.
Solution Approach 2:
The patent changes the time parameter between service requests based on network conditions. By modifying the back-off timer duration according to whether network conditions are good or bad, the system optimizes the balance between maintaining service availability and conserving battery energy during unfavorable network states.
3Use of energy by moving object
If devices implement defined back-off procedures only for specific reject codes, then battery conservation is improved for known conditions, but service request handling worsens for undefined reject codes and ignored requests
Solution Approach 1:
The patent implements a universal back-off mechanism that handles multiple types of service request failures through a single procedure. Rather than requiring separate defined back-off procedures for each specific reject code, the universal mechanism applies to all undefined reject codes and ignored requests, providing adaptable handling while conserving battery energy across diverse failure scenarios.
Data Source
AI summary
The embodiments of the disclosure include methods and apparatus that provide back-off procedures for avoiding device/network resource depletion in bad network conditions. A device user may selectively enable an auxiliary back-off procedure that extends the time between network service requests. For example, the auxiliary back-off procedure may be used if the device determines an attach request is unsuccessful when a reject message is received from the network and the reject message indicates a reject cause for which the device has no defined back-off to follow. The auxiliary back-off procedure may be also be used if the device determines that a service request is unsuccessful when the service request is ignored, i.e. no response is received from the network, or, when a service request reject is received from the network and the reject message indicates a reject cause for which the device has no defined back-off to follow.


