CN100466545C - Data synchronization method between the main board and spare board in the communication system - Google Patents

Data synchronization method between the main board and spare board in the communication system Download PDF

Info

Publication number
CN100466545C
CN100466545C CNB2006100721547A CN200610072154A CN100466545C CN 100466545 C CN100466545 C CN 100466545C CN B2006100721547 A CNB2006100721547 A CN B2006100721547A CN 200610072154 A CN200610072154 A CN 200610072154A CN 100466545 C CN100466545 C CN 100466545C
Authority
CN
China
Prior art keywords
data
slave board
mainboard
synchronization
timer
Prior art date
Application number
CNB2006100721547A
Other languages
Chinese (zh)
Other versions
CN101056195A (en
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 CNB2006100721547A priority Critical patent/CN100466545C/en
Publication of CN101056195A publication Critical patent/CN101056195A/en
Application granted granted Critical
Publication of CN100466545C publication Critical patent/CN100466545C/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1013Network architectures, gateways, control or user entities
    • H04L65/1043MGC, MGCP or Megaco
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/305Authentication, i.e. establishing the identity or authorisation of security principals by remotely controlling device operation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6209Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/71Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
    • G06F21/74Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/88Detecting or preventing theft or loss
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11BINFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10Digital recording or reproducing
    • G11B20/10009Improvement or modification of read or write signals
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11BINFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10Digital recording or reproducing
    • G11B20/10009Improvement or modification of read or write signals
    • G11B20/10305Improvement or modification of read or write signals signal quality assessment
    • G11B20/10398Improvement or modification of read or write signals signal quality assessment jitter, timing deviations or phase and frequency errors
    • G11B20/10425Improvement or modification of read or write signals signal quality assessment jitter, timing deviations or phase and frequency errors by counting out-of-lock events of a PLL
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03LAUTOMATIC CONTROL, STARTING, SYNCHRONISATION, OR STABILISATION OF GENERATORS OF ELECTRONIC OSCILLATIONS OR PULSES
    • H03L7/00Automatic control of frequency or phase; Synchronisation
    • H03L7/06Automatic control of frequency or phase; Synchronisation using a reference signal applied to a frequency- or phase-locked loop
    • H03L7/08Details of the phase-locked loop
    • H03L7/085Details of the phase-locked loop concerning mainly the frequency- or phase-detection arrangement including the filtering or amplification of its output signal
    • H03L7/091Details of the phase-locked loop concerning mainly the frequency- or phase-detection arrangement including the filtering or amplification of its output signal the phase or frequency detector using a sampling device
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/03Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words
    • H03M13/23Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words using convolutional codes, e.g. unit memory codes
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/29Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
    • H03M13/2903Methods and arrangements specifically for encoding, e.g. parallel encoding of a plurality of constituent codes
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/29Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
    • H03M13/2957Turbo codes and decoding
    • H03M13/2993Implementing the return to a predetermined state, i.e. trellis termination
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/63Joint error correction and other techniques
    • H03M13/635Error control coding in combination with rate matching
    • H03M13/6356Error control coding in combination with rate matching by repetition or insertion of dummy data, i.e. rate reduction
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/63Joint error correction and other techniques
    • H03M13/635Error control coding in combination with rate matching
    • H03M13/6362Error control coding in combination with rate matching by puncturing
    • HELECTRICITY
    • H03BASIC ELECTRONIC CIRCUITRY
    • H03MCODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M7/00Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
    • H03M7/30Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
    • H03M7/40Conversion to or from variable length codes, e.g. Shannon-Fano code, Huffman code, Morse code
    • H03M7/4006Conversion to or from arithmetic code
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B10/00Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/25Arrangements specific to fibre transmission
    • H04B10/2575Radio-over-fibre, e.g. radio frequency signal modulated onto an optical carrier
    • H04B10/25752Optical arrangements for wireless networks
    • H04B10/25753Distribution optical network, e.g. between a base station and a plurality of remote units
    • H04B10/25754Star network topology
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/24Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2628Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using code-division multiple access [CDMA] or spread spectrum multiple access [SSMA]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J13/00Code division multiplex systems
    • H04J13/0077Multicode, e.g. multiple codes assigned to one user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J13/00Code division multiplex systems
    • H04J13/16Code allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0064Concatenated codes
    • H04L1/0066Parallel concatenated codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0067Rate matching
    • H04L1/0068Rate matching by puncturing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; Arrangements for supplying electrical power along data transmission lines
    • H04L25/03Shaping networks in transmitter or receiver, e.g. adaptive shaping networks ; Receiver end arrangements for processing baseband signals
    • H04L25/03006Arrangements for removing intersymbol interference
    • H04L25/03012Arrangements for removing intersymbol interference operating in the time domain
    • H04L25/03019Arrangements for removing intersymbol interference operating in the time domain adaptive, i.e. capable of adjustment during data reception
    • H04L25/03038Arrangements for removing intersymbol interference operating in the time domain adaptive, i.e. capable of adjustment during data reception with a non-recursive structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/38Synchronous or start-stop systems, e.g. for Baudot code
    • H04L25/40Transmitting circuits; Receiving circuits
    • H04L25/49Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems
    • H04L25/497Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems by correlative coding, e.g. partial response coding or echo modulation coding transmitters and receivers for partial response systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/28Details regarding addressing issues
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/38Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/12Applying verification of the received information
    • H04L63/126Applying verification of the received information the source of the received data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1003Signalling or session protocols
    • H04L65/1006SIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/085Secret sharing or secret splitting, e.g. threshold schemes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/30Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H04L9/304Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy based on error correction codes, e.g. McEliece
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers; Analogous equipment at exchanges
    • H04M1/72Substation extension arrangements; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selecting
    • H04M1/725Cordless telephones
    • H04M1/72519Portable communication terminals with improved user interface to control a main telephone operation mode or to indicate the communication status
    • H04M1/72522With means for supporting locally a plurality of applications to increase the functionality
    • H04M1/72527With means for supporting locally a plurality of applications to increase the functionality provided by interfacing with an external accessory
    • H04M1/72533With means for supporting locally a plurality of applications to increase the functionality provided by interfacing with an external accessory for remote control of appliances
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Interconnection arrangements between switching centres
    • H04M7/12Interconnection arrangements between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step, decimal and non-decimal, circuit-switched and packet-switched, i.e. gateway arrangements
    • H04M7/1205Interconnection arrangements between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step, decimal and non-decimal, circuit-switched and packet-switched, i.e. gateway arrangements where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1295Details of dual tone multiple frequency signalling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/10Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding
    • H04N19/102Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the element, parameter or selection affected or controlled by the adaptive coding
    • H04N19/103Selection of coding mode or of prediction mode
    • H04N19/109Selection of coding mode or of prediction mode among a plurality of temporal predictive coding modes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/10Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding
    • H04N19/134Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the element, parameter or criterion affecting or controlling the adaptive coding
    • H04N19/136Incoming video signal characteristics or properties
    • H04N19/137Motion inside a coding unit, e.g. average field, frame or block difference
    • H04N19/139Analysis of motion vectors, e.g. their magnitude, direction, variance or reliability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/60Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using transform coding
    • H04N19/625Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using transform coding using discrete cosine transform [DCT]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/90Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using coding techniques not provided for in groups H04N19/10-H04N19/85, e.g. fractals
    • H04N19/91Entropy coding, e.g. variable length coding [VLC] or arithmetic coding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04TPC
    • H04W52/30TPC using constraints in the total amount of available transmission power
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2105Dual mode as a secondary aspect
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2115Third party
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11BINFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/22Signal processing not specific to the method of recording or reproducing; Circuits therefor for reducing distortions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1013Network architectures, gateways, control or user entities
    • H04L65/1016IMS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42221Conversation recording systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes
    • H04W72/042Wireless resource allocation involving control information exchange between nodes in downlink direction of a wireless link, i.e. towards terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • H04W8/245Transfer of terminal data from a network towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • H04W88/085Access point devices with remote components
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S370/00Multiplex communications
    • Y10S370/901Wide area network
    • Y10S370/902Packet switching
    • Y10S370/903Osi compliant network
    • Y10S370/906Fiber data distribution interface, FDDI
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S370/00Multiplex communications
    • Y10S370/901Wide area network
    • Y10S370/902Packet switching
    • Y10S370/903Osi compliant network
    • Y10S370/907Synchronous optical network, SONET

Abstract

The invention discloses a data synchronizing method between the main board and backplane of communication system, the invention may divide the synchronization processing into 'starting synchronization' and 'immediate synchronization' processes, for the non-protocol configured data, as the starting of backplane, the data synchronizing process shall be started by the backplane, if detected on the main board that the non-configured data changed during the system running, then the synchronization process may be started by the main board; moreover, if detected that the message received by the main board is new, then this message data shall be synchronized to the backplane. For the protocol configuration data, during the configuration, if the backplane is also in its place, then synchronize the data to the backplane through the immediate synchronization to ensure the configuration conformity; if the backplane is not in its place during configuration, then during the starting of backplane, the starting synchronization may be applicable. The method in the invention may effectively solve the protocol synchronization processing problems concerning with the message and topology, moreover, ensure the conformity between the main and standby protocol data.

Description

The method of data synchronization of mainboard and slave board in the communication system

Technical field

The present invention relates to active and standby synchronous processing in the communication system, when especially system adopts Hot Spare, the real-time synchronization method of mainboard and slave board agreement.

Background technology

High speed development along with communication network, reliability, the stability of communication have more and more embodied its importance, and key equipment is carried out redundancy backup is the important means that guarantees communication network functional reliability and stability, is exactly a kind of common method as the key equipment in the system being adopted active and standby plate carry out Hot Spare.When mainboard was unavailable, system automatically switched to the slave board operation, and slave board replaces the function of original mainboard, guarantees the free of discontinuities of communication.So just draw following problem: the consistency that how to guarantee active and standby plate configuration data? the free of discontinuities of guarantee agreement how? the consistency of guarantee agreement dynamic data how?

In existing many systems that have an active and standby plate, configuration data often can guarantee that these mechanism have also guaranteed the active and standby switching free of discontinuities of part agreement simultaneously by some unified mechanism synchronously.And some agreement in fact, only can't guarantee active and standby switching free of discontinuities synchronously by configuration data, because also there are some differences except that configuration data in mainboard and slave board, difference as mainboard and slave board packet sending and receiving, perhaps the difference of mainboard and slave board topological data and the related agreement of these difference just can't be only carry out synchronously by configuration data that unremitting business is active and standby have been switched.

At the synchronous problem of configuration data, once there was suggestion to propose the synchronous method of a kind of active and standby plate configuration data, promptly by the sync buffering district is set on mainboard and slave board, data modification, compose buffer then, when buffering area completely then carries out synchronously, successful then delete buffer data, otherwise repetition simultaneous operation is finished until all data sync.This method be applicable to mass data on mainboard and the slave board synchronously, mass data synchronous (as database synchronization) there is certain validity, but for then not relating to synchronously that guarantee agreement data free of discontinuities is handled, simultaneously, when buffering area excessive, and need data in synchronization very few, also the reasonable mechanism of neither one is handled.

Suggestion at the call state data sync was also once proposed at present, promptly pass through the object of UML instrument definition call treatment, and required condition when describing all states of this class object and state migration takes place with state diagram, each state is to a built-in attribute that should object, by synchronously the built-in attribute value of calling out being write down and synchronously.This method can guarantee to call out relevant synchronously, but for still not relating to synchronously that guarantee agreement data free of discontinuities is handled.

Summary of the invention

Technical problem to be solved by this invention is to provide the method for data synchronization of mainboard and slave board in a kind of communication system, at with related agreements such as message, topology, handle free of discontinuities that can guarantee agreement, the consistency of guarantee agreement data again by protocol synchronization.

At above-mentioned technical problem, the invention provides the method for data synchronization of mainboard and slave board in a kind of communication system, comprise the steps:

(1) need to determine the synchronous non-configuration data relevant with communication protocol;

(2),, will need synchronous non-configuration data on the mainboard synchronously to slave board then by slave board log-on data synchronizing process if slave board starts in running;

(3) detect the situation of change that needs synchronous non-configuration data on the mainboard, if in system's running, need synchronous non-configuration data to change on the mainboard, then start synchronizing process by mainboard, packing data is arrived the synchrodata memory block, the synchrodata memory block is full or timer is in time synchronous to then carrying out, with the non-configuration data that changes synchronously to slave board.

The present invention can further include:

(4) detect the message situation that mainboard is received, if new message then is synchronized to slave board with this message data.

Wherein, described step (1) may further include: need to determine the synchronous configuration data relevant with communication protocol; Described step (2) may further include: if slave board starts, then initiate data synchronization process by slave board, will need synchronous configuration data synchronously to slave board on the mainboard; Described step (3) may further include: if slave board is on the throne, and need synchronous configuration data to change on the mainboard, then by mainboard with the configuration data that changes synchronously to slave board.

Wherein, described step (2) can comprise:

(21) slave board sends a synchronization request to mainboard, comprises a sequence number in this request;

(22) mainboard returns a reply data, in this reply data described sequence number is taken back, and is comprised an end mark, and this flag set is represented same EOS, and set does not represent that the data needs are synchronous in addition;

(23) after slave board is received the response data of mainboard feedback, judge whether sequence number is consistent, if consistent, then according to the corresponding data on the reply data renewal slave board, and it is determine whether next time synchronization request, if inconsistent then abandon re-send request may according to the end mark in the reply data;

(24) mainboard is when data sync finishes, in reply data with end mark set.

Wherein, described step (21) can comprise:

(211) to slave board, system start-up then is provided with a request timer, and this timer then back sends synchronization request to mainboard;

(212) after slave board sends the synchronization request success, create this request timer again, receive the reply data of mainboard at slave board after, delete this request timer;

(213) after slave board sends the synchronization request failure, create an overtime timer;

(214) described request timer or overtime timer then after, send current synchronization request by slave board.

Wherein, step (23) is described determines whether to comprise next time synchronization request according to the end mark in the reply data:

Judge the whether set of end mark of reply data,, continue to the new transmission synchronization request of mainboard if not set then increases progressively current SYN; If set then stops to send synchronization request.

Wherein, described step (3) comprising:

(31) a synchrodata memory block is set, and a timer is set;

(32) start when synchronous at mainboard, start described timer, and will need data in synchronization to be sent to described synchrodata memory block;

(33) during timer regularly,, then it is continued to be sent to described synchrodata memory block if need data in synchronization in addition;

(34) full in space, described synchrodata memory block, or timer then after, by mainboard with the data sync in the described synchrodata memory block to slave board, and upgrade corresponding data by slave board;

(35) delete this timer, and empty the synchronized data in the described synchrodata memory block.

Wherein, in the described step (33),, then use follow-up data to cover previous data if the follow-up data that are sent in the described memory block repeat with the data of having stored.

Wherein, will need data in synchronization to be sent to the step of synchrodata memory block described in described step (32), (33), be a plurality of synchrodatas to be packed send together.

Wherein, described step (4) may further include:

After slave board was received the synchronous message of mainboard, the literary composition of receiving telegraph was handled, if slave board according to protocol logic, when discovery need be simulated message, then directly carries out simulation process at slave board according to protocol logic.

The present invention is directed to non-configuration data of agreement and message data, in conjunction with configuration data synchronously, the active and standby synchronization scenario of agreement provided by the invention effectively solution has the protocol synchronization of correlation to handle with message, topology, the consistency of assurance dynamic data; Can effectively improve simultaneously as protocol massages and need in a large number repeatedly repeat the problem synchronous, that the host-standby communication amount is big.

Description of drawings

Fig. 1 is according to the described startup synchronous processor drawing of the embodiment of the invention;

Fig. 2 sends the flow chart that starts the Synchronous Processing request according to the described slave board of the embodiment of the invention;

Fig. 3 is a flow chart of receiving main plate response according to the described slave board of the embodiment of the invention;

Fig. 4 is the flow chart according to the relevant timer processing of the described slave board of the embodiment of the invention;

Fig. 5 is according to the described timely Synchronous Processing flow chart of the embodiment of the invention;

Fig. 6 is according to the described mainboard message of embodiment of the invention Synchronous Processing flow chart;

Fig. 7 is according to the described slave board message of embodiment of the invention Synchronous Processing flow chart.

Embodiment

At the non-configuration data of agreement, for the free of discontinuities of guarantee agreement operation and dynamic data synchronously, the present invention is divided into Synchronous Processing " starting synchronously " process and " synchronously in time " process, specifically, can comprise the steps:

(1) determines the non-configuration data that protocol-dependent needs are synchronous;

(2), then synchronous to the startup that needs the data in synchronization property confirmed if in running, slave board is plugged;

(3) data in synchronization changes in running if desired, and to buffer area, buffer area is full or in time synchro timer is in time synchronous to then carrying out with packing data;

(4) if message data is arranged, it is synchronous to carry out message; Synchronous if desired message is repeated message, adopt a message only synchronously once/or the mode of limited number of time, simulate according to protocol logic at slave board afterwards, reduce the synchronous number of times of message.

If there are a plurality of needs to carry out synchronous module in the system, then step (2), (3) can be used as utility module and unify to handle.

In system's running, if the disconnected incident of active and standby communication link has taken place, need in communication recovery, start again synchronously and message synchronous.

In system's running,, need start synchronous 0 again if the incident of active and standby switching has taken place.

In system's running,, then need to carry out in time synchronously if active and standby communication link leads to.

To the configuration data of agreement, adopt to start synchronously and timely synchronous method, guarantee the consistency of configuration.If promptly in the layoutprocedure, slave board is also on the throne, then, guarantee the consistency of this configuration by in time synchronously data sync being arrived slave board; If in the layoutprocedure, slave board is not on the throne, then in the slave board start-up course, starts synchronously.Because often exist a plurality of modules configured data needs synchronous in the system, so this part can be used as a utility module active and standby synchronous function is provided.

Be described in further detail below in conjunction with the enforcement of accompanying drawing technical scheme:

Fig. 1 is the flow chart of the described startup Synchronous Processing of embodiment of the invention mechanism, and starting synchronous mechanism is initiatively to want data to mainboard after slave board starts, and the method for synchronization is: 1. slave board sends synchronization request, comprises a sequence number in the synchrodata structure; 2. mainboard echoes and answers, and in the reply data this sequence number is taken back, and is comprised an end mark, and same EOS is represented in set, and set does not represent that data are wanted synchronously in addition; 3. slave board receives that main plate response judges earlier whether the response sequence of sequence number and current expectation is number identical, and difference then abandons, re-send request may; Identical then normal process: the one, upgrade corresponding data on the slave board, the 2nd, judge the whether set of end mark position in the response, if set then no longer sends request, set does not then continue to send next request.

Fig. 2, Fig. 3, Fig. 4 are the described startup Synchronous Processing of embodiment of the invention flow charts, and the idiographic flow that starts Synchronous Processing is: to slave board, system start-up then is provided with request timer 1 in order to the triggering synchronous request, is timed to then and sends synchronization request to mainboard; Slave board sends then request to create timer 1 again of synchronization request success, receives that main plate response deletes this timer 1; For guaranteeing the transmission of synchronization message, slave board sends the synchronization request failure and then creates overtime timer 2, and timer 1 and 2 processing then all is to send current request.To mainboard, only need the request of slave board is responded, and the set end mark gets final product when data sync finishes.

Wherein, Fig. 2 is that the described slave board of the embodiment of the invention sends the flow chart that starts the Synchronous Processing request, and detailed process is as follows:

Step 201: current SYN is write in the synchronization request data structure, transmit a request to mainboard;

Step 202: whether send success, if, enter step 203, if not, enter step 204;

Step 203: create timer 1;

Step 204: create timer 2;

Step 205: return.

Wherein, Fig. 3 is the flow chart that the described slave board of the embodiment of the invention is received main plate response, and detailed process is as follows:

Step 301: slave board is subjected to main plate response, deletion timer 1;

Step 302: judge whether response sequence is number identical with current SYN, if, enter step 303, if not, enter step 304;

Step 303: upgrade corresponding data on the slave board;

Step 304: according to transmission synchronization request shown in Figure 2;

Step 305: judge the whether set of response stop bits, if, enter step 307, if not, enter step 306;

Step 306: current SYN increases 1, continues to send synchronization request;

Step 307: return.

Wherein, Fig. 4 is the flow chart of the relevant timer processing of the described slave board of the embodiment of the invention, and detailed process is as follows:

Step 401: timer 1 then enters step 403;

Step 402: timer 2 then enters step 403;

Step 403: send synchronization request according to Fig. 2.

Fig. 5 is the described timely Synchronous Processing flow chart of the embodiment of the invention, in time synchronous treatment mechanism is: when the mainboard data change, initiatively send this variation to slave board, slave board does not need to echo should, because in time data in synchronization can be very not big each time synchronously, consider the possibility that exists mainboard to send failure to slave board, present embodiment retransmits three times miss data, reduce the possibility of makeing mistakes, consider that again inter-sync number of times of short time may be a lot, send failure if cause, can pack to several synchronous bags sends together.

By the above, need to define a space here, when needs send synchrodata, synchrodata is put in this space, when storing data for the first time, a timer is set simultaneously, this synchrodata is temporary transient asynchronous to slave board.During timing, full if there are data to want also to be added in this space synchronously again up to the space, just to carry out when perhaps being timed to synchronously, success synchronously or running fire are all failed for three times, then delete timer, empty the data of storing in this space.Data in synchronization repeats if desired, then goes to cover the data of front with the data of back.

The detailed process of this flow chart is as follows:

Step 5001: have data to need synchronously;

Step 5002: timer is set;

Step 5003: judge whether the synchrodata district has data, if, enter step 5004, if not, enter step 5011;

Step 5004: will data in synchronization be added in the synchrodata district,, cover the data of front with the data of back to the synchrodata of same port;

Step 5005: whether meet the full or timer in synchrodata district then, if, enter step 5006, if not, enter step 5010;

Step 5006: the content synchronization in synchrodata district is arrived slave board;

Step 5007: whether send success, if, enter step 5008, if not, enter step 5009;

Step 5008: the deletion timer empties the data field;

Step 5009: retransmit three times, finally send successfully still transmission failure and all enter step 5008;

Step 5010: return;

Step 5011: will data in synchronization be added in the synchrodata district;

Step 5012: whether need a plurality of sync packet packings are sent, if, enter step 5013, if not, enter step 5006;

Step 5013: timer is set and returns.

Fig. 6 and Fig. 7 are the described message Synchronous Processing of embodiment of the invention flow charts, the synchronous handling process of message is: to mainboard, if the host-standby communication link is normal, then whether the comparison message has been received and has been sent three times when mainboard is received message, and to agreement is duplicate message, can consider to reduce the host-standby communication amount to this situation, directly not carry out synchronously, otherwise it is synchronous then to carry out message; To slave board, if receive the message that mainboard is synchronous, the literary composition of then receiving telegraph is handled, if slave board is handled according to protocol logic, discovery need be simulated these messages, then directly carries out simulation process at slave board according to protocol logic.

Wherein, Fig. 6 is the described mainboard message of an embodiment of the invention Synchronous Processing flow chart, and detailed process is as follows:

Step 601: judge whether active and standby communication link is normal, if, enter step 602, if not, enter step 604;

Step 602: whether the message that judgement is received repeats and has sent three times, if, enter step 604, if not, enter step 603;

Step 603: send sync message;

Step 604: return.

Wherein, Fig. 7 is the described slave board message of an embodiment of the invention Synchronous Processing flow chart, and detailed process is as follows;

Step 701: receive sync message;

Step 702: the receiving literary composition is handled;

Step 703: judge whether agreement needs to continue the simulation duplicate message, if, enter step 704, if not, enter step 705;

Step 704: timing simulation message;

Step 705: return.

The present invention proposes and start synchronously, synchronously and the synchronous protocol synchronization processing method of message in time, the agreement discontinuity problem when this method has effectively solved active and standby the switching has guaranteed the consistency of active and standby protocol data simultaneously.

Claims (10)

1, the method for data synchronization of mainboard and slave board in a kind of communication system is characterized in that, comprises the steps:
(1) need to determine the synchronous non-configuration data relevant with communication protocol;
(2),, will need synchronous non-configuration data on the mainboard synchronously to slave board then by slave board log-on data synchronizing process if slave board starts in running;
(3) detect the situation of change that needs synchronous non-configuration data on the mainboard, if in system's running, need synchronous non-configuration data to change on the mainboard, then start synchronizing process by mainboard, packing data is arrived the synchrodata memory block, the synchrodata memory block is full or timer is in time synchronous to then carrying out, with the non-configuration data that changes synchronously to slave board.
2, the method for claim 1 is characterized in that, further comprises:
(4) detect the message situation that mainboard is received, if new message then is synchronized to slave board with this message data.
3, the method for claim 1 is characterized in that:
Described step (1) further comprises: determine the synchronous configuration data relevant with communication protocol of needs;
Described step (2) further comprises: if slave board starts, then initiate data synchronization process by slave board, will need synchronous configuration data synchronously to slave board on the mainboard;
Described step (3) further comprises: if slave board is on the throne, and need synchronous configuration data to change on the mainboard, then by mainboard with the configuration data that changes synchronously to slave board.
4, the method for claim 1 is characterized in that, described step (2) comprising:
(21) slave board sends a synchronization request to mainboard, comprises a sequence number in this request;
(22) mainboard returns a reply data, in this reply data described sequence number is taken back, and is comprised an end mark, and this flag set is represented same EOS, and set does not represent that the data needs are synchronous in addition;
(23) after slave board is received the response data of mainboard feedback, judge whether sequence number is consistent, if consistent, then according to the corresponding data on the reply data renewal slave board, and it is determine whether next time synchronization request, if inconsistent then abandon re-send request may according to the end mark in the reply data;
(24) mainboard is when data sync finishes, in reply data with end mark set.
5, method as claimed in claim 4 is characterized in that, described step (21) comprising:
(211) to slave board, system start-up then is provided with a request timer, and this timer then back sends synchronization request to mainboard;
(212) after slave board sends the synchronization request success, create this request timer again, receive the reply data of mainboard at slave board after, delete this request timer;
(213) after slave board sends the synchronization request failure, create an overtime timer;
(214) described request timer or overtime timer then after, send current synchronization request by slave board.
6, method as claimed in claim 5 is characterized in that, step (23) is described to be determined whether to comprise next time synchronization request according to the end mark in the reply data:
Judge the whether set of end mark of reply data,, continue to the new transmission synchronization request of mainboard if not set then increases progressively current SYN; If set then stops to send synchronization request.
7, the method for claim 1 is characterized in that, described step (3) comprising:
(31) a synchrodata memory block is set, and a timer is set;
(32) start when synchronous at mainboard, start described timer, and will need data in synchronization to be sent to described synchrodata memory block;
(33) during timer regularly,, then it is continued to be sent to described synchrodata memory block if need data in synchronization in addition;
(34) full in space, described synchrodata memory block, or timer then after, by mainboard with the data sync in the described synchrodata memory block to slave board, and upgrade corresponding data by slave board;
(35) delete this timer, and empty the synchronized data in the described synchrodata memory block.
8, method as claimed in claim 7 is characterized in that, in the described step (33), if the follow-up data that are sent in the described memory block repeat with the data of having stored, then uses follow-up data to cover previous data.
9, method as claimed in claim 7 is characterized in that, will need data in synchronization to be sent to the step of synchrodata memory block described in described step (32), (33), is a plurality of synchrodatas to be packed send together.
10, method as claimed in claim 2 is characterized in that, described step (4) further comprises:
After slave board was received the synchronous message of mainboard, the literary composition of receiving telegraph was handled, if slave board according to protocol logic, when discovery need be simulated message, then directly carries out simulation process at slave board according to protocol logic.
CNB2006100721547A 2006-04-14 2006-04-14 Data synchronization method between the main board and spare board in the communication system CN100466545C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2006100721547A CN100466545C (en) 2006-04-14 2006-04-14 Data synchronization method between the main board and spare board in the communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2006100721547A CN100466545C (en) 2006-04-14 2006-04-14 Data synchronization method between the main board and spare board in the communication system

Publications (2)

Publication Number Publication Date
CN101056195A CN101056195A (en) 2007-10-17
CN100466545C true CN100466545C (en) 2009-03-04

Family

ID=38795820

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2006100721547A CN100466545C (en) 2006-04-14 2006-04-14 Data synchronization method between the main board and spare board in the communication system

Country Status (1)

Country Link
CN (1) CN100466545C (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478435B (en) 2009-01-20 2011-01-12 杭州华三通信技术有限公司 Topology collecting method for stacking system and dual control board equipment
CN101714916B (en) 2009-11-26 2013-06-05 华为数字技术(成都)有限公司 Method, equipment and system for backing up
CN104580488B (en) * 2015-01-20 2018-03-23 株洲南车时代电气股份有限公司 A kind of information synchronization method and system
CN104683486B (en) * 2015-03-27 2018-07-24 新华三技术有限公司 Method, apparatus, the distributed system of synchronization message are handled in distributed system
CN105338006B (en) * 2015-12-15 2018-05-29 烽火通信科技股份有限公司 The method of callee side Session Initiation Protocol stack session status Backup and Restore in IMS systems

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041066A (en) * 1997-01-09 2000-03-21 Fujitsu Limited Method of synchronization status message processing in transmission apparatus
CN1437348A (en) * 2002-02-04 2003-08-20 深圳市中兴通讯股份有限公司 Real-time synchronizing method for data in both main and spare board in communication system
CN1725658A (en) * 2004-07-21 2006-01-25 中兴通讯股份有限公司 Real-time data base main standby synchronous method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041066A (en) * 1997-01-09 2000-03-21 Fujitsu Limited Method of synchronization status message processing in transmission apparatus
CN1437348A (en) * 2002-02-04 2003-08-20 深圳市中兴通讯股份有限公司 Real-time synchronizing method for data in both main and spare board in communication system
CN1725658A (en) * 2004-07-21 2006-01-25 中兴通讯股份有限公司 Real-time data base main standby synchronous method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"面向通信领域的主备倒换与数据同步技术". 何先波,李志蜀,唐宁九,殷锋,吴云波.计算机应用,第25卷第10期. 2005
"面向通信领域的主备倒换与数据同步技术". 何先波,李志蜀,唐宁九,殷锋,吴云波.计算机应用,第25卷第10期. 2005 *

Also Published As

Publication number Publication date
CN101056195A (en) 2007-10-17
CN100466545K3 (en)

Similar Documents

Publication Publication Date Title
US7406050B2 (en) Simulation and test system for at least one item of equipment on an AFDX network
CN103199972B (en) The two-node cluster hot backup changing method realized based on SOA, RS485 bus and hot backup system
US5049873A (en) Communications network state and topology monitor
Cristian Synchronous atomic broadcast for redundant broadcast channels
CN101425961B (en) Method for implementing link state database synchronization, router, circuit board and main control board
DE602005002927T2 (en) Time synchronization device and method and corresponding products
CN100555948C (en) A kind of switching equipment of in the stack exchanger system, being coupled of being used for
CN1649341B (en) Stackable routers employing a routing selecting protocol
US5430730A (en) Method for building a sub-network in a distributed voice messaging system
CN102413046B (en) Method for forwarding flow by means of virtual router redundancy protocol backup set and equipment
CN1980192B (en) Non-stop forwarding in a multi-chassis router
EP0674263B1 (en) Asynchronous remote data copying
US7035264B2 (en) Communication network system and method for synchronously controlling path connection
CN101160836B (en) Redundancy protection method for bridge mode resilient packet ring
CA1313561C (en) Communications network state and topology monitor
CN101907879B (en) Industrial control network redundancy fault-tolerant system
Amir et al. Membership algorithms for multicast communication groups
CN104320459B (en) A kind of node administration method and device
CN100558055C (en) Reduce the method and the router of continuous duration of error smoothness rebooting status
CN101136900B (en) Fast transparent fault shift device and implementing method facing to service
CN101164264B (en) Method and device for synchronising two bus systems, and arrangement consisting of two bus systems
CN101499976B (en) Stack manager protocol with automatic set up mechanism
CN101595669B (en) Method and device for exchanging information for facilitating synchronization of time network
CN100527716C (en) Method and gateway equipment for resuming service after switching status of main/standby gateway device
CN100571115C (en) A kind of method for synchronous and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
EXPY Termination of patent right or utility model
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20090304

Termination date: 20150414