TR201720818A2 - Peer-to-Peer Session RENEWAL METHOD FOR SIP-BASED CONFERENCE SERVERS - Google Patents

Abstract

Invention, in cases where the sessions established between SIP clients and SIP conference servers are provided over non-SIP based communication networks; It is about a peer-to-peer session renewal method developed to eliminate the problems that arise during the use of the RE-INVITE method, which questions the presence of these sessions.

Description

TECHNICAL FIELD The invention is available to users with SIP-enabled clients via a SIP conferencing server. relates to conferences held between

In particular, SIP sessions established between SIP clients and SIP conference servers. where they are provided over non-based communication networks; in these sessions emerging during the use of the RE-INVITE method, which questions the presence of a peer-to-peer developed to eliminate problems It's about the session refresh method.

PRIOR ART In SIP-based audio or video conferencing systems, conference participants someone logged out due to network connection problems or client software problems If it drops, the resources on the server are wasted unnecessarily. Very precious conference to eliminate the problem of unnecessary waste of these resources. server sends messages to the clients connected to it at regular intervals and Detects whether the client is still in session based on the responses it receives to messages. The method that works is called the session refresh method. Conferencing on SIP-based systems session refresh by sending INFO, OPTIONS or INVITE messages can do. A frequently used method is to refresh session by sending INVITE message. and is defined as a standard under the IETF with RFC4028. SIP protocol only This method, which works successfully on the networks used, also allows non-SIP networks to be involved. shows some shortcomings. After the SIP client joins the conference session then re-INVITE for conference server session refresh (re-lNVITE) method, it tries to send INVITE messages to the client at regular intervals. This INVITE Depending on whether the messages are answered or not, the server will still allow the SIP client to Detects whether you are in session or not. Non-SIP-based communication networks are also included. gateways that convert SIP protocol and other protocols in scenarios used. In the INVITE messages that the server sends for session renewal, the session Gateways will send this INVITE message to other devices as there is no feature to change media properties. It does not need to pass the message to the other end and the server does not need to pass the message to the other end. although there is no response, the SIP 200 OK, indicating success, returns. In this case the conference server always gets a 200 OK response and actually the SIP client's it cannot detect whether it has dropped out of the session or not. Eventually the client drops out of the conference session. Even so, resources continue to be allocated on the server for this client who has dropped out of the session, and conference server resources are used inefficiently.

As a result, the above-mentioned problems that cannot be solved in the light of the current technique are related to the technical made it necessary to make an innovation in the field.

BRIEF DESCRIPTION OF THE INVENTION The present invention is intended to eliminate the above mentioned disadvantages and to introduce new technologies into the relevant technical field. It is about the peer-to-peer session renewal method to bring advantages.

The main purpose of the invention is to use SIP-enabled conference sessions on SIP-based session renewal that occurs when non-communicating communication networks are also used. (RE-INVITE) method is to develop a system that eliminates the problem of use.

Another object of the invention is to also use non-SIP-enabled communication networks based on SIP. SIP clients dropped out of their session in conferences held with the use of A system that prevents inefficient use by ensuring that it is detected in such a way is to develop.

All the above-mentioned purposes that will emerge from the detailed description below. The present invention is to implement SIP-based, non-SIP-enabled communications. Session renewal in audio and/or video conferences held via their network (RE-INVITE) method is a method that eliminates the problems that occur during its use. It is a peer-to-peer session renewal method. Accordingly, the system that performs the method; 0 users attending an audio and/or video conference use at least one client o sends the communication messages to different client units to which the mentioned client units are connected and at least one application that acts as a bridge between volumes and network components at least one gateway unit that converts 0 different calling protocols to each other, o perform the audio and video communication in a different way from the SIP protocol. at least one foreign communication network that performs with the protocol, audio/video conference between the mentioned client units with each other at least one conference server contains.

