Network element of a software-defined network

1. A network element for a software-defined network, the network element comprising:

functional entities that include connections that transfer data between the functional entities regardless of a topology of the software-defined network,

two or more of the functional entities being configurable with configuration data received from a controller of the software-defined network,

wherein the network element comprises a processing system that controls the network element to transmit, to the controller of the software-defined network, two or more entity-specific capability descriptors related to the two or more functional entities configurable with the configuration data,

wherein each one of the entity-specific capability descriptors expresses operations operable to be carried out by a functional entity related thereto, and

wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of one or more look-up tables defining actions implementable by a functional entity related to the at least one entity-specific capability descriptor.

2. The network element according to claim 1 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports one or more of the following: L3 network layer routing, L2 data link layer switching, the MultiProtocol Label Switching MPLS.

3. The network element according to claim 1 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports one or more of the following: ingress functionalities for receiving data from outside of the network element, egress functionalities for transmitting data out from the network element, switching functionalities for relaying data between other ones of the functional entities.

4. The network element according to claim 1 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports Deep Packet Inspection DPI.

5. The network element according to claim 1 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports Internet Protocol Security IPSec.

6. The network element according to claim 1 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration is operable to deliver signaling data to one or more other of the functional entities, the signaling data being determined at least partly in accordance with the configuration data and being additional to data received from the other network elements when the network element is operating in accordance with the configuration data.

7. The network element according to claim 1 , wherein one or more of the functional entities are line interface modules each comprising a receiver for receiving data from outside of the network element and a transmitter for transmitting data out from the network element.

8. The network element according to claim 1 , wherein at least one of the functional entities is an ingress side of a line interface module comprising a receiver for receiving data from outside of the network element, and at least one of the functional entities is an egress side of the line interface module comprising a transmitter for transmitting data out from the network element.

9. The network element according to claim 1 , wherein the network element is at least one of the following: an Internet Protocol IP router, a MultiProtocol Label Switching MPLS switch, a packet optical switch, an Ethernet switch.

10. A controller for configuring a network element of a software-defined network, where the network element includes functional entities forming connections for transferring data between the functional entities regardless of a topology of the software-defined network, the controller comprising:

a data transfer interface for receiving data from the network element and for transmitting data to the network element, and

a processing system for forming configuration data for the network element,

wherein the processing system includes a processor and a memory, the memory having programming code stored therein that, upon execution by the processor, causes the processing system to:

form entity-specific portions of the configuration data for the functional entities of the network element in accordance with entity-specific capability descriptors related to the functional entities, and

provide the entity-specific portions of the configuration data with entity-identifiers so as to enable the network element to allocate the entity-specific portions of the configuration data to respective ones of the functional entities and to configure each of the functional entities with an appropriate entity-specific portion of the configuration data,

wherein each one of the entity-specific capability descriptors expresses operations operable to be carried out by the a functional entity related thereto, and

wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of one or more look-up tables defining actions implementable by a functional entity related to the at least one entity-specific capability descriptor.

11. The controller according to claim 10 , wherein the processing system forms the configuration data so that the network element gets configured to forward data to another network element in response to a situation in which, according to the entity-specific capability descriptors, the functional entities of the network element are unable to carry out an operation required to be directed to the data under consideration and the other network element is operable to carry out the required operation.

12. A method for enabling a controller of a software-defined network to configure a network element of a software-defined network, the network element comprising functional entities including connections that transfer data between the functional entities regardless of a topology of the software-defined network, and two or more of the functional entities being configurable with configuration data received from the controller of the software-defined network, the method comprising:

transmitting, to the controller of the software-defined network, two or more entity-specific capability descriptors related to the two or more functional entities configurable with the configuration data,

wherein each one of the entity-specific capability descriptors expresses operations operable to be carried out by the functional entity related thereto, and

wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of one or more look-up tables define actions implementable by a functional entity related to the at least one entity-specific capability descriptor.

13. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports one or more of the following: L3 network layer routing, L2 data link layer switching, the MultiProtocol Label Switching MPLS.

14. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports one or more of the following: ingress functionalities for receiving data from outside of the network element, egress functionalities for transmitting data out from the network element, switching functionalities for relaying data between other ones of the functional entities.

15. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports Deep Packet Inspection DPI.

16. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration supports Internet Protocol Security IPSec.

17. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of look-up tables implementable in the functional entity related to the entity-specific capability descriptor under consideration.

18. The method according to claim 12 , wherein at least one of the entity-specific capability descriptors expresses whether or not the functional entity related to the entity-specific capability descriptor under consideration is operable to deliver signaling data to one or more other of the functional entities, the signaling data being determined at least partly in accordance with the configuration data and being additional to data received from the other network elements when the network element is operating in accordance with the configuration data.

19. The method according to claim 12 , wherein one or more of the functional entities are line interface modules each comprising a receiver for receiving data from outside of the network element and a transmitter for transmitting data out from the network element.

20. The method according to claim 12 , wherein at least one of the functional entities is an ingress side of a line interface module comprising a receiver for receiving data from outside of the network element, and at least one of the functional entities is an egress side of the line interface module comprising a transmitter for transmitting data out from the network element.

21. A method for configuring a network element of a software-defined network, the network element comprising functional entities including connections that transfer data between the functional entities regardless of a topology of the software-defined network, and two or more of the functional entities being configurable with configuration data received from a controller of the software-defined network, the method comprising:

forming configuration data for the network element, and

transmitting the configuration data to the network element,

wherein the forming the configuration data comprises:

forming entity-specific portions of the configuration data for the functional entities of the network element in accordance with entity-specific capability descriptors related to the functional entities, and

providing the entity-specific portions of the configuration data with entity-identifiers so as to enable the network element to allocate the entity-specific portions of the configuration data to respective ones of the functional entities and to configure each of the functional entities with an appropriate entity-specific portion of the configuration data,

wherein each one of the entity-specific capability descriptors expresses operations operable to be carried out by a functional entity related thereto, and

wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of one or more look-up tables defining actions implementable by a functional entity related to the at least one entity-specific capability descriptor.

22. A non-transitory computer readable medium encoded with a computer program comprising computer executable instructions for controlling a programmable processing system of a network element of a software-defined network to:

control the network element to transmit, to a controller of the software-defined network, two or more entity-specific capability descriptors related to two or more functional entities of the network element, the functional entities including connections that transfer data between the functional entities regardless of a topology of the software-defined network,

wherein each of the two or more functional entities is configurable with configuration data received from the controller, and each one of the entity-specific capability descriptors expresses operations operable to be carried out by a functional entity related thereto, and

wherein at least one of the entity-specific capability descriptors expresses limitations relating to structures and interconnections of one or more look-up tables defining actions implementable by a functional entity related to the at least one entity-specific capability descriptor.

23. The non-transitory computer readable medium encoded with a computer program according to claim 22 , wherein the computer program comprises computer executable instructions for controlling a programmable processing system of the controller of the software-defined network to:

form entity-specific portions of the configuration data for the functional entities of the network element in accordance with the entity-specific capability descriptors, and

provide the entity-specific portions of the configuration data with entity-identifiers so as to enable the network element to allocate the entity-specific portions of the configuration data to respective ones of the functional entities and to configure each of the functional entities with an appropriate entity-specific portion of the configuration data.