Page 497 - 5G Basics - Core Network Aspects

Core network aspects 1

phases: (pre-)authentication and (pre-)authorization, IP address configuration, mobility location
management, and transport location management.

UE AM-FE TAA-FE NAC-FE TLM-FE TAA-FE TUP-FE RACF SCF MLM-FE HDC-FE MLM-FE Mobile
proxy server proxy NID-FE central AAA
1.1
1.2
1.3
1.4
1. (Pre) authentication
and (pre) authorization 1.5
1.6
1.7
Split scenario only 1.8
1.9 1.10
1.11

2.1
2.2
2.3
2.4
2. IP configuration
2.5
2.6 Indication of host-based mobility (Table 1)
2.7 Network selection key transfer indication (Table 3)
2.8 Network selection key transfer indication (Table 27)
2.9
2.10

3.1 Mobility location binding update (Table 4)
3.2 Handover indication (Table 22)
3.3 Mobility location binding registration
3. Mobility location /update request (Table 18) (if reqd)
management
3.4 Mobility location binding registration
/update response (Table 19)
3.5 Mobility location binding acknowledgement (Table 5)

4.1
4. Transport location
management 4.2

Y.2018(09)_F05

Figure 5 – Information flows for attachment in the case of host-based mobility
Phase 1: (Pre-)authentication and (pre-)authorization

The procedure is as described in clause II.1, numeral 1) of [ITU-T Y.2014], with the following modifications:
1.1 In its attachment request, the UE indicates that it requires mobility services, and may indicate
whether it supports host-based and/or network-based mobility. In the split scenario, it provides its
mobility service credentials either at this stage or at a later stage (not shown) in an additional
dialogue with the TAA-FE (proxy) before step 1.7.
1.2 The AM-FE forwards the additional mobility-related information provided by the UE to the TAA-FE
along with the information defined in [ITU-T Y.2014].
1.3-1.4 No change from [ITU-T Y.2014].
1.5 In the integrated scenario, the TUP-FE returns mobility service parameters as well as the user
transport profile.
After successful authentication, the entities in the home network may allocate a persistent IP
address for the mobile node (e.g., using a DHCP server) based on the mobile user location

487