IP Library › Granted Patent US 12,382,416
Granted Patent B2
US 12,382,416 · App. 17/711,729 · Granted Aug 5, 2025

Apparatus and method for service subscription through E2 interface in radio access network communication system

Inventors: Junhyuk Song (Suwon-si, KR); Jeongyeob Oak (Suwon-si, KR); Chungkeun Lee (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W60/005H04W8/18H04W88/06
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,382,416
App. No.
17/711,729
Granted
Aug 5, 2025
Kind
B2
Abstract

The 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). A method performed by an E2 node is provided. The method includes receiving a radio access network (RAN) intelligent controller (RIC) subscription request message from an RIC via an E2 interface, and the RIC subscription request message may include information indicating a network interface type.

Claims (68)

1. A method performed by an E2 node, the method comprising:

receiving, from a radio access network (RAN) intelligent controller (RIC) via an E2 interface, an RIC subscription request message,

wherein the RIC subscription request message comprises first information indicating a network interface type, second information indicating a node identifier (ID), and third information indicating a message protocol ID for an interface, and

wherein, in case that the first information indicates an X2 interface, the node ID indicates one of an evolved NodeB (eNB) ID or a new radio (NR) base station ID.

2. The method of claim 1 , wherein the network interface type comprises at least one of an F1 interface, an E1 interface, the X2 interface, an XN interface, a next generation (NG) interface, or an S1 interface.

3. The method of claim 1 ,

wherein the RIC subscription request message further comprises an RAN function ID, and

wherein the RIC subscription request message is a message for subscribing to a function corresponding to the RAN function ID of the E2 node.

4. The method of claim 1 ,

wherein the RIC subscription request message further comprises fourth information indicating an interface direction, and

wherein the interface direction comprises at least one of incoming or outgoing.

5. The method of claim 1 , further comprising:

transmitting, to the RIC, an RIC subscription response message, for accepting the RIC subscription request message.

6. The method of claim 1 ,

wherein the RIC is a near real time (RT) RIC, and

wherein the E2 node comprises an open RAN (O-RAN) distributed unit (O-DU), an O-RAN central unit-control plane (O-CU-CP), an O-RAN central unit-user plane (O-CU-UP), or an O-RAN evolved NodeB (O-eNB).

7. A method performed by a radio access network (RAN) intelligent controller (RIC), the method comprising:

transmitting, to an E2 node via an E2 interface, an RIC subscription request message,

wherein the RIC subscription request message comprises first information indicating a network interface type, second information indicating a node identifier (ID), and third information indicating a message protocol ID for an interface, and

wherein, in case that the first information indicates an X2 interface, the node ID indicates one of an evolved NodeB (eNB) ID or a new radio (NR) base station ID.

8. The method of claim 7 , wherein the network interface type comprises at least one of an F1 interface, an E1 interface, the X2 interface, an XN interface, an NG interface, or an S1 interface.

9. The method of claim 7 ,

wherein the RIC subscription request message further comprises an RAN function ID, and

wherein the RIC subscription request message is a message for subscribing to a function corresponding to the RAN function ID of the E2 node.

10. The method of claim 7 ,

wherein the RIC subscription request message further comprises fourth information indicating an interface direction, and

wherein the interface direction comprises at least one of incoming or outgoing.

11. The method of claim 7 , further comprising:

receiving, from the E2 node, an RIC subscription response message, for accepting the RIC subscription request message.

12. The method of claim 7 ,

wherein the RIC is a near real time (RT) RIC, and

wherein the E2 node comprises an O-RAN distributed unit (O-DU), an O-RAN central unit-control plane (O-CU-CP), an O-RAN central unit-user plane (O-CU-UP), or an O-RAN evolved NodeB (O-eNB).

13. An E2 node, the comprising:

a transceiver; and

a controller coupled with the transceiver, and configured to:

receive, from a radio access network (RAN) intelligent controller (RIC) via an E2 interface, an RIC subscription request message,

wherein the RIC subscription request message comprises first information indicating a network interface type, second information indicating a node identifier (ID), and third information indicating a message protocol ID for an interface, and

wherein, in case that the first information indicates an X2 interface, the node ID indicates one of an evolved NodeB (eNB) ID or a new radio (NR) base station ID.

14. A radio access network (RAN) intelligent controller (RIC) comprising:

a transceiver; and

a controller coupled with the transceiver, and configured to:

transmit, to an E2 node via an E2 interface, an RIC subscription request message,

wherein the RIC subscription request message comprises first information indicating a network interface type, second information indicating a node identifier (ID), and third information indicating a message protocol ID for an interface, and

wherein, in case that the first information indicates an X2 interface, the node ID indicates one of an evolved NodeB (eNB) ID or a new radio (NR) base station ID.

15. The E2 node of claim 13 , wherein the network interface type comprises at least one of an F1 interface, an E1 interface, the X2 interface, an XN interface, a next generation (NG) interface, or an S1 interface.

16. The E2 node of claim 13 ,

wherein the RIC subscription request message further comprises an RAN function ID, and

wherein the RIC subscription request message is a message for subscribing to a function corresponding to the RAN function ID of the E2 node.

17. The E2 node of claim 13 ,

