WO2017097031A1 - 接口恢复方法、移动交换服务器、移动性管理实体及系统 - Google Patents

接口恢复方法、移动交换服务器、移动性管理实体及系统 Download PDF

Info

Publication number
WO2017097031A1
WO2017097031A1 PCT/CN2016/101821 CN2016101821W WO2017097031A1 WO 2017097031 A1 WO2017097031 A1 WO 2017097031A1 CN 2016101821 W CN2016101821 W CN 2016101821W WO 2017097031 A1 WO2017097031 A1 WO 2017097031A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile switching
switching server
mobility management
management entity
failure
Prior art date
Application number
PCT/CN2016/101821
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 中兴通讯股份有限公司
Publication of WO2017097031A1 publication Critical patent/WO2017097031A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • the present disclosure relates to the field of communication technologies, for example, to an interface recovery method, a mobile switching server, a mobility management entity, and a system.
  • the IP Multimedia Subsystem (IMS) network is a multimedia service form developed by the 3rd Generation Partnership Project (3GPP) organization to adapt to the evolving telecommunications technology and market demand.
  • 3GPP 3rd Generation Partnership Project
  • the IP bearer is used as the bearer channel for IMS network control signaling and media transmission.
  • the IMS uses the Session Initiation Protocol (SIP) protocol as the control signaling. It has the characteristics of separate bearer control and access independence. It has the ability to provide unified multimedia services for users under different networks. It is the evolution direction of the current telecommunication network.
  • SIP Session Initiation Protocol
  • It has the characteristics of separate bearer control and access independence. It has the ability to provide unified multimedia services for users under different networks. It is the evolution direction of the current telecommunication network.
  • . 1 is a structure of an IMS network, in which
  • UE User Equipment
  • the Serving Call Session Control Function is the core of the IMS network. It is responsible for handling signaling interactions during the multimedia call session. It cooperates with other network entities to control SIP sessions and conducts service negotiation and resources. Assignment, etc.
  • the application server is a logical entity inside the IMS, which provides service deployment and logic control functions for the IMS service.
  • the Home Subscriber Server (HSS) is the primary subscriber database that supports the IMS network entity for handling calls/sessions.
  • the UE under the IMS network may switch the ongoing conversation to the Circuit Switch (CS) network due to network coverage, and the switching service is provided by the Mobile Switching Center (MSC) under the circuit switched network. .
  • This process is called Single Radio Voice Call Continuity (SRVCC).
  • Figure 2 is a network structure diagram for performing such switching, wherein
  • the first user equipment 201 is a user equipment in which handover occurs.
  • the Mobile Switch Center Server is the switching server where the first user equipment is switched to the circuit domain.
  • the MSC Server provides a handover service for the first user equipment and provides call control functions after the handover.
  • Multiple mobile switching servers in the network can form a pool domain to provide services for the same geographical area and backup each other.
  • the Mobility Management Entity is a management network element of the first user equipment in the packet switched domain.
  • the first user equipment resides under the mobility management entity before the handover, and is connected to the S-CSCF through an IP (Internet Protocol) connection provided by the mobility management entity.
  • IP Internet Protocol
  • the interface between the mobility management entity and the mobile switching server is the Sv interface.
  • the mobility management entity sends a handover request to the MSC through the Sv interface, and interacts with the MSC to complete the handover process.
  • the first user equipment service call session control function 204 is the S-CSCF of the first user equipment.
  • the Service Centralization and Continuity Application Server is an Application Server (AS) that provides call continuity services in the IMS network.
  • AS Application Server
  • the SCC AS is responsible for implementing the interconnection between the switched circuit domain session branch and the call far end.
  • the SCC AS can be combined with the supplementary service AS that provides the forwarding service logic for the UE, or can be set separately.
  • the second user device 206 is the far end of the conversation with the first user device.
  • FIG. 3 is a process of the UE performing the handover, and the process includes:
  • the second user equipment calls the first user equipment and is connected, and the first user equipment and the E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) perform handover decision between the user equipment and the E-UTRAN (Evolved UMTS Terrestrial Radio Access Network). Decided to switch to a circuit switched network;
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • the mobility management entity selects a mobile switching server according to the location of the first user equipment, and sends a handover request message to the mobile switching server through the Sv interface.
  • the mobile switching server After preparing the handover, the mobile switching server returns a handover response to the mobility management entity.
  • S304 The mobility management entity sends a handover command to the first user equipment, where the first user equipment starts an access process to the circuit domain.
  • the mobile switching server sends an INVITE message to the service set and the continuous application server, requesting to establish a media connection between the mobile switching server and the second user equipment.
  • the second user equipment returns 200 OK and carries his media information.
  • the first user equipment sends a handover complete message to the mobile switching server.
  • the mobile switching server notifies the mobility management entity that the current handover has been completed.
  • the service aggregation and the message between the continuous application server and the second user equipment need to be forwarded by the S-CSCF.
  • the mobility management entity if the mobile switching server fails, the mobility management entity will not receive the response message after sending the handover request to the mobile switching server; at this time, the mobility management entity sends an Echo (answer) message to the mobile switching server, if The mobile switching server does not respond and the mobility management entity marks the mobile switching server as a failure.
  • the mobility management entity detects whether the mobile switching server is available according to a certain period; this period is often long, and it takes a long time for the mobility management entity to detect the mobile.
  • the exchange server is already available, and the switchover during this time will fail due to the failure of the mobile switching server, so it is necessary to optimize;
  • the detection method is that the mobility management entity first sends a detection message to the mobile switching server, and moves for the detection message.
  • the switching server returns a detection response message to the mobility management entity, and the mobility management entity analyzes whether the mobile switching server has recovered from the failure based on the detection response message.
  • the mobile switching servers are in a load sharing relationship and a mutual backup relationship; when a mobile switching server fails, the mobility management entity detects the mobile switching server.
  • the Sv interface is unavailable, and subsequent switching loads will be handled by other mobile switching servers in the pool domain. After the faulty mobile switching server recovers, if the mobility management entity cannot detect the faulty mobile switching server in time, the other mobile switching servers will bear additional load for a long time and reduce the stability of the system.
  • the present disclosure provides an interface recovery method, a mobile switching server, a mobility management entity, and a system, which solves the problem in the related art that the mobility management entity cannot know in time whether the failed mobile switching server has recovered from the failure, thereby causing system services. Long interruption time, poor network service quality, and poor system stability.
  • the present disclosure provides an interface recovery method, including: detecting whether a mobile switching server recovers from a failure; and transmitting a notification message to a mobility management entity to notify the mobile when the mobile switching server detects that it has recovered from a failure; The exchange server has recovered from the failure.
  • the mobility management entity establishes a connection with the mobile switching server by using an Sv interface.
  • the present disclosure provides a non-transitory computer storage medium storing computer executable instructions arranged to perform any of the interface recovery methods described above.
  • the present disclosure provides an interface recovery method, including: a mobility management entity receives a notification message sent by a mobile switching server; and the mobility management entity updates a flag of the mobile switching server from a fault flag to a normal flag according to the notification message. .
  • the method further includes: sending a response message for the notification message to the mobile switching server.
  • the method further includes: when the mobility management entity has a new handover task, selecting to switch to the mobile The server sends a switch instruction.
  • the present disclosure provides a non-transitory computer storage medium storing computer executable instructions arranged to perform the interface recovery method of any of the above claims.
  • the present disclosure provides a mobile switching server including a detection module and a first processing module, the detection module configured to detect whether a mobile switching server recovers from a failure; the first processing module is configured to when the mobile switching server is faulty After the recovery, a notification message is sent to the mobility management entity to notify the mobile switching server that it has recovered from the failure.
  • the present disclosure provides a mobility management entity, including a receiving module and a marking module, the receiving module configured to receive a notification message sent by a mobile switching server; the marking module configured to: according to the notification message, the mobile switching server The tag is updated from a fault flag to a normal tag.
  • the method further includes: a response message sending module, where the response message sending module is configured to send, by the marking module, the mark of the mobile switching server to a normal mark by the fault flag, and send the target to the mobile switching server A response message to the notification message.
  • a response message sending module configured to send, by the marking module, the mark of the mobile switching server to a normal mark by the fault flag, and send the target to the mobile switching server A response message to the notification message.
  • the method further includes: a switching instruction sending module, where the switching instruction sending module is configured to: after the marking module updates the marking of the mobile switching server from a fault flag to a normal flag, when a new switching task is selected, A handover instruction is sent to the mobile switching server.
  • a switching instruction sending module configured to: after the marking module updates the marking of the mobile switching server from a fault flag to a normal flag, when a new switching task is selected, A handover instruction is sent to the mobile switching server.
  • the present disclosure provides a communication system including the above-described mobile switching server and a mobility management entity that detects whether it recovers from a failure, and transmits when the mobile switching server detects that it has recovered from a failure. Notifying the mobility management entity that the mobile switching server has recovered from the failure; after receiving the notification message, the mobility management entity updates the marking of the mobile switching server from a fault flag to a normal mark.
  • the interface recovery method provided by the present disclosure, the mobile switching server, the mobility management entity, and the system detect whether the user recovers from the failure through the mobile switching server, and sends a notification when the mobile switching server detects that it has recovered from the failure.
  • the information is sent to the mobility management entity to notify the mobility management entity that the mobile switching server has recovered from the failure; after receiving the notification information, the mobility management entity updates the label of the mobile switching server from the fault flag to the normal flag according to the notification message.
  • the mobility management entity can be actively notified that the mobile switching server has recovered from the fault, so that the mobility management entity can know in time that the faulty mobile switching server has failed.
  • 1 is a schematic diagram of a network structure of an IMS
  • FIG. 2 is a schematic diagram of a network structure of SRVCC handover
  • 3 is a schematic flow chart of SRVCC handover
  • FIG. 5 is a flowchart of another interface recovery method in Embodiment 1 of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a mobile switching server according to Embodiment 2 of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a mobility management entity according to Embodiment 2 of the present disclosure.
  • FIG. 8 is another schematic structural diagram of the mobility management entity in FIG. 7;
  • FIG. 9 is another schematic structural diagram of the mobility management entity in FIG. 7;
  • FIG. 10 is a flowchart of a process for recovering a mobile switching server from a fault when the mobile switching server is in a non-pool domain network according to Embodiment 3 of the present disclosure
  • FIG. 11 is a flowchart of a process for recovering a mobile switching server from a fault when the mobile switching server is in a pool domain network according to Embodiment 4 of the present disclosure
  • FIG. 12 is a structural block diagram of an electronic device according to Embodiment 6 of the present disclosure.
  • FIG. 13 is a structural block diagram of an electronic device according to Embodiment 7 of the present disclosure.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • This embodiment provides an interface recovery method.
  • FIG. 4 including:
  • S420 Send notification information to the mobility management entity to notify the mobile switching server that the recovery has been recovered from the failure.
  • the mobile switching server detects whether it has recovered from the fault, and when detecting that it has recovered from the fault, in order to enable the mobility management entity to know in time that the mobile switching server has recovered from the fault, so as to start to bear the corresponding as soon as possible
  • the switching operation the mobile switching server actively sends notification information to the mobility management entity, notifying the mobility management entity that the mobile switching server has recovered from the failure.
  • the mobility management entity may be a mobility management entity that establishes a connection with the mobile switching server through the Sv interface; optionally, the notification information may be an Echo message, the Echo message including some information related to the Sv interface.
  • the detection may be performed once every second or once every certain period of time, and the detection process may be set as needed.
  • the embodiment further provides a non-transitory computer storage medium storing computer executable instructions, the computer executable instructions being configured to perform the interface recovery method.
  • This embodiment further provides an interface recovery method.
  • FIG. 5 including:
  • the mobility management entity receives the notification message sent by the mobile switching server.
  • the mobility management entity updates the label of the mobile switching server from a fault flag to a normal flag according to the notification message.
  • the mobility management entity marks that the mobile switching server that establishes the connection with the mobility management entity through the Sv interface has recovered from the failure, that is, the marking of the mobile switching server is The fault flag is updated to a normal flag.
  • the mobility management entity updates the label of the mobile switching server from the fault flag to the normal flag. Also included is a response message to the mobile exchange server for the notification message. Then when the mobility management entity has a new handover task, choose to send a handover to the mobile switching server.
  • the mobile switching server is in a non-pool domain network, directly sending a handover instruction to the mobile switching server, so that the mobile switching server starts a corresponding handover operation; if the mobile switching server is in the pool domain In the networking, the mobile switching server that has just recovered from the fault can be preferentially selected, and the switching instruction is preferentially sent to the mobile switching server, so that the mobile switching server performs the corresponding switching operation.
  • the embodiment further provides a non-transitory computer storage medium storing computer executable instructions, the computer executable instructions being configured to perform the interface recovery method.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the mobile switching server includes a detecting module 601 and a first processing module 602.
  • the detecting module 601 is configured to detect whether the mobile switching server recovers from a fault.
  • a processing module 602 is configured to send notification information to the mobility management entity to notify the mobile switching server that the mobile switching server has recovered from the failure after the mobile switching server recovers from the failure.
  • the mobile switching server detects, by the detecting module 601, whether it has recovered from the fault, and when detecting that it has recovered from the fault, in order to enable the mobility management entity to know in time that the mobile switching server has recovered from the fault, so that As soon as possible, the corresponding switching operation is started, and the mobile switching server actively sends the notification information to the mobility management entity through the first processing module 602 to notify the mobility management entity that the mobile switching server has recovered from the failure.
  • the mobility management entity may be a mobility management entity that establishes a connection with the mobile switching server through the Sv interface; optionally, the notification information may be an Echo message, the Echo message including some information related to the Sv interface.
  • the detection may be performed once every second, or once every certain period of time, and the detection process may be set as needed.
  • This embodiment provides a mobility management entity.
  • the receiving module 701 and the marking module 702 are configured.
  • the receiving module 701 is configured to receive notification information sent by the mobile switching server.
  • the marking module 702 is configured to notify according to the notification.
  • the message updates the tag of the mobile switching server from a fault tag to a normal tag.
  • the receiving module 701 after receiving the notification information sent by the mobile switching server, notifies The tagging module 702 marks that the mobile switching server establishing a connection with the mobility management entity through the Sv interface has recovered from the failure according to the notification information, ie, the tag of the mobile switching server is updated from the failure flag to the normal flag.
  • the mobile switching server further includes a response message sending module 703, and the response message sending module 703 is configured to: after the tagging module 702 updates the tag of the mobile switching server from the fault flag to the normal tag, to the mobile switch. The server sends a response message to the notification message notifying the mobile switching server that the mobility management entity has received the notification information and that the mobile switching server's flag has been updated to normal.
  • the mobile switching server further includes a switching instruction sending module 704, and the switching instruction sending module 704 is configured to: after the marking module 702 updates the marking of the mobile switching server from the fault flag to the normal flag, there is a new When the task is switched, the switching instruction is sent to the mobile switching server.
  • the switching instruction is directly sent to the mobile switching server, so that the mobile switching server starts.
  • the mobile switching server is in the pool domain networking, the mobile switching server that has just recovered from the fault may be preferentially selected, and the switching instruction is preferentially sent to the mobile switching server, so that the mobile switching server performs the corresponding switching operation. .
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the mobility switching server that has recovered from the fault finds a mobility management entity that has an Sv interface, and sends notification information to the mobility management entities;
  • the mobility management entity After receiving the notification information, the mobility management entity returns a response message for the notification information to the mobile switching server, and marks that the mobile switching server that sends the notification information has recovered from the failure;
  • S1004 The first user equipment and the second user equipment residing on the mobility management entity establish an IMS conversation, and need to perform handover, and perform a handover decision, and the mobility management entity sends a handover request to the mobile switching server.
  • the mobile switching server After the handover preparation is performed, the mobile switching server returns a handover response to the mobility management entity.
  • S1006 The mobility management entity sends a handover command to the first user equipment, where the first user equipment starts an access process to the circuit domain.
  • the mobile switching server sends an INVITE message to the service set and the continuous application service. Server, requesting to establish a media connection between the mobile switching server and the second user equipment;
  • the second user equipment returns 200 OK, and carries media information of the second user equipment.
  • S1010 The service centralized and continuous application server forwards 200 OK to the mobile switching server;
  • the mobile switching server notifies the mobility management entity that the current handover has been completed.
  • the foregoing notification information may be an Echo message, where the Echo message includes some information related to the Sv interface, and the returned response message may be an Echo response; the return response message may enable the mobile switching server to know that the mobility management entity has received Notification information.
  • the service centralized and the message between the continuous application server and the second user equipment can be forwarded by the S-CSCF.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the mobility switching server that has recovered from the fault finds a mobility management entity that has an Sv interface, and sends notification information to the mobility management entities;
  • the mobility management entity After receiving the notification information, the mobility management entity returns a response message for the notification information to the mobile switching server, and marks that the mobile switching server that sends the notification information has recovered from the failure;
  • S1104 The first user equipment and the second user equipment residing on the mobility management entity establish an IMS session, and need to perform handover, and perform a handover decision.
  • the mobility management entity selects the mobile switching server according to the principle of load sharing and sends the mobile switching server preferentially. Switching request;
  • S1106 The mobility management entity sends a handover command to the first user equipment, where the first user equipment starts an access process to the circuit domain.
  • the mobile switching server sends an INVITE message to the service set and the continuous application server, requesting to establish a media connection between the mobile switching server and the second user equipment.
  • S1109 The second user equipment returns 200 OK, and carries media information of the second user equipment.
  • S1110 The service centralized and continuous application server forwards 200 OK to the mobile switching server;
  • S1112 The mobile switching server notifies the mobility management entity that the current handover has been completed.
  • the foregoing notification information may be an Echo message, where the Echo message includes some information related to the Sv interface, and the returned response message may be an Echo response; returning the response message may enable the mobile switching server to know that the mobility management entity has received To notification information.
  • the service centralized and the message between the continuous application server and the second user equipment can be forwarded by the S-CSCF.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the embodiment provides a communication system, which includes the mobile switching server in the foregoing embodiment and the mobility management entity described in the foregoing embodiment;
  • the mobile switching server detects whether it recovers from a failure
  • the mobility management entity After receiving the notification message, the mobility management entity updates the label of the mobile switching server from a fault flag to a normal flag.
  • FIG. 12 is a structural block diagram of an electronic device according to Embodiment 6 of the present disclosure.
  • the electronic device provided by the embodiment of the present disclosure is configured on the mobile switching server side, and the electronic device may include a processor 1201 and a memory 1203, and may further include a communication interface 1202 and a bus 1204.
  • the processor 1201, the communication interface 1202, and the memory 1203 can complete communication with each other through the bus 1204.
  • Communication interface 1202 can be used for information transmission.
  • the processor 1201 can call the logic instructions in the memory 1203 to perform the interface recovery method of the above embodiment.
  • the logic instructions in the memory 1203 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) Apparatus, etc.) performing the methods of the various embodiments of the present disclosure All or part of the steps.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • a medium that can store program code, or a transitory storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • FIG. 13 is a structural block diagram of an electronic device according to Embodiment 7 of the present disclosure.
  • the electronic device provided by the embodiment of the present disclosure is configured on the mobility management entity side, and the electronic device may include a processor 1301 and a memory 1303, and may further include a communication interface 1302 and a bus 1304.
  • the processor 1301, the communication interface 1302, and the memory 1303 can complete communication with each other through the bus 1304.
  • Communication interface 1302 can be used for information transfer.
  • the processor 1301 can call the logic instructions in the memory 1303 to perform the interface recovery method of the above embodiment.
  • the logic instructions in the memory 1303 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in various embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • a medium that can store program code, or a transitory storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • the features in the above embodiments may be combined arbitrarily without conflict; the above multiple modules or steps of the present disclosure may be implemented by a general-purpose computing device, which may be concentrated in a single On a computing device, or distributed over a network of computing devices, optionally, they can be implemented in program code executable by the computing device so that they can be stored on a non-transitory storage medium (ROM/ The RAM, the disk, the optical disk are executed by the computing device, and in some cases, the steps shown or described may be performed in an order different from that herein, or they may be separately fabricated into a plurality of integrated circuit modules, or Implementing multiple modules or steps in them as a single integrated circuit module.
  • ROM non-transitory storage medium
  • the embodiment of the present disclosure enables the mobility management entity to know in time that the mobile switching server that has failed has recovered from the failure, and then sends a handover instruction to the mobile switching server as needed, so that the Sv interface can be put into operation faster, even if the mobile exchange
  • the server can bear the load of the Sv interface more quickly, reduce the time of system service interruption, improve the network service quality, ensure the stability of the system, and the invention has little change and influence on the existing system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种接口恢复方法、移动交换服务器、移动性管理实体及系统，移动交换服务器检测自身是否从故障中恢复，当所述移动交换服务器检测到自身已从故障中恢复时，则发送通知信息给移动性管理实体，通知移动性管理实体所述移动交换服务器已从故障中恢复；移动性管理实体接收到通知信息后，根据通知消息将移动交换服务器的标记由故障标记更新为正常标记。

Description

接口恢复方法、移动交换服务器、移动性管理实体及系统 技术领域
本公开涉及通信技术领域，例如涉及一种接口恢复方法、移动交换服务器、移动性管理实体及系统。
背景技术
IP多媒体子系统(IP Multimedia Subsystem，IMS)网络是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)组织为适应不断发展的电信技术和市场需求，所发展出来的一种多媒体业务形式，它构建在IP网络之上，使用IP承载作为IMS网络控制信令和媒体传输的承载通道。IMS使用会话初始化协议(Session Initiation Protocol，SIP)协议作为控制信令，具备承载控制分离，接入无关等特点，具备为不同网络下的用户提供统一多媒体业务的能力，是目前电信网络的演化方向。图1是IMS网络的结构，其中，
用户设备101(User Equipment，UE)是用户所使用的移动终端。
服务呼叫会话控制功能102(Serving Call Session Control Function，S-CSCF)是IMS网络的核心，负责处理多媒体呼叫会话过程中的信令交互，与其它网络实体配合控制SIP会话，并进行业务协商和资源分配等。
应用服务器103(Application Server，AS)是IMS内部的逻辑实体，为IMS业务提供业务部署和逻辑控制功能。
归属用户服务器104(Home Subscriber Server，HSS)是支持用于处理调用/会话的IMS网络实体的主要用户数据库。
在IMS网络下的UE，由于网络覆盖的原因，可能将正在进行的对话切换到电路交换(Circuit Switch，CS)网络，由电路交换网络下的移动交换中心(Mobile Switching Center，MSC)提供交换服务。这一过程称为单频语音连续性切换(Single Radio Voice Call Continuity，SRVCC)。图2是进行这种切换的网络结构图，其中
第一用户设备201是发生切换的用户设备。
移动交换服务器202(Mobile Switch Center Server，MSC Server)是第一用户设备切换到电路域后所在的交换服务器。该MSC Server为第一用户设备提供切换服务，并在切换后提供呼叫控制功能。网络中的多个移动交换服务器，可以组成池域，为同一个地理区域提供服务，并互为备份。
移动性管理实体203(Mobility Management Entity，MME)是第一用户设备在分组交换域的管理网元。第一用户设备在切换前，驻留在移动性管理实体下，并通过移动性管理实体提供的IP(Internet Protocol，网络协议)连接，连接到S-CSCF。移动性管理实体和移动交换服务器之间的接口是Sv接口。当需要切换到电路域时，移动性管理实体通过Sv接口发送切换请求到MSC，和MSC交互完成切换流程。
第一用户设备服务呼叫会话控制功能204是第一用户设备的S-CSCF。
业务集中及连续应用服务器205(Service Centralization and Continuity Application Server，SCC AS)是IMS网络中提供呼叫连续性服务的应用服务器(Application Server，AS)。在切换过程中，SCC AS负责实现切换后的电路域会话分支和呼叫远端之间互联。SCC AS可以和为UE提供前转业务逻辑的补充业务AS合设，也可以分开设置。
第二用户设备206是和第一用户设备对话的远端。
图3是UE进行该切换的流程，该流程包括：
S301，第二用户设备呼叫第一用户设备并已接通，第一用户设备和E-UTRAN(Evolved UMTS Terrestrial Radio Access Network，演进的通用移动通信系统陆地无线接入网)之间进行切换决策，决定切换到电路交换网络；
S302，移动性管理实体根据第一用户设备所在位置选择一个移动交换服务器，通过Sv接口发送切换请求消息到移动交换服务器；
S303，移动交换服务器在进行切换准备后，返回切换应答到移动性管理实体；
S304，移动性管理实体发送切换命令到第一用户设备，第一用户设备开始到电路域的接入过程；
S305，同时，移动交换服务器发送INVITE(邀请)消息到业务集中及连续应用服务器，请求建立移动交换服务器到第二用户设备之间的媒体连接；
S306，业务集中及连续应用服务器收到后，发送Update(更新)消息到第二用户设备；
S307，第二用户设备返回200OK，携带他的媒体信息；
S308，业务集中及连续应用服务器转发200OK到移动交换服务器；
S309，第一用户设备在电路域接入完成后，发送切换完成消息到移动交换服务器；
S310，移动交换服务器通知移动性管理实体当前切换已完成。
其中，业务集中及连续应用服务器和第二用户设备之间的消息需要经过S-CSCF的转发。上述过程中，如果移动交换服务器发生故障，移动性管理实体发送切换请求到移动交换服务器后将收不到应答消息；此时移动性管理实体会发送Echo(应答)消息到该移动交换服务器，若移动交换服务器没有反应，则移动性管理实体将该移动交换服务器标记为故障。然而，当故障移动交换服务器恢复后，按照现有的机制，移动性管理实体按照一定周期检测移动交换服务器是否可用；这个周期往往较长，导致需要较长时间移动性管理实体才会检测到移动交换服务器已经可用，而这段时间的切换将会因为移动交换服务器故障而失败，因此有必要进行优化；检测方法为移动性管理实体先向移动交换服务器发送一个检测消息，针对该检测消息，移动交换服务器向移动性管理实体返回一个检测应答消息，移动性管理实体根据该检测应答消息分析移动交换服务器是否已从故障中恢复。类似的，在多个移动交换服务器组成池域的组网中，移动交换服务器之间是负荷分担和互为备份的关系；当一个移动交换服务器故障，移动性管理实体检测到该移动交换服务器的Sv接口不可用，后续的切换负荷将由池域内的其他移动交换服务器处理。故障移动交换服务器恢复后，如果移动性管理实体不能及时检测到所述故障移动交换服务器已恢复，其他移动交换服务器将长时间承担额外负荷，降低系统的稳定性。
发明内容
本公开提供了一种接口恢复方法、移动交换服务器、移动性管理实体及系统，解决了相关技术中移动性管理实体不能及时知道发生故障的移动交换服务器是否恢复已从故障中恢复，从而造成系统业务中断时间长，网络服务质量差，系统稳定性差的问题。
本公开提供一种接口恢复方法，包括：检测移动交换服务器是否从故障中恢复；当所述移动交换服务器检测到自身已从故障中恢复时，发送通知消息给移动性管理实体，通知所述移动交换服务器已从故障中恢复。
可选的，所述移动性管理实体通过Sv接口与所述移动交换服务器建立连接。
本公开提供一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一项接口恢复方法。
本公开提供一种接口恢复方法，包括：移动性管理实体接收移动交换服务器发送的通知消息；所述移动性管理实体根据所述通知消息将所述移动交换服务器的标记由故障标记更新为正常标记。
可选的，所述移动性管理实体将所述移动交换服务器的标记由故障标记更新为正常标记后，还包括：向所述移动交换服务器发送针对所述通知消息的应答消息。
可选的，所述移动性管理实体将所述移动交换服务器的标记由故障标记更新为正常标记后，还包括：所述移动性管理实体在有新的切换任务时，选择向所述移动交换服务器发送切换指令。
本公开提供一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求上述任一项接口恢复方法。
本公开提供一种移动交换服务器，包括检测模块和第一处理模块，所述检测模块设置为检测移动交换服务器是否从故障中恢复；所述第一处理模块设置为当所述移动交换服务器从故障中恢复后，发送通知消息给移动性管理实体，通知所述移动交换服务器已从故障中恢复。
本公开提供一种移动性管理实体，包括接收模块和标记模块，所述接收模块设置为接收移动交换服务器发送的通知消息；所述标记模块设置为根据所述通知消息将所述移动交换服务器的标记由故障标记更新为正常标记。
可选的，还包括：应答消息发送模块，所述应答消息发送模块设置为所述标记模块将所述移动交换服务器的标记由故障标记更新为正常标记后，向所述移动交换服务器发送针对所述通知消息的应答消息。
可选的，还包括：切换指令发送模块，所述切换指令发送模块设置为所述标记模块将所述移动交换服务器的标记由故障标记更新为正常标记后，在有新的切换任务时，选择向所述移动交换服务器发送切换指令。
本公开提供一种通信系统，包括上述移动交换服务器和移动性管理实体，所述移动交换服务器检测自身是否从故障中恢复，当所述移动交换服务器检测到自身已从故障中恢复时，则发送通知消息给所述移动性管理实体，通知所述移动交换服务器已从故障中恢复；所述移动性管理实体接收到所述通知消息后，将所述移动交换服务器的标记由故障标记更新为正常标记。
本公开提供的接口恢复方法、移动交换服务器、移动性管理实体及系统，通过移动交换服务器检测自身是否从故障中恢复，当所述移动交换服务器检测到自身已从故障中恢复时，则发送通知信息给移动性管理实体，通知移动性管理实体所述移动交换服务器已从故障中恢复；移动性管理实体接收到通知信息后，根据通知消息将移动交换服务器的标记由故障标记更新为正常标记。使得发生故障的移动交换服务器从故障中恢复后，能主动地通知移动性管理实体所述移动交换服务器已从故障中恢复，使移动性管理实体能及时知道发生故障的该移动交换服务器已从故障中恢复，然后根据需要发送切换指令给该移动交换服务器，从而使Sv接口能够更快的投入，即使移动交换服务器可以更快的承担Sv接口的负荷，减少系统业务中断的时间，提高网络服务质量，保证系统的稳定性，且本公开对已有系统的改动和影响很小。
附图概述
图1为IMS的网络结构示意图；
图2为SRVCC切换的网络结构示意图；
图3是SRVCC切换的流程示意图；
图4为本公开实施例一的接口恢复方法流程图；
图5为本公开实施例一中的另一接口恢复方法流程图；
图6为本公开实施例二中的移动交换服务器的结构示意图；
图7为本公开实施例二中的移动性管理实体得结构示意图；
图8为图7中的移动性管理实体的另一结构示意图；
图9为图7中的移动性管理实体的另一结构示意图；
图10为本公开实施例三中，当移动交换服务器处于非池域组网中时，移动交换服务器从故障中恢复的处理流程图；
图11为本公开实施例四中，当移动交换服务器处于池域组网中时，移动交换服务器从故障中恢复的处理流程图；
图12是本公开实施例六提供的电子设备的结构框图；
图13是本公开实施例七提供的电子设备的结构框图。
具体实施方式
下面通过具体实施方式结合附图对本公开作详细说明。
实施例一：
本实施例提供一种接口恢复方法，可选的，请参见图4，包括：
S410，检测移动交换服务器是否从故障中恢复，当所述移动交换服务器检测到自身已从故障中恢复时，转到S420。
S420，发送通知信息给移动性管理实体，通知所述移动交换服务器已从故障中恢复。
可选的，移动交换服务器检测自身是否已从故障中恢复，当检测到自身已从故障中恢复后，为了使移动性管理实体及时知道该移动交换服务器已从故障中恢复，以便尽早开始承担相应的切换操作，移动交换服务器主动发送通知信息给移动性管理实体，通知移动性管理实体该移动交换服务器已从故障中恢复。该移动性管理实体可以是通过Sv接口与移动交换服务器建立连接的移动性管理实体；可选地，通知信息可以是Echo消息，该Echo消息包括与该Sv接口相关的一些信息。
另外，若检测得到移动交换服务器还未从故障中恢复，则说明该移动交换服务器还不能进行相应的切换操作，则继续进行检测操作，检测该移动交换服务器是否从故障中恢复。为了及时知道该移动交换服务器是否已从故障中恢复，该检测可以是每秒进行一次，也可以是每隔一定的时间段进行一次，检测过程可根据需要进行设置。
本实施例还提供一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述接口恢复方法。
本实施例还提供一种接口恢复方法，可选的，请参见图5，包括：
S510，移动性管理实体接收移动交换服务器发送的通知消息。
S520，所述移动性管理实体根据所述通知消息将所述移动交换服务器的标记由故障标记更新为正常标记。
可选的，移动性管理实体接收到移动交换服务器发送来的通知信息后，标记与该移动性管理实体通过Sv接口建立连接的移动交换服务器已从故障中恢复，即将该移动交换服务器的标记由故障标记更新为正常标记。可选地，为了使移动交换服务器知道移动性管理实体已收到通知信息且该移动交换服务器的标记已更新为正常，移动性管理实体将移动交换服务器的标记由故障标记更新为正常标记后，还包括向移动交换服务器发送针对所述通知消息的应答消息。然后当移动性管理实体在有新的切换任务时，选择向移动交换服务器发送切换 指令；可选的，若该移动交换服务器处于非池域组网中，则直接发送切换指令给该移动交换服务器，使该移动交换服务器开始进行相应的切换操作；若该移动交换服务器处于池域组网中，则可以优先选择刚从故障中恢复的该移动交换服务器，将切换指令优先发送给移动交换服务器，使移动交换服务器进行相应切换操作。
本实施例还提供一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述接口恢复方法。
实施例二：
本实施例提供一种移动交换服务器，可选的，请参见图6，该移动交换服务器包括检测模块601和第一处理模块602，检测模块601设置为检测移动交换服务器是否从故障中恢复；第一处理模块602设置为当移动交换服务器从故障中恢复后，发送通知信息给移动性管理实体，通知移动交换服务器已从故障中恢复。
可选的，移动交换服务器通过检测模块601检测自身是否已从故障中恢复，当检测到自身已从故障中恢复后，为了使移动性管理实体及时知道该移动交换服务器已从故障中恢复，以便尽早开始承担相应的切换操作，移动交换服务器通过第一处理模块602主动发送通知信息给移动性管理实体，通知移动性管理实体该移动交换服务器已从故障中恢复。该移动性管理实体可以是通过Sv接口与移动交换服务器建立连接的移动性管理实体；可选地，通知信息可以是Echo消息，该Echo消息包括与该Sv接口相关的一些信息。
另外，若检测得到移动交换服务器还未从故障中恢复，则说明该移动交换服务器还不能进行相应的切换操作，则继续进行检测操作，检测该移动交换服务器是否从故障中恢复，需要理解的是，为了及时知道该移动交换服务器是否已从故障中恢复，该检测可以是每秒进行一次，也可以是每隔一定的时间段进行一次，检测过程可根据需要进行设置。
本实施例提供一种移动性管理实体，可选的，请参见图7，包括接收模块701和标记模块702，接收模块701设置为接收移动交换服务器发送的通知信息；标记模块702设置为根据通知消息将移动交换服务器的标记由故障标记更新为正常标记。
可选的，接收模块701接收到移动交换服务器发送来的通知信息后，通知 标记模块702根据通知信息标记与该移动性管理实体通过Sv接口建立连接的移动交换服务器已从故障中恢复，即将该移动交换服务器的标记由故障标记更新为正常标记。可选地，请参见图8，该移动交换服务器还包括应答消息发送模块703，该应答消息发送模块703设置为标记模块702将移动交换服务器的标记由故障标记更新为正常标记后，向移动交换服务器发送针对所述通知消息的应答消息，通知移动交换服务器该移动性管理实体已收到通知信息且该移动交换服务器的标记已更新为正常。另外的，请参见图9，该移动交换服务器还包括切换指令发送模块704，该切换指令发送模块704设置为标记模块702将移动交换服务器的标记由故障标记更新为正常标记后，在有新的切换任务时，选择向所述移动交换服务器发送切换指令；可选的，若该移动交换服务器处于非池域组网中，则直接发送切换指令给该移动交换服务器，使该移动交换服务器开始进行相应的切换操作；若该移动交换服务器处于池域组网中，则可以优先选择刚从故障中恢复的该移动交换服务器，将切换指令优先发送给移动交换服务器，使移动交换服务器进行相应切换操作。
实施例三：
参考图10，本实施例中对处于非池域组网的移动交换服务器从故障中恢复的处理流程做详细说明。
S1001，检测移动交换服务器是否从故障中恢复；当所述移动交换服务器检测到自身已从故障中恢复时，转到S1002；
S1002，已从故障中恢复的移动交换服务器找到和自己有Sv接口的移动性管理实体，发送通知信息到这些移动性管理实体；
S1003，移动性管理实体收到通知信息后，返回针对通知信息的应答消息给移动交换服务器，并标记发送通知信息的移动交换服务器已从故障中恢复；
S1004，在移动性管理实体上驻留的第一用户设备和第二用户设备建立IMS对话，并且需要切换，进行切换决策，移动性管理实体发送切换请求到移动交换服务器；
S1005，移动交换服务器在进行切换准备后，返回切换应答到移动性管理实体；
S1006，移动性管理实体发送切换命令到第一用户设备，第一用户设备开始进行到电路域的接入过程；
S1007，同时，移动交换服务器发送INVITE消息到业务集中及连续应用服 务器，请求建立移动交换服务器到第二用户设备之间的媒体连接；
S1008，业务集中及连续应用服务器收到后，发送Update消息到第二用户设备；
S1009，第二用户设备返回200OK，携带第二用户设备的媒体信息；
S1010，业务集中及连续应用服务器转发200OK到移动交换服务器；
S1011，第一用户设备在电路域接入完成后，发送切换完成消息到移动交换服务器。
S1012，移动交换服务器通知移动性管理实体当前切换已完成。
可选的，上述通知信息可以为Echo消息，该Echo消息包括与该Sv接口相关的一些信息，返回的应答消息可以是Echo应答；返回应答消息可以使移动交换服务器知道移动性管理实体已收到通知信息。业务集中及连续应用服务器和第二用户设备之间的消息可以经过S-CSCF的转发。
实施例四：
参考图11，本实施例中对处于池域组网的移动交换服务器从故障中恢复的处理流程做详细说明。
S1101，检测移动交换服务器是否从故障中恢复；当所述移动交换服务器检测到自身已从故障中恢复时，转到S1102；
S1102，已从故障中恢复的移动交换服务器找到和自己有Sv接口的移动性管理实体，发送通知信息到这些移动性管理实体；
S1103，移动性管理实体收到通知信息后，返回针对通知信息的应答消息给移动交换服务器，并标记发送通知信息的移动交换服务器已从故障中恢复；
S1104，在移动性管理实体上驻留的第一用户设备和第二用户设备建立IMS对话，并且需要切换，进行切换决策，移动性管理实体按照负荷分担的原则选择优先选择该移动交换服务器并发送切换请求；
S1105，移动交换服务器在进行切换准备后，返回切换应答到移动性管理实体；
S1106，移动性管理实体发送切换命令到第一用户设备，第一用户设备开始进行到电路域的接入过程；
S1107，同时，移动交换服务器发送INVITE消息到业务集中及连续应用服务器，请求建立移动交换服务器到第二用户设备之间的媒体连接；
S1108，业务集中及连续应用服务器收到后，发送Update消息到第二用户设 备；
S1109，第二用户设备返回200OK，携带第二用户设备的媒体信息；
S1110，业务集中及连续应用服务器转发200OK到移动交换服务器；
S1111，第一用户设备在电路域接入完成后，发送切换完成消息到移动交换服务器；
S1112，移动交换服务器通知移动性管理实体当前切换已完成。
可选的，上述通知信息可以为Echo消息，该Echo消息包括与该Sv接口相关的一些信息，返回的应答消息可以是Echo应答；返回应答消息的可以使移动交换服务器知道移动性管理实体已收到通知信息。业务集中及连续应用服务器和第二用户设备之间的消息可以经过S-CSCF的转发。
实施例五：
本实施例提供了一种通信系统，该通信系统包括上述实施例中的移动交换服务器和上述实施例所述的移动性管理实体；
所述移动交换服务器检测自身是否从故障中恢复；
当所述移动交换服务器检测到自身已从故障中恢复时，则发送通知消息给所述移动性管理实体，通知所述移动交换服务器已从故障中恢复；
所述移动性管理实体接收到所述通知消息后，将所述移动交换服务器的标记由故障标记更新为正常标记。
实施例六：
图12是本公开实施例六提供的电子设备的结构框图。本公开实施例提供的电子设备配置于移动交换服务器侧，该电子设备可以包括：处理器(processor)1201和存储器(memory)1203，还可以包括通信接口(Communications Interface)1202和总线1204。其中，处理器1201、通信接口1202、存储器1203可以通过总线1204完成相互间的通信。通信接口1202可以用于信息传输。处理器1201可以调用存储器1203中的逻辑指令，以执行上述实施例的接口恢复方法。
此外，上述的存储器1203中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法 的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质，也可以是暂态存储介质。
实施例七：
图13是本公开实施例七提供的电子设备的结构框图。本公开实施例提供的电子设备配置于移动性管理实体侧，该电子设备可以包括：处理器(processor)1301和存储器(memory)1303，还可以包括通信接口(Communications Interface)1302和总线1304。其中，处理器1301、通信接口1302、存储器1303可以通过总线1304完成相互间的通信。通信接口1302可以用于信息传输。处理器1301可以调用存储器1303中的逻辑指令，以执行上述实施例的接口恢复方法。
此外，上述的存储器1303中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质，也可以是暂态存储介质。
本领域的技术人员应该明白，在不冲突的情况下，以上实施例中的特征可以任意组合；上述本公开的多个模块或多个步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在非暂态存储介质(ROM/RAM、磁碟、光盘)中由计算装置来执行，并且在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
以上内容是结合可选的实施方式对本公开所作的详细说明，不能认定本公 开的可选实施例只局限于这些说明。
工业实用性
本公开实施例使得移动性管理实体能及时知道发生故障的该移动交换服务器已从故障中恢复，然后根据需要发送切换指令给该移动交换服务器，从而使Sv接口能够更快的投入，即使移动交换服务器可以更快的承担Sv接口的负荷，减少系统业务中断的时间，提高网络服务质量，保证系统的稳定性，且本发明公开对已有系统的改动和影响很小。

