IP Library Granted Patent US 12,414,167
Granted Patent B2
US 12,414,167 · App. 18/771,378 · Granted Sep 9, 2025

Method and device for communication between network entities in cloud LAN environment

Inventors: Jeongyeob Oak (Suwon-si, KR); Sejin Park (Suwon-si, KR); Jisoo Song (Suwon-si, KR); Wonil Lee (Seongnam-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W76/10H04L67/10H04W72/04H04W80/02
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,414,167
App. No.
18/771,378
Granted
Sep 9, 2025
Kind
B2
Abstract

The present disclosure relates to a research that has been conducted with the support of the “Cross-Departmental Giga KOREA Project” funded by the government (the Ministry of Science and ICT) in 2017 (No. GK17N0100, millimeter wave 5G mobile communication system development). The present disclosure relates to a communication technique for convergence of a 5G communication system for supporting a higher data transmission rate beyond a 4G system with an IoT technology, and a system therefor. The present disclosure may be applied to an intelligent service (for example, smart home, smart building, smart city, smart car or connected car, health care, digital education, retail business, security and safety-related service, etc.) on the basis of a 5G communication technology and an IoT-related technology.

Claims (81)

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

receiving, from a central unit (CU) through an interface between the CU and the DU, a request message for a user equipment (UE) context; and

transmitting, to the CU through the interface, a response message in response to the request message,

wherein the request message includes general packet radio service tunnelling protocol (GTP) tunnel information for a data radio bearer (DRB),

wherein the GTP tunnel information includes a tunnel endpoint identifier (TEID) and address information used for a user plane between the CU and the DU,

wherein the CU has a radio resource control (RRC) protocol and a packet data convergence protocol (PDCP) protocol, and

wherein the DU has 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 request message includes RRC information for configuring the UE, and

wherein the RRC information includes at least one MAC layer parameter and at least one PHY layer parameter.

3. The method of claim 1 , further comprising:

transmitting, to the CU, an uplink transfer message including an RRC container,

wherein the RRC container includes an RRC message transferred from the UE to the CU.

4. The method of claim 1 , further comprising:

receiving, from the CU, a downlink transfer message including an RRC container,

wherein the RRC container includes an RRC message transferred from the CU to the UE.

5. The method of claim 1 , further comprising:

receiving, from the CU, an update message for a control plane of the interface, the update message including system information associated with the CU; and

transmitting, to the CU, a response message in response to the request message.

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

transmitting, to a distributed unit (DU) through an interface between the CU and the DU, a request message for a user equipment (UE) context; and

receiving, from the DU through the interface, a response message in response to the request message,

wherein the request message includes general packet radio service tunnelling protocol (GTP) tunnel information for a data radio bearer (DRB),

wherein the GTP tunnel information includes a tunnel endpoint identifier (TEID) and address information used for a user plane between the CU and the DU,

wherein the CU has a radio resource control (RRC) protocol and a packet data convergence protocol (PDCP) protocol, and

wherein the DU has 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 request message includes RRC information for configuring the UE, and

wherein the RRC information includes at least one MAC layer parameter and at least one PHY layer parameter.

8. The method of claim 6 , further comprising:

receiving, from the DU, an uplink transfer message including an RRC container,

wherein the RRC container includes an RRC message transferred from the UE to the CU.

9. The method of claim 6 , further comprising:

transmitting, to the DU, a downlink transfer message including an RRC container,

wherein the RRC container includes an RRC message transferred from the CU to the UE.

10. The method of claim 6 , further comprising:

transmitting, to the DU, an update message for a control plane of the interface, the update message including system information associated with the CU; and

receiving, from the DU, a response message in response to the request message.

11. A device configured to perform functions of a distributed unit (DU), the device comprising:

at least one processor; and

a memory storing instructions that, when executed by the at least one processor, cause the device to:

receive, from a central unit (CU) through an interface between the CU and the DU, a request message for a user equipment (UE) context,

transmit, to the CU through the interface, a response message in response to the request message, and

perform a communication with a UE associated with the UE context,

wherein the request message includes general packet radio service tunnelling protocol (GTP) tunnel information for a data radio bearer (DRB),

wherein the GTP tunnel information includes a tunnel endpoint identifier (TEID) and address information used for a user plane between the CU and the DU,

wherein the CU has a radio resource control (RRC) protocol and a packet data convergence protocol (PDCP) protocol, and

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

12. The device of claim 11 ,

wherein the request message includes RRC information for configuring the UE, and

wherein the RRC information includes at least one MAC layer parameter and at least one PHY layer parameter.

13. The device of claim 11 ,

wherein the instructions, when executed by the at least one processor, cause the device to transmit, to the CU, an uplink transfer message including an RRC container, and

wherein the RRC container includes an RRC message transferred from the UE to the CU.

14. The device of claim 11 ,

wherein the instructions, when executed by the at least one processor, cause the device to receive, from the CU, a downlink transfer message including an RRC container, and

wherein the RRC container includes an RRC message transferred from the CU to the UE.

15. The device of claim 11 , wherein the instructions, when executed by the at least one processor, cause the device to:

receive, from the CU, an update message for a control plane of the interface, the update message including system information associated with the CU, and

transmit, to the CU, a response message in response to the request message.

16. A device configured to perform functions of a central unit (CU), the device comprising:

at least one processor; and

a memory storing instructions that, when executed by the at least one processor, cause the device to:

transmit, to a distributed unit (DU) through an interface between the CU and the DU, a request message for a user equipment (UE) context, and

receive, from the DU through the interface, a response message in response to the request message,

wherein the request message includes general packet radio service tunnelling protocol (GTP) tunnel information for a data radio bearer (DRB),

wherein the GTP tunnel information includes a tunnel endpoint identifier (TEID) and address information used for a user plane between the CU and the DU,

wherein the CU has a radio resource control (RRC) protocol and a packet data convergence protocol (PDCP) protocol, and

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

17. The device of claim 16 ,

wherein the request message includes RRC information for configuring the UE, and

wherein the RRC information includes at least one MAC layer parameter and at least one PHY layer parameter.

18. The device of claim 16 ,

wherein the instructions, when executed by the at least one processor, cause the CU to receive, from the DU, an uplink transfer message including an RRC container, and

wherein the RRC container includes an RRC message transferred from the UE to the CU.

19. The device of claim 16 ,

wherein the instructions, when executed by the at least one processor, cause the device to transmit, to the DU, a downlink transfer message including an RRC container, and

wherein the RRC container includes an RRC message transferred from the CU to the UE.

20. The device of claim 16 , wherein the instructions, when executed by the at least one processor, cause the device to:

transmit, to the DU, an update message for a control plane of the interface, the update message including system information associated with the CU, and

receive, from the DU, a response message in response to the request message.

Priority Claims (1)
KR 10-2017-0059624 · May 12, 2017 · national
Continuity (4)
Continuation 18316751 · May 12, 2023
Continuation 17497580 · Oct 8, 2021
Continuation 16611346
Related Publication 20240365405A1 · Oct 31, 2024
References Cited (21)
US 11653396B2 · Oak · 2023 [cited by examiner]
US 20130322293A1 · Kang · 2013 [cited by examiner]
US 20140087750A1 · Taori · 2014 [cited by examiner]
US 20140226481A1 · Dahod · 2014 [cited by examiner]
US 20140321419A1 · Kwon · 2014 [cited by examiner]
US 20150372728A1 · Rahman · 2015 [cited by examiner]
US 20160345204A1 · Godin · 2016 [cited by examiner]
US 20170373731A1 · Guo · 2017 [cited by examiner]
US 20180034515A1 · Guo · 2018 [cited by examiner]
US 20180376380A1 · Leroux · 2018 [cited by applicant]
US 20190069333A1 · Kim · 2019 [cited by examiner]
US 20200178326A1 · Sirotkin · 2020 [cited by examiner]
JP 200532752A · 2005 [cited by applicant]
WO 2020101340A1 · 2020 [cited by applicant]
Ericsson, ‘TP on Network deployment based on option 2’, R3-170684, 3GPP TSG-RAN WG3 Meeting #95, Feb. 6, 2017. [cited by applicant]
Nokia, ‘TP of Clean up for functional split’, R3-170416, 3GPP TSG-RAN WG3 Meeting #95, Feb. 6, 2017. [cited by applicant]
SK Telecom, ‘Considerations on function split for 5G deployment’, R3-171864, 3GPP TSG-RAN3 Meeting #96, Hangzhou, P. R. China, May 6, 2017. [cited by applicant]
Nokia, ‘General description of gNB-CU/DU split in TS 38.300’, R3-171431, 3GPP TSG-RAN3 Meeting #96, Hangzhou, P. R. China, May 5, 2017. [cited by applicant]
Samsung et al., F1 interface setup and the delivery of gNB-DU capability, R3-171703, 3GPP TSG-RAN WG3 Meeting #96, Hangzhou, P.R.China, May 5, 2017. [cited by applicant]
European Office Action dated Oct. 11, 2022, issued in European Patent Application No. 17909439.6. [cited by applicant]
Extended European Search Report dated Sep. 25, 2024, issued in European Patent Application No. 22855971.2. [cited by applicant]