WO2016101457A1 - 一种终端及终端呼叫软切换的方法 - Google Patents

一种终端及终端呼叫软切换的方法 Download PDF

Info

Publication number
WO2016101457A1
WO2016101457A1 PCT/CN2015/077197 CN2015077197W WO2016101457A1 WO 2016101457 A1 WO2016101457 A1 WO 2016101457A1 CN 2015077197 W CN2015077197 W CN 2015077197W WO 2016101457 A1 WO2016101457 A1 WO 2016101457A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
terminal
sip
invite message
standby
Prior art date
Application number
PCT/CN2015/077197
Other languages
English (en)
French (fr)
Inventor
李家宁
王晓艳
张建龙
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US15/537,433 priority Critical patent/US20180027028A1/en
Priority to EP15871533.4A priority patent/EP3223484A4/en
Publication of WO2016101457A1 publication Critical patent/WO2016101457A1/zh

Links

Images

Classifications

    • 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/1073—Registration or de-registration
    • 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/1069—Session establishment or de-establishment
    • 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/1083—In-session procedures
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • 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/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This document relates to the field of switching primary and secondary servers in SIP terminals of NGN (Next Generation Network) network, and in particular, to a method for soft handover of terminals and terminals.
  • NGN Next Generation Network
  • the switching between the active and standby servers of the SIP terminal refers to the failure of the SIP server currently registered, and the SIP terminal can register with another server, and the service of the terminal is not affected.
  • the SIP terminal is switched between the active and standby servers. It needs to be managed by two or more SIP servers. These SIP servers adopt the active/standby working mechanism. Under normal circumstances, the SIP terminal is only controlled by the primary server. Once the primary server fails. The SIP terminal registers with the standby server according to the pre-configured address information, and the standby server takes over the control of the primary server to ensure that the system is not interrupted. This working mode is active/standby switching, which is also called disaster recovery or dual-homing.
  • the most common way to switch is for the SIP terminal to use the registration refresh to detect the server status.
  • the validity period of SIP registration is generally long (0.5 hours to 1 hour). If the current server fails, the status of the server cannot be sensed in time, and voice calls cannot be made during the refresh period.
  • Another common way is to use a heartbeat mechanism to detect server status. This method is more sensitive.
  • the disadvantage is that both the SIP terminal and the server support the same heartbeat message, and the heartbeat is sent periodically. To occupy a certain amount of network traffic, the load on the core network device is increased. If the currently registered server is faulty, it takes a certain time for the heartbeat to initiate detection and the active/standby switchover. During this time, the user cannot dial out by dialing the phone.
  • Another way is to notify the SIP terminal to switch by the SIP server. This method is the most sensitive, and the SIP terminal can switch immediately. However, this mechanism requires that both the SIP server and the SIP terminal support specific notification messages (there is no specification at present), the versatility is weak, and in many cases, the server cannot be sent out when the server fails (such as powering off the network), so This method is not very reliable.
  • INVITE It is a SIP protocol session initiation message used to initiate a long-connected session. For a SIP fixed-line terminal, the INVITE is used to initiate a call. The INVITE and its response messages are defined by the protocol specification. The interoperability is very good. No additional messages such as heartbeat are required. The network requirements are low. The INVITE message is used to judge whether the host is performed according to the call status (such as timeout or specific error code). Backup switch. However, after the INVITE retransmission timeout, the SIP terminal switches the active and standby servers, and the INVITE message is discarded. The user needs to hang up and then pick up the phone again.
  • the above several implementation methods have advantages and disadvantages in the active/standby switchover, but they cannot solve a problem. That is, if the current server is the primary server, the primary server cannot communicate with the SIP terminal for some time due to some reason (such as power failure). During this period, the user picks up the phone and the SIP terminal sends an INVITE. The server is unresponsive and the user has to hang up and wait for the appropriate time to pick up the phone again. In this case, at least one call loss will occur in all of the above methods. This is not a good experience for the user.
  • the embodiment of the present invention provides a method for soft handover of a terminal and a terminal call, which is used to solve the problem that when the communication link is faulty between the SIP terminal and the server in the related art, all the active/standby switching modes are at least when the user picks up the phone. There is a problem with a call loss.
  • the embodiment of the present invention provides a method for soft handover of a terminal call, which includes the following steps: when the terminal sends an INVITE message to the currently registered first server and does not receive a response, the terminal according to the retransmission interval time The first server retransmits the INVITE message; when the number of retransmissions of the INVITE message is greater than a preset value, and the response of the first server is not obtained, the terminal sends a registration message to the second server; After the terminal registers with the second server, the terminal sends the INVITE message to the second server.
  • the retransmission interval is sequentially increased according to the number of retransmissions.
  • the terminal is a SIP terminal
  • the first server is a SIP primary server
  • the second server is a SIP standby server.
  • the terminal is a SIP terminal
  • the first server is a SIP standby server
  • the second server is a SIP primary server.
  • the embodiment of the present invention further provides a terminal, including an INVITE message retransmission module, a registration message sending module, and an INVITE message sending module.
  • the INVITE message retransmission module is configured to send an INVITE message to the currently registered first server. Retrieving the INVITE message to the first server according to the retransmission interval time; the registration message sending module is configured to: when the number of retransmissions of the INVITE message is greater than a preset value, When the first server responds, the registration message is sent to the second server; the INVITE message sending module is configured to send the INVITE message to the second server after the terminal registers with the second server.
  • the retransmission interval is sequentially increased according to the number of retransmissions.
  • the terminal is a SIP terminal
  • the first server is a SIP primary server
  • the second server is a SIP standby server.
  • the terminal is a SIP terminal
  • the first server is a SIP standby server
  • the second server is a SIP primary server.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the device such as the terminal and the server does not need to support the heartbeat and the notification message, and the number of retransmissions of the INVITE message can be used to determine whether to perform the active/standby switchover, especially when the server is switched.
  • the INVITE message is also directly switched over, and the call is established normally, the user experience is good, the process is simple, and the reliability is high.
  • FIG. 1 is a flowchart of a method for soft handover of a terminal call according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a SIP terminal switching from a SIP primary server to a SIP standby server according to a first embodiment of the present invention
  • FIG. 3 is a flowchart of a SIP terminal switching from a SIP standby server to a SIP primary server according to a second preferred embodiment of the present invention
  • FIG. 4 is a schematic diagram of a terminal according to an embodiment of the present invention.
  • a preferred embodiment of the present invention provides a method for soft handover of a terminal call, including the following steps: 101: When a terminal sends an INVITE message to a currently registered first server, the terminal does not receive a response. Retransmitting the INVITE message to the first server during the interval; 102: when the number of retransmissions of the INVITE message is greater than a preset value, and the response of the first server is not obtained, the terminal is second The server sends a registration message; 103: after the terminal registers with the second server, the terminal sends the INVITE message to the second server.
  • FIG. 2 is a flow chart showing a process in which a SIP terminal switches from a SIP primary server to a SIP standby server according to a first preferred embodiment of the present invention.
  • the terminal is a SIP terminal
  • the first server is a SIP primary server
  • the second server is a SIP standby server.
  • Step 201 The SIP terminal registers with the SIP primary server. After the user picks up the phone, the INVITE call message is sent to the SIP primary server.
  • Step 202 The SIP primary server is powered off or disconnected at this time, and does not return any response message.
  • the SIP terminal retransmits the INVITE message under the action of the internal retransmission timer. Generally, the retransmission interval is incremented. When the number of retransmissions reaches the preset maximum value and no response is received, the communication link is considered to be disconnected.
  • the network usage experience setting can be modified by media or configuration commands. Here, it is assumed that the retransmission 3 times does not answer that the link has been disconnected;
  • Step 203 After the INVITE retransmission exceeds the maximum number of times, it is considered that the SIP terminal and the SIP primary server link have been disconnected, and the SIP terminal switches to register with the SIP standby server.
  • Step 204 The SIP terminal normally receives the 200 OK response, and the registration is successful.
  • Step 205 After the registration is successful, the SIP terminal sends the cached INVITE message to the SIP standby server.
  • Step 206 The SIP standby server sends a 180RING message to the SIP terminal.
  • Step 207 The SIP standby server sends a 200 OK response to the SIP terminal.
  • Step 208 The SIP terminal sends a correct response (ACK) to the SIP standby server.
  • FIG. 3 is a flow chart showing a process in which a SIP terminal switches from a SIP standby server to a SIP primary server according to a second preferred embodiment of the present invention.
  • the terminal is a SIP terminal
  • the first service is The device is a SIP standby server
  • the second server is a SIP primary server.
  • Step 301 The SIP terminal registers with the SIP standby server, and sends an INVITE call message to the SIP standby server after the user picks up the phone.
  • Step 302 The SIP standby server is powered off or disconnected at this time, and does not return any response message.
  • the SIP terminal retransmits the INVITE message under the action of the internal retransmission timer. Generally, the retransmission interval is incremented. When the number of retransmissions reaches the preset maximum value and no response is received, the link is considered to be disconnected. The second no response considers that the link has been disconnected;
  • Step 303 After the INVITE retransmission exceeds the maximum number of times, it is considered that the communication link between the SIP terminal and the SIP standby server has been disconnected, and the SIP terminal switches to register with the SIP primary server;
  • Step 304 The SIP terminal normally receives the 200 OK response, and the registration is successful.
  • Step 305 After the registration is successful, the SIP terminal sends the cached INVITE message to the SIP primary server.
  • Step 306 The SIP primary server sends a 180 RING message to the SIP terminal.
  • Step 307 The SIP primary server sends a 200 OK response to the SIP terminal.
  • Step 308 The SIP terminal sends a correct response (ACK) to the SIP primary server.
  • the preferred embodiment of the present invention further provides a terminal, including an INVITE message retransmission module 10, a registration message sending module 12, and an INVITE message sending module 14.
  • the INVITE message retransmission module 10 is configured to retransmit the INVITE message to the first server according to a retransmission interval time when the terminal sends an INVITE message to the currently registered first server without receiving a response;
  • the sending module 12 is configured to send a registration message to the second server when the number of retransmissions of the INVITE message is greater than a preset value, and the response of the first server is not obtained;
  • the INVITE message sending module 14 The method is configured to send the INVITE message to the second server after the terminal registers with the second server.
  • the detailed operation process of the terminal is the same as that described above, and therefore will not be described herein.
  • the active/standby server is directly switched, the INVITE message is cached first, and then the REGISTER is initiated to the standby server, and the previously cached INVITE message is sent after the registration is successful. Extract it and continue to send it to the standby server to initiate and establish a call.
  • the user does not need to pay attention to the process of switching between the active and standby servers, this time.
  • the call result is still successful and has no significant impact.
  • the terminal call soft handover method provided by the embodiment of the present invention can also be used in combination with the handover mode in the related art.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the solution of the embodiment of the invention has good user experience, simple process and high reliability.

