JP2018125837A - Seamless service functional chain between domains - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for validating a service functional chain, and a system.SOLUTION: According to one or a plurality of embodiments, one or a plurality of systems, a method and/or a process receive a service functional chain description including a service function related to a plurality of domains. An arbitrary domain from domains does not ignore or deny an external node, and the node may be configured so as to communicate with the external node when mounting the service functional chain related to the service functional chain description. For example, an adjustment device (e.g., a central adjustment device) may provide control information and/or construction information to one or a plurality of system of each domain on the basis of the service functional chain description, As one example, the adjustment device may provide the control information and/or the construction information to a border node of each domain. As another example, the adjustment device may provide the control information and/or the construction information to a domain control part of each domain.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates generally to network function virtualization, and more specifically to systems and methods for establishing service function chaining within multiple domains.

  Emerging network applications such as cloud and big data may jointly consider IT resources that exist in multiple domains within one or more data centers (DCs). Network function virtualization (NFV) can be used to virtualize network functions and migrate them from a single purpose built device to a multi-purpose virtual machine. This can reduce service deployment costs and increase service flexibility. As more service functions move to virtual machines in geographically distributed data centers, and more individually managed network on demand is enabled by software defined networking (SDN) technology, End-to-end network services may implement various mechanisms to coordinate resources across multiple network domains. For example, network services may traverse one or more consumer broadband networks, mobile backhaul networks, mobile packet core networks, and / or virtual private networks.

  Service functions (SF) can be deployed in various networks. The SF can provide a wide range of functions such as security, server load balancing, and wide area network promotion, and the SF can be instantiated at various points in the network infrastructure. Service function (SF) deployment is relatively static and / or coupled to a network topology. As in the past, SF deployment does not adapt well to the flexible service environment enabled by instance virtualization. However, data center networks and / or cloud architectures require more flexible SR deployment. Furthermore, transition to a virtual platform may require an agile service insertion model that can accommodate dynamic and / or flexible service delivery. In addition, the SF may require the ability to easily steer traffic to the required service.

  This disclosure receives a service function chain description that includes service functions associated with multiple domains, and any domain in the domain does not ignore or reject external nodes, One or more systems, methods, and / or processes are provided that may be configured to communicate with external nodes in implementing an associated service function chain. For example, a service function chain description may include a first service function associated with a first service node in a first management domain and a second service node that is external to the first management domain (eg, in a second management domain). Associated with a second service function. For example, a first forwarding node in the first management domain is external to the first management domain that forwards traffic from the first service function to a second service node outside the first management domain (eg, second May be configured to provide data to a second forwarding node (in the domain), wherein the first forwarding node in the first administrative domain is from the first service function to the second forwarding node outside the first administrative domain. Data may be provided to the node.

  In one or more embodiments, a first service classifier (eg, a first service classification node) in the first administrative domain classifies network traffic associated with a service function chain description and associates it with the service function chain description. Configured network traffic to a first forwarding node in the first administrative domain. For example, the first service classifier may introduce and / or provide a network service header that may be utilized to steer and / or direct traffic associated with the service function chain description. For example, the classifier may set a service function identification and / or a network service header label based on the traffic classification, and the first forwarding node uses the information in the network service header to route the traffic to the first service node. May be steered and / or directed. In one or more embodiments, the second forwarding node outside the first management domain (eg, in the second management domain) is based on the service function chain description and the first service node in the first management domain Configured to provide data from the second service function to the first forwarding node in the first management domain that forwards traffic to the first service node in the first management domain, based on the first service function associated with the first service function. Good. For example, traffic can be bidirectional.

For a more complete understanding of the present invention and its features and advantages, reference is made to the following description, taken in conjunction with the accompanying drawings, in which:
2 illustrates exemplary elements of a distributed resource organization framework, according to one or more embodiments. FIG. 3 provides an exemplary block diagram of selected elements of multiple network domains that provide end-to-end services, according to one or more embodiments. 2 provides an exemplary block diagram of a management domain, according to one or more embodiments. 2 illustrates an exemplary administrative domain, according to one or more embodiments. FIG. 4 provides an exemplary block diagram of a management domain in which an arbiter may configure multiple domain controllers, according to one or more embodiments. FIG. 4 provides an exemplary block diagram of a management domain in which an arbiter may configure multiple boundary nodes, according to one or more embodiments. 1 provides a block diagram of an exemplary data processing system, according to one or more embodiments. Fig. 4 illustrates a method for enabling a service function chain according to one or more embodiments.

  In the following description, details are set forth as an example to facilitate discussion of the disclosed subject matter. However, it will be apparent to one skilled in the art that the disclosed embodiments are illustrative and are not exhaustive of all possible embodiments.

  Throughout this disclosure, reference signs in the form of hyphens represent specific instances of one element, and reference signs in the form without a hyphen represent elements in general or collectively. Thus, by way of example (not shown), the widget 12-1 represents an instance of the widget class and may be collectively referred to as the widget 12, any of which are commonly referred to as the widget 12. May be. In the figures and the description, like symbols represent like elements.

  In one or more embodiments, the organization system may provide lifecycle management for services such as augmented / virtual reality, video delivery, streaming media services, and Internet of Things (IoT), among others. For example, the organization system provides resource allocation and / or deployment of application-related service functions (SF) in a virtual network function (VNF) and software defined infrastructure (SDI) and / or Or you may manage. In one example, the SF may include one or more of a video codec, a cache, and an analysis engine, particularly via network function virtualization (NFV). In another example, the VNF may include one or more of a firewall, network address translation (NAT), routing function, switching function, and deep packet inspection (DPI), among others. In one or more embodiments, the SDI may have a physical network function (PNF). For example, the PNF may include optical transport systems, routers, and / or switches that may be controlled by a software defined networking (SDN) controller. In one or more embodiments, a high level management and control architecture for a foundation on which an organization system can be implemented is NFV Infrastructure (NFVI) and NFV management and organization (Management And Organization) that can manage the life cycle of the VNF. Orchestration: MANO).

  In one or more embodiments, the organization system may support end-to-end organization with resource management and allocation. For example, the SDI may be managed through multiple resource specific controls and / or organizers that can implement individual system deployment and / or troubleshooting. For example, the data center may be customary with a cloud resource organizer (eg, OpenStack, etc.), and the cloud resource organizer may provide VMs to SF and / or NVF. In one or a plurality of embodiments, an intra-data center network connecting various VMs may be managed by one or a plurality of SDN controllers, and a wide area network (WAN) for inter-data center connection is used. It may be managed by a different set of one or more SDN controllers. For example, one or a plurality of SDN controllers that manage network functions in a data center that connect various VMs may use ONOS (for example, a network operating system), and one or a plurality of SDN controllers that manage connections between data centers. The SDN controller may use OpenDaylight (eg, a framework that supports software-defined networking and network function virtualization).

  In one or more embodiments, resource management partitioning may generate an evolutionary SDI having nodes (eg, networks and / or computing elements) with heterogeneous functions that span multiple network domains. In one example, one or more nodes may host service functions (eg, SF, VNF, etc.). In the second example, one or more nodes may provide a switch function (eg, router, switch, etc.). For example, one or more nodes that may provide a switch function may combine and / or “chain” a plurality of nodes that may host a service function. In another example, one or more nodes may host both service and switch resources (eg, a “white box” switch with an embedded server that supports VNF). For example, one or more nodes that can host both service and switch resources can provide a resource efficient chain.

  In one or more embodiments, the organizer may interact with the user via a will-based declarative interface to respond to user requests. For example, the organizer may divide the user request into one or more SFs and / or VNFs and provide a transfer graph that can be used in delivering a service associated with the user request. In one or more embodiments, the organizer may provide network connectivity based on VNF / SF sizing and placement, and available resources in the SDI. For example, in the case of a video streaming service, the organizer may route the stream to the codec by instantiating the codec SF with the appropriate node and provisioning the associated network connection. Thus, according to one or more embodiments, the organizer can perform resource allocation that jointly considers VNF, SF, and physical network devices for end-to-end service deployment, and provides end-to-end service automation. Enable and / or improve resource utilization.

  In one or more embodiments, providing end-to-end services may utilize one or more SFs. For example, the SF may have, among other things, one or more firewalls, one or more network address translations (NAT), and / or one or more application specific functions. In one or more embodiments, a service function chain (SFC) is an ordered SF that traffic (eg, network data) is “steered” and / or directed to and / or from the SF of the SFC. May have a set. For example, the classifier may steer and / or direct traffic to and / or from the SF of the SFC. For example, the SFC may include ordering constraints that may be traffic, data packets, data frames, and / or data flows based on classification. In one or more embodiments, the SFC may be bidirectional or unidirectional. For example, traffic, data packets, data frames, and / or data flows can be bidirectional or unidirectional.

  In one or more embodiments, one or more systems, methods, and / or processes receive an SFC description that includes SFs associated with multiple domains, and an element of the first domain is external to the first domain Rather than ignoring or rejecting the SF associated with the node, the element may be configured to communicate with one or more nodes outside the first domain in implementing the SFC associated with the SFC description. In one example, the arbiter may receive an SFC description that includes SFs associated with multiple domains, and may configure domain controllers for multiple domains when implementing an SFC associated with an SFC description. For example, when the SFC associated with the SFC description is implemented, the domain control unit may configure one or more elements of those individual domains. In another example, the arbiter may receive an SFC description that includes SFs associated with multiple domains and may configure boundary nodes of multiple domains when implementing an SFC associated with the SFC description.

  Referring to the figures, FIG. 1 illustrates exemplary elements of an exemplary distributed resource organization framework in accordance with one or more embodiments. As shown, the network domain 100 may be based on nodes that are network elements (NEs). As shown, the network domain 100 may include a domain specific resource organizer 102 and a physical network 110. In one or more embodiments, the physical network 110 is a basic optical, such as an optical transport network (OTN) and / or a flexible optical data plane (eg, a flexible transceiver) configured to adjust the bandwidth of the connection. You may have a network.

  In one or more embodiments, the resource organizer 102 may manage and / or coordinate the use of resources in the network domain 100. For example, the resource organizer 102 may manage and / or coordinate the use of one or more NEs 112. For example, the NE 112 may have one or more types of network functions such as a switch, a router, and the like, and may have hardware that communicatively couples one or more types of physical interfaces.

  As shown, network domain 100 may include NEs 112-1 through 112-6 along communicable coupling between NEs 112-1 through 112-6, which may have various distances. In one or more embodiments, the network domain 100 may have a single network domain network topology in which the network organizer 102 may manage and / or coordinate resource utilization.

  In one or more embodiments, one or more network management functions of the network domain 100 other than that provided by the resource organizer 102 may be provided by the SDN controller 104. For example, in the use of a plurality of network domains, each network domain may be managed by an individual SDN control unit. For example, one or more of resource organizer 102 and SDN controller 104 may continue to track (eg, store) one or more network configurations and / or one or more network topologies of network 110. .

  In one or more embodiments, the network domain 100 may be included in multiple network domains that utilize a distributed processing approach. In a distributed processing approach, a resource organizer and / or network in which messages are associated with individual networks of multiple network domains, such as physical network 110, such as resource organizer 102 and / or SDN controller 104. Exchanged between or among the controllers. In one or more embodiments, resource organizers may operate in concert to perform SFC in multiple network domains. This depends on identifying one or more possible SFC solutions, one or more of one or more possible SFC solutions to perform (eg preference and / or various policies, etc.) Selecting) and configuring physical resources of various network nodes to implement one or more selected solutions.

  As shown, the network domain 100 may include an NFV manager 106. In one or more embodiments, the NFN manager 106 can be utilized in network function virtualization and / or migration of network functions from a device configured for a single specific purpose to a multipurpose virtual machine on a commercial server. . This can reduce service deployment costs and / or increase service flexibility. In one example, the NFV manager 106 may manage the installation and / or lifecycle of one or more VNFs. For example, a virtual network function (VNF) may be implemented by and / or through a virtual machine (VM). In the second example, the NFV manager 106 may store information associated with one or more NEs. For example, the NFV manager 106 is one of the number of virtual machines (VMs) associated with the NE, that a certain amount of storage space is available, and that a certain amount of storage space is used. Or a plurality may be stored. In another example, the NFV manager 106 may provide information associated with one or more NEs to the resource organizer 102.

  In one or more embodiments, the resource organizer 102, the SDN controller 104, and the NFV manager 106 may form the control plane 101, or at least form part of the control plane 101. As described, one or more elements of the control plane 101 may constitute and / or control network elements of the physical network 110, for example.

  According to one or more embodiments, in a system that utilizes an NFV manager, VNFs may be invoked in an order that provides end-to-end services. In one example, service function chaining may include configuring and / or assigning various VMs to implement and / or perform virtual network functions. In another example, service function chaining may include steering, routing, and / or shaping traffic across one or more networks and / or one or more network domains. For example, traffic flows may be steered, routed, and / or shaped through multiple VNFs and / or SFs in an order based on one or more preferences and / or policies.

  In one or more embodiments, service function chaining may be supported by application of a resource organizer. For example, a resource organizer element, referred to herein as a resource organizer, can include one or more resources (one or more service functions, one or more virtual machines, etc.) in each data center to interconnect VNFs. And / or use of one or more networks) and associated network resources may be managed and / or coordinated collectively and / or individually. Distributed across multiple network domains as described herein by migration of VNFs to VMs in geographically dispersed data centers and deployment of on-demand connections controlled by SDN in IP / OTN networks Resource organization may be advantageous for providing end-to-end network services in accordance with one or more embodiments. For example, network services may include, among others, consumer broadband, mobile backhaul, mobile packet core, and / or virtual private networks (eg, networks implemented on Fujitsu Network Communications Inc. 1Finity ™). Across multiple networks.

  In one or more embodiments, a large multiple network domain may include multiple different domains. These domains may have different network topologies, different vendors, different administrators, different types of resources, and / or different virtual networks. For example, these domains include domains where IoT devices, computing resources, storage resources, and / or different types of service functions (including access service functions, metro service functions, and / or core service functions) exist. good. In one or more embodiments, these multiple network domains can maintain inter-domain trust and improve scalability for service providers. In one or more embodiments, each network domain may be controlled by a local organizer, and vertex-centric distributed computing between organizers is utilized for end-to-end resource allocation. May be good.

  Referring to FIG. 2, an exemplary block diagram of selected elements of multiple network domains providing end-to-end services is shown in accordance with one or more embodiments. As shown, the multiple network domain 200 may include four network domains 210, 220, 230, 240. Each domain 210, 220, 230, 240 may have one or more nodes that can be represented by vertices in determining one or more possible SFC solutions. In one or more embodiments, one or more nodes may implement one or more service functions that utilize resources in individual domains.

  As shown, domain 210 can represent the Internet of Things. For example, one or more devices 211 to 213 in the domain 210 may issue one or more SFC requests. As shown, domain 220 may represent one or more data centers and / or other entities that may provide access services that may be included in the SFC. For example, domain 220 may include services 221 through 223, among others. As shown, the domain 230 may represent one or more data centers and / or other entities that may provide computing and / or storage services that may be included in the SFC. For example, the domain 230 may include services 231 to 233 in particular. As shown, domain 240 may represent one or more data centers and / or other entities that may provide core services that may be included in the SFC. For example, the domain 240 may include services 241 to 243, in particular.

  In the illustrated example, a device 211 in domain 210 may issue an SFC request 214 that may include at least one access service, one computing or storage service, and one or more service functions. More specifically, SFC request 214 includes access service function 223 (available on one of the nodes in domain 220), computing (available on one of the nodes in domain 230). Alternatively, an SFC may be specified that includes a storage service function 232 and a core service function 243 (available on one of the nodes in the domain 240).

  In one or more embodiments, each domain in the multiple network domains may include physical nodes and / or internet protocol / optical transport network links. In one or more embodiments, individual resource organizers may be associated with each network domain to manage physical nodes and links within the domain. In one or more embodiments, each physical node can invoke one or more NEs (eg, one or more network switches, network routers, etc.) that can invoke a subset of service functions selected from a service function catalog. ) And / or one or more computing servers and / or storage elements (eg, data centers).

  Some examples of service functions provided within these multiple network domains include firewalls, DPI, NAT, load balancers, and parent control functions. In one example, the SFC may include a firewall service function, a DPI service function, a parent control service function, and an anti-virus function, each of which is provided by one or more nodes in an individual different network domain. Good. In another example, the SFC may include a NAT service function between two other types of service functions and / or between other service functions and an Internet access service function. Each of these may be provided by one or more nodes in an individual different network domain.

  Referring to FIG. 3, an exemplary block diagram of a management domain is shown according to one or more embodiments. As illustrated, the network domain 100 may include one or more management domains 300. For example, the network domain 100-1 may include management domains 300-11 to 300-13, the network domain 100-2 may include management domains 300-21 to 300-23, and the network domain 100-3 may include management domains. 300-31 to 300-33 may be included. As shown, the management domains 300 may be communicatively coupled to each other.

  In one or more embodiments, the management domain may have one or more structures and / or characteristics of a network domain. In one example, the administrative domain may be and / or similar to a network domain that exists within the network domain. For example, the management domain may include network elements and / or computer systems of customers and / or entities in the same location. In one or more embodiments, the management domain may be a network domain. For example, the network domain may not include a plurality of management domains, and the network domain may be a management domain.

  In one or more embodiments, the management domain 300 may implement part of the SFC. In one example, the management domain 300-11 may implement the first part of the SFC, and the management domain 300-12 may implement the second part of the SFC. In another example, management domain 300-21 may implement the first part of SFC, management domain 300-23 may implement the second part of SFC, and management domain 300-31 may be the third part of SFC. And the management domain 300-33 may implement the fourth part of the SFC.

  With reference to FIG. 4, an exemplary administrative domain is shown in accordance with one or more embodiments. As illustrated, the management domain 410-1 may include a domain control unit 415-1, a classification node 420-1, a forwarding node 425-11, and service nodes 440-11 and 440-12. As shown, classification node 420-1 may be communicatively coupled to forwarding node 425-11, and forwarding node 425-11 may be communicatively coupled to service nodes 440-11 and 440-12. Although not specifically illustrated, the domain control unit 415-1 is communicatively coupled to one or more of the classification node 420-1, the forwarding node 425-11, and the service nodes 440-11 and 440-12. good. In one or more embodiments, the domain controller 415-1 may provide control information and / or configuration information to one or more network elements and / or computer systems of the management domain 410-1. For example, the domain control unit 415-1 provides control information and / or configuration information to one or more of the classification node 420-1, the forwarding node 425-11, and the service nodes 440-11 and 440-12. Good.

  As illustrated, the management domain 410-2 may include a domain control unit 415-2, a classification node 420-2, a forwarding node 425-21, and service nodes 440-21 and 440-22. As shown, classification node 420-2 may be communicatively coupled to forwarding node 425-21, and forwarding node 425-21 may be communicatively coupled to service nodes 440-21 and 440-22. Although not specifically illustrated, the domain control unit 415-2 is communicatively coupled to one or more of the classification node 420-2, the forwarding node 425-21, and the service nodes 440-21 and 440-22. good. In one or more embodiments, the domain controller 415-2 may provide control information and / or configuration information to one or more network elements and / or computer systems of the management domain 410-2. For example, the domain control unit 415-2 provides control information and / or configuration information to one or more of the classification node 420-2, the forwarding node 425-21, and the service nodes 440-21 and 440-22. Good.

  As shown, traffic 430 may be received by and / or provided via classifier 420. In one or more embodiments, traffic 430 may comprise data, data packets, data frames, network traffic, and / or data flows, among others. In one or more embodiments, the classifier (eg, classification node 420) may be configured to classify traffic and / or data streams. For example, the classifier may be configured to classify traffic and / or data streams based on one or more rules and / or one or more policies. For example, one or more rules and / or one or more policies may include one or more categories (eg, web, secure shell, email, remote procedure call (RPC), chat, video, audio, It may be used to configure a classifier to classify data and / or traffic according to dynamic host configuration protocol (DHCP), NAT, domain name service (DNS), Internet message access protocol (IMAP), etc. In one or more embodiments, the classifier may examine packet headers to classify data and / or traffic. For example, the classifier may examine the port number of the packet to classify data and / or traffic. In one or more embodiments, the classifier may examine the payload of the packet to classify data and / or traffic. For example, the classifier may determine one or more classifications regardless of port number or header information. For example, the classifier may determine one or more classifications based on one or more signatures.

  In one or more embodiments, the classifier provides information to steer and / or direct data and / or traffic to one or more network elements and / or computer systems for processing. good. For example, a classifier may have metadata that can be utilized in steering and / or directing data and / or traffic. In one or more embodiments, the classifier includes a network service header (NSH) and / or modifies the NSH that may be utilized by the forwarder to steer and / or direct data and / or traffic to the SF. You can do it. For example, the classifier may introduce NSH to steer and / or direct data and / or traffic. For example, the classifier may set SFC identification (ID) and / or NSH labels based on the classification of data and / or traffic. In one or more embodiments, the forwarder may utilize NSH information in steering and / or directing data and / or traffic. For example, the forwarder may utilize the SFC ID and / or NSH label to provide data and / or traffic to a service node associated with the SF associated with the data and / or traffic classification. In one or more embodiments, NSH may provide topology independence. For example, the underlying network topology may not need to be changed when using NSH. As shown, traffic 430-1 may be steered and / or directed to service node 440-11 and traffic 430-2 may be steered and / or directed to service node 440-12. , Traffic 430-1 may be steered and / or directed to service node 440-21, and traffic 430-2 may be steered and / or directed to service node 440-22.

  In one or more embodiments, the classifier may be configured to classify traffic associated with the SFC and / or SFC description. In one example, the SFC and / or SFC description may have one or more categories of traffic. In a second example, the SFC and / or SFC description may have one or more addresses. In another example, the SFC and / or SFC description may have a network mask. In one or more embodiments, the SFC description may comprise one or more of SFC and SFC ID and / or label.

  In one or more embodiments, traffic 430 may include data in one or more processing stages by SFC. As shown, traffic 430 may traverse logical path 435 through one or more administrative domains 430. In one example, traffic 430-1 may include data in one or more processing stages with a first SFC that includes service nodes 440-11 and 440-21, among others. For example, service nodes 440-11 and 440-21 may process traffic 430-1. In another example, traffic 430-2 may include data in one or more processing stages with a first SFC that includes service nodes 440-12 and 440-22, among others. For example, service nodes 440-12 and 440-22 may process traffic 430-2. In one or more embodiments, the logical path 435 may be a RSP (rendered service path).

  As shown, forwarding nodes 425-11 and 425-21 may be communicatively coupled. In one or more embodiments, forwarding nodes 425-11 and 425-21 may be able to communicate via a network tunnel and / or packet encapsulation. In one example, packet encapsulation and / or packet tunneling can generate and / or implement an overlay network topology that can be independent of the physical network topology. In another example, the network tunnel may utilize encryption. For example, the network tunnel may encrypt data transported by the network tunnel.

  In one or more embodiments, forwarding node 425 is configured to provide and / or receive traffic 430 to and / or from one or more SFs and / or to and / or from another forwarding node 425. May be good. In one example, forwarding node 425-11 may be configured to provide and / or receive traffic 430-1 to and / or from service node 440-11. In a second example, forwarding node 425-11 may be configured to provide and / or receive traffic 430-1 to and / or from forwarding node 425-21. In a third example, forwarding node 425-21 may be configured to provide and / or receive traffic 430-1 to and / or from service node 440-21. In another example, forwarding node 425-21 may be configured to provide and / or receive traffic 430-1 to and / or from forwarding node 425-11. Similarly, forwarding nodes 425-11 and 425-21 may be further configured to implement SFCs associated with traffic 430-2 and logical path 435-2.

  In one or more embodiments, the management domain 310 may have one or more structures and / or characteristics of those described with the management domain 410. In one example, the management domain 310-11 may be the management domain 410-1 and the management domain 310-12 may be the management domain 410-2. For example, the management domains 410-1 and 410-2 may be included in a single network domain. In another example, management domain 310-22 may be management domain 410-1 and management domain 310-33 may be management domain 410-2. For example, the management domains 410-1 and 410-2 may be included in different network domains.

  Referring to FIGS. 5A and 5B, an exemplary block diagram of an arbiter and management domain that can configure elements of the management domain according to one or more embodiments is shown. As shown in FIG. 5A, the SFC description 505 may be provided to the arbiter 510. In one or more embodiments, the SFC description 505 may be provided by a user. For example, the administrative user may write and / or provide the SFC description 505 to the arbiter 510. In one or more embodiments, the SFC description 505 may be provided by the system. For example, the system may determine the SFC, configure the SFC description 505 with the determined SFC, and / or provide the SFC description 505 to the arbiter 510.

  In one or more embodiments, the arbiter 510 may be a central entity that may forward SFC information and / or provide configuration information associated with the SFC description 505 to the management domain involved. As shown, arbiter 510 may be communicatively coupled to domain controllers 415-1 and 415-2. In one or more embodiments, the arbiter 510 may provide control information and / or configuration information to the domain controllers 415-1 and 415-2. For example, the arbiter 505 may provide the control information and / or configuration information associated with one or more SFCs to the domain controllers 415-1 and 415-2. For example, the control information and / or configuration information associated with one or more SFCs is based on the SFC description 505 including the service node 440-11 of the management domain 410-1 and the service node 440-21 of the management domain 410-2. good.

  In one or more embodiments, the domain controller may have one or more structures and / or 1 as described with reference to one or more of the resource organizer 102, the SDN controller 104, and the NFV manager 106. Or it may have a plurality of functions. In one example, the domain control unit 415 may configure one or more network elements of the management domain 410. In another example, the domain control unit 415 may configure the service node 440. For example, configuring service node 440 may be one of instructing service node 440 to allocate and / or instantiate a VM and implement SF (eg, implement SF with VM) or There may be more than one. In one or more embodiments, the controllers 415-1 and 415-2 may not accept configurations and / or components that include network elements and / or computer systems that are external to their individual management domains. The arbiter 510 may provide control information and / or configuration information to the control units 415-1 and 415-2. In one example, when the service node 440-21 is outside the management domain 410-1, the domain control unit 415-1 may not accept an SFC description including the service node 440-11 and the service node 440-21. In another example, when the service node 440-11 is outside the management domain 410-2, the domain control unit 415-2 may not accept the SFC description including the service node 440-11 and the service node 440-21. .

  In one or more embodiments, domain controllers 415-1 and 415-2 receive control information and / or configuration information from arbiter 510 and are network elements and / or computers that are external to their respective management domains. One or more elements of these individual management domains may be configured to correspond to the system. In one example, domain controller 415-1 may configure forwarding node 425-11 to receive control information and / or configuration information from arbiter 510 and provide traffic 430-1 to forwarding node 425-21. . In the second example, the domain control unit 415-1 receives the control information and / or configuration information from the arbiter 510, and configures the forwarding node 425-11 to receive the traffic 430-1 from the forwarding node 425-21. You can do it. In the third example, the domain control unit 415-2 receives the control information and / or configuration information from the arbiter 510 and configures the forwarding node 425-21 to provide the traffic 430-1 to the forwarding node 425-11. You can do it. In another example, the domain controller 415-2 receives the control information and / or configuration information from the arbiter 510 and configures the forwarding node 425-21 to receive the traffic 430-1 from the forwarding node 425-11. Good.

  In one or more embodiments, the domain controllers 415-1 and 415-2 may receive control information and / or configuration information from the arbiter 510 and may authenticate the control information and / or configuration information. For example, authenticating the received information may ensure that the received information is from the arbiter 510. For example, if the received information cannot be authenticated, the received information may be discarded and / or ignored. In one or more embodiments, the domain controllers 415-1 and 415-2 may receive encrypted control information and / or configuration information from the arbiter 510. In one example, encrypting control information and / or configuration information may provide one or more private information transfers. In another example, encrypting the control information and / or configuration information may provide authenticating the control information and / or configuration information.

  As shown in FIG. 5B, arbiter 510 may be communicatively coupled to forwarding nodes 425-11 and 425-21. In one or more embodiments, the arbiter 510 may provide control information and / or configuration information to the forwarding nodes 425-11 and 425-21. For example, the control information and / or configuration information may be based on the SFC description 505. In one example, arbiter 510 may configure forwarding node 425-11 to provide traffic 430-1 to forwarding node 425-21. In the second example, the arbiter 510 may configure the forwarding node 425-11 to receive traffic 430-1 from the forwarding node 425-21. In a third example, arbiter 510 may configure forwarding node 425-21 to provide traffic 430-1 to forwarding node 425-11. In another example, arbiter 510 may configure forwarding node 425-21 to receive traffic 430-1 from forwarding node 425-11.

  In one or more embodiments, forwarding nodes 425-11 and 425-21 may receive control information and / or configuration information from arbiter 510 and may authenticate the control information and / or configuration information. For example, authenticating the received information may ensure that the received information is from the arbiter 510. For example, if the received information cannot be authenticated, the received information may be discarded and / or ignored. In one or more embodiments, forwarding nodes 425-11 and 425-21 may receive encrypted control information and / or configuration information from arbiter 510. In one example, encrypting control information and / or configuration information may provide one or more private information transfers. In another example, encrypting the control information and / or configuration information may provide authenticating the control information and / or configuration information.

  Referring to FIG. 6, a block diagram of an exemplary data processing system is shown according to one or more embodiments. As shown, the data processing system 610 includes a processor 620, a memory 622 that is communicatively coupled to the processor 620, an input / output (I / O) subsystem 628 that is communicatively coupled to the processor 620, You may have.

  In one or more embodiments, the memory 622 may include systems, devices, and / or equipment for storing processor instructions 624 and data 626 for a period of time. For example, the memory 622 may have a different number of physical storage devices. For example, the memory 622 includes a random access memory (RAM), an electrically erasable programmable read-only memory (EEPROM), a personal computer memory card international association (PCMCIA) card, a ferroelectric RAM (FRAM (registered trademark)), a flash memory, One or more solid disks, one or more hard disk drives, one or more magnetic tape libraries, one or more optical disk drives, one or more magneto-optical disk drives, one or more compact disk drives, one or more Various types of components and devices may be included such as a compact disk array, one or more disk array controllers, and / or any suitable selection or array of volatile or non-volatile memory. In one or more embodiments, the memory 622 stores information (eg, processor instructions 624, data 626, etc.) for a period of time sufficient to include or include a non-transitory computer readable medium. You can do it. In one or more embodiments, the memory 622 may comprise a non-volatile memory. For example, non-volatile memory may represent memory that retains data after power is turned off.

  In one or more embodiments, processor instructions 624 may be executed by processor 620 to implement one or more methods, one or more processes, and / or one or more systems described herein. It's okay. For example, the processor instructions 624 may be configured, encoded, and / or encoded with instructions in accordance with one or more of the flowcharts, methods, and / or processes described herein. For example, the processor instructions 624 may be executable by the processor 620 when performing seamless service function chaining across multiple domains. In one or more embodiments, data 626 may store information usable by processor 620 and / or processor instructions 624. In one example, the data 626 may store information representing SFCs and / or SFC descriptions. In the second example, the data 626 may store configuration information and / or control information. In another example, the data 626 may be any one or more default values and / or one or more available to implement one or more functions and / or one or more structures described herein. Information representing a plurality of configuration parameters may be stored.

  In one or more embodiments, the I / O subsystem 628 may allow and / or provide interaction with the data processing system 610 and / or associated components of the data processing system 610. For example, the I / O subsystem 628 may allow the data processing system 610 and / or the processor 620 to implement one or more systems, processes, and / or methods described herein, particularly one or more. Multiple buses, one or more serial devices, and / or one or more network interfaces. In one or more embodiments, one or more resource organizers 102, one or more SND controllers 104, one or more NFV managers 106, one or more NEs 112, one or more nodes (eg, one or more A plurality of classification nodes 420, one or more forwarding nodes 425, one or more service nodes 440, etc.) and / or one or more domain controllers 415, one of those described with reference to the data processing system 610 Or it may have multiple structures and / or functions.

  Referring to FIG. 7, a method for enabling a service function chain according to one or more embodiments is shown. At 710, a service function chain description that includes a first service function associated with a first service node in the first management domain and a second service function associated with a second service node outside the first management domain. May be received. For example, the first management domain may be the domain 410-1, and the SFC description 505 includes a first service function associated with the first service node and a second service node associated with the second service node outside the first management domain. 2 service functions. For example, the first service node may be a service node 440-11 that implements a first service function, and the second service node implements a second service function that is external to the first management domain 410-1. It may be a service node 440-21.

  At 715, the first service classifier may be configured to classify network traffic associated with the service function chain description and provide network traffic associated with the service function chain description to the first forwarding node. For example, the first service classifier may be a classification node 420-1, which classifies network traffic 430-1 associated with the SFC description 505 and identifies network traffic 430-1 associated with the SFC description. It may be configured to provide to forwarding node 425-11.

  At 720, the first forwarding node in the first management domain is based on the service function chain description and from the first service function based on the second service function associated with the second service node outside the first management domain. The data may be configured to be provided to a second forwarding node external to the first management domain that forwards traffic to a second service node external to the first management domain. For example, forwarding node 425-11 may be configured to provide data from service node 440-11 to forwarding node 425-21 (eg, second forwarding node) outside management domain 410-1. In one example, the domain control unit 415-1 may configure the forwarding node 425-11 to provide data from the service node 440-11 to the forwarding node 425-21. In another example, the arbiter 510 may configure the forwarding node 425-11 to provide data from the service node 440-11 to the forwarding node 425-21.

  At 725, network traffic and headers associated with the service function chain description may be provided to the first forwarding node. For example, classification node 420-1 may provide traffic node 430-1 and network service header associated with SFC description 505 to forwarding node 425-11. For example, the network service header may have an SFC ID and / or label that can be used by forwarding node 425-11 to steer and / or direct traffic 430-1 to service node 440-11. At 730, data from the first service function may be provided to a second forwarding node that is external to the first management domain. For example, the first forwarding node may provide data from the first service function to the second forwarding node outside the first management domain. For example, the forwarding node 425-11 may provide data from the service node 440-11 to the forwarding node 425-21 outside the management domain 410-1.

  The above disclosed subject matter is to be considered illustrative and not restrictive. Also, the appended claims are intended to cover all modifications, extensions and other embodiments that fall within the true spirit and scope of this disclosure. Thus, to the maximum extent permitted by law, the scope of the present disclosure should be determined by the broadest acceptable interpretation of the claims and their equivalents, and is limited or limited by the foregoing detailed description. Should not.

In addition to the above embodiment, the following additional notes are disclosed.
(Supplementary Note 1) A method of enabling a service function chain, the method comprising:
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain; ,
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring a first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
The first forwarding node in the first management domain providing the traffic from the first service function to the second forwarding node outside the first management domain;
Having a method.
(Supplementary note 2) Classifying the traffic associated with the service function chain description and providing the traffic associated with the service function chain description to the first forwarding node in the first management domain. Configuring a first service classifier within one administrative domain;
The method according to appendix 1, further comprising:
(Supplementary note 3) The method according to supplementary note 1, wherein the first forwarding node is a boundary node.
(Supplementary Note 4) The first service classifier provides a header associated with the service function chain description;
The method according to appendix 1, further comprising:
(Supplementary Note 5) The traffic from the first service function is transferred to the second forwarding node outside the first management domain for forwarding the traffic to the second service node outside the first management domain. The step of configuring the first forwarding node in the first management domain to provide the domain controller associated with the first management domain based on the service function chain description and in the first management domain Based on the second service function associated with the second service node that is external, the traffic from the first service function is forwarded to the second service node that is external to the first management domain. Providing the second forwarding node outside the first management domain to the second forwarding node. The method of claim 1, comprising the step of configuring the first forwarding node in a management domain.
(Supplementary Note 6) The traffic from the first service function is transferred to the second forwarding node outside the first management domain, which forwards the traffic to the second service node outside the first management domain. The step of configuring the first forwarding node in the first management domain to provide the arbiter associated with the second management domain including the first management domain and the second forwarding node comprises the service function Based on a chain description and based on the second service function associated with the second service node that is external to the first management domain, the traffic from the first service function is external to the first management domain The outside of the first administrative domain forwarding the traffic to the second service node The method of claim 1, comprising configuring the first forwarding node in the first administrative domain to provide to a second forwarding node.
(Supplementary note 7) Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is Configuring the second forwarding node outside the first management domain to provide to the first forwarding node in the first management domain that forwards the traffic to the first service node in a domain;
The method according to appendix 1, further comprising:
(Supplementary Note 8) Receiving configuration information from an arbiter associated with a second management domain including the first management domain and the second forwarding node;
Authenticating the configuration information from the arbiter;
Further comprising
Providing the traffic from the first service function to the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain; The method of claim 1, wherein the step of configuring the first forwarding node in the first management domain is further based on the configuration information from the arbiter.
(Supplementary Note 9) The second management domain includes the second service node outside the first management domain,
A single network domain includes the first management domain and the second management domain;
The method according to appendix 1.
(Appendix 10) A system for enabling a service function chain,
A processor;
A memory communicatively coupled to the processor for storing processor executable instructions;
Have
When the processor-executable instructions are executed by the processor, the system
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain;
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring the first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
Providing the traffic from the first service function to the second forwarding node outside the first management domain via the first forwarding node in the first management domain;
system.
(Supplementary Note 11) The memory stores further processor-executable instructions, and when the further processor-executable instructions are executed by the processor, the system:
In the first management domain to classify the traffic associated with the service function chain description and to provide the traffic associated with the service function chain description to the first forwarding node in the first management domain. The first service classifier of
The system according to appendix 10.
(Supplementary note 12) The system according to supplementary note 10, wherein the first forwarding node is a boundary node.
(Supplementary note 13) The traffic from the first service function based on the second service function associated with the second service node outside the first management domain based on the service function chain description. To the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain. The system according to appendix 10, wherein when configuring one forwarding node, the system constitutes a domain control unit of the first management domain constituting the first forwarding node.
(Supplementary note 14) The memory stores further processor-executable instructions, and when the further processor-executable instructions are executed by the processor, the system
Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is routed in the first management domain. Configuring the second forwarding node external to the first management domain to provide the first forwarding node in the first management domain that forwards the traffic to a first service node;
The system according to appendix 10.
(Supplementary Note 15) The second management domain includes the second service node outside the first management domain,
A single network domain includes the first management domain and the second management domain;
The system according to appendix 10.
(Supplementary Note 16) A non-transitory computer-readable storage device storing processor-executable instructions, wherein when the processor-executable instructions are executed by a processor, the processor
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain;
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring a first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
Providing the traffic from the first service function to the second forwarding node outside the first management domain via the first forwarding node in the first management domain;
Non-transitory computer readable storage device.
(Supplementary Note 17) The storage device stores a further processor-executable instruction, and when the further processor-executable instruction is executed by the processor, the processor
In the first management domain to classify the traffic associated with the service function chain description and to provide the traffic associated with the service function chain description to the first forwarding node in the first management domain. The first service classifier of
The non-transitory computer-readable storage device according to appendix 16.
(Supplementary note 18) The non-transitory computer-readable storage device according to supplementary note 16, wherein the first forwarding node is a boundary node.
(Supplementary note 19) The traffic from the first service function based on the second service function associated with the second service node external to the first management domain based on the service function chain description. To the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain. The non-transitory computer-readable storage device according to appendix 16, wherein when configuring one forwarding node, the processor constitutes a domain control unit of the first management domain constituting the first forwarding node.
(Supplementary note 20) The storage device stores a further processor-executable instruction, and when the further processor-executable instruction is executed by the processor, the processor
Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is routed in the first management domain. Configuring the second forwarding node external to the first management domain to provide the first forwarding node in the first management domain that forwards the traffic to a first service node;
The non-transitory computer-readable storage device according to appendix 16.

DESCRIPTION OF SYMBOLS 100 Network domain 101 Control plane 102 Resource organizer 104 SDN control part 106 NFV manager 110 Physical network 112 Network element (NE)

Claims (20)

A method for enabling a service function chain, the method comprising:
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain; ,
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring a first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
The first forwarding node in the first management domain providing the traffic from the first service function to the second forwarding node outside the first management domain;
Having a method. In the first management domain to classify the traffic associated with the service function chain description and to provide the traffic associated with the service function chain description to the first forwarding node in the first management domain. Configuring a first service classifier of
The method of claim 1 further comprising:   The method of claim 1, wherein the first forwarding node is a boundary node. The first service classifier providing a header associated with the service function chain description;
The method of claim 1 further comprising:   Providing the traffic from the first service function to the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain; The step of configuring the first forwarding node in the first management domain includes: a domain control unit associated with the first management domain being based on the service function chain description and external to the first management domain The first management that forwards the traffic from the first service function to the second service node outside the first management domain based on the second service function associated with a second service node The first management domain is provided to the second forwarding node outside the domain. Comprising configuring the first forwarding node in the emissions, the method according to claim 1.   Providing the traffic from the first service function to the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain; The step of configuring the first forwarding node in the first management domain includes: an arbiter associated with the second management domain including the first management domain and the second forwarding node based on the service function chain description. And based on the second service function associated with the second service node outside the first management domain, the traffic from the first service function is routed to the second service outside the first management domain. The second forwarding node outside the first management domain for forwarding the traffic to a node. To provide a de, comprising configuring the first forwarding node in the first management domain The method of claim 1. Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is routed in the first management domain. Configuring the second forwarding node external to the first management domain to provide to the first forwarding node in the first management domain that forwards the traffic to a first service node;
The method of claim 1 further comprising: Receiving configuration information from an arbiter associated with a second management domain including the first management domain and the second forwarding node;
Authenticating the configuration information from the arbiter;
Further comprising
Providing the traffic from the first service function to the second forwarding node outside the first management domain that forwards the traffic to the second service node outside the first management domain; The method of claim 1, wherein the step of configuring the first forwarding node in the first management domain is further based on the configuration information from the arbiter. A second management domain includes the second service node external to the first management domain;
A single network domain includes the first management domain and the second management domain;
The method of claim 1. A system for enabling a service function chain,
A processor;
A memory communicatively coupled to the processor for storing processor executable instructions;
Have
When the processor-executable instructions are executed by the processor, the system
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain;
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring the first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
Providing the traffic from the first service function to the second forwarding node outside the first management domain via the first forwarding node in the first management domain;
system. The memory stores further processor executable instructions, and when the further processor executable instructions are executed by the processor, the system includes:
In the first management domain to classify the traffic associated with the service function chain description and to provide the traffic associated with the service function chain description to the first forwarding node in the first management domain. The first service classifier of
The system according to claim 10.   The system of claim 10, wherein the first forwarding node is a boundary node.   The system is configured to route the traffic from the first service function based on the service function chain description and based on the second service function associated with the second service node external to the first management domain. The first forwarding node in the first management domain is provided to the second forwarding node outside the first management domain for forwarding the traffic to the second service node outside the one management domain. The system according to claim 10, wherein when configuring, the system configures a domain control unit of the first management domain configuring the first forwarding node. The memory stores further processor executable instructions, and when the further processor executable instructions are executed by the processor, the system includes:
Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is routed in the first management domain. Configuring the second forwarding node external to the first management domain to provide the first forwarding node in the first management domain that forwards the traffic to a first service node;
The system according to claim 10. A second management domain includes the second service node external to the first management domain;
A single network domain includes the first management domain and the second management domain;
The system according to claim 10. A non-transitory computer-readable storage device storing processor-executable instructions, wherein when the processor-executable instructions are executed by a processor, the processor
Receiving a service function chain description including a first service function associated with a first service node in a first management domain and a second service function associated with a second service node external to the first management domain;
Based on the service function chain description and based on the second service function associated with the second service node that is external to the first management domain, traffic from the first service function is routed outside the first management domain. Configuring a first forwarding node in the first management domain to provide to a second forwarding node outside the first management domain that forwards the traffic to the second service node at
Providing the traffic from the first service function to the second forwarding node outside the first management domain via the first forwarding node in the first management domain;
Non-transitory computer readable storage device. The storage device stores further processor-executable instructions, and when the further processor-executable instructions are executed by the processor, the processor
In the first management domain to classify the traffic associated with the service function chain description and to provide the traffic associated with the service function chain description to the first forwarding node in the first management domain. The first service classifier of
The non-transitory computer readable storage device of claim 16.   The non-transitory computer readable storage device of claim 16, wherein the first forwarding node is a boundary node.   The processor is configured to route the traffic from the first service function based on the service function chain description and based on the second service function associated with the second service node external to the first management domain. The first forwarding node in the first management domain is provided to the second forwarding node outside the first management domain for forwarding the traffic to the second service node outside the one management domain. 17. The non-transitory computer-readable storage device according to claim 16, wherein, when configured, the processor configures a domain control unit of the first management domain configuring the first forwarding node. The storage device stores further processor-executable instructions, and when the further processor-executable instructions are executed by the processor, the processor
Based on the service function chain description and based on the first service function associated with the first service node in the first management domain, the traffic from the second service function is routed in the first management domain. Configuring the second forwarding node external to the first management domain to provide the first forwarding node in the first management domain that forwards the traffic to a first service node;
The non-transitory computer readable storage device of claim 16.

Images