Connection Release Reason Information Element
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In communication networks, users are not informed about the reason for connection termination, leading to confusion between network-related and party-generated session termination.
Innovation Solution
A mechanism is introduced to include a reason information element in connection terminating messages, allowing users to differentiate between network-generated and party-generated session termination by indicating the cause of connection release, such as a loss of bearer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If connection termination messages are sent without reason information elements, then the network structure remains simple and message protocols remain minimal, but users cannot distinguish between network-related and party-generated session termination, leading to user confusion
Solution Approach 1:
The reason information element is nested within the existing connection termination message structure. The cause code and cause text are embedded as additional fields inside the standard termination message framework, allowing reason information to be carried without requiring a completely new message protocol or structure.
Solution Approach 2:
A reason information element acts as an intermediary between the network's internal termination causes and the user's understanding of termination reasons. This element translates internal network events (such as bearer loss) into user-comprehensible information that can be displayed to clarify why a connection was terminated.
2Ease of operation
If reason information elements are added to connection terminating messages, then users can differentiate between network-generated and party-generated session termination, but the message protocol and network elements require modifications
Solution Approach 1:
The reason information is prepared and attached to the connection termination message before the message is sent to the user. The network element determines the cause code and cause text in advance, embeds them in the termination message, and then transmits the complete message to the user equipment, which can immediately display the reason without requiring additional network interactions.
Solution Approach 2:
The connection termination message is enhanced by adding new parameters (cause code and cause text fields) to its structure. These parameters change the message from a simple termination notification to an informative message that includes diagnostic information about why the connection was terminated, allowing users to understand network-related issues versus user-initiated terminations.
Data Source
AI summary
The present invention relates to a method usable for managing a connection release of an established connection between two or more parties via a communication network. When the reason for terminating a connection/session between at least two parties is caused by circumstances in the communication network, such as a loss of bearer, this is detected in a first network element. Then the first network element generates a connection terminating message to be used in the connection release procedure into which a new information element is introduced indicating the reason for the connection release, for example the loss of bearer. This reason may be indicated to a user as an optional and additional information. Furthermore, a corresponding system, device and/or terminal equipment are proposed.