WO2012075733A1 - Système de service de type vocal et procédé pour réaliser une tolérance aux sinistres - Google Patents

Système de service de type vocal et procédé pour réaliser une tolérance aux sinistres Download PDF

Info

Publication number
WO2012075733A1
WO2012075733A1 PCT/CN2011/071190 CN2011071190W WO2012075733A1 WO 2012075733 A1 WO2012075733 A1 WO 2012075733A1 CN 2011071190 W CN2011071190 W CN 2011071190W WO 2012075733 A1 WO2012075733 A1 WO 2012075733A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
call
management node
backup
management
Prior art date
Application number
PCT/CN2011/071190
Other languages
English (en)
Chinese (zh)
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 WO2012075733A1 publication Critical patent/WO2012075733A1/fr

Links

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
    • 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
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements

Definitions

  • the invention belongs to the field of communication technologies, and relates to a database disaster recovery backup technology, in particular to a method for implementing disaster tolerance of a voice service system and a voice service system using the method.
  • Background technique
  • the existing voice service system backups the core data of the service.
  • the voice service system performs daily backup of the database.
  • the backup of the data is not real-time. If a disaster occurs, it may be lost for one to two days. Business data. Summary of the invention
  • the technical problem to be solved by the present invention is: for the defects existing in the prior art, a disaster recovery implementation method for a voice service system, and a voice service system using the method are proposed to implement voice more effectively. Disaster recovery backup of the business system.
  • the technical solution of the present invention is implemented as follows:
  • a method for implementing disaster tolerance in a voice service system includes the following steps:
  • the backup node accepts data synchronization of the management node of the voice service system
  • the backup node takes over the management node and performs the function of the management node.
  • the call node of the voice service system is divided into two parts, one part is set locally, and the other part is set in the different place, each part can perform the function of the call node by itself; when the local part is faulty, The portion placed in the off-site performs the function of the call node.
  • the data synchronization is real-time data synchronization.
  • the voice type service system is monitored and an alarm is issued when it fails.
  • a voice-based service system includes a management node, a call node, and a backup node; wherein the management node is placed locally and is used for service acceptance;
  • the call node is configured to be responsible for service call processing
  • the backup node is placed off-site for accepting data synchronization of the management node, and when the management node fails, it performs its function.
  • the call node is divided into two parts, one part is placed locally, and the other part is placed in the different place, and each part can perform the function of the call node by itself;
  • the portion placed in the remote location is used to perform the function of the calling node.
  • each database stores all voice-type service call related data, and each service control point of the part is associated with each database of the part Even.
  • the management node and the call node use a separate physical architecture.
  • the data synchronization is real-time data synchronization.
  • the method further includes an alarm module, configured to monitor the management node and the call node, and issue an alarm when a fault is detected.
  • the invention adopts a voice-based business system disaster recovery scheme for real-time backup in different places, and divides the call node into two parts, one part is placed locally with the management node, and the other part is placed in a different place together with the backup node, so that even if it is serious
  • the disaster if the local voice-based business system is completely lost, can still realize the function of the voice-based business system through the backup node and the call node in different places, and realize real-time data backup, so as to have a good disaster tolerance effect.
  • the voice service system can resume normal operation in a short period of time under any severe disaster. It improves the quality of service for operators while reducing the economic loss in the event of a disaster.
  • FIG. 1 is a schematic flow chart of the method of the present invention in a specific embodiment
  • FIG. 2 is a network diagram of a system of the present invention according to a specific embodiment
  • FIG. 3 is a basic flowchart of service data synchronization in an embodiment of the present invention.
  • FIG. 4 is a basic flowchart of processing a voice file according to an embodiment of the present invention.
  • FIG. 5 is a basic flowchart of alarm processing in an embodiment of the present invention.
  • FIG. 6 is a networking diagram of a disaster recovery scenario 1 according to an embodiment of the present invention.
  • FIG. 7 is a networking diagram of a disaster recovery scenario 2 according to an embodiment of the present invention.
  • FIG. 8 is a networking diagram of a disaster recovery scenario 3 according to an embodiment of the present invention. detailed description
  • FIG. 1 is a schematic flowchart of a method of the present invention in a specific embodiment. As shown in the figure, the method for implementing disaster recovery of a voice service system of the present invention specifically includes the following steps:
  • the backup node accepts real-time data synchronization of the management node of the voice service system.
  • the backup node can take over the management node and perform the function of the management node.
  • the call node of the voice service system is divided into two parts, one part is set locally with the management node, and the other part is set in different places together with the backup node, and each part can perform the function of the call node by itself, that is, each part can Responsible for voice service call processing alone.
  • each part can perform the function of the call node by itself, that is, each part can Responsible for voice service call processing alone.
  • the function of the calling node can be performed by the part placed in the remote place.
  • each database stores all of the voice-type service call related data
  • each service control point CP is connected to each database of the part at the same time.
  • the voice service system of the present invention includes a management node, a call node, and a backup node, and the management node and the backup node are set in different regions or cities, and the call is made.
  • the node is divided into two parts, one part is located in the same place as the management node, and the other part is in the same place as the backup node.
  • Each part can complete the function of the calling node by itself, that is, it is responsible for the call processing of the voice type service.
  • the management node is separated from the call node implementation function, and correspondingly physically separate structures are also used, that is, two independent physical entities are formed.
  • the MML (Man-Machine Language) interface refers to the human-machine access interface
  • the RTP is called the Real-time Transport Protocol, which is the real-time transport protocol
  • the SIP is called the Session Initiation Protocol, which is the session initiation protocol.
  • the management node is mainly responsible for business acceptance and synchronization of data to each call node.
  • the business acceptance includes ring tone uploading, modification and deletion, user account opening, account cancellation, user ordering, deleting ring tone (group), user addition, modification, deletion setting, and user inquiry.
  • the management node contains devices, including SMP (service management point), SCP (Service Control Point), web (Internet) server, IMP (integrated interface machine), LanSwith (network switch), BOSS IMP (Interface with BOSS system), SMSC IMP (Interface with Short Message Center), CDR (Charging Data Recording).
  • the management node and the backup node are connected through the network switch, and the service data is synchronized to the backup node in real time, and the service data needs to be synchronized to the database of the call node.
  • the calling node includes a CP and a DB, and the CP is connected to a SIU (signal interface unit).
  • the DB accepts the synchronization of the management node and is responsible for the call processing of the user.
  • Each DB stores all the CRBT call related data.
  • the SIU uses a polling method to distribute call requests to each CP evenly or in a certain proportion. In the embodiment of the present invention, there are a total of five DBs in the calling node, wherein there are three in the local, and there are two in the offsite (that is, where the backup node is set); there are a total of 11 CPs, among which there are local Six, there are five in different places.
  • each CP connects to each DB at the same time, so that any DB in the place fails, and the system automatically forwards the call request to the normal device.
  • the data of the management node and the call node is synchronized with Oracle Advanced Replication technology (the advanced replication technology of ORACLE).
  • the main system architecture of the backup node is the same as that of the management node. It is equivalent to all the devices in the management node have a set at the backup node, and the external interface is the same. Under normal circumstances, most of the devices in the backup node are inactive, but the service database and voice storage device in the backup node are working.
  • the business data in the management node is automatically synchronized to Backup node and call node.
  • Offsite backup of business data is implemented using the Data guard technology provided by ORACLE.
  • the uploading module of the voice content uploads the voice file to the management node and the backup node at the same time.
  • the real-time synchronization process of voice media files is as follows.
  • the WEB interface is mainly responsible for receiving user input including ringtone name, ringtone price, singer information, and physical sound files. Then, the ring tone information is notified to the ring tone upload interface by using a PDU ( Protocol Data Unit) message, and the 4 bar physical sound file is placed on an FTP (File Transfer Protocol) server.
  • PDU Protocol Data Unit
  • FTP File Transfer Protocol
  • the ring tone upload interface receives the request from the WEB interface, and then connects to the service database to perform database operations, and adds ring tone information. After the operation of the database is successful, it will connect to the FTP server to obtain the physical sound, and then FTP to the management node and the backup node's voice storage device to save.
  • the voice service type system of the present invention further includes an alarm module, which is mainly used for detecting data synchronization from the management node to the backup node and data synchronization of the management node to the call node, and monitoring the database status of each node. If a fault occurs, the alarm can be sent to the intelligent network platform, and the alarm can be sent to the network administrator through the short message interface.
  • an alarm module which is mainly used for detecting data synchronization from the management node to the backup node and data synchronization of the management node to the call node, and monitoring the database status of each node. If a fault occurs, the alarm can be sent to the intelligent network platform, and the alarm can be sent to the network administrator through the short message interface.
  • FIG. 5 is a basic flowchart of alarm processing in the present invention.
  • the alarm monitoring process is responsible for monitoring the management section, the calling node, and the backup node. If a data synchronization exception occurs, an alarm message is sent to the service management point SMP and the short message interface.
  • Service Management Point The SMP receives alarm messages and provides a user interface for administrators to check for alarm messages.
  • the short message interface receives the alarm message and is connected to the SMSC short message center.
  • the SMSC Short Message Center is responsible for sending SMS notifications to the end user.
  • the devices that start all the backup nodes include the WEB server and the IMP interface.
  • the equipment and service platform, at the same time, all business acceptance and data synchronization of the call node are switched to the new management node.
  • Scenario 1 When the local management node and the call node are all destroyed, the network structure after system recovery is shown in Figure 6.
  • the recovery steps in this case include:
  • the devices that start all backup nodes include the WEB server, the IMP interface device, and the service platform.
  • the data synchronization of the calling node is switched to the new management node.
  • the routing of the core network directly points to the calling node in the remote location.
  • Scenario 2 When the local management node is down, but the call nodes are all normal, the network structure after the system is restored is as shown in Figure 7.
  • the recovery steps in this case include:
  • the devices that start all backup nodes include the WEB server, the IMP interface device, and the service platform.
  • the voice service system can resume normal operation in a short time under any severe disaster. While providing the quality of service for operators, it also reduces the economic loss in the event of a disaster.
  • the invention can be widely applied to the CRBT service, and can also be applied to other similar voice service systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un système de service de type vocal qui comprend un noeud de gestion, un noeud appelant et un noeud de secours. Le noeud de gestion est responsable de l'acceptation du service et est positionné localement; le noeud de secours est positionné à distance pour accepter la synchronisation de données en temps réel en provenance du noeud de gestion et, lorsque le noeud de gestion est arrêté, le noeud de secours le remplace pour mettre en oeuvre cette fonction; le noeud appelant est responsable du traitement des appels du service, est divisé en deux parties dont l'une est positionnée localement et l'autre à distance, chaque partie pouvant réaliser de manière indépendante la fonction du noeud appelant. Lorsque la partie positionnée localement est arrêtée, la partie positionnée à distance réalise la fonction du noeud appelant. L'invention concerne également un procédé de tolérance aux sinistres pour le système de service de type vocal. En cas de sinistres importants, le système de service de type vocal peut garantir que les données ne sont pas perdues et que le fonctionnement normal reprendra plus rapidement grâce aux solutions de la présente invention.
