B.8 Example analysis for HLR

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

1. An HLR (in non-UDC Networks) stores user data (while no session is ongoing) and performs application logic, therefore step 1 is applicable.

2. An HLR (in non-UDC Networks) stores permanent user data provisioned at the HLR, therefore step 2 is applicable.

3. Outsourced HLR user data may be stored in a common UDR to allow access from any Provisioning-FE connected to the UDR. Step 3 is applicable.

4. Parallel sessions in two different HLR-FEs: It is believed that e.g. one HLR-FE could process a MAP-SendRoutingInfoForSM message while another HLR-FE processes a MAP-AnyTimeInterrogation message for the same user at the same time. This in general holds for all HLR-FE session initiating messages. Furthermore the duration of an HLR-FE session in general is in the range of seconds or minutes rather than hours or days. The transaction mechanism supported on the Ud interface is suitable to address data synchronization.

Step 4 is applicable.

In summary all steps are applicable and provide the full benefits of the UDC concept.