GB2411541A - A SIP server - Google Patents

A SIP server Download PDF

Info

Publication number
GB2411541A
GB2411541A GB0404259A GB0404259A GB2411541A GB 2411541 A GB2411541 A GB 2411541A GB 0404259 A GB0404259 A GB 0404259A GB 0404259 A GB0404259 A GB 0404259A GB 2411541 A GB2411541 A GB 2411541A
Authority
GB
United Kingdom
Prior art keywords
sip
server
messages
routing
load
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
GB0404259A
Other versions
GB0404259D0 (en
GB2411541B (en
Inventor
Nikolaos Kollias
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
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 AG filed Critical Siemens AG
Priority to GB0404259A priority Critical patent/GB2411541B/en
Publication of GB0404259D0 publication Critical patent/GB0404259D0/en
Priority to PCT/EP2005/001425 priority patent/WO2005083948A1/en
Publication of GB2411541A publication Critical patent/GB2411541A/en
Application granted granted Critical
Publication of GB2411541B publication Critical patent/GB2411541B/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

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

Abstract

A Session Initiation Protocol (SIP) server, 2, 3, 4 or 5, includes a routing function (21, figure 2) that utilises SIP messages to obtain the load conditions or other parameters of network nodes (which may be other SIP servers) that may be usefully taken into account when determining the route used in the network. Information concerning at least one of, load on node, overload conditions, link failures or route updates, are contained in the EVENT header of the SIP message. The SIP messages may be used to update routing tables.

Description

! 2411 541 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, SIP:Session 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 SIPservers 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 SIPserver 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: s the provision of a mechanism to update and change routing tables of SIPservers 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 _ T1. 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 IF 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 0671017003Ccserverl.com would be routed to IF 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: event: load-level event: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-level.
The server 3 then responds when the load changes within a predestined 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 NOTIFY: 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 s

Claims (6)

  1. 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. 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. 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. 4. A SIP-server as claimed in any preceding claim wherein the SIP messages are used to update a routing table.
  5. 5. A SIP - server as claimed in claim 4 wherein the routing table associates code points to destination addresses.
  6. 6. A SIP-server substantially as hereinbefore described with reference to and as illustrated by the drawings.
GB0404259A 2004-02-26 2004-02-26 A sip server Expired - Fee Related GB2411541B (en)

Priority Applications (2)

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

Applications Claiming Priority (1)

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

Publications (3)

Publication Number Publication Date
GB0404259D0 GB0404259D0 (en) 2004-03-31
GB2411541A true GB2411541A (en) 2005-08-31
GB2411541B GB2411541B (en) 2006-09-13

Family

ID=32050902

Family Applications (1)

Application Number Title Priority Date Filing Date
GB0404259A Expired - Fee Related GB2411541B (en) 2004-02-26 2004-02-26 A sip server

Country Status (2)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2423436A (en) * 2005-02-18 2006-08-23 Nortel Networks Ltd Media proxy load balance management
EP1926285A2 (en) 2006-10-11 2008-05-28 Murata Machinery Ltd. Relay server
GB2434502B (en) * 2004-12-30 2009-05-06 Motorola Inc System and method for automatic and direct routing of information in a network
EP2183883A1 (en) * 2007-08-06 2010-05-12 Microsoft Corporation Fitness based routing
US8499083B2 (en) 2006-03-29 2013-07-30 Murata Kikai Kabushiki Kaisha Relay device and communication system

Families Citing this family (2)

* 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.
WO2008083587A1 (en) 2006-12-29 2008-07-17 Huawei Technologies Co., Ltd. Method and system and network element for service processing after network element data invalidated and occurring fault

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030110257A1 (en) * 2001-12-11 2003-06-12 Wook Hyun Method for performing a load distribution between session initiation protocol servers within an intra domain

Family Cites Families (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
US6678264B1 (en) * 1999-06-30 2004-01-13 Nortel Networks Limited Establishing connections with a pre-specified quality of service across a communication network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030110257A1 (en) * 2001-12-11 2003-06-12 Wook Hyun Method for performing a load distribution between session initiation protocol servers within an intra domain

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2434502B (en) * 2004-12-30 2009-05-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
US8499083B2 (en) 2006-03-29 2013-07-30 Murata Kikai Kabushiki Kaisha Relay device and communication system
EP1926285A2 (en) 2006-10-11 2008-05-28 Murata Machinery Ltd. Relay server
EP1926285A3 (en) * 2006-10-11 2008-10-29 Murata Machinery Ltd. Relay server
EP2112805A1 (en) * 2006-10-11 2009-10-28 Murata Machinery, Ltd. Relay server
US8316134B2 (en) 2006-10-11 2012-11-20 Murata Machinery, Ltd. File server device arranged in a local area network and being communicable with an external server arranged in a wide area network
EP2183883A1 (en) * 2007-08-06 2010-05-12 Microsoft Corporation Fitness based routing
EP2183883A4 (en) * 2007-08-06 2014-04-16 Microsoft Corp Fitness based routing

Also Published As

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

Similar Documents

Publication Publication Date Title
EP1635521B1 (en) Reducing storage requirement for route information
US7526563B2 (en) Interworking gateway and method
AU772765B2 (en) SIP-based feature control
KR101458336B1 (en) A backup sip server for the survivability of an enterprise network using sip
KR100666951B1 (en) Method and communication system for providing interface information between network elements
US9497230B2 (en) Apparatus and method for computer controlled call processing applications in packet switched telephone networks
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
US7870418B2 (en) Enhanced presence routing and roster fidelity by proactive crashed endpoint detection
JP5247709B2 (en) Method for routing SIP messages when an intermediate node is unavailable
WO2005083948A1 (en) A sip server
CN1602619B (en) Apparatus and method for computer controlled call processing applications in packet switched telephone networks
CA2601850A1 (en) A method and apparatus for distributing load on application servers
US20050044127A1 (en) Dynamic load distribution within a session initiation protocol network
US7565448B1 (en) Network control system for a communication network
CN101166192A (en) Traversing of nat address translation equipment for signaling messages compliant with sip protocol
KR20040065961A (en) Extensible communication controls
US7787373B2 (en) Method and apparatus for providing secure blast calls
JP2004509482A (en) Method and system for dynamic gateway selection in an IP telephone network
KR20070103746A (en) Method and apparatus for multiple unicast delivery of media
KR100814398B1 (en) Voip phone providing multi-call service and method thereof
US20070268912A1 (en) Communication Server Network for Computer Networks
US8842686B2 (en) Communication system configured with an SIP functioned relay server and communication method using the same
Patel Gateway between XMPP & SIP for Extensible Messaging and Voice over IP
WO2024049554A1 (en) Alternative route propogation

Legal Events

Date Code Title Description
732E Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)

Free format text: REGISTERED BETWEEN 20090212 AND 20090218

PCNP Patent ceased through non-payment of renewal fee

Effective date: 20090226