Computer-implemented method, readable medium and node for forwarding data packets in a network

By using NSH in the network to encapsulate data packets and using the information in the forwarded table to dynamically route data packets, the problems of inconvenient and poor scalability of business function chain management in the existing technology are solved, and flexible and efficient business function chain management and Service quality assurance.

CN112956164BActive Publication Date: 2024-11-19HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980073005.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-11-23
Filing Date
2019-11-22
Publication Date
2024-11-19
Estimated Expiration
2039-11-22

AI Technical Summary

Technical Problem

When providing network value-added services, the existing technology has high operating costs and poor scalability, making it difficult for network operators to flexibly deploy and manage business function chains, resulting in inconvenient static configuration and management of business function chains.

Method used

By using the network service header (NSH) to encapsulate data packets in the network and receive and forward data packets at nodes in the business function chain, the service path and processing value information in the forwarding table are used to determine the service quality of the subsequent nodes, dynamically, Routing packets.

Benefits of technology

It realizes flexible business function chain management, reduces operating costs, improves the utilization efficiency and scalability of network resources, and supports the dynamic configuration of multiple business functions and service quality assurance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112956164B_ABST
    Figure CN112956164B_ABST
Patent Text Reader

Abstract

The disclosed technology relates to forwarding a data packet in a network. The data packet is received at a node, wherein the data packet is encapsulated by a Network Service Header (NSH), and the Network Service Header includes a service path header that identifies a service path. The service path is associated with a treatment value, wherein the treatment value directs a subsequent node to process the encapsulated NSH data packet using quality of service treatment. A forwarding table stored in the node is evaluated to identify the service path and the treatment value of the encapsulated NSH data packet, and a quality of service treatment of the encapsulated NSH data packet is determined. The encapsulated NSH data packet is forwarded to the subsequent node according to the service path indicated in the forwarding table and the quality of service treatment corresponding to the treatment value identified in the forwarding table.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application Serial No. 62 / 770,855, filed on November 23, 2018, and entitled “Service Function Chaining Network Services,” which is incorporated herein by reference as if reproduced in its entirety. Technical Field

[0003] The present invention generally relates to routing data packets in a service function link domain. Background Art

[0004] Network operators, especially mobile network operators, want to provide customers with a variety of value-added services. Examples of such services include deep packet inspection (DPI), parental control, SSL traffic optimization, network address translation (NAT), etc. In the past, network operators usually deployed dedicated network elements to provide special services. However, this approach is not flexible enough, has high operating costs, and is not scalable.

[0005] Recently, network operators have begun to move toward service function chaining, or service chaining. In this approach, each supported service can be modeled as a combination of one or more service functions (SFs), where each service function performs a specific task on a network packet or set of packets. For a given service, the service functions are applied sequentially, i.e., network traffic is directed through them in a specified manner. This technique is called service function chaining, and these chains are often called service function chains (SFCs).

[0006] The entity that selects the appropriate chain for received traffic is often referred to as a 'classifier' (also called a 'service classifier' or 'SFC classifier'). A classifier may also perform a load balancing function to select the least loaded service function chain or to divert traffic away from a service function chain that includes nodes that may need to exit the service. There are multiple classifiers active at any time. The service function chain (including the service functions contained in the service function chain) is determined by a static configuration. To change the chain, the configuration is edited by a system user or the like and installed to the service function forwarders along the chain. Summary of the invention

[0007] According to one aspect of the present invention, a computer-implemented method for forwarding a data packet in a network is provided, comprising: receiving the data packet at a node belonging to a service function chain (SFC) in the network, wherein the data packet is encapsulated by a network service header (NSH), the network service header comprising a service path header identifying a service path, the service path being associated with a processing value, wherein the processing value directs one or more subsequent nodes in the network to process the encapsulated NSH data packet using quality of service processing; evaluating a forwarding table stored in the node to identify the service path and the processing value of the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; and forwarding the encapsulated NSH data packet to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0008] Optionally, in any of the above aspects, the service path header includes: a service path identifier (SPI), wherein the service path identifier includes a path index (PI) indicating the service path and a processing index indicating the processing value; and a service index (SI) indicating the position of the encapsulated NSH data packet in the service function chain, and the processing value indicates the quality of service processing of the encapsulated NSH data packet.

[0009] Optionally, in any of the above aspects, the SPI includes one or more most significant bits of the service path header, and the SI includes one or more least significant bits of the service path header, wherein the total number of the one or more most significant bits is 24; the total number of the one or more least significant bits is 8; and the total number of the one or more bits included in the service path header is 32.

[0010] Optionally, in any of the above aspects, the processing index includes one or more bits of the SPI, the PI includes one or more bits of the SPI, the number of bits of the SPI included in the processing index is greater than or equal to 1 and less than or equal to 24, and the sum of the number of bits of the SPI included in the processing index and the number of bits of the SPI included in the PI is 24.

[0011] Optionally, in any of the above aspects, the one or more bits included in the PI are located at a fixed position of the one or more highest order bits in the SPI, the one or more bits included in the processing index are located at a fixed position of the one or more lowest order bits of the SPI, or, the one or more bits of the PI and the processing index are randomly located in the SPI.

[0012] Optionally, in any of the above aspects, the forwarding table includes n entries corresponding to each service path of the encapsulated NSH data packet, wherein n is the number of different processing values ​​associated with the service path.

[0013] Optionally, in any of the above aspects, the service path header includes the service index (serviceindex, SI), wherein the service index indicates the processing value and the position of the data packet in the service function chain, and the processing value indicates the quality of service processing of the encapsulated NSH data packet.

[0014] Optionally, in any of the above aspects, the forwarding table includes a service path identifier (SPI) indicating the service path, a service index (SI) indicating the position of the encapsulated NSH data packet in the service function chain, and a processing index indicating the processing value, wherein the processing value indicates the quality of service processing of the encapsulated NSH data packet.

[0015] Optionally, in any of the above aspects, the network is an SFC-enabled domain.

[0016] Optionally, in any of the above aspects, the computer-implemented method further comprises: processing the encapsulated NSH data packet according to a service function associated with the node.

[0017] Optionally, in any of the above aspects, the computer-implemented method further comprises: decapsulating the encapsulated NSH data packet by removing the NSH, and forwarding the decapsulated data packet to a destination address determined according to information in the header of the decapsulated data packet.

[0018] According to another aspect of the present invention, a non-transitory computer-readable medium is provided, storing computer instructions for forwarding a data packet in a network, characterized in that when one or more processors execute the instructions, the one or more processors perform the following steps: receiving the data packet at a node belonging to a service function chain (SFC) in the network, wherein the data packet is encapsulated by a network service header (NSH), the network service header includes a service path header identifying a service path, the service path is associated with a processing value, wherein the processing value guides one or more subsequent nodes in the network to process the encapsulated NSH data packet using quality of service processing; evaluating a forwarding table stored in the node to identify the service path and the processing value of the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; and forwarding the encapsulated NSH data packet to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0019] According to another aspect of the present invention, a node for forwarding a data packet in a network is provided, the router comprising: a non-transitory memory including instructions; one or more processors communicating with the memory, wherein the one or more processors execute the instructions to: receive the data packet at a node belonging to a service function chain (SFC) in the network, wherein the data packet is encapsulated by a network service header (NSH), the network service header comprising a service path header identifying a service path, the service path being associated with a processing value, wherein the processing value directs one or more subsequent nodes in the network to process the encapsulated NSH data packet using quality of service processing; evaluate a forwarding table stored in the node to identify the service path and the processing value of the encapsulated NSH data packet, and determine the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; forward the encapsulated NSH data packet to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0020] According to another aspect of the present invention, a node for forwarding a data packet in a network is provided, the node comprising: a receiving module, configured to receive the data packet at a node belonging to a service function chain (SFC) in the network, wherein the data packet is encapsulated by a network service header (NSH), the network service header comprising a service path header identifying a service path, the service path being associated with a processing value, wherein the processing value instructs one or more subsequent nodes in the network to process the encapsulated NSH data packet using quality of service processing; an evaluation module, configured to evaluate a forwarding table stored in the node to identify the service path and the processing value of the encapsulated NSH data packet, and determine the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; and a forwarding module, configured to forward the encapsulated NSH data packet to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0021] The summary of the invention briefly introduces some concepts, which will be further described in the detailed description. The summary of the invention is not intended to provide the key features or basic features of the subject matter claimed in the patent application, nor is it intended to determine the scope of the subject matter claimed in the patent application. The subject matter claimed in the patent application is not limited to the implementation method that solves any or all problems mentioned in the background technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The various aspects of the present invention are illustrated by way of example and not limitation in the accompanying figures, in which like references indicate similar elements.

