Optical wavelength switching (or circuit switching) on the otherhand is now becoming available and is an attractive alternativein high capacity backbone networks. By using mixed-technology, multi domain networks the advantages of differenttechnologies can be combined. What is lacking is a unifiedcontrol system, which is exactly what GMPLS provides. I.e., theintegration of MPLS and GMPLS with these circuit-switchedsystems is advantageous because is offers:
Traffic engineering capabilities,
High capacity core
Flexible, controllable edge
Protocol independence (i.e., e.g. IP interoperability)
Real GMPLS networks are highly complex and may coverdevices such as optical wavelength switches and SONETnetwork nodes, i.e. GMPLS can operate with as well electronicas optical technologies. Hence, GMPLS networks can get verycomplex since a multitude of technologies are hidden there,implying a vast number of protocols, devices and configurationoptions.The real-life network must be simplified greatly in order to beable to build a model that can produce results within anacceptable timeframe. A brute-force modeling methodology that just tries to model the real network in every detail isinappropriate. Below the goals for the simulation are identifiedand based on that the simplified simulation model can be set up.Obviously, the model must be simple enough to achieve theidentified goals, while representing a fair model of the realnetwork.
Requirements to the model
The goal of this simulation study is to build a model of howGMPSL interacts with an MPL S based network. With the modelit should be possible to measure/study:
Call setup probability
Optical signal quality
Network topology / routing issuesA list of input parameters is provided below:
Topology generation parameters- Number of nodes- Number of links- Maximum distanceSize and connectivity of thenetwork Path constraints Bandwidth constraintsType of network SONET / pure optical
The GMPLS implementation has been made with OPNETmodeler 8.0 and the MPLS model suite. The MPLS model hasbeen extended/modified in order to create a GMPLS network element that can be built into MPLS network. This GMPLSmodels element represents the entire GMPLS network, i.e. acomplete topology can be built with this single node. Figure 4illustrates how the GMPLS network can interoperate with MPLSdevices, i.e., LSPs can be setup through the GMPLS domain inthis mixed environment. .
Figure 4: A GMPLS model, which can interoperate withMPLS, has been built into OPNET.
A number of modification to the OPNET MPLS models areneeded. As well the user as the control plane need to bemodified.Modification needed:
control plane (path/LSP setup)
Interacts with the label distribution protocol
Setup / tear down of connections
Path constraints handling
data plane (packet forwarding)
Interacts with the label swap/push/pop operations
Signal degradation (for all-optical networks)
More details of the implemented model.
In order to minimize the modifications needed in the OPNETcode, GMPLS has been implemented as a separate processwithin the network nodes. The LDP process has then just beenmodified to detect whether this GMPLS process is present or not(and hence whether this is a MPLS or GMPLS node)
Figure 5: GMPLS has been implemented as a separateprocess in the MPLS node model
The details of the process model is shown below (figure 6)