Claims (13)

  1. 一种接口恢复方法，包括：
    当移动交换服务器从故障中恢复，向移动性管理实体发送通知消息，所述通知消息用于指示所述移动交换服务器已从故障中恢复。
  2. 如权利要求1所述的接口恢复方法，其中，所述移动性管理实体为通过Sv接口与所述移动交换服务器建立连接的移动性管理实体。
  3. 如权利要求1或2所述的接口恢复方法，其中，所述通知消息为回声消息。
  4. 一种接口恢复方法，包括：
    移动性管理实体接收移动交换服务器发送的通知消息，所述通知消息用于指示所述移动交换服务器已从故障中恢复；
    所述移动性管理实体根据所述通知消息将所述移动交换服务器的标记由故障标记更新为正常标记。
  5. 如权利要求4所述的接口恢复方法，其中，所述移动性管理实体将所述移动交换服务器的标记由故障标记更新为正常标记后，还包括：向所述移动交换服务器发送针对所述通知消息的应答消息。
  6. 如权利要求4所述的接口恢复方法，其中，所述移动性管理实体将所述移动交换服务器的标记由故障标记更新为正常标记后，还包括：所述移动性管理实体在有新的切换任务时，选择向所述移动交换服务器发送切换指令。
  7. 一种移动交换服务器，包括检测模块和第一处理模块，
    所述检测模块设置为检测移动交换服务器是否从故障中恢复；
    所述第一处理模块设置为当所述移动交换服务器从故障中恢复后，发送通知消息给移动性管理实体，通知所述移动交换服务器已从故障中恢复。
  8. 一种移动性管理实体，包括接收模块和标记模块，
    所述接收模块设置为接收移动交换服务器发送的通知消息，所述通知消息用于指示所述移动交换服务器已从故障中恢复；
    所述标记模块设置为根据所述通知消息将所述移动交换服务器的标记由故障标记更新为正常标记。
  9. 如权利要求8所述的移动性管理实体，其中，还包括：应答消息发送模块，所述应答消息发送模块设置为所述标记模块将所述移动交换服务器的标记由故障标记更新为正常标记后，向所述移动交换服务器发送针对所述通知消息的应答消息。
  10. 如权利要求8或9所述的移动性管理实体，其中，还包括：切换指令发 送模块，所述切换指令发送模块设置为所述标记模块将所述移动交换服务器的标记由故障标记更新为正常标记后，在有新的切换任务时，选择向所述移动交换服务器发送切换指令。
  11. 一种通信系统，包括权利要求7所述的移动交换服务器和权利要求8-10任一项所述的移动性管理实体；
    所述移动交换服务器检测自身是否从故障中恢复；
    当所述移动交换服务器检测到自身已从故障中恢复时，则发送通知消息给所述移动性管理实体，通知所述移动交换服务器已从故障中恢复；
    所述移动性管理实体接收到所述通知消息后，将所述移动交换服务器的标记由故障标记更新为正常标记。
  12. 一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-3任一项的方法。
  13. 一种非暂态计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求4-6任一项的方法。