[0023] Figure 1 An exemplary system for performing service function chaining to provide services to a mobile network including end users.

[0024] Figure 2 for Figure 1 Example diagram of the service function chain and network elements in a mobile network.

[0025] Figure 3 An example of a network service header packet structure.

[0026] Figure 4 This is an example of forwarding a packet along a service function path.

[0027] Figure 5 This is the network service header format.

[0028] Figure 6 is an exemplary embodiment of a flow monitoring device.

[0029] Figure 7 for Figure 5 The service path identifier field of the service path header.

[0030] Fig. 8A An exemplary forwarding information base table for a service function forwarder.

[0031] Figure 8B This is another example of a forwarding information base table of a service function forwarder.

[0032] Fig. 9 For Figure 1 Flowchart of forwarding data packets in the service function chain of a network.

[0033] Fig.10 The block diagram is a network processing device 801 that can be used to implement various embodiments of the technology of the present invention. DETAILED DESCRIPTION

[0034] The present invention will now be described with reference to the accompanying drawings, which generally relate to a service function chain.

[0035] Various embodiments for routing and implementing business functions along business function chains and business function paths are disclosed herein. Many emerging services, such as multimedia transmission and virtual private networks, require careful allocation of resources in Internet Protocol (IP) networks. In order to allocate sufficient resources for such services, service providers need to know the boundaries to support the provided traffic. The Service Level Agreement (SLA) between the customer and the service provider defines these boundaries, which constitute the traffic strategy or mechanism for measuring and handling the quality of service (QoS). Traffic within the boundaries is served by the network according to the expected QoS specified in the SLA, while excess traffic is forwarded without any guarantee.

[0036] Typically, SLAs are enforced at the interfaces between different network domains. As explained in detail below, edge nodes or border nodes / routers measure and mark incoming traffic to ensure that traffic complies with established policies. In one embodiment, the network service header (NSH) of the NSH encapsulated data packet can be used to mark the incoming data packet with a "color" to identify various policies. The NSH header can use identification information (such as a bit in an NSH header field) to indicate a specific color (or processing value) to indicate a specific regulatory (or service) mechanism used to process the data packet. In one embodiment, the bit is set in the service path identifier (SPI) of the NSH header. In another embodiment, the bit is set in the service index (SI) of the NSH header. Once the data packet is marked, the congestion control mechanism within the network domain will use the results of the marking mechanism to determine the data packets to be processed and the data packets to be discarded during congestion.

[0037] It should be understood that the current embodiments of the present invention can be implemented in many different forms, and the scope of the claims should not be interpreted as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to make the present invention thorough and complete, and to fully convey the concept of the embodiments of the present invention to those skilled in the art. In fact, the present invention is intended to cover substitutes, modifications and equivalents of these embodiments within the scope and spirit of the present invention defined by the appended claims. In addition, in the following detailed description of the current embodiments of the present invention, many specific details are set forth to provide a thorough understanding. However, it should be clear to those of ordinary skill in the art that the current embodiments of the present invention can be practiced without these specific details.

[0038] Figure 1An exemplary system for performing service function chaining to provide services to a mobile network including end users. System 100 includes a service function chain (SFC) network 105, a mobile network 110, and a network 107 (such as the Internet). Typically, an SFC includes a series of service functions (or service function instances) residing on each network node. That is, an SFC is an ordered set of service functions (SFs) and sequencing constraints, applied to data packets, data frames, and / or data streams. An SFC may include one or more service function paths (SFPs) along the SFC. When traffic is forwarded from a user or user device (such as user device 112) through an SFC, the data packets in the traffic traverse the SFPs in order and are processed by various service functions, wherein each service function applies a specific function, such as a firewall, network access translation (NAT), deep packet inspection (DPI), etc., and then forwards the data packet to the next network node.

[0039] exist Figure 1 In an embodiment of the present invention, the SFC network 105 includes a controller 115, an SFC enabling domain 117, and a boundary node 121. The controller 115 can control the SFC enabling domain 117, wherein the enabling domain 117 includes an SFC classifier 117A, a service function forwarder (SFF) 117B, and a service function (SF) 117C. In particular, the controller 115 may include: a path determination module 115A, for determining a path (e.g., a service function path (SFP)) for processing a data packet; a monitoring unit 115B, for monitoring the status information of the SFC classifier node 117A, the SFF 117B, and the SF 117C; a path establishment module 115C, for establishing the determined path to the SFC enabling domain 117; and a policy manager 117D, for managing the processing mode of the data packet according to various policies or agreed services (referred to as quality of service processing in this document alone or together). The SFC enable field 117 may then process the received data packet according to the SFP set by the controller 115 .

[0040] The policy manager 115D configures the network nodes and the border nodes 121 to control the coloring of the packets within the SFC-enabled domain 117. For example, the policy manager 115D can set the network node to color all Voice Over IP (VoIP) packets of a particular flow with "green" (e.g., high priority) and color all File Transfer Protocol (FTP) packets of a particular flow with "yellow" (e.g., low priority). The colors can be associated with one or more Quality of Service (QoS) processing parameters, such as predefined differentiated services code point (DSCP) values ​​and other possible values ​​or characteristics. Although not shown, the policy manager 115D can be coupled to and communicate with any network node.

[0041] In one embodiment, the policy manager 115D provides a mechanism by which a network administrator can define the initial QoS treatment applied to different services and flows within the SFC-enabled domain 117. For example, an administrator can define the initial QoS treatment of a particular flow by setting an initial DSCP value in a data packet, which can be associated with a specific color marked in the data packet. Through the color marked in the data packet, the policy manager 115D can communicate with a meter and marker (described below) or other components to dynamically color the data packets for each flow based on the current bandwidth or throughput of the SFC-enabled domain 117 and the bandwidth requirements of each specific flow.

[0042] The service classifier 117A is a node that classifies data packets and assigns them to SFCs. The service classifier may refer to a functional entity that performs classification or service classification. Here, classification may refer to the following process: classifying traffic by customer / service unit through policies, and classifying the SF used by the corresponding customer according to the profile. In other words, classification may be performed through the forwarding policy suitable for the traffic and the identification of the user and network profile.

[0043] The physical locations of the SFC classifier 117A, SFF 117B, and SF 117C may be the same (or different). Any one or more of these components may be an independent process in a physical node or a virtualized node. In order to uniquely identify the SF, each SF is given a unique identifier, called a business function identifier. In addition to the business function identifier, each SF also carries a business function locator attribute. The business function attribute may be an Internet Protocol (IP) address, a fully qualified domain name (FQDN), or a layer 4 port number. The SFC classifier and SF use the locator as the destination address of the traffic. In order to implement the SFC network 105, the data plane usually carries the actual traffic; the control plane is usually used to manage and coordinate the traffic between the service nodes.

[0044] The SFF 117B forwards the received data packet to the SF 117C. That is, the SFF 117B may forward the traffic or data packet to at least one SF 117C. In one embodiment, the SFF 117B may forward the data packet to another SFF 117B.

[0045] The service function path (SFP) (also referred to as an explicit path) determined by the path determination module 115A may refer to a physical or virtual network path through which a data packet passes to implement the abstract concept of SFC. As understood (and described in the exemplary embodiment), one or more SFFs 117B and one or more SFs 117C may exist on the SFP.

