CU-UP Capability Selection for PDCP Status Report Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current 5G base station architecture faces challenges in determining the service capabilities of user plane entities, leading to manual configuration workloads, increased latency due to differing PDCP status report usage between user equipment and the CU-CP, and undefined Ethernet header compression feedback modes, resulting in inefficient data transmission and resource waste.
Innovation Solution
A method where each CU-UP determines and sends its service support capabilities to the CU-CP, allowing the CU-CP to select appropriate entities and configure PDCP status reports and Ethernet header compression modes based on service requirements, using trigger information to optimize data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual configuration is used to determine service capabilities of user plane entities, then configuration flexibility is maintained, but configuration workload increases and efficiency decreases
Solution Approach 1:
The user plane entity automatically determines and sends its own service support capabilities to the control plane entity, eliminating the need for manual configuration. The system enables self-configuration where the CU-UP autonomously provides capability information (including PDCP status report capabilities, EHC capabilities, and feedback mode preferences) to the CU-CP, which then automatically selects appropriate user plane entities for service bearers based on published capability information.
2Reliability
If PDCP status report is configured for all service bearers, then data reliability is improved, but unnecessary retransmissions increase and latency increases
Solution Approach 1:
The system applies different PDCP status report configurations to different service bearers based on their specific requirements. The control plane entity publishes capability information indicating which service bearers support PDCP status report, and the user plane entity selectively enables status report only for bearers that require it (e.g., bearers with AM mode RLC entities), avoiding unnecessary status reports for bearers where they provide no benefit.
3Speed
If Ethernet header compression is applied to all data packets, then transmission latency is reduced and payload occupation ratio is improved, but compression complexity increases
Solution Approach 1:
The system applies Ethernet header compression selectively based on service bearer requirements and capability information. The user plane entity determines whether to apply EHC to specific bearers based on published capability information and service type, applying compression only where it provides benefit (e.g., for bearers with latency requirements) while maintaining simplicity for other bearers.
4Adaptability or versatility
If all user plane entities support all capabilities, then system versatility is improved, but resource waste increases and configuration simplicity is reduced
Solution Approach 1:
The system allows user plane entities to support only the capabilities they actually need rather than requiring all capabilities. Each CU-UP publishes its actual capability support information (including which compression algorithms it supports, whether it supports PDCP status report, and preferred feedback modes), and the control plane entity makes informed selections based on this partial capability information, avoiding resource waste on unsupported capabilities.
Data Source
AI summary
The present disclosure provides a user plane data processing method and a base station. The method includes: each CU-UP determines a current service support capabilities according to first trigger information, and sends it to a CU-CP; the CU-CP selects a CU-UP for each service bearer of the UE according to the current service support capabilities of the each CU-UP if at least part of service bearers of the UE needs to be configured or updated according to second trigger information; the CU-CP sends first UP configuration information associated with the each service bearer to the UE and second UP configuration information associated with the each service bearer to the each CU-UP, thereby the UE determining whether to configure a PDCP status report according to the first UP configuration information, and each CU-UP determining whether to process the PDCP status report from the UE according to the second UP configuration information.