IP Library Granted Patent US 12,302,434
Granted Patent B2
US 12,302,434 · App. 18/517,899 · Granted May 13, 2025

Method and device for network access

Inventors: Weiwei Wang (Beijing, CN); Lixiang Xu (Beijing, CN); Xiaowan Ke (Beijing, CN); Hong Wang (Beijing, CN)
Assignee: Samsung Electronics Co., Ltd.
H04W76/18H04W76/11H04W76/19H04W76/27H04W80/02H04W88/085H04W92/12
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,302,434
App. No.
18/517,899
Granted
May 13, 2025
Kind
B2
Abstract

The present disclosure relates to a pre-5 th -Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4 th -Generation (4G) communication system such as Long Term Evolution (LTE). The embodiments of the present invention provide methods and devices for network access. The method includes receiving a first request message forwarded by a distributed unit in a base station and indication information of the distributed unit with respect to the first request message, the first request message requesting to connect a user equipment to a network; determining a processing to be performed on the first request message based on the indication Information; and transmitting an indication of the determined processing to the distributed unit.

Claims (78)

1. A method performed by a central unit (CU) node, the method comprising:

receiving, from a distributed unit (DU) node, an initial uplink (UL) radio resource control (RRC) message including a RRC reestablishment request message received by the DU node from a user equipment (UE);

transmitting, to the DU node, a downlink (DL) RRC message transfer message including a RRC reestablishment message and information for retrieving UE context; and

receiving, from the DU node, a UL RRC message transfer message including a RRC reestablishment complete message received by the DU node from the UE,

wherein the information for retrieving UE context includes user identification information,

wherein the CU node serves a RRC protocol and packet data convergence protocol (PDCP) protocol, and

wherein the DU node serves a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer.

2. The method of claim 1 ,

wherein the user identification information is a first UE F1 application identity (UE F1AP ID) of the DU node.

3. The method of claim 2 ,

wherein the initial UL RRC message includes information on a cell-radio network temporary identifier (C-RNTI) associated with the UE, and information used by the CU node to determine that the DU node is able to serve the UE.

4. The method of claim 3 ,

wherein the information used by the CU node to determine that the DU node is able to serve the UE includes configuration information of first signaling radio bearer (SRB1), and

wherein the initial UL RRC message further includes information on a second UE F1 application identity (UE F1AP ID) of the DU node and information on new radio cell global identifier (NR CGI).

5. The method of claim 1 ,

wherein the initial UL RRC message is transmitted based on non-UE associated signaling, and

wherein the CU node further serves a service data adaptation protocol (SDAP) protocol.

6. A method performed by a distributed unit (DU) node, the method comprising:

receiving, from a user equipment (UE) a radio resource control (RRC) reestablishment request message;

transmitting, to a central unit (CU) node, an initial uplink (UL) RRC message including the RRC reestablishment request message;

receiving, from the CU node, a downlink (DL) RRC message transfer message including a RRC reestablishment message and information for retrieving UE context;

transmitting, to the UE, the RRC reestablishment message;

receiving, from the UE, a RRC reestablishment complete message; and

transmitting, to the CU node, a UL RRC message transfer message including the RRC reestablishment complete message,

wherein the information for retrieving UE context includes old-user identification information,

wherein the CU node serves a RRC protocol and packet data convergence protocol (PDCP) protocol, and

wherein the DU node serves a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer.

7. The method of claim 6 ,

wherein the user identification information is a first UE F1 application identity (UE F1AP ID) of the DU node.

8. The method of claim 7 ,

wherein the initial UL RRC message includes information on a cell-radio network temporary identifier (C-RNTI) associated with the UE, and information used by the CU node to determine that the DU node is able to serve the UE.

9. The method of claim 8 ,

wherein the information used by the CU node to determine that the DU node is able to serve the UE includes configuration information of first signaling radio bearer (SRB1), and

wherein the initial UL RRC message further includes information on a second UE F1 application identity (UE F1AP ID) of the DU node and information on new radio cell global identifier (NR CGI).

10. The method of claim 6 ,

wherein the initial UL RRC message is transmitted based on non-UE associated signaling, and

wherein the CU node further serves a service data adaptation protocol (SDAP) protocol.

11. An apparatus of a central unit (CU) node, comprising:

at least one transceiver; and

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

receive, from a distributed unit (DU) node, an initial uplink (UL) radio resource control (RRC) message including a RRC reestablishment request message received by the DU node from a user equipment (UE),

transmit, to the DU node, a downlink (DL) RRC message transfer message including a RRC reestablishment message and information for retrieving UE context, and

