MOBILITY SERVICE CLUSTERING USING NETWORK SERVICE SEGMENTS
First Claim
Patent Images
1. An apparatus, comprising:
- a communication interface; and
logic configured to receive data from the communication interface;
wherein the logic is configured to acquire data representative of at least one Mobility Service Engine cluster slave belonging to a mobility service cluster via the communication interface;
wherein the logic is configured to acquire physical layout data for a network; and
wherein the logic is configured to form at least one network service segment based on the physical layout data, the network service segment is a cohesive grouping that provides at least one mobility service cluster across a set of related infrastructure nodes;
wherein the mobility service cluster provides service to a first area, a second area, and a third area where a first part of the third area overlaps the first area and a second part of the third area overlaps the second area;
wherein the logic is configured to form a first network service segment for providing the service for the first area, a second network service segment for providing the service to the second area, and a third network service segment for providing the service to the third areawherein the logic determines the load for the first network service segment, the second network service segment and the third network service segment;
wherein the logic assigns the first network service segment to one of a first of the at least one Mobility Service Engine cluster slave and a second the at least one Mobility Service Engine cluster slave, the second network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave and the third network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave; and
wherein the logic assigns the first network service segment, second network service segment and third network service segment in a manner that best balances a load between the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave.
0 Assignments
0 Petitions
Accused Products
Abstract
Described in an example embodiment herein is a Mobility Service Engine (MSE) cluster comprising an MSE Cluster Master and at least one MSE Cluster Slave. The MSE Master is configured to define Network Service Segments. The MSE Master of the cluster distributes the Network Service Segments to slaves within the cluster. The network is configured to forward data to the correct Network Service Segment.
-
Citations
20 Claims
-
1. An apparatus, comprising:
-
a communication interface; and logic configured to receive data from the communication interface; wherein the logic is configured to acquire data representative of at least one Mobility Service Engine cluster slave belonging to a mobility service cluster via the communication interface; wherein the logic is configured to acquire physical layout data for a network; and wherein the logic is configured to form at least one network service segment based on the physical layout data, the network service segment is a cohesive grouping that provides at least one mobility service cluster across a set of related infrastructure nodes; wherein the mobility service cluster provides service to a first area, a second area, and a third area where a first part of the third area overlaps the first area and a second part of the third area overlaps the second area; wherein the logic is configured to form a first network service segment for providing the service for the first area, a second network service segment for providing the service to the second area, and a third network service segment for providing the service to the third area wherein the logic determines the load for the first network service segment, the second network service segment and the third network service segment; wherein the logic assigns the first network service segment to one of a first of the at least one Mobility Service Engine cluster slave and a second the at least one Mobility Service Engine cluster slave, the second network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave and the third network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave; and wherein the logic assigns the first network service segment, second network service segment and third network service segment in a manner that best balances a load between the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A method, comprising:
-
acquiring data representative of at least one Mobility Service Engine cluster slave belonging to a mobility service cluster via the communication interface; acquiring physical layout data for a network; forming at least one network service segment based on the physical layout data, the network service segment is a cohesive grouping that provides at least one mobility service cluster across a set of related infrastructure nodes wherein the mobility service cluster provides service to a first area, a second area, and a third area where a first part of the third area overlaps the first area and a second part of the third area overlaps the second area; and forming a first network service segment for providing the service for the first area, a second network service segment for providing the service to the second area, and a third network service segment for providing the service to the third area determining a load for the first network service segment, the second network service segment and the third network service segment; assigning the first network service segment to one of a first of the at least one Mobility Service Engine cluster slave and a second the at least one Mobility Service Engine cluster slave, the second network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave and the third network service segment to one of the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave; and assigning the first network service segment, second network service segment and third network service segment in a manner that best balances a load between the first the at least one Mobility Service Engine cluster slave and the second the at least one Mobility Service Engine cluster slave. - View Dependent Claims (13, 14, 15, 16, 17, 18)
-
-
19. An apparatus, comprising:
-
a communication interface; and logic configured to receive data from the communication interface; wherein the logic determines a mobility service engine slaves belonging to a cluster; wherein the logic determines all devices managed by the cluster, the devices managed by the cluster comprising a first mobility service engine cluster slave, a second mobility service cluster slave, a first controller in communication with the first mobility service engine cluster slave, and a second controller in communication with the first mobility service engine cluster slave and the second mobility service engine cluster slave; wherein the logic acquires data representative of a physical layout, the data representative of the physical layout comprising data representative of an area serviced by each of the devices managed by the cluster; wherein the logic receives radio frequency neighbor environment data from controllers associated with the cluster via the communication interface; wherein the logic forms a plurality of network service segments for the cluster based on the radio frequency environment, wherein a network service segment is a cohesive grouping that provides at least one mobility service across a set of related infrastructure nodes; wherein the logic assigns each of the plurality of network service segments to not more than one of the mobility service engine slaves that comprises assigning a selected one network service segment selected from the plurality network service segment to a cluster slave selected from the group consisting of the first mobility service engine cluster slave and the second mobility service engine cluster slave to service; and wherein the logic communicates a routing path to controllers having infrastructure nodes belonging to the selected one network service segment via the communication interface. - View Dependent Claims (20)
-
Specification