Bearer Connection Handling in Wireless Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communications networks, usage data reports are often lost during the deactivation of default bearer connections due to their receipt by the Mobility Management Entity (MME) too late in the procedure, resulting in the PDN connection being terminated before the reports can be forwarded.
Innovation Solution
The proposed solution involves modifying the procedure flow to ensure that usage data information is transmitted before the communications network connection is terminated. This is achieved by configuring network management entities to receive a request for bearer connection deletion, initiate the release of the user equipment, receive a complete message confirming the deletion, and then transmit a response message acknowledging the deletion, all while ensuring that usage data is included in the complete message.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the MME processes bearer connection deletion requests using the conventional procedure flow, then the bearer connection deletion is completed efficiently, but usage data reports are lost because they arrive too late in the procedure
Solution Approach 1:
The patent applies preliminary action by having the MME send a detach request to the UE before processing the bearer deletion, and by having the eNodeB send the usage data report in the UE context release complete message before the PDN connection is terminated. This reordering ensures usage data is captured before the connection is fully deactivated, preventing data loss while maintaining procedural efficiency.
2Speed
If the PDN connection is terminated immediately upon receiving the deletion request, then the resource release is rapid, but usage data reports cannot be forwarded to the SGW
Solution Approach 1:
The patent ensures usage data is transmitted in the UE context release complete message before the PDN connection termination is finalized. The MME waits to receive this message with usage data before completing the PDN connection release, ensuring data is captured while maintaining rapid resource release.
Solution Approach 2:
The eNodeB provides feedback about usage data in the UE context release complete message to the MME. This feedback mechanism ensures usage information is returned to the network before the connection is fully terminated, allowing the MME to forward the data to the SGW before releasing resources.
3Loss of information
If the MME waits for usage data reports before terminating the PDN connection, then usage data is preserved, but the connection release is delayed
Solution Approach 1:
The patent uses preliminary action by having the eNodeB send the usage data report in the UE context release complete message before the MME terminates the PDN connection. This allows the MME to receive and forward usage data without significantly delaying the overall connection release process, as the data transmission occurs as part of the existing signaling flow.
Data Source
AI summary
The disclosure relates to a network management entity (ME) in a communications network (CN), the network management entity (ME) being configured to; receive (S10) a request message (REQm), transmitted by a network serving entity (SE), indicating deletion of a bearer connection for a user equipment (UE, 600), transmit (S40) a release message (RELm) towards a network entity (NE), receive (S50) a complete message (COMPm +IDU) transmitted by the network entity (NE), confirming that the user equipment (UE, 600) is released, and comprising information regarding data usage (IDU), and transmit (S60) a response message (RESPm +IDU) towards the network serving entity (SE), acknowledging deletion of the bearer connection of the user equipment (UE, 600), in response to receiving the complete message (COMPm +IDU). The disclosure also relates to methods performed in a network management entity (ME).