WO2008028502A1

WO2008028502A1 - Method for handling a disconnection

Info

Publication number: WO2008028502A1
Application number: PCT/EP2006/008649
Authority: WO
Inventors: Volker Mösker; Jörg WIENAND
Original assignee: Siemens Home And Office Communication Devices Gmbh & Co. Kg
Priority date: 2006-09-05
Filing date: 2006-09-05
Publication date: 2008-03-13

Abstract

The invention relates to a method for handling a disconnection, having the following steps: session data are negotiated (S1) for a communication link which has been set up, an end of the disconnection is detected (S4), and the communication link is restored (S5) using the negotiated session data. This allows an already existing communication link to be continued after a disconnection in a user-friendly fashion.

Description

description

Method for handling a call termination

The present invention relates to a method for handling a call disconnection, and more particularly to a method for handling DSL forced disconnect for telecommunication terminals.

FIG. 1 shows a simplified block diagram of a telecommunication system wherein an internal network HN1, such as a first home network, is connected to a second internal network HN2 or a second home network via an external network N, such as the Internet. According to FIG. 1, this may be e.g. a first telecommunication terminal TEl with a so-called VoIP functionality (Voice over IP) connected to a first network node or first router Rl and this example be connected via a DSL line (Digital Subscriber Line) to the external network N, preferably represents a packet-switched network. In the same way, the second telecommunication terminal TE2 is connected to the network N via a second network node or second router R2 and also implements a corresponding VoIP functionality via a DSL line (Digital Subscriber Line).

In order to realize the physical communication connection, such as the DSL line, a network provider SV1 is available in the network N, for example. Furthermore, to provide the network service, such as the VoIP functionality (Voice over IP), the service provider SV2 is available. The network and service providers SV1 and SV2 are usually implemented by corresponding servers in network N.

Typically, such internal networks or home networks HNl and HN2 via so-called NAT network nodes (Network Address Translation) or router Rl and R2 to the network N connected, wherein such a network node Rl and R2 performs a network address / port conversion (NA (P) T, Network Address (Port) Translation) from an external IP address to an internal IP address.

However, in the case of private digital subscriber line (DSL) in particular, a forced disconnection of the physical communication connection is common at regular intervals (for example every 12 or 24 hours), which inevitably leads to the disconnection of an already established e.g. VoIP connection, a download, etc. leads. After restoration of the physical communication connection, or the DSL line, the user gets assigned a new, different IP address, so that a connection to his immediately preceding communication partner in the network N is reset. This is when using a variety of services, such as VoIP phone calls, online game sessions, downloads, P2P queues (peer to peer) are annoying as they inevitably reset.

The invention is therefore based on the object to provide a method for treating such a connection termination.

According to the invention this object is achieved by the measures of claim 1.

Accordingly, for a established communication connection, session data is first negotiated, and after detecting an end of a connection termination, the communication connection is restored using the negotiated session data. Consequently, by negotiating session data during a communication connection, additional signaling can be made possible for a respectively realized connection which, after the physical connection has been reestablished, enables an automatic restoration of the superordinate communication connection in a simple manner. For example, at least one session identification for uniquely identifying a established communication connection is negotiated as session data. Furthermore, the session data may also contain a session context for describing the established communication connection. The session data may further include a session timeout indicating a maximum time for a connection abort. Further, the session data may include a flag indicating whether already running applications should be held or not.

Preferably, detecting a start of a connection abort is detected and a disconnection application is executed until the end of the disconnection, wherein the

For example, a disconnect application represents a replay of a wait message. In this way, a waiting message in the form of a spoken information or a melody can be reproduced in particular for a VoIP connection to a respective subscriber for the duration of the disconnection. User comfort is significantly increased.

For example, the connection abort can also be initiated on the terminal using the session data. In particular, with knowledge of a respective forced disconnection, a respective rebuilding of a physical communication connection can thereby be significantly accelerated.

In the further subclaims further advantageous embodiments of the invention are characterized.

The invention will be described below with reference to embodiments with reference to the drawings.

Show it: Figure 1 is a simplified block diagram illustrating a telecommunications system;

FIG. 2 is a state diagram for illustrating essential process states according to a first exemplary embodiment;

FIG. 3 shows a state diagram for illustrating essential process states according to a second exemplary embodiment; and

FIG. 4 shows a simplified flowchart for illustrating essential method steps of the method according to the invention.

FIG. 2 shows a simplified state diagram for illustrating essential process states for handling a connection termination, as may be present, for example, in a telecommunication system according to FIG. According to state 1, for example, there is a fully established VoIP connection carried over a physical communication link such as a Digital Subscriber Line (DSL) connection. The network node or the router / DSL modem Rl in this case initially has a first external IP address, via which a corresponding IP connection (Internet Protocol) can be realized.

