WO2013037318A1 - Procédé de traitement de données et nœud de traitement de données - Google Patents

Procédé de traitement de données et nœud de traitement de données Download PDF

Info

Publication number
WO2013037318A1
WO2013037318A1 PCT/CN2012/081456 CN2012081456W WO2013037318A1 WO 2013037318 A1 WO2013037318 A1 WO 2013037318A1 CN 2012081456 W CN2012081456 W CN 2012081456W WO 2013037318 A1 WO2013037318 A1 WO 2013037318A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
user
identifier
user identifier
data
Prior art date
Application number
PCT/CN2012/081456
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 WO2013037318A1 publication Critical patent/WO2013037318A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • a data processing method and a data processing node The present application claims priority to a Chinese patent application filed on September 16, 2011 by the Chinese Patent Office, the application number is 201110275291.1, and the invention name is "a data processing method and a data processing node". The entire contents of which are incorporated herein by reference.
  • the present invention relates to the field of communications technologies, and in particular, to a data processing method and a data processing node. Background technique
  • each node maintains user data corresponding to users within its own jurisdiction. This node is called the service node of each user in the jurisdiction.
  • the service node When the Serving/Service Node is overloaded, the user request sent by the user belonging to the service node's jurisdiction will be rejected by the service node. At this time, the peer network will start the backup node of the service node as a temporary. The service node handles the corresponding user request.
  • User A's service node is overloaded, and the upstream node (Upstream Node) of the service node and the backup node (Backup Node) of the service node have learned that the service node is overloaded, as shown in Figure 1.
  • a process flow diagram of processing a session establishment request of user A includes the following steps:
  • the upstream node of the service node of user A receives the session establishment request of user A.
  • the service control function (SCF) module of the upstream node receives the INVITE message of the user A.
  • the upstream node selects, according to a load balancing control algorithm, a backup node of the service node of user A as a node that temporarily provides a service;
  • the resource list function (RLF) module of the upstream node selects a backup node of the service node to provide service for user A according to the load balancing algorithm.
  • the backup node sets a flag on the user data corresponding to the user A.
  • the backup node detects that the service node of user A is overloaded.
  • the backup node sends a message with a high priority to the service node, and the requesting service node grants the permission to allow the backup node to become a temporary service node, and takes over the work of the service node for a period of time;
  • the service node receives the request of the backup node, the service node sets a flag (Flag) in the user data corresponding to the user A, and identifies that the data content of the user A is updated.
  • the tag may include address information of the backup node. If the service node has multiple backup nodes, the tag needs to be stored on multiple backup nodes at the same time. In particular, in some cases, an overloaded service node may not be able to respond to messages sent by the backup node in a timely manner.
  • the service node sends an acknowledgement message to the backup node.
  • the service node sends a confirmation message to the RLF module of the backup node, and the RLF module of the backup node forwards the received confirmation message to the SCF module of the backup node.
  • the backup node serves as the service node of user A to provide service for user A.
  • the backup node sends a session establishment request to the user A, receives the confirmation message returned by the user A, and sends the received confirmation message to the upstream node of the service node.
  • the backup node stores the updated user data of user A in a local database.
  • the user data must be modified (for example, the user's status and other information), that is, each time the user's request is processed, the service node that has been overloaded is still processed, but the processed message is The user's request message becomes a message that sets the tag, so it can be seen that such a processing does not relieve the load of the service node.
  • the registration server when a node joins a P2P network, the registration server assigns each node a unique node that is unique to the entire network, and the node ID can be determined according to the user identifier corresponding to the user that the node needs to govern, for example, If the user identifier corresponding to the user to be governed by the node is 1 100, the registration server takes the user identifier as an input value, and obtains a random number through a hash function, and the registration server can use the random number as the node identifier of the node.
  • the node identifier of the newly added node is determined according to the user identifier corresponding to the user under the jurisdiction of the service node, so that the new join is performed.
  • the node becomes the precursor node of the service node, thereby being able to share the partial load of the overloaded service node.
  • the Bootstrap Node is used to find an Admitting Node that governs the user that needs to be governed, and the acknowledgment node is the original service that administers the user within the scope of the user identification. node.
  • the new join node requests the acknowledgement node for user data of the user who needs its own jurisdiction to alleviate the load of the acknowledged node. Since it is recognized that the user data saved at this time may not be the latest user data, the newly joined node needs to obtain the latest user data from the backup node of the acknowledgement node. As shown in FIG. 2, in the prior art, when a new node is added, the data processing flow diagram includes the following steps:
  • the guiding node After the newly joined node joins the P2P network, the guiding node sends the user identifier corresponding to the user under its jurisdiction to find the acknowledgment node that administers the user;
  • the newly joined node sends a connection request to the identified acknowledgement node through the bootstrap node, and establishes a connection with the acknowledged node;
  • S204 ⁇ S207 the new joining node sends an incoming network request to the acknowledgment node, and the acknowledgment node confirms that the newly joined node will be responsible for some users under its jurisdiction, returns a response message to the new joining node, and simultaneously starts transmitting the new joining node to the new joining node.
  • the acknowledgment node sends the stored data to the newly joined node by sending the stored message to the newly joined node.
  • the newly added node detects a tag in the received user data, indicating that the received user data is not up-to-date, and the tag carries the address information of the backup node that stores the user data.
  • the newly joining node sends a network access request to the backup node, and requests the backup node to transmit the tagged user data, and after receiving the network access request, the backup node returns a network access request response message to the newly joined node;
  • the backup node after receiving the network access request of the newly joined node, the backup node also detects the node identifier of the newly joined node to confirm that the newly joined node will be responsible for some users under the service node, and after the detection is passed, The newly joined node returns a response message of the incoming request;
  • the backup node transmits the user data newly added by the node request to the newly joined node
  • the backup node may transmit the user data requested by the newly added node, that is, the user data modified by the service node during the overload state, to the newly joined node by storing the message, and the newly joined node receives the corresponding user data after receiving the corresponding user data.
  • a response message to store the message is returned to the backup node.
  • the newly added node updates routing information of other related nodes, and officially joins the P2P network.
  • the newly added node updates the routing information of the relevant node according to the P2P algorithm adopted by the P2P network.
  • the newly added node first obtains the user data of the user who needs to be self-administered on the service node that has been overloaded, and obtains the latest user data according to the mark in the user data to the backup node, thereby being visible here.
  • the newly added node needs to obtain part of the user data from the already overloaded service node, which increases the load of the overloaded service node to some extent.
  • the embodiment of the invention provides a data processing method and a data processing node, which are used to process user data when the service node is in an overload state, thereby achieving the purpose of reducing the load of the service node.
  • An embodiment of the present invention provides a data processing method, in which a user identifier and user information of each user that is managed by a service node are stored in a backup node, where the user information includes user data and is used to identify that the user data has been modified last time.
  • the version identifier the method includes: When the serving node is in an overload state, the backup node receives a session establishment request sent by an upstream node of the service node, where the session establishment request carries a first user identifier of a user who needs to establish a session;
  • the backup node modifies user data in the user information corresponding to the first user identifier
  • An embodiment of the present invention provides a data processing node, including:
  • a storage unit configured to store user identifiers and user information of each user that is managed by the service node, where the user information includes user data and a version identifier used to identify that the user data was last modified;
  • a first receiving unit configured to: when the serving node is in an overload state, receive a session establishment request sent by an upstream node of the service node, where the session establishment request carries a first user identifier of a user who needs to establish a session;
  • a modifying unit configured to modify user data in the user information corresponding to the first user identifier
  • an update unit configured to update a version identifier in the user information corresponding to the first user identifier.
  • An embodiment of the present invention provides another data processing method, in which a user identifier and user information of each user that is managed by a service node are stored in a backup node, where the user information includes user data and is used to identify that the user data is last modified. Version identification, the method includes:
  • the backup node When the serving node is in an overload state, the backup node receives a network access request of the newly joined node, where the network access request carries the node identifier of the newly joined node, and the first corresponding to the user under the new joining node a set of user identifiers, where the newly joined node is a precursor node of the service node;
  • the newly joined node For each user identifier in the first set of user identifiers, the newly joined node selects the latest user data according to the version identifier in the user information corresponding to the user identifier, and stores the latest user data.
  • An embodiment of the present invention further provides another data processing node, including:
  • a storage unit configured to store user identifiers and user information of each user that is managed by the service node, where the user information includes user data and a version identifier used to identify that the user data was last modified;
  • a first receiving unit configured to: when the serving node is in an overload state, receive a network access request of a newly joined node, where the network access request carries a node identifier of the newly joined node, and a user that is newly administered by the node Corresponding a first user identifier set, where the newly joined node is a precursor node of the service node;
  • the first sending unit is configured to send the user information corresponding to the user identifier in the first user identifier set to the new joining node corresponding to the node identifier.
  • the backup node when the service node is in an overload state, receives a session establishment request sent by the upstream node of the service node, where the session establishment request carries the user who needs to establish a session.
  • the user identifier the backup node modifies the corresponding user data according to the user identifier, and updates the version identifier of the user data corresponding to the user identifier, so that in the process of processing the user data, the backup node does not need to invite the service node.
  • the backup node when the serving node is in an overload state, receives the network access request sent by the newly joined node, and the backup node according to the user corresponding to the user that the newly joined node carries in the network access request
  • the identifier, the user information corresponding to the user identifier is sent to the new joining node, and the new joining node is configured to read the latest user data corresponding to the user identifier according to the version identifier in the user information, so that the newly joined node directly joins the network.
  • FIG. 1 is a schematic diagram of a processing flow for processing a session establishment request of user A in the prior art
  • FIG. 2 is a schematic diagram of a data processing flow when a new node joins in the prior art
  • FIG. 3 is a schematic flowchart of an implementation process of a data processing method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a data processing process in a session establishment process according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a data synchronization process when a service node is in a normal state in the prior art
  • FIG. 6 is a schematic structural diagram of a network for data synchronization according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a data synchronization process after a service node is restored from an overload state to a normal state according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a data processing flow when a new node joins according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a data processing node according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of an implementation process of another data processing method according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another data processing node according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a data processing method and a data processing node.
  • the backup node of the service node When the service node of the user is overloaded, in order to reduce the load of the service node, the backup node of the service node temporarily becomes the service node of the user. In the process of processing the user data, the backup node inevitably needs to modify the user's use. Household data. In order to reduce the load of the service node as much as possible, and reduce the number of signaling messages received by the service node, the backup node may not notify the service node after modifying the user data, and when the backup node detects that the service node recovers from the overload state to the normal state,
  • the user data version control mechanism is introduced in the embodiment of the present invention to synchronize the user data that has been modified to the service node. In order to ensure that the service node can always obtain the latest user data during the data synchronization process, the user data version control mechanism is introduced in the embodiment of the present invention.
  • the user data version control mechanism provided by the embodiment of the present invention is mainly completed by using the version identifier of the user data.
  • the user data provided by the embodiment of the present invention is referred to as user information.
  • the data structure of the user information includes two parts: a version identifier and user data.
  • the version identifier indicates the user information of the same user in the P2P network when the user data is last modified. If the value corresponding to the version identifier in one of the user information is larger, the user data in the user information is updated. The later the time, the newer the content.
  • Version ID User Data After the backup node has modified the user data in the user information, you need to update the version identifier in the user information. Specifically, you can update the version identifier according to the following formula:
  • SequencelD ⁇ SequencelD ⁇ + /) mod SequmcelD , where: SequencelD is the updated version identifier; ⁇ " ⁇ " ⁇ . "For the pre-update version identifier; for the preset value, for example, it can be set to 1; SequencelD ⁇ is the default, the maximum value of the version identifier.
  • the version identifier can determine the latest user information. With this user data version control, the uniqueness of the latest user data in the P2P network is guaranteed.
  • the service node when the service node cannot provide services for some users due to overload, the service node The backup node can update the user information autonomously, without requesting the service node to obtain the permission to modify the user information, thereby reducing the signaling interaction between the service node and the backup node in the overload state; meanwhile, the service node does not need to process the backup.
  • the signaling sent by the node saves the processing resources of the service node, thereby reducing the load of the service node.
  • the embodiment of the present invention provides a data processing method.
  • the user identifier and user information of each user that is managed by the service node are stored in the backup node, and the user information includes user data and a version identifier for identifying that the user data has been modified last time.
  • a schematic flowchart of an implementation process of a data processing method according to an embodiment of the present invention includes the following steps:
  • the backup node receives the session established by the upstream node of the service node.
  • the session establishment request carries a first user identifier of a user who needs to establish a session;
  • the backup node modifies user data in the user information corresponding to the first user identifier.
  • the backup node updates the version identifier in the user information corresponding to the first user identifier.
  • the data processing method may further include:
  • the backup node confirms that the first user identifier carried in the session establishment request is within the range of the user identifier corresponding to the user under its jurisdiction.
  • the calling user sends a session establishment request to the serving node, requesting to establish a session connection with the called user, and the calling node's service node initiates a P2P route searching process, and finds the called user's service node, and performs routing search.
  • the session establishment request of the calling user is forwarded to the upstream node of the service node of the called user. Since the upstream node has learned that the service node of the called user is overloaded, the upstream node determines according to a preset backup policy.
  • a backup node of the service node of the called user is sent, and the session establishment request of the calling user is sent to the determined backup node.
  • the data processing flow in the session establishment process is in the embodiment of the present invention. , including the following steps:
  • the upstream node of the serving node of the called user receives a session establishment request sent by the calling user, where the session establishment request carries the user identifier of the called user.
  • the session establishment request may be an INVITE message.
  • the upstream node of the service node of the called user determines a backup node of the service node of the called user according to the preset backup policy.
  • the upstream node of the service node of the called user forwards the received session establishment request to the determined backup node.
  • the backup node confirms that the user identifier carried in the received session establishment request is within the range of the user identifier corresponding to the user that is in its own jurisdiction, and the user data in the user information corresponding to the user identifier is modified, and the user corresponding to the user identifier is updated.
  • the version identifier in the information
  • the backup node serves as a temporary service node of the called user, and provides a service to the called user.
  • the backup node sends a session establishment request to the called user, and the called user returns an acknowledgement message to the upstream node of the service node through the backup node, and the called user establishes a session with the calling user.
  • the following application scenarios may exist:
  • the calling user calls the called user
  • the called user is being served by the serving node.
  • the called user establishes a session with other users, and is in a busy state.
  • the upstream node of the called user's service node forwards the session establishment request to the backup node of the serving node, Backup node is The user is called to provide the service, but the backup node does not know that the service node is processing the previous session establishment request of the called user.
  • the backup node and the service node provide services for the called user at the same time, and they do not know the latest of the called user.
  • the status for example, in the above case, for the serving node, the called user is in a busy state of the call, and for the backup node, the called user is in a call idle state, whereby a processing logic error occurs.
  • the backup node before the backup node receives the session establishment request sent by the upstream node of the service node, the backup node may further include: the backup node receiving the overload status notification message sent by the service node, where the overload status message is Carrying a first set of user identities of users who are being processed by the service node;
  • the method may further include: determining that the first user identifier does not exist in the first user identifier set.
  • the service node sends the user identifier of the user that is being processed to the backup node through the overload notification message, so that the backup node knows the user identifier set of the user that the current service node is processing, and if other user points are processing the user at this time. In the set of user IDs, if yes, the service node continues to provide services for the called user. After the service node processes the current session establishment request of the called user, the user identifier of the currently called user is notified to the backup node, so that when the service node is in an overload state, the backup node provides services for the called user.
  • the service node and the backup node need to synchronize related data at intervals. Since the service node normally provides services for each user, the user data in the backup node is not modified, mainly the service node will The modified user data is sent to each backup node. Generally, there may be multiple backup nodes of the service node. In the embodiment of the present invention, the service node has two backup nodes as an example for description.
  • the implementation process of data synchronization between the service node and the backup node includes the following steps:
  • the service node When the data synchronization time arrives, the service node establishes a connection with each backup node of the server. Specifically, the service node may request to establish a connection with the backup node by sending a connection request message to the backup node, after the backup node returns a response message to the service node. Establish a connection between the service node and the backup node.
  • the service node sends the corresponding user data to each backup node according to the preset backup policy; the service node selects the responded user data according to the preset backup policy and sends the response to the backup node.
  • the service node may pass the The backup node sends a storage request message, and sends corresponding user data to the backup node, and each backup node returns a response message of the storage request message to the service node.
  • Each backup node updates the local database according to the received user data.
  • a schematic diagram of a network structure for data synchronization in an embodiment of the present invention includes a service node, and a backup node 1, a backup node 2, and a backup node 3 of the service node.
  • the data synchronization is mainly performed by using the version identifier in the user information, and the value corresponding to the version identifier is larger, indicating that the user information is updated later, the user The newer the user data in the message. Therefore, if the user data in each pair of user information is modified once, the version identifier in the user information must be modified accordingly.
  • the service node and the backup node may perform data synchronization according to a preset period (when the update time arrives, may be initiated by the service node); or, after the service node is restored from the overload state to the normal state,
  • the backup node sends an overload recovery notification, and after the backup node learns that the service node returns to the normal state, it sends the user information processed during the overload state of the service node to the service node; or, the backup node actively detects the working state of the service node. After detecting that the service node returns to the normal state, the user information processed during the overload state of the service node is sent to the service node to ensure the consistency of the user information of the same user in a certain period of time.
  • the data processing method may further include:
  • the backup node synchronizes the modified user information corresponding to the first user identifier to the service node corresponding to the first node identifier;
  • the process flow of the data synchronization process includes the following steps:
  • the service node sends a connection establishment request to each backup node, and after receiving the response message returned by each backup node, the service node establishes a connection with the backup node.
  • Each backup node sends the processed user information to the service node.
  • the backup node may send the user information processed by itself to the service node by storing the message.
  • S711 The service node updates the local database according to the received user information. If there are multiple pieces of user information of the same user, the latest user data storage is selected according to the version identifier in the user information.
  • the backup node when the backup node sends the user message processed by itself to the service node, the backup node may also send the user identifier set of the user that is being processed to the service node, so that the service node is configured according to the service node.
  • the user ID contained in the user ID set can know the user that the current backup node is processing.
  • these user-related session establishment requests will be forwarded to the backup node, and the backup node will continue to be The service is provided until the backup node processes the completion of the session establishment requests of these users, notifying the service nodes, and then the service nodes provide services for these users.
  • the backup node completes the processing of the user information, and the consistency of the user information is controlled by the version identifier in the user information, so that the service node is enabled without increasing the load of the service node.
  • the user information stored therein is updated in time, thereby ensuring the user letter during the data processing process. Consistency of interest.
  • the data processing method may further include:
  • the backup node receives the network access request of the newly joined node, where the network access request carries the second node identifier of the newly joined node, and the second user identifier set corresponding to the user that is newly added by the node, the newly added node is a serving node.
  • Predecessor node
  • the backup node sends the user information corresponding to the user identifier in the second user identifier set to the new joining node corresponding to the second node identifier;
  • the newly joined node selects the latest user data storage according to the version identifier in the user information corresponding to the user identifier.
  • a data processing flow diagram is included, which includes the following steps:
  • the new joining node searches for a service node that administers the user that needs to be governed by the boot node and the preset P2P algorithm, and establishes a connection with the service node; the service node returns the overload information to the newly joined node through the guiding node, and notifies The newly added node itself is in an overload state;
  • the service node may carry the node identifier of the backup node of the backup node in the returned overload information, so that the newly added node obtains the node identifier of the backup node of the backup node; or, after receiving the overload information returned by the service node, the newly added node receives the overload information returned by the service node.
  • the node identifier of the backup node of the service node is determined according to the preset backup policy and its own node identifier.
  • step S805 S806 the new network access node sends a network access request to the service node, and notifies the service node that the new node joins.
  • step S805 S806 may be omitted.
  • the newly joining node sends a connection establishment request to the backup node, requesting to establish a connection with the backup node, and after receiving the connection establishment request response message returned by the backup node, the newly joining node establishes a connection with the backup node;
  • the new joining node sends a network access request to the backup node corresponding to the node identifier in the overload information, where the network access request carries the node identifier of the newly joined node and the user identifier corresponding to the user that is newly added to the node, requesting to obtain the self-administration.
  • User information of the user carries the node identifier of the newly joined node and the user identifier corresponding to the user that is newly added to the node, requesting to obtain the self-administration.
  • the backup node After receiving the network access request sent by the newly joined node, the backup node detects the node identifier of the newly joined node, to confirm that the newly joined node will administer the part of the user identifier corresponding to the user that is under the jurisdiction of the service node. User information, after the detection is passed, returning a response message of the network access request to the newly joined node;
  • the backup node sends the user information requested by the newly added node to the newly joined node according to the user identifier in the received network access request;
  • the backup node may send the user information requested by the newly added node to the newly joined node by storing the message, and the new joining node returns a response message for storing the message to the backup node after receiving the stored message sent by the backup node.
  • the new joining node selects the latest user data storage of the user under its jurisdiction according to the received user information. Specifically, after receiving the network access request sent by the newly joined node, the backup node sends the user information requested by the newly added node to the newly joined node by using a storage message, and the new joining node compares the same user after receiving the user information. The version identifier in the user information is selected, and the user information with the largest value of the version identifier is selected to be stored, thereby ensuring that the user data in the user information stored by itself is the latest user data.
  • the following scenarios may exist:
  • a new joining node sends a network request to a backup node and requests to obtain user information of a user under its jurisdiction
  • the user data of the user under its jurisdiction is being modified by the serving node, which may result in new joining.
  • the user data in the user information obtained by the node from the backup node is not the latest user data.
  • the backup node associates the user information corresponding to the user identifier in the second user identifier set.
  • the method may further include:
  • the backup node sends a data acquisition request to the service node, requesting to acquire a third user identifier set corresponding to the user currently being processed by the service node;
  • the third user identifier set For each user identifier in the third user identifier set, if the user identifier exists in the second user identifier set, set a flag for the user information corresponding to the user identifier, indicating that the newly joined node reacquires the setting to the service node. Tagged user information.
  • the newly added node reads the user information corresponding to each user identifier in the second user identifier set returned by the backup node, if it is detected that the user information corresponding to the user identifier is set with a flag, the user is specified.
  • the user information corresponding to the identifier is being modified by the service node, and the newly joining node re-requests to obtain the user information with the flag set by the service node.
  • the service node completes the modification of the user information corresponding to the user identifier, the corresponding user The information is sent to the new joining node.
  • the newly joined node may also actively request the marked user information from the service node after learning that the service node returns to the normal state.
  • the newly joined node after the newly joined node obtains the user information with the tag set to the service node, the newly joined node needs to notify other related nodes to update the routing table information, for example, the newly joined node needs to notify the upstream node of the service node, and the self-administered node Some users managed by the service node.
  • the newly joined node is successfully connected to the network, and the user data of the user under its jurisdiction is processed.
  • the newly joined node when the newly joined node joins the P2P network, the newly joined node searches for the service node that governs the user that needs to be governed by the boot node and the preset P2P algorithm, and returns through the service node.
  • the overload information is learned that the service node is in an overload state, and the overload information may include a node identifier of the backup node of the service node, or the newly joined node determines the node identifier of the backup node according to the backup policy and its own node identifier, thereby
  • the newly joined node can directly obtain the user information corresponding to the user who needs its jurisdiction from the backup node of the service node.
  • an embodiment of the present invention further provides a data processing node, and another data portion.
  • the method and the data processing node, because the data processing node, and another data processing method and the data processing node solve the problem are similar to the above data processing method, so the data processing node, and another data processing method and data processing node
  • the data processing node, and another data processing method and data processing node For the implementation of the above, refer to the implementation of the above data processing method, and the repetition will not be repeated.
  • a schematic structural diagram of a data processing node according to an embodiment of the present invention includes:
  • the storage unit 901 is configured to store user identifiers and user information of each user that is managed by the service node, where the user information includes user data and a version identifier used to identify that the user data is modified last time;
  • the first receiving unit 902 is configured to: when the serving node is in an overload state, receive a session establishment request sent by an upstream node of the service node, where the session establishment request carries a first user identifier of a user who needs to establish a session;
  • a modifying unit 903 configured to modify user data in the user information corresponding to the first user identifier
  • the updating unit 904 is configured to update the version identifier in the user information corresponding to the first user identifier.
  • the data processing node may further include:
  • a second receiving unit configured to receive, after the first receiving unit receives the session establishment request sent by the upstream node of the serving node, an overload status notification message sent by the serving node, where the overload status message carries the service a first set of user IDs of the user being processed by the node;
  • a determining unit configured to determine that the first user identifier does not exist in the first user identifier set before the modifying unit modifies the user data in the user information corresponding to the first user identifier.
  • the session establishment request further carries the first node identifier of the service node
  • the data processing node may further include:
  • a synchronization unit configured to synchronize, after the service node recovers from the overload state to the normal state, the modified user information corresponding to the first user identifier to the service node corresponding to the first node identifier;
  • the first indication unit is configured to instruct the service node to read the latest user data corresponding to the first user identifier according to the version identifier in the user information corresponding to the first user identifier.
  • the updating unit 904 may be configured to update the version identifier in the user information corresponding to the first user identifier according to the following formula: Se q uenceID (SequenceID old + , ⁇ ) mod Sequence1D , where: SequencelD is the updated version identifier ; ⁇ " ⁇ ⁇ .” is the version identifier before the update; is the default value; SequencelD is the default, the maximum value of the version identifier.
  • the data processing node may further include:
  • a second receiving unit configured to receive, before the first receiving unit 902 receives the session establishment request sent by the upstream node of the serving node, an overload status notification message sent by the service node, where the overload status message carries the user that the service node is processing Second user identifier;
  • the determining unit is configured to determine that the first user identifier does not exist in the second user identifier before the modifying unit 903 modifies the user data in the user information corresponding to the first user identifier.
  • the data processing node may further include: a third receiving unit, configured to receive a network access request of the newly joined node, where the network access request carries a second node identifier of the newly joined node, and a second user identifier set corresponding to the user that is newly added by the node, where the newly added node is The precursor node of the service node;
  • the first sending unit is configured to send the user information corresponding to the user identifier in the second user identifier set to the new joining node corresponding to the second node identifier.
  • the data processing node may further include:
  • a second sending unit configured to: before the first sending unit sends the user information corresponding to the user identifier in the second user identifier set to the new joining node corresponding to the second node identifier, send a data acquisition request to the serving node, requesting to obtain a third set of user identifiers corresponding to the user currently being processed by the service node;
  • a fourth receiving unit configured to receive a data request response message returned by the service node, where the data request response message carries a third user identifier set of a user currently being processed by the service node;
  • a marking unit configured to: for each user identifier in the third user identifier set, if the user identifier exists in the second user identifier set, set a flag for the user information corresponding to the user identifier;
  • a third indication unit configured to instruct the newly joined node to re-acquire the user information set with the tag to the service node.
  • the data processing node may further include:
  • the confirmation unit is configured to confirm that the first user identifier is within the range of the user identifier corresponding to the user under its jurisdiction before modifying the user data in the user information corresponding to the first user identifier.
  • the backup node stores a user identifier and user information of each user that is managed by the service node, where the user information includes user data and a version identifier used to identify the user data that has been modified last time.
  • FIG. 10 is a schematic flowchart of another implementation of a data processing method according to an embodiment of the present invention, including the following steps:
  • the backup node receives the network access request of the newly joined node, where the network access request carries the node identifier of the newly joined node, and the first user identifier set corresponding to the user that is newly added by the node,
  • the newly joined node is the precursor node of the service node;
  • the backup node sends the user information corresponding to the user identifier in the first user identifier set to the newly added node corresponding to the node identifier.
  • the newly added node selects the latest user data storage according to the version identifier in the user information corresponding to the user identifier.
  • the data processing method may further include:
  • the backup node sends a data acquisition request to the service node, requesting to acquire a second user identifier set corresponding to the user currently being processed by the service node;
  • a schematic structural diagram of a data processing node according to an embodiment of the present invention includes:
  • the storage unit 1101 is configured to store user identifiers and user information of each user that is managed by the service node, where the user information includes user data and a version identifier used to identify that the user data was last modified.
  • the first receiving unit 1102 is configured to: when the serving node is in an overload state, receive a network access request of the newly joined node, where the network access request carries the node identifier of the newly joined node, and the first corresponding to the user that is newly added by the node a set of user identifiers, the newly joined node being a precursor node of the service node;
  • the first sending unit 1103 is configured to send the user information corresponding to the user identifier in the first user identifier set to the new joining node corresponding to the node identifier.
  • the data processing node may further include:
  • a second sending unit configured to: before the first sending unit 1103 sends the user information corresponding to the user identifier in the first user identifier set to the new joining node corresponding to the second node identifier, send a data acquisition request to the serving node, requesting to obtain a second set of user identifiers corresponding to the user currently being processed by the service node;
  • a second receiving unit configured to receive a data request response message returned by the service node, where the data request response message carries a second set of user identifiers of the user currently being processed by the service node;
  • a marking unit configured to: for each user identifier in the second user identifier set, if the user identifier exists in the first user identifier set, set a flag for the user information corresponding to the user identifier;
  • a second indication unit configured to instruct the newly joined node to re-acquire the user information set with the tag to the service node.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can take the form of a computer program product embodied on one or more computer usable storage modules (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • computer usable storage modules including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can operate in a particular manner by a computer or other programmable data processing device, such that instructions stored in the computer readable memory are Manufactured, the instruction means implements the functions specified in a block or blocks of a flow or a flow and/or a block diagram of the flow chart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the backup node when the service node is in an overload state, receives a session establishment request sent by the upstream node of the service node, where the session establishment request carries the user who needs to establish a session.
  • the user identifier the backup node modifies the corresponding user data according to the user identifier and updates the version identifier of the user data corresponding to the user identifier, so that in the process of processing the user data, the backup node does not need to request the service node to obtain the modified user data.
  • the privilege allows the service node to set the tag of the user data modified by the backup node, reduces the signaling interaction between the backup node and the service node, and saves the processing resources of the service node, thereby reducing the load of the service node.
  • the backup node when the serving node is in an overload state, receives the network access request sent by the newly joined node, and the backup node according to the user corresponding to the user that the newly joined node carries in the network access request
  • the identifier, the user information corresponding to the user identifier is sent to the new joining node, and the new joining node is configured to read the latest user data corresponding to the user identifier according to the version identifier in the user information, so that the newly joined node directly joins the network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention porte sur un procédé de traitement de données et un nœud de traitement de données, utilisés pour traiter des données d'utilisateur lorsqu'un nœud de service est dans un état de surcharge et réduire la charge du nœud de service. L'identificateur d'utilisateur et les informations d'utilisateur de chaque utilisateur géré par le nœud de service sont sauvegardés d'une manière correspondante dans un nœud de secours, les informations d'utilisateur comprenant les données d'utilisateur et un identificateur de version servant à identifier la modification la plus récente des données d'utilisateur. Le procédé de traitement de données comprend les opérations suivantes : lorsque le nœud de service est dans l'état de surcharge, le nœud de secours reçoit une requête d'établissement de session transmise par le nœud amont du nœud de service, la requête d'établissement de session contenant un premier identificateur d'utilisateur de l'utilisateur demandant un établissement de session ; le nœud de secours modifie les données d'utilisateur dans les informations d'utilisateur correspondant au premier identificateur d'utilisateur, et met à jour l'identificateur de version dans les informations d'utilisateur correspondant au premier identificateur d'utilisateur.
PCT/CN2012/081456 2011-09-16 2012-09-17 Procédé de traitement de données et nœud de traitement de données WO2013037318A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110275291.1A CN103001987B (zh) 2011-09-16 2011-09-16 一种数据处理方法和数据处理节点
CN201110275291.1 2011-09-16

Publications (1)

Publication Number Publication Date
WO2013037318A1 true WO2013037318A1 (fr) 2013-03-21

Family

ID=47882628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/081456 WO2013037318A1 (fr) 2011-09-16 2012-09-17 Procédé de traitement de données et nœud de traitement de données

Country Status (2)

Country Link
CN (1) CN103001987B (fr)
WO (1) WO2013037318A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106528327B (zh) * 2016-09-30 2019-06-21 华为技术有限公司 一种数据处理方法以及备份服务器
CN113138881B (zh) * 2021-04-29 2023-07-25 北京百度网讯科技有限公司 分布式文件系统备份方法、装置和系统
CN113542775B (zh) * 2021-07-15 2023-09-19 广州安思创信息技术有限公司 直播保活服务系统、直播保活管理方法、服务器及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040167972A1 (en) * 2003-02-25 2004-08-26 Nick Demmon Apparatus and method for providing dynamic and automated assignment of data logical unit numbers
CN1886936A (zh) * 2003-10-24 2006-12-27 Ut斯达康公司 用于点对点协议装置冗余的系统及方法
CN101159921A (zh) * 2006-12-01 2008-04-09 华为技术有限公司 移动交换中心池中被叫恢复的方法、系统及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040167972A1 (en) * 2003-02-25 2004-08-26 Nick Demmon Apparatus and method for providing dynamic and automated assignment of data logical unit numbers
CN1886936A (zh) * 2003-10-24 2006-12-27 Ut斯达康公司 用于点对点协议装置冗余的系统及方法
CN101159921A (zh) * 2006-12-01 2008-04-09 华为技术有限公司 移动交换中心池中被叫恢复的方法、系统及设备

Also Published As

Publication number Publication date
CN103001987B (zh) 2016-05-25
CN103001987A (zh) 2013-03-27

Similar Documents

Publication Publication Date Title
JP7326443B2 (ja) Ｎｆ間のダイレクトシグナリングを使用したｎｆサービスコンシューマー再起動検出
JP2021518075A (ja) サービス加入方法および装置
US20070008880A1 (en) Router redundancy in data communication networks
TW201006272A (en) Method and apparatus for maintaining communications connections over a distributed wireless network
CN111200622B (zh) 一种资源传输方法及装置、存储介质
WO2012000271A1 (fr) Procédé d'accès à un terminal et réseau de communication sans fil
US11909840B2 (en) Resource subscription method, device, and storage medium
JP2023537154A (ja) セッション更新方法、端末及びネットワーク側機器
WO2013037318A1 (fr) Procédé de traitement de données et nœud de traitement de données
WO2008089616A1 (fr) Serveur, système réseau p2p et procédé d'acheminement et de transfert de l'affectation de la clé de ressource de ce dernier.......
JP3785101B2 (ja) 通信コネクション確立方法及び通信制御装置並びに記録媒体及び制御プログラム
JP2009194787A (ja) ゲートウェイ装置
WO2014029079A1 (fr) PROCÉDÉ, DISPOSITIF ET SYSTÈME DE GESTION DE LIAISONS RÉSEAU FCoE
JP2007174672A (ja) ピアツーピアルックアップシステムに対するモビリティチャーン処理のための方法および装置
CN102118422A (zh) Reload对等网络的对等节点及其配置的更新方法和系统
US9350621B2 (en) Synchronization after restart of a FC switch
CN107968825B (zh) 一种报文转发控制方法及装置
JP2012178003A (ja) 通信端末、通信方法、及び通信プログラム
WO2008131675A1 (fr) Procédé, nœud de réseau et système pour sauvegarder une ressource dans un réseau p2p structuré
JP4037432B2 (ja) 電話交換システム及び電話交換方法及び電話交換プログラム
WO2016177135A1 (fr) Procédé, dispositif et terminal de commande de gestion de ressources
CN114125827A (zh) 一种终端管理方法、装置及集中化管理系统
WO2017045431A1 (fr) Procédé et appareil de gestion de redémarrage progressif de routeur
WO2014180286A1 (fr) Procédé, cse, et système, pour la transmission d'une demande d'application m2m
WO2011082637A1 (fr) Réseau d'homologue à homologue et procédé de redémarrage de nœud homologue

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

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

Country of ref document: EP

Kind code of ref document: A1