Terminal Device DRB ID Allocation in LTE Dual Connection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Long Term Evolution (LTE) dual connection, the Secondary Node (SN) faces challenges in allocating Data Radio Bearer Identifiers (DRB IDs) due to uncertainty about used DRB IDs by terminal devices, leading to potential conflicts and confusion during DRB configuration.
Innovation Solution
The terminal device allocates or reconfigures DRB IDs upon receiving DRB configuration information from the network side and sends a confirmation instruction containing the allocated or reconfigured ID, allowing it to select from available IDs or replace temporary IDs, thus avoiding conflicts when both Master Node (MN) and SN independently configure DRBs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the SN directly configures a DRB ID, then the configuration process is simple and fast, but DRB ID conflicts and confusion may occur
Solution Approach 1:
Instead of the network side allocating DRB IDs unilaterally, the patent inverts the allocation authority to the terminal device. The terminal device autonomously selects and allocates DRB IDs from an available pool, ensuring uniqueness while maintaining configuration efficiency. This inversion resolves the contradiction by making the terminal device responsible for ID management rather than relying on network allocation.
Solution Approach 2:
The patent implements a feedback mechanism where the terminal device reports its selected DRB IDs to the network side through RRC messages. This feedback loop allows the network to verify and confirm the allocated IDs, ensuring no conflicts occur while maintaining the terminal's autonomy in ID selection. The feedback mechanism balances speed and reliability by enabling verification without adding significant overhead.
2Reliability
If the terminal device autonomously allocates DRB IDs, then DRB ID conflicts are avoided, but the complexity of ID management increases
Solution Approach 1:
The patent leverages the terminal device's existing RRC layer functionality to handle DRB ID allocation. The same RRC processing mechanisms used for other configuration tasks are reused for ID selection and management. This multi-functionality approach avoids adding dedicated ID management complexity while achieving reliable autonomous allocation through existing protocol capabilities.
Solution Approach 2:
The patent changes the parameter space for DRB ID allocation by introducing an available ID pool concept and selection criteria. Instead of fixed network-assigned IDs, the terminal device selects from a defined range based on availability indicators. This parameter transformation simplifies the allocation process while ensuring uniqueness, as the terminal only needs to check against the published available ID pool rather than maintaining complex global state.
3Adaptability or versatility
If the SN does not know which DRB IDs are used, then the SN has more flexibility in configuration, but conflicts and confusion arise
Solution Approach 1:
The patent applies preliminary action by having the network side publish an available DRB ID pool before the terminal device performs autonomous allocation. This pre-established ID pool provides the terminal with a known set of valid IDs to choose from, ensuring flexibility in selection while guaranteeing uniqueness. The preliminary definition of the ID pool eliminates conflicts without restricting the terminal's adaptability in choosing from available options.
Data Source
AI summary
Provided are a method for allocating an Identifier (ID) of a data bearer, a terminal device, a network device and a computer storage medium. The method includes: when receiving Data Radio Bearer (DRB) configuration information sent by a network side, allocating or reconfiguring, by the terminal device, a DRB ID; and sending, by the terminal device, a DRB configuration confirmation instruction to the network side, wherein the allocated DRB ID or the reconfigured DRB ID is used as or is contained in the DRB configuration confirmation instruction.