WO2005083948A1 - A sip server - Google Patents

A sip server Download PDF

Info

Publication number
WO2005083948A1
WO2005083948A1 PCT/EP2005/001425 EP2005001425W WO2005083948A1 WO 2005083948 A1 WO2005083948 A1 WO 2005083948A1 EP 2005001425 W EP2005001425 W EP 2005001425W WO 2005083948 A1 WO2005083948 A1 WO 2005083948A1
Authority
WO
WIPO (PCT)
Prior art keywords
sip
server
messages
routing
network
Prior art date
Application number
PCT/EP2005/001425
Other languages
French (fr)
Inventor
Nikolaos Kollias
Original Assignee
Siemens Aktiengesellschaft
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Publication of WO2005083948A1 publication Critical patent/WO2005083948A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/4872—Non-interactive information services
    • H04M3/4878—Advertisement messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/123—Evaluation of link metrics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/52—Multiprotocol routers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/54—Organization of routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/19—Flow control; Congestion control at layers above the network layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/35—Flow control; Congestion control by embedding flow control information in regular packets, e.g. piggybacking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • a SIP server A SIP server
  • This invention relates to a SIP server for use in a complex SIP network.
  • Session Internet Protocol or SIP is a text based protocol which is designed for flexibility and provides a modular approach to enable voice over IP telephone calls.
  • the protocol is described in Handley et al, SIPiSession Initiation Protocol, Internet Engineering Task Force Request For Comments RFC 2543 and also RFC 3261.
  • the sessions that may be set up by the protocol can include two party or multicast, telephony, video conferences and other multimedia sessions.
  • SIP is designed to be a single module which interoperates with current internet based applications.
  • telephone numbers are denoted as URLs of the form user@host which may be displayed on a webpage. Clicking that part of the webpage can then result in a telephone being initiated.
  • Routing in IP networks is controlled by routers but proposed networks involving SIP are not responsive enough because SIP is a real-time application.
  • the present invention arose from a realisation by the inventor that SIP-servers may be used to perform or participate in routing decisions.
  • a SIP-server for use in a communications network including a plurality of SIP nodes which SIP- server including routing means to determine by SIP messages between the nodes routes through the network.
  • the SIP server will include a routing table.
  • the routing table associates code points with destination addresses.
  • the SIP messages are preferably based on existing SIP messages but may be also provided by new messages added to the existing set defined in the protocol.
  • SIP messages have a general format of a start-line, one or more header fields, an empty line indicating the end of the header fields and an optional message body. The form is set out in RFC 2543.
  • the invention confers the following advantages amongst others: the provision of a mechanism to update and change routing tables of SIP-servers makes it easier to administer complex networks; load sharing controlled by SIP messages which will ensure better speech quality/less delay which is important in real time applications such as SIP- telephony; and the mechanism is possible using the existing SIP messages.
  • Figure 1 shows a communications network comprising a number of linked SIP- servers
  • FIG. 2 shows a block diagram of a SIP server in accordance with the invention.
  • a communications network 1 comprises a number of network nodes 2 to 5 linked together by communication links 6 to 9 as shown in figure 1.
  • the nodes are SIP servers based on computers. Suitable computers for this purpose include Sun Microsystems NETRA TM Tl.
  • the servers include Ethernet switches and the communications links 6 to 9 are high-speed links. It will be appreciated that the network will include more nodes and links which have been reduced in the figure for the purpose of simplicity.
  • the SIP servers are nominally identical and figure 2 shows a SIP server 20 in block diagram form.
  • Block 21 is a routing manager which maintains a routing table 22 held in memory.
  • the invention utilises the existing SIP messages provided by the protocol to enable routing information to be determined and utilised to provide routing functionality.
  • the messaging is utilised to populate and to maintain the routing table 22 by the routing manager 21.
  • the messages available are described in RFC 3256.
  • the messages provide two types of function.
  • notifications of load, overload, failure of a link between servers is communicated.
  • SIP server 2 of figure 1 could send a SIP message to SIP server 3 requesting a notification in the case of a link overload or failure.
  • SIP server 3 detects those conditions it will send a SIP message indicating the condition has occurred.
  • the routing manager 21 of server 2 then updates its routing table 22 accordingly.
  • the routing table associates URLs in E.164 format code points with IP addresses.
  • code point 0671 is associated with 172.23.32.4
  • code point 0794 is associated with 194.64.65.9.
  • the TO header is examined. For example, for the TO header 0671017003@serverl.com would be routed to IP address 172.23.32.4.
  • server 2 wishes to receive load information from server 3. To do this server 2 sends to server 3 a SUBSCRIBE message with the event header being event:load-leveI .
  • the server 3 then responds when the load changes within a predefined value.
  • the response is a NOTIFY message containing the load value in the header.
  • the SIP message REGISTER is used for the second function. This message is used to create an association between a SIP URL given in the "TO" header with a destination IP-address given in the "CONTACT" header (RFC 2543). This message is normally used by SIP clients to inform the server of the current location and thus a new header "F" is included which indicates that the message includes new code point registration.

