Page 486 - 5G Basics - Core Network Aspects
P. 486

1                                                Core network aspects


                     Information element                                 Explanation
             RACF contact point (optional)      The FQDN or IP address of the RACF entity where resource requests shall
                                                be sent (i.e., PD-FE address).
             Anchor point address (optional)    The upper tunnel end point address, from the point of view of the UE.
             NOTE 1 – Either the UE identifier or the persistent IP address must be present.
             NOTE 2 – If the tunnel end-point address is statically provisioned or the MLM-FE can obtain it with its own
             mechanisms, this information is not required.

            6.5.2   Reference point M2 between TLM-FE and HDC-FE

            This  information  flow  provides  the  keying  material  derived  from  the  UE  authentication  procedure  (see
            clause 7.3.2), in support of the security association required between the HDC-FE and the UE. This security
            association is required for the ongoing network selection and decision process subsequent to attachment.
            Reference point M2 supports the "network selection key transfer indication" primitive, as shown in Table 3.


                            Table 3 – Network selection key transfer indication (TLM-FE → HDC-FE)

                     Information element                                 Explanation

             Mobility service subscriber identifier   The user/UE identifier authenticated for mobility services. This will be
                                                the same as the transport subscriber identifier in the integrated scenario.
             Keying material                    The material used for security association between the UE and HDC-FE.

            6.5.3   Reference point M3 between UE and MLM-FE(P)

            This information flow is used by the UE to register and update its mobility location information in the case of
            host-based mobility management. Reference point M3 supports the following primitives:

            •       mobility location binding update, shown in Table 4;
            •       mobility location binding acknowledgement, shown in Table 5.
            It is a requirement that mobility signalling between the UE and the MLM-FE(P) shall be protected by a security
            association. For more details see clause 8.


                                Table 4 – Mobility location binding update (UE → MLM-FE(P))

                     Information element                                 Explanation
             Mobility  service  subscriber  identifier  The user/UE identifier authenticated for mobility services. This will be the
             (Note)                             same as the transport subscriber identifier in the integrated scenario.
             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.
             Temporary IP address information   A set of IP address information used for locating the access network to
                                                which the UE is attached.
               – 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.
             NOTE – Subscriber identifier is required if either persistent or temporary address is private.












            476
   481   482   483   484   485   486   487   488   489   490   491