Abstract: Base stations as well as Radio Access Network (RAN) controllers have embedded communication agents that are responsible from control messaging between these entities that enable creation and management of RAN Slices. At a given time, it is possible that multiple active RAN slices co-exist on the same base station, where each RAN slice may run its own scheduler, its own admission control and have its own handoff management parameter values.

Abstract: Base stations as well as Radio Access Network (RAN) controllers have embedded communication agents that are responsible from control messaging between these entities that enable creation and management of RAN Slices. At a given time, it is possible that multiple active RAN slices co-exist on the same base station, where each RAN slice may run its own scheduler, its own admission control and have its own handoff management parameter values.

Abstract: Base stations as well as Radio Access Network (RAN) controllers have embedded communication agents that are responsible from control messaging between these entities that enable creation and management of RAN Slices. At a given time, it is possible that multiple active RAN slices co-exist on the same base station, where each RAN slice may run its own scheduler, its own admission control and have its own handoff management parameter values.

Abstract: Base stations as well as Radio Access Network (RAN) controllers have embedded communication agents that are responsible from control messaging between these entities that enable creation and management of RAN Slices. At a given time, it is possible that multiple active RAN slices co-exist on the same base station, where each RAN slice may run its own scheduler, its own admission control and have its own handoff management parameter values.

Abstract: Base stations as well as Radio Access Network (RAN) controllers have embedded communication agents that are responsible from control messaging between these entities that enable creation and management of RAN Slices. At a given time, it is possible that multiple active RAN slices co-exist on the same base station, where each RAN slice may run its own scheduler, its own admission control and have its own handoff management parameter values.

Abstract: A novel (software defined network) SDN control plane is introduced having new system capabilities to activate and deactivate controllers in real-time upon automatic measurement of network control traffic and service requirements, and proper controller interactions with network switches as control plane topology changes. Also introduced is a control flow table, which defines the assignment of certain control flows (by originator, location, service type, etc.) to different controllers within the SDN.

Abstract: A method to check health of automatically discovered controllers comprises the steps of: (a) a first controller generating a first Controller-Advertisement message carrying the information required to identify and access the first controller when a new switch port becomes active; (b) the first controller sending the generated first Controller-Advertisement to a first switch having the newly activated port; (c) the first controller receiving at least a second Controller-Advertisement message from at least a second controller; (d) the first controller generating a third unsolicited Controller-Advertisement message with its access information to check health of the second controller; (e) the first controller receiving at least a fourth Controller-Advertisement message from the second controller indicating health information of the second controller, wherein the health information is stored in first controller's Controller Information Base (CIB).

Abstract: A novel (software defined network) SDN control plane is introduced having new system capabilities to activate and deactivate controllers in real-time upon automatic measurement of network control traffic and service requirements, and proper controller interactions with network switches as control plane topology changes. Also introduced is a control flow table, which defines the assignment of certain control flows (by originator, location, service type, etc.) to different controllers within the SDN.

Abstract: A method to check health of automatically discovered controllers comprises the steps of: (a) a first controller generating a first Controller-Advertisement message carrying the information required to identify and access the first controller when a new switch port becomes active; (b) the first controller sending the generated first Controller-Advertisement to a first switch having the newly activated port; (c) the first controller receiving at least a second Controller-Advertisement message from at least a second controller; (d) the first controller generating a third unsolicited Controller-Advertisement message with its access information to check health of the second controller; (e) the first controller receiving at least a fourth Controller-Advertisement message from the second controller indicating health information of the second controller, wherein the health information is stored in first controller's Controller Information Base (CIB).

Abstract: Controllers in a Software Defined Network (SDN) automatically discover and authenticate each other as part of the control plane operations, without any need for manual configuration of other controllers. The new capability of such controllers is based on Controller-Advertisement messages transferred between controllers in the same or different SDNs. In doing so, multiple controllers can be used for load sharing, improved reliability under failure of a controller by enabling seamless take over and recovery. Moreover, controllers can cooperate to enable end-to-end services to work across multiple SDNs. Controller-Advertisement messages are also used to check the health statuses of discovered controllers in the same or different SDNs.

Abstract: Controllers in a Software Defined Network (SDN) automatically discover and authenticate each other as part of the control plane operations, without any need for manual configuration of other controllers. The new capability of such controllers is based on Controller-Advertisement messages transferred between controllers in the same or different SDNs. In doing so, multiple controllers can be used for load sharing, improved reliability under failure of a controller by enabling seamless take over and recovery. Moreover, controllers can cooperate to enable end-to-end services to work across multiple SDNs. Controller-Advertisement messages are also used to check the health statuses of discovered controllers in the same or different SDNs.