[go: up one dir, main page]

WO2018001011A1 - Procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et dispositif de réacheminement de fonctions de service - Google Patents

Procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et dispositif de réacheminement de fonctions de service Download PDF

Info

Publication number
WO2018001011A1
WO2018001011A1 PCT/CN2017/085897 CN2017085897W WO2018001011A1 WO 2018001011 A1 WO2018001011 A1 WO 2018001011A1 CN 2017085897 W CN2017085897 W CN 2017085897W WO 2018001011 A1 WO2018001011 A1 WO 2018001011A1
Authority
WO
WIPO (PCT)
Prior art keywords
network function
function entity
sff
data packet
load
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/085897
Other languages
English (en)
Chinese (zh)
Inventor
克里斯⋅马里斯
克罗尔⋅朱塞佩
卢克⋅克里斯汀
王岩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2018001011A1 publication Critical patent/WO2018001011A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers

Definitions

  • the present invention relates to the field of communications, and in particular, to a method for selecting a network function for data forwarding and a service function forwarder.
  • hot backup solutions are often used to achieve high reliability of services.
  • the main feature of the hot backup solution is that there is a functioning network function entity at the same time, and a backup network function entity, wherein the running network function entity receives all the service data streams, and at the same time, backs up the network function. Entity waits are enabled in case an unexpected event occurs in a running network functional entity (for example, a failure).
  • the current Service Function Chaining usually uses path-level backup, and the default path selection function is used as a backup.
  • SFC Service Function Chaining
  • Path One is a functional entity that is running, and one is a functional entity that performs a hot backup.
  • the backup path is enabled when the current path fails.
  • NSHs network service headers
  • the embodiment of the invention provides a method for selecting a network function for data forwarding and a service function forwarder, which provides an effective hot backup mechanism for the SFC under the distributed data center architecture, and can reduce the path in the service function chain. And the management of NSHs reduces complexity and provides an effective load balancing mechanism for SFC under distributed data center architecture.
  • a first aspect of the embodiments of the present invention provides a method for selecting a network function for data forwarding, where the method includes: a service function forwarder (Service Function Forward, SFF for short) receives a data packet; Running the status information, determining the next hop node forwarded by the data packet, forwarding the data packet to the next hop node, where the next hop node is the first network function entity or another SFF, and the first network function entity is the SFF
  • the associated network function entity, the other SFF is the SFF associated with the second network function entity, and the second network function entity is the network function entity of the same type as the first network function entity, and the running status information includes the load quantity or the operation indication information.
  • the operation indication information indicates whether the first network function entity is operating normally.
  • the service function forwarder SFF receives the data packet, and determines whether the data packet is based on the load quantity or normal operation indication information of the network function entity (the local network function entity of the SFF) associated with the SFF. Forwarded to the local network functional entity or forwarded to another SFF-associated network functional entity. Therefore, the hot backup can be implemented by another SFF-associated network function entity, without adding a path for the same type of network function entity to perform backup, compared with the existing default path selection for backup mechanism, greatly reducing The management of paths and NSHs reduces complexity; in addition, load balancing can be achieved through another SFF-associated network functional entity, thus providing a load balancing implementation.
  • the SFF determines, according to the running state information of the first network function entity, the next hop node of the data packet forwarding. Forwarding the data packet to the next hop node includes: when the operation indication information indicates that the first network function entity is invalid (not working properly), the SFF forwards the data packet to another SFF, so that another SFF forwards the data packet to The second network function entity associated therewith, wherein the second network function entity is an available hot backup network function entity of the first network function entity.
  • the data packet before the receiving, by the first SFF, the data packet includes: the first SFF receiving the information that the first NF is invalid; and the first SFF removing the first NF from the forwarding address table. address.
  • the SFF forwards the received data packet to the network function entity of the hot backup, and the network function entity of the hot backup is a network function entity on another SFF, so the hot can be embedded in the SFF.
  • the backup network function selection method is used to implement hot backup. It is not necessary to add a path for each network function entity of the same type to perform backup, which can reduce the management of the path and NSHs and reduce the complexity.
  • the method further includes: when the operation indication information indicates that the first network function entity is running normally, the SFF is to use the data packet. Forward to the first network functional entity.
  • the method before the SFF receives the data packet, the method further includes: SFF receiving The backup function available information, the backup function available information contains another SFF network identifier; the SFF saves another SFF network identifier, and determines the available hot backup network functional entity of the local network functional entity according to the network identifier of the other SFF.
  • the SFF can be allocated by the hot standby network function entity to the orchestrator or controller in the service function chain, and the hot standby network function entity is another SFF-associated network function entity, instead of the backup path on the same SFF.
  • the data packet can be forwarded to the hot standby network function entity, thereby reducing the management of the path and the NSHs, and providing a hot backup mechanism for the service function chain under the distributed architecture. .
  • the SFF determines the next hop node according to the running status information of the first network function entity, and forwards the data packet to The next hop node includes: when the load of the first network function entity is lower than the first load amount threshold, the SFF forwards the data packet to the first network function entity.
  • the SFF has the capability of selecting a load balancing function entity, and according to the load condition of the local network function, when the local network function entity is not overloaded, the data packet is forwarded to the local to balance the local network functional entity. Processing capacity.
  • the method when the running status information is the load quantity, the method further includes: the SFF records load information of the network function entity of the same type as the first network function entity in the service function chain, where the load information indication is the same as the first network function entity.
  • the congestion state of the network function entity of the type the SFF determines the next hop node forwarded by the data packet according to the running state information of the first network function entity, and forwards the data packet to the next hop node including: when the load of the first network function entity When the amount is higher than the second load threshold, the SFF determines the second network function entity in the non-congested state according to the load information, and forwards the data packet to another SFF, so that the other SFF forwards the data packet to the second network function entity.
  • the SFF forwards the data packet to another non-congested network function entity of the same type, thereby balancing the load of each network function entity in the service function chain.
  • the SFF records the load information of the network function entity of the same type as the first network function entity, including:
  • the source network function entity of the data packet records the load information of the source network function entity.
  • the specific record is: if a data packet of a network function entity is received, the load information of the network function entity is updated to indicate that the network function entity is in a congested state, and then, according to the network function entity received The frequency of the data packet, the size of the data packet, etc. adjust the load information value of the network functional entity to continuously update the congestion degree of the network functional entity.
  • the weighted polling load balancing algorithm may be used to calculate the congestion status of each network functional entity of the same type, and the weighted polling value is used to represent the load information of each network functional entity of the same type, and the weighted polling value is inversely proportional to the congestion degree. .
  • the SFF is The running status information of the first network function entity determines the next hop node forwarded by the data packet, and forwarding the data packet to the next hop node includes:
  • the SFF determines that the data packet is in a non-congested state according to the load information.
  • the second network function entity forwards the data packet to another SFF such that the other SFF forwards the data packet to the second network function entity; and the SFF updates the load information of the network function entity transmitting the data packet to indicate the Network functional entities are more congested than when they received their data last time;
  • the data packet is forwarded to the first network function entity, and the load information of the network function entity that sends the data packet is updated, and the load information indicates that the data packet is sent.
  • the network functional entity of the data packet is in a congested state.
  • an embodiment of the present invention provides a service function forwarder SFF, where the SFF performs the method of selecting a network function for data forwarding described in the first aspect. Specifically include:
  • the receiving module is configured to receive a data packet
  • the forwarding module is configured to determine, according to the running state information of the first network function entity, a next hop node forwarded by the data packet, and forward the data packet to the next hop node, where the next hop node includes a first network function entity or another SFF, the first network function entity is a network function entity associated with the SFF, the other SFF is an SFF associated with the second network function entity, and the second network function entity is a first network function entity
  • the running status information includes the load amount or running indication information.
  • the forwarding module is specifically configured to be used when When the indication information indicates that the first network function entity fails, the data packet is forwarded to another SFF, so that another SFF forwards the data packet to the second network function entity, where the second network function entity is the first network function entity A hot standby network functional entity is available.
  • the forwarding module is configured to: when the operation indication information indicates that the first network function entity is running normally, the SFF data The packet is forwarded to the first network functional entity.
  • the receiving module is further configured to receive a backup function.
  • the available information, the backup function available information includes another SFF network identifier;
  • the service function forwarder further includes: a storage module for storing another SFF network identifier; and a backup network function entity determining module for storing according to the storage module Another SFF network identity identifies the available hot backup network functional entities.
  • the forwarding module is configured to: when the load of the first network function entity is lower than the first load threshold, the SFF forwards the data packet to the first A network functional entity.
  • the service function forwarder further includes: a storage module, configured to record a network of the same type as the first network function entity a load information of the function entity, the load information indicating a congestion state of a network function entity of the same type as the first network function entity, and a forwarding module, specifically, when the load of the first network function entity is higher than a second load threshold
  • the SFF determines the second network function entity in the non-congested state according to the load information, the data packet is forwarded to another SFF such that the other SFF forwards the data packet to the second network function entity.
  • the storage module is configured to record a load of the source network functional entity according to the source network function entity of the received data packet.
  • the specific record is as follows: if a data packet of a network function entity is received, the load information of the network function entity is recorded to indicate that the network function entity is in a congested state, and then, according to the data of the network function entity.
  • the frequency of the packet, the size of the packet, and the like adjust the load information value of the network functional entity to continuously update the congestion degree of the network functional entity.
  • the forwarding module is specifically configured to: when the load of the first network function entity is greater than the first load threshold, less than the second load threshold, if the data is The packet is sent by the same network function entity as the last received data packet, and then the second network function entity in the non-congested state is determined according to the load information, and the data packet is forwarded to another SFF, so that another SFF will be the data packet.
  • the storage module is further configured to update the sending data Load information of a network function entity of the packet, the load information indicating that the network function entity that sent the data packet is in a congested state.
  • an embodiment of the present invention further provides a service function repeater, including: an interconnected transceiver, a processor, and a memory; the memory is configured to store the program code, and the processor calls the program code in the memory to execute the first
  • the method for selecting a network function for data forwarding is described on the one hand: receiving a data packet through a transceiver, determining a next hop node forwarded by the data packet according to the running state information of the first network function entity, and forwarding the data packet to the transceiver through the transceiver Next hop node, the next hop node includes a first network function entity or another SFF, and the first network function entity is SFF
  • the other SFF is the SFF associated with the second network function entity
  • the second network function entity is the network function entity of the same type as the first network function entity
  • the running status information includes the load quantity or the operation indication information.
  • an embodiment of the present invention further provides a storage medium for storing an application, the program executing some or all of the steps of the method for selecting a network function for data forwarding described in the above first aspect.
  • the service function forwarder SFF receives the data packet, and determines whether the data packet is based on the load amount of the network function entity (the local network function entity of the SFF) associated with the SFF or the normal operation indication information. Forwarding to the local network functional entity or forwarding to another SFF-associated network functional entity, eliminating the need to add a path for the same type of network functional entity for backup and load balancing, compared to existing default path selection As a backup mechanism, the management of paths and NSHs is greatly reduced, and the complexity is reduced.
  • FIG. 1 is a schematic diagram of a centralized-based redirected backup mechanism in a prior art service function chain
  • FIG. 2 is a schematic diagram of SFF and NF connections of a distributed data center according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an extension of a forward forwarding function of an SFF in a service function chain SFC according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for selecting a network function for data forwarding according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a service function chain of a multi-network function according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of hardware of a service function repeater according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of a function module of a service function repeater according to an embodiment of the present invention.
  • the embodiment of the invention provides a method for selecting a network function for data forwarding and a service function forwarder, which provides an effective hot backup mechanism and a load balancing mechanism for the SFC under the distributed data center architecture. The details are described below.
  • the service processing functions such as the virtual firewall/load balancer/gateway are called service functions, and the traffic is processed through a series of service functions to form a service function chain (English: Service Function Chaining, SFC for short). .
  • Controller The controller that forms the service function chain is also the general service control plane (full name: Generic Service Control Plane, referred to as: GSCP);
  • Service Classifier performs stream identification on the data stream, and the specific stream performs specific service function chain processing
  • Network function entity full name: Network Function, NF for short: A node that performs service processing on data packets. This type of node only provides network function services and does not participate in network layer routing and forwarding of packets.
  • SFP full name: service function path
  • SFP is a business processing path from the classifier, and then through a number of network functional entities, and finally reach the destination.
  • business function forwarder SFF is mainly responsible for traffic forwarding control on the SFC, maintaining SFP processing from Data traffic forwarded by other SFFs maps different data traffic to other SFFs.
  • the data packets are transmitted between the nodes of the service function chain, and a service function header (Network Service Header: NSH) is encapsulated outside the data frame, and the service function forwarder parses, encapsulates, and decapsulates the service function header. Traffic is distributed from the network to the functional nodes associated with it based on the service function header.
  • NSH Network Service Header
  • the service function forwarder parses, encapsulates, and decapsulates the service function header.
  • Traffic is distributed from the network to the functional nodes associated with it based on the service function header.
  • the service function forwarder is responsible for sending the message back to the network.
  • SFC is a technology that separates network device service functions from forwarding. It implements independent operation and processing of service functions and improves the forwarding performance of network devices.
  • an SFF connects two network functions of the same type (NF), one for the running NF and the other for the hot backup NF.
  • the SFF function can be implemented by a repeater (Switch, SW), and the backup information and the load balancing function are added on the basis of the SFF function.
  • the hot backup NF will be enabled, the classifier receives the notification message of the running NF failure, and the classifier classifies the data into the hot backup NF. In this process, the data packet being transmitted will be lost to the NF that has expired, and some data will be lost.
  • the same type of network function is connected to different selectors (SFF) in case the network function entities are not placed on the same server.
  • SFF selectors
  • Each network function is connected to an isolated SFF, and the SFF forwards the packet forward to the network function connected to it or forwards it to the next SFF. Therefore, the backup scheme based on the centralized redirection mechanism is not suitable for the current SFC, and a new backup mechanism needs to be sought to support the hot backup function of the distributed architecture.
  • the embodiment of the invention is an added solution in the current distributed data architecture, and an effective hot backup mechanism is proposed for the current SFC. On this basis, an effective load balancing function is proposed.
  • the solution does not back up by adding data paths, does not add additional routes, and can be directly applied to a distributed forwarding architecture.
  • the SFF1 when a data stream (or a data packet) arrives on the first SFF1, the SFF1 performs a forward forwarding decision according to the running state of the local network functional entity, and determines the forwarding of the data packet to the local network function.
  • the entity NF1 is forwarded to the next SFF2, and the decision is independent of the rest of the system and is not affected by the rest of the system.
  • the data forwarding method in the embodiment of the present invention is as shown in FIG. 4, and the method includes:
  • the service function forwarder receives the data packet.
  • a data packet that needs to be processed by the network function entity encapsulates a service function header (NSH) through the classifier before the service processing, and the NSH indicates the service function path of the data packet, which needs to be forwarded to a specific network function entity.
  • the classifier sends the data packet encapsulating the NSH to the SFF corresponding to the path, and the SFF receives the data packet encapsulating the NSH.
  • the SFF determines, according to the running state information of the local network function entity (NF), a next hop node forwarded by the data packet, and forwards the data packet to the next hop node, where the next hop node may be an SFF.
  • the local network function entity (the first network function entity) or another SFF, and the other SFF associated network function entity is the second network function entity.
  • the SFF After receiving the data packet, the SFF should send the data packet to the network function entity associated with the SFF according to the existing technology according to the prior art, and the network function entity associated with the SFF is the network function entity of the SFF (ie, the first network). Functional entity).
  • the SFF determines the forwarding next hop node of the data packet according to the running state information of the local network function entity, and specifically determines whether to forward the data packet to the local network function according to the running status of the local network function.
  • the entity if not suitable for forwarding to the local network function entity, forwards to another SFF-associated network function entity, that is, another SFF local network function entity (second network function entity), and the next hop node is another SFF, forwarded by the other SFF to the second network functional entity.
  • another SFF-associated network function entity that is, another SFF local network function entity (second network function entity)
  • the next hop node is another SFF
  • the first network function entity NF1 and the second network function entity NF2 belong to the same type A, and can handle the same type of traffic.
  • the first network function entity and the second network function entity are both firewalls.
  • the running status information of the local network function entity may be running indication information, such as: normal operation, failure; or the load of the local network function entity, for example, the local network function entity is in a congested state, or is in a non-congested state. .
  • the SFF determines that the forwarding next hop node of the data packet mainly includes two aspects according to the running state information of the local network function entity, that is, the following two aspects are extended on the SFF:
  • the running status information is running indication information. If the operation indication information indicates that the local network function entity is running normally, the SFF forwards the data packet to the local network function entity; if the operation indication information indicates that the local network function entity is invalid (for example, downtime, cannot run normally), the SFF determines The backup network function entity of the network function entity forwards the data packet to the SFF associated with the backup network function entity, and then forwards the data packet to the backup network function entity, and the backup network function entity processes the data packet.
  • the running status information is the load amount. If the load of the local network function entity indicates that the local network function entity is in a non-congested state, the SFF forwards the data packet to the local network function entity; if the load quantity of the local network function entity indicates that the local network function entity is in a congested state, then The SFF forwards the packet forward to the SFF of another uncongested network function entity, which forwards the packet to the network functional entity associated with it.
  • the following describes the method of selecting the hot backup function and the method of selecting the load balancing function that SFF has.
  • the present invention is applicable to two or more application scenarios of the same type of network functional entity. As shown in Figure 5, it is a situation with four network functional entities. Includes SFF1, SFF2, SFF3, and SFF4 capable of communicating with each other, and a local network function entity NF1 associated with SFF1, a local network function entity NF2 associated with SFF2, a local network function entity NF3 associated with SFF3, and a local network associated with SFF4 Functional entity NF4.
  • the first embodiment the choice of hot backup function.
  • a hot spare component deployed in the system can be used by all other network functional entities of the same type, that is, multiple network functional entities of the same type can share the same type of backup.
  • NF3 can act as a hot standby network functional entity for NF1, NF2, and NF4.
  • the hot-backed network function entity will temporarily take over the packet (traffic) of the failed network function entity until a new network function entity or a failed network function entity is deployed. Resume normal operation.
  • the system For a network functional entity and its hot standby network functional entity, the system considers that one of the network functional entities is activated to run, and the other is a hot standby network functional entity. In the case that the local network function is activated, the SFF forwards the data packet to the local network function; when the local network function activation fails, the SFF forwards the data packet to the hot standby network functional entity association. On the SFF.
  • the controller (or orchestrator) in the SFC sends the backup function available information to the SFF1 to allocate the hot standby network function entity to the network function entity NF1 associated with the SFF1.
  • the backup function available information may include a backup NSH, and the NSH specifies a network identifier of the available backup SFF2 corresponding to the SFF1.
  • the backup function can be used for specific data traffic, and can be an openflow rule information that has lower permissions than forward packet information that is passed to the local network function.
  • SFF1 saves the received backup function information to the local hot backup information.
  • SFF1 receives data traffic (ie, data packet)
  • data traffic ie, data packet
  • the local network function entity NF1 of SFF1 is activated and running normally, the received data traffic is forwarded only to the local network function entity NF1, and the network function of the hot backup is performed. Entity NF2 is waiting to be enabled.
  • the SFF1 receives a message that the local network function is invalid, and the message indicates that the current network function entity NF1 is invalid.
  • the message may be informed by SFF1 by an activation function entity in the local network function entity, or by a controller or orchestrator in the SFC to inform SFF1.
  • the SFF1 After the SFF1 receives the message that the local network function is invalid, the SFF1 does not forward the received data packet to the NF1.
  • the SFF1 removes the local network function entity NF1 from the forward forwarding table, according to the locally stored hot backup information.
  • the available hot backup SFF2 network identifier forwards all received data traffic (packets) to SFF2, which forwards the packets to the hot standby network functional entity NF2.
  • the SFF1 that needs to be backed up is notified by the backup function available information, and in the case that no failure occurs, the SFF1 forwards the data packet to the running network function entity NF1, and in the event of a failure, the SFF1 can pass the backup network.
  • the identity forwards the packet directly to the backup NF2.
  • the invention can realize the hot backup processing of the system without greatly increasing the data path and the NSHs, and the response is fast and efficient; and the data packet being transmitted is transmitted to the NF2 of the hot backup, so that no data is lost.
  • the second embodiment the selection of the load balancing function.
  • the load information communication is not performed between the SFFs, and the SFF can directly infer the load information of the other party from the data packets they receive, and does not require more explicit information transmission to inform the load conditions between the SFFs.
  • a load table is dynamically maintained in each SFF, and the load information of the local network function entity and the same type of network function entity in the SFC is recorded.
  • the load information of the local network function entity may be: the actual load condition of the local network function entity is reflected by the load quantity, and when the load quantity of the local network function entity exceeds the first load quantity threshold, the local network function entity is considered to be overloaded, that is, In a state of congestion.
  • multiple load thresholds may also be set.
  • the load of the local network function entity exceeds the second load threshold, the local network function entity is considered to be overloaded and in a super-congested state.
  • Recording the load information of the network function entity of the same type in the SFC may be: when receiving the forwarding data packet of a network function entity, the network function entity is considered to be overloaded, and the received data packet cannot be processed by itself, and needs to be forwarded. Indicates that it is in a congested state; if it has not received a forwarding packet of a network function entity, it considers that the network function entity is not overloaded, and the network function entity itself processes the received data packet, indicating that the network function entity is in a non-congested state. .
  • the load information of the network function entity in the load table may be dynamically adjusted according to the frequency of receiving the data packet of the SFF associated with the network function entity, the size of the received data volume, and the like.
  • the load information recorded in the load table is a load balancing value calculated by a load balancing algorithm.
  • the load balancing value may be calculated by a weighted polling decision algorithm, and the load balancing value is represented by a weighted polling value.
  • the SFF receives a data packet, it adjusts the weighted polling value of the network function entity that sent the data packet in the load table.
  • the weighted polling value is inversely proportional to the degree of congestion. The smaller the weighted polling value, the more serious the congestion degree is. The larger the weighted polling value is, the less congested.
  • the weighted polling value of a network function entity recorded in the load table exceeds a certain threshold set by the system, it indicates that the network function entity is in a congested state, and the weighting round of a network function entity recorded in the load table
  • the query value is lower than the threshold set by the system, it indicates that the network function entity is in a non-congested state.
  • the SFF associated with the network function entity broadcasts to the SFF of the same type of network function entity, and the network function entity of the same type of network function entity is added.
  • the table begins to record the load balancing value of the newly added network function entity, and directs part of the traffic to the newly added network function entity.
  • the SFF of other network functions of the same type in the SFC is notified, so that the load balancing value of the network function entity is updated, and the traffic is no longer directed to the network function entity.
  • the load balancing value is represented by a weighted polling value, for SFF2, if NF4 is a newly added network functional entity, SFF2 starts recording the weighted polling value of NF4, and at this time, the weighting round of NF4
  • the query value is a larger value to import traffic to NF4; the weighted polling value of NF2 and NF3 is also recorded in the load table of SFF2.
  • the weighted polling value of the NF1 associated with the SFF1 is adjusted in the load table to indicate that the NF1 is in a congested state; if the SFF2 continuously receives the forwarded data packet of the SFF1, the SFF2 adjusts the load.
  • the weighted polling value of NF1 in the table indicates that NF1 is in a very congested state.
  • the weighted polling value of NF1 in the load table is dynamically adjusted to indicate NF1 is in a non-congested state; If SFF2 has never received the forwarded packet of SFF3, the weighted polling value of NF3 associated with SFF3 recorded in the load table shall indicate that NF3 is in a non-congested state. In this way, SFF2 continuously adjusts the weighted polling value of its network functional entity of the same type through weighted polling load balancing algorithm for load balancing.
  • the SFF When the SFF receives a packet, it passes through a local filter and decides whether to forward it to the local NF or to another SFF based on the load balancing algorithm.
  • the SFF adjusts the load table to send.
  • the SFF load balancing value of the packet the data traffic sent by the SFF to the SFF of the transmitted packet will be reduced, waiting for it to process the congestion data.
  • the local network function entity is not overloaded, the data traffic received from the SFF of the transmitted data packet will be processed by the local network function. If overloaded, an NF without overload will be selected according to the load table (in a non-congested state) NF), forwards the packet to the SFF corresponding to the NF in the non-congested state.
  • the packet is forwarded to the local NF1.
  • the load of the local network function entity NF1 on the SFF1 is greater than the first load amount threshold, less than the second load threshold, for example, the local load is greater than 70%, less than 95%.
  • the weighted polling value of NF2 in the load table is adjusted. Small (weighted polling value is inversely proportional to congestion). And according to the weighted polling value of other network function entities in the load table, select a network function entity in a non-congested state, for example, select a network function entity with the largest weighted polling value (or may be larger), The data packet is sent to the network function entity for processing. Assuming that the packet is selected for transmission to NF3 processing, the packet is forwarded to SFF3, and the packet is forwarded to NF3 by SFF3. Optionally, a part of the local NF1 processing may be used, and a part of the data is forwarded to the NF3 processing. It should be noted that if other network function entities are in a congested state, they are processed by the local NF1.
  • SFF1 forwards the data packet received from NF2 locally. That is, it is forwarded to the NF1 process, and the NF2 that sends the data packet is marked to be in a congested state, that is, the weighted polling value of the NF2 is adjusted to a suitable value to indicate that the NF2 is in a congested state.
  • the load of the local network function entity NF1 on SFF1 is greater than the second load amount threshold, for example: greater than 95%.
  • the weighted polling value of NF2 in the load table is adjusted. small. And according to the weighted polling value of other network function entities in the load table, select a network function entity in a non-congested state, for example, select a network function entity with the largest weighted polling value (or may be larger), The packet is sent to the network The network function entity processes, if other network function entities are congested, discards the data packet or forwards it to the local NF1 process.
  • the NF2 marked to send the data packet is in a congested state, that is, NF2
  • the weighted polling value is reduced.
  • the packet is forwarded to the network function entity without congestion. If other network function entities are congested, the packet is discarded or forwarded to the local NF1 process.
  • the SFF can adopt the following principles in the process of forward data forwarding according to the load status of the local network function entity:
  • the most efficient way to handle data traffic is to forward it to a local network function entity without going through other intermediate communication nodes or forwarding to other networks or data centers for processing, thereby increasing efficiency.
  • a network function entity can process data traffic normally and is in a normal load state, the same group of data packets is preferably processed on a network function entity, thereby making good use of the current NF calculation and processing capabilities.
  • SFF can filter the data packet through the local filter: simple load balancing is performed by matching the IP header. For example, all packets starting with 10.x will be sent to NF1, all starting with 11.x. All will be sent to NF2.
  • an effective load balancing mechanism is proposed for the current data traffic situation of the distributed data center, and a corresponding load balancing algorithm is proposed. Therefore, the distributed network can be made to achieve load balancing. Moreover, each SFF of the embodiment of the present invention can be individually determined according to its purpose, and the system can be triggered to perform adaptive load balancing processing through a small amount of data traffic, which does not require additional management and improves load balancing efficiency.
  • the present invention proposes an effective hot backup mechanism for SFCs of multiple network functions under the current distributed architecture, and on the basis of this, an effective load balancing function is proposed.
  • an effective hot backup function on the SFF
  • the hot backup mechanism is effectively implemented, and a large number of additional paths can be avoided, and the existing backup path selection mechanism is used as a backup mechanism, which greatly reduces the path and the NSHs.
  • the present invention can be implemented by upgrading corresponding network elements without deploying additional external mechanisms.
  • the solution is transparent to the classifier, the network function entity itself or the end-to-end service, and is mutually sensible. Therefore, the present invention simplifies the deployment of the service.
  • the solution provides a service function chain (SFC) that the MAC layer transparently forwards to the IP layer. Only a small number of NSHs are needed, and NSHs are not increased in a large amount, and the hot standby network function does not need to be exposed to the classifier, and information backup is performed only at the SFF level, which reduces unnecessary management and signaling overhead.
  • SFC service function chain
  • the foregoing is a description of an embodiment of a method for performing data forwarding by selecting a network function in the embodiment of the present invention.
  • the service function forwarder in the embodiment of the present invention is introduced from the perspective of a functional module and a hardware implementation.
  • FIG. 6 is a schematic diagram of a hardware structure of a service function repeater according to an embodiment of the present invention.
  • the service function repeater 600 may generate a large difference due to different configurations or performances, and may include one or more processors (central processing units, CPU for short) 622 (for example, one or more processors) and a memory 630 for storing one or more storage applications Sequence 642 or data 644, stores one or more operating systems 641, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and the like.
  • the program stored in memory 630 may include one or more modules (not shown), each of which may include a series of instruction operations in the control plane device.
  • processor 622 can be in communication with memory 630 to perform a series of instruction operations in memory 630 on control plane device 600.
  • Service function repeater 600 also includes one or more transceivers 650, which may be wireless network interfaces.
  • the processor 622 executes the application 642 stored in the memory 630 to perform all or part of the steps performed by the SFF in the foregoing method embodiment (the embodiment shown in FIG. 4), and mainly includes:
  • the data packet is received by the transceiver 650, and the next hop node forwarded by the data packet is determined according to the running state information of the first network function entity, and the data packet is forwarded to the next hop node by the transceiver 650, and the next hop node includes the first a network function entity or another SFF, the first network function entity is a network function entity associated with the SFF, the other SFF is an SFF associated with the second network function entity, and the second network function entity is of the same type as the first network function entity Network function entity, running status information includes load amount or running indication information.
  • the function of the service function repeater in the embodiment of the present invention can also be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the PLD may be a complex programmable logic device (CPLD), an FPGA, a general array logic (GAL), or any combination thereof.
  • the schematic diagram of the function module of the control plane device in the embodiment of the present invention is as shown in FIG. 7, and includes:
  • the receiving module 701 is configured to receive a data packet sent by another node in the SFC.
  • the forwarding module 702 is configured to determine, according to the running state information of the first network function entity, a next hop node forwarded by the data packet, and forward the data packet to the next hop node, where the next hop node includes the first network function entity or another SFF, the first network function entity is a network function entity associated with the SFF, the other SFF is an SFF associated with the second network function entity, and the second network function entity is a network function entity of the same type as the first network function entity, running
  • the status information includes the load amount or the operation indication information.
  • the forwarding module 702 is specifically configured to: when the operation indication information indicates that the first network function entity fails, forward the data packet to another SFF, so that another SFF forwards the data packet to the second network.
  • the forwarding module 702 is specifically configured to: when the operation indication information indicates that the first network function entity is running normally, the SFF forwards the data packet to the first network function entity.
  • the receiving module 702 is further configured to receive the backup function available information, and the backup function available information includes another SFF network identifier.
  • the service function forwarder further includes: a storage module 703, configured to: Saving a network identifier of another SFF; a backup network function entity determining module 704 for storing according to the storage module Another SFF network identity identifies the available hot backup network functional entities.
  • the forwarding module 702 is specifically configured to: when the load of the first network function entity is lower than the first load threshold, the SFF forwards the data packet to the first network function entity.
  • the storage module 703 is further configured to record a congestion status of a network function entity of the same type as the first network function entity, and the forwarding module 702 is specifically configured to: when the load of the first network function entity is higher than the first When the load threshold is two, the SFF determines the second network function entity in the non-congested state according to the congestion state, and forwards the data packet to another SFF to cause another SFF to forward the data packet to the second network function entity.
  • the storage module 703 is specifically configured to record, according to the source network function entity of the received data packet, a congestion status of the source network function entity, where the specific record is: if a packet of a network function entity is received Then, the network function entity is recorded in a congested state, and then the congestion degree of the network function entity is adjusted according to the frequency of receiving the data function entity of the network function entity, the data packet size, and the like.
  • the forwarding module 702 is specifically configured to: when the load of the first network function entity is greater than the first load threshold, less than the second load threshold, if the data packet belongs to the same data packet as the last received data packet Transmitted by a network function entity, the second network function entity in the non-congested state is determined according to the congestion state, and the data packet is forwarded to another SFF, so that another SFF forwards the data packet to the second network function entity; If the packet is not sent by the same network function entity, the data packet is forwarded to the first network function entity.
  • the storage module 703 is specifically configured to record that the network function entity that sends the data packet is in a congested state.
  • each of the above modules can be executed by the processor 622.
  • the receiving module 701 and the forwarding module 702 may correspond to the transceiver 750 in the embodiment shown in FIG. 6, and the storage module 703 corresponds to 630 in the embodiment shown in FIG. 6.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product.
  • the computer software product is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of various embodiments of the present invention. .
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne, dans les modes de réalisation décrits, un procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et un dispositif de réacheminement de fonctions de service (SFF), utilisé pour mettre en œuvre une relève à chaud de fonctions de réseau en chaîne de service ou pour mettre en œuvre un équilibrage de charge. Le procédé selon les modes de réalisation de la présente invention comporte les étapes suivantes: le SFF reçoit des paquets de données et, d'après la charge d'une entité locale de fonction de réseau associée au SFF ou des informations indiquant un fonctionnement normal, décide s'il convient de réacheminer les paquets de données vers l'entité locale de fonction de réseau ou de les réacheminer vers un autre SFF, l'entité locale de fonction de réseau associée à l'autre SFF étant une entité de fonction de réseau de relève à chaud ou une entité de fonction de réseau d'équilibrage de charge d'une entité locale de fonction de réseau. Il n'est donc pas nécessaire qu'une entité de fonction de réseau soit la même pour ajouter un trajet afin de mettre en œuvre une relève, ce qui réduit la gestion des trajets et des NSH, réduisant la complexité, et apportant également un mécanisme efficace d'équilibrage de charge pour une SFC dans une architecture répartie.
PCT/CN2017/085897 2016-06-27 2017-05-25 Procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et dispositif de réacheminement de fonctions de service Ceased WO2018001011A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610480898.6A CN106209419B (zh) 2016-06-27 2016-06-27 一种选择网络功能进行数据转发的方法及业务功能转发器
CN201610480898.6 2016-06-27