Landscapes

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

Abstract

一种终端及终端呼叫软切换的方法，包括以下步骤：当终端向当前注册的第一服务器发出INVITE消息未得到响应时，所述终端根据重传间隔时间向所述第一服务器重传所述INVITE消息；当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，所述终端向第二服务器发送注册消息；当所述终端注册至所述第二服务器后，所述终端将所述INVITE消息发送至所述第二服务器。

Description

一种终端及终端呼叫软切换的方法 技术领域
本文涉及在NGN(Next Generation Network，下一代网络)网络SIP终端切换主备服务器领域，尤其涉及一种终端及终端呼叫软切换的方法。
背景技术
SIP终端主备服务器切换指的是当前注册上的SIP服务器出现故障，SIP终端可以向另外的服务器注册，终端的业务不受影响。一般SIP终端主备服务器切换，需要其能够归属两个或多个SIP服务器的管理，这些SIP服务器采用主备工作机制，在正常情况下，SIP终端仅受主服务器的控制，一旦主服务器出现故障，SIP终端就根据预先配置的地址信息向备服务器注册，备服务器接替主服务器进行控制，从而保证***工作不中断，这种工作方式即为主备切换，又称容灾或者双归属。
SIP终端主备服务器切换相关技术中存在以下一些问题。
最常见的切换方式是SIP终端使用注册刷新检测服务器状态。但是SIP注册有效期一般较长(0.5小时～1小时)，如果当前服务器发生故障，不能及时感知服务器的状态，在刷新周期内会无法进行语音呼叫。
另一种常见方式是采用心跳机制检测服务器状态。这种方式较为灵敏，缺点是需要SIP终端和服务器都支持同样的心跳消息，而且心跳是定期发送的，要占用一定的网络流量，会增加核心网设备的负荷。如果当前注册的服务器发生故障，心跳发起检测和主备切换需要一定时间，这段时间用户摘机拨号无法呼出。
还有一种方式是由SIP服务器通知SIP终端进行切换。这种方式最为灵敏，SIP终端可以立即切换。但是这种机制需要SIP服务器和SIP终端都支持特定的通知消息(目前尚无规范)，通用性较弱，而且在很多情况下服务器故障时是不能发出消息的(比如断电断网)，因此该方式并不是很可靠。
最后一种方式，根据INVITE消息响应来判断是否切换服务器。INVITE 是SIP协议会话发起消息，用来发起一次长连接的会话，对于SIP固话终端，INVITE用来发起呼叫。INVITE及其响应消息都是协议规范定义的，互通性很好，不需要心跳等额外消息，对网络要求较低，使用INVITE消息，根据呼叫状态(如超时或特定错误码)来判断是否进行主备切换。但是INVITE重传超时SIP终端切换主备服务器后，INVITE消息就废弃了，需要用户挂机后重新摘机拨号。
以上几种实现方式，在主备切换时各有优缺点，但是都无法解决一个问题。即如果当前注册上的是主用服务器，主用服务器由于某种原因(如断电断网)，一段时间内无法和SIP终端正常通讯，在这期间，用户摘机拨号，SIP终端发出INVITE，服务器无响应，用户不得不挂机，等待合适时间再次摘机拨号。这种情形下，以上这些方式都至少会出现一次呼损。这样对用户来说体验不佳。
发明内容
本发明实施例提供一种终端及终端呼叫软切换的方法，用来解决相关技术中SIP终端和服务器之间出现通讯链路故障时，所有主备切换方式在用户摘机拨号时，都至少会出现一次呼损的问题。
为了解决上述技术问题，本发明实施例提供一种终端呼叫软切换的方法，包括以下步骤：当终端向当前注册的第一服务器发出INVITE消息未得到响应时，所述终端根据重传间隔时间向所述第一服务器重传所述INVITE消息；当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，所述终端向第二服务器发送注册消息；当所述终端注册至所述第二服务器后，所述终端将所述INVITE消息发送至所述第二服务器。
可选地，所述重传间隔时间随所述重传次数依次递增。
可选地，所述终端为SIP终端，所述第一服务器为SIP主服务器，所述第二服务器为SIP备服务器。
可选地，所述终端为SIP终端，所述第一服务器为SIP备服务器，所述第二服务器为SIP主服务器。
本发明实施例还提供一种终端，包括INVITE消息重传模块、注册消息发送模块以及INVITE消息发送模块；所述INVITE消息重传模块，设置为当终端向当前注册的第一服务器发出INVITE消息未得到响应时，根据重传间隔时间向所述第一服务器重传所述INVITE消息；所述注册消息发送模块，设置为当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，向第二服务器发送注册消息；所述INVITE消息发送模块，设置为当所述终端注册至所述第二服务器后，将所述INVITE消息发送至所述第二服务器。
可选地，所述重传间隔时间随所述重传次数依次递增。
可选地，所述终端为SIP终端，所述第一服务器为SIP主服务器，所述第二服务器为SIP备服务器。
可选地，所述终端为SIP终端，所述第一服务器为SIP备服务器，所述第二服务器为SIP主服务器。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现上面所述的方法。
本发明实施例提供的终端呼叫软切换的方法中，终端和服务器等设备不需要支持心跳和通知消息，仅凭INVITE消息重传次数就可以判断是否进行主备切换，特别是切换服务器时用户本次INVITE消息也直接切换过去，正常发起建立呼叫，用户体验好，流程简单，可靠性高。
附图概述
图1所示为本发明实施例提供的终端呼叫软切换的方法的流程图；
图2所示为本发明第一实施例中SIP终端从SIP主服务器切换到SIP备服务器的流程图；
图3所示为本发明第二较佳实施例中SIP终端从SIP备服务器切换到SIP主服务器的流程图；
图4所示为本发明实施例提供的终端的示意图。
本发明的实施方式
如图1所示，本发明较佳实施例提供一种终端呼叫软切换的方法，包括以下步骤：101：当终端向当前注册的第一服务器发出INVITE消息未得到响应时，所述终端根据重传间隔时间向所述第一服务器重传所述INVITE消息；102：当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，所述终端向第二服务器发送注册消息；103：当所述终端注册至所述第二服务器后，所述终端将所述INVITE消息发送至所述第二服务器。
图2所示为本发明第一较佳实施例中SIP终端从SIP主服务器切换到SIP备服务器的流程图。请参照图2。于本实施例中，终端为SIP终端，第一服务器为SIP主服务器，第二服务器为SIP备服务器。
步骤201：SIP终端注册到SIP主服务器。用户摘机拨号完成后向SIP主服务器发出INVITE呼叫消息。
步骤202：SIP主服务器此时断电或者断网，不回任何响应消息。SIP终端在内部重传定时器作用下重传INVITE消息，一般重传间隔时间依次递增，当重传次数达到预设的最大值且无应答就认为通讯链路断开，这个最大值一般根据现网使用经验设定，可以通过媒介或配置命令来修改，于此，假设重传3次无应答认为链路已断开；
步骤203：INVITE重传超过最大次数后，认为SIP终端和SIP主服务器链路已经断开，SIP终端切换向SIP备用服务器注册；
步骤204：SIP终端正常收到200OK应答，注册成功；
步骤205：注册成功后，SIP终端将缓存的INVITE消息发往SIP备用服务器；
步骤206：SIP备用服务器向SIP终端发送180RING消息；
步骤207：SIP备用服务器向SIP终端发送200OK应答；
步骤208：SIP终端向SIP备用服务器发送正确应答(ACK)。
图3所示为本发明第二较佳实施例中SIP终端从SIP备服务器切换到SIP主服务器的流程图。请参照图3。于本实施例中，终端为SIP终端，第一服务 器为SIP备服务器，第二服务器为SIP主服务器。
步骤301：SIP终端注册到SIP备服务器，用户摘机拨号完成后向SIP备服务器发出INVITE呼叫消息
步骤302：SIP备服务器此时断电或者断网，不回任何响应消息。SIP终端在内部重传定时器作用下重传INVITE消息，一般重传间隔时间依次递增，当重传次数达到预设的最大值且无应答就认为链路断开，于此，假设重传3次无应答认为链路已断开；
步骤303：INVITE重传超过最大次数后，认为SIP终端和SIP备服务器通讯链路已经断开，SIP终端切换向SIP主服务器注册；
步骤304：SIP终端正常收到200 OK应答，注册成功；
步骤305：注册成功后，SIP终端将缓存的INVITE消息发往SIP主服务器；
步骤306：SIP主服务器向SIP终端发送180 RING消息；
步骤307：SIP主服务器向SIP终端发送200 OK应答；
步骤308：SIP终端向SIP主服务器发送正确应答(ACK)。
如图4所示，本发明较佳实施例还提供一种终端，包括INVITE消息重传模块10、注册消息发送模块12和INVITE消息发送模块14。所述INVITE消息重传模块10，设置为当终端向当前注册的第一服务器发出INVITE消息未得到响应时，根据重传间隔时间向所述第一服务器重传所述INVITE消息；所述注册消息发送模块12，设置为当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，向所述第二服务器发送注册消息；所述INVITE消息发送模块14，设置为当所述终端注册至所述第二服务器后，将所述INVITE消息发送至所述第二服务器。关于所述终端的详细操作过程，同上述方法所述，故于此不再赘述。
综上所述，于本发明例中，当INVITE消息重传一定次数后直接进行主备服务器切换，先将INVITE消息缓存起来，再向备服务器发起REGISTER，注册成功后再将之前缓存的INVITE消息提取出来，继续发往备服务器，发起并建立呼叫。如此，对用户来说无需关注主备服务器切换这个过程，这次 呼叫结果仍然是成功的，没有明显影响。此外，本发明实施例提供的终端呼叫软切换方法还可以和相关技术中的切换方式结合使用。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如***、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例的方案用户体验好，流程简单，可靠性高。

