IP Library › Granted Patent US 11,412,554
Granted Patent B2
US 11,412,554 · App. 16/393,753 · Granted Aug 9, 2022

E1 interface setup in NG-RAN

Inventors: Feng Yang (Beijing, CN); Alexander Sirotkin (Tel-Aviv, IL); Jaemin Han (Hillsboro, OR); Xu Zhang (Beijing, CN)
Assignee: Apple Inc.
H04W76/10H04W80/04H04W92/16
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 11,412,554
App. No.
16/393,753
Granted
Aug 9, 2022
Kind
B2
Abstract

Systems and methods of setting up an E1 interface for a gNB are described. A transmitting entity of the gNB-CU-CP and gNB-CU-UP initiates the first TNL association between the gNB-CU-CP and gNB-CU-UP, and is also limited to initiating the E1 Setup procedure. The transmitting entity sends an E1 SETUP REQUEST message to set up the E1 interface. Afterwards, a message is received from the receiving entity. The transmitting entity determines that the setup of the E1 interface is successful if the message contains IEs of an E1 SETUP RESPONSE message. The types of IEs include a message type IE and a name of the transmitting entity.

Claims (63)

1. A computer-readable non-transitory storage medium that stores instructions for execution by one or more processors of a next generation NodeB (gNB), the one or more processors to configure the gNB to, when the instructions are executed:

initiate, by one of a central unit control plane (gNB-CU-CP) and a central unit user plane (gNB-CU-UP), a first Transport Network Layer (TNL) association between the gNB-CU-CP and gNB-CU-UP; and

after the first TNL association is operational, initiate an E1 Setup procedure to set up an E1 interface between the gNB-CU-CP and the gNB-CU-UP,

wherein initiation of the E1 Setup procedure is performed by the gNB-CU-CP when the gNB-CU-CP initiated the first TNL association, and

wherein initiation of the E1 Setup procedure is performed by the gNB-CU-UP when the gNB-CU-UP initiated the first TNL association.

2. The medium of claim 1 , wherein:

when initiation of the E1 Setup procedure is performed by the gNB-CU-UP, and

the E1 Setup procedure is a gNB-CU-UP E1 Setup procedure.

3. The medium of claim I, wherein:

when initiation of the E1 Setup procedure is performed by the gNB-CU-CP, and

the E1 Setup procedure is a gNB-CU-CP E1 Setup procedure.

4. The medium of claim 1 , wherein the one or more processors further configure the gNB to, when the instructions are executed:

initiate the E1 Setup procedure by transmission of an E1 SETUP REQUEST message, and

determine that setup of the E1 interface is successful in response to reception of a message that contains information elements (IEs) of an E1 SETUP RESPONSE message in response to transmission of the E1 SETUP REQUEST message, wherein the E1 SETUP REQUEST message and E1 SETUP RESPONSE message sent by a same entity of the gNB-CU-CP and gNB-CU-UP consist of identical types of the IEs.

5. The medium of claim 4 , wherein when initiation of the E1 Setup procedure is performed by the gNB-CU-CP:

the E1 SETUP REQUEST message is a GNB-CU-CP E1 SETUP REQUEST message, and

the E1 SETUP RESPONSE message is a GNB-CU-CP E1 SETUP RESPONSE message.

6. The medium of claim 5 , wherein:

the GNB-CU-CP E1 SETUP REQUEST message and the GNB-CU-CP E1 SETUP RESPONSE message comprise a message type IE that identifies the message being sent and a gNB-CU-CP Name IE that indicates a name of the gNB-CU-CP.

7. The medium of claim 4 , wherein when initiation of the E1 Setup procedure is performed by the gNB-CU-UP:

the E1 SETUP REQUEST message is a GNB-CU-UP E1 SETUP REQUEST message, and the E1 SETUP RESPONSE message is a GNB-CU-UP E1 SETUP RESPONSE message.

8. The medium of claim 7 , wherein:

the GNB-CU-UP E1 SETUP REQUEST message and the GNB-CU-UP E1 SETUP RESPONSE message comprise a message type IE that identifies the message being sent, a gNB-CU-UP identity (ID) IE that identifies the gNB-CU-UP, and a gNB-CU-CP Name IE that indicates a name of the gNB-CU-CP.

9. The medium of claim 4 , wherein:

the E1 SETUP REQUEST message and E1 SETUP RESPONSE message from the gNB-CU-CP and gNB-CU-UP comprise setup IEs of a same type, including a message type IE and a name of one of the gNB-CU-CP and gNB-CU-UP that has respectively transmitted the E1 SETUP REQUEST message and E1 SETUP RESPONSE message.

10. The medium of claim 4 , Wherein the one or more processors further configure the gNB to, when the instructions are executed:

if the E1 SETUP RESPONSE message in response to transmission of the E1 SETUP REQUEST message has not been received, wait a predetermined amount of time after transmission of the E1 SETUP REQUEST message before re-transmission of the E1 SETUP REQUEST message.

11. An apparatus of a next generation NodeB (gNB), the apparatus corn prising:

processing circuitry; and memory,

wherein the gNB is configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU), the gNB-CU comprising a gNB-CU control plane (gNB-CU-CP) for control-plane functionality and a gNB-CU user plane (gNB-CU-UP) for user-plane functionality, the gNB-CU-CP configured to communicate with the gNB-CU-UP over an E1 interface, the gNB-CU-UP configured to communicate user plane messages with the gNB-DU over an F1 user-plane interface (F1-U), the gNB-CU-CP is configured to communicate control plane messages with the gNB-DU over an F1 control plane interface (F1-C),