receive, from the DU node, a UL RRC message transfer message including a RRC reestablishment complete message received by the DU node from the UE,

wherein the information for retrieving UE context includes old-user identification information,

wherein the CU node serves a RRC protocol and packet data convergence protocol (PDCP) protocol, and

wherein the DU node serves a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer.

12. The apparatus of claim 11 ,

wherein the user identification information is a first UE F1 application identity (UE F1AP ID) of the DU node.

13. The apparatus of claim 12 ,

wherein the initial UL RRC message includes information on a cell-radio network temporary identifier (C-RNTI) associated with the UE, and information used by the CU node to determine that the DU node is able to serve the UE.

14. The apparatus of claim 13 ,

wherein the information used by the CU node to determine that the DU node is able to serve the UE includes configuration information of first signaling radio bearer (SRB1), and

wherein the initial UL RRC message further includes information on a second UE F1 application identity (UE F1AP ID) of the DU node and information on new radio cell global identifier (NR CGI).

15. The apparatus of claim 11 ,

wherein the initial UL RRC message is transmitted based on non-UE associated signaling, and

wherein the CU node further serves a service data adaptation protocol (SDAP) protocol.

16. An apparatus of a distributed unit (CU) (DU) node, comprising:

at least one transceiver; and

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

receive, from a user equipment (UE) a radio resource control (RRC) reestablishment request message,

transmit, to a central unit (CU) node, an initial uplink (UL) RRC message including the RRC reestablishment request message,

receive, from the CU node, a downlink (DL) RRC message transfer message including a RRC reestablishment message and information for retrieving UE context,

transmit, to the UE, the RRC reestablishment message,

receive, from the UE, a RRC reestablishment complete message, and

transmit, to the CU node, a UL RRC message transfer message including the RRC reestablishment complete message,

wherein the information for retrieving UE context includes old-user identification information,

wherein the CU node serves a RRC protocol and packet data convergence protocol (PDCP) protocol, and

wherein the DU node serves a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer.

17. The apparatus of claim 16 ,

wherein the user identification information is an first UE F1 application identity (UE F1AP ID) of the DU node.

18. The apparatus of claim 17 ,

wherein the initial UL RRC message includes information on a cell-radio network temporary identifier (C-RNTI) associated with the UE, and information used by the CU node to determine that the DU node is able to serve the UE.

19. The apparatus of claim 18 ,

wherein the information used by the CU node to determine that the DU node is able to serve the UE includes configuration information of first signaling radio bearer (SRB1), and

wherein the initial UL RRC message further includes information on a second UE F1 application identity (UE F1AP ID) of the DU node and information on new radio cell global identifier (NR CGI).

20. The apparatus of claim 16 ,

wherein the initial UL RRC message is transmitted based on non-UE associated signaling, and

wherein the CU node further serves a service data adaptation protocol (SDAP) protocol.