PCT/CN2016/101821 2015-12-09 2016-10-11 接口恢复方法、移动交换服务器、移动性管理实体及系统 WO2017097031A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510904104.XA CN106856437A (zh) 2015-12-09 2015-12-09 接口恢复方法、移动交换服务器、移动性管理实体及系统
CN201510904104.X 2015-12-09

Publications (1)

Publication Number Publication Date
WO2017097031A1 true WO2017097031A1 (zh) 2017-06-15

Family

ID=59013734

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101821 WO2017097031A1 (zh) 2015-12-09 2016-10-11 接口恢复方法、移动交换服务器、移动性管理实体及系统

Country Status (2)

Country Link
CN (1) CN106856437A (zh)
WO (1) WO2017097031A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101415174A (zh) * 2008-11-20 2009-04-22 华为技术有限公司 移动管理网元、网络恢复方法及系统
CN104010318A (zh) * 2013-02-22 2014-08-27 华为技术有限公司 传输业务的方法和装置
CN104066118A (zh) * 2013-03-21 2014-09-24 中国移动通信集团广东有限公司 一种用于接入方式切换时负荷分担的方法和系统
US20150024751A1 (en) * 2012-01-10 2015-01-22 Nokia Solutions And Networks Oy Handling handover requests in a communications system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656994B (zh) * 2008-08-22 2014-11-05 华为技术有限公司 业务切换及网络资源分配方法、网络节点及移动性管理实体设备
CN103945432B (zh) * 2013-01-18 2017-08-29 中国普天信息产业股份有限公司 集群系统基站的工作模式转换方法
CN104521256B (zh) * 2013-07-22 2018-09-07 华为技术有限公司 位置更新处理方法及设备
US20150098394A1 (en) * 2013-10-08 2015-04-09 Mavenir Systems, Inc. Ims centralized services (ics) interworking function (iwf) system and method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101415174A (zh) * 2008-11-20 2009-04-22 华为技术有限公司 移动管理网元、网络恢复方法及系统
US20150024751A1 (en) * 2012-01-10 2015-01-22 Nokia Solutions And Networks Oy Handling handover requests in a communications system
CN104010318A (zh) * 2013-02-22 2014-08-27 华为技术有限公司 传输业务的方法和装置
CN104066118A (zh) * 2013-03-21 2014-09-24 中国移动通信集团广东有限公司 一种用于接入方式切换时负荷分担的方法和系统

