Method and apparatus for processing data transmission failure

US11290939B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11290939-B2
Application numberUS-201816650658-A
CountryUS
Kind codeB2
Filing dateSep 17, 2018
Priority dateSep 25, 2017
Publication dateMar 29, 2022
Grant dateMar 29, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method and an apparatus of processing data transmission failure are provided. The method includes determining a target event occurs, wherein the target event includes one or more of an event that a target RLC entity reaches a maximum number of retransmissions, an event that a physical layer of a target SCell is out of sync, and an event that a random access procedure of the target SCell fails, target RLC entity is in a terminal corresponding to a duplicate bearer, to-be-sent data of target RLC entity is sent only through an SCell, the target SCell is at least one SCell sending to-be-sent data of target RLC entity; resetting target RLC entity, and/or processing target SCell, and/or processing duplicate bearer. The technical solution specifies specific processing of a terminal if the target event occurs, thereby ensuring performance of the terminal and avoiding interference to other terminals.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of processing data transmission failure, wherein, the method is executed by a terminal device, the method comprises: determining that a target event occurs, wherein the target event comprises at least one of following events: an event that a target Radio Link Control (RLC) entity reaches a maximum number of retransmissions, or an event that a random access procedure of a target SCell fails, the target RLC entity is an RLC entity corresponding to a duplicate bearer in a terminal device, to-be-sent data of the target RLC entity is sent only through one or more SCells, and a target SCell is at least one SCell, in the one or more SCells, for sending the to-be-sent data of the target RLC entity; wherein the target SCell is an SCell in a Master Cell Group (MCG), the method further comprises: in a case that the target event occurs, sending information relevant to the target event to a Master Node (MN) corresponding to the MCG through a signaling radio bearer 1 (SRB1) or SRB2; or, the target SCell is an SCell in a Secondary Cell Group (SCG), the method further comprises: in a case that the target event occurs, sending information relevant to the target event to a Secondary Node (SN) corresponding to the SCG through a signaling radio bearer 3 (SRB3); or, the target SCell is an SCell in a Secondary Cell Group (SCG), the method further comprises: in a case that the target event occurs, sending information relevant to the target event to a Master Node (MN) corresponding to a Master Cell Group (MCG) through a signaling radio bearer 1 (SRB1) or SRB2, wherein, the MN is used to forward the information relevant to the target event to a Secondary Node (SN) corresponding to the SCG; wherein the information relevant to the target event comprises at least one of an identifier of a logical channel corresponding to the target RLC entity and an identifier of a cell group to which the target SCell belong. 2. The method according to claim 1 , wherein, the method further comprises: determining whether to send the information relevant to the target event to a network device in a case that the target event occurs. 3. The method according to claim 1 , wherein the method further comprises: performing at least one of following processing operations: resetting the target RLC entity and processing the target SCell; wherein, processing the target SCell comprises at least one of following processing operations: resetting all RLC entities corresponding to the target SCell; deactivating the target SCell; stopping uplink signal transmission of the target SCell; and stopping downlink signal reception of the target SCell. 4. The method according to claim 1 , wherein the method further comprises: processing the duplicate bearer; wherein, processing the duplicate bearer comprises at least one of following processing operations: deactivating a data duplicate function of a Packet Data Convergence Protocol (PDCP) entity corresponding to the duplicate bearer; changing a default transmission path of the duplicate bearer as a transmission path corresponding to an other RLC entity; suspending the duplicate hearer, wherein, in a case that the duplicate bearer is suspended, the duplicate bearer does not send or receive data; re-establishing a PDCP entity corresponding to the duplicate bearer; and, resetting a Media Access Control (MAC) entity corresponding to the duplicate bearer. 5. The method according to claim 4 , wherein, before changing the default transmission path of the duplicate bearer as the transmission path corresponding to the other RLC entity, the method further comprises: determining that the default transmission path of the duplicate bearer is a transmission path corresponding to the target RLC entity. 6. The method according to claim 4 , wherein, before suspending the duplicate bearer, the method further comprises: determining that at least one of following events occurs in all RLC entities corresponding to the duplicate bearer: an event that an RLC entity reaches a maximum number of retransmissions, an event that a physical layer of the SCell for sending to-be-sent data of an RLC entity is out of sync, and an event that a random access procedure of the SCell for sending to-be-sent data of an RLC entity fails. 7. The method according to claim 4 , wherein, before re-establishing the PDCP entity corresponding to the duplicate bearer, the method further comprises: determining that at least one of following events occurs in all RLC entities corresponding to the duplicate bearer: an event that an RLC entity reaches a maximum number of retransmissions, an event that a physical layer of an SCell for sending to-be-sent data of are RLC entity is out of sync, and an event that a random access procedure of an SCell for sending to-be-sent data of an RLC entity fails. 8. The method according to claim 4 , wherein, before resetting the MAC entity corresponding to the duplicate bearer, the method further comprises: determining that at least one of following events occurs in all RLC entities corresponding to the duplicate bearer: an event that an RLC entity reaches a maximum number of retransmissions, an event that a physical layer of an SCell for sending to-be-sent data of an RLC entity is out of sync, and an event that a random access procedure of an SCell for sending to-be-sent data of an RLC entity fails. 9. The method according to claim 2 , wherein, determining whether to send the information relevant to the target event to the network device in a case that the target event occurs, comprises: determining, according to a protocol pre-configured in the terminal device, whether to send the information relevant to the target event to the network device in a case that the target event occurs. 10. The method according to claim 2 , wherein, determining whether to send the information relevant to the target event to the network device in a case that the target event occurs, comprises: receiving configuration information sent by the network device, wherein the configuration information is used to indicate whether to send the information relevant to the target event to the network device in a case that the target event occurs; determining, based on the configuration information, whether to send the information relevant to the target event to the network device in a case that the target event occurs. 11. The method according to claim 10 , wherein, the network device comprises a Master Node (MN) corresponding to a Master Cell Group (MCG), and/or a Secondary Node (SN) corresponding to a Secondary Cat Group (SCG). 12. The method according to claim 2 , wherein, the information relevant to the target event further comprises any combination of one or more of the following: an identifier of the target SCell; an identifier of a duplicate bearer corresponding to the target RLC entity; an identifier of a target RLC entity; an identifier of a logical channel group to which the logical channel corresponding to the target RLC entity belongs; a measurement result of a cell corresponding to the target RLC entity; a measurement result of a beam of the cell corresponding to the target RLC entity; a measurement result of a serving cell; a measurement result of a beam of the serving cell; a measurement result of cells of a serving frequency; a measurement result of beams of cells of a serving frequency; a measurement result of a serving cell in which a cell group to which the target SCell belongs is; a measurement result of a beam of a serving cell in which a cell group to which the target SCell belongs is; a measurement result of a cell corresponding to a serving frequ

Assignees

Inventors

Classifications

  • Random access procedures, e.g. with 4-step access · CPC title

  • in case of dual connectivity, e.g. decoupled uplink/downlink · CPC title

  • Hand-off preparation specially adapted for end-to-end data sessions · CPC title

  • H04W36/305Primary

    Handover due to radio link failure (control signalling for hand-off failure H04W36/0079) · CPC title

  • Connection re-establishment · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11290939B2 cover?
A method and an apparatus of processing data transmission failure are provided. The method includes determining a target event occurs, wherein the target event includes one or more of an event that a target RLC entity reaches a maximum number of retransmissions, an event that a physical layer of a target SCell is out of sync, and an event that a random access procedure of the target SCell fails…
Who is the assignee on this patent?
Vivo Mobile Communication Co Ltd
What technology area does this patent fall under?
Primary CPC classification H04W36/305. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 29 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).