[0046] The SF 117C node has the function of performing specific processing on data packets and can act on various layers of the protocol stack (such as the network layer or other OSI layers). The SF can be implemented as a virtual element or a physical network element, or it can be embedded in a physical network element. One or more SFs can be embedded in the same network element. Multiple service functions or instances of service functions can exist simultaneously in the same domain. In one embodiment, the SF 117C can be a third-party service node for implementing certain functions of the value-added service function chain. Examples of SF include, but are not limited to, firewalls, wide area networks (WAN) and application acceleration, deep packet inspection (DPI), lawful interception (LI), server load balancing, network address translation (NAT)-44, NAT-64, Internet Protocol version 6 network prefix translation (NPTv6), HOST_ID injection, hypertext transfer protocol (HTTP) header enhancement, and transmission control protocol (TCP) optimization.

[0047] The border node 121 can be an entry point and an exit point for traffic entering the SFC network 105 from an external network (such as the mobile network 110) and traffic entering the mobile network 110 from the SFC network 105. For example, in the upstream direction, the border node 121 can receive encrypted traffic from the client device 112 of the mobile network user and leave the mobile network 110 through the PGW 114 or any other network element. The border node 121, which can access decryption information (such as an SSL / TLS private key), can decrypt the traffic, establish a secure (SSL / TLS) session with the client device 112, and then perform certain value-added services on the traffic from the client device 112. The traffic then continues to flow to the content provider source in the network 107, or returns to the mobile network 110 and / or the client device 112, depending on the specific function. Similarly, the SFC network 105 can perform value-added services on the downstream traffic to the client device 112, encrypt it in the session, and then send it to the client device 112 through the gateway. The mobile network 110 is described below.

[0048] It should be understood that there may be one or more border nodes 121 and that the system 100 is not limited to a single edge node or border node as an ingress source and an egress source between networks.

[0049] Any node (e.g., SFC classifier node 117A, SFF 117B, SF 117C, and boundary node 121) can be a device, including a processor 119A, a memory 119B, and a communication interface 119C. Processor 119A is used to perform processing functions, including encryption, decryption, authentication label creation and authentication, and NSH data and table updates, as described below. Memory 119B is used to store data used by processor 119. Communication interface 119C is used to send and / or receive network data packets, tickets, keys, encryption algorithms, authentication label generation algorithms and authentication algorithms, and any other data (all not shown).

[0050] The mobile network 110 includes conventional mobile network components, such as a PDN Gateway (PGW) 114, which serves as an anchor point for user equipment (also referred to herein as user equipment 112) to engage in a packet network session and manages policy enforcement features. A mobile management entity (MME) 116 for tracking user equipment 112 and facilitating voice and data sessions, and a serving gateway (SGW) 118 for managing user plane mobility are coupled to a base station 120. Also included in the mobile network 110 is a Home Subscriber Server (HSS) 122 for maintaining a user database required by other network elements, and a Policy & Charging Rules Function (PCRF) 124 for maintaining policies and charging rules, wherein the policies and charging rules include user information (such as account opening data, services subscribed by the user, etc.) and bearer and QoS information associated with endpoints within the operator's network. In the systems and methods described herein, these components function in a conventional manner modified by the teachings herein.

[0051] Also disclosed are interfaces from PGW 114 to network 107 and from PGW 114 to SFC network 105 through border node 121. For example, these interfaces can be LAN connections such as S(Gi) interfaces. However, specific network configurations and interfaces are non-restrictive examples. It should also be understood that, although the SFC network 105 is depicted outside the mobile network 110, the mobile network 110 can also include the SFC network 105 being deployed in the mobile network 110. In addition, it should be understood that the SFC network 105 can be a machine deployed in the entire network 107 (such as the Internet).

[0052] Figure 2 for Figure 11 and 2. The network element (or node) 200 may be suitable for implementing the disclosed embodiments. The network element 200 may be any device (e.g., a modem, a switch, a router, a bridge, a server, a client, a controller, etc.) that transmits or assists in transmitting data through a network, system, and / or domain. For example, the network element 200 may be in Figure 1 The network element 200 is implemented in any node shown, such as the SFC classifier 117A, the SFF 117B, the SF 117C and the border node 121. The network element 200 includes an I / O port 210, a transceiver (Tx / Rx) 220, a processor 230, a memory 240 having a business function module 250, and an I / O port 310. The I / O port 210 is coupled to the Tx / Rx 220, and the Tx / Rx 220 can be a transmitter, a receiver, or a combination thereof. The Tx / Rx 220 can send and receive data through the I / O port 210. The processor 230 is used to process data, and the memory 240 is used to store data and instructions for implementing the embodiments described herein. The network element 200 may also include an electrical-to-optical (EO) component and an optical-to-electrical (OE) component coupled to the I / O port 210 and the Tx / Rx 220 for receiving and sending electrical signals and optical signals.

[0053] The processor 230 can be implemented by hardware and software. In one embodiment, the processor 230 can be implemented as one or more central processing unit (CPU) chips, logic units, cores (e.g., multi-core processors), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and digital signal processors (DSPs). The processor 230 communicates with the I / O port 210, Tx / Rx 220, and the memory 240.

[0054] The memory 240 may include one or more disks, tape drives, and / or solid-state hard disks, and may be used as an overflow data storage device to store such programs when such programs are selected for execution, and to store instructions and data read during program execution. The memory 240 may be volatile and non-volatile, and may be a read-only memory (ROM), a random access memory (RAM), a ternary content-addressable memory (TCAM), and a static random access memory (SRAM). The business function module 250 is implemented by the processor 230 to execute instructions for implementing various embodiments, thereby routing and forwarding data packets along different SFPs and forwarding paths according to SFP information; generating SFP entries according to SFP information; generating a steering strategy according to SFP information; generating a local or internal forwarding strategy. Alternatively, the business function module 250 is implemented as instructions stored in the processor 230.

[0055] Figure 3 1 is an example of a network service header data packet structure. In order to guide the SFC enable field (such as SFC enable field 117 ( Figure 1 )), the Internet Engineering Task Force (IETF) has standardized a header called the Network Service Header (NSH). The NSH encapsulates data packets as described in IETF RFC 8300 "Network Service Header (NSH)", which is incorporated by reference. Traffic within the SFC-enabled domain 117 is directed as described in RFC 7665 "Service Function Chaining (SFC) Architecture", which is also incorporated by reference herein. As explained in the IETF specification, the NSH is applied to the data packet (or frame), wherein the NSH includes service path information and optional metadata added to the data packet for creating a service plane. Subsequently, an outer transport encapsulation is applied to the NSH for network forwarding. Upon entering the SFC-enabled domain 117, a service classifier (such as SFC classifier 117A) adds the NSH to the data packet. The NSH is removed by the last SFF in the service function chain (eg, SFF 117B) or the SF that consumes the data packet (eg, SF 117C).

[0056] More specifically, as shown, data packet 302 may include a transport header 306 and an information packet 308. For example, transport header 306 may include addressing and / or other control information associated with the transport layer of the Open Systems Interconnection (OSI) network layer model. For example, transport header 306 may be an Internet Protocol version 4 (IPv4) header or an Internet Protocol version 6 (IPv6) header. For example, information packet 308 may include data of a payload. When data packet 302 travels through the network, NSH 312 may be used to encapsulate data packet 302. Encapsulation is typically performed at a classification node (such as SFC classifier 117A) to produce a packet such as Figure 3 Encapsulated data packet 304 is shown. NSH 312 provides various facilities for controlling and monitoring the progress of the data packet through subsequent nodes (e.g., SFF and SF) until the data packet is decapsulated at some subsequent node, thereby removing NSH 312 and returning data packet 302.

[0057] Combined with the following Figure 4 An example of a data packet 302 traveling through a network is described. Figure 5 NSH 312 is described in detail.

