WO2012167710A1 - Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes - Google Patents

Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes Download PDF

Info

Publication number
WO2012167710A1
WO2012167710A1 PCT/CN2012/076296 CN2012076296W WO2012167710A1 WO 2012167710 A1 WO2012167710 A1 WO 2012167710A1 CN 2012076296 W CN2012076296 W CN 2012076296W WO 2012167710 A1 WO2012167710 A1 WO 2012167710A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
node
subnet
processing
network
Prior art date
Application number
PCT/CN2012/076296
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 WO2012167710A1 publication Critical patent/WO2012167710A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the invention relates to a distributed network exception processing technology, in particular to a method and system for service backup in a network with heterogeneous nodes. Background technique
  • P2P Peer-to-Peer
  • peer-to-peer networking technology interconnects nodes on the network equally to form a distributed peer-to-peer network.
  • Each host node acts as both a client and a server.
  • the P2P technology enables peer-to-peer connections between nodes to share resources and exchange resources.
  • the shared resources include storage resources, computing resources, and network resources. Due to the decentralized and easy-to-scale nature of P2P technology, it is widely used in many technical fields on the Internet.
  • the P2PSIP Working Group of the Internet Engineering Task Force (IETF) defined the first Resource Location And Discovery (RELOAD) for P2P technology.
  • FIG. 1 is a schematic diagram of a distributed service network architecture of the prior art.
  • the peer A and the peer D belong to the device vendor 1; the peer B and the peer E belong to the device vendor 2; C and peer F belong to equipment vendor 3, and all peers A to F form a homogeneous distributed service network 14 to jointly complete the control functions of the core network services, such as: user node access, session control And the triggering of the contracted business.
  • each user is assigned a peer as a service master node, also called a responsible node, according to a pre-configured network algorithm.
  • VoIP Voice over Internet Protocol
  • SIP Session Initiation Protocol
  • PPSP Association Peer to Peer Streaming Protocol
  • Peer-to-peer uses P2P protocol to implement related data access and message routing, such as RELOAD protocol.
  • An implementation manner is to select another peer in a distributed network for a peer, that is, a node, responsible for data and services, and when the primary peer is down, enable the standby peer to take over the master.
  • heterogeneous nodes in actual operation, there may be many heterogeneous nodes in a distributed network.
  • the heterogeneous nodes here refer to nodes of different vendors, or nodes of the same manufacturer but different versions.
  • the service implementation of these nodes may be different. This will result in the conversion of private data when the service is backed up between the heterogeneous nodes.
  • the overhead is large and the implementation is complicated.
  • a node selects its successor or predecessor node as its standby node for storing data and processing traffic according to the established network algorithm.
  • Peer A might choose Peer B as the standby node.
  • Figure 2 is a schematic diagram of the process of implementing service backup in the distributed service network of the prior art.
  • the peer A of the device 1 selects the peer B of the device 2 as the standby node.
  • the peer A receives the session request from the calling user, it performs session processing and updates the user status to the local user data, and simultaneously backs up the user data and its service processing status to the peer B, and each subsequent user A business process state backup is required when the business process status changes.
  • the service processing method and data structure may be different. Therefore, the service backup needs to be converted between the two peers. The cost of business backup is very large, and it is difficult to achieve, and the performance is reduced. Summary of the invention
  • the main purpose of the embodiments of the present invention is to provide a method and system for service backup in a network with heterogeneous nodes, which can effectively solve the problem that distributed networks have heterogeneous nodes.
  • the problem of difficulty in backup is to provide a method and system for service backup in a network with heterogeneous nodes, which can effectively solve the problem that distributed networks have heterogeneous nodes. The problem of difficulty in backup.
  • the embodiment of the present invention provides a method for service backup in a network with heterogeneous nodes, where the method includes:
  • the generated service status information is backed up to other nodes of the subnet to which the service belongs, and the service processing status information is recorded in the user data.
  • the method further includes: when the service active node that is processing the service changes, the new The service primary node sends the service message to the node in the service subnet to which the original service primary node belongs according to the service processing status information in the user data to continue processing.
  • the service active node that is processing the service changes, specifically: the original service primary node fails, or the newly joined network node takes over the original service primary node to process the service;
  • the new service active node sends the service message to the node in the service subnet to which the original service primary node belongs, and the method further includes: after the original service primary node fails, the new service active node is from the data storage.
  • the node obtains user data, and sends the service message to the service backup node according to the service processing status information recorded in the user data to continue processing; when the node newly joining the network takes over the original service main node to process the service, the new service
  • the active node obtains user data from the data storage node, and sends the service message to the original service active node to continue processing according to the service processing status information recorded in the user data.
  • the establishment of the service subnet is specifically in a distributed peer-to-peer network, or a separate subnet; and/or,
  • the method further includes: when the new node joins, sending a request to join the service subnet, acquiring the industry Basic information of the subnet, complete the joining process.
  • the node with the same attribute is specifically: a node with the same processing manner for the same service function; or a node with the same service state information for the same service state.
  • the service status information that is generated is backed up to other nodes of the service subnet, including:
  • the service user node After the service primary node receives the service request message, the service user node obtains the user data from the data storage node. When the user does not have the ongoing service, the service primary node selects the service standby node from the service subnet to which it belongs. The service status information is backed up to the service standby node, and the updated service processing status information is saved to the user data, where the service processing status information includes: whether the user has an ongoing service, and the service is used for the primary use. Node information and alternate node information.
  • the embodiment of the present invention further provides a system for backing up services in a network with heterogeneous nodes, where the system includes: a service subnet composed of the same attribute node; the service subnet includes: a service active node and others Node, where,
  • the service active node is configured to back up the generated service status information to other nodes of the service subnet in the process of processing the service, and record the service processing status information into the user data.
  • the system further includes: a new service active node, configured to: when the service active node that is processing the service changes, send the service message to the original service active node according to the service processing status information in the user data.
  • the nodes in the subnet to which the service belongs continue to process.
  • the system further includes: a newly added node, configured to send a service subnet request, obtain basic information of the service subnet, complete the joining process, and take over the ongoing service, according to the service processing in the user data. Status information, forwarding the service message to the primary node or the standby node.
  • the node with the same attribute is specifically: for the same service function, the processing manner is the same Node; or a node with the same business status information for the same business status.
  • the method and system for service backup in a network with heterogeneous nodes provided by the embodiments of the present invention, by establishing a service subnet composed of the same attribute node; during the process of processing the service by the service main node, the generated service status information is backed up Go to other nodes of the subnet of the service and record the business process status information to the user data.
  • the nodes of the same attribute can be formed into a service subnet, such as service processing and backup, which avoids the conversion of private data between heterogeneous nodes, and reduces the overhead of service backup without affecting the processing process of the peer network service. And implementation complexity, improve system performance.
  • FIG. 1 is a schematic diagram of a prior art distributed service network architecture
  • FIG. 2 is a schematic flowchart of a service backup of a distributed service network in the prior art
  • FIG. 3 is a schematic flowchart of a method for backing up a service in a network with heterogeneous nodes according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a peer device joining a network according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a backup process of a new session service according to a specific embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of network adjustment when a peer device fails according to a second embodiment of the present invention
  • FIG. 7 is a schematic diagram of an in-process service processing flow when a third peer device fails according to a specific embodiment of the present invention
  • FIG. 8 is a schematic diagram of an in-process service processing process when a new peer device joins according to a specific embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a system for service backup in a network with heterogeneous nodes according to an embodiment of the present invention. detailed description
  • the basic idea of the embodiment of the present invention is: establishing a service subnet composed of the same attribute node; During the processing of the service by the node, the service owner backs up the generated service status information to other nodes of the service subnet, and records the service processing status information into the user data.
  • FIG. 3 is a schematic flowchart of a method for backing up services in a network with heterogeneous nodes according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps:
  • Step 301 Establish a service subnet composed of the same attribute node.
  • the establishment of the service subnet is specifically in a distributed peer-to-peer network or an independent subnet.
  • the nodes of the same attribute are specifically: nodes that are processed in the same manner for the same service function; or nodes that have the same service state information for the same service state.
  • the same attribute node may be the same device vendor or a node with the same version of the business program.
  • the method further includes: when the new node joins, sending a request to join the service subnet, acquiring basic information of the service subnet, and completing the joining process.
  • the new node join may be any moment in the method, regardless of whether the service subnet is established.
  • the basic information of the service subnet includes: access node information and an algorithm used in the service subnet.
  • the new node sends a join service subnet request to the subnet boot server, and also needs to send a join peer peer network request to the bootstrap server of the distributed peer network.
  • the new node can join the distributed peer-to-peer network first, or join the service subnet first, and can also send requests to join the distributed peer-to-peer network and service subnet.
  • the specific process of joining the network is consistent with the prior art, and generally includes: sending a join request to the access node, constructing a local routing table, migrating responsible for storing data, and sending a routing update request to other nodes in the network.
  • Step 302 During the process of processing the service by the service primary node, the service status information is backed up to other nodes of the service subnet, and the service processing status information is recorded into the user data.
  • the service active node is specifically: a node in the service subnet that is responsible for processing the service.
  • the backup mode includes: directly synchronizing the corresponding service state information, or forwarding the service message to the backup process.
  • the backing up the service status information to the other nodes of the service subnet includes: obtaining, after the service primary node receives the service request message, the related user data from the data storage node, when the user does not have the ongoing service,
  • the service active node selects a service standby node from the service subnet to which it belongs, backs up the service state information to the service standby node, and saves the updated service processing state information to the user data, where
  • the service processing status information includes: whether the user has an ongoing service, and the active node information and the standby node information of the service.
  • the method further includes: determining, according to the user service status information saved in the user data, whether the user has an ongoing service.
  • the method further includes: when the service primary node that is processing the service changes, the new service primary node sends the service to the original service primary according to the service processing status information in the user data.
  • the nodes in the service subnet to which the node belongs continue to process.
  • the service active node that is processing the service changes, including: the original service primary node is invalid, or the newly added network node takes over the original service primary node to process the service.
  • the new service active node sends the service message to the node in the service subnet to which the original service primary node belongs, and the method further includes: after the original service primary node fails, the new service active node is from the data storage.
  • the node obtains the user data, and sends the service message to the service backup node according to the service processing status information recorded in the user data to continue processing; when the node newly joining the network takes over the original service main node to process the service, the new service is used for the main service.
  • the node obtains the user data from the data storage node, and sends the service message to the original service active node to continue processing according to the service processing status information recorded in the user data.
  • the distributed service network is the foregoing distributed peer-to-peer network
  • the peer device is a node in the network.
  • Step 401 The peer A sends a request to the known bootstrap server to access the distributed service network, and obtains basic information of the distributed service network.
  • the access node the algorithm used by the network, the supported service type, and the boot server of the service subnet;
  • Step 402 Peer A performs a process of joining a distributed service network.
  • the general procedure is: sending a join request to the access node, constructing a local routing table, migrating responsible for storing data, and sending a routing update request to other network nodes;
  • Step 403 The peer A sends a service subnet request to the subnet boot server to obtain basic information of the service subnet, such as an access node and an algorithm used by the network.
  • Step 404 Peer A performs a process of joining the service subnet.
  • the manner in which the peer A joins the service subnet is the same as the manner of joining the distributed service network.
  • the foregoing steps may have multiple embodiments, for example, the peer device performs steps 403-404 to join the service subnet, and then performs steps 401-402 to join the distributed service network; the distributed service network and the service subnet use.
  • the same boot server obtains the basic information of the distributed service network and the subnet to which the service subnet belongs in step 401.
  • the peer device registers with the service subnet boot server and directly obtains other nodes in the service subnet. Information, etc.
  • FIG. 5 is a schematic diagram of a backup process of a new session service according to a specific embodiment of the present invention.
  • the service master node first The data storage node of the user obtains user data, and determines whether the user has an ongoing service according to the user service status saved in the user data. If the user does not have an ongoing service, the service active node selects a service standby node from the service subnet to which the user belongs, and backs up the session processing state of the user to the service standby node, where The user's business status information is updated in the user data and the updated user data is saved to the user data storage node.
  • the specific steps are described as follows:
  • Step 501 the calling user sends a session initiation request message to the service active node A;
  • the service active node A includes: the distributed service network is a peer device designated by the user, for example: an access node of the user equipment; or the distributed service network is selected according to the configured network algorithm and policy.
  • the peer device for example: combines the user's unique identifier to generate a user ID using a hash algorithm of the network configuration, and then selects a peer device whose node ID is closest to the user ID as the user according to the configured policy.
  • Business master node for example: combines the user's unique identifier to generate a user ID using a hash algorithm of the network configuration, and then selects a peer device whose node ID is closest to the user ID as the user according to the configured policy.
  • Step 502 The service active node A obtains the user data from the user data storage node.
  • the service active node A and the user data storage node may be the same peer device or different peer devices.
  • Step 503 The service active node A determines, according to the acquired user data, that the calling user has no other ongoing services, and the peer node acts as the service processing node of the user, and initiates a request for the session of the calling user.
  • Step 504 The service active node A performs service standby node search according to the configuration of the service subnet, and selects the service standby node B as the standby node for the user service processing.
  • Step 505 The service active node A backs up the service processing status of the calling user to the service standby node B.
  • the service active node A and the service standby node B are peer devices with the same attributes.
  • the backup mechanism of the service processing state can be determined internally by the service subnet, for example, the corresponding memory state is directly synchronized, or the user's service message is forwarded and backed up.
  • Step 506 The service active node A records the service status of the user in the user data, and updates to the user data storage node.
  • the user service status includes: whether the user has an ongoing service; and the standby node information of the service when the service is in progress; or the active node information and the service of the service Use node information.
  • the user has an ongoing session, and the service primary node is A, and the service standby node is B.
  • Step 507 The service active node forwards the session initiation request of the calling user to the called side device.
  • the called side device is a service processing device of the called user, or a proxy device of the called user, or a called user equipment. This step completes the establishment of the session, starts the session business process, and also needs to back up the service status information during the process of the session service.
  • the service layer communication connection needs to be established first, and the peer network layer communication is performed. It is necessary to first establish a peer-to-peer network layer communication connection.
  • step 501 when the calling user equipment sends a session initiation request to the service active node A, the service layer communication connection between the calling user equipment and the service active node needs to be established first; When node A obtains user data from the user data storage node, it is necessary to first establish a peer-to-peer network layer communication connection between the service primary node A and the user data storage node.
  • the description of the steps in the embodiment of the present invention is omitted in the embodiment of the present invention as a communication rule between the user equipment and the peer device, the peer device, and the peer device.
  • FIG. 6 is a schematic flowchart of network adjustment when a peer device fails according to a second embodiment of the present invention.
  • a peer device of a distributed service network fails, for example: forced exit, unexpected downtime Network adjustment is needed to avoid user data loss caused by the failure of the peer device, and user service interruption.
  • the network adjustment includes: the service primary node is responsible for storing the user data migration, the user service node responsible for the service primary node is migrated, and the service standby node is responsible for backing up the user processing state of the backup.
  • the specific network adjustment steps are described as follows:
  • Step 601 The service active node A fails, and the user data stored by the node A and the responsible service need to be migrated to other nodes;
  • the service active node A fails: the service active node A device
  • the fault is caused by, for example: downtime, network disconnection, etc.; or the service active node A actively requests to exit the network.
  • the discovery manners of the other nodes include: the active discovery by other related nodes in the distributed service network, or the active service node A actively applying.
  • Step 602 The service primary node A failure information is notified to the related peer node of the distributed service network by using a route update message.
  • the routing update message is sent by the discovery node that is invalidated by the service active node A, or is actively sent by the service active node A.
  • the related peer node that receives the failure information includes: a data storage node that takes over the user data stored by the service primary node A; and a new service primary node C that takes over the service that the service primary node A is responsible for processing ; Responsible for backing up the service standby node B of the ongoing service backup handled by the service primary node A.
  • the selection of the new service active node C is completed by the existing distributed peer-to-peer network.
  • Step 603 The service active node C receives the route update notification, learns that the service active node A is invalid, updates the local routing table, and prepares to take over some or all services handled by the service active node A;
  • Step 604 The data storage node on the distributed service network receives the route update notification, and learns that the service active node A is invalid, and backs up the user data that the service primary node A is responsible for, to the new storage node.
  • Step 605 The service standby node B receives the route update notification, learns that the service active node A is invalid, updates the local routing table, and prepares to take over the ongoing service that the service active node A is responsible for processing;
  • Step 606 The service standby node B reselects a service standby node E from the service subnet to perform service processing state backup according to the backup policy of the distributed service network.
  • the service standby node B may also choose to not further back up the service state information backed up by the service standby node B according to the backup policy of the distributed service network. Step 607: If the service standby node B further selects the service standby node E to back up the service backed by the service standby node B, the service state information of the user is updated to the user data storage node.
  • the steps 603-605 have no strict sequence requirements and are determined by the implementation strategy of the distributed service network.
  • FIG. 7 is a schematic diagram of an in-process service processing process when a peer device fails according to a specific embodiment of the present invention.
  • a peer device in a distributed service network fails (such as forced exit, unexpected downtime)
  • the session request message that is responsible for the failed peer device is rerouted to a new service active node, and the new service active node queries the user data, and is saved according to the user service state information of the user data.
  • the user service standby node information is forwarded to the user service standby node, and the user service standby node continues to complete the session processing of the user.
  • the specific steps are described as follows:
  • Step 701 The service master node C learns that the service master node A is invalid, and takes over the service that the service master node A is responsible for processing;
  • this step is implemented in accordance with the specifications of the prior art.
  • Step 702 The service standby node B learns that the service active node A is invalid, and takes over the ongoing service that the service active node A is responsible for processing;
  • Step 703 The related device sends a session request/response message to the new service active node C.
  • the related device is specifically: the user terminal device, or a related device or a peer device on the user service processing path.
  • Step 704 the new service active node C obtains the updated user data from the user data storage node.
  • the new service active node C and the user data storage node are either the same peer device or different peer devices.
  • Step 705 The new service active node C determines according to the obtained updated user data.
  • the user has other services in progress, and the service active node of the user is B, and the standby service node is E;
  • the updated user data is specifically: user data updated in step 607 in the foregoing second embodiment.
  • Step 706 The new service active node C forwards the received session request/response message to the service standby node B.
  • the service status information of the user in the user data may still be: the service primary node of the user is A, the standby service node.
  • the new service master node C can directly forward the received session request/response message to the service standby node B according to the locally received information that the service primary node A is invalid.
  • Step 707 The service standby node B continues to process the ongoing service of the user as the service primary node.
  • Step 708 The service standby node B backs up the service processing state of the user to the service standby node E that belongs to the same service subnet.
  • Step 709 After the service standby node B completes the user service processing, the new service active node C returns a session request/response message.
  • Step 710 The new service active node C forwards the session request/response message to the related device. Further, in steps 709-710, the service standby node B can also directly send the session request/response message to the related device.
  • FIG. 8 is a schematic diagram of a process of performing an in-progress service when a new peer device joins according to a specific embodiment of the present invention.
  • the new join The peer device will take over the service processing of a part of users of other peer devices, and when the session request message of the part of the user is routed to the newly added peer device, the newly added peer The device obtains information about the user's service status in the user data.
  • the user session request message is forwarded to the original service active node of the user.
  • Step 801 The peer node C completes the distributed service network joining, and according to the network algorithm and strategy configured by the network, takes over part of the service processing that the service primary node A is responsible for, and takes over some of the data that other related peer nodes are responsible for storing;
  • Step 802 The related device sends a session request/response to the newly added service active node C.
  • the related device includes: a user terminal device, or a related device or a peer device on the user service processing path.
  • Step 803 the newly added service active node C acquires user data from the user data storage node
  • the newly added service active node C and the user data storage node are either the same pair of device devices or different peer devices.
  • Step 804 the newly added service active node C determines that the user has other services in progress according to the obtained user data, and the service active node of the user is A, and the standby service node is B;
  • Step 805 The newly added service active node C forwards the received session request/response message to the service active node A;
  • Step 806 the service active node A continues to process the ongoing service of the user;
  • Step 807 the service active node A backs up the service processing state of the user to the service standby node B belonging to the same service subnet;
  • Step 808 the service master node A completes the user service processing, and the newly added service main node C returns a session request/response message;
  • Step 809 the newly added service active node C forwards the session request/response to the related device.
  • the service master node may further send the session request/response message directly to the related device.
  • FIG. 9 is a schematic structural diagram of a system for service backup in a network with heterogeneous nodes according to an embodiment of the present invention.
  • the system is located in a distributed peer-to-peer network, including: a service subnet composed of the same attribute node;
  • the service subnet in FIG. 9 is located in a distributed peer-to-peer network, but the service subnet can also be located in a separate subnet. Therefore, the service subnet is used in the system of the embodiment of the present invention.
  • the location does not need to be specifically defined, and may be located in a distributed peer-to-peer network or in another network. This embodiment illustrates that the service subnet is only located in a distributed peer-to-peer network.
  • the service subnet includes: a service active node 91 and other nodes 92, wherein the service active node 91 is configured to back up the generated service state information to the service subnet in the process of processing the service. On other nodes 92, the business process status information is recorded in the user data.
  • the node with the same attribute is specifically: a node with the same processing manner for the same service function; or a node with the same service state information for the same service state.
  • the same attribute node may be the same device vendor or a node with the same version of the service program.
  • the service active node 91 is specifically: a node in the service subnet that is responsible for processing the service.
  • the backup mode includes: directly synchronizing the corresponding service state information, or forwarding the service message to the backup process.
  • the backing up the service state information to the other nodes 92 of the service subnet includes: after the service primary node 91 receives the service request message, acquiring related user data from the data storage node, when the user does not have the ongoing service.
  • the service active node 91 selects one other node 92 from the service subnet to serve as a service standby node, backs up the service state information to the service standby node, and saves the updated service processing state information to the user.
  • the service processing status information includes: whether the user has The business in the row, as well as the primary node information and alternate node information of the service. Further, after the acquiring the related user data, the method further includes: determining, according to the user service status information saved in the user data, whether the user has an ongoing service.
  • the system further includes: a newly added node 93, configured to send a service subnet request, obtain basic information of the service subnet, complete the joining process, and after taking over the ongoing service, according to the user data.
  • the service processes the status information and forwards the service message to the active node or the standby node.
  • the new node join can be any time, that is, regardless of whether the service subnet is established.
  • the basic information of the service subnet includes: an access node information and an algorithm used in a service subnet.
  • the newly joined node 93 sends a join service subnet request to the subnet boot server, and also needs to send a join peer peer network request to the bootstrap server of the distributed peer network.
  • the newly added node 93 can join the distributed peer-to-peer network first, or join the service subnet first, and simultaneously send requests to join the distributed peer-to-peer network and service subnet.
  • the specific process of joining the network is consistent with the existing technology, and generally includes: sending a join request to the access node, constructing a local routing table, migrating responsible for storing data, and sending a routing update request to other nodes in the network.
  • system further includes: a new service active node 94, configured to: when the service active node that is processing the service changes, send the service message to the original service owner according to the service processing status information in the user data. The processing continues with the nodes in the service subnet to which the node 91 belongs.
  • the service active node that is processing the service changes, including: the original service primary node 91 is invalid, or the node 93 newly joining the network takes over the original service primary node 91 to process the service.
  • the new service active node 94 sends the service message to the node in the service subnet to which the original service active node 91 belongs, and the processing includes: After the original service active node 91 fails, the new service active node The user data is obtained from the data storage node, and the service message is sent to the service backup node according to the service processing status information recorded in the user data to continue processing; when the newly joined node 93 takes over the original service active node 91 to process the service. Rear, The new service active node 94 acquires the user data from the data storage node, and sends the service message to the original service active node 91 to continue processing according to the service processing status information recorded in the user data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé de sauvegarde de services dans un réseau à nœuds hétérogènes, consistant : à établir un sous-réseau de services comprenant des nœuds avec des attributs identiques ; et lors du traitement d'un service, à sauvegarder au moyen d'un nœud maître de service, les informations d'état de service générées dans un autre nœud du même sous-réseau de services, et à enregistrer les informations d'état de traitement de service dans des données utilisateur. L'invention concerne également un système de sauvegarde de services dans un réseau à nœuds hétérogènes. Le procédé et le système précités permettent d'éviter la conversion de données privées entre des nœuds hétérogènes, de réduire le surdébit et la complexité d'implantation d'une sauvegarde de service sans affecter le flux de traitement de service du réseau pair à pair et d'améliorer la performance système.
