IP Library › Granted Patent US 12,477,407
Granted Patent B2
US 12,477,407 · App. 18/348,810 · Granted Nov 18, 2025

Method and device for switching a serving cell and method and device supporting on-demand system information message

Inventors: Weiwei Wang (Beijing, CN); Xiaowan Ke (Beijing, CN); Hong Wang (Beijing, CN); Lixiang Xu (Beijing, CN)
Assignee: Samsung Electronics Co., Ltd.
H04W36/0027H04W36/0033H04W36/0061H04W36/0069H04W36/08H04W76/27H04W74/0833
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,477,407
App. No.
18/348,810
Granted
Nov 18, 2025
Kind
B2
Abstract

The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-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 disclosure provides a method and device for switching a serving cell.

Claims (65)

1 . A method performed by a first entity corresponding to a central unit (CU) of a base station in a wireless communication system, the method comprising:

transmitting, to a second entity corresponding to a distributed unit (DU) of the base station, a user equipment (UE) context setup request message, wherein the UE context setup request message includes identification information of a special cell (SpCell) and a first list of at least one candidate SpCell; and

based on the identification information of the SpCell not being acceptable by the second entity, receiving, from the second entity corresponding to the DU, UE context setup failure message as a response to the UE context setup request message, the UE context setup failure message including a second list of at least one potential SpCell associated with a selection of an opportune SpCell.

2 . The method of claim 1 ,

wherein the at least one candidate SpCell includes a candidate PCell of a master cell group (MCG) or a candidate primary secondary cell (PSCell) of a secondary cell group (SCG).

3 . The method of claim 1 ,

wherein the at least one potential SpCell is from the at least one candidate SpCell, and

wherein the UE context setup failure message further includes a cause associated with the SpCell which is not acceptable by the second entity.

4 . The method of claim 3 ,

wherein the cause indicates an overload associated with the SpCell.

5 . The method of claim 1 ,

wherein the UE context setup request message and the UE context setup failure message are transferred via an F1 interface between the first entity corresponding to the CU and the second entity corresponding to the DU.

6 . The method of claim 1 , further comprising:

transmitting, to the second entity corresponding to the DU, a UE context modification request message for requesting a modification of a UE context; and

receiving, from the second entity corresponding to the DU, a UE context modification response message for confirming the modification of the UE context.

7 . The method of claim 6 ,

wherein the UE context modification request message includes a third list of at least one secondary cell (SCell) to be setup, and

wherein the UE context modification response message includes a fourth list of at least one SCell failed to setup and a cause associated with an SCell failed to setup of the fourth list.

8 . The method of claim 1 , further comprising:

transmitting, to a second base station corresponding to a master node (MN), a modification required message for requesting a modification associated with the base station corresponding to a secondary node (SN); and

receiving, from the second base station corresponding to the MN, a modification confirm message for confirming the modification associated with the base station corresponding to the SN,

wherein the modification required message includes at least one of secondary cell group (SCG) configuration information, a list of at least one bearer to be released, or information on a tunnel endpoint at the SCG for delivering data.

9 . A first entity corresponding to a central unit (CU) of a base station in a wireless communication system, the first entity comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

transmit, to a second entity corresponding to a distributed unit (DU) of the base station, a user equipment (UE) context setup request message, wherein the UE context setup request message includes identification information of a special cell (SpCell) and a first list of at least one candidate SpCell; and

based on the identification information of the SpCell not being acceptable by the second entity, receive, from the second entity corresponding to the DU, a UE context setup failure message as a response to the UE context setup request message, the UE context setup failure message including a second list of at least one potential SpCell associated with a selection of an opportune SpCell.

10 . The first entity of claim 9 ,

wherein the at least one candidate SpCell includes a candidate PCell of a master cell group (MCG) or a candidate primary secondary cell (PSCell) of a secondary cell group (SCG), and

wherein the UE context setup request message and the UE context setup failure message are transferred via an F1 interface between the first entity corresponding to the CU and the second entity corresponding to the DU.

11 . The first entity of claim 9 ,

wherein the at least one potential SpCell is from the at least one candidate SpCell, and

wherein the UE context setup failure message further includes a cause associated with the SpCell which is not acceptable by the second entity.

12 . The first entity of claim 9 , wherein the at least one processor is further configured to:

transmit, to the second entity corresponding to the DU, a UE context modification request message for requesting a modification of a UE context, and

receive, from the second entity corresponding to the DU, a UE context modification response message for confirming the modification of the UE context,

