Device-Specific SIB Validity Times for DRX Power Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems use a uniform system information block (SIB) validity time for all devices, which can lead to inefficient power consumption and suboptimal resource allocation due to varying device types and discontinuous reception (DRX) cycles, particularly affecting low-power devices like IoT devices.
Innovation Solution
Implementing device-specific system information validity times tailored to the device type or DRX cycle, allowing UEs to monitor system information at frequencies appropriate to their capabilities and operations, thereby optimizing resource allocation and reducing power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a uniform SIB validity time is used for all devices, then system information consistency is maintained, but power consumption efficiency deteriorates for low-power devices
Solution Approach 1:
The patent applies local quality by assigning different SIB validity times to different device types and DRX cycles. Instead of a uniform validity time for all devices, the system tailors the validity time to specific device characteristics, allowing low-power devices to use longer validity times while other devices use shorter ones, thus optimizing power consumption for each device category while maintaining system information consistency where needed.
Solution Approach 2:
The patent changes the parameter of SIB validity time from a fixed uniform value to a variable value that depends on device type and DRX cycle. This parameter change enables the system to adapt the validity time to match different device power consumption patterns and monitoring capabilities, resolving the contradiction between consistency and power efficiency.
2Device complexity
If a uniform SIB validity time is used for all devices, then implementation simplicity is maintained, but resource allocation optimality deteriorates
Solution Approach 1:
The patent introduces local quality by differentiating SIB validity times based on device type and DRX cycle characteristics. This differentiation enables optimized resource allocation for each device category without significantly complicating the overall system implementation, as the network entity simply assigns appropriate validity times based on pre-defined device categories.
3Duration of action of moving object
If SIB validity time is extended for low-power devices, then battery life is improved, but system information freshness deteriorates
Solution Approach 1:
The patent applies local quality by extending SIB validity time specifically for low-power devices with longer DRX cycles, while maintaining shorter validity times for devices that require fresher system information. This targeted approach allows battery life extension for low-power devices without compromising information freshness for other devices that need frequent updates.
Solution Approach 2:
The patent introduces dynamics by making the SIB validity time adaptive to device characteristics and DRX cycle configurations. The validity time is not fixed but dynamically adjusted based on device type and operational parameters, allowing the system to balance battery life extension with information freshness requirements for different device categories.
Data Source
AI summary
Methods, systems, and devices for wireless communications are described. In some aspects, a user equipment (UE) and a network entity may support system information block (SIB) validity times that are device, deployment, or operation specific. For example, a network entity may transmit, to a UE, an indication of a SIB validity time that is specific to one or more of the UE, a device type of the UE, or a discontinuous reception (DRX) cycle associated with the UE. In some implementations, the network entity may transmit the indication of the SIB validity time that is specific to the UE via system information along with one or more other SIB validity times that may be specific to one or more other UEs. As such, different SIB validity times indicated via system information may correspond to different UEs, different device types, or different DRX cycles.