The method, which is the subject of the invention and carried out by the said system, is as follows; audio and/or video conferencing of the client unit used by the user. application that acts as a bridge between different client units in order to participate send an invitation (INVITE) message by adding its own IP address data to its server, the invitation (INVITE) message sent by the said client unit forwarding it to an application server that acts as a bridge between units, via a gateway unit of said application server. communication with the communication network and the invitation sent by the client unit. transmitting the message to a conference server over the gateway unit, send the acknowledgment reply message (OK) of the conference server via a gateway unit. to an application server through the foreign communication network with which it communicates. transmit, confirmation message (OK) invitation message (INVITE) of said application server forwarding it to the sending client unit, by the conference server of the client unit that sent the invitation message (INVITE). IP address of the notification message (ACK) indicating that it has received the confirmation (OK) message sent. The task of creating by adding data and bridging between different client units forwarding it to the application presentation that sees it, notification sent by the client unit of said application server message (ACK) via a gateway unit over a foreign communications network. forwarding it to the conference server, thereby setting up the session's standard SIP call. to be established with the method, whether your client unit is still in session after the conference server session has started. directly to the client using the IP address of the client unit. sending a re-invite (RE-INVITE) message to the unit, o If a response to a resent invitation message (RE-INVITE) from the client unit does not arrive, the conference server must wait for a certain time and re-invite. The reserved resource of the client unit to which the RE-INVITE message was sent is empty removal, o If a response to a resent invitation message (RE-INVITE) from the client unit the conference server understands that the client unit is in session. and for the time specified for the next session renewal is waiting.

The embodiment of the present invention and the best use of its advantages with additional elements In order to be understood, it should be evaluated together with the figures explained below.

SIP (Session Initiation Protocol), operation of multimedia services over the Internet It is a protocol developed for The most well-known of these multimedia services and are telephone services offered over the internet. Internet-enabled telephone services (Internet Telephony) are inexpensive but of slightly lower quality, over IP networks. It provides the opportunity to make a voice call. The Internet is the transport medium for these phone calls. Since it is used as an international airport and expensive international private lines are not used, it is relatively more expensive. cheap service is available. SIP is standardized by the IETF (RFC 3261).

BRIEF DESCRIPTION OF THE FIGURES Figure 1 provides a schematic view of the peer-to-peer session renewal system.

Figure 2 gives a schematic view of the peer-to-peer session renewal method.

Figure 3 is the flowchart of the peer-to-peer session renewal method.

REFERENCE N MARKS client unit application server gateway unit foreign communication network conference host message 150. Foreign communication network invitation message message 250. Foreign communication network confirmation message message 350. Foreign communication network notification message DETAILED DESCRIPTION OF THIS ITEM In this detailed description, the innovation that is the subject of the invention is only intended for a better understanding of the subject. It is explained with examples that will not have any limiting effect.

Figure 1 shows the schematic view of the peer-to-peer session renewal system. This according to the system; at least one of the users participating in the audio and/or video conference the client unit (1) is the one to which the mentioned client units (1) are connected and sends their communication messages to different At least one application that acts as a bridge between client units (1) and network components server (2), at least one gateway unit (3) that converts different calling protocols to each other, voice and the realization of video communication with a different protocol than SIP protocol. at least one foreign communication network (4) performing the said client units (1) at least one conference that allows the conference to take place between them as audio/video server (5).

The working method of the request is as follows: Figure 1 shows the network topology in which this method can be used. This method is basically SIP -based audio and video conferencing servers (5) more efficiently will enable you to use it. SIP client units (1) to conference servers (5) how it is connected over non-based foreign communication networks (4) is shown in Figure 2. shown. SlP client unit (1) “Contact” to access conference session (6) SIP application by adding the "maddr" parameter containing its own IP address to the header sends an invitation (lNVITE) message to its server (2). SIP application server (2) sends this message to the network gateway unit (3) and the gateway unit (3) sends the message to a non-SIP-based foreign sends it to the communication network (4). This message is then sent again via the gateway unit (3) via SIP message and transmitted to the SIP-based conference server (5). SIP-based conferencing server (5) returns a confirmation (OK) response to this. This response is the same route back to the SIP client. reaches unit (1). The SIP client unit (1) is again to notify that it has received this acknowledgment (OK) response. sends the message. This notification (ACK) message is also sent to the SIP conference server (5) via the same route. is delivered. Thus, a call is established between the SIP client unit (1) and the conference server (5). The SIP conferencing server (5) will receive the invitation (lNVITE) and notification (ACK) based on the “maddr” parameter in the “Contact” header of the messages, after the session starts SIP directly to the invitation (lNVITE) session renewal message that it will send after a certain period of time. sends it to the client unit (1). The most important difference of this method from previous methods is invitation. (INVlTE) session renewal message is sent in this way peer-to-peer. SIP conference server (5), which is a session refresh standard between the two SIP components while doing this. It uses the method in RFC4028. If the client unit (1) is still in session, again directly to the SIP conference server (5) in response to the invitation (INVITE) message when the answer reaches the conference server (5), the conference server (5) it detects that it is still in session and enters the next session renewal message it will send. (INVITE). If the client unit (1) has dropped out of the conference session, this In this case, the conference server (5) responds to the invitation (INVITE) message it has sent. the time it will not receive and will calculate based on the T1 time defined in RF03261* eventually the client will free up the resources it has reserved for unit (1).