PCT/CN2011/071190 2010-12-09 2011-02-23 Système de service de type vocal et procédé pour réaliser une tolérance aux sinistres WO2012075733A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010580339.5 2010-12-09
CN201010580339.5A CN102026249B (zh) 2010-12-09 2010-12-09 一种语音类业务系统及容灾实现方法

Publications (1)

Publication Number Publication Date
WO2012075733A1 true WO2012075733A1 (fr) 2012-06-14

Family

ID=43866959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/071190 WO2012075733A1 (fr) 2010-12-09 2011-02-23 Système de service de type vocal et procédé pour réaliser une tolérance aux sinistres

Country Status (2)

Country Link
CN (1) CN102026249B (fr)
WO (1) WO2012075733A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102255750B (zh) * 2011-06-28 2017-05-10 中兴通讯股份有限公司 一种业务容灾保护的方法及装置
CN102711091B (zh) * 2012-06-12 2018-11-23 中兴通讯股份有限公司 核心网系统及数据处理方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026496A (zh) * 2007-01-26 2007-08-29 华为技术有限公司 一种容灾系统、方法和网络设备
CN101667937A (zh) * 2008-09-02 2010-03-10 华为技术有限公司 实现数据业务设备容灾的方法、数据业务设备和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100461697C (zh) * 2006-04-18 2009-02-11 华为技术有限公司 基于设备容灾的业务接管方法及备份机

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026496A (zh) * 2007-01-26 2007-08-29 华为技术有限公司 一种容灾系统、方法和网络设备
CN101667937A (zh) * 2008-09-02 2010-03-10 华为技术有限公司 实现数据业务设备容灾的方法、数据业务设备和系统

