Figure 4.1-1 | UDC reference architecture |
Figure 4.1-2 | Comparison Non-UDC Network to UDC Network |
Figure 5.1-1 | General UDC Information Flow |
Figure 5.3-1 | Query data procedure |
Figure 5.4-1 | Create Data flow |
Figure 5.5-1 | Delete Data flow |
Figure 5.6-1 | Update data procedure |
Figure 5.7-1 | Subscription procedure |
Figure 5.8-1 | Notification procedure |
Figure A.1.2-1 | CS terminating call example with Ud Query from HLR-FE |
Figure A.1.3-1 | IMS re-registration flow example with Ud Query from HSS-FE |
Figure A.2.2-1 | CS location update with Ud Update from HLR-FE |
Figure A.2.3-1 | IMS service data change information flow example with Ud Update from HSS-FE |
Figure A.3.2-1 | Subscription over Sh with Ud subscription from HSS-FE |
Figure A.4.2-1 | IMS service data change information flow example with Ud notification towards HSS-FE |
Figure A.4.3-1 | Notification over Sh without Ud notification |
Figure A.4.4-1 | Notification over Sh with Ud notification |
Figure A.4.5-1 | Notification over Sh without Ud notification - Subscription expired |
Figure A.4.6-1 | Notification over Sh with Ud notification |
Figure B.3.1-1 | Separating User Data from Application Logic |
Figure B.4.1-1 | Introducing Provisioning FEs |
Figure B.5.1-1 | Storing outsourced user data in a logically single UDR |
Figure B.5.1-2 | Storing outsourced user data in a logically single UDR |
Figure B.6.1-1 | Full Load Sharing and Failover functionality |
Figure B.7.1-1 | Converging user data in the UDR |