[0058] Figure 4 is an example of forwarding a data packet along a service function path. Network 400 (eg, SFC enabled domain 117 ( Figure 1 )) includes an ingress node (such as SFC classifier 117A) and a network node (such as SFF 117B and / or SF 117C). In one embodiment, the SFF 117B node may also be an egress node from which the data packet is decapsulated and exits the network 400. It should be understood that the network 400 can be configured as shown or in any other configuration including any number of network nodes (including ingress nodes and egress nodes).

[0059] The SFC classifier 117A node is configured as an SFC or SFP ingress node (also referred to as a head end of an SFP) for inserting the SPI into the NSH 312 and encapsulating the data packet 302 with the NSH 312 to form an encapsulated NSH data packet 304 ( Figure 3 In one embodiment, the SFC classifier node 117A is a SFF 117B node.

[0060] The SFF 117B node may include one or more ports and one or more SF 117Cs connected to each port. A port connected to a SF 117C refers to a port of the SFF 117B network node that is physically coupled to, used to couple to, associated with, or used to interact with the SF 117C. The SFF 117B network node is used to transmit a data packet (such as a data packet encapsulated with NSH 312 (i.e., encapsulated data packet 304, Figure 3 )) is forwarded to the connected SF 117C and other network nodes.

[0061] The SFF 117B network node is used to transmit the NSH encapsulated data packet 304 through the network 400. As described above, the SFF 117B network node at the end of the SFC or SFP is the egress node or tail end of the SFP.

[0062] The SFC classifier 117A network node, the SFF 117B network node, and the SF 117C network node may be coupled to each other via one or more tunnels and / or links. Examples of tunnels include, but are not limited to, multiprotocol label switching (MPLS) tunnels and virtual extensible local area network (VxLAN) tunnels. Links may include physical links, such as electrical links and / or optical links, and / or logical links (e.g., virtual links).

[0063] In the depicted example, incoming packet 302 ( Figure 3 ) or frames from mobile network 110 or network 107 ( Figure 1 ) enters a service link domain, such as SFC enabled domain 117. Data packet 302 enters SFC enabled domain 117 through an ingress node (e.g., SFC classifier 117A) and leaves the service domain through an egress node (e.g., SFF 117B). Although the described example shows a single ingress node and a single egress node, it should be understood that multiple ingress nodes and multiple egress nodes may exist within a service domain.

[0064] After receiving the data packet 302 from the service network, the SFC classifier 117A network node adds the NSH header 312 to form the NSH data packet 304 ( Figure 3) to encapsulate the data packet 302. The NSH header 312 effectively guides the path along which the data packet is processed and / or controlled at subsequent nodes. That is, the path of the encapsulated NSH data packet 304 traverses the SFPs of the network 400 according to the NSH header 312. For example, the NSH data packet 304 can be forwarded along a specific SFP (such as SFP1 represented by the solid black arrow line). The node or virtual function as SFF 117B is responsible for forwarding traffic to the connected SF 117C.

[0065] When NSH packet 304 arrives at the egress node (eg, SFF 117B), NSH packet 304 is decapsulated (ie, the NSH header is removed) and packet 302 leaves SFC-enabled domain 117 .

[0066] Figure 5 The network service header format 500 is composed of a basic header 502, a service path header 504, and a context header 506, each of which can be 4 bytes, as detailed in IETF RFC8300. The basic header 502 provides information about the service header and payload protocol; the service path header 504 provides the path identifier and position in the service path; the context header 506 carries metadata (i.e., context data) along the service path (or SFP). The fields in the NSH 500 format are defined as follows:

[0067] • The "Ver" field indicates the NSH version - currently only version 0 is specified or used.

[0068] The "O" field is 1 bit. When the value is 1, it indicates that the data packet is an OAM data packet that requires some kind of operation, administration and maintenance (OAM) processing.

[0069] The five fields marked "U" are 1 bit each, are currently unspecified, and need to be sent as 0 and ignored when received.

[0070] The "TTL" field is used for loop prevention and is decremented at each node that processes the NSH header. If the TTL is 0, the encapsulated packet is discarded.

[0071] "Length" is the length of the NSH in 4-byte words.

[0072] "MD Type" is the type of variable length metadata that appears at the end of the NSH.

[0073] "Next Protocol" indicates the protocol type of the information packet after the NSH or initial portion of the information packet. Figure 3 ) indicates the protocol type of the information packet or the initial part of the information packet. When NSH 312 ( Figure 3 ), the transport header 306 is changed to indicate that the data after the transport header 306 starts with the NSH 312, and the indication of the protocol type of the packet content that was already in the transport header 306 before the NSH 312 was added is placed in the "Next Protocol" field of the NSH 312. The situation is reversed when the packet is decapsulated and the NSH 312 is removed, that is, when the protocol type indication in the "Next Protocol" field of the removed NSH 312 is placed in the transport header 306.

[0074] The "Service Path Identifier (SPI)" and "Service Index (SI)" can be used in conjunction with controlling the processing and routing of packets in the network. Typically, the SPI uniquely identifies the SFP selection. The SI provides the location within the SFP and is decremented at each SFF node that processes the NSH 312. The SI is used in conjunction with the SPI to determine the next SFF / SF in the path.

[0075] "Metadata" is variable length information of the type provided by "MD Type", which can be used for various purposes.

[0076] Using NSH format 500, NSH-aware nodes (which may include SFC classifiers, SFFs, and SFs) may alter the contents of NSH format 500. These nodes may take several actions that may be NSH-related, including but not limited to:

[0077] Insert or remove NSH: These actions can occur at the start and end of the service path respectively. The SFC classifier inserts the NSH at the beginning of the SFP. At the end of the SFP, the SFF removes the NSH and then forwards or transmits the decapsulated data packet.

[0078] Selecting a service path: The service path header 504 provides service path information and is used by the SFF to determine the correct service path selection. The SFF uses the service path header 504 to select the next SF or SFF in the service path.

[0079] Update NSH: SFF decrements the Service Index (SI) by 1. If the SFF receives a packet whose SPI and SI do not correspond to a valid next hop in a valid SFP, the SFF discards the packet. The classifier may also update the context header 506 if a new / updated context is available.

[0080] Business policy selection: SF selects and executes policies (i.e., business actions such as allow or deny) derived from NSH. The metadata shared in NSH can provide a range of business-related information, such as traffic classification.

[0081] Figure 6 6 is an exemplary embodiment of a flow monitoring device. As shown, a flow monitor (or regulator) 600 includes a meter 610, a marker 620, a processor 650, and a memory 660, etc. The flow monitor 600 is connected to the processor 650 for operation, wherein the processor 650 receives instructions from the memory 660 (or some other similar source) and processes them, as understood.