Claims (9)

  1. 一种终端呼叫软切换的方法，包括以下步骤：
    当终端向当前注册的第一服务器发出邀请INVITE消息未得到响应时，所述终端根据重传间隔时间向所述第一服务器重传所述INVITE消息；
    当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，所述终端向第二服务器发送注册消息；
    当所述终端注册至所述第二服务器后，所述终端将所述INVITE消息发送至所述第二服务器。
  2. 如权利要求1所述的终端呼叫软切换的方法，其中：所述重传间隔时间随所述重传次数依次递增。
  3. 如权利要求1所述的终端呼叫软切换的方法，其中：所述终端为会话初始协议SIP终端，所述第一服务器为SIP主服务器，所述第二服务器为SIP备服务器。
  4. 如权利要求1所述的终端呼叫软切换的方法，其中：所述终端为SIP终端，所述第一服务器为SIP备服务器，所述第二服务器为SIP主服务器。
  5. 一种终端，包括邀请INVITE消息重传模块、注册消息发送模块和INVITE消息发送模块；
    所述INVITE消息重传模块，设置为当终端向当前注册的第一服务器发出INVITE消息未得到响应时，根据重传间隔时间向所述第一服务器重传所述INVITE消息；
    所述注册消息发送模块，设置为当所述INVITE消息的重传次数大于预设值，且未得到所述第一服务器的应答时，向第二服务器发送注册消息；
    所述INVITE消息发送模块，设置为当所述终端注册至所述第二服务器后，将所述INVITE消息发送至所述第二服务器。
  6. 如权利要求5所述的终端，其中：所述重传间隔时间随所述重传次数依次递增。
  7. 如权利要求5所述的终端，其中：所述终端为会话初始协议SIP终端，所述第一服务器为SIP主服务器，所述第二服务器为SIP备服务器。
  8. 如权利要求5所述的终端，其中：所述终端为SIP终端，所述第一服务器为SIP备服务器，所述第二服务器为SIP主服务器。
  9. 一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现权利要求1-4任一项所述的方法。