In this state, the two terminals TE1 and TE2, which represent, for example, VoIP telephones, exchange so-called session data or session ID data, which enable additional signaling for a respective higher-level connection.

Such session data include at least one session ID or session ID, which uniquely identifies the already established higher-level communication connection. This can be a unique character and / or number sequence, for example lying VoIP connection between the terminals TEl and TE2 is assigned.

Optionally, a so-called session context, a so-called session timeout and / or a session identifier can also be present in the session data. The session context here describes a respective connection with regard to its characterizing parameters. Such parameters may be, for example, the type of connection, such as a VoIP (Voice over IP) connection, the port number (e.g., 5060) used, and the audio codecs used. In particular, the session timeout or session timeout can specify a maximum time for which a connection termination can be effectively bridged. The session flag or keep-alive flag indicates whether applications that are already running should be held or not. In particular, it can be signaled by this session indicator, whether a respective VoIP, download, Onlinegame- or P2P application to be maintained or can be turned off.

According to FIG. 2, a so-called regular DSL forced disconnection now takes place in state 2, which is usually carried out every 12 or 24 hours in order to keep the DSL lines in a predefined state. Such

Forced disconnection of the physical communication connection, such as a DSL line, is usually initiated by the network operator or its server SVL and causes a connection termination in the higher communication links such as a respective VoIP connection.

According to FIG. 2, such a connection termination or such a regular DSL forced disconnection takes place, for example, between the network N and the first network node R 1 or its terminal TE 1. According to Figure 2, for example, after detecting the disconnection or the forced disconnection in state 3. - triggered by the network node Rl and R2 - now in the respective telecommunications terminal TE2 and TEl the VoIP connection can be maintained. Optionally, a waiting message in the form of a voice message or a waiting melody at the respective telecommunication terminal TE1 and / or TE2 can be reproduced at this time. The detection of the disconnection can be done by different mechanisms, such as UPnP_IDG_WANIPConnection 1.0, polling, etc ..

After a predetermined period of time, the re-establishment of the physical communication connection or the DSL connection (Digital Subscriber Line) takes place, wherein a new external second IP address is assigned to the network node Rl. This situation is forwarded from the first network node Rl to the first telecommunication terminal TE1, whereby the latter experiences its new external IP address and, in addition, is informed that in turn a physical communication connection to the network N exists. As soon as the physical communication connection or the DSL line between the first network node Rl and the network N or the network provider SVl exists again, in the state 4. the first telecommunication terminal TEl now automatically a VoIP connection using his previously negotiated session data and in particular Restore the session ID.

More specifically, among the "old" session data already negotiated in state 1, such as the session identification, the session context, the session timeout, the session identifier, etc., a new VoIP connection is now made using the new external IP address restored, so using the previous data, a new VoIP connection can be restored, significantly increasing user convenience. Both terminals TE1 and TE2 now restore the communication context from before the forced disconnection or before the disconnection of the connection and form it back onto the new external IP address of the first network node R1 and thus of the first terminal TE1. The call can thus be continued in a state 6.

According to FIG. 2, a renewal of session data or session ID data can optionally also be carried out in a state 5, whereby new session data is negotiated again between the first and second telecommunication terminal TE1 and TE2 for the VoIP connection under the new IP address become.

Thus, at the network or application level by means of additional signaling data exchange can be realized, which allows a fast and easy restoration of the original connection, especially in an IP-based communication at a connection termination.

The implementation of the method can be implemented in the network node or router Rl or R2 and thus takes place transparently for all devices behind the network node or router. As network nodes also so-called (not shown) gateways are conceivable. The method would then have to work on the basis of port-based connections. Alternatively, an implementation of the method but also directly in the terminal such as a PC, a VoIP stand-alone phone, etc. possible. Combined end rates are also conceivable in which the functionality of the network node and the terminal are combined in one device.

If the time of the forced disconnection or disconnection is known, this can be communicated in advance to the opposite telecommunication terminal TE2, which would enable a coordinated decommissioning and resumption of the communication. It may make sense to connect shortly before forced disconnection or Manually disconnect the connection. In this case, the connection abort can also be initiated on the terminal side using the session data. Restoring the original parent communication link may be speeded up.

Figure 3 shows a simplified state diagram according to a second embodiment, wherein like reference numerals denote the same or corresponding states as in Figure 2, which is why a repeated description is omitted below.