Priority Claims (5)
CN 201710898572.X · Sep 28, 2017 · national
CN 201710905999.8 · Sep 28, 2017 · national
CN 201710932365.1 · Oct 9, 2017 · national
CN 201711120988.5 · Nov 13, 2017 · national
CN 201810029454.X · Jan 11, 2018 · national
Continuity (3)
Continuation 17673393 · Feb 16, 2022
Continuation 16652227
Related Publication 20240090062A1 · Mar 14, 2024
References Cited (131)
US 8576794B1 · Dinan · 2013 [cited by applicant]
US 10791507B1 · Mukherjee et al. · 2020 [cited by applicant]
US 10932168B2 · Yang · 2021 [cited by examiner]
US 10939333B2 · Jin et al. · 2021 [cited by applicant]
US 11147107B2 · Oak · 2021 [cited by examiner]
US 11297663B2 · Wu · 2022 [cited by examiner]
US 11627042B2 · Gao et al. · 2023 [cited by applicant]
US 11997740B2 · Li · 2024 [cited by examiner]
US 12041587B2 · Sirotkin et al. · 2024 [cited by applicant]
US 12058702B2 · Abedini et al. · 2024 [cited by applicant]
US 12075482B2 · Byun et al. · 2024 [cited by applicant]
US 12156082B2 · Wu · 2024 [cited by examiner]
US 20080107269A1 · Gehrmann et al. · 2008 [cited by applicant]
US 20130322270A1 · Ko · 2013 [cited by applicant]
US 20140046882A1 · Wood · 2014 [cited by applicant]
US 20140177746A1 · Hsu et al. · 2014 [cited by applicant]
US 20160270113A1 · Sun et al. · 2016 [cited by applicant]
US 20170127362A1 · Tavildar et al. · 2017 [cited by applicant]
US 20170331577A1 · Parkvall et al. · 2017 [cited by applicant]
US 20170331785A1 · Xu et al. · 2017 [cited by applicant]
US 20170332372A1 · Lee et al. · 2017 [cited by applicant]
US 20180049270A1 · Kubota et al. · 2018 [cited by applicant]
US 20180092156A1 · Kim et al. · 2018 [cited by applicant]
US 20180213579A1 · Hong et al. · 2018 [cited by applicant]
US 20180234839A1 · Tenny et al. · 2018 [cited by applicant]
US 20180092085A1 · Shaheen et al. · 2018 [cited by applicant]
US 20180270716A1 · Takahashi et al. · 2018 [cited by applicant]
US 20180279218A1 · Park et al. · 2018 [cited by applicant]
US 20180338277A1 · Byun et al. · 2018 [cited by applicant]
US 20180367273A1 · Park et al. · 2018 [cited by applicant]
US 20180368109A1 · Kim · 2018 [cited by applicant]
US 20180368205A1 · Park et al. · 2018 [cited by applicant]
US 20190037631A1 · Byun et al. · 2019 [cited by applicant]
US 20190069333A1 · Kim · 2019 [cited by applicant]
US 20190082376A1 · Hong et al. · 2019 [cited by applicant]
US 20190150220A1 · Byun et al. · 2019 [cited by applicant]
US 20190159277A1 · Zhu · 2019 [cited by examiner]
US 20190166526A1 · Xu et al. · 2019 [cited by applicant]
US 20190182743A1 · Wong et al. · 2019 [cited by applicant]
US 20190215756A1 · Park et al. · 2019 [cited by applicant]
US 20190253966A1 · Park · 2019 [cited by examiner]
US 20190289570A1 · Kim et al. · 2019 [cited by applicant]
US 20190297634A1 · Dai et al. · 2019 [cited by applicant]
US 20190357117A1 · Cudak et al. · 2019 [cited by applicant]
US 20190380128A1 · Park et al. · 2019 [cited by applicant]
US 20200084663A1 · Park et al. · 2020 [cited by applicant]
US 20200196220A1 · Centoza et al. · 2020 [cited by applicant]
US 20200229049A1 · Wu et al. · 2020 [cited by applicant]
US 20200252847A1 · Park et al. · 2020 [cited by applicant]
US 20200336920A1 · Li et al. · 2020 [cited by applicant]
US 20210022031A1 · Liu et al. · 2021 [cited by applicant]
US 20210105174A1 · Pandey · 2021 [cited by applicant]
US 20210120441A1 · Futaki et al. · 2021 [cited by applicant]
US 20220061110A1 · Sirotkin · 2022 [cited by examiner]
US 20220110009A1 · Liu et al. · 2022 [cited by applicant]
US 20220141732A1 · Wu · 2022 [cited by examiner]
US 20220264383A1 · Teyeb · 2022 [cited by examiner]
US 20220369186A1 · Diao et al. · 2022 [cited by applicant]
US 20230199879A1 · Zhu et al. · 2023 [cited by applicant]
US 20230225008A1 · Malkamäki · 2023 [cited by examiner]
US 20240214879A1 · Chandrashekar et al. · 2024 [cited by applicant]
CN 106162730A · 2016 [cited by applicant]
CN 106937238A · 2017 [cited by applicant]
CN 106973403A · 2017 [cited by applicant]
KR 1020160135090A · 2016 [cited by applicant]
WO 2016163747A1 · 2016 [cited by applicant]
WO 2017045259A1 · 2017 [cited by applicant]
Korean Notice of Patent Grant with English translation dated Dec. 6, 2023; Korean Appln. No. 10-2022-7039328. [cited by applicant]
Chinese Office Action dated Mar. 2, 2022, issued in Chinese Application No. 201810029454.X. [cited by applicant]
European Search Report dated Mar. 23, 2022, issued in European Application No. 21215794.5. [cited by applicant]
Huawei, “F1AP procedures for RRC Connection Setup,” 3GPP TSG-RAN3 NR AdHoc, R3-172176, Qingdao, China, Jun. 27-29, 2017. [cited by applicant]
LG Electronics Inc., “Discussion on C-RNTI management in gNB-DU,” 3GPP TSG-RAN WG3 Meeting #97, R3-173004, Berlin, Germany, Aug. 21, 2017-Aug. 25, 2017. [cited by applicant]
LG Electronics Inc., “Consideration on C-RNTI during initial UE access,” 3GPP TSG-RAN WG3 Meeting NR Adhoc, R3-172342, Qingdao, China, Jun. 27, 2017-Jun. 29, 2017. [cited by applicant]
CATT, “Discussion on RRC message transfer,” 3GPP TSG-RAN WG3 Meeting #97, R3-172807, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
Notice of Patent Grant dated Aug. 9, 2022, issued in Korean Application No. 10-2020-7012500. [cited by applicant]
Chinese Office Action dated Feb. 18, 2023, issued in Chinese Application No. 201710898572.X. [cited by applicant]
CATT, “TP for 38.473 on UE Context Management function,” 3GPP TSG-RAN WG2 #97, R3-172816, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
NTT Docomo, Inc., “F1 parameter control,” 3GPP TSG RAN WG3 Meeting #97, R3-173294, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
Intel Corporation, “RAN functional split: intra MAC split description and benefits,” 3GPP TSG RAN WG3 Meeting #93-bis R3-162232, Sophia Antipolis, France, Oct. 10-14, 2016. [cited by applicant]
3rd Generation Partnership Project;Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15), 3GPP TS 38.401 V0.3.3, Aug. 2017. [cited by applicant]
Ericsson, “Description of solutions for centralised retransmission with Option 2,” 3GPP TSG-RAN WG3 Meeting #95bis R3-171169, Spokane, USA, Apr. 3-7, 2017. [cited by applicant]
European Search Report dated Jul. 7, 2023, issued in European Application No. 21215794.5. [cited by applicant]
Korean Office Action dated Jul. 19, 2023, issued in Korean Application No. 10-2022-7039328. [cited by applicant]
CATT, “Stage 2 TP for RRC Message Transfer between CU and DU”, 3GPP TSG-RAN WG3 Meeting #96, R3-171460, Hangzhou, China, May 15-19, 2017. [cited by applicant]
3GPP TS 38.401, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network NG-RAN Architecture description”, vol. 0.2.0, Jul. 2017. [cited by applicant]
China Telecom, “CU-DU Interface: On RRC Message Transport”, 3GPP TSG-RAN3 Meeting #96, R3-171590, Hangzhou, P.R. China, May 15-19, 2017. [cited by applicant]
Huawei, “PDCP Duplication for CU-DU”, 3GPP TSG RAN WG3 Meeting #97, R3-173128, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
3GPP TS 36.331, “3rd Generation Partnership Project Technical Specification Group Radio Access Network Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC) Protocol Specification”, vol. 15.2.… [cited by applicant]
3GPP TS 38.331, “3rd Generation Partnership Project: Technical Specification Group Radio Access Network: NR Radio Resource Control (RRC) Protocol Specification”, vol. 15.2.0, Jun. 2018. [cited by applicant]
3GPP TS 36.423, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP), vol. 15.2.0, Jun. 201… [cited by applicant]
3GPP TS 38.423, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP), vol. 15.0.0, Jun. 2018. [cited by applicant]
3GPP TS 38.473, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP), vol. 15.2.0, Jun. 2018. [cited by applicant]
Samsung, “Discussions on initial access procedure within high-layer split”, 3GPP TSG-RAN WG3 Meeting #97bis, R3-173847, Prague, Czech, Oct. 9-13, 2017. [cited by applicant]
Samsung, KT, “Initial access procedure considering CU-DU split”, 3GPP TSG-RAN WG3 Meeting #98, R3-174606, Reno, USA, Nov. 27-Dec. 1, 2017. [cited by applicant]
Ericsson, “Initial UE Access Full Procedure”, 3GPP TSG RAN WG3 Meeting #98 Tdoc, R3-175017, Reno, Nevada, USA, Nov. 27-Dec. 1, 2017. [cited by applicant]
Ericsson, “DU admission results in Initial UL RRC Message Transfer”, 3GPP TSG RAN WG3 Meeting #98 Tdoc, R3-175018, Reno, Nevada, USA, Nov. 27-Dec. 1, 2017. [cited by applicant]
Samsung, “TP for NSA BL CR on EN-DC X2 parameters over F1”, 3GPP TSG-RAN WG3 #99, R3-181400, Athens, Greece, Feb. 26-Mar. 2, 2018. [cited by applicant]
3GPP TSG-RAN WG3 #99, R3-181873, Sanya, China, Apr. 16-20, 2018. [cited by applicant]
3GPP TSG-RAN WG3 Meeting #99bis, R3-182195, Sanya, China, Apr. 16-20, 2018. [cited by applicant]
3GPP TS 38.425, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NR user plane protocol”, vol. 15.2.0, Jun. 2018. [cited by applicant]
3GPP TR 21.905, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications”, vol. 15.1.0, Dec. 2018. [cited by applicant]
3GPP TS 37.340,“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2”, vol. 15.2.0, Jun. 2018. [cited by applicant]
3GPP TS 38.300, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2”, vol. 15.2.0, Jun. 2018. [cited by applicant]
Huawei: “FIAP procedures for RRC Connection Setup”, 3GPP Draft; R3-172176 FIAP Procedures for RRC Connection Setup, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921… [cited by applicant]
LG Electronics Inc: “Discussion on C-RNTI management in gNB-DU”, 3GPP Draft; R3-173004 Discussion on C-RNTI Management in GNB-DU, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Luci… [cited by applicant]
LG Electronics Inc: “Consideration on C-RNTI during initial UE access”, 3GPP Draft; R3-172342 Consideration on C-RNTI During Initial UE Access, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, … [cited by applicant]
CATT: “Discussion on RRC message transfer”, 3GPP Draft; R3-172807 Discussion on Rrcmessage Transfer, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipol… [cited by applicant]
Extended European Search Report dated Nov. 5, 2020, issued in European Application No. 18862848.1. [cited by applicant]
U.S. Office Action dated Jul. 10, 2020, issued in U.S. Appl. No. 16/652,227. [cited by applicant]
“Technical Specification . . . ” (D1)3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN;Architecture description,(Release 15), Aug. 2017. [cited by applicant]
CATT, “TP for 38.473 on UE Context . . . ” (D2), 3GPP TSG-RAN WG2 #97, R3-172816, Aug. 21-25, 2017. [cited by applicant]
CATT, Discussion on UE Context Management function, 3GPP TSG-RAN WG2 #97, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
U.S. Final Office Action dated May 19, 2021, issued in U.S. Appl. No. 16/652,227. [cited by applicant]
European Search Report dated May 18, 2021, issued in European Application No. 21154971.2. [cited by applicant]
European Office Action dated May 21, 2021, issued in European Application No. 18862848.1. [cited by applicant]
CATT, Discussion on UE Context Management function, 3GPP TSG-RAN WG2 #97 R3-172814,Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
U.S. Notice of Allowance dated Apr. 9, 2021, issued in U.S. Appl. No. 16/835,985. [cited by applicant]
Samsung, Discussions on initial access procedure within high-layer, 3GPP TSG-RAN WG3 Meeting #97bis R3-173847. [cited by applicant]
CATT, TP on RRC message transfer for 38.401, 3GPP TSG-RAN WG3 Meeting #Ad Hoc R3-172213, Qingdao, China, Jun. 27-29, 2017. [cited by applicant]
Indian Office Action dated Sep. 9, 2021, issued in Indian Application No. 202027017858. [cited by applicant]
Chinese Office Action dated Nov. 25, 2021, issued in Chinese Application No. 201711120988.5. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description, (Release 15), 3GPP TS 38.401 V0.3.0, Aug. 2017. [cited by applicant]
European Search Report dated May 21, 2021, issued in European Application No. 18862848.1. [cited by applicant]
CATT, Discussion on UE Context Management, 3GPP TSG-RAN WG3, R3-172215, NR AdHoc, Qingdao, China Jun. 27-29. [cited by applicant]
IAESI, Load Management function in TS 38.470, Thales, Fairspectrum, VTT, 3GGP TSG-RAN WG3 Meeting, #98, R3-174347. [cited by applicant]
Ericsson, CMCC, Description of solutions for centralised retransmission with Option 2, 3GPP TSG-RAN WG3 Meeting #95bis, R3-171169, Spokane, USA, Apr. 3-7, 2017. [cited by applicant]
Huawei, Fast retransmission of lost PDUs, 3GPP TSG-RAN3 Meeting #97, R3-173114, Berlin, Germany, Aug. 21-25, 2017. [cited by applicant]
United States Office Action dated Jun. 6, 2024; U.S. Appl. No. 18/508,892. [cited by applicant]
U.S. Notice of Allowance dated Jan. 15, 2025; U.S. Appl. No. 18/508,892. [cited by applicant]
European Communication pursuant to Article 94(3) EPC dated Nov. 21, 2024; European Appln. No. 21 215 794.5-1215. [cited by applicant]
Indian Office Action dated Mar. 19, 2025; Indian Appln No. 202328064757. [cited by applicant]