Streaming service load sharing method, streaming service processing method, and corresponding device and system

Patent metadata

Field	Value
Publication number	US-9419890-B2
Application number	US-201313739746-A
Country	US
Kind code	B2
Filing date	Jan 11, 2013
Priority date	Jul 16, 2010
Publication date	Aug 16, 2016
Grant date	Aug 16, 2016

Abstract

Embodiments of the present invention disclose a streaming service load sharing method, a streaming service processing method, and a corresponding device and system. According to the embodiments of the present invention, a fixed allocation range is determined for each service node, so that when a service node fails and needs to perform smoothing of stream table items, only a fixed allocation range of the failed service node needs to be shared by other service nodes, thereby better ensuring stability of a processing range of the service node, and reducing the number of the stream table items to be smoothed.

First claim

What is claimed is:

1. A streaming service load sharing method, comprising:
receiving a service stream;
calculating an allocation identifier of the service stream;
determining a first service node according to the allocation identifier of the service stream, wherein the allocation identifier of the service stream belongs to an allocation range of the first service node, wherein the first service node is recorded as currently valid and the allocation range of the first service node comprises the first service node's own fixed allocation range and a part of a fixed allocation range of a second service node that is recorded as currently; and
determining whether the first service node fails;
in response to determining that the first service node does not fail, forwarding the service stream to the first service node; and
in response to determining that the first service node fails, forwarding the service stream to a backup service node of the first service node, recording the first service node as currently invalid, and allocating the allocation range of the first service node to the service node that is recorded as currently valid;
wherein
the first service node's own fixed allocation range is a range obtained by averagely allocating a full set of allocation identifiers to N service nodes; and
the fixed allocation range of the second service node is the range obtained by averagely allocating the full set of allocation identifiers to N service nodes, wherein N is the maximum number of service nodes.

2. A streaming service processing method, comprising:
traversing backup stream table items of a first service node that fails; and
determining, according to a processing range of a normal service node, a part of the backup stream table items that need to be smoothed to the normal service node, wherein the processing range of the normal service node comprises the normal service node's own fixed allocation range and a part of a fixed allocation range of a second service node that is recorded as currently invalid;
a fixed allocation range is a range obtained by averagely allocating a full set of allocation identifiers to N service nodes, wherein N is the maximum number of service nodes; and
the part of the fixed allocation range of the second service node is one of M 2 parts, wherein the M 2 parts are obtained by performing the following operation: averagely dividing a fixed allocation range of the second service node into the M 2 parts, wherein M 2 =N−H, and H is the number of currently invalid service nodes.

3. The method according to claim 2 , wherein the method further comprises:
receiving a service stream; and
forwarding the service stream to a third service node when determining that an allocation identifier of the service stream belongs to a processing range of the third service node, wherein the third service node is valid.

4. The method according to claim 3 , wherein:
the service stream with the allocation identifier belonging to the processing range of the third service node only comprises a service stream for which stream table items need to be created, or comprises a service stream for which stream table items need to be created and a service stream for which stream table items are already created but need to be smoothed to the third service node.

5. A streaming service processing device, comprising:
a processor; and
a memory;
wherein the processor is configured to execute computer-executable instructions stored in the memory to perform operations of:
traversing backup stream table items of a first service node that is failed; and
determining, according to a processing range of a normal service node, a part of the backup stream table items that need to be smoothed to the normal service node, wherein the processing range of the normal service node comprises the normal service node's own fixed allocation range and a part of a fixed allocation range of a second service node that is recorded as currently; and
obtaining a fixed allocation range by averagely allocating a full set of allocation identifiers to N service nodes, wherein N is the maximum number of service nodes; wherein the part of the fixed allocation range of the second service node is one of M 2 parts, wherein the M 2 parts are obtained by performing the following operation: averagely dividing a fixed allocation range of the second service node into the M 2 parts, wherein M 2 =N−H, and H is the number of currently invalid service nodes.

6. The device according to claim 5 , wherein the processor is further configured to perform operations of:
receiving a service stream; and
determining whether an allocation identifier of the service stream belongs to a processing range of a second service node; and if yes, forwarding the service stream to a third service node when determining that an allocation identifier of the service stream belongs to a processing range of the third service node, wherein the third service node is valid.

7. A streaming service load sharing device, comprising:
a processor; and
a memory;
wherein the processor is configured to execute computer-executable instructions stored in the memory to perform operations of:
receiving a service stream;
calculating an allocation identifier of the service stream;
determining a first service node according to the allocation identifier of the service stream, wherein the allocation identifier of the service stream belongs to an allocation range of the first service node, wherein the first service node is recorded as currently valid, and the allocation range of the first service node comprises the first service node's own fixed allocation range and a part of a fixed allocation range of a second service node that is recorded as currently invalid;
determining whether the first service node fails;
in response to determining that the first service node does not fail, forwarding the service stream to the first service node;
in response to determining that the first service node fails, forwarding the service stream to a backup service node of the first service node;
recording the first service node as currently invalid; and
allocating the allocation range of the first service node to the service node that is recorded as currently valid;

wherein
the first service node's own fixed allocation range is a range obtained by averagely allocating a full set of allocation identifiers to N service nodes; and
the fixed allocation range of the second service node is the range obtained by averagely allocating the full set of allocation identifiers to N service nodes, wherein N is the maximum number of service nodes.

Assignees

• Huawei Tech Co Ltd

Inventors

• Teng Xindong

Classifications

• H04L41/0663

  Performing the actions predefined by failover planning, e.g. switching to standby network elements · CPC title

• H04L45/28 Primary

  using route fault recovery · CPC title

• H04L65/4069

  Electricity · mapped topic

• H04L67/1029

  using data related to the state of servers by a load balancer · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title