Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method performed by a user equipment (UE), comprising: receiving a first RRCConnectionReconfiguration message which contains an indication to reconfigure a first data radio bearer (DRB) to a second DRB; and sending a PDCP status report to a base station (eNB), if (a) the UE reconfigures a radio bearer from the first DRB to the second DRB and (b) the UE is configured according to an RRC signaling for configuring the UE to send, when reconfiguring the radio bearer, the PDCP status report, wherein the second DRB is a bearer whose radio protocols are located in a base station (eNB) and are not located in a WLAN to use eNB radio resources among the eNB radio resources and WLAN radio resources, the first DRB is a bearer whose radio protocols are located in both the eNB and the WLAN but which uses only the WLAN radio resources, and the first DRB is a bearer which is not split in the eNB.
This invention relates to wireless communication systems, specifically methods for reconfiguring data radio bearers (DRBs) between a user equipment (UE) and a base station (eNB) in a network that integrates both cellular (eNB) and wireless local area network (WLAN) resources. The problem addressed is the efficient management of radio bearer reconfiguration when transitioning between different types of DRBs, particularly those that utilize only WLAN resources versus those that rely on eNB resources. The method involves a UE receiving a reconfiguration message instructing it to switch a first DRB to a second DRB. The first DRB is a non-split bearer that uses only WLAN radio resources, with its radio protocols located in both the eNB and WLAN. The second DRB is a bearer that uses eNB radio resources exclusively, with its radio protocols located only in the eNB. Upon reconfiguring the bearer, the UE sends a Packet Data Convergence Protocol (PDCP) status report to the eNB if it is configured to do so via RRC signaling. This ensures proper synchronization of data transmission between the UE and the eNB during the bearer transition. The invention optimizes resource utilization and maintains data integrity during dynamic reconfiguration in heterogeneous networks.
2. The method according to claim 1 , further comprising: receiving a second RRCConnectionReconfiguration message which contains an indication to reconfigure the second DRB to the first DRB and a drb-ToAddModList parameter that contains a list of DRBs needed to be added; reconfiguring a PDCP entity in accordance with a pdcp-Config parameter, if the pdcp-Config parameter is included in the drb-ToAddModList parameter, wherein the pdcp-Config parameter is used to set configurable PDCP parameters for the first DRB.
This invention relates to wireless communication systems, specifically to methods for dynamically reconfiguring data radio bearers (DRBs) in a user equipment (UE) device. The problem addressed is the need for efficient and flexible management of DRB configurations to optimize data transmission and resource utilization in wireless networks. The method involves receiving a second RRCConnectionReconfiguration message from a network node, such as a base station. This message includes an instruction to reconfigure a second DRB into a first DRB and a drb-ToAddModList parameter, which specifies a list of DRBs to be added or modified. The method further includes reconfiguring a Packet Data Convergence Protocol (PDCP) entity based on a pdcp-Config parameter, if present in the drb-ToAddModList. The pdcp-Config parameter defines configurable PDCP settings for the first DRB, such as security parameters, header compression, or data transfer modes. This approach allows the network to dynamically adjust DRB configurations, ensuring optimal performance and resource allocation. The method supports seamless reconfiguration of PDCP entities, enabling efficient data transmission and reducing signaling overhead. The solution is particularly useful in scenarios requiring frequent DRB adjustments, such as handover procedures or quality-of-service (QoS) updates.
3. The method according to claim 2 , further comprising: reconfiguring one adaptation entity for a plurality of first DRBs which receives data from the PDCP entity.
A method for managing data radio bearers (DRBs) in a wireless communication system involves dynamically reconfiguring adaptation entities to optimize data transmission. The system includes a Packet Data Convergence Protocol (PDCP) entity that processes data for multiple DRBs, each handling different types of traffic. The method addresses inefficiencies in traditional systems where separate adaptation entities are used for each DRB, leading to resource waste and complexity. By reconfiguring a single adaptation entity to serve multiple DRBs that receive data from the PDCP entity, the system reduces overhead and improves resource utilization. This approach allows the adaptation entity to dynamically adjust its configuration based on the requirements of the DRBs, ensuring efficient data transmission while maintaining quality of service. The method is particularly useful in scenarios where multiple DRBs share similar characteristics or when resource constraints require consolidation of adaptation functions. The reconfiguration process may involve modifying parameters such as buffer sizes, scheduling priorities, or error correction mechanisms to accommodate the varying needs of the DRBs. This flexible approach enhances system performance and scalability in wireless networks.
4. A method performed by a base station (eNB), comprising: sending, to a user equipment (UE), a first RRCConnectionReconfiguration message which contains an indication to reconfigure a first data radio bearer (DRB) to a second DRB; and receiving a PDCP status report from the UE, if (a) a radio bearer of the UE is reconfigured from the first DRB to the second DRB and (b) the UE is configured according to an RRC signaling for configuring the UE to send, when reconfiguring the radio bearer, the PDCP status report, wherein the second DRB is a bearer whose radio protocols are located in the eNB and are not located in a WLAN to use eNB radio resources among the eNB radio resources and WLAN radio resources, the first DRB is a bearer whose radio protocols are located in both the eNB and the WLAN but which uses only the WLAN radio resources, and the first DRB is a bearer which is not split in the eNB.
This invention relates to wireless communication systems, specifically methods for managing data radio bearers (DRBs) in a base station (eNB) when transitioning between different types of radio bearers. The problem addressed is ensuring proper handling of data transmission during reconfiguration between a first DRB, which relies solely on WLAN radio resources and has radio protocols in both the eNB and WLAN, and a second DRB, which uses only eNB radio resources and has its radio protocols located entirely in the eNB. The first DRB is not split in the eNB, meaning it does not distribute traffic between the eNB and WLAN. The method involves the eNB sending an RRCConnectionReconfiguration message to a user equipment (UE), instructing it to reconfigure the first DRB to the second DRB. Upon reconfiguration, if the UE is configured via RRC signaling to send a PDCP status report during such transitions, the UE transmits this report to the eNB. The PDCP status report helps synchronize data transmission between the eNB and UE, ensuring no data loss during the bearer switch. The second DRB is designed to utilize only eNB radio resources, unlike the first DRB, which relies exclusively on WLAN resources. This approach optimizes resource allocation and maintains data integrity during bearer transitions.
5. The method according to claim 4 , further comprising: sending, to the UE, a second RRCConnectionReconfiguration message which contains an indication to reconfigure the second DRB to the first DRB and a drb-ToAddModList parameter that contains a list of DRBs needed to be added, wherein: a PDCP entity of the UE is reconfigured in accordance with a pdcp-Config parameter, if the pdcp-Config parameter is included in the drb-ToAddModList parameter, wherein the pdcp-Config parameter is used to set configurable PDCP parameters for the first DRB.
This invention relates to wireless communication systems, specifically to methods for dynamically reconfiguring data radio bearers (DRBs) in a user equipment (UE) device. The problem addressed is the need for efficient and flexible reconfiguration of DRBs to optimize data transmission, particularly when transitioning between different DRBs or adjusting protocol layer configurations. The method involves sending a second RRCConnectionReconfiguration message to the UE, which includes an instruction to reconfigure a second DRB into a first DRB. This message contains a drb-ToAddModList parameter that specifies the DRBs to be added or modified. If the message includes a pdcp-Config parameter within the drb-ToAddModList, the UE's PDCP (Packet Data Convergence Protocol) entity is reconfigured according to this parameter. The pdcp-Config parameter adjusts configurable PDCP settings for the first DRB, such as header compression, security settings, or other protocol-specific parameters. This allows the network to dynamically adapt the DRB configuration to changing conditions, improving data transmission efficiency and reliability. The reconfiguration ensures seamless transition between DRBs while maintaining service continuity.
6. The method according to claim 5 , wherein one adaptation entity of the UE for a plurality of first DRBs is reconfigured, and the one adaptation entity receives data from the PDCP entity.
In wireless communication systems, particularly in 5G and beyond, user equipment (UE) must efficiently manage data transmission across multiple data radio bearers (DRBs) while maintaining low latency and high reliability. A key challenge is dynamically adapting to varying network conditions and service requirements without excessive signaling overhead or processing delays. Existing solutions often require separate adaptation entities for each DRB, leading to inefficiencies in resource utilization and increased complexity. This invention addresses these issues by introducing a method where a single adaptation entity in the UE is reconfigured to handle multiple first DRBs. The adaptation entity is responsible for receiving data from the Packet Data Convergence Protocol (PDCP) entity, which ensures proper data formatting, integrity, and security before transmission. By consolidating multiple DRBs under one adaptation entity, the system reduces the number of required entities, simplifies configuration, and improves overall efficiency. This approach minimizes signaling overhead, lowers processing latency, and enhances resource management, particularly in scenarios with high data traffic or frequent network condition changes. The reconfiguration process ensures seamless adaptation to different service requirements while maintaining compliance with protocol standards. This solution is particularly beneficial in dense network environments where multiple DRBs must be managed concurrently.
7. A user equipment (UE) comprising: receiving circuitry configured to receive a first RRCConnectionReconfiguration message which contains an indication to reconfigure a first data radio bearer (DRB) to a second DRB; and transmitting circuitry configured to send a PDCP status report to a base station (eNB), if (a) the UE reconfigures a radio bearer from the first DRB to the second DRB and (b) the UE receives an RRC signaling for configuring the UE to send, when reconfiguring the radio bearer, the PDCP status report, wherein the second DRB is a bearer whose radio protocols are located in a base station (eNB) and are not located in a WLAN to use eNB radio resources among the eNB radio resources and WLAN radio resources, the first DRB is a bearer whose radio protocols are located in both the eNB and the WLAN but which uses only the WLAN radio resources, and the first DRB is a bearer which is not split in the eNB.
This invention relates to wireless communication systems, specifically to user equipment (UE) handling data radio bearer (DRB) reconfiguration between a base station (eNB) and a wireless local area network (WLAN). The problem addressed is ensuring reliable data transmission during DRB reconfiguration, particularly when transitioning between bearers that use different radio resources and protocol locations. The UE includes receiving circuitry to obtain an RRCConnectionReconfiguration message indicating a reconfiguration from a first DRB to a second DRB. The first DRB is a non-split bearer where radio protocols are located in both the eNB and WLAN, but only WLAN radio resources are used. The second DRB is a bearer where radio protocols are entirely in the eNB, utilizing only eNB radio resources. Upon reconfiguring the bearer, the UE sends a PDCP status report to the eNB if it receives RRC signaling instructing it to do so. This ensures the eNB is aware of any pending data transmissions, preventing data loss during the transition. The solution optimizes resource utilization by dynamically switching between WLAN and eNB resources while maintaining data integrity.
8. The UE according to claim 7 , wherein the receiving circuitry is further configured to receive a second RRCConnectionReconfiguration message which contains an indication to reconfigure the second DRB to the first DRB and a drb-ToAddModList parameter that contains a list of DRBs needed to be added, and the UE further comprises: reconfiguring circuitry configured to reconfigure a PDCP entity in accordance with a pdcp-Config parameter, if the pdcp-Config parameter is included in the drb-ToAddModList parameter, wherein the pdcp-Config parameter is used to set configurable PDCP parameters for the first DRB.
In wireless communication systems, particularly in 5G and LTE networks, user equipment (UE) devices require efficient data transmission mechanisms to handle different types of data radio bearers (DRBs). A challenge arises when reconfiguring DRBs to optimize data flow, especially when transitioning between different DRB configurations. This invention addresses the need for seamless reconfiguration of DRBs, including the associated Packet Data Convergence Protocol (PDCP) entities, to ensure uninterrupted data transmission. The invention involves a UE configured to receive a second RRCConnectionReconfiguration message from a network node. This message includes an indication to reconfigure a second DRB to a first DRB and a drb-ToAddModList parameter, which specifies the DRBs to be added or modified. The UE further includes circuitry to process this message. If the drb-ToAddModList parameter includes a pdcp-Config parameter, the UE reconfigures the PDCP entity for the first DRB according to the settings defined in the pdcp-Config parameter. This parameter adjusts configurable PDCP parameters, such as security settings, header compression, or data transfer modes, ensuring the first DRB operates optimally after reconfiguration. The invention enables dynamic adaptation of DRB configurations without disrupting ongoing data sessions, improving network efficiency and user experience.
9. The UE according to claim 8 , wherein the reconfiguring circuitry is further configured to reconfigure one adaptation entity for a plurality of first DRBs which receives data from the PDCP entity.
This invention relates to wireless communication systems, specifically to user equipment (UE) configured to optimize data transmission efficiency in a network. The problem addressed is the inefficient handling of data radio bearers (DRBs) in UEs, particularly when multiple DRBs share a single adaptation entity, leading to suboptimal resource utilization and performance degradation. The UE includes circuitry for reconfiguring an adaptation entity to serve multiple data radio bearers (DRBs) that receive data from a Packet Data Convergence Protocol (PDCP) entity. The adaptation entity processes data for transmission over a radio interface, and the reconfiguration allows dynamic adjustment of its operation to handle varying traffic demands from different DRBs. This improves resource allocation and reduces overhead by consolidating processing for multiple DRBs under a single adaptation entity, rather than requiring separate entities for each DRB. The reconfiguration can be based on traffic conditions, network requirements, or UE capabilities, ensuring efficient use of processing and radio resources. The invention enhances data transmission efficiency, reduces latency, and improves overall system performance in wireless networks.
10. A base station (eNB) comprising: transmitting circuitry configured to send, to a user equipment (UE), a first RRCConnectionReconfiguration message which contains an indication to reconfigure a first data radio bearer (DRB) to a second DRB; and receiving circuitry configured to receive a PDCP status report from the UE, if (a) a radio bearer of the UE is reconfigured from the first DRB to the second DRB and (b) the UE is configured according to an RRC signaling for configuring the UE to send, when reconfiguring to radio bearer, the PDCP status report, wherein the second DRB is a bearer whose radio protocols are located in the eNB and are not located in a WLAN to use eNB radio resources among the eNB radio resources and WLAN radio resources, the first DRB is a bearer whose radio protocols are located in both the eNB and the WLAN but which uses only the WLAN radio resources, and the first DRB is a bearer which is not split in the eNB.
This invention relates to wireless communication systems, specifically to the reconfiguration of data radio bearers (DRBs) between a base station (eNB) and user equipment (UE) in a network that integrates both cellular (eNB) and wireless local area network (WLAN) radio resources. The problem addressed is ensuring proper synchronization and data integrity when transitioning a UE from a WLAN-only DRB to an eNB-managed DRB, where radio protocols are handled by the eNB rather than the WLAN. The base station includes transmitting circuitry to send an RRCConnectionReconfiguration message to the UE, instructing it to switch from a first DRB (using only WLAN radio resources and not split in the eNB) to a second DRB (using eNB radio resources and protocols). The UE, if configured via RRC signaling to do so, sends a PDCP (Packet Data Convergence Protocol) status report upon completing the reconfiguration. The base station also includes receiving circuitry to obtain this report, which helps the eNB track data transmission status and maintain service continuity during the transition. The first DRB operates solely over WLAN, while the second DRB leverages eNB radio resources and protocols, ensuring seamless integration between the two network types. This approach optimizes resource utilization and reliability in heterogeneous networks.
11. The eNB according to claim 10 , wherein the transmitting circuitry is further configured to send, to the UE, a second RRCConnectionReconfiguration message which contains an indication to reconfigure the second DRB to the first DRB and a drb-ToAddModList parameter that contains a list of DRBs needed to be added, wherein: a PDCP entity of the UE is reconfigured in accordance with a pdcp-Config parameter, if the pdcp-Config parameter is included in the drb-ToAddModList parameter, wherein the pdcp-Config parameter is used to set configurable PDCP parameters for the first DRB.
This invention relates to wireless communication systems, specifically to methods for reconfiguring data radio bearers (DRBs) in a Long-Term Evolution (LTE) network. The problem addressed is the need for efficient and flexible reconfiguration of DRBs between a user equipment (UE) and an evolved NodeB (eNB) to optimize data transmission while maintaining service continuity. The eNB includes transmitting circuitry configured to send a second RRCConnectionReconfiguration message to the UE. This message contains an indication to reconfigure a second DRB into a first DRB and includes a drb-ToAddModList parameter, which lists the DRBs to be added or modified. If the drb-ToAddModList parameter includes a pdcp-Config parameter, the UE's PDCP (Packet Data Convergence Protocol) entity is reconfigured according to this parameter. The pdcp-Config parameter sets configurable PDCP parameters for the first DRB, such as security settings, header compression, or other PDCP-specific configurations. This allows dynamic adjustment of DRB properties to adapt to changing network conditions or service requirements without disrupting ongoing communications. The solution ensures seamless reconfiguration while maintaining data integrity and service quality.
12. The eNB according to claim 11 , wherein one adaptation entity of the UE for a plurality of first DRBs is reconfigured, and the one adaptation entity receives data from the PDCP entity.
In wireless communication systems, particularly in Long-Term Evolution (LTE) networks, efficient data transmission between user equipment (UE) and evolved Node B (eNB) is critical. A challenge arises when multiple data radio bearers (DRBs) require adaptation for different quality of service (QoS) requirements, leading to complexity in managing separate adaptation entities for each DRB. This increases processing overhead and reduces efficiency. The invention addresses this by reconfiguring a single adaptation entity in the UE to handle multiple first DRBs. This adaptation entity receives data from the Packet Data Convergence Protocol (PDCP) entity, which is responsible for data integrity and security. By consolidating adaptation functions for multiple DRBs into one entity, the system reduces complexity, minimizes resource usage, and improves overall performance. The adaptation entity can dynamically adjust parameters such as packet size, timing, or error handling to meet the QoS requirements of each DRB it serves. This approach ensures efficient data transmission while maintaining flexibility in managing diverse DRB configurations. The solution is particularly useful in scenarios where multiple DRBs with varying QoS needs coexist, optimizing both UE and network resource utilization.
Unknown
December 8, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.