Method for processing RLC failure, network device and computer storage medium
US-11825541-B2 · Nov 21, 2023 · US
US12457660B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12457660-B2 |
| Application number | US-202318515054-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 20, 2023 |
| Priority date | Jun 21, 2018 |
| Publication date | Oct 28, 2025 |
| Grant date | Oct 28, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure relates to a communication method and system for converging a 5 th -Generation (5G) communication system for supporting higher data rates beyond a 4 th -Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The present application relates to the field of wireless communication technologies, and discloses a method for processing an Radio Link Control (RLC) failure, an electronic device and a computer readable storage medium. The method includes: receiving, by a first network device, RLC failure related information of a user equipment (UE); processing the RLC failure correspondingly by interacting with a second network device, based on the received RLC failure related information.
Opening claim text (preview).
What is claimed is: 1. A method performed by a central unit (CU) of a base station for processing a radio link control (RLC) failure, the method comprising: transmitting, to a distributed unit (DU) of the base station, a user equipment (UE) context modification request message including first information indicating a logical channel identifier (LCID) associated with an RLC entity needing re-establishment; and receiving, from the DU, a UE context modification response message including second information indicating a list of secondary cells related to the RLC entity in case that the RLC entity indicated in the first information needs to be re-established, wherein the RLC entity indicated in the first information needs to be re-established is identified by the DU of the base station. 2. The method according to claim 1 , further comprising: receiving, from a UE, information on the RLC failure. 3. A method performed by a distributed unit (DU) of a base station for processing a radio link control (RLC) failure, the method comprising: receiving, from a central unit (CU) of the base station, a user equipment (UE) context modification request message including first information indicating a logical channel identifier (LCID) associated with an RLC entity needing re-establishment; identifying the RLC entity indicated in the first information needs to be re-established; and transmitting, to the CU, a UE context modification response message including second information indicating a list of secondary cells related to the RLC entity in case that the RLC entity indicated in the first information needs to be re-established. 4. The method according to claim 3 , wherein the first information on an RLC failure is received by the CU from a UE. 5. A central unit (CU) of a base station, the CU comprising: a transceiver; and a controller coupled with the transceiver and configured to: transmit, to a distributed unit (DU) of the base station, a user equipment (UE) context modification request message including first information indicating a logical channel identifier (LCID) associated with a radio link control (RLC) entity needing re-establishment, and receive, from the DU, a UE context modification response message including second information indicating a list of secondary cells related to the RLC entity in case that the RLC entity indicated in the first information needs to be re-established, wherein the RLC entity indicated in the first information needs to be re-established is identified by the DU of the base station. 6. The CU according to claim 5 , wherein the controller further configured to receive, from a UE, information on an RLC failure. 7. A distributed unit (DU) of a base station, the DU comprising: a transceiver; and a controller coupled with the transceiver and configured to: receive, from a central unit (CU) of the base station, a user equipment (UE) context modification request message including first information indicating a logical channel identifier (LCID) associated with a radio link control (RLC) entity needing re-establishment, identify the RLC entity indicated in the first information needs to be re-established, and transmit, to the CU, a UE context modification response message including second information indicating a list of secondary cells related to the RLC entity in case that the RLC entity indicated in the first information needs to be re-established. 8. The DU according to claim 7 , wherein the first information on the RLC failure is received by the CU from a UE.
Connection re-establishment · CPC title
Cell handover without a predetermined boundary, e.g. virtual cells · CPC title
using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO] (allocation of physical resources in CoMP or in CA H04L5/0035) · CPC title
for transferring data sessions between adjacent core network technologies · CPC title
Access point devices with remote components · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.