the processing circuitry configured to:

initiate, by one of the gNB-CU-CP and gNB-CU-UP, a first Transport Network Layer (TNL) association between the gNB-CU-CP and gNB-CU-UP; and

after the first TNL association is operational, initiate an E1 Setup procedure to set up the E1 interface between the gNB-CU-CP and the gNB-CU-UP, wherein initiation of the E1 Setup procedure is performed by the gNB-CU-CP when the gNB-CU-CP initiated the first TNL association, and wherein initiation of the E1 Setup procedure is performed by the gNB-CU-UP when the gNB-CU-UP initiated the first TNL association; and

a memory configured to store information of the E1 Setup procedure.

12. The apparatus of claim 11 , wherein:

when initiation of the E1 Setup procedure is performed by the gNB-CU-UP, the E1 Setup procedure is a gNB-CU-UP E1 Setup procedure.

13. The apparatus of claim 11 , wherein:

when initiation of the E1 Setup procedure is performed by the gNB-CU-CP the E1 Setup procedure is a gNB-CU-CP E1 Setup procedure.

14. The apparatus of claim 11 , wherein the one or more processors further configure the gNB to, when the instructions are executed:

initiate the E1 Setup procedure by transmission of an E1 SETUP REQUEST message, and

determine that setup of the E1 interface is successful in response to reception of a message that contains information elements (IEs) of an E1 SETUP RESPONSE message in response to transmission of the E1 SETUP REQUEST message, wherein the E1 SETUP REQUEST message and E1 SETUP RESPONSE message sent by a same entity of the gNB-CU-CP and gNB-CU-UP consist of identical types of the IEs.

15. The apparatus of claim 14 , wherein when initiation of the E1 Setup procedure is performed by the gNB-CU-CP:

the E1 SETUP REQUEST message is a GNB-CU-CP E1 SETUP REQUEST message,

the E1 SETUP RESPONSE message is a GNB-CU-CP E1 SETUP RESPONSE message, and

the GNB-CU-CP E1 SETUP REQUEST message and the GNB-CU-CP E1 SETUP RESPONSE message comprise a message type IE that identifies the message being sent and a gNB-CU-CP Name IE that indicates a name of the gNB-CU-CP.

16. The apparatus of claim 14 , wherein when initiation of the E1 Setup procedure is performed by the gNB-CU-uP:

the E1 SETUP REQUEST message is a GNB-CU-UP E1 SETUP REQUEST message,

the E1 SETUP RESPONSE message is a GNB-CU-UP E1 SETUP RESPONSE message, and

the GNB-CU-UP E1 SETUP REQUEST message and the GNB-CU-UP E1 SETUP RESPONSE message comprise a message type IE that identifies the message being sent, a gNB-CU-UP identity (ID) IE that identifies the gNB-CU-UP, and a gNB-CU-CP Name IE that indicates a name of the gNB-CU-CP.

17. The apparatus of claim 14 , Wherein:

the E1 SETUP REQUEST message and E1 SETUP RESPONSE message from the gNB-CU-CP and gNB-CU-UP comprise setup IEs of a same type, including a message type IE and a name of one of the gNB-CU-CP and gNB-CU-UP that has respectively transmitted the E1 SETUP REQUEST message and E1 SETUP RESPONSE message.

18. The apparatus of claim 14 wherein the processing circuitry is further configured to:

if the E1 SETUP RESPONSE message in response to transmission of the E1 SETUP REQUEST message has not been received, wait a predetermined amount of time after transmission of the E1 SETUP REQUEST message before re-transmission of the E1 SETUP REQUEST message.

19. An apparatus of a central unit user plane of a next generation NodeB (gNB-CU-UP), the apparatus comprising:

processing circuitry configured to:

initiate a first Transport Network Layer (TNL) association between the gNB-CU-UP and a central unit control plane (gNB-CU-CP)); and

after the first TNL association is operational, initiate an E1 Setup procedure to set up an E1 interface between the gNB-CU-CP and gNB-CU-UP,

wherein establishment of the E1 interface is limited to the gNB-CU-UP and comprises:

transmission of a gNB-CU-UP E1 SETUP REQUEST message, and

determination that setup of the E1 interface is successful in response to reception of a message that contains information elements (IEs) of a gNB-CU-UP E1 SETUP RESPONSE message in response to transmission of the gNB-CU-UP E1 SETUP REQUEST message; and

a memory configured to store the IE of the gNB-CU-UP E1 SETUP REQUEST message.

20. The apparatus of claim 19 , wherein:

the gNB-CU-UP E1 SETUP RESPONSE message and a GNB-CU-UP E1 SETUP REQUEST message consist of identical types of the IEs.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2020
From: INTEL CORPORATION
To: APPLE INC.
Reel/Frame 052414/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2019
From: YANG, FENG; SIROTKIN, ALEXANDER; HAN, JAEMIN; ZHANG, XU
To: INTEL CORPORATION
Reel/Frame 049516/0888 →
Continuity (2)
Provisional Application 62669780 · May 10, 2018
Related Publication 20190297652A1 · Sep 26, 2019