Also Published As

Publication number Publication date
CN102026249A (zh) 2011-04-20
CN102026249B (zh) 2016-01-20

Similar Documents

Publication Publication Date Title
JP2646385B2 (ja) 通話転送制御方法及び装置
EP2443815B1 (fr) Architecture de serveur d'enregistrement distribuée pour enregistrer des sessions d'appel sur un réseau voip
WO2011000240A1 (fr) Procédé et système de traitement des défaillances d'agents dans un centre d'appels
US20080025221A1 (en) Methods, systems, and computer program products for a hierarchical, redundant OAM&P architecture for use in an IP multimedia subsystem (IMS) network
EP1906681A2 (fr) Procédé de transfert vers sauvegarde dans un système informatique
CN102231677A (zh) Iptv系统中一种基于双中心容灾的切换方法及其装置
CN101753339B (zh) 一种实现多点控制单元会议备份功能的方法及系统
WO2008046351A1 (fr) Système de communication, et appareil et procédé permettant d'améliorer la fiabilité du système de communication
CN102752464B (zh) 大规模呼叫中心座席网络录音的方法和系统
US20130315382A1 (en) System and method for robust call center operation using multiple data centers
CN105302792B (zh) 一种语音平台架构调整方法
CN102055605A (zh) 一种应用于aaa服务器的容灾系统及方法
WO2011012027A1 (fr) Procédé et système de reprise d’enregistrement vidéo
US20130185425A1 (en) Method for Optimizing Network Performance After A Temporary Loss of Connection
WO2012075733A1 (fr) Système de service de type vocal et procédé pour réaliser une tolérance aux sinistres
JP4592511B2 (ja) Ｉｐネットワークサーバのバックアップシステム
WO2015139377A1 (fr) Procédé et système d'enregistrement audio pour centre d'appel de cloud, et dispositif d'ordonnancement central et support de stockage
WO2021238579A1 (fr) Procédé de gestion de disque dur sata au moyen d'un système de stockage, et système de stockage
US20060078092A1 (en) System and method for providing a backup-restore solution for active-standby service management systems
WO2014110994A1 (fr) Plateforme intégrée assurant une reprise sur sinistre d'un système de technologie de l'information
CN102577316B (zh) 数据监听方法、设备和系统
WO2012097604A1 (fr) Procédé, système et passerelle pour traiter des messages en cas d'échec d'une passerelle
CN102480382B (zh) 在话务台系统中服务大客户客户端的方法及系统
US8780895B1 (en) Method and apparatus for detecting relocation of endpoint devices
CN102821365B (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: 11846489

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

Country of ref document: EP

Kind code of ref document: A1