PCT/CN2012/076296 2011-06-10 2012-05-30 Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes WO2012167710A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110155426.0A CN102821118B (zh) 2011-06-10 2011-06-10 一种具备异构节点的网络中业务备份的方法和系统
CN201110155426.0 2011-06-10

Publications (1)

Publication Number Publication Date
WO2012167710A1 true WO2012167710A1 (fr) 2012-12-13

Family

ID=47295474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076296 WO2012167710A1 (fr) 2011-06-10 2012-05-30 Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes

Country Status (2)

Country Link
CN (1) CN102821118B (fr)
WO (1) WO2012167710A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103944974B (zh) * 2014-04-02 2017-10-17 华为技术有限公司 一种协议报文处理方法、控制器故障处理方法及相关设备
CN109639800B (zh) * 2018-12-14 2022-03-22 深信服科技股份有限公司 一种tcp连接处理方法、装置、设备及存储介质
CN112101590A (zh) * 2020-09-07 2020-12-18 中国人民解放军海军工程大学 一种基于混合对等网的船舶远程维修信息管理系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453754A (zh) * 2008-10-24 2009-06-10 中国移动通信集团山东有限公司 一种数据备份的方法和装置
WO2010071884A2 (fr) * 2008-12-19 2010-06-24 Watchguard Technologies, Inc. Groupe de dispositifs de sécurité de réseau à autosurveillance
CN101977124A (zh) * 2010-11-05 2011-02-16 山东中创软件工程股份有限公司 基于ZooKeeper技术的业务集群方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453754A (zh) * 2008-10-24 2009-06-10 中国移动通信集团山东有限公司 一种数据备份的方法和装置
WO2010071884A2 (fr) * 2008-12-19 2010-06-24 Watchguard Technologies, Inc. Groupe de dispositifs de sécurité de réseau à autosurveillance
CN101977124A (zh) * 2010-11-05 2011-02-16 山东中创软件工程股份有限公司 基于ZooKeeper技术的业务集群方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LIU, ZHENPENG: "Research on Selection Mechanisms for Web Services in Peer-to-Peer Networks", DOCTORAL DISSERTATIONS, 8 July 2010 (2010-07-08) *