Abstract

A SIP server includes a routing function that utilizes SIP messages to obtain the load conditions of network nodes that may be other SIP servers or other parameters that may be usefully taken into account when determining the route used in the network.

Description

A SIP server
This invention relates to a SIP server for use in a complex SIP network.
Session Internet Protocol or SIP is a text based protocol which is designed for flexibility and provides a modular approach to enable voice over IP telephone calls. The protocol is described in Handley et al, SIPiSession Initiation Protocol, Internet Engineering Task Force Request For Comments RFC 2543 and also RFC 3261. The sessions that may be set up by the protocol can include two party or multicast, telephony, video conferences and other multimedia sessions. SIP is designed to be a single module which interoperates with current internet based applications. Thus, telephone numbers are denoted as URLs of the form user@host which may be displayed on a webpage. Clicking that part of the webpage can then result in a telephone being initiated.
Routing in IP networks is controlled by routers but proposed networks involving SIP are not responsive enough because SIP is a real-time application.
The present invention arose from a realisation by the inventor that SIP-servers may be used to perform or participate in routing decisions.
According to the invention there is provided a SIP-server for use in a communications network including a plurality of SIP nodes which SIP- server including routing means to determine by SIP messages between the nodes routes through the network.
Preferably, the SIP server will include a routing table. In the preferred embodiment the routing table associates code points with destination addresses.
The SIP messages are preferably based on existing SIP messages but may be also provided by new messages added to the existing set defined in the protocol. SIP messages have a general format of a start-line, one or more header fields, an empty line indicating the end of the header fields and an optional message body. The form is set out in RFC 2543.
The invention confers the following advantages amongst others: the provision of a mechanism to update and change routing tables of SIP-servers makes it easier to administer complex networks; load sharing controlled by SIP messages which will ensure better speech quality/less delay which is important in real time applications such as SIP- telephony; and the mechanism is possible using the existing SIP messages.
A specific embodiment of the invention will now be described by way of example only, with reference to the drawing in which:
Figure 1 shows a communications network comprising a number of linked SIP- servers;
Figure 2 shows a block diagram of a SIP server in accordance with the invention.
A communications network 1 comprises a number of network nodes 2 to 5 linked together by communication links 6 to 9 as shown in figure 1. The nodes are SIP servers based on computers. Suitable computers for this purpose include Sun Microsystems NETRA ™ Tl. The servers include Ethernet switches and the communications links 6 to 9 are high-speed links. It will be appreciated that the network will include more nodes and links which have been reduced in the figure for the purpose of simplicity. The SIP servers are nominally identical and figure 2 shows a SIP server 20 in block diagram form. Block 21 is a routing manager which maintains a routing table 22 held in memory.
Current SIP servers utilise messages to establish sessions. The invention utilises the existing SIP messages provided by the protocol to enable routing information to be determined and utilised to provide routing functionality. The messaging is utilised to populate and to maintain the routing table 22 by the routing manager 21. The messages available are described in RFC 3256.
The messages provide two types of function.
In a first function, notifications of load, overload, failure of a link between servers is communicated. For example, SIP server 2 of figure 1 could send a SIP message to SIP server 3 requesting a notification in the case of a link overload or failure. When SIP server 3 detects those conditions it will send a SIP message indicating the condition has occurred. The routing manager 21 of server 2 then updates its routing table 22 accordingly.
In a second function, when a new route is added to a server that server send a message to all the servers to which it is connected advertising the new route in order that they may update their routing tables.
In the embodiment, the routing table associates URLs in E.164 format code points with IP addresses. Thus code point 0671 is associated with 172.23.32.4 and code point 0794 is associated with 194.64.65.9.
When a SIP message INVITE arrives at the server, the TO header is examined. For example, for the TO header 0671017003@serverl.com would be routed to IP address 172.23.32.4.
To perform, the first function the existing SIP messages SUBSCRIBE and NOTIFY are used with new events defined for the EVENT header as follows: eventload-level even overload event:Link-failure event:Route-updates (to ask for routing information).
For example, let us suppose that server 2 wishes to receive load information from server 3. To do this server 2 sends to server 3 a SUBSCRIBE message with the event header being event:load-leveI .
The server 3 then responds when the load changes within a predefined value. The response is a NOTIFY message containing the load value in the header. In this case the load is 80% of capacity and the message is of the form NOT_FY:load= 80%.
For the second function, the SIP message REGISTER is used. This message is used to create an association between a SIP URL given in the "TO" header with a destination IP-address given in the "CONTACT" header (RFC 2543). This message is normally used by SIP clients to inform the server of the current location and thus a new header "F" is included which indicates that the message includes new code point registration.
For example, a REGISTER message with a header "TO :F0677@ Server B.com" and "CONTACT: 172.20.30.10 ©Server B.com" would add in the routing table 22 the entry shown in bold below.
Code point destination address
0671 172.23.32.4
0794 194.64.65.9
0677 172.20.30.10 the new route

