ed Planning Parameter Default result subanalysis Result_subanalysis Parameter Default result subanalysis Result_subanalysis Parameter Default result subanalysis Result_subanalysis Parameter Default result subanalysis Final result Figure 4.33 User plane analysis structure origin analysis; preanalysis/extended preanalysis; end of selection analysis/end of selection attribute analysis; routing attribute analysis; digits analysis; charging analysis, etc. Configuring User Plane Resources in the MSS Creating external TDM resources is only applicable in an integrated MSS. ATM and IP resources are not directly configured in the MSS. The related source data templates are circuit groups, routes and special routes. Creating an MGW Database in the MSS The MGW database is a common storage place in the MSS for MGW specific parameters that are used for user plane routing purposes. In the routing configuration the physical resources (i.e. the TDM) are hunted in the MSS, while the ephemeral resources (i.e. IP and AAL2) are hunted in the MGW. This requires that the MSS must have knowledge of the physical resources connected to the MGW. After successful registration of the MGW, the MSS requests the capabilities of the MGW via the auditing process (such capabilities are, for instance, termination Ids of ephemeral resources, supported Core Network Planning and Optimisation H.248 Interconnection Figure 4.34 User plane topology information packages and supported codecs which are stored in MGW database). The MGW can be registered to different MSSs, but only to one MSS at a time. However, it is possible to divide the MGW into several virtual MGWs that can be connected to a single MSS. This is recommended in the case where the network load is high. The MSS controls the resources in the MGW by using the H.248 MEGACO protocol. Therefore creating the MGW database will give the details of the MGWs that are connected to the MSS. The related source data template is the MGW creation. Configuring User Plane Routing and Topology in the MSS The use