Patent ID: 12224907

DETAILED DESCRIPTION

The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.

Intents may be represented in an intent data model, which may be modeled using a unified graph. For example, the intent data model may be represented as a connected graph having nodes (e.g., that represent configuration objects) connected with edges (e.g., that represent relationships between configuration objects). In order to configure a network device to perform the intents, translation programs may translate high-level configuration information (e.g., that includes instructions according to the intent data model, which may be expressed as the connected graph) to low-level configuration information (e.g., that includes instructions according to a device configuration model) for the network device.

A network management system can maintain an intent policy model, such as for cloud services (e.g., secure services edge (SSE) capabilities), that can be deployed to provide services to multiple, different network devices. However, in many cases, each network device also needs to maintain a different intent policy model for on-device services (e.g., firewall or other security services) of the network device. This can result in a network administrator needing to maintain and/or monitor a global intent policy model and individual intent policy models for a network of network devices. Consequently, the network administrator may utilize computing resources (e.g., processing resources, memory resources, communication resources, and/or power resources, among other examples) of a device to manage and monitor the multiple intent policy models.

Some implementations described herein provide a network management system (NMS). The NMS identifies a source intent policy model (e.g., that is associated with cloud services for multiple network devices) and a target intent policy model (e.g., that is associated with on-device services of an individual network device). The source intent policy model is associated with a first graph that has a plurality of source nodes (associated with source intents) connected by a plurality of source edges. The target intent policy model is associated with a second graph that has a plurality of target nodes (associated with target intents) connected by a plurality of target edges.

The NMS identifies a set of source nodes, of the plurality of sources nodes, that are associated with source intents that are to be included in the target intent policy model. The NMS translates the set of source nodes to generate a set of target nodes (e.g., such that the target nodes are formatted to be included in the second graph associated with the target intent policy model). The NMS then identifies a subset of target nodes, of the set of target nodes, that are not included in the second graph. The NMS thereby performs one or more processing operations associated with the set of target nodes and the plurality of target nodes (e.g., that are included in the second graph). For example, the NMS may determine a hierarchical order, identify and resolve conflicts, and/or identify and resolve redundancies associated with the subset of target nodes and the plurality of target nodes. The NMS then may cause the target intent policy model to be updated to include the subset of target nodes and the plurality of target nodes (e.g., such that the second graph is ordered according to the hierarchical order). Further, the NMS may cause the target intent policy model to be updated thereafter based on detecting changes to the source intent policy model.

In this way, the NMS enables multiple intent policy models to automatically be managed and updated (e.g., without manual intervention by a network administrator). Further, the NMS enables automatic conversion of a source intent policy model to a target intent policy model, which allows the network administrator to manage and/or monitor just one intent policy model for a network device, as opposed to two separate intent policy models. Accordingly, computing resources (e.g., processing resources, memory resources, communication resources, and/or power resources, among other examples) of a device are conserved that would otherwise be utilized by the network administrator to manage and monitor multiple intent policy models. Further, ordering issues, conflicts, and/or redundancies that would otherwise be present in association with multiple intent policy models are reduced, which optimizes use of computing resources of the NMS and/or the network device.

FIGS.1A-1Fare diagrams of one or more example implementations100described herein. As shown inFIGS.1A-1F, example implementation(s)100may include an NMS and a network device. The NMS and the network device are described in more detail below in connection withFIGS.2-4. As shown inFIGS.1A-1F, the NMS may include an intent policy model management module, a translation module, and an analysis module.

As shown inFIG.1A, and by reference number102, the NMS (e.g., using the intent policy model management module) may identify a source intent policy model (e.g., an intent policy model, such as for cloud services, that is to be translated to another intent policy model, described herein). The source intent policy model may be a graph-based policy model, such as where source intents and source objects are represented as nodes, and relationships between source intents and source objects are represented as edges, or another type of intent-based model. For example, as shown inFIG.1A, the source intent policy model may be associated with a graph having a plurality of source nodes connected by a plurality of source edges. The plurality of source nodes may include one or more source intent nodes (e.g., where each source intent node is associated with a source intent) and/or one or more source intent object nodes (e.g., where each source intent object node is associated with a source intent object). The plurality of source nodes (e.g., that comprise the one or more source intent nodes and/or the one or more source intent object nodes) may be connected via the plurality of source edges to indicate associations, such as “has” or “reference” associations, between the plurality of source nodes.

