B.6 Step 4 –Full Load Sharing and Failover functionality

23.3353GPPRelease 17Stage 2Technical realization and information flowsTSUser Data Convergence (UDC)

What is said for the provisioning FEs in step 3, in theory also holds for other node-FEs: Node-FE 2 could access via Ud not only its own outsourced data, but also data sourced out by Node-FE 1. However, careful analysis is needed before deciding the cases in which "cross data accessibility" should be allowed. The main point to consider is whether or not parallel sessions in different FEs result in problems.

If routing mechanisms used on the network interfaces allow configuration of alternative routes to address e.g. load sharing, link loss or node outage, and parallel sessions in different FEs are not regarded a problem, FEs of the same application type could share load or could take over in cases of node-FE outage.

Figure B.6.1/1: Full Load Sharing and Failover functionality

This step does not impact FE or UDR implementation but is a routing configuration issue outside the UDC. Furthermore, this step – although it provides great advantages – is believed not to be essential to the UDC concept. Deployments may or may not take advantage of this step if applicable. Non-applicability of this step is not a knock-out criterion for the decision on applicability of the UDC concept for a given node.