Random Access Terminal Type Reporting for eRedCap UE
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies, such as NB-IoT and MTC, struggle to support high-rate, low-latency services like smart homes and industrial sensor measurements due to limitations in terminal capabilities, particularly with the introduction of enhanced Reduced Capability UE (eRedCap UE) in 5G NR, which requires a new mechanism for terminal type reporting during random access.
Innovation Solution
A message sending and receiving method that utilizes a dedicated logical channel identifier (LCID) or a combination of shared LCID and additional indication information to differentiate and report the terminal type of eRedCap UE during the random access process, allowing network devices to identify and accommodate different terminal capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If existing communication technologies (NB-IoT, MTC) are used, then low-rate, high-latency services are supported, but high-rate, low-latency services cannot be supported
Solution Approach 1:
The patent introduces a new terminal type (eRedCap UE) with modified capability parameters that enable higher data rates and lower latency compared to traditional RedCap UEs. This parameter change allows the system to support high-rate, low-latency services while maintaining backward compatibility with existing terminal types.
2Adaptability or versatility
If terminal type reporting is not implemented during random access, then the random access process remains simple, but network devices cannot identify and accommodate different terminal capabilities
Solution Approach 1:
The patent implements terminal type reporting during the random access process, specifically in Message 3 or Message A, so that the network device can identify terminal capabilities before resource allocation and scheduling decisions are made. This preliminary identification enables the network to appropriately configure resources for different terminal types (eRedCap UE, RedCap UE, normal UE) from the outset.
Solution Approach 2:
The patent uses the existing random access message structure (Message 3 or Message A) as an intermediary carrier to convey terminal type information. By embedding the terminal type indicator within these standard messages, the system achieves terminal identification without requiring separate signaling procedures, thus minimizing additional complexity.
3Measurement precision
If dedicated LCID is used for terminal type reporting, then terminal type identification is precise, but signaling overhead increases
Solution Approach 1:
The patent makes the existing LCID field in Message 3 or Message A serve multiple functions: it continues to identify logical channels while also carrying terminal type information. This multi-functionality allows precise terminal type identification without requiring additional dedicated signaling fields, thus avoiding increased signaling overhead.
Solution Approach 2:
The patent merges the terminal type indication function with the existing logical channel identification function by using the same LCID field. This consolidation eliminates the need for separate terminal type signaling, achieving both precise identification and efficient signaling utilization.
Data Source
AI summary
A message sending method is performed by a first type terminal, and includes: sending a message 3 in a random access process to a network device, the message 3 carrying type information for indicating the first type terminal; wherein the type information of the first type terminal is different from type information of a second type terminal and type information of a third type terminal, and a terminal capability of the second type terminal and a terminal capability of the third type terminal are both greater than a terminal capability of the first type terminal.