Network Device Control in a Software Defined Network

• US 20150023210A1
• Filed: 03/27/2012
• Published: 01/22/2015
• Est. Priority Date: 01/09/2012
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Kis, Zoltn Lajos
• Application Number:
  US14/370,495
• Publication Number:
  US 20150023210A1
• Time in Patent Office: Days
• US Class Current: 370/254
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/342 between virtual entities, e.g. orchestrators, SDN or NFV entities
• CPC Class Codes: H04L 45/563 Software download or update

Abstract

A technique for programming or querying a network device in a Software Defined Network (SDN) via a communications protocol is provided. A method realization of that technique implemented by a controller of the SDN comprises the step of creating at least one template for a type message defined by the communications protocol. The template predefines at least one value for at least one parameter conveyed by that type of message. The at least one template is sent to the network device for installation by that network device. The communications protocol may be one of the OpenFlow protocol and the ForCES Forwarding Element Model protocol as defined in RFC 5812.

Claims

1-27. -27. (canceled)

28. A method implemented by a controller in a software defined network for programming or querying a network device via a communications protocol, the method comprising:

creating at least one template for a type of message defined by the communications protocol, wherein the template predefines at least one value for at least one parameter conveyed by that type of message, which is an add flow message directed at installing a new data packet flow onto the network device;

sending the at least one template to the network device for installation by that network device to enable planning to which hardware resources of the network device flows added based on the template will be mapped; and

receiving from the network device a report indicative of how many flows can be added based on the template.

29. The method of claim 28 further comprising:

generating a message of the type for which the at least one template is installed at the network device, wherein the message refers to the template and specifies a value for at least one parameter whose value has not already been specified by that template; and

sending the generated message to the network device.

30. The method of claim 29, wherein the generating step is responsive to determining:

that a message of said type is to be sent to the network device; and

that one or more parameter values to be to conveyed by such a message match or otherwise correspond to a template created for that message type.

31. A method implemented by a network device in a software defined network, wherein the network device is configured to be remotely programmed or queried by a controller via a communications protocol, the method comprising:

receiving at least one template for a type of message defined by the communications protocol, wherein the template predefines at least one value for at least one parameter conveyed by that type of message, which is an add flow message directed at installing a new data packet flow onto the network device;

installing the at least one template, wherein the installation includes planning to which hardware resources of the network device flows added based on the template will be mapped; and

reporting to the controller how many flows can be added based on the template.

32. The method of claim 31, wherein installing the at least one template includes at least one of

storing the at least one template;

interpreting or otherwise inspecting the at least one parameter value;

checking the extent to which the network device is capable of receiving and/or processing messages that refer to the template; and

planning for hardware mapping based on the at least one template.

33. The method of claim 32, wherein the type of message is an add flow message directed at installing a new data packet flow onto the network device, and wherein the checking step is performed once for the at least one template and eliminates at least some flow-specific checking steps upon receipt of an add flow message referring to that template.

34. The method of claim 32, wherein in the at least one template one or more values for one or more masking parameters regarding masking of packet addresses are predefined, and wherein the planning step is based on that one or more predefined values.

35. The method of claim 32, wherein the type of message is an add flow message directed at installing a new data packet flow onto the network device, wherein the at least one template comprises information that describes the extent to which flows are expected to be added from that template, and wherein the planning step is based on that information.

36. The method of claim 31, wherein installing the at least template comprises checking the extent to which the network device is capable of at least one of:

determining whether incoming data packets meet certain criteria specified in the at least one template; and

performing certain processing specified in the at least one template.

37. The method of claim 31, wherein the type of message is an add flow message directed at installing a new data packet flow onto the network device.

38. The method of claim 31, wherein the type of message is a statistics request message that queries the network device for statistics concerning one or more data packet flows installed onto the network device, and wherein installing the at least one template comprises creating one or more counters for the expected requests.

39. The method of claim 31, further comprising:

receiving a message of the type for which the at least one template is installed at the network device, wherein the message refers to the template and specifies a value for at least one parameter whose value has not already been specified by that template; and

processing the message in accordance with at least one parameter value specified in the received message itself and at least one parameter value predefined in the template to which the message refers.

40. The method of claim 39, wherein the at least one template has an identifier, and wherein the message refers to the template by specifying its identifier.

41. The method of claim 31, wherein for a given type of message multiple templates are provided, each template predefining values for a selected subset of parameters, wherein different templates predefine different values for at least one of the same selected subset of parameters and different selected subsets of parameters.

42. The method of claim 31, wherein the type of message is one of a state programming message and a state querying message with respect to a state of the network device.

43. The method of claim 42, wherein the state programming message instantiates, deletes or modifies a rule to the network device that governs or otherwise defines processing in a data plane with respect to received data packets that meet certain criteria.

44. The method of claim 43, wherein the rule pertains to one of a data packet flow entry in a flow table and a data packet flow group in a flow table.

45. The method of claim 42, wherein the state querying message is directed at collecting statistics pertaining to the processing of data packets by the network device.

46. The method of claim 31, wherein the at least one template bears the same format as a data packet flow description specified in the communications protocol.

47. The method of claim 46, wherein the at least one template in the data packet flow description format comprises description fields and an annotation in order to appoint the description fields as being either predefined values or template variables to be filled in later.

48. The method of claim 31, wherein the communications protocol is one of the OpenFlow protocol and the ForCES Forwarding Element Model protocol as defined in RFC 5812.

49. A non-transitory computer-readable medium storing a computer program product comprising program code portions that, when executed on a controller in a software defined network, configures the controller for programming or querying a network device via a communications protocol, including configuring the controller to:

create at least one template for a type of message defined by the communications protocol, wherein the template predefines at least one value for at least one parameter conveyed by that type of message, which is an add flow message directed at installing a new data packet flow onto the network device;

send the at least one template to the network device for installation by that network device to enable planning to which hardware resources of the network device flows added based on the template will be mapped; and

receive from the network device a report indicative of how many flows can be added based on the template.

50. A controller for a software defined network, the controller being configured to program or query a network device via a communications protocol and comprising:

a template creator configured to create at least one template for a type of message defined by the communications protocol, wherein the template predefines at least one value for at least one parameter conveyed by that type of message, which is an add flow message directed at installing a new data packet flow onto the network device; and

an interface configured to send the at least one template to the network device for installation by that network device to enable planning to which hardware resources of the network device flows added based on the template will be mapped, and to receive from the network device a report indicative of how many flows can be added based on the template.

51. The controller of claim 50, further comprising:

a message generator configured to generate a message of the type for which the at least one template is installed at the network device, wherein the message refers to the template and specifies a value for at least one parameter whose value has not already been specified by that template; and

an interface configured to send the generated message to the network device.

52. A network device of a software defined network, wherein the network device is configured to be remotely programmed or queried by a controller via a communications protocol, the network device comprising:

an interface configured to receive at least one template for a type of message defined by the communications protocol, wherein the template predefines at least one value for at least one parameter conveyed by that type of message, which is an add flow message directed at installing a new data packet flow onto the network device; and

a template installer configured to install the at least one template, wherein the installation includes planning to which hardware resources of the network device flows added based on the template will be mapped;

wherein the interface is further configured to report to the controller how many flows can be added based on the template.

53. The network device of claim 52, further comprising:

an interface configured to receive a message of the type for which the at least one template is installed at the network device, wherein the message refers to the template and specifies a value for at least one parameter whose value has not already been specified by that template; and

a message processor configured to process the message in accordance with at least one parameter value specified in the received message itself and at least one parameter value predefined in the template to which the message refers.