wherein the RIC subscription request message further comprises fourth information indicating an interface direction, and

wherein the interface direction comprises at least one of incoming or outgoing.

18. The E2 node of claim 13 , wherein the controller is further configured to:

transmit, to the RIC, an RIC subscription response message, for accepting the RIC subscription request message.

19. The E2 node of claim 13 ,

wherein the RIC is a near real time (RT) RIC, and

wherein the E2 node comprises an open RAN (O-RAN) distributed unit (O-DU), an O-RAN central unit-control plane (O-CU-CP), an O-RAN central unit-user plane (O-CU-UP), or an O-RAN evolved NodeB (O-eNB).

20. The RIC of claim 14 , wherein the network interface type comprises at least one of an F1 interface, an E1 interface, the X2 interface, an XN interface, an NG interface, or an S1 interface.

21. The RIC of claim 14 ,

wherein the RIC subscription request message further comprises an RAN function ID, and

wherein the RIC subscription request message is a message for subscribing to a function corresponding to the RAN function ID of the E2 node.

22. The RIC of claim 14 ,

wherein the RIC subscription request message further comprises fourth information indicating an interface direction, and

wherein the interface direction comprises at least one of incoming or outgoing.

23. The RIC of claim 14 , wherein the controller is further configured to:

receive, from the E2 node, an RIC subscription response message, for accepting the RIC subscription request message.

24. The RIC of claim 14 ,

wherein the RIC is a near real time (RT) RIC, and

wherein the E2 node comprises an O-RAN distributed unit (O-DU), an O-RAN central unit-control plane (O-CU-CP), an O-RAN central unit-user plane (O-CU-UP), or an O-RAN evolved NodeB (O-eNB).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 1, 2022
From: SONG, JUNHYUK; OAK, JEONGYEOB; LEE, CHUNGKEUN
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 059476/0675 →
Continuity (3)
Continuation PCTKR2020013435 · Sep 29, 2020
Provisional Application 62908827 · Oct 1, 2019
Related Publication 20220225264A1 · Jul 14, 2022
References Cited (27)
US 10939333B2 · Jin et al. · 2021 [cited by applicant]
US 11159982B2 · Rajagopal · 2021 [cited by applicant]
US 11330645B2 · Jin et al. · 2022 [cited by applicant]
US 20050015494A1 · Adamczyk et al. · 2005 [cited by applicant]
US 20150358866A1 · Xu et al. · 2015 [cited by applicant]
US 20190223154A1 · Jia et al. · 2019 [cited by applicant]
US 20190297652A1 · Yang et al. · 2019 [cited by applicant]
US 20220225066A1 · Song et al. · 2022 [cited by applicant]
CN 111510959A · 2020 [cited by applicant]
CN 115004797A · 2022 [cited by applicant]
WO 2019157885A1 · 2019 [cited by applicant]
WO 2019183020A1 · 2019 [cited by applicant]
O-RAN Alliance, LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs, 3GPP TSG RAN Meeting #85, RP-192259, Newport Beach, USA, Sep. 16-20, 2019. [cited by applicant]
Indian Office Action dated Feb. 26, 2024, issued in Indian Application No. 202217025391. [cited by applicant]
Chinese Office Action dated Apr. 22, 2024, issued in Chinese Application No. 202080083160.0. [cited by applicant]
Czichy, “5G RAN optimization using the O-RAN software community's RIC (RAN Intelligent Controller)” Open Networking Summit (ONS) Europe 2019, Sep. 23, 2019. [cited by applicant]
Jana et al., “O-RAN SC Release A requirements” O-RAN Tokyo Workgroup Face-to-Face Meeting Information, Jun. 19, 2019. [cited by applicant]
Abeta et al., “O-RAN Alliance Standardization Trends” NTT Docomo Technical Journal, vol. 21, No. 1, 23019.07. [cited by applicant]
Schulz et al. “Network Architectures for Demanding 5G Performance Requirements” IEEE Vehicular Technology Magazine, vol. 14, Issue 2, Apr. 23, 2019. [cited by applicant]
Japanese Office Action dated Jul. 1, 2024, issued in Japanese Application No. JP2022-520519. [cited by applicant]
European Office Action dated Aug. 5, 2024, issued in European Application No. 20871980.7. [cited by applicant]
Chinese Office Action dated Sep. 9, 2024, issued in Chinese Application No. 202080083160.0. [cited by applicant]
O-RAN, working Group 3, “Near-Real-time, RAN Intelligent Controller, E2, Application Protocol (E2AP)” (XP009536365). [cited by applicant]
O-RAN, Working Group 3, “Near-Real-time RAN, Intelligent Controller, E2, Service Model, (E2SM)” XP009539264. [cited by applicant]
Extended European Search Report dated Oct. 6, 2022, issued in European Application No. 20871980.7. [cited by applicant]
Japanese Office Action dated Dec. 2, 2024, issued in Japanese Patent Application No. JP2022-520519. [cited by applicant]
Japanese Notice of Patent Grant dated May 7, 2025, issued in Japanese Patent Application No. JP2022-520519. [cited by applicant]
Cited By (2)
US 12,713,296 US 12,726,856