IP Library › Granted Patent US 12,446,092
Granted Patent B2
US 12,446,092 · App. 17/630,003 · Granted Oct 14, 2025

Master node, secondary node, and methods therefor

Inventors: Hisashi Futaki (Tokyo, JP); Sadafuku Hayashi (Tokyo, JP)
Assignee: NEC CORPORATION
H04W76/19H04W76/15H04W76/27H04W76/34
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,446,092
App. No.
17/630,003
Granted
Oct 14, 2025
Kind
B2
Abstract

A master node (MN) ( 1 ) controls the MN ( 1 ) to enable, for a radio terminal ( 3 ), dual connectivity using a Master Cell Group (MCG) provided by the MN ( 1 ) and a Secondary Cell Group (SCG) provided by a secondary node (SN) ( 2 ). The MN ( 1 ) sends to the SN ( 2 ) a first message related to a modification or release of a configuration or resource in the SN ( 2 ) regarding the dual connectivity. The first message explicitly or implicitly indicates that the modification or release is related to a failure of the MCG or recovery from the failure of the MCG. This, for example, allows the SN to distinguish a message regarding modification or release of an SN configuration (or resource) sent from an MN to the SN for recovery from an MCG failure from other messages.

Claims (28)

1. A method for a Secondary node of a dual connectivity with a Master node, the method comprising:

communicating, with a user terminal, using a Secondary Cell Group (SCG), which is a group of serving cells associated with the Secondary node;

receiving a Radio Resource Control (RRC) Transfer message from the Master node if radio link failure is detected for a Master Cell Group (MCG) which is a group of serving cells associated with the Master node, the RRC Transfer message including a Packet Data Convergence Protocol control-plane (PDCP-C) Protocol Data Unit (PDU) encapsulating a RRC Reconfiguration message, the RRC Transfer message including, in addition to the RRC Reconfiguration message, information indicating to the Secondary node that the RRC Reconfiguration message relates to a recovery of the MCG failure; and

transmitting the RRC Reconfiguration message to the user terminal before a release of resources.

2. The method according to claim 1 , further comprising receiving a Release Request message from the Master node.

3. The method according to claim 2 , further comprising releasing the resources based on the Release Request message.

4. A method for a Master node of a dual connectivity with a Secondary node, the method comprising:

communicating, with a user terminal, using an MCG, which is a group of serving cells associated with the Master node; and

transmitting a RRC Transfer message to the Secondary node if radio link failure is detected for the MCG, the RRC Transfer message including a PDCP-C PDU encapsulating a RRC Reconfiguration message, the RRC Transfer message including, in addition to the RRC Reconfiguration message, information indicating to the Secondary node that the RRC Reconfiguration message relates to a recovery of the MCG failure,

wherein the RRC Reconfiguration message is transmitted to the user terminal before a release of resources.

5. The method according to claim 4 , further comprising transmitting a Release Request message to the Secondary node.

6. The method according to claim 5 , wherein the Release Request message causes the Secondary Node to release the resources based on the Release Request message.

7. A Secondary node of a dual connectivity with a Master node, the Secondary node comprising:

at least one memory; and

at least one processor coupled to the memory and configured to:

communicate, with a user terminal, using an SCG, which is a group of serving cells associated with the Secondary node;

receive a RRC Transfer message from the Master node if radio link failure is detected for an MCG which is a group of serving cells associated with the Master node, the RRC Transfer message including a PDCP-C PDU encapsulating a RRC Reconfiguration message, the RRC Transfer message including, in addition to the RRC Reconfiguration message, information indicating to the Secondary node that the RRC Reconfiguration message relates to a recovery of the MCG failure; and

transmit the RRC Reconfiguration message to the user terminal before a release of resources.

8. The Secondary node according to claim 7 , wherein the at least one processor is further configured to receive a Release Request message from the Master node.

9. The Secondary node according to claim 8 , wherein the at least one processor is further configured to release the resources based on the Release Request message.

10. A Master node of a dual connectivity with a Secondary node, the Master node comprising:

at least one memory; and

at least one processor coupled to the memory and configured to:

communicate, with a user terminal, using an MCG, which is a group of serving cells associated with the Master node; and

transmit a RRC Transfer message to the Secondary node if radio link failure is detected for the MCG, the RRC Transfer message including a PDCP-C PDU encapsulating a RRC Reconfiguration message, the RRC Transfer message including, in addition to the RRC Reconfiguration message, information indicating to the Secondary node that the RRC Reconfiguration message relates to a recovery of the MCG failure,

wherein the RRC Reconfiguration message is transmitted to the user terminal before a release of resources.

11. The Master node according to claim 10 , wherein the at least one processor is further configured to transmit a Release Request message to the Secondary node.

