Multicast Control Channel Segmentation for UE Power Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast session technologies in radio networks lead to inefficient resource usage, particularly power consumption, due to frequent monitoring of multicast control channels by UEs that do not require low latency services, and fail to effectively support services with varying latency requirements.
Innovation Solution
The introduction of multiple multicast control channels with different configuration settings based on latency requirements allows UEs to selectively monitor changes only for services they are interested in, reducing unnecessary monitoring and resource usage, and enabling flexible support for various applications like V2X, MCC, and Mobile Broadband.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If UEs monitor all multicast control channels frequently, then all multicast services can be received, but power consumption increases and resource usage becomes inefficient
Solution Approach 1:
The multicast control channel is segmented into multiple independent channels (e.g., MCCH1, MCCH2, MCCH3) with different monitoring configurations. Each channel serves specific service types with different latency requirements, allowing UEs to selectively monitor only the channels relevant to their service needs rather than all channels, thereby reducing power consumption while maintaining service coverage.
Solution Approach 2:
The monitoring configuration is made dynamic by introducing multiple MCCH configurations with different monitoring periods and latency parameters. UEs can dynamically select and switch between different MCCH configurations based on their current service requirements, enabling adaptive power consumption levels matched to actual service needs.
2Adaptability or versatility
If a single multicast control channel is used, then system complexity is low, but services with different latency requirements cannot be effectively supported
Solution Approach 1:
The single multicast control channel is segmented into multiple specialized channels (MCCH1 for low latency services, MCCH2 for mobile broadband, MCCH3 for other services). Each segment handles specific service types with appropriate latency characteristics, enabling the system to support diverse latency requirements while keeping each individual channel configuration relatively simple and manageable.
Solution Approach 2:
Different local qualities (monitoring periods, latency parameters, service types) are assigned to different MCCH channels. MCCH1 has high-frequency monitoring for low latency services, while MCCH2 has lower-frequency monitoring for mobile broadband services. This local differentiation allows each channel to be optimized for its specific service type without complicating the overall system architecture.
3Speed
If UEs monitor multicast control channels with high frequency, then low latency services are supported, but resource usage efficiency decreases
Solution Approach 1:
The monitoring frequency is segmented by service type through different MCCH channels. Low latency services use MCCH1 with high monitoring frequency to achieve fast service establishment, while mobile broadband services use MCCH2 with lower monitoring frequency to conserve resources. This segmentation allows the system to achieve low latency where needed without wasting resources on services that don't require it.
Solution Approach 2:
The monitoring period parameter is changed based on service requirements and channel type. MCCH1 uses a short monitoring period (e.g., 10ms) for low latency services, while MCCH2 uses a longer monitoring period (e.g., 40ms) for mobile broadband services. This parameter differentiation enables the system to optimize between latency performance and resource efficiency for different service scenarios.
Data Source
AI summary
There is provided a method comprising monitoring (100; 300; 400) at least one multicast control channel (MCCH1) based on at least one selection information (sel) characterizing a selection of at least one multicast control channel configuration (conf1) associated with the at least one multicast control SNET channel (MCCH1).