Bearer Protocol Entity Adaptation for 6G QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication standards, such as 5G, lack flexibility in their bearers, which are unable to adapt to the diversified characteristics of future communication scenarios like 6G, requiring more agile access network resources.
Innovation Solution
The proposed solution involves a method for processing data where a node processes data using protocol entities of a bearer that can have multiple characteristics, including protocol entities of the same type operating in different modes, dynamically or semi-statically changing functions, and including a target entity with part of the functions of a PDCP or RLC entity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the current communication standard bearer definition is used, then the bearer structure is simple and stable, but the bearer lacks flexibility and cannot adapt to diversified application scenarios
Solution Approach 1:
The patent divides the traditional bearer into multiple protocol entities (PDCP entity, RLC entity, MAC entity) that can operate independently. Each entity can be selectively activated or deactivated based on specific service requirements, allowing the bearer to adapt to different scenarios without requiring a completely different bearer structure for each case.
Solution Approach 2:
The patent introduces dynamic configuration where protocol entities can change their operational states based on service characteristics. The bearer can dynamically adjust which protocol entities are active and their specific configurations to match diverse application needs, transforming a static bearer structure into a dynamic adaptive system.
2Adaptability or versatility
If multiple protocol entities of the same type in different modes are used, then the bearer can adapt to different service requirements, but the protocol entity configuration becomes more complex
Solution Approach 1:
The patent designs protocol entities that can perform multiple functions by operating in different modes. A single PDCP entity, for example, can handle different service types (voice, data, video) by switching between operational modes, eliminating the need for separate dedicated entities for each service type and reducing overall configuration complexity.
Solution Approach 2:
The patent utilizes parameter changes to enable protocol entities to adapt to different service requirements. By modifying operational parameters (such as processing modes, priority levels, error handling mechanisms) rather than creating entirely new entities, the system achieves versatility while maintaining configuration simplicity.
3Adaptability or versatility
If the bearer function changes dynamically or semi-statically, then the bearer can respond to changing service needs, but the data processing complexity increases
Solution Approach 1:
The patent implements preliminary configuration where protocol entities are pre-configured with multiple operational modes and service profiles. When service requirements change, the system can quickly switch between pre-configured modes rather than dynamically creating new processing logic, reducing the complexity of real-time adaptation.
Solution Approach 2:
The patent introduces feedback mechanisms that monitor service conditions and automatically trigger appropriate protocol entity mode changes. This closed-loop control enables dynamic adaptation to changing service needs while using simple automated responses rather than complex decision-making algorithms.
Data Source
AI summary
A method for processing data, a communication device and a chip are provided. The method includes the following operations. A node processes data by means of protocol entities of a bearer, and the bearer has at least one of the following characteristics: at least two protocol entities of the bearer are protocol entities of the same type in different modes; the function of at least one protocol entity of the bearer can change dynamically or semi-statically; and the protocol entities of the bearer include a target entity, and the target entity having at least some of the functions of a packet data convergence protocol (PDCP) entity and/or a radio link control (RLC) entity.