As a specific example, as shown inFIG.1A, the source intent policy model may be represented as a graph that includes a first source intent node associated with a Source Intent A, a second source intent node associated with a Source Intent B, and a third source intent node associated with a Source Intent C; and a first source intent object node associated with a Source Intent Object 1, a second source intent object node associated with a Source Intent Object 2, and a third source intent object node associated with a Source Intent Object 3. The first source intent node may be connected to the second source intent node and the third source intent node via respective source edges (e.g., source “has” edges). In this way, the graph indicates that the second source intent node and the third source intent node depend from the first source intent node. The second source intent node may be connected to the first source intent object node and the second source intent object node via respective source edge (e.g., source “reference” edges), and the third source intent node may be connected to the second source intent object node and the third source intent object node via respective source edges (e.g., source reference edges). In this way, the graph indicates that the first source intent object node and the second source intent object node depend from the second source intent node, and the second source intent object node and the third source intent object node depend from the third source intent node.

In some implementations, each node of the source intent policy model may include information. The information may indicate, for example, a name of the source node, an identifier associated with the source node (e.g., a universally unique identifier (UUID) or another identifier associated with the source node), and/or a type of the source node (e.g., that indicates whether the source node is a source intent node or a source intent object node, or another type of node). Additionally, or alternatively, each source node may include, for example, information indicating which source nodes depend from the source node and/or information indicating from which source nodes the source node depends. For example, the first source intent object node (e.g., associated with the Source Intent Object B) may include information indicating that the first source intent object node depends from the second source intent node (e.g., that is associated with the Source Intent B); the second source intent object node (e.g., associated with the Source Intent Object 2) may include information indicating that the second source intent object node depends from the second source intent node (e.g., that is associated with Source Intent B) and the third source intent node (e.g., that is associated with the Source Intent C); and the third source intent object node (e.g., associated with the Source Intent Object 3) may include information indicating that the third source intent object node depends from the third source intent node (e.g., that is associated with the Source Intent C). As another example, the second source intent node (e.g., that is associated with the Source Intent B) may include information indicating that the second source intent node depends from the first source intent node (e.g., that is associated with the Source Intent A) and/or that the first source intent object node (e.g., associated with the Source Intent Object 1) and the second source intent object node (e.g., associated with the Source Intent Object 2) depend from the second source intent node; and the third source intent node (e.g., that is associated with the Source Intent C) may include information indicating that the third source intent node depends from the first source intent node (e.g., that is associated with the Source Intent A) and/or that the second source intent object node (e.g., associated with the Source Intent Object 2) and the third source intent object node (e.g., associated with the Source Intent Object 3) depend from the third source intent node.

As shown inFIG.1B, and by reference number104, the NMS (e.g., using the intent policy model management module) may identify a set of source nodes (e.g., one or more source nodes) of the plurality of source nodes of the graph associated with the source intent policy model. The set of source nodes may be associated with source intents of the source intent policy model that are relevant to the network device (e.g., that can be implemented on the network device). In some implementations, a network administrator may interact with a user interface of the NMS to input a selection that identifies a first group of one or more source nodes of the plurality of source nodes of the graph associated with the source intent policy model. Alternatively, the NMS may include, or may obtain (e.g., from a data structure, such as a database, a table, a file, or another data structure) configuration information that identifies the group of one or more source nodes. The first group of one or more source nodes may be source nodes from which other source nodes depend, and may include, for example, one or more source intent nodes (and may not include one or more source intent object nodes). Accordingly, the NMS may identify a second group of one or more nodes, of the plurality of source nodes, that depend from the first group of one or more source nodes. For example, the second group of one or more source nodes may include one or more source intent nodes and/or one or more source intent object nodes that depend from the first group of one or more source nodes. Accordingly, the NMS may identify the set of source nodes as comprising the first group of one or more source nodes and, in some implementations, as also comprising the second group of one or more source nodes.