Claims

Claims
1. A SIP-server for use in a communications network including a plurality of SIP nodes which SIP- server including routing means to determine by SIP messages between the nodes routes through the network.
2. A SIP-server as claimed in claim 1 wherein the routing means is responsive to information in the EVENT header of the SIP messages to determine routes through the network.
3. A SIP-server as claimed in claim 1 or 2 wherein the SIP messages include information concerning at least one of: load on the node; an overload condition on the node; a link failure and a route update.
4. A SIP-server as claimed in any preceding claim wherein the SIP messages are used to update a routing table.
5. A SIP - server as claimed in claim 4 wherein the routing table associates code points to destination addresses.
6. A SIP-server substantially as hereinbefore described with reference to and as illustrated by the drawings.
PCT/EP2005/001425 2004-02-26 2005-02-07 A sip server WO2005083948A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0404259.4 2004-02-26
GB0404259A GB2411541B (en) 2004-02-26 2004-02-26 A sip server

Publications (1)

Publication Number Publication Date
WO2005083948A1 true WO2005083948A1 (en) 2005-09-09

Family

ID=32050902

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2005/001425 WO2005083948A1 (en) 2004-02-26 2005-02-07 A sip server

Country Status (2)

Country Link
GB (1) GB2411541B (en)
WO (1) WO2005083948A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1944769A1 (en) * 2005-12-09 2008-07-16 BenQ Corporation Methods and devices for selection and synchronous simulcast of content.

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060146838A1 (en) * 2004-12-30 2006-07-06 Motorola, Inc. System and method for automatic and direct routing of information in a network
GB2423436A (en) * 2005-02-18 2006-08-23 Nortel Networks Ltd Media proxy load balance management
US20070233844A1 (en) 2006-03-29 2007-10-04 Murata Kikai Kabushiki Kaisha Relay device and communication system
DE602007012475D1 (en) 2006-10-11 2011-03-24 Murata Machinery Ltd relay server
EP3253033A1 (en) 2006-12-29 2017-12-06 Huawei Technologies Co., Ltd. Method and apparatus for service processing after network element fails
US7961711B2 (en) * 2007-08-06 2011-06-14 Microsoft Corporation Fitness based routing

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1067736A2 (en) * 1999-06-30 2001-01-10 Nortel Networks Limited Establishing connections with a pre-specified quality of service across a communications network
US6584093B1 (en) * 1998-08-25 2003-06-24 Cisco Technology, Inc. Method and apparatus for automatic inter-domain routing of calls

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100426306B1 (en) * 2001-12-11 2004-04-08 한국전자통신연구원 Method for providing a load distributed processing among session initiation protocol servers

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6584093B1 (en) * 1998-08-25 2003-06-24 Cisco Technology, Inc. Method and apparatus for automatic inter-domain routing of calls
EP1067736A2 (en) * 1999-06-30 2001-01-10 Nortel Networks Limited Establishing connections with a pre-specified quality of service across a communications network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GURBANI V K ET AL: "SIP: A ROUTING PROTOCOL", BELL LABS TECHNOLOGY, BELL LABORATORIES, MURREY HILL, NJ, US, vol. 6, no. 2, 2002, pages 136 - 152, XP001132336, ISSN: 1089-7089 *
ROACH A B: "RFC 3265: Session Initiation Protocol (SIP) - Specific Event Notification", NETWORK WORKING GROUP REQUEST FOR COMMENTS, June 2002 (2002-06-01), pages 1 - 38, XP002280672 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1944769A1 (en) * 2005-12-09 2008-07-16 BenQ Corporation Methods and devices for selection and synchronous simulcast of content.

