Network operating system with distributed data architecture
View Patent ↗A network operating system NOS for an agile optical network with a plurality of mesh interconnected switching nodes, manages the network using an object-oriented network information model. The model is common to all applications requiring the data stored in the network managed information base. The core model can be expanded for serving specific application areas. The NOS is organized in layers, at the optical module level, connection level and network level. A distributed topology server DTS organizes the physical, logical and topological data defining all network entities as managed objects MO and topology objects TO for constructing a complete network view. The network information model associates a network element NE information model, specified by managed objects MO and a topological information model, specified by topology objects TO. The MOs are abstract specific NE data that define network implementation details and do not include any topological data, while the TOs abstract specific topological data for defining a trail established within the network, and do not include any NE data. The models are associated in a minimal number of points to construct the model of a trial in response to a connection request.
1. A method for modeling a call in an agile optical network comprising:
receiving a connection request specifying a source node, a destination node, and a class of service CoS;
creating a call identifier (ID) for identifying said call, and a trail ID for identifying a trail beginning at said source node and ending at said destination node, and requesting regenerator locations and nodes along said trail;
reserving said trail, said reserving comprising;
reserving a trail termination point (TTP) object at each said source and destination node, including storing said trail ID in each TTP object; and
activating said trail for establishing said call over said trail.
2. A method for modelling a call in an agile optical network comprising:
receiving a connection request specifying a source node, a destination node, and a class of service CoS;
creating a call identifier (ID) for identifying said call, and a trail ID for identifying a trail beginning at said source node and ending at said destination node, and requesting regenerator locations and nodes along said trail;
at each switching node along said trail, receiving an “activate cross connection” request;
detecting in said network information model associations between a CTP topology object and a CTP managed object;
creating a subnetwork connection SNC across a cross-connect network object between said CTP managed objects;
associating cross-connection objects along said trail with the respective SNC; and
setting an UsageState attribute to “busy” for said SNC topological objects, CTP objects and TTP managed objects;
reserving said trail; and
activating said trail for establishing said call over said trail.
3. A system comprising:
a network services control platform operable to,
receive a connection request specifying a source node, a destination node, and a class of service CoS,
create a call identifier (ID) for identifying said call, and a trail ID for identifying a trail beginning at said source node and ending at said destination node, and requesting regenerator locations and nodes along said trail,
reserve said trail by reserving a trail termination point (TTP) object at each said source and destination node, including storing said trail ID in each TTP object; and
activate said trail for establishing said call over said trail.
4. The system as claimed in claim 3 , wherein the platform is further operable to:
reserve connection termination points (CTP) topology objects along said trail by storing said call ID at each said CTP topology object, setting a UsageState attribute to “active” and incrementing a ReferenceCount attribute by 1;
create subnetwork connection (SNC) objects by binding the appropriate CTP topology objects along said trail and storing said trail ID at each said SNC object; and
reserve an explicit regenerator, if included in said connection request by issuing a “reserve” action on the appropriate regenerator pool object and using said trail ID as a reservation ID for said regenerator.
5. The system as claimed in claim 3 further comprising:
one or more switching nodes along said trail, wherein each node is operable to,
receive an activate cross connection request,
detect associations between a CTP topology object and a CTP managed object;
create a subnetwork connection SNC across a cross-connect network object between said CTP managed objects;
associate cross-connection objects along said trail with the respective SNC; and
set an UsageState attribute to “busy” for said SNC topological objects, CTP objects and TTP managed objects.
6. One or more computing platform memories for storing instructions used to model a call in an agile optical network, the instructions executable to:
receive a connection request specifying a source node, a destination node, and a class of service CoS;
create a call identifier (ID) for identifying said call, and a trail ID for identifying a trail beginning at said source node and destination node, and requesting regenerator locations and nodes along said trail;
reserve said trail by reserving a trail termination point (TTP) object at each said source and destination node, including storing said trail ID in each TTP object; and
activate said trail for establishing said call over said trail.
7. The one or more computing platform memories as in claim 6 further comprising instructions executable to:
reserve all connection termination points (CTP) topology objects along said trail by storing said call ID at each said CTP topology object, setting a UsageState attribute to “active” and incrementing a ReferenceCount attribute by 1;
create subnetwork connection (SNC) objects by binding the appropriate CTP topology objects along said trail and storing said trail ID at each said SNC object; and
reserve an explicit regenerator, if included in said connection request by issuing a “reserve” action on the appropriate regenerator pool object and using said trail ID as a reservation ID for said regenerator.
8. The one or more computing platform memories as in claim 6 , wherein each computing platform memory comprises at least one optical switch controlling element located at each switching node along said trail and each of the optical switch controlling elements further comprising instructions executable to:
receive an “activate cross connection” request;
detect in said network information model all associations between a CTP topology object and a CTP managed object;
create a subnetwork connection SNC across a cross-connect network object between said CTP managed objects;
associate all cross-connection objects along said trail with the respective SNC; and
set an UsageState attribute to “busy” for all said SNC topological objects, CTP objects and TTP managed objects.
9. The method as claimed in claim 1 further comprising:
reserving connection termination points (CTP) topology objects along said trail, including storing said call ID at each said CTP topology object.
10. The method as claimed in claim 9 wherein reserving connection termination points (CTP) topology objects along said trail includes storing said call ID at each said CTP topology object, setting a UsageState attribute to “active” and incrementing a ReferenceCount attribute by 1 .
11. The method as claimed in claim 1 further comprising
creating subnetwork connection (SNC) objects, including binding the appropriate CTP topology objects along said trail and storing said trail ID at each said SNC object.
12. The method as claimed in claim 1 further comprising
creating subnetwork connection (SNC) objects by binding the appropriate CTP topology objects along said trail and storing said trail ID at each said SNC object; and
reserving an explicit regenerator, if included in said connection request by issuing a “reserve” action on the appropriate regenerator pool object and using said trail ID as a reservation ID for said regenerator.
13. The method as claimed in claim 12 wherein reserving connection termination points (CTP) topology objects along said trail includes storing said call ID at each said CTP topology object, setting a UsageState attribute to “active” and incrementing a ReferenceCount attribute by 1 .
14. A method for modeling a call in an agile optical network comprising:
receiving a connection request specifying a source node, a destination node, and a class of service CoS;
creating a call identifier (ID) for identifying said call, and a trail ID for identifying a trail beginning at said source node and ending at said destination node, and requesting regenerator locations and nodes along said trail;
reserving an explicit regenerator, if included in said connection request, by issuing a “reserve” action on the appropriate regenerator pool object and using said trail ID as a reservation ID for said regenerator
reserving said trail, and
activating said trail for establishing said call over said trail.
15. The method as claimed in claim 14 , further comprising
reserving connection termination points (CTP) topology objects along said trail, including storing said call ID at each said CTP topology object.
16. The method as claimed in claim 14 , further comprising reserving a trail termination point (TTP) object at each said source and destination node, including storing said trail ID in each TTP object.