wherein the UE context modification request message includes a third list of at least one SCell to be setup, and

wherein the UE context modification response message includes a fourth list of at least one SCell failed to setup and a cause associated with an SCell failed to setup of the fourth list.

13 . A method performed by a second entity corresponding to a distributed unit (DU) of a base station in a wireless communication system, the method comprising:

receiving, from a first entity corresponding to a central unit (CU) of the base station, a user equipment (UE) context setup request message, wherein the UE context setup request message includes identification information of a special cell (SpCell) and a first list of at least one candidate SpCell; and

based on the identification information of the SpCell not being acceptable by the second entity, transmitting, to the first entity corresponding to a central unit (CU) of the base station, a UE context setup failure message as a response to the UE context setup request message, the UE context setup failure message including a second list of at least one potential SpCell associated with a selection of an opportune SpCell.

14 . The method of claim 13 ,

wherein the at least one candidate SpCell includes a candidate PCell of a master cell group (MCG) or a candidate primary secondary cell (PSCell) of a secondary cell group (SCG), and

wherein the UE context setup request message and the UE context setup failure message are transferred via an F1 interface between the first entity corresponding to the CU and the second entity corresponding to the DU.

15 . The method of claim 13 ,

wherein the at least one potential SpCell is from the at least one candidate SpCell, and

wherein the UE context setup failure message further includes a cause associated with the SpCell which is not acceptable by the second entity.

16 . The method of claim 15 ,

wherein the cause indicates an overload associated with the SpCell.

17 . The method of claim 13 , further comprising:

receiving, from the first entity corresponding to the CU, a UE context modification request message for requesting a modification of a UE context; and

transmitting, to the first entity corresponding to the CU, a UE context modification response message for confirming the modification of the UE context,

wherein the UE context modification request message includes a third list of at least one SCell to be setup, and

wherein the UE context modification response message includes a fourth list of at least one SCell failed to setup and a cause associated with an SCell failed to setup of the fourth list.

18 . A second entity corresponding to a distributed unit (DU) of a base station in a wireless communication system, the second entity comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

receive, from a first entity corresponding to a central unit (CU) of the base station, a user equipment (UE) context setup request message, wherein the UE context setup request message includes identification information of a special cell (SpCell) and a first list of at least one candidate SpCell, and

based on the identification information of the SpCell not being acceptable by the second entity, transmit, to the first entity corresponding to a central unit (CU) of the base station, a UE context setup failure message as a response to the UE context setup request message, the UE context setup failure message including a second list of at least one potential SpCell associated with a selection of an opportune SpCell.

19 . The second entity of claim 18 ,

wherein the at least one candidate SpCell includes a candidate PCell of a master cell group (MCG) or a candidate primary secondary cell (PSCell) of a secondary cell group (SCG), and

wherein the UE context setup request message and the UE context setup failure message are transferred via an F1 interface between the first entity corresponding to the CU and the second entity corresponding to the DU.

20 . The second entity of claim 18 ,

wherein the at least one potential SpCell is from the at least one candidate SpCell, and

wherein the UE context setup failure message further includes a cause associated with the SpCell which is not acceptable by the second entity.