As shown inFIG.1C, and by reference number106, the NMS (e.g., using the translation module) may translate the set of source nodes to generate a set of target nodes. For example, the NMS may traverse the set of source nodes and may thereby translate each source node to at least one target node. The NMS may use a recursive technique, such as a depth first search technique, to traverse the set of source nodes. Accordingly, based on recursively traversing the set of source nodes, the NMS may translate each source node of the set of source nodes to generate the set of target nodes (e.g., in a depth first manner), such that each source node of the set of source nodes corresponds to at least one target node of the set of target nodes. The NMS may use a translation technique that is associated with the target intent policy model described herein to translate the set of source nodes to generate a set of target nodes. For example, the translation technique may indicate how information included in a source node is to be modified (if at all) and included in at least one target node, and/or may indicate how one or more source edges associated with the source node are to be modified (if at all) and associated with the at least one target node.

As shown inFIG.1D, and by reference number108, the NMS (e.g., using the intent policy model management module) may identify a target intent policy model (e.g., an intent policy model, such as for on-device services of the network device, that is to be updated as described herein). The target intent policy model may be a graph-based policy model, such as where target intents and target objects are represented as nodes, and relationships between target intents and target objects are represented as edges, or another type of intent-based model. For example, as shown inFIG.1D, the target intent policy model may be associated with a graph having a plurality of target nodes connected by a plurality of target edges. The plurality of target nodes may include one or more intent nodes (e.g., where each target intent node is associated with a target intent) and/or one or more target intent object nodes (e.g., where each target intent object node is associated with a target intent object). The plurality of target nodes (e.g., that comprise the one or more target intent nodes and/or the one or more target intent object nodes) may be connected via the plurality of target edges to indicate associations, such as “has” or “reference” associations, between the plurality of target nodes.

As a specific example, as shown inFIG.1D, the target intent policy model may be represented as a graph that includes a first target intent node associated with a Target Intent A and a second target intent node associated with a Target Intent 1B; and a first target intent object node associated with a Target Intent Object 1 and a second target intent object node associated with a Target Intent Object 2. The first target intent node may be connected to the second target intent node via a target edge (e.g., a target “has” edge). In this way, the graph indicates that the second source intent node depends from the first source intent node. The second target intent node may be connected to the first target intent object node and the second target intent object node via respective target edges (e.g., target “reference” edges). In this way, the graph indicates that the first target intent object node and the second target intent object node depend from the second target intent node.

In some implementations, each node of the target intent policy model may include information. The information may indicate, for example, a name of the target node, an identifier associated with the target node (e.g., a universally unique identifier (UUID) or another identifier associated with the target node), and/or a type of the target node (e.g., that indicates whether the target node is a target intent node or a target intent object node, or another type of node). Additionally, or alternatively, each target node may include, for example, information indicating which target nodes depend from the target node and/or information indicating from which target nodes the target node depends. For example, the first target intent object node (e.g., associated with the Target Intent Object 1) may include information indicating that the first target intent object node depends from the second target intent node (e.g., that is associated with the Target Intent 1); the second target intent object node (e.g., associated with the Target Intent Object 2) may include information indicating that the second target intent object node depends from the second target intent node (e.g., that is associated with Target Intent 1); and the second target intent node (e.g., that is associated with the Target Intent 1) may include information indicating that the second target intent node depends from the first target intent node (e.g., that is associated with the Target Intent A) and/or that the first target intent object node (e.g., associated with the Target Intent Object 1) and the second target intent object node (e.g., associated with the Target Intent Object 2) depend from the second target intent node.

In some implementations, the target intent policy model may be associated with the source intent policy model. For example, when the source intent policy model is associated with cloud services of a particular type (e.g., security services) that can be applied on multiple, different network devices (including the network device described herein) and the target intent policy model is associated with on-device services of the particular type that are to be applied on the network device described herein, the target policy model may include some (but not all) of the same, or similar, intents of the source intent policy model (e.g., prior to the target policy model being updated as described herein).

As shown inFIG.1E, and by reference number110, the NMS (e.g., using the analysis module) may identify a subset of target nodes (e.g., one or more target nodes), of the set of target nodes (e.g., that correspond to the set of source nodes), that are not included in the target intent policy model (e.g., that is associated with the graph having a plurality of target nodes connected by the plurality of target edges). For example, for each target node of the set of target nodes, the NMS may process (e.g., using a hashing technique) the target node (e.g., process at least some of the information included in the target node) to determine a hash value associated with the target node. The NMS then may determine whether one of the plurality of target nodes (e.g., that are associated with the plurality of target nodes) is associated with the hash value. For example, the NMS may process each of the plurality of target nodes to determine respective hash values associated with the plurality of target nodes (or may obtain the respective hash values from a data structure). The NMS then may search the respective hash values to determine whether any one of the hash values matches (e.g., is equal to) the hash value associated with the target node. Accordingly, when the NMS determines that one of the plurality of target nodes is associated with the hash value (e.g., a positive match determination is made), the NMS may determine that the target node is already included in the target intent policy model and may therefore refrain from performing any additional action associated with the target node. Alternatively, when the NMS determines that not one of the plurality of target nodes is associated with the hash value (e.g., a negative match determination is made), the NMS may determine that the target node is not included in the target intent policy model and may therefore identify the subset of target nodes as comprising the target node. The NMS may also identify the subset of target nodes as comprising one or more target nodes, of the set of target nodes, that depend from the target node.

