E1 Interface Setup Contention in 5G gNB-CU
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The setup of the E1 interface in 5G NodeBs is inefficient due to simultaneous E1 SETUP REQUESTs from the control plane and user plane entities, leading to contention and potential failures in establishing proper connections.
Innovation Solution
The proposed solution involves designing the E1 SETUP REQUEST and RESPONSE messages to include identical information elements, allowing the control plane and user plane entities to recognize each other's requests as responses, and implementing timers and reinitiation procedures to manage contention and ensure successful setup procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If simultaneous E1 SETUP REQUEST messages are sent from control plane and user plane entities, then setup procedure is initiated, but contention and potential failures occur
Solution Approach 1:
The patent implements a preliminary check mechanism where the receiving entity examines incoming E1 SETUP REQUEST messages against previously sent requests. If a matching request is found, the receiving entity recognizes it as a duplicate and responds with E1 SETUP RESPONSE instead of initiating a new setup procedure, thereby preventing contention while maintaining setup initiation speed
Solution Approach 2:
The patent introduces a feedback mechanism where entities exchange E1 SETUP REQUEST and E1 SETUP RESPONSE messages to confirm setup status. The receiving entity provides feedback about whether the request is recognized as a duplicate or a new valid request, enabling the sending entity to adjust its behavior and avoid simultaneous setup attempts
2Ease of operation
If E1 SETUP REQUEST messages include identical information elements, then recognition of requests as responses is enabled, but message design complexity increases
Solution Approach 1:
The patent makes the E1 SETUP REQUEST message structure universal by including identical information elements that can serve dual purposes: as initialization parameters in new setup requests and as recognition keys for duplicate detection. This allows the same message format to function both as a setup initiator and as a duplicate identifier, simplifying the overall procedure despite increased message design complexity
3Reliability
If timers and reinitiation procedures are implemented, then contention management is improved, but procedure complexity increases
Solution Approach 1:
The patent implements periodic timer-based checks where entities wait for a predetermined time period after sending E1 SETUP REQUEST before considering retransmission or alternative actions. This periodic waiting mechanism systematically manages contention by preventing immediate retransmission of duplicate requests, improving reliability while adding structured complexity to the procedure
Data Source
AI summary
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.