12. The Master node according to claim 11 , wherein the Release Request message causes the Secondary Node to release the resources based on the Release Request message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 25, 2022
From: FUTAKI, HISASHI; HAYASHI, SADAFUKU
To: NEC CORPORATION
Reel/Frame 058762/0100 →
Priority Claims (1)
JP 2019-139251 · Jul 29, 2019 · national
Continuity (1)
Related Publication 20220256637A1 · Aug 11, 2022
References Cited (44)
US 11785483B2 · Zhang et al. · 2023 [cited by applicant]
US 20190182881A1 · Teyeb et al. · 2019 [cited by applicant]
US 20200113008A1 · Luo et al. · 2020 [cited by applicant]
US 20200154268A1 · Liu et al. · 2020 [cited by applicant]
US 20200162211A1 · Wang et al. · 2020 [cited by applicant]
US 20200344719A1 · Luo et al. · 2020 [cited by applicant]
US 20210204194A1 · Cao et al. · 2021 [cited by applicant]
US 20210204199A1 · Yu et al. · 2021 [cited by applicant]
US 20210243613A1 · Khanfouci et al. · 2021 [cited by applicant]
US 20210243672A1 · Deshmukh et al. · 2021 [cited by applicant]
US 20210385897A1 · Purkayastha · 2021 [cited by examiner]
US 20220086710A1 · Xu · 2022 [cited by examiner]
US 20220174771A1 · Baek · 2022 [cited by examiner]
US 20230354110A1 · Wang et al. · 2023 [cited by applicant]
CN 108632902A · 2018 [cited by applicant]
CN 108633018A · 2018 [cited by applicant]
EP 3331281A1 · 2018 [cited by applicant]
JP 2018174597A · 2018 [cited by applicant]
WO 2018182231A1 · 2018 [cited by applicant]
WO 2018219039A1 · 2018 [cited by applicant]
WO 2019093940A1 · 2019 [cited by applicant]
WO WO2020135850A1 · 2020 [cited by examiner]
ETSI TS 138 423 V15.3.0; 5G; NG-RAN; Xn Application Protocol (XnAP); (3GPP TS 38.423 version 15.3.0 Release 15); May 2019 (Year: 2019). [cited by examiner]
JP Office Action for JP Application No. 2021-536652, mailed on April 4. 2023 with English Translation. [cited by applicant]
Google Inc., Correction to RRC transfer, 3GPP TSG RAN WG3 #103, R3-191154, Feb. 25, 2019. [cited by applicant]
US Office Action for U.S. Appl. No. 17/628,326, mailed on Feb. 5, 2024. [cited by applicant]
Chinese Office Action for CN Application No. 202080063213.2, mailed on Oct. 13, 2023 with English Translation. [cited by applicant]
Extended European Search Report for EP Application No. 20848546.6, dated Dec. 13, 2022. [cited by applicant]
Rapporteur (ZTE Corporation), “Agreements for MR-DC with 5GC”, 3GPP Draft, R2-1819036, Nov. 12-16, 2018. [cited by applicant]
OPPO, “Fast MCG recovery for MR-DC enhancement”, 3GPP Draft, R2-1905590, Apr. 13-17, 2019. [cited by applicant]
Apple, “MCG Fast recovery”, 3GPP Draft, R2-1907173, May 13-17, 2019. [cited by applicant]
Indian Office Action for IN Application No. 202217004886, mailed on Jul. 6, 2022. [cited by applicant]
International Search Report for PCT Application No. PCT/JP2020/022864, mailed on Sep. 24, 2020. [cited by applicant]
International Search Report for PCT Appiication No. PCT/JP2020/023857, mailed on Sep. 24, 2020. [cited by applicant]
R2-1901414, Ericsson, “Fast MCG recovery in MR-DC”, BGPP TSG-RAN WG2#105, Feb. 2019, pp. 1-2. [cited by applicant]
R2-1901416, Ericsson, “Fast MCG recovery in (NG)EN-DC”, 3GPP TSG-RAN WG2#105, Feb. 2019, pp. 1-3. [cited by applicant]
R2-1900113, Qualcomm Incorporated, “Fast Recovery from MCG faiiure”, 3GPP TSG-RAN WG2#105, Feb. 2019, pp. 1-3. [cited by applicant]
R2-1907493, Huawei et al., “MCG faiiure recovery via spiit SRB1”, 3GPP TSG-RAN WG2#106, May 2019, pp. 1-5. [cited by applicant]
R2-1907497, Huawei et al., “Discussion on MCG faiiure recovery via SRB3”, 3GPP TSG-RAN WG2#106, May 2019, pp. 1-4. [cited by applicant]
R2-1907506, Huawei et al., Discussion on PDCP SN issue for MCG faiiure recovery, 3GPP TSG RAN WG2 #106, May 2019, pp. 1-3. [cited by applicant]
R2-1906921, CATT, “Fallback mechanism for fast recovery”, 3GPP TSG-RAN WG2 #106, May 2019, pp.1-3 (Cited in the ISR in the reiated intemational Application No. PCT/JP2020/022864). [cited by applicant]
R2-1905826, Vivo, “Additional use cases for MCG fast recovery”, 3GPP TSG RAN WG2 #106, May 2019, pp. 1-5 (Cited in the ISR in the related International Application No. PCT/JP2020/022864). [cited by applicant]
Extended European Search Report for EP Application No. 20847082.3, dated on Sep. 9, 2022. [cited by applicant]
CATT: “Fallback mechanisum for fast recovery”, 3GPP Draft; 3GPP TSG-RAN WG2 Meeting #105bis, R2-1903328, Apr. 6, 2019. [cited by applicant]