IP Library › Granted Patent US 12,200,795
Granted Patent B2
US 12,200,795 · App. 17/942,937 · Granted Jan 14, 2025

Failure processing method, handover method, terminal device, and network device

Inventors: Wenjie Peng (Shanghai, CN); Yi Guo (Shenzhen, CN); Mingzeng Dai (Shenzhen, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W76/18H04W36/0016H04W36/0033H04W36/0069H04W36/249
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,200,795
App. No.
17/942,937
Granted
Jan 14, 2025
Kind
B2
Abstract

This application provides failure processing methods, handover methods, terminal devices, and network devices. One method includes receiving a radio resource control (RRC) configuration of a secondary network device, if the RRC configuration of the secondary network device is from the secondary network device and the RRC configuration fails, sending, to a primary network device, first indication information for indicating a configuration failure of the RRC configuration.

Claims (49)

1. An apparatus comprising:

one or more processors; and

a memory having instructions stored thereon for execution by the one or more processors to cause the apparatus to perform operations comprising:

receiving, from a primary network device, a first radio resource control (RRC) configuration of a secondary network device;

sending, to the primary network device, a first message for requesting RRC connection reestablishment in response to the first RRC configuration fails;

receiving, from the secondary network device, a second RRC configuration of the secondary network device; and

sending, to the primary network device, a first indication indicating a configuration failure of the second RRC configuration in response to the second RRC configuration fails.

2. The apparatus according to claim 1 , wherein sending the first indication to the primary network device comprises:

sending, to the primary network device, a second message that comprises the first indication.

3. The apparatus according to claim 1 , wherein the first message comprises a second indication indicating a configuration failure of the first RRC configuration.

4. The apparatus according to claim 1 , wherein sending the first message comprises:

sending the first message to the primary network device in response to receiving a third indication by a first RRC entity of the apparatus from a second RRC entity of the apparatus, wherein the third indication indicates a configuration failure of the first RRC configuration, the first RRC entity controls a RRC connection between the primary network device and the apparatus, and the second RRC entity controls a RRC connection between the secondary network device and the apparatus.

5. An apparatus comprising:

one or more processors; and

a memory having instructions stored thereon for execution by the one or more processors to cause the apparatus to perform operations comprising:

in response to a first radio resource control (RRC) configuration of a secondary network device being received from the apparatus;

receiving, from a terminal device, a first message for requesting RRC connection reestablishment; and

in response to a second RRC configuration of the secondary network device being received from the secondary network device:

receiving, from the terminal device, a first indication indicating a configuration failure of the second RRC configuration; and

sending, to the secondary network device, a request for updating the second RRC configuration or releasing the secondary network device.

6. The apparatus according to claim 5 , wherein the first indication is comprised in the request.

7. The apparatus according to claim 5 , wherein receiving the first indication from the terminal device comprises:

receiving, from the terminal device, wherein a second message that comprises the first indication.

8. The apparatus according to claim 5 , wherein the first message comprises a second indication indicating a configuration failure of the first RRC configuration.

9. The apparatus according to claim 5 , wherein the operations further comprising:

sending, to the terminal device, a third message for reestablishing a signaling radio bearer (SRB).

10. A method comprising:

in response to a first radio resource control (RRC) configuration of a secondary network device being received from a primary network device;

receiving, by a primary network device from a terminal device, a first message for requesting RRC connection reestablishment; and

in response to a second RRC configuration of the secondary network device being received from the secondary network device:

receiving, by the primary network device from the terminal device, a first indication indicating a configuration failure of the second RRC configuration; and

sending, by the primary network device to the secondary network device, a request for updating the second RRC configuration or releasing the secondary network device.

11. The method according to claim 10 , wherein the first indication is comprised in the request.

12. The method according to claim 10 , wherein receiving, by the primary network device from the terminal device, the first indication comprises:

receiving, by the primary network device from the terminal device, a second message that comprises the first indication.

13. The method according to claim 10 , wherein the first message comprises a second indication indicating a configuration failure of the first RRC configuration.

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

sending, by the primary network device to the terminal device, a third message for reestablishing a signaling radio bearer (SRB).

15. A method comprising:

receiving, by a terminal device and from a primary network device, a first radio resource control (RRC) configuration of a secondary network device;

sending, by the terminal device to the primary network device, a first message for requesting RRC connection reestablishment in response to the first RRC configuration fails;

receiving, by the terminal device from the secondary network device, a second RRC configuration of the secondary network device;

sending, by the terminal device to the primary network device, a first indication indicating a configuration failure of the second RRC configuration in response to the second RRC configuration fails;

receiving, by the primary network device, the first indication; and

sending, by the primary network device to the secondary network device, a request for updating the second RRC configuration or releasing the secondary network device.

16. The method according to claim 15 , wherein the first indication is comprised in the request.

17. The method according to claim 15 , wherein the first message comprises a second indication indicating a configuration failure of the first RRC configuration.

18. The method according to claim 15 , wherein sending the first message comprises:

sending the first message to the primary network device in response to receiving a third indication by a first RRC entity of the terminal device from a second RRC entity of the terminal device, wherein the third indication indicates a configuration failure of the first RRC configuration, the first RRC entity controls a RRC connection between the primary network device and the terminal device, and the second RRC entity controls a RRC connection between the secondary network device and the terminal device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2022
From: PENG, WENJIE; GUO, YI; DAI, MINGZENG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 061529/0892 →
Priority Claims (1)
CN 201710314196.5 · May 5, 2017 · national
Continuity (3)
Continuation 16573465 · Sep 17, 2019
Continuation PCTCN2018085710 · May 4, 2018
Related Publication 20230007548A1 · Jan 5, 2023
References Cited (56)
US 10277453B2 · Wu · 2019 [cited by examiner]
US 10887812B2 · Nigam · 2021 [cited by examiner]
US 11089648B2 · Mitsui · 2021 [cited by examiner]
US 11184818B2 · Uchino · 2021 [cited by examiner]
US 20140004863A1 · Zhang · 2014 [cited by applicant]
US 20150201418A1 · Zhang et al. · 2015 [cited by applicant]
US 20150365984A1 · Lee et al. · 2015 [cited by applicant]
US 20160183321A1 · Wen · 2016 [cited by examiner]
US 20160192245A1 · He et al. · 2016 [cited by applicant]
US 20180049213A1 · Gholmieh · 2018 [cited by applicant]
US 20180049214A1 · Kubota · 2018 [cited by applicant]
US 20180302827A1 · Mitsui · 2018 [cited by examiner]
US 20190215886A1 · Lee · 2019 [cited by applicant]
US 20190246286A1 · Henttonen · 2019 [cited by applicant]
CN 101945452A · 2011 [cited by applicant]
CN 104378793 · 2015 [cited by applicant]
CN 104378793A · 2015 [cited by applicant]
CN 105992292A · 2016 [cited by applicant]
CN 107666727 · 2018 [cited by applicant]
EP 2983445 · 2016 [cited by applicant]
EP 3142452 · 2017 [cited by applicant]
EP 3496448A1 · 2019 [cited by applicant]
JP 2016225998 · 2016 [cited by applicant]
RU 2576019 · 2016 [cited by applicant]
WO 2014047878 · 2014 [cited by applicant]
WO 2014163143 · 2014 [cited by applicant]
WO 2014182229A1 · 2014 [cited by applicant]
WO 2015115959 · 2015 [cited by applicant]
WO 2015171053 · 2015 [cited by applicant]
WO 2017029796 · 2017 [cited by applicant]
Extended European Search Report in European Appln No. 23155569.9, dated Jun. 20, 2023, 11 pages. [cited by applicant]
Office Action in Chinese Appln. No. 201710314196.5, dated Feb. 16, 2023, 18 pages. [cited by applicant]
3GPP TS 36.331 V14.2.2, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification … [cited by applicant]
3GPP TS 36.423 V14.2.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-Utran); X2 application protocol (X2AP) (Release 14), … [cited by applicant]
3GPP TS 37.340 V0.1.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity, Stage 2 (Release 15),” May … [cited by applicant]
3GPP TS 38.331 V0.0.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network, NR, Radio Resource Control (RRC), Protocol specification (Release 15),” Mar. 2017, 13 pages. [cited by applicant]
CATT, “Discussion on MN/SN combined procedures,” 3GPP TSG-RAN WG2 Meeting #97bis, R2-1703095, Spokane, USA, Apr. 3-7, 2017, 2 pages. [cited by applicant]
EPO Partial Supplementary European Search Report issued in European Application No. 18794482.2 on May 12, 2020, 13 pages. [cited by applicant]
Ericsson, “SCG SRB configuration and use in LTE-NR interworking,” 3GPP TSG-RAN WG2 #97bis, R2-1702705, Spokane, USA, Apr. 3-7, 2017, 5 pages. [cited by applicant]
Ericsson, “UE capability coordination for LTE-NR interworking,” 3GPP TSG-RAN WG2 #97bis, R2-1702715, Spokane, USA, Apr. 3-7, 2017, 6 pages. [cited by applicant]
Ericsson, “UE capability signalling for tight interworking,” 3GPP TSG-RAN WG2 #96, Tdoc R2-168296; Reno, Nevada, XP051193002, Nov. 14-18, 2016, 3 pages. [cited by applicant]
Extended European Search Report issued in European Application No. 18794482.2 on Sep. 15, 2020, 16 pages. [cited by applicant]
Huawei, HiSilicon, “UE inter RAT capability handling for LTE-NR tight interworking and normal scenario,” 3GPP TSG-RAN WG2 Meeting #97bis, R2-1703652, Spokane, USA, Apr. 3-7, 2017, 3 pages. [cited by applicant]
Nokia, Alcatel-Lucent Shanghai Bell, “On UE capability and network node coordination aspects in LTE-NR tight interworking,” 3GPP TSG-RAN WG2 Meeting #95bis, R2-166243, Kaohsiung, Taiwan, Oct. 10-14, 2016, 9 pages. [cited by applicant]
Nokia, Alcatel-Lucent Shanghai Bell, “S-RLF with Tight Interworking,” 3GPP TSG-RAN WG2 Meeting #97bis, R2-1702631, Spokane, USA, Apr. 3-7, 2017, 5 pages. [cited by applicant]
Office Action issued in Indian Application No. 201937037003 on Mar. 8, 2021, 6 pages. [cited by applicant]
Office Action issued in Japanese Application No. 2019-550751 on Oct. 27, 2020, 8 pages { with English translation). [cited by applicant]
Office Action issued in Japanese Application No. 2021-010498 on Mar. 8, 2022, 8 pages (with English translation). [cited by applicant]
Office Action issued in Korean Application No. 2019-7028670 on Dec. 23, 2020, 14 pages (with English ranslation). [cited by applicant]
Office Action issued in Korean Application No. 2021-7005458 on May 21, 2021, 15 pages (with English translation). [cited by applicant]
Office Action issued in Russian Application No. 2019134196/07(067390) on Sep. 1, 2021, 16 pages (with English translation). [cited by applicant]
PCT International Search Report and Written Opinion in International Application No. PCT/CN2018/085710, dated Jul. 19, 2018, 15 pages (With English Translation). [cited by applicant]
Qualcomm Incorporated, “User Plane Details for Handover without WT Change,” 3GPP TSG-RAN2 Meeting #95bis, R2-167114, Kaohsiung, Taiwan, Oct. 10-14, 2016, 5 pages. [cited by applicant]
ZTE et al., “Consideration on the capability coordination for LTE/NR tight interworking,” 3GPP TSG-RAN WG2 Meeting #97bis, R2-1702833, Apr. 3-7, 2017, 8 pages. [cited by applicant]
ZTE et al., “Consideration on the handling of RRC procedure failure in LTE/NR tight interworking,” 3GPP TSG-RAN WG2 Meeting #97bis, R2-1702830, Spokane, USA, Apr. 3-7, 2017, 3 pages. [cited by applicant]
ZTE, “Further Consideration on Xn Procedures for NR/NR Tight-Interworking,” 3GPP TSG RAN WG3#95, R3-170533, Athens, Greece, Feb. 13-17, 2017, 3 pages. [cited by applicant]