PCT/CN2015/077197 2014-12-23 2015-04-22 一种终端及终端呼叫软切换的方法 WO2016101457A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/537,433 US20180027028A1 (en) 2014-12-23 2015-04-22 Terminal and Terminal Call Soft Switching Method
EP15871533.4A EP3223484A4 (en) 2014-12-23 2015-04-22 Terminal and terminal call soft switching method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410815725.6 2014-12-23
CN201410815725.6A CN105790903A (zh) 2014-12-23 2014-12-23 一种终端及终端呼叫软切换的方法

Publications (1)

Publication Number Publication Date
WO2016101457A1 true WO2016101457A1 (zh) 2016-06-30

Family

ID=56149063

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/077197 WO2016101457A1 (zh) 2014-12-23 2015-04-22 一种终端及终端呼叫软切换的方法

Country Status (4)

Country Link
US (1) US20180027028A1 (zh)
EP (1) EP3223484A4 (zh)
CN (1) CN105790903A (zh)
WO (1) WO2016101457A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634690A (zh) * 2015-06-24 2016-06-01 东莞市芯谷电子科技有限公司 一种用于增强花样机串口通讯可靠性的方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106533798B (zh) * 2016-12-15 2019-09-20 北京小米移动软件有限公司 检测方法和装置
JP6822180B2 (ja) * 2017-02-02 2021-01-27 セイコーエプソン株式会社 印刷装置、印刷装置の制御方法、及び、通信システム
CN107070950B (zh) * 2017-05-24 2021-04-20 深圳市万普拉斯科技有限公司 Ims注册控制的方法、装置和计算机可读存储介质
CN112349083B (zh) * 2020-09-29 2021-09-24 北京空间飞行器总体设计部 一种适用于野外无人值守站的多模式数据管理与通信***
CN116264598A (zh) * 2021-12-14 2023-06-16 荣耀终端有限公司 一种多屏协同的通话方法、***、终端及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002097653A1 (en) * 2001-05-30 2002-12-05 Tekelec Scalable, reliable session initiation protocol (sip) signaling routing node
CN101296511A (zh) * 2008-06-05 2008-10-29 华中科技大学 一种基于会话边缘控制设备sbc的无线异构网垂直切换控制方法
CN101854686A (zh) * 2009-03-30 2010-10-06 上海贝尔股份有限公司 一种用于减小切换VoIP呼叫时的中断时间的方法和设备
CN103685166A (zh) * 2012-09-06 2014-03-26 中兴通讯股份有限公司 起始会话协议终端切换主备服务器的方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8213295B2 (en) * 2006-09-12 2012-07-03 Qualcomm Incorporated Transaction timeout handling in communication session management
WO2009012814A1 (en) * 2007-07-23 2009-01-29 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
CN102263775B (zh) * 2010-05-31 2015-06-17 上海贝尔股份有限公司 一种本区域sip呼叫控制方法及其装置
CN101964806B (zh) * 2010-11-02 2013-05-22 深圳市共进电子股份有限公司 Sip通讯终端切换服务器的方法
US8619547B2 (en) * 2010-11-10 2013-12-31 At&T Intellectual Property I, L.P. Communication system with failover communication services
US20120124431A1 (en) * 2010-11-17 2012-05-17 Alcatel-Lucent Usa Inc. Method and system for client recovery strategy in a redundant server configuration

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002097653A1 (en) * 2001-05-30 2002-12-05 Tekelec Scalable, reliable session initiation protocol (sip) signaling routing node
CN101296511A (zh) * 2008-06-05 2008-10-29 华中科技大学 一种基于会话边缘控制设备sbc的无线异构网垂直切换控制方法
CN101854686A (zh) * 2009-03-30 2010-10-06 上海贝尔股份有限公司 一种用于减小切换VoIP呼叫时的中断时间的方法和设备
CN103685166A (zh) * 2012-09-06 2014-03-26 中兴通讯股份有限公司 起始会话协议终端切换主备服务器的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3223484A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634690A (zh) * 2015-06-24 2016-06-01 东莞市芯谷电子科技有限公司 一种用于增强花样机串口通讯可靠性的方法

