Page 491 - 5G Basics - Core Network Aspects

Core network aspects 1

Table 16 – Resource re-provisioning request (HDC-FE → PD-FE)

Information element Explanation

Persistent IP address information A set of IP address information used for locating the mobile UE.
– Unique IP address The persistent IP address allocated to the attached mobile UE.
– Address realm The addressing domain in which the IP address is significant.
Transport user identifier (conditionally The user/UE identifier authenticated for attachment.
mandatory) (Note)
Temporary IP address information A set of IP address information used for locating the access network to
which the UE is attached. In the host-based mobility case this is the
temporary address. In the network-based mobility case it is the address
of the lower tunnel end point.

– Unique IP address The temporary IP address allocated to the attached mobile UE.
– Address realm The addressing domain in which the IP address is significant.
Operation type Indication of resource reservation operation type:
resource reservation or resource release.
Gateway Address (optional) The address of ABG-FE/IBG-FE containing the anchor point.

NOTE – Transport user identifier is required if either persistent or temporary address is private.

Table 17 – Resource re-provisioning response (PD-FE → HDC-FE)

Information element Explanation
Transport user identifier The user/UE identifier authenticated for attachment.
Persistent IP address information A set of IP address information used for locating the mobile UE.

– Unique IP address The persistent IP address allocated to the attached mobile UE.
– Address realm The addressing domain in which the IP address is significant.
Status The status of operation.
It is assumed that RACF retains the binding between persistent address and the QoS resources allocated to
sessions associated with the UE.

6.5.9 Reference point M9 between MLM-FE(P) and MLM-FE(C)

6.5.9.1 Mobility location binding registration/update request
This information flow is used to register and update mobility location information in both the host-based and
network-based mobility cases. In the network-based mobility case, the MLM-FE(P) will send the location
registration/update request to the MLM-FE(C). In the host-based mobility case, the UE will send the location
registration/update request to the MLM-FE(P), which will pass it on to the MLM-FE(C).
The mobility service subscriber ID and information providing the location binding between the persistent
location identifier and the location of the MLM-FE(P) are included in the messages for both host-based and
network-based mobility.
Reference point M9 supports two primitives for this operation:
• mobility location binding registration/update request (Table 18);

• mobility location binding registration/update response (Table 19).

481