Hewlett Packard Enterprise Development LP

Uyen Chau

Thomas Vachuska

Chinlin Chen

Simon Hunt

Mark A Parenti

Faraz Ahmed

Lianjie Cao

Timothy M Ireland

Mathieu Riverin

Rajaseelan Manavalan

A system and method are provided which facilitate a unified network management for a heterogeneous edge enterprise network. In one aspect, the system establishes, by a cloud controller, a secure connection to an edge device in an edge network. The cloud controller deploys to the edge device a module which includes a proxy agent, thereby allowing the module to be installed on the edge device. The system monitors data obtained from the edge device based on a set of rules. Responsive to detecting a trigger condition based on the monitored data, the system performs a predetermined action corresponding to the detected trigger condition. The predetermined action can comprise sending a configuration command to be executed on the edge device or sending an action to be performed by the proxy agent on other entities communicatively coupled to the edge network (e.g., client devices and applications).

Unified network management for heterogeneous edge enterprise network

A network management system (NMS) that can provision and manage a network is provided. During operation, the NMS can determine, for a respective network device in the network, connectivity information indicating how the network device is connected within the network and a device profile of the network device. The NMS can then determine a connectivity tier of the network device in the network based on the connectivity information. The connectivity tier can correspond to a placement of the network device in a hierarchy of network devices in the network. The NMS can select a device persona associated with the connectivity tier. Here, the device persona indicates specification and configurations for the network device. The NMS can send, to the network device, configuration information that configurates the device persona on the network device.

Dynamic device persona identification in a network

One aspect described in this application provides a unified policy broker. During operation, the system receives configuration information from the set of network devices. At least two network devices in the network can be equipped with a first and a second policy enforcement engine, respectively, for enforcing one or more given policy rules. The system can determine, based on the configuration information, a first and a second representation of the similar policy function corresponding to the first and the second policy enforcement engine, respectively. The system can apply a unified policy model to perform a first mapping from a unified representation of the similar policy function to the first and the second representation. The system can create a unified API based on the unified representation. The system applies, via a user interface, the unified API to configure the similar policy function across the first and the second policy enforcement engines.

Unified policy broker

Modifying a priority for at least one flow class of an application includes registering flow classes for an application with a SDN controller, determining, with the SDN controller, a priority for each of the flow classes based on other installed applications and network services on the SDN controller, modifying, based on an event, the priority for at least one of the flow classes of the application by mapping a priority key associated with the priority to a new priority value, receiving, from the application, at least one flow modification rule using a priority key as the priority, and validating the at least one flow modification rule against registered parameters of at least one of the flow classes of the application to determine a flow of traffic based on the priority.

Modifying a priority for at least one flow class of an application on a software defined networking controller

Prioritizing at least one flow class for an application on a software defined networking (SDN) controller includes registering flow classes for an application with a SDN controller, determining, with the SDN controller, a priority for each of the flow classes based on other installed applications and network services on the SDN controller, receiving, from the application, at least one flow modification rule using a priority key as the priority, and validating the at least one flow modification rule against registered parameters of at least one of the flow classes of the application to determine a flow of traffic based on the priority.

Growing community of inventors

Roseville, CA, United States of America

Uyen Chau