Publications (1)

Publication Number Publication Date
WO2018001011A1 true WO2018001011A1 (fr) 2018-01-04

Family

ID=57461340

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085897 Ceased WO2018001011A1 (fr) 2016-06-27 2017-05-25 Procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et dispositif de réacheminement de fonctions de service

Country Status (2)

Country Link
CN (1) CN106209419B (fr)
WO (1) WO2018001011A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110784535A (zh) * 2019-10-25 2020-02-11 新华三信息安全技术有限公司 报文转发方法、装置及网络设备
CN113645078A (zh) * 2021-08-16 2021-11-12 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
CN114374608A (zh) * 2020-10-15 2022-04-19 中国移动通信集团浙江有限公司 切片实例备份任务调度方法、装置和电子设备
TWI876330B (zh) * 2022-10-04 2025-03-11 大西譽郎 甘草萃取物

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209419B (zh) * 2016-06-27 2019-12-24 上海华为技术有限公司 一种选择网络功能进行数据转发的方法及业务功能转发器
EP3576479A4 (fr) 2017-02-27 2020-03-04 Huawei Technologies Co., Ltd. Procédé de gestion ainsi qu'unité et système de gestion
US11184283B2 (en) 2018-02-22 2021-11-23 Futurewei Technologies, Inc. Service function chaining congestion tracking
US10924405B2 (en) 2018-02-23 2021-02-16 Futurewei Technologies, Inc. Service function chaining congestion feedback
US10805221B2 (en) * 2018-11-06 2020-10-13 Nanning Fugui Precision Industrial Co., Ltd. Service function chain (SFC) path selection method and system
KR102589484B1 (ko) * 2018-11-23 2023-10-13 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 기능 체이닝 네트워크 서비스
CN112583719A (zh) * 2019-09-29 2021-03-30 中兴通讯股份有限公司 一种业务转发方法、装置、设备及计算机可读存储介质
CN113141307B (zh) * 2020-01-20 2024-07-09 华为技术有限公司 信息更新方法、装置、网络设备以及计算机可读存储介质
CN113535359B (zh) * 2021-07-23 2023-11-10 中国科学技术大学苏州高等研究院 一种多租户云中服务请求调度方法和装置
CN114157612B (zh) * 2021-12-09 2024-11-22 中国电信股份有限公司 流量牵引控制方法和装置、引流装置、流量牵引系统
CN119030918B (zh) * 2023-05-23 2025-10-24 北京星网锐捷网络技术有限公司 一种业务链保护方法、装置、节点以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651680A (zh) * 2009-09-14 2010-02-17 杭州华三通信技术有限公司 一种网络安全部署方法和一种网络安全设备
CN104954274A (zh) * 2014-03-25 2015-09-30 华为技术有限公司 生成转发信息的方法、控制器和业务转发实体
EP3013002A1 (fr) * 2014-10-24 2016-04-27 ZTE Corporation Procédé et système pour analyse intelligente à partir d'une inspection approfondie de statistiques pour chaînage de fonction réseau/service
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的系统及方法
CN106209419A (zh) * 2016-06-27 2016-12-07 上海华为技术有限公司 一种选择网络功能进行数据转发的方法及业务功能转发器

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102752395B (zh) * 2012-07-13 2015-10-28 浙江大学 一种用于分布式数据中心实时业务分配的在线调度方法
CN104765967B (zh) * 2015-04-20 2016-05-11 中国人民解放军国防科学技术大学 一种离网混合可再生能源系统的多目标优化设计方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651680A (zh) * 2009-09-14 2010-02-17 杭州华三通信技术有限公司 一种网络安全部署方法和一种网络安全设备
CN104954274A (zh) * 2014-03-25 2015-09-30 华为技术有限公司 生成转发信息的方法、控制器和业务转发实体
EP3013002A1 (fr) * 2014-10-24 2016-04-27 ZTE Corporation Procédé et système pour analyse intelligente à partir d'une inspection approfondie de statistiques pour chaînage de fonction réseau/service
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的系统及方法
CN106209419A (zh) * 2016-06-27 2016-12-07 上海华为技术有限公司 一种选择网络功能进行数据转发的方法及业务功能转发器

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110784535A (zh) * 2019-10-25 2020-02-11 新华三信息安全技术有限公司 报文转发方法、装置及网络设备
CN110784535B (zh) * 2019-10-25 2022-06-28 新华三信息安全技术有限公司 报文转发方法、装置及网络设备
CN114374608A (zh) * 2020-10-15 2022-04-19 中国移动通信集团浙江有限公司 切片实例备份任务调度方法、装置和电子设备
CN114374608B (zh) * 2020-10-15 2023-08-15 中国移动通信集团浙江有限公司 切片实例备份任务调度方法、装置和电子设备
CN113645078A (zh) * 2021-08-16 2021-11-12 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
CN113645078B (zh) * 2021-08-16 2023-10-27 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
TWI876330B (zh) * 2022-10-04 2025-03-11 大西譽郎 甘草萃取物

