# US 10,455,053 B2 · Systems and methods for provisioning network automation by logically separating L2-L3 entities from L4-L7 entities using a software defined network (SDN) controller > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,053 B2 - Document ID: US10455053B2 - Status: Granted - Kind: B2 - Application number: 15/601,476 - Filed: 2017-05-22 - Published: 2017-11-23 - Granted: 2019-10-22 - Earliest claimed: 2016-05-23 - Assignees: Citrix Systems, Inc. - Applicants: Citrix Systems, Inc. - Inventors: Satyendra Tiwari; Vijay Kumar Venkatachalam; Yi Wang - Web page: https://patentgrep.com/patent/US10455053B2 ## CPC - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 67/566: Grouping or aggregating service requests, e.g. for unified processing - H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) - H04W 76/11: Allocation or use of connection identifiers - H04W 76/12: Setup of transport tunnels - H04L 41/046: comprising network management agents or mobile agents therefor - H04L 41/0876: {Aspects of the degree of configuration automation} - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 41/50: Network service management, e.g. ensuring proper service fulfilment according to agreements - H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters - H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV - H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)} - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Methods and systems for providing network models and network configurations for communications are described. The method includes establishing, by a device intermediary to a plurality of clients and servers, a first interface on a manager of the device for delivering a network model of the device from the manager of the device to a software defined network (SDN) controller of an SDN. The method includes providing, via the first interface, the network model configured to provide definitions of one or more network layer entities of the device that are configured to provide network layer services. The method includes establishing, a second interface on the manager of the device configured to transmit and receive communications between the device and the SDN controller. The method includes receiving, by the manager via the second interface, network configuration to configure the device to process SDN application requests received from the SDN controller. ## Claims ### Claim 1 A method for providing network models and network configurations for communications, the method comprising: establishing, by a device intermediary to a plurality of clients and one or more servers, a first interface on a manager of the device for delivering a network model of the device from the manager of the device to a software defined network (SDN) controller of an SDN; providing, by the device to the SDN controller, via the first interface, the network model configured to provide definitions of one or more network layer entities of the device that are configured to provide network layer services; establishing, by the device, a second interface on the manager of the device configured to transmit and receive communications between the device and the SDN controller; and receiving, by the manager of the device via the second interface, network configuration to configure the device to process SDN application requests received from the SDN controller, the network configuration established using the network model provided by the device to the SDN controller. ### Claim 2 (depends on 1) The method of claim 1, wherein the network model comprises definitions of layer 2 to layer 3 network entities configured on the device. ### Claim 3 (depends on 1) The method of claim 1, wherein the network model is configured to allow the SDN controller to identify or discover capabilities of the layer 2 to layer 7 network entities configured on the device. ### Claim 4 (depends on 1) The method of claim 1, further comprising receiving, by the manager of the device via the second interface, a request including a payload that is generated using the network model. ### Claim 5 (depends on 1) The method of claim 1, further comprising receiving, by the manager of the device via the second interface, a request including a payload that is generated by mapping SDN callouts to application programming interface (API) calls to the device. ### Claim 6 (depends on 5) The method of claim 5, wherein the request from the SDN controller is generated responsive to the SDN controller converting SDN specific callouts into function calls configured to be processed by the second interface established on the device. ### Claim 7 (depends on 5) The method of claim 5, wherein the request includes at least one of an SDN specific callout method, a device payload or a configuration payload. ### Claim 8 (depends on 1) The method of claim 1, wherein the second interface is configured to cause the manager of the device to accept the request for processing. ### Claim 9 (depends on 1) The method of claim 1, further comprising generating, by the manager of the device, a response to the request including an SDN-specific error message converted from a device specific error, the SDN-specific error message generated using the network configuration received from the SDN controller via the second interface. ### Claim 10 (depends on 9) The method of claim 9, wherein the error handling module includes a list of SDN-specific error codes and is configured to convert device specific errors to SDN-specific error codes based on a mapping of the list of SDN-specific error codes to a list of device specific error codes. ### Claim 11 A system for providing network models and network configurations for communications, the method comprising: a device intermediary to a plurality of clients and one or more servers, the device including a first interface established on a manager of the device for delivering a network model of the device from the manager of the device to a software defined network (SDN) controller of an SDN, the first interface configured to provide, to the SDN Controller, the network model configured to provide definitions of one or more network layer entities of the device that are configured to provide network layer services; and a second interface established on the manager of the device for transmitting and receiving communications between the device and the SDN controller, the second interface configured to receive a network configuration to configure the device to process SDN application requests received from the SDN controller, the network configuration established using the network model provided by the device to the SDN controller. ### Claim 12 (depends on 11) The system of claim 11, wherein the network model comprises definitions of layer 2 to layer 3 network entities configured on the device. ### Claim 13 (depends on 11) The system of claim 11, wherein the network model is configured to allow the SDN controller to identify or discover capabilities of the layer 2 to layer 7 network entities configured on the device. ### Claim 14 (depends on 11) The system of claim 11, wherein the manager of the device is configured to receive, via the second interface, a request including a payload that is generated using the network model. ### Claim 15 (depends on 11) The system of claim 11, wherein the manager of the device is configured to receive, via the second interface, a request including a payload that is generated by mapping SDN callouts to application programming interface (API) calls to the device. ### Claim 16 (depends on 15) The system of claim 15, wherein the request from the SDN controller is generated responsive to the SDN controller converting SDN specific callouts into function calls configured to be processed by the second interface established on the device. ### Claim 17 (depends on 15) The system of claim 15, wherein the request includes at least one of an SDN specific callout method, a device payload or a configuration payload. ### Claim 18 (depends on 11) The system of claim 11, wherein the second interface is configured to cause the manager of the device to accept the request for processing. ### Claim 19 (depends on 11) The system of claim 11, wherein the manager of the device is configured to generate a response to the request including an SDN-specific error message converted from a device specific error, the SDN-specific error message generated using the network configuration received from the SDN controller via the second interface. ### Claim 20 (depends on 19) The system of claim 19, wherein the error handling module includes a list of SDN-specific error codes and is configured to convert device specific errors to SDN-specific error codes based on a mapping of the list of SDN-specific error codes to a list of device specific error codes.