WO2005109804A2 - Session initiation protocol retransmission method - Google Patents

Session initiation protocol retransmission method Download PDF

Info

Publication number
WO2005109804A2
WO2005109804A2 PCT/US2005/007964 US2005007964W WO2005109804A2 WO 2005109804 A2 WO2005109804 A2 WO 2005109804A2 US 2005007964 W US2005007964 W US 2005007964W WO 2005109804 A2 WO2005109804 A2 WO 2005109804A2
Authority
WO
WIPO (PCT)
Prior art keywords
sip
mobile unit
server
timer
retransmission method
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.)
Ceased
Application number
PCT/US2005/007964
Other languages
French (fr)
Other versions
WO2005109804A3 (en
Inventor
William N. Shores
Nandakishore A. Albal
Louis C. Depalma
Thomas P. Emmons, Jr.
Derek A. Oxley
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.)
Motorola Solutions Inc
Original Assignee
Motorola Inc
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 Motorola Inc filed Critical Motorola Inc
Publication of WO2005109804A2 publication Critical patent/WO2005109804A2/en
Publication of WO2005109804A3 publication Critical patent/WO2005109804A3/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/04Error control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/188Time-out mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • H04L65/1104Session initiation protocol [SIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28Timers or timing mechanisms used in protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08Upper layer protocols
    • H04W80/10Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention pertains to packet data communication systems and more particularly to Session Initiation Protocol based retries of communication between a network and a user.
  • Session Initiation Protocol SIP
  • Internet protocol IP
  • Session Initiation Protocol provides for certain methodology to retry an attempted communication between a server and a mobile unit (SIP invite request) .
  • SIP employs retransmission request procedures to insure reliable transfers among networks and between the network and a user.
  • UDP User Datagram Protocol
  • SIP provides for a retransmission time period which increases on an exponential basis.
  • the SIP protocol waits for approximately one-half second before retransmitting a message. For a retransmission and each successive retransmission, the SIP protocol doubles the time interval. For example, the original one-half second wait from the initial transmission would be doubled to one second before the second retransmission of a message. The retransmission time period would then be doubled successively until a response is received or a final response time out condition occurs.
  • a wireless system such as a CDMA (Code Division Multiple Access) system the response times typically become larger since the mobile user may be in an idle or dormant state and must be connected over an air interface (wireless) .
  • CDMA Code Division Multiple Access
  • connection and response to the initial invite message or several of the retry messages will not occur within a time expected by the standard SIP response timers.
  • more retry transmissions will occur over the air interface. Accordingly, it would be desirable to have a retransmission method which is customized for the applicable interface environment thereby lowering the traffic through the system and network.
  • FIG. 1 is a block diagram of an internet protocol based packet data communication system in accordance with the present invention.
  • FIG. 2 is a flow diagram of a SIP invite request and subsequent retries in accordance with the prior art .
  • FIG. 3 is a flow chart of a SIP invite retransmission method in accordance with the present invention.
  • FIG. 1 a block diagram of a wireless packet data communication system is shown.
  • This system is a Session Initiation Protocol (SIP) based communication system.
  • the communication system shown in FIG. 1 embodies a CDMA (Code Division Multiple Access) , however this invention is similarly applicable to GSM
  • Communication system 100 is shown including mobile unit 10 being coupled to network server 35 and to other networks not shown.
  • Mobile unit 10 is coupled via a wireless link 12 to base station 15.
  • base station 15 In general the mobile unit 10 may be any client capable of being served by the communication system 100.
  • Base station 15 in turn is coupled to packet control function (PCF) 20.
  • Packet control function 20 may operate as a queuing point for internet protocol traffic to mobile unit 10. This queuing occurs when the Mobile Unit needs to be connected to the network.
  • Packet data switch node (PDSN) 25 forms a portion of the core internet protocol network. It is coupled to the PCF 20 and to the internet protocol network 30. This system extends IP to the Mobile Unit and supports the Session Initiation Protocol as defined in SIP standard RFC3261.
  • Internet protocol network 30 is coupled to a network server 35.
  • Network server 35 is coupled to other networks and other servers as necessary. These other networks and servers are not shown.
  • SIP invite request is sent through IP network 30, PDSN 25, PCF 20 to base station 15 where it is wirelessly transmitted to mobile unit 10 via wireless link 12. Establishing the wireless link 12 between base station 15 and mobile unit 20 may take some time.
  • Typical times may range from three to four seconds for a mobile unit that is not active in a call.
  • the transmission of the SIP invite from the network server 35 to mobile unit 10 is shown diagrammatically in FIG. 2.
  • FIG. 2 demonstrates the prior art that is.
  • FIG. 2 shows the flow of various SIP based messages between the network server 35 and mobile unit 10 based upon the standard IETF RFC3261.
  • the message flow of the SIP invite request 40 is shown from right to left, that is from network server 35 to mobile unit 10.
  • the timing of typical message transmission is shown downward in FIG 2 from top to bottom as measured in seconds.
  • network server sends a SIP invite request 40 through IP network 30, through PDSN 25 to the packet control function 20.
  • Packet control function 20 provides for queuing of traffic.
  • the SIP invite message is received by mobile unit 10 at a time which may be three seconds or more from the original time zero when the network server 35 sent the SIP invite request.
  • Mobile unit 10 then proceeds .to respond as is required by the SIP protocol to the network server 35. Based upon various situations, it responds with a SIP
  • 1XX-6XX type message 45 This message typically would be received by network server 35 approximately four seconds after the original SIP invite request was sent at time zero.
  • the SIP protocol arrangement will attempt retries since the network server 35 has not received a response from the mobile unit 10.
  • This standard SIP protocol typically calls for a retry approximately a half second after the original SIP invite.
  • This first retry SIP invite request 41 is again queued by PCF 20 since mobile unit 10 has not established the necessary connection and acknowledged to network server 35.
  • SIP 1XX-6XX response 45 was generated as a result of receiving Sip invite request 40.
  • SIP invite 1XX-6XX responses 46-48 correspond to retry SIP invites 41-43.
  • the SIP replies, SIP 1XX-6XX messages 45-48 begin to be received by network server 35 between 4 and 5.5 seconds after the original SIP invite request was transmitted. It is to be noted that all times are approximate and are based upon minimal other network traffic and appropriate network traffic engineering. These times may be further delayed if substantial network traffic exists.
  • the standard SIP protocol RFC3261 provides for a poor call processing performance. That is, SIP invite retries 41-43 and their responses 1XX-6XX 46-48 may not have been needed at all. These messages being sent back and forth through the network further load network traffic and prevent the network from operating in an optimal way. Further, this network loading may be multiplied many times for a number of mobile users.
  • FIG. 3 a flow chart of an improved retransmission SIP invite request method 50 is shown. The method is initiated and block 52 is entered. Block 52 sends an initial SIP invite request to mobile unit 10 as was done by the prior art method.
  • block 54 sets timer A equal to a time of an initial retry. This time may be set based upon the type of system and may be system specific. For example, in a wireless system this time may be set for a time greater than 3.5 seconds which is typically the time for a mobile unit to be on line and start responding. Further, block 54 starts timer A and sets an indicator K equal to zero. K may be stored in software memory of the network server 35 or in a hardware latch, for example and represents the retransmission counter. That is, K indicates the number of retransmission attempts for an initial SIP invite that have been made. Then, network server 35 begins waiting for a response from mobile unit 10 or a time out indicator of timer A, block 56.
  • Block 58 determines the type of response or time out that has occurred. If a SIP response of the type 1XX is received, block 58 transfers control to block 60 via the SIP 1XX path. This corresponds to a timely provisional response by mobile unit 10 and as a result block 60 stops timer A, which is the retry timer. Then, block 60 transfers control to block 56 to wait for another SIP response or time out. If a SIP 2XX-6XX type message was received as the SIP response, block 58 transfers control to block 62 via the Sip 2XX-6XX path.
  • a SIP 2XX-6XX message indicates a successful final response or an unrecoverable condition such as a fault or error.
  • Block 62 stops the timer A, which is the retry timer.
  • block 62 ends the retry method since the final response has been received.
  • the controlling system then processes the response in accordance with the application that sent the first SIP Invite at block 52. Typically this would include either sending other SIP messages or recovery from the error condition.
  • timer A which is the retry timer expires, block 58 transfers control to block 64 via the timer A expire path.
  • Block 64 increments the retransmission counter K by one.
  • block 66 determines whether the retransmission counter K is greater than a maximum number of retransmission attempts.
  • block 66 transfers control to end the process via the yes path.
  • the controlling system then processes the response in accordance with the application that sent the first SIP Invite at block 52. Since the timer A was initially set with an initial retransmission time, this initial retry or retransmission time allows the system operator to insure that SIP behaviors match expected responses from the target unit, such as a mobile unit. That is, an initial time before a retry may be set as to match the characteristics of the network. Therefore, timer A is a variable parameter which may be engineered by the system operator to correspond with real response times of the network. As a result, much retry or retransmission of the initial SIP invite messages is eliminated from the network.
  • retransmission SIP invite messages 41-43 will each be eliminated from being sent by network server 35 by this method. Further, the responses 46-48 will be eliminated from being transmitted through the network by the mobile unit 10 back to the network server 35. For typical behavior of method 50 without a fault only a SIP invite 40 and a SIP IXX response 45 will be sent through the network. Retransmissions 41-43 and their corresponding replies 46-48 will not occur.
  • block 66 determines that the retransmission count is less than or equal to the maximum number of retransmissions, block 66 transfers control to block 68 via the no path.
  • Block 68 retransmits the SIP request to the user.
  • block 70 determines whether the retransmission mode is mode one or mode two. For mode one a typical value is set is timer A. This may be the same value as the standard SIP initial retry value (known as Tl) or some slight variation. Block 70 transfers control to block 72 via the mode one path. Block 72 sets timer A equal to time Tl as mentioned above. Block 72 then transfers control to block 56 to begin the wait for response. If the retransmission mode is mode two, block 70 transfers control to block 74 via the mode two path.
  • Tl standard SIP initial retry value
  • Block 74 sets timer A equal to two raised to the K th power which is the retransmission counter times the basic time value Tl. Effectively, this doubles the waiting time for each subsequent transmission. Block 74 then transfers control to block 56 to wait for a SIP response or time out.
  • the linear case is where aO is equal to Tl and all other coefficients are zero and the exponential case is the corresponding Taylor expansion of the exponential function.
  • the initial retry or retransmission time may be dynamically adjusted based upon a statistical analysis of measurement data taken by a system operator. Although four seconds was initially recommended above as an example, the time may be varied depending upon observed traffic flow or even dynamically adjusted to account for traffic peaks. For example, communication systems typically collect statistics regarding average time between SIP invite requests and SIP trying responses.
  • the system may set the initial retry or retransmission timer, timer A, to a value of approximately 90% of when responses are typically received.
  • timer A the initial retry or retransmission timer
  • the present SIP retransmission method enables optimal use of message retransmission and minimizes bandwidth utilization for retransmission messages. This results in optimization of call processing performance; efficient use of precious air interface resources; promotes convergence of internet and wireless products and services; and effectively extends Session Initiation Protocol services to wireless services.
  • the present invention determines that retrying the transmission of messages is premature. The system waits until there is a greater likelihood that a wireless target is able to receive and respond before sending a retry transmission.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Communication Control (AREA)

Abstract

For a network server (35) communicating with a wireless unit (10) via a Session Initiation Protocol, a retransmission method (50) first sets a timer based upon a time likely for a mobile unit to respond (54). Then the network server waits for a response (56). When the timer set for the kind of mobile unit being used expires (64), a retransmit of the original SIP request takes place (68). Optionally, modes for waiting may include a linear mode (72) and an exponential mode (74).

Description

SESSION INITIATION PROTOCOL RETRANSMISSION METHOD
BACKGROUND OF THE INVENTION
The present invention pertains to packet data communication systems and more particularly to Session Initiation Protocol based retries of communication between a network and a user. Session Initiation Protocol (SIP) over Internet protocol (IP) is commonly used in packet data networks to provide services including voice to wireless or mobile users. Session Initiation Protocol provides for certain methodology to retry an attempted communication between a server and a mobile unit (SIP invite request) . When using User Datagram Protocol (UDP) as a transport protocol, SIP employs retransmission request procedures to insure reliable transfers among networks and between the network and a user. Currently SIP provides for a retransmission time period which increases on an exponential basis. That is, the SIP protocol waits for approximately one-half second before retransmitting a message. For a retransmission and each successive retransmission, the SIP protocol doubles the time interval. For example, the original one-half second wait from the initial transmission would be doubled to one second before the second retransmission of a message. The retransmission time period would then be doubled successively until a response is received or a final response time out condition occurs. When SIP is used over a wireless system, such as a CDMA (Code Division Multiple Access) system the response times typically become larger since the mobile user may be in an idle or dormant state and must be connected over an air interface (wireless) . For such mobile users there is a very high probability that connection and response to the initial invite message or several of the retry messages will not occur within a time expected by the standard SIP response timers. As a result more retry transmissions will occur over the air interface. Accordingly, it would be desirable to have a retransmission method which is customized for the applicable interface environment thereby lowering the traffic through the system and network.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of an internet protocol based packet data communication system in accordance with the present invention. FIG. 2 is a flow diagram of a SIP invite request and subsequent retries in accordance with the prior art . FIG. 3 is a flow chart of a SIP invite retransmission method in accordance with the present invention.
PREFERRED EMBODIMENT OF THE INVENTION Referring to FIG. 1, a block diagram of a wireless packet data communication system is shown. This system is a Session Initiation Protocol (SIP) based communication system. The communication system shown in FIG. 1 embodies a CDMA (Code Division Multiple Access) , however this invention is similarly applicable to GSM
(Global System Mobile) , GPRS (GSM Packet Radio Service) , or iDEN communication systems. CDMA type communication systems include IS-95, UMTS (Universal Mobile Telephone Service) and other CDMA variations. Communication system 100 is shown including mobile unit 10 being coupled to network server 35 and to other networks not shown. Mobile unit 10 is coupled via a wireless link 12 to base station 15. In general the mobile unit 10 may be any client capable of being served by the communication system 100. Base station 15 in turn is coupled to packet control function (PCF) 20. Packet control function 20, among other things, may operate as a queuing point for internet protocol traffic to mobile unit 10. This queuing occurs when the Mobile Unit needs to be connected to the network. Packet data switch node (PDSN) 25 forms a portion of the core internet protocol network. It is coupled to the PCF 20 and to the internet protocol network 30. This system extends IP to the Mobile Unit and supports the Session Initiation Protocol as defined in SIP standard RFC3261. Internet protocol network 30 is coupled to a network server 35. Network server 35 is coupled to other networks and other servers as necessary. These other networks and servers are not shown. For the network server 35 to initiate communications with mobile unit 10, a SIP invite request is sent through IP network 30, PDSN 25, PCF 20 to base station 15 where it is wirelessly transmitted to mobile unit 10 via wireless link 12. Establishing the wireless link 12 between base station 15 and mobile unit 20 may take some time. Typical times may range from three to four seconds for a mobile unit that is not active in a call. The transmission of the SIP invite from the network server 35 to mobile unit 10 is shown diagrammatically in FIG. 2. FIG. 2 demonstrates the prior art that is. FIG. 2 shows the flow of various SIP based messages between the network server 35 and mobile unit 10 based upon the standard IETF RFC3261. The message flow of the SIP invite request 40 is shown from right to left, that is from network server 35 to mobile unit 10. The timing of typical message transmission is shown downward in FIG 2 from top to bottom as measured in seconds. At time zero, network server sends a SIP invite request 40 through IP network 30, through PDSN 25 to the packet control function 20. Packet control function 20 provides for queuing of traffic. Since it is known that this is a wireless system, sending a SIP invite to a mobile unit which is not currently on line will produce no value. As a result the PCF queues the SIP invite request until the Mobile Unit is connected. Further, the PCF 20 indicates to base station 15 that it is wishing to communicate with mobile unit 10. Base station 15 then goes about establishing a communication link 12 with mobile unit 10. The elapsed time is shown as the downward portion of the SIP invite request in the dashed line portion. Before the SIP invite request may finally be transmitted by the PCF 20, a connection acknowledgment must be received. After connection of the mobile unit 10 to base station 15, the SIP invite message is received by mobile unit 10 at a time which may be three seconds or more from the original time zero when the network server 35 sent the SIP invite request. Mobile unit 10 then proceeds .to respond as is required by the SIP protocol to the network server 35. Based upon various situations, it responds with a SIP
1XX-6XX type message 45. This message typically would be received by network server 35 approximately four seconds after the original SIP invite request was sent at time zero. According to SIP standard RFC3261, the SIP protocol arrangement will attempt retries since the network server 35 has not received a response from the mobile unit 10. This standard SIP protocol typically calls for a retry approximately a half second after the original SIP invite. As a result network server 35 sends a retry of the SIP invite request 41 at time = .5 seconds. This first retry SIP invite request 41 is again queued by PCF 20 since mobile unit 10 has not established the necessary connection and acknowledged to network server 35. Next the standard SIP retransmission protocol requires waiting a time which is doubled from the previous retry before retrying again. Therefore, at time = 1.5 seconds from the original SIP invite, a second retry Sip invite request 42 is made by network server 35. Again, it is transmitted through IP network 30, PDSN 25 and is queued by PCF 20 since mobile unit 10 is not yet on line and active. Since according to SIP standard protocol an interval is doubled from the previous retry interval, at time = 3.5 seconds, which is a two second delay or doubling the previous delay of one second, a third retry SIP invite request 43 is sent by network server 35 and is queued by PCF 20 similar to each of the previous SIP invite requests 40-42. As mobile unit 10 comes on line through base station 15, it begins responding to each of the SIP invites, the original SIP invite 40 and the retry SIP invites 41-43. The SIP 1XX-6XX response 45 was generated as a result of receiving Sip invite request 40. Similarly, SIP invite 1XX-6XX responses 46-48 correspond to retry SIP invites 41-43. As - can be seen from FIG. 2, the SIP replies, SIP 1XX-6XX messages 45-48, begin to be received by network server 35 between 4 and 5.5 seconds after the original SIP invite request was transmitted. It is to be noted that all times are approximate and are based upon minimal other network traffic and appropriate network traffic engineering. These times may be further delayed if substantial network traffic exists. As can be seen for the case of wireless packet data system 100 as shown in FIG. 1, the standard SIP protocol RFC3261 provides for a poor call processing performance. That is, SIP invite retries 41-43 and their responses 1XX-6XX 46-48 may not have been needed at all. These messages being sent back and forth through the network further load network traffic and prevent the network from operating in an optimal way. Further, this network loading may be multiplied many times for a number of mobile users. Referring to FIG. 3, a flow chart of an improved retransmission SIP invite request method 50 is shown. The method is initiated and block 52 is entered. Block 52 sends an initial SIP invite request to mobile unit 10 as was done by the prior art method. Next, block 54 sets timer A equal to a time of an initial retry. This time may be set based upon the type of system and may be system specific. For example, in a wireless system this time may be set for a time greater than 3.5 seconds which is typically the time for a mobile unit to be on line and start responding. Further, block 54 starts timer A and sets an indicator K equal to zero. K may be stored in software memory of the network server 35 or in a hardware latch, for example and represents the retransmission counter. That is, K indicates the number of retransmission attempts for an initial SIP invite that have been made. Then, network server 35 begins waiting for a response from mobile unit 10 or a time out indicator of timer A, block 56. If either a response or a time out is detected, block 58 is entered. Block 58 determines the type of response or time out that has occurred. If a SIP response of the type 1XX is received, block 58 transfers control to block 60 via the SIP 1XX path. This corresponds to a timely provisional response by mobile unit 10 and as a result block 60 stops timer A, which is the retry timer. Then, block 60 transfers control to block 56 to wait for another SIP response or time out. If a SIP 2XX-6XX type message was received as the SIP response, block 58 transfers control to block 62 via the Sip 2XX-6XX path. A SIP 2XX-6XX message indicates a successful final response or an unrecoverable condition such as a fault or error. Block 62 stops the timer A, which is the retry timer. Next, block 62 ends the retry method since the final response has been received. The controlling system then processes the response in accordance with the application that sent the first SIP Invite at block 52. Typically this would include either sending other SIP messages or recovery from the error condition. If timer A which is the retry timer expires, block 58 transfers control to block 64 via the timer A expire path. Block 64 increments the retransmission counter K by one. Next, block 66 determines whether the retransmission counter K is greater than a maximum number of retransmission attempts. If K is greater than the maximum number of retransmission attempts selected by the network operator, block 66 transfers control to end the process via the yes path. The controlling system then processes the response in accordance with the application that sent the first SIP Invite at block 52. Since the timer A was initially set with an initial retransmission time, this initial retry or retransmission time allows the system operator to insure that SIP behaviors match expected responses from the target unit, such as a mobile unit. That is, an initial time before a retry may be set as to match the characteristics of the network. Therefore, timer A is a variable parameter which may be engineered by the system operator to correspond with real response times of the network. As a result, much retry or retransmission of the initial SIP invite messages is eliminated from the network. For example, retransmission SIP invite messages 41-43 will each be eliminated from being sent by network server 35 by this method. Further, the responses 46-48 will be eliminated from being transmitted through the network by the mobile unit 10 back to the network server 35. For typical behavior of method 50 without a fault only a SIP invite 40 and a SIP IXX response 45 will be sent through the network. Retransmissions 41-43 and their corresponding replies 46-48 will not occur. Next, if block 66 determines that the retransmission count is less than or equal to the maximum number of retransmissions, block 66 transfers control to block 68 via the no path. Since this is a non-fatal error and is a simple retry or retransmission due to a lost data packet or the like, retransmission of the SIP invite increases the probability of successful SIP session establishment. Block 68 retransmits the SIP request to the user. Next, block 70 determines whether the retransmission mode is mode one or mode two. For mode one a typical value is set is timer A. This may be the same value as the standard SIP initial retry value (known as Tl) or some slight variation. Block 70 transfers control to block 72 via the mode one path. Block 72 sets timer A equal to time Tl as mentioned above. Block 72 then transfers control to block 56 to begin the wait for response. If the retransmission mode is mode two, block 70 transfers control to block 74 via the mode two path.
Block 74 sets timer A equal to two raised to the Kth power which is the retransmission counter times the basic time value Tl. Effectively, this doubles the waiting time for each subsequent transmission. Block 74 then transfers control to block 56 to wait for a SIP response or time out. Although Figure 3 shows only linear or exponential retransmission timers, any other functions may be used to define the subsequent retransmission . This function can be approximated as an n dimensional polynomial of the form: tl = aO + al*K+ a2*KΛ2 + a3 *KΛ3 an*KΛn where aO, al, a2, .... an are optimized coefficients. The linear case is where aO is equal to Tl and all other coefficients are zero and the exponential case is the corresponding Taylor expansion of the exponential function. Under certain conditions it may be advantageous to dynamically adjust the value of the initial retry or retransmission set by block 54 for timer A. Thus, the initial retry or retransmission time may be dynamically adjusted based upon a statistical analysis of measurement data taken by a system operator. Although four seconds was initially recommended above as an example, the time may be varied depending upon observed traffic flow or even dynamically adjusted to account for traffic peaks. For example, communication systems typically collect statistics regarding average time between SIP invite requests and SIP trying responses. The system may set the initial retry or retransmission timer, timer A, to a value of approximately 90% of when responses are typically received. As can be seen from the above description, the present SIP retransmission method enables optimal use of message retransmission and minimizes bandwidth utilization for retransmission messages. This results in optimization of call processing performance; efficient use of precious air interface resources; promotes convergence of internet and wireless products and services; and effectively extends Session Initiation Protocol services to wireless services. The present invention determines that retrying the transmission of messages is premature. The system waits until there is a greater likelihood that a wireless target is able to receive and respond before sending a retry transmission. As a result, superfluous retry messages and their eventual response messages are inhibited by this system. Considerable end-to-end system processing is saved. Further, this system provides further call processing capability instead of using processing time for superfluous retry messages. Although the preferred embodiment of the invention has been illustrated, and that form described in detail, it will be readily apparent to those skilled in the art that various modi ications may be made therein without departing from the spirit of the present invention or from the scope of the appended claims.

Claims

1. A message retransmission method for a server and a mobile unit in a Session Initiation Protocol (SIP) based communication system, the message retransmission method comprising the step of: sending a SIP message by the server to the mobile unit; setting by the server a timer based upon a mobile unit type, network type and a time likely for response by the mobile unit type; and waiting by the server until the timer expires before sending a retransmission of the SIP message.
2. The message retransmission method as claimed in claim 1, wherein the communication system is a Code Division Multiple Access (CDMA) type of communication system.
3. The message retransmission method as claimed in claim 1, wherein the communication system is a Global System Mobile (GSM) .
4. The message retransmission method as claimed in claim 1, wherein the communication system is an iDEN communication system.
5. The message retransmission method as claimed in claim 1, wherein the step of setting by the server a timer includes a step of starting the timer.
6. The message retransmission method as claimed in claim 1, wherein the step of setting by the server the timer includes a step of setting a retransmission counter to zero.
7. The message retransmission method as claimed in claim 6, wherein there is further included steps of: determining by the server a response from the mobile unit; and determining by the server a lack of a response by the mobile unit based on expiration of the timer.
8. The message retransmission method as claimed in claim 7, wherein if a SIP IXX response was determined by the server, there is further included the steps of: stopping the timer; and repeating the step of waiting by the server.
9. The message retransmission method as claimed in claim 7, wherein if the response determined by the server is a SIP 2XX-6XX message, there is further included the steps of : stopping the timer; and ending the message retransmission method.
10. The message retransmission method as claimed in claim 7, wherein if the timer expires, there is further included a step of incrementing the retransmission counter by one .
PCT/US2005/007964 2004-04-23 2005-03-10 Session initiation protocol retransmission method Ceased WO2005109804A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/830,557 US7031273B2 (en) 2004-04-23 2004-04-23 Session initiation protocol retransmission method
US10/830,557 2004-04-23

Publications (2)

Publication Number Publication Date
WO2005109804A2 true WO2005109804A2 (en) 2005-11-17
WO2005109804A3 WO2005109804A3 (en) 2006-04-27

Family

ID=35136335

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/007964 Ceased WO2005109804A2 (en) 2004-04-23 2005-03-10 Session initiation protocol retransmission method

Country Status (4)

Country Link
US (1) US7031273B2 (en)
KR (1) KR100786991B1 (en)
CN (1) CN1947393A (en)
WO (1) WO2005109804A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8412997B2 (en) 2006-03-30 2013-04-02 Alibaba Group Holding Limited Method and system for message retransmission and intersystem message delivery

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7113980B2 (en) 2001-09-06 2006-09-26 Bea Systems, Inc. Exactly once JMS communication
FI20040742A0 (en) * 2004-05-31 2004-05-31 Nokia Corp Providing control information for the protocol
US7870265B2 (en) * 2005-06-30 2011-01-11 Oracle International Corporation System and method for managing communications sessions in a network
US7747921B2 (en) * 2005-08-05 2010-06-29 Sony Corporation Systems and methods for transmitting data over lossy networks
CN101346634B (en) * 2005-11-04 2012-10-24 甲骨文国际公司 System and method for a gatekeeper in a communications network
US8112525B2 (en) * 2006-05-16 2012-02-07 Oracle International Corporation Engine near cache for reducing latency in a telecommunications environment
US8001250B2 (en) * 2006-05-16 2011-08-16 Oracle International Corporation SIP and HTTP convergence in network computing environments
US8171466B2 (en) 2006-05-16 2012-05-01 Oracle International Corporation Hitless application upgrade for SIP server architecture
US8219697B2 (en) 2006-05-17 2012-07-10 Oracle International Corporation Diameter protocol and SH interface support for SIP server architecture
WO2007140162A2 (en) * 2006-05-26 2007-12-06 Whaleback Systems Corporation Sending a page
US7661027B2 (en) * 2006-10-10 2010-02-09 Bea Systems, Inc. SIP server architecture fault tolerance and failover
US20080086567A1 (en) * 2006-10-10 2008-04-10 Bea Systems, Inc. SIP server architecture for improving latency in message processing
US9667430B2 (en) * 2006-12-13 2017-05-30 Oracle International Corporation System and method for a SIP server with offline charging
US8078737B2 (en) * 2006-12-13 2011-12-13 Oracle International Corporation System and method for efficient storage of long-lived session state in a SIP server
US20080147551A1 (en) * 2006-12-13 2008-06-19 Bea Systems, Inc. System and Method for a SIP Server with Online Charging
US7742417B2 (en) 2007-02-16 2010-06-22 International Business Machines Corporation Burst traffic smoothing for SIP processing elements
US11095583B2 (en) 2007-06-28 2021-08-17 Voxer Ip Llc Real-time messaging method and apparatus
US8180029B2 (en) 2007-06-28 2012-05-15 Voxer Ip Llc Telecommunication and multimedia management method and apparatus
US20110019662A1 (en) 2007-06-28 2011-01-27 Rebelvox Llc Method for downloading and using a communication application through a web browser
US9178916B2 (en) 2007-06-28 2015-11-03 Voxer Ip Llc Real-time messaging method and apparatus
US7895475B2 (en) * 2007-07-11 2011-02-22 Oracle International Corporation System and method for providing an instrumentation service using dye injection and filtering in a SIP application server environment
JP4905325B2 (en) * 2007-11-02 2012-03-28 ソニー株式会社 Content providing system and monitoring server
US8289870B2 (en) * 2009-09-23 2012-10-16 Avaya Inc. Priority-based, dynamic optimization of utilized bandwidth
US8260197B2 (en) * 2010-02-11 2012-09-04 Kabushiki Kaisha Kenwood Radio repeating system, radio repeating apparatus, radio terminal operating method and radio repeating method
US8981857B2 (en) 2012-11-15 2015-03-17 Freescale Semiconductor, Inc. Temperature dependent timer circuit
US20140364118A1 (en) * 2013-06-10 2014-12-11 Broadcom Corporation Method and Apparatus for Incoming Call Detection in a Dual SIM Single RF Communication Device
US9660719B2 (en) 2014-11-17 2017-05-23 Honeywell International Inc. Minimizing propagation times of queued-up datalink TPDUs
US9998360B2 (en) 2014-11-17 2018-06-12 Honeywell International Inc. Minimizining message propagation times when brief datalink interruptions occur
US10069871B2 (en) * 2016-02-01 2018-09-04 Verizon Patent And Licensing Inc. Measuring session initiation protocol (SIP) messaging latency
CN109391593B (en) * 2017-08-08 2022-04-19 展讯通信(上海)有限公司 Retry time determination method and device for media session, storage medium and terminal
US10462643B1 (en) * 2018-04-04 2019-10-29 T-Mobile Usa, Inc. Call setup logic with emerg-request-non-100 timer
CN112187615B (en) * 2020-08-31 2022-11-08 Oppo(重庆)智能科技有限公司 Message response method, device, terminal and storage medium
CN113079394A (en) * 2021-03-27 2021-07-06 深圳市研强物联技术有限公司 Method, system and terminal for realizing streaming media playing by ASR platform voice assistant

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1260108B1 (en) * 2000-03-03 2010-04-28 QUALCOMM Incorporated Method and apparatus for participating in group communication services in an existing communication system
US20040255039A1 (en) * 2001-05-10 2004-12-16 Bernard Honeisen Method, system and network element device for controlling sessions between terminals
US7272113B2 (en) * 2001-12-05 2007-09-18 Nokia Corporation Apparatus, and associated method, for communicating frame-formatted data at a selected QoS level in a radio communication system
KR100498932B1 (en) * 2002-12-30 2005-07-04 삼성전자주식회사 Apparatus and method for session establishment in radio network organized mobile nodes
US20040230659A1 (en) * 2003-03-12 2004-11-18 Chase Michael John Systems and methods of media messaging

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8412997B2 (en) 2006-03-30 2013-04-02 Alibaba Group Holding Limited Method and system for message retransmission and intersystem message delivery

Also Published As

Publication number Publication date
KR100786991B1 (en) 2007-12-18
WO2005109804A3 (en) 2006-04-27
US20050237999A1 (en) 2005-10-27
CN1947393A (en) 2007-04-11
KR20070015405A (en) 2007-02-02
US7031273B2 (en) 2006-04-18

Similar Documents

Publication Publication Date Title
US7031273B2 (en) Session initiation protocol retransmission method
JP5684301B2 (en) Transaction timeout processing in communication session management
TWI483589B (en) Data transmission method and data retransmission method
US6611495B1 (en) System and method for improved data transfer in packet-switched communication networks
US7028094B2 (en) Data communication method, system, and transmitter and receiver constituting the system
EP1161036B1 (en) Prevent transmission of packets to terminal when the terminal switches to the suspend state in the packet switched service to use a circuit switched service
JP4601871B2 (en) Data flow control method in communication system
WO1999001965A1 (en) Method for pacing data flow in a packet-based network
US7733826B2 (en) Method and related apparatus of default timer configurations of wireless communications system
KR100804082B1 (en) Method and apparatus for avoiding redundant negotiations during communication establishment
EP2168261B1 (en) Method for enhancing of controlling radio resources, method for transmitting status report, and receiver in mobile communication system
US20070159985A1 (en) Method and an arrangement for avoiding unnecessary retransmissions
JP4485684B2 (en) Method and apparatus for transmitting data packet in communication system
US12609973B2 (en) Method for handling calls with sessions initiation protocol
CN114143291B (en) HTTP communication method and system based on TCP and UDP
Jayananthan TCP performance enhancement over wireless networks
Kueh et al. On the Interaction Between SIP and RLC Error Recovery in Session Establishment over Satellite-UMTS
Igarashi et al. Mobility-aware TCP: Making robust TCP against segment loss in wireless networks
HK1101463B (en) A method and an arrangement for avoiding unnecessary retransmissions

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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: A2

Designated state(s): 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
WWE Wipo information: entry into national phase

Ref document number: 200580012531.1

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 1020067021997

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

WWP Wipo information: published in national office

Ref document number: 1020067021997

Country of ref document: KR

122 Ep: pct application non-entry in european phase