Also Published As

Publication number Publication date
CN102821118A (zh) 2012-12-12
CN102821118B (zh) 2017-11-28

Similar Documents

Publication Publication Date Title
US7859992B2 (en) Router redundancy in data communication networks
JP5414807B2 (ja) ネットワークにおけるアドレス割り当て
WO2020063876A1 (fr) Procédé de migration d'ue, appareil, système et support d'informations
US20080098121A1 (en) P2p sip enabled multimedia network communication system
WO2020063412A1 (fr) Procédé, appareil et système de rétablissement de session pdu, et support de stockage
WO2019134648A1 (fr) Procédé et dispositif de mise en œuvre pour une migration de ressources de plan de commande, et entité de fonction de réseau
US10097460B2 (en) Routing in an communications network having a distributed S/PGW architecture
WO2008034353A1 (fr) Procédé, système et dispositif permettant d'établir une connexion entre homologues dans un réseau d'homologues
WO2023165277A1 (fr) Procédé de gestion de session, dispositif de communication et support d'enregistrement
WO2009094945A1 (fr) Procédé d'imagerie pour entité de décision de politique, élément de réseau de gestion et système de gestion
WO2019134649A1 (fr) Procédé et appareil de mise en œuvre pour une migration de ressource de plan de commande, et entité fonctionnelle de réseau
WO2016177056A1 (fr) Procédé, dispositif, et système de traitement de données pour une vidéoconférence
WO2018090386A1 (fr) Procédé, dispositif et système de traitement d'anomalies de modules nf
EP3095229B1 (fr) Procédé et noeuds pour la configuration d'un trajet de communication pour un service média
WO2009117946A1 (fr) Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition
PH12014502594B1 (en) Service node switching method and system
US20110078489A1 (en) Method, apparatus, and system for maintaining status of bootstrap peer
US20170353589A1 (en) Supporting hitless upgrade of call processing nodes in cloud-hosted telephony system
US9948726B2 (en) Reconstruction of states on controller failover
WO2012167567A1 (fr) Procédé pour activer un groupe de contrôleurs périphériques de session (sbc) et sbc
WO2012167710A1 (fr) Procédé et système de sauvegarde de services dans un réseau à nœuds hétérogènes
US9325599B2 (en) Methods for providing a status to devices in a distributed system
CN104660550A (zh) 一种在多服务器之间进行会话迁移的方法
US8493892B1 (en) Resolving conflicts in distributed systems
WO2012000366A1 (fr) Procédé de relais pour des données de service et système de nœud de relais

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

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

Country of ref document: EP

Kind code of ref document: A1