As shown inFIG.1F, and by reference number112, the NMS (e.g., using the analysis module) may perform one or more processing operations associated with the subset of target nodes and the plurality of target nodes (e.g., of the target intent policy model).

In some implementations, the one or more processing operations may include determining a hierarchical order associated with the subset of target nodes and the plurality of target nodes. For example, the NMS may determine whether a first target node of the subset of target nodes is to depend from a second target node of the plurality of target nodes, or vice versa. A target node is considered to be ordered before another target node in the hierarchical order when the other target node depends (e.g., directly or indirectly) from the target node. Accordingly, the NMS may determine a hierarchical order in which target nodes (of the subset of target nodes and the plurality of target nodes) associated with “specific” target intents are ordered before other target nodes (of the subset of target nodes and the plurality of target nodes) associated with “broad” target intents. For example, in a security firewall intent policy context, the NMS may determine that one or more target nodes associated with allowing a marketing user group to access a marketing website is ordered before one or more target nodes associated with allowing all user groups to access the Internet.

In some implementations, the one or more processing operations may include identifying one or more conflicts between the subset of target nodes and the plurality of target nodes. A conflict exists when at least two target nodes of the subset of target nodes and the plurality of target nodes are associated with contradictory target intents (e.g., target intents associated with different actions for the same, or similar, target resources or objects). For example, in the security firewall intent policy context, the NMS may determine that one or more target nodes that are associated with allowing the marketing user group to access a marketing website conflicts with one or more target nodes that are associated with denying the marketing user group access to the marketing website. In some implementations, the NMS may determine that a first target node, of the subset of target nodes, and a second target node, of the plurality of target nodes, conflict with each other. For example, the NMS may compare at least some of the information included in the first target node and at least some of the information included in the second target node (e.g., that corresponds to the at least some of the information included in the first target node) to determine that the first target node and the second target node conflict with each other. The NMS may provide information indicating that the NMS identified the one or more conflicts (e.g., information indicating that the NMS determined that the first target node and the second target node conflict with each other), such that the information can be presented to a network administrator (e.g., via a display screen associated with the NMS).

Further, the one or more operations may include resolving the one or more conflicts between the subset of target nodes and the plurality of target nodes (e.g., that are identified by the NMS). In some implementations, the NMS may remove at least one target node, of the subset of target nodes and the plurality of target nodes, that conflicts with at least one other target node of the subset of target nodes and the plurality of target node. Alternatively, the NMS cause conflicting target nodes to be ordered in a particular manner (e.g., in the hierarchical order). For example, based on determining that a first target node, of the subset of target nodes, and a second target node, of the plurality of target nodes, conflict with each other, the NMS may cause the second target node to be ordered before the first target node in the hierarchical order (or vice versa). In this way, a precedence relationship (or dependency relationship) between the first target node and the second target node may be established in the hierarchical order.

In some implementations, the one or more processing operations may include identifying one or more redundancies between the subset of target nodes and the plurality of target nodes. A redundancy exists when at least two target nodes, of the subset of target nodes and the plurality of target nodes, are associated with matching target intents (e.g., target intents associated with the same, or similar, actions for the same, or similar, target resources or objects). For example, in the security firewall intent policy context, the NMS may determine that one or more target nodes associated with allowing the marketing user group to access a marketing website are redundant with one or more other target nodes associated with allowing all user groups access to the Internet. In some implementations, the NMS may determine that a target node, of the subset of target nodes and the plurality of target nodes, is redundant with another target node of the subset of target nodes and the plurality of target nodes. For example, the NMS may compare at least some of the information included in the target node and at least some of the information included in the other target node (e.g., that corresponds to the at least some of the information included in the first target node) to determine that the target node is redundant with the other target node. The NMS may provide information indicating that the NMS identified the one or more redundancies (e.g., information indicating that the NMS determined that the target node is redundant with the other target node), such that the information can be presented to a network administrator (e.g., via display the screen associated with the NMS).

Further, the one or more operations may include resolving the one or more redundancies between the subset of target nodes and the plurality of target nodes (e.g., that are identified by the NMS). In some implementations, the NMS may remove at least one target node, of the subset of target nodes and the plurality of target nodes, that is redundant with at least one other target node of the subset of target nodes and the plurality of target node. For example, based on determining that a target node is redundant with another target node, the NMS may remove the target node (or the other target node) from the subset of target nodes and the plurality of target nodes. In this way, a size of the subset of target nodes and the plurality of target nodes may be reduced.

As shown by reference number114, the NMS (e.g., using the intent policy model management model) may cause the target intent policy model to be updated (e.g., based on performing the one or more processing operations). For example, the NMS may cause the target intent policy model to be updated to include the subset of target nodes and the plurality of target nodes (e.g., after identifying and/or resolving conflicts and/or redundancies), such that that the graph associated with the target intent policy model is ordered according to the hierarchical order. In this way, the target intent policy model may be updated to be the same, or similar, as the source intent policy model (but formatted and ordered in a manner to enable the target intent policy model to be deployed on the network device).

In some implementations, the NMS (e.g., using the intent policy model management model) may maintain a mapping, or other data structure, that indicates a correspondence between source nodes of the graph associated with the source intent policy model and the target nodes of the graph associated with the target intent policy model (e.g., after the target intent policy model is updated). Accordingly, the NMS may identify (e.g., using the intent policy model management model) a change to a particular source node of the plurality of source nodes of the graph associated with the target intent policy model (e.g., due to updates to a particular source intent and/or a particular source intent object that are associated with the particular source node). For example, the NMS may identify a change to at least some of the information included in the particular source node. The NMS may therefore identify a group of one or more source nodes, of the plurality of source nodes, that includes the particular source node. The group of one or more source nodes may include the particular source node and may also include one or more source nodes that depend from the particular source node. The NMS may translate the group of one or more source nodes to generate a group of one or more target nodes (e.g., in a similar manner as that described herein in relation toFIG.1Cand reference number106). The NMS may further cause the target intent policy model to be updated based on the group of one or more source nodes.

For example, for each target node, of the group of target nodes, the NMS may identify a corresponding target node of the graph associated with the target intent policy model (e.g., of the subset of target nodes and the plurality of target nodes included in the graph). The NMS may determine whether the target node matches the corresponding target node (e.g., whether information included in the target node is the same as information included in the corresponding target node). Accordingly, the NMS may replace the corresponding target node with the target node (e.g., in the graph) based on determining that the target node does not match the corresponding target node. Otherwise, the NMS may remove the target node from the group of target nodes.

As indicated above,FIGS.1A-1Fare provided as an example. Other examples may differ from what is described with regard toFIGS.1A-1F.

FIG.2is a diagram of an example environment200in which systems and/or methods described herein may be implemented. As shown inFIG.2, environment200may include a network management system201, which may include one or more elements of and/or may execute within a cloud computing system202. The cloud computing system202may include one or more elements203-212, as described in more detail below. As further shown inFIG.2, environment200may include a network220and/or a network device230. Devices and/or elements of environment200may interconnect via wired connections and/or wireless connections.

The cloud computing system202may include computing hardware203, a resource management component204, a host operating system (OS)205, and/or one or more virtual computing systems206. The cloud computing system202may execute on, for example, an Amazon Web Services platform, a Microsoft Azure platform, or a Snowflake platform. The resource management component204may perform virtualization (e.g., abstraction) of computing hardware203to create the one or more virtual computing systems206. Using virtualization, the resource management component204enables a single computing device (e.g., a computer or a server) to operate like multiple computing devices, such as by creating multiple isolated virtual computing systems206from computing hardware203of the single computing device. In this way, computing hardware203can operate more efficiently, with lower power consumption, higher reliability, higher availability, higher utilization, greater flexibility, and lower cost than using separate computing devices.

The computing hardware203may include hardware and corresponding resources from one or more computing devices. For example, computing hardware203may include hardware from a single computing device (e.g., a single server) or from multiple computing devices (e.g., multiple servers), such as multiple computing devices in one or more data centers. As shown, computing hardware203may include one or more processors207, one or more memories208, and/or one or more networking components209. Examples of a processor, a memory, and a networking component (e.g., a communication component) are described elsewhere herein.

The resource management component204may include a virtualization application (e.g., executing on hardware, such as computing hardware203) capable of virtualizing computing hardware203to start, stop, and/or manage one or more virtual computing systems206. For example, the resource management component204may include a hypervisor (e.g., a bare-metal or Type 1 hypervisor, a hosted or Type 2 hypervisor, or another type of hypervisor) or a virtual machine monitor, such as when the virtual computing systems206are virtual machines210. Additionally, or alternatively, the resource management component204may include a container manager, such as when the virtual computing systems206are containers211. In some implementations, the resource management component204executes within and/or in coordination with a host operating system205.

A virtual computing system206may include a virtual environment that enables cloud-based execution of operations and/or processes described herein using computing hardware203. As shown, a virtual computing system206may include a virtual machine210, a container211, or a hybrid environment212that includes a virtual machine and a container, among other examples. A virtual computing system206may execute one or more applications using a file system that includes binary files, software libraries, and/or other resources required to execute applications on a guest operating system (e.g., within the virtual computing system206) or the host operating system205.

Although the network management system201may include one or more elements203-212of the cloud computing system202, may execute within the cloud computing system202, and/or may be hosted within the cloud computing system202, in some implementations, the network management system201may not be cloud-based (e.g., may be implemented outside of a cloud computing system) or may be partially cloud-based. For example, the network management system201may include one or more devices that are not part of the cloud computing system202, such as device300ofFIG.3or device400ofFIG.4, which may include a standalone server or another type of computing device. The network management system201may perform one or more operations and/or processes described in more detail elsewhere herein.

The network220may include one or more wired and/or wireless networks. For example, the network220may include a cellular network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a private network, the Internet, and/or a combination of these or other types of networks. The network220enables communication among the devices of the environment200.

The network device230includes one or more devices capable of receiving, processing, storing, routing, and/or providing traffic (e.g., a packet or other information or metadata) in a manner described herein. For example, the network device230may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router or a provider core router), a virtual router, or another type of router. Additionally, or alternatively, the network device230may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, or a data center server), a load balancer, and/or a similar device. In some implementations, the network device230may be a physical device implemented within a housing, such as a chassis. In some implementations, the network device230may be a virtual device implemented by one or more computer devices of a cloud computing environment or a data center. In some implementations, a group of network devices230may be a group of data center nodes that are used to route traffic flow through network220.

The number and arrangement of devices and networks shown inFIG.2are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown inFIG.2. Furthermore, two or more devices shown inFIG.2may be implemented within a single device, or a single device shown inFIG.2may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of the environment200may perform one or more functions described as being performed by another set of devices of the environment200.

FIG.3is a diagram of example components of a device300associated with translation of a source intent policy model to a target intent policy model. The device300may correspond to the network management system201, the computing hardware203, and/or the network device230. In some implementations the network management system201, the computing hardware203, and/or the network device230may include one or more devices300and/or one or more components of the device300. As shown inFIG.3, the device300may include a bus310, a processor320, a memory330, an input component340, an output component350, and/or a communication component360.

The bus310may include one or more components that enable wired and/or wireless communication among the components of the device300. The bus310may couple together two or more components ofFIG.3, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling. For example, the bus310may include an electrical connection (e.g., a wire, a trace, and/or a lead) and/or a wireless bus. The processor320may include a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. The processor320may be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the processor320may include one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

The memory330may include volatile and/or nonvolatile memory. For example, the memory330may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). The memory330may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). The memory330may be a non-transitory computer-readable medium. The memory330may store information, one or more instructions, and/or software (e.g., one or more software applications) related to the operation of the device300. In some implementations, the memory330may include one or more memories that are coupled (e.g., communicatively coupled) to one or more processors (e.g., processor320), such as via the bus310. Communicative coupling between a processor320and a memory330may enable the processor320to read and/or process information stored in the memory330and/or to store information in the memory330.

The input component340may enable the device300to receive input, such as user input and/or sensed input. For example, the input component340may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. The output component350may enable the device300to provide output, such as via a display, a speaker, and/or a light-emitting diode. The communication component360may enable the device300to communicate with other devices via a wired connection and/or a wireless connection. For example, the communication component360may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

The device300may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory330) may store a set of instructions (e.g., one or more instructions or code) for execution by the processor320. The processor320may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors320, causes the one or more processors320and/or the device300to perform one or more operations or processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, the processor320may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown inFIG.3are provided as an example. The device300may include additional components, fewer components, different components, or differently arranged components than those shown inFIG.3. Additionally, or alternatively, a set of components (e.g., one or more components) of the device300may perform one or more functions described as being performed by another set of components of the device300.

FIG.4is a diagram of example components of a device400associated with translation of a source intent policy model to a target intent policy model. Device400may correspond to the network management system201, the computing hardware203, and/or the network device230. In some implementations, the network management system201, the computing hardware203, and/or the network device230may include one or more devices400and/or one or more components of device400. As shown inFIG.4, device400may include one or more input components410-1through410-B (B≥1) (hereinafter referred to collectively as input components410, and individually as input component410), a switching component420, one or more output components430-1through430-C (C≥1) (hereinafter referred to collectively as output components430, and individually as output component430), and a controller440.

Input component410may be one or more points of attachment for physical links and may be one or more points of entry for incoming traffic, such as packets. Input component410may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, input component410may transmit and/or receive packets. In some implementations, input component410may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memories, and/or input queues. In some implementations, device400may include one or more input components410.

Switching component420may interconnect input components410with output components430. In some implementations, switching component420may be implemented via one or more crossbars, via busses, and/or with shared memories. The shared memories may act as temporary buffers to store packets from input components410before the packets are eventually scheduled for delivery to output components430. In some implementations, switching component420may enable input components410, output components430, and/or controller440to communicate with one another.

Output component430may store packets and may schedule packets for transmission on output physical links. Output component430may support data link layer encapsulation or decapsulation, and/or a variety of higher-level protocols. In some implementations, output component430may transmit packets and/or receive packets. In some implementations, output component430may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and/or output queues. In some implementations, device400may include one or more output components430. In some implementations, input component410and output component430may be implemented by the same set of components (e.g., and input/output component may be a combination of input component410and output component430).

Controller440includes a processor in the form of, for example, a CPU, a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), and/or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller440may include one or more processors that can be programmed to perform a function.

In some implementations, controller440may include a RAM, a ROM, and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by controller440.

In some implementations, controller440may communicate with other devices, networks, and/or systems connected to device400to exchange information regarding network topology. Controller440may create routing tables based on the network topology information, may create forwarding tables based on the routing tables, and may forward the forwarding tables to input components410and/or output components430. Input components410and/or output components430may use the forwarding tables to perform route lookups for incoming and/or outgoing packets.

Controller440may perform one or more processes described herein. Controller440may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

Software instructions may be read into a memory and/or storage component associated with controller440from another computer-readable medium or from another device via a communication interface. When executed, software instructions stored in a memory and/or storage component associated with controller440may cause controller440to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown inFIG.4are provided as an example. In practice, device400may include additional components, fewer components, different components, or differently arranged components than those shown inFIG.4. Additionally, or alternatively, a set of components (e.g., one or more components) of device400may perform one or more functions described as being performed by another set of components of device400.

FIG.5is a flowchart of an example process500associated with translation of a source intent policy model to a target intent policy model. In some implementations, one or more process blocks ofFIG.5are performed by a system (e.g., the network management system201). In some implementations, one or more process blocks ofFIG.5are performed by another device or a group of devices separate from or including the system, such as a network device (e.g., the network device230). Additionally, or alternatively, one or more process blocks ofFIG.5may be performed by one or more components of device300, such as processor320, memory330, input component340, output component350, and/or communication component360; one or more components of device400, such as input component410, switching component420, output component430, and/or controller440; and/or one or more components of another device.

As shown inFIG.5, process500may include identifying a source intent policy model that is associated with a first graph having a plurality of source nodes connected by a plurality of source edges (block510). For example, the system may identify a source intent policy model that is associated with a first graph having a plurality of source nodes connected by a plurality of source edges, as described above.

As further shown inFIG.5, process500may include identifying a set of source nodes of the plurality of source nodes (block520). For example, the system may identify a set of source nodes of the plurality of source nodes, as described above.

As further shown inFIG.5, process500may include translating the set of source nodes to generate a set of target nodes (block530). For example, the system may translate the set of source nodes to generate a set of target nodes, as described above.

As further shown inFIG.5, process500may include identifying a subset of target nodes, of the set of target nodes, that are not included in a target intent policy model that is associated with a second graph having a plurality of target nodes connected by a plurality of target edges (block540). For example, the system may identify a subset of target nodes, of the set of target nodes, that are not included in a target intent policy model that is associated with a second graph having a plurality of target nodes connected by a plurality of target edges, as described above.

As further shown inFIG.5, process500may include determining a hierarchical order associated with the subset of target nodes and the plurality of target nodes (block550). For example, the system may determine a hierarchical order associated with the subset of target nodes and the plurality of target nodes, as described above.

As further shown inFIG.5, process500may include causing the target intent policy model to be updated to include the subset of target nodes and the plurality of target nodes, such that the second graph is ordered according to the hierarchical order (block560). For example, the system may cause the target intent policy model to be updated to include the subset of target nodes and the plurality of target nodes, such that the second graph is ordered according to the hierarchical order, as described above.

Process500may include additional implementations, such as any single implementation or any combination of implementations described below and/or in connection with one or more other processes described elsewhere herein.

In a first implementation, the plurality of source nodes includes one or more source intent nodes that are each associated with a source intent of the source intent policy model, the plurality of source nodes includes one or more source intent object nodes that are each associated with a source intent object of the source intent policy model, and the plurality of source edges indicate associations between the plurality of source nodes.

In a second implementation, alone or in combination with the first implementation, identifying the set of source nodes comprises identifying a first group of source nodes of the plurality of source nodes, identifying a second group of source nodes, of the plurality of source nodes, that depend from the first group of source nodes, and identifying the set of source nodes as comprising the first group of source nodes and the second group of source nodes.

In a third implementation, alone or in combination with one or more of the first and second implementations, translating the set of source nodes to generate the set of target nodes comprises traversing, using a depth first search technique, the set of source nodes, and translating, using a translation technique and based on the traversing the set of source nodes, a source node to a target node, wherein the translation technique is associated with the target intent policy model.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, the plurality of target nodes includes one or more target intent nodes that are each associated with a target intent of the target intent policy model, the plurality of target nodes includes one or more target intent object nodes that are each associated with a target intent object of the target intent policy model, and the plurality of target edges indicate associations between the plurality of target nodes.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, identifying the subset of target nodes that are not included in the target intent policy model comprises for each target node of the set of target nodes processing the target node to determine a hash value, determining whether one of the plurality of target nodes is associated with the hash value, and identifying the subset of target nodes as comprising the target node based on determining that one of the plurality of target nodes is not associated with the hash value.

In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, process500includes determining, based on determining the hierarchical order associated with the subset of target nodes and the plurality of target nodes, that a first target node, of the subset of target nodes, and a second target node, of the plurality of target nodes, conflict with each other.

In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, process500includes causing, based on determining that the first target node and the second target node conflict with each other, the second target node to be ordered before the first target node in the hierarchical order.

In an eighth implementation, alone or in combination with one or more of the first through seventh implementations, process500includes identifying, based on determining the hierarchical order associated with the subset of target nodes and the plurality of target nodes, that a target node, of the subset of target nodes and the plurality of target nodes, is redundant with another target node, of the subset of target nodes and the plurality of target nodes, and removing the target node from the subset of target nodes and the plurality of target nodes.

In a ninth implementation, alone or in combination with one or more of the first through eighth implementations, process500includes identifying, after causing the target intent policy model to be updated, a change to a particular source node of the plurality of source nodes; identifying a group of one or more source nodes, of the plurality of source nodes, that includes the particular source node, translating the group of one or more source nodes to generate a group of one or more target nodes; and for each target node of the group of one or more target nodes identifying a corresponding target node, of the subset of target nodes and the plurality of target nodes, determining whether the target node matches the corresponding target node, and replacing the corresponding target node with the target node based on determining that the target node does not match the corresponding target node.

AlthoughFIG.5shows example blocks of process500, in some implementations, process500includes additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.5. Additionally, or alternatively, two or more of the blocks of process500may be performed in parallel.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the implementations.

As used herein, the term “component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code—it being understood that software and hardware can be used to implement the systems and/or methods based on the description herein.

Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various implementations includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiple of the same item.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).