IP FPM Applications on Seamless MPLS

Networking Description

Seamless MPLS supports highly flexible deployment and high scalability. LSPs established among nodes allow for service rollouts or node addition between any two nodes. In a seamless MPLS scenario, IP FPM can be performed in either per-node proactive or on-demand mode to measure service performance. Therefore, IP FPM monitors per-hop packet loss and delay, which helps locate faults.

Figure 1 Seamless MPLS solution networking

Seamless MPLS allows a BGP LSP to be established across the access, aggregation, and core layers, implementing E2E service transmission. An LSP is established between each pair of nodes on a network to transmit upstream and downstream traffic. Such a network architecture maximizes service scalability. Only signaling needs to be configured on a service access point for all services. The same transport-layer convergence technique is used to handle network-side faults, whereas the service layer does not need to discern the faults.

Feature Deployment

On the Seamless MPLS shown in Figure 1, various carriers may operate the transport network between CSG and MASG and the wireless networks between NodeBs/eNodeBs and CSG and between MASG and MME/SGW. The transport network quality, as indicated by the packet loss rate, delay, and jitter, also affect the wireless service quality. This requires that the transport network carrier use reliable performance measurement measures to monitor the transport network. When the wireless service quality deteriorates, the transport network carrier can promptly identify whether the fault has occurred on the transport network or wireless network using the transport network performance data.

The following example uses the application of IP FPM in the intra-Seamless MPLS scenario.

**Table 1** IP FPM deployment
Seamless MPLS Solution	IP FPM Deployment
Intra-Seamless MPLS	Deploy an MCP: If routes are reachable over the entire transport network, deploy an MCP on any of CSG1, AGG1, AGG2, Core ABR1, Core ABR2, MASG1, and MASG2. Deploying an MCP on MASG1/MASG2 is recommended. If routes are reachable only within areas on the transport network, CSG1 does not have a route to MASG1/MASG2. Therefore, deploy an MCP on AGG1/AGG2. Deploy a DCP: When performance measurement is implemented for end-to-end services, IP FPM runs on the edge devices of the transport network. Therefore, deploy DCPs on CSG1, MASG1, and MASG2. When performance measurement is implemented for local switching services, deploy a DCP on CSG1. Deploy a TLP: When performance measurement is implemented for end-to-end services, IP FPM runs on the edge devices of the transport network. Therefore, deploy a TLP on CSG1 and bind the TLP to the user-side interface on CSG1, and deploy TLPs on MASG1 and MASG2 and bind the TLPs to user-side interfaces on MASG1 and MASG2. When performance measurement is implemented for local switching services, deploy a TLP on CSG1 and bind it to the user-side interface.