Abstract: Data packets are received at a communication device that is coupled to a network node in a communication network, to a gateway router that is coupled to other network nodes in the communication network, and to a further communication network. For each received data packet, a determination is made as to whether the received data packet is to be routed toward a destination by the communication device instead of by the gateway router. The received data packet is routed toward the destination by the communication device based on determining that the received data packet is to be routed toward the destination by the communication device instead of by the gateway router. Otherwise, the received data packet is switched from the communication device to the gateway router to be routed by the gateway router toward the destination.

Abstract: Data packets are received at a communication device that is coupled to a network node in a communication network, to a gateway router that is coupled to other network nodes in the communication network, and to a further communication network. For each received data packet, a determination is made as to whether the received data packet is to be routed toward a destination by the communication device instead of by the gateway router. The received data packet is routed toward the destination by the communication device based on determining that the received data packet is to be routed toward the destination by the communication device instead of by the gateway router. Otherwise, the received data packet is switched from the communication device to the gateway router to be routed by the gateway router toward the destination.

Abstract: Header field identifiers can be dynamically bound to header fields in software defined networks via signaling between software defined network (SDN) controllers and switches. Dynamically establishing header binding definitions may allow new header fields to be recognized and manipulated (e.g., matched, modified, etc.) by SDN switches without having to update the corresponding standard. To achieve this, an SDN controller sends a binding request to an SDN switch to propose that a header field identifier be dynamically associated with a header field type. If the SDN switch acknowledges the binding request, then the header field identifier is used to identify the header field type in messages (e.g., control messages, etc.) transmitted to the SDN switch.

Abstract: A method implemented by a network controller in a software-defined network (SDN), the method comprising obtaining a first control macro (CM) that defines at least one first flow pattern, wherein the first CM comprises at least one command and at least one parameter associated with the command, identifying a first network function associated with the first flow pattern and a first network node, determining a parameter value for the parameter according to the first network function, and sending a first CM invocation message to the first network node to request execution of the first CM to establish the first network function, wherein the first CM invocation message comprises the parameter value.

Abstract: A method implemented in a network element (NE), comprising receiving a flow configuration message identifying a flow context in a software-defined network (SDN) and a network control associated with the flow context, wherein the flow configuration message comprises a function object (FO) reference that identifies the network control, generating an FO based on the FO reference, wherein the FO comprises a plurality of network behaviors associated with the network control, and performing the network control for the flow context based on the FO generated by the NE.

Abstract: Header field identifiers can be dynamically bound to header fields in software defined networks via signaling between software defined network (SDN) controllers and switches. Dynamically establishing header binding definitions may allow new header fields to be recognized and manipulated (e.g., matched, modified, etc.) by SDN switches without having to update the corresponding standard. To achieve this, an SDN controller sends a binding request to an SDN switch to propose that a header field identifier be dynamically associated with a header field type. If the SDN switch acknowledges the binding request, then the header field identifier is used to identify the header field type in messages (e.g., control messages, etc.) transmitted to the SDN switch.