[0082] Traffic monitor 600 typically measures the flow of IP packets in a network and marks the packets in the flow with a “color” (e.g., packet 302, Figure 3 For example, metering and marking incoming IP packet flows can be used for ingress policing of services, where the policing policy is determined by the policy manager 115D ( Figure 1 ) etc. In one embodiment, the traffic monitor 600 is located or resides in an edge node or a border node (such as the border node 121 ) in the SFC network 105 .

[0083] The meter 610 can operate in one of two modes to indicate color. In color-blind mode, the meter 610 assumes that the data packets 302 entering the traffic monitor 600 are colorless. In color-aware mode, the meter 610 assumes that some previous entity has pre-colored the incoming data packets 302 so that each data packet has a color, such as marked as green, yellow, or red. This is a label, typically encoded as one or more bits associated with the traffic in the NSH header, which can be used to affect the processing of the traffic, or for traffic measurement or other purposes defined by the network operator. In one embodiment, the color is encoded into the SPI field of the data packet in the NSH header 500 format, as described in detail below.

[0084] Marker 620 colors (or recolors) the packets based on the results of meter 610. When policing the incoming IP packet stream, packet 302 can be marked red when it exceeds the peak information rate (PIR), otherwise it can be marked yellow or green depending on whether it exceeds the committed information rate (CIR). PIR is the burstable rate set for a network node (e.g., a router or switch), allowing for throughput overhead, while CIR is the guaranteed or capped committed rate. For example, a CIR of 10 Mbit / s and a PIR of 12 Mbit / s can achieve a minimum rate of 10 Mbit / s, while burst / spike control can be implemented, allowing for an additional 2 Mbit / s of throttling.

[0085] More specifically, IETF RFC 2697 and IETF RFC 2698 define a single rate three color marker (srTCM) and a two rate three color marker (trTCM), respectively, which can be used as components in a traffic monitor, and the contents are incorporated by reference. IETF RFC 4115 defines a two rate three color differential service marker for efficiently processing incoming traffic of different services, which can also be used as a component in a traffic monitor, and is also incorporated by reference.

[0086] The srTCM described in IETF RFC 2697 marks packets in an IP flow based on the flow rate CIR and two different burst sizes: committed burst size (CBS) and excess burst size (EBS). Consistent with the above description, if the packet does not exceed the CBS, it is marked as "green" (e.g., by marker 620); if the packet exceeds the CBS but does not exceed the EBS, it is marked as "yellow"; if the packet exceeds the CBS and the EBS, it is marked as "red". A limitation of srTCM is that it uses the length of the burst flow rather than the peak rate to determine the color associated with the flow. Then, services or service levels are provided to the flow based on the color of the flow.

[0087] trTCM, described in RFC 2698, marks packets in an IP flow according to two different flow rates (PIR and CIR) and corresponding burst sizes (CBS and PBS). According to trTCM, if a packet exceeds the PIR, it is marked as "red"; if the packet does not exceed the PIR, it is marked as "yellow" or "green" depending on whether the packet exceeds the CIR. By using two rates: peak traffic rate (or simply, peak rate) and committed rate, trTCM is able to monitor peak rate traffic and committed rate traffic separately.

[0088] Both srTCM and trTCM may use a metering device that meters each packet in a traffic flow and forwards or passes the packets to a marker (such as marker 620) to pre-color the packets. The details of the pre-coloring process and the manner in which the meter detects or determines the color of the packet are implementation specific and are outside the scope of the RFC and this document. The RFC discloses that the marker recolors the packet based on the results of the meter and provides an example of encoding the color as a code point in the DiffServ (DS) field of the packet in a per-hop behavior (PHB) specific manner and refers to IETF RFC 2474 for more information. According to RFC 2597, the color can also be encoded as the discard priority of the packet.

[0089] It should be understood that although the referenced RFCs describe the color rate marking algorithm in the context of an Internet Protocol (IP) based packet switching network, such an algorithm may also be implemented in a communication network such as a cell switching network.

[0090] In one exemplary embodiment of marking colors, the identification color of the incoming data packet 302 can be used to control the actions of nodes (e.g., SFF 117B or SF 117C) that process the NSH header 312 as it traverses a network (e.g., SFC network 105). The actions taken by the node are configurable and can include: the node processing a packet with a higher or lower priority, the node processing a packet that would not otherwise be processed, or the node ignoring processing of a packet that would otherwise be processed. The ability to perform these actions (or similar actions) may help operators meet service level agreements (SLAs) by coloring traffic according to customer categories.

[0091] In a second exemplary embodiment of marking colors, the indicated colors can be used to designate traffic that exceeds the quota allowed for a particular customer or customer class. For example, a customer's traffic over a period of time can be initially set to one color, and when the customer's cumulative traffic over that period of time exceeds the quota, a different color can be assigned to subsequent traffic over that period of time (until the quota is renewed at the end of that period of time). In another example, a running average traffic rate can be maintained, and the color can be marked based on whether the rate is below or above the customer's purchased rate. In yet another example, two or more colors can indicate traffic within the quota, traffic slightly above the quota, or traffic far above the quota.

[0092] In a third exemplary embodiment of marking colors, the traffic color can be set to a value that changes every N packets in a flow, where a "flow" is defined as all packets or a subset of packets set to pass through a particular node in a traffic path. Subsequent nodes can meter the number of packets of each color, assuming that processing packets along the path should maintain the number of packets in the flow, or a certain number of packets in the flow should be dropped or a certain number of packets in the flow should be generated. Any deviation from the number of packets received and the expected number of packets can be reported. Subsequent nodes receiving packets can also detect delayed or out-of-order packets, where a packet with a particular color is received after a packet with a subsequent transmission color is sent.

[0093] In one embodiment, when enough colors are available (i.e., there are enough bits available to indicate the colors in the packet header), colors can be used for different purposes simultaneously. For example, this can be achieved by encoding multiple bits to include any one or more of the above examples.

[0094] Figure 7 for Figure 5 In one embodiment, the service path identifier (SPI) field 702 may be used to indicate the NSH format 500 ( Figure 5 Unlike conventional mechanisms, SPI field 702 allows for indicating color (traffic) without using any undefined ("U") bits in NSH format 500 and without changing any other fields in NSH format 500 (e.g., fields in the base header or context header).

[0095] In the described embodiment, the SPI field 702 includes two fields: a path index (PI) 704, which effectively identifies the path of the NSH encapsulated data packet 304; and a color portion 706 (also referred to herein as a processing index), which includes bits reserved for assigning traffic colors on the path of the NSH encapsulated data packet 304. As described above, when entering a specific SFC-enabled domain, the color of the traffic can be pre-colored (i.e., the color can be pre-set) or colored (or re-colored) by the ingress node. In this case, the coloring (or re-coloring) can be performed based on the results of metering the data packets received by the ingress node, as described above.

[0096] As shown, the SPI field 702 includes 24 bits, which can be allocated between the PI 704 and the color portion 706. The 24 bits in the SPI 702 field are the set number specified by the service path header 504 in the NSH format 500 specified by RFC 8300. For example, the number of low-order bits in the SPI field 702 can be used to indicate the color of the traffic, and the high-order bits in the SPI field 702 can be used to identify the service path of the NSH encapsulated data packet 304. The number of low-order bits is identified as the color portion 706, which includes N bits. The high-order bits are identified as the PI 704, which includes (24-N) bits. Therefore, if N bits (e.g., N low-order bits) are used to indicate the color of the traffic along the service path, the remaining (24-N) bits are used in the PI 704 to identify the service path itself.

[0097] Although not described, in one embodiment, a service index (SI) field may also be used as a mechanism to indicate color in the NSH format 500. The SI field includes 8 bits that are divided between the SI bits and the bits indicating the traffic color of the packet. The 8 bits in the SI field are a set number specified by the service path header 504 in the NSH format 500 specified by the RF 8300. In operation, the bits in the SI field may be arranged in a manner similar to the bits in the above-described SPI embodiment.

[0098] In one embodiment, the SPI 702 and SI fields may be used together as a mechanism to indicate color in the NSH format 500 .

[0099] In the SPI or SI embodiments, the color of the traffic may be indicated by one or more bits in a fixed position of the SPI or SI field. In one embodiment, the SPI field 702 is used and any of the 24 bits in the field may be used to indicate the color of the traffic. In another embodiment, the SI field ( Figure 5), any of the 8 bits in this field can be used to indicate the color of the traffic. Bits not used to identify the traffic color can be used to indicate SI. Whether SPI or SI is used, any number of high-order bits, any number of low-order bits, or any number of scattered bits can be used.

[0100] The node receiving the data packet 302 processes the data packet according to the NSH header 312. In particular, the NSH header 312 can be used to forward the data packet at the service plane layer. The SPI 702 and SI are used for this purpose. More specifically, a unique SPI is used to identify a given service path instantiation of a service function chain, and the SI is initialized to 255 or a number between 255 and the total number of hops between the SF and each SFF in the service function chain, and is decremented at each service node as the data packet (frame) is transmitted along the service path.

[0101] In one example, reference Figure 1 Each NSH-based forwarding node (e.g., SFC classifier 117A or SFF 117B) in SFC-enabled domain 117 may include a forwarding table (also referred to as a path table) that is responsible for associating the contents of an incoming packet with a corresponding port or interface (for the next hop) that can receive and forward the packet. Fig. 8A and Figure 8B As described, the forwarding table may include, among other fields, the SPI 702, a service index (SI) and / or a color part (or a processing index).

[0102] In one embodiment, for each n different number of colors used to indicate traffic in the NSH header 312, there are n SPI 702 entries and corresponding n SI entries in the forwarding information base (FIB) for each service path. In contrast, when the color of the traffic is not included in the table, a single SPI 702 and corresponding service index (SI) entry may be used for each service path. Since the color may be determined based on the color portion 706 of the SPI 702, any additional information used to implement the traffic color may be included in the path lookup table.

[0103] In another embodiment, a separate table indexed by color (processing index) can be accessed or evaluated to determine the processing of a data packet according to the color of the data packet. In this embodiment, each SFF 117B is used to interpret the number of the lowest bits indicating the color in the SPI 702. In addition, a specific color has a corresponding quality of service processing specified in a separate table, regardless of the highest bit in the SPI 702. In this case, the forwarding table can be based on the highest bit of the SPI 702 and the SI (excluding the color bit), and a separate column in the forwarding table can identify the color to indicate the quality of service processing, as further described below.

[0104] Fig. 8A 800A can be stored in a network node (such as SFF117B). As shown, the forwarding table 800A includes SPI 702 and SI 802 in addition to other fields. SPI 702 can be divided into two fields: path index (PI) 704 and color part 706 (or processing index), as described above in conjunction with Figure 7 It is understood that the SPI 702 need not be divided into two fields, but bits at any random or fixed position may be used within the SPI 702, or may be divided into more than two fields. In addition, the forwarding table 800A may also include various other fields such as output port, output encapsulation, destination address, decapsulation flag, etc., but they are not the focus of this article.

[0105] In the described embodiment, for the purpose of description, it is assumed that the SPI 702 has been divided into two fields: the PI 704 and the color part 706. In this example, the least significant two bits of the SPI field 702 are used to mark the traffic color of the incoming NSH encapsulated data packet 304. Figure 7 The number of bits in the color portion 706 is shown. In this example, the bits are provided in the color portion 706 where N = 2. In the case where N = 2 in the color portion 706, the PI 704 has 22 bits (eg, (24 - N) = 22) for identifying the traffic path.

[0106] In one embodiment, continuing the above example, the two least significant bits can be used to set the color of the traffic indicating a specific service path. By setting the two least significant bits, the NSH encapsulated data packets 304 entering the data packet flow can use colors to identify different service levels. For example, as shown in Table I below, when N=2, the two least significant bits can be set to identify the color of the traffic on the service path. For example, when the two least significant bits are set in the network node, any one service path can use up to 4 different colors (when all values ​​are used).

[0107] Table I

[0108] Bit 23-2 Bit 1 Bit 0 color Path A 0 0 Green(0) Path A 0 1 Yellow(1) Path A 1 0 Red(2) Path A 1 1 [blank](3)

[0109] For example, a green packet may indicate that packet delivery is guaranteed, or at least packet forwarding is guaranteed, with a low probability of the packet being dropped or discarded; a yellow packet may indicate that the packet will be forwarded in a "best effort" manner; and a red packet will be dropped or discarded. Other colors and services associated with these colors may also be added, and they may vary depending on the number of color portion 706 bits used in the SPI 702.

[0110] In one embodiment, if the quantity of the appropriate color for a particular path is less than the sum of the appropriate color, then the list item can be removed or omitted. For example, as shown in Table 1, when the two lowest bits were set to "1", the color associated with path A was empty. In this case, forwarding table 800A can indicate unused color (for example, being "empty") or can remove or omit whole list item from forwarding table 800A. As mentioned above, the number of bits used to identify color in SPI 702 is not limited to the two lowest bits. Any number of bits (N bits) can be used for this purpose in SPI 702.

[0111] continue Fig. 8A , a unique SPI 702 is used to identify a specific service path instantiation of a service function chain. As explained, SPI 702 is divided into PI 704 and color part 706. Service index (service index, SI) 802 is initialized to indicate the value of the service within each instantiation of the service function chain of the corresponding SPI 702, so that the value can be decreased according to the mode of processing data packets at a specific network node in the SFC. As shown, table 800A identifies two PI 704 with associated color marks ("0"-"3") (represented by color part 706) and SI 802 (e.g., 'k' or 'm').

[0112] For example, table 800A may be stored as a forwarding table of a network node (e.g., SFF 117B). During implementation, when NSH encapsulates packet 304 ( Figure 3) arrives at the network node, SPI 702 and SI 802 are looked up in forwarding table 800A. The information in forwarding table 800A determines: from which port the NSH encapsulated packet 304 is forwarded; to which destination address the NSH encapsulated packet 304 is forwarded; whether to (1) decapsulate the NSH encapsulated packet 304 by removing the NSH header 312, or (2) retain the NSH header 312 and forward the NSH encapsulated packet 304 using the specific output encapsulation indicated by the outer transport header, etc. If the packet is forwarded as an NSH encapsulated packet 304 using the NSH header 312, SI 802 is decremented.

[0113] These "colors" can then be used to differentiate between services that determine how the network processes the packets. More specifically, depending on the color indicated for each PI 704 in the color portion 706, the NSH encapsulated packets 304 can be processed in different ways. Figure 1 As described above, the policy manager 115D may be responsible for setting various QoS treatments for incoming packets, wherein QoS is defined by coloring the NSH encapsulated packets 304 for a given data flow or service path. For example, by connecting to the policy manager 115D, an administrator may define a QoS policy whereby VoIP packets for path A are marked as "green" to receive a high forwarding priority (e.g., 60% of the network bandwidth is allocated), and FTP packets for path B are marked as "yellow" to receive a low forwarding priority (e.g., 20% of the network bandwidth is allocated).

[0114] Figure 8B Another example of a forwarding table for a service function forwarder. Forwarding table 800B is stored in a network node (such as SFF117B). In one embodiment, forwarding table 800B is widened or expanded (e.g., adding an extra column) to include n bits to indicate a color 804 (processing index) corresponding to each SPI 702 and SI 802. For example, as shown, SPI702 entry A1 has an SI 802 of 'k' and a corresponding color 804 of "red".

[0115] In another embodiment, the amount of increase in the number of forwarding entries depends on the number of different coloring paths used, where a color of "0" (or an empty field) indicates operation in a non-coloring mode. For example, path entries A1 and A2 use two color paths (e.g., red and green), and path entries B1-B4 use four color paths (e.g., red, blue, purple, and empty (0)).

[0116] With forwarding table 800A( Fig. 8A), the SPI 702 in the NSH header 312 does not provide a direct indication of the traffic color (because the "color part" is not used in the SPI or any other field). Therefore, the received data packet (i.e., the NSH encapsulated data packet 304) cannot be used to directly determine the color associated with the service path. The forwarding table 800B is responsible for identifying a specific data packet color upon arrival. For example, when an NSH encapsulated data packet 304 is received at a network node that supports NSH, the SPI 702 and SI 802 are searched in the forwarding table 800B. When there is an entry for SPI 702, the corresponding color 804 is also obtained from the forwarding table 800B. The received data packet can then be processed according to the service or service level associated with the color, as explained above. In one embodiment, if the SPI is not in the forwarding table, the data packet should be discarded.

[0117] Fig. 9 For Figure 1 Flow chart of forwarding data packets in a service function chain of a network. For the purpose of description, the process described in the embodiment is implemented by a network node in a service function chain (SFC). However, it should be understood that the implementation is not limited to the network nodes in the SFC, and any component or node in the network can implement the process.

[0118] In step 902, a network node receives a data packet belonging to an SFC of an SFC-enabled domain. In one embodiment, the network node is an SFC classifier node 117A.

[0119] In step 904, the received data packet is encapsulated with a network service header (NSH). In one embodiment, the SFC classifier node (such as SFC classifier 117A) encapsulates the data packet with the NSH to form an encapsulated NSH data packet 304. In another embodiment, the encapsulated NSH data packet includes a service path header that identifies a service path. The service path can be identified by a service path identifier (SPI) 702.

[0120] In step 906, the service path is associated with the processing value in the encapsulated NSH data packet. In one embodiment, the SPI is divided into two parts: a path index (PI) for identifying the service path; and a color part (or processing index) for associating the encapsulated NSH data packet with the processing value indicating the quality of service processing. In another embodiment, the service path header includes the SPI 702 and the service index (SI), wherein the SI associates the encapsulated NSH data packet with the processing value indicating the quality of service processing. For example, the processing value can guide one or more subsequent network nodes in the SFC-enabled domain to encapsulate the NSH data packet using the quality of service processing.

[0121] In step 908, a forwarding table stored in the network node is evaluated to identify the service path and processing value of the encapsulated NSH data packet. For example, a forwarding table (such as forwarding table 800A or 800B) is "looked up" or evaluated to identify information of the encapsulated NSH data packet received at the node. In one embodiment, a quality of service treatment of the encapsulated NSH data packet can be determined. For example, the quality of service treatment can indicate the manner in which the subsequent network node handles the encapsulated NSH data packet. For example, the quality of service treatment can identify a service or policy that one or more subsequent network nodes should perform.

[0122] In step 910, the encapsulated NSH data packet is forwarded to one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0123] Fig.10 1 is a block diagram of a network processing device 1001 that can be used to implement various embodiments provided by the present invention. A particular network processing device may use all of the components shown or only a subset of the components, and the degree of integration between devices may vary. In addition, the network processing device 1001 may include multiple component instances, such as multiple processing units, processors, memories, transmitters, receivers, and the like. The network processing device 1001 may be equipped with one or more input / output devices, such as a network interface, a storage interface, and the like. The processing unit 1001 may include a central processing unit (CPU) 1010, a memory 1020, a mass storage device 1030, and an I / O interface 1060 connected to a bus 1070. The bus 1070 may be one or more of several bus architectures of any type, including a memory bus or a memory controller, a peripheral bus, and the like.

[0124] CPU 1010 may include any type of electronic data processor. Memory 1020 may include any type of system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In one embodiment, memory 1020 may include ROM used at boot time and DRAM used to store programs and data when executing programs. In an embodiment, memory 1020 is a non-transient memory. In one embodiment, the memory 1020 includes: a receiving module 1020A, used to receive a data packet at a node belonging to a service function chain (SFC) in a network, wherein the data packet is encapsulated by a network service header (NSH), and the network service header includes a service path header identifying a service path, and the service path is associated with a processing value, wherein the processing value guides one or more subsequent nodes in the network to process the encapsulated NSH data packet using quality of service processing; an evaluation module 1020B, used to evaluate a forwarding table stored in the node to identify the service path and processing value of the encapsulated NSH data packet, and determine the quality of service processing of the encapsulated NSH data packet to be performed by one or more subsequent nodes; a forwarding module 1020C, used to forward the encapsulated NSH data packet to one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

[0125] The mass storage device 1030 may include any type of storage device for storing data, programs, and other information and making the data, programs, and other information accessible via the bus 1070. For example, the mass storage device 830 may include one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, an optical disk drive, and the like.

[0126] The processing device 1001 also includes one or more network interfaces 1050, or one or more networks 1080, wherein the one or more network interfaces 1050 may include wired links such as Ethernet cables, and / or wireless links for accessing nodes. The network interface 1050 allows the processing unit 1001 to communicate with remote units via the network 1080. For example, the network interface 1050 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In one embodiment, the processing unit 1001 is coupled to a local area network or a wide area network for data processing and communication with remote devices such as other processing units, the Internet, remote storage facilities, etc.

[0127] It should be understood that this theme can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to make this theme thorough and complete, and to fully convey the present invention to those skilled in the art. In fact, this theme is intended to cover substitutes, modifications and equivalents of these embodiments within the scope and spirit of this theme defined by the appended claims. In addition, in the following detailed description of this theme, many specific details are set forth in order to provide a thorough understanding of this theme. However, it will be clear to those of ordinary skill in the art that this theme can be practiced without such specific details.

[0128] The present invention is described in detail in the flowchart and / or block diagram of the method, device (system) and computer program product provided in conjunction with the embodiments of the present invention. It should be understood that each square frame of the flowchart and / or block diagram and the combination of the square frames in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable instruction execution device create a mechanism for implementing the function / action specified in one or more frames of the flowchart and / or block diagram.

[0129] Non-transitory computer-readable media include all types of computer-readable media, including magnetic storage media, optical storage media, and solid-state storage media, and specifically do not include signals. It should be understood that the software can be installed in the device and sold with the device. Alternatively, the software can be obtained and loaded into the device, including through optical disk media or from any form of network or distribution system, including, for example, from a server owned by the software creator or from a server not owned by the software creator but used. For example, the software can be stored in a server for distribution over the Internet.

[0130] One or more computer-readable storage media do not themselves include propagating signals, can be accessed by a computer and / or one or more processors, and include removable and / or non-removable volatile and non-volatile internal and / or external media. For a computer, various types of storage media are suitable for storing data in any suitable digital format. It should be understood by those skilled in the art that other types of computer-readable media, such as zip drives, solid-state drives, magnetic tapes, flash cards, flash drives, boxes, etc., can be used to store computer-executable instructions for performing the novel methods (actions) of the disclosed architecture.

[0131] The terms used herein are only for describing specific aspects and are not intended to limit the present invention. Unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" used herein are also intended to include plural forms. It should be further understood that the term "comprising" used in this specification describes the presence of stated features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0132] The description of the present invention is presented for illustration and description and is not intended to be exhaustive or limited to the present invention in the disclosed form. Various modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present invention. Various aspects of the present invention are selected and described in order to better explain the principles and practical applications of the present invention and to enable those of ordinary skill in the art to understand the present invention and various modifications suitable for the intended specific use.

[0133] For the purposes of this document, each process associated with the disclosed technology can be performed serially by one or more computing devices. Each step in the process can be performed by a computing device that is the same or different from the computing device used in other steps, and each step is not necessarily performed by a single computing device.

[0134] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A computer-implemented method for forwarding a data packet in a network, characterized in that: include: The data packet is received at a node belonging to a service function chain (SFC) in the network, wherein: The data packet is encapsulated by a network service header (NSH), wherein the network service header includes a service path header identifying a service path; The service path is associated with a processing value, wherein the processing value instructs one or more subsequent nodes in the network to process the encapsulated NSH data packet using a quality of service processing, wherein the quality of service processing identifies a service or policy performed by the one or more subsequent network nodes, wherein the service or policy is a traffic policy or service determined according to a service level agreement SLA; evaluating a forwarding table stored in a node that receives the data packet to identify the service path and the processing value for the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; The encapsulated NSH data packet is forwarded to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

2. The computer-implemented method of claim 1, wherein: The service path header includes: a service path identifier (SPI), wherein the service path identifier includes a path index (PI) indicating the service path and a processing index indicating the processing value; and a service index (SI) indicating a position of the encapsulated NSH data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

3. The computer-implemented method according to any one of claims 1 to 2, characterized in that: A service path identifier (SPI) includes one or more most significant bits of the service path header, and a service index (SI) includes one or more least significant bits of the service path header, wherein: The total number of the one or more most significant bits is 24; The total number of the one or more least significant bits is 8; The total number of the one or more bits included in the service path header is 32.

4. The computer-implemented method of claim 2, wherein: The processing index includes one or more bits of the SPI, the PI includes one or more bits of the SPI, the number of bits of the SPI included in the processing index is greater than or equal to 1 and less than or equal to 23, and the sum of the number of bits of the SPI included in the processing index and the number of bits of the SPI included in the PI is 24.

5. The computer-implemented method of claim 4, wherein: The one or more bits included in the PI are located at a fixed position of one or more highest bits in the SPI, and the one or more bits included in the processing index are located at a fixed position of one or more lowest bits in the SPI, or, The one or more bits of the PI and the processing index are randomly located in the SPI.

6. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: The forwarding table includes n entries corresponding to each service path of the encapsulated NSH data packet, where n is the number of different processing values ​​associated with the service path.

7. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: The service path header includes a service index (SI), wherein the service index indicates the processing value and the position of the data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

8. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: The forwarding table includes a service path identifier (SPI) indicating the service path, a service index (SI) indicating the position of the encapsulated NSH data packet in the service function chain, and a processing index indicating the processing value; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

9. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: The network is an SFC-enabled domain.

10. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: Also includes: The encapsulated NSH data packet is processed according to a service function associated with the node.

11. The computer-implemented method according to any one of claims 1, 2, 4 and 5, characterized in that: Also includes: The encapsulated NSH data packet is decapsulated by removing the NSH, and the decapsulated data packet is forwarded to a destination address determined based on information in the header of the decapsulated data packet.

12. A non-transitory computer readable medium storing computer instructions for forwarding data packets in a network, characterized in that: When one or more processors execute the instructions, the one or more processors perform the following steps: The data packet is received at a node belonging to a service function chain (SFC) in the network, wherein: The data packet is encapsulated by a network service header (NSH), wherein the network service header includes a service path header identifying a service path; The service path is associated with a processing value, wherein the processing value instructs one or more subsequent nodes in the network to process the encapsulated NSH data packet using a quality of service processing, wherein the quality of service processing identifies a service or policy performed by the one or more subsequent network nodes, wherein the service or policy is a traffic policy or service determined according to a service level agreement SLA; evaluating a forwarding table stored in a node that receives the data packet to identify the service path and the processing value for the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; The encapsulated NSH data packet is forwarded to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

13. The non-transitory computer readable medium of claim 12, wherein: The service path header includes: a service path identifier (SPI), wherein the service path identifier includes a path index (PI) indicating the service path and a processing index indicating the processing value; and a service index (SI) indicating a position of the encapsulated NSH data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

14. The non-transitory computer readable medium according to any one of claims 12 to 13, wherein: A service path identifier (SPI) includes one or more most significant bits of the service path header, and a service index (SI) includes one or more least significant bits of the service path header, wherein: The total number of the one or more most significant bits is 24; The total number of the one or more least significant bits is 8; The total number of the one or more bits included in the service path header is 32.

15. The non-transitory computer readable medium of claim 13, wherein: The processing index includes one or more bits of the SPI, the PI includes one or more bits of the SPI, the number of bits of the SPI included in the processing index is greater than or equal to 1 and less than or equal to 23, and the sum of the number of bits of the SPI included in the processing index and the number of bits of the SPI included in the PI is 24.

16. The non-transitory computer readable medium of claim 15, wherein: The one or more bits included in the PI are located at a fixed position of one or more highest bits in the SPI, and the one or more bits included in the processing index are located at a fixed position of one or more lowest bits in the SPI, or, The one or more bits of the PI and the processing index are randomly located in the SPI.

17. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The forwarding table includes n entries corresponding to each service path of the encapsulated NSH data packet, where n is the number of different processing values ​​associated with the service path.

18. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The service path header includes a service index (SI), wherein the service index indicates the processing value and the position of the data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

19. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The forwarding table includes a service path identifier (SPI) indicating the service path, a service index (SI) indicating the position of the encapsulated NSH data packet in the service function chain, and a processing index indicating the processing value; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

20. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The network is an SFC-enabled domain.

21. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The one or more processors further perform the following steps: processing the encapsulated NSH data packet according to a service function associated with the node.

22. The non-transitory computer readable medium according to any one of claims 12, 13, 15 and 16, wherein: The one or more processors also perform the steps of decapsulating the encapsulated NSH packet by removing the NSH, and forwarding the decapsulated packet to a destination address determined based on information in the header of the decapsulated packet.

23. A node for forwarding data packets in a network, characterized in that: The nodes include: A non-transitory memory including instructions; one or more processors in communication with the memory, wherein the one or more processors execute the instructions to: The data packet is received at a node belonging to a service function chain (SFC) in the network, wherein: The data packet is encapsulated by a network service header (NSH), wherein the network service header includes a service path header identifying a service path; The service path is associated with a processing value, wherein the processing value instructs one or more subsequent nodes in the network to process the encapsulated NSH data packet using a quality of service processing, wherein the quality of service processing identifies a service or policy performed by the one or more subsequent network nodes, wherein the service or policy is a traffic policy or service determined according to a service level agreement SLA; evaluating a forwarding table stored in a node that receives the data packet to identify the service path and the processing value for the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; The encapsulated NSH data packet is forwarded to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.

24. The node according to claim 23, characterized in that The service path header includes: a service path identifier (SPI), wherein the service path identifier includes a path index (PI) indicating the service path and a processing index indicating the processing value; and a service index (SI) indicating a position of the encapsulated NSH data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

25. The node according to any one of claims 23 to 24, characterized in that A service path identifier (SPI) includes one or more most significant bits of the service path header, and a service index (SI) includes one or more least significant bits of the service path header, wherein: The total number of the one or more most significant bits is 24; The total number of the one or more least significant bits is 8; The total number of the one or more bits included in the service path header is 32.

26. The node according to claim 24, characterized in that The processing index includes one or more bits of the SPI, the PI includes one or more bits of the SPI, the number of bits of the SPI included in the processing index is greater than or equal to 1 and less than or equal to 23, and the sum of the number of bits of the SPI included in the processing index and the number of bits of the SPI included in the PI is 24.

27. The node according to claim 26, characterized in that The one or more bits included in the PI are located at a fixed position of one or more highest bits in the SPI, and the one or more bits included in the processing index are located at a fixed position of one or more lowest bits in the SPI, or, The one or more bits of the PI and the processing index are randomly located in the SPI.

28. A node according to any one of claims 23, 24, 26 and 27, characterized in that The forwarding table includes n entries corresponding to each service path of the encapsulated NSH data packet, where n is the number of different processing values ​​associated with the service path.

29. A node according to any one of claims 23, 24, 26 and 27, characterized in that The service path header includes a service index (SI), wherein the service index indicates the processing value and the position of the data packet in the service function chain; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

30. A node according to any one of claims 23, 24, 26 and 27, characterized in that The forwarding table includes a service path identifier (SPI) indicating the service path, a service index (SI) indicating the position of the encapsulated NSH data packet in the service function chain, and a processing index indicating the processing value; The treatment value indicates the quality of service treatment of the encapsulated NSH packet.

31. A node according to any one of claims 23, 24, 26 and 27, characterized in that The network is an SFC-enabled domain.

32. A node according to any one of claims 23, 24, 26 and 27, characterized in that The one or more processors further execute the instructions to process the encapsulated NSH data packet according to a service function associated with the node.

33. A node according to any one of claims 23, 24, 26 and 27, characterized in that The one or more processors also execute the instructions to decapsulate the encapsulated NSH packet by removing the NSH and forward the decapsulated packet to a destination address determined based on information in the header of the decapsulated packet.

34. A node for forwarding data packets in a network, characterized in that: The nodes include: A receiving module is used to receive the data packet at a node belonging to a service function chain (SFC) in the network, wherein: The data packet is encapsulated by a network service header (NSH), wherein the network service header includes a service path header identifying a service path; The service path is associated with a processing value, wherein the processing value instructs one or more subsequent nodes in the network to process the encapsulated NSH data packet using a quality of service processing, wherein the quality of service processing identifies a service or policy performed by the one or more subsequent network nodes, wherein the service or policy is a traffic policy or service determined according to a service level agreement SLA; an evaluation module for evaluating a forwarding table stored in a node that receives the data packet to identify the service path and the processing value of the encapsulated NSH data packet, and determining the quality of service processing of the encapsulated NSH data packet to be performed by the one or more subsequent nodes; A forwarding module is used to forward the encapsulated NSH data packet to the one or more subsequent nodes according to the service path indicated in the forwarding table and the quality of service processing corresponding to the processing value identified in the forwarding table.