According to FIG. 3, not only a connection between a first and a second telecommunication terminal TE1 and TE2 can be realized, but also only between a telecommunication terminal TE1 or its associated network node R1 and an associated service provider or its server SV2. The service provider or server SV2 serves to implement, for example, a VoIP service or a VoIP connection. Again, even with such a VoIP connection by exchanging or negotiating session data in the state of 1. after a forced disconnection or a disconnection in state 2. a very fast recovery of a VoIP connection using the negotiated "old" session data realized which significantly increases user comfort.

Consequently, in particular for so-called download sessions, it is not necessary to start again at the beginning, but a download interrupted by a forced disconnection can be continued after the physical communication connection or the DSL line has been restored.

FIG. 4 shows a simplified flow diagram for illustrating essential steps of the method according to the invention. After a start in step SO, in a step S1, session data and in particular a session identification between a first and second telecommunication terminal or between a telecommunication terminal and a server are first negotiated in an already established higher-level communication connection. In this case, further information such as a session context for describing the established communication connection, a session timeout for specifying a maximum time for a connection termination and a session identifier for indicating information whether an already running application is to be held or not, be negotiated.

In an optional step S2 it can be checked whether a forced disconnection of the connection or a disconnection has taken place or not. More specifically, a start of a disconnection can be detected, and in an optional step S3, a waiting message can be reproduced as soon as such a start of a disconnection has been detected. As a waiting message, a corresponding voice message ("please hold the line") or a suitable waiting melody can be output on the terminal side to a respective subscriber, as known in particular from private switching systems Step S4 branches further.

In step S4 it is now checked whether a new external IP address has been assigned. This new external IP address can in this case be assigned to the network node R1 as soon as a physical communication connection between the network node R1 and the network provider or its server SV1 has been restored. More specifically, it is checked in step S4 whether there is an end of a communication termination for the physical communication connection. If this is the case, the method branches on to step S5, where the previously negotiated session data or session ID data is used to rebuild the separated superordinate communication connection. If, however, the check result in step S4 is negative, the system branches back to the input of step S4 and thus waits for the allocation of a new IP address.

Accordingly, in step S5, the already negotiated session data such as, in particular, the session identification, but optionally also the session context, the session timeout and the session identifier, are communicated to the opposite communication partner, whereby the aborted communication connection can be retrieved in a very simple and fast manner. can be made. As a result, a VoIP call, a data download, an online game session, or a P2P queue can seamlessly continue at the point of disconnection.

Optionally, after restoration of the DSL connection and the higher-level communication connection, new session data can be negotiated in a step S6, which replaces the previous session data. The method ends in a step S7.

The invention has been described above with reference to a VoIP connection. However, it is not limited to this and also includes alternative communication links such as online game sessions, data downloads, peer-to-peer (P2P) queues, etc. Furthermore, the invention has been described as a physical communication link using a DSL connection , However, it is not limited thereto and equally includes any alternative physical communication links.

Furthermore, the invention has been described with reference to a home network consisting of a telecommunication terminal and a network node. However, the invention is not thereon limited and includes in the same way also alternative private networks and in particular terminals in which the network node is integrated in the terminal.

LIST OF REFERENCE NUMBERS

TEl, TE2 telecommunication terminals

Rl, R2 network node N telecommunication network

SVl network provider

SV2 service provider

HNl, HN2 home network

SO to S7 process steps

Claims

claims

A method of handling a disconnect, comprising the steps of: negotiating (S1) session data for a established communication connection prior to the disconnect; Detecting (S4) an end of the disconnection; and restoring (S5) the communication link using the negotiated session data.

2. Method according to claim 1, characterized in that the session data comprise at least one session identification for uniquely identifying a established communication connection.

3. A method according to claim 2, wherein: the session data further comprises a session context for describing the established communication connection.

4. The method of claim 2 or 3, wherein: the session data further comprises a session timeout indicating a maximum time for a connection abort.

5. The method of claim 2, wherein the session data further comprises a session identifier indicating whether applications already running should be held or not.

6. Method according to one of the claims 1 to 5, wherein the steps: detecting (S2) a beginning of the connection termination; and

Execute (S3) a connection abort application until the end of the connection abort.

7. The method according to claim 6, wherein a connection termination application realizes a reproduction of a waiting message.

8. The method according to any one of the claims 1 to I ₁ characterized by the further step:

Renegotiating (S6) session data for the recovered communication connection.

9. Method according to one of the claims 1 to 8, in that a communication connection is a VoIP connection that is realized via a DSL connection.

10. The method according to one of the claims 1 to 9, wherein a communication connection between two telecommunication terminals (TE1, TE2) is established.

11. Method according to one of the claims 1 to 9, wherein a communication connection between a telecommunication terminal (TE1) and a server (SV2) is established.

12. The method as claimed in one of the claims 1 to 11, in which the connection termination is initiated on the terminal side using the session data.