Also Published As

Publication number Publication date
CN106209419B (zh) 2019-12-24
CN106209419A (zh) 2016-12-07

Similar Documents

Publication Publication Date Title
WO2018001011A1 (fr) Procédé de sélection d'une fonction de réseau pour mettre en œuvre un réacheminement de données et dispositif de réacheminement de fonctions de service
US11411770B2 (en) Virtual port channel bounce in overlay network
US20230070345A1 (en) Communication method and apparatus
US9729473B2 (en) Network high availability using temporary re-routing
US9100329B1 (en) Providing non-interrupt failover using a link aggregation mechanism
US8948003B2 (en) Fault tolerant communication in a TRILL network
JP5497244B2 (ja) スイッチング・ネットワークにおいてフロー制御を実施するための方法、マスタ・スイッチ、スイッチング・ネットワーク、プログラム、装置、システム
CN114024969B (zh) 一种负载均衡方法、装置和系统
JP2013545359A (ja) スイッチング・ネットワークにおけるスイッチングのための方法、マスタ・スイッチ、スイッチング・ネットワーク、プログラム、装置、システム
US20240267324A1 (en) Packet forwarding method and apparatus
WO2022012145A1 (fr) Procédé, appareil et système d'équilibrage de charges
WO2021232841A1 (fr) Procédé et appareil de communication
EP3534571A1 (fr) Procédé de transmission de paquet de service, et appareil de noeud
KR20150067365A (ko) 가상 섀시 시스템 제어 프로토콜
CN105490937A (zh) 以太虚拟网络网关切换方法和服务商边缘节点设备
GB2602802A (en) Management of radio link failure and deficiencies in integrated access backhauled networks
US20220166721A1 (en) Traffic balancing method, network device, and electronic device
WO2022148714A1 (fr) Gestion de défaillance et de déficiences de liaisons radio dans des réseaux à accès et liaison terrestre intégrés
US8228823B2 (en) Avoiding high-speed network partitions in favor of low-speed links
KR20170000787A (ko) 서비스 펑션 체이닝의 안정성 보장을 위한 sff-sf 간 링크 구성 방법
CN115988074B (zh) 分布式隧道结构的虚拟网关的动态流量重定向
EP4436134A1 (fr) Reroutage de sortie de paquets au niveau d'un dispositif de communication
CN119893493A (zh) 与订户组相关联的虚拟互联网协议地址

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17819008

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

Country of ref document: EP

Kind code of ref document: A1