Also Published As

Publication number Publication date
CN106856437A (zh) 2017-06-16

Similar Documents

Publication Publication Date Title
JP5174178B2 (ja) 着信転送のための方法、システム、およびデバイス
US9338625B2 (en) Geographically redundant and multiple EATF nodes
CN103190187A (zh) Ims架构中的分组交换到电路交换接入切换
EP3157224B1 (en) Method and system for converting session control signaling
WO2015062468A1 (zh) 一种单一无线语音通话连续性切换的方法、设备及系统
WO2013156061A1 (en) Failure handling within a network implementing srvcc
EP2487986A1 (en) Method, device and system for processing connection of called party
JP5666577B2 (ja) セッションの継続性を改善するための方法及びデバイス
CN109804609A (zh) 通信会话请求的后到先服务处理
EP2577931B1 (en) Preserving mid-call state in ims centralized services sessions
EP3420464B1 (en) Initiation of conference and transfer call in internet protocol multimedia subsystem based emergency services network
US20150016308A1 (en) Method and apparatus for service control
WO2009149635A1 (zh) 一种实现显式呼叫转移的方法、设备及移动通信系统
WO2017097031A1 (zh) 接口恢复方法、移动交换服务器、移动性管理实体及系统
KR20120095201A (ko) 이동 통신 시스템에서 음성 호 연속을 위한 도메인 선택 방법 및 장치
EP3085046B1 (en) Session initiation handling
WO2015106558A1 (zh) 呼叫处理方法、装置及系统
CN105763524A (zh) Ip多媒体子系统中的注册方法、装置和系统
EP3073799A1 (en) Method and apparatus for notifying/triggering call forwarding/deflection service
WO2013102394A1 (zh) 一种反向单待业务连续性实现方法和装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16872225

Country of ref document: EP

Kind code of ref document: A1