IP Library › Granted Patent US 10,541,872
Granted Patent B2
US 10,541,872 · App. 15/507,461 · Granted Jan 21, 2020

Network policy distribution

Inventors: Duane E. Mentze (Roseville, CA); Charles F. Clark (Roseville, CA); Shaun Wackerly (Roseville, CA)
Assignee: Hewlett Packard Enterprise Development LP
H04L41/0893H04L41/20H04L69/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,541,872
App. No.
15/507,461
Granted
Jan 21, 2020
Kind
B2
Abstract

Example implementations relate to network policy distribution. For example, a system for network policy distribution can include a state engine to determine a change in a state of a network, a policy engine to determine a number of policy changes based on the change in the state of the network, an identification engine to identify a number of network endpoints that correspond to the number of policy changes, and a distribution engine to load instructions based on the number of policy changes to the number of endpoints that correspond to the number of policy changes.

Claims (43)

1. A system, comprising:

a processing resource; and

a memory resource including instructions that, when executed by the processing resource, cause the system to:

determine a number of network changes for a network;

assign a category to the number of network changes;

determine a number of policy changes based on the number of network changes;

identify a number of network endpoints that correspond to the number of network changes; and

load instructions based on the number of policy changes to the number of endpoints that correspond to the category assigned to the number of network changes.

2. The system of claim 1 , wherein the network endpoints that correspond to the number of network changes include endpoints that are affected by the number of network changes.

3. The system of claim 1 , wherein the network endpoints that correspond to the number of network changes include endpoints where the number of policy changes are to be instantiated.

4. The system of claim 1 , wherein the instructions are loaded to only the number of endpoints where the number of policy changes are to be instantiated.

5. The system of claim 4 , wherein the instructions are not loaded to the number of endpoints where the policy changes are not to be instantiated.

6. The system of claim 1 , wherein the number of endpoints have been located at a plurality of locations within the network.

7. The system of claim 6 , wherein the instructions are loaded to each of the plurality of locations where the number of endpoints have been located.

8. A non-transitory computer readable medium storing instructions executable by a processing resource to cause a computer to:

identify a number of network changes;

determine a number of endpoints from a plurality of endpoints that correspond to the number of network changes;

assign a category to the number of network changes;

apply a number of policy changes based on the number of network changes to the number of endpoints that correspond to the number of network changes; and

load instructions based on the number of policy changes to the number of endpoints that correspond to the category assigned to the number of network changes.

9. The medium of claim 8 , wherein the number of policy changes include:

new policies;

edited policies;

unedited policies; and

deleted policies.

10. The medium of claim 8 , wherein the number of policy changes are put into at least one of a number of categories including:

policy changes;

application changes;

extensibility changes;

domain changes;

endpoint changes;

device changes; and

server group member changes.

11. The medium of claim 10 , wherein the number of endpoints that correspond to the number of network changes is based on the category of the number of network changes.

12. A method, comprising:

identifying a number of network changes for a network;

determining a number of endpoints corresponding to a number of network controllers of the network;

assigning a category to the number of network changes;

determining a number of policy changes based on the number of network changes; and

loading instructions based on the number of policy changes to the number of endpoints that correspond to a category assigned to the number of network changes.

13. The method of claim 12 , wherein the number of policy changes are sent to a portion of the number of network controllers that correspond to the number of endpoints.

14. The method of claim 12 , wherein the category indicates a number of network devices that service the number of endpoints.

15. The method of claim 12 , wherein determining the number of policy changes includes comparing a previous list of orthogonal merge units (OMUs) to an updated list of OMUs.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 8, 2017
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 041918/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 28, 2017
From: MENTZE, DUANE E.; CLARK, CHARLES F.; WACKERLY, SHAUN
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 041399/0696 →
Continuity (1)
Related Publication 20180227184A1 · Aug 9, 2018