Also Published As

Publication number Publication date
GB0404259D0 (en) 2004-03-31
GB2411541A (en) 2005-08-31
GB2411541B (en) 2006-09-13

Similar Documents

Publication Publication Date Title
EP1635521B1 (en) Reducing storage requirement for route information
US7526563B2 (en) Interworking gateway and method
CN101156409B (en) A method and apparatus for distributing load on application servers
KR100666951B1 (en) Method and communication system for providing interface information between network elements
EP1911229B1 (en) Associating a telephone call with a dialog based on a computer protocol such as sip
US7646761B2 (en) Integrating multimedia capabilities with legacy networks
US7536481B2 (en) Method and system for re-synchronizing end points when an intermediary detects that the end points may be unsynchronized
US20030097447A1 (en) Bridging user agent and a proxy server for supporting network services
JP5247709B2 (en) Method for routing SIP messages when an intermediate node is unavailable
US7870418B2 (en) Enhanced presence routing and roster fidelity by proactive crashed endpoint detection
WO2005083948A1 (en) A sip server
CN1602619B (en) Apparatus and method for computer controlled call processing applications in packet switched telephone networks
US20050044127A1 (en) Dynamic load distribution within a session initiation protocol network
CN101166192A (en) Traversing of nat address translation equipment for signaling messages compliant with sip protocol
CN100574474C (en) Set up the method that communication traffic connects in a kind of communication system
US9083744B2 (en) Use of a distributed hash table to federate many small-sized IMS core infrastructures
KR20040065961A (en) Extensible communication controls
JP2014235643A (en) Cluster system of session border controller, cluster system of application server, and its sip dialog generation method
CN102624759B (en) A kind of method and node for realizing Data Migration in session
EP2064864B1 (en) Remote monitoring of phone calls
KR20070103746A (en) Method and apparatus for multiple unicast delivery of media
KR100814398B1 (en) Voip phone providing multi-call service and method thereof
US7817646B2 (en) Communication server network for computer networks
JP2006352543A (en) Sip telephone exchange system
US8842686B2 (en) Communication system configured with an SIP functioned relay server and communication method using the same

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
122 Ep: pct application non-entry in european phase