IP Library › Granted Patent US 12,628,228
Granted Patent B2
US 12,628,228 · App. 17/890,900 · Granted May 12, 2026

Re-establishment method and communication apparatus

Inventors: Liangliang Zhang (Beijing, CN); Junren Chang (Beijing, CN); Zhenhua Dai (Shanghai, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W76/19H04W36/0055H04W76/18H04W76/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,628,228
App. No.
17/890,900
Granted
May 12, 2026
Kind
B2
Abstract

A re-establishment method includes: If a link failure occurs in a handover procedure of a terminal device, the terminal device releases configuration information used in a source cell. The terminal device further determines a re-establishment request message based on configuration information used in the target cell, and sends the re-establishment request message in a re-establishment cell. A method for selecting a re-establishment cell and releasing configuration information when a link failure occurs in a dual active protocol stack (DAPS) handover procedure of the terminal device reduces memory consumption of the terminal device.

Claims (64)

1 . A re-establishment method, comprising:

receiving, by a terminal device, a handover command from a source network device, wherein the handover command indicates that the terminal device is to perform a dual active protocol stack (DAPS) handover from a source cell to a target cell, the handover command comprises first configuration information, and the first configuration information is configuration information used in the target cell;

performing, by the terminal device, the DAPS handover, and after successfully accessing the target cell and before receiving a first message from a target network device indicating to release the source cell, determining that link failure has occurred in the target cell;

releasing, by the terminal device, second configuration information, wherein the second configuration information is configuration information used in the source cell;

determining, by the terminal device, a first cell;

determining, by the terminal device, a radio resource control (RRC) re-establishment request message based on the first configuration information, wherein the RRC re-establishment request message comprises a cell-radio network temporary identifier (C-RNTI) used in the target cell and a short message authentication code for integrity (short MAC-I) used in the target cell; and

sending, by the terminal device, the RRC re-establishment request message in the first cell.

2 . The method according to claim 1 , wherein determining that link failure has occurred is further based on determining that one or more of the following cases occur in the target cell or the source cell:

an RRC connection reconfiguration failure occurs;

integrity check fails;

a quantity of radio link control (RLC) retransmissions reaches a preset threshold;

a timer T310 expires; or

random access fails and a timer T311 is not running.

3 . The method according to claim 1 , wherein determining that link failure has occurred is based on determining that an RRC connection reconfiguration failure occurs in the target cell, and wherein determining that the RRC connection reconfiguration failure occurs in the target cell comprises:

receiving a first reconfiguration message from the target network device, wherein the first reconfiguration message comprises third configuration information, and the third configuration information is new configuration information used in the target cell;

performing reconfiguration based on the first reconfiguration message; and

determining that the RRC connection reconfiguration failure occurs in the target cell.

4 . The method according to claim 3 , wherein the first reconfiguration message is received from the target network device in a DAPS handover procedure, after successfully accessing the target cell and before receiving the first message indicating to release the source cell from the target network device.

5 . The method according to claim 3 , wherein the first reconfiguration message further comprises first indication information, and the first indication information indicates to release the second configuration information.

6 . The method according to claim 1 , wherein determining that link failure has occurred is based on determining that one or more of the following cases occur in a handover procedure:

inter-system handover fails; or

intra-system handover fails.

7 . The method according to claim 1 , wherein the first cell is a cell to which the target network device belongs or a cell to which a non-source network device belongs.

8 . The method according to claim 1 , wherein the RRC re-establishment request message comprises second indication information, and the second indication information indicates the link failure.

9 . The method according to claim 1 , wherein the RRC re-establishment request message further comprises: a physical cell identifier (PCI) of the target cell.

10 . The method according to claim 1 , further comprising:

in a DAPS handover procedure, starting a timer after successfully accessing the target cell;

before receiving the first message indicating to release the source cell from the target network device, determining that the timer expires; and

sending a second message to the target network device, wherein the second message indicates that the first message has not been received or indicates that the first message failed to be received.

11 . An apparatus, comprising:

one or more processors; and

one or more memories coupled to the one or more processors and storing programming instructions;

wherein the one or more processors are configured to execute the programming instructions to facilitate performance of the following by the apparatus:

receiving a handover command from a source network device, wherein the handover command indicates that the apparatus is to perform a dual active protocol stack (DAPS) handover from a source cell to a target cell, the handover command comprises first configuration information, and the first configuration information is configuration information used in the target cell;

performing the DAPS handover, and after successfully accessing the target cell and before receiving a first message indicating to release the source cell from a target network device, determining that link failure has occurred in the target cell;

releasing second configuration information, wherein the second configuration information is configuration information used in the source cell;

determining a first cell;

determining a radio resource control (RRC) re-establishment request message based on the first configuration information, wherein the RRC re-establishment request message comprises a cell-radio network temporary identifier (C-RNTI) used in the target cell and a short message authentication code for integrity (short MAC-I) used in the target cell; and

sending the RRC re-establishment request message in the first cell.

12 . The apparatus according to claim 11 , wherein determining that link failure has occurred is further based on determining that one or more of the following cases occur in the target cell or the source cell:

an RRC connection reconfiguration failure occurs;

integrity check fails;

a quantity of radio link control (RLC) retransmissions reaches a preset threshold;

a timer T310 expires; or

random access fails and a timer T311 is not running.

13 . The apparatus according to claim 11 , wherein determining that link failure has occurred is based on determining that an RRC connection reconfiguration failure occurs in the target cell, wherein determining that the RRC connection reconfiguration failure occurs in the target cell comprises:

receiving a first reconfiguration message from the target network device, wherein the first reconfiguration message comprises third configuration information, and the third configuration information is new configuration information used in the target cell;

performing reconfiguration based on the first reconfiguration message; and

determining that the RRC connection reconfiguration failure occurs in the target cell.

14 . The apparatus according to claim 13 , wherein the first reconfiguration message is received from the target network device in a DAPS handover procedure, after successfully accessing the target cell and before receiving the first message indicating to release the source cell from the target network device.

15 . The apparatus according to claim 13 , wherein the first reconfiguration message further comprises first indication information, and the first indication information indicates to release the second configuration information.

16 . The apparatus according to claim 11 , wherein determining that link failure occurs is based on determining that one or more of the following cases occur in a handover procedure:

inter-system handover fails; or

intra-system handover fails.

17 . The apparatus according to claim 11 , wherein the first cell is a cell to which the target network device belongs or a cell to which a non-source network device belongs.

18 . The apparatus according to claim 11 , wherein the RRC re-establishment request message comprises second indication information, and the second indication information indicates the link failure.

19 . The apparatus according to claim 11 , wherein the RRC re-establishment request message further comprises: a physical cell identifier (PCI) of the target cell.

20 . A non-transitory computer-readable storage medium having processor-executable instructions stored thereon, wherein the processor-executable instructions, when executed, facilitate:

receiving a handover command from a source network device, wherein the handover command indicates a dual active protocol stack (DAPS) handover from a source cell to a target cell, the handover command comprises first configuration information, and the first configuration information is configuration information used in the target cell;

performing the DAPS handover, and after successfully accessing the target cell and before receiving a first message indicating to release the source cell from a target network device, determining that link failure has occurred in the target cell;

releasing second configuration information, wherein the second configuration information is configuration information used in the source cell;

determining a first cell;

determining a radio resource control (RRC) re-establishment request message based on the first configuration information, wherein the RRC re-establishment request message comprises a cell-radio network temporary identifier (C-RNTI) used in the target cell and a short message authentication code for integrity (short MAC-I) used in the target cell; and

sending the RRC re-establishment request message in the first cell.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2022
From: ZHANG, LIANGLIANG; CHANG, JUNREN; DAI, ZHENHUA
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 061486/0289 →
Priority Claims (1)
CN 202010103185.4 · Feb 19, 2020 · national
Continuity (2)
Continuation PCTCN2021076803 · Feb 19, 2021
Related Publication 20220394802A1 · Dec 8, 2022
References Cited (33)
US 20180279193A1 · Park et al. · 2018 [cited by applicant]
US 20190182881A1 · Teyeb et al. · 2019 [cited by applicant]
US 20200022035A1 · Kadiri et al. · 2020 [cited by applicant]
US 20200045764A1 · Kim · 2020 [cited by examiner]
US 20200314716A1 · Kim · 2020 [cited by examiner]
US 20210360503A1 · Lu et al. · 2021 [cited by applicant]
US 20230370933A1 · Kim · 2023 [cited by examiner]
CN 109327833A · 2019 [cited by applicant]
CN 110351896A · 2019 [cited by applicant]
CN 110637478A · 2019 [cited by applicant]
WO 2018014154A1 · 2018 [cited by applicant]
WO 2018117313A1 · 2018 [cited by applicant]
WO 2018182231A1 · 2018 [cited by applicant]
Intel Corporation, “Daps failure handling,” 3GPP TSG RAN WG2 Meeting #108, R2-1914840, Reno, USA, Total 5 pages, 3rd Generation Partnership Project, Valbonne, France (Nov. 18-22, 2019). [cited by applicant]
VIVO, “Discussion on the signaling procedures of the RUDI HO,” 3GPP TSG-RAN WG2 Meeting #107bis, R2-1912350, Chongqing, China, Total 4 pages, 3rd Generation Partnership Project, Valbonne, France (Oct. 14-18, 2019). [cited by applicant]
VIVO, “Single or two RRC messages for DAPS handover,” E-Meeting, 3GPP TSG-RAN WG2 Meeting #109 electronic, R2-2000382, Total 4 pages, 3rd Generation Partnership Project, Valbonne, France (Feb. 24-Mar. 6, 2020). [cited by applicant]
LG Electronics Inc., “Handling Excess of UE Capability in DAPS HO,” 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, R2-1916210, Revision of R2-1913864, Total 3 pages, 3rd Generation Partnership Project, Valbonne, France (Nov.… [cited by applicant]
Huawei et al., “Discussion on subsequent RRC procedures after DAPS handover,” 3GPP TSG-RAN WG2 #109bis-e, R2-2003046, Total 3 pages, 3rd Generation Partnership Project, Valbonne, France (Apr. 20-30, 2020). [cited by applicant]
Ericsson, “Open issues at fallback to source cell at DAPS handover,” 3GPP TSG-RAN WG2 #109 electronic, Elbonia, Tdoc R2-2000125, Total 8 pages (Feb. 24-Mar. 6, 2020). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 15),” 3GPP TS 3… [cited by applicant]
ETRI, “Source Cell Release in DAPS Handover,” 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, R2-1915041 (Revision of R2-1913798), Total 4 pages (Nov. 18-22, 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15),” 3GPP TS 38.300 V15.8.0, Total 99 pages (Dec. 2019). [cited by applicant]
Ericsson et al., “Introduction of Even futher Mobility enhancement in E-UTRAN,” 3GPP TSG-RAN2 Meeting #109-e, Electronic meeting, R2-2001129, Total 81 pages (Feb. 24-Mar. 6, 2020). [cited by applicant]
ETSI MCC, “Report of 3GPP TSG RAN2#107bis meeting, Chongqing, China,” 3GPP TSG-RAN WG2 meeting #108, R2-1914301, Total 3 pages (Oct. 14-18, 2019). [cited by applicant]
VIVO, “Clarification on stopping the source link failure,” 3GPP TSG-RAN WG2 Meeting #109 electronic, E-Meeting, R2-2000381, Total 4 pages (Feb. 24-Mar. 2, 2020). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state (Release 15),” 3GPP TS 38.304 V15.6.0, Total 30 pages (Dec.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 15),” 3GPP TS 38.322 V15.5.0, Total 33 pages (Mar. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15),” 3GPP TS 38.323 V15.6.0, Total 26 pages (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” 3GPP TS 38.331 V15.8.0, Total 532 pages (Dec. 2019). [cited by applicant]
Intel Corporation, “Control Plane Signaling Flow for DAPS Based RUDI HO,” 3GPP TSG RAN WG2 #107bis, Chongqing, China, R2-1912777 revision of R2-1909572, XP051804617, total 3 pages, 3rd Generation Partnership Project, Va… [cited by applicant]
China Telecom, “Stage-2 CR for Introduction of Even Further Mobility Enhancement in E-UTRAN,” 3GPP TSG-RAN2 Meeting #109, Athens, Greece, R2-2001653, XP051849944, total 35 pages, 3rd Generation Partnership Project, Valb… [cited by applicant]
Ericsson, “Subsequent RRC Procedures after DAPS Handover,” 3GPP TSG-RAN WG2 #109 electronic, Elbonia, Tdoc R2-2000129, XP051848492, total 28 pages, 3rd Generation Partnership Project, Valbonne, France (Feb. 24-Mar. 6, 2… [cited by applicant]
Vivo, “Discussion on the RLF and HOF for Daps,” 3GPP TSG-RAN WG2 Meeting #107, Prague, Czech Republic, R2-1909775 revision of R2-1905975, XP051767570, total 8 pages, 3rd Generation Partnership Project, Valbonne, France … [cited by applicant]