Priority Claims (3)
CN 201710459634.7 · Jun 16, 2017 · national
CN 201710681888.3 · Aug 10, 2017 · national
CN 201810437646.4 · May 9, 2018 · national
Continuity (4)
Continuation 17227853 · Apr 12, 2021
Continuation 16712380 · Dec 12, 2019
Continuation In Part PCTKR2018006866 · Jun 18, 2018
Related Publication 20230354110A1 · Nov 2, 2023
References Cited (52)
US 8660076B2 · Park et al. · 2014 [cited by applicant]
US 9071962B2 · Janakiraman et al. · 2015 [cited by applicant]
US 9736705B2 · Yun et al. · 2017 [cited by applicant]
US 20150264621A1 · Sivanesan et al. · 2015 [cited by applicant]
US 20150271726A1 · Kim et al. · 2015 [cited by applicant]
US 20150327322A1 · Huang et al. · 2015 [cited by applicant]
US 20150365852A1 · Xu et al. · 2015 [cited by applicant]
US 20160044744A1 · Lee et al. · 2016 [cited by applicant]
US 20160192244A1 · Worrall et al. · 2016 [cited by applicant]
US 20170127362A1 · Tavildar et al. · 2017 [cited by applicant]
US 20170223694A1 · Han et al. · 2017 [cited by applicant]
US 20170223762A1 · Worrall et al. · 2017 [cited by applicant]
US 20170331670A1 · Parkvall et al. · 2017 [cited by applicant]
US 20180014229A1 · Chiba et al. · 2018 [cited by applicant]
US 20180288826A1 · Chiba · 2018 [cited by applicant]
US 20180368109A1 · Kim · 2018 [cited by applicant]
US 20190132066A1 · Park et al. · 2019 [cited by applicant]
US 20190132778A1 · Park · 2019 [cited by examiner]
US 20190380158A1 · Gao · 2019 [cited by examiner]
CN 105453643A · 2016 [cited by applicant]
CN 105612776A · 2016 [cited by applicant]
CN 106538034A · 2017 [cited by applicant]
CN 107006055A · 2017 [cited by applicant]
KR 101496591B1 · 2015 [cited by applicant]
KR 1020150110275A · 2015 [cited by applicant]
KR 1020150133211A · 2015 [cited by applicant]
KR 101640681B1 · 2016 [cited by applicant]
KR 1020160108467A · 2016 [cited by applicant]
KR 1020160108468A · 2016 [cited by applicant]
KR 101988093B1 · 2019 [cited by applicant]
KR 102157618B1 · 2020 [cited by applicant]
WO 2016020146A1 · 2016 [cited by applicant]
WO 2016021821A1 · 2016 [cited by applicant]
WO 2016112970A1 · 2016 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15)”, 3GPP Draft; 38.401-010-RM, 3RD Generation Partnership Project (3GPP), Mobile Compe… [cited by applicant]
Nokia et al., “Introduction of F1 interface functions”, 3GPP Draft; R3-171436 38.473 Introduction of F1 Interface Functions. 3RD Generation Partnership Project (3GPP). Mobile Competence Centre; 650, Route Des Lucioles; … [cited by applicant]
CATT, “Consideration on the RRC message transfer between CU and DU”, 3GPP T5G RAN WG3 Meeting #96, Hangzhou, China, May 15-19, 2017, R3-171456, May 19, 2017. [cited by applicant]
Samsung, KT, SK Telecom, “On-demand 51 support in high layer functional split”, 3GPP T5G-RAN Ad Hoc, Qingdao, P. R. China, Jun. 27-29, 2017, R3-172250, Jun. 20, 2017. [cited by applicant]
Extended European Search Report dated Aug. 25, 2020, issued in European Application No. 18817615.0-1212. [cited by applicant]
Chinese Office Action dated Nov. 4, 2020, issued in Chinese Application No. 201810437646 .4. [cited by applicant]
3GPP TSG RAN WG3 Meeting #96, R3-171598 “TP for UE Radio Bearer Management”, ZTE Corporation, May 2017, pp. 1-6. [cited by applicant]
AT&T, “RRM/RRC Design for LTE-NR Tight Integration”, 3GPP TSG-RAN WG2 Meeting #97, R2-1701140, Athens, Greece, Feb. 13-17, 2017, Feb. 2, 2017. [cited by applicant]
3GPP TS 36.300 V14.2.0 “Overall description”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial… [cited by applicant]
3GPP TR 38.912 V1.0.0 “Study on New Radio (NR) Access Technology”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology (Release 14), Mar. 16,… [cited by applicant]
Chinese Office Action dated Sep. 3, 2021, issued in Chinese Application No. 201710681888.3. [cited by applicant]
Huawei, Discussions on mobility procedures, 3GPP TSG-RAN3 Meeting#96, R3-171815, May 6, 2017, Hang Zhou, China. [cited by applicant]
Chinese Office Action dated Apr. 15, 2022, issued in Chinese Application No. 201710681888.3. [cited by applicant]
Mobile Communications, Issue No. 03, Discussion on Wireless Access Network Architecture, Liu Liang, Chen Zhuo, Jin Ba, Huang Xue-yan, Liu Guang-yi (China Mobile Group Design Institute Co., Ltd., Beijing 100032, China), … [cited by applicant]
Chinese Notice of Allowance dated Sep. 27, 2022, issued in Chinese Application No. 201710681888.3. [cited by applicant]
Korean Notice of Allowance dated Jul. 13, 2023, issued in Korean Application No. 10-2019-7038023. [cited by applicant]
Indian Office Action dated Oct. 25, 2023, issued in Indian Application No. 202248027175. [cited by applicant]
Korean Notice of Allowance dated May 26, 2024, issued in Korean Patent Application No. 10-2023-7035189. [cited by applicant]