Also Published As

Publication number Publication date
EP3223484A1 (en) 2017-09-27
CN105790903A (zh) 2016-07-20
EP3223484A4 (en) 2017-11-29
US20180027028A1 (en) 2018-01-25

Similar Documents

Publication Publication Date Title
WO2016101457A1 (zh) 一种终端及终端呼叫软切换的方法
US8374079B2 (en) Proxy server, communication system, communication method and program
JP2013544408A (ja) 冗長サーバ構成におけるクライアント回復戦略のための方法およびシステム
CN101513016A (zh) 通信会话管理中的交易超时处理
US8345840B2 (en) Fast detection and reliable recovery on link and server failures in a dual link telephony server architecture
JP2008547329A (ja) 無線ネットワークにおけるセッションの保持
US20140359340A1 (en) Subscriptions that indicate the presence of application servers
CN101997850B (zh) 用于ip多媒体子***的呼叫管理方法及装置
CN101964806A (zh) Sip通讯终端切换服务器的方法
WO2016062008A1 (zh) 一种容灾方法及网元、服务器、存储介质
JP2014504392A (ja) ネットワーク要素のサービス回復のための方法およびシステム
CN103685166A (zh) 起始会话协议终端切换主备服务器的方法及装置
CN101702712B (zh) 一种探测技术与语音呼叫备份联动方法及装置
US10841344B1 (en) Methods, systems and apparatus for efficient handling of registrations of end devices
WO2021047513A1 (zh) 一种视频会议通信方法、装置以及计算机可读存储介质
US8451828B2 (en) Registering an internet protocol phone in a dual-link architecture
JP2007243814A (ja) Ｉｐ電話システム
WO2012071882A1 (zh) 会话检测方法、装置及会话初始协议服务器
CN104811426B (zh) 用户代理客户端发送注册请求的方法及用户代理客户端
US9319266B2 (en) Method and apparatus for managing diameter routing
CN113595765A (zh) 一种VoIP终端注册业务的故障转移方法及装置
CN108880882B (zh) 一种基于健康检查改进机制的gslb处理方法
JP2008005076A (ja) ネットワークシステム、ネットワーク端末及びそれらに用いるネットワーク機器切替え方法
CN110602339A (zh) 一种基于语音网关的故障检测方法、***及存储介质
JP2014007617A (ja) 呼制御サーバ、通信システム、および呼制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15871533

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15537433

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015871533

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE