# US 2025/0158882 A1 · Incremental network intent provisioning

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0158882 A1
- Document ID: US20250158882A1
- Status: Published application
- Kind: A1
- Application number: 19/025,745
- Filed: 2025-01-16
- Published: 2025-05-15
- Earliest claimed: 2022-01-12
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Ankur Bhargava; Anand Krishnamurthy; Kenneth William Chambers; Gavin Llewellyn Camp
- Web page: https://patentgrep.com/patent/US20250158882A1

## CPC

- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0886: {Fully automatic configuration}
- H04L 41/12: Discovery or management of network topologies
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 41/145: {involving simulating, designing, planning or modelling of a network}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for provisioning a network may include, with a network controller, identifying a first network intent of a computing network based at least in part on an execution of a user interface (UI) or API layer at a client device, and identifying a modification of an object within the first network intent within the UI or API layer at the client device as the first network intent is being modified. The modification defines a delta between the first network intent and a second network intent. The method may further include, with a provisioning service executed by the network controller, receiving the delta from the client device, and provisioning a computing device within the computing network based at least in part on the delta. The method further includes automatically modifying the object based on the received delta, including a further modification of the second network intent.

## Claims

### Claim 1

A method of provisioning a configuration, comprising:
identifying a first configuration intent of a computing device based at least in part on an execution of an application program interface (API) at a client device;
identifying a modification of an object within the first configuration intent at the client device as the first configuration intent is being modified, the modification defining a delta between the first configuration intent and a second configuration intent, wherein:
the delta comprises a size that is smaller relative to the first configuration intent and the second configuration intent, and
the delta is defined by a change log identifying a type of change log item, the change log item storing the modification of the object in a base class;
receiving the delta as a payload from the client device; and
provisioning the second configuration intent on the computing device based at least in part on the delta.

### Claim 2 (depends on 1)

The method of claim 1, further comprising automatically modifying the object based on the delta, wherein automatically modifying the object includes a further modification of the second configuration intent.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the change log item includes a name, a type, and a property type,
the type includes a method, and
the property type incudes at least one of an attribute, an association, or combinations thereof.

### Claim 4 (depends on 3)

The method of claim 3, wherein identifying the modification further comprises adding logic to the change log to record the delta within the change log for every instance of the attribute, the association, or the combinations thereof.

### Claim 5 (depends on 1)

The method of claim 1, further comprising modifying the API based at least in part on the second configuration intent.

### Claim 6 (depends on 5)

The method of claim 5, wherein:
the modification of the API comprises at least one of modification of the object within the API due to user input, modification of the object within the API due to an automatic calculation in a backend of a network controller, or combinations thereof, and
the modification comprises at least one of a number of attributes and a number of associations between computing devices within the computing device.

### Claim 7 (depends on 1)

The method of claim 1, further comprising translating the second configuration intent into a device model based at least in part on the delta.

### Claim 8 (depends on 7)

The method of claim 7, wherein the second configuration intent is serialized as JavaScript object notation (JSON) data-interchange format including the delta for the object.

### Claim 9 (depends on 8)

The method of claim 8, wherein provisioning the second configuration intent on the computing device within the computing device based at least in part on the delta, comprises:
with a plugin of a network controller, reading a change log generated based at least in part on the delta; and
based at least in part on the change log:
invoking a translation method associated with the change log;
generating a first resource-facing service (RFS) object operation; and
ignoring a remaining translation that does not change in at least a second RFS object operation.

### Claim 10

A non-transitory computer-readable medium storing instructions that, when executed, causes a processor to perform operations, comprising:
identifying a first configuration intent of a computing device based at least in part on an execution of an application program interface (API) at a client device;
identifying a modification of an object within the first configuration intent at the client device as the first configuration intent is being modified, the modification defining a delta between the first configuration intent and a second configuration intent, wherein:
the delta comprises a size that is smaller relative to the first configuration intent and the second configuration intent, and
the delta is defined by a change log identifying a type of change log item, the change log item storing the modification of the object in a base class;
receiving the delta as a payload from the client device; and
provisioning the second configuration intent on the computing device within the computing device based at least in part on the delta.

### Claim 11 (depends on 10)

The non-transitory computer-readable medium of claim 10, the operations further comprising automatically modifying the object based on the delta, wherein automatically modifying the object includes a further modification of the second configuration intent.

### Claim 12 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein:
the change log item includes a name, a type, and a property type,
the type includes a method, and
the property type incudes an attribute, an association, or combinations thereof.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, the operations further comprising:
adding logic to the change log for every instance of attribute or association; and
translating the second configuration intent into a device model based at least in part on the delta,
wherein an intent model is serialized as JavaScript object notation (JSON) data-interchange format, including the delta for the object.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein provisioning the second configuration intent on the computing device within the computing device based at least in part on the delta, comprises:
with a plugin of a network controller, reading a change log generated based on at least in part on the delta; and
based at least in part on the change log:
invoking a translation method associated with the change log;
generating a first resource-facing service (RFS) object operation; and
ignoring a remaining translation that does not change in at least a second RFS object operation.

### Claim 15

A network controller comprising:
a processor; and
a non-transitory computer-readable media storing instructions that, when executed by the processor, causes the processor to perform operations comprising:
identifying a first configuration intent of a computing device based at least in part on an execution of an application program interface (API) at a client device;
identifying a modification of an object within the first configuration intent at the client device as the first configuration intent is being modified, the modification defining a delta between the first configuration intent and a second configuration intent, wherein:
the delta comprises a size that is smaller relative to the first configuration intent and the second configuration intent, and
the delta is defined by a change log identifying a type of change log item, the change log item storing the modification of the object in a base class;
receiving the delta as a payload from the client device; and
provisioning the second configuration intent on the computing device within the computing device based at least in part on the delta.

### Claim 16 (depends on 15)

The network controller of claim 15, wherein:
the change log item includes a name, a type, and a property type,
the type includes a method, and
the property type incudes an attribute, an association, or combinations thereof.

### Claim 17 (depends on 16)

The network controller of claim 16, the operations further comprising adding logic to the change log for every instance of attribute or association.

### Claim 18 (depends on 15)

The network controller of claim 15, the operations further comprising:
modifying the API based at least in part on the second configuration intent,
wherein the modification of the API comprises modification of at least one object within the API due to user input, the modification comprising at least one of a number of attributes and a number of associations between computing devices within the computing device.

### Claim 19 (depends on 15)

The network controller of claim 15, the operations further comprising translating the second configuration intent into a device model based at least in part on the delta.

### Claim 20 (depends on 19)

The network controller of claim 19, wherein provisioning the second configuration intent on the computing device within the computing device based at least in part on the delta, comprises:
with a plugin, reading a change log generated based at least in part on the delta; and
based at least in part on the change log:
invoking a translation method associated with the change log;
generating a first resource-facing service (RFS) object operation; and
ignoring a remaining translation that does not change in at least a second RFS object operation.
