SDAP Data Flow Sequencing Across DRB Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G mobile communication systems, ensuring that data flows delivered to higher-layer protocol entities follow the sequence in which they arrive at the receiving end after a DRB change is challenging.
Innovation Solution
The SDAP entity employs indication information in various formats, including an SDAP header with reserved indication bits or control packets, to distinguish and sequence data flows arriving via source and target DRBs, ensuring proper delivery to higher-layer protocol entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DRB is changed from source DRB to target DRB for QoS data flow, then data transmission flexibility is improved, but data flow sequence delivery to higher-layer protocol entity cannot be guaranteed
Solution Approach 1:
The patent applies preliminary action by introducing indication information before the actual data flow transmission. The indication information is sent in advance to notify the receiving end of the DRB change, allowing the receiving end to prepare for proper data flow sequencing and delivery to higher-layer protocol entities.
Solution Approach 2:
The patent uses indication information as an intermediary element between the source DRB and target DRB. This indication information acts as a mediator that carries necessary control signals and sequencing information, enabling the receiving end to correctly identify and sequence data flows during the DRB transition.
2Reliability
If indication information is added to SDAP header to track data flow sequence, then data flow sequence delivery is improved, but SDAP header complexity increases
Solution Approach 1:
The patent applies local quality by adding indication information only to specific portions of the SDAP header where needed, rather than redesigning the entire header structure. The indication information is inserted at specific locations within the existing header format, maintaining compatibility while adding necessary sequencing functionality.
Solution Approach 2:
The patent makes the SDAP header multi-functional by enabling it to carry both traditional data flow information and the new indication information for DRB change notification. The header structure is designed to accommodate multiple functions without requiring complete redesign, thus avoiding excessive complexity increase.
3Productivity
If multiple DRBs are used for data transmission, then transmission capacity is improved, but data flow sequencing and delivery control becomes more difficult
Solution Approach 1:
The patent applies segmentation by dividing the data flow management into distinct segments: indication information for control signals and data flow information for actual data packets. This segmentation allows the receiving end to process control information separately from data information, simplifying the sequencing control mechanism even when multiple DRBs are used.
Data Source
Figure 1~4(b)
Figure 5~9
Figure 10~12
AI summary
A method and device for configuring a data flow are disclosed in embodiments of this disclosure. The method includes: transmitting indication information to an SDAP entity receiving end if a DRB corresponding to a QoS data flow is changed from a source DRB to a target DRB. The indication information is used to indicate that transmission of a first QoS data flow is completed on the source DRB or transmission of data of a second QoS data flow starts on the target DRB. Data of the QoS data flow includes data of the first QoS data flow and data of the second QoS data flow.