Claims (1)

REQUESTS The client unit (1) used by the user sends an invitation message to the application server (2), which acts as a bridge between different client units (1) in order to participate in the audio and/or video conference, by adding its own IP address data, the said application server (2), a network Communication with the foreign communication network (4), which performs the audio and video communication with a different protocol than the SIP protocol, over the gateway unit (3) and the invitation message sent by the client unit (1) to a conference server (again via the gateway unit (3)). 5) forwarding, that the conference server (5) forwards the confirmation message response to an application server (2) via the foreign communication network (4) with which it communicates over a gateway unit (3), that said application server (2) sends the confirmation message to the client that sent the invitation message. unit (1), the confirmation sent by the conference server (5) of the client unit (1) that sent the invitation message. The application server (2) sent by the client unit (1) to create the notification message indicating that it has received the message by adding the IP address data and forward it to the application server (2), which acts as a bridge between different client units (1), and to establish the session with the standard SIP call setup method. After the process steps of forwarding the notification message to the conference server (5) over the foreign communication network (4) via a gateway unit (3), it is a SIP-based method that eliminates the problems that occur during the use of session renewal method in conferences held via non-SIP-enabled communication networks. It is a peer-to-peer session renewal method, and its feature is; . the conference server (5) sends an invitation message directly to the client unit (1) using the IP address of the client unit (1) to see if the client unit (1) is still in the session after the session starts, 0 if the invitation message is resent from the client unit (1) if there is no reply, the conference server (5) waits for a certain time and frees up the resource reserved for the client unit (1) to which the re-invitation message was sent, o if the client unit (1) responds to the resent invitation message, the conference server (5) has the client unit (1 ) understand that it is in the session and wait for the next session renewal process for the specified period of time. . It is a peer-to-peer session renewal method in accordance with Claim 1, and its feature is; The client unit used by the user (1) sends an invitation message by adding its own IP address data to the "maddr" parameter under the title "Content" to the application server (2), which acts as a bridge between different client units (1) in order to participate in the audio and/or video conference. . It is a peer-to-peer session renewal method in accordance with Claim 1, and its feature is; The client unit used by the user (1) sends a notification message by adding its own IP address data to the "maddr" parameter under the title of "Content" to the application server (2), which acts as a bridge between different client units (1) in order to participate in the audio and/or video conference. It is a peer-to-peer session renewal method in accordance with Claim 1, and its feature is; when there is no response to the resent invitation message from the client unit (1), the conference server (5) idles the resource reserved for the client unit (1) to which the invitation message was sent after waiting based on the T1 time defined in RFC3261. . It is a peer-to-peer session renewal method in accordance with Claim 1, and its feature is; If the client unit (1) responds to the re-sent invitation message, the conference server (5) waits for the time defined in RF03261 for the next session renewal after realizing that the client unit (1) is in the session. . It is a peer-to-peer session renewal method in accordance with Claim 1, and its feature is; when the conference server (5) sends an invitation message to the client unit (1) that has joined the conference before, if the said client unit is still in the session, the said client unit (1) sends a confirmation message to the conference server (5) in accordance with the method in RFC4028.